Fitting Web Dynpro to Your Needs

You can fit a Web Dynpro application to your needs on a number of different levels and through a number of different people.

• The fundamental modelling of a Web Dynpro application occurs on the development level . Here, the various Web Dynpro components used in the application are created in the Web Dynpro Explorer, programmed, and given a basis configuration by developers.

• On the Customizing level , these applications with their basis configuration can be fitted to enterprise-specific requirements at the customer site for all users. This is done without modification. These kinds of adjustments usually occur on the client-level. The Customizing level can only be called up in administrator mode . This level has a transport link that allows changes in the system landscape to be transported.

• On the personalization level , these applications can be changed on the user level by individual users in various ways to fit their personal needs. This is done without modification.

In each of these levels, Web Dynpro distinguishes between implicit and explicit changes, each of which generates its own configuration schema. These configuration schemas are not identical, but may contain some of the same attributes.

Implicit configuration (processing view: Web Dynpro Built-In) allows user interface elements to be changed by determining their attributes, such as visibility, texts, and standards values, in the development phase. The changes you make here are processed automatically by the Web Dynpro runtime. They are completely transparent for the application, which means that they can be changed at any time.

The attributes that can be changed for a user interface element depend on the element as well as the user group. Developers and administrators have access to all of an element's attributes, while application users personalizing the application have only a limited selection of attributes that they can change. Developers and administrators can also block an attribute from being changed. You can set this block using the Final indicator in implicit configuration. There is also the Cannot Be Personalized indicator. When it is set, any settings made on the personalization level are ignored and reset to the settings from the Customizing or development levels.

Explicit configuration (processing view: Component-Defined) allows you to define user-specific configuration schemas in the development phase as Web Dynpro configuration contexts. To do this, Web Dynpro provides generic user interfaces and a transport link. In Web Dynpro runtime, the configuration context for an application is filled in automatically, meaning that the application can react appropriately to the configuration content.

Explicit configuration is used in Floorplan Manager for composing and adjusting application interfaces and is set up as a standard configuration mode in the Floorplan Manager Configuration Editor .

For more information, see SAP Library for Web Dynpro ABAP: Adaptation .