Open Maintenance Notifications Without Order Aging Report
Short answer: 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 date. Planners see in the daily meeting which request has been forgotten and which breakdown is waiting, on one screen.
- Estimated effort
- S · 2–3 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
IW28 and IW29 list notifications by status and date, but they do not calculate how many days notifications without an order have been waiting, how far they are past the required end or the age buckets. The status selection for notifications without an order has to be set up by hand every time. Planners age the list in Excel to prioritize waiting requests.
Who uses it? Maintenance planners, maintenance managers, shift supervisors and production supervisors.
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 |
|---|---|---|---|
| QMELNotification Header | Notification type, short text, priority, date and required end (driving table) | — | ECC + S/4 |
| QMIHNotification Maintenance Data | Planning plant, planner group, equipment and breakdown flag | QMIH-QMNUM = QMEL-QMNUM | ECC + S/4 |
| JESTIndividual Object Status | Notification system statuses | JEST-OBJNR = QMEL-OBJNR | ECC + S/4 |
| ILOAPM Object Location and Account Assignment | Functional location | ILOA-ILOAN = QMIH-ILOAN | ECC + S/4 |
| EQKTEquipment Short Texts | Equipment description | EQKT-EQUNR = QMIH-EQUNR AND EQKT-SPRAS = SY-LANGU | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | QMIH-IWERK | Yes | 1000 |
| S_QMART | Notification type | Range / multiple | QMEL-QMART | No | M1 |
| S_PRIOK | Priority | Range / multiple | QMEL-PRIOK | No | 1 |
| S_INGRP | Planner group | Range / multiple | QMIH-INGRP | No | M01 |
| S_EQUNR | Equipment | Range / multiple | QMIH-EQUNR | No | 10000045 |
| S_TPLNR | Functional location | Range / multiple | ILOA-TPLNR | No | TR01-URT-* |
| S_QMDAT | Notification date | Range / multiple | QMEL-QMDAT | No | 01.09.2026 – 17.11.2026 |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes | 17.11.2026 |
| P_BRKDN | Breakdowns only | Checkbox | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Notification | QMEL-QMNUM |
| 2 | Type | QMEL-QMART |
| 3 | Short text | QMEL-QMTXT |
| 4 | Equipment | QMIH-EQUNR |
| 5 | Equipment description | EQKT-EQKTX |
| 6 | Functional location | ILOA-TPLNR |
| 7 | Priority | QMEL-PRIOK |
| 8 | Planner group | QMIH-INGRP |
| 9 | Notification date | QMEL-QMDAT |
| 10 | Required end | QMEL-LTRMN |
| 11 | Age (days) | Calculated Key date − QMEL-QMDAT |
| 12 | Past required end (days) | Calculated Key date − QMEL-LTRMN (at least 0) |
| 13 | Breakdown | QMIH-MSAUS |
| 14 | Age bucket | Calculated 0–1, 2–7, 8–30 or 30+ days |
Sample output
| Notification | Type | Short text | Equipment | Equipment description | Functional location | Priority | Planner group | Notification date | Required end | Age (days) | Past required end (days) | Breakdown | Age bucket |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 10004521 | M2 | Press guard door sensor faulty | 10000045 | Hydraulic press 400 t | TR01-URT-PRS | 1 | M01 | 11/10/2026 | 11/11/2026 | 7 | 6 | X | 2–7 days |
| 10004498 | M1 | Compressor oil level low | 10000078 | Screw compressor 75 kW | TR01-YRD-KMP | 3 | M01 | 10/21/2026 | 10/31/2026 | 27 | 17 | 8–30 days | |
| 10004455 | M1 | Conveyor belt misalignment | 10000102 | Belt conveyor line 2 | TR01-URT-KNV | 2 | M02 | 09/30/2026 | 10/07/2026 | 48 | 41 | 30+ days | |
| 10004530 | M2 | Panel fan not running | 10000110 | Main distribution panel | TR01-ELK-ADP | 2 | M02 | 11/16/2026 | 11/18/2026 | 1 | 0 | X | 0–1 days |
How does the report work?
- Maintenance notifications with a blank order number (AUFNR) are read from QMEL; maintenance planning plant, planner group, equipment and breakdown flag are added from QMIH.
- Status is checked with JEST: outstanding (OSNO, I0068) or in process (NOPR, I0070) notifications remain; notifications with order assigned (ORAS, I0071), completed (NOCO, I0072) or deletion flag (I0076) are skipped.
- Age = key date − QMEL-QMDAT. Days past required end = key date − QMEL-LTRMN (zero when negative). Buckets: 0–1, 2–7, 8–30 and 30+ days.
- The equipment description is added from EQKT, the functional location through QMIH-ILOAN → ILOA-TPLNR.
- ALV is sorted by priority and age; breakdowns and notifications past the required end are highlighted.
Performance notes
Narrow QMEL by blank order number and notification date range, and QMIH by planning plant. Read JEST with FOR ALL ENTRIES on the object numbers of the selected notifications. The report usually runs in seconds.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the notification opens IW23; it can be converted to an order in IW22.
- Export to Excel
- Runs as a background job
- Send the result by email Notifications older than 30 days can be sent to the planner group weekly.
Authorization objects
- I_QMELDisplay maintenance notifications by notification type
- I_INGRPAuthorization by planner group
- I_SWERKDisplay by maintenance plant
Frequently asked questions
Do postponed notifications stay in the list?
By default postponed notifications are shown as well and flagged in a separate column. A checkbox that excludes them can be added to the selection screen if needed.
Is the age based on the notification date or the creation date?
By default the notification date (QMEL-QMDAT) is used; it is the day the problem was reported. The creation date can be added as an option during installation.
Does it work on S/4HANA?
Yes. QMEL, QMIH and JEST keep the same structure in S/4HANA. For a clean core approach, the I_MaintenanceNotification CDS view can be used.
Packages that include this solution
Maintenance Notification-to-Confirmation Pack
A five-component pack that speeds up maintenance work from notification to confirmation: open notifications without an order, mass maintenance order …
Related reports
MTBF and MTTR Reliability Report by Equipment
A custom ALV report that calculates, from breakdown notifications, the number of breakdowns, total downtime, mean time to repair (MTTR), mean time …
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 …
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.