SAP ABAP Data Element /BOBF/CONF_ENQUEUE_SCOPE (Lock Behavior)
Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation
   AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration
     /BOBF/CONFIGURATION (Package) Business Object Processing Configuration
Basic Data
Data Element /BOBF/CONF_ENQUEUE_SCOPE
Short Description Lock Behavior  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type /BOBF/CONF_ENQUEUE_SCOPE    
Data Type NUMC   Character string with only digits 
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 LockBehvr 
Medium 15 Lock Behavior 
Long 20 Lock Behavior 
Heading 30 Lock Behavior 
Documentation

Definition

The lock behavior defines the enqueue scope when one of the following locks are requested:

  • Dialog Lock (Scope 1) : Do not use! A Lock is owned by dialog work process.
  • Update Lock (Scope 2): A Lock is owned by update work process.
  • Dialog and Update Lock (Scope 3): Do not use! Locks are owned by dialog and update dialog work process. Locks of both owners are always in sync (requesting an exclusive lock means requesting an exclusive lock for the dialog and update work process).
  • Optimistic Dialog and Update Lock (Scope 3): Locks are owned by dialog and update dialog work process. Locks of both owners are not always in sync (dialog work process keeps optimistic lock even if an exclusive lock is requested).

Use

Use Update Lock for business objects that are saved asynchronously.

If you are working with optimistic locks and you want to keep the business object data in the buffer after saving, then use the Optimistic Dialog and Update Lock to ensure that the optimistic lock is also stored after saving.

Dependencies

Example

History
Last changed by/on SAP  20130604 
SAP Release Created in 702