The SAP readiness check is normally used to asses the impact of an ECC to an S4HANA system upgrade or conversion (read this blog).
It can also be used to asses the impact of an upgrade of a lower S4HANA version to a newer S4HANA version.
Preparation for the S4HANA readiness check
First apply the notes listed in master note 3059197 – SAP Readiness Check for SAP S/4HANA upgrades. If you have a short dump after start of program RC_COLLECT_ANALYSIS_DATA, follow the instructions in OSS note 3093810 – Executing report RC_VALUE_DISCOVERY_COLL_DATA immediately results in an ABAP Dump CX_SY_DYN_CALL_ILLEGAL_FUNC.
Also apply the notes mentioned in OSS note 3061414 – Enabling extended integration impact analysis for SAP Readiness Check, if you want to include ALE scenario’s in your analysis.
If you have to upgrade to a newer version, apply the latest version of the 305197 note and afterwards use the “Update latest version form SAP catalog”, as explained in OSS note 3213713 – SAP S/4HANA Readiness check report do not show latest S/4HANA target releases.
Running the check
Start program RC_COLLECT_ANALYSIS_DATA:
Start the batch job and wait until it is done.
Start program RC_COLLECT_ANALYSIS_DATA again and push button Download Analysis Data.
This file you need to upload on the SAP Readiness check site.
After you have uploaded the results SAP needs about 1 hour to process the results. Then you can look at the items you need to consider for your S4HANA release upgrade:
Remark: the amount of items will be far less than the ECC to S4HANA conversion readiness check.
Bug fix notes
Bug fix notes: