Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SAP S/4HANA Conversion Road Map: High Level – SAP Basis

former_member706983
Explorer
‎11-05-2020 9:10 AM
Introduction:

I, Pradeep Srigiri working as Architect and has around 15 years of experience in SAP. Currently, I work for YASH Technologies. This blog post consists of High-Level technical information on S/4HANA Conversion Road Map from SAP Basis perspective from On-Premise to Cloud or Vice-Versa or Cloud to Cloud. However, I would like to recommend following the SAP Standard Guides & SAP Notes during the S/4HANA Conversion Process. This blog post will take you there in a structured method for current release and can use same process for other releases to find out the details easily.

SAP S/4HANA Conversion Road Map:

The blog post consists of the below steps.
Discovery Phase

System Requirements & Planning:


  • Supported OS Versions for S/4HANA 1909
    SUSE Linux 12.0 or greater
    RHEL 7.0 or greater
    AIX 7.1 & 7.2
    Microsoft Windows 2016 or 2019

  • Supported DB Version – S/4HANA 1909
    HANA 2.0 SP04 (Min)

  • Minimum Source Versions with UNICODE required for S/4HANA 1909
    SAP ERP 6.0 SP20
    EHP2 FOR SAP ERP 6.0 SP10
    EHP3 FOR SAP ERP 6.0 SP09
    EHP4 to EHP8 FOR SAP ERP 6.0 No minimum SP required.

  • Compatible NetWeaver versions for S/4HANA 1909
    SAP NetWeaver 7.0 SP14
    SAP EHP1 for SAP NetWeaver 7.0 SP05
    SAP EHP2 for SAP NetWeaver 7.0 SP06
    SAP EHP3 for SAP NetWeaver 7.0 SP01
    SAP NetWeaver 7.4 SP02

  • For Cloud Support OS, DB & SAP, Check the below SAP Notes
    1656099 - SAP Applications on AWS: Supported DB/OS and AWS EC2 products
    1928533 - SAP Applications on Azure: Supported Products and Azure VM types
    SAP Note 2456406 - SAP on Google Cloud: Support Prerequisites

  • Compatibility Matrix Checks – use PAM in SAP Support Portal

  • Tools Used – DMO of SUM 2.0 SP8 (Latest) if Source is on non-HANA DB
    DMO with System Move for Conversion with DB Migration & data center relocation

  • Use Data Volume Reduction – SAP Data Volume Management
    Reduces the data footprint & achieve a shorter conversion duration
    Capabilities supporting the pre- and post-conversion phases
    One central tool is the SAP DVM Work Center (DVM WoC) in SAP Solution Manager

  • Maintenance Planner
    Generates the download files for Conversion

  • List of supported add-ons see SAP Note 2214409.

  • Business functions can have the following status: always_on, customer_switchable, and always_off (SAP Notes 2240359 and 2240360)

  • Checks Industry Solutions - SAP Note 2799003





  • SAP Solution Manager & SAP Systems – Backend SAP Support Connection

  • To download & implement the SAP Notes

  • To Pull the Latest Simplification Items from Support Portal to run the reports


Conversion Pre-Check:

Readiness Check


  • Implement SAP Note 2758146

  • RC_COLLECT_ANALYSIS_DATA is the Report

  • Activity 16 (Execution) of Authorization Object S_DEVELOP is required

    • For Discovery Phase Selection

    • Implement SAP Note 2185390: Set up custom code analysis

    • Implement SAP Note 1872170: Enabling SAP S/4HANA sizing

    • Implement SAP Note 2399707 - Simplification Item Check

    • Implement SAP Note 2769657 - INR: Interface Discovery for Idoc

    • Implement SAP Note 2721530 - Enabling Data Volume Management analysis

    • Implement SAP Note 2811183 - Enabling BP/CVI Analysis with Readiness Check 2.0

    • Implement SAP Note 2781766 - Enabling ATC check result export for SAP Readiness Check 2.0

    • Implement SAP Note 2502552 - S4TC - SAP S/4HANA Conversion & Upgrade new Simplification Item Checks



  • I Executed the Report RC_COLLECT_ANALYSIS_DATA in SE38 choosing relevant pre-check options (Background)




  • Launch the SAP Readiness Check application using https://rc.cfapps.eu10.hana.ondemand.com and use the ZIP file that was generated from the program RC_COLLECT_ANALYSIS_DATA.

  • To create a new analysis, I have clicked Create New Analysis





  • SAP Readiness Check 2.0 will be ready under 30 minutes and followed with Pre-Checks Analysis

  • For Custom Code Adjustments – Run program SYCM_DOWNLOAD_REPOSITORY_INFO

  • Download the ZIP file and upload it to the Readiness check Link by selecting “Update Analysis”


 

