End-to-End ABAP on SAP BTP (RAP) — Tutorial &
Code (PDF)
Author: Generated by ChatGPT (GPT-5 Thinking mini). Date: 2025-11-23
1. Prerequisites
- Access to SAP BTP account with ABAP Environment (aka 'ABAP Cloud' / Steampunk) entitlement. -
ABAP Development Tools (ADT) in Eclipse or SAP Business Application Studio (BAS). - Basic ABAP and
CDS knowledge. - Role and authorizations to create/activate ABAP objects in the cloud instance.
2. Overview (What we'll build)
We will create a minimal RAP-based CRUD backend: a 'Hello' entity with an integer key and a message
field, expose it as an OData V4 service, and include sample ABAP logic. This is intentionally minimal to be
easy to follow end-to-end.
3. Step-by-step code
3.1 CDS: Define the root entity (ZI_HELLO)
@[Link]: 'Hello Entity'
@[Link]: #NOT_REQUIRED
define root view entity ZI_HELLO
{
key id : abap.int4;
message : [Link](100);
}
3.2 Behavior (Managed) - Define behavior for the entity
managed;
define behavior for ZI_HELLO alias Hello
implementation in class ZBP_HELLO unique;
create;
update;
delete;
3.3 Behavior Implementation Class (skeleton)
CLASS zbp_hello IMPLEMENTATION.
METHOD create.
" Implement create logic (if custom)
ENDMETHOD.
METHOD update.
" Implement update logic (if custom)
ENDMETHOD.
METHOD delete.
" Implement delete logic (if custom)
ENDMETHOD.
ENDCLASS.
3.4 Service Definition (Expose entity in service)
define service ZI_HELLO_SRV {
expose ZI_HELLO as Hello;
}
3.5 Service Binding (Create an OData V4 binding in
ADT or BAS)
- In ADT: Right-click the service definition and choose 'Create Service Binding' -> Choose 'OData V4' ->
Activate. - In BAS: Use the Cloud Foundry tools / service binding wizard for the ABAP environment. - After
activation, the service endpoint will be available under the ABAP endpoint, typically under:
/sap/opu/odata4/// - Ensure the Communication Arrangement / Role collection has appropriate
permissions if using business users.
3.6 Example ABAP class (helper / simple logic)
CLASS zcl_hello_helper DEFINITION PUBLIC FINAL CREATE PUBLIC.
PUBLIC SECTION.
METHODS get_default_message
RETURNING VALUE(rv_msg) TYPE string.
ENDCLASS.
CLASS zcl_hello_helper IMPLEMENTATION.
METHOD get_default_message.
rv_msg = |Hello from ABAP on BTP!|.
ENDMETHOD.
ENDCLASS.
3.7 Example Report to insert test data (for
development)
REPORT zhello_seed.
DATA: ls_hello TYPE zhello. " assume table/entity mapping exists
ls_hello-id = 1.
ls_hello-message = 'Hello from ABAP on BTP!'.
" For RAP-backed persistence, use appropriate service APIs or CDS update; example pseudo-code:
" /demo only - in real RAP use behavior actions or repository APIs
TRY.
"Use ABAP SQL or repository calls depending on persistence model
INSERT zhello_table FROM ls_hello.
COMMIT WORK.
WRITE: / 'Inserted'.
CATCH cx_root INTO DATA(lx).
WRITE: / 'Error:', lx->get_text( ).
ENDTRY.
4. Testing the OData V4 service
- Use an HTTP client (Postman, curl) to call the activated OData V4 endpoint. - Example GET (list): GET
[Link] - Example GET single: GET .../Hello(1) - Example
POST/PUT/DELETE according to OData V4 conventions. Authentication via SAP Cloud Identity or ABAP
user credentials depending on setup.
5. Deployment & Activation Tips
- Activate CDS, Behavior Definition, Service Definition, and Service Binding objects in ADT/BAS. - If using
BAS, use the Deployment view to push to the ABAP environment. - Check the Cloud Foundry logs and
ABAP runtime logs for activation errors. - Ensure entitlements and subscriptions are assigned in your BTP
subaccount for 'ABAP Environment' prior to creating the instance. - Use the 'SAP Cloud SDK' or local Fiori
tooling if you plan to build a frontend (Fiori Elements/UI5) on top of this service.
6. Advanced / Next steps (suggestions)
- Add Authorization checks: implement CDS-based or ABAP-based authorization checks. - Add
BOPF/Transactional handling or use RAP-managed transaction semantics. - Create Behavior Actions and
implement them in the behavior implementation class for business logic. - Build a Fiori Elements
List-Report + Object Page using the service as backend (Annotation-driven UI). - Write unit tests with
ABAP Unit for your classes and behavior logic.
Appendix: Full combined code (copyable)
-- CDS (ZI_HELLO)
@[Link]: 'Hello Entity'
@[Link]: #NOT_REQUIRED
define root view entity ZI_HELLO
{
key id : abap.int4;
message : [Link](100);
}
-- Behavior (ZB_HELLO)
managed;
define behavior for ZI_HELLO alias Hello
implementation in class ZBP_HELLO unique;
create;
update;
delete;
-- Service Definition (ZI_HELLO_SRV)
define service ZI_HELLO_SRV {
expose ZI_HELLO as Hello;
}
-- Behavior Implementation (skeleton)
CLASS zbp_hello IMPLEMENTATION.
METHOD create.
" custom create logic (optional)
ENDMETHOD.
METHOD update.
" custom update logic (optional)
ENDMETHOD.
METHOD delete.
" custom delete logic (optional)
ENDMETHOD.
ENDCLASS.
-- Helper class
CLASS zcl_hello_helper DEFINITION PUBLIC FINAL CREATE PUBLIC.
PUBLIC SECTION.
METHODS get_default_message RETURNING VALUE(rv_msg) TYPE string.
ENDCLASS.
CLASS zcl_hello_helper IMPLEMENTATION.
METHOD get_default_message.
rv_msg = |Hello from ABAP on BTP!|.
ENDMETHOD.
ENDCLASS.
Notes & References
This PDF provides an end-to-end minimal example meant for a development sandbox on SAP BTP ABAP
Environment. Adapt object names and package layout to your organization's naming conventions and
packages. For production apps, follow SAP guidelines on security, performance, and transport
management.