Registering Personalization Objects 

To be able to use the central repository for personalization data, you must create a key with which the data is to be saved using transaction PERSREG. You can also specify the type of repository used and, if necessary, the function module for the dialog call.

Key

The personalization data is later accessed using the key.

Description

You can enter a short description of the personalization object in the Description field.

Class for Access / Use Standard Repository

The class for access to the personalization data is required if an external table is to be integrated. If the checkbox Use Standard Repository is checked, any class that is entered is ignored.  In this case, the generic repository for personalization data is used.

Dialog Function Module

You can enter the function module for the central dialog call here. This entry is only meaningful is the generic repository is used.

Application Component

The keys for central access to personalization data are structured by application components.

Various Indicators

·         Access via user maintenance

The personalization data for the specified key is taken into account when manipulating user data.

·         Access via role maintenance

The personalization data for the specified key is taken into account when manipulating role data.

·         Transport with Roles

The personalization data for the specified key is transported with the role for which it was created.

·         Visible in User Maintenance

The personalization data for the specified key is displayed in user maintenance and can be changed there.

·         Visible in Role Maintenance

The personalization data for the specified key is displayed in role maintenance and can be changed there.