MDG Topic 1

5/19/2023
Master Data Governance

Generated on: 2023-05-19 14:25:57 GMT+0000
SAP S/4HANA | 2022 Latest
PUBLIC
Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549?locale=en-

US&state=PRODUCTION&version=2022.001
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
This is custom documentation. For more information, please visit the SAP Help Portal 1
5/19/2023
Import Data for Consolidation
Use
With this app you can upload records for consolidation into the source data tables using an Office Open XML or CSV le. This
creates a new data package with the uploaded records and you can use to create a consolidation process. Alternatively, launch
the app Create Consolidation Process from the SAP Fiori Launchpad. This allows you to create a consolidation process for
multiple data packages.
 Note
The app can handle both, CSV and Compressed CSV (.zip) format.
 Note
If cross references between uploaded records exist, make sure to use a process template that contains a key mapping step.
The key mapping step will resolve cross references. You can nd suitable process templates in the predelivered content.
Key Features
Straightforward user interface to enable updating of records for consolidation.
You can use data packages to divide your records up for organizational purposes.
In addition, the app supports the following technical features and options:
If the extended material number has been activated in your back-end system, it is automatically displayed in the Material eld in
this app. For more information, see Extended Material Number in SAP Fiori Apps.
 Note
You can use the Download File Templates feature to either download a set of Example Files or the Full Template.
You can also import data without a source system. To do so mark the Import without Source System checkbox.
 Note
Select this checkbox to indicate that the source system is irrelevant for the records to be imported. This applies when you
want to carry out a mass creation of new records or relationships without references in a source system. If the checkbox is
selected, the system will disregard key mapping and value mapping information of the imported records.
When importing data without a source system, you cannot use process templates that contain key value or value mapping
steps.
Example
You want to create new records without the creation of key mapping information, for example, in a migration.
You want to create Business Partner relationships for already existing Business Partner records. In this case, the
Business Partner IDs in the uploaded le will be not checked against key mapping.
5/19/2023
Supported Device Types

Desktop
Tablet
Manage Consolidation Processes
Use
The Manage Consolidation Processes feature enables you to manage consolidation processes. Click on the tile to enter the
Consolidation Processes overview screen:
Features
The Consolidation Processes overview screen shows you processes according to the lter criteria you enter. For
information on how to lter, see Filter Processes.
You can create consolidation processes on the Consolidation Processes overview screen. For further information on how
to create a process, see Create Consolidation Processes.
You can navigate to an existing consolidation process. For further information on how to run a consolidation process, see
Run Consolidation Processes.
You can delete consolidation processes. For information on how to delete processes, see Delete Processes.
Filter Processes
Use
The hit list of the Processes overview screen shows consolidation and mass processes according to your lter criteria.
Features
The Processes overview screen offers a lter bar with the following lter criteria:
Process ID
Description
Data Source
User
Creation Date
Status
To hide the lter bar choose Hide Filter Bar.
To display the lter bar choose Show Filter Bar.
To con gure the lter bar choose Filters. The Filters dialog box is displayed. Mark or unmark the lter criteria using the
Add to Filter Bar indicators and choose Go.
5/19/2023
 Note
You can save your settings as a variant. To do so choose Save, in the Save Variant dialog box enter a name and choose
OK.
To restore the standard settings choose Restore.
Activities
To lter the result of your hit list, enter search criteria in the corresponding elds of the lter bar and choose Go.
Use the input help for the elds User and Status.
Use the calender function for the Start Date eld.
Delete Processes
Use
 Note
According to the authorization assigned, you can either mark processes for deletion or delete processes permanently.
You can delete all processes that do not have the status In Process. You can delete processes in the hit list of the Processes
overview screen and in any Process detail screen.
Procedure
In the hit list of the Processes overview screen:
1. Mark the processes you want to delete.
2. Choose Delete and OK to con rm.
In the Process detail screen, choose Delete and OK to con rm.
Run Consolidation Processes
Use
A consolidation process consists of several process steps. The order of the process step is de ned by the process template you
select when you create the process. For further information on the setup of process templates, see Specify Process Template.
A typical consolidation process consists of the process steps listed below in the displayed order:
Standardization
Matching
Best Record Calculation
Validation
5/19/2023
Activation
Features
Within the Consolidation Process details screen you can select any process step to display the assigned process step
parameters.
 Note
According to the authorizations assigned, you can change the process step parameter:
Use the input help to change the Adapter
Use the input help tho change the corresponding Adapter Con guration.
You can set a checkpoint that stops the consolidation process after a speci c process step. This is visualized by
changing the Forward symbol to a Pause symbol. To do so, select the Check Point Active indicator.
System Messages are displayed for individual process steps. Errors or exceptions are visualized by the color of the process step
ikon:
Green: No errors or exceptions occurred.
Orange: Errors or exceptions occurred.
Messages are displayed in the lower part of the process step screen. For certain messages links to details are offered.
Red: Process step failed.
In addition you can call up a list of all messages generated throughout the consolidation process by choosing the corresponding
button.
Activities
1. In the hit list of the Consolidation Processes overview screen click the corresponding line to navigate to an existing
consolidation process.
The Consolidation Process details screen opens.
2.
To start a consolidation process, choose Start or Continue.
 Note
Depending whether a consolidation process has not been started yet or has been paused temporarily the one
or the other button is displayed.
 Note
The Continue button might appear inactive according to the settings in the Customizing activity Specify
Process Template for example to ful ll the four-eyes-prinzipal and according the role assigned to your user.
For more information, see Specify Process Template.
You can start or continue a consolidation process at any process step as long as the predecessor steps are
completed.
5/19/2023
To retry a consolidation process step , choose Retry.
Using the Retry feature might be required for example when validation has detected a missing entry in a
mandatory eld.
To roll back to a certain process step, choose Rollback.
A dialog box offers offers the process steps that have already been processed.
To save the con guration of the consolidation process, choose Save.
To delete a consolidation process, choose Delete.
You can delete consolidation processes that do not have the status Complete.
For more information, see Delete Processes.
To display the Audit Trail pane, choose Show Audit Trail. In case the Audit Trail pane is displayed you can hide it
choosing Hide Audit Trail. For more information, see Audit Trail.
To discard changes in the con guration and to leave the consolidation process, choose Cancel.
Constraints
To keep the performance of the consolidation and mass processing high, for processes containing more than 100.000 records
changes are not displayed.
Create Consolidation Process
Use
The Create Consolidation tiles enable you to create consolidation processes for business partner, business partner
relationsship, or material.
Activities
1. On the Consolidation and Mass Processing for Business Partner Data or Consolidation and Mass Processing for
Material Data launch pad, click the Create Consolidation tile.
2. Enter a Description.
3. Use the input help to select a Process Goal.
Consolidation of Source Records: Records can be loaded repeatedly to be consolidated. The records are not
replicated to the source systems.
Consolidation for Central Maintenance: Records are loaded only once in the hub system. After being consolidated
the records are replicated to the source systems. You can use MDG, central governance to perform the central
maintenance.
Consolidation of Active Records: Your active master data records are checked for duplicates and best record are
de ned according to your settings.
4. Use the input help to select a Process Template.
For further information of process templates, see Specify Process Template.
5. Use the input help to select the Data Sources for the consolidation process.
5/19/2023
6. Select the Delete Source Data indicator, if you want the source data to be deleted after the consolidation process has
nished. Select the Keep Source Data indicator, if you want the source data to be kept after the consolidation process
has nished.
7. Choose Save.
Result
You have created a consolidation process.
Related Information
Standardization
Use
Standardization normalizes and enriches address data. Additionally a check ensures that a speci c address really exists.
 Example
Enrichment: A record only contains the postal code 69190. The corresponding city Walldorf is added.
Normalization: Baker Str, is converted to Baker Street.
Activities
1. Depending on the authorizations assigned, you can change the process step parameter.
Select an adapter in the Process Using eld and the corresponding adapter con guration in the Con guration
using the input help.
If you want the process to stop after this process step, mark the Check Point Active indicator.
2. To start a process, choose Start or Continue.
 Note
Depending whether a process has not been started yet or has been paused temporarily the one or the other button is
displayed.
 Note
The Continue button might appear inactive according to the settings in the Customizing activity Specify Process
Template for example to ful ll the four-eyes-principle and according the role assigned to your user.
You can start or continue a process at any process step as long as the predecessor steps are completed.
If a checkpoint is con gured for the process step, the process stops after nishing the process step.
To display the results of the process step choose Show Results.
5/19/2023
 Note
Depending on your authorization, the status of the process, and the status of the current process step the following
additional options exist:
Retry
The results of the current process step are discarded and the process step restarts.
Rollback
A dialog box offers the process steps that have already been processed. You can select an entry to restart the
processing at this point.
Save
The con guration of the process is saved.
Delete
For more information on deleting processes, see Delete Processes.
Cancel
To discard changes in the con guration and to leave the process, choose Cancel.
 Note
This process step allows you to manually replace values of elds or to clear the elds content completely:
1. On the Process detail screen choose Show Results.
2. Choose one of the table speci c tabs, such as General, as the feature is not available on the Overview tab.
3. Mark the records you want to edit and select Replace Value or Clear Fields.
To replace values, enter the new value in the Replace Value for selected records dialog box and choose
Replace.
To clear elds, mark the corresponding eld in the Clear elds for selected records dialog box and choose
Clear.
Matching
Use
Matching checks data from various source systems and the active area for duplicates. Records that are considered to be
duplicates are displayed in match groups. Part of the matching is the match review to check match groups for possible
duplicates.
Activities
 Note
5/19/2023
Depending on the number of records you process and the Customizing for Step Scheduling a dialog box might be displayed.
Here you have the options to either specify the exact starting point or to start the process immediately. In case you have
speci ed a starting point and you want to change it, once again choose Continue.
 Note
displayed.
 Note
If a checkpoint is con gured for the process step, the consolidation process stops after nishing the process step.
To start the match review, choose Match Review.
For more information see, Match Review.
 Note
Retry
Rollback
Save
Delete
Cancel
5/19/2023
 Note
If you consolidate active records the header displays the process strategy for duplicate records to be applied. For more
information, see Consolidation of Active Records.
Match Review
Use
Matching identi es match groups. Depending on certain parameters these match groups are either automatically approved or
they are set to the status Open. The status Open is set if the speci ed approval score is not met or if user interaction is
required for example if a record matches with more than one active record. Open match groups should not be left in the
process, but be reviewed by the user to be either approved or rejected.
The identi ed match groups can be processed in the best record calculation. If you set a checkpoint for matching the
consolidation process stops after matching and enables you to check the matches in the match review.
Features
The Match Review Results screen gives you an overview on potential duplicates identi ed in the matching.
For business partner data you can toggle between Address Data and Identi ers that were used to identify the potential
duplicates.
 Note
As identi er only the identi cation type BUP001 (Dun & Bradstreet Number) is supported.
The potential duplicates are displayed in match groups.
The number of potential duplicates and whether a best record exist in the active area is displayed.
The Match Review Results screen offers a lter bar with a wide range of lter criteria.
Group Status allows you to display match groups in the status Approved, Open, or Rejected.
Match Group Size allows you to display match groups of different sizes.
Groups per Page enables you to adapt the amount of displayed groups to your needs
A wide range of further lters allows you to adapt the search.
 Note
For more information on how to work with the lter bar see Filter Processes.
The Match Review Results screen allows you to edit the match groups.
You can reject match groups.
You can reject single records in a match group.

5/19/2023
You can split match groups.
Activities
1. To start the match review in the Consolidation Process detail screen select the process step Matching and choose
Match Review.
The Match Review Results screen displays the match groups. As default the match groups are automatically approved
and get the Group Status Approved.
2. To split a match group mark at least two records and choose Split.
The marked records are bundled to a new match group. All records remain their status.
 Note
As a match group must at least contain two records, you can split groups that contain at least four records.
3. To reject a complete match group choose Undo Approval.
The match group gets the status Open. It disappears from the list with Group Status Approved. To nally reject
the match group search for Group Status Open and choose Reject All. The match group gets the status
Rejected. It disappears from the hit list with Group Status Open.
To undo the rejection search for Group Status Rejected and choose Undo Rejection.
 Note
Open match groups should not be left in the process, but be reviewed by the user to be either approved or rejected.
4. To reject single records in a match group choose Reject.
 Note
As a match group must at least contain two records, the Reject buttons only appear for match groups as of three
records.
The record is grayed out but remains visible in the match group. In the best record calculation the record is
treated as a single record without assignment to the match group.
To reassign the record to the match group choose Undo Rejection.
5. If two or more records of a match group belong to the active area, one of these active records is preselected as the
target record for the best record calculation. This is visualized by a target and arrow icon. The other active records are
treated as single records though displayed in the match group.
If you want to change the selection choose Set as Target.
 Note
The new target record is marked with the target and arrow icon and is displayed in the rst row of the match group.
Constraints
To keep the performance of the consolidation process high, for processes containing more than 100.000 records changes are
not displayed.
5/19/2023
Best Record Calculation
Use
Best record calculation results in a best record containing the cumulated, most valuable data for each match group that is
identi ed by the matching. This calculation follows a well de ned process based on a set of rules.
Activities
 Note
displayed.
 Note
If a checkpoint is con gured for the process step, the consolidation process stops after nishing the process step.
 Note
Retry
Rollback
Save
Delete
5/19/2023
Cancel
Example
Your source systems show the following entries in table BUT0BK (BP: Bank Details) for the elds BANKL (Bank Key), BANKN
(Bank Account Number) and, KOINH (Account Holder Name).
System BANKL BANKN KOINH
A11 10010010 32168000 Rosy
B22 10010010 32168000 Rosi
C33 10010010 32168000
The Customizing activity is con gured in the following way:
Order of Source Systems:
Table Seq. No. Business System
1 C33
2 B22
3 A11
As the table eld does not contain any entry the order of source system is taken into account for all tables.
Order of Rules for Tables:
Table Seq.No. Rule ID
BUT0BK 1 SOURCE_SYSTEM
The rule SOURCE_SYSTEM is taken into account for the table BUT0BK.
Order of Rules for Fields:
Table Field Name Seq.No. Rule ID
BUT0BK KOINH 1 COMPLETENESS
The rule COMPLETENESS is taken into account for the eld KOINH in table BUT0BK.
The rules are applied as follows:
1. On table level the rule SOURCE_SYSTEM selects system C33 as system with the highest priority. Therefore in the rst
step the following set of data is selected for the preliminary best record:
5/19/2023
BANKL BANKN KOINH
10010010 32168000
2. On eld level the rule COMPLETENESS is applied. The eld KOINH remained empty in the rst step. Now the set of data
is completed with data from system B22 as this is the highest rated system that contains data in the KOINH eld.
BANKL BANKN KOINH
10010010 32168000 Rosi
 Note
Only if Order of Rules for Table contains an entry referring to the rule SOURCE_SYSTEM, either speci c for table
BUT0BK or generic for all tables, the KOINH eld is completed in the described way. If the Order for Rules for Table
settings do not contain a corresponding entry, the source system is not taken into account and it is not to be
predicted what data is used to complete the KOINH eld.
Best Record Calculation Review

Use
Best record calculation results in a best record containing the cumulated, most valuable data for each match group that is
identi ed by the matching. This calculation follows a well de ned process based on a set of rules.
Features
The Review Best Record screen gives you an overview on the results of the best record calculation.
It shows you in detail how the best records were calculated.
The data can be reviewed for each individual table
You can manually adapt certain data.
You can manually delete super uous rows.
 Note
Deletion is supported for a speci ed set of tables. It might be used for example to delete an address that is a
potential duplicate. For certain tables deletion only is allowed if you select one duplicate out of the remaining to
replace the duplicate to be deleted.
To undo a deletion use the standard Rollback option of the process step Best Record Calculation.
Activities
1. To start the best record calculation review in the Consolidation Process details screen select the process step Best
Record Calculation and choose Show Results.
2. On the Best Record Calculation Results screen mark the records you want to review and choose Review
3. On the Review Best Record screen choose a certain table to review the corresponding best record calculation.
5/19/2023
4. To edit the data choose Edit.
5. To delete a record, mark the corresponding row and choose Delete.
Constraints
To keep the performance of the consolidation process high, for processes containing more than 100.000 records changes are
not displayed.
Update
Use
Within the process step update data is updated by the system using BRF+ rules.
For more information, see De ne Rules Using the Business Rule Framework plus.
Activities
 Note
displayed.
 Note
 Note
Retry
Rollback
5/19/2023
Save
Delete
Cancel
 Note
Replace.
Clear.
Filter and Remove
Use
Within the process step lter and remove a certain selection of records is removed from the current consolidation process.
According to your settings this selection of records then is moved to a new consolidation process or – in case of records with
errors out of a validation process – further options can be applied. The process step lter and remove can be used only as
successor of the following process steps:
Best record calculation
Validation
Matching
 Note
Filter and remove is a background step executed by the system without user interaction.
In the newly created process the Delete Source Records indicator always has the value “unde ned”. The value of the original
process is not copied.
To process the source records according to the settings of the original process, the original process needs to be nalized.
5/19/2023
Activities
 Note
displayed.
 Note
 Note
Retry
Rollback
Save
Delete
Cancel
5/19/2023
 Note
Replace.
Clear.
Derivation
The derivation step enables you to update your elds based on one or more derivation scenarios de ned in the De ne
Derivation Scenarios app.
Prerequisites
When creating the process you have selected a process template that supports the derivation step.
Activities
 Note
displayed.
 Note
 Note
If you want to change the Package Size, choose Adjust and then enter a number in the Package Size eld. The Package Size
de nes how many objects can be processed within one package in the run. If you are encountering timeout issues for your
runs, you can use this setting to reduce the volume of objects to avoid these issues. If you don’t enter a number in the
Package Size eld, the system uses 500 as the default size.
5/19/2023
 Note
Retry
Rollback
Save
Delete
Cancel
 Note
Replace.
Clear.
Validation
Use
Validation checks whether the quality of a record is sufficient to meet the requirements de ned in the back-end system. If the
quality requirements are met data can be saved, if not corrections and data enrichment might be required.
Activities
 Note
5/19/2023
Choose the Process Using and the corresponding Con guration using the input help.
 Note
displayed.
 Note
3. To display the results of the process step choose Show Results.
 Note
You can manually replace values of elds or clear the content of elds completely:
a. Choose one of the table speci c tabs, such as General, as the feature is not available on the Overview tab.
b. Mark the records you want to edit and select Replace Value or Clear Fields.
Replace.
To clear elds, mark the corresponding eld in the Clear elds for selected records dialog box and
choose Clear.
If you have changed the results of the validation and you choose Continue the system offers to create a new
validation step with exactly the same settings as the current validation.
4. To export the records to a spreadsheet, choose Export Business Partners, Export BP Relationships, or Export Products.
You are directed to the Export Master Data app.
 Note
You can also export records that caused messages in the validation step. In this case the export le contains the data
of the selected records and the related messages.
The export is not possible if there has been a matching or best record calculations step in the process before.
 Note
5/19/2023
Retry
Rollback
Save
Delete
Cancel
Further information
If you want the validation to use validation rules, select the Apply Validation Rules indicator.
For more information, see Using Validation Rules.
Activation
Use
Activation adds the records to the systems active area. How the system proceeds with different types of records is speci ed in
the con guration of MDG, consolidation and mass processing.
Activities
 Note
Select the Adapter and the corresponding Adapter Con guration using the input help.
 Note
displayed.
5/19/2023
 Note
Template for example to ful ll the four-eyes-prinzipal and according the role assigned to your user.
As activation is the last process step before a optional replication, the process stops after nishing this process step.
To display the results of the process step, choose Show Results.
In case incorrect records where detected, choose Show Incorrect Records.
 Note
Retry
Rollback
Save
Delete
Cancel
The Result (Activation) chart enables you to display a Summary of Changes screen. This screen offers an overview of all the
records that were changed within the process.
To access the Summary of Changes screen click a column of the Result (Activation) chart and then choose Show Details.
All records belonging to the selected column are displayed.
The Summary of Changes screen offers a Show Changes link for each item. Here the changes on table and eld level are
displayed in the same way as in the Track Changes app.
To export the active records of your process to a spreadsheet, press the Export Active Records button. This will lead you to the
Export Master Data app. Here the By Process ID eld is pre lled with the Process ID of the current process.
Concept of Concurrent Changes

Within the process step activation con icts caused by concurrent changes may be detected:
5/19/2023
Con icting but unchanged records will be updated with active data.
Con icting and changed records with same values will not change.
Con icting and changed records with different values provoke an error message and get the status Partially nished.
For error handling you can choose between the options listed below:
Finishing the process will ignore the changes from the process and will keep the active values. To do so choose
Finish.
Retry will take over the changed values from the process. To do so choose Retry.
Removing con icting records allows a retry or nish of the process. Active values stay valid.
Further information
If you want the activation to use validation rules, select the Apply Validation Rules indicator.
For more information, see Using Validation Rules
Audit Trail
Use
The audit trail lists all events that take place within a process, such as starting and nishing a process step or changing process
parameters.
Features
The audit trail displays an abstract for each event in a time line, the most recent ones on top of the list. The abstracts contain
the following information:
User name
Timestamp
Description
A system generated short description of the event.
 Example
Configuration changed
Best Record Calculation" (step 3) started
Link to the Audit Trail: Details (optional)
In case the process has been changed several times the Audit Trail: Details offer a summary of the changes.
Activities
To display the Audit Trail pane in the process detail screen, choose Show Audit Trail.
In case the Audit Trail pane is displayed, you can hide it by choosing Hide Audit Trail.
5/19/2023
To refresh the Audit Trail pane choose Refresh.
A lter function enables you to see these sets of events:
All
Exclude System User
System User
Export Master Data
Use
The Export Master Data app enables you to export a selection of master data to a local le. This le can be used for Mass
Maintenance and for Mass Processing of Master Data.
Features
The following business objects are supported:
Business Partner
Business Partner Relationship
Product
Activities
1. De ne Scope
To select data from speci c elds, mark Select Speci c Fields and use the input help for your selection. The Select: Table
and Field Name dialog box is displayed.
To select all data mark Select all Fields from All Tables.
 Note
Due to reasons of data protection and privacy, sensitive personal data such as bank data and credit
management data is not included in the export les for mass processing. To maintain this kind of data, please
use the appropriate single-object processing.
When generating the export le, the system always uses the most restrictive authorization pro le to select
the data records.
For example, a user has two authorization pro les, a master data maintenance pro le with display
authorization, and a mass change and export pro le with full authorization. In this case, the display pro le is
taken into account and as display authorization is not sufficient to export data records no data is written to
the export le.
2. Select Business Partner / BP relationships / Product
By Selection Criteria
Use the selection criteria with Include and Exclude options.
5/19/2023
If you want your selection criteria also to be applied as a lter for the resultant export le, mark the Use Selection
Criteria as Filter indicator.
 Example
You have entered the following selection criteria for a product:
FIELD Operator Value
Material Number (MARA-MATNR) contains AB0000*
Plant (MARC-WERKS) contains 0001
If the Use Selection Criteria as Filter is not marked the following data is visible on the MARC - Plant
Data tab:
SOURCE_ID WERKS
AB00001 0001
AB00002 0001
AB00003 0001
AB00001 0002
AB00001 0003
For AB00001 the plant 0001 data and also the plant 0002 and 0003 data is exported.
If the Use Selection Criteria as Filter is marked the following data is visible on the MARC - Plant Data
tab:
SOURCE_ID WERKS
AB00001 0001
AB00002 0001
AB00003 0001
For AB00001 only the plant 0001 data is exported.
By Process ID
Use the input help to select a Process ID. The records of the selected process are taken into account.
3. File Format
Use the radio buttons to select either Office Open XML (*.xlsx) or Compressed CSV (*.zip) as le format for the data
export.
 Note
In case of large data quantities SAP recommends to use the Compressed CSV (*.zip) as this format has less memory
consumption on the application server. For additional information, see File Format for File Upload.
4. Export
5/19/2023
To export, choose Export. The system generates a le to be downloaded.
5. Download
To download the le, choose Download File.
 Note
The Office Open XML (*.xlsx) created by the Export Master Data app displays the downloaded tables as separate
worksheets. All key elds are displayed in the formatting type Underline.
Track Mass Changes
Use
The Track Mass Changes app enables you to display and monitor the changes on eld level that were made to a business object
based on a consolidation, mass processing or mass maintenance process.
 Note
Track Mass Changes is based on change documents in the backend system. Only tables and elds for which change
documents are activated are displayed.
Features
Business Partner
Product
Activities
1. Enter Selection Criteria
Enter selection criteria to obtain a list of consolidation processes and mass processes and choose Go.
All changes corresponding to your selection criteria are displayed.
2. Obtain additional information on the processes
The hitlist according to your selection criteria is a smart list offering popovers displaying additional information.
3. Display changes on eld level
To display a change to a business object select the corresponding line.
The changes are displayed showing the old and the new value on eld level.
Support of Business Partner relationships
Use
5/19/2023
This feature enables you to support business partner relationships.
Features
You can use consolidation for business partner relationships as follows:
As a combined process with the business partners and their relationship
As a simple process with only the relationships of the business partners that are already in the system
Manage Source Data for Consolidation
Use
This feature enables you to manage source data for consolidation.
Features
You can manage your source data in the following ways:
Organize your source data for your consolidation process
View a list of your source data organized by source system and divided by data package.
Delete source data
Use
This feature enables you to import data for consolidation
Features
The Import of data supports you in the following way:
Upload records for consolidation into the source data tables using an Office Open XML or CSV le
Use data packages to divide your records up for organizational purposes
Consolidation of Active Records
Use
This feature enables you to consolidate active records.
Features
5/19/2023
You can run consolidation processes based on the active data you already have in the system rather than just data you are
loading into in the system.
In the best record calculation the best record is determined according to the rules and may be improved be additional data from
its duplicates. Additionally you apply a certain process strategy for duplicate records to be applied:
Remove Duplicates: The duplicates are marked for deletion. The key mapping is directed to the best record
 Note
If you have selected the Remove Duplicates strategy, the system will not nd the removed duplicates anymore in
case of further consolidation processes.
Improve Best Record: The duplicates are kept unchanged. The key mapping remains unchanged.
Improve All Records: The duplicates are kept, but become copies of the best record. The key mapping remains
unchanged.
This type of process can also be scheduled. For more information, see Schedule Consolidation of Active Records.
Procedure
A typical consolidation of active records process consists of the process steps listed below in the displayed order:
1. Selection: Enter the search criteria to select the objects that you want to edit.
2. Matching
 Note
The match review offers information about the Match Decision of the currenct process. If consolidation processes
were already performed on the active records, then Previous Decisions are also displayed.
3. Best Record Calculation
4. Validation
5. Activation
Support of classi cation data in consolidation
Use
This feature enables you the support the classi cation data in consolidation.
Features
Classi cation data for product, customer, and supplier is supported.
Mass Processing of Master Data
Use
5/19/2023
Mass Processing enables you to update multiple master data records at a time. The function is available for the product master,
business partner (including customer and vendor), business partner relationship, and custom object domains. You can access
this function through the Start Mass Processing and Manage Mass Processing tiles in the SAP Fiori Launchpad.
To update records you select the elds and records you want to change. The system then displays a list of elds to change based
on your selection. Once you enter your changes, the system provides statistics on the changed elds and validates the data. You
check the validated data and then activate it. Activation copies the data from the staging area to active memory, enabling the
system to use it in business transactions.
 Note
Business partners that have reached the end of purpose (EoP) cannot be processed in MDG, mass processing. For more
information, see Scheduling Block Business Partners under Master Data Business Partner/Customer/Supplier
Integration .
Integration
You can use mass processing with or without Master Data Governance, Central Governance. If you use Central Governance,
you can choose to use the change request and validation features.
Mass processing uses the same technical foundation as the consolidation capabilities of Master Data Governance, allowing you
to combine the features in a exible process con guration. Packaging, queuing, and parallelization contribute to enhanced
performance even when processing large volumes of data.
Features
Administrators can prepare templates called con gurations for frequently executed change scenarios. These
con gurations enable users to perform their tasks without the need to understand eld and table structures in detail.
You can use the le upload feature to upload changes to business objects in .XLSformat and .CSV format (using a
semicolon as a delimiter). When using le upload the elds and records are set by the le and the system hides the
Selection step. For more information see Technical Settings for File Upload.
The system executes processing in the background, enabling users to close the application and check the status later.
You can also save a Mass Processing run and come back to work on it later.
In the case of business partner relationsships a mass deletion process is supported. For more information, see Mass
Deletion of Business Partner Relationships.
Master Data Governance, Mass Processing

With this app you can update multiple master data records at a time. The function is available for the material, business partner
(including customer and vendor), and custom object domains. You can also process business partner relationships. To update
records, you select the elds and records you want to change. The system then displays a list of elds to change based on your
selection. Once you enter your changes, the system provides statistics on the changed elds and validates the data. You check
the validated data and then activate it. Activation copies the data from the staging area to active memory, enabling the system
to use it in business transactions.
Key Features
This app provides the following key features:
5/19/2023
Administrators can prepare templates called con gurations for frequently executed change scenarios. These
con gurations enable users to perform their tasks without the need to understand eld and table structures in detail.
You can use the le upload feature to upload changes to business objects in .XLSX and .CSV format (using a semi-colon
as a delimiter).
The system executes processing in the background, enabling users to close the application and check the status later.
You can also save a Mass Processing run and come back to work on it later.

Desktop
Tablet
Mass Deletion of Business Partner Relationships
Use
If you run mass processes on business partner relationships the option of mass deletion is supported.
Features
The mass deletion process consist of the process steps Edit and Activation.
Activities
1. Open the Manage Mass Processes (BP Relationships) tile and choose Create Process Mass Deletion
2. Enter a Description.
3. Select the process template SAP: Mass Deletion BP Relationships.
4. Choose Save to create a new process.
5. Enters Selection criteria and choose Start.
Manage Mass Processing
Use
The Manage Mass Processes feature enables you to manage mass processes. Choose the Manage Mass Processes tile to
enter the Manage Mass Processes overview screen.
Features
The Manage Mass Processes overview screen shows you processes according to the lter criteria you enter.
You can create mass processes on the Manage Mass Processes overview screen. For further information on how to
create a process, see Start Mass Processing.
You can navigate to an existing mass process. For further information on how to run a mass process, see Run Mass
Processes.
5/19/2023
You can delete mass processes. For information on how to delete processes, see Delete Processes.
Procedure
1. Choose the Manage Mass Processes tile for the object type you want to process.
2. From the Processes list, select the mass process you want to work on.
3. Choose Continue and then Start to begin the process and move to the Edit step.
 Note
At any point in the process, you can use the Rollback button to undo your changes and reset the objects to their
status in the previous step. Once you have completed the activation step, you cannot use the rollback feature.
You can also use the Show Audit Trail button to get an overview of what has happened in the process.
4. In the Edit step, choose Edit Records and make the required changes. Choose Continue to proceed with the process.
5. In the Remove Unchanged Data step, the system removes unchanged data from the process. This may improve
performance for the Validation and Activation steps.
6. On the Validation screen, check the validity of the edited data.
7. On the Activation screen, choose the adaptor and con guration for your activation. This is usually prede ned for you. You
can choose Adjust to manually change the settings. Choose Continue to nalize the process and write your changes
according to the adaptor and con guration.
Result
You have successfully started mass processing for the selected objects.
Filter Processes
Use
The hit list of the Processes overview screen shows consolidation and mass processes according to your lter criteria.
Features
The Processes overview screen offers a lter bar with the following lter criteria:
Process ID
Description
User
Creation Date
Status
5/19/2023
To con gure the lter bar choose Filters. The Filters dialog box is displayed. Mark or unmark the lter criteria using the
Add to Filter Bar indicators and choose Go.
 Note
You can save your settings as a variant. To do so choose Save, in the Save Variant dialog box enter a name and choose
OK.
To restore the standard settings choose Restore.
Activities
To lter the result of your hit list, enter search criteria in the corresponding elds of the lter bar and choose Go.
Use the input help for the elds User and Status.
Use the calender function for the Start Date eld.
Delete Processes
Use
 Note
According to the authorization assigned, you can either mark processes for deletion or delete processes permanently.
You can delete all processes that do not have the status In Process. You can delete processes in the hit list of the Processes
overview screen and in any Process detail screen.
Procedure
In the hit list of the Processes overview screen:
1. Mark the processes you want to delete.
2. Choose Delete and OK to con rm.
In the Process detail screen, choose Delete and OK to con rm.
Run Mass Processes
Use
A mass process consists of several process steps. The order of the process step is de ned by the process template you select
when you create the process. For further information on the setup of process templates, see Specify Process Template.
A typical mass process consists of the process steps listed below in the displayed order:
Start Mass Processing
Scope
Selection
5/19/2023
Edit
Validation
Activation
Additionally, you can add the following steps:
Update
Filter and Remove
Features
Within the Process details screen you can select any process step to display the assigned process step parameters.
 Note
According to the authorizations assigned, you can change the process step parameter:
Use the input help to change the Adapter
Use the input help tho change the corresponding Adapter Con guration.
You can set a checkpoint that stops the process after a speci c process step. This is visualized by changing the
Forward symbol to a Pause symbol. To do so, select the Check Point Active indicator.
System Messages are displayed for individual process steps. Errors or exceptions are visualized by the color of the process step
icon:
Green: No errors or exceptions occurred.
Orange: Errors or exceptions occurred.
Messages are displayed in the lower part of the process step screen. For certain messages, links to details are offered.
Red: Process step failed.
In addition you can call up a list of all messages generated throughout the process by choosing the corresponding button.
Activities
1. In the hit list of the Processes overview screen click the corresponding line to navigate to an existing process.
The Process details screen opens.
2.
To start a process, choose Start or Continue.
 Note
Depending whether a process has not been started yet or has been paused temporarily the one or the other
button is displayed.
 Note
The Continue button might appear inactive according to the settings in the Customizing activity Specify
Process Template for example to ful ll the four-eyes principal and according the role assigned to your user.
5/19/2023
To retry a process step , choose Retry.
Using the Retry feature might be required for example when validation has detected a missing entry in a
mandatory eld.
To roll back to a certain process step, choose Rollback.
A dialog box offers the process steps that have already been processed.
To save the con guration of the process, choose Save.
To delete a process, choose Delete.
You can delete processes that do not have the status Complete.
Constraints
To keep the performance of the consolidation and mass processing high, for processes containing more than 100.000 records
changes are not displayed.
Start Mass Processing
Use
Mass Processing enables you to change multiple business objects at the same time.
Procedure
1. Choose the Start Mass Processing tile for the object type you want to process.
2. Enter a description and choose a process template for your mass processing. The process template speci es which steps
are included in the process and their sequence.
3. If you require, you can browse for and import a le containing the changes you want to apply. This le must be in .CSV
format using a semicolon as a delimiter. To improve performance only include the elds that you want to update in the
le. For more information on the settings required for le upload see Technical Settings for File Upload.
 Note
You can also use the Export Master Data app to generate a le that might serve as an example for the le format.
4. Choose Save.
 Note
You can set check points throughout the process so that you can examine the data before moving it to the next step.
This allows you better control over the data.
5/19/2023
5. On the Scope screen, choose the con guration you want to use. The con guration is a prede ned scope selection
containing certain tables and elds. You can choose your own elds here instead of using a con guration. Set any check
points you want to use and choose the Selection icon to move to the next screen.
 Note
If you have selected a le in step 3, the Scope screen is not displayed. The scope is determined according to the
tables and elds maintained in the le. This may also overrule a scope de nition that is con gured in the process
template.
6. On the Selection screen, enter the search criteria to select the objects that you want to edit.
 Note
If you have selected a le in step 3, the Selection screen is not displayed. The selection is determined according to the
tables and elds maintained in the le.
7. Choose Save.
Result
You have set up a new Mass Process.
Technical Settings for File Upload

When uploading a le for mass processing you should consider a number of points. The le for upload must contain the following
information:
The rst row must contain all the elds that make up the primary key of the tables you want to update. The rst row also
contains the elds to be updated. Each key/ eld combination must be separated by a semicolon. The elds must be
speci ed as follows: <tablename>-<fieldname>. For example BUT000-PARTNER;BUT000-NAME_ORG2.
The remaining rows contain the values of the elds separated by a semicolon. For example: FUPTEST-01;Hello
World. If a value contains a semicolon you must wrap the value in double quotation marks. Use the following format for
values:
Date: YYYYMMDD
Time: HHMMSS
Numbers: Do not use characters for example, full stops or commas to group digits. Use a full stop to denote a
decimal.
Boolean: Use uppercase X for true.
If you want to use a different delimiter, enter transaction SU3 and set the Parameter Value of the GET/SET Parameter
MDC_FILE_SEPERATOR to the character you want to use.
If you want to use a different wrapper character, enter transaction SU3 and set the Parameter Value of the GET/SET
Parameter MDC_FILE_ESCAPE to the character you want to use.
You can use the le upload to insert or delete rows in tables related to an existing business object. You cannot use this function
to create or delete rows in the root table. For example you can create new identi cation numbers for an existing business
partner (updating table BUT0ID) but you cannot create a new business partner.
5/19/2023
For every table you want to add a row to you must insert a column name <Tablename>--ACTION_CODE, for example,
BUT0ID--ACTION_CODE. The possible values for this column include I (insert) and D (delete). You can only delete rows from a
limited range of tables based on the SAP ERP settings. You cannot delete rows for the material business object. The following
tables of the business partner business object (and customer and vendor respectively) support deleting rows:
ADR12 URL
ADR2 Phone
ADR3 Fax
ADR6 E-Mail
ADRC Address
BUT020 Technical Link Table for Addresses
BUT021_FS Address Usage
BUT0BK Bank Account
BUT0ID Identifier
BUT0IS Industry
BUT100 Role
DFKKBPTAXNUM Tax Number
KNB5 Dunning (Customer)
KNBW Withholding Tax (Customer)
KNVI Tax Indicator
KNVP Partner Function (Customer)
LFB5 Dunning (Supplier)
LFBW Withholding Tax (Supplier)
WYT1 Vendor Subrange
WYT1T Text Table Vendor Subranges
WYT3 Partner Function (Supplier)
 Note
If you delete a row it will not appear in the process. If you add a row it will appear as a changed row in the process. The
change will be still be visible in the Change Documents. To view change documents for a business object either enter the
object directly or use transaction RSSCD100.
Scope
Use
On the Scope screen, you choose the scope of elds you want to use for mass processing. You can choose from a con gured list
of xed scopes. The con guration is a prede ned scope selection containing tables and elds. You can also choose your own
elds here instead of using a xed con guration.
5/19/2023
Activities
Choose Adjust to adapt the prede ned scope chosen when creating the mass process. When adjusting the scope you can
use the Remove button to remove a eld from the process.
Choose Add Row to add new elds and tables. Use the input help to enter data in these new rows.
 Note
Depending on your authorization, the status of the mass process, and the status of the current process step the following
Save
The con guration of the mass process is saved.
Delete
Audit Trail
To display the Audit Trail pane, choose Show Audit Trail. If the Audit Trail pane is displayed you can hide it by choosing
Hide Audit Trail. For more information, see Audit Trail.
Back
To discard changes in the con guration and to leave the process, choose Back.
Selection
Use
On the Selection screen, you enter the search criteria to select the objects that you want to edit.
Activities
Choose Add New Line and use the input help to add new parameters to the mass process.
Choose Remove All to clear all parameters.
Choose Start to begin the mass process.
 Note
