Skip to Content
Technical Articles
Author's profile photo Mahesh Sardesai

S/4HANA Conversion – t2 – Readiness Check 2.0 step-by-step

Updated Feb-2021

This blog is for the detailed steps for Readiness Check (RC) 2.0 for step t2 of conversion to S/4HANA. 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.

Please find other blogs as follows at S/4HANA SQUARE ONE

SAP S/4HANA  SQUARE  ONE

NEW INSTALLATION     PART1 – MP PART2 –  Installation
PART3 –  BP Activation
PART4 – Fiori Activation PART5 – DATA MIGRATION
S/4HANA 2020 fps1 fps0 fps1 fps0 fps1 fps0 fps1 fps0 fps0
S/4HANA 1909 fps2 fps1  fps0  fps2 fps1  fps0 fps2 fps1  fps0 fps2 fps1  fps0 fps0
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
UPGRADE   t2 – MP t3 – SIC
t4 – CCM t5 – SUM
S/4HANA 1809+ link link link link
SYSTEM CONVERSION t2 –  RC t3 – MP t4 – SIC
t5 – CCM t6 – SUM 
S/4HANA 1909+ rc2
bsr
link link link prepare
EHP6/mss
S/4HANA 1809
rc2 link link link EHP7/hdb
EHP6/db6
EHP5/ora
EHP6/mss
SAP S/4HANA ON-PREM APPLIANCE INSTALL USING MEDIA ACTIVATE FROM CAL
S/4HANA 1909+ link custom link standard link
SAP S/4HANA CERTIFICATION
S/4HANA Certification Exams through SAP Certification Hub link

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

All steps are according to Note 2913617 – SAP Readiness Check 2.0 version 8. Click on Show Changes for revision comparison.

STEP 1: PREPARATION

De-implement any of the notes if they were implemented earlier. In case of ABAP class inconsistency, please clean up the class header in tcode SE24, specify the object and select Utilities => Regenerate sections in the change mode. If you have SAP Note 2310438 implemented in your system, de-implement note 2310438 first.

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.

STEP 2: SETTING UP READINESS CHECK

Using SNOTE apply Note 2758146 – SAP Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendations

STEP 3: SET UP CUSTOM CODE ANALYSIS

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 now or after the optional step to run it in parallel to improve performance. This is a long running job and runs single threaded by default.

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.

If you have issues in running this job the component for OSS message is BC-DWB-CEX.

STEP 3A: (OPTIONAL) IMPROVE PERFORMANCE OF JOB SAPRSEUC

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.

You can now schedule the job SAPRSEUC if you decided to do the optional steps.

STEP 4: ENABLING S/4HANA SIZING DATA COLLECTION

Read Note 1872170 – ABAP on HANA sizing report (S/4HANA, Suite on HANA…) – cannot be implemented in SNOTE.

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

Please note:

  1. Note requires minimum ST-PI 740/SP02-12 or 700,710/SP12-22 to apply the note.
  2. 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: You could save lot of manual work by applying ST-PI. To apply it doesn’t need any other components or stack.xml.

IMPORTANT: In the Note 2913617 it is mentioned that to include sizing in analysis report dashboard, it is recommended to have min 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 13.

STEP 5: ENABLING SIMPLIFICATION ITEM CHECK

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

STEP 6: ENABLING BUSINESS PROCESS ANALYTICS ANALYSIS

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

STEP 7: ENABLING IDOC ANALYSIS

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.

STEP 8: ENABLING DATA VOLUME MANAGEMENT ANALYSIS

Read Note 2721530 – FAQ for collecting DVM data during S/4HANA Readiness Check – cannot be implemented in SNOTE.

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

FIRST: Follow Note 1159758 – Data Volume Management: Central Preparation Note all steps related to Target system (System to be analyzed)

tCode SA38, RTCCTOOL, Click on Settings, Flag option ‘Prepare for DVM (Data Volumt Mgmt) service ?’, Click on Save.
Please make sure that this section shows a green light for all SAP Notes which are related to the planned DVM services

SECOND: Apply Note 2612179 using SNOTE.

As per manual instructions follow 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/4HANA Readiness Check

THIRD: tCode SA38, RTCCTOOL – check other DVM notes required on the system

STEP 9: ENABLING BP/CVI

Apply Note 2811183 – S/4 Readiness Check Development

If you have issues in running the job the component for OSS message is AP-MD-BF-SYN

Please do the manual steps as below:

STEP 10: ENABLE INNOVATION POTENTIAL CHECK

