SAP RAP & Transactional Integrity

SAP RAP Concurrency & Draft Lock Architect

Eliminate lost updates and concurrency collisions in SAP Fiori apps. Architect lock master/dependent hierarchies, Total ETag annotations, and optimistic concurrency controls.

⚙️ Concurrency Specification

Timestamp updated on every row modification (child or root).
System timestamp updated only when the entire business object is committed.
// Generating Root Entity BDEF Concurrency...
// Generating Item Entity BDEF Concurrency...
// Generating CDS ETag Annotations...

🛡️ Clean Core Concurrency Golden Rules

Total ETag vs Master ETag Distinction

etag master protects single-row optimistic locks during active draft editing. total etag evaluates overall BO validity during draft activation to prevent overriding external changes.

Strict Lock Master Delegation

Child items must always specify lock dependent by _Parent. Independent locks on child entities create deadlocks in high-concurrency environments.

Zero Long-Running Database Locks

RAP drafts use SAP Lock Server enqueue locks with 15-minute expirations. The physical database is never held locked while a user has a draft tab open in the browser.

Master SAP RAP Architecture & Clean Core Design

Get complete RAP behavior blueprints, EML transactional patterns, and Clean Core migration architectures in our definitive guides.