Save
Delete
You can delete processes that do not have the status Complete. For more information, see Delete Processes.
Audit Trail
5/19/2023
Back
Edit
Use
In the Edit step the system presents a table where you can directly enter the new values for one or several records at a time.
Statistics about the changed elds are automatically calculated. This provides con dence and transparency when changing
large volumes of data.
Activities
The Analytics pane enables you to drill down into the changed data to examine details and help in issue resolution.
The Edit Records button enables you to change individual records.
The System Messages pane shows you details of error and warning messages generated by the mass process.
 Note
Rollback
Save
Delete
You can delete processes that do not have the status Complete. For more information, see Delete Processes.
Audit Trail
Back
Update
Use
5/19/2023
Within the process step update data is updated by the system using BRF+ rules.
For more information, see De ne Rules Using the Business Rule Framework plus.
Activities
 Note
displayed.
 Note
 Note
Retry
Rollback
Save
Delete
Cancel
5/19/2023
 Note
Replace.
Clear.
Filter and Remove
Use
Within the process step lter and remove a certain selection of records is removed from the current consolidation process.
According to your settings this selection of records then is moved to a new consolidation process or – in case of records with
errors out of a validation process – further options can be applied. The process step lter and remove can be used only as
successor of the following process steps:
Best record calculation
Validation
Matching
 Note
Filter and remove is a background step executed by the system without user interaction.
In the newly created process the Delete Source Records indicator always has the value “unde ned”. The value of the original
process is not copied.
To process the source records according to the settings of the original process, the original process needs to be nalized.
Activities
 Note
5/19/2023
displayed.
 Note
 Note
Retry
Rollback
Save
Delete
Cancel
 Note
Replace.
Clear.
5/19/2023
Derivation
The derivation step enables you to update your elds based on one or more derivation scenarios de ned in the De ne
Derivation Scenarios app.
Prerequisites
When creating the process you have selected a process template that supports the derivation step.
Activities
 Note
displayed.
 Note
 Note
If you want to change the Package Size, choose Adjust and then enter a number in the Package Size eld. The Package Size
de nes how many objects can be processed within one package in the run. If you are encountering timeout issues for your
runs, you can use this setting to reduce the volume of objects to avoid these issues. If you don’t enter a number in the
Package Size eld, the system uses 500 as the default size.
 Note
Retry
Rollback
Save
5/19/2023
Delete
Cancel
 Note
Replace.
Clear.
Remove Unchanged Data
Use
In the Remove Unchanged Data step the system removes unchanged data from further processing to improve the performance
for the Validation and Activation steps.
Features
Unchanged product records are removed
In changed records the data of certain unchanged tables is removed. These tables are:
MARC (Plant Data)
MARD (Storage Location)
MLGN (Warehouse)
MVKE (Sales Data)
In the tables mentioned above unchanged entries including dependent data sets are removed.
Activities
This process step is running autonomously and directly leads to the next process step. It does not call for any manual
interaction.
5/19/2023
Validation
Use
Validation checks whether the quality of a record is sufficient to meet the requirements de ned in the back-end system. If the
quality requirements are met data can be saved, if not corrections and data enrichment might be required.
Activities
 Note
Choose the Process Using and the corresponding Con guration using the input help.
 Note
displayed.
 Note
3. To display the results of the process step choose Show Results.
 Note
You can manually replace values of elds or clear the content of elds completely:
a. Choose one of the table speci c tabs, such as General, as the feature is not available on the Overview tab.
b. Mark the records you want to edit and select Replace Value or Clear Fields.
Replace.
To clear elds, mark the corresponding eld in the Clear elds for selected records dialog box and
choose Clear.
If you have changed the results of the validation and you choose Continue the system offers to create a new
validation step with exactly the same settings as the current validation.
5/19/2023
4. To export the records to a spreadsheet, choose Export Business Partners, Export BP Relationships, or Export Products.
You are directed to the Export Master Data app.
 Note
You can also export records that caused messages in the validation step. In this case the export le contains the data
of the selected records and the related messages.
 Note
Retry
Rollback
Save
Delete
Cancel
Further information
If you want the validation to use validation rules, select the Apply Validation Rules indicator.
For more information, see Using Validation Rules.
Activation
Use
Activation adds the records to the systems active area. How the system proceeds with different types of records is speci ed in
the con guration of MDG, consolidation and mass processing.
Activities
 Note
5/19/2023
Select the Adapter and the corresponding Adapter Con guration using the input help.
 Note
displayed.
 Note
Template for example to ful ll the four-eyes-prinzipal and according the role assigned to your user.
As activation is the last process step before a optional replication, the process stops after nishing this process step.
To display the results of the process step, choose Show Results.
In case incorrect records where detected, choose Show Incorrect Records.
 Note
Retry
Rollback
Save
Delete
Cancel
The Result (Activation) chart enables you to display a Summary of Changes screen. This screen offers an overview of all the
records that were changed within the process.
5/19/2023
To access the Summary of Changes screen click a column of the Result (Activation) chart and then choose Show Details.
All records belonging to the selected column are displayed.
The Summary of Changes screen offers a Show Changes link for each item. Here the changes on table and eld level are
displayed in the same way as in the Track Changes app.
To export the active records of your process to a spreadsheet, press the Export Active Records button. This will lead you to the
Export Master Data app. Here the By Process ID eld is pre lled with the Process ID of the current process.
Concept of Concurrent Changes

Within the process step activation con icts caused by concurrent changes may be detected:
Con icting but unchanged records will be updated with active data.
Con icting and changed records with same values will not change.
Con icting and changed records with different values provoke an error message and get the status Partially nished.
For error handling you can choose between the options listed below:
Finishing the process will ignore the changes from the process and will keep the active values. To do so choose
Finish.
Retry will take over the changed values from the process. To do so choose Retry.
Removing con icting records allows a retry or nish of the process. Active values stay valid.
Further information
If you want the activation to use validation rules, select the Apply Validation Rules indicator.
For more information, see Using Validation Rules
Audit Trail
Use
The audit trail lists all events that take place within a process, such as starting and nishing a process step or changing process
parameters.
Features
The audit trail displays an abstract for each event in a time line, the most recent ones on top of the list. The abstracts contain
the following information:
User name
Timestamp
Description
A system generated short description of the event.
 Example
5/19/2023
Configuration changed
Best Record Calculation" (step 3) started
Link to the Audit Trail: Details (optional)
In case the process has been changed several times the Audit Trail: Details offer a summary of the changes.
Activities
To display the Audit Trail pane in the process detail screen, choose Show Audit Trail.
In case the Audit Trail pane is displayed, you can hide it by choosing Hide Audit Trail.
To refresh the Audit Trail pane choose Refresh.
A lter function enables you to see these sets of events:
All
Exclude System User
System User
Export Master Data
Use
The Export Master Data app enables you to export a selection of master data to a local le. This le can be used for Mass
Maintenance and for Mass Processing of Master Data.
Features
Business Partner
Product
Activities
1. De ne Scope
To select data from speci c elds, mark Select Speci c Fields and use the input help for your selection. The Select: Table
and Field Name dialog box is displayed.
To select all data mark Select all Fields from All Tables.
 Note
Due to reasons of data protection and privacy, sensitive personal data such as bank data and credit
management data is not included in the export les for mass processing. To maintain this kind of data, please
use the appropriate single-object processing.
5/19/2023
When generating the export le, the system always uses the most restrictive authorization pro le to select
the data records.
For example, a user has two authorization pro les, a master data maintenance pro le with display
authorization, and a mass change and export pro le with full authorization. In this case, the display pro le is
taken into account and as display authorization is not sufficient to export data records no data is written to
the export le.
2. Select Business Partner / BP relationships / Product
By Selection Criteria
Use the selection criteria with Include and Exclude options.
If you want your selection criteria also to be applied as a lter for the resultant export le, mark the Use Selection
Criteria as Filter indicator.
 Example
You have entered the following selection criteria for a product:
FIELD Operator Value
Material Number (MARA-MATNR) contains AB0000*
Plant (MARC-WERKS) contains 0001
If the Use Selection Criteria as Filter is not marked the following data is visible on the MARC - Plant
Data tab:
SOURCE_ID WERKS
AB00001 0001
AB00002 0001
AB00003 0001
AB00001 0002
AB00001 0003
For AB00001 the plant 0001 data and also the plant 0002 and 0003 data is exported.
If the Use Selection Criteria as Filter is marked the following data is visible on the MARC - Plant Data
tab:
SOURCE_ID WERKS
AB00001 0001
AB00002 0001
AB00003 0001
For AB00001 only the plant 0001 data is exported.
5/19/2023
By Process ID
Use the input help to select a Process ID. The records of the selected process are taken into account.
3. File Format
Use the radio buttons to select either Office Open XML (*.xlsx) or Compressed CSV (*.zip) as le format for the data
export.
 Note
In case of large data quantities SAP recommends to use the Compressed CSV (*.zip) as this format has less memory
consumption on the application server. For additional information, see File Format for File Upload.
4. Export
To export, choose Export. The system generates a le to be downloaded.
5. Download
To download the le, choose Download File.
 Note
The Office Open XML (*.xlsx) created by the Export Master Data app displays the downloaded tables as separate
worksheets. All key elds are displayed in the formatting type Underline.
File Format for File Upload
Use
You can change master data by uploading a le that is either in CSV or in Office Open XML format. The le de nes which master
data objects are updated, which tables and elds to update, and the respective values. Besides changing existing data, you can
also add and delete rows of tables that support this operation. If you use a le for changing master data, you see all affected
elds on the UI in the Scope step. The Selection step will not be visible on the UI, as the selection is completely de ned by the
le content. The le must be formatted as de ned below.
 Note
You can use the Export Master Data app to generate a le that might serve as an example for the le format.
 Note
SAP recommends to use the compressed CSV format as described in the chapter Compressed CSV (*.zip) format as this
format offers the best performance and has less memory consumption on the application server.
CSV Format (*.csv)

The le contains the data in plain text and is interpreted by the system line-by-line. The le must be formatted according to the
following rules:
The le represents one single data table, each line in the le representing one row of the table.
Lines are formatted as a sequence of elds, each eld representing one cell of the table.
Lines are terminated by <CR><LF> or by <CR>.
5/19/2023
Adjacent elds are separated with a semi-colon.
Field values can optionally be enclosed in double-quotes.
If a eld value contains a semi-colon it must be enclosed in double-quotes. For example A;B is represented by "A;B".
If a eld value contains a double-quote it must be enclosed in double-quotes and the value's double-quote hast to be
duplicated. For example A"B is represented by "A""B".
The rst line in the le is the header line. It de nes the columns of the data table by referring to a table and eld
combination of the object's data model. The notation of the reference is <TABLE>-<FIELD>. Examples of <TABLE> are
BUT000, MARA, ADRC, MARA_STXH, and KNB1. The values for <FIELD> are de ned by the corresponding template table.
Examples are PARTNER, MATNR, VKORG, NAME_ORG1, and GROES.
You can change the elds that are available when de ning the scope of a mass process using the user interface.
All subsequent lines in the le are interpreted as lines of data to be used for updating the master data object.
The values in each data line are in the sequence as speci ed by the header line.
The system assumes an encoding with UTF-8.
Key elds
The master data object to be updated is identi ed by the key elds in the root table, for example, BUT000-PARTNER or MARA-
MATNR. As an alternative you can use SOURCE_ID. In all cases the root tables name can be omitted, so PARTNER, MATNR and
SOURCE-ID are valid options. If two colums like PARTNER and SOURCE-ID both appear in the same le, always the SOURCE-
ID is taken into account as object key.
The le must contain every key eld of all tables that contain data. For example, in case of storage location data for products
(MARD), these are: MATNR, WERKS, and LGORT. You can omit key elds of a table, if the respective values can be derived from
the table’s parent table. For example, you can omit MARD-WERKS, if a value for MARC-WERKS is present.
The relevant key elds are not detected based on the corresponding active table, but based on the assigned process table, for
example KNA1_PRC instead of KNA1. That is why in the mentioned example the eld ASSIGNMENT_ID exists to load several
KNA1 data sets for a single business partner.
Inserting and Deleting Rows

You can use le upload to insert or delete rows in tables related to an existing business object. You cannot use this function to
create or delete rows in the root table. For example, you can create new identi cation numbers for an existing business partner
(updating table BUT0ID) but you cannot create a new business partner.
For every table you want to add a row to you must insert a column name <Tablename>-_ACTION_CODE, for example,
BUT0ID-_ACTION_CODE. The possible values for this column include I (insert) and D (delete). You can only delete
rows from a limited range of tables based on the SAP ERP settings. For compatibility reasons -ACTION_CODE is equivalent to
_ACTION_CODE.
 Note
All key elds have to be lled with data.
The Office Open XML (*.xlsx) created by the Export Master Data app displayes all key elds in the formatting type Underline.
Keys as a combination of several key elds must not occure multiple times in the table.
The following tables of the business partner business object (and customer and vendor respectively) support deleting rows:
5/19/2023
ADR12 URL
ADR2 Phone
ADR3 Fax
ADR6 E-Mail
ADRC Address
BUT020 Technical Link Table for Addresses
BUT021_FS Address Usage
BUT022 Address-Dependent International Location Number
BUT0BK Bank Account
BUT0ID Identi er
BUT0IS Industry
BUT100 Role
DFKKBPTAXNUM Tax Number
DFKKBPTAXNUM_ADR Address-Dependent Tax Numbers
KNB5 Dunning (Customer)
KNBW Withholding Tax (Customer)
KNVI Tax Indicator
KNVP Partner Function (Customer)
LFB5 Dunning (Supplier)
LFBW Withholding Tax (Supplier)
WYT1 Vendor Subrange
WYT1T Text Table Vendor Subranges
WYT3 Partner Function (Supplier)
KNA1_AUSP Characteristics (Customer)
KNA1_KSSK Class Assignment (Customer)
LFA1_AUSP Characteristics (Supplier)
LFA1_KSSK Class Assignment (Supplier)
KNA1_ASSGMNT Additional ERP Customers
LFA1_ASSGMNT Additional ERP Vendors
The following tables of the product master support deleting rows:
MARA_AUSP Characteristics
MARA_KSSK Class Assignment
The following tables of business partner relationship data support deleting rows:
5/19/2023
ADR12 URL
ADR2 Phone
ADR3 Fax
ADR6 E-Mail
Formatting of Values
No conversion is applied to elds contents.
This means that values for PARTNER (Business Partner Number), MATNR (Material Number), or ADDRNUMBER (Address
Number) must include leading zeros. For example, 0000004711.
The values of elds that use conversion routines, for example SPRAS (language), must be given in their internal format.
For example, for the SPRAS eld E and not EN for English and for the MEINS (Base Unit of Measure) eld, KAR and not
CAR or CT for carton and IN3 for cubic inches.
Calendar dates appear in 8 digits, like the ABAP DATS format. For example, 19701217 for December 17, 1970
Timestamps appear in 15 digits, like the ABAP TIMESTAMP format. For example, 19490523170000 for May 23, 1949
5pm.
Numbers use the full stop as a decimal separator. Do not use a sign for digit grouping. Examples of correct values
include: 1234,1234.59, and 0.12345. Examples of incorrect values are: 1,234.56, 1.234,56, and 1234,56.
Office Open XML Format (*.xlsx)

This format might be more convenient than CSV, as it offers formating features and the option to hide rows or sheets. In
general, all statements for CSV also apply for the Office Open XML (XLSX) format with the following exceptions and additions:
The workbook ( le) can either contain one or multiple worksheets. Each worksheet must be structured as speci ed for
CSV. If you use multiple worksheets you can organize the content by providing one worksheet for each table of the data
to be imported.
You have the option to name the worksheet the same as the corresponding table, for example, MARA. In this case the
table name can be omitted in the reference. For example, if the sheet is named MARA, the reference can be MATNR
instead of MARA-MATNR.
 Note
If an entry in the header row has no hyphen, the worksheet's name up to the rst blank is interpreted as table name.
All following text is ignored by the upload but could be used for example as a description. If you name a sheet for
example BUT000 General Data only BUT000 is used as table name.
If you deal with tables in a certain namespace containing the / character, every / has to be replaced by a +. For
example +AB+MARA represents the table /AB/MARA. This restriction is only relevant for worksheet names.
If you structure the data in multiple worksheets, all key elds must be present on each worksheet. For example, a
worksheet for the address (ADRC) must contain the columns PARTNER (and/or SOURCE_ID), SOURCE_ADDRNUMBER,
DATE_FROM, and NATION.
Worksheets, rows, and columns that are marked as hidden are ignored during the import.
In general, you should use the format option Text for each cell in all worksheets. For example, this will not remove leading
zeroes when entering 0000004711. Values can be formatted using the possibilities in the XLSX format, such as when
entering calendar dates.
5/19/2023
Compressed CSV (*.zip) format

You can also use the compressed CSV format. In case of large data quanties SAP recommends to use the compressed CSV as
this format has less memory consumption on the application server.
The compressed CSV format consists of several CSV les that are bundled in a zip archive.
All the rules described in the chapters for CSV Format (*.csv) and Office Open XML Format (*.xlsx) are also valid for
compressed CSV.
The name of the CSV les up to the rst blank is interpreted as table name, all following text is ignored by the upload but
could be used as a description. If you name a le for example BUT000 General Data only BUT000 is used as table
name.
If you deal with tables in a certain namespace containing the / character, every / has to be replaced by a +. For example
+AB+MARA represents the table /AB/MARA. This restriction is only relevant for CSV le names.
All les in the ZIP-archive with endings other than .CSV are ignored by the upload process.
All les in sub folders within the Zip-archive are ignored by the upload process.
The CSV format does not offer the convenient Office Open XML features like the option to hide rows or worksheets. If
you want rows are les to be ignored by the upload you have to delete them.
Restrictions
Longtext elds such an MARA_STXL are not supported by the le upload
Speci c Syntax for Dynamic File Upload
Use
The le upload process offers a dynamic behaviour if you use the speci c syntax as described in this document. The tables below
contain example data to explain the given options. The example data is displayed in the Office Open XML format but would be
similar for the CSV format.
General
The eld names in the header row have the following naming convention as described in the document File Format for File
Upload.
 Note
SAP recommends to use the compressed CSV format as described in the chapter Compressed CSV (*.zip) format as this
format offers the best performance and has less memory consumption on the application server.
Selection Criteria
Key elds as selection criteria
A dynamic behaviour is achieved by using an asterisk (*) for key elds such an the source ID ( PARTER, MATNR).
The hitlist is reduced by additional key data which can also be combined with an asterisk. In this example all business partners
with the BUT0ID-TYPE BUP001 and a BUT0ID-IDNUMBER starting with the character string 1234 are selected.
5/19/2023
PARTNER BUT0ID-TYPE BUT0ID-IDNUMBER
* BUP001 1234*
The asterisk can also be combined with the rst characters of the source ID. In this example all business partners having a
source ID starting with AB, the BUT0ID-TYPE BUP001, and a BUT0ID-IDNUMBER starting with the character string 1234 are
selected.
PARTNER BUT0ID-TYPE BUT0ID-IDNUMBER
AB* BUP001 1234*
Attribute values as selection criteria
To use an attribute value as selection criteria the @ character has to be set in front of the eld name. The attribute value can be
combined with an asterisk.
In the example below all business partners with the BUT0ID-TYPE BUP001 having an address in COUNTRY DE are selected.
PARTNER BUT0ID-TYPE ADRC-@COUNTRY
* BUP001 DE
Dynamic Behaviour
Within the le upload process, all the values entered in attribute elds are assigned to the business partner that meet the
selection critieria.
Range Update
The values of existing data sets are updated with the values entered in the attribute elds.
 Note
If you want to maintain values to not yet existing data sets you have to use the Dynamic Insert as described below.
For all business parters meeting the selection criteria COUNTRY is set to DE, REGION to O8 and LANGU to D.
Tab name: ADRC
 Note
In this example the tab is named ADRC. This name is added to all header elds where a table name is not mentioned
explicitely. The effect is the same as if for example the header eld COUNTRY was named ADRC-COUNTRY.
PARTNER BUT0ID-TYPE BUT0ID-IDNUMBER COUNTRY REGION LANGU
* BUP001 1234* DE 08 D
In this example the value DE in COUNTRY is used as additional selection critierea. REGION is set to 08 and LANGU is se to D.
Tab name: ADRC
PARTNER @COUNTRY REGION LANGU
5/19/2023
PARTNER @COUNTRY REGION LANGU
* DE 08 D
Dynamic Insert
The values entered in the attribute elds are inserted in new data sets.
 Note
If you want to update values in existing data sets you have to use the Range update as described above.
If you set the _ACTION_CODE to the value I values are inserted.
 Note
Each header-cell needs a table. If it is not given in the cell directly, the sheet name is considered as table name. In this
example _ACTION_CODE is equivalent to BUT100-_ACTION_CODE
In this example to all business partners having the BUT0ID-TYPE BUP001 and a BUT0ID-IDNUMBER starting with the
character string 1234 the customer role is assigned (BUT100-RLTYP has the value FLCU01).
Tab name: BUT100
PARTNER BUT0ID-TYPE BUT0ID-IDNUMBER _ACTION_CODE RLTYP
* BUP001 1234* I FLCU01
Dynamic Delete
If you set the _ACTION_CODE to the value D records are deleted. In the example for the business partner meeting the criteria -
among others BUT0ID-IDNUMBER 1234* the BUT0ID-IDNUMBER is deleted.
Tab name: BUT100
PARTNER _ACTION_CODE TYPE IDNUMBER
* D BUP001 1234*
Combined Dynamic Behaviour
You can combine the options as shown above in one le upload. The example shows entries on serveral tabs, each representing
a speci c data base table. In this example the business partners meeting the selection criteria are assigned to the customer
role, ADRC-LANGU is set to D, and BUT000-AUGRP is set to 0001.
Tab name: BUT100
PARTNER BUTOID-TYPE BUT0ID-IDNUMBER _ACTION_CODE RLTYP
* BUP001 329260281 I FLCU01
Tab name: ADCR
PARTNER BUTOID-TYPE BUT0ID-IDNUMBER LANGU
5/19/2023
PARTNER BUTOID-TYPE BUT0ID-IDNUMBER LANGU
* BUP001 329260281 D
Tab name: BUTOID
PARTNER BUTOID-TYPE BUT0ID-IDNUMBER AUGRP
* BUP001 329260281 0001
Range Copy
If you set the _ACTION_CODE to C data sets are copied. In this case a source and a target have to be speci ed. Between source
and target the operator ::= is used. In this example for all selected business partners the KNVV data with KNVV-VKORG 0001
are copied in data sets with KNVV-VKORG 0002. Additionally the value for KNVV-BZIRK is set to 000002 in the new data sets.
The related KNVP-VKORG data is also copied from 0001 to 0002.
Tab name: KNVV
PARTNER BUT0ID- BUT0ID- _ACTION_CODE VKORG WAERS BZIRK KNVP- KNVP-

TYPE IDNUMBER _ACTION_CODE VKORG
* BUP001 329260281 C 0001::=0002 USD 000002 C 0001::=0002
Track Mass Changes
Use
The Track Mass Changes app enables you to display and monitor the changes on eld level that were made to a business object
based on a consolidation, mass processing or mass maintenance process.
 Note
Track Mass Changes is based on change documents in the backend system. Only tables and elds for which change
documents are activated are displayed.
Features
Business Partner
Product
Activities
1. Enter Selection Criteria
Enter selection criteria to obtain a list of consolidation processes and mass processes and choose Go.
5/19/2023
All changes corresponding to your selection criteria are displayed.
2. Obtain additional information on the processes
The hitlist according to your selection criteria is a smart list offering popovers displaying additional information.
3. Display changes on eld level
To display a change to a business object select the corresponding line.
The changes are displayed showing the old and the new value on eld level.
Process Analytics for MDG, Consolidation and Mass Processing
Master Data Process Overview for Business Partners
Use
The Master Data Process Overview for Business Partner app shows overview information on both completed and open tasks.
You can use information from change request processes, consolidation processes, and mass processes as trigger to work on
tasks requiring your attention.
To use the lter bar options in order to restrict your results shown on the cards from this app, choose Adapt Filters.
The following lter bar options are valid for all cards from this app:
Created On:
You can lter for objects created during a speci c period of time.
Created By:
You can lter for objects created by selected users.
The following lter bar options are valid for change request-related cards from this app:
Change Request Type
You can lter for objects assigned to selected change request types.
Change Request Status
You can lter for objects assigned to selected change request statuses.
Business Object Type
You can lter for objects assigned to selected business object types.
The following lter bar options are valid for change process-related cards from this app:
Process Goal
You can lter for objects assigned to selected process goals.
Process Template
You can lter for objects assigned to selected process templates.
5/19/2023
Process Status
You can lter for objects assigned to selected process statuses.
 Note
You can create your own views of this app, save these views as tiles with indivual descriptions for your personal or for public
use. You can also send these views as email to other users.
For example, you can use the lter bar option Business Object Type, select Supplier or Customer to restrict your results and
save this as a variant as your own view.
From every card of the Master Data Process Overview for Business Partner app, you can navigate to the Change Request
Analysis for Business Partners app to display the corresponding change requests or to the Change Process Analysis for
Business Partners app to display the corresponding change processes.
Key Features
Total Change Requests
The information from this card can provide insights into the workload coming from change requests created and might
allow you to predict future trends based on this set of data.
Open Change Requests
This card displays the number of open change requests grouped by change request status or by change request type.
The information from this card can provide insights into the current workload and can help to optimize the processing
time of open change requests.
Overdue Change Requests
This card displays the number of overdue change requests that exceed a de ned due date. The overdue change requests
are sorted by days overdue.
The information from this card can provide insights into ways to reduce the number of delayed change requests and with
this might allow you to accelerate the remaining processing time.
Rejected Change Requests
This card displays the number of rejected change requests grouped by reasons for rejection.
The information from this card provides an overview of the volume of rejections, of the reasons for rejections, such as
the most used reasons. The information from this card can be used to analyze rejected change requests and to reduce
the number of rejected change requests to improve the change request process.
Change Requests with My Participation
This card displays the number of change requests with your participation grouped by change requests created by you
and change requests with your work ow involvement.
The information from this card provides an overview of those change requests where you are or where you have been
involved in the change request processing to support the analysis of all change requests with your involvement.
Longest Running Open Change Requests
This card displays the longest running open change requests sorted from the oldest change request to be displayed rst
to the newest change request to be displayed last.
The information from this card can provide insights to analyze and nalize the processing of these change requests with
the goal to improve the overall change request processing and to reduce the number of long-running change requests.
5/19/2023
Change Requests Older than 48 Hours
This card displays the number of open change requests older than 48 hours grouped by logical action.
The information from this card might allow you to trigger the processing of delayed change requests and to analyze the
delay of the process.
Processing Duration of Finalized Change Requests
This card displays the number of days of the average processing duration of nalized change requests grouped by
change request type and change request priority.
The information from this card can provide insights on how to optimize the average processing time comparing change
requests of selected change request types or change request priorities.
Open Consolidation and Mass Processes
This card displays the number of open change processes grouped by status.
time of the open change processes.
Duration of Consolidation and Mass Processes
This card displays the number of days of the average processing duration of change processes sorted by process goals
and grouped by open or nished change processes.
processes of selected open change processes and nished change processes.
Finished Consolidation and Mass Processes
This card displays the number of nished change processes by date.
The information from this card can provide insights into the workload coming from change processes and might allow
you to predict future trends based on this set of data.
Number of Processed Business Partners
This card displays the number of processed business partners grouped by process goal or by process template.
time of open change processes.
Consolidation Validation Results
This card displays the number of validation errors by date.
You can navigate from this card to the Change Process Analysis for Business Partner app to drill down to a selected
validation error for analysis.
Changed Business Partner Attributes
This card displays the number of business partner attributes that have been changed grouped by business partner table.
The information from this card can provide insights into the size and workload of nished change processes and can help
to optimize the overall processing of change processes.
Open Work Items by Responsibility and Status
This card displays the number of open work items for change requests grouped by responsibility or work item status. The
information from this card provides insights into the current workload and how many work items are being processed or
still waiting in the queue.
5/19/2023
Open Work Items by Change Request Type
This card displays the number of open work items for change requests grouped by change request type and steps. This
card displays the number of open work items for change requests grouped by change request type and processing hours.
For more details of processing hours, refer to De ne Time Frames for Analytics Attributes.
Completed Work Items
This card displays the number of open work items for change requests grouped by change request action, by change
request step, or by processing hours. The information from this card provides insights on volume of rejections and how
long ago the action took place, to decide if further analysis and improvement on change request processing is needed.
Total Processing Days of Completed Work Items
This card displays the total processing days for change requests work items in the past months. The information from
this card shows history workload trends for change request processing, so can decide if more resources are needed for
change request processing at certain times.
Average Processing Hours of Completed Work Items
This card displays the average processing hours of work items for change requests grouped by change request step, by
month, or by year. The information from this card helps you understand the processing efficiency on each change request
step and trends of average processing times in previous months and years, so you can decide if you need further analysis
and improvement of your change request processing.

Desktop
Tablet
5/19/2023
Relevant Business Catalogs

ERP Customer Governance (SAP_MDG_BC_ERPCUS_DATA)
ERP Vendor Governance (SAP_MDG_BC_ERPVEN_DATA)
Supplier Governance (SAP_MDG_BC_SUPPLIER_DATA)
Business Partner Governance (SAP_MDG_BC_BUPA_DATA)
Customer Governance (SAP_MDG_BC_CUSTOMER_DATA)
CMD - Consolidation and Mass Processing for Business Partner Data (SAP_CMD_BC_BP_MONPROCS)
Change Process Analysis for Business Partners

With this app you can carry out root cause analysis monitoring business partner-related process quality issues and keep a track
of your process quality in consolidation and mass processes using various drill-down dimensions.
Check the business partner data that is imported from consolidation and mass processes
Analyze change processes using different drill-downs on dimensions, such as, status, goal, and month of creation
Keep a track of the average processing time
You can navigate to the selected change process in consolidation or mass processing

Desktop
Tablet
Relevant Business Catalog

SAP MDG, Consolidation and Mass ProcessingSAP_TC_CMD_CMP_MONPROCS_COMMON
Business Role Template: SAP_BR_BUPA_MASTER_SPECIALIST
Master Data Process Overview for Products
Use
The Master Data Process Overview for Product app shows overview information on both completed and open tasks. You can use
information from change request processes, consolidation processes, and mass processes as trigger to work on tasks requiring
your attention.
To use the lter bar options in order to restrict your results shown on the cards from this app, choose Adapt Filters.
The following lter bar options are valid for all cards from this app:
Created On:
You can lter for objects created during a speci c period of time.
5/19/2023
Created By:
You can lter for objects created by selected users.
The following lter bar options are valid for change request-related cards from this app:
Change Request Type
You can lter for objects assigned to selected change request types.
Change Request Status
You can lter for objects assigned to selected change request statuses.
The following lter bar options are valid for change process-related cards from this app:
Process Goal
You can lter for objects assigned to selected process goals.
Process Template
You can lter for objects assigned to selected process templates.
Process Status
You can lter for objects assigned to selected process statuses.
From every card of the Master Data Process Overview for Product app, you can navigate to the Change Request Analysis for
Products app to display the corresponding change requests or to the Change Request Analysis for Products app to display the
corresponding change processes.
Key Features
Total Change Requests
This card displays the number of total change requests grouped by request date, change request status, and change
request type.
The information from this card can provide insights into the workload coming from change requests created and might
allow you to predict future trends based on this set of data.
Open Change Requests
This card displays the number of open change requests grouped by change request status or by change request type.
time of open change requests.
Overdue Change Requests
This card displays the number of overdue change requests that exceed a de ned due date. The overdue change requests
are sorted by days overdue.
The information from this card can provide insights into ways to reduce the number of delayed change requests and with
this might allow you to accelerate the remaining processing time.
Rejected Change Requests
This card displays the number of rejected change requests grouped by reasons for rejection.
5/19/2023
The information from this card provides an overview of the volume of rejections, of the reasons for rejections, such as
the most used reasons. The information from this card can be used to analyze rejected change requests and to reduce
the number of rejected change requests to improve the change request process.
This card displays the number of change requests with your participation grouped by change requests created by you
and change requests with your work ow involvement.
The information from this card provides an overview of those change requests where you are or where you have been
involved in the change request processing to support the analysis of all change requests with your involvement.
Longest Running Open Change Requests
This card displays the longest running open change requests sorted from the oldest change request to be displayed rst
to the newest change request to be displayed last.
The information from this card can provide insights to analyze and nalize the processing of these change requests with
the goal to improve the overall change request processing and to reduce the number of long-running change requests.
Change Requests Older than 48 Hours
This card displays the number of open change requests older than 48 hours grouped by logical action.
The information from this card might allow you to trigger the processing of delayed change requests and to analyze the
delay of the process.
Processing Duration of Finalized Change Requests
This card displays the number of days of the average processing duration of nalized change requests grouped by
change request type and change request priority.
requests of selected change request types or change request priorities.
Open Consolidation and Mass Processes
This card displays the number of open change processes grouped by status.
time of the open change processes.
Duration of Consolidation and Mass Processes
This card displays the number of days of the average processing duration of change processes sorted by process goals
and grouped by open or nished change processes.
processes of selected open change processes and nished change processes.
Finished Consolidation and Mass Processes
This card displays the number of nished change processes by date.
The information from this card can provide insights into the workload coming from change processes and might allow
you to predict future trends based on this set of data.
Number of Processed Products
This card displays the number of processed products grouped by process goal or by process template.
time of open change processes.
5/19/2023
Consolidation Validation Results
This card displays the number of validation errors by date.
You can navigate from this card to the Change Process Analysis for Products app to drill down to a selected validation
error for analysis.
Changed Product Attributes
This card displays the number of product attributes that have been changed grouped by product table.
The information from this card can provide insights into the size and workload of nished change processes and can help
to optimize the overall processing of change processes.

Desktop
Tablet
Relevant Business Catalogs

Material Governance (SAP_MDG_BC_MATERIAL_DATA)
CMD - Consolidation and Mass Processing for Product Data (SAP_CMD_BC_PR_MONPROCS)
Change Process Analysis for Products

5/19/2023
With this app you can carry out root cause analysis monitoring product-related process quality issues and keep a track of your
process quality in consolidation and mass processes using various drill-down dimensions.
Key Features
Check the product data that is imported from consolidation and mass processes
Analyze change processes using different drill-downs on dimensions, such as, status, goal, and month of creation
Keep a track of the average processing time
You can navigate to the selected change process in consolidation or mass processing
Send emails
You can use this app to send an email containing a URL to the selected information in this app.
Share in SAP Jam
If your company uses SAP Jam groups, you can post your comments about a task there.
Save as a tile
You can create a tile that uses the current selection criteria as default settings.
Export to spreadsheet
You can use this app to export content to a spreadsheet.

Desktop
Tablet

SAP MDG, Consolidation and Mass ProcessingSAP_TC_CMD_CMP_MONPROCS_COMMON
Business Role Template: SAP_BR_PRODMASTER_SPECIALIST
App Extensibility: Process Analytics for MDG, Consolidation and

Mass Processing Apps
Use
You cannot extend Process Analytics for MDG, Consolidation and Mass Processing apps.
More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.
5/19/2023
Working with MDG, Central Governance

The following documents contain the information needed to work with master data governance. The documents explain
functions, describe commonly used processes, and give additional background information on objects and procedures in the
system.
General Functions
To enable you to execute the functions of Master Data Governance (CA-MDG), the following processes for importing,
processing, and replicating master data are provided:
Data Transfer
You use these functions to transfer master data between different systems.
Master Data Processing
You use these functions to change master data using the change request process.
Key Mapping
You use this function to create mappings between object instances by connecting their object IDs.
Data Replication
You use these functions to replicate data from the Master Data Governance hub to target systems.
Analysis of Change Requests
You use these functions to analyze the efficiency of change request processing in your organization.
Concept of Change Requests
De nition
You use change requests 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
de ned. The change request process starts with a user's rst entry for the purpose of creating or changing data.
The user selects a suitable change request type. This change request type determines the next steps in the process. A
prede ned group of people is assigned to each change request step. This group is authorized to carry out the activities of the
change request step — for example, adding additional information — and to pass the change request on to the next step.
The following gure illustrates the change request process. This process mainly consists of the submission, processing,
checking, and approval of a data change.
5/19/2023
Simplified example of a change request process
You can de ne the following in a change request step:
How to determine the processor
Checks
Data enrichment
User interface
A change request step type determines which activities can be executed by a speci c user.
More Information
For more information about change requests, see Customizing for Master Data Governance under General Settings
Process Modeling Change Requests , and also the following documents:
Authorizations for Change Requests
Creation of a Change Request
Processing of a Change Request
Change Requests
5/19/2023
Authorizations for Change Requests
De nition
You can use the authorization object Change Request Type (USMD_CREQ) to execute the following activities in change
requests:
Create
You need to assign the users who submit change requests to the Create activity.
Change
You need to assign the users who process change requests in a speci c change request step to the Change activity.
You also need to assign the users to the change request step in one of two ways: either directly as the processor, or
indirectly via Organization Management (for example, as a member of the organizational unit that is assigned as the
processor of a change request step). In this case, the users can perform any action possible in the change request step -
as de ned in the respective change request step type.
Display
You need to assign the users who determine the change requests using the business activity Display Change Requests
to the Display activity. The assignment of this activity is also required for displaying the header data of a change request.
Delete
You need to assign the users who delete change request drafts to the Create or Change activities, once each per change
request type. You also need to assign those users to the Discard activity so that they are able to delete data changes
that have not yet been activated.
Users require authorization for the Delete activity to be able to delete change requests in report program
USMD_DELETE_CREQUEST.
Discard
You need to assign the users who must be able to delete data changes that have not yet been activated to the Discard
activity. Users can use this activity to execute the report program USMD_DELETE_CREQUEST to reset a change request
back to its original state without changing the change request status or the current change request step.
Integration
In addition to the authorization for the change request, the system also checks authorizations at the data level. The system
de nes these authorizations either as generic using the authorization object USMD_MDAT or as non-generic using MDG
applications. In this manner, the system provides its own authorization checks for active data using the class of the reuse active
area. All users permitted to submit change requests of a certain type are able to save a draft before submitting the change
request. At any given time, a master data object must belong to a maximum of one change request. All change request drafts of
all users with authorization for a given change request type are available to allow for collaborative work on the master data.
More Information
For more information about authorization objects of SAP Master Data Governance, run the transaction SU21 and see the
objects FMDM and MDG.
For more information about change requests, see Concept of Change Requests.
5/19/2023
Locking, Interlocking, and Blocking of Entities
Use
To control the concurrent access to data, MDG uses the following concepts:
Locking of Objects
The system prevents simultaneous access from different logical units of work (LUWs) to the same object by locking the
object. This ensures, that at a single point in time an object is processed by only one user. When you edit any part of an
object, the system automatically locks the complete object. As a consequence, you cannot work on more than one
parallel change requests for the same object at the same time, even if it is a change request of a parallel change request
type.
Interlocking of Entities
The system ensures that there is not more than one open change request assigned to an entity by interlocking an entity
with an open change request. If you use a non-parallel change request to process an object, all its entities are interlocked
by this change request using the object list.
In parallel change requests the object list only registers the processed object but does not interlock it. Interlocking is
done on entity level by creating, changing or deleting entities of a business object. For this purpose the change list has
been introduced for interlocking entities of business objects. The change list contains the entities that are changed with
a change request. For each parallel change request you need to con gure the scope on entity type level to de ne which
parts of a business object can potentially be edited with a certain change request type. However, an entity is only
interlocked with a change request as soon as it is changed or created.
 Note
