10Steps2S4
{SAP Readiness Check}
Pre-activities
Installed Base Conversion
February 2019
Version 2.0
10Steps2S4 – [PRE] Readiness Check
1 Introduction ............................................................................................................................................. 3
2 Preparation of SAP Readiness Check ................................................................................................... 5
2
10Steps2S4 – [PRE] Readiness Check
1 Introduction
The activities described in this document have been already executed in the systems you will use to
complete the activities.
The purpose of this document is to collect these activities for your reference with the scope of document
all the steps you should perform during a real conversion project.
1.1 SAP Readiness Check for S/4HANA
SAP Readiness Check for SAP S/4HANA supports customers who plan to convert existing SAP ERP 6.x
systems to SAP S/4HANA. It checks both your production systems (or copies thereof) and your
development systems for SAP S/4HANA conversion compatibility and necessary conversion preparation
steps.
The results are consolidated in an interactive dashboard for internal or for SAP communication. SAP
Readiness Check for SAP S/4HANA provides a pre-conversion overview, useful for identifying current
system landscape preparation steps, well in advance of your SAP S/4HANA system conversion project
start date.
The SAP Readiness Check for SAP S/4HANA evaluates specific areas and provides detailed information
about the results. The areas are as follows:
1.2 Readiness Check execution mode
The SAP Readiness Check can be executed in 2 different ways:
1. Using the Solution Manager to extract the data from the managed system to be converted and
send this data in a secure way to SAP Portal where will be analyzed to produce the resulting
dashboard. This option is recommended.
3
10Steps2S4 – [PRE] Readiness Check
2. Use directly the managed system without Solution Manager and then upload the data manually to
the SAP Readiness Check tool in the cloud
For the purpose of this program has been decided to use option 2 because it provides an easy way to
obtain the result for each partner in the local customer number without involving use of Solution Manager.
4
10Steps2S4 – [PRE] Readiness Check
2 Preparation of SAP Readiness Check
2.1 Implement required notes
2310438 - SAP Readiness Check for SAP S/4HANA - Managed System
Implement all the notes listed here in the latest release before executing the extraction for the analysis.
Preparation Step SAP Note Title Note Comment
Number
Setting up custom Custom Code Analyzer 2185390
code analysis
Collecting HANA sizing Suite on HANA memory Sizing report 2504480 Minimum ST-PI version:
data
700 SP12
or 740 SP02
This preparation step is not necessary if
you have ST-PI version
ST-PI 700 SP17
or ST-PI 740 SP07
Enabling Simplification SAP Readiness Check – Simplification 2399707 You shall use SNOTE to implement the
item check Item Check correction instructions of this note only.
No need to follow the description to
implement other notes, which are not
relevant for Readiness Check analysis,
especially the SAP Note 2502552 is not
required.
Enabling Business SAP Readiness Check for SAP 2443236
Process Analytics S/4HANA Business Process
analysis Improvement Content
Enabling Data Volume DVM API to trigger monitor ST14 2612179
Management analysis analyses for readiness check
Setting up SAP SAP Readiness 2310438 You can use SNOTE to implement the
Readiness Check Check for SAP S/4HANA - Managed correction instructions of this note only.
System
1. Implement version 55 of note 2185390 using transaction SNOTE
2. Implement version 108 of note 2399707 using transaction SNOTE
3. Implement version 5 of note 2504480 using transaction SNOTE
4. Implement version 30 of note 2443236 using transaction SNOTE
5. For the Data Volume Management analysis:
a. Implement version 6 of note 2611746 using transaction SNOTE as a pre-requisite
b. After implementing note 2611746 run the report “NOTE_2611746” with the option
“Update & Activate”
c. Implement version 3 of note 2612179 using transaction SNOTE
d. Implement version 15 of note 2693666 using transaction SNOTE
6. Implement or update to version 73 of note 2310438 using transaction SNOTE
