Skip to Content
Technical Articles

Upgrade to SAP S/4HANA 2020 – time to change

Last Changed: 15th of October 2020

Upgrade to SAP S/4HANA 2020 – time to change

What is SAP S/4HANA?

SAP S/4HANA is an intelligent, integrated ERP system that runs on our in-memory database, SAP HANA.

Ha, ha, ha just kidding but the slogan comes straight from the SAP Website. Nevertheless this Article concentrates on the Upgrade to the latest Version of our Flagship Application S/4 which is (still) the core of all our integrated software applications.

In case there is a mismatch in the naming Support Package Stack (SPS) and/or Feature Package Stack (FPS), please refer to the SAP Release Strategy


How S/4HANA fits into the Intelligent Enterprise

Note 2912919 – SAP S/4HANA FOUNDATION 2020: Release Information Note

Evolution and Details SAP S/4HANA Software Stack

White Paper – Upgrading SAP S/4HANA – How, Why, and Best Practices

as already introduced the S/4HANA software stack in the Blog – SAP S/4HANA 1709 SPS03 – back on the Mothership again … the are no really big changes in the base components.

SAP S/4HANA Software Stack Evolution

still, there is a difference to the SAP BW/4HANA software components stack as follows:


SAP BW/4HANA Software Stack Evolution

SAP Solution Manager and SAP Maintenance Planner

make sure your SAP S/4HANA system is updated in the SAP Solution Manager LMDB and transferred to the SAP Maintenance Planner.

In advance check before the technical Upgrade, if your installed Add-On’s are compatible with SAP S/4HANA. In this case: well, this Add-On cannot be uninstalled via SAINT …
Information on uninstallation of ABAP Add-Ons can be found in SAP Note 2011192

These Add-On’s can be removed with tx. SAINT before you start the SUM process
SAP Help – SAP Add-On Installation Tool

Note 2011192 – Uninstallation of ABAP add-ons
Note 2144806 – Uninstallation of UIAPFI70 100 and UIFSCM70 100 from the Product Version SAP Fiori 1.0 for the SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA
Note 2227939 – Deinstallation of SAP Cloud for Travel and Expense Add-Ons OTM_EXTR, ODTHCMER, ODTGEN, ODTFINCO, ODTFINCC, TEMODFI and DCFLPROC
Note 2256000 – Uninstallation of SAP Fiori UI Component: UI for Basis Applications
Note 2240359 – SAP S/4HANA: Always-Off Business Functions
Note 2771798 – S/4HANA readiness of Fiori Business Suite Add-Ons

for these UI Add-On’s there are successors available, so there is no need to remove them beforehand anymore, and the upgrade planning process can be continued and finalized in the SAP Maintenance Planner.


Plan Changes for SAP S/4HANA 1909 – Details 1


Plan Changes for SAP S/4HANA 1909 – Details 2

Plan Changes for SAP S/4HANA 1909 – Details 3


Plan Changes for SAP S/4HANA 1909 – Details 4

SAP S/4HANA – Simplification Item Check

the Report /SDF/RC_START_CHECK is explained in the Blog – Upgrade to SAP S/4HANA 1809 SPSx – the final frontier

If under some circumstances the SAP Note 2502552 cannot be implemented due to missing CI, try to download a SAP Note which contains e.g. S4CORE and implement this Note first. Then try to download the SAP Note 2502552 completely again. With that step all missing metadata which is necessary for the implementation will be downloaded. “s4core/19773”

SAP S/4HANA – Simplification Item Check

coming from lower SAP S/4 Releases, e.g. 1709 you might have to do more checks here …

Note 2858850 – Error in the Phase SUM PREP_EXTENSION/RUN_S4H_SIF_CHECK_INIT with the Job /SDF/RC_START_CHECK during SUM upgrade


details of Report /SDF/RC_START_CHECK

Note 2679118 – Simplification item check for duplicate output request entries
Note 2927227 – SI-Check – Renovation Task Management parameter in table S4SIC_PARAM
Note 2943919 – Simplification Item Check: Duplicates check for INOB

Report /SDF/RC_START_CHECK – solved

