Retain existing system characteristics
With this transformation approach, your existing system is converted to an SAP S/4HANA system as part of an in-place conversion. If your source landscape is not yet running on SAP HANA, you can also migrate the database with this approach. For some years now, this database and system migration has no longer been carried out in two separate projects / steps, but planned within the same project. Even though the basic idea behind the system conversion is to keep the existing system configuration, you will have to make adjustments due to simplified and modified system settings. Code extensions will also have to be adapted to the target landscape if they are to be retained.
Basically, this transformation approach eliminates the need for a "re-implementation" with associated new process design. Existing business processes should remain unchanged. This basis simplifies the transition to a complete SAP S/4HANA architecture.
Possible target landscapes are SAP S/4HANA On-Premise and SAP S/4HANA Cloud-Private Edition.
Economic efficiency and transparency
Often the reason for "failed" projects or project budget overruns is the insufficiently defined system and process scope. The advantage of the brownfield approach is that this scope is defined by your existing SAP ERP solution:
The settings of your existing SAP ERP solution form the basis for the new system, changes are only made in those areas where the Readiness Check has identified configuration needs.
The SAP Readiness Check identifies the necessary changes that need to be made in your project due to system differences. The brownfield approach is therefore in most cases the fastest and most economical transformation.
The activities of "System Conversion" include
- Check of existing add-ons, business functions and industry solutions for SAP S/4HANA compatibility
- Check of components and coding for SAP S/4HANA compatibility
- Carrying out the real, physical "system conversion" in one step