Transaction Variants

[Former Member]

Hi,

We have created Transaction Variant ZMM02 for Transaction MM02.

We have not given access to MM02 transaction to a user , but only ZMM02.

But when they execute ZMM02 and enter data and save the transaction.

They are getting message : "You are not authorised to use this transaction MM02".

We do not want this message .

How can we prevent this message,since we have removed S_TCODE (MM02)

from users profile.

Priti

[Former Member]

Hi Priti,

After the message type su53 in the command and add the respective authorizations to the ZMM02 transaction.

Regards,

Gilberto Li

[Former Member]

Hi Gilberto,

Its checking for S_TCODE MM02 , but we do not want to add this in user profile.

Is there any other way ?

Regards,

Priti

[Former Member]

Hi Priti,

Try determining the authorization objects used by the MM02, and add them to the profile with the corresponding permissions.

And add to the S_TCODE ZMM02.

I think this are the ones:

M_MATE_BUK

M_MATE_LGN

M_MATE_MAN

M_MATE_MAR

M_MATE_MAT

M_MATE_MEX

M_MATE_MZP

M_MATE_STA

M_MATE_VKO

M_MATE_WGR

M_MATE_WRK

Regards,

Gilberto Li

null

[Former Member]

hi,

Probably there might be some AUTHORITY-CHECK code in the program.

Comment that out and try.

Regards

Subramanian

[Former Member]

HI preeti,

Authorization object will always come inbetween where you are using transaction variants. So the best way to do this is create your own transaction using the programm name and window name for the second screen.

In your programm set parameters for the 1st screen.

In case of mm02 create transaction ZMM02 for programm name SAPLMGMM and screen name 4004.

So programm may look like...

PARAMETERS: p_matnr TYPE RMMG1-MATNR,

AENNR TYPE RMMG1-AENNR.

SET PARAMETER ID 'AEN' FIELD p_AENNR.

SET PARAMETER ID 'MAT' FIELD p_matnr.

CALL TRANSACTION 'ZMM02'.

[Former Member]

Hi,

We have created transaction for Transaction Variant . Since, we have used Transaction MM02 and variant ZMM02 .

The system is checking for authority check MM02 , which we do not want .

Regards,

Priti

[Former Member]

Hello -

I am interested as to whether this issue was further analyzed/resolved? I am facing a similar issue with XD02 and would like to know if anyone has managed to restrict certain fields to a subset of users using a custom transaction (ZD02) WITHOUT granting access to all functionality within XD02. Any help or input would be greatly appreciated.

Thanks,

Tiffany

[Former Member]

Try note 529116. It resolved the issue for me. Now when I save a change I get the message 'Your changes have been saved'. Beautiful... but I have sent back a note to SAP because after the save it returns you to the main screen for another material like the regular MM02 transaction but the Back and Exit buttons do not work so you have to cancel the session.

If you try note 529116 and you have the same issue with the back and exit button could you let me know and let SAP know, so I am not the only one requesting this change.

[Former Member]

Try note 529116. It resolved the issue for me. Now when I save a change I get the message 'Your changes have been saved'. Beautiful... but I have sent back a note to SAP because after the save it returns you to the main screen for another material like the regular MM02 transaction but the Back and Exit buttons do not work so you have to cancel the session.

If you try note 529116 and you have the same issue with the back and exit button could you let me know and let SAP know, so I am not the only one requesting this change.

[Former Member]

Try note 529116. It resolved the issue for me. Now when I save a change I get the message 'Your changes have been saved'. Beautiful... but I have sent back a note to SAP because after the save it returns you to the main screen for another material like the regular MM02 transaction but the Back and Exit buttons do not work so you have to cancel the session.

If you try note 529116 and you have the same issue with the back and exit button could you let me know and let SAP know, so I am not the only one requesting this change.

[Former Member]

SAP generally does th S_TCODE check at a system level and then relies on the program for any additional authorization checks.

Hwoever SAP commonly uses drill down which takes your from own transaction to another. Because of this MM02 has been developed by SAP to recheck for S_TCODE to ensure that you are allowed to you use this tcode rather then just rely on the MM auth objects that allow you to change.

You have one of two options:

- Create a complete costum version of the MM02

- Check if MM02 has a BAPI that will allow you to check that if you have Z_TCODE ZMM02 to ignore the failed check for MM02 (ive never dont this - but it may be possible)