on 01-15-2014 10:43 AM
Hi
We are implementing MDG 6.1 for Customers in co-deployment mode, meaning users that can create a CR can also access XD02 t-code;
Those users have XD02 in authorization object TCD.
How can we prevent them from using t-code XD02? We do not want them to bypass approval workflows.
Thanks
Access to the transaction is different than access to actually create data. Your security team can remove access to the transaction itself but leave the CVI authorization. Please discuss this with your security team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Radis,
This you can restrict in TA : SU21. Maintain/restrict the needed authorization object from MDG object class and regenerate the object.
Regards,
Reema
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.