© 2012 by SAP AG. All rights reserved.

SAP and the SAP logo are registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo are trademarks or
registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and the Sybase logo are registered trademarks of Sybase Inc.
Sybase is an SAP company. Crossgate is a registered trademark of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

FLEXIBLE GOVERNANCE –
GOVERN YOUR OWN OBJECTS IN
SAP MASTER DATA GOVERNANCE
EIM264

Exercises / Solutions – Version for Virtual TechEd

Andreas Seifried / SAP AG
INTRODUCTION

With its domain-specific out-of-the-box applications, SAP Master Data Governance provides instant support for central
maintenance scenarios of supplier, customer, material, and financial master data. Additionally, the application
foundation of SAP Master Data Governance can be used for other data domains and to support customer-specific data
management scenarios. Thus, this application can be the common platform within your organization to provide
governance around all of your master data. In this session, you will be introduced to the concepts of SAP Master Data
Governance's application foundation and learn how to configure a basic scenario by defining your own data model,
user interface configuration and change request process to manage a custom object.

Session Outline
This session is split into 5 exercises that must be completed in sequence as they build upon each other. After each
exercise you will find a step-by-step solution.
Goal: Perform a basic configuration of a custom governance scenario from scratch and with the least amount of
configuration to be able to successfully create and process a change request.
Exercise 1 – Create the data model
Exercise 2 – Create the UI configuration
Exercise 3 – Create the process configuration
Exercise 4 – Create the user menu
Exercise 5 – Use the newly created scenario

As part of the exercise solution in this document, just before the detailed step-by-step solution, there is a section
Naming and Configuration Choices which lists the settings that are required to apply the step-by-step solution of
subsequent exercises without any adaptation.

Naming of objects
All objects of this exercise are named with a prefix ID for uniqueness. Please substitute the placeholder ## with the ID
that matches to your group number according to the table “Assignment of Group Numbers – User IDs – Prefix IDs”.
nn = Group number from 01 – 60
## = prefix ID from X1 to XU, Y1 to YU
Note:
For the configuration IDs in exercise “Create UI Configuration” there is an additional Z as the prefix required, as X
and Y are no valid customer namespaces for FPM configurations.

Naming Convention
It is good practice to use the ID of the data model as a prefix for all configuration settings that you create. This exercise
uses the naming convention below.

Configuration Setting Example of ID / Name Remark

Data Models X0 max 2 characters
FPM UI Applications ZX0_USMD_ENTITY_VALUE2 Initial Z required to satisfy
namespace requirements
FPM UI Components ZX0_FORM_CARMANUF Initial Z required to satisfy
namespace requirements
Suggested pattern:
Z<data model>_<type>_<entity type>
Configuration Setting Example of ID / Name Remark
Business Activities X0C1 max 4 characters
Suggested pattern:
<data model><letter for entity
type><number>

Number: to distinguish different type e.g.

create and change, if required.

Change Request Types X0C1A max 8 characters

Suggested pattern:
<business activity><letter>

Letter: to distinguish different type e.g.

create with different processors.

Remove forgotten left-overs

In case you find left-overs with your prefix of somebody else who previously performed the exercise, please refer to

Reset of environment – tidy-up for the next One for instructions how to clean up.
Assignment of Group Numbers – User IDs – Prefix IDs

Group Number User ID Prefix ID Group Number User ID Prefix ID

