What are the SAP S/4HANA System Conversion Steps involved?
An SAP S/4HANA system conversion is the process of moving from SAP ERP to SAP S/4HANA. In this blog, I’ll talk about the SAP S/4HANA System Conversion steps involved. If you are already aware of the steps and looking for ways to automate and manage the move from ECC to S/4HANA, check out KTern – the all-in-one product for S/4HANA Conversions.
This phase includes technical evaluations such as System Design, Architecture and Sizing, Identification of hardware resources, Dependencies on SAP NetWeaver Gateway / Front-End servers
This phase includes preparatory activities.
- The SAP S/4HANA source system should be connected to SAP Solution Manager
- System data in SAP Service Marketplace should be up to date
- 3rd Party Vendor Add-Ons are evaluated and checked if they are compatible with S/4 HANA. If not, they may have to be removed.
The functional team perform the functional conversion activities during this phase. The report R_S4_PRE_TRANSITION_CHECKS should be run to check if the prerequisites are met from the application standpoint. You cannot proceed with the system conversion process if there are any errors.
- Convert Customers, Vendors to BP
- Activate Material Ledger.
- Material Field Length Extension.
- Pricing Data Model Changes
- Inventory Management Data Model simplification
- Run the program FINS_MIG_PRECHECK_CUST_SETTNGS for consistency check in ledger, company code and controlling area.
Custom Code Remediation
This phase is an extension of t3. If there are errors in the report R_S4_PRE_TRANSITION_CHECKS because of custom code conflicts, you will not be able to proceed to the next step. The code Inspector identifies conflicts. Potential conflict areas could be Material Number Field length, Pricing, key tables like BKPF, BSEG, MKP, MSEG table enhancement, document flow and document status tables usage, CI_COBL, etc.
If the report R_S4_PRE_TRANSITION_CHECKS indicates that all the errors have been corrected, you can then proceed to the next step.
Software Update Manager (SUM)
This is the technical system conversion phase. Follow the guided procedure of the SUM Phases. The below are the steps in SUM as per the conversion guide.
- Database migration (optional). If your source system is not yet running on the SAP HANA database, use the database migration option (DMO) of the Software Update Manager to migrate your database to SAP HANA during the conversion.
- Installation of the SAP S/4HANA software.
- Conversion of your data into the new data structure used by SAP S/4HANA (this is the automated part of the data migration).
Cross Application Follow up activities
In this phase, you need to do the necessary steps to make the S/4HANA system ready. Some of the key activities are as below:
- SPAU/SPDD checks
- Configuration of new output management
- Run reports RASUVAR1 and RASUVAR2 for variants updates
- Run PRC_MIG_POST_PROCESSING for pricing updates
- Activation of Webdynpro services (SICF)
- Run Finance Migration activities.
- Configuration and Migration of credit management.
- Carry out pricing related updates.
- Migration to Material Ledger
- Activate necessary business functions and implement the necessary notes.
This concludes the SAP S/4HANA system conversion steps.
A high tech manufacturer in the USA recently decided to transform their enterprise with SAP S/4HANA. They opted for an SAP ECC to SAP S/4HANA System conversion. You can read through the details of the project by accessing our whitepaper.