SAP ABAP Data Element OIRA_LOCKOBJ (Document base table object to be locked)
Hierarchy
☛
IS-OIL (Software Component) IS-OIL
⤷ IS-OIL-DS-SSR (Application Component) Service Station Retailing
⤷ OIR (Package) SSR Service Station Retailing (master/overall)
⤷ IS-OIL-DS-SSR (Application Component) Service Station Retailing
⤷ OIR (Package) SSR Service Station Retailing (master/overall)
Basic Data
Data Element | OIRA_LOCKOBJ |
Short Description | Document base table object to be locked |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OIRA_LOCKOBJ | |
Data Type | CHAR | Character String |
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 | 8 | Lock obj |
Medium | 15 | DBT lock object |
Long | 15 | DBT lock object |
Heading | 15 | DBT lock object |
Documentation
Definition
Records in the document base table may need to be accessed by many processes at once. These processes may be update processes and not only read processes. Due to the large number of transactions contained in the document base table then the accesses are controlled by a virtual locking process.
When accessing the document base table it is possible to "lock" all records for a lock object in table OIRA_DBT_LOCK. This lock object might be a business location (PBLNR) or a clearing house object (CHOBJ). No other calling process can access these records until the "lock" is released
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |