SAP MDG Consolidation

PUBLIC
2023-10-30
Configuration of SAP MDG, Consolidation and

Mass Processing
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Configuration of SAP MDG, Consolidation and Mass Processing. . . . . . . . . . . . . . . . . . . . . . . . 4
2 Services for SAP MDG, Consolidation and Mass Processing (Web Dynpro and Gateway)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3 Configure Gateway Services for SAP MDG, Consolidation and Mass Processing. . . . . . . . . . . . .8
4 Set up the Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 Configure Process Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6 Specify Adapters for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.1 Configure SAP HANA Smart Data Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7 Specify Adapters for Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8 Define Rules Using the Business Rule Framework plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9 Configure Scope for Mass Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
10 Configure Standardization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
11 Configure Parallelization for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
12 Configure Matching for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
13 Configure Matching for Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
14 Configure Best Record Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
15 Configure Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
16 Configure Filter and Remove. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
17 Configure Activation for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
18 Configure Activation for Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
19 Specify Process Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
20 Data Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
20.1 Example: Loading Vendor and Customer Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
21 Usage of Consolidation Processes for SOA-Inbound Processing. . . . . . . . . . . . . . . . . . . . . . . . 72
22 Configure MDG, Consolidation and Mass Processing for Custom Objects. . . . . . . . . . . . . . . . . 73
Configuration of SAP MDG, Consolidation and Mass Processing

2 PUBLIC Content
22.1 Preparations for Custom Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
22.2 Create and Configure Process Model for Custom Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
22.3 Configure BRFplus for Custom Object Consolidation and Mass Processes. . . . . . . . . . . . . . . . . . . . 76
22.4 Configure Gateway Service and Activate BC-Set for Custom Objects. . . . . . . . . . . . . . . . . . . . . . . . 77
22.5 Add Tile to Launchpad for Custom Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Content PUBLIC 3
1 Configuration of SAP MDG, Consolidation
and Mass Processing
Use
SAP MDG, consolidation and mass processing enables you to consolidate your master data and it enables you
to run mass processes to update multiple master data records at a time. The order of the process steps as well
as the behavior of each individual process step type can be adapted to your requirements.
This document provides the information you require to set up SAP MDG, consolidation and mass processing. It
contains information about Customizing as well as the information about additional activities that you need to
execute.
Prerequisites
Services
You have activated the gateway services and services for web dynpro applications. For a detailed list of the
relevant services, see Services for SAP MDG, Consolidation (Web Dynpro and Gateway) [page 7].
Business Function
In the Customizing activity Activate Business Functions (transaction SFW5), you have activated at least one of
the following sets of business functions:
• Master Data Governance for Customer, Consolidation 8.0 and Master Data Governance for Customer,
Consolidation and Mass Processing 9.0
• Master Data Governance for Supplier, Consolidation 8.0 and Master Data Governance for Supplier,
Consolidation and Mass Processing 9.0
• Master Data Governance for Material, Consolidation and Mass Processing 9.0
 Note
If you want to run MDG, consolidation and mass processing for custom objects you have to activate the
business function Master Data Governance for Custom Objects, Consolidation and Mass Procesing 9.0
 Note
If you want to run SAP MDG, consolidation and mass processing in parallel with SAP MDG, central
governance you have to activate the corresponding business functions. For more information, see
Configuration of Master Data Governance
Authorization Objects
You have assigned the relevant authorization objects and roles. For more information about authorization
objects and roles, see Authorization Objects and Roles Used by SAP MDG, Consolidation and Mass Processing.

4 PUBLIC Configuration of SAP MDG, Consolidation and Mass Processing
Autorization for Workflow System User
The following authorization objects with authorization for all activities are assigned to the workflow system
user (WF batch user).
• MDC_ADMIN
• MDC_PROOT
• MDC_PFILT
• MDC_MASS
• S_BGRFC
SAP HANA-Based Fuzzy Matching
To work with views and rule sets in SAP HANA, the ABAP system database user has the privileges and the
permissions for the tasks listed below:
• Permission
• Create packages and write objects into packages
• Create, change and drop attribute views
• Create, change and drop SQL views
• Create, execute and drop rule sets
• Privileges
• Execute for the object EXECUTE_SEARCH_RULE_SET(SYS) of the schema SYS
• Execute for the object GET_PROCEDURE_OBJECTS of the schema SYS
• Execute for the object TRUNCATE_PROCEDURE_OBJECTS of the schema SYS
For more information, see http://help.sap.com/hana/sap_hana_security_guide_en.pdf and http://

help.sap.com/saphelp_hanaplatform/helpdata/en/cc/602780bb5710148aa2bf6cab3c015b/content.htm .
Basic Configuration of bgRFC
You have configured the bgRFC settings. For more information see, http://help.sap.com/saphelp_nw70/
helpdata/en/44/fda148f5de41dee10000000a1553f6/content.htm .
 Note
If you want to use the automated setup of bgRFC, see SAP Note 1043195 . This note includes the
configuration of web service runtime.
General
Determination of own business system:
Either the MDG hub system and the source systems are connected to the System Landscape Directory (SLD) or
the BAdI MDG_IDM_GET_LCL_SYSTEM is implemented to determine the local system ID.
• To verify the correctness of the SLD content run transaction SLDCHECK in the MDG hub and client systems.
Ignore the browser dialog box. In the systems check that the message reads: Summary: Connection to
SLD works correctly.
• If you decide to implement the BAdI and not to use SLD, see the documentation of the IMG activity under
Master Data Governance Central Governance General Settings Data Replication Define Custom
Settings for Data Replication Define Technical Settings BAdI: Determination of Local System Name .

Configuration of SAP MDG, Consolidation and Mass Processing PUBLIC 5
Process
You run the settings for this process in Customizing under Cross-Application Components Processes and
Tools for Enterprise Applications Master Data Governance Consolidation and Mass Processing .
 Note
You can access all SAP MDG, consolidation and mass processing specific Customizing activities using the
transaction MDCIMG.
1. Services for SAP MDG, Consolidation and Mass Processing (Web Dynpro and Gateway) [page 7]
2. Configure Gateway for SAP MDG, Consolidation and Mass Processing [page 8]
3. Set up the Workflow [page 11]
4. Specify Process Model [page 12]
5. Specify Adapters for Business Partner [page 14]
6. Specify Adapters for Material [page 19]
7. Define Rules Using the Business Rule Framework plus [page 22]
8. Configure Scope of Changeable Fields for Mass Processing [page 24]
9. Configure Standardization [page 25]
10. Configure Parallelization for Update [page 28]
11. Configure Matching for Business Partner [page 30]
12. Configure Matching for Material [page 35]
13. Configure Best Record Calculation [page 39]
14. Configure Validation [page 43]
15. Configure Filter and Remove [page 45]
16. Configure Activation for Business Partner [page 47]
17. Configure Activation for Material [page 51]
18. Specify Process Template [page 55]
19. Data Load [page 57]
20.Usage of Consolidation Processes for SOA-Inbound Processing [page 72]
21. Configure MDG, Consolidation and Mass Processing for Custom Obje [page 73]
Result
The system is configured for SAP MDG, consolidation and mass processing.
More Information
Master Data Governance Security Guide

6 PUBLIC Configuration of SAP MDG, Consolidation and Mass Processing
2 Services for SAP MDG, Consolidation
and Mass Processing (Web Dynpro and
Gateway)
Use
For security reasons the services delivered for Web Dynpro applications initially are available in an inactive state
only. You have to activate the services you want to use.
Activities
To activate the services, proceed as described below in the corresponding system:
1. On the Maintain Services screen (transaction SICF), make sure that the Hierarchy Type SERVICE is
selected, enter theService Name, and choose Execute.
2. Choose Service/Host Activate , to activate the service.
 Note
You have to perform the procedure for each single service you want to activate.
The table below provides a list of the services used in the respective components of MDG, consolidation.
Service Name System Use
MDC_HDB_MATCH Match Configurations Over- Backend system Web dynpro

view
MDC_HDB_MATCH_CONF Create Match Configuration Backend system Web dynpro
MDG_HDB_SV_GENERATION Search View Generation Backend system Web dynpro
MDG_HDB_SV_INITIAL Search View Initial UI Backend system Web dynpro
MDG_CONS Master Data Consolidation FIORI frontend system Gateway

Service

Services for SAP MDG, Consolidation and Mass Processing (Web Dynpro and Gateway) PUBLIC 7
3 Configure Gateway Services for SAP
MDG, Consolidation and Mass Processing
Use
You can run the gateway server either on a separate frontend system or on the backend system.
Gateway server on the frontend system
Prerequisites
• On the frontend system, the launchpad UIMDC01 Master Data Consolidation Launchpad is listed in the
transaction LPD_CUST. This launchpad is part of the standard delivery of SAP MDG, consolidation and
mass processing.
• The following role is available on the frontend system as part of the standard delivery of
SAP MDG, consolidation and mass processing: Master Data Specialist (Consolidation) - Apps
SAP_MDC_BCR_MASTERDATA_SPEC_T.
 Note
In case you want to use MDG, Consolidation for Custom Objects [page 73] the role Master Data
Administrator (Consolidation) - Apps SAP_MDC_BCR_MASTERDATA_ADMIN_T is required on the frontend
system.
The gateway service to be activated for this role as described below is MDC_CUSTOM_OBJECT_SRV.
Activities
1. In the frontend system, create a trusted RFC connection to the backend system. To do so, run
the Customizing activity under SAP Customizing Implementation Guide SAP NetWeaver Gateway
OData Channel Configuration Connection Settings SAP NetWeaver Gateway to SAP System
Manage RFC Destinations (transaction SM59)
• Select the Connection Type 3 Connection to ABAP System.
• On the Technical Settings tab, enter the Target System Settings for the backend system.
• On the Logon & Security tab, mark the Current User indicator and mark the Yes radio button for Trust
Relationship.
• Choose Remote Logon and Connection Test to check the RFC connection.
2. To create an SAP system alias run the Customizing activity under SAP Customizing
Implementation Guide SAP NetWeaver Gateway OData Channel Configuration Connection
Settings SAP NetWeaver Gateway to SAP System Manage SAP System Aliases .
• Enter an SAP System Alias and a Description.
• Use the entry help to select the RFC destination you created in step 1.
• Select DEFAULT as Software Version.

8 PUBLIC Configure Gateway Services for SAP MDG, Consolidation and Mass Processing
3. To activate the service run the Customizing activity under SAP Customizing Implementation Guide
SAP NetWeaver Gateway OData Channel Administration General Settings Activate and Maintain
Services
1. Choose Add Service.
2. Use the entry help to select the system alias you created in step 2.
3. In the Technical Service Name field, enter the technical name of the required service as listed below:
• MDC_PROCESS_SRV__147 MDC Process Object For BP
• MDC_PROCESS_SRV__MDC_147 MDC Process Object For BP light
• MDC_PROCESS_SRV__194 MDC Process Object For Material
4. Choose Get Services.
5. Mark the corresponding entry in the list and choose Add Selected Services.
6. Adjust Technical Service Name if required and choose Continue.
7. Mark the service and choose Add System Alias.
8. Select New Entries and assign the role mentioned above.
 Note
If no entry exists proceed as follows:

1. Choose New Entries.
2. Use the entry help to select the Service Doc. Identifier.
The Service Doc. Identifier has the format <technical service name (see above)>_<service
version (0001)>, for example ZMDC_PROCESS_SRV_0001.
3. Assign the role mentioned above.
4. Use the entry help to select the system alias you created above.
9. Make sure the service has the status Active. To activate the service choose ICF Node Activate .
Gateway server on the backend system
Prerequisites
• The launchpad UIMDC01 Master Data Consolidation Launchpad is listed in the transaction LPD_CUST. This
launchpad is part of the standard delivery of SAP MDG, consolidation and mass processing.
• The following role is available on the frontend system as part of the standard delivery of
SAP MDG, consolidation and mass processing: Master Data Specialist (Consolidation) - Apps
SAP_MDC_BCR_MASTERDATA_SPEC_T.
 Note
