Migrating from SAP ECC into SAP S/4 HANA?
We put together some pro tips to help and a short video that shows you how SDN tackles the first step of the challenge. Staging your ECC Data into a Cleansing and Conversion Database. Our solution was born as a direct result of years of SAP Implementations.
OK! Here we go.
A perfectly configured HANA system won't yield good results if the system has bad data. The sooner you prioritize and begin your data cleansing and migration preparation, the better!
A few of key thoughts:
1) The actual loading of the data is the final step. There are a lot more steps leading up to the load that produce a high quality of data.
2) Previous S/4 HANA experience shouldn't be your driving factor on staffing data resources. There are a wealth of SAP ECC resources! Although there is a new data loading workbench, many load mechanisms remain unchanged in S/4. The actual loading of the data isn't even where the money is. It is in the preparation of the data that will be loaded and the creation of a solid, repeatable process.
3) Billions of records were loaded in SAP R2, R3 and ECC before the industry complicated the situation by providing tools that are expensive, limited in capability, require niche resources, and reduce your ability to create a repeatable process. Many of today's projects even rely 100% on EXCEL to produce the load files!! Do yourself a favor and get some talented database programmers to apply real business logic in a world class manner as opposed to a VLOOKUP rockstar.
4) We suggest creating load programs (LSMW, BDC, BAPI, Migration Cockpit) that ONLY process transactions. If you keep them free from logic, lookups, aggregations, transformations, they run faster and can be reused on future deployments. Your functional design drives your load program requirements (i.e. what structures/fields need to be populated to accomplish the transaction). The load program drives your file format (how the data file(s) should look). Your pristine data file created by a talented data analyst should contain the EXACT data you want loaded.
5) In preparation for cleansing and conversion, stage your legacy/ECC data exactly how it exists in the old system. Avoid transforming data in many places. Example: A ETL process extracts legacy data and processes transformations as part of staging. More data transformation is injected during the file preparation step. And even more during the load step. When you try to validate where a given value that shows up in S/4 HANA came from, it is a daunting task.
Our standard SQL based methods use tried and proven processes that are a breeze to staff. This is your chance to purge or consolidate old or bad legacy/ECC data as you begin your journey into SAP S/4 HANA. A clean start begins will clean data.
LINKS:
Watch the video @ https://youtu.be/Z6aXfrQe7HU
Find out more @ https://simplydatanow.com/
Contact us @ info@simplydatanow.com