{"audience":"Maintenance planners, shift supervisors and teams that connect production monitoring (MES/OEE) systems to SAP.","authorization_objects":[{"note":"Create maintenance notifications by notification type","object":"I_QMEL"},{"note":"Technical object authorization by maintenance plant","object":"I_SWERK"}],"components":[],"countries":[],"effort_days_max":6,"effort_days_min":4,"effort_size":"M","faq":[{"a":"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.","q":"What happens if the same file is loaded twice?"},{"a":"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.","q":"Can a maintenance order be created from the notification automatically?"},{"a":"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.","q":"Can the file template be changed?"}],"features":[{"code":"test_run","label":"Test mode (check without posting)","note":""},{"code":"log","label":"Line-by-line result and error log","note":""},{"code":"error_file","label":"Download failed lines as a separate file","note":""},{"code":"background","label":"Runs as a background job","note":"Files from the production monitoring system can be processed automatically at the end of every shift."}],"functions":[{"name":"BAPI_ALM_NOTIF_CREATE","role":"Creates the breakdown notification with damage and cause for each row"},{"name":"BAPI_ALM_NOTIF_SAVE","role":"Saves the created notification and assigns the final number"},{"name":"BAPI_TRANSACTION_COMMIT","role":"Saves successful rows permanently"},{"name":"BAPI_TRANSACTION_ROLLBACK","role":"Rolls back in test mode and for failed rows"}],"gap":"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.","id":"pm-breakdown-notification-upload","industries":[],"input_columns":[{"derived":false,"label":"Notification type","required":false,"rule":"","target_field":"QMART","target_table":"QMEL"},{"derived":false,"label":"Equipment","required":true,"rule":"","target_field":"EQUNR","target_table":"QMIH"},{"derived":false,"label":"Functional location","required":false,"rule":"","target_field":"TPLNR","target_table":"ILOA"},{"derived":false,"label":"Short text","required":true,"rule":"","target_field":"QMTXT","target_table":"QMEL"},{"derived":false,"label":"Malfunction start date","required":true,"rule":"","target_field":"AUSVN","target_table":"QMIH"},{"derived":false,"label":"Start time","required":true,"rule":"","target_field":"AUZTV","target_table":"QMIH"},{"derived":false,"label":"Malfunction end date","required":false,"rule":"","target_field":"AUSBS","target_table":"QMIH"},{"derived":false,"label":"End time","required":false,"rule":"","target_field":"AUZTB","target_table":"QMIH"},{"derived":false,"label":"Breakdown","required":false,"rule":"","target_field":"MSAUS","target_table":"QMIH"},{"derived":false,"label":"Damage code group","required":false,"rule":"","target_field":"FEGRP","target_table":"QMFE"},{"derived":false,"label":"Damage code","required":false,"rule":"","target_field":"FECOD","target_table":"QMFE"},{"derived":false,"label":"Cause code group","required":false,"rule":"","target_field":"URGRP","target_table":"QMUR"},{"derived":false,"label":"Cause code","required":false,"rule":"","target_field":"URCOD","target_table":"QMUR"},{"derived":false,"label":"Priority","required":false,"rule":"","target_field":"PRIOK","target_table":"QMEL"}],"kind":"program","language":"en","lastmod":"2026-11-17","logic":"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.\n2. 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.\n3. 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.\n4. 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.\n5. 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.","module":"PM","object_type":"upload","output_columns":[{"calculated":true,"formula":"Row number in the file","label":"Row","source_field":null,"source_table":null},{"calculated":false,"formula":"","label":"Equipment","source_field":"EQUNR","source_table":"QMIH"},{"calculated":false,"formula":"","label":"Functional location","source_field":"TPLNR","source_table":"ILOA"},{"calculated":false,"formula":"","label":"Short text","source_field":"QMTXT","source_table":"QMEL"},{"calculated":false,"formula":"","label":"Malfunction start","source_field":"AUSVN","source_table":"QMIH"},{"calculated":false,"formula":"","label":"Notification","source_field":"QMNUM","source_table":"QMEL"},{"calculated":true,"formula":"(AUSBS + AUZTB) − (AUSVN + AUZTV)","label":"Downtime (minutes)","source_field":null,"source_table":null},{"calculated":true,"formula":"Created, test passed, already exists, skipped or error","label":"Status","source_field":null,"source_table":null},{"calculated":true,"formula":"BAPI return message or check error","label":"Message","source_field":null,"source_table":null}],"parameters":[{"example":"C:\\temp\\vardiya-duruslari.xlsx","kind":"parameter","label":"Downtime file (XLSX or CSV)","name":"P_FILE","ref_field":"","required":true},{"example":"M2","kind":"parameter","label":"Default notification type","name":"P_QMART","ref_field":"QMEL-QMART","required":false},{"example":"5","kind":"parameter","label":"Minimum downtime (minutes, shorter rows skipped)","name":"P_MINDUR","ref_field":"","required":false},{"example":"X","kind":"checkbox","label":"Test mode (check without posting)","name":"P_TEST","ref_field":"","required":false}],"part_of":[],"performance":"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.","quote_url":"https://nekuhub.com/en/request-a-quote/?report=pm-breakdown-notification-upload","related":["pm-mtbf-mttr-by-equipment","pm-repeat-breakdowns-by-equipment"],"releases":[],"source":"custom","standard_alternatives":[{"note":"Creates one notification at a time; there is no mass entry from a file and no duplicate check.","tcode":"IW21"}],"summary":"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.","tables":[{"access":"write","join_on":"QMEL-QMNUM = yeni bildirim","role":"Notification header: type, short text, priority","table":"QMEL","variant":"both"},{"access":"write","join_on":"QMIH-QMNUM = QMEL-QMNUM","role":"Equipment, malfunction start/end and breakdown indicator; duplicate check","table":"QMIH","variant":"both"},{"access":"write","join_on":"QMFE-QMNUM = QMEL-QMNUM","role":"Damage code group and code","table":"QMFE","variant":"both"},{"access":"write","join_on":"QMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUM","role":"Cause code group and code","table":"QMUR","variant":"both"},{"access":"read","join_on":"EQUI-EQUNR = dosya ekipman","role":"Existence check of the equipment","table":"EQUI","variant":"both"},{"access":"read","join_on":"EQUZ-EQUNR = EQUI-EQUNR AND EQUZ-DATBI = '99991231'","role":"Current location link of the equipment","table":"EQUZ","variant":"both"},{"access":"read","join_on":"ILOA-ILOAN = EQUZ-ILOAN","role":"Installation location when no functional location is given","table":"ILOA","variant":"both"}],"title":"Mass Breakdown Notification Creation from Shift Downtime File Program","url":"https://nekuhub.com/en/programs/mass-breakdown-notification-upload-program/","vendor_id":"nekudos"}