In case you want to use MDG, Consolidation for Custom Objects [page 73] the role Master Data
Administrator (Consolidation) - Apps SAP_MDC_BCR_MASTERDATA_ADMIN_T is required.
The gateway service to be activated for this role as described below is MDG_CUSTOM_OBJECT_SRV.
Activities
To activate the service run the Customizing activity under SAP Customizing Implementation Guide
SAP NetWeaver Gateway OData Channel Administration General Settings Activate and Maintain
Services

Configure Gateway Services for SAP MDG, Consolidation and Mass Processing PUBLIC 9
2. Use the entry help to select the system alias you created in step 2.
3. In the Technical Service Name field, enter the technical name of the required service as listed below:
• MDC_PROCESS_SRV__147 MDC Process Object For BP
• MDC_PROCESS_SRV__MDC_147 MDC Process Object For BP light
• MDC_PROCESS_SRV__194 MDC Process Object For Material
4. Choose Get Services.
5. Mark the corresponding entry in the list and choose Add Selected Services.
6. Adjust Technical Service Name if required and choose Continue.
7. Mark the service and choose Add System Alias.
8. Select New Entries and assign the role mentioned above.
 Note
If no entry exists proceed as follows:

2. Use the entry help to select the Service Doc. Identifier.
The Service Doc. Identifier has the format <technical service name (see above)>_<service version
(0001)>, for example ZMDC_PROCESS_SRV_0001.
3. Assign the role mentioned above.
4. Use the entry help to select the system alias you created above.
9. Make sure the service has the status Active. To activate the service choose ICF Node Activate .
Result
You have configured the gateway services for SAP MDG, consolidation and mass processing.
More Information
For further information of gateway services, see http://scn.sap.com/community/gateway .
For further information of SAP FIORI, see http://help.sap.com/fiori .

10 PUBLIC Configure Gateway Services for SAP MDG, Consolidation and Mass Processing
4 Set up the Workflow
Workflow Template
The workflow template delivered for SAP MDG, consolidation and mass processing is WS54500001.
 Note
Do not enter this workflow template as Receiver Type in the type linkage.
Activate type linkage
To check the type linkage settings required for the workflow run transaction SWE2 and ensure that the Object
Type BUS2240 has the following settings:
• Event STARTED
• Receiver Type blank
• Linkage Activated yes
• Enable event queue no
The Linkage Activated indicator must not be active for other receiver types of the object type BUS2240 and the
event STARTED. This receiver type is defined by the Receiver Type Function Module MDC_RECEIVER_TYPE_GET.
Make sure that Receiver Function Module SWW_WI_CREATE_VIA_EVENT_IBF is entered.
 Note
The Customizing for the object type BUS2240 is delivered in the client 000 in transaction SWE2.

Set up the Workflow PUBLIC 11
5 Configure Process Model
Use
In the standard delivery, process models for the following business object types are preconfigured:
• Business Partner 147

• The data model includes tables for business partner, customer, and supplier.
• The validation uses ERP checks.
• Records can be activated with SAP MDG, central governance using change requests and cleansing
cases or can be activated directly.
• The replication uses the Data Replication Framework (DRF).
• Business Partner: Non-SAP-BS MDC_147
• The data model includes tables for business partner, customer, and supplier.
• SAP does not deliver a validation step, therefore no ERP checks are used.
• Material 194
• The data model includes tables for material.
• The validation uses ERP checks.
• Records can be activated with SAP MDG, central governance using change requests or can be activated
directly.
• The replication uses the Data Replication Framework (DRF).
Activities
 Caution
Do not change the standard configuration unless you extend fields or nodes of the data model, or unless
you use your own business object type.
If you extend fields or nodes of the data model, or if you use your own business object type, further
configuration is required.
For information about how to extend fields and nodes, see How-to Information for SAP Master Data
Governance .
 Note
To perform the configuration steps described below, cross client customizing authorization is required.
To configure the process model for SAP MDG, consolidation, run the Customizing activity under Master Data
Governance Consolidation and Mass Processing Configure Process Model .

12 PUBLIC Configure Process Model
1. To see the tables that are assigned to the business object for the consolidation process, select the business
object type and choose Tables.
2. To add further tables, select New Entries.
Only tables listed under a specific business object type are taken into account in the consolidation process.
One table is marked as the Root table.
3. In the Tables view you can specify further settings for the customer specific tables:
• For tables that are relevant for process data, set the Process indicator.
• If you want to define BRF+ rules or a specific table in the Customizing activity Define Rules Using the
Business Rule Framework plus, set the BRF+ indicator.
• If you want a table to omit the rules for the best record calculation, set the Omit Rules indicator.
• If you want a table to be hidden on the UI, set the Hidden indicator.
4. In the Tables view, select a specific table and choose Joins to see the joined tables.
5. To add further tables, select New Entries.
The Process indicator and the Active indicator show whether a table is used in the process data model or in
the active data model.
6. In the Joins view, select a table and choose Join Fields to see the join conditions.
If required select New Entries to add further fields to join the tables. The Process indicator and the Active
indicator show whether a field is used in the process data model or in the active data model.
7. In the Table Fields view you can specify settings for the fields of the customer specific tables.
• If you want a field not to be processed by the user on the UI, set the Technical indicator.
• If you want a field to be read-only on the standard Fiori UI, set the Read-only indicator.
• If you want a field to be used as selection criteria on the UI, set the Selective indicator.
• If you want a field to be hidden on the UI, set the Hidden indicator.

Configure Process Model PUBLIC 13
6 Specify Adapters for Business Partner
Use
The standard delivery contains the adapters listed below for the different step types of the consolidation
process. You can add adapters, you created to meet your business requirements. Each adapter can be
configured individually in the corresponding Customizing activity.
Standardization
CL_MDC_ADAPTER_BP_BAS_STD (Business Address Services)
• Uses the third party interface of Business Address Services (BAS) to execute address validation against
(external) address repositories.
• You configure this adapter in the Customizing activities Configure Parallelization for Standardization and
Configure Business Objects Data Services for BAS Adapter.
• Default behaviour of the adapter without further configuration: No parallelization
• In the SAP Fiori UI users can switch between the configurations for this adapter.
CL_MDC_ADAPTER_BP_IM_STD (HANA smart data quality)
• Adapter that uses the SAP HANA smart data quality and does the standardization directly on the SAP
HANA database. The standardization of names and addresses is supported. The adapter does not support
databases other than SAP HANA.
• To use this adapter the configuration steps as described under Configure SAP HANA Smart Data Quality
[page 17] are required.
• In the SAP Fiori UI users can switch between the configurations for this adapter or adjust the selected
configurations by creating custom configuration - according to their authorizations.
CL_MDC_ADAPTER_BP_KEY_MAP_STD (Evaluate Key Mapping for Business Partners & ERP Customers /
Suppliers)
• If the key mapping between the source system and the consolidation system is set up, the source field
value is replaced by the consolidation system value
• If no key mapping is set up, the source field value is deleted.
CL_MDC_ADAPTER_BP_VALUEMAP_STD (Evaluate Value Mapping for Business Partners & ERP

Customers / Suppliers)
• If the value mapping between the source system and the consolidation system is set up, the source field
value is replaced by the consolidation system value
• If no value mapping is set up, the source field value is kept.
CL_MDC_ADAPTER_BRF_STD ( BRFplus)
• Use this adapter if you want to run BRF+ for checks and data enrichment on single record level. For further
information, see the Customizing activity Define Rules Using the Business Rule Framework plus.
Matching
CL_MDC_ADAPTER_BP_BAS_MTC (Business Address Services)

14 PUBLIC Specify Adapters for Business Partner
• Adapter that uses the third party interface of Business Address Services (BAS). Records are checked one
by one with index, therefore the adapter is not appropriate for mass data (more than 500.000).
• You configure this adapter in the Customizing activity Configure Business Objects Data Services for BAS
Adapter.
• In the SAP Fiori UI users can switch between the configurations for this adapter.
CL_MDC_ADAPTER_BP_IM_MTC (HANA smart data quality)
• Adapter that uses the SAP HANA smart data quality and does the standardization directly on the SAP
HANA database. The standardization of names and addresses is supported. The adapter does not support
databases other than SAP HANA.
• To use this adapter the configuration steps as described under Configure SAP HANA Smart Data Quality
[page 17] are required.
CL_MDC_ADAPTER_FUZZY_MTC (HANA fuzzy search)
• Adapter that uses the SAP HANA fuzzy algorithm. SAP HANA rulesets are generated for this adapter which
can be configured and implemented. The adapter does not support databases other than SAP HANA.
• To use this adapter you have to configure it in the Customizing activity Create Match Configurations for
Fuzzy Matching.
Best record calculation
CL_MDC_ADAPTER_BP_BRC (Business Partner Best Record Calculation)
• Supports the best record calculation. The adapter works on an application server and supports by default
the following rules:
• BRFPLUS
• SOURCE_SYSTEM
• RECENCY
• COMPLETENESS
• You configure this adapter in the Customizing activities Specify Rules for Best Record Calculation and
Specify Order of Rules for Best Record Calculation.
• Default behaviour of the adapter without further configuration:
• No parallelization
• If an active record is available within a matchgroup it is chosen as best record.
• If no active record is available the best record is chosen randomly.
Due to the random selection described above, we recommend to use this adapter only with adequate
configuration.
Validation
CL_MDC_ADAPTER_BP_VAL (Business Partner Validations (Business Suite))

Specify Adapters for Business Partner PUBLIC 15
• Validation of business partner data using the business suite standard APIs. As a precondition to use this
adapter the Customer Vendor Integration (CVI) has to be configured.
• You configure this adapter in the Customizing activitiy Configure Validation.
Activation
CL_MDC_ADAPTER_BP_ACT (Business Partner Activation (Consolidation))
• Activation of business partner data using the business suite standard APIs. As a precondition the
Customer Vendor Integration (CVI) has to be configured.
• You configure this adapter in the Customizing activity Configure Activation for Business Partner.
• Direct activation of correct records
• No activation of incorrect records
• Replication as part of the activation step
Replication
CL_MDC_ADAPTER_BP_REP (Business Partner Replication with DRF)
• Executes the replication of business partners if you use SAP MDG, consolidation and mass processing as a
standalone application.
 Note
In case MDG, consolidation is processed in parallel with SAP MDG, central governance we recommend
to use the adapter CL_MDC_ADAPTER_BP_ACT for replication.
• Configuring the adapter is required.
Edit
CL_MDC_ADAPTER_EDI (Interactive Mass Processing)
• Use this adapter if you want to use the mass processing.
Filter & Remove
CL_MDC_ADAPTER_BP_FAR (Delete Business Partners with incomplete address data)
• Based on the results of the best record calculation all business partner records without any address data
are removed and deleted.
CL_MDC_ADAPTER_FAR (Filter & Remove)
• Based on the results of the predecessor step a selection of records is either moved to a parallel
consolidation process or it is removed and deleted.
• To configure the adapter run the Customizing activity Configure Filter and Remove.

Update
CL_MDC_ADAPTER_BRF_UPD (BRFplus)
• Use this adapter if you want to run BRF+ for checks and data enrichment for mass update. For further
information, see Define Rules Using the Business Rule Framework plus.
Activities
 Note
