Authorization Checks in Configuration/Personalization

Each Web Dynpro ABAP application should be able to be personalized or configured. There are two variants of personalization – one for the administrator and one for the end user. The end user has limited personalization options, whereas the administrator can change practically all the properties of screen elements.

When the personalization process is started, the development authorization is checked at runtime using authorization object S_DEVELOP. If this authorization has been assigned to the user, he or she is allowed to carry out all actions, including personalization and configuration.

If authorization object S_DEVELOP is not assigned to the user, authorization object S_WDR_P13N is checked for. S_WDR_P13N provides authorization to personalize if the user has no developer authorization.

Authorization object S_WDR_P13N should be set by the application if it is required.

Authorization object S_WDR_P13N contains the following fields:

·        OBJNAME

Name of the Web Dynpro ABAP application. This allows you to restrict the applications which the user can personalize. If no restrictions are needed, enter *.

You can find the personalization options for the UI elements offered to the end user and to the administrator  in the documentation on the properties of UI elements (see Reference ).