When processing incoming and outgoing IDocs in an SAP system, exception errors are likely to occur. Depending on the type of error, the IDocs will remain in a passive state until processing is manually restarted.

In today’s blog post we show how faulty IDocs can be reprocessed.

SAP IDocs

IDocs are the central import and export format of SAP ERP systems. The basic structure and concepts behind IDocs can be viewed in our previous article. During the inbound and outbound processing of IDocs errors can occur, which lead 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 for example, also looks after other EDI topics in the company.

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

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, which is defined by a status code. Depending on the state an IDoc gets stuck in, it is necessary to use different programs to reprocess the IDoc. Naturally, before doing so it is first necessary to correct the issue that is keeping the IDoc from being processed.

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

Type the respective program name in the text field Program and start its execution 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) RBDSYNEI -
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 for the reprocessing of IDocs

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.

Program RBDINPUT

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.

Program RBDINPUT

Program RBDINPUT

Program RBDOUTPU

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.

Program RBDINPU

Program RBDINPU

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 would love to help you!