Transition from SAP ECC to S/4 HANA
Before embarking on upgrade of the conversion from ECC to S4, we recommend the following preparatory activities:
A. PLANNING PHASE
Techatalyst first establishes an overall understanding of the project steps and necessary technical infrastructure/steps required for the upgrade. We use the following tools to do your project planning. We use the Roadmap Viewer to familiarize the client with the project steps required for the transition to SAP S/4HANA. We highly recommend to run the SAP Readiness Check for SAP S/4HANA in advance of the conversion project to identify any issues we need to consider and activities we need to handle in preparation for your project.
2. System Requirements
Techatalyst will make you aware of system requirements, start releases, conversion paths, and data volume, in the following broad areas:
- System Requirements – Hardware, and related elements
- What’s the Impact on Your System Landscape?
- Supported Start Releases
- Data Volume Reduction
3. Maintenance Planner
Techatalyst will run the maintenance planner tool as a first step in the conversion process. It helps to check your components, add-ons, and business functions to ensure compatibility with SAP S/4HANA and also creates the stack file used for the actual conversion process (done by the Software Update Manager tool).
The Maintenance Planner has replaced the Maintenance Optimizer, which is not supported by SAP.
4. Simplification Item-Checkr
These checks identify important steps we take to make sure that your system can technically be converted and that your business processes can start running directly after the conversion process has been completed.
5. Custom Code Migration
The custom code migration tool checks your custom code against a list of simplifications developed for SAP S/4HANA. While not mandatory, we highly recommended this step. Ideally, we combine the SAP S/4HANA conversion project with housekeeping activities for your existing custom code base. In particular, you need a consolidated view of productively used custom developments and you should remove custom code that is no longer used. In most cases we find significant amount of custom code developed but not used.
6. Cross-application preparation activities
In addition to the general preparation steps described above, we also need to do some cross-application preparations.
7. Application-specific preparation activities
In addition to the cross-application preparations, we may also need to do some application-specific preparatory steps. These steps and their documentation are partly provided by the pre-checks and the custom code checks.
B. REALIZATION PHASE
After we conclude the steps of the planning phase, we continue with the activities of the realization phase:
1. Software Update Manager (SUM)
When we complete the steps above, and implement all the adaptations required to ensure your system and your custom code is suited to SAP S/4HANA, we then run the SUM. The SUM does the database migration (if required), the actual software update, and the data conversion. After the completion of the SUM run, we highly recommend that we adapt your custom code considering the issues raised in the planning phase.
2. Cross-application follow-on activities
Other manual cross-application activities may also be required.
3. Application-specific follow-on activities
In addition to the cross-application follow-on activities, we may also have the need to do application-specific manual steps. These steps and their documentation are provided by the pre-checks and the custom code checks, which provide the list of simplification items relevant for your specific systems.