SAP architecture · Lesson

IDoc

Quick answer

IDocs are one of the most common integration mechanisms in SAP, robust, restartable and well-monitored.

Key takeaways

An IDoc is a container with a defined structure, a control record (routing/metadata), data records (the actual business data in…
IDocs are exchanged using ALE (for SAP-to-SAP) or EDI subsystems (for external partners).
Transactions like WE02/WE05 display IDocs and their statuses; a status 51 (error) or 30 (ready to dispatch) tells you what happened.
Watch out: Ignoring IDoc statuses when troubleshooting (e.g. status 51).

What an IDoc is

An IDoc is a container with a defined structure, a control record (routing/metadata), data records (the actual business data in segments), and status records (its processing history). It represents a business document (an order, a delivery, material master) in a standard, system-independent format.

How IDocs flow

IDocs are exchanged using ALE (for SAP-to-SAP) or EDI subsystems (for external partners). Outbound, SAP generates an IDoc and sends it; inbound, SAP receives an IDoc and posts it into the application. Each IDoc carries a status telling you exactly where it is in that journey.

Monitoring IDocs

Transactions like WE02/WE05 display IDocs and their statuses; a status 51 (error) or 30 (ready to dispatch) tells you what happened. IDoc monitoring and reprocessing are everyday tasks in an integrated landscape.

Why IDocs matter

IDocs are one of the most common integration mechanisms in SAP, robust, restartable and well-monitored. Understanding their structure, statuses and tools is essential for anyone touching interfaces.

Common pitfalls

Ignoring IDoc statuses when troubleshooting (e.g. status 51).
Confusing IDoc, ALE and EDI roles.
Not monitoring the IDoc queue, errors pile up silently.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

Which statement is true of IDoc?
- A. SAP’s classic architecture is a three-tier client-server model, presentation, application and database…
- B. Vendor management in MM concerns the vendor master data, now the Business Partner in S/4HANA, that…
- C. An IDoc is a container with a defined structure, a control record (routing/metadata), data records (the…
Show answer
C. An IDoc is a container with a defined structure, a control record (routing/metadata), data records (the…
Covered in the “What an IDoc is” section of this lesson.
Which of these also applies to IDoc?
- A. It represents a business document (an order, a delivery, material master) in a standard, system-independent…
- B. Guessing instead of using the reference tools.
- C. Using the wrong variant (e.g. create vs change vs display).
Show answer
A. It represents a business document (an order, a delivery, material master) in a standard, system-independent…
Covered in the “What an IDoc is” section of this lesson.
Which part of the Learn SAP curriculum covers IDoc?
- A. SAP how-to guides
- B. SAP architecture
- C. SAP labs
Show answer
B. SAP architecture
This lesson sits in the SAP architecture section of the Learn SAP course.

Frequently asked questions

What does IDoc mean in SAP architecture?

An IDoc (Intermediate Document) is SAP’s standard structured document format for exchanging business data between systems, for example sending orders, invoices or master data to and from SAP. IDocs are a cornerstone of SAP integration, especially with EDI and other SAP systems.

What connects to IDoc in SAP architecture?

IDocs are exchanged using ALE (for SAP-to-SAP) or EDI subsystems (for external partners).

Which transaction codes come up with IDoc?

Transactions like WE02/WE05 display IDocs and their statuses; a status 51 (error) or 30 (ready to dispatch) tells you what happened.

What tends to go wrong with IDoc in SAP architecture?

Ignoring IDoc statuses when troubleshooting (e.g. status 51). Confusing IDoc, ALE and EDI roles. Not monitoring the IDoc queue, errors pile up silently.