Group 01 EIM264-01 X1 Group 31 EIM264-31 Y1
Group 02 EIM264-02 X2 Group 32 EIM264-32 Y2
Group 03 EIM264-03 X3 Group 33 EIM264-33 Y3
Group 04 EIM264-04 X4 Group 34 EIM264-34 Y4
Group 05 EIM264-05 X5 Group 35 EIM264-35 Y5
Group 06 EIM264-06 X6 Group 36 EIM264-36 Y6
Group 07 EIM264-07 X7 Group 37 EIM264-37 Y7
Group 08 EIM264-08 X8 Group 38 EIM264-38 Y8
Group 09 EIM264-09 X9 Group 39 EIM264-39 Y9
Group 10 EIM264-10 XA Group 40 EIM264-40 YA
Group 11 EIM264-11 XB Group 41 EIM264-41 YB
Group 12 EIM264-12 XC Group 42 EIM264-42 YC
Group 13 EIM264-13 XD Group 43 EIM264-43 YD
Group 14 EIM264-14 XE Group 44 EIM264-44 YE
Group 15 EIM264-15 XF Group 45 EIM264-45 YF
Group 16 EIM264-16 XG Group 46 EIM264-46 YG
Group 17 EIM264-17 XH Group 47 EIM264-47 YH
Group 18 EIM264-18 XI Group 48 EIM264-48 YI
Group 19 EIM264-19 XJ Group 49 EIM264-49 YJ
Group 20 EIM264-20 XK Group 50 EIM264-50 YK
Group 21 EIM264-21 XL Group 51 EIM264-51 YL
Group 22 EIM264-22 XM Group 52 EIM264-52 YM
Group 23 EIM264-23 XN Group 53 EIM264-53 YN
Group 24 EIM264-24 XO Group 54 EIM264-54 YO
Group 25 EIM264-25 XP Group 55 EIM264-55 YP
Group 26 EIM264-26 XQ Group 56 EIM264-56 YQ
Group 27 EIM264-27 XR Group 57 EIM264-57 YR
Group 28 EIM264-28 XS Group 58 EIM264-58 YS
Group 29 EIM264-29 XT Group 59 EIM264-59 YT
Group 30 EIM264-30 XU Group 60 EIM264-60 YU
Logon information
Replace nn with your two-digit group number
• Logon to the SAP System M10 Client 800
• Username: EIM264-nn
• Password: welcome

Logon with SAP NetWeaver Business Client 3.5

Please logon to the system using SAP NetWeaver Business Client – Desktop (NWBC) in version 3.5 from the start
menu or using the shortcut on the desktop:

 

Do not use NWBC 4.0

NWBC 4.0 uses a new design and layout, so that you will not be able to follow the description of the exercise and
particularly the solution which is based on screenshots.
 EXERCISE 1 – CREATE THE DATA MODEL

The objective is to create a data model to store information about car manufacturers. The requirements are simple and
for each manufacturer only this information should be stored:
 Manufacturer ID
 Manufacturer Name
 Manufacturer Description (only one language is sufficient)
It is not required to have special features such as Editions or Hierarchies.
Later on, it should be possible to create a change request to maintain one manufacturer.
Please make use of the pre-defined data elements:
 ZCARMANUFID – Car Manufacturer ID and
 ZCARMANUF – Car Manufacturer Name.
Please use the data model with the ID that matches the prefix ID of your group number! (see table Assignment of
Group Numbers – User IDs – Prefix IDs on page 4)

Please use the following questions to structure your way through the exercise:

 What is the ID of your data model?

 How many entity types do you need?

Considering that
- the key of an entity can be determined by the data element property of the entity type and
- entity types can be configured to provide description texts,
how many attributes are needed?
 Solution Exercise 1
To satisfy the requirements it is sufficient to add just one entity type to the data model. As the data should be entered
using MDG and a change request should be used for that, it must be of storage and usage type 1. As stated in the
requirements, the data element ZCARMANUFID should be used for the entity type in order to determine the keys of the
entities. To store the description the text feature can be used. Only one attribute is needed and this is to store the
manufacturer’s name. The data element ZCARMANUF is used for the name attribute.

Naming and Configuration Choices

Use these settings in case you want to apply the step-by-step solutions of subsequent exercises:
Entity Type for car manufacturer: CARMANUF
Description is stored in Long Text (60 is used as the value of property Long Text – Length)
Attribute for car manufacturer’s name: NAME
 Step-by-step Solution

Launch MDG Configuration

Workbench

Choose “Configuration Workbench”

from the NWBC menu, like shown on
the screenshots.

