Transition Paths to S/4HANA Flashcards
New Implementation
Brand new installation of a system, also known as a Greenfield implementation. Semi-Greenfield refers to an installed-based customer starting with a new implementation.
Technical methodology - Brand new installation (re-design)
System Conversion
Guided technical process for a 1:1 conversion of an existing SAP ERP system to SAP S/4HANA. Example: convert SAP ECC to SAP S/4HANA Cloud Private Edition.
Technical methodology - Guided 1:1 migration and update (re-use)
Lift & Shift
Lift and move an entire system without change to a new landscape (typically involves a system copy).
Eg: on-prem to cloud.
Selective Data Transition
Tool-based approach to selectively migrate and transform configuration & master and transaction data. Example: move from SAP ECC to SAP S/4HANA Cloud Private Edition.
Technical methodology - Custom blend of new implementation & system conversion
Upgrade
Upgrade system to a new software version base release. Example: upgrade SAP S/4HANA from base release 2022 to 2023.
Update
Apply new software updates to a system, such as a Feature Pack Stack (FPS) or Support Pack Stack (SPS).
Software conversion tool
Software Update Manager (SUM) or SUM with Data Migration Option (DMO)
Big bang rollout
One step with single downtime
New Implementation Process
- Software installation - new SAP S/4HANA instance in the cloud
- Pre-Configuration Content Activation - SAP Best practices, Enterprise Managemnt Layer (EML), SAP Qualified Partner PAckaged Solutions
- Software Configuration
- Initial Data Load - Transfer the business data required to run the new system by loading master and open transactional data from the legacy system. SAP S/4HANA Migration Cockpit facilitates migration of legacy data to the target SAP S/4HANA system - Master Data , Open Items
SAP Best practices for S/4HANA cloud private edition
Starting with predefined business processes enables a customer to get up and running much faster because process flows, apps, and business roles to complete different job tasks are already defined. It also makes it easier to train end-users in how to use the new system because documentation lives in SAP Signavio Process Navigator website. SAP will activate the chosen business processes for one country version. Implementation team is responsible for activating additional countries.
Enterprise Management Layer (EML) for SAP S/4HANA
The EML is a selection of business processes from the master package, SAP Best Practices for SAP S/4HANA Cloud Private Edition, with a focus on multinational companies.
Includes 43 country versions with a focus on intercompany processes.
SAP will install the preconfigured EML package and additional templates can be activated by request for an additional cost.
SAP Qualified Partner Packaged Solutions
Partner-created best practice templates built on top of empty systems are qualified by SAP to ensure the solutions are proven and repeatable.
These qualified partner solutions may address specific industry functionality or niche areas a customer requires on top of the standard SAP best practice business processes.
System Conversion Process
- Prepare ERP System: Custom code needs to be cleaned up and data volumes should be reduced as much as possible.
- Database Migration: Data is moved from the legacy database the SAP HANA database.
- System Update: The system is updated with new applications and database tables.
- Data Conversion: The original database tables are converted to the new data model.
- Software Configuration: Implement SAP S/4HANA mandatory items and simplification items and reuse most of the original business processes.
Software Update Manager (SUM)
Tool that facilitates the database migration, software update, and data conversion steps. The SUM creates a shadow repository on the target database. A shadow system consists of a shadow instance and a shadow repository.
Database Migration Option (DMO)
Optional feature of the Software Update Manager (SUM) tool.
It combines three system conversion processes into a single step procedure: database migration + system update + data conversion.
Selective Data Transition Process
Allows transfer of data from one or more existing ERP solutions to a new S/4HANA solution.
There are two common approaches:
1. Shell Conversion: A shell copy of the production system is made without master and transaction data and converted to SAP S/4HANA.
2. Mix & Match: A new SAP S/4HANA install is created and elements of existing configuration and ABAP repository are transferred.
Lift & Shift a system Process
- Check Prerequisites: Source system must be on a supported release.
- Provision Target System: Provision new hardware in the new landscape.
- Backup & Restore: Use Software Provisioning Manager to backup the current system and restore it on the target system.
Transitioning from SAP ERP on Any DB to SAP HANA
- Dual-stack Split: If the current system is on an dual stack it must be split into two individual stacks
- Unicode Conversion: If the current system uses multiple code pages (MDMP) it must be converted to Unicode which defines each character only once.
- Database Upgrade: The current system must be upgraded to a supported release.
- Software Upgrade: The current system software must be upgraded to a supported release.
- Database Migration: Technical migration of current database to SAP HANA.
