ABAP Cloud interviews revolve around one theme: the clean core. Interviewers want to know if you can build in the cloud ABAP environment using only released APIs and modern RAP — or if you still reach for classic tricks that no longer compile.
ABAP Cloud and Clean Core
Q1. What is ABAP Cloud?
ABAP Cloud is the cloud-ready ABAP development model, running on SAP BTP (Steampunk) and S/4HANA Cloud. It restricts development to released APIs and objects to keep the core clean. Code that violates this fails the ABAP Test Cockpit checks.
Q2. What does clean core mean for an ABAP developer?
Never modify SAP standard objects; extend via released extension points, custom fields, and side-by-side services. Upgrades then apply without retrofit pain. It is a discipline enforced by tooling, not just a guideline.
Q3. What are released APIs and API contracts?
Released APIs are SAP objects marked stable for customer use, with contracts (e.g. C1) guaranteeing upgrade stability. Only these may be used in ABAP Cloud. Unreleased objects are blocked at activation or flagged by ATC.
Q4. What is the 3-tier extensibility model?
Tier 1: key-user extensibility (custom fields, no code). Tier 2: on-stack developer extensibility in ABAP Cloud. Tier 3: side-by-side extensions on BTP. Choose the lowest tier that satisfies the requirement.
RAP Fundamentals
Q5. What is the ABAP RESTful Application Programming Model (RAP)?
RAP is the framework for building transactional Fiori apps and services in ABAP Cloud, based on CDS data models and behavior definitions. It covers managed, unmanaged, and draft scenarios. It is the successor to BOPF and classic dynpro programming.
Q6. What is the difference between managed and unmanaged RAP?
Managed RAP has the framework implement CRUD and draft handling; you add determinations, validations, and actions. Unmanaged RAP leaves all implementation to you for full control over complex logic. Start managed and go unmanaged only when needed.
Q7. What is a behavior definition?
It declares the transactional behavior of a business object: operations, draft enablement, actions, validations, and determinations. The behavior implementation class contains the ABAP logic. It separates the contract from the code.
Q8. What is EML?
Entity Manipulation Language is the ABAP language for reading and modifying RAP business objects in code. Statements like READ ENTITIES, MODIFY ENTITIES, and COMMIT ENTITIES replace direct table updates. Always use EML instead of touching underlying tables.
READ ENTITIES OF zi_booking
ENTITY booking
FIELDS ( booking_id customer )
WITH VALUE #( ( booking_id = '42' ) )
RESULT DATA(lt_result).In RAP, the database table is an implementation detail. If your code reads the table directly instead of using EML, the behavior logic is bypassed.
CDS and Data Modeling
Q9. What role do CDS views play in RAP?
CDS views define the data model: interface views for the database layer, projection views for the service exposure. Annotations add UI and OData semantics. The virtual data model keeps consumption views stable across releases.
Q10. What are determinations, validations, and actions?
Determinations compute derived field values automatically; validations check consistency and raise messages; actions expose custom operations as buttons. They run at defined points in the transaction. Together they implement business logic declaratively.
Authorization and Draft
Q11. How is authorization handled in RAP?
Via access control (DCL) documents on CDS entities defining who can read or modify data, plus instance-based authorization in behavior implementations. The framework enforces both automatically. Test with different users, not just your developer account.
Q12. How does draft handling work in RAP?
Draft tables store in-progress edits keyed by draft UUID while active data stays unchanged. The framework provides draft actions (edit, activate, discard) and handles locking. Enable it in the behavior definition with minimal extra code in managed scenarios.
Q13. How do you expose a RAP BO as an OData service?
Define a service definition listing the exposed entities and a service binding choosing the protocol (OData V4 UI or Web API). The binding generates the service at activation. Fiori elements apps consume the UI binding directly.
Q14. What is ABAP Test Cockpit (ATC) and why does it matter?
ATC runs static checks including ABAP Cloud readiness: released API usage, forbidden statements, and performance rules. ABAP Cloud code must pass these checks. Run them before transport, not after rejection.
ABAP Cloud interviews test whether your habits changed: released APIs only, EML over direct table access, and RAP over classic module pools.
Interviewing soon? Drop your toughest question in the comments.