MDG Central Governance - Config Guide - 1

4/23/2019
SAP Master Data Governance

Generated on: 2019-04-23
SAP Master Data Governance | MDG92_SP01
PUBLIC
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 SAP Help Portal.
This is custom documentation. For more information, please visit the SAP Help Portal 1
4/23/2019
SAP Master Data Governance

Use
Product Information
Product SAP Master Data Governance 9.2
Based On For detailed information, see SAP Note 2645428 .
SAP Master Data Governance (SAP MDG), central governance provides central ownership of master data in line with a
company’s business rules and processes. MDG delivers domain-speci c, out-of-the-box applications as well as a framework for
custom-de ned master data. MDG offers change request-based processing of master data with integrated work ow, staging,
approval, activation, and distribution. MDG can be deployed as a separate hub system, or co-deployed with SAP ERP. In both
cases, MDG can use SAP and company-speci c business logic to create master data ready to be used in a company’s business
processes.
MDG, consolidation and mass processing provides an understanding of enterprise master data that is owned and maintained
de-centrally, as well as general mass processing capabilities for master data. MDG, consolidation delivers capabilities to
standardize the master data and to detect duplicates. For each of the resulting match groups, MDG, consolidation calculates a
best record out of the duplicates in that group, using survivorship rules on the master data attributes. The best records can be
used in dedicated analytical or business scenarios. MDG, mass processing enables you to update multiple master data records
at a time. To update records, you select the elds and records you want to change. The system then provides statistics on the
changed elds and validates the data for business transactions use before activating the changes.
Within SAP MDG you can combine consolidation and central governance to support various master data management
scenarios, like initial load of master data as a starting point for central governance, consolidation of master data after mergers
and acquisitions, or combinations where you keep de-central ownership of master data in some parts of the company while
centralizing master data ownership in other parts.
Features
SAP Master Data Governance offers the following features:
Centrally Governed Master Data
You can manage master data centrally in the Master Data Governance system. You can use a change requests to
request changes to existing master data or to create new master data. A exible work ow concept enables you to
create the exact master data control process you require, including quality checks and authorizations.
Pre-Built Content for Master Data Domains
SAP Master Data Governance provides standard data models, user interfaces, and work ow de nitions for nancial
master data, material master data, business partners, customers, and suppliers. This standard content can be exibly
enhanced as needed.
Create Custom-Objects
You can use the SAP MDG Application Foundation to build central governance processes for your unique master data
objects.
Replicate Central Master Data
You can use the data replication framework (DRF) to replicate your master data to target systems. Filters allow you to
determine the data sent to each target system. Key mapping allows for different IDs in different systems and value
4/23/2019
mapping supports translation of attribute values so that they can be understood in the target systems. You can use
enterprise services, IDocs, or the le download functions, as the underlying replication technology.
Load Master Data
You can use functions such as File Upload or Import Master Data to transfer data into your Master Data Governance
system.
Ensure Master Data Quality
To increase your master data quality, you can check the data in your MDG governance processes against SAP business
logic and rules you have de ned in the BRF+, or you can use data quality checks from external service calls.
Change Multiple Master Data Records
SAP Master Data Governance offers a range of methods to change multiple master data objects in a single change
request.
Side Panel
Side Panels enable you to extend the SAP MDG user interface by enriching it with additional content for the end-user.
Process Quality Analytics
You can use SAP HANA for search and duplicate detection, for real-time aggregation of KPIs and trends in process
analytics, as well as for increased throughput in master data consolidation.
SAP Fiori Apps
A suite of dedicated SAP Fiori apps support use cases such as display and approval of master data requests.
Consolidate Master Data
You can standardize master data loaded from different sources and identify potential duplicates. You can calculate best
records based on duplicate groups and survivorship rules.
Mass Processing
Mass Processing enables you to update multiple master data records at a time.
Con guration of SAP Master Data

