topic Re: Resolve IDoc Errors in Application Development and Automation Discussions

Resolve IDoc Errors

Former Member — Wed, 20 Jun 2007 16:25:56 GMT

Could anyone define the ways in which IDoc errors are resolved?

Based on my understanding, any IDoc processing error (inbound or outbound) creates a pre-defined or custom workflow that eventually leads to the modification (if necessary) and re-processing of the IDoc.

Re: Resolve IDoc Errors

Former Member — Wed, 20 Jun 2007 18:30:04 GMT

You have to setup workflow.

If you want to process manually then execute transaction BD87 or

use program RBDINPUT and select status 51 .

I try to send breif workflow configuration.

Thanks,

Narayan

Re: Resolve IDoc Errors

Former Member — Wed, 20 Jun 2007 19:18:35 GMT

Status 30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)

Status 64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.

Status 51 - Error - application document not posted ( Problem at Partner profile )

Status 65 - Error in ALE service - indicates partner profiles are incorrect

Status 32 - Resubmit edited intermediate document (DO NOT USE)

See table TEDS1 for all status codes via SE16 in SAP

Re: Resolve IDoc Errors

varma_narayana — Thu, 21 Jun 2007 05:48:18 GMT

Hi Kevin,

You can resolve the Errors in IDOC processing in different ways.

In Outbound:

Status

29 Error in ALE Service (Problem can be in the Partner profile settings)

30 Idoc ready for dispatch (Execute the Report RSEOUT00 )

26 Syntax error in IDOC (When IDOC Data records are created properly)

We can use the Tcode BD87 to monitor the idocs and Reprocess the Failed idocs

In Inbound Processing

Status

51 Application doc not posted (When IDOC contains data that cannot be updated in the receiving system. Such as integrity errors, Missing mandatory fields etc.

Display the Application log to find the errors.

We can use IDOC test tool WE19 and execute the inbound processing using the inbound Function module in Debugging mode.

56 or 65 : Check the Partner profile settings.

62 : Application doc has to be posted using the report RBDAPP01

Hope this info would help you.

Regards,

Varma