SAP Cloud ERP Public vs. Private: Differences Between the Public Edition and the Private Edition

SAP Cloud ERP and SAP Cloud ERP Private are the commercial names of the two cloud editions of SAP S/4HANA. SAP Cloud ERP is SAP S/4HANA Cloud Public Edition: a public cloud service with standardized processes, extensibility through released mechanisms only, and two upgrades a year applied by SAP. SAP Cloud ERP Private is SAP S/4HANA Cloud Private Edition: a system dedicated to one customer, with a scope comparable to on-premise SAP S/4HANA, full access to Customizing, classic ABAP available, and one release every two years, installed by SAP on request.

Both editions include maintenance management, but not the same one. The public edition works with its own scope items and, in release 2602, had no scope item for refurbishment of spare parts or for the checklist process. The private edition keeps the classic SAP PM processes. SAP's mobile app changes too: SAP Maintenance Assistant on the public edition, SAP Service and Asset Manager on the private edition. Where each edition sits in the product family is covered in What is SAP S/4HANA.

Technical name and commercial name of each edition

SAP uses two vocabularies in parallel. The technical product name remains on SAP Help Portal, in contracts, in courses, and in API topics. The commercial name appears on the website and in presentations. The table maps one to the other, following SAP's Exploring SAP Cloud ERP course in its October 2026 version.

Technical name	Commercial name	Associated offering	Architecture
SAP S/4HANA Cloud Public Edition	SAP Cloud ERP	GROW with SAP (SAP GROW)	Shared among customers (multi-tenant)
SAP S/4HANA Cloud Private Edition	SAP Cloud ERP Private	RISE with SAP	Dedicated to one customer (single tenant)

The same course notes that SAP Cloud ERP is also used as a broad category covering both editions. In a contract, a proposal, or an integration specification, use the technical name. The difference between the offerings that package each edition is in RISE with SAP vs. GROW with SAP.

Public Edition vs. Private Edition: what changes in each dimension

The table compares the two editions on the dimensions that define a project. The rows come from SAP's official offering comparison, the ABAP Cloud documentation, the upgrade schedule, and the SAP Learning courses listed in the references, with data as of October 2026.

Dimension	Public Edition (SAP Cloud ERP)	Private Edition (SAP Cloud ERP Private)
Functional scope	Configurable, standardized processes, with a smaller but growing scope compared with SAP S/4HANA	Comparable to SAP S/4HANA, including line-of-business and industry processes
Configuration	Scope items are mandatory, set up through SAP Central Business Configuration	Full access to Customizing (IMG). Scope items are optional
Implementation	New implementation	New implementation, system conversion, selective data transition, or lift and shift
Extensibility and ABAP	Key user extensibility, ABAP Cloud, and side-by-side extensions on SAP BTP. Standard ABAP is not available, and only released APIs are accepted	All options. Standard ABAP is available, ABAP Cloud is the recommended model, and modifications are possible but not recommended
Upgrades	Two a year, in February and August. The release name carries year and month: 2602 and 2608	One release every two years. The release name carries the year: 2023 and 2025
Who installs	SAP, on the dates of the schedule it publishes	SAP, at the customer's request. The customer must plan the upgrade in time to stay in maintenance
Who tests	Customer and partner, in the test system upgraded ahead of production	Customer and partner, who plan, prepare, and test
User metric	Per user, per month (PUPM), with user types by package	FUE (full use equivalent)
Infrastructure	A service operated by SAP, without the provider choice the Private Edition offers	SAP data center or hyperscaler. SAP lists Microsoft Azure, AWS, and Google Cloud, among others, depending on region and offering
SAP GUI and Fiori	SAP Fiori launchpad. Some apps are SAP GUI for HTML apps opened in the launchpad, such as IK11 and IK18	Classic transactions and Fiori apps, depending on configuration
OData integration	Public APIs, activated per communication scenario	APIs according to the installed release
RFC and BAPI integration	Restricted to released interfaces. SAP limits RFC and IDoc to connections with SAP ERP on-premise systems	Available according to release, network, and authorization
Add-ons	Only add-ons qualified for the Public Edition	Add-ons qualified for SAP S/4HANA

On the Private Edition, technical capability is not the same as a contractual right: modifications to standard code, add-ons, and operations services depend on the offering purchased and on the version of the documents attached to the order form. The extensibility rules, with levels A to D, are in SAP clean core.

How do upgrades work in releases 2602 and 2608?

On the Public Edition, 2602 is the February 2026 release and 2608 is the August 2026 release. The official schedule for the 2-system landscape, in its version dated September 17, 2026, shows the 2608 upgrade on quality systems on August 1 and 2 and on production systems on August 15 and 16, with a two-week testing period in between. For release 2702, the planned dates are January 30 and 31, 2027, for quality and February 13 and 14, 2027, for production, subject to change by SAP.

In the 3-system landscape, the 2608 documentation describes the upgrade first in the test system and, four weeks later, in the development and production systems. In both cases SAP sends an e-mail notice six weeks ahead, and regression testing of processes and integrations is the job of the customer and the partner. Between major upgrades, SAP deploys monthly hotfix collections and smaller features the customer may activate before the next release.

