Skip to Content

This blog is for Conversion from ECC6/EHP7 to S/4HANA 1809FPS0t3 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 and will be discussed in Conversion blogs.

Please find other blogs as follows:


NEW INSTALLATION PART 1 – MP          PART 2 –  Installation
PART 3 –  BP Activation
S/4HANA 1809 FPS0    link link link
S/4HANA 1709 FPS2            link link link -US   link -DE
S/4HANA 1709 FPS1  link link link -US   link -DE
S/4HANA 1709 FPS0    link link link -US   link -DE
S/4HANA 1610 FPS2  link link link -US   link -DE
S/4HANA 1610 FPS1 link -US   link -DE
S/4HANA 1610 FPS0 link link link -US   link -DE
S/4HANA 1511 FPS2/1   link FPS2/link FPS1
S/4HANA UPGRADE   t2 – MP t3 – SIC
t4 – CCM t5 – SUM
S/4HANA 1809 FPS0              link link link link
SYSTEM CONVERSION t2 –  RC     t3 – MP      t4 – SIC      
t5 – CCM      t6 – SUM       
S/4HANA 1809 FPS0  link link link link EHP7/hdb
S/4HANA 1610 FPS0         link link link
S/4HANA 1709 FPS1 link link
OUTPUT MANAGEMENT     link  link  link link

Given the numerous notes and corrections to be applied, you may like to try this in sandbox first. If its 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 S4HCONV in Client 000 as copy of DDIC.
Enter tCode SPAM, check and apply SPAM 69 or higher. Latest version is highly recommended.

STEP 2: 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 Conversion Guide 3.6 Simplification Item-Check and described in document attached to SAP Note2187425TCI_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 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. 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) Rollback

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: Apply Note 2499199 TCI – Remove unnecessary Note downloads and exclude unwanted

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

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 5: Enter tCode SA38  =>  /SDF/RC_START_CHEC

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 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 6: 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 based on your source system like here it is ECC6/EHP6. 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(3) 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.

Normally for Conversion it is expected that there are 60+ items above and each one takes its own time to resolve.

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 – S4HANA MM-IM data model conversion

REFERENCES: – Excellent blog for understanding the finer details that is updated regularly
Note 2399707 – Simplification Item Check
Simplification Item Catalog
Simplification List                <==This is over 1000 pages pdf where you may find some details.

S/4HANA 1809 Conversion Guide

Hope you enjoyed the blog !

Mahesh Sardesai
Product Expert – S/4HANA

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply