Duplicate Checks in MDG

1. Introduction:
This document entails about duplicate check on the Business Partner (BP) entity in MDG and also mentioned
about detail steps regarding configurations.
2. Scope:

We have implemented a duplicate checks using DB search on the Business Partner (BP) entity in MDG, and also
Configured search implementation for Duplicate checks.
3. Pre Requisites:

MDG 8.0
MDG user to do customizing of Search and Duplicate Check

4. Steps for duplicate checks configuration:

1) Go to the transaction: MDGIMG

2) Expand the General Settings
3) Inside Expand Data Quality and search
4) Expand and select Search and Duplicate Check

5) Execute Define Search Application

Define the search providers available for the different types of search used in Master Data Governance (MDG). The available
search applications are:
Address Search
Database Search
Enterprise Search
Remote Key Search
SAP HANA Search

For each search type, we have to specify which features are supported by the underlying search provider implementation, for
example, fuzzy search or free text search.
We can also specify if complex selections are supported for search. Complex search means that several attribute sets can be
processed in one step (instead of processing them one after the other). For example, when searching for duplicates of a
business partner, who has multiple addresses, all of these addresses can be processed at once.

6) Allocation of Search Help to Search Application:

Some search providers require the allocation of one or more search helps.
The search provider DB requires allocation of search helps from DDIC.
The search provider HA requires allocation of search views.

In Our MDG system already configured with DB Search, So select the DB search and got to the Allocation of Search Help to
Search Application.
The above include searches are come by frame work these entries available in the table: usmd2041
7) Creation of Duplicate Checks:
We can create profiles that specify which attributes the system compares in order to identify duplicates. For example, to
compare addresses, you can specify that the system should consider the house number, street, city, postcode, and country of
each record.
We can specify that a field is mandatory for duplicate check. During a duplicate check, all fields that you specify as
mandatory must contain a value in order for the check to be performed.
We can also assign a relative weight to each field indicating the importance of that field in identifying duplicates so that the
system can prioritize certain attributes for the purposes of the comparison.
For example, two addresses with identical postcodes could be considered more likely to be duplicates than two addresses
in which the values for country are identical.
Here select the DB Search and click on Match Profile.
8) We can create one or more match profiles. At any point in time, only one match profile can be active.
We can also use the Rule Set Name field to specify the name of the rule set used for HANA-based searches and to identify
duplicates. When you enter a rule set here the information from the rule set is used instead of the attribute view for
duplicate checks.

Here We have created on Match profile ID for Duplicate Check for BP data model.
9) Select the Match Profile Id and click on relevant fields.

Mandatory Flag for Duplicate Check Attributes

Specifies that a field is mandatory for duplicate check. During a duplicate check, all fields that you specify as mandatory
must contain a value in order for the check to be performed.
Exclude Attribute from Search
Excludes the field from the duplicate search but displays the field in the duplicate check window based on the sequence
For example, if we select the Exclude from Search checkbox for Material Description, the material description will not be
used to determine the duplicates, but will display in the duplicate check window regardless.
9) Save the all relevant Configurations come back to the Define Search Application option.
Now we have to configure our Match profile ID
Execute the below Configure Duplicate check for Entity types Icon.

Here we have to configure our Match profile ID

Here Low and High Thresholds are Match frequencies.

Save the configurations and go back.
10) Go to NWBC Transaction.
Execute the
Execute the application and create one new customer

While creating new customer request if any mandatory fields missing in from our configuration then it will throw below
warning message.
After
After entering the all mandatory fields for duplicates then if any duplicate entries available in creation at same time it will
show the pop-up related to duplicate checks.