Shop Floor (MES) Confirmation Interface Log and Error Monitor
Short answer: A monitoring report that shows on one screen which production confirmations from the shop floor system (MES) were posted in SAP, which failed and which are pending. Failed messages are grouped by cause, the user can correct the data and reprocess the confirmation from the report; posted confirmations are matched to the order and confirmation number.
- Estimated effort
- M · 7–10 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
If MES confirmations arrive as IDocs their status is visible in WE02 and BD87; if they arrive through direct function calls they appear only in the application log (SLG1); goods movement errors after the confirmation are in COGI. None of these shows the message with its production order and operation in business terms, and reprocessing differs by channel. The custom report combines the three sources and offers one reprocessing path.
Who uses it? Production system owners, PP consultants, interface support teams and shift supervisors.
Closest standard alternatives
- WE02 Display IDoc. Shows IDocs and their status; does not match them with order and operation in business terms.
- BD87 Status Monitor for ALE Messages. Reprocesses failed IDocs; does not cover confirmations received through direct calls.
- COGI Postprocess Faulty Goods Movements. Corrects failed goods movements after confirmation; does not show the interface message.
- SLG1 Application Log: Display Logs. Shows the application log; does not group messages or offer reprocessing.
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| EDIDCIDoc Control Record | IDoc control record: message type, time, current status (driving table on the IDoc channel) | — | ECC + S/4 |
| EDIDSIDoc Status Records | IDoc status history and error text | EDIDS-DOCNUM = EDIDC-DOCNUM | ECC + S/4 |
| BALHDRApplication Log Header | Application log header on the direct call channel | BALHDR-EXTNUMBER = MES message ID / mesaj kimliği | ECC + S/4 |
| AFRUOrder Confirmations | Confirmation created in SAP: quantities, confirmation number, reversal flag | AFRU-AUFNR, AFRU-VORNR ↔ MES message / mesaj | ECC + S/4 |
| AFFWGoods Movements with Errors from Confirmations | Failed goods movements after confirmation | AFFW-RUECK = AFRU-RUECK AND AFFW-RMZHL = AFRU-RMZHL | ECC + S/4 |
| AFKOOrder Header Data for PP Orders | Order header and material | AFKO-AUFNR = AFRU-AUFNR | ECC + S/4 |
| CRHDWork Center Header | Work center | CRHD-OBJTY = 'A' AND CRHD-OBJID = AFRU-ARBID | ECC + S/4 |
BAPIs and functions used
- BAPI_PRODORDCONF_CREATE_TTEnter Production Order Confirmation (Time Ticket). Creates a confirmation from a corrected message
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Commits a successful reprocessing
- IDOC_READ_COMPLETELYRead IDoc Completely. Reads the data of a failed IDoc for the correction screen
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_DATE | Receipt date | Range / multiple | EDIDC-CREDAT | Yes | 14.11.2026 – 15.11.2026 |
| P_WERKS | Plant | Single value | AFRU-WERKS | Yes | 1000 |
| S_AUFNR | Production order | Range / multiple | AFRU-AUFNR | No | 1004601 |
| P_STAT | Status: all / failed / pending / posted | Radio button | — | Yes | Hatalı |
| P_TEST | Test run when reprocessing | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Received at | Calculated EDIDC-CREDAT/CRETIM or the receipt time in the log table |
| 2 | Message / IDoc | EDIDC-DOCNUM |
| 3 | Order | AFRU-AUFNR |
| 4 | Operation | AFRU-VORNR |
| 5 | Work center | CRHD-ARBPL |
| 6 | Yield | AFRU-LMNGA |
| 7 | Scrap | AFRU-XMNGA |
| 8 | Status | Calculated Posted, failed, pending or confirmation OK / movement failed |
| 9 | Error text | EDIDS-STATXT |
| 10 | Confirmation no. | AFRU-RUECK |
| 11 | Attempts | Calculated Number of attempts in the log table |
Sample output
| Received at | Message / IDoc | Order | Operation | Work center | Yield | Scrap | Status | Error text | Confirmation no. | Attempts |
|---|---|---|---|---|---|---|---|---|---|---|
| 15.11.2026 07:02 | 0000000004518823 | 1004601 | 0030 | KYN-02 | 250 | 3 | Posted | 100245 | 1 | |
| 15.11.2026 07:15 | 0000000004518830 | 1004615 | 0020 | CNC-04 | 40 | 0 | Failed | Order is locked by another user | 2 | |
| 15.11.2026 07:31 | 0000000004518841 | 1004622 | 0060 | PKT-01 | 280 | 0 | Confirmation OK / movement failed | Insufficient stock for component | 100251 | 1 |
| 15.11.2026 07:48 | 0000000004518852 | 1004640 | 0010 | KSM-01 | 500 | 12 | Failed | Operation already finally confirmed | 1 |
How does the report work?
- Every incoming MES message is written to an interface log table: message ID, receipt time, order, operation, work center, yield/scrap quantity, times, status and number of attempts. If the existing interface uses IDocs, the log can be filled from EDIDC/EDIDS; if it uses direct calls, from the BALHDR application log; the choice is made during installation according to the interface design.
- For the IDoc channel, the message type, creation time and current status are read from EDIDC and the latest status text from EDIDS; status 53 is classified as posted, 51 and 56 as failed, 64 as pending.
- Posted messages are matched to the confirmation in AFRU (order, operation, posting time and quantity; directly via RUECK/RMZHL if the log table holds the confirmation number); reversed confirmations are flagged separately.
- If the confirmation was saved but the automatic goods movement failed, the AFFW record is matched by order and confirmation and the status ‘confirmation OK, movement failed’ is set.
- Error messages are grouped by message class and number (e.g. order locked, operation finally confirmed, insufficient stock) and the count per group is shown.
- Reprocessing: on the IDoc channel the IDoc is reprocessed; on the direct channel BAPI_PRODORDCONF_CREATE_TT is called with the corrected data and saved with BAPI_TRANSACTION_COMMIT. An automatic retry job can be scheduled for lock errors; each attempt is written to the log table.
Performance notes
Index the log table on receipt date and status. Restrict EDIDC by message type, direction and creation date; read only the latest status record from EDIDS. Run the retry job between shifts to reduce order locks.
Features
- ALV list (sort, filter, subtotals)
- Double-click drill-down to the document From a line you open the IDoc, the application log, the confirmation (CO14) or COGI.
- Test mode (check without posting) Reprocessing is tried in test mode first.
- Line-by-line result and error log Every reprocessing attempt is logged with user and time.
- Runs as a background job An automatic retry job can be scheduled for lock errors.
- Send the result by email Messages that stay failed longer than a set time are reported to the support team.
Authorization objects
- C_AFRU_AWKDisplay confirmations and create them when reprocessing
- S_IDOCMONIIDoc monitoring and reprocessing
- S_APPL_LOGDisplay the application log
Frequently asked questions
Do we need to change our existing MES interface?
If the interface uses IDocs, no change is needed; the report reads the IDoc records. If it uses direct function calls, a small addition writes every incoming message to the log table. This addition usually takes one day and is included in the effort range.
How is the same confirmation prevented from being posted twice?
The unique ID of every MES message is kept in the log table and a posted message cannot be reprocessed. Before reprocessing, the report also checks whether a recent confirmation exists for the same order, operation and quantity and warns the user.
Is it different on S/4HANA?
Confirmation and IDoc structures are the same. In S/4HANA goods movements after confirmation are written to MATDOC, and failed movements still stay in COGI. If MES integration is done with SAP Digital Manufacturing, the report shows the SAP side in addition to that solution's own monitor.
Related reports
COGI Failed Goods Movements Aging Report
A custom ALV report that groups the backflush and automatic goods receipt errors waiting in COGI by age, error reason and material, and flags which of …
Mass Production Order Confirmation Upload Program
A custom program that reads operation confirmations (yield, scrap, rework, activity times) coming from MES, shop-floor terminals or Excel at the end …
Released Production Orders Without Any Confirmation Report
A custom ALV report that lists production orders that were released but have not received a confirmation for a single operation, with the days since …
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.