Upgrade to S/4HANA 1809FPS0 – t3 – Simplification Item Check
This blog is for Upgrade of S/4HANA – t3 of the Prepare Phase mandatory steps to be done in sequence below. Simplification Item Catalog is a tool that allows you to search or browse the complete collection of simplification items online. Each simplification item details the steps that need to be taken for the conversion and/or the upgrade from a business and a technical point of view, both preparatory and follow-on steps and each item is available as a SAP Note. This is a mandatory step and will be triggered by SUM tool. We will focus on Sandbox type system with co-deployed (embedded) gateway.
Readiness Check (RC) is relevant to Conversion to S/4HANA and will be discussed in Conversion blogs.
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|
||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|
All steps are according to Note 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks ver 60. Click on Show Changes for revisions,
Note 2399707 SAP Readiness Check – Simplification Item Check ver 113. Click on Show Changes for revisions and
If you are using older system copy, update data using SAP Note 2568736 – SAP Readiness Check for SAP S/4HANA – copy ST03N data. Please note the Simplification Item Check is only applicable to S/4HANA BackEnd system, not applicable to the FrontEnd Central Hub.
STEP 1: CREATE USER AND APPLY SPAM
Create user S4HUPGR in Client 000 as copy of DDIC.
Enter tCode SPAM, check and apply SPAM 69 or higher. Latest version is highly recommended.
STEP 2: ENABLE TRANSPORT BASED CORRECTIONS IMPLEMENTATION (TCI)
To be done in every system DEV QAS PROD as of SPAM 70, please check Note 2502552 for latest updates. Login to Client 000.
Enable Transport based Corrections Implementation (TCI) with preparation tasks as mentioned in Upgrade Guide 3.3 Simplification Item-Check and described in document attached to SAP Note2187425 – TCI_for_Customer.pdf.
Check your Basis Release in SPAM as below. Our Basis Release is 751 SP01.
All steps below can be executed in Client 000, this is where SUM tool will execute them 2 times during the upgrade in phases.
Apply notes 2536585, 2606986, 2615270, 2569813(manual steps), (ignore any note if it cannot be applied)
Then for Download Bootstrap TCI – apply notes 2344014 and 2134534 (ignored as could not be implemented).
Apply Note 1995550, As you apply the note you will get message that K751001CPSAPBASIS.SAR of is not available. The 3 digits 751 correspond to the basis component in SPAM as below.
Download from note as below
In SNOTE click the (F3) Back button and upload using option Upload TCI shown below and then select file K751001CPSAPBASIS.SAR click on Decompress.
After this select Note 1995550 and continue application in SNOTE.
TIP: When prompted for the file K751001CPSAPBASIS.SAR instead of looking for it through note, it is also available with direct search in Software Download as below but don't forget to read the note.
STEP 3: ENABLE TCI ROLLBACK
Enable TCI Rollback. This step is transportable as mentioned in Note 2502552.
Login to Client 000. In step 2 we already applied notes 2536585, 2606986, 2615270.
Apply Note 2408383 TCI – Enabling System for SAP Note Transport-Based Correction Instruction (TCI) Rollback
You will get message that SAPK751002CPSAPBASIS.SAR is not available, download from note 2408383.
In SNOTE click the (F3) Back button and upload using option Upload TCI shown below and then select Note 2408383, then click on Decompress and continue application. You will get dump with LOAD_PROGRAM_*_MISMATCH, enter SNOTE again to continue note application.
Apply Note 2643757- TCI – Handling of Messages and Note status during TCI processing
STEP 4: IMPLEMENT OTHER NOTES
Apply Note 2499199 TCI – Remove unnecessary Note downloads and exclude unwanted delivery event information during equivalence calc
Apply note 2617167 S4TC – SAP S/4HANA 1809 SP00 Conversion & Upgrade – TCI Note
When applying the note you may get message “The transport based correction SAPK101008CPS4CORE of SAP note is not available”, The 3 digits 101 correspond to the S4CORE component in SPAM as below.
Download from note as below:
In SNOTE click the (F3) Back button and upload using option Upload TCI shown below Click on Decompress and then apply the note as before.
STEP 5: APPLY THE TWO MAIN NOTES
Apply SAP Note 2399707 SAP Readiness Check – Simplification Item Check which delivers new check report and SAP Note 2502552 S4TC – S/4HANA Conversion & Upgrade new Simplification Item which delivers the check classes via transport-based correction instructions (TCI) and prerequisite notes.
STEP 6: EXECUTE REPORT
Enter tCode SA38 => /SDF/RC_START_CHECK
It is better to run the job in background mode as it takes time. The screen is explained below:
(1) Both Notes should be marked green with Latest version, (2) select the correct target version S/4HANA 1809 from list, (3) Update Catalog with latest version (4) You will get message Simplification Item Content is downloaded successfully from SAP,(5) Local version changes to current date. (6) to select New check as background and (7) Execute.
TIP: After successful conversion it is recommended to freeze the simplification catalogs for subsequent conversions in the landscape shown in yellow to Quality and Production. please use the other 2 buttons shown for (1) download current/ (2) upload from file the Simplification Item Catalog.
You will get message the job is scheduled and to check job in tCode SM37. This job can run long depending on the system.
Please note when the above same job is scheduled by the SUM tool 2 times later on in extraction phase different JobName RUN_S4H_SIF_CHECK_INIT and in preprocessing phase different JobName RUN_S4H_SIF_CHECK_EXEC with log file /usr/sap/SID/SUM/abap/tmp/S4_SIF_TRANSITION_CHECKS.SID.
You can click on Job log icon to view log.
STEP 7: VIEW SIMPLIFICATION ITEM CHECK RESULTS
The next step is to view the Simplification Item Check results.
Enter tCode SA38 => /SDF/RC_START_CHECK
Select target system (1) SAP S/4HANA 1809 [Initial Shipment Stack], select (2) Display Check Result and click on (3) Execute.
(1) Relevancy shows items that are relevant for the source system you are running the check like here it is S/4HANA 1610 FPS1. The Yellow triangle means its probably relevant and green tick mark means it is not relevant.
(2) Status column is Released
(3) Last Consistency Result shows if there are data inconsistencies when system is migrated to new data structures that could cause conversion to fail, so you are aware to correct or exempt them before actual conversion starts. Red is for Inconsistency at level Error – these are mandatory to be fixed before upgrade/conversion. Yellow is for Warning and Green is for No inconsistency, the ones with X are Not applicable.
(4) Exemption shows items that have errors can be exempted.
Notes column shows the Note Number to refer to for the item that you can click and directly go to for information.
The first line points to SAP Note 2618018 – S4TWL – Generic Check for SAP S/4HANA Conversion and Upgrade
The next step is to see individual Simplification Item detail log.
(5) Display Consistency Log to show the error in more detail
Note the above error is in SI22 – GENERIC_CHECKS. The solution is provided to run report RS4SIC_TNIW5CORR and points to note 1484142 – MRN1: Incorrect Customizing entries deleted for more information. Please run the report in SA38 – Client 000.
(6) Display Exemption Log to show the exemptions applied. (a) Messages with return code 7 will block system conversion, so action is required. You may be able to set exemption for the error and get through. (b) Messages with return codes 8 or 12 will block system conversion and need detailed application specific knowledge to resolve and you may have to refer to the note/open OSS message to get them resolved.
Experience shows that there are 20+ items relevant. Each one will take time to resolve, so be patient.
After successful conversion it is recommended to freeze the simplification catalogs for subsequent conversions in the landscape for Quality and Production. please use the 2 buttons shown in yellow for (1) Download Current Simplification Item Catalog (2) Upload Simplification Item Catalog from file. You may have newer version of notes 2399707 and 2502552 but don’t Update Catalog with latest version.
Note 2245333 – Pre-Transition Checks for FIN: Error Messages and Possible Solutions
Note 2618023 – Migration Preparatory Checks for FI-AA: Error Messages and Possible Solutions
Note 2679566 – S/4HANA MM-IM data model conversion
SAP S/4HANA Simplification Item Check – How to do it right <== updated regularly
Conversion to SAP S/4HANA- Consistency checks in Finance: Part 1
Note 2399707 – Simplification Item Check
Simplification Item Catalog
Simplification List <==This is over 1000 pages pdf where you may find some details.
Upgrading SAP S/4HANA AnyPremise – How, Why, and Best Practices guide now available !
Hope you have enjoyed the blog.
Product Expert – S/4HANA
Brought to you by the SAP S/4HANA Regional Implementation Group
Thanks for your blogs. It helps to check the system before upgrade to 1909.
Now I’m able to test the simplification list in DEV. But unable to transport into QA, getting dump in the SPAM program.
While doing R& D got to know last month business people by mistake implement supporting sap note(nearly 250 notes) which was not relevant. within this list, some of the notes( as per your suggestion) already there. Due to this mistake system getting dump while running Tcode – SPAM or getting status of the system in QA.
What are the next step should I follow? or is it required to restore QA?
The SI notes clearly state that old notes have to be de-implemented before new notes as SNOTE procedure is easy but cannot perfectly handle the update to old notes. For this customers de-implement the notes in dev and send a transport only for de-implementation across the landscape. And then implement the new notes.
The dump has to be analysed for resolving the issue. The information provided here is insufficient. I would open OSS message for assistance. They may suggest to update SPAM.
If not much work has been done and its faster to restore, it is worth it, but there may be possibility you run into same situation again so some effort to mitigate existing situation is worth it as it would provide knowledge into the current issue.