variant tcode ZME22N

[Former Member]

A transaction code ZME22n has been created in the R/3 system as a variant to ME22N.

Now, when the transaction is being run, it calls for ME22N internally and is thus causing authorization issues to the users since this transaction has not been granted.

Question: Is it possible to restrict the call of ME22N? if yes, can it be restricted by security methods or by the program methods?

Please provide your opinions on the same.

Thanks, Nitin

[Former Member]

Hi,

You can make use of CALL Transaction. This is the task of ABAPers. You can work with them to include the CALL Transaction and call ME22N transaction code in your custom transaction.

However, you still may need to tag all the authorization objects required to execute ME22N to have the user execute the custom transaction code.

Regards,

Raghu

[Former Member]

Hi,

Please refer to following thread for further details on this issue

[;

Thanks,

Sandipan

[former_member701183]

Hi,

Can you check whether restriction can be imposed via tcdcouples table or se97 in case of call transaction problems..please check and let us know if any issue.

Regards

Aveek.

[Former Member]

Not possible. SE97 does not work in all cases.

You can only switch the screen variant of ME22N itself or use ME22.

Cheers,

Julius

[Former Member]

Hi Nitin

What is the difference between ZME22N and ME22N please?

Regards

David