Managing Views 

In a view, users are able to save information on column structure, sorting criteria, filter conditions, various display options, and so on. In this way, they are able to display their ALV outputs with the same properties every time.

You are able to use your application to affect the options that users have for using views.

You are not able to use the ALV object model to either create or delete views.

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 (see SET_DATA).

You must therefore make sure that a view is clearly assigned to both the current application and the data structure that is currently loaded. To do this, you give the data structure a unique key. All views that the user saves from now on are given this identifying key.

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

For information on showing and hiding UI elements for views, see Providing Standard ALV Functions.

User-Specific View/Non-User-Specific View

Views can be available to only one user or for all users of your application. Consequently, views are either user-specific or non-user-specific.

A user of your application normally generates a user-specific view. To save a non-user-specific view, the user must have authorizations for personalization and configuration functions (see Personalization and Configuration).