On the Private Edition, the customer chooses the window and requests the installation. What SAP operates and what stays with the customer in that model is covered in RISE with SAP.

What the Public Edition accepts for OData, RFC, and BAPI

The Public Edition is not OData-only, but it does not accept arbitrary RFC calls either. The page Available Interfaces for Your Selected Scope, on SAP Help Portal, maps each scope item to its available interfaces. In version 2608, it shows three things for maintenance:

• The current scope items 4HH, 4HI, 4VT, and 4WM are mapped to OData interfaces only. The maintenance order, in API API_MAINTENANCEORDER_0002, and the maintenance notification sit in scenario SAP_COM_0397. Operation confirmation and measurement document sit in SAP_COM_0398. Equipment, functional location, and measuring point sit in SAP_COM_0395.
• BAPIs such as BAPI_ALM_ORDER_MAINTAIN, BAPI_ALM_CONF_CREATE, and BAPI_ALM_NOTIF_CREATE appear only under the deprecated scope items BH1, BH2, and BJ2, in scenarios SAP_COM_0344 and SAP_COM_0322.
• The page states that RFC and IDoc-type APIs are restricted for use with and connecting to SAP ERP on-premise systems.

A BAPI on that list is therefore not a guaranteed path for a new tenant or for any external application. Each interface requires a communication arrangement, with a communication scenario, user, and system. When evaluating an integration, ask in writing for the object, the read or write operation, the exact API, the release, and the scenario.

Plant maintenance in each edition

On the Public Edition, maintenance is activated through scope items. The table lists the ones SAP names in the public edition Asset Management course and in the comparison lesson for release 2602, as published in October 2026.

Scope item	Official name	Status
4HH	Reactive Maintenance	Available
4HI	Proactive Maintenance	Available
4VT	Improvement Maintenance	Available
4WM	Operational and Overhead Maintenance	Available
7Z4	Permit to Work	Available
43R	Maintenance Resource Scheduling	Requires an additional license
4RV	SAP Maintenance Assistant	Requires an additional license
7Z2	Maintenance Order Processing with SAP Field Service Management	Requires an additional license
BH1	Corrective Maintenance	Deprecated as of release 2302. Successor: 4HH
BJ2	Preventive Maintenance	Deprecated as of release 2302. Successor: 4HI
BH2	Emergency Maintenance	Deprecated as of release 2602. Successor: 4HH
3YE	Integration with Asset Central Foundation	Deprecated as of release 2508, with no replacement planned

A deprecated scope item can no longer be scoped or activated. Functions already configured may remain usable, and SAP neither deletes nor updates that configuration. New projects use the successors.

The gap carries a release number: for Public Edition 2602, SAP's comparison lesson states there is no scope item for Refurbishment of Spare Parts or for the Checklist Process. The same check has to be repeated for 2608 before any decision. On the Private Edition and on-premise, maintenance has the classic SAP PM processes and the phase-based processes, configured through the IMG. The objects involved are described in SAP PM maintenance orders.

Which SAP mobile app serves each edition?

SAP Service and Asset Manager and SAP Maintenance Assistant are different products for different back ends. The SAP Service and Asset Manager 2511 quick start guide lists as back end SAP S/4HANA Cloud Private Edition, on-premise SAP S/4HANA, or SAP ERP 6.0 with enhancement package 7 or 8, along with SAP Gateway, Cloud Connector, and SAP BTP Mobile Services. The same guide states that with a Public Edition back end, the app to use is SAP Maintenance Assistant, activated through scope item 4RV with an additional license.

A mobile solution validated on ECC or on the Private Edition is not thereby validated on the Public Edition: objects, APIs, and release need their own proof. The questions to settle before a field mobility rollout are in SAP PM mobile project.

Does the Public Edition have a local version for the United States?

Yes. The United States is among the 60 countries and regions with an SAP-delivered local version in the Public Edition 2608 documentation, alongside Canada and Mexico. For SAP-delivered local versions, delivering legal changes is SAP's responsibility. For any other country, SAP supports customer local versions built with its localization tools, and there the delivery of legal changes is the customer's responsibility.

For a U.S. group with plants abroad, that makes the country list a scoping item: each legal entity's country is checked against the list for the release in scope, and coverage is confirmed process by process.

How to choose between the public and the private edition

• Current system: if the history, configuration, and code of the ECC system must be preserved, only the Private Edition accepts a system conversion. The Public Edition is always a new implementation.
• Maintenance processes: check, scope item by scope item and for the current release, what operations use today, including refurbishment and checklists.
• Extensions: list the custom PM programs and separate what can be rebuilt on released APIs from what depends on Standard ABAP.
• Calendar: verify that regression testing of integrations fits two windows a year set by SAP, and how those windows line up with planned shutdowns and turnarounds.
• Field execution: settle the mobile app before the edition, because the back end restricts the options.

The transition paths into each edition are in SAP S/4HANA migration: greenfield and brownfield.

PM RUN is the maintenance execution, mobility, and planning platform that runs on top of SAP PM without replacing SAP, and it uses SAP PM on ECC 6.0 or on S/4HANA, on-premise or in the cloud. In an edition decision, the integration of any execution platform goes through the same test as every other interface: object, operation, API, and release named and tested. The page on asset management in SAP describes what the platform executes.