MWMTO002 Not Triggering

[Former Member]

Dear All,

I have to update some table ( Not LTAK or LTAP) and I found the above mentioned user exit.

However, after creating and activating this enhancement , this enhancement is not triggering during the confirmation of the TO.

The description of the component is: User Exit at End of TO Confirmation (in Update Task)

I found from another SDN post that it directly will not get triggered during TO confirmation.But, I want to check what data at the run time system is capturing in this exit, how can I check that ?

I have tried by setting a breakpoint in the FM - CALL FUNCTION IN UPDATE TASK, but ultimately could not fathom anything.

Please help,

Thanks in advance.

[Former Member]

Dear All,

I have to update some table ( Not LTAK or LTAP) and I found the above mentioned user exit.

However, after creating and activating this enhancement , this enhancement is not triggering during the confirmation of the TO.

The description of the component is: User Exit at End of TO Confirmation (in Update Task)

I found from another SDN post that it directly will not get triggered during TO confirmation.But, I want to check what data at the run time system is capturing in this exit, how can I check that ?

I have tried by setting a breakpoint in the FM - CALL FUNCTION IN UPDATE TASK, but ultimately could not fathom anything.

Please help,

Thanks in advance.

[brad_bohn]

You can use Runtime Analysis to determine whether or not the enhancement is part of the call stack. The enhancement is called in 2 different functions; do a where-used of the function component to find the call points if you haven't already and set your breakpoints there (or check the Runtime Analysis hit list for the function names). If you want to debug the functions in the update task, make sure you have the update debugger turned on.

[Former Member]

Hi Brad,

Thanks for the quick response.

However, as you said can you help me in - how to debug an update task, I am really a newbie in this field !!

See, my ultimate aim is to check at the debugging mode i.e. at the runtime, what are the values which are getting populated in this exit.

Thanks again,

[brad_bohn]

You simply need to set a breakpoint in the code before the update function call and then inside the function call. When the code stops in debug before the function call, turn on the update debugger (Settings -> Update Debugger). As a result, your breakpoint inside the function will also hit (you may have to hit 'continue' at first when the update task triggers).

[Former Member]

Hi Brad,

Many many thanks.

After I received your reply, I did a bit of google on Update debugging and learned how to set it on.

After that, I tested and this time the breakpoint triggered.

Thanks again, closing the issue.

N.B. - For switching on debugger in update mode, go to normal debugging mode, then go to settings > Display/Change debugger settings > Update debugging.

Helpful tip for functional consultants like me !!