Skip to Content
Technical Articles

Conversion to S/4HANA 1809FPS0 – t2 – Readiness Check 2.0

This blog is for the detailed steps for Readiness Check (RC) 2.0 for step t2 of conversion to S/4HANA 1809FPS0, FPS1 and FPS2. Readiness Check is an optional step and is a high level analysis to get a Results  Dashboard and also download to a Results Document with details of Active Business Functions, Add-On Compatibility,  Custom Code Analysis, Recommended Fiori Apps, S/4HANA Sizing, Simplification Items, Business Process Analytics and Data Volume Management.

Download the Readiness Check User Guide for reference

Please find other blogs as follows:


NEW INSTALLATION        PART1 – MP PART2 –  Installation
PART3 –  BP Activation
PART4 – Fiori Activation
S/4HANA 1809 fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0
S/4HANA 1709
fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0
S/4HANA 1610
fps2  fps0 fps2  fps0 fps2  fps1  fps0
S/4HANA 1511 fps2  fps1
S/4HANA UPGRADE   t2 – MP t3 – SIC
t4 – CCM t5 – SUM
S/4HANA 1809 link link link link
t5 – CCM t6 – SUM 
S/4HANA 1809 rc2  rc1 link link link EHP7/hdb
S/4HANA 1610 FPS0 link link link
S/4HANA 1709 FPS1 link link
OUTPUT MANAGEMENT link  link  link link

Please find the process flow diagram with application of notes as below.

All steps are according to Note 2758146 – SAP Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendations  version 11. Click on Show Changes for revisions.


De-implement any of the notes if they were implemented earlier. In case of ABAP class inconsistency, please clean up the class header in transaction SE24, specify the object and select Utilities => Regenerate sections in the change mode.

If you face issues with above, please open OSS message. If you try to download latest version of note and apply, it may cause a bigger issue with a lot of time wasted later on.

You should have 6-8 weeks of transaction history (tcode ST03) in the production system or the system in which you want to execute the application analysis. Otherwise, SAP Readiness Check for SAP S/4HANA can return inaccurate or incomplete results.


Apply Note 2185390 – Custom Code Analyzer  (includes manual steps)

This note will download other dependent notes, and then some other dependent notes and this goes on. Number may vary depending on your patch level. The Note requires Manual steps as below:

As per Manual steps above, In SE80 create Package SYCM_MAIN

Create SubPackage SYCM_ANALYSIS

Confirm Manual step. Then the note application will prompt for another manual step depending on your SP level, its only applicable to the narrow range of SAP_BASIS SP08 to SP11 only.

In SE11, create table WBINDEX You will require the developer key and object access key.

Add field PROGNAME and confirm manual step.

In SA38, run SAPRSEUC in background. This is a long running job and runs single threaded by default. You can run it in parallel to save time as explained in the next step which is optional.

TIP: Please note it is not required to run the job SAPRSEUB, which updated Where-Used list for the whole system, the SAPRSEUC updates Where-Used list for Customization only. Job SAPRSEUB used to run several days like 11 days at one customer. The good thing is if it is cancelled it continues from the point it was cancelled with a overhead or 20-30 mins for every restart.


Apply note Note 2667023 – Runtime of job EU_INIT or SAPRSEUB/SAPRSEUC, performance  Manual steps are in Note 2228460 – Runtime of job EU_INIT, SAPRSEUB, performance

You will have to register developer if needed, and register object to get Access key and fill in as below:

Add 2 fields as below:

In SE38, BSP_INIT_INDEX_CROS, Variant , Change, add text elements as below. there are 7 programs and 1 class with text elements to be updated.

You may also be prompted for Programs WDY_INIT_INDEX_CROSS, SAPRSEUI, QSC_INDEX_ALL_PROXIES to add text elements.

After applying the note, job runs with one background process and uses number of dialog processes as defined in (1) table RSEUPACTRL as below. (2) Add column ALLSERVER, if it is blank, (3) Mark X for parallel processing and (4) define percentage of dialog processes to be used according to timezone. If this is sandbox that you want to finish the job as soon as possible you could jackup these percentages.