A change in one entity may result in a cross derivation of another entity of a different entity type. Since the change
request must then also interlock the derived entity, both entity types need to be part of the change request scope.
For more information, see Parallel Change Requests.
Blocking of Entities
The system prevents that an entity is changed that must not be changed due to application speci c reasons by blocking
an entity. With the MDG application framework you can block entities to ensure that these entities are not added to
change requests. The system checks, if application speci c reasons exist, whenever an entity is added to the object list of
a change request.
Because the blocking reason is provided by the access class, only entities with a reuse active area can be blocked or can
be used to create blocks for other entities
For more information, see Blocking of Entities (Block List).
More Information
Related Glossary
lock
interlock
block
5/19/2023
Master Data Processing

You can use the following Web Dynpro applications to change master data:
Single Processing of an Entity
Collective Processing
Mass Change
The changes you make in these applications are saved in an inactive version. When the change request that contains the
changes is completed, the changed master data is saved as an active version in the database tables.
You can track your changes using the change documents, which you can display with the Web Dynpro application Change
Documents.
Search Business Object
Use
The Generic Search (USMD_SEARCH) service enables you to search for and display instances of business objects based on
speci ed criteria. You can use a large range of attributes to search.
 Note
The generic search is currently implemented in Financials and in Custom Objects. For information about application-speci c
search services, see the relevant help document in the structure for your application area under Working with Master Data
Governance.
Prerequisites
You have con gured the search according to your requirements. For more information, see Con guration of the Generic Search.
Features
Speci cation of Search Controls
Hierarchy Type
If the Hierarchy Type dropdown list displays, the business objects that are con gured to be searched can belong to hierarchies.
If the eld is left blank, a standard business object search occurs. Otherwise, a hierarchy search occurs.
Search Method
If a search method dropdown list displays, it has been con gured. If only one default search method is available, there is no
dropdown list. You can determine what kind of search is used, for example, a fuzzy search or a database search.
Speci cation of Search Criteria
Entry of Criteria
You can use dropdown lists and text boxes to specify values or value ranges for elds belonging to business objects that you
want the search to return. Each row in which you specify values is a search criterion. You can add a search criterion using Insert
5/19/2023
Row icon. You can delete a search criterion using the Delete Row icon. You can clear search criteria by choosing the Reset to
Default button.
You can specify criteria for multiple elds. You can also specify more than one criterion for the same eld.
If you have speci ed a Hierarchy Type, you must specify a Hierarchy. If the hierarchy is edition-dependent, you must specify the
Edition. If the hierarchy is version-dependent, you must specify the Version.
Logic Applied to Entered Criteria
The search returns instances of business objects that match the combined search criteria. The following logic applies:
AND logic for queries that refer to the same eld.
OR logic for queries that refer to different elds.
 Example
Search criteria:
Airline is LH
Airline is AF
Airline Name Contains Air
The query logic is as follows: (Airline Name is LH OR Airline Name is AF) AND Airline Name Contains Air
The search returns a row for Airline AF because its Airline Name, Air France, contains the string Air
The search does not return a row for Airline LH because its Airline Name, Lufthansa, does not contain the string Air.
Use of Saved Searches
You can save searches, use saved searches, and delete saved searches.
Restriction of Results
You can set the maximum number of results you want the search to return.
 Note
For edition-based business objects, it is possible for many results to appear for the same business object. Each result
represents an instance in which the business object data is changed and has its own valid-from date or valid-from period and
valid-to date or valid-to period.
Interpretation of Search Results
Search Without Hierarchy
This is the use case if you do not specify a hierarchy type, or if the hierarchy type is not relevant and therefore not available. The
display of search results is slightly different depending on whether the business object or objects being searched are edition-
based. With edition-based business objects, you can schedule changes for particular validity periods using editions.
Not Edition-Based
One row displays for each standard business object that satis es the search criteria.
5/19/2023
Edition-Based
A separate row displays for each validity timeframe of an edition-based business object that satis es the search criteria
The validity timeframe consists of the following:
The valid-from date or valid-from period of the scheduled change (inherited from the edition to which the change was
assigned).
The valid-to date or valid-to period of the scheduled change (one day or one period before the next occasion in which the
business object is changed.)
 Note
With hierarchy search, you must specify just one edition for an edition-dependent hierarchy.
Search with Hierarchy
The search results show business objects in the context of the hierarchy. A Hierarchy Type and a Hierarchy must be speci ed.
The hierarchy nodes that are shown are as follows:
All hierarchy nodes in the path from the root node to the node that matches the search
Nodes that match the search (Checkbox selected in Matches Search column)
A selection of hierarchy nodes beside the node that matches the search (up to 3 nodes before the match and up to 3
nodes after the match).
Use of the Search Results
 Note
The buttons and icons that display depend on how the search is con gured for your area.
Search without Hierarchy
Display
You can open the active data and inactive data (pending change requests) for business objects.
An icon in the Pending Change Requests A hyperlink to the business object Meaning
column allows you to access pending instance allows you to access active data.
change requests.
Yes No Someone has created a new instance of a

business object but has not nalized
changes.
Yes Yes An active instance of the business object

exists. A request to change the active
instance is in progress.
No Yes An active instance of the business object

exists. No request to change the active
instance is in progress.
Creation and Editing
5/19/2023
You can create a new business object, by choosing the Create button. If more than one change request type is available for the
Create action, you are prompted to enter a change request type. You can edit an instance of a business object that is in
process, by choosing the Pending Change Requests icon. You can edit an active instance of a business object by clicking its link
and then choosing the Edit button.
For more information about change requests, see Concept of Change Requests and the related documents.
If the business object is edition-based, you must assign an edition with an appropriate valid-from date or valid-from period to
the change request. The valid-to date or valid-to period is the end of time, until you schedule a subsequent change to the
business object. For more information about how the concept of editions enables the scheduling of changes to business objects,
see Using Editions to Schedule Changes to a Business Object.
You can create an instance of an edition-based business object by copying an existing instance. For more information, see the
description of the Copy feature.
Replicate
The Replicate button replicates the business object instance, providing replication is possible. You can choose the systems to
which you want to replicate data and view the replication log.
For more information, see Manual Replication by Object Selection.
Copy
You can use an existing instance of a business object as a template for creating a new instance by selecting the relevant row
and choosing the Copy button. If a pending change request exists for the object instance, the system copies the business object
instance from the pending change request. If more than one change request type is available for the Create action, you are
prompted to enter a change request type.
For business objects that use editions, you can use the copy feature to create a new instance of the same business object in a
different edition. For example, you can create an instance of account 1234 in the edition for Q2 based on account 1234 in the
edition for Q1. No other instances can exist in between the current edition and the target edition.
 Note
You can also create a new edition-based business object from an existing one and assign it to a different edition. This feature
is available with business function Master Data Governance, Generic Functions 7.0 Feature Pack (MDG_FOUNDATION_5).
This business function is available with support package 02 and higher support packages of MDG 7.0.
Mass Change
You can change the same data for multiple instances of a business object by selecting the relevant rows and choosing the Mass
Change button. For more information, see Mass Change.
Replication Status
You view the replication status of a scheduled change by selecting the relevant row and choosing the Replication Status button.
For more information, see Display of Data Replication Logs.
Multi-Processing
You can create, edit, or delete a number of master data records at the same time by selecting the records and choosing the
Multi-Processing button.
 Example
5/19/2023
An example of a multi-processing application is Multiple Record Processing. For more information, see Multiple-Record
Processing.
Block
You can indicate that a business object must not be used in certain business processes outside of Master Data Governance. For
example, you cannot order goods from a blocked supplier. The application that consumes the business object considers the
block in an application-speci c way. You can continue processing the business object using change requests regardless of this
block.
Mark for Deletion
You can indicate that a business object should be deleted by choosing the Delete icon. Until the deletion is activated outside of
Master Data Governance, you can continue processing the business object using change requests.
Search with Hierarchy
Next Match
You can use the Next Match button to navigate between the business objects that match your search criteria.
Expand All
You can choose the Expand All button to expand collapsed nodes in the search results display.
Hierarchy Processing
You can start hierarchy processing from any row in the search results list by selecting the row and choosing the Hierarchy
Processing button. The Hierarchy Processing user interface opens and the selected node is highlighted. For more information,
see Collective Processing.
Access Active Data
To access the active data for a business object, choose the hyperlink to the business object.
Creation of a Change Request
Use
You use this Web Dynpro application (USMD_CREQUEST_CREATE) to create a change request, which enables you to request
changes to master data.
Prerequisites
You have created at least one change request type in Customizing for Master Data Governance under General
Settings Process Modeling Change Requests Create Change Request Type .
If Edition is selected in the Validity eld for the entity type to be processed in Customizing under General Settings
Process Modeling Change Requests Create Change Request Type , you must have created an edition that you can
assign to this change request.
Activities
5/19/2023
Explain the reasons for the changes requested. You can upload a le instead (or as supplementary information).
If you have selected the Objects Required indicator for the type of change request, you have to enter all of the objects (entities
and hierarchy nodes) that are to be processed with this change request. You can include only objects that are not contained in
any open change requests.
If you include a hierarchy node in the change request, then you can process the substructure underneath that node (for
example, add new nodes).
Once you have requested the changes, the system automatically starts a work ow that forwards the change request to the
person responsible.
File Upload
Use
You use this Web Dynpro application (USMD_FILE_UPLOAD) to copy master data from a le to the database tables de ned in
the data model for Master Data Governance.
 Note
You can also copy master data from the database tables to a local le in CSV or Office Open XML (.xlsx) format using a le
download.
Prerequisites
A standard data model has been assigned to you. If a standard data model has not been assigned to you by means of the
user master record, you must assign a data model in this Web Dynpro application by choosing Change Model.
The le that is to be uploaded is a text le (for example, a CSV le) or an Office Open XML.
Binary les are not supported except for Office Open XML les.
For text-based les, eld values can be separated by a semi-colon, tab, comma, or other printable character. With the
exception of the tab, the system does not support hidden characters.
You have saved the le that is to be uploaded on either the presentation server (that is, your local PC) or the application
server.
Features
The application enables you to enter all of the parameters relevant for the le upload and then starts the upload process.
You upload the le for a speci c entity type (and for a speci c edition if an edition is required for the edition type). When you do
so, you can only upload master data for entity types with the storage and use types (SU type) 1 (Changeable via Change
Request; Generated Database Tables) or 4 (Changeable via Other Entity Type; Generated Database Tables).
You can also specify how the existing master data is to be handled during the upload process as follows:
The system deletes all existing master data. It then recreates the data records contained in the upload le.
The system deletes only the existing master data for which the upload le contains data records. It then recreates the
data records contained in the upload le.
5/19/2023
The system overwrites only those attributes in the existing master data that are contained in the upload le. All other
attributes are retained.
If the data records contained in the upload le are in an external format (the format that you see on the user interface), you can
convert them automatically to internal format (the format in which the data is stored in the database tables).
You can save the current settings as a variant. This means that you do not have to recon gure the parameters each time you
upload a le.
The system logs each le upload automatically in an application log. You can view the log in transaction SLG1 (object FMDM,
subobject UPLOAD).
Activities
If you have installed the Business Package for Financial MDM 1.51 in SAP Enterprise Portal, you can call this Web Dynpro
application in the Financial Master Data Governance work center by choosing the File Upload service in the Distribution
Monitor workset.
The application includes the following steps:
1. De ne entity type
2. De ne le structure
3. Specify upload settings
4. Check and execute
5. Con rm
De ne Entity Type
In this step, select a previously saved variant or con gure the general parameters for the le upload as follows:
Under Entity Type, select the relevant entity type for the le upload.
Use the Type of Transfer to specify which master data of the entity type is to be uploaded (attributes, language-
dependent texts, or hierarchies).
 Note
The Language-Dependent Texts transfer type can be selected only for entity types of (SU type) 1 that have language-
dependent texts.
You can upload texts directly in the respective logon language using the Attributes transfer type.
When you upload language-dependent texts, you must always ll in the Language Key eld.
De ne File Structure
In this step, select the entity types or attributes that you want to include in the upload data.
Specify Upload Settings
In this step, make the following settings:
Upload Mode
5/19/2023
In the Delete All and Add Records upload mode and the Attributes transfer type, the system deletes all existing
master data. It then recreates the data records contained in the upload le. This upload mode is only offered if
the settings of the Entity Type view of the Customizing activity Edit Data Model under General Settings Data
Modeling allow for deletion. However, this is permitted only if:
The master data to be deleted is not already used as a node in a hierarchy.
 Note
The system automatically deletes master data that is used as leaves in a hierarchy.
The master data to be deleted is not used in any other entity types.
 Note
Examples from the Financials area that show why master data must not be used in any other entity
types are as follows:
Each account is assigned to exactly one chart of accounts. If the chart of accounts is deleted, the
accounts that belong to it become invalid.
An account has the attribute Breakdown Type. If the breakdown type is deleted, the master
data for the account becomes invalid.
In the Overwrite or Add Records upload mode, the system deletes master data for which there are data records
in the upload le. It then recreates the data records contained in the upload le. This upload mode is only offered
if the settings of the Entity Type view of the Customizing activity Edit Data Model under General Settings
Data Modeling allow for deletion.
If the upload process does not include all of the attributes, the system sets the missing attributes to initial. If
attributes that are speci ed as required entry elds are not uploaded, the system issues an error message.
In the Overwrite or Add Attributes upload mode, the system deletes attributes for which there are attributes in
the upload le. It then recreates the attributes contained in the upload le in the following way:
If the upload le contains an attribute with an empty value for an existing attribute of the MDG system,
the system overwrites the existing attribute of the MDG system with the empty value of the upload le.
If the upload le contains no attribute for an existing attribute of the MDG system, the system keeps the
existing attribute of the MDG system.
If the upload le contains an attribute with a lled value for which there was no existing attribute in the
MDG system before, the system adds the attribute from the upload le to the MDG system.
Conversion
As a result of the settings in the user master record (transaction SU01 – Fixed Values tab page), it may be necessary to
convert the format of data records from external to internal format (date values and gures). To specify that the system
is to carry out a conversion, select the Execute Conversion option.
File Store
The le to be uploaded can be stored on either the presentation server (local PC) or on the application server.
If the le is stored on the application server, you must enter the absolute (complete) le path as the File Name.
 Note
You can display the le system of the application server using transaction AL11.
File Format
5/19/2023
In general, the system accepts only text les and Office Open XML les for the le upload.
 Note
When uploading Office Open XML les to the application server, the suffix of the lename must be .xlsx.
You can specify whether eld values are to be separated by a semi-colon, tab, comma, or other printable
character for a text le.
With the exception of the tab, the system does not support hidden characters.
You can specify the character used to begin a comment row in the uploaded le. The rst column of each
comment row must then contain this character. For text les, the rst character of a line controls whether this
line is considered as a comment. It is not required to place the comment character prior to each value in this line.
For Office Open XML les, this rst character of the rst column of a worksheet (typically column A) controls
whether this row is considered as a comment row. It is not required to place the comment character prior to each
cell value of the other columns in this row.
For Office Open XML les, if the rst character of a worksheets name is the comment character the whole
worksheet is considered a comment. If the comment character is *, it cannot be used to comment an entire
worksheet.
Check and Execute
In this step, the system uploads the data and checks it for consistency. In cases where there are messages that arise during le
upload, you can download them to an Office Open XML le.
If you have selected the Delete Uploaded upload mode, the system also identi es the master data that is to be deleted.
Before the system can delete the existing master data and save the uploaded master data in this step, changes to the master
data must be requested, approved, and logged using one or more change requests. As a result, the following must also be taken
into account in this le upload step:
If the uploaded master data and the data to be deleted is not yet included in a change request, the system prompts the
user to select or create a change request.
If the uploaded master data and the data to be deleted is not fully contained in a change request with a xed object list,
the user must enter a change request during the le upload process.
 Note
The change request type de nes whether a change request has a xed object list. You de ne the change request type
in Customizing for Master Data Governance under General Settings Process Modeling Change Requests
Create Change Request Type .
If the uploaded master data and the data to be deleted is already contained in a change request that has not yet been
released, a distinction must be made between the following cases:
The change request is assigned to the user who uploads the le.
In this case, no further steps are required.
The change request is assigned to a different user.
This leads to a termination.
If part of the uploaded master data and the data to be deleted is contained in different change requests (that are
assigned to the user and not yet released) and part is not assigned to a change request, only the master data that is not
5/19/2023
assigned to a change request is requested and logged in the change request speci ed by the user during the le upload
process.
If master data is to be deleted during the le upload and deleting the data automatically causes hierarchy entries to be
deleted, the hierarchy changes are also included in the change request. However, these hierarchy entries must not be
already used in a different change request of the user that has not yet been released.
Authorizations
File upload is an administrative and mass tool. If you do not want all of your users to be able to use it, you need to restrict
access using transaction PFCG. In addition, please note the following information regarding use of the le upload tool:
For performance reasons, le upload doesn’t check every object presented in the upload le
The system checks authorization at data type level only.
File upload is a generic tool and can be launched from any role. This means that any user can upload and download data
regardless of their roles, by changing the data model type. They do so by choosing the Data Model pushbutton. If you
want to disable (and hide) this pushbutton, you need to set the PROCESS parameter in transaction PFCG accordingly.
You can restrict the entity types displayed in the rst view of the File Upload Wizard by implementing BAdI
USMD_FILE_UPLOAD.
For more information about authorizations for change requests, see Authorizations for Change Requests.
Example
Initial population of master data tables during production startup.
File Download
Use
You can use this Web Dynpro application (USMD_FILE_DOWNLOAD) to copy master data from MDG-speci c database tables to
a local le in CSV format or as an Office Open XML le (.xlsx), allowing you to upload the data from this le to decentralized
systems.
Prerequisites
A standard data model is de ned in your user master record.
Features
The application lets you enter all the relevant parameters for the download and then starts the download process.
To avoid having to set the parameters again for each download process, you can save the current settings in a variant. The
variant management functions are integrated in the application.
Activities
application in the Financial Master Data Governance work center from the File Download iView.
5/19/2023
Authorizations
File download is an administrative and mass tool. If you do not want all of your users to be able to use it, you need to restrict
access using transaction PFCG. In addition, please note the following information regarding use of the le download tool:
File download is a generic tool and can be launched from any role. This means that any user can upload and download
data regardless of their roles, by changing the data model type. They do so by choosing the Data Model pushbutton. If
you want to disable (and hide) this pushbutton, you need to set the PROCESS parameter in transaction PFCG
accordingly.
You can restrict the entity types displayed in the rst view of the File Download Wizard by implementing BAdI
USMD_FILE_DOWNLOAD. For more information, see 2826197 .
For more information about authorizations for change requests, see Authorizations for Change Requests.
Example
This can be used to manually distribute data from the Master Data Governance hub to decentralized storage locations.
More Information
File Upload
File Formats for File Upload
Use
You can change master data by uploading a le that is either in CSV or Office Open XML format (.xlsx) using the File Upload app.
The le must be formatted as de ned here.
 Note
You can use the File Download app to generate a le that serves as an example for the le format for CSV and for Office
Open XML.
Formatting Requirements Applicable to CSV Format (*.csv) and Office Open XML
Format (*.xlsx)
The seperator character speci ed in the File Upload application must not be used in any value. For example, when the
seperator character is set to / (slash) there cannot be any value like He/she should....
A le generated by the File Download application contains comments that provide information about the data model,
entity type, variant, user, date, and time as well as selection conditions, edition, and hierarchy name (if applicable).
Moreover, the technical names of all columns are listed. These lines start with the character the user speci ed for
comments.
CSV Format (*.csv)

This le type contains the data in plain text and is interpreted by the system line-by-line. The le must be formatted according
to the following requirements:
Lines are formatted as a sequence of elds, each eld representing one cell of the table.
5/19/2023
Lines are terminated by a carriage return (CR) plus a line feed (LF) or by a carriage return only.
Fields are separated with a Separator de ned in the File Upload app.
The values in each data line are in the sequence as indicated in the comment section using the technical eld names.
The system assumes encoding with UTF-8-BOM.
Key Fields
A le must contain every key eld of the respective entity type. It is recommended to provide as many key elds as possible in
the header to expedite the performance of the File Upload application.
Formatting of Values
One of the nal steps in the le upload or le download is whether or not to execute conversion. If no conversion is
applied to eld content, values for PARTNER (Business Partner), MATNR (Material Number), or ADDRNUMBER (Address
Number) that include leading zeros will remain as entered. For example, 0000004711 with no conversion remains
0000004711. If however, conversion is executed, the leading zeros are deleted and the number becomes 4711.
The values of elds that use conversion routines, for example SPRAS (language), must be given in their internal format.
For example, for the SPRAS eld, E and not EN for English and for the MEINS (Base Unit of Measure) eld, KAR and not
CAR or CT for carton and IN3 for cubic inches.
Calendar dates appear in eight digits, like the ABAP DATS format. For example, 19701217 for December 17, 1970.
Timestamps appear in 15 digits, like the ABAP TIMESTAMP format. For example, 19490523170000 for May 23, 1949
5pm.
Numbers use the full stop as a decimal separator. Don’t use a sign for digit grouping. For example, 1234, 1234.56, and
0.12345. Incorrect examples include, 1,234.56, 1.234,56, and 1234,56.
Office Open XML Format (*.xlsx)

The Office Open XML format may be more convenient than the CSV format as it offers formatting features. The le must be
formatted according to the following requirements:
The workbook le can either contain one or multiple worksheets. The workbook must contain data for only one entity
type with the same attribute structure. The header data must only be speci ed once in the rst worksheet. For more
information, see SAP Note 2196009 .
Each worksheet must be structured with rows formatted as a sequence of elds in columns. Each eld represents one
cell of the table.
Worksheets can be excluded from processing by the File Upload application using the comment character at the
beginning of their name. That is, the worksheet name needs to start with the character speci ed for comments. For
example, a worksheet with the name #CostCenter would be excluded if the comment character is #.
 Note
The asterisk (*) character cannot be used in a worksheet's name. If the user speci es the asterisk as the character
for comments, it is not possible to exclude any worksheet using this mechanism.
Worksheets, rows, and columns that are marked as hidden are ignored during processing in the File Upload application.
When downloading data using the File Download application in Office Open XML format, in general the format option
Text is used for each cell in all worksheets. This prevents the removal of leading zeros for values such as 0000004711.
When editing or creating Office Open XML les, cells can be formatted using the possibilities of the Office Open XML
format.
5/19/2023
Processing of a Change Request
Use
You can use this Web Dynpro application (USMD_CREQUEST_PROCESS) to change or display a change request.
Prerequisites
A change request has been created. For more information, see Creation of a Change Request.
Features
 Note
Some of the following functions are available only if permitted by the change request status and if you are currently the
change request processor.
Processing General Change Request Data
You can add or change general data for the change request, such as its name or priority.
Adding or Removing Master Data Objects (Entities) to Be Changed
You can add master data objects to be changed to the change request or remove master data objects from the change request.
 Note
You can add only objects that are not contained in another change request still in process. You can no longer remove objects
that have already been changed with this change request.
Calling Other Functions for Master Data Objects
When you have selected an object, you can directly start the single processing of an entity for that object or you can go to
Related Services and access the respective change documents, where-used list, work ow log, or replication log. When you
select multiple objects, you can run a mass change for those objects.
Adding Comments and Other Information
You can add comments and les or hyperlinks to additional information to a change request.
Using the Change Request Tracker to Monitor Progress
The Change Request Tracker allows processors assigned to a change request to view the current work ow step, all previously
executed dialog work ow steps, as well as all future steps needed until the change request is successfully approved (referred to
as the 'golden path'). The Change Request Tracker can be called up via the What’s Next link, which is displayed in the change
request UIBB next to the entry for the current work item.
For work ow templates and standard change request types delivered by SAP, the Customizing settings required for determining
the next steps and golden path are prede ned. To de ne the golden path for custom change request types, use the Next Step
column in Customizing for Master Data Governance, Central Governance under General Settings Process Modeling
Work ow Rule-Based Work ow De ne Change Request Steps for Rule-Based Work ow or under General Settings
Process Modeling Work ow Other MDG Work ows De ne Change Request Step Numbers . Here you enter the IDs of
the next dialog steps following the current steps along the golden path of the current change request, until the nal and
5/19/2023
successful approval of a change request is achieved. You need to de ne all current and next step pairs up until the end of the
change request.
 Note
You don't need to de ne a next step for the last step of the change request.
Example:
The following example shows the con guration of work ow template WS75700040, the template used by many of the SAP-
de ned change request types for MDG for Financials. The change request consists of the steps:
0 Submission
1 Processing
2 Final Check
3 Revision
The de nition of the golden path for this change request includes both the direct way as well as the "detour" using the Revision
step. The following list shows the required setup using a current step -> next step view:
0 -> 1 (go from the Submission to the Processing step)
1 -> 2 (go from the Processing to the Final Check step)
2 -> SPACE (the Final Check is the last step in this change request; no next step needed)
3 -> 1 (if the change request is sent to Revision, the next step in the golden path after the revision is always the
Processing step)
Running a Validation and Displaying the Validation Log
To check the consistency of the speci ed changes to the master data, you can validate the change request and display a
validation log.
 Note
You can create validation rules in Customizing for Master Data Governance under General Settings Data Quality and
Search Validations and Enrichments De ne Validation and Derivation Rules .
For more information about de ning validation rules, see De ne Validations and Derivations.
You can also use existing validation rules for processes within SAP MDG, central governance. Check type 07 Validation Rules
(Data Quality) in Customizing allows you to de ne the change request types and change request steps in which these rules
are used. Note that you can only enable the use of Validation Rules (Data Quality) for change requests of data models that
use a re-use active area.
For more information about using existing validation rules, see De nition of Validations Using Validation Rules.
Activities
If you are the current processor of the change request and you have nished your part of the processing of the change request,
you forward the change request to the next processor through the work ow. The following actions are available in
V_USMD220C:
5/19/2023
01 Agree
02 Disagree
03 Approve
04 Reject
05 Finalize Processing
06 Send for Revision
07 Resubmit
08 Withdraw
09 Activate
10 Send for Revision
12 Recall by Requestor
As mentioned above, you can also use the Change Request Tracker under the What’s Next link in the change request header to
view the current work ow step, all previously executed dialog work ow steps, as well as all future steps needed until the change
request is successfully approved.
More Information
Change Documents
Where-Used List
Work ow Log
Mass Change
Approve Master Data - Extended
Use
With this app you can approve MDG master data change requests for a new or changed master data. Once a request is
submitted by requestor, it has to be approved by senior steward to create/change the master data in MDG. This app enables an
approver to see the details of requested master data and approve/reject it accordingly. You can use this app for the Cost
Center and Pro t Center, Customer, Supplier, GL Account, and Material objects.
Key Features
Approve or reject MDG Master Data
Display only the changed data to approver for approval of master data
Navigate to details of changed data when requested by approver
Display only elds which have data entered by the requestor
Display only relevant data based on authorization. For example, if a user is authorized to see data for a speci c company
code, they would not see data for other company codes.
5/19/2023
Display all requests of step type 2 (Approve) to approver in the inbox by default. You can extend the app to include
requests in other steps, that need only approval without editing data, by extending the backend classes.
If the long material number has been activated in your back-end system, it is automatically displayed in the Material eld in this
SAP Fiori app. For more information, see Extended Material Number in SAP Fiori Apps.

Desktop
Tablet
Smartphone

SAP_MDG_BC_APPROVER_T
Single-Object Processing
Use
You can use the USMD_OVP_GEN application to display or change individual business objects (or edition-based instances of
business objects) and to process these objects as part of the change request process.
Features
Accessibility from the Generic Search
You can view and change business objects directly from the Generic Search (USMD_SEARCH). For more information, see Search
Business Object.
Actions in Display Mode
When you view the active version of a business object you can start creating a change request using the Edit button in the
global toolbar of the application. Depending on the business object that you are working with you may also use the Edit or New
buttons in the assignment blocks. Depending on the customizing you may also create a change request to delete the business
object using the Delete button.
Actions to Create a Change Request
Save
Saves the current state of the change request as a draft for later processing.
Submit
Creates the change request and forwards it to the processor.
Cancel
Cancels the creation of this change request.
5/19/2023
Check
Checks the current state of the change request and the business object.
Actions to Process a Change Request
Edit
When you process a change request and the current step in the change request process allows you to change the
business object you can switch to edit mode.
Cancel
Switches to display mode and discards unsaved changes.
Save
Saves the current state of the change request for later processing.
Check
Checks the current state of the change request and the business object.
Change Documents
Opens a list of changes that were done in previous steps of this change request. For more information, see Change
Documents.
Work ow Log
Allows you to examine the previous change request process steps and to see which persons were already involved.
Depending on the current step in the change request process, buttons appear on the UI that enable you to send the change
request on to the next processor (as de ned in the work ow). For example:
Approve
Reject
Agree
Disagree
Withdraw
Finalize Processing
Send for Revision
Request Again
For more information, see the Customizing activity De ne Change Request Step Types and Assign Actions under General
Settings Process Modeling Work ow .
Change Request Assignment Block
When you create or process a change request you can edit general information about the change, notes, and attachments in
this area.
Validity Assignment Block
5/19/2023
If you work with an edition-dependent business object, you can identify in this area for how long a change is valid and when the
next change is going to occur.
Highlight Changes
 Note
This feature is available with business function Master Data Governance, Generic Functions 7.0 Feature Pack
(MDG_FOUNDATION_5). This business function is available with support package 02 and higher support packages of MDG
7.0.
The system highlights changes of a business object on the UI in the change request process. This helps you to nd a particular
change on the change request UI telling you what you need to check and approve. You can use the highlight changes feature
together with the MDG Web Dynpro applications for single-object processing. For more information, see Highlight Changes.
Undo Changes
 Note
7.0.
The MDG system collects all your actions between two client/server roundtrips in MDG Web Dynpro applications in one step
that can be undone. You can undo all actions of this step using Undo. You can undo all steps carried out since the last save. After
you have used Undo, you can use Redo to recover your actions.
After you have saved or deleted an object, you cannot use Undo anymore. After you have canceled your changes, you cannot
use Undo anymore.
To deactivate this function, set the application parameter DO_START_VETO to X.
Next Change
If an edition-dependent business object is changed in the future, the Validity section allows you to accomplish the following:
View when the business object is next changed.
Identify the edition in which the business object is next changed.
Access the relevant instance of the business object by clicking the date beside the Next Change eld.
Hierarchy Assignment Block
 Note
This assignment block is only available for selected business objects in Master Data Governance, Financial Data and Master
Data Governance for Custom Objects,.
You can assign a business object to one or more hierarchies from single-object processing, and you can remove the assignment
of a business object to a hierarchy. To create a hierarchy assignment, you can navigate to the parent node and make the
assignment, or you can specify the parent node directly. To remove an assignment, you can simply delete the relevant table row.
The Next Hierarchy Changes button allows you to open a dialog box that lists further editions that you can use to change the
hierarchy assignments. The list contains editions in the objects' validity period with hierarchy changes for any object of the
5/19/2023
same object type in any hierarchy or version (if version-dependent). The list does not contain the edition of the change request
but the next changing edition of the object.
For more information about the process of assigning single objects to hierarchies, see Hierarchy Assignments in Single-Object
Processing.
 Note
When assigning business objects to the hierarchy in the single-object processing user interface, be aware of the following:
If you want to restructure a hierarchy, rather than simply assigning individual business objects as nodes to the
hierarchy, we recommend you use the Collective Processing (USMD_ENTITY) WebDynpro application. For more
information see Collective Processing.
If the target hierarchy has one root node and no subnodes, you must enter the root node of that hierarchy in the
Parent Node column. This node is not found when you search for it.
You must nalize the change request before the system allows you to add, delete, remove, or change the hierarchy
properties of other hierarchy nodes that have the same parent node. If you prefer to be able to process other nodes
with the same parent while the hierarchy assignment is pending, use the Collective Processing (USMD_ENTITY)
WebDynpro application instead.
Hierarchy Assignments in Single-Object Processing

Concept
In Master Data Governance for Financials and in Master Data Governance for Custom Objects, you can create or remove the
assignments of just one business object to one or more hierarchies in Single-Object Processing (USMD_OVP_GEN). For example,
while you create or edit an airline in single-object processing, you can assign it to one or more airline alliances in a hierarchy.
Process
Requestor
1. Create or edit a business object from the search.
2. Assign the business object to a hierarchy. In the initial screen, you can type either the Parent Node by itself or the Parent
Node and the Previous Node. Alternatively, you can search for the location in the hierarchy into which you want to insert
the node, by clicking the New pushbutton, which opens up a new dialog box. To search for a point of insertion, proceed as
follows:
a. Search for attributes either of the desired parent node or of a desired adjacent node. .
b. Scroll or choose the Next Match pushbutton until you have found the part of the hierarchy into which you want to
insert the node. Select a node and then choose either the Insert as Subnode pushbutton (to assign the node as
the rst subnode of a selected parent node) or the Insert as Next Node pushbutton (to assign the node
immediately after the selected node).
3. Save changes. The status of the change request is now Changes to be Executed. After making the assignment, related
nodes are interlocked. For more information, see De ne Scope for Changes.
5/19/2023
Requestor Step
Processor
1. Edit and enrich the business object from the incoming change request.
2. Proceed as follows
a. In the Hierarchy Assignment block, view existing hierarchy assignments.
b. If necessary, create an additional hierarchy assignment. For instructions, see the description of the process for
the Requestor in this document.
3. Submit changes for approval. The status of the change request is now Final Check to be Performed.
5/19/2023
Processor Step
Approver
1. Edit and review the business object from the incoming change request.
2. Proceed as follows
a. View existing hierarchy assignments.
b. Display these assignments in the context of the hierarchy. Click the hierarchy icon to display the assignment in
context.
3. Approve or reject the changes. The status of the change request is now either Final Check Approved. or Final Check
Rejected
5/19/2023
Approver Step
Business Context Viewer in Single-Object Processing
Use
In Master Data Governance you can use the Business Context Viewer (BCV) to display context-related information on the
current business object in single-object processing applications such as USMD_OVP_GEN. The system displays the information
in an area at the right side of the screen called side panel.
Prerequisites
Business Functions
FND, Business Context Viewer Main Application (/BCV/MAIN)
FND, Business Context Viewer Main Application 2 (/BCV/MAIN_1)
FND, Business Context Viewer NWBC Side Panel (/BCV/NWBC_SIDEPANEL)
Business Content
You have activated the BC set BCV Content for MDG Framework (MDGAF_BCV) in transaction SCPR20.
5/19/2023
If you want to pass on information on the current business object (for example, the object key) to BCV for which no BCV
meanings exist yet, you have to create appropriate meanings.
If you want to display information on the business object for which no BCV business content exists yet, you have to create
appropriate content. You have to assign this content to BCV context key MDGAF_SOM or to a context key you have created
before.
For more information, see Con guring Business Context Viewer (BCV).
Activities
1. Open the application con guration of the single-object processing application in change mode. Enter
/BCV/SIDEPANEL_20 in the Con guration ID of Side Panel eld. Enter the BCV context key (for example MDGAF_SOM)
in the BCV_CONTEXT_KEY eld. Save the con guration.
2. Open the component con guration of the relevant UIBBs of the single-object processing application in Change mode.
Enter the corresponding BCV meanings, extended by the pre x /BCV/: (for example /BCV/:1ACCOUNT), in the Tag
Name elds of those UI elements whose values the system should pass to BCV. Save the con guration.
 Note
You can access the con gurations either in the Customizing for Master Data Governance under General Settings
UI Modeling Manage UI Con gurations or in transaction SE80.
3. When running the single-object processing application, open the BCV side panel by choosing the Side Panel link in the
upper right corner of the screen. In the Overview area of the side panel, choose the business content you want to display
from the Select Content dropdown list.
More Information
For more information about the functions of BCV, see Business Context Viewer.
Blocking of Entities (Block List)
Use
With this function you can prevent that entities are changed that must not be changed due to application speci c reasons. For
example, in MDG for Supplier changes to certain types of business partner relationships must be prevented, if a particular
business partner relationship has been changed.
With the MDG application framework you can block entities to ensure that these entities are not added to change requests.
Application speci c reasons need to be implemented with an access class using the methods GET_BLOCKLIST_FOR_READ and
GET_BLOCKLIST_FOR_WRITE of the interface IF_USMD_PP_ACCESS. The system checks, if application speci c reasons exist,
whenever an entity is added to the object list of a change request.
 Note
Because the blocking reason is provided by the access class, only entities with a reuse active area can be blocked or can be
used to create blocks for other entities.
This function covers the following use cases that have been implemented in the example access class for the ight data model.
1. External Reason
5/19/2023
The entity is blocked independent of whether any other entity is being processed with a change request, in particular
independent of any entry in the block list. In this case the access class throws the exception CX_USMD_PP_BLOCKLIST.
Optionally a message can be added to inform the user of the reason for the block. In the ight data model example the
airline BA is always blocked this way and an application speci c message is raised. All ight connections for airlines X6
and X61 are blocked this way as well.
If the access class does not provide an application speci c message, MDGAF adds a generic message. This case is
covered with the block of airline CX.
2. Same Entity Type (Symmetric)
The processing of an entity blocks the processing of another entity and vice-versa. In the ight example the processing of
airline CO blocks airline DL, as well as processing of airline DL blocks airline CO.
3. Same Entity Type (Asymmetric)
The processing of one entity blocks another, but not vice-versa. CX blocks DL, but DL does not block CX. In conjunction
with the previous use case, this means that DL could be blocked twice: Once from CO and once from CX.
4. Other Entity Type
Processing of one entity blocks entities of another type. CARR -> PFLI: Processing of CO blocks all ight connections of
CO, CX blocks all ight connections of CO with a number starting with 5 (block list entry), DL blocks ight connections 1111
and 2222 of DL PFLI->CARR, processing of ight connections of CO blocks airline CO.
The following table provides an overview of the blocking use cases implemented in the data model SF:
Reason for Block Blocked Entity Comment
External reason BA Use case 1: Block with application speci c

message
External reason BX Use case 1: Block with generic message

created from the application framework
External reason Flight connections of airlines X5 and X61 Use case 1: Block with generic message
created from the application framework
CO is in change request DL Use case 2
DL is in change request CO Use case 2
CX is in change request DL Use case 3
CO All ight connections of CO Use case 4
CX All ight connections of CO with a number Use case 4

