Series of Technology Essentials for Moving to SAP S/4HANA – tip #2: Check Your Finance Data Quality
This is a series of blogs written by SAP subject matter experts to prepare you for your journey to SAP S/4HANA. Ready? Let’s go!
Topic #2 is Finance Data Quality.
A successful SAP S/4HANA conversion hinges on the smooth migration of your financial data. You need to convert transactional and master data into the new data model of the universal journal – while keeping that data error-free and consistent. That’s why it’s important to run a data analysis and correct possible inconsistencies prior to conversion. This may take some time depending on the volume and quality of data, so plan these activities well in advance of the conversion.
What are some effective data quality tools you can use?
A great starting point is the financial data quality check, which identifies inconsistencies in financial data. It’s executed as part of the SAP Readiness Check tool.
We also highly recommend running reconciliation checks for FI-GL and FI-AA on your SAP ERP application prior to your SAP S/4HANA migration. They cover a subset of checks normally executed during the finance data migration for general ledger and asset accounting. To run the checks and display the results, use the transactions FIN_CORR_RECONCILE and FIN_CORR_DISPLAY for general ledger, and FIN_AA_CORR_RECON and FIN_AA_CORR_DISPLAY for asset accounting.
You can also run these checks as part of the data collection function of SAP Readiness Check, which lets you classify and visualize detected issues. To rectify them, you can use the correction monitor tool (transaction FINS_CORR_MONITOR). Please refer to SAP Note 2887318 for further details.
Other useful tools at your disposal can check the quality of financial data already in your source SAP ERP system. For example:
- Material ledger help desk (transaction FCMLHELP) provides in-depth analysis of material ledger transactional data (SAP Note 2148839).
- The following tools for reconciling general ledger totals with subledger totals during the closing process are recommended:
– FI-AA: Transaction ABST and ABST2
– MM: Programs RM07MMFI and RM07MBST
– ML: Program FAGL_MM_RECON
– EC-PCA: Transaction KE5T or KE5U
– Special ledgers: Transaction GCAC
- Comparative analysis reports including SAPF190 (for classic general ledger) and TFC_COMPARE_VZ (for new general ledger) let you compare values from document line item tables with transaction total tables and secondary application index tables. Many of these checks are included in the new “reconciliation prior conversion to SAP S/4HANA” tool.
One final tip: The reconciliation checks can help you find most data quality issues in your financial data. However, during the conversion you may encounter a few inconsistencies not covered by these checks. Therefore, you should plan for several test iterations of your SAP S/4HANA conversion, always using the latest copy of the production system.
Check out all topics of the series:
tip #1: Check Your Add-ons. Now.
tip #2: Check Your Finance Data Quality
tip #3: Don’t Just Rework Custom Code. Rethink it!
tip #4: How to Build Custom Extensions
tip #5: Plan Ahead with Compatibility Packs
tip #6: Gain Insight to Build a Solid Business Case
tip #7: Hardware Planning and Data Volume Management
tip #8: Curate Your Master Data before Deployment
tip #9: Understand the Functional Impact
tip #10: Fix Issues Without Bogging Down Conversion
tip #11: Optimizing Downtime in Conversions
tip #12: Find Relevant SAP Notes
tip #13: Accelerate your Rollout with Test Automation
tip #14: Implementing SAP Fiori