Technical Articles
Upgrade to SAP S/4HANA 2020 – time to change
Last Changed: 25th of January 2023
Upgrade to SAP S/4HANA 2020 – time to change
Blog Content
-
- What is SAP S/4HANA?
- Evolution and Details SAP S/4HANA Software Stack
- SAP Solution Manager and SAP Maintenance Planner
- SAP S/4HANA – Simplification Item Check
- New Check and Preparation Steps before SUM starts
- Changes with ABAP 7.55 Platform
- Starting the SUM Process
- SAP S/4HANA 2020 – Post Activities
- SAP S/4HANA 2020 – What next …
What is SAP S/4HANA?
SAP S/4HANA is an intelligent, integrated ERP system that runs on our in-memory database, SAP HANA.
SAP S/4HANA is a future-ready enterprise resource planning (ERP) system with built-in intelligent technologies, including AI, machine learning, and advanced analytics. It transforms business processes with intelligent automation and runs on SAP HANA – a market-leading in-memory database that offers real-time processing speeds and a dramatically simplified data model.
Ha, ha, ha just kidding but these slogans come 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.
How S/4HANA fits into the Intelligent Enterprise
the SAP Data Value Formula
Evolution and Details SAP S/4HANA Software Stack
(my) Presentation – Upgrade S/4HANA Version 2020 -Basis View
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.
Blog – SAP Fiori deployment options and SAP Fiori front-end server strategy – UPDATE 2020
Document – SAP Fiori deployment options and system landscape recommendations
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
Important SAP Notes for SAP S/42020 – Overview
Note 2884313 – SAP S/4HANA 2020: Release Information
Note 2912919 – SAP S/4HANA FOUNDATION 2020: Release Information Note
Note 2912253 – SAP S/4HANA 2020 Feature Package Stack 00: Additional Release Information
Note 2943206 – SAP S/4HANA 2020: Restriction Note
Note 2977657 – CDS View Replication for SAP S/4HANA 2020 and following: Restriction note
Note 2924833 – SAP S/4HANA 2020 – app specific notes in system conversion / upgrade preparation phase
Note 2924845 – SAP S/4HANA 2020 – app specific notes in system conversion / upgrade follow-on phase
SAP Help – SAP S/4HANA 2020 Latest – What’s new Viewer
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 …
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 2214409 – SAP S/4HANA: Compatible Add-Ons
Note 2053132 – How to find the import conditions of a Support package or ADD-ON
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
Note 2980681 – SAP S/4HANA APL selections in maintenance planner
Note 3030010 – There are add-ons that are not compatible with target SAP S/4HANA 2020 while planning system in MP
Note 3049346 – “The Installation/Upgrade Package for Add-on RTLCAB rel. 500 is not available” in 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
- EA-HR608.SAR
- GBX01HR5605.SAR
- GBX01HR600.SAR
- SRA004600.SAR
- ST-PI740.SAR
- UIMDG001200.SAR
SAP S/4HANA – Simplification Item Check
Note 2399707 – Simplification Item Check
Note 3143951 – SAP S/4HANA 2022 Conversion & Upgrade checks – TCI Note #11
Note 3028788 – SAP S/4HANA 2021 Conversion & Upgrade checks – TCI Note #10
Note 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks
Note 3059197 – SAP Readiness Check for SAP S/4HANA upgrades
Note 3045936 – SNOTE: The system is currently updated using the Software Update Manager
the Report /SDF/RC_START_CHECK is explained in the Blog – Upgrade to SAP S/4HANA 1809 SPSx – the final frontier
Blog – Simplification Item Catalog, Simplification Item Check and SAP Readiness Check for SAP S/4HANA
SAP S/4HANA – Simplification Item Check – 07/2021
coming from lower SAP S/4 Releases, e.g. 1709 you might have to do more checks here …
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
Note 3057330 – Simplification Item SI28: CT_CHK_ITEM_DEVICE – Check for invalidated Output Devices
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)
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 3043459 – SAP HANA 2 SPS05 Revision 056.00
Note 3120845 – SAP HANA 2 SPS05 Revision 059.01
Note 3027730 – SAP HANA Client 2.8.16
Note 3063656 – SAP HANA Client 2.9.19
Note 3117481 – SAP HANA Client 2.10.20
furthermore the NSA HANA Functionality which was introduced with SAP HANA 2.0 SP04 is now by default in SAP HANA 2.0 SP05 and SAP S/4 2020 and reflected in the Upgrade by the SUM.
be careful with the usage of SAP HANA 2.0 SP06 and onwards. some new security measurements are now mandatory, like the SSL connection when connection to the SAP HANA Studio. This might interfere with the Connection between SUM and SAP HANA in general.
Note 2799997 – FAQ: SAP HANA Native Storage Extension (NSE)
Note 2927591 – SAP HANA Native Storage Extension 2.0 SPS 05 Functional Restrictions
Note 2983008 – Enable/Disable NSE (PAGE LOADABLE) for column tables of HANA statistics server
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.
tx. SJOBREPO
If this is not possible, you can run the Report R_SDM_ONLINE_EXEC to trigger the migration for a single class manually.
Report R_SDM_ONLINE_EXEC
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
tx. SDM_USER
tx. SDM_MON
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!
Note 2776773 – Inconsistencies found between HTA and HANA
tx. SCTS_HTA_TOOLS
Changes with ABAP 7.55 Platform
new system behavior 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 behavior of the main and 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 2020 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/116 (14th of April 2021)
new Client Copy Tool available
Blog – New Client Copy Tool
Note 2962811 – New Client Copy Tool: General Information
new Version of SAP_UI 7.55
please Note that the new delivered SAP_UI Version 7.55 is not anymore compatible with SAP NetWeaver Releases like 7.40 up to 7.51 anymore. SAP_UI 7.54 is the last Version supporting this lower Releases. you see this also in the Description of the Version of the SAP FES for S/4HANA.
new secure by default options SAP Basis 7.55
Blog – Secure By Default for SAP S/4HANA 2020
Blog – Secure By Default for SAP S/4HANA 2021
Starting the SUM Process
Always get the latest Version of the SUM from the SLT Main Page
Note 2882379 – Central Note – Software Update Manager 2.0 SP09 [lmt_021]
Note 3024369 – Central Note – Software Update Manager 2.0 SP12 [lmt_020]
SAP SUM 2.0 SP09 or higher 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
=== Phase: PREP_EXTENSION/EHP_INCLUSION
=== 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
Phase PREP_CONFIGURATION/CHECK4NOTES_TOOL
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 2953369 – Handling of Incorrect Adjustment Status of Note in SPDD
Note 2958954 – SNOTE: Note Implementation fails during ZDO Upgrade
Note 2980265 – Wrong message ‘All Changes Already Exist’ …
Note 2997543 – DD: DDL source could not be read – dependent activation of deleted DDLS
Note 2997792 – DD: Extend activation fails with “The component & does not exist or is not active”
Phase HDB_CHK_NSE_OLDPERSISTENCE
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
Phase RUN_RSUPG_TADIR_COMPONENT_CHECK
Report ZRSUPG_TADIR_COMPONENT_CHECK
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 2378526 – /IWFND/I_MED_SRH table index issue during system upgrade
Note 3056869 – Handling /IWFND/I_MED_SRH table index issue during system upgrade in HANA
Phase REPACHK1
Phase EU_IMPORT_ALL
Phase SHADOW_IMPORT_UPG2
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
Note 2890515 – SYNTAX ERROR in MAIN_NEWBAS/XPRAS_AIMMRG phase of upgrade
Phase DOWNCONF_DTTRANS
last exit before execution Phase …
Phase EU_SWITCH
Phase Kernel KX_SWITCH
MAIN_TRANSEXEC/ACT_TRANS – error with FPS02 and IS-OIL
Phase PARCONV_UPG
Phase HANA_DEPLOY_UPG
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_’
tx. SCTS_HTA_TOOLS
Report SCTS_HOTA_ORGANIZER/tx. SCTS_HTA_DEPLOY
tx. SCTS_HTA_DEPLOY – 2
tx. SCTS_HTA_DEPLOY – 3
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
Note 2769345 – “No field was selected from com structure” occurs during the ERP upgrade
Note 2986755 – Activation of BC Set end up in recursion when there are follow on BC Sets
Note 2773484 – SUM Checks After Phase MAIN_NEWBAS/XPRAS_AIMMRG were Negative – Error in Parallel XCLA “CL_XCLA_ACDOCA” Execution
Note 3071284 – CL_XCLA_FAAT_DOC_IT upgrade job cancellation due to timeout
Phase XPRAS_AIMMRG – continued
Phase UPCONF – End of SUM technical Downtime
Phase SPAUINFO
Phase REQ_UP_FINAL – Postprocessing
Procedure finished – Your SUM procedure is complete
SAP S/4HANA 2020 – Post Activities
SAP S/4HANA 2020 – Update 07.2021
SAP S/4HANA 2020 – Update 11.2021
- tx. SPAU
- tx. SDDLAR
- tx. SCTS_HTA_TOOLS
- tx. SNOTE
tx. SDDLAR – with SAP S/4HANA 2020
Note 3063842 – Supplier Evaluation by Quantity – Evaluate suppliers on partial delivery
tx. SDDLAR – Repair Tools
tx. SCTS_HTA_TOOLS
apply the latest SAP Corrections in advance
Blog – Note Analyzer – Revamp 2021
Note 2912253 – SAP S/4HANA 2020 Feature Package Stack 00: Additional Release Information
Note 3019642 – SAP S/4HANA 2020 Feature Package Stack 02: Additional Release Information
Note 3113354 – SAP S/4HANA 2020 SP Stack 03 – Release & Information Note
Note 2912919 – SAP S/4HANA FOUNDATION 2020: Release Information Note
Note 2935911 – SAP FIORI FOR SAP S/4HANA 2020: Release Information Note
Check for corrections of the main/core components after FPS03 or higher:
- SAPK-60003INUIBAS001
- SAPK-75503INSAPBASIS
- SAPK-75503INSAPBW
- SAPK-75503INSAPGWFND
- SAPK-75503INSAPUI
- SAPK-75F03INSAPABA
- ST-A/PI 01U_731
- SAPK-10503INS4CORE
- SAPK-10503INS4COREOP
- SAPK-10503INS4FND
- SAPK-80503INMDGFND
- SAPK-80503INMDGAPPL
check the DDIC/DDL consistency
Blog – A new generation of CDS views: CDS view entities (new with ABAP 7.55)
Blog – CDS View Entity
Blog – Analytics in S4HANA real shape
Blog – How To Integrate SAP Data Intelligence and SAP S/4HANA AnyPremise
Blog – Hello World: CDS View – SAP S/4HANA On Premise 2022
Note 2023690 – CDS views are inactive
Note 2421686 – CDS view(DDL SQL View) cannot be activated with RUTDDLSACT
Note 2577424 – EU_INIT customer objects, modified or enhanced objects are missing
Note 3109997 – DDLS Where-Used: No deletion of DDLS index for SAPRSEUC
report SAPRSEUC
Note 2581518 – Jobs in the Technical Job Repository (SJOBREPO)
Note 2833335 – DDLS object missing in the where-used result list
report SDDIC_DDLS_INDEX_ALL_SOURCES
Note 2992214 – Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 2020
Note 2902786 – Upgrade to HANA View based Info providers in Analytics and CDS views for 1909
Note 2952620 – Upgrade to CDS View based Info Provider for CV_EMPLOYEE HANA view
map CV_EMPLOYEE with IMPWFPERSON
SAP S/4 2020 – What next?
A good start for technical post activities is the SAP S/4HANA SQUARE ONE series from Mahesh Sardesai
Before S/4 2020 is after S/4 2020, as SAP S/4 2021 already available and SAP S/4 2022 underway
Blog – SAP Fiori for SAP S/4HANA – Foundational SAP Notes for SAP S/4HANA 2021
Blog – SAP Fiori for SAP S/4HANA – Foundational SAP Notes for SAP S/4HANA 2022
SAP S/4HANA Software Stack Evolution 2021
SAP BW/4HANA Software Stack Evolution 2021
SAP BW/4 2021 is based (finally) on the same ABAP Stack as S/4 2021 and also the main Add-On’s will be available with the first Support Package for SAP BW/4 2021
- SAP BPC 12.0
- SAP BCS/4 3.0
See more Details in the Blog – SAP BW/4 HANA 2021 – 3rd Generation in Sync with SAP S/4
Note 2289865 – Configuration steps for SAP S/4HANA Analytics
Note 2626107 – How to execute task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT
Note 2712785 – Fiori Setup: Initial Setup for Fiori Applications S/4
Note 2729492 – Configuring notifications in Fiori Launchpad and known restrictions
Note 2947824 – Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2020
Note 3045635 – Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2020 FPS02
Blog – SAP ILM based on SAP IQ Database
configuring the SAP ILM Functionality based on SAP IQ Database in S/4 2020
Roland Kramer, SAP Platform Architect for Analytics SAP SE
@RolandKramer
“I have no special talent, I am only passionately curious.”
love your motto 😉
Waiting for the next document update.. way to go.. ????
Thanks Roland! Very useful. I have tweeted this out to my network as well
Kind rgds
Jocelyn
(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!
Thanks
Joachim
Hi Joachim, That is correct and has already been officially confirmed elsewhere, e.g.
SAP Fiori deployment options and SAP Fiori front-end server strategy – UPDATE 2020
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!
best
Joachim
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 ?
Thanks
Hi Said, Usually the Simplification List and technical prerequisites are made available a few days before the new release becomes officially available. Customers who sign up to be part of the Guided Beta program for the new release get early access to these details a couple of months beforehand. SAP S/4HANA 2020 is currently expected in early Q4 2020.
Check Carola's blog above including the diagrams for a few insights. These have already been confirmed for SAP S/4HANA 2020:
You can also find this announced on the SAPUI5 Versions Maintenance Status page
Hello Jocelyn Dart,
Upgrade finished and Blog updated ... 😉
Best Regards Roland
Great news! Thanks Roland
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,
Mukesh
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
Thanks Roland!
I could see in screenshot that HANA database version is 2.00.048 that means S4 2020 will be supported on HANA version 2.0 SPS4 and customer no need to go for 2.0 SPS5, Is my understanding correct?
Best regards,
Mukesh
Hello Mukesh Jain,
probably If you read one of the countless Documents or SAP Notes you will find this Information. Currently there are Issues with SAP HANA 2.0 SP05 and ES despite if you are using SAP S/4 or any other SAP HANA based SAP Application, see - https://twitter.com/JensGleichmann/status/1302968105946230785?s=20
best regards Roland
According https://launchpad.support.sap.com/#/notes/2912253 for S/4 HANA 2020 FP00:
The minimum required revision of SAP HANA 2.0 is Support Package 05 Revision 50. SAP generally recommends customers to implement the highest SAP HANA 2.0 revision available.
Thanks a lot for this blog! This is very helpful information.
To check PAM before upgrade to S/4 HANA 2020 to prevent bad surprises is advisable.
One example: actually S/4HANA 2020 seems to be not supported with RHEL 7 any more (in contrast to S/4HANA 1909, where RHEL 7 was supported) and RHEL 8 seems to be mandatory, when using RHEL in S/4HANA environments.
Hello Uta Hedemann,
this is the reason why I have mentioned important SAP Notes right at the beginning of the Blog ...
Best Regards Roland
OK. I just saw that hint to PAM is included in note "2884313 - SAP S/4HANA 2020: Release Information".
Hello Roland Kramer
Thanks for sharing your experiences during the upgrade of S4HANA to 2020. Right now I'm performing my own upgrade to the same version and your blog has been useful for me during the resolution of a couple of issues (mainly in phase XPRAS_AIMMRG).
I had to deal with accessing the system during the Execution phase to create and execute a report (note 2918366 and 2244827), but now the process is running again.
I hope to share my annotations also (at least the most relevant points) with the community.
Best regards.
Andres.
Thanks for sharing.
very detailed information, thanks for sharing this.
Good one!! informative.
Hello Roland,
Nice blog!
I have a question. We are already in S4HANA 1709 FPS02. Is it possible to upgrade both front and backend systems to S4HANA 2020 FPS01 directly?
or mandatory to upgrade it to 1809 before moving 2020?
Kindly advise.
Thanks,
Bala
Hello,
We're doing a upgrade from S/4HANA 1709 to 2021 but we're having the following error during addon queue calculation.
2EETN085X"The following component versions" "were decided to remain unchanged" "during the update/upgrade process." " "
2EETN085 "But since underlying component versions" "are changed, this decision needs" "to be revised or confirmed with a" "vendor key"
3 ETN085 "Software component" "GBX01HR" "rel." "600"
3 ETN085 "Software component" "GBX01HR5" "rel." "605"
2EETN085 "Check and clarify the upgrade strategy" "of the listed components" "with the component vendors." " "
2EETN085 "Check and revise the decisions" "in the planning process in" "Maintenance Planner and/or" "in phase IS_SELECT"
2EETN085 "Repeat the Configuration road map step" "with an updated stack XML" "and/or with correct decisions" "in phase IS_SELECT"
How should handle that software components into the MP to get a consistent queue?
Thanks in advance
Hello Sergio Torres
I have handled the Issue with Vendor Keys in the Blog -
Upgrade to S/4HANA 1809 SPSx – the final frontier
Best Regards Roland
Sorry Roland, but I don't see the Vendor Keys in that blog.
I hadn't the option to include Vendor Keys in the SUM process, and the maintenance planner transacción seems to be correct to upgrade to 2021 version but I couldn't find what It's missing.
Check the Content above and download the missing ACR files manually for these Components
Best Regards Roland
Thanks a lot Roland