starting with 5
DL DL ight connections 1111 and 2222 Use case 4
Any ight connection of CO Airline CO Use case 4
For more information about the example access class for the ight data model, see the documentation of the access class
CL_MDG_FS_SFLIGHT_ACCESS of the data model SF.
Integration
Technical Implementation
5/19/2023
1. Before an entity type is added to a change request, the method GET_BLOCKLIST_FOR_READ is called. If the processing
of an entity must be prevented regardless of the processing of any other entity, the access class
CL_MDG_FS_SFLIGHT_ACCESS provides the exception CX_USMD_PP_BLOCKLIST. Optionally a message can be added
(see use case 1). If the blocking depends on the processing of other entities, block values are returned. The framework
checks a table of block list values, whether this entry exists. Only if the entry is not in the table adding the entity to the
change request is possible.
2. After an entity is added to a change request, the method GET_BLOCKLIST_FOR_WRITE is called. The access class
provides block values that are added to the table of block values and are considered when determining blocks the next
time an entity should be added to a change request.
For more information, see the documentation of the interface IF_USMD_PP_BLOCKLIST.
Activities
When Can Blocked Entities Be Processed?
Finalizing Change Requests Removes its Blocks
After a change request is nalized that caused entries in the block list, the application framework removes these entries
from the block list. Then the respective blocks no longer exist. Previously blocked entities can now be processed again.
Using the Blocking Change Request to Process an Entity
It is possible to process a blocked entity using the blocking change request. Example: You created a change request to
process multiple airlines and added airline CO to this change request. This causes a block for airline DL and airline DL
cannot be added to another change request. However, you can add airline DL to the same change request with which
airline CO is processed.
Blocking an Entity with More than One Change Request
If an entity is blocked by more than one change request it is not possible to process the entity with any of the blocking
change requests. Example: You process airline CO in a change request, which creates a block for airline DL. At the same
time you process airline CX in another change request, which causes a block for airline DL as well. Now it is not possible
to process airline DL with any change request until one of the two change requests is nalized.
Blocking an Entity with an External Reason
If an entity is blocked due to an external reason, then it is not possible to process the entity in any change request until
the block is removed.
Processing an Entity in an Existing Change Requests Despite of New Blocks
Existing change requests can still be processed despite of new blocks. Example: You created a change request CR_A for
airline DL. Now a second change request CR_B is created for airline CO, which causes a block for airline DL. Still the
change request CR_A for DL can be processed. Note that this case can only occur, if blocks are created asymmetrically
like in use case 3.
Use
In the hierarchy view of the Collective Processing (USMD_ENTITY) Web Dynpro application, you can visualize and change the
structure of a hierarchy and the master data objects belonging to this hierarchy. You can also use this Web Dynpro application
to work on several master data objects in parallel if the list view is available.
5/19/2023
A hierarchy is tree-like structure consisting of hierarchy nodes that is identi ed by its hierarchy name. The hierarchy type
de nes which objects can be used as nodes.
Integration
The Collective Processing (USMD_ENTITY) Web Dynpro application integrates with other applications in the following ways:
You can start processing hierarchies from the results list of the Generic Search (USMD_SEARCH) Web Dynpro
application, if it is con gured for use with hierarchies. For more information, see Search Business Object.
You can open the Single-Object Processing (USMD_OVP_GEN) Web Dynpro application for individual business objects
displayed in the List View and in the Hierarchy view of the Collective Processing (USMD_ENTITY) Web Dynpro
application. For more information, see Single-Object Processing.
You can open the hierarchy in Office Open XML format by choosing Download from the Display As dropdown list. The
hierarchy is maintained in the output and you can use the features of the third-party app to view the data.
(Applicable for selected business objects in Master Data Governance for Custom Objects and Master Data Governance
for Financials only) You can assign individual business objects to hierarchies in the Hierarchy Assignment block of the
Single-Object Processing (USMD_OVP_GEN) Web Dynpro application. For more information, see Hierarchy Assignments
in Single-Object Processing.
 Note
After working with a hierarchy assignment, users must nalize the change request before the system allows them to
add, delete, remove, or change the hierarchy properties of other hierarchy nodes that have the same parent node.
You can upload and download hierarchies in the relevant applications. For more information, see the following:
File Upload (USMD_FILE_UPLOAD)
File Download (USMD_FILE_DOWNLOAD)
You can change multiple master data objects at the same time through integration with the Mass Change process.
When you change data in Collective Processing (USMD_ENTITY), the process of either creating a new change request or
assigning an existing change request to your changes is supported.
Prerequisites
A standard data model has been assigned to you. The data model can be derived from the settings of the PFCG role that
is assigned to your user.
The hierarchy type for the hierarchy you want to work with is con gured. For more information, see Con guring
Hierarchy Types
Features
This section describes how to work with hierarchies using the Collective Processing (USMD_ENTITY) Web Dynpro application.
Navigating the User Interface
Views
Collective processing offers the following views:
Hierarchy
5/19/2023
You can navigate to the structure of a hierarchy expanding or collapsing the levels in the hierarchy. The structural view of
the hierarchy is derived automatically from the master data objects con guration for descriptions and attributes. For
more information, see Con guring Hierarchy Types.
List View
In the list view, you can lter master data objects and print or download a list of objects.
Download
When you choose Download, the current view selection will remain and a download will be triggered.
Searching in Hierarchies
The Find in Hierarchy eld allows you to search for a string in a hierarchy. Hits are highlighted on the screen. You can navigate
between hits by choosing Next Hit and Previous Hit. You can also choose Find All and then select the relevant hierarchy node
from a dialog box. The search considers the following elds:
Hierarchy IDs, descriptions, and attributes
Hierarchy attribute and description
Switching Between Active and Inactive Versions
If applicable, you can switch between the active and inactive versions of the hierarchy structure and master data objects.
Pending Change Requests
The Pending Change Request column indicates when a hierarchy node is interlocked with a pending change request and allows
you to access the relevant pending change request. For more information, including graphics describing how interlocking works,
see Scope for Hierarchy-Speci c Changes.
Change Documents
You can access the history of changes to a parent node in a hierarchy from the Changes column. The context-sensitive change
document UI describes changes to nodes associated with a particular parent node. Moved nodes display below their new parent
node (status: New ) as well as below their old parent node (status: Deleted).
The following statuses are possible:
Deleted: This status can mean deleted entirely or moved to another parent node.
New: This status can mean inserted for the rst time or moved from another parent node.
Changed: Changes have taken place to hierarchy attributes or to hierarchy positioning (for example, repositioning of a
node from position 3 to position 4 after a node was inserted.)
You can lter change documents to only include nodes with a status of New or Deleted, (in other words not Changed) you can
use the following lter on the Status column: !Changed . This makes it easier to identify which nodes have been moved.
New Selection
You can navigate between different instances of the hierarchy by choosing the New Selection button and specifying an
appropriate key. For example, you can choose a different validity timeframe or a different version.
Number of Expanded Nodes
5/19/2023
To optimize performance, the user parameter MDG_HRYUI_NODE_LIMIT limits the number of expanded nodes shown on the
user interface. You can click the ... symbol to show all nodes.
Changing Hierarchies
Hierarchy changes are distinct from changes to the business objects represented in the hierarchy. They involve working with
hierarchy nodes.
Creating Hierarchies or Hierarchy Versions
If applicable for the hierarchy type in process, you can create a new hierarchy selecting Insert Create New Hierarchy .
If applicable for the hierarchy type in process, you can create a new hierarchy version selecting Related Services Copy
Hierarchy Version
Inserting Hierarchy Nodes
To insert single objects or several objects as hierarchy nodes in one step, choose Insert. Here you can also locate objects that
are not yet assigned to the hierarchy using the Not Assigned option. Depending on the hierarchy type you can form hierarchies
as nets: One node can have several higher-level nodes.
The following insert options are available:
With the Insert <Business Object> option, you can insert single objects or several objects in one step. From the
popup that displays, you can accomplish the following:
Enter the names of the business objects you want to insert:
Upload an excel le of hierarchy nodes (so long as the inserted nodes have no subnodes)
With the Insert <Business Object (Unassigned)> option, you can also locate objects that are not yet assigned to the
hierarchy. The popup menu includes column Fragment Subnode. Fragments are structures that are created when their
root nodes are removed from hierarchies.
 Note
The fragment subnode and its lower-level nodes may be accidentally duplicated if, after the assignment of a fragment
subnode to a hierarchy, a node at a higher level in the fragment is assigned to the hierarchy. In this situation, the
fragment subnode and its lower-level nodes disappear from the Insert <Business Object (Unassigned)> popup. The
abovementioned nodes are now assigned. They are not however removed from the fragment. The complete structure
is no longer visible in the Insert popup, but it continues to exist.
Deleting or Removing Hierarchy Nodes
You can remove objects represented as hierarchy nodes by selecting Edit Remove . You can start a deletion process to
remove hierarchy objects from the hierarchy and to delete the objects selecting Edit Delete .
Moving Hierarchy Nodes
To move objects that are represented as hierarchy nodes, use the arrow buttons, the drag and drop function, or the cut and
paste function selecting Edit Cut and then Edit Paste . You can move several objects at once using either drag and
drop or cut and paste.
De ning Hierarchy Attributes and Hierarchy Ranges
You can change hierarchy attributes and permitted ranges with the context menu using right-click. Ranges can be expanded at
any time to see which entities currently fall into the range.
5/19/2023
You can change hierarchy attributes and permitted ranges with the context menu using right-click. Ranges can be expanded at
any time to see which entities currently fall into the range.
Changing or Creating Master Data
To change single objects, select the object key which is displayed as a hyperlink. To change more than one object a time, select
several objects of the same type and choose Mass Change. To create objects, choose New and insert these new objects into the
hierarchy in a later step.
Saving Hierarchy Changes and Assigning Changes to Change Requests
Changes to hierarchies are captured in change requests. Change request processing is integrated with the hierarchy processing
user interface.
Save Button
You save changes to the hierarchy to change requests. What happens after you choose the Save button depends on the
following:
Icon in Pending Change Requests column
The affected node is interlocked with a pending change request. The system assigns the change to the relevant pending
change request.
For each hierarchy type, either strict or loose interlocking is implemented. Strict interlocking interlocks nodes at all levels
of the hierarchy. Loose interlocking only interlocks nodes directly below the parent node of the node being changed.
For more information about interlocking, see Scope for Hierarchy-Speci c Changes.
No icon in Pending Change Requests column
The affected node is not interlocked with a pending change request. A popup allows you to create a change request, or
assign the change to an existing change request. As soon as this change request is created, related nodes are
interlocked with the pending change request.
Add to Change Request
Allows you to assign a business object, which is represented as a hierarchy node, to a pending change request. For example,
after moving an airline to a different airline alliance, you can select the hierarchy node that represent the airline, and assign it
to a pending change request. You can then use the assigned change request to change the contact person for the airline. This
ensures that structural changes are grouped with content changes in the same change request.
More Information
For a high-level description of the considerations involved in processing hierarchies, see Processing Hierarchies
For a process description of how you can structure and restructure hierarchies in the Collective Processing
(USMD_ENTITY) WebDynpro application, see Hierarchy Assignment in Collective Processing.
Hierarchy Assignments in Collective Processing
Use
In the hierarchy view of the Collective Processing (USMD-ENTITY) Web Dynpro application, you can visualize and change the
structure of a hierarchy and the master data objects belonging to the hierarchy. The requestor requests changes and the
5/19/2023
approver approves changes.
Process
Requestor
1. Open the hierarchy and search for the relevant part of the hierarchy.
a. You can open the Hierarchy View of the Collective Processing WebDynpro application in the following ways:
In the Collective Processing (USMD_ENTITY) WebDynpro application, specify the relevant elds for the
hierarchy, and choose the Hiearchy View.
In the Generic Search (USMD_SEARCH) WebDynpro application, search for a business object that is
represented as a node in the hierarchy, select the relevant row from the results list, and choose the
Hierarchy Processing pushbutton. For more information, see Search Business Object.
b. If you opened the Collective Processing (USMD_ENTITY) application directly, search for the relevant part of the
hierarchy. If you opened the application from the Generic Search (USMD_SEARCH) application, the correct part of
the hierarchy is already highlighted.
2. Restructure the hierarchy by inserting and removing nodes where necessary.
3. Save your changes to a new change request or to an existing change request.
The status of the change request changes to Final Check to be Performed.
The graphic below illustrates the process.
5/19/2023
Hierarchy Processing in Collective Processing (USMD_ENTITY) - Requestor
Approver
1. Open the change request for a hierarchy change.
2. Review the details of the changed nodes.
a. Reference the change request header to identify who changed which node when.
b. Open the changed nodes in the context of the hierarchy.
3. Approve or reject changes. The status of the change request changes to Final Check Approved or Final Check Rejected.
5/19/2023
Mass Change
Use
You can use this Web Dynpro application (USMD_MASS_CHANGE) to change individual master data items to a common value
for multiple selected entities of an entity type.
You can set the Initialize indicator to delete the values for the selected attribute from the database for all entities, for example,
when an attribute is no longer relevant for an entity and the values for it should no longer be displayed.
 Caution
This Web Dynpro application only supports changes to attributes of entities with storage and use type 1. Attributes of
entities with storage and use type 4 can be used to restrict the selection for mass change. If there is a 1:1–relationship
between the entity with storage and use type 1 and the dependent entity with storage and use type 4, attributes of the
entity with storage and use type 4 can be changed as well. You can restrict the availability of attributes in this Web Dynpro
application using the Customizing activity De ne Field Properties for UI under General Settings UI Modeling .
Prerequisites
A standard data model has been assigned to you. If a standard data model has not been assigned to you by means of the user
master record, you must assign a data model in this Web Dynpro application by choosing Change Model.
5/19/2023
Activities
You can run this Web Dynpro application with the following services:
Directly using the service Mass Change in the Change Requests workset
Within Collective Processing for all search results you have selected
Within the iView Processing Change Requests for all objects you have selected
Multiple-Record Processing
Use
The Multiple-Record Processing service enables you to create, edit, or delete a number of master data records at the same
time. The service is recommended for small numbers of records and should not be considered a replacement for the Mass
Change service.
Multiple-Record Processing offers a streamlined process, with a UI that enables you to create change requests for multiple
records with greater efficiency.
Features
The Multiple-Record Processing function enables you to use the following features:
Streamlined Processing
Multiple records can be updated without creating a separate mass change request before beginning processing. The
service can be accessed directly from the search function.
Entity Pre-Selection
A Multiple-Record Processing change request automatically includes entities from the related data model, thereby
speeding up the creating process. Depending on the MDG application you are using, BC sets may be available with pre-
con gured scenarios for your entities.
UI Options
The Multiple-Record Processing UI enables you to use a Find and Replace feature, to copy data to selected rows, and to
highlight rows with identical values.
Highlight Changes
The Multiple-Record Processing UI highlights changes of master data records in the change request process. This helps
you to nd particular changes on the change request UI telling you what you need to check and approve. For more
information, see Highlight Changes.
Multiple-record processing can be used for the following MDG applications:
Master Data Governance for Custom Objects
Master Data Governance for Material
Master Data Governance for Supplier
Master Data Governance for Customer
5/19/2023
Change Documents
Use
If you change master data in Master Data Governance, your changes are documented in change documents. You use this Web
Dynpro application (USMD_CHANGE_DOCUMENT) to display change documents in order to check who changed particular data
and when, what application was used, and what the old and new values are.
The system writes change documents of type USMD during the processing of a change request. These change documents record
the changes of the users in each processing step. During the activation of the change request, MDG writes change documents
of type USMD_ACT and displays the last change that the system has written to the active area. If a reuse active area is used, the
system can write additional change documents depending on the interfaces and the Customizing settings of the reuse active
area.
Prerequisites
You have successfully made master data changes with one of the following functions:
Single Processing
Mass Change
File Upload
Features
If you want to display the change documents written during activation (USMD_ACT) then select Include Change Documents of
Activation.
If you want to display the change documents written by the reuse active area then select Include Change Documents of Active
Area.
You can call single processing from the values displayed.
If you call the application from iView Processing a Change Request (USMD_CREQUEST_PROCESS), then all of the change
documents are displayed in the results list that have already been created for the change request selected in the iView.
If you call the application from iView Single Processing , then all of the change documents are displayed in the results list that
have already been created for the object selected in the iView.
Activities
To select the change documents, enter the required selection criteria.
The system activates the execution in the background, using a technical user with the ID SAP_WFRT. MDG writes the change
documents of the activation (USMD_ACT) with the user ID of the work ow container variable RELEASED_BY. The work ow
assigns the ID of the user who has approved the change request to the container variable RELEASED_BY. This user is also used
in the change documents of the reuse active area if this is supported by the MDG application. This is supported by SAP Master
Data Governance for Material.
 Note
5/19/2023
For time and date, you can only enter single values or intervals, not single value lists. If you leave the value for the end of the
interval open, the system automatically sets this value to either the current date or the time 23:59:59.
If you want to switch between the display of attribute changes and hierarchy changes, then in the results list in drop-down box
Display choose the required display.
Where-Used List
Use
You use this Web Dynpro application (USMD_WHERE_USED) to display the entities that use a speci c entity type. This allows you
to determine, for example, the hierarchies in which entities are used.
Prerequisites
If the entity type requires editions, you have created edition types in Customizing for Master Data Governance under
General Settings Process Modeling Create Edition Type .
Features
You can specify the entity type for which the where-used list is created. When you do so, you can restrict the where-used list to
speci c entities or editions of the entity type.
The results list contains all of the entities that use the entity type you speci ed. You can add a description of the entities to the
information shown in the list.
For certain entities in the results list, you can call single processing by clicking the entity.
Activities
application in the Financial Master Data Governance work center as follows:
Using the Where-Used List service in the Change Requests workset
From the Single Processing iView, for example, by choosing Related Links
Remote Where-Used List
Use
You use this Web Dynpro application (USMD_REMOTE_WHERE_USED) to check existing entity usage in a remote system. You
can check the nancial con guration of default entity type Account, and which con guration is used. This makes dependencies in
the remote system transparent. The entity type Account is created using the BAdI implementation
USMD_REMOTE_WHERE_USED.There are several implementation options available, for example, the default implementation
using the remote function call module TABLE_ENTRIES_GET_VIA_RFC, Operational Data Providers (ODP), and SAP
NetWeaver Enterprise Search. You can also perform your own BAdI implementation. For more information about setting up the
5/19/2023
BAdI implementation, see Customizing for Master Data Governance under General Settings Data Quality and Search
Business Add-Ins BAdI: Remote Where-Used List .
Prerequisites
You have con gured the remote system in Customizing for Data Replication under De ne Custom Settings for Data
Replication De ne Technical Settings De ne Technical Settings for Business Systems and set the RFC destination
column.
 Note
Only the systems con gured with the RFC destination column value will be considered by remote where-used list.
Features
You can specify the entity type for which the where-used list is created. When you do so, you can restrict the where-used list to
speci c entities or editions of the entity type. The results list contains all of the entities that use the entity type you speci ed.
This is a read-only list.
Activities
1. Select an entity type.
2. Select a chart of accounts and the business system you want to display the results in.
Duplicate Check
Use
This function validates data that you input, and allows you to control the creation of duplicate data records. When you input
data to create a new change request, the system compares the data you’ve entered with data already in the system. If the data
you've entered matches one or more existing records, the system warns you that you’re about to create a duplicate. For
example, if you’re entering a new business partner, you enter the name and address. The system rst compares the data from
these elds with existing business partner records in the database. The duplicate check identi es any records that are potential
duplicates of the record you’re creating. Each potential duplicate is given a score to indicate the probability of it being a
duplicate of the new record. You can choose to proceed with creating the new record or, if you agree that by continuing, you
would create a duplicate, you can begin to work directly with the existing record – effectively canceling the creation of a new
record.
 Note
In the standard, the duplicate check is performed on active data only. This is because data in the staging area is not yet
complete and could change during the change request process, which would lead to a high number of “false positive”
matches during the duplicate check.
In business, it’s sometimes necessary to create duplicate data. For example, a bank customer could have a personal account
and a commercial account, for which the data would include common elements.
Prerequisites
5/19/2023
You’ve con gured the match pro le in Customizing for Master Data Governance under General Settings Data
Quality and Search Search and Duplicate Check De ne Search Applications .
You've con gured the duplicate check, in Customizing for Master Data Governance under General Settings Data
Quality and Search Search and Duplicate Check Con gure Duplicate Check for Entity Types .
You’ve con gured the properties of the duplicate check, in Customizing for Master Data Governance under General
Settings Process Modeling Change Requests Con gure Properties of Change Request Step .
Features
Match Pro le
You can specify a match pro le to control which attributes the system compares to identify duplicates. For example, to compare
name and address details, you can specify that the system considers the name elds, house number, street, city, postcode, and
country or region of each record. You can specify that a eld is mandatory for duplicate check. During a duplicate check, all elds
that you specify as mandatory must contain a value to perform the check. If you’re using search mode HA (SAP HANA-based
search), you can also assign a relative weight to each eld indicating the importance of that eld in identifying duplicates. The
system can then prioritize certain attributes for the purposes of the comparison. When the system has completed a duplicate
check, it displays a score for each found potential duplicate. This score is calculated based on the relative weights and indicates
the probability that the new record is a duplicate. For example, two addresses with identical postcodes could be considered
more likely to be duplicates than two addresses in which only the values for country or region are identical.
You can de ne the sequence in which the system displays attributes compared for the duplicate check in the Sequence column.
To do this, you enter a number for each attribute, indicating its position in the order, for example 1 indicates that an attribute is
the rst to be displayed (after the entity key attributes), 2 indicates the second and so on. If you don’t want to de ne a
sequence, you can enter the same value – 1 – for each attribute. In case the sequence number is empty, the attribute is only
considered for the score calculation but not displayed.
You can create one of more match pro les per data model and entity type. To create match pro les, go to the Match Pro le
view in Customizing Master Data Governance, Central Governance General Settings Data Quality and Search Search
and Duplicate Check De ne Search Applications . At any point in time, only one match pro le can be active per data model
and entity type. Customizing Master Data Governance, Central Governance General Settings Data Quality and Search
Search and Duplicate Check Con gure Duplicate Check for Entity Types .
Low and High Thresholds
For search mode HA (SAP HANA-based search), you can specify a low and high threshold for duplicate scores. The system
deems as potential duplicates only those records with a score within these thresholds. Only such potential duplicates are
displayed to the user.
The low threshold speci es the minimum matching score that a record must achieve in order for the system to consider it as a
potential duplicate. The system excludes records with a lower matching score from consideration as duplicates.
The high threshold speci es the maximum matching score that a record must achieve for the system to consider it a potential
duplicate. The system excludes records with a higher matching score from consideration, as they are deemed to be identical
and therefore not potential duplicates.
Note that both thresholds are not relevant for database search or remote key search.
The low and high thresholds can be de ned in Customizing for Master Data Governance under General Settings Data
Quality and Search Search and Duplicate Check Con gure Duplicate Check for Entity Types .
Field Weight
5/19/2023
In the Relevant Fields view, you can assign a relative weight to a eld indicating the importance of that eld in identifying
duplicates so that the system can prioritize certain attributes for the purposes of the comparison.
Note that the weight is only relevant for SAP HANA-based search.
Example: You could assign a lower value to the City eld, and a relatively higher value to a Postcode eld so that the system
considers two addresses with identical postcodes as more likely to be duplicates than two addresses in which the values for city
are identical.
Fuzziness Threshold
In the Relevant Fields view, you can specify the fuzziness threshold that will be applied to an attribute during matching. The
higher the threshold, the more the attribute value needs to match the reference value to be found during a search or duplicate
check.
Examples: 0.7 (Recommended and the default) and 1.0 (Exact search).
Perform Duplicate Check on Demand
When a duplicate check is con gured in the Enhancements and Checks per Change Request Step view, the Duplicate Check
button is displayed on the UI. The Duplicate Check button enables you to perform a duplicate check on demand, independent of
whether it has already been performed or if the data has changed.
Layout for Found Potential Duplicates When Using Match Pro le-Based UI
The match pro le-based UI is used when the ag in the MPbased UI (UI Based on Match Pro le ID) column is selected for the
respective data model and entity type in Customizing for Master Data Governance, Central Governance under General
Settings Data Quality and Search Search and Duplicate Check Con gure Duplicate Check for Entity Types . When this
value is not selected, the standard layout is used for displaying the found potential duplicates.
In case of a match pro le-based UI, the columns of the Potential Duplicates Found table are determined as follows:
Visibility of attributes
Except for key attributes which are always visible, only attributes which are de ned in the match pro le in Customizing
for Master Data Governance under General Settings Data Quality and Search Search and Duplicate Check
De ne Search Applications , view Relevant Fields, column Resolve Attribute for Duplicate Check.
The sequence number (column Sequence for Duplicate Check Attribute) must be lled. For the visualization, this
number determines the column ordering in the table. Attributes with sequence number initial are not displayed.
Example
The following is an example match pro le, the visibility per attribute is as follows:
Entity Type Resolved Weight Fuzziness Mandatory Sequence Excluded Visible

Attribute for Attribute
Duplicate From Search
Check
AD_POSTAL CITY1 Yes 2 Yes
AD_POSTAL HOUSE_NR1 1,00 3 Yes
AD_POSTAL POST_COD1 1,00 Yes 4 Yes
AD_POSTAL REF_POSTA 1,00 Yes 5 Yes
5/19/2023
Entity Type Resolved Weight Fuzziness Mandatory Sequence Excluded Visible

Attribute for Attribute
Duplicate From Search
Check
AD_POSTAL STREET 1,00 6 Yes
BP_CENTRL BU_SORT1 1,00 7 Yes No
BP_CENTRL BU_SORT2 1,00 Yes No
BP_CENTRL MCNAME1 1,00 Yes 1 Yes
In this example, search term 2 (BP_CENTRAL~BU_SORT2) is not displayed in the table of found potential duplicates. All
non-key attributes not de ned in the match pro le are also not be displayed.
Attribute's relevance for score calculation
All attributes de ned in a match pro le are considered for score calculation except for the ones marked as Ex. Attr
(Exclude Attribute from Search). If you want to display a certain attribute but don't want to include it in the score
calculation, select the Ex. Attr ag. In the example, attributes BP_CENTRAL~BU_SORT1/2 (search term 1 and search
term 2) are not considered for score calculation.
Special combination of properties: An empty sequence number combined with excluding an attribute from the search
If the sequence number of an attribute is empty, it will not be displayed as a column of table Potential Duplicates Found.
When also excluding this attribute from the search, it does not in uence the score calculation. Such an entry can be
deleted from the match pro le. The system behavior for such an attribute is the same as for all non-key attributes which
have not been de ned in the match pro le. In the example above attribute search term 2 (BP_CENTRAL~BU_SORT2) is
such a candidate.
Search
Use
Depending on your master data needs you may need to search for different types of master data objects. Master Data
Governance offers three different search providers:
Database Search
Database Search nds data in a database based on user-speci ed search criteria. Database Search can also be used in
applications such as duplicate check.
Enterprise Search
Enterprise Search supports free text search and fuzzy search . Unlike Database Search, Enterprise Search considers all
attributes of a data object, for example, if you enter a street name, Enterprise Search searches across all attributes and
returns all records containing the search string, regardless of attribute. To use fuzzy search you enable the fuzzy search
option on the UI. With fuzzy search enabled, the system normalizes input strings that differ by a few letters from an
index term making the search more error tolerant. Enterprise Search supports real-time indexing using change pointers.
Example of Enterprise Search
You enter a free text Heidelberg. No attributes are speci ed so the system searches all entries and returns
results for any attribute, for example any record that has Heidelberg as the city name or, as the street name.
With fuzzy search enabled, you enter Heidelburg. The system returns results for any attributes that are similar
to the text entered.
5/19/2023
Key Search
Key search is performed in a hub system allowing you to search for object by IDs across the system landscape, where the
object ID on the client system is not identical to the object ID on the hub. Given a client system master data object ID,
the Key Search returns the corresponding master data object on the hub.
SAP HANA-based Search
SAP HANA-based search enables you to perform searches based on user-speci ed search criteria. SAP HANA-based
Search can also be used to perform duplicate checks on master data residing in the SAP HANA database. As a
prerequisite you must con gure SAP HANA-based Search as described in SAP HANA-Based Search.
SAP HANA-based Search supports free style search and fuzzy search. For free style search, it considers all attributes of
a data object and returns all records containing the search string regardless of the attributes.
SAP HANA-based Search performs fuzzy search by default. With fuzzy search it returns records with data that differ by a
few letters along with a search rank or score that indicates the similarity of the searched data to the search term.
Example of SAP HANA Fuzzy Search
You enter a free text Heidelberg. You do not specify attributes so the system searches all entries and returns
results for any attribute, for example, any record that has a text similar to the search string Heidelberg along
with a search rank.
You enter a search text Heidelberg for the attribute City, the system returns results for any record with City
similar to the text entered, along with a search rank.
With the SAP HANA-based Search, you can retrieve the number of records which match the speci ed search criteria
instead of the matching entities.
Search Operators
The Search Operators available for a search are speci c to the attribute type. For example, when searching for a date you can
select from the search operators to nd dates that are “exactly, “prior to” or “after” the speci ed date. Whereas, a search for a
name can nd names that start with, end with, contain or are exactly equal to the search string.
Example
Database Search
You enter the name of a speci c rm in a speci c city on a speci c street and the search returns one result.
Key Search
Client System PTQ/810 contains Supplier master data with unique ID 200. During replication from hub system to client system,
this ID was mapped to the corresponding master data entry on the hub system, in this case ID 100.
From the client system, you perform a search, specifying object ID 200. This value is passed to the hub system. Based on the
mapping, the hub system identi es the corresponding hub system ID – in this case 100 – and returns the corresponding master
data to the client system.
Validation and Enrichment
Use
5/19/2023
When you enter data to create a new change request, the system validates and enriches the data, to ensure high data quality in
your system.
Validation
Validation is the process of checking data that a user enters and verifying that it is correct.
When you enter data to create a new change request, the system veri es the correctness of the data you have entered. If, for
example, you enter the city Heidelberg, the system checks that this is a valid city name, according to an external index. If you
enter an invalid value, the system warns that this is not a valid entry.
There are different types of validation such as data validation or mandatory check validation. The standard checks provided are
as follows:
Basic Check
Authorization Check
Duplicate Check
Validation Rules (BRF+)
Validation Rules (Data Quality)
BAdI Validations
Existence Check
Reuse Area Check
You can customize validations in master data governance. A user can decide which validations the system must run for a
particular change request step for a process. You can do this in Customizing for Master Data Governance under General
Settings Process Modeling Change Requests Con gure Properties of Change Request Step .
Enrichment
Enrichment can enhance the data you enter in the system. For example, if you enter data for a city, country/region and street,
the system can derive the postal code that applies for these values.
The basis of enrichment is the Enrichment Framework. This framework provides a platform for the integration of enrichment
tools that the MDG framework supports. The Enrichment Framework comprises the following basic components:
Enrichment feeder
An ABAP class that converts data from Master Data Governance format into a format that is readable for the external
or internal service. It also converts in the opposite direction so that the enriched data from the external or internal
service can be saved to Master Data Governance.
Enrichment adapter
An ABAP class that connects with the external data or internal data. The enrichment adapter receives converted Master
Data Governance data from the enrichment feeder, and then makes the external service call or internal service call for
enriching the data.
Enrichment spot
One or more elements of a data model (entity type or attribute) that are grouped together for the purpose of data
enrichment. Each enrichment spot is supplied with external data by one or more enrichment adapters. Before external
data can be read at the enrichment spot, an enrichment feeder must translate it into a Master Data Governance format.
5/19/2023
Prerequisites
You have completed Customizing for Master Data Governance under General Settings Process Modeling Change
Requests Con gure Properties of Change Request Step
You have completed Customizing for Master Data Governance under General Settings Data Quality and Search
Validations and Enrichments
Features
You can suppress particular check types at change request-step level. You can suppress checks for entity types and attributes.
Example
You want to enter an address for a new supplier. You begin by entering a street name, number, postcode, and country/region.
The system then compares the data from these elds with existing address records. If the system nds a similar record but, for
example, the postcode that you have entered differs from an existing address, you can update your entered data with this
validated address or proceed with the data that you have entered.
Change Requests
You can use this Web Dynpro application (USMD_EDITION_CREQUEST) to display all change requests. From this Web Dynpro
application, you can process change requests and access single processing.
Using Editions to Schedule Changes
Use
In Master Data Governance, editions provide the mechanism for you to schedule changes to business objects and hierarchies. In
areas such as nancial accounting, you must plan certain changes, enter them into the system in advance, and make the
changes active at a precise date or period.
The Master Data Governance system has standard business objects and edition-based business objects. Changes to a standard
business object apply immediately and cannot be scheduled for a particular date or period. In contrast, you can schedule a
change to an edition-based business object by assigning an edition to a change request. The system creates a new instance of
the business object, which is a copy of the existing instance. The changes you apply to the new instance of the business object
are valid from the valid-from date or valid-from period of the edition assigned to the change request.
To ensure business object data or hierarchy data is inherited into the future when no changes are made, all editions are valid
until the end of time.
5/19/2023
Edition E1 is valid from 01 2014 until the end of time; Edition E2 is valid from 02 2014 until the end of time.
The instances of the business objects or hierarchies to which you schedule changes using editions have consecutive timeframes.
There is one instance of Account A, which is created in edition E1 and is never changed. There are two instances of Account B which is created in
01 2014 and changed in 02 2014.
5/19/2023
When you search for an account that has changed on different occasions, the Generic Search (USMD_SEARCH) returns multiple
instances of the account. Each instance has a validity timeframe, which consists of the following elements:
The valid-from date or valid-from period of the scheduled change (inherited from the edition to which the change was
assigned.)
The valid-to date or valid-to period of the scheduled change (one day or one period before the next occasion in which the
business object is changed.)
For more information about the search, see Search Business Object.
 Note
You cannot use edition-based entities together with parallel change requests.
 Note
You access hierarchies through Collective Processing rather than through the Generic Search (USMD_SEARCH).
Prerequisites
To be able to select an edition when submitting a change request for a business object or for a hierarchy, and thereby assign a
validity timeframe to the changed object, you must ensure the following:
You have nalized all change requests for the business object within all other validity timeframes.
A master data steward has created an edition with the following attributes:
The valid-from date or valid-from period suits your requirements.
The edition type is compatible with the business object type.
The edition is in process. If a suitable edition is released, a master data steward must create a new edition with
the same valid-from date or valid-from period.
Features
You can create and schedule changes to business objects and to hierarchies. You can also reschedule changes by moving change
requests from one edition to another.
Create and Schedule Changes
After creating business objects or hierarchies, you can schedule changes to the objects.
To make changes for an identical validity timeframe, you keep the edition assignment the same. To trigger changes on a later
date or period, you change the edition assignment. When you assign a new edition to the change request, the system creates a
new object instance with a new validity timeframe.
5/19/2023
Creating and Scheduling Changes to an Account
1. A master data steward creates editions E1 and E2. E1 is valid from 01 2014 until the end of time. E2 is valid from 02 2014
2. You create an account in edition E1 and nalize changes.
3. You schedule a change to the account in edition E2. An inactive instance of the account is now valid from 02 2014 until 04
9999. An active instance remains valid from 01 2014 until 04 9999
4. You nalize changes. The following instances of the account now exist:
An active instance with a valid-from period of 01 2014 and a valid-to period of 01 2014.
 Recommendation
We recommend that, where possible, you schedule changes in chronological order. Each scheduled change results in the
creation of a new copied instance of the business object or hierarchy. The creation of a new instance breaks the connection
with the previous instance. So, if you nalize changes to an account in Q1 before you start working with the same account in
Q2, all Q1 changes are carried forward. If, however, you introduce changes in Q1 after making changes in Q2, the system does
not carry your changes forward.
Business Object
5/19/2023
From the Search Business Object (USMD_SEARCH) user interface, you can create a business object and schedule changes to a
business object.
You can create an edition-based business object, by choosing the New button and assigning an edition with an appropriate valid-
from date or period to the change request.
You can schedule changes to a business object by editing the instance of the business object whose validity timeframe includes
the valid-from date (or period) of your intended change. Validity timeframes can span several editions.
Hierarchy
To create a hierarchy, you rst create a change request and you assign an edition to the change request. Next, in Collective
Processing, you choose a hierarchy and the edition you previously assigned to the change request. You then change the nodes in
the hierarchy. When you save your changes, you are prompted to select the correct change request assigned to the edition. To
schedule a change, you repeat the process with your desired edition.
Reschedule Changes
A master data steward can change a validity timeframe by moving a pending change request from one edition to another. One
use case for this is when you want to release an edition, but there are pending change requests that you must postpone.
 Example
The following are examples of how the ability to reschedule changes using editions can make your business run more
effectively:
A plan exists for two branches within an enterprise to consolidate their resources in the rst quarter of the year.
Several accountants process accounts in an edition for the rst quarter, based on the plan. The plan is postponed
until the second quarter. You reschedule the accounts by moving the change requests to the edition for the second
quarter.
You are not sure when a project is going to go live, but you want to work with the relevant business objects. The ability
to reschedule multiple changes to a later edition ensures you can start working immediately.
You can only reschedule a pending change request if no con icting approved or pending changes exist for the relevant business
object at any time between the valid-from date or valid-from period of the source edition and the valid-from date or valid-from
period of the target edition. This rule applies when moving change requests backwards and forwards in time (see graphic).
Rescheduling a Change Request for an Account by Moving it to Another Edition
Activities
5/19/2023
Creating and Scheduling Changes
Business Object
This activity is based on the graphic shown in Features: Creating and Scheduling Changes to an Account. The user interface is
different for hierarchies and business objects, but the process is applicable to both object types.
2. You create an account in edition E1, and nalize changes using the standard work ow. The account is active in the MDG
hub from 01 2014. When you search for the account, one instance exists.
3. You open the account instance for editing. When prompted to assign an edition to the change request, you choose
edition E2. The system creates a new inactive instance of the account that is valid from 02 2014 until the end of time. You
make changes and submit your changes. The nalized instance, created earlier continues to be valid from 01 2014 until
the end of time. When you search for the account by its account number, the search returns the following:
An active instance with a valid-from period of 01 2014 and a valid-to period of 04 9999. You can view the active
instance by clicking the link to the account.
An inactive instance with a valid-from period of 02 2014 and a valid-to period of 04 9999 . You can view the open
instance by choosing the icon in the Pending Change Requests column.
4. You nalize changes. Two active instances of the account now exist. The rst instance is valid from 01 2014 to 01 2014.
The second instance is valid from 02 2014 to the end of time.
Hierarchy
This activity is based on the graphic shown in Features: Creating and Scheduling Changes to an Account. The user interface is
different for hierarchies and business objects, but the process is applicable to both object types.
2. You create a change request and assign it to edition E1. In collective processing, you create a hierarchy, and nalize
changes using the standard work ow. The hierarchy is active in the MDG hub from 01 2014.
3. You create another change request and assign it to edition E2. In Collective Processing, you edit the hierarchy you
created earlier. The system creates a new inactive instance of the hierarchy that is valid from 02 2014 until the end of
time. You make changes and submit your changes. The following instances of the hierarchy now exist:
An inactive instance with a valid-from period of 02 2014 and a valid-to period of 04 9999.
4. You nalize the change request. Two active instances of the hierarchy now exist. The rst instance is valid from 01 2014
to 01 2014. The second instance is valid from 02 2014 to the end of time.
Rescheduling Changes to a Business Object
1. In the Edition Management work center, search for and select the edition in which change requests are pending.
2. Choose the Display Change Requests button.
3. Select the pending change requests that you want to reschedule, and choose the Reschedule button.
4. Select the target edition for the change requests.
5/19/2023
Processing of an Edition
Use
You can create and edit editions using the Edition (USMD_EDITION) Web Dynpro application, which you can call from the
Analysis of Editions application. Editions are used to enable you to schedule changes to business objects and hierarchies.
For more information about the Analysis of Editions application, see Analysis of Editions. For more information about the role of
editions in scheduling changes, see Using Editions to Schedule Changes,
 Recommendation