Apply Note 2827612  Enable Innovation Potential check in SAP Readiness Check for SAP S/4HANA

STEP 11: ENABLE EFFORT DRIVERS OF SIMPLIFICATION ITEMS

Apply Note 2903677 – SAP Readiness Check: Effort Drivers of Simplification Items Check

STEP 12: ENABLING FINANCIAL DATA QUALITY ANALYSIS

Apply Note 2972792 – Financial Data Quality: Trigger Data Collection Reports to Check Your Financial Data Quality and to Enable the Financial Data Quality Check in SAP Readiness Check

STEP 13: RUN BACKGROUND JOB IN DEV SYSTEM TO DOWNLOAD METADATA INFO

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.

ERROR SITUATION: If the where-used list index for customer objects is not up to date you will get error below:

Please refer Note: 2655768 – Custom Code Analyzer – The where-used list index for customer objects is not up to date

STEP 14:  MONITOR BACKGROUND JOB AND DOWNLOAD ZIP FILE

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

In case you get below dump:

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.

STEP 15: TRANSPORT 7+ NOTES TO PRODUCTION

In tCode SE01, release transport and using tCode STMS import into QAS and PROD systems in the landscape.

STEP 16: RUN BACKGROUND JOB IN PROD SYSTEM

In the productive client, tCode SE38RC_COLLECT_ANALYSIS_DATA (1) select target S/4HANA Version, (2) Schedule Analysis, (3) Immediate and (4) ok. 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: The scope selection “Simplification item relevance” can be checkmarked from above screen as it is client independent. BUT…… , when selecting “Simplification Item Consistency” the job has to be run in client 000 since the SUM tool runs this in client 000 during conversion.

ERROR SITUATION 1: 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/4HANA Readiness Check.

ERROR SITUATION 2: 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.

STEP 17: MONITOR BACKGROUND JOB AND DOWNLOAD ZIP FILE

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

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

The above jobs are related to below along with components in case you would like to create OSS message. In case the job is cancelled due to error, you will not be able to download analysis data. Rerun the job again.

TIP: The financial Data Quality Analysis is a new feature and in case the job cancels you can create ticket for now and may take time to resolve. You can add that option later after the issue is resolved.

JOB COMPONENT STEP REPORT
RC_COLLECT_ANALYSIS_DATA SV-SCS-S4R 2 Master Report
TMW_RC_BPA_DATA_COLL SV-SMG-MON-BPM-ANA 6 Business Process Analysis
TMW_RC_EFD_DATA_COLL CA-TRS-PRCK 11 Effort Drivers of Simplification Items
TMW_RC_INNOVA_DATA_COLL SV-SCS-S4R 10 Innovation Potential
TMW_RC_SITEM_DATA_COLL CA-TRS-PRCK 5 Simplification Item Check
TMW_RC_FDQ_DATA_COLL SV-SCS-S4R 12 Financial Data Quality
/SDF/HDB_SIZING_SM XX-SER-SAPSMP-ST 4 Sizing
TMW_RC_HANAS_DATA_COLL XX-SER-SAPSMP-ST 4 Sizing
BO APPLICATION ANALYSIS 02 SV-SMG-DVM 8 Data Volume Management
DANA ANALYSIS SV-SMG-DVM 8 Data Volume Management
TAANA ANALYSIS SV-SMG-DVM 8 Data Volume Management
TMW_RC_DVM_DATA_COLL SV-SMG-DVM 8 Data Volume Management

ERROR SITUATION 1: If the job TMW_RC_HANAS_DATA_COLL gives error – internal Error! Set GF_INCLNO in 00F_SET_INCLNO, refer SAP Note  2809344 – Job TMW_RC_BPA_DATA_COLL is cancelled with error: “internal Error! Set GF_INCLNO in 00F_SET_INCLNO” which suggests to apply Note 2557474.

ERROR SITUATION 2: If the job fails with error below, please apply SAP note 2919704 – Background Job of Readiness Check terminates because of error message being raised from underlying API’s and run the job again.

STEP 18: GENERATE READINESS CHECK RESULTS DASHBOARD

