RAP Interview Questions

1. What is SAP RAP?

SAP RAP (RESTful ABAP Programming Model) is SAP’s modern framework to build transactional

Fiori applications and REST-based APIs using ABAP on S/4HANA.

2. Why was RAP introduced?

RAP was introduced to simplify application development and align ABAP with REST, Fiori

Elements, and Clean Core principles.

3. Which architecture does RAP follow?

RAP follows RESTful and service-oriented architecture where data is exposed as services rather

than tightly coupled programs.

4. Which SAP versions support RAP?

RAP is supported from SAP S/4HANA 1909 onwards and in SAP BTP ABAP Environment.

5. Which UI works with RAP?

RAP mainly works with Fiori Elements which automatically generates UI from metadata.

6. Which protocol is used in RAP?

RAP uses the OData protocol, mainly OData V4, for communication.

7. What is a CDS View in RAP?

CDS View defines the data model, relationships, and annotations used by RAP for UI and services.

8. What is an Interface CDS View?

Interface View represents the core data model and is used for behavior and persistence.

9. What is a Consumption CDS View?

Consumption View is built on interface view and contains UI annotations for Fiori.

10. What is a root entity?

Root entity is the main transactional object that controls the lifecycle of child entities.

11. What is a child entity?

Child entity depends on the root entity and cannot exist independently.

12. What is a Service Definition?

Service Definition specifies which RAP entities are exposed as APIs.

13. What is Service Binding?

Service Binding exposes the service definition via OData V2 or V4.

14. What does CRUD mean?

CRUD represents Create, Read, Update, and Delete operations on business data.

[Link] Page | 1
 RAP Interview Questions

15. Is RAP stateless?

Yes, RAP is stateless, which improves scalability and performance.

16. Does RAP support draft handling?

Yes, RAP supports draft to allow saving incomplete data.

17. What is Clean Core?

Clean Core means keeping SAP standard untouched and extending via RAP.

18. Which language is used in RAP?

RAP is developed entirely using ABAP.

19. Is RAP cloud-ready?

Yes, RAP is designed for both on-premise and cloud environments.

20. Is RAP SAP’s strategic model?

Yes, RAP is SAP’s recommended and future-proof programming model

21. What is Managed RAP?

In Managed RAP, SAP framework handles database operations, locking, and commits

automatically.

22. What is Unmanaged RAP?

In Unmanaged RAP, the developer manually handles database operations and transaction control.

23. When do you use Managed RAP?

Managed RAP is used for new developments where SAP best practices are followed.

24. When do you use Unmanaged RAP?

Unmanaged RAP is used when working with legacy tables or existing complex logic.

25. What is Behavior Definition?

Behavior Definition defines what operations like create, update, delete, and actions are allowed.

26. What is Behavior Implementation?

Behavior Implementation is the ABAP class that contains business logic for behavior.

27. What is a Determination?

Determination automatically derives or updates fields during modify or save operations.

28. What is a Validation?

Validation checks business rules and can block saving of invalid data.

29. What is an Action in RAP?

Action is a custom operation triggered by the user, such as approve or cancel.

[Link] Page | 2
 RAP Interview Questions

30. Can an action modify data?

Yes, actions can change entity data.

31. What is Draft data?

Draft data stores incomplete user changes before final activation.

32. How is locking handled in RAP?

RAP uses optimistic locking based on ETags.

33. What is ETag?

ETag is a version identifier used to detect concurrent changes.

34. How is authorization handled?

Authorization is handled using CDS annotations and behavior definitions.

35. What is late numbering?

Late numbering assigns keys only at save time.

36. What is early numbering?

Early numbering assigns keys at creation time.

37. What is transactional buffer?

Transactional buffer temporarily stores changes before commit.

38. What is save sequence in RAP?

The sequence is validation → determination → save → commit.

39. What is strict mode?

Strict mode enforces clean syntax and best practices.

40. What is projection view?

Projection view exposes only required fields to the service.

41. What is a RAP Business Object?

A RAP BO is a transactional object consisting of root and dependent entities.

42. Explain the RAP save lifecycle.

RAP processes data through validation, determination, persistence, and commit phases.

43. How are commits handled in Managed RAP?

Commits are automatically handled by the RAP framework.

44. What is transactional consistency?

It ensures all changes are saved together or rolled back.

45. What is deep insert?

[Link] Page | 3
 RAP Interview Questions

Deep insert creates root and child entities in a single request.

46. Difference between association and composition?

Composition enforces lifecycle dependency, association does not.

47. How do you debug RAP applications?

Using ABAP Development Tools (ADT) debugger.

48. How do you handle performance in RAP?

By optimizing CDS views and minimizing logic in behavior.

49. What is optimistic locking?

Conflicts are detected at save time, not during edit.

50. What is pessimistic locking?

Data is locked immediately for exclusive access.

51. When should unmanaged RAP be preferred?

When custom commit or legacy integration is required.

52. How are errors returned to UI?

Via reported and failed messages.

53. What is the failed structure?

Failed structure blocks persistence due to errors.

54. What is the reported structure?

Reported structure shows messages without blocking save.

55. What is mapped structure?

Mapped structure maps temporary keys to final keys.

56. RAP vs SEGW OData?

RAP is metadata-driven and modern, SEGW is manual and legacy.

57. RAP vs BOPF?

RAP replaces BOPF with simplified and standardized development.

58. RAP vs CAP?

RAP uses ABAP, CAP uses [Link] or Java.

59. How does RAP support Clean Core?

By enabling extensions without modifying SAP standard.

60. What is the future of RAP?

RAP is SAP’s long-term standard for ABAP development.

[Link] Page | 4