To help users who process change requests, we recommend that you create editions months or even years in advance, and
that you give editions intuitive names such as Finance Q1 2013.
Prerequisites
You have ensured the following:
You have the authorizations to use the Edition (USMD_EDITION) web application. The relevant role is Master Data
Steward.
For Financials, we recommend that you keep the edition-relevant Customizing for edition types and data models (all
entity types belong to the same edition type).
For Custom Objects, you have ensured the following:
The relevant edition types exist.
Path: Customizing for Master Data Governance, Central Governance under General Settings Process
Modeling Create Edition Type .
The relevant entity types have the correct settings for editions:
Path: Customizing for Master Data Governance, Central Governance under General Settings Data Modeling
Edit Data Model :
View: Entity Types:
You have ensured the following
The entity types are relevant for editions.
You have selected Edition in the Validity of Entity eld.
The tables in which the entity types are stored are MDG tables ( ex option).
You have ensured that the Active Area eld has a value of MDG or blank.
All interdependent entity types are assigned to the same Edition Type.
Features
General Settings
You can apply the following settings at any time: Description, Comment, and Edition Status.
Replication Timing
5/19/2023
You can only apply the Replication Timing setting before you assign change requests to an edition.
The settings are as follows:
Selected in Each Change Request
Require a user decision for each change request
Manually Started on Release of Edition
Require manual replication when the edition is released.
On Final Approval of Change Request
Replicate data when a change request is nally approved
Edition Status
You can change the status of an edition. The following statuses are available: Set in Progress, Mark for Release, and Released.
You can only release an edition if all of its change requests are nalized.
If it is not possible to nalize an edition because of open change requests, you can postpone the change requests by choosing
the Display Change Requests option in the Analysis of Editions, selecting the relevant change requests and choosing the
Reschedule button and then moving the change requests to a later edition.
 Recommendation
Consult with your business users before rescheduling changes.
After you release an edition, you cannot use it again. To reuse the valid-from date or period of a released edition, you must
create a new edition. After you create a new edition with the same validity as a previously released edition, you can access
information about changes made in the previously released edition in change documents but not in the business object search.
 Note
Change requests that contain a hierarchy cannot be rescheduled.
Activities
1. A master data steward creates an edition.
2. Users assign the edition to the business objects or hierarchies that they create or change. The standard process for
creating and approving change requests is followed.
For more information about change requests and the process, see Concept of Change Requests
For more information about how to change business object instances from the generic search (USMD_SEARCH),
see Using Editions to Schedule Changes
3. A master data steward replicates the business objects assigned to the edition, if the Replication Mode is not
Immediately on Release of Change Request or if users have not chosen to replicate data when given a choice. The
following replication options are available:
Users can replicate business objects individually from the search (for more information, see Search Business
Object)
The master data steward can replicate the data in a more granular way using the Distribution Monitor. For more
information, see Distribution Monitor.
5/19/2023
In cases where the target system does not support time dependency for the relevant business objects, schedule
the Replication from Edition-Dependent Source to Time-Independent Target (USMD_EDITION_REPLICATE)
report, on or shortly after the valid-from date or valid-from period of the changes. Running this report ensures the
timely replication of changes to edition-based business objects belonging to a data model .
Analysis of Editions
Use
You can use the Analysis of Editions application to search for, create, edit, monitor, and manage editions. You can use editions to
control the timing of changes to a business object or hierarchy and to determine when and how replication occurs
In MDG, there are standard business objects and edition-based business objects. Changes to standard business objects are
valid immediately. Changes to edition-based business objects are valid on the valid-from date or valid-from period of the edition
that you must assign to the relevant change request.
Features
The Edition (USMD_EDITION) web application has the following features:
Search
You can search for an edition by status, edition-type, valid-from date, valid-from period, created on, released on, and released
by.
View
You can view a range of edition attributes, such as the status, the number of open change requests, and the valid-from date or
period.
Create and Edit Editions
You can launch the Edition (USMD_EDITION) Web Dynpro application, to create and edit editions. From this application you can
apply a range of settings, including a Replication Mode which determines how objects that use editions are replicated. For a
description of all edition settings, and an explanation of the end-to-end process of creating, editing, releasing, and replicating
editions see Processing of an Edition
Delete
You can only delete editions in which no data has been changed.
Display Change Requests
You can display change requests for an edition, and then work with the change requests in the following ways:
Open change requests for editing
After you display change requests, you can open them for editing.
Reschedule change requests
You can reschedule change requests by moving open change requests from one edition to another, providing con icts do
not prevent the move. For more information, see Using Editions to Schedule Changes.
5/19/2023
Validate
You can validate the edition and view the validation log.
Change Status
You can change the status of an edition. The following statuses are available: Set in Progress, Mark for Release, and Released.
You can only release an edition if all of its change requests are nalized.
If it is not possible to nalize an edition because of open change requests, you can postpone the change requests by choosing
the Display Change Requests option in the Analysis of Editions, selecting the relevant change requests and choosing the
Reschedule button and then moving the change requests to a later edition.
 Recommendation
Consult with your business users before rescheduling changes.
After you release an edition, you cannot use it again. To reuse the valid-from date or period of a released edition, you must
create a new edition. After you create a new edition with the same validity as a previously released edition, you can access
information about changes made in the previously released edition in change documents but not in the business object search.
Export to Excel
You can export the search output to excel.
Print Version
You can create a print version of the results list as a PDF document.
Edition Comparison
Use
You can use the Edition Comparison (USMD_EDITION_COMPARE) Web Dynpro application to compare data between editions,
either for an entire data model or for speci c business objects represented as entity types in a data model. The comparison
helps you to identify the following:
Which elds of which business objects changed between the earlier edition and the later edition
The values of the changed elds in the earlier edition and in the later edition
The new elds added to business objects in the later edition
You can also use the Edition Comparison (USMD_EDITION_COMPARE) Web Dynpro application to compare the eld values of
business object types across two groups that contain these business object types (for example, you can compare the eld
values of accounts across two charts of accounts) in the same edition or in different editions.
If you would like to compare data between editions for hierarchy assignments, either for an entire data model or for speci c
business objects represented as entity types in a data model, see Edition Comparison for Hierarchy Assignments.
Prerequisites
master record, you must assign a data model in this Web Dynpro application by choosing the Change Model button.
5/19/2023
Features
Selection of Comparison Criteria
In addition to selecting two editions, you can optionally select a business object represented as an entity type. You can decide
whether you want to show changed data only in the results, or to show all elds.
 Example
You want to see the changes made to all accounts between January (Edition ACC_2014_01) and February (Edition
ACC_2014_02). You select edition ACC_2014_01 as Edition 1 and ACC_2014_02 as Edition 2, and choose an Entity Type of
Account.
You can also compare the eld values of entity types across two higher-level entity types (for example, accounts across two
charts of accounts) in the same edition or in different editions. To make such a comparison possible, the following elds are
added to the Selection Criteria: Higher Level Field 1 and Higher-Level Field 2.
 Example
To compare the account eld values between Chart of Accounts:: CoA - Germany and Chart of
AccountsCoA - International in the same Edition E1, you enter the following elds as selection criteria:
Entity Type: Account
Edition 1: E1
Edition 2: E1
Higher-Level Field 1: CoA - Germany
Higher-Level Field 2: CoA - International
Comparison of Field Values
After selecting comparison criteria, you can compare eld values on the MDG hub for speci c business objects at the valid-from
date of each of the compared editions. In the results list, the value that the master data has in edition 1 is displayed as Value 1
and the value that it has in edition 2 as Value 2.
 Example
You want to see the changes made to all accounts between January (Edition ACC_2014_01) and February (Edition
ACC_2014_02). You select edition ACC_2014_01 as Edition 1 and ACC_2014_02 as Edition 2, and choose an Entity Type of
Account. The following row illustrates a change to the person responsible for Account 1000 in February:
Account: 1000
Change: Changed
Attribute: Person Responsible
Value 1: Patrick Price
Value 2: Amanda Adams
Navigation to Instances of Business Objects (Entities)
You can display business object details by choosing the Display Detail button.
5/19/2023
Printing of Edition Comparison
You can print out the comparison of edition based data for business objects in PDF format.
Edition Comparison for Hierarchy Assignments
Use
You can use the Edition Comparison (USMD_EDITION_COMPARE) Web Dynpro application to compare data between editions
for hierarchy assignments, either for an entire data model or for speci c business objects represented as entity types in a data
model. You can compare the hierarchy structure for an entity type and the master data assignments to the hierarchy structure
in different editions.
For more information, see Edition Comparison.
Prerequisites
You must have activated the business function MDG_FOUNDATION_12, switch MDG_CC_2021_252186. For more information
about this business function, see Master Data Governance, Generic Functions 2021.
A standard data model has been assigned to you. If a standard data model hasn't been assigned to you by means of the user
master record, you must assign a data model in this Web Dynpro application by choosing the Change Model button. This data
model must have a hierarchy.
Feature
Selection of Comparison Criteria for Hierarchies
In addition to choosing two editions, choose one of the following precon gured entity types for the data model 0G or any entity
type that is con gured as a hierarchy in your relevant data model:
Cost Center Group
Cost Element Group
Consolidation Group
Fin. Reporting Structure Item
Item
Pro t Center Group
This entity type selection enables the option to select the Compare Hierarchies checkbox. When you select the Compare
Hierarchies checkbox, two things happen:
The Display Changes Only checkbox becomes unavailable.
The Higher-level Fields section is replaced by a Select Hierarchy for Comparison section. There is mandatory
information to be inputted here before you can continue.
 Example
You want to see the differences of a hierarchy structure and the relevant master data assignments over two editions.
5/19/2023
You enter the following elds as selection criteria:
Entity Type: Cost Center Group
Edition 1: IMM_DISTR
Edition 2: SEL_DISTR
Compare Hierarchies: selected
Controlling Area: 0001
Cost Center Hierarchy: CCH01
Comparison of Field Values
In the resulting screen, a collapsed tree-like display shows the status of the structure of and master data of each edition. You
can toggle the descriptions of the entity type using the Descriptions button. The Levels button allows you to quickly expand
hierarchy nodes in the tree to various levels or expand and collapse the entire tree.
The entity type, in this example a cost center group or a cost center, is a link and when chosen displays the master data.
The status of the editions is marked with icons and inconsistencies are propagated up the hierarchy. For example, an entity
missing in edition 1, and therefore only exists in edition 2, is marked with an x and a checkmark respectively. Each hierarchy node
above this inconsistency then shows a not equal sign in each edition column. Where there are no inconsistencies within a
hierarchy node, an equal sign is shown in each status edition column.
Number of Expanded Nodes
To optimize performance, the user parameter MDG_HRYUI_NODE_LIMIT limits the number of expanded nodes shown on the
user interface. You can click the ... symbol to show all nodes.
Edition History
Use
This Web Dynpro application (USMD_EDITION_HISTORY2) displays a graphical overview (as a bar chart) of the validity period
for the editions of a data model.
Prerequisites
master record, you must assign a data model in this Web Dynpro application by choosing Change Model.
Features
The edition history of the Web Dynpro application enables you to:
Call the edition history for a data model
Specify which editions are displayed in the edition history
Specify that editions with a certain entity are indicated accordingly in the edition history
5/19/2023
Call an overview of the change requests of an edition
Compare two editions
Activities
Proceed as follows in the Web Dynpro application:
1. Use the following elds to specify which editions and information are to be contained in the edition history:
a. Edition Type
This eld speci es whether the edition history contains only those editions of a speci c edition type. If you do not
complete this eld, the edition history contains all edition types.
b. Valid From/To
These elds specify whether the edition history contains only those editions that are valid within a speci c period.
 Note
The format in which you have to enter the period in these elds depends on the settings for the edition type.
If the edition type is date-based (that is, valid inde nitely as of a speci c date), enter the period in the format
DD.MM.YYYY.
If the edition type is based on posting periods (that is, valid inde nitely as of a speci c period), enter the
period in the format PP.YYYY.
c. Entity
Once you have restricted the edition type, the system displays additional elds in which you can specify the
corresponding entity more precisely. You can also use the entity elds to specify that editions containing speci c
entities are to be indicated accordingly in the edition history.
2. Choose Start to generate the edition history.
The edition history is displayed as a bar chart. A legend at the bottom of the screen explains the icons used within the
bar chart.
3. To display all change requests of a speci c edition, select the bar for the relevant edition in the bar chart. Choose Change
Requests of an Edition.
The Web Dynpro application Change Requests of an Edition launches.
4. To compare two editions of the same data model, select the bars for both editions in the bar chart (while pressing and
holding CTRL). Choose Edition Comparison.
The Web Dynpro application Edition Comparison launches.
Processing Hierarchies
Use
A hierarchy is a tree-like structure consisting of hierarchy nodes that is identi ed by its hierarchy name. The hierarchy type
de nes which objects can be used as nodes. The de nition of the hierarchy type also includes whether hierarchies are edition-
dependent, have versions, and are synchronized. Hierarchies allow you to structure related master data objects. They re ect
business logic – for example, an airline logically belongs to an airline alliance.
5/19/2023
The organization of consolidated, validated master data records in analytical hierarchies can help address business questions if
you integrate the data with analytical applications or spreadsheets. For example, you can use the information gathered in SAP
Master Data Governance to analyze revenue by airline alliance.
For more information on the con guration of hierarchies, see Con guring Hierarchy Types and Structure of the Data Model and
Database Tables.
Assignment of Business Objects to Hierarchies
You can assign business objects to hierarchies in the following ways
Create or remove the assignments of just one business object to one or more hierarchies in Single-Object Processing
(USMD_OVP_GEN)
For example, when you create or edit an airline in single-object processing, you can assign it to one or more airline
alliances in a hierarchy.
For more information about the hierarchy assignment block in single-object processing, see Single-Object Processing.
Visualize and work with hierarchy structures in Hierarchy Processing (USMD_ENTITY)
In this application, you can add, move, and remove hierarchy nodes. You can also change hierarchy node attributes.
For more information about the Hierarchy Processing user interface, see Collective Processing.
File Upload and Download
You can upload and download hierarchies using the following Web Dynpro applications:
File Upload (USMD_FILE_UPLOAD)
File Download (USMD_FILE_DOWNLOAD)
Validity Timeframes (Dependent on Con guration)
You can assign validity timeframes to hierarchies to make hierarchies time-dependent. You can use editions to schedule
changes that apply from the valid-from date of an edition. For more information, see Using Editions to Schedule Changes.
Version-Dependent Hierarchies (Dependent on Con guration)
Hierarchies can be version dependent. These versions can be copied to another version.
If the Airline Alliances - Regional hierarchy is version dependent, it can have a planning version and a current version. If it is not
version dependent it can only have one version (see gure below).
5/19/2023
Version-Dependent Hierarchy Type
Synchronized Hierarchies (Dependent on Con guration)
Certain subhierarchies are customized to be synchronized in all hierarchies they belong to. For more information, see
Con guring Hierarchy Types.
In the example below, you have con gured the Airline (CARR) hierarchy type to be synchronized. Airlines are the main building
block within airline alliances. As a result of airlines being synchronized across airline alliances, the addition of a new airline to
subhierarchy Alliances Regional EU Oyster Airline Alliance is mirrored in subhierarchy Alliances - Tiers Tier 1
Oyster Airline Alliance . If the hierarchy type Airline is not synchronized, no mirroring occurs (see gure below).
5/19/2023
Use as Hierarchy Type Setting With and Without Synchronization
To control the hierarchy's visualization, you can use the user parameter MDG_HRYUI_VISIB_ROWS. With this parameter, the
nuber of rows shown at once in the hierarchy processing is con gured. For more information, see SAP Note 3269637
Process
For a description of working with Hierarchies in the Collective Processing application, see Hierarchy Assignment in Collective
Processing.
For a description of working with Hierarchies in the Single-Object Processing application, see Hierarchy Assignments in Single-
Object Processing
Analysis of Change Requests
Use
You can use this function to analyze how effectively change requests are processed in your organization.
You can analyze change requests from the following perspectives:
Processing times
Statuses
5/19/2023
Change requests involving you
Prerequisites
You have completed the tasks required to ensure it is possible to analyze change requests in the system. For instructions, see
Enabling Detailed Analysis of Change Requests.
Features
Analysis of Processing Times
After you specify a priority and a time frame, you can nd out whether change requests across the organization are meeting or
violating target processing times. This information is available for the whole organization, for data models within the
organization, and for change request types within each data model. You can access statistical information in the list view and
graphical illustrations in the graphical view. In the Processing Time (List View), you can navigate to individual change requests
that are causing problems.
 Note
The target processing times can depend on service level agreements de ned in Customizing for priorities of change request
types, or on due dates speci ed when change requests are created. For instructions on how to set up a service level
agreement, see Enabling Detailed Analysis of Change Requests.
The table below shows additional technical information.
Screen Application Type Technical Name
Processing Time (List View) Web Dynpro MDG_MONITOR_CR_PROCESTIME
The same application is used for the Status

(List View) screen and Processing Time
(List View) screen.
Processing Time (Graphical View) Dashboard 0XC_MDG_MONITOR_CR
Analysis of Statuses
For any time frame or change request priority, you can get an overview of how many change requests are completed and
rejected, completed and accepted, and created. This information is available for the whole organization, for data models within
the organization, and for change request types within each data model. You can navigate to individual change requests that are
causing problems. You can also access a screen that shows the main reasons why change requests are being rejected.
The table below shows additional technical information.
Status (List View) Web Dynpro MDG_MONITOR_CR_PROCESTIME
The same application is used for the Status

(List View) screen and Processing Time
(List View) screen.
Rejection Reasons Web Dynpro MDG_ANLY_CR_REJ_REASON
Analysis of Change Requests Involving You
5/19/2023
You can view a graphical summary of the nature of your involvement in change requests involving you.
This information is available to you if you open a side panel in the My Change Requests screen
You can refer to the following documents:
For more information about the business context viewer, see Business Context Viewer (BCV).
For more information about side panels, see Side Panel
My Change Requests (Side Panel) Web Dynpro USMD_EDITION_CREQUEST
Track My Requests
Use
With this app you can display all of your master data requests. The number of requests and the status of each request is also
displayed.
Key Features
Use a lean UI for tracking the requests created by the user
View the number of requests over a set time period. You can customize the time period of the number of requests
displayed, for example, 15 requests in last 30 days; 6 requests in last 7 days.
See requests broken into 3 categories – in process, approved, and rejected.
Take the option to lter requests by master data type, for example, all customer requests
Personalize your view, for example, add or remove columns

Desktop
Tablet
Smartphone

SAP_MDG_BC_REQUESTOR_T
Analysis of Change Requests (BI Content)

The following documents contain the information needed to work with BI content. The documents provide business and
technical information covering data sources, queries, search and analytics models, and dashboards.
5/19/2023
Queries
The following documents contain information on BI queries. The documents explain the business uses of the queries and provide
the structure of the queries as well as listing their lters, rows, and columns.
Change Request Weekly Analysis

0MDG_CR_T01_Q0001
Use
This query provides a weekly breakdown of the punctuality of change request processing.
A change request is late if it exceeds its due date or if it violates a Service Level Agreement (SLA). The due date is an optional
eld of the change request. You can de ne the SLA in Customizing for priorities of change request types. If no due date is
de ned and no SLA is de ned, no Key Performance Indicator (KPI) exists to measure whether change requests are on time or
late.
 Note
You can de ne an SLA for a particular priority of a change request type in Customizing for Master Data Governance under
General Settings Process Modeling Change Requests Create Change Request Type .
This query is run when a user selects a weekly time scale in one of the following screens:
The Change Request: Processing Time screen, which uses the (MDG_MONITOR_CR_PROCESTIME) WebDynpro
application.
The Change Request: Status screen, which also uses the (MDG_MONITOR_CR_PROCESTIME) WebDynpro application.
The Change Request: Processing Time dashboard.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calculation
Characteristic CR Created Week 2O0MDG_CR_T01- –

CREATED_WEEK
Characteristic Change Request Priority 2O0MDG_CR_PRIO –
Characteristic Change Request Type 2O0MDG_CR_TYPE –
Rows
Characteristic CR Created Week 2O0MDG_CR_T01- —

CREATED_WEEK
Columns
5/19/2023
Formula Total Amount of Change TOT_CRQ —

Requests
Formula Late: Due Date Exceeded CR_DD_VIOL —
Formula Late: SLA Violation CR_SLA_VIOL —
Formula On Time N/A —
Formula No KPI De ned N/A —
Key Figure Final - Rejected 20-REJECTED-INT4 —
Key Figure Final - Approved 20-APPROVED-INT4 —
Key Figure Check Whether the CR Violated 20-DD-VIOLATED-INT4 —

the Due Date
Key Figure Check Whether the CR Violated 20-SLA-VIOLATED-INT4 —

the SLA
Key Figure Total CR On Time 20-TOTAL_ON_TIM-INT4 —
Key Figure SLA or Due Date is not 20-OTHERS-INT4 —

Maintained
Change Request Monthly Analysis

0MDG_CR_T01_Q0002
Use
This query provides a monthly breakdown of the punctuality of change request processing.
late.
 Note
This query is run when a user selects a monthly time scale in one of the following screens:
application.
Structure
5/19/2023
Filters
Characteristic CR Created Month 200MDG_CR_T01- –

CREATED_MONT
Rows
Characteristic CR Created Month 200MDG_CR_T01- —

CREATED_MONT
Columns

Requests

the Due Date

the SLA

Maintained
Change Request Quarterly Analysis

0MDG_CR_T01_Q0003
Use
This query provides a quarterly breakdown of the punctuality of change request processing.
late.
5/19/2023
 Note
This query is run when a user selects a quarterly time scale in one of the following screens:
application.
Structure
Filters
Characteristic CR Created Quarter 2O0MDG_CR_T01- –

CREATED_QUAR
Rows
Characteristic CR Created Quarter 200MDG_CR_T01- —

CREATED_QUAR
Columns

Requests

the Due Date

the SLA
5/19/2023

Maintained
Change Request Yearly Analysis

0MDG_CR_T01_Q0004
Use
This query provides a yearly breakdown of the punctuality of change request processing.
late.
 Note
This query is run when a user selects a yearly time scale in one of the following screens:
application.
Structure
Filters
Characteristic CR Created Year 2O0MDG_CR_T01- –

CREATED_YEAR
Rows
Characteristic CR Created Year 200MDG_CR_T01- —

CREATED_YEAR
Columns
5/19/2023

Requests

the Due Date

the SLA

Maintained
Monitoring CR Processing Time

0MDG_CR_T01_Q0005
Use
You use this query to retrieve the details of the processing times for change requests that are late because they exceeded a
due date, for change requests that are late because they violated a Service Level Agreement (SLA), and for change requests
that are on time.
This query is run in the following circumstances:
When you choose the Show Details pushbutton in the Change Request: Processing
Time(MDG_MONITOR_CR_PROCESTIME) Web Dynpro application.
In the Change Request Processing Time (0XC_MDG_MONITOR_CR) dashboard.
Structure
Filters
Characteristic Data Model 2O0MDG_DM -
Characteristic CR Created Week 2O0MDG_CR_T01- -

CREATED_WEEK
Characteristic CR Created Month 2O0MDG_CR_T01- -

CREATED_MONT
5/19/2023
Characteristic CR Created Quarter 2O0MDG_CR_T01- -

CREATED_QUAR
Characteristic CR Created Year 2O0MDG_CR_T01- -

CREATED_YEAR
Characteristic Change Request Priority 2O0MDG_CR_PRIO -
Characteristic Change Request Type 2O0MDG_CR_TYPE -
Rows
Characteristic Data Model 2O0MDG_DM —
Characteristic Change Request Priority 2O0MDG_CR_PRIO —
Characteristic Change Request Type 2O0MDG_CR_TYPE —
Columns
Formula SLA Days — —
Formula Late: Due Date Exceeded CR_DDVIOLATED —
Formula Late: SLA Violation CR_SLAVIOLATED —
Formula On Time CR_ONTIME —
Key Figure No KPI De ned CR_NOKPI —
Formula Total Amount CR_TOTAL —
Key Figure Check Whether the CR Violated 20-DD_VIOLATED-INT4 —

the Due Date
Key Figure Check Whether the CR Has 20-SLA_VIOLATED-INT4 —

Violated the SLA
Key Figure Check Whether the CR Is On 20-TOTAL_ON_TIME-INT4 —

Time
Formula Average Processing Time —
Key Figure Processing Time 20-CR_PRO_TIME-DEC —

Maintained
Formula Total CRs with SLA — —
Key Figure SLA in Days 20-SLA_IN_DAYS-DEC —
Key Figure Check Whether the CR With SLA 20-SLA_ON_TIME-DEC —

Is On Time
Monitor Statuses of Change Requests by Data Model and CR

Type
5/19/2023
0MDG_CR_T01_Q0006
Use
You use this query to retrieve detailed summaries of the statuses of change requests broken down by data model and change
request type.
The output of this query is shown after the user chooses the Show Details button in the Change Request: Status screen. Both
screens use the Change Request: Processing Time (MDG_MONITOR_CR_PROCESTIME) Web Dynpro application.
Structure
Filters

CREATED_WEEK

CREATED_MONT

CREATED_QUAR

CREATED_YEAR
Rows
Columns
Key Figure Final Rejected 20-REJECTED-INT4 —
Formula Created - —

the Due Date

Violated the SLA
Key Figure Check Whether the CR Is On 20-TOTAL_ON_TIM-INT4 —

Time
5/19/2023

Maintained
Monitoring CR Processing Time for Change Requests

QR_0MDG_CR_T01_Q0007
Use
You use this query to retrieve processing time information pertaining to individual change requests belonging to a change
request type within a data model. The system runs the query after you complete the following steps in the Processing Time
(List View) screen:
1. Choose the Show Details pushbutton
The screen displays details of the processing times of change requests broken down by change request type within data
model.
2. Click a hyperlinked cell entry representing a number of change requests.
The Processing Time (List View) screen uses the :Change Request Processing Time (MDG_MONITOR_CR_PROCESTIME) Web
Dynpro application.
Structure
Filters

CREATED_WEEK

CREATED_MONT

CREATED_QUAR

CREATED_YEAR
Rows
5/19/2023
Characteristic Change Request 2O0MDG_CR_T01- —

USMD_CREQUES
Columns
Formula Late: Due Date Violated CR_DDVIOLATED —
Formula Late: SLA Violated CR_SLAVIOLATED —
Formula On Time CR_ONTIME —
Formula No KPI De ned CR_NOKPI —
Formula Average Processing Time - —
Formula Total CR_TOTAL —

the Due Date

Violated the SLA

Time
Key Figure Processing Time 20-CR_PRO_TIME-DEC —

Maintained
Monitor Status of Change Requests

0MDG_CR_T01_Q0008
Use
You use this query to retrieve status information pertaining to individual change requests belonging to a change request type
within a data model.
The system also runs the query after you complete the following steps in the Change Request Status screen.
1. Specify a Priority and a Time Scale
2. Choose the Show Details pushbutton
The screen displays details of the statuses of change requests broken down by change request type within data model.
3. Click a hyperlinked cell entry representing a number of change requests.
The screen belongs to the :Change Request Processing Time (MDG_MONITOR_CR_PROCESTIME) Web Dynpro application.
Structure
Filters
5/19/2023

CREATED_WEEK

CREATED_MONT

CREATED_QUAR

CREATED_YEAR
Rows
Columns
Key Figure Check Whether the Status of CR 20-REJECTED-INT4 —

Is Rejected
Key Figure Check Whether the Status of the 20-APPROVED-INT4 —

Change Request Is Approved
Formula Created - —

the Due Date

Violated the SLA
Key Figure Check Whether the CR Is On 20-TOTAL_ON_TIM-INT4 —

Time
Rejection Reason
0MDG_CR_T01_Q0009
Use
You use this query to collect the reasons why change requests were rejected. The system runs the query whenever you choose
the Rejection Reasons pushbutton when analyzing the statuses of change requests is the Change Request: Processing Time
(MDG_MONITOR_CR_PROCESTIME) Web Dynpro application.
5/19/2023
Structure
Filters

CREATED_WEEK

CREATED_MONT

CREATED_QUAR

CREATED_YEAR
Rows
Long Name Technical Name —
Columns
Formula Total - —

the Due Date

Violated the SLA

Time

Maintained
Change Request Type

0MDG_CR_T01_Q0011
Use
You use this query to retrieve all change request types for which change requests exist that meet the lter criteria. This
populates a dropdown list on the Rejection Reasons screen associated with the analysis of the statuses of change requests. The
relevant WebDynpro application is Change Request: Rejection Reason(MDG_ANLY_CR_REJ_REASON).
Structure
5/19/2023
Filters

CREATED_WEEK

CREATED_MONT

CREATED_QUAR

CREATED_YEAR
Rows
Characteristic Change Request Type 200MDG_CR_TYPE —
Columns
Long Name Technical Name —
Change Requests Data Model

BWBCT_QR_0MDG_CR_T01_Q0012
Use
You use this query to retrieve all data models for which change requests exist that meet the lter criteria. This populates a
dropdown list on the Rejection Reasons screen associated with the analysis of the statuses of change requests. The relevant
WebDynpro application is Change Request: Rejection Reason(MDG_ANLY_CR_REJ_REASON).
Structure
Filters

CREATED_WEEK

CREATED_MONT

CREATED_QUAR
5/19/2023

CREATED_YEAR
Rows
Columns
- - —
Data Sources
The following documents contain information on BI data sources. The documents explain the business uses of the data sources,
and provide data modeling information.
Change Request Data Source

DataSource Attributes 0MDG_ANLY_CR_DATASOURCE
Use
You use this data source to extract data required to analyze the processing of change requests in an organization, from the
perspective of processing time and from the perspective of status.
The data source was created using the BS_ANLY_OIP_MODELER tool. The tool generates a function module that uses the
CL_MDG_ANLY_CR_DATASOURCE class to fetch the data.
The GET_DATA method of the CL_MDG_ANLY_CR_DATASOURCE class in turn uses the GET_CREQUEST_LIST method of the
CL_USMD_CREQUEST_UTIL class to fetch all information related to change requests.
The CL_MDG_ANLY_CR_DATASOURCE class implements the following interfaces:
BW Data Source Emulation (IF_BS_ANLY_DATASOURCE)
Metadata for DataSource Generation (IF_BS_ANLY_DSOURCE_DEFINITION)
Data Source Runtime Behavior (IF_BS_ANLY_DSOURCE_RUNTIME)
Technical Data
Application Component MDG Analytics (0MDG_ANLY_DS)
Exchange Available as of Release ECC 6.0 EHP6
Shipment Not applicable
5/19/2023
Content Versions FND703
RemoteCube-Capable No
Delta-Capable No
Extraction from Archives No
Veri able No
Data Modeling
Fields of Origin for the Extraction Structure
Fields in the Extraction Description of the Field in the Table of Origin Field in the Table of Origin
Structure Extraction Structure
USMD_PRIORITY Priority USMD210C USMD_PRIORITY
CREATED_YEAR CR Created Year - MDG_ANLY_YEAR
CREATED_QUARTER CR Created Quarter - MDG_ANLY_QUARTER
CREATED_MONTH Created Month - MDG_ANLY_CREATED_MONTH
CREATED_WEEK CR Created Week - MDG_ANLY_WEEK
CREATED_DATE Change Request Creation Date - MDG_CR_CREATED_AT
USMD_MODEL Data Model USMD_001 USMD_MODEL
USMD_CREQ_TYPE Type of Change Request USMD110c USMD_CREQUEST_TYPE
USMD_CREQUEST Change Request USMD120c USMD_CREQUEST
DD_VIOLATED Check Whether the CR Violated - MDG_ANLY_DD_VIOLATED

the Due Date
DD_ON_TIME Check Whether the Change - MDG_ANLY_DD_ON_TIME

Request with Due Date is On
Time
SLA_VIOLATED Check Whether the CR has - MDG_ANLY_SLA_VIOLATED

Violated the SLA
SLA_ON_TIME Check Whether the CR With SLA - MDG_ANLY_SLA_ON_TIME

Is On Time
OTHERS SLA or Due Date is not - MDG_ANLY_OTHER_CR

Maintained
CR_PRO_TIME Processing Time - MDG_CR_PROCESSING_TIME
TOTAL_ON_TIME Check Whether the CR is On - MDG_ANLY_OTHERS_ON_TIME

Time
IN_PROCESS Check Whether the Status of the - MDG_ANLY_CR_INPROCESS

CR is In Process
REJECTED Check Whether the Status of CR - MDG_ANLY_CR_REJECTED

is Rejected
APPROVED Check Whether the Status of the - MDG_ANLY_CR_APPROVED

Change Request is Approved
5/19/2023
SLA_IN_DAYS SLA in Days - MDG_ANLY_SLA_IN_DAYS
USMD_REASON_REJ Reason for Rejection - -
USMD_MODEL_ID Data Model Description - -
Change Request Priority Text

DataSource Texts 0MDG_ANLY_PRIORITY_TEXT
Use
You use this data source to obtain the description of a priority for a change request.
These descriptions are speci ed in Customizing for Master Data Governance under General Settings Process Modeling
Change Requests De ne Priorities for Change Requests .
Technical Data
Delta-Capable Yes
Veri able No
Data Modeling
LANGU Language ID
USMD_PRIORITY Priority
TXTMI Description
Change Request Priority

DataSource Attributes 0MDG_ANLY_PRIORITY_ATTR
5/19/2023
Use
You use this data source to retrieve the priorities of change requests.
These priorities are speci ed in Customizing for Master Data Governance under General Settings Process Modeling
Change Requests De ne Priorities for Change Requests .
Technical Data
Delta-Capable Yes
Veri able No
Data Modeling
Data Model Description

0MDG_ANLY_DM_TEXT
Use
You use this data source to obtain language-speci c text descriptions associated with active data models.
These descriptions are speci ed in Customizing for Master Data Governance under General Settings Con guration
Workbench .
Technical Data
5/19/2023
Delta-Capable Yes
Veri able No
Data Modeling
LANGU Language ID USMD001T LANGU
USMD_MODEL Data Model USMD001T USMD_MODEL
TXTMI Description (Medium Text) USMD001T TXTMI
Data Model
DataSource Attributes 0MDG_ANLY_DM
Use
You use this data source to retrieve the data model so it can be used for the analysis of change requests.
These data models are speci ed in Customizing for Master Data Governance under General Settings Con guration
Workbench .
Technical Data
Delta-Capable Yes
Veri able No
Data Modeling
5/19/2023
USMD_MODEL Data Model USMD001C USMD_MODEL
USMD_UNAME User Name USMD001C USMD_UNAME
USMD_AEDTM Changed on USMD001C USMD_AEDTM
USMD_ATIME Last changed at USMD001C USMD_ATIME
PP_DOMAIN Reuse Active Area USMD001C PP_DOMAIN
Change Request Type Text

DataSource Texts 0MDG_ANLY_CR_CR_TYPE_TEXT
Use
You use this data source to obtain language-speci c text descriptions associated with change request types.
The texts for change request types are speci ed in Customizing for Master Data Governance under General Settings
Process Modeling Change Requests Create Change Request Type .
Technical Data
Delta-Capable Yes
Veri able No
Data Modeling
LANGU Language Key USMD110T LANGU
USMD_CREQ_TYPE Type of Change Request USMD110T USMD_CREQ_TYPE
TXTMI Description (medium text) USMD110T TXTMI
5/19/2023
Change Request Type

0MDG_ANLY_CR_TYPE
Use
You use this data source to obtain all possible change request types in the system.
These change request types are speci ed in Customizing for Master Data Governance under General Settings Process
Modeling Change Requests Create Change Request Type .
Technical Data
Delta-Capable Yes
Veri able No
Data Modeling
USMD_CREQ_TYPE Type of Change Request USMD110C USMD_CREQUEST_TYPE
USMD_EDTN_TYPE Edition Type USMD110C USMD_EDITION_TYPE
USMD_MODEL Data Model USMD110C USMD_MODEL
USMD_OBJLIST_REQ Objects to Be Changed Need to USMD110C USMD_OBJLIST_REQ

Be Speci ed
USMD_SINGLE_OBJ Change Request Includes One USMD110C USMD_SINGLE_OBJ

Entity Only
USMD_ENTITY_MAIN Main Entity Type USMD110C USMD_ENTITY_MAIN
USMD_CREQUEST_WF Work ow USMD110C USMD_WORKFLOW
USMD_TARGET_SYS Display Target Systems on USMD110C USMD_TARGET_SYSTEMS

Maintenance Screens
Change Request Rejection Reason Text
5/19/2023
DataSource Texts USMD212
Use
You use this data source to retrieve the texts describing the reasons why change requests were rejected.
These texts are speci ed in Customizing for Master Data Governance under General Settings Process Modeling Change
Requests De ne Rejection Reasons for Change Requests .
Technical Data
Delta-Capable Yes
Veri able No
Data Modeling
LANGU Language Key
USMD_CREQ_TYPE Type of Change Request
USMD_REASON_REJ Reason for Rejection
TXTMI Description (medium text)
Rejection Reason
DataSource Attributes 0MDG_ANLY_CR_REJ_REASON
Use
You use this data source to retrieve the possible reasons for rejecting change requests.
These reasons are speci ed in Customizing for Master Data Governance under General Settings Process Modeling
Change Requests De ne Rejection Reasons for Change Requests .
Technical Data
5/19/2023
Delta-Capable Yes
Veri able No
Data Modeling
USMD_CREQ_TYPE Type of Change Request - -
Change Request Data Source

DataSource Attributes 0MDG_ANLY_CR_DATASOURCE
Use
You use this data source to extract data required to analyze the processing of change requests in an organization, from the
perspective of processing time and from the perspective of status.
The data source was created using the BS_ANLY_OIP_MODELER tool. The tool generates a function module that uses the
CL_MDG_ANLY_CR_DATASOURCE class to fetch the data.
The GET_DATA method of the CL_MDG_ANLY_CR_DATASOURCE class in turn uses the GET_CREQUEST_LIST method of the
CL_USMD_CREQUEST_UTIL class to fetch all information related to change requests.
The CL_MDG_ANLY_CR_DATASOURCE class implements the following interfaces:
BW Data Source Emulation (IF_BS_ANLY_DATASOURCE)
Metadata for DataSource Generation (IF_BS_ANLY_DSOURCE_DEFINITION)
Data Source Runtime Behavior (IF_BS_ANLY_DSOURCE_RUNTIME)
Technical Data
5/19/2023
Delta-Capable No
Veri able No
Data Modeling
CREATED_YEAR CR Created Year - MDG_ANLY_YEAR
CREATED_QUARTER CR Created Quarter - MDG_ANLY_QUARTER
CREATED_MONTH Created Month - MDG_ANLY_CREATED_MONTH
CREATED_WEEK CR Created Week - MDG_ANLY_WEEK
CREATED_DATE Change Request Creation Date - MDG_CR_CREATED_AT
USMD_MODEL Data Model USMD_001 USMD_MODEL
USMD_CREQ_TYPE Type of Change Request USMD110c USMD_CREQUEST_TYPE
USMD_CREQUEST Change Request USMD120c USMD_CREQUEST
DD_VIOLATED Check Whether the CR Violated - MDG_ANLY_DD_VIOLATED

the Due Date
DD_ON_TIME Check Whether the Change - MDG_ANLY_DD_ON_TIME

Request with Due Date is On
Time
SLA_VIOLATED Check Whether the CR has - MDG_ANLY_SLA_VIOLATED

Violated the SLA
SLA_ON_TIME Check Whether the CR With SLA - MDG_ANLY_SLA_ON_TIME

Is On Time
OTHERS SLA or Due Date is not - MDG_ANLY_OTHER_CR

Maintained
CR_PRO_TIME Processing Time - MDG_CR_PROCESSING_TIME
TOTAL_ON_TIME Check Whether the CR is On - MDG_ANLY_OTHERS_ON_TIME

Time
IN_PROCESS Check Whether the Status of the - MDG_ANLY_CR_INPROCESS

CR is In Process
REJECTED Check Whether the Status of CR - MDG_ANLY_CR_REJECTED

is Rejected
5/19/2023
APPROVED Check Whether the Status of the - MDG_ANLY_CR_APPROVED

Change Request is Approved
SLA_IN_DAYS SLA in Days - MDG_ANLY_SLA_IN_DAYS
USMD_MODEL_ID Data Model Description - -
Search and Analytics Models

The following documents contain information on search and analytics models. The documents explain the business uses of the
models and provide technical information on the model nodes and on the operational data providers.
Change Request Priority

