Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CST-EQ (Application Component) Enqueue⤷
SENQ (Package) Enqueue Handling
Basic Data
| Data Element | EQEUSETXT |
| Short Description | Cumulative Counter for Lock Entry /Dialog |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM10 | |
| Data Type | NUMC | Character string with only digits |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Use Count. |
| Medium | 20 | Use Counter |
| Long | 20 | Cumulative Counter |
| Heading | 55 | Cumulative |
Documentation
Definition
A cumulation counter specifies how often a lock operation (enqueue) has been executed on this lock enty. Mulitple locking, for example, in nested functions is possible (cumulation).
The lock is not canceled until the corresponding number of unlock operations (dequeue) have been executed and both cumulation counters are back to zero again.
Use
Background information:
A lock can have one or two owners. Accordingly, a transaction contains two lock owners. One of the lock owners is passed to the update task when the update is called. The other lock owner remains in the transaction. There is one cumulation counter for each lock owner.
When a lock operation is called, the parameter "_SCOPE" specifies the lock owner the operation is for.
_SCOPE = 1 : for the owner remaining in the transaction
_SCOPE = 2 : for the owner passed to the update task
_SCOPE = 3 : for both owners
For more information see the documentation on enqueue and the update process.
Dependencies
Example
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 630 |
