How To Plan and Execute The Financial Data Migration During Conversion of SAP ERP Solution To Sap S/4Hana
How To Plan and Execute The Financial Data Migration During Conversion of SAP ERP Solution To Sap S/4Hana
How To Plan and Execute The Financial Data Migration During Conversion of SAP ERP Solution To Sap S/4Hana
Symptom
You are performing the system conversion to the SAP S/4HANA and identify a number of errors in the
transaction FINS_MIG_STATUS or FINS_MIG_MONITOR_RC0 that should be resolved before Gong Live.
Environment
Cause
You are planning the conversion of your SAP ECC solution to SAP S/4HANA and would like to understand
the important recommendation for the project planning and execution of the post-processing steps for the
conversion of the financial data.
Resolution
Important! The recommendations in this note are based on practical project experience and
should be verified by the project team during the planning, testing and execution of the project.
The content of this note may be updated at anytime.
1. General considerations
1. Perform the SAP Readiness Check and carefully review the findings
2. Consider starting archiving project to reduce the amount of historical data in the solution
3. Plan running the data consistency checks available in the SAP ERP as early as possible (p.2)
4. Test the conversion results consistency in the corresponding test runs to ensure the correctness of the
data migraiton. Follow the recommendations in the note 2332030.
5. Implement the best practices for the project managment: introduce the issue list with clear
responsibility assignment, split the activities in the work packages(e.g. per area of expertise), plan and
perform sufficient tests, prepare cutover plan.
2. Execute the consistency checks tools available on SAP ERP platform to verify the data consistency in SPA
ERP before the conversion
1. Execute Simplification items consistency checks in your SAP ERP solution provided with the note
2399707
2. Execute the financial data reconciliation checks in your SAP ERP solution provided with the note
2755360. See p.5 for details as well.
3. Usage of these tools in advance before the SAP S/4HANA conversion project start could enable you
with
• transparency over the data quality in SAP ERP before the conversoin project start
• additional details for the reliable conversion to SAP S/4HANA project planning
• ability to start data inconsistency cleanup project before the SAP S/4HANA conversion project
start
• potentially reduce the number of necessary financial data test conversion cycles.
• Important: the tools listed above partially perform the same data consistency analysis as the
necessary data consistency checks integrated into the SAP S/4HANA conversion process but do
not replace them. Further data consistency checks are performed during the S/4HANA
conversion e.g. for validation of the data consistency in the new data models that could not be
performed in ERP.
3. Project planning
1. Plan several test cycles for the conversion of your SAP ERP solution to SAP S/4HANA. We
recommend to consider 2 to 3 test cycles(see p.4.2 as well).
2. Prepare a test system as a new copy of your productive system for each conversion cycle.
3. Plan enough time for the first sandbox conversion test to understand and complete the procedure.
4. Plan enough time between the first and the second test conversion to cleanup potential inconsistencies
in the productive data (see p.4 as well).
5. Prepare the cutover plan including complimentary data consistency verification steps
6. Assign responsible to follow the cutover plan step sequence and orchestrate the productive conversion
process. Test the cutover plan execution, control and handover between execution steps during the
dress rehearsal.
During execution of the financial data migration a set of extensive data quality checks is performed to
ensure the data consistency before migrating it into the new data models of SAP S/4HANA. The issues
that have been identified during these checks also in the historical data must be investigated, verified
and resolved or evaluated as not critical (see p.4.2.1). The results of the checks could be reviewed with
the transaciton FINS_MIG_MONITOR_RC0, FINS_MIG_STATUS. When planning this activity please
consider the following lessons learned:
(following p.3.2: having a new copy of productive system for each test cycle) will ensure that the
relevant data migration will be retested in the next S/4HANA conversion test cycle.
3. You may combine the financial data cleanup activities with the techncal conversion tests in the
way that a new copy of productive system is used for the system conversion and the financial
data migration test takes place on that system.
• When planning conversion project to SAP S/4HANA please carefully review and follow the conversion
guide available at SAP Help Portal https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE
• When planning Financial data migration please carefully review the Converting Your Accounting
Components to SAP S/4HANA guide available in the note 2332030
• For verification of the conversion results please follow recommendations in the guide available in the
note 2332030, part 5.3. Document your posting data.
• Please ensure that all latest updates to the tool are installed for the financial data reconciliation checks
note 2755360 (currently notes 2833447, 2831943, 2755360, 2833232, 2833865, 2835751, 2834278,
2840019, 2839441, 2835646, 2822400, 2837303, 2843406, 2848596)
Keywords
SAP S/4HANA, SAP HANA, performance, S4, S/4, S/4 HANA, Financial Data migration, FIN MIG,
FINS_MIG_STATUS, RC0, FINS_MIG_MONITOR_RC0, R20, R21
Products
Other Components
Component Description