in addition: a little bit of SPAU/SPDD and and SPAM/SAINT (incl. Kernel) on my side …

Note 2944943 – Wrong Add-On conflict calculation in upgrades and S/4HANA conversions (execute Report RSSPAM_CORRECT_AVERS Version 4)

and hey: remember tx. SDDLAR to check the CDS consistency?

Note 2023690 – CDS views are inactive
Note 2536195 – Unable to upgrade to S/4HANA 1709

Blog: Let’s talk SAP S/4HANA AnyPremise Upgrade (Thanks to Yashith Hospet Manjunath)

New Check and Preparation Steps before SUM starts

actually before starting the SUM process, I came up with some issues which should be considered, even that I was in a very early stage of the SAP S/4HANA 2020 Upgrade.

SAP HANA 2.0 SP05 Update is necessary

the SAP SUM 2.0 SP09 Version usually checks explicitly the SAP HANA Version which is underlying  and for the Upgrade to SAP S/4HANA 2020 SP05 for SAP HANA 2.0 or higher is mandatory.

Note 2844322 – SAP HANA Platform 2.0 SPS 05 Release Note
Note 2955475 – SAP HANA 2 SPS05 Revision 052.00
Note 2968930 – SAP HANA 2 SPS05 Revision 053.00

Silent Data Migration (SDMI) – new functionality

Blog – Monitoring Silent Data Migration (SDM_MON) – S/4HANA 1909 upgrade/conversion

starting with SAP S/4HANA 1909 this new functionality is now present in the System and in every productive client. Despite the fact, that the SUM process takes care about the process, it is more than suitable to make yourself familiar with the Silent Data Migration Functionality, as it is not possible to deactivate or exclude this in further Upgrades.


Job RSUPGJOB stops for SDMI

In a Nutshell: from the Start Release SAP S/4 1909 onwards, you will need in every productive client a SDMI user with has the permission to execute the Report SAP_SDM_EXECUTOR_ONLINE_MIGR. the Report can be customized in tx. SJOBREPO individually in every client (default 15 min.) and it has at least to be executed once completely.



If this is not possible, you can run the Report R_SDM_ONLINE_EXEC to trigger the migration for a single class manually.



Note 2664638 – Create and assign SDMI User in a client
Note 2949148 – SDMI: Exclude obsolete client 066 from SDMI
Note 2850918 – Authorizations req. for Silent Data Migration (SDMI) in SAP S/4HANA Rel. 1909
Note 2821421 – SDM_USER: Allow creation without SAP_ALL profile
Note 2916801 – Silent Data Migration (SDMI) Configuration Options
Note 2943697 – Handling IN PROCESS class migration





check inconsistent ABAP managed HDI container

it is suitable to check the ABAP managed HDI container to prevent errors in Phase HANA_DEPLOY_UPG. Depending on your SAP S/4HANA Release, use either tx. SCTS_HTA_TOOLS or Report SCTS_HTA_ADMIN.

Note 2854985 – Check and repair inconsistent ABAP managed HDI container
Note 2906041 – Checks after phase MAIN_NEWBAS/HANA_DEPLOY_UPG were negative!



new system behaviour with SAP Enqueue Server 2 (ENSA 2.0)

during the complete SUM process in the Upgrade of SAP S/4HANA 20xx the new SAP Enqueue Server 2 (ENSA 2.0) influences the start/stop behaviour of the main ans shadow S4 Instance. make yourself familiar with the changes in the Default and Instance Profiles.

SAP Help – Configuration of the Enqueue Server 2
Note 2630416 – Support for Standalone Enqueue Server 2
Note 2754662 – SUM upgrade/Installation of S/4HANA fails due to Enqueue problem

using the latest SAP Kernel 7.81

as I’m doing the Upgrade to SAP S/4HANA 20xx in a very early stage, it showed that the latest SAP Kernel 7.81 help preventing errors in various Upgrade Phases, e.g. ENSA 2.0 usage and CDS handling. Currently 7.81/015 (5th of October 2020)


Starting the SUM Process


