Personalization and Configuration 

When business requirements are mapped onto an ERP system, many standard applications arise that can be implemented by different companies. This does not automatically mean that also the user interface of a business application is always the same. Depending on the very different factors (for example, the required function of an application, size, or business industry of a company), changes to the UI of an application can vary greatly. On the other hand, it is often necessary to give users of business applications the option of independently co-designing the UI through which they perform their work  Applications that are created with the help of Web Dynpro ABAP can be adjusted in different ways and by different target groups. In this context, we distinguish between two areas:

 

Configuration

The configuration of business applications takes place in two subsequent steps:

First, configuration data records are created for the individual Web Dynpro components (Component Configuration). Such configuration data records are absolutely necessary when using generic components, such as the ALV or Pattern component. Configuration data is created and edited mainly by developers.

The following step is the application configuration. Each of these used components is required in a particular configuration. The application configuration defines which component with which configuration is required for the application. This step, too, is carried out primarily by application developers.

Application and component configuration data is created and maintained with the help of the configurator.

Personalization and Customization (Cross-Client Adjustments)

In contrast to configuration, personalization is a function that is also available to the user of an application and provides him or her with the option of adjusting the application to suit his or her own personal requirements or preferences. The framework for variation options within personalization is less far-reaching than that in configuration; personal settings in the UI must never limit the running ability of an application. Personalization of an application is performed directly by a user from within the current application.

It is possible to maintain personalization settings in a uniform manner for larger user groups (adjustment – also called customization). A system administrator can process personalization settings on the basis of his or her extended authorization, provided the respective application runs in so-called configuration mode. For more information, refer to the chapter Personalization.

Configuration of Web Dynpro applications of a Web Dynpro component takes place almost always at design time (only exception here is the configuration of a bound ALV Component; see also Component Configuration). In contrast to this, personalization and customization are always executed at runtime of an application.