Governance
This documentation provides the information you require to set up SAP Master Data Governance (CA-MDG). This information
supplements the information provided in Customizing as well as the information about activities that you need to execute in
addition to con guring Customizing settings.
Con guration of SAP MDG, Central

Governance
This documentation provides the information you require to set up Master Data Governance, Central Governance (CA-MDG).
This information supplements the information provided in Customizing as well as the information about activities that you need
to execute in addition to con guring Customizing settings.
Note
4/23/2019
The relevant Customizing settings are under Cross-Application Components Processes and Tools for Enterprise
Applications Master Data Governance, Central Governance .
Working with SAP Master Data Governance

This documentation provides the information you require to work with SAP Master Data Governance (CA-MDG).
Working with SAP MDG, Consolidation and

Mass Processing
SAP MDG, consolidation and mass processing enables you to consolidate your master data and to update multiple master data
records at a time.
All is done in a sequence of process steps adapted to your requirements. Each individual process step can be con gured as well.
You can use SAP MDG, consolidation and mass processing as a stand alone application or in combination with SAP MDG,
central governance. This document provides the information you require to run SAP MDG, consolidation and mass processing.
SAP MDG, consolidation and mass processing is available for the material master, business partner including customer and
vendor, and custom object domains.
Consolidating Master Data

Use
SAP MDG, consolidation enables you to consolidate your master data using a sequence of process steps adapted to your
requirements. Each individual process step can be con gured as well. You can use SAP MDG, consolidation as a stand alone
application or in combination with SAP MDG, central governance. This document provides the information you require to run
SAP MDG, consolidation.
Process
SAP MDG, consolidation offers the following optional process steps:
Note
Whether certain process steps are used in your consolidation process and the order of their occurrence is speci ed in the
con guration of SAP MDG, consolidation.
For details see, Specify Process Template.
Standardization
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.
4/23/2019
For more information see, Standardization.
Matching
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.
For more information see, Matching.
Best Record Calculation
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.
For more information see, Best Record Calculation.
Validation
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.
For more information see, Validation.
Activation
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 SAP MDG, consolidation and mass processing.
For more information see, Activation.
More Information
For information on how to con gure SAP Master Data Governance, Consolidation, see Con guring SAP Master Data
Governance, Consolidation and Mass Processing.
Master Data Governance, Consolidation

Use
With this app you can run a process to consolidate and harmonize your master data. This includes steps for standardization,
matching, best-record calculation, validation, activation, and replication.
Key Features
Perform consolidation for SAP business partner, customer, supplier, material master, and custom objects
Use a process UI to start and monitor consolidation processes for all tables and elds including edit capabilities
Integration of standardization capabilities, including BRFplus integration
Use matching capabilities to identify duplicates
4/23/2019
Display match review UI to approve or reject matching results
Use con gurable best-record calculation
Use best record calculation UI to check and amend the result data
Perform analytics for each process step including drill-down capabilities
Split and remove data from the process
Consolidate classi cation data
Consolidate active records
Consolidate business partner relationships
Supported Device Types

Desktop
Tablet
Relevant Business Catalog

SAP_CMD_BC_PR_MONPROCS_PC for materials
SAP_CMD_BC_BP_MONPROCS_PC for business partners
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.
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 section Extended Material Number in Apps in the SAP S/4HANA UI Technology guide.
Note
You can use the Download File Templates feature to either download a set of Example Files or the Full Template.

Desktop
4/23/2019
Tablet
File Format for Data Import

