Overdue Maintenance Orders and Backlog by Work Center Report
Short answer: 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.
- Estimated effort
- S · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Maintenance managers, maintenance planners, team leads and site managers.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| AUFKOrder Master Data | Order type, short text and object number (driving table) | — | ECC + S/4 |
| AFIHMaintenance Order Header | Planning plant, planner group, priority, equipment and main work center | AFIH-AUFNR = AUFK-AUFNR | ECC + S/4 |
| AFKOOrder Header Data for PP Orders | Basic start and finish dates, routing number | AFKO-AUFNR = AUFK-AUFNR | ECC + S/4 |
| AFVCOperation within an Order | Order operations | AFVC-AUFPL = AFKO-AUFPL | ECC + S/4 |
| AFVVQuantities, Dates and Values of Order Operations | Planned and actual work hours | AFVV-AUFPL = AFVC-AUFPL AND AFVV-APLZL = AFVC-APLZL | ECC + S/4 |
| CRHDWork Center Header | Main work center code | CRHD-OBJTY = 'A' AND CRHD-OBJID = AFIH-GEWRK | ECC + S/4 |
| JESTIndividual Object Status | Active system statuses | JEST-OBJNR = AUFK-OBJNR | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | AFIH-IWERK | Yes | 1000 |
| S_INGPR | Planner group | Range / multiple | AFIH-INGPR | No | M01 |
| S_ARBPL | Main work center | Range / multiple | CRHD-ARBPL | No | MEK-01 |
| S_AUART | Order type | Range / multiple | AUFK-AUART | No | PM01 |
| S_PRIOK | Priority | Range / multiple | AFIH-PRIOK | No | 1 |
| S_ILART | Maintenance activity type | Range / multiple | AFIH-ILART | No | 001 |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes | 17.11.2026 |
| P_WKHRS | Default weekly capacity (hours per work center) | Single value | — | No | 40 |
| P_OVERDU | Overdue only | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Maintenance order | AUFK-AUFNR |
| 2 | Order type | AUFK-AUART |
| 3 | Short text | AUFK-KTEXT |
| 4 | Equipment | AFIH-EQUNR |
| 5 | Priority | AFIH-PRIOK |
| 6 | Main work center | CRHD-ARBPL |
| 7 | Basic start | AFKO-GSTRP |
| 8 | Basic finish | AFKO-GLTRP |
| 9 | Days late | Calculated Key date − AFKO-GLTRP |
| 10 | Planned work (h) | Calculated Σ AFVV-ARBEI, converted to hours |
| 11 | Actual work (h) | Calculated Σ AFVV-ISMNW, converted to hours |
| 12 | Remaining work (h) | Calculated Planned work − actual work (at least 0) |
| 13 | Work center backlog (weeks) | Calculated Total remaining work of the work center ÷ weekly available hours |
| 14 | System status | Calculated Texts of the active statuses in JEST |
Sample output
| Maintenance order | Order type | Short text | Equipment | Priority | Main work center | Basic start | Basic finish | Days late | Planned work (h) | Actual work (h) | Remaining work (h) | Work center backlog (weeks) | System status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 4000123 | PM01 | Press hydraulic leak | 10000045 | 2 | MEK-01 | 11/03/2026 | 11/05/2026 | 12 | 16 | 6 | 10 | 2.40 | Released, partially confirmed |
| 4000131 | PM02 | Compressor 2000-hour service | 10000078 | 3 | MEK-01 | 11/08/2026 | 11/10/2026 | 7 | 24 | 0 | 24 | 2.40 | Released |
| 4000140 | PM01 | Conveyor motor failure | 10000102 | 1 | ELK-01 | 11/12/2026 | 11/13/2026 | 4 | 8 | 3 | 5 | 1.10 | Released, partially confirmed |
| 4000152 | PM03 | Panel thermal camera check | 10000110 | 3 | ELK-01 | 11/14/2026 | 11/15/2026 | 2 | 4 | 0 | 4 | 1.10 | Released |
How does the report work?
- 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.
- Days late = key date − AFKO-GLTRP. With overdue only selected, only positive values remain.
- 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.
- 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).
- ALV shows subtotals per work center and priority; overdue priority 1 orders are highlighted.
Performance notes
Narrow AFIH by planning plant and planner group; read operations once with FOR ALL ENTRIES on AFKO-AUFPL. The report can run in the background before the morning meeting and be distributed by email.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the order number opens IW33.
- Export to Excel
- Runs as a background job
- Send the result by email Each planner group can receive its own overdue orders weekly.
Authorization objects
- I_IWERKDisplay orders by maintenance planning plant
- I_AUARTAuthorization 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.
Packages that include this solution
Maintenance KPI Pack
A pack that delivers the four core indicators of the monthly maintenance review with one plant, work center and equipment selection: maintenance …
Related reports
Open Maintenance Notifications Without Order Aging Report
A custom ALV report that lists open notifications not yet converted to a maintenance order by age, priority and how far they are past the required end …
Maintenance Orders Waiting for Material with Purchase Tracking Report
A custom ALV report that shows, for every component of open maintenance orders, stock status, purchase requisition, purchase order, vendor and …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.