Escolar Documentos
Profissional Documentos
Cultura Documentos
Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner
About
About
Home / Community / Blogs + Actions
Kathiravan Subramaniam
more by this author
share
0 share
0 tweet share
14
Follow
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 1/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
Abstract
Introduction
Overview of de-duplication process
Advantages of de-duplication process
Execution of de-duplication process
Abstract
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 2/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
and provides solution on how to eliminate them. This whitepaper delves into
the advantages of de-duplication, explains the process steps to execute de-
duplication along with information on fields which should be used to pick the
duplicate records, suggests the best team structure to manage de-duplication
projects and provides a guide explaining the common pitfalls and the
mitigation plans while executing de-duplication projects.
Introduction
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 3/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
The scope for de-duplication of master data comprises all the master data in
the source systems except those which would fall under one or more below
criteria:
a. Master data which are deleted or blocked at the highest level in the
organisational structure. However master data which are blocked at one of the
lower organisational structure level might still be active and relevant at another
organisational level, hence those data should still be considered for de-
duplication exercise.
b. Vendor master data which are not created at company code level but
created only at purchasing organisational level for different purposes
The initial cleansing of source master data is important since this would
dramatically reduce the number of duplicated group of master records. Initial
cleansing would include both enrichment of key master data and performing
corrections in the master data. Predominantly, initial cleansing will be
performed on the data within the source system only.
b. Correct material master with material type HERS duplicated with the
material type HIBE to which the HERS material master is assigned to
c. Update key details used in de-duplication logic which are missing in the
material and vendor master data
Important fields which are focused during initial cleansing or enrichment within
source system in material master and vendor master are as follows:
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 5/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
Material Master:
a. Material description
b. Unit of measure
c. Manufacturer details
d. UNSPSC code
Vendor Master:
a. Vendor name
b. Address
d. DUNS
This step is the core of de-duplication process. After the data is cleansed and
enriched, it would be compared against each other. The result of this
comparison would be the grouping of similar master data. The source system
for the master data could be single ERP system or multiple ERP systems.
There are tools available for comparing the master data and creating the
groups of similar master data.
The criteria used to determine the group of similar master data would depend
on many factors like the availability of data, level of initial cleansing done,
scope of enrichment performed within source data, etc.,
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 6/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
d. Similar description
Likewise, some of the rules used in vendor master de-duplication logic would
be as follows:
d. Same address details like name, street number, PO box, Postal code,
etc.,
Master data de-duplication table is the result of initial data cleansing activity
and the application of de-duplication logic on the pre-cleansed source data.
De-duplication tool has the capability in order to identify group of master
records within single ERP system or across multiple ERP systems based on
the de-duplication logic.
Source
Group Material
System Material Manufacturer
number Description
Name
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 7/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
In the above example the de-duplication logic has worked on the source
system data and grouped these three materials which are of similar nature.
Once the grouping of similar master data has been done, there is need to
select the material which should get migrated into the target system.
Source Vendor
Group Material
System Material Manufacturer part
number Description
Name number
In the above example, refer to the column Vendor part number. The same
part number provided by the same manufacturer was created in two different
systems in three different ways. Hence text search logic like normalization of
the text (removing the special characters to determine the actual text) should
be implemented to determine the duplicates.
If a group contains master data from two different systems, then there is
conflict of which system specific master data is given first preference to be
selected as leading material. Here normally the thumb rule is to have the
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 8/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
oldest system master data which has the updated information to get the first
preference. The other approach would be to select the master data which has
most transactional data. This issue becomes complex (during the selection of
the leading material) when the different systems are owned by different
internal organizations. Normally the de-duplication process should be carried
out centrally with central co-coordinator to mitigate conflicts arising out of
selecting the leading material in the groups.
During this process step we should have arrived with all the manual
nominations of identifying the leading and non-leading master data. This
would enable us to segregate the leading material which will get migrated to
the target system. The leading material which would get migrated to the target
system would have new material number in the target system as per the target
system material number nomenclature.
As a final process step within the de-duplication process, after receiving the
new material number in the target system, we should arrive at the mapping of
leading and non-leading master data number (old source system material
number) to the leading master data number (new material number in the
target system) which would appear as per above example in section 3.3 as
follows:
The Old source system material number contains both the leading (parent)
and the non-leading (child) master data number.
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 9/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
New material number in the target system contains the material number
which is created in the target system.
The non-leading (child) material and vendor inherits the leading (parent)
material and vendor master data. Certain data like bank details of child vendor
will be consolidated to the parent vendor. Child vendor will inherit parent
vendor general data.
The non-leading master data will not be migrated to the target system. The
transactional data of the non-leading master data would be created using the
equivalent mapped leading master data.
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 10/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
The common pitfalls and the mitigation plans in de-duplication projects are as
follows:
During initial review stages, there is likely As a general guideline, the resource e
underestimation of resources needed to based on 100 master data a week per
review the items and perform the on authors experience in de-duplicatio
nomination for leading / non-leading with complete analysis including inves
master data history
If there are multiple system owners, time The role of central coordinator and the
taken to reach consensus on nominating more so that conflicts could be settled
the leading master data was huge
High risk (or) high value items High risk and (or) high value items sh
with caution
Conclusion
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 11/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
This whitepaper discusses the de-duplication process during the initial stages
of rollout/implementation projects. However once the parent master data is
identified and the new master data are created after eliminating the child
duplicates, it is imperative to have defined approach to avoid duplicates further
in the target system. There could be single source for master data creation
and changes along with effective rules & processes to prevent duplicates at
source.
Alert Moderator
1 Comment
You must be Logged on to comment or reply to a post.
Ted Kwon
Thanks
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 12/13
11/16/2017 De-duplication of Master Data during large SAP Implementation Projects | SAP Blogs
https://blogs.sap.com/2014/03/07/de-duplication-of-master-data-during-large-sap-implementation-projects/ 13/13