Use
You import data records for consolidation from a le that is either in CSV or in Office Open XML format. The system assumes
that all records in the le originate from the same source system. You enter the ID of the source system when de ning the
import. At the same time, you also enter a data package name. All records of the le are assigned to this data package. The le
must be formatted as de ned below.
CSV Format (*.csv)
The le contains the data in plain text and is interpreted by the system line-by-line. The format is simple and it is intended to be
used for basic use cases, for example business partner data with at most one address for each business partner, but not
multiple addresses. If you want to upload business partners with multiple addresses, the Office Open XML format is
recommended. 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 <CR>.
Adjacent elds are separated with a semi-colon.
Fields can be enclosed in double-quotes.
A eld must be enclosed in double-quotes, if it contains a semi-colon, <CR>, <LF>, or <CR>
A eld must be enclosed in double-quotes if it contains a double-quote. Each double-quote must be preceded by a
double-quote.
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.
A complete list of tables and elds is provided in the le BPARTNER-TABLES-FIELDS.xlsx for the object business
partner and in the le MATERIAL-TABLES-FIELDS.xlsx for the business object material. You can download these
les from the app using the link Download File Template.
The eld SOURCE_ID is a special eld and its content uniquely identi es a record.
All subsequent lines in the le are interpreted as lines of data to be written to the source data tables.
The values in each data line are in the sequence as speci ed by the header line.
CSV has the limitation that each key value for any table must only occur once. This means that it is not possible to
import materials with data for more than one plant for each material. However, it is possible for example to import
materials with data for one plant for each material. Alternatively, you can use the Office Open XML le format.
The system assumes an encoding with UTF-8.
SOURCE_ID and SOURCE_RECENCY are special columns in the le.
4/23/2019
SOURCE_ID contains the Source Record ID of a record in the source system. This string must uniquely identify the record in the
source system. The Source ID together with Source System form the unique ID used during consolidation. The eld is optional
in the le, but essential for the consolidation process. If this eld is not present in the le, the value of the key eld of the root
table is used. For example BUT000-PARTNER or MARA-MATNR. SOURCE_ID and <root table>-SOURCE_ID are synonyms.
You can write a timestamp in the SOURCE_RECENCY eld to indicate how recent the information in the respective row is. This
can be used in best record calculation during consolidation. The format is YYYYMMDDhhmmss. For example, 20161130162600
for November 30, 2016 16:26:00.
Key elds
The le must contain every key eld of all tables that contain data. For example, in case of storage location data for materials
(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. See also object-speci c
defaulting of values.
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.
No conversion is applied to eld contents. 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 is much more versatile than CSV, as it allows to import data that has a more complex structure. 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 single worksheet (table) or multiple worksheets. If you use a single worksheet
then the content 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.
Each worksheet must contain a header line as the rst row. Each cell carrying the reference to a table and eld
combination of the objects data model. The notation of the reference is <TABLE>-<FIELD>.
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.
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), ADDRNUMBER,
DATE_FROM, and NATION.
Worksheets, rows, and columns that are marked as hidden are ignored during the import.
4/23/2019
In general, you should use the format option Text. 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.
Object-Speci c Defaulting of Values

Besides the defaulting of key elds from the corresponding eld of the parent table on the same sheet, the system provides
defaults for the elds listed below. This defaulting occurs only if the eld is not present as a column in the le.
Busines Partner Data
Business Partner Data
Table Reference Field Default Value
BUT100 (Role) DFVAL Blank
BUT0BK (Bank Account) BKVID A unique number for each business partner
BUT021_FS (Address Usage) ADR_KIND XXDEFAULT
BUT021_FS (Address Usage) VALID_TO 99991231
ADRP (Person Data) NATION Blank
ADRP (Person Data) DATE_FROM 00010101
ADRP (Person Data) DATE_TO 99991231 or BUT021_FS-VALID_TO (if

present)
ADRC (Address) NATION Blank
ADRC (Address) DATE_FROM 00010101
ADRC (Address) DATE_TO 99991231 or BUT021_FS-VALID_TO (if

present)
ADR6 (E-Mail), ADR3 (Fax), ADR2 CONSNUMBER A unique number for each address
(Phone), ADR12 (URL)
ADR6 (E-Mail), ADR3 (Fax), ADR2 DATE_FROM 00010101

