What is an IDoc?
IDoc is an Intermediate document used for exchanging business data between SAP and
non-SAP systems.
It acts as a Data container, facilitating smooth communication across different modules or
systems.
Every IDoc has a unique Number.
➢ Ensures seamless data exchange between SAP and external systems.
➢ Standardizes business communication across different SAP landscapes.
➢ Reduces manual intervention, making processes faster and more efficient.
IDocs Process:
➢ Inbound IDoc: It means data coming into SAP from an external system.
➢ Outbound IDoc: It means data sent from SAP to an external system.
IDocs Exchange Methods:
➢ ALE (Application Link Enabling): Format of Data is not changing between
exchanging 2 systems.
➢ EDI (Electronic Data Interchange): Format of Data is changing between exchanging
2 systems.
Key Components of IDoc:
1. Control Record: It contains the Inbound / Outbound records such as Port Number,
Partner Number, Message Type, IDoc Number, Direction, Start Date – End Date of
IDoc etc.
Table: EDIDC (All record found in this table).
2. Data Record: Holds the actual business data in segments.
Table: EDID4 (All record found in this table).
3. Status Record: It shows the IDoc Status whether it is in the error or success state.
Table: EDIDS (All record found in this table).
Inbound Status Code: 50 To 75.
Outbound Status Code: 01 To 49.
Document Prepared by Anish Khole 1
IDoc Configuration Part:
➢ Message Type: It tells the meaning or purpose of the IDoc.
Tcode: WE81.
➢ IDoc Type: It tells the structure of Data.
Tcode: WE30.
➢ IDoc Segment: It stored the actual data of the IDoc.Segments are stored in IDoc
type.
Tcode: WE31.
➢ Mapping of IDoc Type and Message Type:
Tcode: WE82.
IDoc Settings:
➢ Port Number:
The Port in IDoc processing is used to define the communication link between the
Sender and Receiver systems.
It determines how the IDoc is transmitted from one system to another.
TCode: WE21
➢ Partner Number:
The Partner Number defines the Sender and Receiver in IDoc communication.
It ensures that IDocs are exchanged with the correct Business Partner (e.g., Vendors,
Customers, Logical Systems).
Tcode: WE20
Document Prepared by Anish Khole 2
Real-world Use Cases:
➢ Sales Order Processing (ORDERS05 IDoc) – Automating sales order creation between
SAP and external vendors.
➢ Invoice Processing (INVOIC02 IDoc) – Seamless invoice exchange between customers
and suppliers.
➢ Material Master Data Distribution (MATMAS05 IDoc) – Synchronizing material master
data across SAP systems.
➢ Goods Movement (MBGMCR IDoc) – Automating stock transfers and inventory updates.
Conclusion: IDocs are the backbone of SAP’s integration framework, enabling smooth
and structured communication between systems. Whether you’re handling sales orders,
invoices, or material master data, IDocs ensure efficiency, accuracy, and automation.
Document Prepared by Anish Khole 3
