# Overdue Maintenance Orders and Backlog by Work Center Report

> A custom ALV report that lists open maintenance orders past their basic finish date with days late and remaining work hours, and calculates how many weeks of backlog each work center carries. The maintenance manager sees which team is behind and which high-priority job is waiting, on one screen.

- Type: Report, Custom development, ALV report
- Module: PM
- Estimated effort: S (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/overdue-maintenance-orders-and-backlog-report/


## Why is the standard not enough?

The IW38 and IW39 order lists show basic dates, but they do not calculate days late since the finish date, remaining work hours or how many weeks of backlog each work center carries. The IW37N operation list shows remaining work but not the delay or the ratio to capacity. The backlog indicator is usually built every week by merging two lists in Excel.

### Closest standard alternatives

- IW38: The order list has the dates; no days late, remaining work or backlog weeks.
- IW37N: Shows remaining work per operation; no delay and no ratio to capacity.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| AUFK | Order type, short text and object number (driving table) | Read | - | ECC + S/4 |
| AFIH | Planning plant, planner group, priority, equipment and main work center | Read | AFIH-AUFNR = AUFK-AUFNR | ECC + S/4 |
| AFKO | Basic start and finish dates, routing number | Read | AFKO-AUFNR = AUFK-AUFNR | ECC + S/4 |
| AFVC | Order operations | Read | AFVC-AUFPL = AFKO-AUFPL | ECC + S/4 |
| AFVV | Planned and actual work hours | Read | AFVV-AUFPL = AFVC-AUFPL AND AFVV-APLZL = AFVC-APLZL | ECC + S/4 |
| CRHD | Main work center code | Read | CRHD-OBJTY = 'A' AND CRHD-OBJID = AFIH-GEWRK | ECC + S/4 |
| JEST | Active system statuses | Read | JEST-OBJNR = AUFK-OBJNR | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | AFIH-IWERK | Yes |
| S_INGPR | Planner group | Range / multiple | AFIH-INGPR | No |
| S_ARBPL | Main work center | Range / multiple | CRHD-ARBPL | No |
| S_AUART | Order type | Range / multiple | AUFK-AUART | No |
| S_PRIOK | Priority | Range / multiple | AFIH-PRIOK | No |
| S_ILART | Maintenance activity type | Range / multiple | AFIH-ILART | No |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes |
| P_WKHRS | Default weekly capacity (hours per work center) | Single value | - | No |
| P_OVERDU | Overdue only | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Maintenance order | AUFK-AUFNR |
| Order type | AUFK-AUART |
| Short text | AUFK-KTEXT |
| Equipment | AFIH-EQUNR |
| Priority | AFIH-PRIOK |
| Main work center | CRHD-ARBPL |
| Basic start | AFKO-GSTRP |
| Basic finish | AFKO-GLTRP |
| Days late | Calculated: Key date − AFKO-GLTRP |
| Planned work (h) | Calculated: Σ AFVV-ARBEI, converted to hours |
| Actual work (h) | Calculated: Σ AFVV-ISMNW, converted to hours |
| Remaining work (h) | Calculated: Planned work − actual work (at least 0) |
| Work center backlog (weeks) | Calculated: Total remaining work of the work center ÷ weekly available hours |
| System status | Calculated: Texts of the active statuses in JEST |

## How does the report work?

1. Maintenance orders (AUTYP = 30) are read from AUFK, and planning plant (IWERK), planner group (INGPR), priority (PRIOK), maintenance activity type (ILART), equipment and main work center (GEWRK) from AFIH. Orders with CRTD or REL and without active TECO (I0045), CLSD (I0046) or deletion flag (I0076) in JEST remain.
2. Days late = key date − AFKO-GLTRP. With overdue only selected, only positive values remain.
3. Operations are read from AFVC and AFVV through AFKO-AUFPL. Planned work AFVV-ARBEI, actual work AFVV-ISMNW; the unit AFVV-ARBEH is converted to hours. Remaining work = ARBEI − ISMNW, at least zero.
4. The main work center code is found with AFIH-GEWRK = CRHD-OBJID. Backlog (weeks) = total remaining work of all open orders of the work center ÷ weekly available hours (from the work center capacity; the default on the selection screen when not defined).
5. ALV shows subtotals per work center and priority; overdue priority 1 orders are highlighted.

## Authorization objects

- I_IWERK: Display orders by maintenance planning plant
- I_AUART: Authorization by maintenance order type

## Frequently asked questions

### How should backlog weeks be read?

The value shows how many weeks the work center needs to finish its open work without taking new jobs. In maintenance management 2–4 weeks is usually seen as healthy; a very low value means idle capacity, a very high value means accumulated risk.

### Can orders waiting for material be separated?

Yes. Orders waiting for material can be flagged in a separate column through a user status or an open reservation check; for detailed tracking, the Maintenance Orders Waiting for Material report is used.

### Does it work on S/4HANA?

Yes. AUFK, AFIH, AFKO, AFVC and AFVV keep the same structure in S/4HANA. For a clean core approach, CDS views such as I_MaintOrderOperationData can be used.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pm-overdue-maintenance-orders-backlog
