Idoc
Idoc
T-Code Description
IL
WE19 IDoc Test Tool
H
WE20 Partner Profile
SA R
WE21 Port Definition
A
WE30 IDoc Type Development
E W
WE31 Segment Creation
BB
WE60 IDoc Documentation
A
WE81 Message Type Configuration
P WE82
BD87
BD10
Message Type and IDoc Type Link
L
MATMAS05 Material Master Data MATMAS
I
DEBMAS06 Customer Master Data DEBMAS
A H
CREMAS05 Vendor Master Data CREMAS
S R
HRMD_A07 HR Master Data HRMD_A
WA
DELINS04 Delivery Schedule DELINS
E
Shipping Notification (ASN - Advanced Shipping
DESADV06 DESADV
B
Notice)
B
FINSTA01 Financial Status Update FINSTA
PA
PAYEXT01 Payment Order PAYEXT
IL
(Application Link Enabling) processes. IDocs allow structured
H
data to be transferred in a standardized format.
SA
1. What is EDI (Electronic Data Interchange)?
AR
EDI is used for electronic communication between different
business partners (external systems). It enables the structured
W
exchange of business documents (e.g., purchase orders,
E
invoices) between companies in a standardized format.
A BB
2. What is ALE (Application Link Enabling)?
P
ALE is used for data exchange between different SAP systems
(SAP-to-SAP communication). It enables distributed processing
by replicating and synchronizing master and transaction data
across SAP landscapes.
Types of IDocs
IDocs can be classified based on processing direction and usage:
1. Based on Processing Direction
IL
Inbound IDoc: Data flows into the SAP system from an
H
external system.
A
Outbound IDoc: Data flows out of the SAP system to an
S AR
external system.
E W
2. Based on Processing Mode
BB
Synchronous IDoc: Immediate processing (rarely used).
A
Asynchronous IDoc: Processed later in the background.
P
3. Based on Usage
Basic IDoc Types: Standard SAP structures defining the
format of data.
Extension IDoc Types: Custom-enhanced IDoc structures
based on business needs.
IL
systems.
🔹 Use Case: B2B communication (e.g., SAP to a supplier’s ERP system).
H
🔹 Data Format: Uses standardized formats like ANSI X12, EDIFACT, IDoc, XML,
SA R
JSON.
🔹 Processing Mode: Mostly Outbound (send to external) and Inbound (receive
A
from external).
W
Example EDI Flow:
E
SAP generates an Outbound IDoc (e.g., ORDERS for a sales order).
B
The IDoc is converted into an EDI format (e.g., EDIFACT) using middleware like
B
SAP PI/PO, Seeburger, or Gentran.
A
The EDI message is sent to the trading partner’s system.
P
The trading partner's system processes the message and may send an Inbound
EDI response.
The response is converted back to an IDoc in SAP and processed accordingly.
📌 Common EDI Messages in SAP:
ORDERS (Purchase Order)
INVOIC (Invoice)
DELINS (Delivery Schedule)
DESADV (Despatch Advice/Shipping Notice)
L
SAP landscapes.
I
🔹 Purpose: Communication between SAP systems within the same
H
organization.
A
🔹
S
Use Case: Transferring Material Master, Vendor Master, or
AR
Purchase Orders between SAP systems (e.g., SAP ECC to SAP
S/4HANA).
W
🔹 Data Format: Uses IDocs for data exchange.
E
🔹 Processing Mode: Can be Real-time or Batch Processing.
BB
Example ALE Flow:
A
The sending SAP system generates an Outbound IDoc.
P
The IDoc is transferred to the receiving SAP system using tRFC
(Transactional RFC).
The receiving SAP system processes the Inbound IDoc and updates
its database.
📌 Common ALE IDocs:
MATMAS (Material Master Data Transfer)
DEBMAS (Customer Master Data Transfer)
CREMAS (Vendor Master Data Transfer)
HRMD_A (HR Master Data Transfer)
IL
B2B Communication SAP-to-SAP
Purpose
H
(SAP ↔ Non-SAP) Communication
SA R
Exchanging
A
documents with Data distribution
W
Use Case external partners within SAP
E
(e.g., customers, systems
B
suppliers)
A B
ANSI X12, EDIFACT,
Formats IDoc only
P
XML, JSON, IDoc
Uses middleware
Uses RFC, tRFC,
Communication (SAP PI/PO,
or qRFC
Seeburger, etc.)