SERVICES

My years of experience have led me to recognize the basic client scenarios related to the process of data migration to SAP R/3:

• We have data in a legacy system, we understand its structure in the system and We can save it as CSV (XLSX, TXT, etc.) That’s it.
• We have the data in the legacy system, we understand its structure in the system and we can save and split it into individual files according to infotypes as CSV (XLSX, TXT, etc.).
• We have the data in a legacy system, we understand its structure in the system, and we can save and split it into individual files by infotype as CSV (XLSX, TXT, etc.). We can also map the data to SAP R/3 values according to the project documentation. We can save the result in the data format according to the specification. But we need help to validate the data files.

Apart from the above, I have come across a disaster scenario: “We have data in a legacy system. And we don’t know what is their structure due to their export from our system. That’s it.” But in this case it is really a crisis already.

For each of the above scenarios, there is a way to support data migration to SAP R/3. Including the “ideal” one mentioned under #3. In this case, you can validate an already finished data file against several important criteria. The main goal is then to validate the quality of the data file before the actual upload to SAP R/3.

What I Offer

My offer comes from three basic scenarios. These scenarios are based on the experience of R/3 data migrations that I personally performed on PY implementation projects in the period 2005 – 2021.

SCENARIO ‘B’

• we understand the data structure in our HR/PA system
• we are able to divide the data exactly according to the required structure of individual infotypes
• we can export (save) the split data as CSV (XLSX, TXT, etc.

What can I do to help:

• loading exported data into the ETL tool
• importing data into the NDW Studio environment
• performing technical checks on the imported data
• export final data of individual infotypes in XLSX format (MS Excel) for data validation by the key user
• export of data in the required format for import into SAP R/3

To the above we can add two more important areas.

The first is the selection of relevant records in the data file for transformation into the target system format. This need not always be a trivial matter. Some people can do it themselves; others rely on qualified help.

The latter is support during parallel testing. It is one thing to migrate the data for testing. Then you start to calculate, compare and check. And you find out that here we are missing three employees, here we are missing a monthly bonus for the entire cost center, etc. , etc. And then it’s “just” a matter of getting the missing data in, or fixing it. And even in this case, someone will take care of it on their own – it’s usually manual work. But someone else will use the possibility of qualified support during parallel testing.

Each of these offers is priced differently based on the workload calculated in man-days – the price thus reflects the complexity of the support provided.

If any of these scenarios appealed to you and you thought you could use my support, please get in touch. Once contacted, I will send you a detailed description of the service you require and the quotation.

And even if your request doesn’t exactly match any of the above options, let me know, one of my essential strengths is flexibility. That is, I have no problem going beyond the standard list price.