ABAP Cloud as a contract
Cloud-ready language, released objects and public APIs to limit core dependency.
Cloud strategy · 03/05
One architecture, any edition.
RHP does not impose a topology. ABAP Cloud discipline and ATC Cloud Readiness as a common guardrail across on-premise, RISE Private, Public Edition and BTP.
Compatibility matrix
| — | On-premise | RISE Private | Public Edition | BTP ABAP Env. |
|---|---|---|---|---|
| Runtime | Embedded / on-stack | Embedded / on-stack | Side-by-side | Native |
| Developer extensibility | OK | OK | ABAP Cloud / Fiori Ext. | OK |
| OData V4 | Native | Native | Released APIs | Native |
| Clean-core control | ATC gate | ATC gate | Released objects | ABAP Cloud |
| Deployment | Embedded | Embedded | BTP integration | RHP runtime on BTP |
Lifecycle assurance
Every change associated with version, transport and ATC result.
-
ABAP development
RAP, CDS, OData V4 and released objects when applicable.
-
gCTS commit
Versioned repository, traceable by functional change.
-
ATC Cloud Readiness
Cloud-compatibility gate bound to the commit.
-
Controlled transport
Landscape promotion with readiness evidence.
-
Target runtime
On-stack or BTP ABAP Environment per SAP strategy.
SAP strategy fit
BTP as the natural platform
Side-by-side on SAP BTP ABAP Environment when lifecycle and operation must be decoupled.
RISE and S/4HANA as continuity
The same approach governs on-premise, private edition and transition to public/BTP without redoing the architecture.
Edition strategy
Installed base / on-premise
Deploy on existing S/4HANA with ABAP Cloud discipline and ATC Cloud Readiness.
RISE with SAP / Private
Functional and technical continuity for customers with full scope and partner add-ons.
Public Edition + BTP
RHP side-by-side on BTP ABAP Environment; apps published via Fiori launchpad / SAP Build Work Zone.