Each company has its own, entirely individual history with SAP. Many twists and turns in the use of SAP software have left their footprints in the system and from today’s perspective cause a smile, a shake of the head or recognition. The same is also true of numerous product and technology changes over the past decades, which have also left their mark in the SAP software landscape of customers. And finally, there have been changes on the business side, such as sales or acquisitions of company units and new business models that have shaped software implementation. Here all SAP customers are different and that is why the roadmap toward SAP S/4HANA, the timetable or the setting of targets and priorities will also vary. The challenge is to find the best strategy among the standard tools and process models and put together the best combination of model and tools.
Ergo: Every path to SAP S/4HANA is individual – the challenge is to find your own path and take it. How does that work in practice?
A company from the chemical industry spins off a company unit from the group. The company unit was previously maintained as a company code and plant in the shared SAP ECC system and now should be spun off and implemented in a new SAP S/4HANA. Under current procedural logic, there are three possibilities: New implementation, conversion and Selective Data Transition.
Method assignment for the changeover to SAP S/4HANA
Ultimately the customer did not find any of the standard models satisfactory. An example is the preservation of the data history: Although all the data is preserved at conversion, unfortunately so is the data that will no longer belong to the company in the future and it must even be deleted. This is a substantial effort and requires a high level of coordination.The solution was to combine the modules of the models in order to obtain a model that was optimal for the customer. But ultimately, the key thing was the readiness of the customer to find its own solution for the data history. Thus, the following highly individualized model was conceived:
- Copy of the current PRD system
- Client copy of the PRD client without data and deletion of the PRD client
- Conversion of the empty copy system to SAP S/4HANA
- Adaption in customizing/optimizations
- Data migration with Standard Migration Cockpit
- Setup of of the SAP system landscape (QA and PRD system)
- Cutover, GoLive and HyperCare
This means in particular that the adaptations can be completed in customizing and with the in-house software, which will enable the new company to launch with an optimal SAP S/4HANA implementation.The charm of this concept is the customized implementation for the current individual situation of the company. At the same time this lays the basis for the development of an Intelligent Enterprise. It pays when selecting your own path to take a closer look and reevaluate your options.
Nagarro Allgeier ES can help you here – ask us about it!
You may also find this interesting: Our blog post on SAP S/4HANA licensing
Our service offering for the SAP Adoption Starter Program, in which you virtually develop a SAP S/4HANA Roadmap with us and SAP.