SAP / SAP Mid Level (3 to 8 yrs) Interview questions
What is the difference between RAP and the classical ABAP programming model?
The classical model typically meant hand-writing a BAPI or function module for business logic, a separate SAP Gateway service implementation class for OData exposure, and manually wiring the two together — a lot of custom, imperative code for functionality that follows largely the same repetitive pattern (create, read, update, delete, plus validations) across many different business objects.
| Classical Model | RAP |
| Hand-written BAPI/function module + separate Gateway service class. | Declarative behavior definition + CDS View + generated service. |
| A lot of repetitive, imperative boilerplate per object. | Common CRUD/validation patterns handled by the framework itself. |
| Two separately maintained layers (business logic, service exposure) to keep in sync. | Unified, metadata-driven model reducing that duplication. |
RAP's declarative approach means a lot of standard behavior (basic CRUD, draft handling, standard validations) comes largely "for free" from the framework, letting developers focus custom code specifically on the genuinely unique business logic rather than repetitive plumbing.
What did the classical model typically require developers to hand-write separately?
What does RAP's declarative approach reduce for developers?
More Related questions...