ADR12 (URL) URI_TYPE HPG
The table BUT020 (the link table between business partner and address) can be omitted. In this case, BUT000-PARTNER and
ADRC-ADDRNUMBER must be present and the system will create a row for BUT020 to link for each address of a business
partner to its business partner.
Material Master Data
Material Master Data
MARA_DRAD DOKOB MARA
MARA_DRAD_STXH TDOBJECT DRAD
MARA_DRAD_STXH TDID LTXT
MARA_DRAD_STXL TDOBJECT DRAD
MARA_DRAD_STXL TDID LTXT
4/23/2019
MARA_DRAD_STXL LINE_COUNTER A unique number for each text row.
MARA_STXH TDOBJECT MATERIAL
MARA_STXL TDOBJECT MATERIAL
MARA_STXL LINE_COUNTER A unique number for each text row.
MARC_STXH TDOBJECT MDTXT
MARC_STXH TDID LTXT
MARC_STXL TDOBJECT MDTXT
MARC_STXL TDID LTXT
MARC_STXL LINE_COUNTER A unique number for each text row.
MBEW BWKEY If the valuation area is set to plant and

MARC is on the same sheet, use MARC-
WERKS
MEAN LFNUM A unique number for each GTIN
MVKE_STXH TDOBJECT MVKE
MVKE_STXH TDID 0001
MVKE_STXL TDOBJECT MVKE
MVKE_STXL TDID 0001
MVKE_STXL LINE_COUNTER A unique number for each text row.
Manage Source Data for Consolidation

Use
With this app you can organize your source data for your consolidation process. You can view a list of your source data organized
by source system and divided by data package. You can use this app for business partner (including customer and supplier),
business partner relationships, and material.
Key Features
View a list of source data
View the source data by status
Delete source data by data package
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 section Extended Material Number in Apps in the SAP S/4HANA UI Technology guide.
4/23/2019
Desktop
Tablet
Relevant Business Catalogs
SAP_CMD_BC_PR_MONPROCS for material
SAP_CMD_BC_BP_MONPROCS for business partner
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 Consolidation 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
User
Creation Date
Status
To hide the lter bar choose Hide Filter Bar.
To display the lter bar choose Show Filter Bar.
4/23/2019
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 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

4/23/2019
Validation
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.
4/23/2019
You can start or continue a consolidation process at any process step as long as the predecessor steps are
completed.
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 SAP 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.
4/23/2019
For further information of process templates, see Specify Process Template.
5. Use the input help to select the Data Sources for the consolidation process.
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
Import Data for Consolidation
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 the Adapter and the corresponding Adapter 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.
4/23/2019
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.
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.
4/23/2019
Activities
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
4/23/2019
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 and approves them automatically. 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.
You can toggle between Address Data and Identi ers that were used to identify the potential duplicates.
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 Consolidation 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.
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.
4/23/2019
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
Match groups in the status Open are processed as match groups in the best record calculation.
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 greyed 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.

Use
Activities
4/23/2019
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
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).
4/23/2019
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:
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
4/23/2019
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
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.
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
4/23/2019
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
Save
Delete
Cancel
4/23/2019
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.
Activities
Note
displayed.
Note
4/23/2019
Note
Retry
Rollback
Save
Delete
Cancel
Note
Replace.
Clear.
Validation
4/23/2019
Use
Activities
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.
Note
Retry
Rollback
4/23/2019
Save
Delete
Cancel
Activation
Use
Activities
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
4/23/2019
Retry
Rollback
Save
Delete
Cancel
Concept of Concurrent Changes

Within the process step activation con icts caused by cocurrent 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.
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:
4/23/2019
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 summery 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
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 mass processing or a consolidation process.
Features
The following business objects are supported:
Business Partner
Business Partner Relationship
Material
Activities
1. Enter Selection Criteria
Enter selection criteria to obtain a list of consolidation processess and mass processess and choose Go.
All changes corresponding to your selection criteria are displayed.

