This approach ensures compatibility with most standards. If there is a conflict in data size between standards, the one with greater length is adopted.
For example, if a material number is represented by 20 characters in an EDIFACT message, the corresponding data element in the IDoc is also 20 characters.
The size and format of data elements in an IDoc type are derived from these standards wherever applicable. IDocs are based on EDI standards, ANSI ASC X12 and EDIFACT, but are closer to the EDIFACT standards. They can be used for SAP-to-SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. IDocs are independent of the sending and receiving systems. When an IDoc is generated in the system, a unique number is assigned to it. For details, refer to Chapter 11, "Monitoring the Interface." Several utilities are available to display the information contained in an IDoc and present it in different ways. In the SAP system, they are stored in database tables. In an inbound ALE or EDI process, an IDoc serves as input to create an application document. An IDoc is created as a result of executing an outbound ALE or EDI process. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. The term IDoc stands for intermediate document. and Sample code for ALE.įollow the link for step by step ALE/IDOC tutorials. What is inbound and outbout process of IDOC?
0 kommentar(er)
