SAP ECC Data Migration

[Former Member]

Hello,

About a year ago I was assigned to an SAP data migration project at a global engineering firm. The objective of the project was to migrate the master and transactional data from the legacy local SAP ECC system to a global SAP system. The project involved the extraction of data from the company's legacy systems into a staging area (a SQL database), where several mapping rules and transformations were applied to meet the requirements of the new system. The data was ultimately populated into excel templates designed by the functional team which were then uploaded via LSMW into the new global SAP system. The ETL process took place over several mock runs and were loaded into several test clients before the final load into the production system.

With regard to the above-mentioned process of migrating the data (Extract from Legacy -> Transform in Staging -> Load into global system), I would like to understand if this data migration project could have been approached differently, or have been migrated using any relevant SAP services? Could there have been a more efficient and robust process to complete the data migration?

Your advice would be appreciated.

Yuveer

[Former Member · Accepted solution]

Hi Mike,

Thanks for the response. The data quality at my client was very poor which resulted in a significant amount of logic being applied to the data to either correct it or improve it. The material master for instance required over 70 logical rules which were applied in the staging area (written in SQL). These logic rules were defined by the business who also provided the mapping files.

I am not familiar with rapid migration or the SAP Data Services tool, however would I have been able to apply such complex logic rules using the above-mentioned tools?

Regards,

Yuveer

[FrankDensborn · Accepted solution]

Hi Yuveer,

SAP Data Services is an ETL tool (Extract from the source SAP system, Transform the data, Load the data to the target SAP system) that has an own scripting language where you can work on the data and massage the data. Furthermore, it has a built-in data quality engine that enables you to cleanse and validate data records. Together with SAP Information Steward, which is the user interface for the business users, you can handle and correct the data right within the repository. As the tool loads directly from the repo to SAP via standard SAP interfaces (BAPI/IDoc), why would you first want to write the data into files that then will be loaded via LSMW? Data Services can do all within one tool and in one step.

Regards,

FRANK.