What is optimistic concurrency control in SAP BC-ESI-RAP - RESTful ABAP Programming Model?

SAP Term: optimistic concurrency control

• Component: BC-ESI-RAP

• Component Name: RESTful ABAP Programming Model

• Description: Optimistic concurrency control enables transactional access to data by multiple users while avoiding inconsistencies by unintentional changes of already modified data. In RAP this is ensured by using an ETag field in the CDS behavior definition.

Smart SAP Assistant

• Key Concepts: 
  Optimistic concurrency control is a feature of the BC-ESI-RAP RESTful ABAP Programming Model that helps to ensure data integrity when multiple users are accessing the same data. It works by keeping track of the version of the data that each user has, and if a user attempts to update the data with an outdated version, the update will be rejected. 
  
  How to use it: 
  Optimistic concurrency control is enabled by default in the BC-ESI-RAP RESTful ABAP Programming Model. When a user attempts to update data, the system will check to see if the version of the data they have is up-to-date. If it is not, then the update will be rejected and the user will need to retrieve the latest version of the data before attempting to update it again. 
  
  Tips & Tricks: 
  When using optimistic concurrency control, it is important to ensure that all users are using the same version of the data. This can be done by having a central repository for all versions of the data, or by having each user check for updates before attempting to update any data. 
  
  Related Information: 
  Optimistic concurrency control is similar to pessimistic concurrency control, which also helps to ensure data integrity when multiple users are accessing the same data. However, pessimistic concurrency control works by locking out other users from accessing or updating the data until it has been updated by one user.