SAP ABAP Data Element EQEGRAMODE (Lock Mode (Shared/Exclusive) of a Lock Entry)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-CST-EQ (Application Component) Enqueue
     ⤷ SENQ (Package) Enqueue Handling

Basic Data

Data Element	EQEGRAMODE
Short Description	Lock Mode (Shared/Exclusive) of a Lock Entry

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	CHAR1
Data Type	CHAR	Character String
Length	1
Decimal Places	0
Output Length	1
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Lock Mode
Medium	15	Lock Mode
Long	20	Lock Mode
Heading	55	Lock Mode

Documentation

Definition

The mode used to set a lock entry.

'S' means that the lock entry was set in 'shared mode' and can therefore accept further lock entries by other users also in 'shared mode'.

Background:

The lock mode regulates whether several users can access data records at the same time. The lock mode can be assigned separately in the lock object for each table. When you set the lock, the lock entry is stored for the relevant table in the system lock table.

There are different ways to synchronize access by several users:

• Exclusive lock (E): The locked data can be displayed or edited by one user only. Requests for either another exclusive lock or a shared lock are rejected.
• Shared Lock (S): Several users can access the locked data at the same time in display mode. Requests for further shared locks are accepted, even if they are from other users. Exclusive locks are rejected.
• Exclusive but not cumulative lock (X): While exclusive locks are requested repeatedly by the same transaction and can be reset again in succession, exclusive but not cumulative locks can only be requested by the same transaction once only. All further lock requests are rejected.
• Optimistic Lock (O): An optimistic lock can be set if the data is displayed in change mode and the lock behaves like a shared lock if there are access collisions. But if the data is changed, the optimistic lock converts to an exclusive lock. 0ptimistic locks on the object then become invalidated. It can therefore be possible that the conversion fails, if beforehand another optimistic lock was converted. In such cases the use of optimistic locks is only beneficial, if the probability that the data will NOT be changed is high.

History

Last changed by/on	SAP	20141013
SAP Release Created in	630