- SAP Web Dynpro Tutorial
- SAP Web Dynpro - Home
- SAP Web Dynpro - Overview
- Configuration & Integration
- Architecture
- Navigation
- Component
- Mapping & Data Binding
- Event & Actions
- Application
- URL of an Application
- Creating an Application
- Component Interfaces
- Faceless Components
- Assistance Class
- Service Call In an Application
- Using a Service Call
- Debugging an Application
- Version Management
- Messages
- Integration Messages
- Personalization & Configuration
- Portal Integration
- Integrate WDA in Portal
- Interactive Forms
- SAP List Viewer(ALV)
- Administration
- Monitoring an Application
- SAP Web Dynpro Useful Resources
- Web Dynpro - Questions Answers
- SAP Web Dynpro - Quick Guide
- SAP Web Dynpro - Useful Resources
- SAP Web Dynpro - Discussion
Personalization & Configuration
As per the business requirement, you can implement many standard applications and the UI of Web Dynpro application can vary as per the requirement.
Configuration of Application
To configure a Web Dynpro application, you first configure data records for individual Web Dynpro components.
Using the component configuration, it allows you to manage the behavior.
Next is to configure the application. All the components that are created require to be used in the specific configuration. The configuration of Web Dynpro application defines which component is configured in an application.
How to Start Component Configurator?
In ABAP object list, select a Web Dynpro component −
Right-click → Create/Change configuration.
This opens a browser with the dialog window of the configurator. The mode Component Configurator is active and you enter a name for your new component configuration.
You can also define implicit and explicit configuration. Save the configuration and close the window.
Note − You can save a new configuration only when it actually contains values. An empty configuration file that doesn’t contain any data and has a name is not stored.
As this configurator is not part of the ABAP Workbench and runs separately in the browser, you need to update the hierarchy of the object list in the workbench after completion of the creation or change procedure in a configuration.
This allows you to store different configurations for each object.
Delta Handling in Personalization
When you save the application configuration, you can’t check the changes made by an administrator and an end user. There is a need to store customization and personalization data that allows merged data to be managed.
The following points should be considered −
Application users and administrators should be able to reverse the changes.
Customization changes of an application should be visible to the user for all the pages.
Application administrator should have access to mark the report as final and this should be valid for all users. When an administrator flags a property final, any changes to the value as a personalization of a single user must no longer be permitted.