0MDG_CR_PRIORITY
Use
This technical search and analytics model is used to feed the Change Request (0MDG_CR_T01) application search and analytics
model with data relating to change request priorities.
Technical Data
Model Usage Technical Model
Software Component for Search and Analytics MDG_FND
Root Node: Change Request Priority
Technical Name of Root Node 0MDG_ANLY_PRIO_ATTR
Data Source 0MDG_ANLY_PRIORITY_ATTR
Operational Data Provider: Change Request Priority
Technical Name 0MDG_CR_PRIO
ODP Semantics Master Data Attributes
Direct Access Enabled Yes
Node: Change Request Priority
Technical Name 0MDG_ANLY_PRIO_TEXT
Data Source 0MDG_ANLY_PRIORITY_TEXT
5/19/2023
Operational Data Provider: Change Request Priority Description
Technical Name 0MDG_CR_PRIO
ODP Semantics Texts
Rejection Reason
0MDG_CR_REJ
Use
model with texts describing why change requests in the system were rejected.
Technical Data
Root Node: Rejection Reason
Technical Name of Root Node 0MDG_ANLY_CR_REJ
Data Source 0MDG_ANLY_CR_REJ_REASON
Operational Data Provider: Rejection Reason
Technical Name 0MDG_ANLY_CR_REJ
Node: Change Request Rejection Reason
Technical Name of Node 0MDG_ANLY_CR_REJ_TXT
Data Source 0MDG_ANLY_CR_REJ_REASON_TXT
Operational Data Provider: Rejection Reason Text
Technical Name 0MDG_ANLY_CR_REJ_TXT
Change Requests
5/19/2023
0MDG_CR_T01
Use
This application search and analytics model provides the metadata for analyzing how effectively an organization processes
change requests. You can conduct the analysis from the following perspectives:
Processing Time
Status
All BI queries used to analyze the status and processing time of change requests use this search and analytics model. The
business object this model searches for is Change Request USMD_CREQUEST.
Model Usage Application Model
Default Request
Technical Name DEFAULT
Usage Attribute Search
Root NodeChange Request DataSource
Technical Name of Root Node 0MDG_ANLY_CR_DS
Data Source 0MDG_ANLY_CR_DATASOURCE
Operational Data Provider: Change Request DataSource
Technical Name 0MDG_CR_T01
ODP Semantics Transaction data
Authorization Checks
Check ID ABAP Authorization Object Description
ACTVT USMD_CREQ Complete speci c activities with change

request types, for example Display.
CREQ_TYPE CREQ_TYPE Access change request types.
Change Request Type

0MDG_CR_TYPE
Use
5/19/2023
model with data relating to change request types.
Technical Data
Root Node: Change Request Type
Technical Name of Root Node 0MDG_CR_TYPE
Data Source 0MDG_ANLY_CR_TYPE
Operational Data Provider:
Technical Name 0MDG_CR_TYPE
Authorization Checks
Check ID ABAP Authorization Object Description
ACTVT USMD_CREQ Complete speci c activities with change

request types, for example Display.
CREQ_TYPE CREQ_TYPE Access change request types.
Node: Change Request Type Text: Data Source
Technical Name 0MDG_CR_TYPE_TEXT
Data Source 0MDG_ANLY_CR_TYPE_TEXT
Operational Data Provider:
Technical Name 0MDG_CR_TYPE_TEXT
Data Model Description

0MDG_DM
Use
5/19/2023
model with data model descriptions.
Technical Data
Root Node: Data Model
Technical Name of Root Node 0MDG_ANLY_DM
Data Source 0MDG_ANLY_DM
Operational Data Provider: Data Model
Technical Name 0MDG_ANLY_DM
Node: Data Model Descriptions
Technical Name 0MDG_ANLY_DM_TEXT
Data Source 0MDG_ANLY_DM_TEXT
Operational Data Provider: Data Model Descriptions
Technical Name 0MDG_ANLY_DM_TEXT
ODP Semantics Texts
Dashboards
The following documents contain information on BI dashboards. The documents explain the business use of the dashboards as
well as describing their views and associated queries.
Monitor Change Request SLA and Due Date Violations

Technical name
Use
You can use this dashboard to monitor the processing times of change requests.
Structure
5/19/2023
View Description Query Used
Processing Time of Change Requests for See the Query documentation. Change Request Weekly Analysis
all Data Models (Weeks)
Processing Timeof Change Requests for See the Query documentation. Change Request Monthly Analysis
all Data Models (Months)
Processing Time of Change Requests for See the Query documentation. Change Request Quarterly
all Data Models (Quarters) Analysis
Processing Time of Change Requests for See the Query documentation. Change Request Yearly Analysis
all Data Models (Years)
Processing Time of Change Requests by See the Query documentation. Change Requests Priority
Data Model
Cleansing Cases
Use
You use a cleansing case to merge the master data from potential duplicates into one target record.
Features
Search and create cleansing cases
You can create a cleansing case from the Search Cleansing Cases UI. This opens the cleansing case in an overview page
where you can select the business objects you want to include in the cleansing case. All cleansing cases are created and
stored with a unique ID. You can use the ID along with other search criteria to search for a cleansing case on the Search
Cleansing Cases UI. This allows you to save a cleansing case and work on it at a later point.
Manage target records and potential duplicates
If you identify duplicate records for your business objects, you can merge the duplicates into the target record to ensure
that your data is consistent. You can identify potential duplicates from the business object’s Search UI or using the
duplicate check.
Cleansing tree
Multiple selections of the same entity type in the cleansing tree trigger automatic comparison and the optional merging
of data sets. This must be con gured on entity level in the backend.
Keep data entries of target record
The Keep eld displays the data sets of the target record selected automatically. You can then choose to add more data
to the target record from the potential duplicates, or else deselect the Keep checkbox to discard data. You can switch off
the dialog box that opens after you deselect the Keep checkbox with the user parameter BS_CC_NOTIFY_UNKEEP.
Drag and drop selected entities
You can con gure your UI to allow the drag and drop of data for selected entities from potential duplicates to the target
record. For example, the business partner application allows drag and drop for communication data.
Details section
When you select an entry in the cleansing tree, the entry details are displayed. To set up the Details section, you must
de ne a speci c UI con guration for the selected entity. Otherwise, a generic description of the entity is displayed.
5/19/2023
For business partners, the Details section is the same as the data entry available during single object processing, as the
system is con gured for each entity in the cleansing tree. This gives you a complete overview of your master data when
working with a cleansing case. You can also edit the information that already exists for your target record. This allows
you to correct any errors in the data that might have occurred.
Customizable view
You can set up the cleansing case according to your requirements, for example, how the Overview table is displayed or
where the details appear on the screen.
Processor handling
Before submitting the change request, you can forward the cleansing case to another user by entering their user ID in
the Processor eld.
Creating a Cleansing Case for Customer, Supplier, and Business

Partner
Use
You can create a cleansing case for two or more business objects that you have marked as duplicates for Master Data
Governance for Customer, Supplier, or Business Partner. The application assigns the selected business objects a cleansing case
ID. The cleansing case merges the data from the duplicates into one target record.
Prerequisites
A cleansing case can be created for customer, supplier, and business partner. Therefore, you have to activate the related
business functions for customer (MDG_ERP_CUSTOMER_3), supplier (MDG_ERP_SUPPLIER_4), or business partner
(MDG_BUPA_1) to use the cleansing case function.
You have noted the IDs of the duplicate business objects that you want to cleanse. Otherwise, you can identify the
relevant business objects using the other search criteria.
Procedure
The following is an example of the process for creating a cleansing case for business partners:
1. From the application homepage, select Search Cleansing Case. Select the New button.
Alternatively, you can use the search UI to nd business partners. Select the required business partners from the results
list after executing a search and choose the Create Cleansing Case button.
2. The cleansing case application opens. Enter a description and priority.
3. Search for the business partners that you want to include in the cleansing case. You must select at least two business
partners.
Note that you don’t need to add more business partners if you have opened the cleansing case from the search UI, but
you have the option to add more if required.
4. Assign one of the business partners as the target record. The other business partners should be marked as potential
duplicates. The data from the potential duplicates can be transferred to the target record. Business partners marked as
No Duplicate are not included in the cleansing tree in the Overview area.
5. From the Overview area, choose the Start button. The system creates a change request for the cleansing case.
5/19/2023
6. In the Overview area, the business partner data is displayed in a tree structure, with the same data sets grouped
together. The data sets of the target record are selected automatically and highlighted with a background color for
increased visibility. Choose the data you want to include in the target record by selecting the Keep checkbox for each
entry. You can also drag and drop attributes from one node to the other, for example, phone numbers or address usages.
It is also possible to edit certain entries of the target record data directly, for example, the address data. When you
select a data entry, the Details screen opens where you can make changes.
7. If you want to discard data assigned to the target record, deselect the Keep checkbox for the corresponding data set.
These data sets are not removed from the target record until you consolidate the data by choosing the Consolidate
button.
8. When you are ready, save the cleansing case. Once you save the cleansing case, you can go back and make changes later.
9. If you do not want to make any other changes, choose Submit to submit the change request carrying all of the target
record changes.
Result
You have created a cleansing case.
Note that once you have processed the cleansing case, you can mark the potential duplicates for deletion or set blocking ags
from the business partner search UI.
Work ow Log
Use
You use this Web Dynpro application (USMD_CREQUEST_PROTOCOL2) to display the work ow log for a change request.
Features
The work ow log shows the respective work items along with the processor, work item type and status, and the decision that
must be taken. The date of creation and completion are also displayed.
You can show or hide any background steps by choosing Background Steps. The default setting shows dialog steps only.
You can call the technical work ow log by choosing Related Services.
You can print the work ow log in PDF format by choosing Print Version.
Activities
If you have installed the Business Package for Financial MDM 1.51 you can call this Web Dynpro application in the Financial
Master Data Governance work center from the following iViews:
Single Processing by choosing Related Services
My Change Requests
Process Change Request by choosing Related Services
Application Log
5/19/2023
Use
Using this Web Dynpro application (USMD_APPLICATION_LOG), you can output messages that belong to the application logs
created by the system.
In the following situations, for example, the system creates or updates application logs:
When master data is changed
Validation
When master data is replicated
Integration
The Web Dynpro application makes features speci cally adapted for master data governance available to the transaction
Analyze Application Log (SLG1).
Features
You can display a user-speci c results list of the created application logs and use the following functions:
Display the messages for an entry in the log list (at the top of the screen).
The system uses colors and symbols to indicate the following message types:
Termination messages
Success messages
Warning messages
Error messages
The system displays all message types by default. By clicking the relevant symbols, you can show or hide the respective
message type.
Display the long text for an entry in the message list (at the bottom of the screen).
The system uses an information symbol to indicate whether a long text exists.
Print the message list in PDF format
Export the message list to Microsoft Excel
Filter the messages
You can use the column headers in the message list as lter criteria.
Activities
1. To list the messages created for a speci c message type, date, time, or user, select an application log from the list at the
top of the screen.
2. To display messages of a speci c type only, click the symbols for the message types that are to be hidden. For example,
to display error messages only, click the symbols for all other message types (but not the red symbol).
3. To display the long text for a selected message, click on the information symbol in the lower screen area.
5/19/2023
See Also
For more information, see Evaluation of Data Replication Logs.
Data Replication
Use
You can use this function to replicate data from the Master Data Governance (MDG) hub to target systems.
The data replication is carried out using the Data Replication Framework.
Prerequisites
You have con gured the data replication.
For more information, see Con guration of Data Replication.
If you wish to use external data replication lters, you have de ned lter criteria.
For more information, see Use of Data Replication Filters.
You have de ned the necessary authorizations. For more information, see the documentation on the authorization
objects DRF_ADM and DRF_RECEIV.
Features
You can start the manual replication of data using the following options:
Web Dynpro applications (Manual Replication)
You can use these applications to respond to one-off requests to replicate data to selected target systems. The available
Web Dynpro applications are as follows:
Replicate by Replication Model
You use this Web Dynpro application to replicate business objects within a replication model to selected target
systems. The application selects the business objects according to de ned lter criteria. This task is typically
completed by a master data steward.
 Example
After a scheduled replication run fails, a master data steward must replicate data immediately.
For more information, see Manual Replication by Replication Model
Replicate by Object Selection
You use this Web Dynpro application to replicate to selected target systems either a list of business objects or a
set of business objects with speci ed relationships (depending on the business object type). This task is typically
completed by a master data administrator.
 Example
A master data administrator responds to an urgent request to replicate a supplier in a target system.
For more information, see Manual Replication by Object Selection

5/19/2023
The Execute Data Replication (DRFOUT) option on the SAP Easy Access menu (Manual Replication or scheduled
replication)
You can use this option, if you want to closely control the conditions of data replication, for example if you want to
schedule data replication to run regularly.
This option allows you to choose between initial data replication, delta data replication (for replication of changes only),
and data replication on a one-off basis. This task is typically completed by a master data administrator.
You can apply lter criteria to the data you replicate. For more information, see Use of Data Replication Filters.
When carrying out the data replication, the system automatically generates data replication logs, which you can subsequently
evaluate. For more information, see Evaluation of Data Replication Logs - SAP Easy Access and Display of Data Replication
Logs.
De ne Filter Criteria (Deprecated)
Use
You can use this application to de ne lter criteria that restrict data replication to other business systems: for example, to
replicate supplier data for just one group of suppliers.
Features
The user interface displays a work list that allows you to edit lters for combinations of business objects and replication models.
Checking the Status of Filters
The status icons in the work list have the following meanings:
Icon Description
Filter criteria are already de ned. You can change the lter criteria
by selecting the row and choosing the Change button.
No lter criteria are de ned yet. You can de ne lter criteria by

selecting the row and choosing the Create button.
Creating or Editing Filters
To create or edit lters, you can select a row on the table and choose the Create button or the Change button. A screen then
allows you to create or change lter criteria for explicit lters ( lters that you de ne online). The table below describes the
features of the screen.
Feature Description
Inclusion or Exclusion of Business Objects The screen is divided into the following sections:
The Filter Criteria to Include Business Objects section

allows you to de ne lter criteria for the business objects
you want to replicate.
The Filter Criteria to Exclude Business Objects section

allows you to de ne lter criteria for the business objects
you do not want to replicate.
5/19/2023
Feature Description
Formulation of Filter Criteria Each lter criterion includes the following elements:
Attribute: A eld on which a condition is de ned.
Operator: A logical function such as ʻequals to’ or ʻis greater

than’ to determine value ranges for speci c elds.
Value: A threshold value.
The standard formulation for a lter criterion is: <attribute>

<operator> <value>. For example, Supplier No. equals
141.
If you choose the operator 'is between', an extra entry box appears,
and the formulation changes to: <attribute> is between
<value> and <value>
System Evaluation of Filter Criteria The system evaluates the lter criteria using the following logic:
If several lter criteria are applied to the same attribute,

the system applies the lter if any lter criterion is true.
For example, Supplier No. equals 141 OR

Supplier No. equals 142.
If several lter criteria are applied to different attributes,

the system applies the lter if all lter criteria are true.
For example, Supplier No. equals 141 AND

Company equals 0001.
Copying of Filter Criteria If you use the same business object in another replication model,
you can copy its lter criteria with the Copy icon.
Deletion of Filter Criteria If you choose the Delete All Criteria button, all de ned lter criteria
are deleted. If you then save your changes, the status of the lter
changes from green to yellow with the next refresh of the work list.
Displaying Filters De ned In Customizing
You can choose the Show Prede ned Filters button to display prede ned lters ( lters de ned in Customizing).
Displaying Segment Filters
You can choose the Show Segment Filters button to create or change lter criteria for segment lters. When you de ne a
segment lter, you ensure that only selected segments of a business objects are replicated. Specifying segment lters reduces
not the number of business objects that are replicated, but the size of each business object.
Transporting Filter Criteria
If you select this option for one or more selected table entries, you can include the lters on a transport request, so that they
can be imported into another system. You can de ne and test lters in a test system before transporting them into a productive
system.
De ne Filter Criteria
 Remember
5/19/2023
SAP strongly recommends that you use this SAP Fiori app instead of the existing De ne Filter Criteria (Deprecated) tile
based POWL framework to restrict data replication to other business systems by using DRF framework.
App ID: F6519
With this app, you can maintain conditions using which the user can restrict data replication to other business systems using
Data Replication Framework (DRF). To use the app, you must have con gured the role SAP_BR_ADMINISTRATOR_DATA_REPL
for your user.
Key Features
This app enables you to de ne lter criteria for Replication Model as well as Business Object Type. You can use this app to
perform the following tasks:
Creating or Editing Filters
To edit lters, you can choose the Edit button and then make the required changes to your lter criteria. To create lters,
choose the Edit button, go to the Main Filters tab, and then click Create. The table below describes the features of the
screen.
Feature Description
Inclusion or Exclusion of Business Objects The Filter column, in the Main Filters tab, enables you to
include or exclude de ne lter criteria for the business objects
you want to replicate.
Formulation of Filter Criteria Each lter criterion includes the following elements:
Field Name: A eld on which a condition is de ned.
Filter: A logical function such as equals to or is greater

than to determine value ranges for speci c elds.
Value: A threshold value.
The standard formulation for a lter criterion is: <field

name> <filter> <value>. For example, Supplier No.
equals 141.
If you choose the operator 'is between', an extra entry box

appears, and the formulation changes to: <field name> is
between <value> and <value>
System Evaluation of Filter Criteria The system evaluates the lter criteria using the following logic:
If several lter criteria are applied to the same

attribute, the system applies the lter if any lter
criterion is true.
For example, Supplier No. equals 141 OR

Supplier No. equals 142.
If several lter criteria are applied to different

attributes, the system applies the lter if all lter
criteria are true.
For example, Supplier No. equals 141 AND

Company equals 0001.
5/19/2023
Feature Description
Deletion of Filter Criteria Choose the checkbox adjacent to a lter criteria and then click
Delete to remove the selection from your list. You can also
delete all the lter criteria at once by choosing the checkbox
adjacent to the Field Name tab and then clicking Delete.
Displaying Filters De ned In Customizing
You can choose the Prede ned Filters tab to display prede ned lters ( lters de ned in Customizing). Note that, these
lter criteria are set by the system and are not editable.
Displaying Segment Filters
You can choose the Segmented Filters tab and then choose a segmented lter item to create or change lter criteria for
the segmented lters. When you de ne a segmented lter, you ensure that only selected segments of a business objects
are replicated. Specifying segment lters reduces not the number of business objects that are replicated, but the size of
each business object.
Main Filters
You can choose the Main Filters tab to create or change lter criteria for business objects.
 Tip
SAP enables you to download a copy of the lter criteria in an XLS or PDF le format. You can do so by clicking the XLS
dropdown list and then selecting your preferred le format to which you wish to download the lter criteria.

Desktop
Tablet
Execution of Data Replication - SAP Easy Access
Use
You use this function to start the replication of master data (transaction DRFOUT).
Features
A screen allows you to choose replication criteria.
Section of Screen Description
Replication Model You must replicate data for a particular replication model.
Outbound Implementation You can choose to replicate data for particular outbound implementation. The outbound
implementation must be de ned for the replication model. If you do not choose an outbound
implementation, the system replicates data for all outbound implementations associated with the
replication model.
5/19/2023
Replication Mode You can choose a replication mode. By default, the system uses the preexisting lters de ned in
transaction DRFF (De ne Filter Criteria) for all replication modes.
The available replication modes are as follows:
Initialization
The system replicates the current state of master data from the Master Data Governance
(MDG) hub to a target system. Change pointers are not considered. Note that the replication of
data in initialization mode can consume a signi cant amount of time and resources.
Changes
The system replicates all changed data or uses the Limit Changes Using Time Interval check
box to only replicate data changed in a particular date and time frame. The system uses
change pointers to determine which data has changed.
Manual
The system replicates data using one of the following options:
If you de ned lter criteria using the Manual Replication Filter Criteria button, the
system selects the Manual Replication Filter Criteria Available checkbox. During
replication, the system ignores the preexisting lters de ned in transaction DRFF and
applies the manual lter criteria.
If you did not de ne lter criteria using the Manual Replication Filter Criteria button,
the Manual Replication Filter Criteria Available checkbox is deselected.
If you want to replicate large volumes of data, it may make sense to execute data replication as
a one-time background job.
Manual Replication Filter This button is only available if you select a Replication Mode of Manual.
Criteria (Button)
You can use the key components of object IDs as lter criteria for the replication of data. For example,
you can replicate data about ights involving a particular airline by specifying a two-character code for
the Airline key component of the Flight object ID.
You can only use these lter criteria if you have completed the following actions:
De ned a key structure for the object ID
Selected an outbound implementation that is associated with the relevant business objects
If you specify manual lter criteria here, all preexisting lters de ned in transaction DRFF (De ne Filter
Criteria) are ignored for the current run.
After you save lter criteria, the system selects the Manual Replication Filter Criteria Available
checkbox in the Replication Mode section of the screen
5/19/2023
Options for Report Control You can choose from the following options:
Parallel Processing
If you need to replicate a large quantity of data quickly, you can use multiple servers and split
the job up into work processes. You must specify the server group and the number of work
processes involved.
Test Run Only
If you select this checkbox, the system does not send data to the target system. After you
choose Execute, the data replication log shows the data that would have been replicated if it
was not a test run. The change pointers are not deleted.
Local Download
If you select this check box and the outbound implementation supports le download, the
system prompts you to specify a le location.
The le location you specify overrides the le location speci ed in Customizing for Master
Data Governance under General Settings Data Replication De ne Custom Settings for
Data Replication De ne Technical Settings for Business Systems .
After you execute data replication, the system generates data replication logs, which you can evaluate. For more information,
see Evaluation of Data Replication Logs.
Activities
To execute data replication, starting from the SAP Easy Access screen, choose Cross-Application Components Processes
and Tools for Enterprise Applications Master Data Governance Data Replication Execute Data Replication (DRFOUT) .
To de ne lter criteria for data replication, starting from the SAP Easy Access screen, choose Cross-Application Components
Processes and Tools for Enterprise Applications Master Data Governance Data Replication De ne Filter Criteria
(DRFF) .
Replicate by Replication Model
Use
You can use this application to immediately start data replication in case of an urgent one-off request, for example if a
scheduled run failed.
The application allows you to specify a replication model and a business object type as the scope for the data replication. Only
data that ful ll the lter criteria are replicated.
Prerequisites
For more information, see De ne Filter Criteria (Deprecated).
Features
5/19/2023
Selecting a Replication Scope
The scope for data replication must include a replication model, one or more business objects, and one or more target systems.
For each business object, you can access lter criteria by choosing the Display Filter Criteria button, and then change lter
criteria by choosing the Edit button.
Selecting a Replication Option
You can apply the following technical settings when you execute data replication:
Parallel Processing
If you need to replicate a large quantity of data quickly, you can use multiple servers and split the job up into work
processes. You must specify the server group and the number of work processes involved.
Test Run Only
If you select this check box, the system does not send data to the target system. After you choose Replicate, the data
replication log shows the data that would have been replicated if it was not a test run.
 Note
Background mode of data replication is not supported in a test run.
Background mode
If you select this checkbox, the system replicates data for the speci ed business objects from the source to the target
system in the background. You can choose to execute the background job for Initialization mode or Changes mode. If you
want the background job to be performed for Initialization, the system replicates all the data for the business object
from the source system to the target system. If you choose the Changes mode, the system replicates only the data that
has changed for the business object for which change pointers exist, from the source system to the target system. Note
that when you select the Background Mode of data replication for Changes, the data is replicated only once the user
chooses Replicate. This must be done each time you want to replicate data that has changed in a background mode.
Replicate by Object Selection
Prerequisites
For more information, see De ne Filter Criteria.
Context
You can use this application to quickly replicate business object data to target systems that you select.
You can complete the following tasks:
For all business object types, you can replicate a list of business objects
You can search for the business objects you want to replicate before including them in the list. You can also directly
specify their IDs.
5/19/2023
For some business object types, you can replicate all business objects with speci ed relationships
There are multiple selection options.
You typically use this application to respond to one-off requests for the replication of speci c business objects.
 Example
You can use this application to respond to an urgent request to replicate a supplier to a target system.
Procedure
1. Complete the appropriate tasks for the replication option you want.
Replication Option Tasks
Replicate a list of business objects

a. In the Business Object Type drop down menu, choose
an entry that represents a business object type, for
example, Business Partner.
b. In the Business Objects to Be Replicated table, enter

business objects for replication, with or without the
help of a search.
Replicate business objects with speci ed relationships.

a. In the Business Object Type drop down menu, choose
an entry representing a business object type and its
relationships, for example Business Partner Involved
in Relationships.
b. In the Business Objects to Be Replicated table,

specify relationships that the business objects to be
replicated must ful ll.
 Example
You can request the replication of business partners
that ful ll the following criteria:
The relationship is of a speci c type, for

example “is contact person.”
The speci ed relationship stays valid until a

Valid To date.
2. Select or deselect the following conditions for the replication.
Apply Object Filter Criteria
You can apply the lter criteria you have con gured for the replication of this business object type. After you
apply this setting, the system only replicates business objects that ful ll the criteria.
For more information, see De ne Filter Criteria.
Test Run Only
If you select the Test Run Only checkbox, the system does not send data to the target system when you choose
the Replicate button. Instead, the system only shows the data that would have been replicated in the data
replication log.
5/19/2023
3. Select target systems in the Target System Selection table.
4. Replicate the business objects by choosing the Replicate button.
5. Display the replication log by choosing the Display Log button. For more information about the replication log, see
Monitor Replication.
Monitor Replication
Use
You can use this application to view and analyze messages in the data replication log. The system uses icons to represent
message types and propagates the message type of the least successful child message to its parent.
Features
You can quickly drill down to unsuccessful messages. To do this, select the replication model from the Replication Model drop
down and specify the lter criteria. Click Continue.
The screen shows two lists:
Main list: Replication logs
Detail list: Messages for a selected replication log
Navigation of Replication Logs List
Column Description
5/19/2023
Column Description
Propagated Type / Date / Time / User Shows a hierarchy of messages that are related to a replication log.
The column title describes the replication log and provides the
following information:
Propagated type
Describes the type of the least successful child message.

Each type has its own icon. If a grandchild message shows
an Error icon, the parent message and grandparent
message also show an Error icon.
In decreasing order of success, the icons and their

corresponding types are as follows:
Success
Warning
Error
Abort
Date
Time
User
You can expand the replication log and all messages with a value in
the Count column that is greater than 1.
Messages are formulated as follows: <Type (or Propagated

Type if the message is expandable)> /
<Description>.
Count Shows the number of child messages for the replication log or for
one of its messages. You can expand all messages with a value in
the Count column that is greater than 1.
Navigation of Messages List
If a selected replication log or a selected message has child messages, these messages are displayed in the Messages list. If a
selected message has no child messages, the message is repeated in the Messages list.
To make the output more readable, you can show or hide messages of a particular type using the following toggle buttons:
Success
Warning
Error
Abort
In the Action column, you can click links that provide contextual information about the message. For example, you can click the
Show Filter Criteria link when analyzing certain messages about the lters used during data replication. From there you can
view and edit lter criteria.
In the Long Text column, you can access the detailed descriptions of how to address individual messages, if such descriptions
exist.
5/19/2023
Evaluation of Replication Logs - SAP Easy Access
Use
You can use this function to complete the following tasks:
Search for and analyze logs about data replication runs (transaction DRFLOG)
Delete logs about data replication runs (transaction DRFLOGDEL)
Features
Searching for Replication Logs
The table below shows the search criteria you can use when searching for replication logs using the DRFLOG transaction.
Section of Search Screen Description
Replication Model You must choose a replication model as a search criterion.
Selection Options for Object IDs (Button) You can use the key components of object IDs as search criteria.
For example, you can search for replication logs about ights
involving a particular airline by specifying a two-character code for
the Airline key component of the Flight object ID.
You can only specify selection options for an object ID if you have
completed the following actions:
De ned a key structure for the object ID
Selected an outbound implementation that is associated

with the relevant business objects
The system only applies the lter criteria if you select the Use
Maintained Selection Options for Object IDs as Message Filter
checkbox.
Outbound Implementation You can choose an outbound implementation as a search criterion.

The outbound implementation must be de ned for the replication
model. If you do not choose an outbound implementation, the
system returns logs for all outbound implementations related to the
speci ed replication model.
Additional Restrictions
You can search using a date range.
You can search for data replications executed by a

particular user.
You can search for overview (header) logs only or detailed

logs only.
You can search for logs matching criteria you speci ed

using the Selection Options for Object IDs button. To do
this, select the Use Maintained Selection Options for
Object IDs as Message Filter checkbox.
Replication Mode You can search for replication logs that are relevant to speci c
replication modes or relevant to all replication modes. For example,
you can search for logs that were previously created during an
initial replication run.
5/19/2023
Section of Search Screen Description
Log Formatting You can choose between a hierarchical display or a display in order
of log class.
Analyzing Replication Logs
After you execute a search in the DRFLOG transaction, the system displays replication logs.
Depending on the Log Formatting options speci ed during the search, you see either a hierarchical display or a display in order
of log class. You can double-click a message to view its detail.
You can perform actions on replication logs. Possible actions range from opening message long texts to restarting data
replication for objects that were replicated with errors. To perform an action on a log, you select the log and choose an icon. The
table below describes the icons.
Icon Description
Shows the lter criteria used when the replication occurred and displays the objects that were
replicated after the lter was applied. Filter criteria are only shown for detail logs about objects
Shift + F8
replicated using lters.
Restarts data replication for all objects belonging to a particular run ID that were replicated with
errors. The restart is only possible if you select a detail log. The system sends the object IDs of the
Shift + F9
objects that need to be replicated again using the same runtime parameters used by the original
replication run.
Restarts a data replication run for all objects belonging to a particular run ID. The restart is only
possible if you select a detail log.
Shift + Ctrl + 0
Provides detailed information about the selected message on a new screen, if this information exists,
and sometimes allows further navigation.
F7
If the selected message refers to a service, you can view its XML.
If the selected message refers to an Enterprise Service, you can navigate directly to
Integration Engine: Monitoring using transaction SXMB_MONI.
Provides the long text for a message, if one exists.
F5
Shows technical information about a selected message, for example the message type, message
class, and message number.
F6
Deleting Replication Logs
The table below shows the criteria you can use when deleting replication logs using the DRFLOGDEL transaction.
Screen Section Description
Replication Model You must choose a replication model for which you want to delete
selected logs.
Replication Mode You can delete logs that were generated by data replication runs
executed in speci c modes or in all modes.
Expiry Date You can restrict deletion to logs that have exceeded an expiry date.
5/19/2023
Screen Section Description
Selection Conditions You can delete logs for a range of users, a range of log numbers, a
range of problem classes, or a range of dates.
Options You can delete logs directly or just calculate the amount of logs that
the system would mark for deletion with the current search criteria.
Delete after No. of Logs You can choose a number of logs to be deleted at a time before the
system commits the deletion to the database.
Activities
To evaluate replication logs, starting from the SAP Easy Access screen, choose Cross-Application Components
Processes and Tools for Enterprise Applications Master Data Governance Data Replication Evaluate Replication
Log (DRFLOG) .
To delete replication logs, starting from the SAP Easy Access screen, choose Cross-Application Components
Processes and Tools for Enterprise Applications Master Data Governance Data Replication Delete Replication Log
(DRFLOGDEL) .
To call up alert processing, starting from the SAP Easy Access screen, choose Tools CCMS Control/Monitoring
CCMS Monitor Sets . If the system has written an alert, a node for the Data Replication Framework is displayed under
SAP CCMS Technical Expert Monitors All Monitoring Contexts .
Subscription of Objects for Data Replication - SAP Easy Access
Use
You use this function to request the future data replication of object instances for a particular business object type belonging to
a speci c business system. For example, you can use this function to subscribe all supplier business objects in a particular
system for a future replication. This function is useful if you want to overrule lters that block business objects from replication.
Features
The selection criteria are as follows:
You must select a business object type and a business system.
You can run the report as a test run or as a productive run.
If you select the Test Run checkbox, the system does not subscribe object instances for replication. If you deselect the
Test Run checkbox, the system subscribes all object instances belonging to the selected business object type in the
selected system for data replication.
You can opt to display or just count the object instances.
If you select the Display Data checkbox, the system displays the object instances. If you deselect the Display Data
checkbox the system counts the object instances.
Activities
To subscribe objects for data replication, starting from the SAP Easy Access screen, choose Cross-Application Components
Processes and Tools for Enterprise Applications Master Data Governance Data Replication Subscribe Objects for Data
Replication (DRFSUB) .
5/19/2023
Example
Suppose you want to restrict replication of supplier data so that a newly connected target system receives replicated data for
the following suppliers:
New suppliers from Germany
Legacy suppliers from any country or region
You complete the following steps:
1. Connect the new system to the Master Data Governance (MDG) hub.
2. Upload suppliers to the MDG hub.
3. Create key mapping entries.
4. De ne a lter that ensures only suppliers from Germany are replicated.
5. Overrule the lter for legacy suppliers outside of Germany by subscribing all existing suppliers in the target system for
replication.
Display of Object Replication Status - SAP Easy Access
Use
You use this function to monitor the outcome of data replication runs involving business objects within business systems.
Features
Running the Search
You can run the search using any combination of the following search criteria: business object, business system, change request,
or run ID.
 Tip
You can either choose single or multiple business objects in the search criteria.
If a business object ID has a key structure assigned, you can use the key components of the key structure as search criteria. To
do this, choose the Free Selection button and specify search criteria. For example, you can search for ights involving a
particular airline by specifying a two-character code for the Airline key component of the Flight object ID.
 Note
You can assign key structures to business object identi ers in Customizing for Master Data Governance under General
Settings Data Replication Enhance Default Settings for Data Replication De ne Business Objects and Object
Identi ers Assign Key Structures to Object Identi ers
Working With the Search Output
After you execute the search, replication details for replication runs involving business objects within business systems are
displayed.
5/19/2023
For each object ID, you can complete the following actions:
Check the progress of data replication.
The table below shows the codes for replication status:
Replication Status Description
SE Error in message sent.
PO Message was posted.
PE Error in message posted.
TS Message to be sent. (Not sent yet.)
Block or unblock data replication for all replication runs involving combinations of business systems and object IDs
To do this, select one or more rows and choose the Block / Unblock Data Replication button. If you select a row and
choose the pushbutton, the system automatically selects all rows with a matching combination of business system and
object ID.
We recommend you only block data replication on a temporary basis and you only do this if business objects are unstable
for a short time. To block a business object permanently, set up a lter.
Display the replication log.
To do this, select a row and choose the Display Replication Log button. Alternatively, double-click the Handle entry.
The replication log shows detailed information about what happened during a particular replication run.
Using Variants
A variant is a saved set of selection criteria that helps you in searching for the object replication status. If you specify a variant
to search for a replication status, the system uses the values saved in the selected variant.
To create a variant,
1. Run the app using your Fiori launchpad.
2. Enter relevant values in the required elds.
3. Click Save.
The variant screen is displayed.
4. In the variant screen, enter values in the mandatory elds such as the Variant Name and Description.
5. Click Save to retain the selected values in the variant.
You can save multiple variants, as required. While searching for an object replication status, you can use the Get Variant icon to
view all the saved variants. You can now choose a variant with the relevant search criteria and then execute the report.
Activities
To display object replication status, starting from the SAP Easy Access screen, choose Cross-Application Components
Processes and Tools for Enterprise Applications Master Data Governance Data Replication Subscribe Objects for Data
Replication (DRFSUB) .
5/19/2023
Display Replication Status
Use
You use this application to obtain replication status information about a business object.
Features
Searching for Replication Status Records
Search Criteria
To search for replication status records, you must enter an Object ID (for example, Supplier) and an ID value.
Search Results
Not all of the records returned match the search criteria. The system uses key mapping to add physically different instances of
the same business object to the search results.
Working With Replication Status Records
Replication Status Icons
The table below explains the meaning of Replication Status icons.
Icon Explanation
Green Light: Success The message is posted in the target system.
Yellow Light: Caution The message is sent, or the message is about to be sent. The
message is not yet posted.
Red Light: Error There was an error in sending the message to the target system or
an error in posting the message in the target system.
Blank: No replication No attempt at replication was made in this system.
Replication Logs
For details of what happened during data replication, click the Display Log link in the Application Log column. For more
information, see Monitor Replication.
Deletion of Object Replication Status - SAP Easy Access
Use
The Delete Object Replication Status report allows you to save database space by deleting unwanted records about the status
of object replication.
Prerequisites
You have decided which records about object replication status to delete. To view object replication status records from the SAP
Easy Access menu, go to Cross-Application Components Processes and Tools for Enterprise Applications Master Data
5/19/2023
Governance Data Replication DRFRSD - Display Object Replication Status . For more information, see Display of Object
Replication Status - SAP Easy Access.
Features
You can specify conditions for deleting records. You can then delete the records immediately, or count how many records would
be deleted with the deletion conditions you speci ed.
Specifying Deletion Conditions
Under Deletion Conditions, you can choose any combination of the following criteria for deleting records about object
replication status:
Business Object Type
You can delete records that refer to a selected business object type.
Business System
You can delete records that refer to one or more business systems.
Records Older Than (in Days)
When you specify a number in this eld, the system subtracts this number from today’s date to calculate a cut-off date.
The system then deletes records created before the cut-off date.
The system prevents you from deleting critical information. Regardless of the deletion conditions, the system ensures the
following information is never deleted:
The last attempt to replicate an object.
This attempt may have succeeded or failed.
The last successful replication of an object.
Successfully replicated objects have a status of PO (Message Posted).
For more information see Display of Object Replication Status - SAP Easy Access.
Specifying Run Options
Under Run Options, you can choose the following options for running the report:
Count Records Only
If you select this checkbox, a status message displays after you run the report. This status message shows the number of
records that would be deleted if a run option of Delete Records Immediately was selected.
Delete Records Immediately
The object replication log shows a statusPO (Message Posted) when objects are successfully replicated.
Activities
To delete object replication status records from the SAP Easy Access menu, go to Cross-Application Components
Processes and Tools for Enterprise Applications Master Data Governance Data Replication DRFRSDEL - Delete Object
Replication Status
5/19/2023
Key Mapping
Use
You can use this function to create mappings between object instances by connecting their object IDs.
In business processes with several systems, each object instance requires one or more object IDs to ensure it can be identi ed
and mapped to other object instances. During data replication, the object instance is replicated from a central system to one or
more target systems. In the process, each system can use its own logic to create object IDs.
Features
Creation, Editing, and Deletion of Key Mapping information
To create, change, or delete key mapping information, you can complete the following actions:
Use the Create and Edit Key Mapping Web Dynpro application
For more information, see Creation, Editing, and Deletion of Key Mapping Information.
Call the key mapping Application Programming Interface (API) within your programs.
Direct Access to Key Mapping Information
To access key mapping information directly, you can complete the following actions:
Use the Search Key Mapping Web Dynpro application.
For more information, see Searching of Key Mapping Information.
Call the key mapping Application Programming Interface (API) within your programs.
Remote Access to Key Mapping Information
You can access key mapping information from the central registry of a client system. This is only possible if, in Customizing, you
have de ned a business system as a central registry for each business object that uses key mapping.
When you access key mapping remotely, you have the following options:
Extending key mapping for an existing object
With this option, you must de ne an object ID type and you may have to de ne an object node type for the object ID type.
Using key mapping for your own business objects
With this option, you must de ne an object ID type and an object node type for the object ID type.
 Note
