Support for converting from ECC to SAP S/4HANA in the automotive industry
Conversion from a traditional SAP ECC system to SAP S/4HANA consists of two main phases.
1.Preparation and planning
In this step, the client and their partner jointly determine the best path for migrating to SAP S/4HANA. This process involves the steps described below.
- Planning
At this stage, all activities are carefully planned. An SAP S/4HANA Readiness Check 2.0 analysis is performed. This standard system verification report helps identify issues that should be considered when planning the conversion, as well as activities that need to be completed in preparation for the project.
- System requirements assessment
Together with the implementation partner, the client reviews system requirements, conversion paths, data volume, and start releases. Before starting the migration to SAP S/4HANA, the system to be migrated must be analyzed. The analysis covers the system release, its type (standard or extended), and any additional tools. The implementation team also determines the support package level from which the client will begin the migration.
If the start release does not meet the required prerequisites, the team adds the necessary extensions and tools to the system to ensure a smooth migration.
- Maintenance Planner
Maintenance Planner is a tool used during the conversion preparation phase. It verifies the compatibility of system components, add-ons, and business functions with SAP S/4HANA. Based on this analysis, the tool generates a stack file that defines the subsequent technical steps performed by Software Update Manager during the actual conversion.
While the system is being prepared for migration, the tool identifies any remaining technical gaps. Based on this, a technical file is generated describing the subsequent steps of the migration process.
- Simplification Item Check
At this stage of the conversion, the Simplification Item Check is also used to identify critical steps that must be completed to ensure that the system can be technically converted to SAP S/4HANA. In addition, using the tool enables all available business processes to be activated after the conversion is complete.
- Custom Code Migration
This is another tool used during the preparation phase of an SAP S/4HANA conversion. It compares custom code against the list of process adaptations defined for the target system.
- System sizing and environment preparation
As part of conversion preparation, the organization’s current and future requirements in terms of performance, number of users, and data volume are analyzed. Based on the SAP Readiness Check results and SAP sizing tools, the target size of the SAP Cloud ERP Private environment is determined.
Unlike traditional on-premises deployments, there is no need to design and purchase your own infrastructure. The environment is provided, maintained, and monitored by SAP, and its size can be adjusted as business needs change. This allows the organization to focus on using the SAP system while leaving infrastructure and technical matters to SAP.
SAP materials
Summary of the planning and preparation phase
The planning and preparation phase concludes with a summary report. In it, conversion experts present the readiness check results and recommend the optimal approach to converting to SAP S/4HANA. Two conversion models are available:
- Greenfield – full SAP S/4HANA implementation that includes all new SAP features. In practice, this means reimplementing the system from scratch based on the processes of the new system.
- Brownfield – purely technical migration to the new system without deploying it as a separate, parallel implementation. It does not include additional SAP functionality other than what is required for the system to operate properly.
2. Realization
The activities described below apply to a conversion carried out using the brownfield approach.
This stage begins by cloning the structure of the previous SAP ECC system. Until the final conversion is performed, the existing production environment is secured and remains unchanged. The conversion team introduces a development freeze and prepares a dedicated emergency procedure for any required changes to the original ECC system that must be replicated in the new SAP S/4HANA version. The cloned system is then converted, and all project steps are documented.
- Software Update Manager (SUM 2.0)
During the SAP S/4HANA conversion realization phase, SUM 2.0 is one of the tools used to perform database migration (if required), data conversion, and the actual software update.
- Custom code adaptation
After the conversion, complications may arise due to the structure of custom code created by developers for the previous system version. Code for SAP S/4HANA differs from code used in a standard SAP ECC system. To ensure that the new version operates correctly and achieves the best possible performance, implementation teams should adapt the syntax of the aforementioned code. SAP provides its clients and partners with access to the ABAP Test Cockpit (ATC), which helps identify potential code issues and supports developers in resolving them. Clients can also use this step to identify and deactivate custom code that is no longer used by their organization’s business processes.
- Additional activities for specific cross-application tools
The conversion itself may require additional work to configure tools outside the SAP S/4HANA application suite. In such cases, the processes described below are carried out.
-
- Configuration of process adaptations (Simplification Items), for example: implementation of SAP Business Partner or use of the new output management logic based on SAP Business Rule Framework (BRFplus) with Adobe Document Services.
- Authorization conversion: existing roles (single/job) are reviewed for legacy transactions and mapped to the role structure required in SAP S/4HANA.
- Configuration of new business processes
During the conversion from SAP ECC to SAP S/4HANA, new business processes are also converted in line with the business requirements established during the planning and preparation phase.
- Testing
During the conversion phase, testing the new SAP S/4HANA system is critical. Testing is typically carried out by the implementation team in two rounds. First, a user acceptance test is performed for the implemented process adaptations, authorizations, and activated SAP Fiori apps. Regression testing is then performed on unchanged business processes.
- Deployment
The final deployment of the new SAP S/4HANA system is carried out using appropriate documentation. It is carried out in accordance with the conversion steps specified by SAP for the production environment.
How long does an SAP S/4HANA migration take?
Converting from SAP ECC to SAP S/4HANA is a highly individual process that depends to a large extent on the specific characteristics of the client’s organization. Project duration and cost depend primarily on process complexity, the client’s preferences, the methodology used, and the tools available to the organization.
The table below shows the typical duration of a conversion in three different scenarios:
Converting SAP ECC automotive components to SAP S/4HANA
SAP S/4HANA supports all key processes for the automotive industry:
- Vehicle Management System (VMS) – available in SAP S/4HANA. The conversion follows the standard procedure, with particular emphasis on custom code adaptation. Hicron recommends using SAP FIORI UX and the New Hicron Dealer Portal in the Vehicle Portal variant.
- Warranty (WTY) – available in SAP S/4HANA. The conversion follows the standard procedure, with particular emphasis on adapting the custom data presentation layer. Hicron recommends using the New Hicron Dealer Portal in the After Sales Portal variant.