Alternatively you can launch it from the

IMG or with transaction MDGDT.

Alternatives

Alternative 1: From IMG Alternative 2: Transaction MDGDT

Open data model

Select your data model, matching the

prefix ID of your group number.

<YOUR ID> <Your group name>

Switch to edit mode <YOUR ID>, <Your group name>

<YOUR ID>

Add a new entity type

Choose New in the Entity Types block.

Entity Type Properties (Part I)

Define the General Data properties of

the entity type.

Entity Type: CARMANUF

Description: Car Manufacturer
SU Type: 1
Data Element: ZCARMANUFID

Leave all other properties at their

default values.

Entity Type Properties (Part II)

Enter a value, e.g. 60 for the length of

the long text.

Leave all other properties at their

default values.
Create a new attribute

Switch to the Attributes tab and choose

New.

Define properties of attribute

Enter the properties of the new attribute:

Attribute (name): NAME

Description: Car Manufacturer Name
Data Element: ZCARMANUF

Leave all other properties at their

default values.

Save the data model

Create / Choose Workbench Request

Create a workbench request to save the

changes.
Activate the changed data model

Check Status

Check the activation status by selecting

View Log.
Verify successful activation

Since this is the first activation of the

model you can ignore a warning
concerning change request adjustment.

Check the log for a success message

“Data Model Activated”.

Exercise 1 Completed!
You have created a new data model and activated it, so that it is ready for storing data and for the next configuration
steps.
Further Info for Technical Experts
Data Model Overview
You can use SE38 to start report USMD_DISPLAY_DATA_MODEL and to get an overview of your data model:

Generated Tables
Based on your definition of the data model, the system has created tables to store the data during staging and after
activation of the change request. You can have a look at these tables by using transaction MDG_DATA_MODEL:
 EXERCISE 2 – CREATE THE UI CONFIGURATION

In order to maintain the data of the car manufacturers, a simple user interface is required that displays the attributes in
the style of a form.
Objective of this exercise is to create a new configuration for the generic UI USMD_ENTITY_VALUE2 of MDG using
Floor Plan Manager (FPM).

Basically you need to perform these steps:

1. Start FPM tools – Start the “Manage UI Configuration” screen of MDG from the IMG. There you can create a
new configuration, which will bring you to the FPM tools.
2. Copy template – To create a new configuration, you actually copy 3 template configurations for the generic
MDG Web Dynpro application USMD_ENTITY_VALUE2.
3. Link UI configuration to data model – The UI configurations are based on the actual data model for which
they should be used. Therefore you need to link the two together.
4. Create new form – The attributes of the car manufacturer entity are displayed using a new configuration of a
form UI building block (FPM_FORM_UIBB).
5. Create Layout – Using the FPM Configurator you define which attributes shall be displayed, their position on
the UI and further properties.
 Solution Exercise 2
See below for the step-by-step solution in detail.

Naming and Configuration Choices

Use these settings in case you want to apply the step-by-step solutions of subsequent exercises:
Application Configuration ID for USMD_ENTITY_VALUE2: Z<your_prefix_id>_USMD_ENTITY_VALUE2

Step-by-step Solution

Manage UI Configurations
Launch the MDG screen “Manage UI
Configurations” from the NWBC menu,
like shown on the screenshots.

Alternatively you can launch it from the

IMG.

Alternative: From IMG

Create New Configuration
Select Create to launch the FPM
configurator in deep-copy mode and
with its settings prepared to create a
new configuration for
USMD_ENTITY_VALUE2 based on the
delivered template.

Adapt Configuration IDs

The FPM configurator automatically
suggests Target Configuration IDs for
the copies to be created.
Choose Change Affixes to modify the
suggested values.