Please Note the following screenshots are already based on SUM 2.0 SP09, which is the minimum Version to upgrade/migrate to SAP S/4 2020. You will just see the most important screens, as several SUM 2.0 details are already shown in other various Blogs.

Note 2882379 – Central Note – Software Update Manager 2.0 SP09 [lmt_021]


SAP SUM 2.0 SP09 usage is mandatory

only available as Request/Pilot:


Note 2225630 – Executing and monitoring Zero Downtime Option of SUM for SAP Bus Suite
Note 2707753 – Executing and monitoring Zero Downtime Option of SUM for SAP S/4HANA

some of the checks are already explained before to continue the SAP Upgrade process here.

===  Title: Add-On Retrofit Information
Component BSNAGT moves to S4CORE 104
Component ECC-SE moves to S4COREOP 104
Component ERECRUIT moves to S4CORE 104
Component IS-H moves to S4CORE 104
Component IS-M moves to S4CORE 104
Component MDG_UX moves to MDG_APPL 805
Component MSGPMCON moves to INSURANCE 804
Component REVREC moves to S4CORE 104
Component REVRECSD moves to S4CORE 104



Note 2949944 – CHECK4NOTES_TOOL Type error: Missing SAP Notes for Tools

Note 2642660 – ZDO revoke capabilities for HANA Repository content
Note 2768794 – HTA for HDI: Error in locking/unlocking development environment
Note 2797905 – AMDP: Termination of CL_AMDP_RUNTIME_SERVICE after upgrade
Note 2854985 – Check and repair inconsistent ABAP managed HDI container
Note 2950218 – Enable creation of new shared workspace on new XSA server or SAP Web IDE

Note 2918366 – Issue with class CL_XCLA_FAAT_DOC_IT in a XCLA phase MAIN_NEWBAS/XPRAS_AIMMRG during an S/4HANA conversion
Note 2925002 – FM SUMO_RESOLVE_E071_OBJ: add handling of missing subobject types WAPP, SOTT, SOTU, HOTP, HOTO
Note 2941075 – Switch procedure: Adjustment for zero downtime upgrade
Note 2941394 – DDIC: onPrem upgrade to 2020, error for table SRF_REP_TYPE_DEF in PARDIST_SHD
Note 2840923 – SNOTE: Enable De-implementation of DDIC Correction Instructions
Note 2878284 – DDIC: table content not deleted from physical table pool
Note 2950218 – Enable creation of new shared workspace on new XSA server or SAP Web IDE
Note 2958954 – SNOTE: Note Implementation fails during ZDO Upgrade



only a few tables were affected here and it is not related to the SDMI functionality.
Note 2858832 – SAP HANA Native Storage Extension Functional Restrictions for SAP HANA Cloud


generated sql script for affected tables (NSE)

for the overall consistency of the SUM process this Phase can be ignored for now and proceed later. see also the Blog – Upgrade to SAP S/4HANA 1809 SPSx – the final frontier





Note 2318321 – Differences in SUM for the rescue of Non-SAP objects between load and delta procedure



Note 2408272 – Analyzing Results of Object Directory Entry and Software Component Check
Note 2215288 – ABAP Test Cockpit: Analyzing Objects Using Arbitrary Prefix Namespaces
Note 2464754 – SUM: RUN_RSUPG_TADIR_COMPONENT_CHECK phase “objects found without delivery transport”
Note 2915357 – UNKNOWN_COMPONENT_OBJECT for objects in package ASU1
Note 2910608 – Issue with applying changes to ‘TYPES’, ‘DATA’ or ‘CONSTANTS’ within ABAP Class definition







Note 2898700 – SAP S/4HANA 1909 upgrade stops with conflicting unique indexes on table /LTB/TR_HDR
Note 2950229 – Secondary index for database table /LTB/TR_HDR can’t be created after upgrade




last exit before execution Phase …




Phase Kernel KX_SWITCH



unfortunately in the Upgrade Phase HANA_DEPLOY_UPG there is not possibility at this time to skip or exclude Calculation Views, even it would be possible to repair them after the technical Upgrade.



Note 2789289 – Activation of Calculation View Fails with Error “column store error: [34011] Inconsistent calculation model”
Note 2810639 – ‘_SYS_BI’: the object name must not start with the reserved prefix ‘_SYS_’










Phase HANA_DEPLOY_UPG – continued


Phase XPRAS_AIMMRG – error

Always check the root cause for the XPRAS_AIMMRG interruption. Mostly the main errors already occurred during ACT_UPG and PARCONV Phases.
Note 2213074 – MESSAGE_TYPE_X in Program MANDT_UNIQUE_GET during Upgrade
Note 2529195 – Runtime error during conversion / upgrade to S/4HANA in phase XPRAS_AIMMRG
Note 2771607 – Error in SDOK_CONTREP_AFTER_IMP Table for document contents does not exist
Note 2890515 – SYNTAX ERROR in MAIN_NEWBAS/XPRAS_AIMMRG phase of upgrade
Note 2918366 – Issue with class CL_XCLA_FAAT_DOC_IT in a XCLA phase MAIN_NEWBAS/XPRAS_AIMMRG during an S/4 HANA conversion


Phase XPRAS_AIMMRG – continued


Phase UPCONF – End of SUM technical Downtime




Phase REQ_UP_FINAL – Postprocessing


Procedure finished – Your SUM procedure is complete


SAP S/4HANA 20xx – Post Activities

SAP S/4HANA 20xx – Installed Product Versions

  • tx. SPAU
  • tx. SDDLAR
  • tx. SNOTE

tx. SDDLAR – with SAP S/4HANA 2020


tx. SDDLAR – Repair Tools


tx. SDDLAR – 2

apply the latest SAP Corrections

due to the early stage of the availability there are no additional Support Packages available at this time. however for some components there are already corrections included in SP01 available
(app. 523 Notes applied … ;-)):

  • SAPK-60001INUIBAS001
  • SAPK-75501INSAPUI => available since 05.10.2020

for these components there are no corrections available at this time (05.10.2020):

  • SAPK-10501INS4CORE
  • SAPK-10501INS4FND


Roland Kramer, SAP Platform Architect for Analytics SAP SE



“I have no special talent, I am only passionately curious.”

You must be Logged on to comment or reply to a post.
  • (Maybe a stupid question, but then again, maybe not)

    Your post seems to imply that after S/4HANA 1909 (1909 as in release Year = 2019 + release Month = 09), the next release is S/4HANA 2020 (2020 as in release Year = 2020 ).

    Can someone confirm that? (Can I read up on that somewhere?)

    It would make a lot of sense to me!


      • Hi Jocelyn Dart ,

        thanks for the link and confirming again.

        As I said, the new naming (4-digit year) makes a lot of sense to me.
        But is that change of naming-logic actually explained somewhere?!

        I’d appreciate a blog “How SAP S/4HANA versions are named”, explicitly stating the change in login (as opposed to just using the new name without explanation).
        I have no direct benefit from it, I would just appreciate it and consider it good practice. Getting things (e.g. Names) right is hard, so resources helping with it are nice!

        I myself do make an effort to keep track of names, and using them right!


        • Hi Joachim, At this stage there are a just a scattering of early announcements out there. I expect there will be a more formal announcement by SAP S/4HANA leadership of the new naming closer to the general release date which is expected in early Q4 2020 on current planning.

  • Hi,


    Thank you for this article.

    Do you have any updates / news when the Simplification List and technical Prequisistes for S/4HANA 2020 will be avalable for the public ?



  • Hello Roland,

    Thanks for the detailed steps on the upgrade.

    Could you please let us know what is the minimum HANA database version would require for S4 2020 installation/upgrade? Although I know it is always recommended to go with latest version.

    Best regards,


    • Hello Mukesh Jain,

      whatever you want to do with SAP HANA, you should have at least 64GB Memory at least.

      In my case this is still a quite strong machine with 1TB RAM and 100 CPUs.

      As you can see the Memory usage, it is around 158 GB for a moderate loaded IDES SAP S/4 System. So you should have at least 128 GB, better 256 GB RAM as minimum. the CPU rate is automatically calculated with the RAM.

      Best Regards Roland