#S4HANA prep for #Sapphire – on the transition to SAP S/4HANA
Every one should know by now that SAP #S4HANA is a new product line. The classical SAP Business Suite & SAP ERP is a separate product line and will still be available. Now a key question we often get is: how to get there? We would like to share the latest with this blog, leading up to Sapphire in Orlando week may 16th where we hopefully meet a lot of you to discuss more details.
We see 3 major transition paths to move to SAP S/4HANA:
• New Implementation
• System Conversion
• Landscape Transformation
Always check back here for the latest information: www.sap.com/S4-paths
Let us focus in this blog on System Conversion. And yes, some people will call this complex as they love to punch, but the first customers who have gone live using this option are happy with this approach.
For the system conversion to SAP S/4HANA we offer different tools and approaches to support the customer:
- Maintenance Planner
- Conversion Pre-Checks
- Custom Code Migration Worklist
- Simplification List
- Software Update Manager (SUM)
The Maintenance Planner is a solution hosted by SAP and offers easy maintenance of systems in your landscape.
For more information regarding Maintenance Planner see SAP Help: http://help.sap.com/maintenanceplanner
Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to SAP S/4HANA. The results list the instances that need addressing before attempting the conversion process.
Implement SAP Note 2182725, and all the related notes attached to it.
Custom Code Migration Worklist
The Custom Code Migration Worklist displays all customer objects that refer to simplified SAP objects and links to information about how to adopt these customer objects
To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List”. In this list we are describing in detail on a functional level what happens in SAP S/4HANA to individual transactions and solution capabilities. If some transactions or capabilities are falling away, this does not mean that we are decommissioning functionality, but that we have merged this functionality with other elements or reflected it within a new solution / architecture. Simplification List for SAP S/4HANA, on-premise edition: Link
The Simplification List serves three purposes:
- Planning the actual system conversion from a traditional ERP solution to SAP S/4HANA
- Reducing efforts during the actual conversion by enabling individual Simplification Items to be dealt with in advance for those customers intending to migrate in a future project.
- Implementing SAP S/4HANA-compliant strategic capabilities when rolling out new capabilities to avoid rework on SAP S/4HANA (relevant to, for example, customers who still need to finish major rollouts prior to converting to SAP S/4HANA)
Customers are supported by:
- Descriptions of the changes in the Simplification List
- Pre-checks to establish whether a customer is currently using the changed solutions or technologies
- Custom Code Migration Worklist content to support the customer in adapting custom code for use with SAP S/4HANA, where required.
- Tools and guidelines on handling the necessary adaptations related to these changes, for example, reports for automatically migrating data to the new data model during the system conversion
It is planned to provide additional support and information package for the identified more challenging Simplification items (PPT, How-To-Guide, more automated logic …)
Software Update Manager (SUM) is the technical tool for system conversion to SAP S/4HANA, on-premise edition 1511. Note:
- You must run the Maintenance Planner before the SUM.
- Ensure that the latest version of the Software Update Manager is used:
For all information about using the SUM, please see the document Conversion of SAP Systems to SAP S/4HANA, on-premise edition Using Software Update Manager available at: service.sap.com/sltoolset (LINK).
Within the SUM procedure the following steps are executed in a one-step procedure (dedicated start releases:
- Step 1: In case the database is not yet on SAP HANA, the database is migrated to SAP HANA (Database Migration Option of SUM à
- DMO processing overview:
The processing sequence is based on the shadow system functionality of SUM: the SUM creates the shadow repository on the traditional database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, …). Then the shadow repository is copied to SAP HANA, the database connection of the SAP system is switched to SAP HANA database, and then the downtime starts. After migration of the application data (including data conversion), the upgrade is finalized and the SAP system runs on SAP HANA. The traditional database continues to run and the application data in it are not modified, so it remains a fallback throughout the complete process
- DMO processing overview:
- Step 2: Installation of the SAP S/4HANA software
- Step 3: Converting the data into the new SAP S/4HANA data structure (automate part)
I trust you find this information useful and please feel free to engage with SAP Services and the S/4 Regional Implementation Group of Product Experts.
Check out SAP S/4HANA @SAPPHIRENOW 2016 – be prepared here SAP S/4HANA @SAPPHIRENOW 2016 – be prepared