SAP ABAP Data Element OIJ_NOM_LOCKSTRATEGY (Nomination Lock Strategy)
Hierarchy
☛
IS-OIL (Software Component) IS-OIL
⤷
IS-OIL-DS-TSW (Application Component) Trader's and Scheduler's Workbench
⤷
OIJ (Package) TSW Traders and Schedulers Workbench
IS-OIL (Software Component) IS-OIL⤷
IS-OIL-DS-TSW (Application Component) Trader's and Scheduler's Workbench⤷
OIJ (Package) TSW Traders and Schedulers Workbench
Basic Data
| Data Element | OIJ_NOM_LOCKSTRATEGY |
| Short Description | Nomination Lock Strategy |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OIJ_NOM_LOCKSTRATEGY | |
| 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 | OIJ_NOM_LOCKSTRATEGY | |
| 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 Str. |
| Medium | 15 | Lock Strategy |
| Long | 20 | Lock Strategy |
| Heading | 2 | LS |
Documentation
Definition
The lock strategy determines when the data records are enqueued for data changes.
The following two strategies are supported:
- Early lock
The data is locked before reading the data from the database. If the data is already locked by a different user, you can only display the data. - Late lock
No lock is placed on the data records for the change transaction. Instead, the lock is placed just before the data is updated to the database. To ensure consistency, the system re-reads the data from the database to detect any 'conflicting' data changes by different users. If a conflict is detected, the system 'merges' the field changes of the 'new' database versions and your actual input. With this 'merged' record you can try to save again.
Note: The ideal lock strategy depends on your way of working. If you typically work with a relatively small number of records to which you make big changes before saving, you should choose 'early lock' to avoid conflicts and the related additional work for verifying the merged data.
However, if you enter many data records in one go but typically change only a small amount of data, the late lock is preferable so other users are not locked.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 46C |
