CONTAX Logo

IDoc Monitoring for SD Orders in SAP S/4HANA with EMORD

August 19, 2019  |  by Brian Hui

SAP S/4HANA includes process-related IDoc monitors as standard, including one for incoming SD orders. This paper explains why IDoc errors on EDI orders become business problems, and how the EMORD monitor lets business users find, fix and reprocess those errors themselves instead of waiting on IT.

Key Takeaways

  • Delays in posting EDI orders can lead to wrong sales orders, inaccurate MRP requirements, missed deliveries and customer disputes
  • Process-related IDoc monitors are part of the S4CORE software component and available out of the box in S/4HANA; in ECC they were limited to IS-A and ECC-DIMP
  • The monitors combine IDoc data with the related SD transaction data in one ALV report, so users can troubleshoot, reprocess or flag IDocs for deletion from one screen
  • The monitor for SD orders is transaction EMORD, covering message types ORDERS, ORDCHG and DELNOT

Why IDoc Errors Become Business Problems

IDoc processes are technical and can be a hassle for a business user to manage alone. Users often depend on their IT department or an outside SAP vendor for help, which delays getting EDI orders posted into SAP. Those delays can have costly downstream effects:

  • Incorrect sales order data
  • Inaccurate requirements in MRP
  • Fines for missing same-day deliveries
  • The need to expedite deliveries
  • Vendor performance rating downgrades
  • Disputes with customers

IDoc Monitors Now Standard in S/4HANA

Process-related IDoc monitors are included in the S4CORE software component and can be used out of the box with S/4HANA. In ECC, these transactions were only available in SAP systems using the IS-A module (Industry-Specific Component Automotive) or the ECC-DIMP component (Discrete Industries and Mill Products).

What the Monitors Do

The monitors present their data in an ALV report that combines key IDoc data with the corresponding SD transaction data. From that one screen, business users can troubleshoot and reprocess IDoc errors, or flag IDocs for deletion (status 68) when the issue is inconsequential. This central view is a significant improvement and reduces the number of transaction codes users need.

The selection screen lets users filter by when IDocs were created, by document type (request, order, order change, delivery order), by partners and references such as sold-to party, ship-to party, purchase order number and customer material, and by processing status, such as application document not posted or IDoc ready for transfer.

The IDoc Monitor for SD Orders

Transaction

EMORD, IDoc Monitor for Incoming SD Orders

Message types

ORDERS, ORDCHG and DELNOT

Basic types

ORDERS01 to ORDERS05

Package

ISAUTO_SUE_MON (EDI Monitors)

ABAP program

RESDEDIORD

A Step in the Right Direction

EMORD is still not the ideal IDoc monitoring tool, but it is a clear step by SAP toward a better standard solution for business users who manage EDI orders.

How CONTAX Can Help

CONTAX works with SAP customers on EDI and IDoc processing in SAP. Learn more about SAP EDI Integration or contact us.

About the Author

Brian Hui

Brian is an expert in EDI, SAP integration, and interface technology, having worked on hundreds of customer solutions.

Talk to Our Team

Questions about SAP, EDI or Acumatica? We're glad to help.