This document describes how to configure the generic MDG single-object processing user interface that is provided by the MDG Web Dynpro application USMD_OVP_GEN.
You have completed the following:
You can use an active MDG data model with at least one entity type with storage and use type 1. You have assigned a business object type code (OTC) to this entity type.
You have generated the required structures in the Customizing activity Generate Data Model-Specific Structures
under .
You have set the standard data model in your user profile.
The data model is in the customer namespace. If the data model is not in the customer namespace follow the description in Creating genIL Components and Transaction Handler Manually.
For more information, see Creating User Interfaces for Single Object Processing.
Note
Instead of using transaction SE80 for the processes described below, you can also use the Customizing activity Manage UI Configurations
under for the deep-copy of application configurations and the creation of MDG communicator settings. For more information, see Managing of UI Configurations.
Deep-Copy of Application Configuration
This section describes how to configure the MDG Web Dynpro application USMD_OVP_GEN creating a deep-copy of the template USMD_OVP_GEN_TEMPLATE.
Start transaction SE80 and display the Web Dynpro application configuration USMD_OVP_GEN_TEMPLATE from the package USMD_GENERIC_BOLUI.
Choose Display Configuration
. Then choose the application configuration name USMD_GEN_OVP_TEMPLATE of the component FPM_OVP_COMPONENT.
Choose
.Open Configurable Components
and enter the target configuration IDs for the application configuration, the context-based adaptation FPM_ADAPTABLE_OVP, and the overview page (OVP) floorplan FPM_OVP_COMPONENT. Then choose Start Deep-Copy
.
Recommendation
Replace <GEN>
in the configuration IDs with the combination of an MDG data model and the main entity type using meaningful names. For example, Z_USMD_OVP_SF_CARR for the application configuration and Z_USMD_SF_CARR_OVP for the OVP configuration.
Open the new application configuration and change the parameter USMD_OTC to the object type code of the business object that you want to process with this configuration as mentioned in step 1 of the Prerequisites section of this document.
Create MDG Communicator Settings
For the integration of the new application configuration with the MDG framework the system requires the configuration of the MDG communicator.
Note
In this configuration activity you will create MDG communicator settings from a template that contains dummy entries for the UIBB of the main entity and the page ID of the OVP. After you have added this UIBB to the OVP component, remember to replace these dummy entries with the actual IDs that you have chosen.
To create this configuration perform the following steps:
Start transaction SE80 and display the Web Dynpro component configuration MDG_BS_GOV_COMMUNICATOR_TEMPLATE from the package USMD_GENERIC_BOLUI.
Choose Start Configurator
.
Choose Copy Configuration
.
Enter the same configuration ID for the MDG communicator settings that you have chosen for the configuration ID of the MDG application USMD_OVP_GEN when you have created the deep-copy. For example, Z_USMD_OVP_SF_CARR.
Note
The two configuration IDs need to match exactly. Otherwise, the application is unable to determine the settings for the MDG communicator.
The settings of the MDG communicator must be completed in a later step, after you have configured the UIBB that displays the main entity on the OVP. Only then you know which values need to be entered here. To complete this step, open the copied configuration of the MDG communicator. In the table Configuration Context
, navigate to and enter the following values: :
Page Id
ID of the page in the OVP that contains the UIBB with the main entity
Source Component
The UIBB that contains the main entity
Source Config Name
The UIBB that contains the main entity
Note
If you make a mistake in the configuration of the MDG communicator, the integration with the MDG framework will not work.
Possible symptoms at runtime are:
There is no change request UIBB displayed after choosing Edit
in one of the UIBBs
No change request ID is generated
There are no change request action buttons displayed in the main toolbar