Configuration of an Included ALV Component 

An application developer has the option of setting up the ALV component so that it matches the including application. For this purpose, the ALV component provides predefined interface methods. From the viewpoint of the application developer, the ALV component is therefore a component application whose configuration is performed by the application developer himself/herself using interface methods released by the ALV.

A configuration of the ALV component in the configuration editor does not make any sense since the data structures used are not known at design time. Therefore, configuration is possible for embedded ALV components at runtime.

Storage Options for Personalization Settings

Just like other components, an embedded ALV component always provides a dialog for personalization data. Here, implicit and explicit configuration options are offered. You can call up this dialog at runtime via the Settings link and make the required settings.

If you start, in administration mode, the application that embeds the ALV component, you have the option of storing this setting as a customized setting for all clients. If you have developer authorization for the embedding component, you will also be offered the option of additionally saving the setting data as configuration data. In this case, the data – just like all other component configurations – is stored as separated development objects and supplied with a TADIR entry.

 

●     Customizing and personalization of the ALV component can be set as the default view by selecting the Initial View flag in the Save dialog or in the ALV component settings.

●     If a configuration is to be set as the default, you must select the previously saved configuration of the ALV component for the relevant ALV component usage in the application configuration. You can either change an existing application configuration or create a new configuration for the application.

●     For the application configuration to become effective, you must either set it as the default configuration in the application itself or it must always be passed as a URL parameter. This can be set in the Portal iView, for example.