PM Program Custom development Mass upload

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.

TableRoleAccessSystem
QMELNotification HeaderNotification header: type, short text, priorityWriteECC + S/4
QMIHNotification Maintenance DataEquipment, malfunction start/end and breakdown indicator; duplicate checkWriteECC + S/4
QMFENotification ItemsDamage code group and codeWriteECC + S/4
QMURNotification CausesCause code group and codeWriteECC + S/4
EQUIEquipment Master DataExistence check of the equipmentReadECC + S/4
EQUZEquipment Time SegmentCurrent location link of the equipmentReadECC + S/4
ILOAPM Object Location and Account AssignmentInstallation location when no functional location is givenReadECC + 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

ParameterDescriptionTypeReference fieldRequiredExample
P_FILEDowntime file (XLSX or CSV)Single value—YesC:\temp\vardiya-duruslari.xlsx
P_QMARTDefault notification typeSingle valueQMEL-QMARTNoM2
P_MINDURMinimum downtime (minutes, shorter rows skipped)Single value—No5
P_TESTTest mode (check without posting)Checkbox—NoX

Input file columns

The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.

#ColumnTarget fieldRequired
1Notification typeQMEL-QMARTNo
2EquipmentQMIH-EQUNRYes
3Functional locationILOA-TPLNRNo
4Short textQMEL-QMTXTYes
5Malfunction start dateQMIH-AUSVNYes
6Start timeQMIH-AUZTVYes
7Malfunction end dateQMIH-AUSBSNo
8End timeQMIH-AUZTBNo
9BreakdownQMIH-MSAUSNo
10Damage code groupQMFE-FEGRPNo
11Damage codeQMFE-FECODNo
12Cause code groupQMUR-URGRPNo
13Cause codeQMUR-URCODNo
14PriorityQMEL-PRIOKNo

Sample upload file

1Notification typeEquipment *Functional locationShort text *Malfunction start date *Start time *Malfunction end dateEnd timeBreakdownDamage code groupDamage codeCause code groupCause codePriority
2M210004512Compressor overheating11/16/202608:40:0011/16/202610:10:00XPM-HSRHT01PM-NDNNE032
3M210004630TR01-URT-HAT2Belt slipping11/16/202613:05:0011/16/202613:25:00XPM-HSRHT07PM-NDNNE113
4M210004718Hydraulic pressure low11/16/202621:50:0011/16/202621:53:00XPM-HSRHT04PM-NDNNE023
A view built with fictional sample data; not real system data.

Result list columns

#ColumnSource
1RowCalculated Row number in the file
2EquipmentQMIH-EQUNR
3Functional locationILOA-TPLNR
4Short textQMEL-QMTXT
5Malfunction startQMIH-AUSVN
6NotificationQMEL-QMNUM
7Downtime (minutes)Calculated (AUSBS + AUZTB) − (AUSVN + AUZTV)
8StatusCalculated Created, test passed, already exists, skipped or error
9MessageCalculated BAPI return message or check error

Sample result list

RowEquipmentFunctional locationShort textMalfunction startNotificationDowntime (minutes)StatusMessage
210004512TR01-URT-HAT1Compressor overheating11/16/20261002817090CreatedNotification 10028170 saved
310004630TR01-URT-HAT2Belt slipping11/16/20261002817120CreatedNotification 10028171 saved
410004718TR01-PRS-01Hydraulic pressure low11/16/20263SkippedDowntime shorter than 5 minutes
A view built with fictional sample data; not real system data.

How does the program work?

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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

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

PM Report Custom ALV report

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 …

QMEL · QMIH · QMFE · QMUR

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.

Related report: Mass Breakdown Notification Creation from Shift Downtime File Program