Hierarchy

⤷

⤷

Basic Data
Data Element | RSPLS_MLCK |
Short Description | Master Locks |
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 | 10 | Locks |
Medium | 20 | Master Locks |
Long | 40 | Locks |
Heading | 50 | Locks |
Documentation
Definition
Master locks are privileged locks for transaction data. These locks are set when planning sequences in BI planning are executed. Master locks are set at InfoCube level and are included as a step in a process chain.
Use
Master locks are intended for processing mass data in BI Planning. You use this type of lock to ensure that complex planning sequences do not terminate because of lock conflicts with other users.
Before processing the data, the system determines all required selections. The system first tries to set a normal lock for these selections. If this is possible, these selections are saved as master locks and the normal locks are lifted.
Particular areas are now protected by the master locks: Users cannot change the data within these areas. The process chain itself runs in the background. However, the master lock does not necessarily apply to the individual subprocesses. These individual subprocesses - and only these subprocesses - can run anyway. At the runtime of the planning sequences, the data that is to be edited is protected by normal locks, as usual.
When the process chain has finished processing the data, the master locks are lifted.
In the lock monitor, you can display the master locks that are currently set. Master locks that are set by process chains have a 'lock handle' assigned to them. You find this information in table 'Master Locks: Header Entries'. The master locks themselves are set at InfoCube level. The locked selections for the lock handle are listed in table 'Lock Records'. The 'Number of the Selection' delimits logically-related selections.
You can delete master locks by selecting the relevant rows in the 'Master Locks: Header Entries' table. Even if you delete master locks, the transaction data is protected at runtime by normal locks. However, without the master locks, you can no longer guarantee that the individual parts of planning sequences are executed despite lock conflicts with other users.
Dependencies
Master locks are only set by planning sequences in process chains.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 710 |