SAP IDoc errors
IDoc errors interrupt document-based integration (orders, invoices, master data). This page covers diagnosing and reprocessing failed IDocs.
When an expected document did not post, open WE02 or WE05, filter by status and message type, and read the failing IDoc's status records, which carry the application error. The causes, in order: a status 51 application error, a missing or wrong partner profile in WE20, missing master data, an outbound dispatch problem. Fix, then reprocess in BD87.
- Open WE02/WE05, filter by status (e.
- Watch out: reprocess through BD87 rather than the display transaction, or you create duplicates.
Symptom
An expected document did not post; an IDoc sits in error (commonly status 51 inbound, or a dispatch error outbound).
Start here: read the evidence
Open WE02/WE05, filter by status (e.g. 51) and message type, and read the status records of the failing IDoc, they carry the application error message that explains why it did not post.
Likely causes, in order
- Status 51, application error on inbound posting (data/config).
- Missing/incorrect partner profile (WE20).
- Master data missing for the inbound document.
- Outbound dispatch errors (RFC/port/partner).
How to fix it
- Read the status-record error text in WE02.
- Fix the underlying data or configuration.
- Reprocess with BD87 (or correct-and-test with WE19).
- Confirm the IDoc reaches status 53 (posted).
Preventing recurrence
Monitor IDoc queues proactively (errors are invisible if unwatched), keep partner profiles correct (especially after system copies), and ensure required master data exists before inbound posting.
Common pitfalls
- Guessing instead of reading the log/dump.
- Fixing the symptom, not the root cause.
- Changing several things at once.