Strategy for Employee Historical Data Migration to SAP from Legacy

[Former Member]

Dear Friends,

Are there any SAP recommended best practice for Employee PA, OM, Time and Payroll Historical Data Migration to SAP from Legacy?

What are you all best advices and leranings from your own SAP HR implementation?

Not able to decide on any cutover strategy and how much data to take into SAP. I am very much confused and tensed related to Payroll and Time Data takeover.

The client is a SPanish client and their Fiscal Year is starting from 1st January and mine Go-Live date is 1st April.

Please pour in your suggestions. Lets make this thread a bible for every SAP HCM consultant working on Implementation.

Thanking You.

Sunny Singh

[Former Member]

Hi Sunny,

For the implemenation we need to follow accelerated SAP Methodology and Solution Manager which is a comprehensive solution to streamline SAP R/3 projects. ASAP optimizes time, quality and efficient use of resources. You also have various tools like project estimator, concept check tool, QADB Methodology, Business process Master List, Issue data base, scope of project, procedure for scope, project deliverables and many more.

The mentioned modules point of view entire org structure will be uploaded.

Unit Testing, Random Testing, volume testing and objects integration with the other modules need to be checked for which we may run RHINTE report in OM.

After mass data transfer for all modules (mass data transfer may be through LSMW (if there is less records <1000 /<5000), if not through BDC.

Once all data is ready after testing then we can plan for cutover activites.

Data migration need to be given more importance and the data migrated to be error free.

I just shared my knowledge. Let this thread be useful for every one.

Venu

[former_member193210]

Hello Sunny,

If you would have searched this forum (and perhaps elsewhere on the web), you would have learned that there is no "perfect" time for the cut-over (in other words, to "Go Live"). Anytime where there are enough resources available is fine.

As for the Historical Data, the client can import as much as he/she wants, but there must be resources for that. The more history, the more resources are needed (people and time), since the historical data will have to be mapped to SAP's tables and fields, the data will have to be extracted from the Legacy System (perhaps with a new report), imported into SAP (with SAP's conversion programs or custom built interfaces), and double checked for acuracy.

The whole process should be done at least 3 times; Unit testing, Integration Testing, Go-Live.

The basic requirements would be to populate as many of the OM and PA infotypes as possible, with the start date of the Pay Period before the planned Go-Live, and to transfer all the Old Payroll Results required to be able to calculate the first pay and have the cumulated results required for the Annual Year-End Reports.