topic Re: debugging outbound idocs in Application Development and Automation Discussions

debugging outbound idocs

Former Member — Tue, 11 Dec 2012 03:57:25 GMT

Hi Experts ,

how can we debug outbound idocs through WE19 tcode only,

how we can debugging outbound idoc's

OUTBOUND IDOC DEBUGGING

i have refered above links i couldnot find any clear information.

could you please suggest how to proceed.

if give any screen shot examples that would be appriciate

Thanks in advance

Regards,

Srini.

Re: debugging outbound idocs

vinoth_aruldass — Tue, 11 Dec 2012 05:40:47 GMT

hi,

for example,

Take Sales order Outbound
IDoc Process as an example.

Put the Break points in outbound programs, where ever you want.

Enter T Code VA02 for changing the order.

Provide the Order number and Press enter.

In Menu Path: Extras -> Output -> Header -> Edit.

Select the Output type and Click on Repeat output button.

Now Select the Output type again and click on further data button.

Select Send with periodically scheduled job.

Click on Back.

Now click on Save. An entry will be created in NAST table, once order is saved.

Go to SE11 and Check the entry in NAST table by providing Application and Date.

Copy the Object Key.

Now Go to WE15 to process Outbound IDoc.

Provide Application, Object Key and Output Type. And Execute.

ABAP Debugger will be on.

hope this will be helpful

Re: debugging outbound idocs

Former Member — Tue, 11 Dec 2012 05:50:39 GMT

Hi Vinoth Aruldass ,

thanks for your quick response .

here we donot have authorization to SE11 and VA02 tcodes .

how can we do further way

is there any option from WE19

Regards,

Srini.

Re: debugging outbound idocs

vinoth_aruldass — Tue, 11 Dec 2012 05:57:33 GMT

hi ,

other wise check tables TBDME and TBDA2 to check which function creates the IDOC. Set breakpoit there.

hope this helps,

Vinoth Aruldass

Re: debugging outbound idocs

Former Member — Wed, 12 Dec 2012 08:12:59 GMT

Hi Srinivas,

if you not have at least WE20 for partner profiles, you can find out the process code. Than with the processcode you can find the function module in transaction WE41. Place the breakpoint at FM entry and start..

Robert