Skip to Content
Technical Articles

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

This blog is for the detailed steps for Readiness Check (RC) for step t2 of conversion to S/4HANA 1809FPS0 and is also valid for S/4HANA 1809FPS1. 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:

S/4HANA  SQUARE  ONE

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
SYSTEM CONVERSION t2 –  RC t3 – MP t4 – SIC
t5 – CCM t6 – SUM 
S/4HANA 1809 rc2  rc1 link link link EHP7/hdb
EHP6/db6
EHP5/ora
EHP6/mss
S/4HANA 1610 FPS0 link link link
S/4HANA ON-PREM APPLIANCE INSTALL USING MEDIA ACTIVATE FROM CAL
S/4HANA 1709 FPS1 link link
S/4HANA CLOUD      CPM  MASTER  CONTENT   EMAIL
OUTPUT MANAGEMENT link  link  link link

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

All steps are according to Note 2310438 – SAP Readiness Check for SAP S/4HANA – Managed System version 76. Click on Show Changes for revisions.

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

STEP 2: SETTING UP CUSTOM CODE ANALYSIS

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

This note downloads 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.

STEP 3: (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, Variant , Change add text elements as below. there are 7 programs and 1 class with text elements to be updated.

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.

STEP 4: COLLECTING HANA SIZING DATA

Apply Note 2504480 – Suite on HANA memory Sizing report – Advanced correction 9

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.

ST-PI is independent and doesn’t need other components or stack.xml to apply, this would save lot of manual work.

Also please apply Note 2734952 – HANA memory Sizing report – Advanced correction 12

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 TMW_RC_DOWNLOAD_ANALYSIS_DATA is run as per STEP 12.

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 2443236 – SAP Readiness Check for SAP S/4HANA Business Process Improvement Content.  This can be applied quickly. There are no Manual corrections

STEP 7: ENABLING DATA VOLUME MANAGEMENT ANALYSIS

Apply note 2612179 follow this sequence.

The note can be implemented for ST-PI 2008_1_700/710 SP09 to SP17 or 740 SP01 to SP07

As per manual instructions,

  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, check Note 1159758 -Data Volume Management: Central Preparation Note

STEP 8: SETTING UP READINESS CHECK

Apply Note 2310438 – SAP Readiness Check for SAP S/4HANA – Managed System

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

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

STEP 10:  MONITOR BACKGROUND JOB AND DOWNLOAD ZIP FILE

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.

STEP 11: TRANSPORT 6 NOTES TO PRODUCTION

STEP 12: RUN BACKGROUND JOB IN PROD SYSTEM

in tCode SE38 – TMW_RC_DOWNLOAD_ANALYSIS_DATA create variant as below:

(1) Select items and (2) Schedule Analysis. This will trigger number of background jobs as shown in next step.

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 13: MONITOR BACKGROUND JOB AND DOWNLOAD ZIP FILE

There are various jobs launched

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 TMW_RC_SITEM_DATA_COLL is scheduled to collect Simplification Item relevance check data

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

STEP 14: GENERATE READINESS CHECK RESULTS DASHBOARD

In SAP Launchpad (S-USER is required) url (1) https://launchpad.support.sap.com/#readiness
(2) Import Analysis, (3) SAP S/4HANA, (4) Enter Analysis name, (5) select TMW_RC_DOWNLOAD_ANALYSIS_DATA.zip and (6) select SYCM_DOWNLOAD_REPOSITORY_INFO.zip (7) click on Upload

You can view the Results Dashboard and if you need to download report, click on Create Results Document and the report will be available in word format. You can also download data in Excel file.

Above steps complete the readiness check.

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

STEP 14 (OPTIONAL): READINESS CHECK WITH SOLUTION MANAGER

Take this option when you have Solution Manager setup well, and you manage different systems in the landscape. Advantage here is that generally the notes are in sync.

  1. Apply Note 2290622 – SAP Readiness Check for SAP S/4HANA This note has elaborate steps.
  2. In tCode SA38 execute report AGSRC_START_ANALYSIS
  3. Enter the managed custom code client. Recommended to enter DEV system here
  4. Enter the analyzed system and client. Recommended to enter PRD system here.
  5. Enter eMail address of the user who should get the result of the analysis.
  6. Uncheck the selections that you dont need – Simplification Item Relevance, HANA Sizing, Transaction Usage, Business Process Analytics, Data Volume Management & Business Warehouse Extractor.

Once analysis is completed, a link to the result is set to the users whose e-Mail addresses you have entered.

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.

LANDSCAPE CONSIDERATIONS:

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.

It is recommended to have the same ST-PI across the landscape.

OTHER REFERENCES:

Readiness Check Help Portal
Readiness Chck User Guide
Note 2310438 – SAP Readiness Check for SAP S/4HANA – Managed System
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

 

 

1 Comment
You must be Logged on to comment or reply to a post.