Addon Compatibility Check

  • Retrieves the add-on and business function data from Maintenance Planner

  • Check SAP Note 2214409





  • Business functions

  • Simplification Item Check to identify the mandatory steps before converting your system.

  • CVI Conversion Prep


Custom Code Migration & Simplification Item Checks:

  • Need to be performed by the respective teams using the latest custom code apps provided by SAP and implement the SAP Notes related to the Simplification Item Checks in the system before the Basis Team runs the SUM tool to start the Technical Conversion


Conversion Planning - landscape


Parallel Landscape Build

  • Implement emergency fixes and to reduce the timelines for the code-freeze - build a parallel conversion/migration landscape.

  • Any emergency change that is implemented in production landscape should also be applied in conversion/migration landscape.



 

It’s always recommended to have Sandbox ready with a copy of Production System in order to start the S/4HANA Conversion to have a better under standing on the impact and procedure that can be followed in the upcoming systems with lessons learn during the Sandbox System conversion. However, the above Parallel Landscape is being used only for Development, Quality & Production Systems

High Level Roadmap

  • Below pictorial diagram shows the process flow to achieve S/4HANA Conversion & Migration to Cloud or to On-Premise


 


 

High Level Cost Estimate


H/W Estimates:



  • To determine the H/W sizing, implement SAP Note 1872170: Enabling SAP S/4HANA sizing

  • Execute the program /SDF/HDB_SIZING in SE38





  • or select the pre-check option in SAP Readiness Check Report RC_COLLECT_ANALYSIS_DATA



Result: Upload the ZIP file in Readiness Check Link

  • Below is the Sizing information





  • Sizing for SAP Applications can be determined based on the current landscape for DEV, QAS & PRD systems with some additional increase in the Hardware Resources


S/W Estimates:

  • Based on the system requirements column, any one of the mentioned releases & version can be on the source system to perform the conversion to S/4HANA

  • S/4HANA 1909: Impact on current landscape – Use Upgrade Dependency Analyzer from Support Portal : https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ==)/support/uda/main.htm and System Requirements for NetWeaver

  • Procurement of S/4HANA License from SAP

  • Identify the Solution Approach based on the existing releases

  • Based on the Solution Approach, estimate the man days required for Basis to perform


Pre-Conversion Action list


Basis:

  • Implement SAP Notes related to pre-checks using SNOTE

  • Remove Client 066 – Not used in S/4HANA: Check SAP Note 1749142

  • Uninstall Fiori Apps – if not released for SAP_UI 7.50: Check SAP Note 2034588

  • Use Maintenance Planner to calculate stack.xml file and download files required for S/4HANA conversion

  • Perform OS Prerequisites on S/4HANA Application & Target HANA Server

  • Download the HANA Installation Media

  • Setup Target HANA Server based on the Installation Guide

  • Perform the prerequisites for HANA DMO – if required. For Prerequisites check SAP Notes 2882441 & 2832250

  • Download SUM 2.0 SP8 on Source and Target Application Servers with the downloaded files


Target Landscape



  • Based on the source SAP, DB & OS versions – below are the Major migration options


Note: Target or Source can be On-Premise or Cloud

  1. One Step Migration: HANA DMO with S/4 HANA Conversion during the same maintenance window



2. Two Step Migration: Existing SAP/DB Upgrade and HANA DMO with S/4HANA Conversion

or

Lift & Shift AS-IS to Cloud and HANA DMO with S/4HANA Conversion




  • HANA DMO required if source is on Non-HANA DB


Conclusion:

 

I would like to conclude that I have validated the SAP SUM DMO Guides and S/4HANA Conversion Guides from Support Portal and relevant information from the Notes mentioned in this blog post. I have followed the above mentioned steps & process and was able to achieve the goal which is S/4HANA 1909 conversion.


Reference below:

https://help.sap.com/doc/2b87656c4eee4284a5eb8976c0fe88fc/1909/en-US/CONV_OP1909_latest.pdf

 

Thank you! Hope the blog post is helpful.

 

Best Regards,

Pradeep Srigiri, Architect
2 Comments
Labels in this area
Popular Blog Posts