Apply Note 1872170 – ABAP on HANA sizing report (S/4HANA, Suite on HANA…) – cannot be implemented in SNOTE. Please read the note.

Using tCode SNOTE apply Note 2734952 – HANA memory Sizing report – Advanced correction 12 So far this is the latest, if there is later note please apply that note instead of 2734952.

Please note:

  1. Note requires minimum ST-PI 740/SP02 or 700,710/SP12 to apply the note.
  2. If you already have ST-PI 740/SP08 or 700,710/SP18 the note is already applied.
  3. If you don’t want to apply ST-PI, instead of applying this note, implement report ZNEWHDB_SIZE as described in Note 1872170 – ABAP on HANA sizing report  Please note that if you take this option, there are 3 programs and function module to be created/updated to latest code.

TIP: ST-PI is independent and doesn’t need other components or stack.xml to apply, this would save lot of manual work. In the Note it is mentioned that to include sizing in analysis report dashboard, it is recommended to have ST-PI 740/SP07, 700,710/SP17

In tcode SE38, check that program /SDF/HDB_SIZING is available and you can even run it for test now.

Please use below for troubleshooting if you run into issues. The same program runs later on when  scheduling analysis and the job RC_COLLECT_ANALYSIS_DATA is run as per STEP 12.


Apply Note 2399707 – Simplification Item Check. This can be applied quickly. There are no Manual corrections.


Apply Note 2745851 – Business Process Improvement Content for SAP Readiness Check 2.0 and Next Generation SAP Business Scenario Recommendations Content.  This can be applied quickly in the productive client. There are no Manual corrections


Apply Note 2769657 – Interface Discovery for IDoc as part of Readiness Check

You need minimum ST-A/PI 01S_700/01S_731. Apply using SAINT.


The note can be implemented for ST-PI 740 SP01 700/710 SP09

Apply Note 2612179 using SNOTE.

As per manual instructions folow this sequence,

  1. SNOTE apply Note 2611746 – DVM Create objects for APIs for triggering and monitoring ST14 analyses
  2. tCode SE38 run program NOTE_2611746
  3. SNOTE will apply Note Note 2612179 – DVM API to trigger and monitor DVM ST14 analyses for Readiness Check
  4. In SNOTE apply Note 2693666 – Enhance error handling when collecting DVM ST14 data for SAP S/4 HANA Readiness Check

TIP: If there are any errors in DVM data collection, refer Note 1159758 -Data Volume Management: Central Preparation Note and also Note 2721530 – “FAQ for collecting DVM data during S/4 HANA Readiness Check.


Apply Note 2758146 – SAP Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendations

This prompts for applying Note 2185390 – Custom Code Analyzer and you already did it in earlier step, so confirm. We have already applied this note.


Apply Note 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks

There is an elaborate process to apply this note. Please refer the steps 1-5  in the Simplification Item Check blog

TIP: You could apply this note later and then run the job RC_COLLECT_ANALYSIS_DATA to output the zip archive file to update the dashboard later.


In SE38 run background job SYCM_DOWNLOAD_REPOSITORY_INFO. Define the variant to restrict to the required namespace.

Then run the program in background using this variant.


In case you get below dump:

After the job is finished, in SE38 run SYCM_DOWNLOAD_REPOSITORY_INFO again and click on button to Download Zip file…

The solution is – Enter tCode SE38, Program LZEHPRC_CP_BB20UXX, click on Change (You will need developer access). Go to menu option Utilities, Settings.

select option above, click on OK, Save and Activate the program. Unfortunately you have to Rerun the job from the beginning.




In the productive client, tCode SE38RC_COLLECT_ANALYSIS_DATA (1) select target S/4HANA Version, (2) Schedule Analysis, (3) Immediate. As per the note 2758146, if you do not have the min ST-PI 700/710 SP17 or 740 SP07, then unmark the checkbox for HANA Sizing Data.

This will trigger number of background jobs as shown in next step.

You should get message that Job RC_COLLECT_ANALYSIS_DATA is scheduled, and a series of messages.

TIP: If there are any errors in DVM data collection, refer Note 1159758 -Data Volume Management: Central Preparation Note and also Note 2721530 – “FAQ for collecting DVM data during S/4 HANA Readiness Check.

