PM Report Custom development ALV report

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

  • IW28 Change Notifications (List). Lists notifications by status and date; no age and no days past the required end.
  • IW29 Display Notifications (List). Displays notifications; it does not group those without an order by age.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
QMELNotification HeaderNotification type, short text, priority, date and required end (driving table)—ECC + S/4
QMIHNotification Maintenance DataPlanning plant, planner group, equipment and breakdown flagQMIH-QMNUM = QMEL-QMNUMECC + S/4
JESTIndividual Object StatusNotification system statusesJEST-OBJNR = QMEL-OBJNRECC + S/4
ILOAPM Object Location and Account AssignmentFunctional locationILOA-ILOAN = QMIH-ILOANECC + S/4
EQKTEquipment Short TextsEquipment descriptionEQKT-EQUNR = QMIH-EQUNR AND EQKT-SPRAS = SY-LANGUECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_IWERKMaintenance planning plantRange / multipleQMIH-IWERKYes1000
S_QMARTNotification typeRange / multipleQMEL-QMARTNoM1
S_PRIOKPriorityRange / multipleQMEL-PRIOKNo1
S_INGRPPlanner groupRange / multipleQMIH-INGRPNoM01
S_EQUNREquipmentRange / multipleQMIH-EQUNRNo10000045
S_TPLNRFunctional locationRange / multipleILOA-TPLNRNoTR01-URT-*
S_QMDATNotification dateRange / multipleQMEL-QMDATNo01.09.2026 – 17.11.2026
P_KEYDTKey date (default: today)Single valueSY-DATUMYes17.11.2026
P_BRKDNBreakdowns onlyCheckbox—No—

Output columns

#ColumnSource
1NotificationQMEL-QMNUM
2TypeQMEL-QMART
3Short textQMEL-QMTXT
4EquipmentQMIH-EQUNR
5Equipment descriptionEQKT-EQKTX
6Functional locationILOA-TPLNR
7PriorityQMEL-PRIOK
8Planner groupQMIH-INGRP
9Notification dateQMEL-QMDAT
10Required endQMEL-LTRMN
11Age (days)Calculated Key date − QMEL-QMDAT
12Past required end (days)Calculated Key date − QMEL-LTRMN (at least 0)
13BreakdownQMIH-MSAUS
14Age bucketCalculated 0–1, 2–7, 8–30 or 30+ days

Sample output

NotificationTypeShort textEquipmentEquipment descriptionFunctional locationPriorityPlanner groupNotification dateRequired endAge (days)Past required end (days)BreakdownAge bucket
10004521M2Press guard door sensor faulty10000045Hydraulic press 400 tTR01-URT-PRS1M0111/10/202611/11/202676X2–7 days
10004498M1Compressor oil level low10000078Screw compressor 75 kWTR01-YRD-KMP3M0110/21/202610/31/202627178–30 days
10004455M1Conveyor belt misalignment10000102Belt conveyor line 2TR01-URT-KNV2M0209/30/202610/07/2026484130+ days
10004530M2Panel fan not running10000110Main distribution panelTR01-ELK-ADP2M0211/16/202611/18/202610X0–1 days
A view built with fictional sample data; not real system data.

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.

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

PM Package Custom

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 …

5 components · v1.0

Related reports

PM Report Custom ALV report

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 …

QMIH · QMEL · QMFE · QMUR

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.

Related report: Open Maintenance Notifications Without Order Aging Report