4/23/2019
2. Obtain additional information on the processess
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
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
Consolidation of Active Records

Use
This feature enables you to consolidate active records.
Features
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
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.
Mass Processing of Master Data

Use
Mass Processing enables you to update multiple master data records at a time. The function is available for the material
master, business partner (including customer and vendor), and custom object domains. You can access this function through
the Start Mass Processing and Manage Mass Processing tiles in the SAP Fiori Launchpad.
4/23/2019
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.
Prerequisites
The following business functions must be active for the domains you want to use:
MDG_CONSOLIDATION_CUSTOBJ_2
MDG_CONSOLIDATION_MATERIAL_2
MDG_CONSOLIDATION_CUSTOMER_2
MDG_CONSOLIDATION_SUPPLIER_2
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 .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.
Processing of business partner relationship data
Master Data Governance, Mass Processing

Use
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
4/23/2019
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
Relevant Business Catalog
SAP_CMD_BC_PR_MONPROCS for materials
SAP_CMD_BC_BP_MONPROCS for business partners
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. For
information on how to lter, see Filter Consolidation Processes.
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.
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/23/2019
4. In the Edit step, choose Edit Records and make the required changes. Choose Continue to proceed with the process.
5. On the Validation screen, check the validity of the edited data.
6. 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
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.
4/23/2019
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
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
4/23/2019
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.
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.
4/23/2019
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. The function is recommended for updating
up to ve elds in up to 10,000 objects.
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. 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.
6. On the Selection screen, enter the search criteria to select the objects that you want to edit.
7. Choose Save.
Result
You have set up a new Mass Process.
4/23/2019
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.
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
4/23/2019
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.
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
4/23/2019
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
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
4/23/2019
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
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
4/23/2019
Note
Retry
Rollback
Save
Delete
Cancel
Note
Replace.
Clear.
Filter and Remove

4/23/2019
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.
Activities
Note
displayed.
Note
Note
Retry
Rollback
4/23/2019
Save
Delete
Cancel
Note
Replace.
Clear.
Validation
Use
Activities
Choose the Process Using and the corresponding Con guration using the input help.
Note
displayed.
Note
4/23/2019
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.
Note
Retry
Rollback
Save
Delete
Cancel
Activation
4/23/2019
Use
Activities
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
4/23/2019
Concept of Concurrent Changes

Within the process step activation con icts caused by cocurrent 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.
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 summery 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.
4/23/2019
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 an Office Open XML le. This le can be used
for Mass Processing of Master Data.
Features
The following business object types are supported:
Business Partner 147
Business Partner Relationship 1405
Material 194
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.
2. Select Business Partner / BP relationships / Material
Use the selection criteria with Include and Exclude options.
3. Export
To export choose Export. The system generates a le to be downloaded.
4. Download
To download the le choose Download File.
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
4/23/2019
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.
CSV Format (*.csv)
The le contains the data in plain text and is interpreted by the system line-by-line. The format is simple and it is intended to be
used for basic use cases, for example business partner data with at most one address for each business partner, but not
multiple addresses. If you want to upload business partners with multiple addresses, the Office Open XML format is
recommended. 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 <CR>.
Adjacent elds are separated with a semi-colon.
Fields can be enclosed in double-quotes.
A eld must be enclosed in double-quotes, if it contains a semi-colon, <CR>, <LF>, or <CR>
A eld must be enclosed in double-quotes if it contains a double-quote. Each double-quote must be preceded by a
double-quote.
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.
CSV has the limitation that each key value for any table must only occur once. This means that it is not possible to
import products with data for more than one plant for each product. However, it is possible for example to import
products with data for one plant for each product. Alternatively, you can use the Office Open XML le format.
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.
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. See also object-speci c
defaulting of values.
Inserting and Deleting Rows
4/23/2019
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.
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)
KNA1_AUSP Characteristics (Customer)
KNA1_KSSK Class Assignment (Customer)
LFA1_AUSP Characteristics (Supplier)
LFA1_KSSK Class Assignment (Supplier)
KNA1_ASSGMNT Additional ERP Customers
4/23/2019
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:
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.
No conversion is applied to eld contents. 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 is much more versatile than CSV, as it allows to import data that has a more complex structure. 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 single worksheet (table) or multiple worksheets. If you use a single worksheet
then the content 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.
Each worksheet must contain a header line as the rst row. Each cell carrying the reference to a table and eld
combination of the objects data model. The notation of the reference is <TABLE>-<FIELD>.
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.
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), ADDRNUMBER,
DATE_FROM, and NATION.
Worksheets, rows, and columns that are marked as hidden are ignored during the import.
4/23/2019
In general, you should use the format option Text. 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.
Object-Speci c Defaulting of Values

