4 minute read

Reprocessing IDocs in SAP ERP

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.

Webinar - Achieving Deep ERP SAP Integration
View our webinar in which we look in depth at 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­tusDes­cript­ionPro­gra­mCo­de
51Appli­cation doc­ument not pos­tedRBDMANI2
56IDoc with errors addedRBDAGAI2BD84
60Error during syntax check of IDoc (inbound)RBDSYNEI
61Processing despite syntax error (inbound)RBDAGAI2BD84
63Error passing IDoc to applicationRBDAGAI2BD84
64IDoc ready to be transferred to app­lica­tionRBDAPP01BD20
65Error in ALE ser­viceRBDAGAI2BD84
66IDoc is waiting for pre­dece­ssor IDoc (serial­izat­ion)RBDAPP01BD20
69IDoc was editedRBDAGAIEWPIE

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­tusDes­cript­ionPro­gramCo­de
02Error passing data to portRBDAGAINBD83
04Error within control infor­mat­ion of EDI sub­systemRBDAGAINBD83
05Error during translationRBDAGAINBD83
25Processing despite syntax error (outbound)RBDAGAINBD83
26Error during syntax check of IDoc (outbound)RBDSYNEO
29Error in ALE ser­viceRBDAGAINBD83
30IDoc ready for dispatch (ALE service)RSEOUT00WE14
32IDoc was editedRBDAGAIEWPIE

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!

You may also find the following articles helpful:

Subjects

most read

Keep on reading

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.