PM Report Custom development ALV report

Repeat Breakdowns by Equipment Report

Short answer: A custom ALV report that shows breakdown notifications repeating on the same equipment within a selected window of days, with the previous notification, the days in between, and the damage and cause codes on the same line. Repeats with the same cause are flagged, so equipment that needs a permanent fix is visible at a glance.

Estimated effort
M · 3–5 working days
System
ECC and S/4HANA
Tables
6
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

IW29 lists notifications by equipment and date, but it does not cluster them per equipment and compare each with the previous one; the days between two breakdowns, the previous cause code and a 'repeat with the same cause' flag are missing. For reliability analysis the list is exported to Excel, sorted and compared with formulas. The existing MTBF report gives averages; this report shows the individual repeat events and their causes.

Who uses it? Maintenance planners, reliability engineers, maintenance managers and teams that run root cause analysis.

Closest standard alternatives

  • IW29 Display Notifications (List). Lists notifications; does not cluster repeats on the same equipment or compare them with the previous cause code.

Tables used

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

TableRoleJoinSystem
QMELNotification HeaderNotification header: type, date, short text, linked order (driving table)—ECC + S/4
QMIHNotification Maintenance DataEquipment, maintenance plant, malfunction start and downtimeQMIH-QMNUM = QMEL-QMNUMECC + S/4
QMFENotification ItemsDamage code and object partQMFE-QMNUM = QMEL-QMNUMECC + S/4
QMURNotification CausesCause codeQMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUMECC + 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-QMARTNoM2
S_EQUNREquipmentRange / multipleQMIH-EQUNRNo10004512
S_TPLNRFunctional locationRange / multipleILOA-TPLNRNoTR01-URT-HAT1
S_QMDATNotification date rangeRange / multipleQMEL-QMDATYes01.01.2026 – 17.11.2026
P_DAYSRepeat window (days)Single value—Yes90
P_BRKDNBreakdowns onlyCheckbox—NoX
P_SAMEDMOnly repeats with the same damage codeCheckbox—No—

Output columns

#ColumnSource
1EquipmentQMIH-EQUNR
2Equipment descriptionEQKT-EQKTX
3Functional locationILOA-TPLNR
4NotificationQMEL-QMNUM
5Malfunction startQMIH-AUSVN
6Short textQMEL-QMTXT
7Damage codeQMFE-FECOD
8Cause codeQMUR-URCOD
9Downtime (hours)Calculated QMIH-AUSZT converted to hours from the QMIH-MAUEH unit
10Previous notificationCalculated QMEL-QMNUM of the previous notification on the same equipment
11Previous causeCalculated QMUR-URCOD of the previous notification
12Days since previousCalculated QMIH-AUSVN − QMIH-AUSVN of the previous notification
13Same causeCalculated X when the cause code equals the previous one
14Repeats in windowCalculated Number of notifications on the equipment flagged as repeats within the window

Sample output

EquipmentEquipment descriptionFunctional locationNotificationMalfunction startShort textDamage codeCause codeDowntime (hours)Previous notificationPrevious causeDays since previousSame causeRepeats in window
10004512Compressor K-12TR01-URT-HAT11002778110/28/2026Compressor overheatingHT01NE036.5010027215NE0334X3
10004512Compressor K-12TR01-URT-HAT11002814011/12/2026Compressor stopped againHT01NE03410027781NE0315X3
10004630Conveyor belt B2TR01-URT-HAT21002790211/03/2026Belt slippingHT07NE111.5010026877NE05611
10004718Hydraulic press P-3TR01-PRS-011002801111/07/2026Hydraulic leakHT04NE02810027650NE0222X2
A view built with fictional sample data; not real system data.

How does the report work?

  1. Notifications with equipment are read from QMEL and QMIH by maintenance plant (IWERK), notification type and notification date range on the selection screen; with ‘breakdowns only’ selected, those with QMIH-MSAUS set are taken. To catch the first repeats at the start of the range, reading starts the window length before the range start.
  2. The first damage item (FEGRP, FECOD, OTEIL) is added from QMFE and the first cause (URGRP, URCOD) from QMUR; the functional location comes through ILOA.
  3. Notifications are sorted by equipment and malfunction start (AUSVN, AUZTV; QMDAT when blank). Each notification is compared with the previous one on the same equipment: when the days in between are within the window, the line is flagged as a repeat.
  4. When the cause code equals the previous one, a ‘same cause’ flag is set; with ‘same damage code only’ selected, repeats with a different damage code are removed.
  5. Downtime is converted to hours from QMIH-AUSZT and its unit MAUEH. Per equipment the number of repeats in the window and the total downtime are calculated; the list is sorted by repeat count, descending.

Performance notes

Narrow QMEL by notification date and type, QMIH by maintenance plant. Read QMFE and QMUR once with the list of notification numbers. Even for a year of history the report finishes within minutes; it can run in the background before the monthly reliability meeting.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document The notification and the previous notification open IW23, the equipment opens IE03.
  • Export to Excel
  • Runs as a background job
  • Send the result by email Equipment above a repeat threshold can be sent weekly to the reliability team.

Authorization objects

  • I_QMELDisplay maintenance notifications by notification type
  • I_SWERKTechnical object and notification authorization by maintenance plant

Frequently asked questions

How should the repeat window be chosen?

Most plants start with 30, 60 or 90 days. For critical equipment a shorter window highlights 'the repair did not hold' cases, a longer window highlights chronic failures. The window can be changed on the selection screen and saved in different variants.

Does it work by functional location as well?

Yes. For notifications without equipment but on a functional location, the functional location can be chosen as the clustering key; this option is within the base effort range.

Does it work on S/4HANA?

Yes. QMEL, QMIH, QMFE and QMUR keep the same structure in S/4HANA. The report runs without changes.

Related reports

PM Report Custom ALV report

Maintenance Cost and Downtime by Equipment Report

A custom ALV report that splits the actual cost of maintenance orders per equipment in a period into labor, material, external services and other, and …

AFIH · AUFK · COEP · QMIH

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: Repeat Breakdowns by Equipment Report