New Developer’s Guide to IDocs in SAP

The SAP IDoc Technology is used in ALE, EDI, and 3rd Party Systems Integration scenarios. An IDoc stands for intermediate document and is simply a data container used to exchange information between any two processes that can understand the semantics of the data. IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. IDocs in the SAP system are stored in database tables. We can use transactions to view, edit, and process them. When an IDoc is generated in the system, a unique number is assigned to it via a Number Range Object. This number is unique within a client. An IDoc is created as a result of executing an Outbound ALE or EDI process whereas with an inbound ALE or EDI process, an IDoc serves as input to create an application object in SAP, like a Sales Order or PO. Using this technique avoids creating redundant IDoc types.
In this book, you will explore the architecture of an IDoc, IDoc’s definition and runtime components.

  • Basic IDoc Type
  • IDoc RUN Time Components
  • Technical Description of the IDoc Format
  • IDoc extensionsand enhancements. Why do We Need an Extended IDoc?
  • Create a new IDoc Segment using transaction WE31
  • Create a new Custom IDoc Message Type using transaction WE81
  • Create a New IDoc Assignment using transaction WE82
  • IDoc Processing and Message Control
  • Finding and Updating an IDoc Customer Exit Using SMOD

Download PDF – New Developer’s Guide to IDocs in SAP

Leave a Comment

Exit mobile version