topic Re: Debugging EDI Outbound IDOC in Application Development and Automation Discussions

Debugging EDI Outbound IDOC

Former Member — Wed, 24 Dec 2008 08:04:58 GMT

Hi experts,

How to Debug the EDI outbound IDOC? I refered the fourm before i post but no clear idea....

Thanks.

Re: Debugging EDI Outbound IDOC

piyush_mathur — Wed, 24 Dec 2008 08:37:16 GMT

Hi,

If you have any Idoc which is alreday processed, then go to We19 and pass the existing Idoc no. There is an option avaliable to debug the Idoc process.

Regards,

Piyush

Re: Debugging EDI Outbound IDOC

Former Member — Wed, 24 Dec 2008 09:06:38 GMT

Hi Vino,

In case of problems using WE19, you can try to reprocess the same idoc in the debug mode. Various programs can be used to do this depending on the idoc status. The programs are:

Program RBDMANI2 for status 51

Program RBDAPP01 for status 64

Program RBDAGAIE for status 32 and 69 (Edited IDocs)

Program RBDSYNER for status 26

Program RSEOUT00 for status 30

etc.

The reports will require you to provide the idoc number.

Regards,

Nimish

Re: Debugging EDI Outbound IDOC

Former Member — Wed, 24 Dec 2008 09:14:53 GMT

HI,

IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc with BD87 you can have a breakpoint in the function and it will stop.For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase

orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).

Thanks & Regards

Sathish R Raj

Re: Debugging EDI Outbound IDOC

Former Member — Wed, 24 Dec 2008 09:21:05 GMT

goto WE41 (for outbound idoc) and check your message name, there is one function module attached for processing.

make breakpoint in that function module, you can debug that idoc now.

sandeep