Besides the defaulting of key elds from the corresponding eld of the parent table on the same sheet, the system provides
defaults for the elds listed below. This defaulting occurs only if the eld is not present as a column in the le.
BUT100 (Role) DFVAL Blank
BUT0BK (Bank Account) BKVID A unique number for each business partner
BUT021_FS (Address Usage) ADR_KIND XXDEFAULT
BUT021_FS (Address Usage) VALID_TO 99991231
ADRP (Person Data) NATION Blank
ADRP (Person Data) DATE_FROM 00010101
ADRP (Person Data) DATE_TO 99991231 or BUT021_FS-VALID_TO (if

present)
ADRC (Address) NATION Blank
ADRC (Address) DATE_FROM 00010101
ADRC (Address) DATE_TO 99991231 or BUT021_FS-VALID_TO (if

present)
ADRC (Address) ADDRNUMBER Address number of the business partner’s

standard address
ADR6 (E-Mail), ADR3 (Fax), ADR2 CONSNUMBER A unique number for each address
ADR6 (E-Mail), ADR3 (Fax), ADR2 DATE_FROM 00010101

ADR6 (E-Mail), ADR3 (Fax), ADR2 ADDRNUMBER If ADRC-ADDRNUMBER is on the same

(Phone), ADR12 (URL) sheet, use ADRC-ADDRNUMBER
ADR12 (URL) URI_TYPE HPG
The table BUT020 (the link table between business partner and address) can be omitted. In this case, BUT000-PARTNER and
ADRC-ADDRNUMBER must be present and the system will create a row for BUT020 to link for each address of a business
partner to its business partner.
Product Master Data
Product Master Data
MARA_DRAD DOKOB MARA
MARA_DRAD_STXH TDOBJECT DRAD
4/23/2019
MARA_DRAD_STXH TDID LTXT
MARA_DRAD_STXL TDOBJECT DRAD
MARA_DRAD_STXL TDID LTXT
MARA_DRAD_STXL LINE_COUNTER A unique number for each text row.
MARA_STXH TDOBJECT MATERIAL
MARA_STXL TDOBJECT MATERIAL
MARA_STXL LINE_COUNTER A unique number for each text row.
MARC_STXH TDOBJECT MDTXT
MARC_STXH TDID LTXT
MARC_STXL TDOBJECT MDTXT
MARC_STXL TDID LTXT
MARC_STXL LINE_COUNTER A unique number for each text row.
MBEW BWKEY If the valuation area is set to plant and

