Upgrade to S/4HANA 1709 FPS01 – fast trak
Last Update: 4th of June 2020
Upgrade to S/4HANA 1709 FPS01 – fast track
S/4HANA 1709 FPS02 – the story continues …
S/4HANA 1709 SPS03 – back on the Mothership again …
Upgrade to S/4HANA 1809 SPSx – the final frontier
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
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
Note 2532587 – Add. info. on converting to SAP S/4HANA using SUM 2.0 SP01
Note 2594074 – Add. info. on converting to SAP S/4HANA using SUM 2.0 SP02
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 SPS03 – back on the Mothership again …
Prepare the S/4HANA readiness Check
The S/4HANA 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 – S/4HANA 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
Note 2741379 – SAP S/4HANA 1809 SP* Conversion & Upgrade – TCI Note #7
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.
Note 2144394 – DMO: Views missing from database in phase RUN_RSDB02CK_END
Note 2318321 – Differences in SUM for the rescue of Non-SAP objects between load and delta procedure
Note 2418979 – CDS views (DDL SQL views) cannot be activated with unknown function name
Note 2421686 – CDS view (DDL SQL View) cannot be activated with RUTDDLSACT
Note 2516565 – missing objects after upgrade to ERP 6.0 EHP8
Note 2565447 – ACT_UPG: Missing objects starting with CE9*
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
Blog – Getting started with the S/4Hana Migration Cockpit (OnPremise)
Blog – Discover the S/4HANA Migration Cockpit Migration Object Modeler (OnPremise) /NLTMOM
Blog – Fiori for S/4HANA – Performance: What is CDN?
Blog – SAPUI5 Application Startup Performance – Best Practices
Roland Kramer, SAP Platform Architect for Intelligent Data & Analytics
“I have no special talent, I am only passionately curious.”
Hi Roland Kramer,
I'm getting below error same as per above in phase
Checks after phase MAIN_SHDRUN/SUBMOD_PARDIST_CDS/RUN_DIST_ADD_DDLS_FOR_CONV_TABS were negative!
Batchjob RSUPGJOB on shadow system failed.
Detected the following errors:
4 ETG011 " "
4 ETG039 -------------------------------------------------------------------------
4 ETG011 "No DDLS for table conversions found, nothing to do"
4 ETG011 "Read Import Queue from""/usr/sap/S4H/SUM/abap/var/TRIMPQUEUE.LST"
4 ETG013 "Import Queue" "78" "entries found"
2EETG012 "No nametab found for DDLS view" "ZSQL_ITC"
Trouble Ticket Generation
Trouble ticket: "/usr/sap/S4H/SUM/abap/log/SAPup_troubleticket.log"
Log archive: "/usr/sap/S4H/SUM/abap/log/SAPup_troubleticket_logs.sar"
Initialize phase MAIN_SHDRUN/SUBMOD_PARDIST_CDS/RUN_DIST_ADD_DDLS_FOR_CONV_TABS to restart it from the beginning
Can you please guide me how to fix this issue..?
In the meantime your incident is solved as also described in the Blog above, section RUN_DIST_ADD_DDLS_FOR_CONV_TABS
Best Regards Roland
after the upgrade we are getting several errors regarding inactive InfoCubes, InfoObjects and missing HANA views, have you also experienced such an behaviour?
That is related to the BW Upgrade (obviously BW embedded ...), so check the BW SL Blog for Upgrade Topics - https://blogs.sap.com/2016/10/11/software-application-lifecycle-management-sap-bw/#bwupgrade
in Particular -
Best Regards Roland
Thanks for the nice article. How many items you found in SPAU/SPDD after upgrade? Also how much time it took roughly? We are also going to upgrade 1610 to 1709.
this is really hard to predict and is purely dependent to your Implementation
I used an IDES Version where you can be sure, that there were lots of objects to reset
Since NetWeaver 7.50 the SPAU procedure is really simplified ans should not me a problem which can be solved within hours.
Best Regards Roland