ABAP Cloud is the development model for ABAP applications defined by SAP that is optimized for the cloud and runs on modern SAP platforms. It is used to create cloud-ready applications, services, and extensions that are stable, upgrade-safe, and built according to modern programming principles.
You can think of it as an evolution of classic ABAP, specifically designed for the following environments:
- SAP Business Technology Platform (BTP), ABAP Environment: Often referred to as “Steampunk”. Here you can develop completely new, standalone cloud applications or build so-called “side-by-side” extensions for your existing SAP systems (cloud or on-premise).
- SAP S/4HANA Cloud (Public and Private Edition): Here, ABAP Cloud is used to extend the core system (“on-stack” extensions) without directly modifying SAP standard code. This follows the “Clean Core” principle.
- SAP S/4HANA On-Premise (from Release 2022): ABAP Cloud can also be used here for on-stack extensions to make them upgrade-stable.
Core Features of ABAP Cloud
Use of Released APIs
Developers may only use stable, explicitly released local APIs (classes, CDS views, function modules, etc.) and defined extension points. Direct calls to non-released SAP objects or modifications to SAP standard code are not allowed. This guarantees that extensions will continue to work even after a cloud or S/4HANA upgrade.
ABAP RESTful Application Programming Model (RAP)
This is the central programming model in ABAP Cloud. It is used for efficient development of intrinsically cloud-ready, OData-based services (for SAP Fiori UIs or web APIs). It replaces older models such as Dynpro or Web Dynpro ABAP in this context.
Cloud Optimization
The entire runtime environment and development principles are designed for scalability, security, and efficiency in the cloud.
Development Tools
Development takes place exclusively in the ABAP Development Tools (ADT) for Eclipse, no longer in the classic SAP GUI (Transaction SE80).
Language Version
A cloud-optimized version of the ABAP language is used, which excludes certain older commands or commands unsuitable for the cloud.
Lifecycle Management
Uses modern tools such as Git or abapGit for version control and transport (gCTS).
Difference from Classic ABAP (Classic ABAP vs ABAP Cloud)
In classic ABAP (as in SAP ECC or older S/4HANA on-premise versions without ABAP Cloud restrictions), developers had much more freedom: They could call almost any SAP objects (including non-released ones), directly read/write standard tables, and even modify SAP standard code. This often led to problems and high effort during upgrades. ABAP Cloud deliberately restricts these freedoms to ensure stability and upgrade safety.
In Summary, ABAP Cloud Is
- The strategic ABAP development model from SAP for the cloud and S/4HANA.
- Focused on stability and upgrade safety through the use of released APIs (“Clean Core”).
- Based on the ABAP RESTful Application Programming Model (RAP).
- Developed in ADT for Eclipse.
- Enables the development of cloud applications on SAP BTP and extensions for S/4HANA (Cloud and On-Premise).
It enables companies to leverage their existing ABAP skills to develop modern, cloud-native applications and extensions in the SAP ecosystem.