Last Update: 4th of June 2020
S/4HANA 1709 SPS03 – back on the Mothership again
since I’m back at SAP SE as Platform Architect for Intelligent Data & Analytics, I also checked my “Innovation Landscape” for updates and new Software Stacks.
As SAP BW/4HANA 2.0 will be available by end of February, the Upgrade will take some time until the BPC Add-On is available. As almost everyone uses integrated planning (IP) on BW/4HANA, this will be the majority of the upgrades.
SAP BW/4HANA 2.0, ABAP FND 1809 on HANA and S/4HANA 1809 are sharing now the same SAP Application Stack. Unfortunately the ABAP FND 1809 differs from a NW AS ABAP 7.51 INNOVATION PKG, as it contains additional components in the core ABAP foundation:
- ABAPFND 1.0
- MDG_FND 8.03
- S4FND 8.03
Therefore it is not possible to install the BW/4HANA Starter Add-On on top of the ABAP FND 1809 and convert directly the BW/4HANA 2.0.
Correction of installed software information
Verification in the Maintenance Planner – Part I: Principle and Evolution
Verification in the Maintenance Planner – Part II: How-to & Examples
Recommendation for Landscape Data Gathering: Use HTTP(S) for All Data Suppliers including RZ70
(Blogs created by Wolf Hengevoss)
So, first thing is to create a so called “CISI stack file” (correction of installed software information).
Therefore log on to the Maintenance Planner and check your personal settings as follows:
When you now switch to the main entry screen of the Maintenance Planner for your S/4HANA system, you will see that the Verification option is marked as red and the Plan option is grey at this time. Not always will the correct SPS level recognized from the system information either uploaded as sysinfo XML or direct connection from the LMDB of the Solution Manager on premise.
Compare existing and uploaded system information
The editor screen allows you now (see also the following examples):
- to edit the correct SPS level,
- overwrite the SPS level
- delete a unwanted Add-On
- add a missing Add-On manually (Details in the Maintenance Planner Guide, CH 4.3)
edit the validated software stack from the stack.xml
overwrite the validated software stack from the stack.xml
delete the software Add-On from the stack.xml
add add an necessary Add-On manually to the stack.xml
once you finished the editing of the CISI stack.xml file you can continue with the validation
it can also happen that after the validation of the software stack, that there are still some inconsistencies which also has to be acknowledged.
You can search for these missing Add-On’s in the Download Center and add them manually to the EPS/in directory when the Download Basket is available
finally Activate the changes and download the Correction file for later usage.
apply the CISI file to the S/4HANA backend
to avoid that the made setting are going lost, you must apply the changes to the S/4HANA backend. This is done with the SUM (software update manager) part of the SL Toolset 1.0
A short overview of the usage of the SUM can also be found here – SAP First Guidance – Using the new DMO to migrate to BW on HANA
Now the Installed Product Versions Tap Strip looks much more better and validated to ensure a clean and successful SPS update to higher S/4HANA releases.
Create your target software vector for S/4HANA 1709
Log on to the Maintenance Planner update the system data with the correct information, until you can plan your software change.
If you get unspecific errors in this phase you have to use the “Undo” option and correct your former selections. You can search for possible solutions in the Expert Search under the component BC-UPG-MP
Roland Kramer, SAP Platform Architect for Intelligent Data & Analytics
“I have no special talent, I am only passionately curious.”