SAP S/4HANA Readiness Check for System Conversion

Step 1: Preparation

1.1 SAP Readiness Check for SAP S/4HANA – 2913617 (current version 39)

To run SAP Readiness Check for SAP S/4HANA, data collectors are required to gather statistical data and a limited set of configuration data from your system. To install the data collection framework and the associated collectors, implement the SAP Notes that are listed in the Implementation of Data Collectors

Step 2: Readiness check framework

2.1 Using transaction code SNOTE implement 2758146 – SAP Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendations

STEP 3: Enable Simplification Item Relevance Check & Compatibility Scope Analysis

3.1 Using transaction code SNOTE implement 2399707 – Simplification Item Check

3.2 Compatibility Scope Analysis in SAP readiness check – https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/compatibility-scope-analysis-in-sap-readiness-check-an-evolution-of-the/ba-p/13519365

STEP 4: Enable Effort Drivers of Simplification Items

4.1 Using transaction code SNOTE implement 2903677 – SAP Readiness Check: Effort Drivers of Simplification Items Check

STEP 5: (Optional) Enable Consistency Check

5.1 Using transaction code SNOTE implement 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks

There is a simplified process to apply this note. It may require more notes to be downloaded and some Transport based Correction Instructions. 

STEP 6: Enable S/4 HANA Sizing Analysis

6.1 Analyze 1872170 – ABAP on HANA sizing report (S/4HANA, Suite on HANA…)

6.2 Using transaction code SNOTE implement 3104284 – HANA memory Sizing report – Advanced correction 15.

While applying this note you may be requested to apply notes SAP Note 2987346 – HANA memory Sizing report – Advanced correction 14 and  Note 2810633 – HANA memory Sizing report – Advanced correction 13 + dependent notes.

NOTE: 

• Minimum requirements ST-PI 740/SP02-12 or 700,710/SP12-22 to apply the note.
• 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.

NOTE: You could save lot of manual work by applying ST-PI. To apply it doesn’t need any other components or stack.xml. If you don’t want to apply ST-PI, please note that 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 or 700,710/SP17

In tcode SE38, check that program /SDF/HDB_SIZING is available and you can even run it for test now as the job normally takes long time.

STEP 7: Enable Data Volume Management Analysis

7.1 Analyze Note 2721530 – FAQ for collecting DVM data during S/4HANA Readiness Check.

Implementation of the note requires ST-PI 740 SP01 700/710 SP09

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

1. TCODE SA38, RTCCTOOL, Click on Settings, Flag option ‘Prepare for DVM (Data Volume 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.
2. Apply Note 2612179 using SNOTE. You may be prompted for manual steps below:

As indicated in the manual activity, please follow the below sequence.

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

    3. TCode SA38, RTCCTOOL – check other DVM notes required on the system

STEP 8: Enable Financial Data Quality Analysis

8.1 2972792 – Financial Data Quality: Trigger Data Collection Reports to Check Your Financial Data. 

More information on – https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/sap-readiness-check-for-sap-s-4hana-what-s-new-in-november-2020/ba-p/13477214

Manual activities – Enter tCode SA38 – program name /SDF/NOTE_2909538, Update and Activate.

There are also some steps below before implementing note 2972792:

1. Ensure Make sure that the SAP Note 2758146 is implemented
2. Implement the FIN_CORR_RECONCILE report via SAP Note 2755360
3. Refer to this SAP Note 2887318 and implement the included SAP notes if required.

Please ensure Online collectors are active – Enter tCode SA38 – RTCCTOOL, Goto->Online colllectors; Allow Online Collectors.

STEP 9: Enable Customer Vendor Integration Analysis

9.1 Using transaction code SNOTE implement 3010669 – Enhancements to SAP Readiness Check Dashboard for Business Partner/CVI There are manual steps – in SE24 change Object type CL_CVI_READINESS_CHECK and Goto-> Text elements and add Sym 015-025. There are some dependent notes – may prompt to apply Note 2811183 – S/4 Readiness Check Development.

Manual activities need to perform under this note:

STEP 10: Enable Integration Analysis

More details on https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/new-customer-vendor-integration-analysis-cvia-check-in-sap-readiness-check/ba-p/13505506

1.  Analyze and Follow – 3061414 – Enabling extended integration impact analysis for SAP Readiness Check.
2.  Please update ad-on ST-A/PI to 01U* SP03+. For this you may have to apply the addons below using TCode SAINT as below shown for Basis 731 and higher. You should also be on min SAP_BASIS 7.00 SP0+, SAP_BASIS 7.02 SP15+, SAP_BASIS 731 SP12+, SAP_BASIS 740 or above.
3.  Using transaction code SNOTE implement 3035012 – ATC check for ALE objects for SAP S/4HANA simplification. Implement SAP Note 3057501 and SAP Note 2781766 in central ABAP test cockpit system (not ERP). More info. on (https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/extended-integration-analysis-in-sap-readiness-check-is-now-live/ba-p/13503076)

STEP 11: Enable Business Process Discovery Analysis

•  Using transaction code SNOTE implement 2745851 – Business Process Improvement Content for SAP Readiness Check 2.0 and Next Generation ….

STEP 12: (Optional) Enable Innovation Potential Dashboard Results

• Using transaction code SNOTE implement 2827612 Enable Innovation Potential check in SAP Readiness Check for SAP S/4HANA.

STEP 13: Enable Custom Code Analysis

• Using transaction code SNOTE implement 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

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.

STEP 13A: (Optional) Improve Performance of Job SAPRSEUC

13.1A Using transaction code SNOTE implement 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:

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 14: Enable Custom Code Analysis via ABAP Test Cockpit

14.1 Using transaction code SNOTE implement 2781766 – Enabling ATC check result export for SAP Readiness Check 2.0

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.

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

STEP 15: Run Background Job in DEV System to Download Metadata Info

15.1 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:

Refer Note: 2655768 – Custom Code Analyzer – The where-used list index for customer objects is not up to d…

STEP 16:  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…

Incase of dump

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 must Rerun the job from the beginning.

STEP 17: Transport 13+ Notes to Production

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

STEP 18: Update Simplification Item Catalog

18.1 Using TCode SA38 program /SDF/RC_START_CHECK, check that your (1) Target S/4HANA Version shows up in the popup as below. If it doesn’t show, then click on (2) Update Catalog with latest version from SAP and you should see message (3) Simplification content downloaded successfully from SAP.

Note: If above did not work, you can manually download the file in SAP Portal.

https://launchpad.support.sap.com/#sic, and upload using Upload Simplification Item Catalog file.

STEP 19: Run Background Job in Prod System

19.1 In the productive client, tCode SE38 – RC_COLLECT_ANALYSIS_DATA (1) select target S/4HANA Version, (2) Schedule Analysis, (3) Immediate and (4) ok. As per the note 2913617, 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 the needed ST-A/PI through SPAM.

STEP 20: 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.

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… 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 raise… and run the job again.

STEP 21: Generate Readiness Check Results Dashboard

21.1 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.

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.