Which ways are there to process IDocs?

AuthorTobias Glembotzki
Process IDocs Icon

With EDI (Electronic Data Interchange), processes that have a certain degree of standardization can be mapped and automated electronically. This is especially  valid for logistical processes related to sales and procurement. For example, purchase orders can be automatically processed by a program or sent to a user and data can be transferred to the user's own system.

The SAP IDoc is SAP's standard data structure for exchanging documents between SAP applications as well as between SAP and external systems. At SAP, we basically distinguish between three different IDoc processing methods: outbound processing, inbound processing and status processing.

In each case, there are different paths that the IDoc can take:

SAP IDoc outbound processing

In SAP IDoc outbound processing, IDocs are sent from your system to a downstream system.

  • Message Control finds the message via conditions and forwards it to the SAP IDoc interface.
  • The SAP IDoc is then  generated directly by the application and forwarded to the IDOC interface.

SAP IDoc inbound processing

In SAP IDoc inbound processing, IDocs are sent from another system to your SAP system.

  • Data from the SAP IDoc is automatically converted to the corresponding application data and forwarded to the appropriate application.
  • The SAP IDoc interface starts a workflow in which a user can check or even edit the data.

In addition, data in SAP IDoc inbound processing can be automatically converted into values suitable for the user's own system using mapping.

SAP IDoc status processing

All the steps that an IDoc goes through in processing are logged into the status records. The downstream system can send back a status confirmation with the status records. This allows problems  concerning sending or processing SAP IDocs to be identified, resolved, and the doc status to be changed.

IDoc transaction  can be used to view SAP IDocs that have already been sent and their processing status. The traffic light of the statuses shows directly if an error occurred during sending or processing. In addition, each step is tagged with a status, consisting of a number and the associated status text, from which the error can be read.

Since we now know the error in the event of a problem with SAP IDoc processing, we can correct it using IDoc transaction 9. In IDoc transaction , the content of the SAP IDoc can be processed and the IDoc can be resent or its processing can be triggered again. In this way, the incorrect Doc status can be adjusted.

Libelle EDIMON provides a summary overview of all relevant SAP IDocs and their status, thus simplifying manual troubleshooting. In addition, Libelle EDIMON automates the process of troubleshooting and enables a regulated processing of your SAP IDocs. (Source)

Would you like to learn more about various IT topics? For example, Communication via IDocs in the SAP environment? . Then feel free to visit our blog and follow us on LinkedIn.

Recommended articles
Icon DevOps Libelle IT Group
December 22, 2022 Libelle IT Glossary Part 22: What is DevOps?
Icon IDoc and EDI
June 15, 2022 Libelle IT Glossary Part 12: The differences between SAP IDoc and EDI

All blog articles