Last Update: 6th of June 2019
Upgrade to S/4HANA 1709 FPS01 – Lessons learned
Ok, actually upgrading S/4HANA System is not really my turf. However getting the latest NetWeaver 7.52 Version and S/4HANA 1709 is also interesting together for the usage with BW/4HANA.
So my Source System is based on S/4HANA 1610 FPS02 IDES and it used also from the SAP Mentors as a Test System. Due to the fact that the System is hosted in the Azure Cloud, it is possible to work simultaneously together with our external colleagues and internally.
Good to know:
Even that I used the option “Single System” as the main Upgrade strategy, you have to deal with a Shadow Instance and several activation processes
the following sources were used from support.sap.com/sltoolset: SUM 2.0 SP02 from 29.01.2018
Important SUM Phases
Plan the target Vector in the Maintenance Planer
As the source System contains several Add-On, the MP has to calculate a lot of dependencies which might not work from the beginning.
additional Information about the Maintenance Planner can also be found in the Blog – S/4HANA 1709 FPS03 – back on the Mothership again …
Prepare the S/4HANA readiness Check
The S/4 readiness check is the essential check before the technical Upgrade starts and will be called as Report /SDF/RC_START_CHECK
Note 2495992 – SAP S/4HANA 1709 – application specific notes in system conversion / upgrade preparation phase
Note 2471149 – SI Check 1709: Reconstruction of indirect relationships in table VBFA needed. Upgrade not possible
Note 2418242 – SD – Issue in Document Flow (SAP S/4HANA): Correction
Note 2383423 – SAP S/4HANA Simplification: Software License Management
If you have a lower start release then S/4HANA 1610 check also the following Note:
Note 2182725 – S4TC Delivery of the SAP S/4HANA System Conversion Checks for SAP S/4HANA 1511 or 1611
Note 2210486 – S/4HANA Business Partner Conversion Reports
Note 2245333 – Pre-Transition Checks for FIN: Error Messages and Possible Solutions
Note 2389794 – SAP S/4HANA 1610 – application specific notes in system conversion preparation phase
Note 2399707 – SAP Readiness Check – Simplification Item Check
Note 2502552 – S4TC – S4/HANA Conversion & Upgrade new Simplification Item Checks
Note 2538018 – S4TC – S/4HANA 1709 Conversion & Upgrade – TCI Note #3
Note 2708143 – SAP S/4HANA 1809 SP01 Conversion & Upgrade – TCI Note #6
make sure you implemented the latest Version of the Notes 2399707 (at least Version 84, currently Version 121) and 2502552 (at least Version 34, currently Version 63) as you cannot update them during the relevant SUM phases anymore.
Here the Target SAP S/4HANA Version 1709 [01(01/2018) FP] must be selected, otherwise the SUM process cannot calculate the target System in the Phase
Background Job /SDF/RC_START_CHECK Failed
Errors occurred during Execution of S/4HANA Readiness Checks to verify if upgrade is possible. For more information, see log file S4_SIF_TRANSITION_CHECKS.S4H.
Log file error summary:
File S4_SIF_TRANSITION_CHECKS.S4H does not exist in directory /usr/sap/<SID>/SUM/abap/log (it will be written once the Phase is successful)
Target product version and stack cannot be read from stack.xml Check execution has been stopped because prerequisites of consistency check in SUM mode have not been met. Job finished
SUM Phase: MAIN_SHDRUN/
If you encounter Problems with the following DDLS objects, then make sure you checked the Nametab’s before the Upgrade starts for consistency.
ZV_DEMO_01 ZCVHADOOPCDS ZFVHADOOPCDS ZZ1_D40EA67C16EB ZSQL_ITC
the DDL’s must be deleted manually, as there are inconsistencies with the name-tab’s.
this is a collection of Notes which deals with potential inconsistencies during the activation phase.
Mostly the Solution is to sync the missing entries with the active name tab’s.
You have decided in phase PREP_CONFIGURATION/INITSUBST to do the SGEN on shadow instance which turns out not to be the best idea (actually a very bad Idea) …
use the solution from the following
Note 2475935 – How to skip phase RUN_SGEN_GENER8 on shadow instance
select count(GENSTATUS) from "SAPS4H"."UPGGENSET~" where genstatus = 'I'; truncate table "SAPS4H"."UPGGENSET~";
use the solution from the following Note 2516565 – missing objects after upgrade to ERP 6.0 EHP8
Final Steps in the S/4HANA Upgrade
see the log file /usr/sap/S4H/SUM/abap/log/LONGPOST.LOG
You can run SPAU now and remove old and obsolete Add-On’s if possible …
Good to know:
The S/4HANA Readiness Check /SDF/RC_START_CHECK will show that Note 2502552 is not implemented, as the purpose of the Check is relevant only for the preparation of an Upgrade or Conversion to SAP S/4HANA 1709 and above.
As soon, as the Upgrade or Conversion to SAP S/4HANA 1809 is available, the Note 2502552 will be relevant again.
Have fun …
So what to do next?
Check the following Blog’s from Jörg Knaus about the usage of the new Migration tools
Roland Kramer, SAP Platform Architect for Intelligent Data & Analytics
“I have no special talent, I am only passionately curious.”