SAP S/4HANA Cloud - Software Lifecycle Management for Customers with Notes
Software Lifecycle Management for SAP S/4HANA Cloud Customers Enhanced with Notes for More Details Download the DocumentPublic
SAP S/4HANA Cloud Public Edition
Software Lifecycle Management for Customers
SAP S/4HANA Cloud Delivery, SAP
May 07, 2025
1
SAP S/4HANA Cloud Public Edition
Software Lifecycle Management for Customers
SAP S/4HANA Cloud Delivery, SAP
May 07, 2025
1
2Public
SAP S/4HANA Cloud Public Edition for Customers using a 3-System Landscape
• Upgrade and Maintenance Schedule
This section describes the structure of (and information covered in) the Maintenance and Upgrade Schedule documents that exist for
different landscape versions.
• Upgrade Process and Limitations for Customers
This section describes the upgrade process used by SAP, related scheduling/timing aspects and limitations that occur for customer activities
during different process phases
• Hotfix Collection Deployment Process and Limitations for Customers
This section describes the process used by SAP to deploy Hotfix Collections, related scheduling/timing aspects and limitations that occur for
customer activities during different process phases
Appendix
The appendix covers additional information related to topics listed below
• Default schedule for ATO transport jobs and recommended regional adjustments
• 2-System Landscapes: Hotfix Collection Deployment Schedule per Data Center Region
• SAP S/4HANA Cloud Public Edition Upgrade and Maintenance Schedules for Customers using a 2-System
Landscape and for Partners
Contents
2
SAP S/4HANA Cloud Public Edition for Customers using a 3-System Landscape
• Upgrade and Maintenance Schedule
This section describes the structure of (and information covered in) the Maintenance and Upgrade Schedule documents that exist for
different landscape versions.
• Upgrade Process and Limitations for Customers
This section describes the upgrade process used by SAP, related scheduling/timing aspects and limitations that occur for customer activities
during different process phases
• Hotfix Collection Deployment Process and Limitations for Customers
This section describes the process used by SAP to deploy Hotfix Collections, related scheduling/timing aspects and limitations that occur for
customer activities during different process phases
Appendix
The appendix covers additional information related to topics listed below
• Default schedule for ATO transport jobs and recommended regional adjustments
• 2-System Landscapes: Hotfix Collection Deployment Schedule per Data Center Region
• SAP S/4HANA Cloud Public Edition Upgrade and Maintenance Schedules for Customers using a 2-System
Landscape and for Partners
Contents
2
SAP S/4HANA Cloud Public Edition, 3-System Landscape
Upgrade and Maintenance Schedule
3
Upgrade and Maintenance Schedule
3
4Public
Upgrade and Maintenance Schedule
Software Lifecycle Events and Schedule
SAP S/4HANA Cloud Public Edition, 3-System Landscape - Upgrade and Maintenance Schedule
SAP S/4HANA Cloud Public Edition, 3-System Landscape – Upgrade & Maintenance Schedule
Upgrade
Hotfix Collection with
• Corrections
Hotfix Collection with
• Corrections
• Innovations
Software Lifecycle Events
SAP S/4HANA Cloud is Software as a Service public cloud offering. Thus all
customers have the same software lifecycle schedule.
All systems are upgraded according to this common schedule and all systems
receive hotfix collections according to it.
The schedule is published on SAP.com and can be accessed via the link
displayed on the slide.
The visualization shows an excerpt of the calendar section with different
colored boxes for upgrade and hotfix collection weekends being scheduled.
For SAP S/4HANA Cloud there are 3 types of scheduled lifecycle events:
1. Upgrade (twice per year)
2. Hotfix Collections with Corrections (applied roughly every four weeks)
3. Hotfix collections with Corrections and Innovations (roughly per month)
In addition there is an Emergency Correction process (so called Emergency
Patch). Emergency Patches are intended to
• bring in urgently required corrections into individual customer systems
• solve business critical emergency situations caused by software of
business configuration/SAP reference content defects.
The Emergency Patch process can be used in the time in between Hotfix
Collections. As it is intended to solve urgent issues in customer systems fast
Emergency Patches do not follow any predefined schedule.
4
Upgrade and Maintenance Schedule
Software Lifecycle Events and Schedule
SAP S/4HANA Cloud Public Edition, 3-System Landscape - Upgrade and Maintenance Schedule
SAP S/4HANA Cloud Public Edition, 3-System Landscape – Upgrade & Maintenance Schedule
Upgrade
Hotfix Collection with
• Corrections
Hotfix Collection with
• Corrections
• Innovations
Software Lifecycle Events
SAP S/4HANA Cloud is Software as a Service public cloud offering. Thus all
customers have the same software lifecycle schedule.
All systems are upgraded according to this common schedule and all systems
receive hotfix collections according to it.
The schedule is published on SAP.com and can be accessed via the link
displayed on the slide.
The visualization shows an excerpt of the calendar section with different
colored boxes for upgrade and hotfix collection weekends being scheduled.
For SAP S/4HANA Cloud there are 3 types of scheduled lifecycle events:
1. Upgrade (twice per year)
2. Hotfix Collections with Corrections (applied roughly every four weeks)
3. Hotfix collections with Corrections and Innovations (roughly per month)
In addition there is an Emergency Correction process (so called Emergency
Patch). Emergency Patches are intended to
• bring in urgently required corrections into individual customer systems
• solve business critical emergency situations caused by software of
business configuration/SAP reference content defects.
The Emergency Patch process can be used in the time in between Hotfix
Collections. As it is intended to solve urgent issues in customer systems fast
Emergency Patches do not follow any predefined schedule.
4