4 minute read

Reprocessing IDocs in SAP ERP


IDocs are the central import and export format of SAP ERP systems. The basic structure and concepts behind IDocs can be viewed in our other article. During the inbound and outbound processing of IDocs, errors can occur, leading to IDocs getting stuck in specific error states. It is the responsibility of the designated SAP user to restart the IDoc processing. In most cases this is not done by the business department itself, but rather by a trained employee who also looks after other EDI topics in the company, for example.

The following image shows the central starting point for identifying faulty IDocs in a SAP ERP system – transaction BD87.

Selection screen of transaction BD87
Selection screen of transaction BD87

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

With the help of this transaction it is possible to filter IDocs according to specific criteria, e.g. Show all faulty outbound DESADV since yesterday.

An IDoc always holds a specific status in an SAP ERP system. This status is defined by a status code (those interested in how the status of an IDoc can be changed can read our article here). Depending on the state an IDoc gets stuck in, it is necessary to use different programs to reprocess the IDoc. Naturally, before doing so you must first correct the issue that is keeping the IDoc from being processed.

White Paper - EDI Integration in SAP

Reprocessing of inbound IDocs

To process inbound IDocs, the following programs can be utilised. If it is available, a program can also be called with the assigned transaction code, which is displayed in the last column.

Sta­tus Des­cript­ion Pro­gra­m Co­de
51 Appli­cation doc­ument not pos­ted RBDMANI2
56 IDoc with errors added RBDAGAI2 BD84
60 Error during syntax check of IDoc (inbound) RBDSYNEI
61 Processing despite syntax error (inbound) RBDAGAI2 BD84
63 Error passing IDoc to application RBDAGAI2 BD84
64 IDoc ready to be transferred to app­lica­tion RBDAPP01 BD20
65 Error in ALE ser­vice RBDAGAI2 BD84
66 IDoc is waiting for pre­dece­ssor IDoc (serial­izat­ion) RBDAPP01 BD20
69 IDoc was edited RBDAGAIE WPIE

To call a program in SAP you can use transaction SE38 as shown in the following image.

Calling a program via transaction SE38
Calling a program via transaction SE38

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

Type the respective program name in the text field Program and start it by pressing F8.

Reprocessing outbound IDocs

To process outbound IDocs the following programs can be utilised.

Sta­tus Des­cript­ion Pro­gram Co­de
02 Error passing data to port RBDAGAIN BD83
04 Error within control infor­mat­ion of EDI sub­system RBDAGAIN BD83
05 Error during translation RBDAGAIN BD83
25 Processing despite syntax error (outbound) RBDAGAIN BD83
26 Error during syntax check of IDoc (outbound) RBDSYNEO
29 Error in ALE ser­vice RBDAGAIN BD83
30 IDoc ready for dispatch (ALE service) RSEOUT00 WE14
32 IDoc was edited RBDAGAIE WPIE

SAP frontends IDoc reprocessing

SAP offers two additional programs which serve as the frontend for all programs used for the processing of inbound and outbound IDocs. There are no transaction codes assigned to both of these programs, which is why they usually need to be started via transaction SE38.


By using program RBDINPUT it is possible to call different programs for the processing of inbound IDocs. The following image shows the user interface of the application.


© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.


With the help of program RBDOUTPU the different programs for outbound processing of IDocs can be called. The following image shows the frontend of the program.


© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

Do you have any questions?

Do you still have any questions regarding the topic of processing IDocs in SAP ERP systems? Feel free to contact us, we’re always happy to help!

You may also find the following articles helpful:


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. 


most read

Keep on reading

3 minute read

How to create an SAP transaction code

Want to know how to create an SAP transaction code for an existing ABAP program so that you can easily call the program?

6 minute read

How to Set Up and Manage Automatic SAP Jobs

SAP jobs can be used to automate processes in SAP ERP so they can be carried out without user intervention. We explore the key features.

4 minute read

IDoc Status Change in SAP ERP

IDoc statuses are not always the clearest - particularly when errors occur. In this article we explain how to change IDoc status as required.

5 minute read

How Can I Add an Entry to an SAP Table?

In this article we show how to add entries to an existing SAP table - even if it does not have its own maintenance dialog.

5 minute read

Alternatives to the Seeburger PI Adapter

The end of maintenance for the Seeburger PI Adapter is imminent. What alternatives are there and which is the best suited for your business?

4 minute read

IDocs in SAP S/4HANA: The Differences to SAP ECC 6.0

The change to S/4HANA also impacts the format of IDocs. In this article we explore IDocs in S/4HANA and the new and changed elements.

11 minute read

Migration to SAP S/4HANA - 5 Key Considerations

Are you prepared for migration to SAP S/4HANA? Discover the 5 key questions all businesses looking to upgrade to SAP's new ERP system should consider.

11 minute read

Exchange of Electronic Invoices with the SAP eDocument Framework

Companies have to increasingly implement e-Invoicing for different countries. This blog post explains how the SAP eDocument Framework can help you.

2 minute read

How Can You Save an IDoc from SAP on Your Hard Drive?

Wondering how to export IDocs as a file on your local computer? We created a handy guide!

5 minute read

Create and Process UBL Documents with Attachments in SAP

Enable your SAP solution for UBL based e-Invoicing over Peppol. Click here for an example case based on the XRechnung in Germany.

6 minute read

IDoc Processing in an SAP ERP System with Transaction BD87

Companies utilising SAP ERP and exchanging documents need a central tool to manage, view and search for IDocs. Transaction BD87 is the answer.

12 minute read

EDI_DC40: Understand the SAP IDoc Control Record

A correctly filled control header is essential for the identification and processing of IDocs. We show what settings are needed in SAP.

We use cookies to provide an optimal website experience. You decide which one you want to allow. Depending on the setting, however, not all functionalities may be available to you. Data protection & imprint.