Mass Breakdown Notification Creation from Shift Downtime File Program
Short answer: A custom program that reads the downtime list kept at the end of a shift, or a file from a production monitoring system, and creates a maintenance breakdown notification for every row with equipment, malfunction start and end time, damage and cause code. In test mode every row is checked and duplicates are filtered out.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
IW21 creates one notification at a time; on lines with dozens of short stops per shift, operators do not enter these records and the downtime stays only in Excel. As a result MTBF, MTTR and downtime analyses run on incomplete data. The standard has no mass entry that reads a downtime file and creates notifications with start/end time, damage and cause code.
Who uses it? Maintenance planners, shift supervisors and teams that connect production monitoring (MES/OEE) systems to SAP.
Closest standard alternatives
- IW21 Create PM Notification (General). Creates one notification at a time; there is no mass entry from a file and no duplicate check.
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| QMELNotification Header | Notification header: type, short text, priority | Write | ECC + S/4 |
| QMIHNotification Maintenance Data | Equipment, malfunction start/end and breakdown indicator; duplicate check | Write | ECC + S/4 |
| QMFENotification Items | Damage code group and code | Write | ECC + S/4 |
| QMURNotification Causes | Cause code group and code | Write | ECC + S/4 |
| EQUIEquipment Master Data | Existence check of the equipment | Read | ECC + S/4 |
| EQUZEquipment Time Segment | Current location link of the equipment | Read | ECC + S/4 |
| ILOAPM Object Location and Account Assignment | Installation location when no functional location is given | Read | ECC + S/4 |
BAPIs and functions used
- BAPI_ALM_NOTIF_CREATECreate PM/CS Notification. Creates the breakdown notification with damage and cause for each row
- BAPI_ALM_NOTIF_SAVESave PM/CS Notification. Saves the created notification and assigns the final number
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Saves successful rows permanently
- BAPI_TRANSACTION_ROLLBACKRoll Back BAPI Transaction. Rolls back in test mode and for failed rows
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Downtime file (XLSX or CSV) | Single value | — | Yes | C:\temp\vardiya-duruslari.xlsx |
| P_QMART | Default notification type | Single value | QMEL-QMART | No | M2 |
| P_MINDUR | Minimum downtime (minutes, shorter rows skipped) | Single value | — | No | 5 |
| P_TEST | Test mode (check without posting) | Checkbox | — | No | X |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Notification type | QMEL-QMART | No |
| 2 | Equipment | QMIH-EQUNR | Yes |
| 3 | Functional location | ILOA-TPLNR | No |
| 4 | Short text | QMEL-QMTXT | Yes |
| 5 | Malfunction start date | QMIH-AUSVN | Yes |
| 6 | Start time | QMIH-AUZTV | Yes |
| 7 | Malfunction end date | QMIH-AUSBS | No |
| 8 | End time | QMIH-AUZTB | No |
| 9 | Breakdown | QMIH-MSAUS | No |
| 10 | Damage code group | QMFE-FEGRP | No |
| 11 | Damage code | QMFE-FECOD | No |
| 12 | Cause code group | QMUR-URGRP | No |
| 13 | Cause code | QMUR-URCOD | No |
| 14 | Priority | QMEL-PRIOK | No |
Sample upload file
| 1 | Notification type | Equipment * | Functional location | Short text * | Malfunction start date * | Start time * | Malfunction end date | End time | Breakdown | Damage code group | Damage code | Cause code group | Cause code | Priority |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | M2 | 10004512 | Compressor overheating | 11/16/2026 | 08:40:00 | 11/16/2026 | 10:10:00 | X | PM-HSR | HT01 | PM-NDN | NE03 | 2 | |
| 3 | M2 | 10004630 | TR01-URT-HAT2 | Belt slipping | 11/16/2026 | 13:05:00 | 11/16/2026 | 13:25:00 | X | PM-HSR | HT07 | PM-NDN | NE11 | 3 |
| 4 | M2 | 10004718 | Hydraulic pressure low | 11/16/2026 | 21:50:00 | 11/16/2026 | 21:53:00 | X | PM-HSR | HT04 | PM-NDN | NE02 | 3 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Equipment | QMIH-EQUNR |
| 3 | Functional location | ILOA-TPLNR |
| 4 | Short text | QMEL-QMTXT |
| 5 | Malfunction start | QMIH-AUSVN |
| 6 | Notification | QMEL-QMNUM |
| 7 | Downtime (minutes) | Calculated (AUSBS + AUZTB) − (AUSVN + AUZTV) |
| 8 | Status | Calculated Created, test passed, already exists, skipped or error |
| 9 | Message | Calculated BAPI return message or check error |
Sample result list
| Row | Equipment | Functional location | Short text | Malfunction start | Notification | Downtime (minutes) | Status | Message |
|---|---|---|---|---|---|---|---|---|
| 2 | 10004512 | TR01-URT-HAT1 | Compressor overheating | 11/16/2026 | 10028170 | 90 | Created | Notification 10028170 saved |
| 3 | 10004630 | TR01-URT-HAT2 | Belt slipping | 11/16/2026 | 10028171 | 20 | Created | Notification 10028171 saved |
| 4 | 10004718 | TR01-PRS-01 | Hydraulic pressure low | 11/16/2026 | 3 | Skipped | Downtime shorter than 5 minutes |
How does the program work?
- The file (XLSX or CSV) is read from the user’s PC or, in a background job, from a folder on the application server; the first row is skipped as the header.
- For every row the notification type, equipment or functional location, start and end time are checked: the equipment must exist in EQUI; when no functional location is given, the equipment’s installation location is taken through EQUZ and ILOA; the end cannot be before the start.
- Duplicate check: when a notification with the same malfunction start date and time already exists on the same equipment in QMIH, the row is skipped as ‘already exists’, so loading the same file twice does not create duplicates.
- The row is mapped to the BAPI_ALM_NOTIF_CREATE structures: equipment, functional location, short text, malfunction start/end and breakdown indicator in the header; damage code group and code in the item; cause code group and code in the cause table.
- In test mode the BAPI is called and the change is rolled back. In a real run BAPI_ALM_NOTIF_SAVE and BAPI_TRANSACTION_COMMIT are called; the new notification number and the downtime are written on the row, and failed rows can be downloaded as a separate file.
Performance notes
A commit is done per notification; shift files with a few hundred rows are processed within minutes. For files from a production monitoring system the program can run in the background at the end of every shift and move the processed file to an archive folder.
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file
- Runs as a background job Files from the production monitoring system can be processed automatically at the end of every shift.
Authorization objects
- I_QMELCreate maintenance notifications by notification type
- I_SWERKTechnical object authorization by maintenance plant
Frequently asked questions
What happens if the same file is loaded twice?
For every row the program looks for a notification with the same malfunction start date and time on the same equipment. When it finds one, it skips the row as 'already exists' and shows the existing notification number in the message.
Can a maintenance order be created from the notification automatically?
The base version only creates notifications. If required, a step that creates an order from the notification for certain priorities or damage codes can be added; this extension is planned according to order type and work center rules.
Can the file template be changed?
Yes. Column order and headers are adapted to the output of the production monitoring system; when code groups are missing from the file, defaults can be taken from the equipment's catalog profile.
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 …
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 …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.