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

OUTBOUND IDOC DEBUGGING

Former Member
0 Likes
12,493

I have Output type defined for the application V3

i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.

This output type is defined for edi processing.

Now the problem is when invoice is created and this

outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code and find the function module that is running in the background for collection of data of invoice and

filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.

Help me out i will be waiting for the response.

6 REPLIES 6
Read only

Former Member
0 Likes
1,842

Hello Manish,

Im not getting ur problem exactly. However if u have the idoc number, try debugging with Tcode BD73. Check whether it stops in that FM.

Regards,

Senthil

Read only

Former Member
0 Likes
1,842

can u tell me how i will debug outbound idoc

Read only

0 Likes
1,842

Use the Tcode BD73 from the other end(SAP System). Give your idoc number and execute.

Regards,

Senthil

Read only

Former Member
0 Likes
1,842

In your invoice go to the outputs. Click on ZD00 and hit the Further Data button. Set the Dispatch Time to '1'. Place your breakpoint. Now use SE38 with program RSNAST00 to execute the output.

Now you will stop at your breakpoint.

Read only

0 Likes
1,842

Manish,

Go to EDI PROCESSING routine in RSNASTED program and set a break point there. When you create an output and save it, the control should stop at the break point. You should check to trigger the messages immediatley in the output configuration though.

Thanks,

Read only

Former Member
0 Likes
1,842

Hi,

You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.

Let me know if you need further help.

Thanks,

Eric