SAP S/4 Hana Conversion – II – Prepare

Welcome to SAP S/4 Hana Conversion – Part 2.

In this blog we will take a deep dive into Prepare phase of SAP S/4 Hana Conversion. This blog is the continuation of my previous blog SAP S/4 Hana Conversion – I. Please read previous blog first to get better understand this blog.

Prepare phase, as shown in figure 1 is all about discovering readiness of your system, infrastructure and organization for S/4 Hana conversion .This is the most important phase of Hana conversion process. You should invest enough time and resources in this phase to maximize the conversion success.

Prepare Phase is all about check.. Checks and more checks. What kind of checks we need to do to determine readiness? Well …

We need to check and ensure our ECC system is not Dual Stack.
We need to check, if we good with code page.
We need to check, how much Hana we need .
We need to check, if add-ons are compatible with SAP S/4 Hana.
We need to determine which Fiori roles and apps we need.
We need to check which business functions are affected.
We need determine impact to custom code.
We need to also determine obsolete/unused custom code.
We need to also check if there are any archiving potentials

Good news here is SAP have outlined tools / activities / Best practices and methodologies for not only performing these checks but also mitigating the abnormalities found during checks.

Let’s deep dive and determine what are the different checks involved in each activity of Prepare phase in detail.

Planning and System Requirements

Here we are required to perform checks to determine feasibility for conversion and determine if there are any precursor to S/4 Hana conversion project. Below table lists them in detail.

Maintenance planner

You have to use the Maintenance Planner to do the conversion to SAP S/4HANA to generate downloadable files .Maintenance Planner checks if the following items are supported for the conversion:

Add-ons to your system
Active business functions in your system
Industry solutions

SI Checks

The SI-Checks, checks your system for data consistency and effects on the data after the conversion. SI checks are executed in source systems however they run against the selected S/4 Hana version .With SAP S/4HANA 1709 the Simplification Item-Check (SI-Check) replaces the pre-checks available with earlier SAP S/4HANA releases. The SI-Check identifies all simplification items relevant for the current system. They will be called by the Software Update Manager (SUM) tool to ensure that the system is in a consistent state. To run SI checks you need to implement SAP Note 2502552 . This note delivers check classes used to refine the list of relevant simplification items. After that you can implement SAP Note 2399707 which delivers /SDF/RC_START_CHECK report. You are required to execute /SDF/RC_START_CHECK report in 000 client.

The severity of the resulting messages indicates whether there are no inconsistencies, warnings you should look at, or inconsistencies you need to resolve. The results are provided as green, yellow, or red messages:

Custom code migration and Analysis

With SAP S/4HANA, business processes have been changed and simplified. Hence before converting to SAP S/4HANA you need to check your custom code against the SAP S/4HANA simplifications catalogue. The simplifications are loaded into the Custom Code Migration tool. After you run the tool, you get a list of instances where your custom code does not comply with the scope and data structure of SAP S/4HANA. For Custom code analysis you need a central check system which needs to be either >=1809 or Runs ABAP BASIS 7.52. You can also use App in SAP cloud platform. You need to run tcode ATC (ABAP Test cockpit to run the tests).

Create a RFC connection from Central check system to Source (checked) system
Then you need to configure ATC in central check system to connect to Source (checked) system .
Then you need to import CCMSIDB.zip in your central check system
Now you can run the series from ATC in central check system and evaluate the results of the Remote Code Analysis in ATC via transaction SE80.
Following notes required in Source (Checked system ) -2485231 , 2270689, 2190065
Following notes required in central Check system – SAP Notes 2436688, and 2364916

Cross application and application specific preparation activities

Remove client 066 and all other unused clients.
Uninstall SAP Fiori apps.

Perform application-specific preparations as per S/4 Hana conversion guide. Many checks can be done automatically, using the SAP Readiness Check 2.0. SAP Readiness Check 2.0 is a web based interface which generates dynamic dashboard and static project artifact documentation for the deep analysis based on the data collected by RC_COLLECT_ANALYSIS_DATA report. .Follow SAP Note 2913617 – SAP Readiness Check 2.0. https://help.sap.com/docs/SAP_READINESS_CHECK

SAP Readiness check 2.0 ties all the different analysis and checks and presents the data collected in drillable graphical representation. It’s a dynamic dashboard so you can keep updating information.

Analysis for SAP readiness check is collected by running RC_COLLECT_ANALYSIS_DATA report. You should run this report in your production environment or a copy of your production environment. If using copy addition step is required to download usage data(st03n) from production system and upload into the copy system following the SAP Note 2913617.

Execute program RC_COLLECT_ANALYSIS_DATA in transaction SA38 in the production system to download all checks except the consistency check in the zip file by clicking the button “Download Analysis Data” after the job is completed. RC_COLLECT_ANALYSIS_DATA executes multiple jobs in the background based on the checks you selected while executing the report.

After this Schedule program SYCM_DOWNLOAD_REPOSITORY_INFO as background job in the development system to download the custom code header information in one zip file. Your actual Z-code is not transferred into this file or to SAP. See 2185390 ->

You can launch SAP Readiness Check application https://rc.cfapps.eu10.hana.ondemand.com and use the zip file generated from program RC_COLLECT_ANALYSIS_DATA and click the button Create New Analysis to create a new analysis. You can access the Analysis created when status changes to ready. Now you can open the analysis and update by uploading the zip file generated from program SYCM_DOWNLOAD_REPOSITORY_INFO. You can navigate SAP Readiness check dashboard in different manner and filter on different criteria. You can also provide manual status for the activities as well as provide the comments on each activities. You can also download the report in a fully formatted analysis document to kick start your discovery workshops for SAP S/4 conversion.

With this I would like to conclude this blog . Hope you got good conceptual and technical understanding of the activities and tools required in Prepare phase . Please feel to add any comments to provide details as per your unique conversion experience. Also feel free to revert for any questions you have in this regard.

Reference :- https://rc.cfapps.eu10.hana.ondemand.com

Reference :- Conversion Guide for S/4 Hana

Reference :- SAP Roadmapviewer

Reference :- SAP Readiness Check 2.0

Reference :- ADM328 Guide

Reference :- SAP OSS Notes

Related blog :- SAP S/4 Hana Conversion – I