S/4HANA
As an SAP Value Added Reseller and Support Center (PCOE), we were able to and had to deal with the new SAP system S/4HANA at an early stage.
SAP S/4HANA is the successor to SAP ERP (ECC), whose maintenance period ends at the end of 2027. All SAP ERP customers who do not want to accept a significantly higher maintenance fee for continued use of the old system will therefore be forced to make the switch in the next few years.
Our S/4 packages for you
Pre-Check
Sales appointment-
Non-binding sales meeting
-
Questionnaire
-
IT-Strategy
-
Check framework conditions
-
Organizational dependencies
-
Basic technical requirements
S/4 Starter Package
Consulting appointment-
Contains Pre-Check
-
New functionalities & added value
-
Greenfield, Brownfield, RISE with SAP
-
Readiness Check
-
Custom Code Check
-
Simplification Item Check
-
BSR-Report
-
Pathfinder
-
FAR-Report
-
Maintenance Planner
-
Hardware Check
-
Presentation of results and evaluation of migration scenarios
Aim of the S/4 Starter Packages
With our starter package we would like to help you with your decision making. After our workshop and presentation of results, you will have answers to the following questions:
- What is the right migration scenario for me?
- Conversion or new implementation or a hybrid?
- All-inclusive package or do-it-yourself?
An important part of the strategic planning that takes place at the beginning of the project is the analysis and decision as to whether you will perform a technical migration of the system (brownfield), set up on a new system with new processes in the standard (greenfield), or use a mixture of both approaches (i.e., performing a technical migration but still setting up anew and reverting to the standard for selected processes).
The implementation of S/4HANA should not be a (technical) constraint, but should really bring advantages for the business and thus enable higher profitability.
We would be happy to advise you on your project and show you the possible advantages of a changeover.
Your data in the S/4HANA migration
Have you decided to transform your current ERP system to S/4 HANA? Then, you probably know that preparing the existing master and transaction data is a central and most of the time underestimated task in the preparation for a system transformation.
In addition, the approach chosen for the transformation – e.g. brownfield or greenfield – plays an essential role.
In the brownfield approach, the existing system is upgraded and the data is migrated (converted) “in place”.
In contrast, in the greenfield approach, the system is completely rebuilt and set up. The data is then migrated from the old ERP system to the new S/4 HANA.
In both cases, a quality check and cleanup of the existing data is required prior to the transformation. This includes the deletion or deletion flagging of data that is no longer needed and the correction of incorrect data that is still required.
The greenfield approach is often accompanied by a process redesign. The associated changes in the customizing result in extensive mapping tasks when migrating the data. This has an impact on the time sequence of the transformation steps. The migration is therefore only possible after the processes have been set up.
Procedure and tools for data migration in S/4HANA greenfield approach
A successful migration requires a defined strategy. After a detailed analysis of all components and the planning of all tasks a concrete approach can be outlined.
The initial focus is on qualifying the data for migration. Your process owners will be supported by our team of consultants when it comes to checking the data and the associated correction or deletion.
With the greenfield approach, initial migration test runs can usually only take place after the processes have been set up and the associated customizing has been completed.
In special cases, intermediate steps based on standard processes/customizing and migration test runs based on these can be useful.
The effort involved in data migration is influenced by the following factors:
- Scope of the migration objects (material master, bills of material, FI documents, etc.)
- Number of object instances (e.g. number of material masters)
- Complexity of the migration objects (e.g. number of material types in the material master)
- Extensions to migration objects (e.g. Z-Appends)
- Extent of self-developed migration objects (e.g. Z-tables)
- Extent of changes in customizing between old ERP and new S/4 HANA
Migration: Step by Step
The data migration process takes place in four steps per migration object.
In the first step, the data is selected from the legacy system. This creates mapping tasks for relevant data fields to convert values from the legacy system to other values for the new system. This way, changes between the old and new customizing can be mapped.
In the second step, the resulting mapping tasks are to be processed.The old values are to be assigned to the corresponding new values.
In the third step, the creation of the selected and converted data in the new system can be simulated. In this way, causes of errors can be identified and corrected in advance of the migration.
In the fourth step, the migration takes place with the transfer of the selected, converted and successfully simulated data.
During the migration process, the dependencies between the migration objects must be taken into account. For example, material masters must be migrated before the BOMs because they are part of the BOMs.
The entire migration process is carried out using the “Migration Cockpit” and “Migration Object Modeler” tools provided by SAP for this purpose.
The “Migration Cockpit” guides you through the four steps of the migration process described above, and the “Migration Object Modeler” allows you to adapt selection criteria and mappings, as well as to create customer-specific migration objects.
In the course of a system transformation, data migration is performed at least twice. The first test migration is usually followed by an integration test in the new system. If necessary, further test migrations are required to check the effectiveness of corrections that have been made and to optimize processes with regard to the final migration.
Are you about to implement S/4HANA? Contact us now and arrange a non-binding consultation.
Implementation & Migration
