SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP IDoc Status Codes Reference

Every IDoc carries a status that tells you where it is in its life: created, dispatched, posted or stuck. This reference lists the status codes you will see in WE02, WE05 and BD87, with the direction and the first thing to check.

Download:

Status	Direction	Kind	Meaning	Typical next step
01	Outbound	Info	IDoc created	Wait for the dispatch job or run RSEOUT00 / WE14
02	Outbound	Error	Error passing data to port	Check port in WE21 and the target path or RFC destination
03	Outbound	Success	Data passed to port OK	No action, IDoc has left SAP
04	Outbound	Error	Error within control information of EDI subsystem	Check the EDI subsystem log and the control record
05	Outbound	Error	Error during translation	Check the translation or mapping in the EDI subsystem
06	Outbound	Info	Translation OK	No action
07	Outbound	Error	Error during syntax check	Check the EDI syntax result from the subsystem
08	Outbound	Info	Syntax check OK	No action
11	Outbound	Error	Error during dispatch	Check the partner connection in the EDI subsystem
12	Outbound	Success	Dispatch OK	Wait for acknowledgement if the partner sends one
29	Outbound	Error	Error in ALE service	Read the status log; check filters, conversion rules in BD64 and SALE
30	Outbound	Waiting	IDoc ready for dispatch (ALE service)	Run RSEOUT00 or WE14, or check the partner profile collect setting
31	Both	Error	Error, no further processing	Create a corrected copy or discard; nothing will reprocess it
32	Both	Info	IDoc was edited	Check the original in status 33
33	Both	Info	Original of an IDoc which was edited	No action, kept for audit
34	Outbound	Error	Error in control record of IDoc	Check sender, receiver and partner profile in WE20
37	Outbound	Error	IDoc added incorrectly	Review the control record and segment data for the incorrect entry
38	Both	Info	IDoc archived	No action
40	Outbound	Error	Application document not created in receiving system	Check the application error returned by the receiving system
41	Outbound	Success	Application document created in receiving system	No action
50	Inbound	Info	IDoc added	Wait for the processing job or run BD87
51	Inbound	Error	Application document not posted	Read the message in BD87 or WE05, fix master data or customizing, reprocess
52	Inbound	Error	Application document not fully posted	Review which items failed, correct and reprocess
53	Inbound	Success	Application document posted	No action
56	Inbound	Error	IDoc with errors added	Fix the control record or partner profile in WE20, then edit and reprocess
60	Inbound	Error	Error during syntax check of IDoc (inbound)	Correct the segment structure or mandatory fields in WE19
62	Inbound	Info	IDoc passed to application	No action
63	Inbound	Error	Error passing IDoc to application	Check that the inbound function module and process code exist in WE42
64	Inbound	Waiting	IDoc ready to be transferred to application	Run RBDAPP01 or BD87, or check why background processing is not scheduled
65	Inbound	Error	Error in ALE service	Check inbound ALE settings, filters and conversion rules
66	Inbound	Waiting	IDoc is waiting for predecessor IDoc (serialization)	Process the predecessor first or run RBDAPP01 with serialization in mind
68	Inbound	Error	Error, no further processing	Edit and reprocess or discard
69	Inbound	Info	IDoc was edited	Check the original in status 70
70	Inbound	Info	Original of an IDoc which was edited	No action
73	Inbound	Info	IDoc archived	No action

Outbound statuses run 01 to 42 and inbound statuses run 50 to 74. Status text can differ slightly by release, so confirm in WE47 (IDoc status maintenance). Always read the status record message in WE02 or WE05 before reprocessing.

Cut the IDoc error backlog

Ask for a review of your recurring 51 and 56 errors and whether a private AI triage assistant would help.

Optional. The tool and every export work without this. No spam.

How to use the reference

Filter by the number you see in WE05 or by a word such as posted or waiting. Use the Direction and Kind columns to narrow the list, then read the next step column for the transaction to open. Export the table to Excel to give your support team a one page cheat sheet for the interface runbook.

Reading outbound versus inbound statuses

Outbound IDocs start at 01 and a healthy one normally ends at 03 when it leaves SAP, or at 12 if an EDI subsystem confirms dispatch. Inbound IDocs start at 50 and a healthy one ends at 53 when the application document is posted. Anything between those and the error codes means the process is waiting or failed.

03 or 12 is the normal outbound end state
53 is the normal inbound end state
51 means the business posting failed, usually data or customizing
64 and 30 mean ready but not yet processed or sent

Typical reprocessing path

For a 51, open BD87, double click the error to see the application message, fix the cause such as a missing material, plant or posting period, and reprocess. For a 56 or 60, fix the control record or segment data through WE19 or the IDoc edit function, then reprocess. For a 64, schedule RBDAPP01 so it stops piling up.

Common mistakes

Reprocessing a 51 repeatedly without fixing the cause floods the log. Deleting IDocs in status 51 hides a real business gap. Leaving statuses 30 and 64 untouched for days usually signals a missing background job, not an application problem.

Frequently Asked Questions

What does IDoc status 51 mean?

Status 51 means the IDoc reached the application but the business document could not be posted. The status record holds the real error message, for example a missing material or a closed posting period. Fix the cause and reprocess in BD87.

What is the difference between IDoc status 53 and 03?

Status 03 is an outbound success: the IDoc was passed to the port. Status 53 is an inbound success: the application document was posted. They never appear on the same IDoc because the direction differs.

Why is my IDoc stuck in status 64?

Status 64 means it is ready for the application but no process has picked it up. Usually the background job for RBDAPP01 is missing, or the partner profile is set to trigger by background program. Run BD87 manually to confirm.

How do I reprocess an IDoc in error?

Use BD87 for inbound IDocs or WE14 and BD75 for outbound. Fix the root cause first, then select the IDoc and process in foreground to see the message. For control record problems, edit the IDoc through WE02 or WE19 first.

Netray can build an assistant that reads your IDoc status logs and groups failures by root cause, running privately next to your SAP landscape.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools