Transaction SU21: Authorization Object Class Assignment

Updated May 18, 2018

While using the transaction of Su21 for maintaining of authorization of objects. There are few of the problems that occurs. What are these problems and give a proper solution for it.

Comments

24 May 2016 6:18 pm Abhijeet Mudgal Helpful Answer

The problem that occurs while using transaction SU21 to authorization object maintenance are:
a) System starts to display authorized object lists of the dummy class object “ Not assigned to class”.
b) The Authorized objects that are already in system but they are a part of Authorization class object. But these objects are not declared in system thus they can neither be displayed nor corrected by using SU21.
c) SAP namespace which are missing in system it can only be entered using only Support Package. The advance manual correction cannot be used.

24 May 2016 6:22 pm Abhijeet Mudgal Helpful Answer

The solution for the above are as follows:
a) The display of authorization object list “Not assigned to a class” is there when only one type of authorization object lists is not defined with any defined object class assignment.
b) The object class “Objects having invalid object classes” is a dummy class object is only displayed when only one abject assignment class had been defined which is not existing in the current system.
c) Option for implementation of advance correction is added to stringent name checking of class objects which is implemented with a 1135888. Now and object class can be created in SAP namespace after the confirmation of relevant message warning and relevant SAP Software Change Registration (SSCR).