Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-PLA (Application Component) Planning⤷
RSPLS (Package) Planning: General Services
Basic Data
| Data Element | RSPLS_LCK_TABLES |
| Short Description | Number of Lock Tables |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 11 | |
| 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 | Number |
| Medium | 20 | No. of Lock Tables |
| Long | 40 | Number of Lock Tables |
| Heading | 50 | Number of Lock Tables |
Documentation
Definition
If the lock tables are managed in the shared object memory of an application server, the system creates a lock table for each InfoCube the first time the BI lock server is accessed. This table contains the locked selections. A selection defined in the lock table only represents an active lock if a lock record is defined on the SAP lock server for synchronization purposes.
Even if no locks are active for the transaction data in an InfoCube, the lock table may still contain data: In some circumstances, released locks are only deleted from the lock table the next time the BI lock server is accessed. The system synchronizes the lock table with the SAP lock server.
The 'Number of Lock Tables' field contains the number of lock tables that have been created since the system was set up. You can use this table to manage active locks. If you choose 'Clean Up Lock Tables', the system checks whether active locks are still being managed in the lock table. If this is not the case, the system releases any lock tables that are not being used. This action is non critical and can be performed at any time.
Use
If the area for the shared object memory is too small, this may cause a program termination when the area is accessed since this exception cannot be raised in all Releases. In this case, it is no longer possible to synchronize with the SAP lock server. If the lock table that caused the problem no longer contains active locks, choose 'Clean Up Lock Table' to release the lock table.
Dependencies
This field is only relevant if the BI lock server manages the lock tables in the shared object memory of an application server. For information about the sizing of the BI lock server, see SAP Note 928044.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 710 |
