The status of an IDoc
IDoc documents are used to exchange business documents such as purchase orders, invoices, delivery notes, etc. with an SAP system. Upstream of the SAP system, an EDI service provider typically converts the IDocs to and from the various formats of the individual business partners (for example, EDIFACT or ANSI ASC X12).
Errors can occur during processing of both inbound and outbound IDocs in the SAP system. For example, incomplete IDocs may arrive in the SAP system because a business partner has not sent all the information requested. In this case, the IDoc “hangs” in an error status.
The following figure shows an extract from SAP transaction BD87.
BD87 transaction with IDoc overview
© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.
For example, an outgoing IDoc has stuck in status 20. This status means ‘Error when triggering the EDI subsystem’. One reason for this error could be incorrectly configured settings in the system. The IDoc detail view provides more information. As soon as the error has been corrected, processing of the IDoc must be restarted. However, status 20 does not allow direct processing, so the status must first be set to 30. 30 stands for ‘IDoc is ready to send (ALE service)’.
A list of all the possible statuses of an IDoc can be found at the end of this article.
Change Status
To change the status of an IDoc, proceed as follows.
Call transaction SE38 and execute the program RC1_IDOC_SET_STATUS.
Program call in transaction SE38
© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.
The following report will then open. If you want to change the status of several IDocs at once, you can use the button next to the text field ‘IDOC number’ and specify several IDoc numbers.
© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.
You can then trigger the processing of the IDoc again — for example, in transaction WLF_IDOC.
Our blog is filled with helpful “how to” articles, which can be found by clicking the “How to Guides” tab on our blog overview page.
Any more questions?
Do you still have questions about IDocs or electronic data exchange with an SAP ERP system? Do not hesitate and contact us or use our chat. We’re always happy to help!
IDoc statuses
The following table provides an overview of the standard IDoc statuses in an SAP system.
| STATUS | Description |
|---|---|
| Outgoing IDocs (from SAP view) | |
| 00 | Not used, only R/2 |
| 01 | IDoc created |
| 02 | Error passing data to port |
| 03 | Data passed to port OK |
| 04 | Error within control information of EDI subsystem |
| 05 | Error During Translation |
| 06 | Translation OK |
| 07 | Error during syntax check |
| 08 | Syntax check OK |
| 09 | Error during interchange handling |
| 10 | Interchange handling OK |
| 11 | Error during dispatch |
| 12 | Dispatch OK |
| 13 | Repeat transmission (Retransmission) OK |
| 14 | Interchange acknowledgement positive |
| 15 | Interchange acknowledgement negative |
| 16 | Functional acknowledgement positive |
| 17 | Functional acknowledgement negative |
| 18 | Triggering EDI subsystem OK |
| 19 | Data passed to port for test |
| 20 | Error triggering EDI subsystem |
| 21 | Error passing data for test |
| 22 | Dispatch OK, acknowledgement still due |
| 23 | Error during retransmission |
| 24 | Control information of the EDI subsystem OK |
| 25 | Processing despite syntax error (outbound) |
| 26 | Error during syntax check of IDoc (outbound) |
| 27 | Error in dispatch level (ALE service) |
| 28 | IDoc sent to ALE distribution unit retroactively |
| 29 | Error in ALE service |
| 30 | IDoc ready for dispatch (ALE service) |
| 31 | Error, no further processing |
| 32 | IDoc was edited |
| 33 | Original of an IDoc that was edited |
| 34 | Error in the control record of IDoc |
| 35 | IDoc reloaded from archive |
| 36 | Electronic signature not performed (timeout) |
| 37 | Error when adding IDoc |
| 38 | IDoc archived |
| 39 | IDoc is in target system (ALE service) |
| 40 | Application document not created in target system |
| 41 | Application document created in target system |
| 42 | IDoc created by test transaction |
| Incoming IDocs (from SAP view) | |
| 50 | IDoc added |
| 51 | Application document not posted |
| 52 | Application document not fully posted |
| 53 | Application document posted |
| 54 | Error during formal application check |
| 55 | Formal application check OK |
| 56 | IDoc with errors added |
| 57 | Test IDoc: Error during application check |
| 58 | IDoc copy from R/2 connection |
| 59 | Not used |
| 60 | Syntax error in IDoc (inbound) |
| 61 | Processing despite syntax error (inbound) |
| 62 | IDoc passed to application |
| 63 | Error passing IDoc transfer to application |
| 64 | IDoc ready to be passed to application |
| 65 | Error in ALE service |
| 66 | IDoc waits for predecessor IDoc (serialization) |
| 67 | Not used |
| 68 | Error, no further processing |
| 69 | IDoc was edited |
| 70 | Original of an IDoc that was edited |
| 71 | IDoc reloaded from archive |
| 72 | Not used, only R/2 |
| 73 | IDoc archived |
| 74 | IDoc created from test transaction |
| 75 | IDoc is in inbound queue |
SAP ERP and SAP S/4HANA are the trademarks or registered trademarks of SAP SE or its affiliates in Germany and in several other countries.
