Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

How do you debug an iDoc?

Former Member
0 Likes
25,495

I have an OUTBOUND idoc created via WE19 and wish to debug it as it is created. I have put soft break points in all of the code but it never hits one of these points.

Also - how do you run WE19 in the foreground?

Thanks.

Scott

Edited by: Alvaro Tejada Galindo on Jan 21, 2008 5:54 PM

Edited by: Scott Strong on Jan 22, 2008 9:25 AM

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
18,921

Hi Scott,

You can debug the IDoc processing like this,

1.Find the Inbound/Outbound Processing function (using t-code WE41/WE42 respectively)

2. put a break-point at the 1st executable staement in the the function module

3. In WE19, click Inbound Function or Outbound processing button and execute in 'foreground' mode and also dont forget to select check box 'call in debuggin mode'.

Execution will stop at the break-point.

Regards,

SR

6 REPLIES 6
Read only

Former Member
0 Likes
18,921

If it is inbound Idoc then go to WE19 and after entering the data click on inbound function module button and give the function module name and then select the check box Call in debugging mode and click on continue button. It will stop at the related function module in the debug mode.

And select the radio button In foreground.

Hope it helps.

Thanks,

Srinivas

Edited by: Srinivas R on Jan 21, 2008 11:12 PM

Read only

Former Member
0 Likes
18,921

Hi Scott,

In we19, once you click 'Inbound Function Module', you will get an check box for 'Call in Debugging Mode'.

Enable the check box, it will let you debug the application.

For collecting IDOCs in WE20,

you have to enable the radio button 'Trigger by background program'.

It can be viewed in this path,

we20-> create inbound parameter ... In this screen, you can find the above option.

shylesh

Read only

Former Member
0 Likes
18,921

WE19 tcode is the Test tool for IDOC. You can put a break-point in the correspond inboound or outbound function module for that IDOC and debug it

Also check this thread.

Regards,

Maha

Read only

Former Member
0 Likes
18,921

Hello Scott,

You can debug IDOC processing in the following way in WE19:

(1) Find the Inbound/Outbound Processing function (WE41/WE42)

(2) Apply break-point at the debugging location inside the function

(3) In WE19, click Inbound Function or Outbound processing button and execute in 'foreground' mode.

You will find that the program flow stops at break-point.

Thanks,

Venu

Read only

Former Member
0 Likes
18,922

Hi Scott,

You can debug the IDoc processing like this,

1.Find the Inbound/Outbound Processing function (using t-code WE41/WE42 respectively)

2. put a break-point at the 1st executable staement in the the function module

3. In WE19, click Inbound Function or Outbound processing button and execute in 'foreground' mode and also dont forget to select check box 'call in debuggin mode'.

Execution will stop at the break-point.

Regards,

SR

Read only

0 Likes
18,921

You cannot use WE19 to debug the outbound IDoc being created. It is already created. What you need to do is to repeat the output of the sap document in question and set it to 1 ( output via batch job ) or what ever the option is called.

Then run program RSNAST00.

Dont forget to put a break point in the function module that creates the IDoc though.

Edited by: Martin Shinks on Jan 22, 2008 4:05 PM