Technical Background


From a technical point of view, the scenarios always follow the same procedure: After the application document being sent has been posted by the application, the application either generates an IDoc, or uses message control to generate a message. Using the IDoc Interface, the system generates an outbound IDoc from the message and the application document.

On the recipient side, an inbound IDoc is transferred to the IDoc interface, and from there to the database. This process is the same regardless of the method by which the inbound IDoc arrives in the SAP system. To test the scenario, you can use the Test Tool to generate an inbound IDoc from the outbound IDoc in the same system and client.

The data from the inbound IDoc is then transferred to the relevant application tables, and the application document is posted.


Processing of the scenario has the following prerequisites (for both the sender and the recipient):

  • You have carried out application Customizing, including any EDI-specific Customizing settings. If the application uses message control, ensure that the message control condition elements are maintained.
  • You have made any possible additional EDI-specific presettings in the master data of the application.
  • You have maintained the Partner Profiles and Port Definition of the IDoc Interface.


The sender posts the document to be sent. If sending using message control, the user can display the message found by message control before posting, and edit it if necessary.

On the recipient side, IDoc inbound processing is normally automatic, which means the application document is posted after inbound processing of the IDoc. This process can be controlled from several locations, for example, from the IDoc display, or from the corresponding application documents.

If an error occurs in IDoc processing, exception handling is started by a workflow. This is the first point at which user interaction is required.

The IDoc Interface Test Tool offers a useful option for tracking errors in inbound processing. You can use this tool to determine the ALE inbound processing module behind the Inbound Processing Process Code, and call it directly in the inbound test. Also select the option Foreground after error. This displays the screen on which the error has occurred. This option is only available for applications that use, for example, a CALL TRANSACTION.