According to the Roles and Responsibilities document for RISE with SAP S/4HANA Cloud, private edition, the implementation of updates to the managed SAP solution using standard tools and methods is a standard service, for which SAP is responsible. However, there are some steps within this task for which the customer is responsible. The process of updating application software therefore requires interaction between SAP and the customer:
Hint
The term "update" denotes the change to a new minor release of the hosted SAP software, typically focused on bug fixes and small enhancements. This includes the implementation of support package stacks for SAP S/4HANA as well as the implementation of feature package stacks, but does not include the upgrade of SAP S/4HANA to the next major release.
Note that the update of the application software requires scheduled downtime to implement.
SAP Enterprise Cloud Services is responsible for many technical tasks such as preparing the update, implementing the latest version of the Support Package Manager (transaction SPAM), and running the Software Update Manager (SUM) tool.
The Maintenance Planner generates the download files that SUM uses to execute the update. It is the task of the customer to create a Maintenance Planner ID and attach it to the Upgrade Service Request for SAP Enterprise Cloud Services.
Hint
If you need support from SAP Enterprise Cloud Services generating the Maintenance Planner ID, mention this in the Service Request. SAP Enterprise Cloud Services then generates the ID as a standard service (free of charge) and sends it back to you with the Service Request for review. The update is executed once you approve the Maintenance Planner ID.
SAP Enterprise Cloud Services clarifies any application-related breakpoints such as the modification adjustment (transactions SPDD and SPAU), Simplification Items Checks (SI-Checks), and so on with you and informs you as soon as the uptime is complete. Once you have completed the necessary ramp-down activities, you hand them over to SAP Enterprise Cloud Services. Based on the schedule indicated in the Service Request, SAP Enterprise Cloud Services then triggers the SUM downtime.
Hint
Ramp-down activities include stopping application-related background jobs, locking business users, clearing stuck transaction queues, and updating errors. The goal is to ensure the system is idle and ready for downtime activities.
For more information on the Simplification Item (SI) Checks, see the blog SAP S/4HANA Simplification Item Check - How to do it right.
Note
In your development system, you create transport requests to record the modification adjustments. These transport requests can be included in the subsequent system updates.
Any post-installation task required which is not technical (such as application-related settings, manual code creation in the customer namespace, or manual activities required in the SAP namespace) has to be performed by the customer.
