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

message control method--orders05 basic type

VivekG
Participant
0 Likes
1,148

Hi All,

I am triggering idoc with message type ORDERS(basic type ORDERS05). I am using message control technique to trigger the same and am successful in doing that with me23n transaction.

I need to extend the ORDERS05 BASIC TYPE to add additional fields in idoc. Now I am putting a break point in IDOC_OUTPUT_ORDERS fm but when triggering the idoc from ME23N , ITS not stopping at any point or user exit in IDOC_OUTPUT_ORDERS. Please help why its not stoppiojg at the break point in triggering FM??

Thanks,

Vivek Gupta

9 REPLIES 9
Read only

VivekG
Participant
0 Likes
1,026

Adding to above thread, the idoc is being created but control is not stopping in the triggering FM idoc_output_orders.

I need to debug to add the logic to extend this idoc type.

Please help.

Vivek

Read only

Former Member
0 Likes
1,026

Activate "update debugging" to debug the IDOC function module attached to output type. For this activate normal debugging using /h, then after starting debugging select the menu option "Settings->update Debgging".

Regards

Vinod

Read only

0 Likes
1,026

Hi,

This way, I am able to come in debugging but how will the debugging control come inside the triggering function module idoc_output_orders please explain.

Vivek Gupta

Read only

0 Likes
1,026

Put implicity break point inside the function "idoc_output_orders" to debug the function module. Since your idoc processing is based on message control (output type), the execution will as update task, that's why you have to activate "update debugging" to debug the function module.

Regards

Vinod

Read only

0 Likes
1,026

Hi Vinod,

Thanks for quick replies. I have put a break point in the FM idoc_output_orders but control is not stopping there.

When executing ME23N and putting output type and giving /h before saving in me23n in order to trigger idoc, control is stopping at ME_UPDATE_DOCUMENT program but after this on pressing F8 the debugging control is not coming inside FM inspite of putting a break point there.

Please help.

Thanks,

Vivek

Read only

0 Likes
1,026

Check whether update debuggin is on. As per me IDOC will be created only through ME21N & ME22N. Since ME23N is only for display, nothing is getting updated in database and no update task will be executed.

Regards

Vinod

Read only

0 Likes
1,026

Hi,

As the idoc is being created while manually entering the o/p trype in me23n then control should also stop at the break point right??

why its not stopping at that point even when idoc is being created.

Vivek Gupta

Read only

0 Likes
1,026

Hi ,

Got the solution actually, i have to keep the output type status as send through periodically scheduled job and then run program RSNAST00 to trigger the idoc. This way the control is stopping at the FM.

Thanks for ur help any ways...

Vivek

Read only

VivekG
Participant
0 Likes
1,026

Its solved on my own