Show TOC

Background documentationConfiguring Views Locate this document in the navigation structure

 

You can configure Web Dynpro applications and therefore specify at design time which details are presented to users during their work and which are not. In addition, administrators and users can make and save their own settings at runtime and therefore adjust the application by means of customization and personalization (see Personalization and Configuration).

In the ALV component there are also various options for modifying a standard set of properties and providing users with suitable variants depending on their business needs. Unlike in the rest of the Web Dynpro environment, however, you cannot make this configuration at design time. At design time, it is possible that the structure to which the configuration relates has not yet been specified. For this reason you cannot, as is usual, use the application configurator to configure your ALV output.

Personalization, Configuration, and Customizing of an ALV Output

Depending on who is modifying the ALV output, a differentiation is made between the following strategies:

  • Personalization: One of the functions of the ALV output that is available to users is the saving of views. Users can save information about column structure, sort criteria, filter conditions, various display options, and so on, in an unlimited number of views. In this way, users can always display the ALV output with the properties they choose. However, these views are only available to the user who created them. Other users cannot see these views. This form of modification of the ALV output is referred to as 'personalization'.

  • Configuration: Application developers can neither create nor delete views using the classes and methods of the ALV configuration model. They can, however, start their ALV component in a special mode, create an unlimited number of views for it, and deliver these views with the product. Views that application developers save in this way are stored as configuration data records and are transported and delivered together with their ALV programming. This form of modification of the ALV output is referred to as 'configuration'. The following sections describe the options available when saving configuration data records:

  • Customizing: At customer sites, administrators can change the views they provided or insert their own views. These views are then available to all users client-wide. This form of modification of the ALV output is referred to as 'customizing' (see User-Independent, Client-Wide Modifications in Personalization).

    Note Note

    For configuration and for Customizing, you must start the application in the respectively required mode and make the necessary settings at runtime.

    End of the note.
Views and Data Structure of ALV Configuration Model

All settings that the user saves in a view for an ALV output relate to the fields of a specific data structure of the ALV configuration model. If, for example, you load another structure, the settings for the view may not work.

You must therefore ensure that the system can uniquely assign a view to both the current application and the data structure that is currently loaded. You flag the data structure with a unique key (KEY). All views that the user saves from now on are given this identifying key.

Recommendation Recommendation

You can find an example of this in the documentation for the Interface Controller SALV_WD_TABLE.

End of the recommendation.

You can get all settings for a view using the method GET_CONFIG_DATA in the interface controller of the ALV component.

More Information

You can find more detailed information on the methods of the Interface Controller in the system in the controller documentation for the SALV_WD_TABLE.