EXIT_SAPMM06E_012 TRTYP changes

[pratik30]

Hello Experts,

I am facing issue with user exit exit_sapmm06e_012. I am having a screen exit i.e. additional screen in item as shipping. The user exit here is to check some business changes made in PO through ME23n.

So when I make changes in PO quantity (Standard field in ME23N) the TRTYP is V for both before and after entering the user exit. thus the program can track the changes and work as expected.

Now when I try to make changes only in shipping tab which is created through screen exit, the TRTYP is V before going into user exit and becomes A when we go inside it, due to which the check gets fails and our program fails to work accordingly.

So is this due to custom screens the program behaves differently or there is any other issue.

Thank you

[pratik30]

Hello Experts,

I am facing issue with user exit exit_sapmm06e_012. I am having a screen exit i.e. additional screen in item as shipping. The user exit here is to check some business changes made in PO through ME23n.

So when I make changes in PO quantity (Standard field in ME23N) the TRTYP is V for both before and after entering the user exit. thus the program can track the changes and work as expected.

Now when I try to make changes only in shipping tab which is created through screen exit, the TRTYP is V before going into user exit and becomes A when we go inside it, due to which the check gets fails and our program fails to work accordingly.

So is this due to custom screens the program behaves differently or there is any other issue.

Thank you

[VXLozano]

I'm having a dejà vu... maybe is this an update of a question you recently deleted?

Anyways, it's the same thing: which are the scopes of the TRTYP when you debug the process before and after entering the user exit?
I have a hunch: different scopes, and one has the value from the current status and the other the previous one.

[pratik30]

Hi vicen.lozano ,

Thank you for your reply and yes I did delete the earlier question 🙂

Yes the scopes are different, but the question here is why for some changes it still remains V and for changes in custom field it changes to A.

[VXLozano]

There are different variables, if the scope is different. As I told you, probably one of them is a pre-save status and the other one a post-save.
They should be the same value only if they were the same variable (i.e. you were controlling their value in the same FORM). Then you could know the variable was changed in the EXIT, and you should debug the EXIT.