In a complete UI configuration for single object processing, several components work together and need to be configured accordingly as shown in the figure MDG UI Configuration for Single-Object Processing below.

One of these components is the generic MDG Web Dynpro application USMD_OVP_GEN with its application configurations. Each application configuration is specific for an object type and this object type is defined with the parameter USMD_OTC.

This Web Dynpro application implements an adaptable overview page (OVP) component of the Floorplan Manager (FPM): FPM_ADAPTABLE_OVP. This OVP component is a wrapper that contains an FPM overview page component (FPM_OVP_COMPONENT). The configuration of the adaptable OVP references the adaptation scheme for creating context based adaptations (CBA) of the included OVP component and of its sub-components.

For more information, see Generic Context-Based Adaptation Scheme.

The configuration of the OVP contains at least one page. At least one section of the page contains user interface building blocks (UIBBs). Most UIBBs enable the processing of business object data on the UI. The UIBBs are configured for all entity types that belong to the business object. Usually, there’s more than one entity type.

The MDG framework provides the following UIBBs:

These UIBBs are no explicit parts of the configuration of the Web Dynpro application, but are added at runtime by the MDG communicator, which has overall responsibility for the change request process. The MDG communicator controls the availability of change request actions, which are represented as buttons in the global toolbar. The settings that the MDG communicator uses are stored in its component configuration.

If you want to have an object-specific search, the OVP can include an initial screen with an FPM search UIBB to enter search criteria and a list UIBB to display search results.

MDG Data Model

The UI configuration is based on the active version of an MDG data model. At design-time, when you create the configuration of a UI or customize a UI, the relevant data model is determined by the standard data model from your user profile. You set the standard data model in the following way:

At run-time, when the UI is used to process data, the MDG data model is determined by the business object type code given in the parameter USMD_OTC of the configuration of the Web Dynpro application USMD_OVP_GEN.

genIL Component

When you activate an MDG data model that is in the customer namespace, the system creates two genIL components as local objects. The names of the components are as follows:

You can check the successful creation of the genIL components by calling transaction GENIL_MODEL_BROWSER.

Business Object Type Code

Every configuration of the Web Dynpro application USMD_OVP_GEN contains the parameter USMD_OTC that must be set to the business object type code (OTC) of the object that the UI should be used for. The OTC is defined in Customizing for Master Data Governance under  General Settings Data Replication Enhance Default Settings for Outbound Implementations Define Business Objects and Object Identifiers Define Business Objects . At least the columns BO Type, which contains the OTC, and Description need to be filled. You need to assign the OTC to the data model and the entity type in the view Business Object Type in the Customizing activity Edit Data Model under  General Settings Data Modeling . You also need to set the indicator Root in the same view. Additionally, you need to assign the data model and the entity type to the OTC in the Customizing activity Define Entity Type to Be Used by Business Object Type under  General Settings Data Modeling .

Data Model-Specific Structures

The UI components of MDG require several DDIC structures that are specific to the data model used for the UI configuration. Initially and also after every change to the data model, these structures need to be generated. Use the Customizing activity Generate Data Model-Specific Structures under  General Settings Data Modeling for all entity types that you use in the UI configuration to generate the required structures for the following entries of the column Where Used:

Mandatory Naming Convention for the MDG Communicator

The application configuration ID must be the same as the configuration ID for the MDG communicator settings. Otherwise, the application cannot determine which settings to use and the integration with the MDG framework will not work.

Possible symptoms of a mismatch between configuration IDs at runtime are as follows:

Recommended Naming Conventions for Other Configurations

Highlight Changes

You can set the colors and the activation of the highlight changes function in the configuration of the used MDG Web Dynpro application, for example USMD_OVP_GEN, using the parameters MDG_HC_DISABLE, MDG_HC_COLOR_SAVED, and MDG_HC_COLOR_UNSAVED. For more information, see Highlight Changes.