Upgrade to S/4HANA – t1 – Readiness Check
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||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0||fps2 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|
|SYSTEM CONVERSION||t2 – RC||t3 – MP||t4 – SIC
||t5 – CCM||t6 – SUM|
|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.
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: READINESS CHECK FRAMEWORK
Using tCode SNOTE apply Note 2758146 – SAP Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendations
STEP 3: ENABLE SIMPLIFICATION ITEM RELEVANCE CHECK & COMPATIBILITY SCOPE ANALYSIS
Please refer blog for Compatibility Scope Analysis for more details
Using tCode SNOTE apply Note 2399707 – Simplification Item Check
STEP 4: ENABLE EFFORT DRIVERS OF SIMPLIFICATION ITEMS
Please refer blog for for more details on Effort Drivers
Using tCode SNOTE apply Note 2903677 – SAP Readiness Check: Effort Drivers of Simplification Items Check
STEP 5: (OPTIONAL) ENABLE CONSISTENCY CHECK
Using tCode SNOTE apply Note 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks
There is an elaborate process to apply this note. It may require more notes to be downloaded and also some Transport based Correction Instructions.
Please refer the steps 1-5 in the Simplification Item Check blog – Upgrade to S/4HANA 1809FPS0 – t3 – Simplification Item Check
STEP 6: ENABLE INTEGRATION ANALYSIS
Please refer blog for Extended Integration Analysis for more details
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.
Using tCode SNOTE implement SAP Note 3035012 – ATC check for ALE objects for SAP S/4HANA simplification
STEP 7: (OPTIONAL) ENABLE INNOVATION POTENTIAL DASHBOARD RESULTS
STEP 8: ENABLE CUSTOM CODE ANALYSIS VIA ABAP TEST COCKPIT
Implement steps as shown in SAP Note 2781766 – Enabling ATC check result export for SAP Readiness Check 2.0
This step to be implemented in ATC system with NW 7.52. 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 download a file named <SID>_atc_findings.zip
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
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 11: TRANSPORT 7+ NOTES TO PRODUCTION
In tCode SE01, release transport and using tCode STMS import into QAS and PROD systems in the landscape.
STEP 12: UPDATE SIMPLIFICATION ITEM CATALOG
This is important if you want to run readiness check for the latest releases. Please refer blog for How to update RC to support latest release for more details
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.
STEP 13: RUN BACKGROUND JOB IN PROD SYSTEM
In the productive client, tCode SE38 – RC_COLLECT_ANALYSIS_DATA (1) select target S/4HANA Version, (2) Schedule Analysis, (3) Immediate and (4) ok.
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.
STEP 14: 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.
|TMW_RC_EFD_DATA_COLL||CA-TRS-PRCK||4||Effort Drivers of Simplification Items|
|TMW_RC_SITEM_DATA_COLL||CA-TRS-PRCK||5||Simplification Item Check|
STEP 15: GENERATE READINESS CHECK RESULTS DASHBOARD
In SAP Launchpad (S-USER is required) url (1) https://rc.cfapps.eu10.hana.ondemand.com
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.
There is no option available to create the Readiness Check 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.
Readiness Check Help Portal
SAP Note 2758146 – SAP Readiness Check for SAP S/4HANA & Process Discovery (evolution of SAP Business Scenario Recommendations) or SAP Innovation and Optimization Pathfinder
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.
Compatibility Scope Analysis – Compatibility Scope Analysis in SAP Readiness Check – An Evolution of the Simplification Items Check
Integration Analysis – Extended Integration Analysis in SAP Readiness Check Is Now Live
Effort Drivers – SAP Readiness Check for SAP S/4HANA – What’s New in November 2020
Thank you. Hope you enjoyed the blog !
Product Expert – S/4HANA
Brought to you by the SAP S/4HANA Regional Implementation Group