Capgemini’s Highway to SAP S/4HANA® shows us that one approach to moving your landscape to SAP S/4HANA is conversion. Based on my experience of a S/4HANA conversion, the devil is in the details, meaning that you need to be aware of every aspect of your system.
If we look at the SAP S/4HANA simplification item list, the system can be checked by standard tooling from SAP or the Capgemini Fitgap Analysis Tool (C-FAT). This analysis is part of the overall methodology of iCaptivate and is completely connected to its process decomposition.
I would describe the SAP S/4HANA simplification item list as an extensive check of your SAP system, with all possible changes that would affect you as a company or user. Examples are the Business Partner setup, New Asset Accounting, Account-Based COPA, and the Material Ledger. For the SAP S/4HANA simplification item list, I have listed some items to keep in mind:
- At the start, implement the latest versions of the SAP notes
- Run the provide check programs from SAP or Capgemini tooling where useful
- Important to prepare your financial data towards the conversion
- Run always the consistency checks.
After this simplification item check is finished and everything is ok, the SAP Software Upgrade Manager (SUM) will start after implementing some notes with the conversion to SAP S/4HANA. The data migration happens during the installation of SAP S/4HANA and after SAP S/4HANA is installed. Now you are in a system with SAP S/4HANA and different steps need to be taken in order to migrate your finance data.
Keep in mind that within the finance conversion, there is still a lot of work to do. The list below provides an overview of some of the important decisions and actions that need to be taken:
- Partitioning of the Universal Journal Entry Line items, as you have more than 500 million records
- Regeneration of CDS views
- Analysis of transactional data, where it allows us to find inconsistent documents on BKPF, BSEG, BSIS, BSID, BSIK, BSAS, BSAD, and BSAK tables. This analysis does some checks like “clearing information missing,” “zero balance,” and “line items are consistent”
- Start and Monitor Data Migration is the actual migration to the ACDOCA table. This is a monitor or cockpit that executes several migration programs, showing the status of completion and errors. The following checks will be executed:
- GCC Check Consistency of G/L Accounts and Cost Elements. Checks that GL accounts and cost elements are consistent before migration.
- GCM G/L Account and Cost Element Merge: Merges the cost elements into GL account master data.
- DAA Default Assignment of Cost Elements: Default assignments in the former cost element master (CSKB) are transferred to the default account assignments.
- R20 Reconciliation of Transactional Data: Checks that FI documents are consistent and ready to be migrated.
- ENR Enrich Transactional Data: This data enrichment is required due to the merge of FI and CO documents. The program performs several activities:
- Fills some BSEG fields with information from BKPF
- Fills some COEP fields with information from COBK and OBJNR
- Fills profit center into CO line items
- Fills company code data into old CO line items
- Makes certain adjustments to fix asset depreciation
- R22 Check enrichment of transactional data:If any error is displayed, it can be corrected.
- MUJ Data Migration into Unified Journal: The actual migration of line items into ACDOCA happens in this step. Items from BSEG or FAGFLEXA, COSP, COSS, ANEX, and ANEP are migrated.
- R23 Check Migration of Journal Entry: Shows the results, and if there are errors, they need to be corrected and the migration restarted.
- M10 Migrate Material Ledger Master Data: Ensures that the material ledger is activated for all valuation areas.
- M20 Check Material Ledger master data: Checks the results from the previous step.
- M11 Migrate Material Ledger Order History: If material ledger was not active in any valuation area before S4 conversion, this step ensures that all existing PO records are converted into the material ledger currencies.
- M21 Migrate Check ML Production Order and Purchase Order History: Checks the results of the previous step.
- DLT Data Migration into Unified Journal: Aggregate Deltas: This step is also called Migration of Balances. It ensures that the ACDOCA table shows the same total balances as before migration. In SAP ECC theSo this step ensures consistency of those total balances, due to differences that could come from balance carry forward, archiving, customer-specific programs, etc.
- R24 Check Migration of Balances: Checks the results from the previous step and displays errors.
- AFA Initial Depreciation Calculation: This activity builds the initial depreciation values for asset accounting.
- R25 Check Initial Depreciation Calculation
- Checks the results from the previous step.
- Migrate General Ledger allocations
- Migration of House Banks.
Last but not least, when the comparison reports are executed, the complete button can be pushed and the system is open for posting again. It is important to execute all steps and go through them one by one. As I said in the beginning, the devil is in the details.
In the next blog, I will go in more detail on how to continue with the converted SAP S/4HANA system and develop the renewable enterprise.
If you are interested to learn more about S/4HANA conversion at Capgemini, please connect with me or my colleagues.