SAP DATA CONSISTENCY

Get Example source ABAP code based on a different SAP table
  SAP Help

Data Consistency
When data in database tables is modified by application programs, it must be ensured that the data is consistent after the changes have been made. This is particularly important when data is processed in the database. The time span in which a consistent data state is transferred to another consistent state is known as a Logical Unit of Work (LUW). If an error occurs in an LUW, it is possible to undo all changes made up to this point and restore the data to its original consistent state (rollback). When a new consistent state has been reached, this new state can be committed and a new LUW can be opened.
For an AS ABAP two types of LUWs play a role:

Database LUWs realized by the database system

SAP LUWs realized using special ABAP programming techniques
BEGIN_SECTION VERSION 5 OUT
Accordingly, there are two lock types that are of significance:

Database locks set by the system

SAP locks set using special ABAP programming techniques
END_SECTION VERSION 5 OUT



Latest notes:
The authorizations of a user when accessing data are also relevant for data consistency. The statement AUTHORITY-CHECK is used for explicit authorization checks in ABAP programs. ABAP CDS also offers its own access control based on implicit evaluations of access conditions.
NON_V5_HINTS
ABAP_HINT_END