Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Do you have questions about SAP S/4HANA deployment? Have you ever wondered…
How big should my SAP HANA database be?
Are my add-ons compatible with SAP S/4HANA?
What SAP Fiori applications are relevant to my users?
Which business functions I run are affected by SAP S/4HANA?
Which transactions I run are affected by SAP S/4HANA?
Will my custom code objects work with SAP S/4HANA?
You could get answers to these questions before, of course, but you needed several different SAP tools to get them and it was time consuming. Sadly, this complexity kept many SAP customers from beginning their SAP S/4HANA planning and discovery tasks. Now this will no longer be an excuse!
Readiness Check is available free to anyone who has an SAP maintenance agreement (an S-user account). Working with your BASIS team, you upload your SAP ECC 6 configuration and the result is a beautiful dashboard:
The dashboard covers everything from HANA sizing to custom code analysis, to recommended Fiori applications. The best part is the information is based on your exact deployment. By clicking on each of the tiles, you drill down to more detail and can act on what you see. Here, for example, is the HANA sizing detail:
Even if you are unsure of your exact SAP S/4HANA deployment plans, there is a lot of valuable information in Readiness Check. Be sure to check it out on the SAP Help Portal. We have 2 other tools that can help your S/4HANA planning as well: Business Scenario Recommendations and Transformation Navigator. Watch this "S/4HANA in 2 Minutes" video to learn more:
Excellent blog Carl. Cleared a lot a questions about Readiness check.
As per OpenSAP courses Readiness check is part of SAP Solution Manager.
Will this feature also be available via Solution Manager 7.2 or is it a cloud application like Maintenance planner which is only available via SAP Marketplace?
It is a cloud application and you will need an S-user account. Once I get the link to it when it goes live, I plan to update this blog post with that info.
Readiness Check is for planning a system conversion (converting an ECC system to S/4HANA), which can be done with on premise deployments or private cloud deployments. The S/4HANA public cloud does not support a system conversion.
BSR is different than RC and both will be useful in planning S/4HANA. BSR is focused on business processes and how they improve with S/4HANA, while RC is focused on the technical details that need to be done before a system conversion.
Anyone with an S-user account assigned to your company can look at the RC cloud dashboard and this is the preferred way to share results. For those who do not have an S-user, there is a "Create Results Document" option in Solution Manager for printing or sharing the RC results.
Very interesting topic Carl! With the lure of the potential benefits of deploying SAP S/4 HANA, companies are already beginning explore the business case of making a transition to this latest release from SAP. The option of running SAP S/4HANA on-premise or in the cloud gives customers the flexibility of choosing a model that best matches their IT strategy and business needs. Hence it becomes all the more important for such organizations to have an SAP S/4HANA Readiness Check to create their migration strategy.
thank you for the blog, we already tried the Readiness Check Tool. It gives a ton of information.
One question emerged though. Is it still necessary to make the Pre-Checks, which are done via the report “R_S4_PRE_TRANSITION_CHECKS” in the system? Is the new tool complementary to the Pre-Checks?
Because as we have done the Readiness Check both ways, the Pre-Checks showed us slightly different results than the Simplification Items in the new Readiness Check.
I will wait for Carl to reply and confirm below understanding.
As per my research, Pre-Check done via report R_S4_PRE_TRANSITION_CHECKS will still be required, used during planning for system conversion and during system-conversion step.
The tool “Readiness Check” is primarily to be used much before, at S/4HANA enquiry stages to get a high-level view of quantum of work/effort to be expected if adopting S/4HANA thru System Conversion.
Thanks, Monika. Yes, you are correct. The system conversion toolset requires the readiness check report. Why the two result sets are slightly different as reported by Tobias, though, I don't know.
For S/4HANA 1709 a new pre-check report based on Simplification Item will be delivered. The report is /SDF/RC_START_CHECK. Detail description will be provided in the SAP Note https://launchpad.support.sap.com/#/notes/0002399707 when S/4HANA 1709 is released. Currently the relevance result has already been consumed by SAP Readiness Check. The consistent check will come soon.
The new pre-check report is /SDF/RC_START_CHECK, actually it has a new name "Simplification Item Check". AGSRC_START_ANALYSIS is the report to start the SAP Readiness Check in SAP Solution Manager. More detail will be provided when SAP S/4HANA 1709 is released.
You can find the user guides here: https://help.sap.com/viewer/p/SAP_READINESS_CHECK. Readiness Check requires an S-User account with SAP. Someone with an S-User and the appropriate rights to run the reports described in the documentation would then start the process to run Readiness Check.
About service marketplace and S-users: https://websmp201.sap-ag.de/
For customers that aren't using all the functionalities in Solution Manager such as CCLM, is there a way to extract the data from the ECC system itself and still generate the Readiness Check report?
have you find an answer to this question? I am also interested what is the minimum system requirements for readiness check to run? I have heard that readiness check report can be run only on an ERP system running on SAP ECC 6.0 [any enhancement package from 0 to 8] or on SAP S/4HANA Finance [1503/1605] or on SAP S/4HANA [1511, 1610, and 1709], but I couldn't find the information on an official SAP note or something.