topic Re: how to debug outbound 855 in Application Development and Automation Discussions

how to debug outbound 855

Former Member — Wed, 05 Aug 2009 12:38:15 GMT

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

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:00:48 GMT

Hi,

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

Thanks & regards,

ShreeMohan

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:06:01 GMT

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

Re: how to debug outbound 855

Pawan_Kesari — Wed, 05 Aug 2009 13:15:45 GMT

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.

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:18:14 GMT

Put a break point in funciton module.

Thanks

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:21:04 GMT

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

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:21:12 GMT

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

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:21:44 GMT

Hi Naren,

I put a breakpoint and still did not work.

thanks

Joyce

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:36:21 GMT

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

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:36:29 GMT

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

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:42:16 GMT

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

Re: how to debug outbound 855

Pawan_Kesari — Wed, 05 Aug 2009 13:43:00 GMT

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) ?

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 13:55:38 GMT

need to reply to users

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 14:03:09 GMT

Hi Naren,

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

Thanks

Joyce

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 14:04:26 GMT

Hi ShreeMohan,

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

thank you !

Re: how to debug outbound 855

Former Member — Wed, 05 Aug 2009 19:19:20 GMT

Thank you to everyone who responded.

Re: how to debug outbound 855

Former Member — Tue, 06 Oct 2009 23:57:42 GMT

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

Re: how to debug outbound 855

Former Member — Wed, 07 Oct 2009 12:20:34 GMT

HI Brian,

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

Joyce

Re: how to debug outbound 855

Former Member — Wed, 07 Oct 2009 22:57:53 GMT

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

Re: how to debug outbound 855

Former Member — Thu, 08 Oct 2009 15:32:50 GMT

Brian,

Did you put 'Break' in your program ?

Joyce