SAP ECC 2025
SAP ECC is retiring and time is running out. Don’t wait up until last moment, start your plan Now
Why SAP S/4HANA
The origin of the products line in R/3 is an architecture whose functional and technical bases are 25 years old. During these years the product has been changing and evolving on these bases.
The compatibility of the functionality maintenance in each version is a burden that does not allow for some aspects to re-engineering.
SAP S/4HANA inherits most of the functionality and logic of ancestor but in some aspects it is disruptive with the consequent impact on the passage from one product to another..
When do you need to go to S/4HANA?
The decision to go to S/4HANA has already been made. The manufacturer has set deadlines for customers to move from the ECC to S/4HANA announcing when they will stop maintaining the ECC system.
Observations:
- SAP ERP 6 (ECC 6.0 to ECC 6.08) with maintenance up to 2025 in all supported databases
- In S/4HANA 1709 almost everything is supported and almost everything is convertible but there are still exceptions
- SAP announces that there are many ECC functionalities supported for the moment in S/4HANA which are not part of the objective architecture and which should be adapted in the future. SAP could stop maintaining these functionalities. For example WM stops being maintained in 2025.
1
Prepare
At the beginning of a project, we perform a readiness assessment and interface scan, we assess your existing SAP platform, databases and operating system.
We will then determine the steps required and provide a migration road map, budget and timeline. A functional assessment will also be performed to realign business processes to S/4HANA best practice. Or we can take the assessment one step further still and define a strategic road map, determining how S/4 HANA can help your company on its digital transformation journey.
We will then determine the steps required and provide a migration road map, budget and timeline. A functional assessment will also be performed to realign business processes to S/4HANA best practice. Or we can take the assessment one step further still and define a strategic road map, determining how S/4 HANA can help your company on its digital transformation journey.
2
Explore
In this step, we will map your business processes and business priorities, define pain points, discuss where custom development will be needed and provide a more detailed road map.
Discovery sessions will help you understand specific features of S/4HANA and how to leverage innovation.
Moreover, our S/4HANA initial discovery environment lets you explore the real impact of S/4HANA within 6 weeks by running the solution on a copy of your own productive system on-premise or cloud with your own data sets. This reduces change management and alleviates risk as end users are exposed to the system early in the migration / transformation to S/4 HANA.
Discovery sessions will help you understand specific features of S/4HANA and how to leverage innovation.
Moreover, our S/4HANA initial discovery environment lets you explore the real impact of S/4HANA within 6 weeks by running the solution on a copy of your own productive system on-premise or cloud with your own data sets. This reduces change management and alleviates risk as end users are exposed to the system early in the migration / transformation to S/4 HANA.
3
Realise
The purpose of this phase is to build up the solution based on the business scenarios, process requirements and interfaces identified in the previous (explore) phase. The solution is incrementally built, based on requirement captured in the explore phase. Once the build and test is done successfully, the solution is moved to the deploy phase with multiple mock runs to prepare and a simulate cutover plan.
We can guide you through the entire migration process – from the preparation and migration phase to introducing SAP Fiori and determining user roles.
We can guide you through the entire migration process – from the preparation and migration phase to introducing SAP Fiori and determining user roles.
4
Deploy
The purpose of the deploy phase is to setup the production system, ensure customer end users are ready to use the solution productively, and to switch the business operations to the new system.
In this phase, the project team executes a cutover plan that was defined in the realise phase and refined during the deploy phase. The plan outlines a list of tasks including go / no-go decision points, migration / creation of data, and the non-transportable object setup. When ready, the project teams will execute the cutover tasks per the cutover plan to facilitate transition to the productive system.
In this phase, the project team executes a cutover plan that was defined in the realise phase and refined during the deploy phase. The plan outlines a list of tasks including go / no-go decision points, migration / creation of data, and the non-transportable object setup. When ready, the project teams will execute the cutover tasks per the cutover plan to facilitate transition to the productive system.
5
Run
The purpose of the run phase is to continue adoption of the implemented solution across the organisation.
During this phase, Acclimation will provide you with support services to add new users, enable business users and manage quarterly upgrades and activate additional functionality as required.
During this phase, Acclimation will provide you with support services to add new users, enable business users and manage quarterly upgrades and activate additional functionality as required.
6
INNOVATION
Start small and think big: Once the basics are live, we can help you explore new features and domains, like digital marketing, digital manufacturing, Fiori APPS, analytics etc.
