- SAP Managed Tags:
This blog is for Conversion from ECC6 to S/4HANA - t4 of the conversion 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 but you can do the readiness check for S/4HANA upgrade between releases (not release support pack upgrade), although there is much less benefit for upgrade.
All steps are according to Note 2502552 - S4TC - SAP S/4HANA Conversion & Upgrade new Simplification Item Checks ver 76. Click on Show Changes for revisions,
Note 2399707 SAP Readiness Check - Simplification Item Check ver 133. Click on Show Changes for revisions and
Note 2187425 - Information about TCI as per attached TCI_for_Customer.pdf is only applicable if TCI has to be enabled for Netweaver SP level mentioned later.
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.
Note 2399707 SAP Readiness Check - Simplification Item Check ver 133. Click on Show Changes for revisions and
Note 2187425 - Information about TCI as per attached TCI_for_Customer.pdf is only applicable if TCI has to be enabled for Netweaver SP level mentioned later.
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 S4HCONV in Client 000 as copy of DDIC.
Enter tCode SPAM, check and apply SPAM 71 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 71, please check Note 2502552 for latest updates. Login to Client 000.
Enable TCI with preparation tasks as mentioned in Conversion Guide 3.6 Simplification Item-Check and described in document attached to SAP Note 2187425 - TCI_for_Customer.pdf.
Check your Basis Release in SPAM as below. Our Basis Release is 740 SP04.
All steps below can be executed in Client 000, this is where SUM tool will execute them during the conversion. Please note the steps below are executed for ECC systems with 1.3.2 SAP_Basis Release 731 and above.
Apply notes 2536585, 2606986, 2615270, 2569813 (manual steps), (ignore any note if it cannot be implemented)
Then for Download Bootstrap TCI – apply notes 2344014 and 2134534 (Since the SP level was less than 740 SP16 as shown in table in 1.3 of TCI_for_Customers.pdf these were needed to be applied otherwise they may show as Cannot be Implemented).
Open Note 1995550 in internet browser, It is not necessary at this stage to download note in SNOTE but it may show as Cannot be implemented and we will see this change this later on to Can be Implemented.
Please download K74000FCPSAPBASIS.SAR package to be applied through SPAM as below. The 3 digits 740 correspond to the basis component in SPAM.
In SPAM choose Menu: Support Package => Load Packages => From Front End, Choose file K74000FCPSAPBASIS.SAR
Then choose Directory: New Support Packages and Click on button Display, select (1) SAPK74000FCPSAPBASIS, (2) Calculate Queue (3) Ok, answer Yes to add modification transport to Queue, and Back (F3)
Menu: Support Package => Import Queue
TIP: It may be convenient to start in Dialog Mode as by selecting Start options.
You may get dump LOAD_TYPEPOOL_VERSION_MISMATCH. Import Queue again.
If you go Menu: Support Package => Confirm you will get message that "The TCI queue must be finished with the Note".
Now in tCode SNOTE, select note 1995550, download latest version of the note (again if you already downloaded before) and continue note application.
TIP: After clicking on "Download Latest version" if status is still "cannot be implemented", the trick here is to click button "Download SAP Note" for a fresh download.
Continue and apply note.
TIP: When prompted for the file SAPK74000FCPSAPBASIS.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. (already applied)
Apply Note 2408383 TCI - Enabling System for SAP Note Transport-Based Correction Instruction (TCI) Rollba...
You will get message that SAPK74000ICPSAPBASIS is not available, download form note 2408383 as below:
.
In SNOTE click the (F3) Back button and upload using option Upload TCI shown below
and then apply the note 2408383 to continue application. You will get dump with LOAD_PROGRAM_*_MISMATCH, enter SNOTE again and 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 informati...
Apply note according to your release - Note 2761703 - SAP S/4HANA 1909 SP00 Conversion & Upgrade - TCI Note #8
When applying the note you may get message “The transport based correction SAPK61700BCPSAPAPP of SAP note is not available”,
download from note as below.
You also need to go to ECC-DIMP 617-617
and download K617005CPECCDIMP.SAR
TIP: If you have ECC-DIMP 600 then upload corresponding file which is K600005CPECCDIMP.SAR
In SNOTE click the (F3) Back button and upload using option Upload TCI shown below and then apply the note 2617167.
De-Implement SAP note 2502552 (if already implemented). Download and implement via SNOTE SAP Note 2761703 - SAP S/4HANA 1909 SP00 Conversion & Upgrade - TCI Note #8 and then implement SAP note 2502552 in the next step.
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 - S4/HANA 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 1909 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 in Quality and Production. please use the other 2 buttons shown in yellow 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 JobName RUN_S4H_SIF_CHECK_INIT and in preprocessing phase RUN_S4H_SIF_CHECK_EXEC it has a different job name as /SDF/RC_START_CHECK 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
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.
(A) RELEVANCE CHECK:
Relevance check shows items that are relevant based on your source system like here it is ECC6/EHP6. The Yellow triangle means its probably relevant and down below there are green tick marks which mean the item is not relevant.
Above list has 645 Simplification Items. Out of these 645 simplification items 180 with the yellow triangle are relevant for the EHP6=>S4H1909 conversion. Each of these 180 items have SAP Notes on the right hand side "Note" column. The team has to go through these 180 items for the project and completely ignore the 465 irrelevant items which are down below.
Now these 180 items are further split into the next step....
(B) CONSISTENCY CHECK - LAST CONSISTENCY:
Last Consistency column 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 STOP sign items are for Inconsistency at level abortion. These are complete show stoppers that need some action and cannot be exempted
RED items are for Inconsistency at level Error
Both above are mandatory simplification items to be fixed before S/4HANA upgrade/conversion.
YELLOW items are for Warning and
GREEN items are for No inconsistency,
(B) CONSISTENCY CHECK - EXEMPTION:
The purpose of the exemption is for you to confirm that you have read the note and checked out the implications before setting exemption.
Exemption status with X as Not applicable means that these items cannot be exempted. Simplification Items where exemption can be applied are shown with Yellow triangle.
The next step is to see individual Simplification Item detail log.
(C) DISPLAY CONSISTENCY CHECK LOG:
The Display Consistency Check log button is used to show the errors in more detail. Now let us discuss some them in more detail:
(1) SI22 - GENERIC_CHECKS You will most probably find these error in every check.
The solution is provided to run report RS4SIC_TNIW5CORR and points to note 1484142 - MRN1: Incorrect Customizing entries deleted for more information. Please run report using tCode SA38 - Client 000.
You will also have to run report RS4SIC_PSMTABCORR and this one points to note 2749796 - S4TC - Funds Management tables with illegal entries during S/4 system conversion Please run report using tCode SA38 - Client 000.
(2) SI2: MASTERDATA_BP You will find these as showstoppers with Return Code 12 if Customer Vendor Integration steps are not completed.
(D) DISPLAY EXEMPTION LOG:
This button shows 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.
(E) NOTES:
The Notes column shows the Note Number to refer to for the item that you can click and directly go to for information.
Experience shows that there are approx 150 items relevant for every project. The project team has to go through each of these but all of then don't stop the conversion. Each one will take time to resolve, so be patient.
Out of these about 10+ items will be of status Red and have to be resolved and cleared with elaborate steps for some of these so that SUM tool can do the conversion. I already showed you how to resolve one of them - SI22 - GENERIC_CHECKS.
TIP: In case you have resolved some of the simplification items it is not necessary to rerun the Simplification Item Check for the entire list again. This may take time for large databases. You have to run report /SDF/RC_TROUBLE_SHOOT for individual check in background. The Check Consistency Details button is detailed check mode with in-depth analysis for individual simplification item, has longer runtime.
PERFORMANCE CONSIDERATIONS:
The duration of the pre-check report /SDF/RC_START_CHECK background job is relative to the size of the database, nature of data, hardware, operating system & database used, and may take several hours for e.g. with MSEG table over 500 million records. The program is run again twice by SUM tool during conversion.
To reduce the runtime of report:
- Check database parameters & update database statistics
- Do performance evaluation using ST12 traces and create database indexes if necessary
Use the Notes below for guidance:
Note 2679566 – S/4HANA MM-IM data model conversion
Note 2678215 – Poor Performance in RUN_S4H_SIF_CHECK_INIT using Oracle DB
Note 2753888 – Increase Precheck performance: skip KALNR-check
Note 2646649 – Performance improvements of generated methods of class CLS4SIC_MM_IM_SI1
- If the job is taking too long, check with experienced DBA to identify the bottlenecks and then, if necessary, create OSS message for SAP using component MM-IM-GF-MIG
LANDSCAPE CONSIDERATIONS:
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 available but don't press button Update Catalog with latest version.
After the sandbox run, when you start with conversion of DEV system, please apply notes in DEV/QAS/PROD/PREPROD/TRAINING as applicable so that the notes are same across the landscape. If you do this later the older
SOLUTIONS:
Please refer
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
REFERENCES:
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.
S/4HANA 1909 Conversion Guide
SAP S/4HANA 1909 System Conversion Steps & Details – How to be prepared
Hope you enjoyed the blog !
Mahesh Sardesai
Product Expert – S/4HANA
Brought to you by the SAP S/4HANA Regional Implementation Group
1 Comment
