Lesson 3 of 5
Deployment options
8 min
SAP S/4HANA is offered in three main ways. They share much of the same functional core, but they differ in who runs the system, how it is upgraded, how far it can be extended, and which transition paths lead to it. The deployment choice shapes the whole program, including its testing.
The three options
| Cloud Public Edition | Cloud Private Edition | On-premise | |
|---|---|---|---|
| What it is | Software as a service on SAP's multi-tenant cloud | A dedicated SAP S/4HANA system run by SAP in the cloud, usually bought through RISE with SAP | The customer runs SAP S/4HANA in its own data center or with a hosting provider |
| Who operates it | SAP | SAP, for technical operations | The customer or its provider |
| Upgrades | SAP upgrades every customer on a fixed schedule | Customer plans upgrades within SAP's maintenance rules | Customer plans and runs upgrades |
| Extensibility | Key user and developer extensibility in released, upgrade-stable ways only | Broad, with clean core recommended | Broad, with clean core recommended |
| Transition paths | New implementation only | New implementation, system conversion, selective data transition | New implementation, system conversion, selective data transition |
| Release naming | Year and month, for example 2508 | Year, for example 2025 | Year, for example 2025 |
Public Edition
SAP S/4HANA Cloud Public Edition is a standardized SaaS offering. Customers adopt SAP's preconfigured processes, configure within defined limits, and extend only in released, upgrade-stable ways. SAP delivers major releases twice a year, named by year and month, and keeps all customers current. The benefit is low operating effort and fast access to innovation. The trade-off is less freedom: you cannot convert an ECC system into Public Edition, and you cannot modify the standard. Because upgrades arrive on SAP's schedule, regression testing becomes a regular, time-boxed activity; SAP provides a Test Automation Tool in Public Edition to support it.
Private Edition and RISE with SAP
SAP S/4HANA Cloud Private Edition gives each customer its own system, with the same software as the on-premise product, run by SAP in a cloud environment. It is usually purchased as part of RISE with SAP, a bundle of software, infrastructure, technical operations and related services. SAP has used newer names for its private cloud ERP offering in recent marketing, so contract documents may differ in wording; the product inside is SAP S/4HANA. Private Edition supports all three transition paths, and customers keep more control over upgrade timing and extensions, though SAP encourages a clean core.
On-premise
SAP S/4HANA on-premise is the classic model: the customer licenses the software and runs it, in its own data center or with a hosting provider or hyperscaler. It offers the most control and the most responsibility. Many large companies still choose it for specific regulatory, integration or operational reasons.
What deployment means for testing
- Public Edition: fit-to-standard testing during implementation, then regression testing for every SAP release on a fixed timetable.
- Private Edition and on-premise: transformation testing for the chosen transition path, then upgrade and feature package testing on a schedule the customer plans.
- All options: integration testing with surrounding systems, security and role testing, data validation, and cutover rehearsal.
What would you do?
A Contoso architect proposes moving ECC to Public Edition by system conversion "to get the lowest operating effort and keep our custom code". What is the issue?
- Public Edition: SaaS, standard processes, SAP-scheduled upgrades, new implementation only.
- Private Edition: dedicated system run by SAP, usually via RISE with SAP; all three transition paths.
- On-premise: customer-run with most control and responsibility.
- Deployment sets the testing rhythm: scheduled regression in Public Edition, planned upgrades otherwise.
Check your understanding · not graded
Lesson check
1. Which deployment option can be reached only by new implementation?
2. How is Private Edition usually purchased?
3. Who decides when Public Edition is upgraded?
4. What testing rhythm does Public Edition create?