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