Web Dynpro ABAP Configuration FrameworkLocate this document in the navigation structure

Use

When business applications are mapped to an ERP system many complex standard applications are created whose user interfaces do not necessarily meet individual requirements. With the Web Dynpro ABAP configuration framework you can adapt Web Dynpro applications without having to change the source code in an application.

Structure of the Web Dynpro ABAP Configuration Framework

Adaptations can take place in three layers: Personalization, Customizing, and Configuration. Not all the layers have to exist. A user can personalize a Web Dynpro application at runtime, if neither a configuration nor a customizing exists. If, say, a customizing does exist, a personalization will sit on top of this.

Built-In Functions

For each Web Dynpro application the configuration framework functions are activated in the standard setting. This is known as the Built-In Adaptation.

  • Personalization

    Users can personalize interfaces individually, that is, for a a single user. Your adaptation options are restricted to functions that do not affect the running of an application. At application runtime, for instance, you can move table columns, hide UI elements using the context menu, or set default values for input fields. These adaptations are persisted implicitly, which means that you are not requested to save these changes.

    For more information: Personalizing Web Dynpro Applications

  • Customizing

    Administrators can make these settings for the whole client. These adaptations are made at runtime. There are other ways you can change the appearance of the user interface, for instance, by adding Decorative UI Elements. You can also specify which adaptations users are allowed to change. You save the adaptations you make explicitly, and you can transport them too.

    For more information: Customizing Web Dynpro Applications

  • Configuration

    Developers adapt Web Dynpro components for the whole system, and define which settings can be overwritten in customizing or personalization. Make sure that the correct component configurations are available to users. You define the configuration at design time in the configuration editor. Administrators can use this editor to adapt a configuration in the customizing layer.

    For more information: Configuring Web Dynpro Components

Component-Defined Adaptations

If the built-in functions are not sufficient, developers can enhance a Web Dynpro component using the infrastructure of the configuration framework. Your enhancement will then be visible in the configuration editor and can be configured here. You can also implement a user interface with which your component-defined functions are also available at runtime in the layers above.

For more information, see Enhancing a Configuration with a Component-Defined Adaptation

More Information

  • Floorplan Manager

    The framework of the Floorplan Manager is based on the configuration framework. FLUID provides an enhanced editor with which you can configure complex applications with a standardized and consistent user interface.

    For more information: Floorplan Manager for Web Dynpro ABAP

  • Web Dynpro ABAP Page Builder

    The Web Dynpro ABAP Page Builder is also based on the configuration framework and provides a runtime authoring environment where pages can be created and adapted in the different layers.

    For more information: Page Builder

Enhancement Framework

Another way to enhance existing Web Dynpro applications without having to change the source code is to use the Enhancement Framework. These changes are saved as modification-free programming.

For more information: Modification-Free Enhancements