In my previous blog I showed how to gain some Quick wins from the SAP Readiness Check for SAP S/4HANA given that you had already run the Custom Code Analyzer and the Suite on HANA memory Sizing report.
In this blog, I would like to go into more details and potential stumbling blocks of the SAP Readiness Check for SAP S/4HANA. To start with, it is important to understand how the communication between your Solution Manger and the system that you would like to analyse, the so called managed system, work. In Solution Manager, you get this information from the Technical System that represents the system you would like to analyse:
In my case, there are two RFC destinations from my Solution Manager to my managed system:
- SM_S02CLNT001_READ with user SM_S01
- SM_S02CLNT001_TMW with user SMTMS01
As it turns out, the SAP Readiness Check for SAP S/4HANA uses the latter, so I must ensure that this user has the correct authorizations otherwise you will receive an error message like the following when trying to run it:
There is also one RFC destination back from my managed system to my Solution Manager:
- SM_S01CLNT001_BACK with user SMB_02
This destination I must maintain in maintenance view BCOS_CUST in transaction SM30:
With that I am prepared and able to run the different reports in my managed system:
Custom Code Analyser
Implementing and running the Custom Code Analyser is straight forward, but program SAPRSEUB to update the where-used-index for customer and SAP objects might run for quite some time.
Suite on HANA memory Sizing report
Here it is important not to start program /SDF/HDB_SIZING from transaction SE38 but schedule this program as a background job with function module /SDF/TRIGGER_HDB_SIZING in transaction SE37:
Thus, you can monitor the progress of job /SDF/HDB_SIZING_SM in transaction SM37. As it turns out, the SAP Readiness Check for SAP S/4HANA checks for the successful execution of this job:
Simplification Item Check
Creating the Simplification Item List is straight forward and quite quick:
Business Process Improvement Content
For this ST-A/PI Release higher equal 01S is required. If you ignore this precondition, in the current version of the SAP Readiness Check for SAP S/4HANA, you do not even get an error message but a short dump, because there is a bug in the call of the error message.
SAP Readiness Check for SAP S/4HANA
If you have not implemented Usage and Procedure Logging (UPL) you will get a warning that is safe to ignore:
Finally, the SAP Readiness Check for SAP S/4HANA is on its way and you can monitor its progress in transaction SM37 on the managed system:
Thus, you will get an e-mail with a link to your results in the SAP ONE Support Launchpad:
Also, a respective transaction in the Maintenance Planner will have been created, in case you wanted to progress with the conversion.