To specify the adapters required for a specific step type of the consolidation process of a business object
run the Customizing activity under Master Data Governance Consolidation and Mass Processing Specify
Adapters .
If you want to add own adapters or assign adapters to further business object types, proceed as described:

2. In the BO Type field, select the business object type using the input help.
3. In the Step Type field, select a step type using the input help.
4. In the Adapter field, enter the adapter. The adapter has to be part of the customer namespace.
The adapter has to be assigned to a class that has implemented the interface IFMDC_ADAPTER.
5. Repeat the steps 2 to 4 to enter all required adapters.
Constraints
To ensure that within the application the Adapter Configuration is displayed correctly in the Manage
Consolidation Processes process detail screen, the amount of configurations per adapter should not exceed
100.
6.1 Configure SAP HANA Smart Data Quality
• To configure SAP HANA Smart Data Quality proceed as described below: :

1. Deploy the address directory files for the required countries according to chapter 3.2
Download and Deploy Directory Files of the SAP HANA Smart Data Quality Installation and
Configuration Guide: https://help.sap.com/doc/dd356918159e4ba1a32927b0b917b78c/1.0_SPS12/
en-US/SAP_HANA_EIM_Administration_Guide_en.pdf.
2. Enable the data provisioning server according to chapter 2.2 Enable the Data Provisioning Server.
3. Enable the script server according to chapter 3.1 Enable the Script Server.
4. Enable the operation cache according to chapter 5.5.3 Configuring
the Operation Cache of the SAP HANA Smart Data Quality

Specify Adapters for Business Partner PUBLIC 17
Administration Guide: https://help.sap.com/doc/c2f6df6348ab44fbb66ff5545305381e/1.0_SPS12/
en-US/loio16f160c6deef44f89e23848698b7c7d9_16f160c6deef44f89e23848698b7c7d9.pdf.
5. Run the Customizing activity Import Predefined Settings for SAP HANA Smart Data Quality to
activate the BC Set CA-MDG-EE-BP_IMHANA_C01 (MDG-BP Consolidation: IM in Hana).
6. Run the transaction SM30 to check the view SIMDQ_ADDR_STG and in case there is an entry with
an empty Country field, delete this table entry. For more information, see point 3 of the SAP note
2179627 .
 Note
In case you are not using HANA SDQ Geocode functionality SAP recommends to set the geocode and
geocode_rt values to 0 under adapter_operation_cache | enable_adapter_operation_cache within the
script server ini. A script server restart may be required after changing these settings.

7 Specify Adapters for Material
Use
The standard delivery contains the adapters listed below for the different step types of the consolidation
process. You can add adapters, you created to meet your business requirements. Each adapter can be
configured individually in the corresponding Customizing activity.
Standardization
CL_MDC_ADAPTER_BRF_STD (BRFplus)
• Use this adapter if you want to run BRF+ for checks and data enrichment on single record level. For further
information, see the Customizing activity Define Rules Using the Business Rule Framework plus.
CL_MDC_ADAPTER_MAT_KEY_MAP_STD (Evaluate Key Mapping for Material)
• If the key mapping between the source system and the consolidation system is set up, the source field
value is replaced by the consolidation system value.
• If no key mapping is set up, the source ID is deleted.
CL_MDC_ADAPTER_MAT_VALMAP_STD (Evaluate Value Mapping for Material)
• If the value mapping between the source system and the consolidation system is set up, the source field
value is replaced by the consolidation system value.
• If no key mapping is set up, the source ID is deleted.
Matching
CL_MDC_ADAPTER_FUZZY_MTC (HANA fuzzy search)
• Adapter that uses the SAP HANA fuzzy algorithm. SAP HANA rulesets are generated for this adapter which
can be configured and implemented. The adapter does not support databases other than SAP HANA.
• To use this adapter you have to configure it in the Customizing activity Create Match Configurations for
Fuzzy Matching.
CL_MDC_ADAPTER_MAT_MTC Material Matching (Old Material Number)
• Adapter to be used if you do not use SAP HANA

• You can use the coding of the method as a template for own methods.
Best record calculation
CL_MDC_ADAPTER_MAT_BRC (Material Best Record Calculation)
• Supports the best record calculation. The adapter works on an application server and supports by default
the following rules:
• BRFPLUS
• SOURCE_SYSTEM
• RECENCY

Specify Adapters for Material PUBLIC 19
• COMPLETENESS
• You configure this adapter in the Customizing activities Specify Rules for Best Record Calculation and
Specify Order of Rules for Best Record Calculation
• If an active record is available within a matchgroup it is chosen as best record.
• If no active record is available the best record is chosen randomly.
Due to the random selection described above, we recommend to use this adapter only with adequate
configuration.
Validation
CL_MDC_ADAPTER_MAT_VAL (Material Validations (Business Suite))
• Validation of material data using the business suite standard APIs.

• You configure this adapter in the Customizing activitiy Configure Validation.
Activation
CL_MDC_ADAPTER_MAT_ACT (Activation for Material)
• Activation of material data using the business suite standard APIs.

• You configure this adapter in the Customizing activity Configure Activation for Material.
• Direct activation of correct records
• No activation of incorrect records
• Replication as part of the activation step
Replication
CL_MDC_ADAPTER_MAT_REP (Material Replication with DRF)
• Executes the replication of material if you use SAP MDG, consolidation and mass processing as a
standalone application.
 Note
In case MDG, consolidation and mass processing is processed in parallel with SAP MDG, central
governance we recommend to use the adapter CL_MDC_ADAPTER_MAT_ACT for replication.
• Configuring the adapter is required.
Edit
CL_MDC_ADAPTER_EDI (Interactive Mass Processing)

20 PUBLIC Specify Adapters for Material
• Use this adapter if you want to use the mass processing.
Filter & Remove
CL_MDC_ADAPTER_FAR (Filter & Remove)
• Based on the results of the predecessor step a selection of records is either moved to a parallel
consolidation process or it is removed and deleted.
• To configure the adapter run the Customizing activity Configure Filter and Remove.
Update
CL_MDC_ADAPTER_BRF_UPD (BRFplus)
• Use this adapter if you want to run BRF+ for checks and data enrichment for mass update. For further
information, see Define Rules Using the Business Rule Framework plus.
Activities
 Note
To specify the adapters required for a specific step type of the consolidation process of a business object
run the Customizing activity under Master Data Governance Consolidation and Mass Processing Specify
Adapters .
If you want to add own adapters or assign adapters to further business object types, proceed as described:

2. In the BO Type field, select the business object type using the input help.
3. In the Step Type field, select a step type using the input help.
4. In the Adapter field, enter the adapter. The adapter has to be part of the customer namespace.
The adapter has to be assigned to a class that has implemented the interface IFMDC_ADAPTER.
5. Repeat the steps 2 to 4 to enter all required adapters.
Constraints
To ensure that within the application the Adapter Configuration is displayed correctly in the Manage
Consolidation Processes process detail screen, the amount of configurations per adapter should not exceed
100.

Specify Adapters for Material PUBLIC 21
8 Define Rules Using the Business Rule
Framework plus
Use
You can use BRFplus checks for the following process steps:
• Standardization (STD)
• Validation (VAL)
• Best record calculation (BRC)
Prerequisites
In the Customizing activity under Master Data Governance Consolidation and Mass Processing Configure
Process Modell you have selected a business object type and in the Tables view you have set the BRFplus
indicator for certain tables.
• The system will create the functions required in BRRplus.

• The naming convention is MDC_<abreviation of process step>_FOR_<table name>, for example:
MDC_STD_FOR_BUT_ADRC_PRC.
To use BRFplus rules for a certain process step type proceed as described:
• Standardization: Select the corresponding adapter in the Process Template Step view in the Customizing
activity under Master Data Governance Consolidation and Mass Processing Specify Process
Template .
• Validation: Set the Execute BRFplus indicator for a specific adapter in the Customizing activity under
Master Data Governance Consolidation and Mass Processing Configure Validation .
• Best record calculation: Run the Customizing activity under Master Data Governance Consolidation
and Mass Processing Specify Order of Rules for Best Record Calculation and select an entry. In the
Order of Rules for Tablesview select the Rule ID BRF+ for specific tables.
Activities
1. To define rules in BRFplus run the Customizing activity under Master Data Governance Consolidation
and Mass Processing Define Rules Using the Business Rule Framework plus .
2. In the Business Rule Framework plus screen choose Search.
3. In the Search dialog box enter MDC* as Application Name and select Function as Object Type and choose
Search.

22 PUBLIC Define Rules Using the Business Rule Framework plus
4. Select your function in the Search Result list and proceed as described in the BRFplus documentation.

Define Rules Using the Business Rule Framework plus PUBLIC 23
9 Configure Scope for Mass Processing
Use
You can use the Configure Scope customizing activity to configure the default scope for your mass process.
This default scope is displayed on the Scope screen in the SAP Fiori UI. This scope determines the fields that
are available in the Edit step of the SAP Fiori UI.
Activities
To configure the scope run the Customizing activity under Master Data Governance Consolidation and
Mass Processing Configure Scope .
1. Select New Entries.

2. Enter a Scope ID and a Scope Description.
3. Enter a BO Type using the entry help.
4. Mark the scope you created and select Scope Fields.
6. Enter a Table using the entry help.
7. Enter a Field Name using the entry help.
8. Choose Next Entry to enter further fields.

24 PUBLIC Configure Scope for Mass Processing
10 Configure Standardization
Use
Within the process step standardization, address data is enriched and normalized by the system. In addition a
check ensures that a specific address really exist:
 Example
• Enrichment: A record only contains the postal code 69190. The corresponding city Walldorf is added.
• Normalization: Baker Str, is converted to Baker Street
Prerequisites
You have configured SAP HANA Smart Data Quality. For more information, see Configure SAP HANA Smart
Data Quality [page 17]
Activities
To configure the standardization for MDG, consolidation, run the Customizing activity under Master Data
Governance Consolidation and Mass Processing Configure Standardization :
1. To configure the number of parallel processes run the Customizing activity Configure Parallelization for
Standardization.
Adapting the number of parallel processes can improve the performance of the consolidation process.
 Note
To use parallelization in SAP MDG, consolidation you have to set up an RFC destination:
• To create the bgRFC inbound destination manually, the authorization object S_BGRFC with activity
02 and type 07 has to be assigned to you.
1. Run transaction SBGRFCCONF.
2. On the Define Inbound Dest. tab choose Create.
3. Enter a name in the Destination field.
4. Enter MDC_QUEUE_ in the Prefixes field.
If you use a queue prefix other than MDC_QUEUE_ this has to be entered in the corresponding
field as described below.
5. On the Scheduler: Destination tab select the destination by double clicking on it.
If the destination does not exists, proceed as described:
1. Choose Create and on the bgRFC Configuration dialog box select Inbound.

Configure Standardization PUBLIC 25
2. Enter the destination name into the Destination field and leave all other values as
defaulted.
6. In the Open Connections field enter the number of allowed parallel processes or queues you
wish to be managed by this destination. This number also specifies the maximum of parallel
processes to be configured during the step configuration.
• If you do not create the bgRFC inbound destination manually the very first consolidation
process will trigger the automatic creation of the inbound destination under prerequisite that the
authorization object S_BGRFC with full authorization is assigned to workflow system user.
For more information see http://help.sap.com/saphelp_nw70ehp2/

helpdata/de/f0/225c3c60065627e10000000a114084/content.htm

2. Enter a Configuration ID and the corresponding description
3. In the Number of Processes field enter the number of processes you want to be processed in parallel.
4. If required enter the Prefix for Queue Name.
 Note
If you use queue prefixes other than MDC_QUEUE_ these have to be entered in the Prefix for Queue
Name field.
2. To configure the Business Objects Data Services for BAS Adapter, see the documentation of the
Customizing activity Configure Business Objects Data Services for BAS Adapter.
Check the Customizing settings under SAP BusinessObjects Data Quality Management and adapt if
required.
3. To import the predefined settings for SAP HANA smart data quality run the Customizing activity Import
Predefined Settings for SAP HANA Smart Data Quality.
In this Customizing activity, you can activate the BC Set CA-MDG-EE-BP_IMHANA_C01 MDG-BP
Consolidation: IM in Hanacontaining predefined sets of table entries, that are required to run the process
steps standardization and matching with the adapters for the SAP HANA smart data quality.
The BC Set contains settings for the tables listed below. You can use transaction SM30 to configure some
of these tables to fulfill your requirements. Be aware, that some settings are not to be changed. For details,
see the description for each table.
Standardization and Matching
• SIMDQ_INP_FILTER IM in HANA Filter for input
Settings to specify filters for standardization and matching. Records can be filtered out and do not take
part in the corresponding process step.
 Note
To ensure the correct processing of the consolidation process, the settings delivered by SAP are
not to be changed.
Standardization
• SIMDQ_ADDR_STG IM in HANA address related settings
Settings to specify the address standardization, for example address formats such as Woodstr. versus
Wood Street.
• SIMDQ_OTHR_STG IM in HANA non-address settings

26 PUBLIC Configure Standardization
 Note
The settings delivered by SAP are required for technical reasons. Changing these settings does not
have any impact.
Matching
• SIMDQ_CMPRSRC IM in HANA compare source settings for Match Policy
Settings to specify the data sources to be considered for matching. The delivered settings compare
process data with process and active data and do not compare active data with each other.
 Note
not to be changed.
• SIMDQ_MTCADDRSTG IM in HANA address settings for the Match Policy

Settings to specify the matching for addresses, such as the threshold.
• SIMDQ_MTCFIRMSTG IM in HANA firm settings for the Match Policy
Settings to specify the matching for firms, such as the threshold.
• SIMDQ_MTCPERSTG IM in HANA person settings for the Match Policy
Settings to specify the matching for persons, such as the threshold.
• SIMDQ_MTCCSTMSTG IM in HANA custom component settings for Custom Match Policy
Settings to specify the matching for ID numbers.
1. To adapt the predefined settings, run transaction SM30.
2. Enter the table in the Table/View field and choose Edit.

Configure Standardization PUBLIC 27
11 Configure Parallelization for Update
Use
Within the process step update data is updated by the system using BRF+ rules.
For more information, see Define Rules Using the Business Rule Framework plus [page 22].
For the process step update you can configure the number of parallel processes to improve the performance of
the consolidation process.
Prerequisites
• To create the bgRFC inbound destination manually, the authorization object S_BGRFC with activity 02 and
type 07 has to be assigned to you.
If you use a queue prefix other than MDC_QUEUE_ this has to be entered in the corresponding field as
described below.
2. Enter the destination name into the Destination field and leave all other values as defaulted.
6. In the Open Connections field enter the number of allowed parallel processes or queues you wish to
be managed by this destination. This number also specifies the maximum of parallel processes to be
configured during the step configuration.
• If you do not create the bgRFC inbound destination manually the very first consolidation process will
trigger the automatic creation of the inbound destination under prerequisite that the authorization object
S_BGRFC with full authorization is assigned to workflow system user.

Activities
To configure the parallelization for the process step update run the Customizing activity under Master Data
Governance Consolidation and Mass Processing Configure Parallelization for Update .

28 PUBLIC Configure Parallelization for Update
• Choose New Entries.
• Enter a Configuration ID and the corresponding description.
• In the Number of Processes field enter the number of processes you want to be processed in parallel.
• Enter the Prefix of the Queue Name.

Configure Parallelization for Update PUBLIC 29
12 Configure Matching for Business Partner
Use
Within the process step matching, the data records to be consolidated are checked for possible duplicates.
According to a configured threshold records are considered to be duplicates and are displayed as match
groups in the attached match review.
Prerequisites
If you want to run matching using SAP HANA Smart Data Quality, you have to configure SAP HANA Smart Data
Quality. For more information, see Configure SAP HANA Smart Data Quality [page 17]
Activities
To configure the matching for MDG, consolidation, run the Customizing activities under Master Data
Governance Consolidation and Mass Processing Configure Matching :
1. To create the match configurations for the fuzzy matching run the Customizing activity Create Match
Configurations for Fuzzy Matching.
In this Customizing activity, you define and generate a match configuration that SAP HANA uses to match
master data records when using fuzzy matching. This activity is only possible within a client allowing
cross-client changes. Configurations created here are used during configuration of process templates
when assigning step type matching and adapter fuzzy matching.
 Note
SAP provides the standard match configuration BPMATCH1 that can act as template to help you to
define and generate your own match configurations.
This Customizing activity calls the Web Dynpro application Match Configuration MDC_HDB_MATCH. You can
use this screen to create, change, copy, and delete a match configuration.
• Create match configuration
1. To create a match configuration, choose New.
2. On the General Data screen, enter a name in the Match Configuration field.
3. Enter a description in the Description field.
4. Enter the business object type in the Business Object Type field.
5. Enter a name for the SAP HANA package in the HANA Package field.
The SAP HANA Package is generated with this name in the SAP HANA database when the
match configuration is created. After the generation of the package its name cannot be changed
anymore.

30 PUBLIC Configure Matching for Business Partner
6. Enter an ABAP package in the ABAP Package field.
 Note
Do not use a package from standard delivery but create a package using transaction SE80.
• On the Select Attributes screen, the attributes in the tables from the process model are
presented in tree form. You can select the attributes that are relevant for matching in your match
configuration.
• On the Review and Generate screen, you can review your choices from the previous screens, and if
necessary, you can go back to the previous screens to make changes.
• The Generate button generates the match configuration. Before generation you must save the
configuration.
 Note
