Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
BJarkowski
Active Contributor
Following my previous posts about S/4HANA installation and maintenance I would like present you today how to perform the system upgrade from 1511 to 1610. Our current landscape consists of two systems:

BJH – S/4HANA Backend system
BJF – S/4HANA Frontend system

If you’d like to refresh your memory about system provisioning, please have a look on my previous posts.

PREREQUISITES:

- S/4HANA 1610 requires HANA SP12 (read Frank's post on how to perform the upgrade)
- Your S/4HANA system should be connected to Solution Manager
- System data in SAP Service Marketplace are up to date

MAINTENANCE PLANNER

First tool we are going to use today is the Maintenance Planner, which will calculate all required files and packages for the upgrade.



We need to select SAP S/4HANA Upgrade and the target product version should be S/4HANA 1610.



On the next screen we need to inform, which operating system are we using as application server. After that, we just have to push files to download basket and get our stack file.



SOFTWARE UPDATE MANAGER

Now it’s time to start Software Update Manager and provide location of the stack file.



Next we can decide about SPAM update (highly recommended!)



Software Update Manager informs us about missing SAP Note that implements some preliminary checks before the upgrade (like DB version check). Once this note has been applied we can move to the next screen.



As at the moment downtime is not our biggest worry we can choose Single System configuration – but anyway as it’s upgrade, the shadow system will be created.



On next screen we can see what language packages are going to be imported (depends on languages installed in SAP system).



Finally, we can see the summary of target support package level. As you can see, component S4CORE has a version 101 assigned.



Next step is to create the system backup… and we are ready to start the actual upgrade:



Finally, after several hours Software Update Manager informs us that the upgrade has been completed!



The system is started, so we can immediately log in and check system version.





It looks like all went fine and our system is now upgraded. But we didn’t finish the whole process yet. Our environment has separate gateway instance which we need to patch as well!

NETWEAVER GATEWAY UPDATE

As the whole process of upgrading front-end server looks similar I would like to show only some differences.

In Maintenance Planner we need to choose AS ABAP 7.51 for S/4HANA 1610



To make the installation a bit different I chose to verify SAP archives in Software Update Manager.



And suddenly I saw the warning saying the authentication or validity of one archive could not be established. Fortunately, it turns out that one file was not fully downloaded.



On next screen again I chose Single System configuration to minimize run time.



What surprised me was that one add-on component was not calculated in update queue and I had to download the file separately.



Now, we can verify the target support package stack and start the upgrade.



And again after few hours we get nice message from SUM saying the procedure is completed.



Quick look into system status:





Our gateway is now updated!

S/4HANA 1610 has a new Fiori theme I really wanted to see. After logging in, SAP Belize was already selected as the default theme!















This is the fifth part of my blog series about S/4HANA installation and maintenance. You can access previous parts by using following links:

Part 1 – Maintenance Planner, System Installation and Update
Part 2 – SAP NW Gateway and Fiori Launchpad
Part 3 – Best Practices Content Activation
Part 4 – Fact Sheet apps, Fiori Search and Web Dispatcher
Part 5 – Upgrade to 1610
Part 6 – Fully Activated Appliance on Microsoft Azure
Part 7 – Fiori Launchpad SAML Single Sign-On with Azure AD


17 Comments