MARC is on the same sheet, use MARC-
WERKS
MEAN LFNUM A unique number for each GTIN
MVKE_STXH TDOBJECT MVKE
MVKE_STXH TDID 0001
MVKE_STXL TDOBJECT MVKE
MVKE_STXL TDID 0001
MVKE_STXL LINE_COUNTER A unique number for each text row.
Business Partner Relationship Data
Business Partner Relationship Data
BUT050_TD (Time Dependent and General DATE_TO 99991231 (31.12.9999)

Data)
BUT050_TD (Time Dependent and General DATE_FROM 00010101 (1.1.0001)

Data)
BUT052 (Techn.Link Addresses) NATION Blank
BUT053 (Company Interest) DATE_TO 99991231 (31.12.9999)
ADCP (Person/Address Assignment) NATION Blank
ADCP (Person/Address Assignment) DATE_FROM Default value 00010101 (1.1.0001)
ADR6 (E-Mail), ADR3 (Fax), ADR2 (Phone), CONSNUMBER A unique number for each address
ADR12 (URL)
4/23/2019
ADR6 (E-Mail), ADR3 (Fax), ADR2 (Phone), DATE_FROM 00010101 (1.1.0001)

ADR12 (URL)
ADR12 (URL) URI_TYPE HPG (Homepage)
Note
The table BUT050_TD (Time Dependent and General Data) can be omitted. In this case, the table BUT053 must be present.
For each row in BUT053, a row for BUT050_TD is created. PARTNER1, PARTNER2, RELTYP, and DATE_TO are used for these
rows.
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 mass processing or a consolidation process.
Features
The following business objects are supported:
Business Partner
Business Partner Relationship
Material
Activities
1. Enter Selection Criteria
Enter selection criteria to obtain a list of consolidation processess and mass processess and choose Go.
All changes corresponding to your selection criteria are displayed.
2. Obtain additional information on the processess
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.

MDG Central Governance - Config Guide - 1

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

MDG Central Governance - Config Guide - 1

Caricato da

Copyright:

Formati disponibili

4/23/2019

SAP Master Data Governance

SAP Master Data Governance | MDG92_SP01

For more information, please visit the SAP Help Portal.

SAP Master Data Governance

Product SAP Master Data Governance 9.2

Based On For detailed information, see SAP Note 2645428 .

Centrally Governed Master Data

Pre-Built Content for Master Data Domains

Replicate Central Master Data

Load Master Data

Ensure Master Data Quality

Change Multiple Master Data Records

Process Quality Analytics

SAP Fiori Apps

Consolidate Master Data

Con guration of SAP Master Data

Con guration of SAP MDG, Central

Working with SAP Master Data Governance

Working with SAP MDG, Consolidation and

Consolidating Master Data

For details see, Specify Process Template.

Normalization: Baker Str, is converted to Baker Street.

For more information see, Standardization.

For more information see, Matching.

Best Record Calculation

For more information see, Best Record Calculation.

For more information see, Validation.

For more information see, Activation.

Master Data Governance, Consolidation

Integration of standardization capabilities, including BRFplus integration

Use matching capabilities to identify duplicates

Use con gurable best-record calculation

Perform analytics for each process step including drill-down capabilities

Split and remove data from the process

Consolidate classi cation data

Consolidate active records

Consolidate business partner relationships

Supported Device Types

Relevant Business Catalog

SAP_CMD_BC_BP_MONPROCS_PC for business partners

Import Data for Consolidation

Supported Device Types

File Format for Data Import

CSV Format (*.csv)

Lines are terminated by <CR>, <LF>, or <CR>.

Adjacent elds are separated with a semi-colon.

Fields can be enclosed in double-quotes.

A eld must be enclosed in double-quotes, if it contains a semi-colon, <CR>, <LF>, or <CR>

The system assumes an encoding with UTF-8.

SOURCE_ID and SOURCE_RECENCY are special columns in the le.

No conversion is applied to elds contents.

Oﬃce Open XML Format (*.xlsx)

Object-Speci c Defaulting of Values

Busines Partner Data

Business Partner Data

Table Reference Field Default Value

BUT100 (Role) DFVAL Blank

BUT021_FS (Address Usage) ADR_KIND XXDEFAULT

BUT021_FS (Address Usage) VALID_TO 99991231

ADRP (Person Data) NATION Blank

ADRP (Person Data) DATE_FROM 00010101

ADRP (Person Data) DATE_TO 99991231 or BUT021_FS-VALID_TO (if