Is it possible to restrict layouts user based?
Answer:
The ALV contains the S_ALV_LAYO authorization object as of Release 46C. The activity of this authorization object is checked within the ALV. This authorization object can be used to further restrict the authorization for saving layouts (predetermined by the developer).
You will obtain the following results if the authorization does not exist for S_ALV_LAYO:
- I_SAVE = ' ' -> layouts cannot be saved
- I_SAVE = 'A' -> is set to 'U'
-> only user-specific layouts can be saved
- I_SAVE = 'X' -> is changed to ' '
-> layouts cannot be saved
- I_SAVE = 'U' -> user-specific layouts can be saved
If you do not want the ALV authorization check on the
S_ALV_LAYO object, you can set the IS_LAYOUT-NO_AUTHOR parameter to 'X'.
As a result, an authorization check will not occur when you call the ALV.
Also:
There is the authorization object S_ALV_LAYO with the authorization field 'ACTVT' (activity) and the value '23' for "Maintain". All ALV versions (Classic, Grid Control and Grid in full screen) perform an authorization check against this object. Users whose profile contains the value '23' are then allowed to create and maintain standard layouts and save them as defaults.
The authorization object can be checked via transaction SU21, object class BC_Z, S_ALV_LAYO and only exists from Release 46C.
