ABAP Cloud Environment
SAP BTP's managed ABAP runtime — the bridge between classic ABAP expertise and cloud-native development. Build clean core-compliant extensions using RAP, released APIs, and ABAP Cloud rules.
Executive Summary
The ABAP Cloud Environment is a fully managed ABAP-as-a-Service on SAP BTP. It allows ABAP developers to build cloud-native extensions using the same language they know, but constrained to the ABAP Cloud programming model: released APIs only (C1/C2 classification), no direct database table access, no classic ABAP syntax (CALL TRANSACTION, RFC calls, etc.).
It is the ideal landing zone for ABAP teams transitioning to the cloud. The runtime is fully managed by SAP — no OS, database, or ABAP system administration required. Development uses ADT (Eclipse) or the BAS ABAP Dev Space. Deployment follows a three-tier flow: local unit test → cloud integration → production, using software component transport via gCTS.
ABAP Cloud Architecture Concepts
RAP Entity + Behavior Definition Example
1" CDS Entity — Business Partner extension
2@AccessControl.authorizationCheck: #CHECK
3@EndUserText.label: 'Enhanced Business Partner'
4define root view entity ZDEWA_I_BUSPARTNER
5 as select from I_BusinessPartner
6{
7 key BusinessPartner,
8 BusinessPartnerFullName,
9 BusinessPartnerIsBlocked,
10 " Virtual element for calculated field
11 @ObjectModel.virtualElement: true
12 @ObjectModel.virtualElementCalculatedBy: 'ABAP:ZDEWA_BP_CALC'
13 cast( '' as dewa_partner_tier ) as PartnerTier,
14 CreatedByUser,
15 CreationDate
16}
17
18" RAP Behavior Definition
19managed implementation in class zbp_dewa_buspartner unique;
20strict;
21
22define behavior for ZDEWA_I_BUSPARTNER alias BusinessPartner
23persistent table zdewa_bp_ext
24lock master
25authorization master ( instance )
26{
27 create;
28 update;
29 delete;
30 field ( readonly ) BusinessPartner;
31
32 action updateTier result [1] $self;
33
34 mapping for zdewa_bp_ext
35 {
36 BusinessPartner = business_partner;
37 PartnerTier = partner_tier;
38 }
39}Clean Core Compliance: Released API Classification
| Classification | Meaning | ABAP Cloud Allowed |
|---|---|---|
| C1 — Use System-Internally | Released for use within the same software component only | No |
| C2 — Use in Key User Apps | Released for key user extensibility scenarios (BAdIs, CDS extensions) | Yes |
| C0 — Released for Cloud | Fully released for ABAP Cloud custom code — stable API contract guaranteed | Yes |
| No classification | Internal implementation detail — no stability guarantee | No |
Enterprise Example: DEWA Meter-to-Cash Extensions
Best Practices
ATC enforces clean core rules automatically. Enable it in CI/CD pipelines to catch violations before they reach the ABAP Cloud system.
Configure external system connections via Communication Arrangements — the cloud-native equivalent of SM59 RFC destinations. No hardcoded credentials.
Never use old-style ABAP Gateway (SEGW). RAP + CDS is the only supported pattern for new OData V4 services in ABAP Cloud.
Plan API versioning for all RAP-exposed entities. Breaking changes require new entity versions — retrofitting versioning is painful.
ABAP Cloud uses software component transport (gCTS), not classic ABAP transport requests. Maintain distinct DEV/TEST/PROD systems.
Common Pitfalls
Security Considerations
ABAP Cloud Environment uses IAS for user authentication — no direct SAP system users. Configure role-based authorization via Business Role assignments in the IAM app (equivalent to PFCG). Use Communication Users (technical users) for system-to-system communication via Communication Arrangements — never use personal named users for API access. Enable audit logging for all inbound and outbound Communications to meet compliance requirements.