RAP
ABAP RESTful Application Programming Model
The cloud-ready programming model for transactional apps and OData services, built on CDS views and behavior definitions.
A RAP business object combines a CDS data model with a behavior definition that declares which operations — create, update, delete, actions — are allowed and how they are validated.
In ABAP Cloud, data of SAP applications is changed through the released RAP business object of the owning application (with EML statements such as MODIFY ENTITIES). Direct writes to SAP tables bypass its validations and are blocked.
Classic dynpro transactions are rebuilt as RAP-based Fiori elements apps when custom code moves to ABAP Cloud.
In ERP Preflight
Clean Core Object Guard reports direct writes to SAP tables and points to the released RAP business object or API of the owning application as the fix.
Problems that involve RAP
- BlockerDirect write to an SAP standard table
- MajorLegacy object needs a cloud extension
- MajorCustom Z/Y transaction needs Clean Core review
- CriticalRequirement implies a Clean Core violation (tier 11)
- CriticalDirect read of an SAP standard table
- CriticalObsolete or cloud-forbidden ABAP statement
- CriticalCall to a function module not released for cloud development
- CriticalUse of a class not released for cloud development
Related terms
Free tools
- Clean Core Object Lookup
Is a table, CDS view, class or function module released for ABAP Cloud?
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.