SAP MDG Technical Concept:-

You use change request in SAP Master Data Governance to trigger and process changes to master data.
You use change requests in your daily work to make changes to your data. The system applies the
governance rules and processes you have defined. The change request process starts with a user's first
entry for the purpose of creating or changing data.

[Type the company name] 1

[Type the company name] 2
Exact use of change request-

[Type the company name] 3

 Extending SAP Master Data Governance for Supplier:-

From my experience, many companies want to manage custom objects in a central master data system
to be able to harmonize this information across their landscape. Custom objects can be individually
defined objects such as assets or locations. Custom objects are typically less complex master data
objects with a small and simple data model. They are often used as reference data in major objects such
as material, suppliers and customers.
The How-To Guide describes the necessary steps to implement a custom object in SAP MDG. The guide
is based on an object called “Location” and includes the following steps during the implementation phase:
 Create a new Data Model
 Define a new Business Object and Activity
 Create a custom User Interface
 Process Modeling
 Test of the custom object
The target audiences of the document are typically technology consultants and MDM/MDG architects.
Please access the guide here:

[Type the company name] 4

Below requirement I got in LINDE AG MDG Assignment:
1st Part

Overview-

In SAP Master Data Governance data can be stored in a staging- or active area. The location used for the
temporary storage of the working version of master data that is undergoing change within a change
request process is called staging area. The location used for the permanent storage of the active
instances of master data after changes have been approved by a change request process is called active
area.
Extending the data model in SAP Master Data Governance with custom attributes or tables involves
changes to the data structures in both the active and staging areas and defining a mapping between
these data structures.
Extending active area data model
Extending BUT000
The extension of standard entity types is a common and straight forward task. Let’s say you want to
extend SAP Master Data Governance for Supplier by a custom field called ZSDN_CI. You start by
extending the append structures for supplier (BUT000). You add the field to structures CI_EEW_BUT000
and CI_EEW_BUT000_X. 

Figure 1: Extending structure INCL_EEW_BUT000 

[Type the company name] 5

Figure 2: Extending structure INCL_EEW_BUT000_X 

Extending LFA1
Next you extend the append structures for vendor (LFA1). You add the field to structures
VMDS_EI_VMD_CENTRAL_DATA and VMDS_EI_VMD_CENTRAL_DATA_XFLAG . 

Figure 3: Extending structure VMDS_EI_VMD_CENTRAL_DATA 

[Type the company name] 6

Figure 4: Extending structure VMDS_EI_VMD_CENTRAL_DATA_XFLAG 

Extending staging area data model

Extending MDG BP data model
Finally you extend the data model in SAP Master Data Governance. Using the IMG activity Edit Data
Model as an entry point you add our field ZSDN_CI to the Entity Type BP_CENTRAL of data model BP. 

Figure 5: List of Entity Types for data model BP 

[Type the company name] 7

 Figure 6: List of attributes for Entity Type BP_CENTRL 

>Generating MDG tables

Since the MDG data model was changed you need to regenerate the tables. In this customizing activity,
for each data model and entity type you generate technical structures and tables in the ABAP Dictionary.
The system uses these structures internally for implementing the staging area. To generate these Data
Model-specific structures follow the steps below:
ACTIVITY
 In Customizing for Master Data Governance, choose General Settings -> Data Modeling -> Generate
Data Model-specific structure
 Select the row with Data Model BP
 Double-click Structures in the left hand panel
 Click Generate Structures
Note
In general if you change a data model (for example, if you change attributes of entity types or
relationships), you need to regenerate the structures.

To verify that your custom fields have been added to the MDG-generated tables follow the steps below
ACTIVITY
 Start the ABAP Editor with transaction SE38
 In the Program input field enter USMD_DATA_MODEL
 Execute the program
 In the Data Model input field enter BP
 Click on Execute

[Type the company name] 8

 In the column Included Entity Type double-click on BP_CENTRL
 On the Fields tab in the Field column verify that your custom field is listed here

2nd Part
UI Configuration

