# 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 date. Planners see in the daily meeting which request has been forgotten and which breakdown is waiting, on one screen.

- Type: Report, Custom development, ALV report
- Module: PM
- Estimated effort: S (2–3 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/open-maintenance-notifications-without-order-aging-report/


## 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.

### Closest standard alternatives

- IW28: Lists notifications by status and date; no age and no days past the required end.
- IW29: Displays notifications; it does not group those without an order by age.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| QMEL | Notification type, short text, priority, date and required end (driving table) | Read | - | ECC + S/4 |
| QMIH | Planning plant, planner group, equipment and breakdown flag | Read | QMIH-QMNUM = QMEL-QMNUM | ECC + S/4 |
| JEST | Notification system statuses | Read | JEST-OBJNR = QMEL-OBJNR | ECC + S/4 |
| ILOA | Functional location | Read | ILOA-ILOAN = QMIH-ILOAN | ECC + S/4 |
| EQKT | Equipment description | Read | EQKT-EQUNR = QMIH-EQUNR AND EQKT-SPRAS = SY-LANGU | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | QMIH-IWERK | Yes |
| S_QMART | Notification type | Range / multiple | QMEL-QMART | No |
| S_PRIOK | Priority | Range / multiple | QMEL-PRIOK | No |
| S_INGRP | Planner group | Range / multiple | QMIH-INGRP | No |
| S_EQUNR | Equipment | Range / multiple | QMIH-EQUNR | No |
| S_TPLNR | Functional location | Range / multiple | ILOA-TPLNR | No |
| S_QMDAT | Notification date | Range / multiple | QMEL-QMDAT | No |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes |
| P_BRKDN | Breakdowns only | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Notification | QMEL-QMNUM |
| Type | QMEL-QMART |
| Short text | QMEL-QMTXT |
| Equipment | QMIH-EQUNR |
| Equipment description | EQKT-EQKTX |
| Functional location | ILOA-TPLNR |
| Priority | QMEL-PRIOK |
| Planner group | QMIH-INGRP |
| Notification date | QMEL-QMDAT |
| Required end | QMEL-LTRMN |
| Age (days) | Calculated: Key date − QMEL-QMDAT |
| Past required end (days) | Calculated: Key date − QMEL-LTRMN (at least 0) |
| Breakdown | QMIH-MSAUS |
| Age bucket | Calculated: 0–1, 2–7, 8–30 or 30+ days |

## How does the report work?

1. 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.
2. 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.
3. 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.
4. The equipment description is added from EQKT, the functional location through QMIH-ILOAN → ILOA-TPLNR.
5. ALV is sorted by priority and age; breakdowns and notifications past the required end are highlighted.

## Authorization objects

- I_QMEL: Display maintenance notifications by notification type
- I_INGRP: Authorization by planner group
- I_SWERK: Display 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pm-open-notifications-without-order
