how to debug outbound 855

[Former Member]

Hi all,

I have an EDI outbound sales order confirmation 855. I need to modify the program.

How can I debug the program ?

thanks

Joyce

[Former Member]

Hi,

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

Thanks & regards,

ShreeMohan

[Former Member]

Hi ShreeMohan,

None of the tables containthe message type I am looking for. I like to debug the sales order confirmation EDI 855.

Thanks

Joyce

[Pawan_Kesari]

What is the message type. Incase it is ORDRSP the processing module will be IDOC_OUTPUT_ORDRSP.

To debug you need to process the idoc in online mode.

[Former Member]

Hi

Put a break point in funciton module.

Thanks

[Former Member]

Hi Pawan,

I put a breakpoint in the customer processing module for 855. Since this is an outbound sales order, i create the output type which recreate the sales order confirmnation and send it out via EDI. It worked but it did not stop at breakpoint.

thanks

Joyce

[Former Member]

Hi Naren,

I put a breakpoint and still did not work.

thanks

Joyce

[Former Member]

Hi,

You can also do in one more way,

Initially, you need to put a break point at the Outbound Idoc Processing Routine. Then, while performing the operation on that Tcode or Screen, for which the Idoc is going to get triggered, go into the Debugging Mode and then set as following:

Settings --> Update Debugging --> Save. Automatically, while running that operation the control will come to the break point area and you can debug the Idoc.

Pls get back to me in case of any queries on the same.

Thanks & regards,

ShreeMohan

[Former Member]

Hi ShreeMohan,

It worked this time ! Why so much work to get to a debugging ?

thank you !

[Former Member]

Joyce:

I'm having the same difficulty in getting to my break-point.

What was your best method of getting the debug to stop for you?

Thanks!

// Brian

[Former Member]

HI Brian,

Follow the reply from ShreeMohan. Do a print preview to debug.

Joyce

[Former Member]

hmmm...

1. << check tables TBDME and TBDA2 to check which function creates the IDOC. Set breakpoit there... >>

I get nothing. From WE20 (partner profile) my message type is ORDRSP and my iDoc type is ORDERS05. My application is V1 message control message type is ZEDI and the process code is SD10.

2. << The IDoc is generated by message control (output control). >>

3. << Go to NACE transaction. . >>

4. << For your output type, go to the condition record. >>

with appication set to V1 and my Condition record ZEDI. My Medium type is set to "1" (for print). I set the Date/Time to "1".

5. << Change the timing to '1' -> Message will be processed by report RSNAST00. >>

6. << After this go transaction and make changes. This time the IDoc will not be generated. You will see the output type proposed (with yellow). >>

When I bring up a Sales Order (VA03) and look at >> Extras >> Output >> Header >> Edit , I see the date/time is set to 4. OUtput is configured to go out the the filesystem, as it will be picked up for EDI translation to be sent to my customer.

7. << Now go to RSNAST00 and give the output type. On executing you will stop at the breakpoint set. >>

I get .. there are none.

I'm still missing something!

Thanks!

// Brian

[Former Member]

Brian,

Did you put 'Break' in your program ?

Joyce

[Former Member]

<< Did you put 'Break' in your program ? >>

Yes. both a "soft" break point and a (in the customer function) a coded break-point.

// Brian

[Former Member]

<< Now go to RSNAST00 >>

OK, it stopped this time. I set a new output in an old sales order, using >> Extras >> Output << Header >> Edit. Then under "Further data", I changed the Dispatch Time to "1" - send with periodically scheduled job. Then executed RSNAST00.

Thanks for the help.

// Brian

[Former Member]

Hi,

The IDoc is generated by message control (output control).

Go to NACE transaction. .

For your output type, go to the condition record.

Change the timing to '1' -> Message will be processed by report RSNAST00.

After this go transaction and make changes. This time the IDoc will not be generated. You will see the output type proposed (with yellow).

Now go to RSNAST00 and give the output type. On executing you will stop at the breakpoint set.

Thanks &regards,

Shree

[Former Member]

Hi ShreeMohan,

I did what you stated and changed to 1. Still yellow but do not work. The program is using RSNASTED instead of RSNAST00.

This is EDI outbound confirmation. I went to RSNASTED and it did not stop there.

thanks

Joyce

[Former Member]

Hi

Put a break point in function module .

From application repeat the output as triggered bacth

give ur object key in RSNASTED

200% it will stop in ur FM

tHANKS

[Pawan_Kesari]

Could you describe the way you are testing or the transaction you are using to test it.

Is there any Idoc generated after test?

What is the direction, message type of Idoc (get this from WE02 transaction) ?

[Former Member]

Hi Naren,

Still do not work. What do you mean by 'give ur object key in RSNASTED' ?

Thanks

Joyce

[Former Member]

need to reply to users

[Former Member]

Thank you to everyone who responded.

[uwe_schieferstein]

Hello Joyce

The debugging of outbound IDocs is described in the blog:

[Debugging Outbound IDoc Output Control scenarios|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/6355] [original link is broken] [original link is broken] [original link is broken];

There are additional hints in the comments to this blog. When you are in the debugging mode set a specific break-point at the function module for outbound processing (presumably IDOC_OUTPUT_ORDERS).

Regards

Uwe

[Former Member]

Hi Uwe,

Thank you for additional info.

Joyce