If you get this error, apply Note 2443236 – SAP Readiness Check for SAP S/4HANA Business Process Improvement Content and also the needed ST-A/PI through SPAM.


There are various jobs launched in order as below and you must check job logs to ensure the data was collected properly.

Job RC_COLLECT_ANALYSIS_DATA is the main job to collect analysis data.
Job TMW_RC_BPA_DATA_COLL is scheduled to collect Business Process Analytics data
Job TMW_RC_HANAS_DATA_COLL is scheduled to collect HANA Sizing data
Job TMW_RC_DVM_DATA_COLL is scheduled to collect Data Volume Management data
Job /SDF/HDB_SIZING_SM is scheduled to collect data for sizing
Job TMW_RC_SITEM_DATA_COLL is scheduled to collect Simplification Item relevance check data
Job BO APPLICATION ANALYSIS NN scheduled for DVM triggers TAANA and DANA Analysis
Job TAANA ANALYSIS is scheduled for large Table Analysis
Job DANA ANALYSIS is scheduled for Data Volume Management Analysis

After the job is finished, in SE38 run RC_COLLECT_ANALYSIS_DATA again and click on button to Download Analysis Data as shown in previous step.


In SAP Launchpad (S-USER is required) url (1)
(2) Start New Analysis, (3) Analysis Name, (4) Customer, (5) Browse, (6) Select zip file, (7) & (8) Terms of use, (9) Create.

Once the analysis is in ready state (about an hour), Open the analysis and use the zip file generated from program SYCM_DOWNLOAD_REPOSITORY_INFO and click (1) icon on the top right, (2) Browse, (3) select filename, (4) Terms of Use,(5) Update .

You can click on wheel (1) and switch on (3) for Update & Delete to input  details of (3) email id click on Save (4). You can click on + to add more email id’s.

You can view the Results Dashboard as shown below.

Above steps complete the readiness check.

Unlike Readiness Check 1.0 you cannot download the report in a word document. The idea is to use it as a dashboard which has much more benefit to the project and team collaboration online. Customer can provide access to any Implementation Partner with P-User which can be easily created or SAP employee.

TIP: In case you decided to apply the Note 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks later, you can run the program RC_COLLECT_ANALYSIS_DATA ,simply click on Update Analysis icon to upload the zip archive update the analysis. Dashboard will retain old data for other items and update the Simplification Item consistency check.
You can also do this for example sizing data is required to be updated => apply the latest sizing note and run the program RC_COLLECT_ANALYSIS_DATA with checkmark on Hana sizing and then click on Update Analysis to upload the zip archive.

There is no option available to create the Readiness Check 2.0 through Solution Manager.

Use component for Readiness Check: SV-SCS-S4R to report problems during preparation or execution.


As shown in the main graphic, you could run analysis related to Custom Code on DEV system so you analyze code that has never gone into production. If you want to analyze only code that has gone into production please run analysis related to Custom Code in PROD.
Another reason for running Custom Code Analysis job in DEV system is where used index may take a while in PROD system.

TIP: During your regular maintenance patch update, please include ST-PI & ST-A/PI, that way some of the required notes are already applied. Both these OCS Packages ST-PI and ST-A/PI do not need stack the xml and can be applied separately.


Readiness Check Help Portal
Readiness Chck User Guide
Note 2758146 – SAP Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendations
Readiness Check Jam Group
Readiness Check video
Expert Guided Implementation (EGI)     <====sessions on Learning hub

Thank you. Hope you enjoyed the blog !

Mahesh Sardesai
Product Expert – S/4HANA

