SAP MDG data migration – Part 5
Part 1 in this series lists down various tools and techniques available for MDG data migration.
Part 2 explains the MDG Data Import Framework and File upload method
Part 3 provides details about SAP Data Services and S/4HANA Migration cockpit in terms of MDG data loads
Part 4 explores how next-generation HANA powered tools such as Smart Data Integrator (SDI), Smart Data Quality (SDQ) and SAP Agile Data Preparation (ADP) help in MDG on S/4HANA data migration.
This blog discusses MDG consolidation data import and how traditional data load techniques such as direct input methods and enterprise services can be leveraged for data load in SAP MDG.
Master Data consolidation data import
SAP MDG, consolidation and mass processing allow you to consolidate the master data and assists you to run mass processes to update multiple master data records at a time.
Data Import Fiori Application
Though the above process flow diagram shows only data import from file, you can leverage other SAP solutions such as SLT and ETL tools to load the data directly into MDG consolidation source tables.
MDG consolidation tables follow <table>_src as naming convention.
BP table names: BUT000_SRC, BUT020_SRC, BUT_ADRC_SRC, KNA1_SRC, LFA1_SRC
Material master table names: MARA_SRC, MARC_SRC, MVKE_SRC
Report MDC_BP_TRANSFORM_SOURCE_DATA can be used for transforming the customer or vendor data to the business partner data model after the source tables are populated.
To load data directly into source tables, refer to SAP note: 2233142 – Example: How to fill Source Tables
Back-end Functions Direct Input/ALE
You can use the traditional data load methods such as Direct input using BAPI, LSMW or ALE to directly load the data into the active area. Ensure that desired data quality is met before using these methods to transfer the data from the old system to the MDG system. Also, note that though LSMW is available but is not considered strategic in SAP S/4HANA.
Refer to following SAP notes when you use LSMW for initial data loads in S/4HANA.
- 2287723 – LSMW in SAP S/4HANA on-premise
- 2538170 – Migration of Retail Objects to SAP S/4HANA on-premise
Though the SOA services generally used in data replication from MDG to external systems, they can be used for data import in MDG.
If your source system (both SAP and non-SAP) can create SOA messages, you can send the master data to be created in the MDG system using the following services.
Using these services, the master data can be created in the inactive area or staging area so it can be following through the governance process.
By now you’ve learned about quite a number of tools and techniques to consider for the MDG data migration. As I stated earlier, different factors need to be considered while selecting the migration tools and techniques. While there is no comprehensive answer to which tool is good for (your) MDG data migration, my personal preference is SAP Data Services as it pretty much covers all the MDG data migration scenarios.
I hope you find this series of blogs helpful. Please leave a comment on your experience on these tools or anything that I might have missed.
Thank you for sharing informative topic.
I have one question.
One of my customers is thinking about data integration between Non-SAP(Windchill) and MDG-M, and now I am wondering if the Non-SAP system supports SOA, is it generally possible to create specific SOA message: MaterialERPBulkReplicateRequests so MDG can directly import the data without any middle ware like PO?
Do you mean SAP PI?. If yes, MaterialERPBulkReplicateRequests does not need PI. Refer to this document under section 4.6
Thank you, Magesh. It was a good series of blogs.!
Hi Magesh Subramanian,
thanks for this helpful blog post regarding to data migration. You posted an example how to fill the source tables. Can you give me a solution to delete all source tables? Also refer to my blog post:
Firstly, thank you so much for series of blogs with very useful information.
We have a scenario where in we are migrating suppliers from 8 different ECC source systems into MDG. Post migration the ECC systems would still continue for few more years until complete S4 HANA transformation.
This means MDG will be the source for supplier data and will replicate them to ECCs.
Now, as part of the data migration we need to get the key mapping updated with all the 8 different ECC systems as source so that post migration the updates in MDG are replicated to ECC with the right ECC supplier number.
Our customer is requesting to use the MDG Consolidation to create the key mapping and not to go with any custom development. Also, SAP contact person recommended the same instead of Data Import.
Can you please share more details to upload the source data to MDC to create the mapping?
Appreciate your reply.