sap-rap-comprehensive

SAP RAP — RESTful Application Programming Model

Related Skills

• sap-s4hana-extensibility — Extending standard SAP RAP BOs
• sap-security-authorization — RAP authorization patterns
• sap-testing-quality — RAP test doubles in depth

Quick Start

RAP BO in 5 artifacts:

1. Database Table     → ZTAB_TRAVEL
2. CDS View Entity    → ZI_Travel (interface, root)
3. Behavior Definition → ZI_Travel (managed, draft)
4. Behavior Impl.     → ZBP_I_Travel (handler + saver)
5. Service Definition  → ZSD_Travel → Service Binding (V4)

Minimum BDEF (managed with draft):

managed implementation in class zbp_i_travel unique;
strict ( 2 );
with draft;

define behavior for ZI_Travel alias Travel
persistent table ztab_travel
draft table zdraft_travel
etag master LocalLastChangedAt
lock master total etag LastChangedAt
authorization master ( global, instance )
{
  field ( readonly ) TravelUUID;
  field ( mandatory ) AgencyID, CustomerID;

  create; update; delete;

  determination SetStatusNew on modify { create; }
  validation ValidateDates on save { field BeginDate, EndDate; }
  action ( features : instance ) AcceptTravel result [1] $self;

  draft action Resume;
  draft action Edit;
  draft action Activate optimized;
  draft action Discard;
  draft determine action Prepare;

  mapping for ztab_travel corresponding;
}

Core Concepts

RAP Architecture Layers

┌─ Service Layer ──────────────────────────────┐
│  Service Definition → Service Binding (V2/V4) │
├─ BO Projection Layer ────────────────────────┤
│  CDS Projection View (C_*) + Projection BDEF  │
├─ BO Interface Layer ─────────────────────────┤
│  CDS View Entity (I_*) + Behavior Definition   │
│  + Behavior Implementation (Handler/Saver)     │
├─ Data Layer ─────────────────────────────────┤
│  Database Tables / CDS Abstract Entities       │
└──────────────────────────────────────────────┘

Implementation Types

Type	When to Use	Key Difference
Managed	New greenfield development	Framework handles CRUD + persistence
Unmanaged	Wrapping legacy (BAPIs, FMs)	Developer handles all persistence
Managed + Unmanaged Save	Managed CRUD but custom save	Framework CRUD, you handle DB write
Managed + Additional Save	Managed save + extra side-effects	Framework saves, you do extra work