You must be Logged on to comment or reply to a post.
  • Hello Mahesh,

    Great effort on highlighting all steps for Readiness Check 2.0.

    But I would like to highlight few things here. The last screenshot of dashboard, is really from new application of SAP Readiness check 2.0? Because I got different visualization in dashboard.

    I think for SAP Readiness Check 2.0 we have to use URL, not as mentioned in your steps.

    Also we first need to upload only RC_COLLECT_ANALYSIS_DATA file while creating analysis report (there is no provision to upload both report at the same time) and once it is in ready state we upload SYNC_DOWNLOAD_REPOSITORY_INFO by clicking on the left hand icon of “update analysis”. It will update the report.

    I feel steps mentioned here are bit misinforming as it highlights some part of SAP Readiness Check 1.0 as well.



  • Hi Mahesh,

    I came to step 16 without any problem and while uploading my, I received this warning: “Analysis creation failed: The uploaded file is not valid. Check that the file is downloaded using report RC_COLLECT_ANALYSIS_DATA.”

    I don´t know what to do or where to find the reason.

    Can you help me please?

    Best regards

    Slavomír Hronec

  • Hi Mahesh,

    I executed a readiness check 2.0 and I got some problems:

    • the rc_collect_data extractor has been executed on QUA system, where there are some statistics data of production system (QUA is a recent copy of production system), linked to production SID: the RC_COLLECT_DATA report manage correctly these production infos?
    • to get the hana db sizing preview I execute the custom ZNEWHDB_SIZE report. When I execute the RC_COLLECT_DATA report, i have to exclude the DVM and Hana Size flag because on my system I haven’t the /SDF/NEWHDB_SIZE report. It’s possible to generate the xml file related the hanadb size, to add the RC2*.zip file, so I could upload these information to readiness check 2.0 cockpit?
    • from the readiness check cockpit I don’t get informations about the business process discovery. The log of TMW_RC_BPA_DATA_COLL job doesn’t show messages, I don’t find missing authorizations…what could be happened?

    thank you in advance


    • Hi Simone,

      have you get any reply for the topic “why don´t get any informations in section business process discovery”?
      We have the same problem but I can´t get any information how to solve that issue.

      Thanks & Regards,

    • Hi Simone,

      1. You should have 6-8 weeks of transaction history (tcode ST03) in the production system or the system in which you want to execute the application analysis. Otherwise, SAP Readiness Check for SAP S/4HANA can return inaccurate or incomplete results. If you are using older system copy, update data using SAP Note 2568736 – SAP Readiness Check for SAP S/4HANA – copy ST03N data.
      2. I am not sure if you can add the file manually. I would prefer to apply ST-PI so job can be run for the latest advance correction for sizing as mentioned.
      3. Please apply note 2758146-SAP Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendations

        Please note that this particular note is to be applied in productive client and if you have applied it in client 000 it may not pull data. Also please note the main graphic the program RC_COLLECT_ANALYSIS_DATA has to be run in productive client not 000 or other client.


      • Mahesh
      • Thank you Mahesh for your reply.

        About first point, I charged the productive statistics on TST system and I got the infos.

        About the second, ok: I’ll analyze the summary from the ZNEWHDB_SIZE log.

        On referring to point 3, I applyed the suggested sapnote into the used client, and executed the RC* tool on correct client, but the business process analysis is unavailable from both readiness check, because the bpa.xml is quite empty.


  • HI Mahesh

    is it possible to run the readiness check in a CCS (SAP Utilities) version 6.03?

    SAP ECC is installed in another instance and will be kept as is.

    In CCS there are thousands of developments and readiness would help in the evaluation

    another question: my customer is live in S/4HANA  1511. Can I run readiness check?

    thanks a lot in advance


    • Hi,

      Readiness Check is primarily for Conversion of ERP to S/4HANA. It looks like you would like to analyse custom code and it would be good to do the check for Custom Code Migration Worklist and this will require Netweaver 7.52 system.

      You can do the readiness check for upgrade to get summary report but being already on S/4HANA the benefit here is reduced. You could prepare the simplification list itself by applying note 2502552 as you already have TCI note in the system, it may be little effort to get to the final iist.

  • Hi all,

    do you – really?! – call this a decent “Readyness check”? I’d assume, that nothing is ready, i.e. prepared from the vendor. “Run simple” by delegating the work, trial and error  to the customer.

    What a foreseeable mess…


    • Hi Joerg,

      Sorry that the tool did not meet your expectations. It has been tested well with our testing team and partners. Please let us know issues you are facing so we can consider for improvement.


  • Hi @ all,

    does anyone have an idea why section business process discovery don´t deliver any information?
    In every section of the readiness check 2.0 I receive information except for this section of business process discovery.

    Would be great to get an answer how to solve this issue.

    Thanks & Regards,