After generating the configuration you may maintain the rule set in the SAP HANA studio to meet
your requirements.
• The rule set can be found in the package used for creating the match configuration. The rule
set naming convention is: <MatchConfigurationName>RULESET.searchruleset.
• By default one rule is generated with all the selected match attributes with minimum fuzziness
of 0.8. All attributes are equally weighted.
• To update the Rule Set, edit the rule set in the repositories view. Editing in the repositories
view is possible since SAP HANA Studio SPS09. Authorizations should be the same as for the
project explorer view.
1. Create a repository work space.
2. Open the rule set in the package folder
3. Edit the rule set to change rule property or column property and conditions, such as the
minimum fuzziness value or weight of an attribute.
4. Save and Activate your changes.
• For more information see the documentation on the SAP Help Portal:
• Overview - SAP HANA Studio (http://scn.sap.com/docs/DOC-60363 )
• SAP HANA Search Developer Guide (http://help.sap.com/hana/
SAP_HANA_Search_Developer_Guide_en.pdf )
• SAP HANA Fuzzy Search Reference (http://help.sap.com/hana/
SAP_HANA_Fuzzy_Search_Reference.pdf )
 Note
When the match configuration is transported to the target system, the HANA package name is not
transported and the field will be blank. In Edit mode the configuration must be updated with the
appropriate HANA package name, saved and generated in the target system.
• Edit match configuration

To edit a match configuration, select the entry and choose Edit.

Configure Matching for Business Partner PUBLIC 31
 Note
If you change the Select Attributes section by adding or removing attributes you have to set the
Re-generate Rule Setindicator. Any manual adjustment done on the ruleset has to be done on the
regenerated rule set if intended.
• Copy match configuration

To copy a match configuration, select the entry and choose Copy.
In the Copy Match Configuration dialog box, enter the name of the target Match Configuration.
 Note
After copying the configuration you may maintain the rule set in the SAP HANA studio to meet your
requirements. To do so, proceed as described under Create match configuration.
• Delete match configuration

To delete a match configuration, select the entry and choose Delete and OK.
 Note
The match configuration is marked for deletion. To finally delete the match configuration run
transaction MDC_HDB_MTC_DEL.
2. To configure the number of parallel processes and to specify an upper threshold run the Customizing
activity Configure SAP HANA Fuzzy Search for Direct Matching. Adapting the number of parallel processes
can improve the performance of the consolidation process.
 Note
defaulted.


 Note
The upper threshold for matching is the value as of which two records are rated automatically as a
match without having to be checked in the match review process.

2. Choose a Match Configuration ID.
3. In the Number of Processes field, enter the number of processes you want to be processed in parallel.
 Note
Name field.
5. Enter the upper threshold in the Up.Thrsld field.

3. To configure the Business Objects Data Services for BAS Adapter and to specify an upper threshold run the
Customizing activity Configure Business Objects Data Services for BAS Adapter.
• Business Objects Data Services
See the documentation of Customizing activity Configure Business Objects Data Services for BAS
Adapter and follow the link to check the Customizing settings under SAP BusinessObjects Data Quality
Management and adapt if required.
• Upper Threshold
 Note
To specify an upper threshold proceed as follows:

1. Enter a Config. ID and an Adapter Config Description.
2. Enter the upper threshold in the Up.Thrsld field.
4. To import the predefined settings for SAP HANA smart data quality run the Customizing activity Import
Predefined Settings for SAP HANA Smart Data Quality.
In this Customizing activity, you can activate the BC Set CA-MDG-EE-BP_IMHANA_C01 MDG-BP
Consolidation: IM in HANAcontaining predefined sets of table entries, that are required to run the process
steps standardization and matching with the adapters for the SAP HANA smart data quality.
The BC Set contains settings for the tables listed below. You can use transaction SM30 to configure some
of these tables to fulfill your requirements. Be aware, that some settings are not to be changed. For details,
see the description for each table.
Standardization and Matching
• SIMDQ_INP_FILTER IM in HANA Filter for input
Settings to specify filters for standardization and matching. Records can be filtered out and do not take
part in the corresponding process step.
 Note
not to be changed.
Standardization

Configure Matching for Business Partner PUBLIC 33
• SIMDQ_ADDR_STG IM in HANA address related settings
Settings to specify the address standardization, for example address formats such as Woodstr. versus
Wood Street.
• SIMDQ_OTHR_STG IM in HANA non-address settings
 Note
The settings delivered by SAP are required for technical reasons. Changing these settings does not
have any impact.
Matching
• SIMDQ_CMPRSRC IM in HANA compare source settings for Match Policy
Settings to specify the data sources to be considered for matching. The delivered settings compare
process data with process and active data and do not compare active data with each other.
 Note
not to be changed.
• SIMDQ_MTCADDRSTG IM in HANA address settings for the Match Policy

Settings to specify the matching for addresses, such as the threshold.
• SIMDQ_MTCFIRMSTG IM in HANA firm settings for the Match Policy
Settings to specify the matching for firms, such as the threshold.
• SIMDQ_MTCPERSTG IM in HANA person settings for the Match Policy
Settings to specify the matching for persons, such as the threshold.
• SIMDQ_MTCCSTMSTG IM in HANA custom component settings for Custom Match Policy
Settings to specify the matching for ID numbers.
1. To adapt the predefined settings, run transaction SM30.
2. Enter the table in the Table/View field and choose Edit.

13 Configure Matching for Material
Use
Within the process step matching, the data records to be consolidated are checked for possible duplicates.
According to a configured threshold records are considered to be duplicates and are displayed as match
groups in the attached match review.
Activities
To configure the matching for MDG, consolidation, run the Customizing activities under Master Data
Governance Consolidation and Mass Processing Configure Matching :
1. To create the match configurations for the fuzzy matching run the Customizing activity Create Match
Configurations for Fuzzy Matching.
In this Customizing activity, you define and generate a match configuration that SAP HANA uses to match
master data records when using fuzzy matching. This activity is only possible within a client allowing
cross-client changes. Configurations created here are used during configuration of process templates
when assigning step type matching and adapter fuzzy matching.
 Note
SAP provides the following standard match configuration that can act as template to help you to define
and generate your own match configurations:
Match Configuration Description
MAT_MATCH1 Match by EAN/UPC, Mfr Part Number, Description
This Customizing activity calls the Web Dynpro application Match Configuration MDC_HDB_MATCH. You can
use this screen to create, change, copy, and delete a match configuration.
• Create match configuration
1. To create a match configuration, choose New.
2. On the General Data screen, enter a name in the Match Configuration field.
3. Enter a description in the Description field.
4. Enter the business object type in the Business Object Type field.
5. Enter a name for the SAP HANA package in the HANA Package field.
The SAP HANA Package is generated with this name in the SAP HANA database when the
match configuration is created. After the generation of the package its name cannot be changed
anymore.
6. Enter an ABAP package in the ABAP Package field.

Configure Matching for Material PUBLIC 35
 Note
Do not use a package from standard delivery but create a package using transaction SE80.
• On the Select Attributes screen, the attributes in the tables from the process model are
presented in tree form. You can select the attributes that are relevant for matching in your match
configuration.
• On the Review and Generate screen, you can review your choices from the previous screens, and if
necessary, you can go back to the previous screens to make changes.
• The Generate button generates the match configuration. Before generation you must save the
configuration.
 Note
After generating the configuration you may maintain the rule set in the SAP HANA studio to meet
your requirements.
• The rule set can be found in the package used for creating the match configuration. The rule
set naming convention is: <MatchConfigurationName>RULESET.searchruleset.
• By default one rule is generated with all the selected match attributes with minimum fuzziness
of 0.8. All attributes are equally weighted.
• To update the Rule Set, edit the rule set in the repositories view. Editing in the repositories
view is possible since SAP HANA Studio SPS09. Authorizations should be the same as for the
project explorer view.
1. Create a repository work space.
2. Open the rule set in the package folder
3. Edit the rule set to change rule property or column property and conditions, such as the
minimum fuzziness value or weight of an attribute.
4. Save and Activate your changes.
• For more information see the documentation on the SAP Help Portal:
• Overview - SAP HANA Studio (http://scn.sap.com/docs/DOC-60363 )
• SAP HANA Search Developer Guide (http://help.sap.com/hana/
SAP_HANA_Search_Developer_Guide_en.pdf )
• SAP HANA Fuzzy Search Reference (http://help.sap.com/hana/
SAP_HANA_Fuzzy_Search_Reference.pdf )
 Note
When the match configuration is transported to the target system, the HANA package name is not
transported and the field will be blank. In Edit mode the configuration must be updated with the
appropriate HANA package name, saved and generated in the target system.
• Edit match configuration

To edit a match configuration, select the entry and choose Edit.
 Note
If you change the Select Attributes section by adding or removing attributes you have to set the
Re-generate Rule Setindicator. Any manual adjustment done on the ruleset has to be done on the
regenerated rule set if intended.

36 PUBLIC Configure Matching for Material
• Copy match configuration
To copy a match configuration, select the entry and choose Copy.
In the Copy Match Configuration dialog box, enter the name of the target Match Configuration.
 Note
After copying the configuration you may maintain the rule set in the SAP HANA studio to meet your
requirements. To do so, proceed as described under Create match configuration.
• Delete match configuration

To delete a match configuration, select the entry and choose Delete and OK.
 Note
The match configuration is marked for deletion. To finally delete the match configuration run
transaction MDC_HDB_MTC_DEL.
2. To configure the number of parallel processes and to specify an upper threshold run the Customizing
activity Configure SAP HANA Fuzzy Search for Direct Matching. Adapting the number of parallel processes
can improve the performance of the consolidation process.
 Note
defaulted.

 Note

Configure Matching for Material PUBLIC 37
2. Choose a Match Configuration ID.
 Note
Name field.
5. Enter the upper threshold in the Upper Threshold in % field.

38 PUBLIC Configure Matching for Material
14 Configure Best Record Calculation
Use
Within the process step Best Record Calculation, for each match group a best record is calculated. This
calculation follows a well defined process based on certain rules.
Activities
To configure the Best Record Calculation for MDG, consolidation, run the Customizing activities under
Master Data Governance Consolidation and Mass Processing Configure Best Record Calculation .
1. For an overview on the rules for the Best Record Calculation run the Customizing activity Specify Rules for
Best Record Calculation.
The standard delivery contains the following rules to determine the best record:
• COMPLETENESS: Determines that on field level completely maintained record win.
• RECENCY: Determines that on table level the most recent record wins.
• SOURCE_SYSTEM: Determines that on table level the record from a specified source system wins.
• BRF+: Best record calculation is up to the Business Rule Framework (BRFplus).
 Note
To set up a table for best record calculation using BRFplus proceed as described:
• Run the Customizing activity Configure Process Models.
• Select a business object type.
• On the Tables view set the BRF+ indicator for the corresponding table.
2. To specify the order of rules and the parallelization for the best record calculation run the Customizing
activity Specify Order of Rules for Best Record Calculation. Adapting the number of parallel processes can
improve the performance of the consolidation process.
 Note

Configure Best Record Calculation PUBLIC 39
defaulted.

The process step matching has bundled records considered to be duplicates, the so called match groups.
In a first step, the records of a match group are compared on table level. For a specific table the
source system or the recency can be considered to have higher priority. Depending on this setting the
corresponding data is taken into account for the best record. The information, what source system has a
certain priority for a specific table is maintained in the Order of Source Systems view.
In a second step the preliminary best record is processed on field level. If a field does not contain data but
completeness is assigned to this field as highest priority, then the data is completed with data derived from
the record with the next highest order.
1. Choose New Entries
2. In the BO Type field, enter a business object type using the entry help.
3. In the Config. ID field, enter a configuration ID.
4. In the Adapter Config. Description field, enter the corresponding description.
5. In the Number of Processes field enter the number of processes you want to be processed in parallel.
 Note
Name field.
7. Mark your entry and configure the order of rules:

• Order of Source Systems
If you use the rule SOURCE_SYSTEM you have to specify the order of source systems for specific
tables. For tables not explicitly mentioned all source systems have the same order.
 Note
You can reduce maintenance effort, in case you want to apply the same order of source
systems to all tables: To do so, create an entry with Space in the Table field and assign it to a
source system. This order of source systems now is valid for all tables, except tables that are
explicitly assigned to another order of source systems.
• Order of Rules for Tables

On table level you can configure the order in which the rules SOURCE_SYSTEM and RECENCY are
applied to a specific table.

40 PUBLIC Configure Best Record Calculation
 Note
You can reduce maintenance effort, in case you want to apply the same order of rules to all
tables: To do so, create an entry with Space in the Table field and assign it to a rule. This order
of rules now is valid for all tables, except tables that are explicitly assigned to another order
rules.
• Order of Rules for Fields

On field level you can specify if the rule COMPLETENESS is applied to a specific field.
To do so select the corresponding table and field name.
Example
Your source systems show the following entries in table BUT0BK (BP: Bank Details) for the fields 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 configured in the following way:
• Order of Source Systems:
Table Seq. No. Business System
1 C33
2 B22
3 A11
As the table field 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.

Configure Best Record Calculation PUBLIC 41
• Order of Rules for Fields:
Table Field Name Seq.No. Rule ID
BUT0BK KOINH 1 COMPLETENESS
MLAN TAXM1 1 COMPLETENESS
The rule COMPLETENESS is taken into account for the field KOINH in table BUT0BK.
The rule COMPLETENESS might proof helpful for tax classification.
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 first step the following set of data is selected for the preliminary best record:
BANKL BANKN KOINH
10010010 32168000
2. On field level the rule COMPLETENESS is applied. The field KOINH remained empty in the first 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 field.
BANKL BANKN KOINH
10010010 32168000 Rosi
 Note
Only if Order of Rules for Table contains an entry referring to the rule SOURCE_SYSTEM, either specific
for table BUT0BK or generic for all tables, the KOINH field 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 field.
Related Information
Background Communication

42 PUBLIC Configure Best Record Calculation
15 Configure Validation
Use
Within the process step validation the system checks whether the quality of a record is sufficient to meet
the requirements defined in the backend system. If the quality requirements are met the data can be saved
directly, in other cases corrections and data enrichment might be required.
The process step validation runs without further configuration. Nevertheless you can configure the number of
parallel processes to improve the performance of the consolidation process.
 Example
Data only can be saved if Street and House Number are maintained.
Activities
To configure the validation run the Customizing activity under Master Data Governance Consolidation and
Mass Processing Configure Validation .
 Note
• To create the bgRFC inbound destination manually, the authorization object S_BGRFC with activity 02
and type 07 has to be assigned to you.
If you use a queue prefix other than MDC_QUEUE_ this has to be entered in the corresponding field
as described below.
2. Enter the destination name into the Destination field and leave all other values as defaulted.
6. In the Open Connections field enter the number of allowed parallel processes or queues you wish to
be managed by this destination. This number also specifies the maximum of parallel processes to
be configured during the step configuration.
• If you do not create the bgRFC inbound destination manually the very first consolidation process will
trigger the automatic creation of the inbound destination under prerequisite that the authorization
object S_BGRFC with full authorization is assigned to workflow system user.

Configure Validation PUBLIC 43

2. Enter a Configuration ID and the corresponding Description.
 Note
Name field.
5. If you want to execute MDG, central goverance validation checks select the Execute Central Governance
Checks (Validation Rules (BRF+) & BAdI Validations) indicator.
 Note
The Execute Central Governance Checks (Validation Rules (BRF+) & BAdI Validations) indicator only
appears if you run MDG, central governance.
6. If you want to execute BRF+ checks, select the Execute BRFplus Checks indicator.
 Note
As a prerequisite run the Customizing activity under Master Data Governance Consolidation and
Mass Processing Define Rules Using the Business Rule Framework plus . For more information, see
Define Rules Using the Business Rule Framework plus [page 22].
7. To specify a threshold for the validation, enter a value in the Threshold field.
 Note
If you have not defined a checkpoint after validation this threshold is used to pause the process after
the validation step, if the number of records with errors is equal to or exceeds the percentage value you
have set here.

44 PUBLIC Configure Validation
16 Configure Filter and Remove
Use
Within the process step filter 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 filter 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 “undefined”. 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 finalized.
Activities
To configure filter and remove for MDG, consolidation run the Customizing activity under Master Data
Governance Consolidation and Mass Processing Configure Filter and Remove .

2. Enter a Configuration ID and the corresponding Description.
3. Use the input help to select the Predecessor Process Step Type.
The corresponding group box becomes ready for input. According to this selection the filter and remove
process can be used in the process step Specify Process Template [page 55].
4. Select the indicators to fit your requirement:
• Matching
You can filter and move Open Match Groups to a new process.
• Best Record Calculation
You can filter and move records to a new process using up to two of the following criteria:
• Single records
• New Match groups
• Updates
• Validation
You can filter and move records with warning to a new process for up to three of these criteria

Configure Filter and Remove PUBLIC 45
• Single records
• New Match groups
• Updates
You can filter records with errors using the same criteria and select one of following actions using the
input help:
• Move records to new duplicate process
• Remove & Delete Source Records
• No Action

46 PUBLIC Configure Filter and Remove
17 Configure Activation for Business Partner
Use
Within the process step activation records are activated and thereby added to the systems active area. You can
configure how the system proceeds with different types of active data and you can set up a parallelization for
the activation process.
Features
The activation can be adapted for all three possible types of records:
• New record: Record does neither yet exist in the active area nor does it have any duplicates.
• Updated record: Record already existed in the active area.
• Match group: Record does not exist in the active area, but has duplicates in the process data.
Records that did not pass all validity requirements are considered as records with errors. You can specify an
individual system reaction for each type of record, depending whether a record contains errors or not. If you
use SAP MDG, central governance in parallel with SAP MDG, consolidation and mass processing you can use
change requests to have your records approved.
Activities
To configure the activation run the Customizing activity under Master Data Governance Consolidation and
Mass Processing Configure Activation Configure Activation for Business Partner .
1. Select New Entries

2. Enter a Configuration ID and a Description.
3. Configure the parallelization for the activation adapter.
The activation is running without configuring the parallelization for the activation adapter. Nevertheless
you can configure the number of parallel processes to improve the performance of the process.
 Note

Configure Activation for Business Partner PUBLIC 47
defaulted.

1. In the field Number of Parallel Processes, enter the number of processes you want to be processed in
parallel.
 Note
Name field.
4. Specify the types of activation dependent on different record types and whether these records are
considered as correct or incorrect by the process step validation:
 Note
Records that did not pass all validity requirements are considered as records with errors. You can
specify an individual system reaction for each type of record, depending whether a record contains
errors or not. If you use SAP MDG, central governance in parallel with SAP MDG, consolidation and mass
processing you can use change requests to have your records approved.
 Note
If you want to activate using change requests make sure the selected change request type does not run
checks that prevent the creation of the record:
Run the Customizing activity Configure Properties of Change Request Step and for Change Request
Step 00 check the setting under Enhancements and Checks per Change Request Step and Entity Types
per Change Request Step.
 Note
For mass processing only the activation of updated records is relevant.
1. Configure the system behavior for New Records. In the field Activation Target for New Records, select
an entry using the input help and assign a corresponding change request type. In the field Target for

48 PUBLIC Configure Activation for Business Partner
New Incorrect Records, select an entry using the input help assign a corresponding change request
type.
2. Configure the system behavior for Updated Records. In the field Activation Target for Updated Records,
select an entry using the input help and assign a corresponding change request type. In the field Target
for Updated Incorrect Records, select an entry using the input help and assign a corresponding change
request type.
3. Configure the system behavior for Match Groups. In the field Activation Target for Match Groups, select
an entry using the input help and assign a corresponding change request type. In the field Activation
Target for Mtch Grps (Errors), select an entry using the input help and assign a corresponding change
request type.
5. If you want the records to be replicated to connected systems set the Call DRF after Activation indicator. If
you use the activation using change requests, we recommend to set the Call DRF after Activation indicator.
 Note
The Call DRF after Activation indicator is only valid for the process goal Central Maintenance. For the
process goal Consolidation no replication is executed.
• If you activate all types of records using change requests or cleansing cases flag does not have any
impact.
• If you activate all types of records with the Direct Activation you can choose the setting to meet your
requirements.
• If you activate using change requests and Direct Activation, we recommend to set the flag.
 Note
 Note
8. If you want to check the data after the final process step, the activation, specify the retention time in days
and the retention time in hours.
 Note
To use the Retention Time make sure of the following settings:
• In the transaction SWU3 Automatic Workflow Customizing under Edit Runtime Environment the
entry Schedule Background Job for Condition Evaluation is flaged green.
• In the transaction SWDD Workflow Builder enter workflow WS54500001 and choose Process
Process Object. ChooseTask description and then choose Additional Information Classification
Display . The General Task indicator has to be selected.

Configure Activation for Business Partner PUBLIC 49
Constraints
If you use SAP MDG, consolidation and mass processing without activating SAP MDG, central governance the
possibilities for this configuration step are reduced, as less activation targets are offered and no selection fields
for Change Request Type are displayed.
Record With MDG, central governance Without MDG, central governance
Activation Target for New Records No Activation No Activation
Direct Activation Direct Activation
Activation with Change Request
Target for New Incorrect Records No Activation No Activation
Direct Activation
Activation Target for Updated Records No Activation No Activation
Direct Activation of Best Record Direct Activation of Best Record
Activation of Best Record with Change

Request
Activation with Cleansing Case
Target for Updated Incorrect Records No Activation No Activation

Request
Activation Target for Match Groups No Activation No Activation

Request
Activation Target for Mtch Grps (Errors) No Activation No Activation

Request

50 PUBLIC Configure Activation for Business Partner
18 Configure Activation for Material
Use
Within the process step activation records are activated and thereby added to the systems active area. You can
configure how the system proceeds with different types of active data and you can set up a parallelization for
the activation process.
Features
The activation can be adapted for all three possible types of records:
• New record: Record does neither yet exist in the active area nor does it have any duplicates.
• Updated record: Record already existed in the active area.
• Match group: Record does not exist in the active area, but has duplicates in the process data.
Records that did not pass all validity requirements are considered as records with errors. You can specify an
individual system reaction for each type of record, depending whether a record contains errors or not. If you
use SAP MDG, central governance in parallel with SAP MDG, consolidation and mass processing you can use
change requests to have your records approved.
Activities
To configure the activation run the Customizing activity under Master Data Governance Consolidation and
Mass Processing Configure Activation Configure Activation for Material .
1. Select New Entries

2. Enter a Configuration ID and a Description.
3. Configure the parallelization for the activation adapter.
The activation is running without configuring the parallelization for the activation adapter. Nevertheless
you can configure the number of parallel processes to improve the performance of the process.
 Note

Configure Activation for Material PUBLIC 51
defaulted.

1. In the field Number of Parallel Processes, enter the number of processes you want to be processed in
parallel.
 Note
Name field.
4. Specify the types of activation dependent on different record types and whether these records are
considerd as correct or incorrect by the process step validation:
 Note
Records that did not pass all validity requirements are considered as records with errors. You can
specify an individual system reaction for each type of record, depending whether a record contains
errors or not. If you use SAP MDG, central goverance in parallel with SAP MDG, consolidation and mass
processing you can use change requests to have your records approved.
 Note
If you want to activate using change requests make sure the selected change request type does not run
checks that prevent the creation of the record:
Run the Customizing activity Configure Properties of Change Request Step and for Change Request
Step 00 check the setting under Enhancements and Checks per Change Request Step and Entity Types
per Change Request Step.
 Note
For mass processing only the activation of updated records is relevant.
1. Configure the system behavior for New Records. In the field Activation Target for New Records, select
an entry using the input help and assign a corresponding change request type. In the field Target for

52 PUBLIC Configure Activation for Material
New Incorrect Records, select an entry using the input help assign a corresponding change request
type.
2. Configure the system behavior for Updated Records. In the field Activation Target for Updated Records,
select an entry using the input help and assign a corresponding change request type. In the field Target
for Updated Incorrect Records, select an entry using the input help and assign a corresponding change
request type.
3. Configure the system behavior for Match Groups. In the field Activation Target for Match Groups, select
an entry using the input help and assign a corresponding change request type. In the field Activation
Target for Mtch Grps (Errors), select an entry using the input help and assign a corresponding change
request type.
5. If you want the records to be replicated to connected systems set the Call DRF after Activation indicator. If
you use the activation using change requests, we recommend to set the Call DRF after Activation indicator.
 Note
The Call DRF after Activation indicator is only valid for the process goal Central Maintenance. For the
process goal Consolidation no replication is executed.
• If you activate all types of records using change requests or cleansing cases flag does not have any
impact.
• If you activate all types of records with the Direct Activation you can choose the setting to meet your
requirements.
• If you activate using change requests and Direct Activation, we recommend to set the flag.
 Note
 Note
8. If you want to check the data after the final process step, the activation, specify the retention time in days
and the retention time in hours.
 Note
To use the Retention Time make sure of the following settings:
• In the transaction SWU3 Automatic Workflow Customizing under Edit Runtime Environment the
entry Schedule Background Job for Condition Evaluation is flaged green.
• In the transaction SWDD Workflow Builder enter workflow WS54500001. Press Enter and choose
Process Process Object. ChooseTask description and then choose Additional Information
Classification Display . The General Task indicator has to be selected.

Configure Activation for Material PUBLIC 53
Constraints
If you use SAP MDG, consolidation and mass processing without activating SAP MDG, central governance the
possibilities for this configuration step are reduced, as less activation targets are offered and no selection fields
for Change Request Type are displayed.
Record With MDG, central governance Without MDG, central governance
Activation Target for New Records No Activation No Activation
Direct Activation Direct Activation
Activation with Change Request
Target for New Incorrect Records No Activation No Activation
Direct Activation
Activation Target for Updated Records No Activation No Activation

Request
Target for Updated Incorrect Records No Activation No Activation

Request
Activation Target for Match Groups No Activation No Activation

Request
Activation Target for Mtch Grps (Errors) No Activation No Activation

Request

54 PUBLIC Configure Activation for Material
19 Specify Process Template
Use
The process template you use to create a consolidation or mass process specifies whether and in what
configuration certain process steps are executed and in which order the steps apply. The setup of process
templates is tied to certain rules concerning the order and recurrence of the individual process steps.
Process step Recurrence Order Used by Consolida- Used by Mass Proc-

tion essing
Standardization [page No limitation x x

25]
Update [page 28] No limitation x x
Matching [page 30] Once x
Best Record Calcula- Once After Matching x

tion [page 39]
Validation [page 43] No limitation x x
Filter and Remove No limitation After x x

[page 45]
• Best Record Cal-
culation
• Validation
• Matching
Activation [page 47] Once Last or last but one x x
 Note
Mandatory for
Replication
Replication Once Last x x
Activities
To specify the Process Template run the Customizing activity under Master Data Governance
Consolidation and Mass Processing Specify Process Template .

Specify Process Template PUBLIC 55
• Create Process Template
2. Enter a Process Template ID, a corresponding Description, select the Business Object Type (147
Business Partner, MDC_147 Business Partner for Consolidation, or 194 Material), and the Workflow
Template WS54500001.
3. In the Process Goal field, use the input help to select either Consolidation or Central
Maintenance.
 Note
• If you select the Process Goal Consolidation records can be loaded repeatedly to be
consolidated. The records are not replicated to the source systems.
• If you select the Process Goal 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.
• If you select the process goal Mass Update, a selection of active records is updated. The
process steps matching and best record calculation are not supported.
4. The Delete Source indicator enables you to configure a default value for the UI. If you want as default
value on the UI that source data is deleted after finalizing the process as set the flag Delete.
5. Save your entries.
• Configure Process Template
1. Mark a process template and choose Process Template Step
3. Enter a Step Number.
4. Select a Step Type using the input help.
5. Select a corresponding Adapter using the input help.
6. Select a corresponding Configuration ID.
7. If you want the process to stop to review the data after finalizing this process step set the Check Point
active indicator.
8. In case you have set the Check Point indicator, choose one of the following options using the input help:
• No action control: The process can be continued by a user assigned to a role with the required
authorization.
• Apply the four-eyes-principle: The process can be continued by a user assigned to a role with the
required authorization except the requestor.
• Action is only allowed for requestor: The process can exclusively be continued by the requestor.
 Note
The users have to be assigned to roles that contain the authorization object MDC_PROOT:
• The activity 31 Confirm has to be assigned to continue processes.
• The activity 37 Accept has to be assigned to continue processes despite unfinished match
reviews.

56 PUBLIC Specify Process Template
20 Data Load
Use
The data to be consolidated can be loaded from SAP and non-SAP-systems using ETL tools (extract, transform,
load).
Solutions offered by SAP are the following:
• SLT System Landscape Transformation
 Note
Recommended for existing SAP business suite models, as identical data models are used.
• SAP HANA Studio Data provisioning including data transformation

• CSV File (comma-separated values), for data down- and upload
 Note
SAP recommends to import the data in the SAP HANA Studio into an interim table. In a second step
the content of the interim tables can be loaded to the source tables using SQL or a custom ABAP
report.
Prerequisites
The data has to be transformed into the SAP data structure before the data load can be performed.
Features
Settings for business partner, supplier, and customer
Load the data into the source tables for the BP data model listed below:
Table Data
BUT000_SRC Central BP data
 Note
The table is required in all cases.

Data Load PUBLIC 57
Table Data
BUT020_SRC Address data
BUT_ADRC_SRC
 Note
The tables are required if address-related data is up-
loaded.
KNA1_SRC ERP customer data
 Note
The table is required in case you use the customer data
model
LFA1_SRC ERP vendor data
 Note
The table is required in case you use the vendor data
model
 Note
For a complete list of the tables run the Customizing activity under Master Data Governance
Consolidation and Mass Processing Configure Process Models , select the Business Object Type 147
and double click on Tables in the dialog structure.
For source tables the naming convention <table>_src applies.
 Note
For the upload of data related to organizations, you can also use the vendor or the customer data model. In
this case you have to run the report MDC_BP_TRANSFORM_SOURCE_DATA to transform the data to the BP
data model after the source tables are filled. The report only supports the transformation of data related to
organizations. It does not supports the transformation of person-related data.
Settings for material
Load the data into the source tables for the material data model listed below:
Table Data
MARA_SRC Central material data
 Note
The table is required in all cases.

58 PUBLIC Data Load
Table Data
MARC_SRC Plant data for material
 Note
The table is required if plant related data is uploaded.
MVKE_SRC Sales data for material
 Note
The table is required if distribution chain related data is
uploaded.
 Note
For a complete list of the tables run the Customizing activity under Master Data Governance
Consolidation and Mass Processing Configure Process Models , select the Business Object Type 194
and double click on Tables in the dialog structure.
For source tables the naming convention <table>_src applies.
20.1 Example: Loading Vendor and Customer Data
Use
The two examples below demonstrate the use of the various tables for the data load in different scenarios. The
first example describes the upload of vendor data with the vendor being an organization. The second example
describes the upload of customer data with the customer being a person. You can upload both, vendor and
customer data using the BP data model, as MDG, consolidation also uses the BP data model.
 Note
For the upload of data related to organizations, you can also use the vendor or the customer data model. In
this case you have to run the report MDC_BP_TRANSFORM_SOURCE_DATA to transform the data to the BP
data model after the source tables are filled. The report only supports the transformation of data related to
organizations. It does not supports the transformation of person-related data.
 Note
The source system is XYZ_333. All data is uploaded to the client 401.
Upload of Vendor Data (Organization)

Data Load PUBLIC 59
The record contains the following data:
Data Value
Name SAP SE
Street and house number Dietmar-Hopp-Allee 16
City 69190 Walldorf
Country Germany
Telephone +49/6227/7-47474
Fax +49/6227/7-57575
E-Mail info@sap.com
VAT identification number DE 143454214
D-U-N-S number 316268655
Bank details 987654321
1234567890
BP Data Model
Using the BP data model for the upload, the following tables are filled:
Master Data Consolidation: Source Table Description
BUT000_SRC BP: General data I
BUT020_SRC BP: Addresses
BUT_ADRC_SRC Addresses (Business Address Services)
BUT_ADR2_SRC Telephone Numbers (Business Address Services)
BUT_ADR3_SRC Fax Numbers (Business Address Services)
BUT_ADR6_SRC E-Mail Addresses (Business Address Services)
BUT0BK_SRC BP: Bank Details
DFKKBPTAXNUM_SRC Tax Numbers for Business Partner
BUT0ID_SRC BP: ID Numbers
BUT100_SRC BP: Roles
LFA1_SRC Vendor Master (General Section)

60 PUBLIC Data Load
Vendor Data Model
Using the supplier data model for the upload, the following tables are filled:
 Note
It is required to run the report MDC_BP_TRANSFORM_SOURCE_DATA after the source tables are filled.
Master Data Consolidation: Source Table Description
LFA1_SRC Vendor Master (General Section)
BUT_ADR2_SRC Telephone Numbers (Business Address Services)
BUT_ADR3_SRC Fax Numbers (Business Address Services)
LFBK_SRC Vendor Master (Bank Details)
DFKKBPTAXNUM_SRC Tax Numbers for Business Partner
BUT0ID_SRC BP: ID Numbers
Tables in detail
The tables listed below show in detail the data to be loaded.
BUT000_SRC
Field Content
CLIENT 401
SOURCE_SYSTEM XYZ_333
SOURCE_ID 1234567890
TYPE 2
 Note
2 = Organization
NAME_ORG1 SAP SE
SOURCE_RECENCY 20150706000000

Data Load PUBLIC 61
Field Content
SOURCE_FILTER TEST1
 Caution
NULL is not supported.
We recommend to use a proper value for the field

SOURCE_FILTER.
BUT020_SRC
Field Content
CLIENT 401
SOURCE_ADDRNUMBER 1234567891
BUT_ADRC_SRC
Field Content
CLIENT 401
DATE_FROM 00010101
ADDRNUMBER 1234567891
 Note
Used with the supplier model
CITY1 Walldorf
POST_CODE1 69190
STREET Dietmar-Hopp-Allee

62 PUBLIC Data Load
Field Content
HOUSE_NUM1 16
COUNTRY DE
LANGU D
BUT_ADR2_SRC
Field Content
CLIENT 401
DATE_FROM 00010101
CONSNUMBER 001
COUNTRY DE
FLGDEFAULT X
TEL_NUMBER 06227/7-47474
TELNR_LONG +496227747474
 Note
Used as an alternative to TEL_NUMBER
BUT_ADR3_SRC
Field Content
CLIENT 401

Data Load PUBLIC 63
Field Content
DATE_FROM 00010101
CONSNUMBER 001
COUNTRY DE
FLGDEFAULT X
FAX_NUMBER 06227/7-57575
FAXNR_LONG +496227757575
 Note
Used as an alternative to FAX_NUMBER
BUT_ADR6_SRC
Field Content
CLIENT 401
DATE_FROM 00010101
CONSNUMBER 001
FLGDEFAULT X
SMTP_ADDR info@sap.com
BUT0BK_SRC
Field Content
CLIENT 401

64 PUBLIC Data Load
Field Content
BKVID 0001
BANKS DE
BANKL 987654321
BANKN 1234567890
DFKKBPTAXNUM_SRC
Field Content
CLIENT 401
TAXTYPE DE0
TAXNUM DE143454214
BUT0ID_SRC
Field Content
CLIENT 401
TYPE BUP001
IDNUMBER 316268655
BUT100_SRC
Field Content
CLIENT 401

Data Load PUBLIC 65
Field Content
RLTYP FLVN01
 Note
Role for suppliers
LFA1_SRC
Field Content
CLIENT 401
LIFNR 1234567890
 Note
Only required if you use the supplier model.
NAME1 SAP SE
 Note
ADRNR 1234567891
 Note
KTOKK KRED
SPRAS D
 Note

66 PUBLIC Data Load
Field Content
LFBK_SRC
Field Content
CLIENT 401
BANKS DE
BANKL 987654321
BANKN 1234567890
BVTYP 0001
Upload of Customer Data (Person)
The record contains the following data:
Data Value
Name Erika Mustermann
Street and House number Heidestrasse 17
City 51147 Köln
Country Germany
E-Mail erika.mustermann@email-adresse.com
Birth date 12.08.1964
BP Data
 Note
As the report MDC_BP_TRANSFORM_SOURCE_DATA does not support the transformation of person-related

data, in this example the customer data model can not be used.
Customer data related to organizations can be uploaded using the customer model. This can be done in
analogy to the supplier model.

Data Load PUBLIC 67
Using the BP data model for the upload, the following tables are filled:
Table Description
BUT000_SRC BP: General data I
BUT020_SRC BP: Addresses
BUT100_SRC BP: Roles
KNA1_SRC General Data in Customer Master
Tables in detail
The tables listed below show in detail the data to be loaded.
BUT000_SRC
Field Content
CLIENT 401
TYPE 1
 Note
1 = Person
NAME_LAST Mustermann
NAME_FIRST Erika
XSEXF X
BIRTHDT 19640812

68 PUBLIC Data Load
Field Content
SOURCE_FILTER TEST2
 Caution
NULL is not supported.
We recommend to use a proper value for the field

SOURCE_FILTER.
BUT020_SRC
Field Content
CLIENT 401
BUT_ADRC_SRC
Field Content
CLIENT 401
DATE_FROM 00010101
CITY1 Koeln
POST_CODE1 51147
STREET Heidestrasse
HOUSE_NUM1 17
COUNTRY DE
LANGU D

Data Load PUBLIC 69
Field Content
BUT_ADR6_SRC
Field Content
CLIENT 401
DATE_FROM 00010101
CONSNUMBER 001
FLGDEFAULT X
SMTP_ADDR erika.mustermann@email-adresse.com
BUT100_SRC
Field Content
CLIENT 401
RLTYP FLCU01
 Note
role for customers
KNA1_SRC
Field Content
CLIENT 401

70 PUBLIC Data Load
Field Content
KTOKD DEBI
More Information
 Note
The source ID has to be a unique identifier for a specific source system. If you upload data using the
vendor or customer data model, you have to make sure that the ID remains unique. If there are vendor-
and customer IDs within the same number range the IDs might be made unique by adding a suffix. For
example a customer and a vender, both with the ID 1234567890 might be renamed to K123456789 and
L123456789.

Data Load PUBLIC 71
21 Usage of Consolidation Processes for
SOA-Inbound Processing
Use
With this feature it is possible to automatically both create and start consolidation and mass processes using
the payload data for each SOA-message during the SOA-inbound-processing.
Constraints
This feature is only supports business partner, supplier, and customer master data.
Activities
To use the feature run the Customizing activity under Master Data Governance Central Governance
General Settings Data Replication Define Custom Settings for Data Replication Define Technical Settings
Define Technical Settings for Business Systems :
1. On the Define Business Systems level select a business system and choose Define Bus. Systems, BOs.
2. On the Define Bus. Systems, BOs level select a business object type and choose Define Bus. Systems, BOs,
Communication Channel.
3. On the Define Bus. Systems, BOs, Communication Channel level use the input help to select a process
template:
• For newly created records use the Cr Template field.
• For changed records use the Ch Template field.
 Note
You specify the process templates in the Customizing activity Specify Process Template [page 55]

72 PUBLIC Usage of Consolidation Processes for SOA-Inbound Processing
22 Configure MDG, Consolidation and Mass
Processing for Custom Objects
Use
You can run MDG, consolidation and mass processing for custom objects.
For the objects business partner and material, the process model, gateway services and some process
configuration are part of the standard delivery. For custom objects this is not provided. In order to run
consolidation and mass processes for custom objects, the corresponding objects and configuration have to
be created.
 Note
You can use consolidation and mass processing only for custom objects that do not use MDG as the active
area. For more information see Designing a Data Model.
Prerequisites
The role Master Data Administrator (Consolidation) - Apps (SAP_MDC_BCR_MASTERDATA_ADMIN_T) is

assigned to your user.
Activities
1. Preparations for Custom Objects [page 73]

2. Create and Configure Process Model for Custom Objects [page 74]
3. Configure BRFplus for Custom Object Consolidation and Mass Processing [page 76]
4. Configure Gateway Service an Activate BC-Set for Custom Objects [page 77]
5. Add Tile to Launchpad for Custom Objects [page 78]
22.1 Preparations for Custom Objects
Use
This document describes the preparations in order to run consolidation and mass processes for custom
objects. For the complete procedure see, Configure MDG, Consolidation and Mass Processing for Custom
Objects [page 73]

Configure MDG, Consolidation and Mass Processing for Custom Objects PUBLIC 73
Activities
 Note
For the Customizing settings described below run the activities under Master Data Governance Central
Governance General Settings Key Mapping
1. Create a custom object by creating a data base table

This table is used as template for the consolidation tables in transaction SE11
2. Create a key structure that contain the key field only from the table created above.
 Note
The client field must not be part of the key structure.
The key field must have the same name as in the table.
3. To create a new UKM mapping contex run the Customizing activity under Key Mapping Define a
Mapping Context for UKMS Define mapping contexts . Confirm the popup for every table.
4. To create a new OTC run the Customizing activity under Key Mapping Enhance Key Mapping Content
Define Business Objects .
5. To create a new OITC run the Customizing activity under Key Mapping Enhance Key Mapping Content
Define Object Identifiers) and assign to OTC
6. To assign the created OITC to new OTC run the Customizing activity under Key Mapping Enhance Key
Mapping Content Define Business Objects .
7. To assign your key structure to the OITC run the Customizing activity under Key Mapping Enhance Key
Mapping Content Assign Key Structures to Object Identifiers
8. To assign the business objects to main contexts run Customizing activity under Key Mapping Enhance
Key Mapping Content Assign Business Objects to Main Contexts
22.2 Create and Configure Process Model for Custom

Objects
Use
This document describes how to create and configure a process model in order to run consolidation and
mass processes for custom objects. For the complete procedure see, Configure MDG, Consolidation and Mass
Processing for Custom Objects [page 73]

74 PUBLIC Configure MDG, Consolidation and Mass Processing for Custom Objects
Activities
Configure Custom Object
1. To create a process model start the FIORI Launchpad.

2. Click the Configure Custom Objects tile.
3. Choose Create Object.
4. Use the entry help to select your data and choose Save.
• Select the created OTC as Object (OTC).
• Select the created table as Template Table.
 Note
The Table automatically is named <Template Table>_ACT.
• Select a Package Name.

• The SAP HANA Package Name should be tmp.mdg.customobjects.
• Select a Workbench Request and a Customizing Request.
Activate Process Model
1. To activate your process model mark the Custom Object and choose Edit.
Switch the matching relevant fields to Yes and choose Activate.
2. Select a Package Name.
3. The SAP HANA Package Name should be tmp.mdg.customobjects.
4. Select a Workbench Request and a Customizing Request.
Check generated objects
To check the generated objects proceed as follows:
• Run the Customizing activity under Master Data Governance Consolidation and Mass Processing
Configure Process Models : For your OTC a model exist and a target table is assigned to the model.
• Run the Customizing activity under Master Data Governance Consolidation and Mass Processing
Specify Adapters : For your OTC 7 adapters for the following process steps exist:
• Activation
• Best Record Calculation
• Edit
• Matching
• Standardization
• Update
• Validation
• Run transaction SE11: The following tables exist:
• Z<OTC>_ACT
• Z<OTC>_PRC
• Z<OTC>_SRC
• Z<OTC>_SRC_STAT

 Note
Table names might alter if the template table name is to long.
22.3 Configure BRFplus for Custom Object Consolidation

and Mass Processes
Use
This document describes how to configure BRFplus in order to run consolidation and mass processes for
custom objects. For the complete procedure see, Configure MDG, Consolidation and Mass Processing for
Custom Objects [page 73]
Activities
You can use BRFplus to create rules for the certain process steps:
1. Run the transaction BRF+.

2. Select the application MDC<OTC> and expand the node and select the corresponding function:
• MDC_STD_FOR_<OTC>_PRC for standardization
• MDC_VAL_FOR_<OTC>_PRC for validation
• MDC_BRC_FOR_<OTC>_PRC for best record calculation
3. Choose Edit and on the Assigned Rulesets tab choose Create Ruleset and enter a Name.
4. Choose Create and Navigate to Object.
5. Create a rule.
More Information

22.4 Configure Gateway Service and Activate BC-Set for
Custom Objects
Use
This document describes how to configure the gateway service and activate a BC-set in order to run
consolidation and mass processes for custom objects. For the complete procedure see, Configure MDG,
Consolidation and Mass Processing for Custom Objects [page 73]
Activities
Check model for the gateway service
1. Run transaction /iwbep/reg_model.

2. Enter MDC_PROCESS_MDL__<OTC> as Technical Model Name and Model Version 1.
3. Choose Display and check if the Model Provider Class is CL_MDC_PROCESS_MPC_EXT and a description has
been generated
 Note
If no entry exists choose create, enter CL_MDC_PROCESS_MPC_EXT as Model Provider Class, enter a
description, and choose Save.
Check service for gateway service
1. Run the transaction /iwbep/reg_service.

2. Enter MDC_PROCESS_SRV__<OTC> as Technical Service Name and Service Version 1.
3. Choose Display and check if the Model Provider Class is CL_MDC_PROCESS_DCP_EXT and a description has
been generated
 Note
If no entry exists choose create, enter CL_MDC_PROCESS_DPC_EXT as Model Provider Class, enter a
description, and choose Save. Choose Assign Model, confirm the model MDC_PROCESS_MDL__<OTC> and
choose Save.
Register Gateway Service in UI-Frontend
1. In your frontend system run the transaction /iwfnd/maint_service.

3. Use the input help to enter the System Alias of you backend system and choose Get Services.
4. In the Select Backend Services list click on the Technical Service Name.
5. In the Add Service dialog box choose Local Object and confirm the popup.
Assign new service to role
1. In your frontend system run the transaction /iwfnd/maint_service.

2. Mark the added service, choose Add System Alias and confirm the popup.
3. Mark the entry and choose Copy.
4. Enter the User Role SAP_MDC_BCR_MASTERDATA_SPEC_T and choose Save.
Switch roles for users
1. Run the transaction SU01.

2. Remove the role SAP_MDC_BRC_MASTERDATA_ADMIN_T from the user
3. Add the role SAP_MDC_BCR_MASTERDATA_SPEC_T to the user.
Activate BC-Set
1. Run the transaction SCPR20.

2. Enter Z_MDC_PRC_TEMPLATE_<OTC> as BC Set.
3. Choose Activate BC Set.
4. Select a Customizing request and confirm the popup.
5. Run the Customizing activity under Master Data Governance Consolidation and Mass Processing
Specify Process Template to check that two process templates for your OTC have been created, one for
consolidation and one for mass processing.
22.5 Add Tile to Launchpad for Custom Objects
Use
This document describes how to add a tile to the Fiori Launchpad in order to run consolidation and mass
processes for custom objects. For the complete procedure see, Configure MDG, Consolidation and Mass
Processing for Custom Objects [page 73]
Activities
Add tile to application catalog
1. Start the Fiori Tile Catalog.

The catalogue SAP_MDC_BC_MASTERDATA_SPECIALIST_T is displayed.
2. To add a new tile to the Catalog Collection choose the + icon.
3. Choose App Launcher - Static.
4. Enter a Title, a Subtitle, and Keywords.
5. Use the entry help to select an Icon.
6. Set the Use semantic object navigation indicator.
7. Use the entry help to select MasterData as Semantic Object.
8. Enter consolidate as Action.
9. Enter &/otc=<OTC>/massUpdate=X as Parameters.
10. Choose Save.
Add tile to UI

1. Start the Fiori Launchpad.
2. Click the pencil icon in the right bottom corner
3. To add a new tile choose the + icon.
4. To select the tile from the catalog click on the corresponding + icon.
5. Choose Back.
6. Click the pencil icon to exit the action mode.

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

80 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 81
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

SAP MDG Consolidation

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

SAP MDG Consolidation

Uploaded by

Copyright:

Available Formats

PUBLIC

Configuration of SAP MDG, Consolidation and

THE BEST RUN

1 Configuration of SAP MDG, Consolidation and Mass Processing. . . . . . . . . . . . . . . . . . . . . . . . 4

4 Set up the Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5 Configure Process Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

6 Specify Adapters for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

7 Specify Adapters for Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8 Define Rules Using the Business Rule Framework plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

9 Configure Scope for Mass Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

11 Configure Parallelization for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

12 Configure Matching for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

13 Configure Matching for Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

14 Configure Best Record Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

15 Configure Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

16 Configure Filter and Remove. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

17 Configure Activation for Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

18 Configure Activation for Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

19 Specify Process Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

21 Usage of Consolidation Processes for SOA-Inbound Processing. . . . . . . . . . . . . . . . . . . . . . . . 72

22 Configure MDG, Consolidation and Mass Processing for Custom Objects. . . . . . . . . . . . . . . . . 73

Configuration of SAP MDG, Consolidation and Mass Processing

Configuration of SAP MDG, Consolidation and Mass Processing

Configuration of SAP MDG, Consolidation and Mass Processing

SAP HANA-Based Fuzzy Matching

For more information, see http://help.sap.com/hana/sap_hana_security_guide_en.pdf and http://

Basic Configuration of bgRFC

Determination of own business system:

Configuration of SAP MDG, Consolidation and Mass Processing

Master Data Governance Security Guide

Configuration of SAP MDG, Consolidation and Mass Processing

To activate the services, proceed as described below in the corresponding system:

Service Name System Use

MDC_HDB_MATCH Match Configurations Over- Backend system Web dynpro

MDC_HDB_MATCH_CONF Create Match Configuration Backend system Web dynpro

MDG_HDB_SV_GENERATION Search View Generation Backend system Web dynpro

MDG_HDB_SV_INITIAL Search View Initial UI Backend system Web dynpro

MDG_CONS Master Data Consolidation FIORI frontend system Gateway

Configuration of SAP MDG, Consolidation and Mass Processing

Gateway server on the frontend system

Configuration of SAP MDG, Consolidation and Mass Processing

If no entry exists proceed as follows:

Gateway server on the backend system

Configuration of SAP MDG, Consolidation and Mass Processing

If no entry exists proceed as follows:

For further information of gateway services, see http://scn.sap.com/community/gateway .

For further information of SAP FIORI, see http://help.sap.com/fiori .

Configuration of SAP MDG, Consolidation and Mass Processing

Activate type linkage

Configuration of SAP MDG, Consolidation and Mass Processing

• Business Partner 147

Configuration of SAP MDG, Consolidation and Mass Processing

Configuration of SAP MDG, Consolidation and Mass Processing

CL_MDC_ADAPTER_BP_BAS_STD (Business Address Services)

CL_MDC_ADAPTER_BP_IM_STD (HANA smart data quality)

CL_MDC_ADAPTER_BP_VALUEMAP_STD (Evaluate Value Mapping for Business Partners & ERP

CL_MDC_ADAPTER_BP_BAS_MTC (Business Address Services)

Configuration of SAP MDG, Consolidation and Mass Processing

CL_MDC_ADAPTER_BP_IM_MTC (HANA smart data quality)

CL_MDC_ADAPTER_FUZZY_MTC (HANA fuzzy search)

Best record calculation

CL_MDC_ADAPTER_BP_BRC (Business Partner Best Record Calculation)

CL_MDC_ADAPTER_BP_VAL (Business Partner Validations (Business Suite))