Common routes to SAP S/4HANA
Your journey to SAP S/4HANA is unique, but there are some common routes outlined below.
1. System conversion
- In this scenario, we take your current SAP ECC solution, provide a database change to SAP HANA (assuming you are not already on Suite on HANA) and then convert the data and functionality into the new S/4HANA.
- We will check your custom code to confirm it will work on the HANA database and with the new data models and processes within S/4HANA and convert the traditional ECC table base into the new simplified data models.
We find this option is most attractive if you have a reasonably clean ECC environment, do not want to apply additional functionality within S/4HANA and have a reasonable downtime window.
This option is least attractive if you have a complex environment with a significant amount of unused data and code, with a requirement to install new functionality and have a tight downtime window.
2. New install
- Rather than keep all of your old and unused custom code (and in some cases data), a new install is a way of providing a clean landscape to grow from.
- We can migrate all relevant data and use the SAP Activate methodology to manage the project. This also presents an opportunity to base your configuration on SAP Best Practice to ensure you stay close to standard SAP.
- This scenario gives you the ability to add all of the required new functionality in the initial release
This is most attractive to organisations with complex environments, plenty of unused data and code and a requirement to install new functionality with a tight downtime window.
This option is least attractive to customers with a clean ECC environment or those who do not want to apply additional functionality within S/4HANA.
3. Landscape optimisation
- If you have more than one ECC environment to manage your global requirements, S/4HANA can be used as the vehicle to consolidate these environments into one.
- When you have more than one SAP ERP system you have the flexibility to do things in different ways. The downside is that when you want to provide a single global view for reporting it becomes difficult to achieve. S/4HANA can be used to link to your current ERP systems (SAP and non-SAP) and provide a consolidated environment to manage your financial data. This is referred to as the “Central Finance” option.
- There is also the ability for you to create a new S/4HANA environment and start to run combined processes from a single system. This will provide you with significant cost saving in terms of support and maintenance, however all divisions would need to follow the central patching strategy.
This option can only be used if you have more than one ERP environment. There will need to be a compelling business case to consolidate the ERP environments as you could still use either option 1 or 2 to move to S/4HANA for each of their separate ECC systems.