User-exit after Transfer Order Confirmation ?

[Former Member]

Hello !

I need to write a specific ABAP code just after a standard Transfer Order Confirmation. That confirmation can be done using transactions LT12, LT24, LT11, etc, in foreground or background modes.

Is there any user-exit or an enhancement-point that I can use ?

Thanks for any help !

Mauro.

[Former Member · Accepted solution]

Hi,

Check this

MWMTO002 - Enhancement

EXIT_SAPLL03T_002 - User Exit at End of TO Confirmation (in Update Task)

Regards

Sumanth

[Former Member · Accepted solution]

Hi Sumanth !

I tried to use the enhancement MWMTO002, but SAP simply doesn't execute the code I've written in the User Exit !

I wrote a BREAK-POINT and activated it. But when I run transaction LT12 nothing happens...

Is there another customization I have to do before I can use this User Exit ?

Thanks again !

Mauro.

[Former Member · Accepted solution]

Hi Mauro,

Since this EXIT gets triggered in Update Task. You have to change your system debugging settings. When to run LT12 and go into debug mode(using /h) functionality.

Check the Update debugging option at the below config.

Settings->Display/Change Debugger settings->Update debugging.

Let me know if this works.

Regards

Sumanth

[Former Member · Accepted solution]

Hello Sumanth !

Yes, it works perfectly !! Thanks a lot !!

My problem now is that I have to do a COMMIT in that User Exit, because I must change the status of  more than one Kanban when a TO is confirmed...

I'm using the "BAPI_KANBAN_CHANGESTATUS1" to make the change, and that BAPI requires a COMMIT between each call... but the User Exit doesn't allow me to do a COMMIT...

Thanks a lot for any other idea !

Mauro.

[Former Member · Accepted solution]

Hi Mauro,

Since you are using "BAPI_KANBAN_CHANGESTATUS1", are you using COMMIT WORK? If so use "BAPI_TRANSACTION_COMMIT".

Let me know if this helps.

Regards

Sumanth

[Former Member · Accepted solution]

Hello Sumanth !

I tried the "BAPI_TRANSACTION_COMMIT" but it returns a DUMP :

"Calling a COMMIT WORK in an update process is not allowed

  because the function modules triggered in a Logical Unit

  of Work cannot then be processed correctly."

And if I don't use a COMMIT, only the first kanban is changed...

Thanks again,

Mauro.

[Former Member · Accepted solution]

Hi Mauro,

Check the below link,

http://scn.sap.com/thread/840429

If the above link doesnt help, try to post in ABAP forum.

Regards

Sumanth

[Former Member · Accepted solution]

Hello Sumanth !

Thanks a lot for all your help and attention !

I found the solution here : http://scn.sap.com/thread/1906285 !

Best regards,

Mauro.

[Former Member · Accepted solution]

This message was moderated.

[Former Member]

Hi..

I am going to use user exit MWMTO002 in T-Code LT12 too. I have created the code and assign to project as well. but when i set the break point and tried LT12, the transaction doesn't stop in that exit. I have changed Debugger settings to Update debugging but still not succeed.

Please Help..

Thanks Advance

[Former Member]

Hello Budhi !

Are you sure you have activated the enhancement (transaction CMOD) ?

Best regards,

Mauro.

[Former Member]

Hi Mauro!

Thanks for your reply, previously i assign this exit with other exit in one project. but then i tried to assign this exit to one project and it works.thanks.

I add some logic in that exit, and add the message error if the condition is false.

when i tried this case (when the the condition is false) the message error was not appeared. but when i exit the transaction there was message error : Express Document "Update was terminated" founded.

the question: is that possible to add the message error and remove express document message in this exit?

Thanks

[Former Member]

Hi,

The "Express Document termination" is a short dump and which can be seen in T.code - SBWP(Inbox). Check your code once.

Regards

Sumanth

[Former Member]

Hello Budhi !

Much probably, the exit is running in "update task"... that's why you can't send an error message, ok ?

(An error message, in this exit, raises an exception and causes that kind of dump).

I think you have to find another way to stop the transaction...

Best regards,

Mauro.