Data Storage/Personalization Hierarchy

The personalization hierarchy consists of personalization nodes (such as the node for the cost center information system). Nodes in the personalization hierarchy often relate to a particular application or iView (for example, the node for cost center planning is associated with the planning application). This is usually the case for the node at the lowest level of the hierarchy. For this reason the nodes in the personalization hierarchy are also designated as ‘personalization applications’. However, it is possible for different applications/iViews to access the same personalization node, meaning the same personalization application.

At least one personalization characteristic (such as internal order ) is assigned to each personalization application. Each personalization characteristic relates to a particular personalization application of the personalization hierarchy. For this reason, the values (personalization data) for that characteristic are assigned to this personalization application separately for each user. For each characteristic, the corresponding ABAP Dictionary information is stored so that the associated personalization data (characteristic values) can be read by type, displayed, and saved.

For each characteristic, the personalization data can be stored in the form of one or more individual values, intervals, or groups.

Inheritance

One basic function of the personalization hierarchy is the inheritance of characteristics. The characteristics are inherited from the top down based on the hierarchy path. An application that uses personalization accesses the hierarchy at a particular level (this is often the lowest level). The application then receives the personalization data of that initial level as well as all levels above it. This means that certain central characteristics are stored higher up in the personalization hierarchy in personalization applications (for example, in the personalization hierarchy for financials applications the characteristic controlling area ). Other, more specific characteristics on the other hand are stored much lower in the personalization hierarchy.

Personalization Dialog

The personalization dialog is an input template that the end user or administrator can use to predefine or restrict the selection criteria of an iView. As a rule, a particular personalization dialog is assigned to an iView. The end user can call this up, providing he has the necessary authorization, from the iView by choosing Personalize Data . In Customizing under  Cross-Application Components General Application Functions Generic mySAP Suite Functions Personalization Personalization Data: Collective Processing an administrator can call up all of the existing personalization dialogs, and enter personalization data for several end users centrally.

Administrative data entered for a characteristic is overwritten by the personalization data defined individually by the end user for this characteristic. The administrative data is valid for each characteristic again the moment the individually personalized data for this characteristic is deleted.

The administrator can simulate the data entry of an end user, for example if an error message is issued for an end user. The following IMG activity is available for this:  Cross-Application Components General Application Functions Generic mySAP Suite Functions Personalization Personalization Data: Single Processing .