Change Affixes
According to the naming convention,
change the value for the prefix to Z## Z<YOUR ID>
(## = prefix for your group).
Remove the value for the suffix.
Start Deep-Copy
Verify the new values for the target
configuration IDs. In order to make them
unique, the ID of your data model Verify that you use YOUR prefix!
should be part of it.
Then choose Start Deep-Copy.

Select Package
Select Local Object.

Verify Result
Check the message whether the copies
were created successfully.
Navigate to New Application
Configuration
Choose the configuration ID of the new
application configuration that you
copied.
(in Target Configuration ID select first
line)
Switch to Edit Mode
When the FPM Configurator comes up
with your application configuration,
choose Edit.

Configure Model
In order to link your application
configuration with your data model,
enter the ID of your data model for the
parameter USMD_MODEL.
Make sure to use the ID of your group!

Save Changes
Choose Save.

Verify that you use YOUR prefix!

Navigate to OIF Configuration

Choose the configuration name of the
copy you created for the
FPM_OIF_COMPONENT.
Create Variant for Entity Type
As soon as the FPM configurator comes
up with your copy of the configuration,
choose New  Variant.

Enter Entity Type as ID of Variant

Use the value help of the field ID in
order to set its value to the entity type
for which you want to create the
configuration.
If there is no value suggested or a
different name that you expected, there
is something wrong with the assignment
of your application configuration to your
data model.
Enter ID for Main View
The new variant is created with values
that need to be corrected.
Enter a new value for the Main View ID:
MAIN_VIEW_1 and press Return.
Add a Form
By default one subview was added to
the main view. (As there is only one
subview, actually no subview will be
sown at runtime.)
Furthermore a yet unspecified UI
building block (UIBB) was added to the
subview.
Complete the configuration of the UIBB
by entering these values:
Component:
FPM_FORM_UIBB
Configuration Name:
Z<YOUR ID>_FORM_CARMANUF
Window Name:
FORM_WINDOW Verify that you use YOUR prefix!

Do not use FPM_FORM_UIBB_GL2 or

select “Form Component” from the “Add
UIBB” pushbutton, as this is not
supported by MDG.

Remove Dummy Variant

Finally select the variant
USMD_DUMMY (click line “Variant”)
and choose Delete to remove it from the
configuration.
Confirm Warning

Save OIF Configuration

An error message will inform you that
the configuration name that you entered
for the UIBB does not yet exist, the
configuration is not yet useable at
runtime.
To proceed save the configuration.
Start UIBB Configuration
Select the FPM_FORM_UIBB (with the
yet not created configuration), then
choose Configure UIBB.

Create New UIBB Configuration

The FPM editor informs you that the
given configuration does not yet exist.
Choose New to create it.

Enter Description
Enter a description of the new form
UIBB configuration.
Select Package
Choose Local Object.

Confirm Feed Class

The feeder class
CL_USMD_ENTITY_VALUE2_PROXY
for the UIBB is automatically added.
Leave the value of Contained Entity
Type empty.
Choose OK.

Configure Form UIBB Schema

Select the respective tab for the form
UIBB schema.
Add New Group
Choose Element  Add Group to add a
new element for grouping the fields to
be placed on the screen.

Add Elements to Group

While having the newly created group
selected, choose Child Element  Add
Elements to Group.
Select Fields to be Displayed
The system presents a list with all
available attributes of the entity type.
Select NAME and TXTLG, and then
choose OK.

OPTION: Adapt Layout and Labels

Optionally, change the labels and
further attributes of the fields.

Save Configuration
Chose Save and verify that the system
does not detect any errors in your
configuration.

Close all FPM Editor windows.

 Exercise 2 Completed!
You have created a UI configuration from scratch, which means in detail:
- Create a copy of the template configuration for the generic MDG UI USMD_ENTITY_VALUE2, including copies
of the configurations for the contained components FPM_OIF_COMPONENT and FPM_IDR_COMPONENT.
- Link the application configuration to your data model.
- Add a variant to the configuration of FPM_OIF_COMPONENT with a form UIBB to display the data of the car
manufacturer entity as a form.

The new UI configuration is useable, if it is supplied with the correct parameters, which you will prepare in the next
exercise.
 EXERCISE 3 – CREATE THE PROCESS CONFIGURATION

After you have completed the setup of the data model and the user interface, it is now about to configure how the
change request process should look like.
The process shall be started from the menu of NWBC. It is sufficient to have one process for both creating and
changing car manufacturers.
The change process shall have an initial request step, then a data processing step and a final approval. (Hint: Use the
example 3 step workflow WS54300020 “MDG_FS_3STEP”.)
For demonstration purposes it is sufficient to configure your own user as a processor for the processing and the
approval steps.
 Solution Exercise 3
## = Prefix of your group

Business Activity
As it should be possible to start the change process NWBC a business activity is required. Following the naming
convention, create a business activity ##C1 for your data model. It is not required to enter anything for the business
object type and the logical action.
Change Request Type
Then create a change request type ##C1A for your data model, flag it as “single object”, the main entity shall be
CARMANUF and the workflow template to be used is WS54300020.
Assign Processors to Change Request Steps
As a next step create an entry for the processor of step 1 “Processing” and another entry for step 2 “Final Check”,
assign your user to each step.

Naming and Configuration Choices

Use these settings in case you want to apply the step-by-step solutions of subsequent exercises:
Business Activity: <your_prefix_id>C1

Step-by-step Solution

Start IMG of MDG

Create Business Activities
Start the activity Master Data
Governance  General Settings 
Process Modeling  Business Activities
 Create Business Activities.

Confirm Warning

Select New Entries

Enter Properties of New Activity

Enter a name for your business activity
following the naming convention ##xy
(## = your ID).
Enter a description and the ID of your
data model.
Leave the values for BO Type and
Logical Action empty.
Save the new entry and accept warning
about the namespace.
Workbench Request
When prompted for a workbench
request select the request that you
created when setting up the data model.

Create Change Request Type

Start the activity Master Data
Governance  General Settings 
Process Modeling  Change Requests
 Create Change Request Type.

Choose New Entries.

Enter Properties of New Change
Request Type (CR Type)
Enter a value for the CR Type according
to the naming convention and with your
ID.
Enter the ID of your data model and a
description.
Mark the check box Single Object.
Enter your entity type and the workflow
template WS54300020.
Leave all other values to their defaults.

Go to Entity Types Dialog

Press ENTER, select the complete new
row and double click on Entity Types in
the dialog structure.

Choose New Entries.

Enter Your Entity Type

Enter your entity tape as you have
named it in your data model.

Assign UI Configuration Name

Press ENTER and then use the value
help to select the UI configuration that
you have created previously.
Verify that the name of your UI
configuration is suggested. If this is not
the case, there is a configuration error.

Go to Business Activities Dialog

Double click on Business Activities in
the dialog structure.
Choose New Entries.

Assign Business Activity

Enter the name of your business activity
to assign it to this change request type.

Save the CR Type

Save your newly created change
request type. The system will warn you
that you have not yet assigned
processors to the steps of the change
request type.

Assign Processors
Start IMG activity Master Data
Governance  General Settings 
Process Modeling  Workflow  Other
MDG Workflows  Assign Processor to
Change Request Step (Simple
Workflow).
Choose New Entries.

Enter processors
Enter your change request type, step 1
“Processing”, the value US for the agent
type and your user ID for the agent.
After that create another entry for Step
2 “Final Check”.

Save the Settings

Exercise 3 Completed!
You have made the basic settings to define how the change request process should look like and are now ready for the
final step to provide make it available to your users.
 EXERCISE 4 – CREATE THE USER MENU

End users will access MDG from SAP Portal or NetWeaver Business Client (NWBC). To make this possible a role with
an appropriate menu needs to be provided. The provided default role for MDG for Custom Objects shall be used an
extended to be able to start processing of car manufacturers.
The menu shall be based on the role SAP_MDGX_MENU.
A menu entry for search shall be available using the Web Dynpro application USMD_ENTITY_SEARCH.
A menu entry for creating change requests to process car manufacturers shall be available using Web Dynpro
application USMD_ENTITY_VALUE2.

Solution Exercise 4
1. Copy template role SAP_MDGX_MENU with PFCG to a new ID ##_SAP_MDGX_MENU.
2. Create folder for the new entries (e.g. Car Manufacturers)
3. Add search capability by adding Web Dynpro application USMD_ENTITY_SEARCH. Set the parameter
PROCESS to the business activity of your group.
4. Add the create and maintain capability by adding Web Dynpro application USMD_ENTITY_VALUE2. Set the
parameter PROCESS to the business activity of your group and flag IS_CREQ_MODE to X to have an
integrated UI of change request and object.
5. Assign the role to your user.
Naming and Configuration Choices
Use these settings in case you want to apply the step-by-step solutions of subsequent exercises:
--- Not required ---
 Step-by-step Solution

Start transaction PFCG.

Type in the name of the template role

SAP_MDGX_MENU.

Select Copy and enter the new role id:

##_SAP_MDGX_MENU
(Replace ## with your group id)

Change the copied role.

Select the Menu tab.

Select the folder Master Data

Governance for Custom Objects, then
select Create Folder.

Enter a name for the new folder e.g. Car

Manufacturers.
The new folder is created below Master
Data Governance for Custom Objects.
Be sure that the newly created folder is
selected, then select Add Transaction
 Web Dynpro Application.

Enter USMD_ENTITY_SEARCH as the

name of the application and Search Car
Manufacturer as the descriptionn of the
menu entry.
Enter parameter PROCESS with the
value of the business activity of your
group: ##C1

Verify that you use YOUR prefix / business activity!

The new menu entry is created below

the new folder.
Again, select Add Web Dynpro
Application.
Enter USMD_ENTITY_VALUE2 as the
name of the application and Process
Car Manufacturer as the description.
Enter parameter PROCESS with the
value of the business activity of your
group: ##C1
Enter parameter IS_CREQ_MODE with
value X.

Verify that you use YOUR prefix / business activity!

The new menu entry is created below

the new folder.
Select the tab User.
Enter your user ID in the table.
EIM264-nn

Save the changes.

EIM264-nn

Disconnect and Logon Again

Close NWBC and logon again. You
should see the menu Master Data
Governance for Custom Objects from
the additional role and the Car
Manufacturers folder that you added.

With having extended the template menu, you are now ready to use the functionality of MDG in the context of this
exercise scenario.
 EXERCISE 5 – USE THE NEWLY CREATED SCENARIO

Use the functions of MDG provided through the previously created menu to make you familiar with searching for car
manufacturers, creating a change request for a new manufacturer, and processing this change request.
Note: As you added a new menu to your user, it is required to reload the menu in NWBC. For that, just log off and log
on again. Otherwise you will not see the new menu Master Data Governance for Custom Objects with the subfolder
Car Manufacturers.

Solution Exercise 5
A possible sequence to use your configuration of MDG for processing car manufacturers is:
1. Search for manufacturers – As each of the groups use dedicated data models with own tables, the result of the
search might be empty.
2. Use the Create button in the search result to create a change request for a new manufacturer.
3. Go to the Change Request inbox to process the change request (step 1).
4. Use the search to see how not yet approved data is presented by the system.
5. Again, open the change request from the inbox, examine the change documents to see what is subject to this
change request and to approve the change request (step 2).
6. Use the search to see the approved and active data.

Step-by-step Solution

Launch Search
Choose Master Data Governance for
Custom Objects  Car Manufacturers
 Search Car Manufacturer.
Start Search
Choose Search.

Start Create
If there is not data yet, the result will be
empty. Choose Create to create a
change request for a new car
manufacturer.

Enter ID
Enter an ID for the new car
manufacturer and choose Continue.
Enter Details and Submit
Enter a description of the change
request, as well as values for the two
fields: name and description. Then
choose Submit.

Close Window
The system informs you about the ID of
the new change request. Choose Close.

Search Shows Inactive Manufacturer

If you perform the search again, you will
see the car manufacturer and that it is
subject to a change request.

Open Change Request Workitem

Inbox
From the menu choose Master Data
Governance for Custom Objects  Car
Manufacturers  Change Requests to
open your inbox.
Open Change Request for
Processing
The inbox should display the work item
for processing of the previously created
change request. It shows the change
request in the status Changes to Be
Executed. Select the subject of the work
item to open the change request for
processing.

Finalize Processing
Optionally review the details of the
change request by selecting the
Change Request button. You could also
modify the data of the car manufacturer.
Choose Finalize Processing.

Close Window

Observe Status Change

If the inbox is still open, you can see the
change request in its old status
Changes to Be Executed with the
former work item. This is because the
status change as well as potentially
other processing occurs in the
background.
Choose Refresh.
Open Change Request
The processing work item should be
replaced by a new one for approving the
change request. The status of the
change request should have changed to
Final Check to Be Performed.
Select the new work item of the change
request to open it for approval.

Examine Changes
Before approving the change request
you can have a look at the related
change documents.
Choose Show  Change Documents.

Overview of Changes
The system presents a list that
summarizes all changes.
Choose Display  Attribute Changes to
have a more detailed view.

Attribute Changes
The system shows all changes in detail.
Close the window.

Approve the Change Request

Choose Approve to finally approve the
change request.
Close Window

Search Again
The search result now shows the car
manufacturer and that it is active.

My Change Requests vs
Change Request Inbox
From the menu choose Master Data
Governance for Custom Objects 
Change Requests  Reporting  My
Change Requests.
My Change Requests
The system provides you with a list of
change request that were created by
you. This list is available independent of
the processing status of the change
request. (Mind that there is now no work
item related to the change request in
the inbox any longer.)
My Change Requests is not meant to
show the “workflow perspective” with
the potentially multiple work items for a
change request. It serves as a status
overview and history of the user’s
requests.

Exercise 5 Completed!
You used the basic functions of MDG to process a car manufacturer in this simple example scenario. If there is still
time left, you can investigate further possibilities from the menu Master Data Governance for Custom Objects or from
the example scenario Governance for Flight Data Model… Enjoy!
 RESET OF ENVIRONMENT – TIDY-UP FOR THE NEXT ONE

It might be the case that somebody else wants to perform the exercise before the system is reset from backup.
Because of this we kindly ask you to undo all your changes by following this short procedure:

Remove role
Start transaction PFCG, enter the name
of your role ##_SAP_MDGX_MENU
and select Delete.
##

Delete change requests

Delete all change requests that you
created for your model.
Start transaction
MDG_DELETE_CREQUEST by
selecting MDG Configuration -> Delete
Change Requests.

Execute Deletion
Enter the ID ## of your model and
select Execute. Confirm the deletion.
##
Delete processors
Start IMG activity
Master Data Governance  General
Settings  Process Modeling 
Workflow  Other MDG Workflows 
Assign Processor to Change Request
Step (Simple Workflow)

Perform Deletion
Select the two entries for your change
request type ##C1A and select Delete.
Confirm the deletion and press Save. ##
##

Delete Change Request Type

Start IMG activity
Master Data Governance  General
Settings  Process Modeling 
Change Requests  Create Change
Request Type

Perform Deletion
Select your change request type ##C1A
and select Delete.
##
Confirm the deletion including the
dependent entries and press Save.
Delete Change Request Type
Start IMG activity
Master Data Governance  General
Settings  Process Modeling 
Business Activities  Create Business
Activities

Perform Deletion
Select your business activity ##C1 and
select Delete.
Confirm the deletion and press Save.
##

Delete UI Configuration
Launch transaction SE80
Display Local Objects
Select Repository Browser, in the dop-
down Local Objects and your user ID.
Then for all objects below Web Dynpro
choose Delete from the context menu
and confirm the deletion.

##

##

Delete Entity Type

Launch the Configuration Workbench.
Select your data model

##

Delete Entity Type

Switch to edit mode, select each entity
type, press delete, then save the
changes.