Adopt SAP S/4HANA
SAP S/4HANA Innovation: Introduced in 2015, S/4HANA replaces SAP ECC6 and brings numerous functional advancements and technical innovations that enhance business productivity and simplify user workflows.
End of Maintenance for SAP ECC6: Maintenance ends on December 31, 2027 (2030 with an extension), requiring migration to S/4HANA for continued support.
Companies using this version must incorporate conversion or migration to SAP S/4HANA into their roadmap before this deadline to ensure ongoing system maintenance.
RISE with SAP: SAP S/4HANA is available as an On-Premise license or a Cloud subscription.
Meeting Tomorrow’s Challenges: Businesses face cross-functional challenges. Now, they must also manage the accelerated adoption of solutions, including their ERP systems. This trend originates from departments like Finance, HR, Procurement, and CRM, which have reappropriated their IT systems and are seeking more flexible, simpler, and user-friendly solutions.
Benefit from the Latest Innovations: S/4HANA offers an enhanced interface, integrates decision-making functions, fosters collaboration, leverages real-time data, and improves user experience while simplifying customer SAP landscapes.
SURFtoS/4: smooth migration to SAP S/4HANA
The support is provided by experts covering all functional and technical aspects, led by dedicated project managers.
The solution covers up to four main steps of the migration process: scoping study, POC creation, conversion project, and the deployment of new functionalities and innovations.
Scoping phase
- The first step of the SURFtoS4 offer is the scoping phase, not mandatory but highly recommended. SAP clients, often facing complex questions, can get clear answers by entrusting this phase to our experts.
- The SURFtoS4 scoping is completed in 4 to 6 weeks.
- It explores the technical, functional, infrastructural, and licensing aspects of the migration to S/4HANA.
A Proof Of Concept (POC) production ::
- A S/4HANA instance is made available, a copy of your SAP ECC6 instance, on Microsoft Azure, OVHcloud, or your own infrastructure (in-house or with a partner).
- The goal is to allow your users and IT teams to discover S/4HANA at their own pace before proceeding with the migration. This lets them evaluate the technological innovation, new functionalities, and the Fiori interface of SAP S/4HANA.
- Full testing on your SAP system, identifying technical and functional impacts, validating the required effort.
- Duration: 2 to 4 months, with open access post-conversion ensured by Applium.
• The conversion/migration project :
- Several approaches are available to meet set objectives:
Technical Migration (Brownfield): Fast and economical, using SAP migration tools to migrate SAP ECC6 objects to S/4HANA. The goal is to perform a technical migration with functional equivalence.
New Implementation (Greenfield): Installation of a new SAP S/4HANA instance, potentially incorporating existing elements from SAP ECC6 (configuration, custom programs, etc.). More costly but tailored to specific needs. - There is no one-size-fits-all approach to migration to S/4HANA. The choice between Greenfield and Brownfield depends on the organization’s specifics. The scoping phase is essential to determine the best approach.
- Applium recommends a scoping phase to identify the best approach for your context.
The deployment of new functions and innovations
- After migration to S/4HANA, a range of innovative functionalities becomes accessible, surpassing SAP ECC6’s capabilities, including predictive analysis, cash management, closing cockpit, Customer 360°, supplier evaluation, procurement workflow, item coverage, DDMRP, resource planning, advanced eWM functions, re-scheduling of production orders, and many more.
Depending on your priorities, we can assist you in deploying these innovative features to continue enhancing user efficiency and satisfaction.
Applium team beliefs
Applium strongly recommends a Brownfield migration, whenever possible, for several reasons:
- SAP’s migration tools are highly effective.
- The costs of a Brownfield project are much lower.
- The duration of a Brownfield project is shorter.
- The need for business involvement is significantly reduced.
- S/4HANA innovations are available from the start.
- There is no need for complex data recovery tools (PNS or others).
In a Brownfield project, the conversion method is the same as for the POC. An import on a clone machine is done to prepare the ECC6 version for conversion.
In close collaboration with your teams, Applium can support and take responsibility for all project dimensions.
During the technical migration phase itself:
- Adjusting the configuration and impacted custom objects
- Implementing Business Partner
- Consolidating and converting financial data
- Implementing certain Fiori tiles
- Migrating to the HANA database
- Executing various data conversion tools
During successive optimization phases:
Once migration is complete, you have an updated technical foundation that enables you to seize the opportunity to enrich your solution with new functionalities and technologies and benefit from the power and intelligence of a “Next-Generation” ERP:
- Deployment of the SAP Fiori interface
- Use of new Embedded Analytics features
- Leveraging the power of the HANA database (new reports, etc.)
- Deployment of new S/4HANA functionalities across logistics and finance areas (Cash Management, Credit Management, Contract Management, eWM, Demand Driven MRP, MRP Live, etc.)
- Deployment of complementary solutions such as SAP Enable Now or SAP Analytics Cloud.
The transition to S/4HANA also requires considering the following aspects:
- Infrastructure: The use of the HANA database, the only database offered with S/4HANA, and its “In-Memory” operation requires an upgrade of the existing infrastructure, if not its replacement. Migration to S/4HANA is often an opportunity to switch to a Cloud hosting solution or the Cloud version of S/4HANA offered by SAP.
- User Interface: S/4HANA offers numerous improvements in terms of user interface, particularly with SAP Fiori. S/4HANA clients retain the ability to use the historical SAP Gui transactions from ECC6, but this approach doesn’t allow for the full value of S/4HANA.
- Licenses: The definition of S/4HANA user licenses evolves and simplifies compared to ECC6. It is essential to define the S/4HANA licenses corresponding to the actual use of each client and calculate the Conversion Credit amount to determine if the client will need to pay anything or not. There could be some pleasant surprises! Another approach is to use S/4HANA while keeping the SAP ECC6 license contract (the prerequisite is the acquisition of the SAP HANA database and an additional license priced at €9,000).
Deliverables
What is the cost of an S/4HANA migration project?
The determination of the size corresponding to each client is done through a questionnaire covering several criteria:
- Technical Criteria: EHP level, installed Add-Ons, custom objects, Business Partner already implemented, etc.
- Scope of services: architecture management, SAP administration (BC), technical corrections, S/4 functional corrections (Finance data, Business Partner), specific adaptations (Unicode, S/4HANA model), functional tests, reintegration of standard processes.
- The t-shirt size concept provides an initial pricing approach, tailored to each client by a detailed study of their situation.
| XS | S | M | L | XL | XXL | |
| Price | 90 K€ | 120 K€ | 220 K€ | 300 K€ | 400 K€ | > 500 K€ |
| Planning | 2 mouths | 3 mouths | 6 mouths | 7 mouths | 9 mouths | 12 to 18 mouths |
Focus on Maison Johanes Boubée
Other migration projects to SAP S/4HANA
Associated solutions
Testimonial
Testimonial
I take this opportunity to congratulate the Project Team that worked on the Chorus A2C connector, especially considering the time constraints imposed by AIFE. They were highly dedicated and attentive to our needs. I believe this product has been really well developed, and you will surely find clients interested in A2C, especially with the upcoming opening of Chorus to private structures!
