Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-PLA (Application Component) Planning⤷
RSPLS (Package) Planning: General Services
Basic Data
| Data Element | RSPLS_LOCK_CHAS |
| Short Description | Documentation on Lock Characteristics |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| 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 | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
When transaction data is requested in change mode, this data has to be locked exclusively for one user. The records to be locked are described in one selection table. A data record is locked by the selection table if the characteristic value in the data record is inlcuded in the selection for each characteristic in the selection table. If the selection table is empty, every data record is locked. It does not matter whether the data record exists in the database.
These locks are effected at InfoCube level. As a presetting, all characteristics in the InfoCube and the artificial characteristic '1KYFNM' (key figures are understood as values for this artificial characteristic) are relevant for locking.
Use
For many applications it is not necessary to make all characteristics relevant for locking. Therefore you may wish to determine just those characteristics that are relevant for locking. This means that the other characteristics are not used in the collision check, the selection tables for lock management are smaller and less complex. This is a very simple way of significantly reducing the load on the lock server.
Dependencies
If no characteristics are relevant for locking, the whole InfoCube is locked.
Example
In cost center planning you are using the characteristics 'Cost Center' 'Cost Element', 'Version', 'Fiscal Year'. If several users are planning for the same year and same cost elements, the characteristics 'Cost Center' and 'Version' are enough to ensure that selections for different users do not overlap. Determine only these characteristics as being relevant for locking.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 700 |