You can apply the relevant settings in Customizing for Master Data under General Settings Key Mapping Customize
Business Objects for Key Mapping .
More Information
For more information about data replication, see Data Replication.
5/19/2023
Manage Key Mapping
Use
You use this application to create, edit, or delete key mapping information for object instances, by creating, editing, or deleting
records in mapping groups.
A mapping group speci es the key mapping data for object IDs that are mapped to each other. Each mapping group includes an
object type, a business system, an object ID type, and an object ID. Each object instance can have one or more object IDs.
Prerequisites
You have de ned mapping groups.
To facilitate data entry, we recommend that you sort long lists by object type.
Features
You can search for and then modify a key mapping group.
To search for the key mapping group, you specify details for one record. The search returns the record (if it exists) and all object
instances whose object IDs map to the object ID you speci ed.
 Note
A search that returns 0 records is valid. You can create a new mapping group based on the search criteria
Activities
1. Search for a mapping group by specifying the following details about one record in the mapping group: object type,
business system, object ID type, and object ID.
A list containing 0-n rows of object instances whose object IDs map to the object ID you searched for is displayed. If the
list contains 0 rows, an information message states that key mapping data does not exist for the selected ID.
2. Add, edit, or delete rows. For details, refer to the table below.
Action Description
5/19/2023
Action Description
Add Choose the Add Row button and add the relevant information.
When entering data for new rows, note the following:
If several rows refer to the same object, we recommend

you give them the same number
This ensures key mapping data is consistent. You can

overwrite the auto-generated numbers.
If you add a row that refers to an object ID that is

already mapped to other object IDs, the system adds
extra rows for all of the mapped object IDs.
This only happens after you choose the Save push

button.
For example, suppose object ID B is already mapped to

object ID C. If you map object ID A to object ID B,
object IDs A, B, and C all become part of the same
mapping group.
Edit To edit key mapping data, overwrite the cell data where this is
allowed.
Delete To delete key mapping data, select a row and choose the Delete
Row push button. If you delete all rows for an object, the
complete object is deleted from the key mapping database.
3. Choose the Save push button.
Search Key Mapping

Use
You use this application to search for examples of key mapping between the ID values of object instances.
Features
You can search for key mapping information using any combination of the following elds:
Object Type
Object ID Type
Business System
ID Value
The search output is shown in the table below.
Work list Description
Main Work List Displays key mapping records that match your search criteria.
Selected Objects
5/19/2023
Work list Description
Detail Work List Displays key mapping records for all ID values that are mapped to
the ID value in the Selected Objects work list. The contents of the
Existing Key Mappings for <Object Type> (<Object Type
list comprise a mapping group.
Description>) / <Object ID Type> (<Object ID Type Description>)
/ <Business System> / <ID Value>
Data Transfer
Use
Data transfer represents a collection of functions and features that enable you to move master data and mapping information
between systems and clients. Examples of these systems include existing ERP systems and your Master Data Governance hub
system. To transfer master data and mapping information, follow this process:
1. Export the master data and mapping information from the source system to an XML le. This le rests on your
application server.
2. Copy the XML le from the application server of the source system to the application server of your target system.
3. Import the master data and mapping information to the target system.
The master data governance business functions for supplier and customer support the export, import, monitoring, and
conversion of business partner data and key mapping information. The Master Data Governance for Material business functions
support the import and monitoring of material master data and key mapping information. As of SAP MDG 7.0, it is possible and
recommended to use Data Transfer functions to import and export the following master data objects:
G/L Account
Company
Cost Center
Cost Element
Pro t Center
 Note
For all other nancial master data objects, the File Upload and File Download functions need to be used when transferring
data.
Features
Import and Export Master Data
This is a two-step process. You start by exporting master data from a source system to an XML le, which is stored on an
application server. You then import the master data into the target system. For more information, see Importing Master
Data and Exporting Master Data.
Monitor Master Data Transfer
You can monitor the import and export of master data using the Monitor Data Transfer function. For more information,
see Monitor Data Transfer.
5/19/2023
Exporting Master Data
Context
You can use the Export Master Data service to extract data from your source systems. You can choose to export supplier
master data, customer master data, key mapping information, or value mapping information. To use this service select the
Export Master Data iView under the Data Transfer workset.
The Export Master Data service extracts data into an XML le. The structure of this XML le corresponds to the service
interface Import Master Data.
Procedure
1. On the SAP NetWeaver Portal or SAP NetWeaver Business Client, open the Export Master Data service. You can also
access the screen using transaction DTEXPORT.
2. In the Export Settings section, use the Object Type drop-down menu to choose the Object Type you want to export.
You can export supplier master data, customer master data, key mapping information, or value mapping information.
3. In the Description eld, enter a description for your export.
This description can be searched for in the data transfer log and on the Monitor Data Transfer screen.
4. Choose or create a variant. The variant is a bundle of selection criteria for data export.
If you have stored selection criteria in a le you can upload it here by choosing the Import Values button. The le must be
saved in tab-delimited text le format with the data contained in a single column. You can add reference data to your
export by choosing additional object to export from the Add. Objects eld. This reference data can be used for value
mapping.
5. If required, select the Delta Export checkbox.
If you select a delta export then the system only takes data that has changed since the last export that used the same
variant.
6. In the Technical Settings section, choose the method you want to use to export the data from the Communication
Channel drop-down menu.
You can choose to write to a le (or les) or to call a SOA service in the target system. If you want to extract data to a
le, you must create a logical directory (target directory) on the application server and map it to a physical directory
path.
All les extracted to the application server le system using the Export Master Data service are placed in this directory.
If you have chosen to write to le you must enter a target directory in the Target Directory eld. For more information
on logical directories see the documentation for the customizing activity De ne File Source and Archive Directories for
Data Transfer.
 Note
If you have selected the communication channel Service, no XML le is created physically on the local or application
server le system. In this case, a SOA message is created, which can be consumed by a service inbound proxy.
7. If you have chosen to export using les then you can choose your own le pre x to make locating and identifying les
easier.
8. In the Package Size eld enter a package size.
The package size represents the number of supplier master data records allowed in a single le. If you choose a package
size of 100 and export 1000 records then the system creates 10 les. This is only valid for supplier master data and
customer master data. You do not need to enter a value here if you are exporting key or value mapping information.
5/19/2023
9. In the Target System eld, use the input help to select a target system.
You need to choose a target system if you want to perform value mapping during the master data extraction process or
if you want to export value mapping information. You must create the mapping in advance in the source system using the
Maintain Value Mapping (Transaction VMIMG) Customizing activity.
10. In the Scheduling Settings section, select whether you want to import now or at a future date.
11. In the Parallel Processing Settings section, select the checkbox if you want to use parallel processing to speed up the
export.
Note that there should be a queue name pre x set up already for your exports. You should use this pre x when naming
your queue so that the queue will be executed automatically. If you do not have the queue set up you will have to
manually trigger the processing. For more information on setting up queues, see the con guration documentation.
12. To see how many records you have selected for export, choose the Number of Selected Objects button.
Dependent records may also be included in your export so this allows you to check the exact number of records you are
exporting.
13. Choose the Export Data button to run the service.
14. To monitor your export choose the Display Monitoring button. This opens the Monitor Data Transfer service where you
can supervise your export. For more information, see Monitor Data Transfer.
Results
You have successfully created a run to export your master data from your source systems.
Importing Master Data
Prerequisites
You have prepared your le for import in IDoc-XML format. Supplier and Customer information can also be imported in SOA
message format.
Context
You can use the Import Master Data service to import les containing supplier, customer, material, and classi cation data to
the Master Data Governance system. You can also import key and value mapping information. The data from these les can
update existing master data records or create new ones using the options available in the Import Master Data service.
We recommend that you import the classi cation data for a material together with the material data. We also recommend that
you import the business partner relationship data with the business partner data.
The Import Master Data and Export Master Data services use the same XML tag structure in their les. You can run a sample
export from the Export Master Data service and view the resulting le to determine the tag structure for importing key and
value mapping information that you have created outside the MDG hub.
Procedure
1. On the SAP NetWeaver Portal or SAP NetWeaver Business Client, open the Import Master Data service. You can also
access the screen using transaction DTIMPORT.
2. In the Import Settings section, select an object type to import, enter a description for the import run, and choose
whether or not to overwrite existing data with information from the import. Business partner, supplier, and customer
imports automatically overwrite existing records. This cannot be changed.
If you have set up a custom le converter in Customizing, you can select it here.
5/19/2023
3. In the Governance Settings section, choose whether or not you want to use governance for your import.
If you choose not to use governance, the objects are imported directly to the active area and you must choose a post
processing type. If you select governance, data is imported to the staging area using change requests. The post
processing settings are determined by your change request type.
 Note
You use the post processing settings to determine where to send objects that contain errors. If you choose change
requests, the system sends the objects with errors to the staging area where you can work on them. If you choose
manual post processing, the records with errors are sent to either IDoc handling, if the import was done using IDoc-
xml, or forward error handling, if the import was done using SOA message.
To access forward error handling use transaction /SAPPO/PPO2. In the Business Process eld enter BP_BUPA001 for
business partner and BP_RELSOO1 for business partner relationships. In the Order Assignment eld enter 2 if you
are not already assigned as a processor. To reduce the number of records selected, enter a date in the Created On
eld.
4. In the Scheduling Settings section, select whether or not you want to import now or at a future date.
5. In the Parallel Processing Settings section, select whether or not you want to use parallel processing to speed up the
import.
Note that there should be a queue name pre x already set up for your imports. You should use this pre x when naming
your queue so that the queue is executed automatically. If you do not have the queue set up, you have to manually
trigger the processing. For more information on setting up queues, see the con guration documentation.
6. In the Data Sources section, choose the Add button and select an object type. In the Source Directory eld, use the
input help to select a source directory for the import. You can use the Show Directory Content button to preview the
les stored in a selected source directory.
7. To test your import, choose the Simulate Import button.
8. To execute your import, choose the Import button.
Results
You have successfully created a run to import your master data into the Master Data Governance system. After the successful
import of the les into the system, the les are moved automatically from the selected source directory into the archive
directory. The les in the archive directory should be deleted manually in order to free disk space.
To monitor your import or simulated import choose the Display Monitoring button. This opens the Monitor Data Transfer
service where you can supervise your import. For more information, see Monitor Data Transfer.
Monitor Data Transfer
Use
You can use this function to oversee the transfer of master data between source and target systems. This function enables you
to view a list of import and export runs, to navigate to detailed information about objects within those runs, and to navigate to
the logs for a given run. You can access the function through the SAP NetWeaver Portal, the SAP NetWeaver Business Client, or
by using transaction DTMONITOR.
Activities
You can view a list of runs by making a selection in the Search Criteria section and choosing Search. You can limit search
results by entering a number in the Maximum Number of Results eld.
5/19/2023
You can save your common searches by entering the search criteria, entering a description in the Save Search As eld,
and selecting the Save button. Saved searches appear in the Saved Searches dropdown menu.
You can export your search results to a spreadsheet by choosing the Export to Spreadsheet button. The information in
this spreadsheet can also be used as export criteria in the Export Master Data application.
You can navigate to detailed information about objects within a given import run by selecting the run and choosing Show
Details. This opens a screen containing detailed information about the transfer of the objects within the run, including
any error information. The screen also contains a breakdown of the transfer status by object and by le. You use this
screen to quickly identify les or objects with errors and export information on the objects with errors to a spreadsheet
for further examination.
You can navigate to the log for a run, by selecting the link for the run in the Run Number column.
Example
John Miller is a master data steward in a company that uses Master Data Governance (MDG) to maintain its material master
data. He wants to check the status of his latest import of material records into the MDG hub system.
John opens the Monitor Data Transfer service, enters a combination of his own user and the material object type as search
criteria, and executes the search. Since he makes this search every week John saves the search for easy access later. John’s run
appears in the Results List, and he notes that the run has completed successfully.
John wants to check the status of the individual records within the run so he selects the run and chooses the Show Details
button. The detailed information screen shows that a number of the records were not imported. John exports the detailed error
information to a spreadsheet for further analysis.
Parallel Change Requests

Creating More Than One Change Request in Parallel for One Business Object
Since change requests are disjoint you can process change requests separately. You can activate or reject one change
request independently from process results of other change requests for the same business object. Therefore you need
to process entity data that belongs together in one change request. Changes of a business object in one change request
are not visible in another change request for the same business object.
Scope on Entity Type Level
You can edit business data of one business object in several parallel change requests with a special change request type.
You can con gure these change request types in the Customizing activity Create Change Request Type under Master
Data Governance General Settings Process Modeling Change Requests .
For each parallel change request you need to con gure the scope on entity type level to de ne which parts of a business
object can be edited with a certain change request type. For this change request type scope de nition there is a BAdI
(CHECK_CREQUEST_TYPE_SCOPE) for the MDG applications to inform you which entities need to be potentially in scope
in addition to the already selected entity types.
 Note
Derivations
A change in one entity may result in a cross derivation of another entity of a different entity type. Both entity types
need to be part of the entity type scope.
The setting of the indicator for parallel change requests and the setting of the entity type scope are irreversible, once
there is an existing change request in your productive system. This implies also that the consistency of the business
5/19/2023
object of each change request has to be guaranteed. The checks consider only the active and inactive data that belong
to the change request.
Interlocking
As in non parallel change requests the whole business object is interlocked by a change request using the object list, in
parallel change requests the object list only registers the business object but does not interlock it. Interlocking is done on
entity level by creating, changing or deleting the entity of a business object. For this purpose the change list has been
introduced for interlocking entities of business objects. The change list contains the entities that are changed with a
change request.
Checks
The system checks entity data according to the con guration in the Customizing activity Con gure Properties of Change
Request Step under Master Data Governance General Settings Process Modeling Change Requests .
The system checks on object level on the basis of the entity data assigned to the change request. Using non parallel
change requests you can check the whole object including all its changed entities. Using parallel change requests you can
check the whole object on the basis of only those changed entities of the assigned change request.
Deletion of Entities in Parallel Change Requests
Dependent entities of a deleted entity are deleted and interlocked.
 Example
Example 1: If you want to delete an entity in one parallel change request, you cannot create a dependent entity
for that deleted entity in another parallel change request.
Example 2: If you have created a dependent entity to a parent entity, you cannot delete the parent entity in
another parallel change request.
Activating and Rejecting Parallel Change Requests
There may be inactive data that belongs to several change requests. When you activate one change request then the
system only activates inactive data of a business object that belongs to that change request. The same applies for
inactive data of a business object in a rejected change request.
Parallel change requests can be used for the following MDG applications:
Master Data Governance for Custom Objects
Master Data Governance for Material
Master Data Governance for Business Partner
Master Data Governance for Supplier
Master Data Governance for Customer
Highlight Changes
Use
 Note
5/19/2023
7.0.
In the single-object processing UI, saved and unsaved changes are highlighted in different colors. This means you can quickly nd
the particular changes that you need to check and approve.
Features
To support the processor of a change request in identifying the requested changes to a business object, the system highlights
elds with changed data in the following way:
Highlighting of Saved and Unsaved Changes
The system shows saved changes and unsaved changes in two different colors on the UI. If you create an object, the
system highlights unsaved changes but no saved changes. If you change an object, the system highlights unsaved
changes and those saved changes that have a different value to the active value. If you change an edition-based object,
the system uses the active value either from the validity timeframe of the change or from the previous validity
timeframe. If the business object did not exist before the validity timeframe to which the change refers to or if the object
was deleted in the previous validity period, the system highlights unsaved changes but no saved changes.
After you have deleted an already existing active object, the system displays the deleted objects and highlights unsaved
and saved deletions. You can discard the deletion of those objects. If you want to discard the deletion of dependent
objects you need to discard the deletion for each dependent object separately.
Highlighting of Table Rows
The system highlights table rows referring to changes that you can only see after navigating from a table row to the
details of a dependent entity.
You can distinguish new rows, changed rows, and deleted rows in a table.
Tooltip Information
The tooltip of the eld shows the previous value. If you change a value several times before saving it, the tooltip displays
the active value and the last saved value.
The tooltip of a deleted eld shows the active value of the deleted object.
 Note
The following elds and single-object processing screens do not provide the highlight changes function:
Fields of the UI building block (UIBB) for the change request header data and the elds of the UIBB displaying the
time validity for edition-based entities
Fields with processing information that are changed by the system, for example elds with audit information
Fields of nalized change requests
Fields and table rows displayed when processing cleansing cases
The Web Dynpro application USMD_ENITITY_VALUE2
The Web Dynpro component Set Maintenance (USMD_SET)
Deleted inactive objects that have not been active before.
Activities
5/19/2023
To activate this function, set the highlight changes indicator in the view User Interface per Change Request Step of Customizing
activity Con gure Properties of Change Request Step under General Settings Process Modeling Change Requests .
To change the default color for highlighting for saved changes, set the parameter MDG_HC_COLOR_SAVED in your pro le with
transaction SU3. To change the default color for highlighting for unsaved changes, set the parameter
MDG_HC_COLOR_UNSAVED. Colors that can be used are listed in the following table:
Color ID Color Name
68 aqua
41 black
61 blue
62 blue gray
75 bright green
49 brown
53 dark blue
51 dark green
56 dark red
52 dark teal
58 dark yellow
73 gold
79 gray 25%
71 gray 40 %
63 gray 50 %
55 gray 80 %
59 green
54 indigo
86 lavender
69 light blue
83 light green
65 light orange
84 light turquoise
82 light yellow
66 lime
50 olive green
57 orange
85 pale blue
72 pink
5/19/2023
78 plum
64 red
80 rose
67 sea green
77 sky blue
81 tan
60 teal
76 turquoise
70 violet
87 white
74 yellow
To disable the highlighting of changes, set the user parameter MDG_HC_DISABLEto X in your pro le with transaction SU3. To
disable the highlighting of unsaved changes set the parameter MDG_HC_COLOR_UNSAVED to OFF. If you only want to see the
unsaved changes highlighted set the parameter MDG_HC_COLOR_SAVED to 00 (transparent color).
The colors and the activation of the highlight changes function can also be set in the con guration of the used MDG Web Dynpro
application, for example USMD_OVP_GEN, using the same parameters MDG_HC_DISABLE, MDG_HC_COLOR_SAVED, and
MDG_HC_COLOR_UNSAVED.
 Caution
The highlight changes function uses the tooltip to inform the user about the previous value. This is not possible if a xed
value for the tooltip is either entered in the UI con guration or in the UI customizing. In this case, the xed value is displayed.
Obsolete Web Dynpro Applications

With MDG 7.0 the following Web Dynpro applications are obsolete. It is recommended to use their functional equivalent.
Use
 Note
With MDG 7.0 this Web Dynpro application is obsolete. It is recommended to use the equivalent Web Dynpro applications for
single-object processing.
You use this Web Dynpro application (USMD_ENTITY_VALUE2) to process a speci c entity (for example, to create a new
account) and change its master data.
Prerequisites
To process changes, you need a change request, which is used to approve and track the changes, and you must be the
current processor. If you are not the current processor, you can only display the data.
5/19/2023
If this Web Dynpro application is called from an iView for which the parameters PROCESS=<name of business activity>,
EDITING_MODE=CREATE, and IS_CREQ_MODE=X are lled, the process for creating a change request is started automatically.
For more information, see Setting Up New Business Activities.
Features
The Web interface is dependent on the selected UI con guration that you have speci ed in Customizing for Master Data
Governance under General Settings UI Modeling Edit UI Con guration .
For more information, see Managing of UI Con gurations.
The data of the inactive version appears in display mode. To display the data from the active version, choose Switch to Active
Version.
Choose Related Services to call the following functions from this Web Dynpro application:
Where-Used List
Copy
Change Request
More Single Processing
Business Context Viewer in Single Processing
Use
 Note
With MDG 7.0 the Web Dynpro application USMD_ENTITY_VALUE2 is obsolete. It is recommended to use the equivalent Web
Dynpro applications for single-object processing.
In SAP Master Data Governance, you can link the Business Context Viewer (BCV) to a Web Dynpro application such as
USMD_ENTITY_VALUE2 and use it for single processing of master data objects. This connection enables you to display
additional data of the master data object that is currently undergoing single processing. For more information about single
processing of master data objects, see Single Processing of an Entity.
The Business Context Viewer is a Web Dynpro ABAP application that provides analytic functions to other applications. For more
information about the functions of BCV, see Business Context Viewer.
Prerequisites
You have activated the Business Con guration Set (BC Set) MDGAF_BCV in the transaction SCPR20.
Activities
1. Select a UI con guration for single processing in Customizing for Master Data Governance under General Settings UI
Modeling Edit UI Con guration . Then choose Edit.
5/19/2023
2. In the application con guration, choose Continue in Change Mode. Enter /BCV/SIDEPANEL_20 in the Con guration ID
of Side Panel eld and save the application con guration.
3. Now, choose Side Panel in the Web Dynpro application USMD_ENTITY_VALUE2 to use the BCV functions.
Example
You have added the BCV side panel of the Web Dynpro application My Change Requests (USMD_EDITION_CREQUEST). To use
the BCV side panel, open the service map and choose My Change Requests (USMD_EDITION_CREQUEST). Specify a time period
and choose Side Panel. Now you can use graphics that re ect the following evaluations in the evaluation list:
My Change Requests
Select a graphical display type, for example, a pie chart. Furthermore, you can display the side panel on your entire screen and
display a combination of graphics and tables.
More Information
For more information, see Enabling Detailed Analysis of Change Requests.
Search for Entities
Use
 Note
With MDG 7.0 this Web Dynpro applications is obsolete. It is recommended to use the equivalent Web Dynpro application
Search Business Object.
You use this Web Dynpro application (USMD_ENTITY_SEARCH) to nd objects of entity types.
 Example
If you want to nd an address, you can search by the eld contents of the address elds.
Prerequisites
If you want to change the default settings for nding entities (for example, to enter different search criteria), you have created
and activated an implementation of BAdI: Search of Entities (USMD_SEARCH) in Customizing for Master Data Governance
under General Settings Data Quality and Search Business Add-Ins .
If you want to use a fuzzy search and/or a free text search for shipped or custom search types, you have con gured the
relevant settings in Customizing for Master Data Governance under General Settings Data Quality and Search De ne
Search Applications .
Features
We provide the following search types to nd master data in the staging area and the active area:
Database search
5/19/2023
This search identi es master data in de ned elds.
 Note
The following searches support the fuzzy search and free text search in addition to the eld-speci c search.
Enterprise search
This identi es master data in customer-speci c business objects.
Address search
This identi es address data based on Business Address Services (BAS).
The system displays a separate input screen for each search service, on which the search criteria relevant for the search type
are already entered (for example, if you search for an address, standard address elds such as the postal code and street are
lled).
Form-Based Change Request Processing
Use
 Note
With MDG 7.0 form-based change requests, including the Web Dynpro application USMD_ISR_PROCESS, are obsolete.
Instead, use the Web Dynpro applications USMD_OVP_GEN and MDGF_OVP_GEN to create exible UIs for single-object
processing. For more information, see Creating User Interfaces for Single Object Processing.
You use this Web Dynpro application (USMD_ISR_PROCESS) to process a change request for a single entity. Data is displayed
and changed in a form.
Prerequisites
You have created a scenario in Customizing for Master Data Governance under General Settings Process Modeling
Change Requests Form-based Change Requests Edit Scenario for Form-based Change Requests . This speci es
which form is used for the form-based change request as well as which elds are displayed in the form.
If input help is required for the individual elds, you have de ned the OVS input help in Customizing for Master Data
Governance under General Settings Process Modeling Change Requests Form-based Change Requests
Con gure OVS Input Help for Form-based Change Requests .
A change request has been created with a change request type for form-based change requests.
For more information about creating change requests, see Creation of a Change Request.
Features
 Note
Some of the following functions are available only if permitted by the change request status and if you are currently the
change request processor.
Processing General Change Request Data
5/19/2023
You can add or change general data for the change request, such as its name or priority.
Calling Additional Functions Using “Related Services”
Change Documents
Where-Used List
Work ow Log
Replication Log
Adding Notes and Attachments
You can add comments and les or hyperlinks to additional information to a change request.
Running a Validation and Displaying the Validation Log
To check the consistency of the speci ed changes to the master data, you can validate the change request and display a
validation log.
 Note
You can create validation rules in Customizing for Master Data Governance under General Settings Data Quality and
Search De ne Validation and Derivation Rules .
For more information about de ning validation rules, see De ne Validations and Derivations.
Activities
If you are the current processor of the change request and you have nished your part of the processing of the change request,
you forward the change request to the next processor via work ow functionality. Depending on the status of the change
request, the following options are available:
Approve
Reject
Agree
Disagree
Withdraw
Finalize Processing
Send for Revision
Request Again
Financials
Use
You can use this component to request, approve, and execute changes to the data, as well as replicate those changes to
decentralized systems by means of enterprise services. You can in uence the ow of this process by selecting a work ow. The
5/19/2023
available work ow templates can be found under Work ow Templates for Financials.
Features
The management of master data usually follows the pattern below:
1. You create an edition (see Processing of an Edition).
 Note
If you are using Master Data Governance for Financials for the rst time, you can use the File Upload function to
populate your database tables.
2. You create a change request (see Creation of a Change Request).
3. The change request undergoes an approval procedure. You can use the function Processing of a Change Request.
4. You execute the master data change (see Master Data Processing).
5. You replicate the changes (see Data Replication).
Internal Orders
MDG for Financial data (MDG-F) helps your nancial organization to get to nancial close. MDG provides the means to centrally
create nancial entities and to distribute these entities to decentral systems. Therefore, you can be assured that these entities
are consistently used across all nancial systems, such as operational systems, planning, reporting, or nancial consolidation
systems.
To date, the entities G/L Account, Cost Center, Pro t Center, Cost Element, and relevant Hierarchies are covered in MDG-F.
Internal Order governance in Controlling is a high requirement and with this release it is now possible.
Initial Load of Internal Order
Whenever a new system is connected to the MDG hub (or when the MDG is setup for the rst time), internal order data can be
extracted from the client system and imported into the MDG hub.
Central Governance and Replication of Internal Order
An Internal Order is created or changed centrally in the MDG hub. The requested changes are collected in a Change Request. All
changes are following a Governance process which can be con gured by our Customers (for example, with the four-eyes
principle). After the approval of the Change Request the data is stored in the MDG generated staging area on the hub and
replicated to all connected client systems based on a replication model.
Multiple Internal Order Processing
Users can use MDG Mass Change application to change internal order data, use File Upload application to upload new internal
orders or change existing internal orders in MDG, use File Download application to download internal order data into les.
More Information
For more information on the con guration of MDG for Financials, see Con guring Master Data Governance for Financials.
Request Pro t Center
5/19/2023
Use
With this app you can request a new pro t center for an organization. This app is easily accessible for a general user with limited
knowledge of master data governance.
Key Features
Use the lean requestor form for a user new to MDG
View an automatically generated list of potential duplicates
You can customize the Duplicates button to display the + sign when a certain number of duplicates are found (for
example, 20+).
Use the Track My Requests UI to track the request status
Upload attachments containing request details
When you upload an attachment, the Reason for Request eld is automatically lled with the text
Check attached documents.

Desktop
Tablet
Smartphone

Request Cost Center
Use
With this app you can request a new cost center for an organization. This app is easily accessible for a general user with limited
Key Features
Use the lean requestor form for a user new to MDG
See an automatically generated list of potential duplicates
example, 20+).
Use the Track My Requests UI to track the request status
Upload attachments containing request details
5/19/2023

Desktop
Tablet
Smartphone

Material
Master Data Governance for Material enables you to monitor and control the creation, editing, and deletion of material master
data.
Below you nd a simpli ed sample work ow for material creation or change. The work ow follows the request from the business
user who triggers the change request, to the master data expert (usually the Master Data Steward) who reviews the change
request, back to the business user who may need to make changes, and nally back to the master data expert for nal approval.
Following this work ow the system will update or create the appropriate material master record.
Sample Work ow for Material
Logical Representation of the Sample Work ow
5/19/2023
Change Request Processing

The change request processing documents outline the functions and processes used for creating and processing change
requests. During a typical work ow a user might rst search for and display materials, then generate change requests to
create, change, or mark materials for deletion depending on their requirements. The user can also update multiple materials at
the same time using the Create Change Request and Mass Change services.
The user does not actually create, change, or mark materials for deletion here; instead they create change requests that, in a
typical work ow, are sent for approval by a master data expert. Once the expert approves the change request, the system
performs a validity check, and if there are no errors the new or updated material data is written to the active area. During the
change request process the new or changed master data is stored in the master data governance staging area.
The change request worklist provides the user - either a normal user or a reviewer - with a list of work items to be considered.
The user typically opens a work item in the Change Requests screen from which he can activate the change request, reject the
change request, validate the change request data, view the validation log, forward the change request, or perform a duplicate
check. The user can also access the BCV side panel to view additional information for the change request. For more information,
see Con guring Business Context Viewer for MDG Material.
The steps in a typical work ow are outlined below:
1. The user creates a change request and the data in the change request is written to the staging area. The user may use
the duplicate check to have the system scan for duplicate master data entries.
2. The change request is sent to a Master Data Steward to review and approve.
5/19/2023
3. The Master Data Steward reviews the change request and either approves it or rejects it. The Master Data Steward has
the option to use the built-in duplicate check to have the system scan for duplicate master data entries. Note that the
duplicate check does not provide a ranking feature for the duplicate entries.
4. If the Master Data Steward rejects the change request it is sent back to the creator who can either discard the change
request or modify and resubmit it.
5. If the Master Data Steward approves the change request the system performs a validity check on the data contained
within it.
6. If the validity check comes back with errors then the change request cannot be activated. The Master Data Steward
must correct the errors.
7. If the validity check comes back without errors, the information in the change request is written to the active area and
the process is complete.
Search Material
Use
The Search service provides a exible UI for performing and reviewing searches. The UI enables you to view search results with
or without organization-level data.
The material search function enables you to search for and display materials based on speci ed criteria. The search criteria can
include material attributes, class characteristics assigned to the material, and the values for these material attributes and
class characteristics. You can search for materials in both the active and staging areas.
You can use a the Enterprise Search template for material to search by a large range of attributes including material, old
material number, classi cation, characteristic, and base unit of measure. Furthermore it allows you to search based on
organizational levels such as Plant, Sales Organization, and Distribution Channel. You can also search based on pre-de ned
MRP and Sales elds. Regardless of the search criteria selected the results list only displays one line for each material. From
the search results list you can choose to display, edit, replicate, create, or copy a material. You can also view change documents
for a material or start a mass change for several materials. The search service can take information from an inputted search
and use it as the basis for creating a new material using a change request.
Activities
You can use this function to carry out the following activities:
Restricting Search
Normally, the search application returns data from both the active and staging areas. If you select the Search Active
Data Only checkbox the system will only search within the active area. To conform to the general search standards for
MDG, this checkbox is deactivated as of MDG 7.0 SP2 (Feature Pack), if the business function MDG_MATERIAL_5 is
active.
Additional Search Lines
You can add or remove lines from your search using the Insert Line and Delete Line buttons.
Save and Load Searches
You can save a set of search parameters and load them for use at a later time.
Fuzzy Search
5/19/2023
By selecting the Fuzzy Search attribute and selecting the checkbox, you can activate fuzzy search logic for your
searches.
Maximum Number of Records
You can use the Maximum Number of Results eld to limit the number of records displayed.
Launch Follow-On Activities
You can use the search results screen to display a material or change request, open multiple-record processing, copy a
material, launch single material creation, or start mass material creation. You can also perform replication-related
activities.
The following points should be kept in mind when formatting your search:
If you specify multiple search criteria then the system returns only those materials that ful ll all the search criteria. For
example, you search for materials with a material attribute of Material Group with a value of 01, and a characteristic of
Color with a value of red. The system returns all materials with both a Material Group value of 01 and a Color
characteristic value of red.
If you choose to specify multiple values for one search criteria then the system returns all materials that contain at least
one of these speci ed values. For example, you search for materials with a characteristic of Clothing Type and the values
Shirt and Pants. In this case, the search returns all materials that are assigned to the classi cations Shirt, Pants, or
both.
Creating a Material
Prerequisites
You must have maintained a change request type for material creation and have set up your work ow for this change request
type.
Context
You can use the Create Material service to create a change request for material creation. This change request goes through
the predetermined work ow process and when complete results in the creation of a new material in the active area.
Procedure
1. Choose material ID and change request type
In the Material eld enter a material ID or leave it blank and the system will create a temporary ID that is changed to the
standard ID when the change request is approved. In the Change Request Type eld enter the change request type for
creating a material. Choose the Continue button to proceed.
If required, you can enter a plant assignment with or without a storage location. You can also enter a distribution chain
and warehouse assignment for the material. To create a plant assignment, enter a plant name in the Plant eld and
enter a storage location if required.
To create a distribution chain assignment, enter a sales organization and distribution channel in the corresponding elds.
To create a warehouse assignment, enter the warehouse number and storage type.
 Note
You can also select an existing material to use as a template to create your new material. You can select this
template material using the Material (Template) eld. In this case, the material data is copied to the new material,
5/19/2023
excluding organizational data.
If you want to copy organizational data to your new material then you need to specify a template plant and
distribution chains and warehouse assignments. You can only copy one plant and distribution chain or warehouse
assignment each time you launch the New Material screen. To copy multiple plants and distribution chains and
warehouse assignments, re-launch the New Material screen.
Copying multiple dependent organizational units is only possible when using the initial Create Material screen where
you specify your source and target organizational units. On the material change request UI, when you copy a selected
organizational unit you do not automatically copy its dependent organizational units.
You can control the elds that are copied by the copy function. To do this enter transaction OMSR, choose the Position
on Field Name button, then enter the eld (for example, MARA-MEINS) whose content you want to include or exclude
from copying. Double-click on the eld from the list and on the screen that opens select or deselect the Propose Field
Content checkbox. Save your changes and from now on the content from that eld will be copied or not copied
according to your new setting.
Flex entities and custom entities (which are not posted with function module MATERIAL_MAINTAIN_DARK) are
copied completely. All other entities which have only material and additional keys, but no data, are not created when
copying from active area to prevent a large maintenance status. They are copied when using an inactive material as a
template.
You also have the option to specify a change request ID and a template material. The inactive data from the speci ed
change request is then used as a template.
2. Enter change request details
In the General tab, enter a description for your change request in the Description eld. You can enter details for your
change request such as priority, due date, and reason. You can also add comments and attach relevant les directly or by
link if you wish.
3. Enter details for new material
In the Basic Data, Design Data, Descriptions, Basic Text, Dimensions, GTIN/EAN, Classi cation, and Internal Comment
sections enter the data for your new material.
 Note
If you navigate to the Classi cation section before choosing a material type the system derives a default class from
the default material type. If you have selected a material type, the system derives the default class from the selected
material type. Later changes to the material type will not automatically update the class assignments.
You need to enter a Material Type and Industry Sector in order to see all mandatory elds.
If you only want to maintain one EAN for a unit of measure (UoM), use the Dimensions section directly, as the EAN
you enter here is always the main EAN for the UoM, and is re ected in the main EAN ag in the GTIN/EAN section.
If you want to maintain multiple EANs for one UoM, use the GTIN/EAN section instead. Make sure you specify which
one is the main EAN so that the system updates the Dimensions records accordingly. If you do not set the main EAN
ag but there is only one EAN per UoM maintained in the GTIN/EAN section, the main EAN ag is automatically set
during activation.
4. Enter plant, valuation, distribution, and warehouse data
Enter plant, valuation, costing, distribution chain, and warehouse information in the appropriate sections. You can
change the selected plant in the Plants section. You can change the selected distribution chain in the Distribution Chain
section.
You can also copy one of the plants, storage locations, distribution chains, or warehouse assignments in these sections
to create multiple new plants, storage locations, distribution chains or warehouse assignments for this material.
5/19/2023
 Note
You can use these screens to add or remove links to DMS documents. It is also possible to create new DMS
documents. New documents are stored in the active area. DMS documents are not placed under governance.
5. Submit your change request
When you have con rmed your data entry click the Submit button to create the change request. To check the replication
status of your changes, enter the change request and choose the Replication Status button to see the current
replication status broken down by IDoc and system.
Results
The new change request for material creation is created and sent for processing according to the rule-based work ow you have
assigned to the create material process. Usually, this means that it passes to a Master Data Steward who reviews the changes.
During this time the new material is stored in the master data governance staging area and does not appear in the active area.
Once the Master Data Steward has approved the change request and technical validation has taken place, the new material is
written to the active area.
Changing a Material
Prerequisites
The material to be changed must exist in the active area and must not be locked by another change request. In the case of
parallel change requests the relevant entities must not be locked by another change request. You must have maintained a
change request type for material change and have set up your work ow for this change request type.
Context
You can use the Change Material service to create a change request for changing a single material. This change request goes
through the predetermined work ow process and when complete results in the change of the selected material in the active
area. Creating the change request copies the material to the staging area. A material can only be assigned to one active
change request at a time, so no new change requests can be created for a material that is already in the staging area. Parallel
processing of change requests enables multiple change requests for a single material. See Parallel Change Requests for more
detail on parallel processing.
 Caution
Avoid using the back-end system to change material master elds under governance. If you make changes to these elds
while the material is part of the change request process, all your changes to elds under governance are overwritten when
the change request is approved and not just those elds affected by the change request.
You will however receive a warning during validation that this data has changed and you then have the option of viewing the
changes made in the back-end system and incorporating them into your change request. You can then submit the change
request for validation again.
You can adjust the default behavior with SAP Note 1797009 . Implementing this note means that the system only
overwrites changes to entities present in the change request rather than all entities.
Procedure
1. Open the Change Material Service
5/19/2023
In the Material Governance work center, select the Change Material service.
2. Select a material
Enter a material ID in the Material eld or use the input help to choose one. In the Change Request Type eld enter the
change request type for editing a material. Click the Continue button to proceed.
You can also use the template feature to add a new plant assignment or distribution chain to the material at this point.
You cannot overwrite existing plant assignment or distribution chain data in this way.
3. Change to edit mode
To change the material to edit mode, choose the Edit button.
In the Change Request section, enter a description for your change request in the Description eld. You can enter details
for your change request such as priority, due date, and reason. You can also add comments and attach relevant les.
5. Enter changes and submit
Enter the changes you want to make to the material and click the Submit button to submit your change request.
Results
Your new change request is created and sent for processing according to the rule-based work ow you have assigned to the
change material process. Normally this means that it passes to a Master Data Steward who reviews the changes. Once the
change request has been approved and technical validation has taken place the changed material data replaces the existing
data in the active area. The material is no longer available in the staging area and can be included in new change requests. In
the case of parallel change requests the relevant entities are no longer available in the staging area and can be included in new
parallel change requests.
Creating a Change Request
Context
This service enables you to create change requests for the mass update of existing materials. Updating multiple materials is a
two-step process; you rst create a single change request for multiple materials using this service, then you use the Mass
Change service to enter the details for the changes you want to make.
Although you can enter the IDs for the materials you want to change in this screen, we recommend that you use the Mass
Change service to add the materials instead.
Procedure
1. Open the Change Request screen
Click the Create Change Request link to open the Create Change Request screen.
2. Enter general data
Enter a description, due date, priority, and reason for your new change request. Click the Next button to continue.
3. Enter a reason for the change
In the Explanation text box enter a reason for this mass change request. This eld is mandatory. You can also upload
attachments if required. Click the Next button to continue.
4. Specify materials for the change request
5/19/2023
To add materials to the change request, click the Specify Objects button. You can then use the input help in the elds of
Material column to add materials to the change request.
 Note