In SAP Launchpad (S-USER is required) url (1) https://rc.cfapps.eu10.hana.ondemand.com
(2) Start New Analysis, (3) Analysis Name, (4) Customer, (5) Browse, (6) Select zip file RC2AnalysisDataSIDyyyymmdd.zip, (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 S4HMigrationRepositoryInfoSID.zip, (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.

Readiness Check should be used as a interactive dashboard which has the greatest benefit of online team collaboration. It is now possible to download the Readiness Check as a word document like in Readiness Check 1.0. Customer can provide access to any Implementation Partner with P-User which can be easily created or SAP employee. The access can also be revoked as needed.

ERROR SITUATION 1: In case you get the message below, it is likely that your system is not connected properly through Solution Manager to the SAP Support Portal. Please refer Note 2408911 and blog that explains how the system should be connected to Solution Manager – https://blogs.sap.com/2018/11/12/conversion-to-s4hana-1809fps0-t3-maintenance-planner/

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

STEP 19: (OPTIONAL) ENABLE ATC CHECK RESULT EXPORT

This step to be implemented in ATC system with NW 7.52 (not ERP). First you have to setup the systems as needed for ATC check.

Please follow the elaborate process to apply notes in Checked System as per blog – S/4HANA Conversion – t5 – Custom Code Migration step-by-step

From above blog, apply the required 4+ notes in checked system, Apply 3+ notes in Central Checking system which should be Netweaver 7.52 or higher.

In the Central Checking system run tCode ATC, Runs, Manage Results. In the ATC Results Browser select (1) the result series, Right Click and select (2) Export File for, (3) SAP Readiness Check for S/4HANA”. You will doenload a file named <SID>_atc_findings.zip

You can get the results in the Custom Code Analysis tile as shown below:

If you have issues in running this job the component for OSS message is BC-DWB-CEX.

STEP 20: (OPTIONAL) ENABLE CONSISTENCY CHECK RESULT EXPORT

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 – S/4HANA Conversion – t4 – Simplification Item Check step-by-step

You can run the program RC_COLLECT_ANALYSIS_DATA selecting all items or below.

Download the zip file and 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. If you have issues in running this job the component for OSS message is CA-TRS-PRCK.

You can also do this for example if only 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.

LANDSCAPE CONSIDERATIONS:

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

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.

After the sandbox run, when you start with conversion of DEV system, please apply notes in DEV/QAS/PROD/PREPROD/TRAINING at the same time so that the notes are same across the landscape. If you do this at different times the notes are likely to be of different version. Also apply ST-PI & ST-A/PI at same time.

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.

OTHER REFERENCES:

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

Expert Guided Implementation (EGI) <===== sessions on SAP Learning Hub, SAP Enterprise Support Edition*
*Only SAP Enterprise Support customers are eligible to attend this remote training workshop. Please note that to access the SAP Learning Hub, edition for SAP Enterprise Support, a one-time registration is required. A detailed step-by step guidance can be found here

FAQ blog – SAP Readiness Check 2.0 for SAP S/4HANA – FAQ & What’s New in Releases

SAP Readiness Check for SAP S/4HANA – What’s New in November 2020

SAP S/4HANA 1909 System Conversion Steps & Details – How to be prepared

Thank you. Hope you enjoyed the blog !

Mahesh Sardesai
Product Expert – S/4HANA

Brought to you by the SAP S/4HANA Regional Implementation Group

Assigned tags

      20 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Wenjie He
      Wenjie He

      very good!

      Author's profile photo shuai hu
      shuai hu

      hi, i wonder how to deal with the zip file generated by SYCM_DOWNLOAD_REPOSITORY_INFO. thanks

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi Shuai,

      As shown in the graphic, the zip file generated by SYCM_DOWNLOAD_REPOSITORY_INFO should be uploaded as the next step (upload2).
      This is to be done after you have the report online from the first file import.

      • Mahesh
      Author's profile photo damodara damodara
      damodara damodara

      Hi,

      Do you have anything for sap CRM to s/4 Hana cm conversion?

       

      Regards

       

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi damodara,

      Sorry I don't have anything for conversion from CRM to S/4HANA CRM.

      • Mahesh
      Author's profile photo Somraj Roy
      Somraj Roy

      Dear Mahesh,

       

      We are planning a conversion to S/4HANA. Can you please inform what kind of estimation we can use for CCM ? Customer is asking for estimates. Does SAP provides any tool ? If not then can we use our earlier bottom-up estimator ?

      Additionally according to my understanding after RC2.0 we would not need maintenance planner. Can you kindly clarify ? Incase you suggest that we need then please mention the exactly which tools shall I use ? I will follow it on my project which has just started. This is little urgent. Kindly help with details

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi Somraj,

      Sorry for delayed reply. I am not aware of any tool for CCM estimation

      Readiness Check is used well in advance for finding the details of tasks required to be resolved but when you actually want to do your first sandbox conversion you will have to run the maintenance planner in order to download the stack xml file needed for conversion.

      You can start working on items on Readiness check but don't wait till just before sandbox conversion to do the Maintenance planner. There maybe showstopper items that may not have been shown in the readiness check and may take some time to resolve.

      Thank you,

      • Mahesh Sardesai
      Author's profile photo Hiroya Kita
      Hiroya Kita

      Thank you for your sharing.
      I check your blog post every each time a new version of the software is released.
      I have two question:
      1. in program "RC_COLLECT_ANALYSIS_DATA", there is "transaction Usage" check box.What changes when this is turned on and off?
      2. Which check in program "RC_COLLECT_ANALYSIS_DATA" is related to "Recommended Fiori Apps"?

      Author's profile photo Team SAP TCC SUPPORT
      Team SAP TCC SUPPORT

      Hello Mahesh Sardesai,
      Thank you for your blog.
      I have one question. We run the report SYCM_DOWNLOAD_REPOSITORY_INFO in our development system. Then we downloaded the ZIP file S4HMigrationRepositoryInfo<SID>.zip and uploaded it in the SAP Readiness Check 2.0 application (with the button Update Analysis), then the section "Custom Code Migration" is displayed as "In Preparation" but a few minutes later the text "No data" is displayed in this section. Do you have any idea why the section is not updated with the expected analysis ?
      Thank you for your help.

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi,
      It looks like there is a mismatch in the format due to some note being older version. The solutions to this type of issues have been to apply the latest version of notes. Check if any of the jobs is showing error. Resolve errors and rerun the job.

      Check that note releases are current or else you can create ticket.

      • Mahesh
      Author's profile photo Prabhu Reddy
      Prabhu Reddy

      Hi SAP Team,

      This is a helpful blog.

      I have a basic doubts on the Readiness checks for S/4 HANA Conversion 2020.

      1. What is the difference between /SDF/RC_START_CHECK and RC_COLLECT_ANALYSIS_DATA reports?
      2. What is the best option to run the /SDF/RC_START_CHECK in parallelism?

       

      Regards,

      Prabhu Reddy.

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi Prabhu,

      Report /SDF/RC_START_CHECK is for detailed simplification list and RC_COLLECT_ANALYSIS_DATA is for Readiness Check.

      I am not aware of parallelism in /SDF/RC_START_CHECK but if the report is taking longtime please try the methods suggested in opensap course Week1 Topic 3 towards the end -  https://open.sap.com/courses/s4h14-1/items/1xmyNDSayheuZCaKbWfW1q

      Author's profile photo Catalin Diaconu
      Catalin Diaconu

      Hello,

      does point 20 (Consistency Check) need to be run in the productive client also?

       

      Thanks,

      Catalin

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi Catalin,

      The report RC_COLLECT_ANALYSIS_DATA is recommended to be run in Productive client only.

      • Mahesh
      Author's profile photo Catalin Diaconu
      Catalin Diaconu

      Hi Mahesh,

      thank you for answering!

       

      I found after I asked my question, that in note 2913617 it mentions to run RC_COLLECT_ANALYSIS_DATA with the Simplification Item Consistency checkbox checked, in client 000 (point 5 from the Frequently Asked Questions? section). Or maybe I misread that.

       

      Regards,

      Catalin

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi Catalin,

      Yes. Good point for awareness. The note states that - SAP Readiness Check should be executed in the production system and must be run in the productive client, with the exception of the simplification item consistency check (Simplification Item Consistency checkbox). This ensures that all checks are executed properly.

      - Mahesh

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi Catalin,

      Just want to add that the checkmark for Simplification Item relevance can be selected while the job is run in productive client.

      When selecting checkmark down below for simplification item consistency, it has to be run in client 000 so that it runs the same way as in SUM tool.

      Author's profile photo Banjapally Satyanarayan
      Banjapally Satyanarayan

      Hi Mahesh,

      I run the RC_COLLECT_ANALYSIS_DATA with all options but getting error message in 'Business Partner'. If i removed tick on "Business Partner" option and run again then report is finish successfully. In readiness report, the business partner data is not coming.

      Author's profile photo Mahesh Sardesai
      Mahesh Sardesai
      Blog Post Author

      Hi Banjapally,

      Please check if the related notes have been applied. Also it depends on the error you are getting, so please create a ticket so support can login and take a look at the system.

      • Mahesh
      Author's profile photo Sanjay Rawat
      Sanjay Rawat

      Hi Mahesh Sardesai,, Awesome blog, very detailed. Would be keen to hear your take on SAP CRM (Ehp 4) to  S/4 HANA Conversion readiness check. I understand most of it is manual. Thanks!