topic Re: INCLUDE DOUBT in Application Development and Automation Discussions

INCLUDE DOUBT

Former Member — Tue, 27 Jun 2006 19:24:58 GMT

Hi all,

I HAVE FM IDOC_OUTPUT_ORDERS AND FROM THERE I HAVE EXIT_SAPLEINM_002 IN WHICH I HAVE AN INCLUDE ZXM06U02 IN WHICH I HAVE CODE WRITTEN . cAN ANYBODY TELL WHEN THIS INCLUDE IS GOING TO GET TRIGERRED .

PLEASE LET ME KNOW IF YOU NEED ANY DETAILS.

DEEPTHI

Re: INCLUDE DOUBT

Manohar2u — Tue, 27 Jun 2006 19:34:36 GMT

This include will get triggered when inbound/outbound idoc gets processed.

Try to create some sample idoc from we19 and process the same, and check whether this gets triggered or not.

Am not sure whether its an inbound or outbound?

Regds

Manohar

Re: INCLUDE DOUBT

Former Member — Tue, 27 Jun 2006 19:46:45 GMT

I AM CREATING A PO AS SOON AS PO IS CRETED I SEE AN IDOC BEING CREATED IN WE02 T CODE.

I have no idea about idoc's ,can you tell me when that include is goint get triggered.

thanks in advance

Re: INCLUDE DOUBT

Former Member — Tue, 27 Jun 2006 19:46:54 GMT

This is an outbound IDoc, so it is probably associated with an output type of an order. When you create/change the order, the output associated with this order will be triggered and depending on the timing(immediate or scheduled), you can either find it processed in NAST table with object key equal to order number or you will find it in new status in NAST.

Run RSNAST00 program, enter the output type, object key(=order number) and execute. If you have a breakpoint in your include it will stop there.

Re: INCLUDE DOUBT

JackGraus — Tue, 27 Jun 2006 19:48:32 GMT

Did you already create an enhancement (transaction CMOD) for MM06E001 and activated it ? When the PO output timing is in the PO update (mode 4) you have to enable update debugging to hit your include. But easier is to set the output to batch processing (mode 1) and then trigger the PO output via ABAP RSNAST00.

best regards Jack