# Repeat Breakdowns by Equipment Report

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

- Type: Report, Custom development, ALV report
- Module: PM
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/repeat-breakdowns-by-equipment-report/


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

### Closest standard alternatives

- IW29: Lists notifications; does not cluster repeats on the same equipment or compare them with the previous cause code.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| QMEL | Notification header: type, date, short text, linked order (driving table) | Read | - | ECC + S/4 |
| QMIH | Equipment, maintenance plant, malfunction start and downtime | Read | QMIH-QMNUM = QMEL-QMNUM | ECC + S/4 |
| QMFE | Damage code and object part | Read | QMFE-QMNUM = QMEL-QMNUM | ECC + S/4 |
| QMUR | Cause code | Read | QMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUM | 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_EQUNR | Equipment | Range / multiple | QMIH-EQUNR | No |
| S_TPLNR | Functional location | Range / multiple | ILOA-TPLNR | No |
| S_QMDAT | Notification date range | Range / multiple | QMEL-QMDAT | Yes |
| P_DAYS | Repeat window (days) | Single value | - | Yes |
| P_BRKDN | Breakdowns only | Checkbox | - | No |
| P_SAMEDM | Only repeats with the same damage code | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Equipment | QMIH-EQUNR |
| Equipment description | EQKT-EQKTX |
| Functional location | ILOA-TPLNR |
| Notification | QMEL-QMNUM |
| Malfunction start | QMIH-AUSVN |
| Short text | QMEL-QMTXT |
| Damage code | QMFE-FECOD |
| Cause code | QMUR-URCOD |
| Downtime (hours) | Calculated: QMIH-AUSZT converted to hours from the QMIH-MAUEH unit |
| Previous notification | Calculated: QMEL-QMNUM of the previous notification on the same equipment |
| Previous cause | Calculated: QMUR-URCOD of the previous notification |
| Days since previous | Calculated: QMIH-AUSVN − QMIH-AUSVN of the previous notification |
| Same cause | Calculated: X when the cause code equals the previous one |
| Repeats in window | Calculated: Number of notifications on the equipment flagged as repeats within the window |

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

## Authorization objects

- I_QMEL: Display maintenance notifications by notification type
- I_SWERK: Technical 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pm-repeat-breakdowns-by-equipment
