- SAP Managed Tags:
Introduction:
The following document describes the steps taken for an upgrade to SAP S/4HANA 1909. The source system is our internal RIG test system which was on SAP S/4HANA 1809 with embedded Fiori Front End Server.
The RIG document is available for download here: SAP S/4HANA 1909 Upgrade
The document includes:
Prerequisite:
We upgraded our HDB 2.0 to the latest revision at the time, which was REV 43. Also, we used SUM Tool version 2.0 SP 6 Patch Level 2
Analysis:
Our SUM Uptime and Downtime timing for this small instance are listed below.
![]()
The total Runtime is 32 hours and 36 minutes while the downtime is 5 hours and 23 minutes. Since this is a test system with a small database and memory footprint, we were able to achieve the weekend downtime with the downtime minimized option.
Longest steps in Downtime = ~ 5 hours in TABIM_UPG and XPRAS
![]()
Conclusion:
This guide is a reference along with the more detailed Upgrade Guide to SAP S/4HANA 1909 on premise. Please read both guides before starting your upgrade journey as your system and environment are different.
For planning a system conversion to SAP S/4HANA, please refer to this blog for a great technical overview by our RIG team.
https://blogs.sap.com/2020/05/27/sap-s-4hana-1909-system-conversion-steps-details-how-to-be-prepared...
Thank you.
RIG
The following document describes the steps taken for an upgrade to SAP S/4HANA 1909. The source system is our internal RIG test system which was on SAP S/4HANA 1809 with embedded Fiori Front End Server.
The RIG document is available for download here: SAP S/4HANA 1909 Upgrade
The document includes:
- Steps for Maintenance Planner to generate the stack.xml and planning steps.
- SUM tool screenshots of each steps along with additional notes and comments we have encountered in our test system.
Prerequisite:
We upgraded our HDB 2.0 to the latest revision at the time, which was REV 43. Also, we used SUM Tool version 2.0 SP 6 Patch Level 2
Source: UPGANA.xml file
Analysis:
Our SUM Uptime and Downtime timing for this small instance are listed below.
The total Runtime is 32 hours and 36 minutes while the downtime is 5 hours and 23 minutes. Since this is a test system with a small database and memory footprint, we were able to achieve the weekend downtime with the downtime minimized option.
Longest steps in Downtime = ~ 5 hours in TABIM_UPG and XPRAS
Conclusion:
This guide is a reference along with the more detailed Upgrade Guide to SAP S/4HANA 1909 on premise. Please read both guides before starting your upgrade journey as your system and environment are different.
For planning a system conversion to SAP S/4HANA, please refer to this blog for a great technical overview by our RIG team.
https://blogs.sap.com/2020/05/27/sap-s-4hana-1909-system-conversion-steps-details-how-to-be-prepared...
Thank you.
RIG
1 Comment
