Hierarchy
⤷ BW-PLA (Application Component) Planning
⤷ RSPLS (Package) Planning: General Services
Basic Data
Data Element | RSPLS_LOCK_METH_LC |
Short Description | Planning: liveCache as Lock Server |
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 | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | Lock |
Medium | 20 | Lock Method |
Long | 40 | liveCache as Lock Server |
Heading | 50 | liveCache as Lock Server |
Documentation
Definition
If transaction data is requested in change mode, this data has to be locked exclusively for one user. The data records that need to be locked are described in a selection table. A data record is locked by the selection table if for each characteristic in the selection table, the characteristic value in the data record lies within the selection. If the selection table is empty, each data record is locked. In this case it is irrelevant whether the data record exists in the database.
These selection tables have to be stored and managed centrally for all users and application servers. The SAP Standard Lock Server cannot manages locks that are based on selection tables. For this reason, you have to make your own settings for storing locks that are described by selection tables.
Use
You have the option of creating selection tables in SAP liveCache. This option is only available if SAP liveCache is installed on a separate server. In this case, the collision check is also performed in SAP liveCache. Only use SAP liveCache in the BW lock server if explicitly requested by SAP Support or Development. Usually it is sufficient (and much easier) to activate the shared objects memory solution (option 2 in transaction RSPLSE on the 'Lock Table' tab).
Dependencies
You only need to use the SAP liveCache as the lock server, if the situation occurs where none of the options for sizing the lock table described in SAP Note 928044 have worked. If you are uncertain whether this situation has occurred, contact SAP Support. Read SAP Note 928044 to find out the relevant parameters for sizing the table.
For more information about configuring the liveCache as a lock server, see SAP Note 816730.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 730 |