topic Re: difference b/w process codes and processing routines in EDI in Application Development and Automation Discussions

difference b/w process codes and processing routines in EDI

Former Member — Mon, 18 Jan 2010 13:14:35 GMT

Hi,

While configuring EDI for any partner we specify process codes at message control tab in partner profile, also we specify processing routines at output types.

what is the functionality happened at process codes and processing routines?

I have tried to debug the application by keeping break-points at process codes and processing routines, but i'm not able to enter into debugging mode, but finally i'm able to post the document and create IDoc.

Thanks in advance..

Re: difference b/w process codes and processing routines in EDI

brad_bohn — Mon, 18 Jan 2010 15:12:27 GMT

Generally, you need to turn on your update debugger if you want to debug output processing. Without going into too much detail, your 'processing routine' is the subroutine in your output program that is configured in NACE and called dynamically based on a read of the TNAPR table during output processing. If you have specified an ALE/EDI output mode, then the standard program and routine are used which further reads your partner profile and message configuration. Your 'process code' is the function that is configured in your ALE/EDI setup to format and fill the IDOC prior to dispatch.

Re: difference b/w process codes and processing routines in EDI

Former Member — Tue, 19 Jan 2010 04:24:55 GMT

Thanks Brad,

But I have taken ST12 trace while posting the document, but i could not find at least any process code call or processing routine program 'RSNASTED' in the trace. how these programs are triggered.

In such case, how to turn ON update debugging?

Re: difference b/w process codes and processing routines in EDI

brad_bohn — Tue, 19 Jan 2010 15:01:39 GMT

Like I mentioned, it's a read of TNAPR and a dynamic call from the application program. You will see the output program in the ABAP call stack if the output is set to process immediately. If not, then you need to run RSNAST00 to process the output.

You turn on the update debugger using Settings -> Update debugging from the debugger.