The UI is configured with the Floorplan Manager. The Floorplan Manager (FPM) is a Web Dynpro ABAP
application that provides a framework for developing new Web Dynpro ABAP application interfaces
consistent with SAP UI guidelines.
An FPM application is composed of a number of different Web Dynpro components (most of which are
instantiated dynamically at runtime). However, the following two components are always present:
 A floorplan-specific component (FPM_GAF_COMPONENT or FPM_OIF_COMPONENT)
 A component for the Header Area (FPM_IDR_COMPONENT)
In simple terms, the configuration of an FPM application is the configuration of these two components. 

Floorplan Manager Configuration: -

It is recommended to make your changes only in the Floorplan Manager customizing layer of the SAP
delivered UI-configuration. In this section you will find step-by-step instructions on how to do this.
In addition to the approach outlined below there are at least two other possibilities for making UI changes.
You can either copy a SAP delivered UI-configuration and change the copied configuration or make your
changes directly in the configuration layer of a SAP delivered UI-configuration. Both of these approaches
are not recommended due to the following disadvantages:
If you make changes directly in the configuration layer of a SAP delivered UI-configuration these changes
will always be overwritten if a new version from SAP is imported. Changes within this layer are treated as
modifications. Therefore you should not make changes in the configuration layer of the SAP delivered UI-
configuration.
If you copy a SAP delivered UI-configuration and change the copied configuration you will also have to
copy the UI BAdI. The disadvantage of copying the UI BAdI is, that adjustments made by SAP do not run
automatically into your coding. 

Recommendation
Working with this example you should make your changes only in the customizing layer of a SAP
delivered UI-configuration. 

By making your changes in the customizing layer they will be client-dependent and the SAP delivered
original will be unchanged. The customizing data will only contain the differences to the original
configuration, so you are not disconnected from corrections or new features delivered by SAP in future
Service Packs or releases. At runtime the changes of the customizing layer are added to the original
configuration and the application will look like you customized it. 

Activating administrator mode

You can launch the configuration editor in customizing mode by running the application in administrator
mode. This can be achieved by simply adding URL parameter sap-config-mode=X or by launching the
[Type the company name] 9
 application from SE80 by navigating to the application (configuration) you want to start and then Shift+F8
