With the release of S/4HANA 1809 On premise, the most common question is if there is a comprehensive document available which provides detailed phases, steps, required SAP documents, and SAP Notes to follow to successfully convert a SAP system to S/4HANA 1809. We understand that the relevant documentation is scattered in multiple places in the SAP “world” and it’s very hard to find and consume it in a timely manner.
We have attempted to create the following approach document with as much as possible relevant information included so that users can follow and successfully convert their Business Suite systems to S/4HANA 1809.
This document will start with information on what approaches are there to move to S/4HANA based on the three different scenarios in “Transition Paths to SAP S/4HANA”. This blog and document provides only System Conversion scenario in detail.
Then we will consider in detail different Phases and Steps in each phase to follow for a successful conversion to S/4HANA 1809.
SAP HANA 2.0 is mandatory for S/4HANA 1809. This requirement may entail a change in Hardware and/or upgrade to the Operating System depending on your initial environment, which will add time and effort to the overall project and an adequate planning is recommended.
After we will deliver into the steps to make sure the source system is ready for the S/4HANA 1809 conversion by executing Readiness Checks, reviewing the Simplification List, and executing Pre-Checks, at this moment it's necessary to check and make sure the sizing planning meets the business requirements.
Sizing SAP S/4HANA using the Quick Sizer Tool - SAP.com
It is necessary to add the resource for Fiori Frontend Server (FES) in addition in case FES is embedded in S/4HANA Backend Server. It can be estimated with Quick Sizer.
Maintenance Planner (MP) is used to check the source system for Add-ons, Business Functions, and Industry Solutions to make sure the system is convertible. You must resolve all issues reported by the MP before you can get a valid Stack.xml file.
In the Realization Phase, we will detail the steps to proceed system conversion using Software Update Manager (SUM) tool. SUM will run ‘uptime’ and ‘downtime’ steps to complete the system conversion.
Hope this blog provides the necessary and relevant information for a successful S/4HANA 1809 OP system conversion. Please click here for the latest help documentation.
If you have any questions or comments, please let us know in the comments section.
If you enjoyed, click on like button !
Thank you,
Brought to you by the S/4HANA RIG
We have attempted to create the following approach document with as much as possible relevant information included so that users can follow and successfully convert their Business Suite systems to S/4HANA 1809.
This document will start with information on what approaches are there to move to S/4HANA based on the three different scenarios in “Transition Paths to SAP S/4HANA”. This blog and document provides only System Conversion scenario in detail.
Then we will consider in detail different Phases and Steps in each phase to follow for a successful conversion to S/4HANA 1809.
SAP HANA 2.0 is mandatory for S/4HANA 1809. This requirement may entail a change in Hardware and/or upgrade to the Operating System depending on your initial environment, which will add time and effort to the overall project and an adequate planning is recommended.
After we will deliver into the steps to make sure the source system is ready for the S/4HANA 1809 conversion by executing Readiness Checks, reviewing the Simplification List, and executing Pre-Checks, at this moment it's necessary to check and make sure the sizing planning meets the business requirements.
Sizing SAP S/4HANA using the Quick Sizer Tool - SAP.com
It is necessary to add the resource for Fiori Frontend Server (FES) in addition in case FES is embedded in S/4HANA Backend Server. It can be estimated with Quick Sizer.
Maintenance Planner (MP) is used to check the source system for Add-ons, Business Functions, and Industry Solutions to make sure the system is convertible. You must resolve all issues reported by the MP before you can get a valid Stack.xml file.
In the Realization Phase, we will detail the steps to proceed system conversion using Software Update Manager (SUM) tool. SUM will run ‘uptime’ and ‘downtime’ steps to complete the system conversion.
Hope this blog provides the necessary and relevant information for a successful S/4HANA 1809 OP system conversion. Please click here for the latest help documentation.
If you have any questions or comments, please let us know in the comments section.
If you enjoyed, click on like button !
Thank you,
Brought to you by the S/4HANA RIG
- SAP Managed Tags:
4 Comments
