Skip to Content
avatar image
Former Member

Always many "New" authorizations when I edit authorizations....

Guys...

A thing that irritates me a lot is all these u201CNewu201D objects that keep appearing when I am making minor changes to a role.

Let me explain. If I am making a big role (many transaction codes) from scratch there might be 10-15 authorizations for e.g. S_TABU_DIS, one for each transaction code based on the SU24 input. If I want to make this role display only, rather than editing all authorizations I keep one and deactivate the rest (not delete, just deactivate).

Next day I want to delete a transaction code (not the first time the customer changes their mind!) when I edit the authorizations a large number of authorizations are u201CNewu201D and I have to go though them to inactivate them again.

Am I doing something wrong or is it just SAPu2019s way of keeping us busy?

/vitofava

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 30, 2011 at 08:47 PM

    I hope there are not many auth objects in a CHANGE status and causing Yellow trafic light problem.

    If the object which had status as STANDARD is changed directly instead of creating a copy of it (and then changing it in the copy while deactivating the standard one), then when you change the role agains t-codes in menu will pulls the auth object again in Standard status.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      The choice of transaction should be your weapon of prefered choice, so what you are looking for here is transaction SU01D for display only.

      As SU01 has the capability of being used in a display only manner, you can also consider removing the ACTVT values and leave the field open to being maintained. If chosen, then this should be done early (i.e. before other roles are dependent on the fields being filled with values.

      If you set to inactive and create a manual authorization, then you loose the benefit of SU24 to propose changes to the object in the role again in future.

      Worste-case scenario is to change the authorization directly. Even with copying and changing the copy, this still hurts you a lot when you upgrade.

      Cheers,

      Julius

  • avatar image
    Former Member
    Mar 30, 2011 at 02:53 PM

    You are doing something wrong and this is SAP's way of keeping you busy if you do not read the manual before you start using an application... 😉

    Cheers,

    Julius

    Add comment
    10|10000 characters needed characters exceeded