(or via menu 'Web Dynpro Configuration' -> 'Test' -> 'Execute in Administration Mode'.
After starting the application in administrator mode you will see a link in the upper right corner of your
application (Adapt Configuration), which will lead you to the configuration editor in customizing mode. The
configuration editor in customizing mode will look identical as in the configuration mode, only your
changes will not be stored within the original configuration file, but instead in the customer adaptation file.

 
Figure 1: Execute in Administration Mode 

Figure 2: Adapt Configuration Link 

Note
To call up administrator mode, you need the S_DEVELOP or S_WDR_P13N authorization profile. 

If you do not see the Adapt Configuration link in the top right hand corner of the window after following the
steps above you can also try to activate the administrator mode using the steps below. 

ACTIVITY
Alternative method to activate administrator mode
 On the SAP Easy Access screen, choose System -> User Profile -> Own Data
 On the Maintain User Profile screen, select the Parameters tab.
 Enter FPM_CONFIG_EXPERT for the parameter ID and A for the parameter value.
 Choose Save 

Adding custom fields

After starting the Floorplan Manager Editor via the Adapt Configuration link you can start adding
additional fields to the UI. 
[Type the company name] 10
 ACTIVITY
For example to add the field ZLARS01 to the Organisational Data tab in the Address subview follow the
steps below.
 In the main window make sure Organizational Data and Address items are selected (default)
 In the Address subview locate the top UI Building Block (Configuration Name:
MDG_BS_BP_FORM_UIBB_ADMIN)
 In this UI Building Block click on Configure UUIB

Figure 3: Navigate to UIBB configuration 

 You are now in the Component Configuration for MDG_BS_BP_FORM_UIBB_ADMIN

 Click the Add Group button
 Locate the Group Attributes section
 In the input field Text enter Extensibility as the group name and press return
 You have created a group Extensibility
 Press the Add Melting Group button
 To add fields to the Melting Group press the Configure Melting Group button
 In the new window move the fields you want to add from the Available Fields table to the Displayed Fields
table
 When you have finished adding fields click the OK button

[Type the company name] 11

  
Figure 4: Configure Group Dialog 

 You then assign the FPM event ID USMD_ENTER to the new field. Specifying this means that the system
triggers a roundtrip when a value is selected from the dropdown list box, allowing dependent UIBB fields
to be changed by means of a Business Add-In (USMD_UI_EVENT2).
 Click the Save button to save the configuration changes

Figure 5: UI Field Extension 

[Type the company name] 12

 (Optional) UI BAdI Implementation
You can override the standard processing of the UI configuration by means of the Business Add-In:
Adjust User Interface for Single Processing (USMD_UI_EVENT2). This BAdI allows for extensive UI
adjustments. You have options for making changes in the following areas: 

 Adjust the definition of attributes or add new attributes

 Initialize the displayed data (when creating a new entity type, for example)
 Restrict the values displayed in a dropdown list field or selection field group
 Restrict the values displayed in the input help
 Dynamically control the visibility of fields on the user interface and of the property that determines if fields
are required or display-only
 Define navigation destinations of UI elements of the type hyperlink (or pushbutton)
 Check if the lead selection of a table may be changed

 
Figure 6: BAdI Adjust User Interface for Single Processing 

If you want to use fields or set default values that do not exist in the data model but that are instead
calculated, derived, or defaulted on the UI, you must implement a User Interface BAdI (Business Add In).
Under UI Modeling -> Business Add-Ins -> BAdI: Adjust User Interface for Single Processing (BAdI
USMD_UI_EVENT2), create your own implementation.
 In your implementation, allow the methods that you want to adjust to be inherited from the implementing
class of a delivered standard implementation. If the implementing class does not allow inheritance
because it is marked as FINAL, you need to create a copy of the class.
 Deactivate the existing BAdI implementation and activate your new BAdI implementation

Copying a UI BAdI
If you have copied a SAP delivered UI-configuration in a previous step you have to copy the
corresponding UI BAdI as well and change the filter value to the new UI configuration ID. 

Note
Note that the copy does not automatically contain corrections from Support Packages or SAP Notes.

[Type the company name] 13

 Therefore ensure you check the relevant SAP Notes for the implementing class and manually implement
any corrections. 

ACTIVITY
In this activity you
 Copy enhancement implementation MDG_UI_EVENT_SUPPLIER to Z_LR_
MDG_UI_EVENT_SUPPLIER 

 Copy implementation class CL_MDG_BS_UI_EVENT_SUPPLIER to Z_LR_

CL_MDG_BS_UI_EVENT_SUPPLI

[Type the company name] 14

 In your enhancement implementation Z_LR_MDG_UI_EVENT_SUPPLIER change the implementing
class from CL_MDG_BS_UI_EVENT_SUPPLIER to Z_LR_CL_MDG_BS_UI_EVENT_SUPPLI

 In your enhancement implementation Z_LR_MDG_UI_EVENT_SUPPLIER change the filter value to the

previously copied UI configuration (for example MDG_BP_SUPPLIER_APPL_RT_1) and delete any
obsolete filter entries.

 Activate your changes

In order to test if your custom UI configuration works together with your copy of the UI BAdI you have to
create a new Change Request Type in customizing (activity Create Change Request Type) and set the UI
configuration parameter to your previously copied UI configuration (for example
MDG_BP_SUPPLIER_APPL_RT_1).

[Type the company name] 15

  

Launching the Create Supplier UI will now allow you to select your custom change request type. This in
turn will invoke your custom UI Configuration and customized UI and BAdI.

Testing data model changes

To verify your changes are working create a change request for a new business partner and note the
number of the change request from the table My Change Requests. When creating the business partner
make sure you enter a value for our custom field ZSDN_CI. To activate the change request you can go
through the approval workflow. As an alternative you can start the Business Object Builder transaction
SWO1. Enter BUS2250 in the Object Type input field and press the_Test_ button. In the pop-up window
enter your change request number. In the following screen execute the method ACTIVATE_2 to activate
the business partner.
After the activation you should check tables LFA1 and BUT000 if the value of your custom field was
correctly transferred to the active area.

[Type the company name] 16