SAP's long-standing document format for system-to-system exchange — and the monitoring most estates never set up.
An IDoc (Intermediate Document) is SAP's structured container for exchanging business documents between systems. It has a control record identifying type and partner, data records holding the content in segments, and status records tracking what happened. IDocs are asynchronous: one is created, queued and processed, and each step records a status.
IDocs remain the backbone of SAP integration in most estates, and the common failure is not the format but the silence. Because processing is asynchronous, a failed IDoc does not interrupt anyone — it sits in error status. Without active monitoring, the first sign of a problem is a customer asking where their order went.
Message type, basic type, sender and receiver partner, direction. This is what routing decisions read.
The content, in segments and fields defined by the basic type and any extension.
A trail of what happened. 53 means posted successfully inbound; 51 means an application error; 03 means sent outbound.
Defined per partner and message type, controlling processing mode, ports and whether processing is immediate or batched.
Error statuses need an owner and a daily review. Most errors are data problems that can be corrected and reprocessed.
A business receives sales orders from a customer by EDI, converted into IDocs. For four weeks everything looks fine, because the interface is judged by whether IDocs arrive rather than by whether they post.
Then a reconciliation finds thirty-one orders missing. All thirty-one IDocs arrived and all thirty-one sit at status 51 — application error. The cause is mundane: the customer added new ship-to locations that do not exist in SAP, so the orders cannot post. The IDocs are not lost, they are parked, and nobody has looked at the queue because nothing alerted.
Two lessons follow, and the second matters more. An inbound interface needs monitoring on posting status rather than on receipt, with an alert on anything sitting at 51 past a threshold — an hour, not a day. And a reprocessing procedure has to exist before it is needed, because the fix here is to create the ship-tos and reprocess, which is straightforward if someone has done it before and alarming if nobody has.
| Term | What it means |
|---|---|
| Basic type | The IDoc structure definition — which segments exist and how they nest. |
| Segment | A record within the IDoc, roughly equivalent to a line or a block of fields. |
| Partner profile | Configuration saying which partner sends or receives which message type, and how. |
| Status code | The processing state. The numbers matter: 53 is posted successfully, 51 is an application error. |
| Extension | A customer addition to a basic type, for fields the standard structure does not carry. |
The most common and most expensive gap. Failed IDocs accumulate silently and surface as business problems weeks later.
Immediate processing on a high-volume interface can overwhelm the system. Collect and batch instead.
Application errors indicate a data or configuration problem that will keep recurring until it is fixed at source.
Interfaces need a named owner. Without one, errors are everyone's problem and therefore nobody's.
| Metric | What it tells you | What distorts it |
|---|---|---|
| IDocs in error status | The health of the interface. Should be checked continuously, not at reconciliation. | |
| Time in error before resolution | How quickly failures are noticed. Usually the real gap rather than the error rate itself. | |
| Error reasons by category | Master data gaps, mapping faults or genuine business exceptions — three different fixes. | |
| Reprocessing success rate | Whether errors are genuinely fixed or repeatedly retried against the same cause. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.