Technical Implementation of the Scenarios (SAP Library - IDoc Interface: EDI Application Scenarios (BC-SRV-EDI))

Technical Implementation of the Scenarios

Use

From a technical point of view, the same procedure is used in each of the scenarios. When the document to be sent has been posted by the application, the application itself either creates an IDoc or a message is generated by the Message Control module. An outbound IDoc is generated by the IDoc Interface from this message and the application document.

On the recipient side, an inbound IDoc is transferred to the IDoc Interface and created in the database from there. This scenario is not concerned with way in which the inbound IDoc was transferred to the R/3 System. To test the scenario, you can generate an inbound IDoc from the outbound IDoc in the same system and client via the test tool.

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

Prerequisites

The following default settings are required for the scenarios (for both sender and recipient):

Application Customizing, especially for EDI - Customizing includes the maintenance of condition components for Message Control, if the application uses this module (always the case in MM and SD).

Additional EDI-specific default settings may be required in the application master data.

Partner profiles and port definition for the IDoc Interface.

Activities

The sender posts the document to be sent. In the case of outbound processing using Message Control, the message found by Message Control can be displayed before being posted and edited if necessary.

On the recipient side, IDoc inbound processing usually takes place automatically, i.e. the document is posted when IDoc inbound processing is complete. This procedure can be monitored at several points, e.g. when the IDocs or the corresponding application documents are displayed.

If an error occurs during IDoc processing, exception handling via workflow is started. Only then can users play an active role in the procedure.

The IDoc Interface test tool can be used to detect errors in inbound processing. Define the ALE inbound function module which is behind the inbound process code and call the module directly in the inbound test. In addition, you should select the option Fgd after error. This screen on which the inbound error occurred is now displayed.