It is recommended that you use the Mass Change service to add materials later rather than at this point.
Click the Enter button followed by the Next button to continue.
5. Review
Check and review your new change request. Click Submit to create your new change request.
Results
A new change request has been created for the mass change of materials. Click the Close button to return to the Material
Governance work center.
Mass Change
Context
You can use this service to simultaneously change the attribute values for selected materials. You can change one or more
attributes for the selected materials, but each attribute must have the same new value. You can create a change request for
your mass change in advance or create it during the Mass Change process.
Procedure
1. Open the Mass Change screen
Select the Mass Change link from the Material Governance work center.
2. Select materials to include
Use the Selections list to choose the materials you want to include in your change request. Click the Next button to
continue.
 Note
While you can select materials in the Create Change Request service, we recommend that you use this screen
instead.
3. Re ne your selection
Use the Scope of Selection table to review your chosen materials and remove any materials you do not want to include
in your change request. Note that if a material you have selected already exists in the staging area, this change request
overwrites it. A warning about this overwrite appears when you attempt to execute the changes. Click the Next button to
continue.
4. De ne values
Choose the attributes you want to change and the value you wish to set them to. To do so, enter the new value in the
Replace With column of the attribute you want to change. This value is set for the attribute in each material you
selected. Note that only attributes available for mass change are visible on this screen. Click the Next button to
continue.
5/19/2023
Review your changes. If you are happy with them, click the Execute Changes button to submit your change request.
Results
Once the change is submitted, the following results are possible:
If all materials are already contained in existing change requests where you are the owner, those change requests are
modi ed and a warning message appears. If you are not the owner, an error message appears.
If none of the materials to be changed are contained in change requests, the systems asks you for the number of a mass
change request where you are the processor. You can create a mass change request with the Create Change Request
service. The materials are added to the new mass change request.
If some materials appear in an existing change request and some do not, the system asks you for a mass change request
number. When you enter the mass change request number, all materials that were not in a change request are added to
the mass change request and those that were part of an existing change request are modi ed using their own change
requests.
Once materials are assigned to a mass change request, it is usually sent to a Master Data Steward who reviews the changes.
During this time the materials are stored in the master data governance staging area. Once the Master Data Steward has
approved the change request and technical validation has taken place the changed materials are written to the active area.
Request Material
Use
With this app you can request a new material for an organization. This app is easily accessible for a general user with limited
Key Features
Lean requestor form for a user new to MDG
Automatically generated list of potential duplicates
example, 20+).
Track My Requests UI to track the request status
Option to upload attachments containing request details
If the long material number has been activated in your back-end system, it is automatically displayed in the Material eld in this
SAP Fiori app. For more information, see Extended Material Number in SAP Fiori Apps.

Desktop
Tablet
5/19/2023
Smartphone

Business Partner
Use
Master Data Governance for Business Partner enables you to monitor and control the creation, editing, and deletion of
business partner master data.
A typical work ow starts with a user creating or changing data and submitting the change request. A master data expert then
reviews the change request. In an additional step the initial user may need to make changes, and nally the master data expert
approves the change request. As a result the system updates or creates the appropriate business partner master record.

The following documents about change request processing outline the functions and processes used for creating and
processing change requests. During a typical work ow a user might rst search for a business partner, then generate a change
request to create, change, or mark a business partner for deletion, depending on his or her requirements. The user can also
change multiple business partners at the same time using the Create Change Request and Mass Change services.
The user does not actually create, change, or mark business partners for deletion; instead he or she creates change requests
that are sent for approval by a Master Data Specialist. Once this expert approves the change request, the new or updated
business partner data is written to the active area. During the change request process the new or changed master data is
stored in the master data governance staging area. See also: Master Data Governance for Business Partner: Specialist
change request, validate the change request data, view the validation log, forward the change request, or perform a variety of
checks.
the duplicate check to have the system scan for duplicate data as well as additional checks to ensure the consistency of
data.
3. The Master Data Steward reviews the change request and either approves it or rejects it.
If the Master Data Steward rejects the change request, it is sent back to the creator, who can either discard the
change request or modify and resubmit it.
If the Master Data Steward approves the change request, the information in the change request is written to the
active area and the process is complete.
 Note
5/19/2023
Any work ow step offers the possibility to perform checks either by choosing a Check button, by choosing Next to continue
or by choosing Enter. The extent of checks being performed at each work ow step, for example duplicate check, validity
check or required elds check are speci ed in the Customizing.
If a validity check or required elds check reports an error then the change request cannot be activated.
Search Business Partner
Use
The search business partner service enables you to search for and display business partners based on speci ed criteria. You can
use a large range of attributes to search including names, addresses, bank details and identi cation numbers. From the search
results list you can choose to display, edit, replicate, create, or copy a business partner.
Activities
The search offers the following possibilities:
Search Method
A variety of search methods offer sets of prede ned search criteria.
You can extend or reduce the number of search criteria if required using the Insert New Row and Delete Row buttons.
Fuzzy Search
Depending on the Search Method chosen a Fuzzy check box is offered.
Maximum Number of Results
You can use the Maximum Number of Results eld to limit the number of results displayed.
Number of Search Result Records
You can see the number of search result records, which includes blocked data related to business partner.
 Note
If you search for two or more different attributes then the search lters its results based on an AND logic.
When searching a single attribute for more than one parameter the search lters its results based on an OR logic.
Creating a Business Partner
Prerequisites
5/19/2023
You have maintained a change request type for business partner creation and have set up your work ow for this change request
type.
Context
You can use the Create Request service to create a change request for business partner creation. This change request goes
through the predetermined work ow process and when complete results in the creation of a new business partner in the active
area.
Procedure
1. Selecting the business partner category
In the Search business partner section, choose New and then select organization or person or group.
for your change request such as priority, due date, and reason. You can also add comments on the Notes tab and attach
relevant les using the Attachments tab.
3. Enter details for new business partner
In the business partner Details section, enter the data for your business partner. You can enter details for your change
request such as general data, organizational data, address data and communication data.
 Note
You can check your entries choosing theCheck button. Depending on the data entered an Address Validation dialog
box is displayed, asking for further input. If similar business partner data already exists in the system a duplicate
check dialog box will inform you about the potential duplicate. We recommend to start creating a business partner
with the Search Business Partner function.
4. Enter additional data for new business partner
Enter further data for your business partneIn in the sections provided below.
When you have entered your data choose the Submit button to trigger the work ow. As the rst step the checks as
mentioned above will be performed.
 Note
To save the change request for use at a later time choose Save.
Results
The new change request for business partner creation is created and sent for processing according to the work ow you have
assigned to the create business partner process. Usually, this means that it passes to a Master Data Steward who reviews the
changes. During this time the new business partner is stored in the master data governance staging area and does not appear
in the active area. Once the master data steward has approved the change request and technical validation has taken place,
the new business partner is written to the active area.
Enriching a Business Partner

 Restriction
5/19/2023
As of Q1 of 2021, the SAP Data Enrichment service is not available for purchase. Existing customers can continue to use SAP
Data Enrichment until the end of their license term.
Use
By integrating with SAP S/4HANA Cloud for data enrichment, you can enrich your existing business partner with data from
external data providers. This eliminates or reduces the costs and efforts involved with manual data creation and maintenance.
You can use these integration features with the Change Request app.
Prerequisites
You have con gured data enrichment integration as described in Data Enrichment Integration.
You have maintained a change request type for business partner creation and change.
You have set up your work ow for this change request type.
You have speci ed BP Enrichment as relevant in enhancement spots and checks using the Change Request step view. To
do this, use the Customizing activity Master Data Governance, Central Governance General Settings Process
Modeling Change Requests Con gure Properties of Change Request Step .
You have activated the following event type linkages:
Object Type: BUS2250, Event: ACTIVATED , Receiver Type: ACTIVATED_DE
Object Type: BUS2250, Event: ROLLED_BACK , Receiver Type: ROLLED_BACK_DE
To do this, use the Customizing activity Master Data Governance, Central Governance General Settings Process
Modeling Work ow Activate Event Type Linkage
You have added the Data Enrichment UIBB in the Change Request app by choosing Personalize Change Layout
Add Data Enrichment .
Procedure
1. Select the business partner category.
In the Search Business Partner section, choose New, and select Organization. Note that you can enrich data only for
business partner type Organization.
2. Choose Create Business Partner.
3. Enter the details of the new business partner.
In the Change Request section, enter a description for your change request in the Description eld.
In the Business Partner Details section, enter Name1, Country, and City. These are the mandatory elds for data
enrichment.
4. Check your entries by choosing the Check button. Depending on the data entered, a dialog box is displayed with
matched records from data enrichment.
5. Choose Continue to view details of the matched records. Another dialog box opens with the eld level data from data
enrichment.
6. Select the data you want to import, and choose Enrich. The system navigates back to the business partner screen.
7. Make sure that the Address, Identi cation Numbers, and Data Enrichment blocks are lled correctly.
8. If required, enter additional data for the new business partner.
9. Choose Submit to trigger the work ow.
5/19/2023
Key Mapping
Key mapping is maintained between MDG and data enrichment systems for Business Partner ID and Data Enrichment ID. You
can view the key mapping information in the Data Enrichment UIBB.
Changing a Business Partner
Prerequisites
The business partner to be changed exists in the active area and is not locked by another change request.
You have maintained a change request type for business partner change and have set up your work ow for this change
request type.
Context
You can use the Change Request service to create a change request for changing a single business partner. This change request
goes through the predetermined work ow process and when complete results in the change of the selected business partner in
the active area. Creating the change request copies the business partner to the staging area. A business partner can only be
assigned to one active change request at a time, so no new change requests can be created for a business partner that is
already in the staging area.
 Caution
If you use the back-end system to make changes to a eld in the BP data model while the business partner is undergoing the
change request process, when the change request is approved, all your changes will be overwritten and not just those elds
affected by the change request.
Procedure
1. Select a business partner in the Search Business Partner result list
In the Search business partner service, select a business partner in the result list.
2. Select data block and change to edit mode
To change the business partner to edit mode, choose the Edit button offered at the corresponding data block.
In the Change Request section, enter a description for your change request in the Description eld. For further details
see the corresponding section in Creating a Business Partner.
4. Enter changes
Enter the changes you want to make to the business partner. For further details see the corresponding section in
Creating a Business Partner.
 Note
To change data blocks that contain complex data such as Addresses or Bank Accounts use the New button. A
corresponding input screen is displayed.
5/19/2023
You can edit the Relationships block of a business partner and create the business partner you are referring to in one
step. For further details see One Step Creation of Business Partners for Relationships.
5. Submit changes
Click the Submit button to submit your change request.
Results
Your new change request is created and sent for processing according to the work ow you have assigned to the change
business partner process. Normally this means that it passes to a Master Data Steward who reviews the changes. Once the
change request has been approved and technical validation has taken place, the changed business partner data replaces the
existing data in the active area. The business partner is no longer available in the staging area and can be included in new
change requests.
One Step Creation of Business Partners for Relationships
Use
The one step creation of business partners enables you to edit relationship-speci c data of business partner A, and in parallel
create a business partner master data record for business partner B.
The data for both business partners is submitted and can be approved using the same change request.
Activities
You edit the business partner master data for business partner A.
1. In the Relationships section select a Relationship Category.
2. To create business partner master data for business partner B choose Create .
 Note
For existing business partners use the input help of the Partner ID eld.
3. Select a business partner category. Business partner categories are:
Organization
Person
Group
4. Enter the required data and choose Done.
Result
Relationship-speci c data for business partner A as well as business partner master data for business partner B is created and
can be submitted using the same change request.
Marking a Business Partner for Deletion
5/19/2023
Prerequisites
The business partner exists in the active area and is not part of an ongoing change request.
Context
You can use the Change Request service to create a change request that, once approved, will ag the business partner for
archiving in the next archiving run.
Procedure
1. Select a business partner in the Search Business Partner result list.
In the Search business partner service, select a business partner in the result list and choose Mark for Deletion.
2. Enter change request data.
3. Submit change request.
To trigger the deletion work ow, click the Submit button.
Results
The system creates a change request for deleting the chosen business partner. The change request triggers the appropriate
work ow and, once approved, results in the business partner being agged for archiving in the next archiving run.
Blocking/Unblocking a Business Partner
Prerequisites
The business partner exists in the active area and is not part of an ongoing change request.
Context
You can use the Change Request service to create a change request that, once approved, will ag the business partner as
blocked or respectively will unblock it.
Procedure
1. Select a business partner in the Search Business Partner result list.
In the Search Business Partner service, select a business partner in the result list and choose Block or Unblock.
2. Enter change request data
3. Submit change request
To trigger the blocking or unblocking work ow, click the Submit button.
5/19/2023
Results
The system creates a change request for blocking or unblocking the chosen business partner. The change request triggers the
appropriate work ow and, once approved, results in the business partner being blocked or respectively unblocked.
Replicating a Business Partner
Prerequisites
The business partner to be replicated exists in the active area and is not locked by another change request.
You have maintained a change request type for business partner change and have set up your work ow for this change
request type.
You have set up appropriate communication channels to your client systems using Services or IDocs.
Context
You can use the Replication by Object Selection service to replicate approved business partners from the hub system to client
systems.
Procedure
1. Select a business partner in the Search Business Partner result list
In the Search business partner service, select a business partner in the result list and choose Replicate.
2. Select target system
In the Replication by Object Selection service, select the target systems and choose Replicate.
 Note
Select the Test Run Only check box, if you only want a test being performed without your business partner really
being replicated.
Results
The business partner data is replicated to the selected client systems.
 Note
Information about the replication status of business partners are available using the Replication Status button. The
Replication Status Information service includes information about the status, the target systems and communication
channels.
Mass Change
Prerequisites
You have created a mass change request using the Create Change Request service. See also: Creating a Mass Change Request
5/19/2023
Context
You can use the Mass Change service to change the attribute values for selected business partners simultaneously. You can
change one or more attributes for the selected business partners, but each attribute must have the same new value.
Procedure
Select the Mass Change link from the Business Partner Governance work center.
2. Select business partners to include
Use the Selections list to choose the business partners you want to include in your change request. Choose Next to
continue.
 Note
While you can select business partners in the Create Change Request service, we recommend that you use this
screen instead.
Use the Scope of Selection table to review your chosen business partners and remove any business partners you do not
want to include in your change request. Choose Next to continue.
 Note
If a business partner you have selected already exists in the staging area, this change request overwrites it. A
warning appears when you attempt to execute the changes.
4. De ne values
Choose the attributes you want to change and the value you want to set them to. To do so, enter the new value in the
Replace With column of the attribute you want to change. This value is setfor the attribute in each business partner you
selected. To initialize an attribute set the Initialize indicator. Choose Next to continue.
 Note
Only attributes available for mass change are visible on this screen.
Review your changes and choose Execute Changes to submit your change request.
Results
If all business partners are already contained in existing change requests where you are the owner, those change
requests are modi edand a warning message appears. If you are not the owner, an error message appears.
If none of the business partners to be changed are contained in change requests, the system asks you for a mass change
request where you are the processor. You can create a mass change request with the Create Change Request service.
The business partners are added to the new mass change request.
If some business partners appear in an existing change request and some do not, the system asks you for a mass change
request. When you enter a mass change request, all business partners that were not in a change request are added to
the mass change request. Those business partners that were partof an existing change request aremodi ed using their
own change requests.
5/19/2023
Once business partners are assigned to a mass change request, the change request is sent to a Master Data Steward who
reviews the changes. During this time the business partners are stored in the master data governance staging area. Once the
master data steward has approved the change request and technical validation has taken place the changed business partners
are written to the active area.
Creating a Mass Change Request
Context
The Create Mass Change Request service enables you to create change requests for the mass update of existing business
partners. Updating multiple business partners is a two-step process; you rst create a single change request for multiple
business partners using this service, then you use the Mass Change service to enter the details for the changes you want to
make.
 Note
Although you can enter the IDs for the business partners you want to change in this screen, SAP recommends to use the
Mass Change service to add the business partners instead.
Procedure
1. Open the change request service
Choose Processing of Multiple business partners and click the Create Mass Change Request link to open the Create
Mass Change Request service.
Enter a description, type, due date, priority, and reason for your new change request. Choose Next to continue.
attachments if required. Choose Next to continue.
4. Specify business partners for the change request
 Note
We recommend that you use the Mass Change service to add business partners later rather than at this point.
To add business partners to the change request, click the Specify Objects button. You can then use the input help in the
elds of the business partner column to add business partners to the change request.
Choose the Enter button followed by Next to continue.
5. Review
Check and review your new change request. Choose Submit to create your new change request.
Results
A new change request has been created for the mass change of business partners. Choose Close to return to the Business
Partner Governance work center.
Address Screening
5/19/2023
Use
If your system is set up for address screening, you can use the optional feature address screening. It enables you to perform the
screening of a person or organization by SAP Business Integrity Screening within a speci ed change request step.
Prerequisites
You are authorized for the address screening.
The address screening is con gured according to the document Set up Address Screening.
Features
One certain change request step is speci ed for the address screening. When a change request is approved, rejected, or
checked within the speci ed change request step the address screening starts automatically. If a potential hit exists, a dialog
box shows you details comparing your current record with data of the hit. You now can decide whether to con rm the hit or not.
In the case of a hit the standard system con guration allows the user to decide whether to continue the processing or not.
 Note
In the speci ed change request step, the Check button enables you to request the address screening manually at any time.
More Information
For more information on the address screening feature, see MDG, Business Partner: Address Screening
For more information on SAP Business Integrity Screening, see http://help.sap.com/bis .
Request Business Partner
Use
With this app you can request a new business partner for an organization or person. This app is easily accessible for a general
user with limited knowledge of master data governance.
Key Features
Separate forms to create a business partner as an organization and a person
example, 20+).
5/19/2023
Address format that automatically changes to EU or US when you enter the country or region

Desktop
Tablet
Smartphone

Supplier
Use
Master Data Governance for Supplier enables you to monitor and control the creation, editing, and deletion of supplier master
data.
A typical work ow starts with a user creating or changing data and submitting the change request. A master data expert then
reviews the change request. In an additional step the initial user may need to make changes, and nally the master data expert
approves the change request. As a result the system updates or creates the appropriate business partner master record.

The following documents about change request processing outline the functions and processes used for creating and
processing change requests. During a typical work ow a user might rst search for a supplier, then generate a change request
to create, change, or mark a supplier for deletion, depending on his or her requirements. The user can also change multiple
suppliers at the same time using the Create Change Request and Mass Change services.
The user does not actually create, change, or mark suppliers for deletion; instead he or she creates change requests that are
sent for approval by a Master Data Steward. Once this expert approves the change request, the new or updated supplier data is
written to the active area. During the change request process the new or changed master data is stored in the master data
governance staging area.
change request, validate the change request data, view the validation log, forward the change request, or perform a variety of
checks. The user can also access the BCV side panel to view additional information for the change request. For more
information, see Con guring Business Context Viewer for MDG Supplier.
the duplicate check to have the system scan for duplicate data as well as additional checks to ensure the consistency of
data.
3. The Master Data Steward reviews the change request and either approves it or rejects it.
5/19/2023
If the Master Data Steward rejects the change request, it is sent back to the creator, who can either discard the
change request or modify and resubmit it.
If the Master Data Steward approves the change request, the information in the change request is written to the
active area and the process is complete.
 Note
Any work ow step offers the possibility to perform checks either by choosing a Check button, by choosing Next to continue
or by choosing Enter. The extent of checks being performed at each work ow step, for example duplicate check, validity
check or required elds check are speci ed in the Customizing.
If a validity check or required elds check reports an error then the change request cannot be activated.
Search Supplier
Use
The Search Supplier service enables you to search for and display suppliers based on speci ed criteria. You can use a large
range of attributes to search including names, addresses, bank details and identi cation numbers. From the search results list
you can choose to display, edit, replicate, create, or copy a supplier.
Activities
The search offers the following possibilities:
Search Method
A variety of search methods offer sets of prede ned search criteria.
You can extend or reduce the number of search criteria if required using the Insert New Line and Delete Row buttons.
Fuzzy Search
Depending on the Search Method chosen a Fuzzy Search check box is offered.
Maximum Number of Results
You can use the Maximum Number of Results eld to limit the number of results displayed.
Number of Search Result Records
You can see the number of search result records, which includes blocked data related to supplier.
 Note
If you search for two or more different attributes then the search lters its results based on an AND logic.
When searching a single attribute for more than one parameter the search lters its results based on an OR logic.
5/19/2023
Creating a Supplier
Prerequisites
You have maintained a change request type for supplier creation and have set up your work ow for this change request type.
Context
You can use the Create Request service to create a change request for supplier creation. This change request goes through the
predetermined work ow process and when complete results in the creation of a new supplier in the active area.
Procedure
1. Selecting the change request type
In the Search Supplier section, choose New and then select Organization or Person or Group.
2. Select a change request type in the Available Change Request Types dialog box.
for your change request such as priority, due date, and reason. You can also add comments and attach relevant les
directly or by link.
4. Enter details for new supplier
In the supplier Details section, enter the data for your supplier. You can enter details for your change request such as
general data, organizational data, address data and communication data.
 Note
You can check your entries choosing theCheck button. Depending on the data entered an Address Validation dialog
box asking for further input may be displayed. If similar supplier data already exists in the system a duplicate check
dialog box will inform you about the potential duplicate. We recommend to start creating a supplier with a search.
When you have entered your data choose the Submit button to trigger the work ow. As the rst step the checks as
mentioned above will be performed.
 Note
To save the change request for use at a later time choose Save.
Results
The new change request for supplier creation is created and sent for processing according to the rule-based work ow you have
assigned to the create supplier process. Usually, this means that it passes to a Master Data Steward who reviews the changes.
During this time the new supplier is stored in the master data governance staging area and does not appear in the active area.
Once the Master Data Steward has approved the change request and technical validation has taken place, the new supplier is
written to the active area.
Enriching a Supplier
 Restriction
5/19/2023
As of Q1 of 2021, the SAP Data Enrichment service is not available for purchase. Existing customers can continue to use SAP
Data Enrichment until the end of their license term.
Use
By integrating with SAP Cloud Platform Data Enrichment, you can enrich your existing supplier with data from external data
providers. This eliminates or reduces the costs and efforts involved with manual data creation and maintenance. You can use
these integration features with the Change Request app.
Prerequisites
You have con gured data enrichment integration as described in Data Enrichment Integration.
You have maintained a change request type for supplier creation and change.
You have set up your work ow for this change request type.
You have speci ed BP Enrichment as relevant in enhancement spots and checks using the Change Request step view. To
do this, use the Customizing activity Master Data Governance, Central Governance General Settings Process
Modeling Change Requests Con gure Properties of Change Request Step .
You have activated the following event type linkages:
Object Type: BUS2250, Event: ACTIVATED , Receiver Type: ACTIVATED_DE
Object Type: BUS2250, Event: ROLLED_BACK , Receiver Type: ROLLED_BACK_DE
To do this, use the Customizing activity Master Data Governance, Central Governance General Settings Process
Modeling Work ow Activate Event Type Linkage
You have added the Data Enrichment UIBB in the Change Request app by choosing Personalize Change Layout
Add Data Enrichment .
Procedure
1. Select the supplier category.
In the Search Supplier section, choose New, and select Organization. Note that you can enrich data only for supplier type
Organization.
2. Choose Create Supplier.
3. Enter details of the new supplier.
In the Change Request section, enter a description for your change request in the Description eld.
In the Supplier Details section, enter Name1, Country, and City. These are the mandatory elds for data
enrichment.
4. Check your entries by choosing the Check button. Depending on the data entered, a dialog box is displayed with
matched records from data enrichment.
5. Choose Continue to view details of the matched records. Another dialog box opens with the eld level data from data
enrichment.
6. Select the data you want to import and choose Enrich. The system navigates back to supplier screen.
7. Make sure that the Address, Identi cation Numbers, and Data Enrichment blocks are lled correctly.
8. If required, enter additional data for the new supplier.
9. Choose Submit to trigger the work ow.
5/19/2023
Key Mapping
Key mapping is maintained between MDG and data enrichment systems for Business Partner ID and Data Enrichment ID. You
can view the key mapping information in the Data Enrichment UIBB.
Additional Information
For more information on SAP Cloud Platform Data Enrichment, see SAP Cloud Platform Data Enrichment.
Changing a Supplier
Prerequisites
The supplier to be changed exists in the active area and is not locked by another change request.
You have maintained a change request type for supplier change and have set up your work ow for this change request
type.
Context
You can use the Change Request service to create a change request for changing a single supplier. This change request goes
through the predetermined work ow process and when complete results in the change of the selected supplier in the active
area. Creating the change request copies the supplier to the staging area. A supplier can only be assigned to one active change
request at a time, so no new change requests can be created for a supplier that is already in the staging area.
 Caution
If you use the back-end system to make changes to a eld in the BP data model while the supplier is undergoing the change
request process, when the change request is approved, all your changes will be overwritten and not just those elds effected
by the change request.
Procedure
1. Select a supplier in the search result list
In the Search Supplier service, select a supplier in the result list.
2. Change to edit mode
To change the supplier to edit mode, choose the Edit button.
3. Select a change request type
In the Available Change Request Types dialog box, select a change request type.
see the corresponding section in Creating a Supplier.
5. Enter changes and submit
5/19/2023
Enter the changes you want to make to the supplier and click the Submit button to submit your change request. For
further details see the corresponding section in Creating a Supplier.
Results
Your new change request is created and sent for processing according to the rule-based work ow you have assigned to the
change supplier process. Normally this means that it passes to a Master Data Steward who reviews the changes. Once the
change request has been approved and technical validation has taken place, the changed supplier data replaces the existing
data in the active area. The supplier is no longer available in the staging area and can be included in new change requests.
Marking a Supplier for Deletion
Prerequisites
The supplier exists in the active area and must not be part of an ongoing change request.
Context
You can use the Change Request service to create a change request that, once approved, will ag the supplier for archiving in
the next archiving run.
Procedure
1. Select a supplier in the search result list.
In the Search Supplier service, select a supplier in the result list and choose Mark for Deletion.
2. Select a change request type.
In the Available Change Request Types dialog box, select an change request type.
3. Enter change request data.
4. Submit change request.
To trigger the deletion work ow, click the Submit button.
Results
The system creates a change request for deleting the chosen supplier. The change request triggers the appropriate work ow
and, once approved, results in the supplier being agged for archiving in the next archiving run.
Blocking/Unblocking a Supplier
Prerequisites
The supplier exists in the active area and is not part of an ongoing change request.
Context
5/19/2023
You can use the Change Request service to create a change request that, once approved, will ag the supplier as blocked or
respectively unblock it.
Procedure
1. Select a supplier in the search result list.
In the Search Supplier service, select a supplier in the result list and choose Block or Unblock.
2. Select a change request type
In the Available Change Request Types dialog box, select an change request type.
3. Enter change request data
4. Submit change request
To trigger the blocking or unblocking work ow, click the Submit button.
Results
The system creates a change request for blocking or unblocking the chosen supplier. The change request triggers the
appropriate work ow and, once approved, results in the supplier being blocked or respectively unblocked.
Replicating a Supplier
Prerequisites
The supplier to be replicated exists in the active area and is not locked by another change request.
You have maintained a change request type for supplier change and have set up your work ow for this change request
type.
You have set up appropriate communication channels to your client systems using Services or IDocs.
Context
You can use the Replication by Object Selection service to replicate approved suppliers from the hub system to client systems.
Procedure
1. Select a supplier in the search result list
In the Search Supplier service, select a supplier in the result list and choose Replicate.
2. Select target system
In the Replication by Object Selection service, select the target systems and choose Replicate. .
 Note
Select the Test Run Only check box, if you only want a test being performed without your supplier really being
replicated.
5/19/2023
Results
The supplier data is replicated to the selected client systems.
 Note
Information about the replication status of suppliers are available using the Replication Status button. The Replication
Status Information service includes information about the status, the target systems and communication channels.
Creating a Mass Change Request
Context
The Create Mass Change Request service enables you to create change requests for the mass update of existing suppliers.
Updating multiple suppliers is a two-step process; you rst create a single change request for multiple suppliers using this
service, then you use the Mass Change service to enter the details for the changes you want to make.
 Note
Although you can enter the IDs for the suppliers you want to change in this screen, SAP recommends to use the Mass
Change service to add the suppliers instead.
Procedure
1. Open the change request service
Choose Processing of Multiple Suppliers and click the Create Mass Change Request link to open the Create Mass
Change Request service.
2. Create Change Request
Select a draft of a change request or create a new change request by choosing the Continue button.
Enter a description, due date, priority, and reason for your new change request. Choose Next to continue.
attachments if required. Choose Next to continue.
5. Specify suppliers for the change request
To add suppliers to the change request, click the Specify Objects button. You can then use the input help in the elds of
the Supplier column to add suppliers to the change request.
 Note
We recommend that you use the Mass Change service to add suppliers later rather than at this point.
Choose theEnter button followed by Next to continue.
6. Review
Check and review your new change request. Choose Submit to create your new change request.
Results
5/19/2023
A new change request has been created for the mass change of suppliers. Choose Close to return to the Supplier Governance
work center.
Mass Change
Prerequisites
You have created a mass change request using the Create Change Request service.
Context
You can use the Mass Change service to simultaneously change the attribute values for selected suppliers. You can change one
or more attributes for the selected suppliers, but each attribute must have the same new value.
Procedure
Select the Mass Change link from the Supplier Governance work center.
2. Select suppliers to include
Use the Selections list to choose the suppliers you want to include in your change request. Choose Next to continue.
 Note
While you can select suppliers in the Create Change Request service, SAP recommends that you use this screen
instead.
Use the Scope of Selection table to review your chosen suppliers and remove any suppliers you do not want to include in
your change request. Choose Next to continue.
 Note
If a supplier you have selected already exists in the staging area, this change request overwrites it. A warning about
this overwrite appears when you attempt to execute the changes.
4. De ne values
Choose the attributes you want to change and the value you want to set them to. To do so, enter the new value in the
Replace With column of the attribute you want to change. This value is set for the attribute in each supplier you selected.
Choose Next to continue.
 Note
Only attributes available for mass change are visible on this screen.
Review your changes and choose Execute Changes to submit your change request.
Results
5/19/2023
If all suppliers are already contained in existing change requests where you are the owner, those change requests are
modi ed and a warning message appears. If you are not the owner, an error message appears.
If none of the suppliers to be changed are contained in change requests, the systems asks you for a mass change
request where you are the processor. You can create a mass change request with the Create Change Request service.
The suppliers are added to the new mass change request.
If some suppliers appear in an existing change request and some do not, the system asks you for a mass change request.
When you enter a mass change request, all suppliers that were not in a change request are added to the mass change
request and those that were part of an existing change request are modi ed using their own change requests.
Once suppliers are assigned to a mass change request, the change request is usually sent to a Master Data Steward who
reviews the changes. During this time the suppliers are stored in the master data governance staging area. Once the Master
Data Steward has approved the change request and technical validation has taken place the changed suppliers are written to
the active area.
Address Screening
Use
If your system is set up for address screening, you can use the optional feature address screening. It enables you to perform the
screening of a person or organization by SAP Business Integrity Screening within a speci ed change request step.
Prerequisites
You are authorized for the address screening.
The address screening is con gured according to the document Set up Address Screening.
Features
One certain change request step is speci ed for the address screening. When a change request is approved, rejected, or
checked within the speci ed change request step the address screening starts automatically. If a potential hit exists, a dialog
box shows you details comparing your current record with data of the hit. You now can decide whether to con rm the hit or not.
In the case of a hit the standard system con guration allows the user to decide whether to continue the processing or not.
 Note
In the speci ed change request step, the Check button enables you to request the address screening manually at any time.
More Information
For more information on the address screening feature, see MDG, Business Partner: Address Screening
For more information on SAP Business Integrity Screening, see http://help.sap.com/bis .
Request Supplier
Use
5/19/2023
With this app you can request a new supplier for an organization or person. This app is easily accessible for a general user with
limited knowledge of master data governance.
Key Features
Separate forms to create a supplier as an organization and a person
example, 20+).
When you upload an attachment, the Reason for Request eld is automatically lled with the text Check attached
documents.
Address format that automatically changes to EU or US when you enter the country or region

Desktop
Tablet
Smartphone

Data Transfer
Use
Data transfer represents a collection of functions and features that enable you to move master data and mapping information
between systems and clients. Examples of these systems include existing ERP systems and your Master Data Governance hub
system. To transfer master data and mapping information, follow this process:
1. Export the master data and mapping information from the source system to an XML le. This le rests on your
application server.
2. Copy the XML le from the application server of the source system to the application server of your target system.
3. Import the master data and mapping information to the target system.
Features
Export master data and mapping information from a source system to an XML le. This le is saved on your application
server. You can also use a SOA service to transfer the data. For more information, see Exporting Master Data.
5/19/2023
 Note
If the release level of your source systems is below ERP 6.05 use the following options for exporting the data:
For exporting supplier and customer master data from systems with release levels below ERP 6.05, use the
existing functions in that release. For more information, see Extraction of Supplier and Customer Master Data
(Earlier Releases).
For exporting business partner master data from systems with release levels below ERP 6.05, use the report
BUPA_SEND. For more information, see Extraction of Business Partner Master Data (Earlier Releases).
Import master data and mapping information into the target system. For more information, see Importing Master Data.
Monitor data transfer between source and target systems. For more information, see Monitor Data Transfer.
Convert XML les to SOA message format if required by the system landscape. For more information, see Converting
Master Data.
Extraction of Supplier and Customer Master Data (Earlier ERP

Releases)
Use
If your supplier or customer master data is stored in systems with ERP releases lower than SAP Business Suite Enhancement
Package 5, you have the following options for extracting the data:
For ERP releases 4.70 and higher, use the transaction MDM_CLNT_EXTR. With this transaction, the data is extracted as
an IDoc with the message types CREMDM for supplier and DEBMDM for customer.
For releases lower than 4.70, use the transaction Send Vendor BD14 or Send Customer BD12. With these transactions,
the data is extracted as an IDoc with the message type CREMAS or DEBMAS accordingly.
Prerequisites
You have con gured the ALE distribution model as follows:
You have con gured the respective message type.
You have created an XML port and assigned it to the recipient system.
Activities
1. Start the transaction Send Vendor, or the transaction Send Customer, or the report MDM_EXTRACTION.
2. Enter your selection criteria.
With the transactions Send Vendor and Send Customer for each master data record, an individual IDoc is created in XML
format that can be imported on the server side in data import. With the transaction MDM_CLNT_EXTR you can determine how
many master data records you want to put in a single IDoc.
More Information
For information on the extraction of master data objects, also see SAP Note 1035601 .
5/19/2023
Extraction of Business Partner Master Data (Earlier SRM and

ERP Releases)
Use
If you want to extract business partner master data from source systems with lower SRM and ERP releases, you can use the
report Send Business Partner Data (BUPA_SEND). With this report, the data is extracted in IDoc format with the message type
BUPA_INBOUND_MAIN_SAVE_M for the business partners and the message type BUPA_INBOUND_REL_SAVE_M for the
business partner relationships.
Prerequisites
You have con gured the ALE distribution model as follows:
You have con gured both message types.
You have created an XML port and assigned it to the recipient system.
Activities
1. Start the report Send Business Partner Data.
2. Enter your selection criteria.
Depending on the block size you select, one or more IDocs are created in XML format that can be imported on the target side
during data import.
Converting Master Data
Prerequisites
You have exported the master data from your client system in XML format to the application server.
Context
You can use the Convert Master Data service to convert master data les in XML format into SOA message format. This is only
relevant if you are transferring data from a client system directly to a system that requires input in SOA message format.
As of SAP enhancement package 5 for SAP ERP 6.0 this conversion is only necessary if you want to send supplier master data to
the SAP NetWeaver Master Data Management for data quality checks and if your client system is running on SAP ERP,
Enhancement Package 4 or earlier.
The Convert Master Data service is not required for material master data or if your client system is running on SAP ERP,
Enhancement Package 5 or later releases.
Procedure
1. Open the Convert Master Data service from the SAP NetWeaver Portal or SAP NetWeaver Business Client. You can also
access the screen using the transaction DTCONVERT.
2. In the Technical Settings section, select an object type from the Object Type drop-down menu. In the Description eld,
enter a description for your conversion.
5/19/2023
3. In the Technical Settings section, select a target directory from the Target Directory drop-down menu.
The target directory is the storage location in the system where the converted les are stored.
4. In the File Pre x eld, enter a pre x for your converted les.
This pre x is added to the le name of your converted les to make it easier for you to identify them in the target
directory.
5. In the Scheduling Settings section, choose if you want to execute your conversion now or at a later date.
6. In the Data Sources section, to add a source directory, choose the Add button.
This source directory is the location where you have stored your les for conversion. Once you have chosen a source
directory you can use the Show Directory Content button to review the les in the directory.
7. To start or schedule your conversion run choose Convert.
Results
You have successfully set up a conversion run to convert your master data les from XML format to SOA message format.
Once the run starts you can choose the Display Monitoring button. This opens the Monitor Data Transfer service where you can
supervise the progress of your conversion run. For more information, see Monitor Data Transfer.
Working with MDG, Data Quality Management

The following documents provide information about the various apps that are available in SAP Master Data Governance to
check and improve the quality of your master data.
Integration Topics
This section provides information about integration options of MDG with other solutions.

MDG Topic 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MDG Topic 1

Uploaded by

Copyright:

Available Formats

5/19/2023

Master Data Governance

SAP S/4HANA | 2022 Latest

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549?locale=en-

For more information, please visit the https://help.sap.com/docs/disclaimer.

Import Data for Consolidation

Supported Device Types

Manage Consolidation Processes

To hide the lter bar choose Hide Filter Bar.

To display the lter bar choose Show Filter Bar.

To restore the standard settings choose Restore.

Use the calender function for the Start Date eld.

1. Mark the processes you want to delete.

2. Choose Delete and OK to con rm.

In the Process detail screen, choose Delete and OK to con rm.

Run Consolidation Processes

Best Record Calculation

Use the input help to change the Adapter

Green: No errors or exceptions occurred.

Orange: Errors or exceptions occurred.

Red: Process step failed.

The Consolidation Process details screen opens.

To start a consolidation process, choose Start or Continue.

For more information, see Specify Process Template.

To roll back to a certain process step, choose Rollback.

To save the con guration of the consolidation process, choose Save.

To delete a consolidation process, choose Delete.

For more information, see Delete Processes.

Create Consolidation Process

3. Use the input help to select a Process Goal.

4. Use the input help to select a Process Template.

For further information of process templates, see Specify Process Template.

Normalization: Baker Str, is converted to Baker Street.

2. To start a process, choose Start or Continue.

For more information, see Specify Process Template.

To display the results of the process step choose Show Results.

The con guration of the process is saved.

For more information on deleting processes, see Delete Processes.

1. On the Process detail screen choose Show Results.

2. To start a process, choose Start or Continue.

For more information, see Specify Process Template.

To start the match review, choose Match Review.

For more information see, Match Review.

The con guration of the process is saved.

For more information on deleting processes, see Delete Processes.

The potential duplicates are displayed in match groups.

A wide range of further lters allows you to adapt the search.

To hide the lter bar choose Hide Filter Bar.

To display the lter bar choose Show Filter Bar.

You can reject match groups.

You can reject single records in a match group.

3. To reject a complete match group choose Undo Approval.

4. To reject single records in a match group choose Reject.

To reassign the record to the match group choose Undo Rejection.

If you want to change the selection choose Set as Target.

Best Record Calculation

2. To start a process, choose Start or Continue.

For more information, see Specify Process Template.

To display the results of the process step choose Show Results.

The con guration of the process is saved.

For more information on deleting processes, see Delete Processes.

System BANKL BANKN KOINH

A11 10010010 32168000 Rosy