Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 5

RISE with SAP and the private edition operating model

10 min

Listen to this lesson

0:00 / 8:42

RISE with SAP is SAP's subscription offering for moving an ERP customer to SAP S/4HANA in the cloud. For a customer like Contoso, coming from ECC with years of custom code and configuration, the ERP inside RISE is SAP S/4HANA Cloud Private Edition, which SAP also markets as SAP Cloud ERP Private. It is single-tenant: Contoso gets its own CMD, CMQ and CMP systems, with its own code and configuration, but it no longer runs the infrastructure, operating system, database or most technical administration itself. SAP Enterprise Cloud Services (ECS) does, on a hyperscaler or in an SAP data center chosen in the contract.

Business processes, configuration, custom code, data, testingContoso and its partner
Application operationsShared: some tasks in SAP's standard service, many available as paid Packaged Services (formerly SAP Cloud Application Services, CAS) or done by the customer
Technical operations: SAP application layer and SAP HANASAP ECS: updates on request, kernel patches, backups, technical monitoring
Operating system, infrastructure, network inside the cloudSAP ECS, with the hyperscaler or SAP data center as SAP's provider
The private edition operating model in layers. The higher the layer, the more it belongs to the customer.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-304

The roles and responsibilities document

The single most useful document for a platform team under RISE is SAP's Roles and Responsibilities (R&R) for RISE with SAP S/4HANA Cloud, private edition. It lists hundreds of tasks, each with an identifier and a responsibility. SAP states that the PDF version published on its agreements site is the documentation of record, and that the tasks are a catalog: their relevance differs per customer and should be reviewed with SAP's Cloud Architect Advisor or Client Delivery Manager. This course uses version v.3-2025 (March 2025) for task details. That version calls the paid application-operations category SAP Cloud Application Services (CAS); the newer v7-2025 renames it Packaged Services, the name used here. Check your RISE Roles & Responsibilities document for the version your contract references and the category names it uses.

CategoryWho performs itCost
Standard ServicesSAPCovered by the service fee
Optional ServicesOnly SAP; must be contracted and itemizedAdditional fees
Additional ServicesOnly SAP; one-off tasksAdditional fees
Packaged ServicesSAP if bought; otherwise the customer must do itAdditional fees if bought from SAP
Excluded TasksOnly the customerCustomer's own effort

The five task categories in SAP's RISE R&R (v.3-2025, using the v7-2025 name Packaged Services). Check your RISE Roles & Responsibilities document.

How a task's owner is found: the R&R catalog gives its category, the contract says whether it was bought, and whatever is left lands in Contoso's own matrix.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-304

The R&R also describes how a brownfield customer arrives. Integrating installed systems into SAP's cloud operations is a standard service performed once per new system; when the initial set-up is a conversion to SAP S/4HANA, the v.3-2025 document includes two additional test runs, one for a non-production system and one for production, with further runs billable. For Contoso, that line explains why the mock conversions and the dress rehearsal had to be booked with SAP ECS early: each one consumes onboarding effort on SAP's side, not just Sam's.

One sentence in the document deserves a highlighter: all tasks not purchased by the customer, or not provided by SAP as part of the standard service, but applicable to the customer's environment, are the customer's responsibility. In other words, the default owner of anything nobody bought is the customer. A platform team's first job under RISE is to find those gaps before an auditor or an outage does.

  1. Is the task a Standard Service?Yes → SAP performs it; Contoso requests or monitors · No → next question
  2. Is it an Optional or Additional Service?Yes → only SAP can do it; is it in the contract? If not, order it or accept the gap · No → next question
  3. Is it a Packaged Services task?Yes → bought from SAP, or Contoso must staff it · No → next question
  4. Is it an Excluded Task?Yes → Contoso owns it, always · Not listed → Contoso owns it by default
Reading any task in the R&R. The last line is where unowned work hides.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-304
Two landscapes, two ALM tools: RISE includes SAP Cloud ALM for the S/4HANA program, while the legacy ECC line keeps ChaRM on Solution Manager 7.2 until it retires.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-304

What would you do?

Six weeks after go-live, Contoso's auditors ask who reviews the security audit log of CMP. Sam searches the R&R and finds no task for it in SAP's standard services. What follows?

Key points
  • RISE gives Contoso a single-tenant SAP S/4HANA Cloud Private Edition (SAP Cloud ERP Private) operated by SAP ECS.
  • SAP's R&R is the reference: Standard, Optional, Additional, Packaged Services and Excluded tasks.
  • Anything applicable that nobody bought defaults to the customer.
  • RISE includes SAP Cloud ALM, not Solution Manager usage rights.

Check your understanding · not graded

Lesson check

  1. 1. Which R&R category covers tasks only the customer can perform?

  2. 2. What happens to a Packaged Services task if the customer does not buy the service?

  3. 3. Which document version does SAP name as the documentation of record for the R&R?

  4. 4. What does SAP's ALM FAQ say RISE includes?