Show TOC

Locking Transaction Data in Planning (Changed)Locate this document in the navigation structure

Technical Data

Function Is

Changed
In Release

Software Component

  • Component: SAP NetWeaver
  • Release 7.0
Assignment to Application Component

BW-PLA-BPS
Country Setting

Valid for all countries
Use

Locking transaction data in a planning application against changes by other users has been newly implemented. The locks are used by both BW-BPS and the new BI integrated planning so both planning tools can be operated in parallel.

Depending on the number of users working in planning in parallel and the complexity of lock requests necessitated by the modeling, you can use various techniques to manage the lock table.

  • Shared object memory of an application server (default setting): better performance than the lock server.
  • Lock server (present implementation in BPS): particularly suited to small and mid-size installations. This option requires the least administrative effort.
  • SAP liveCache: suitable for very large installations. An SAP liveCache server has to be installed and connected. If you are considering this option for your project, first contact the development team at SAP.

For a more detailed description of the options, see transaction RSPLSE or the corresponding IMG activity. You use this transaction to perform all lock server settings for planning. You can also monitor the current lock entries.

Effects on Customizing

For more information, see SAP Reference IMG → SAP Customizing Implementation Guide → SAP NetWeaver → SAP Business Intelligence → BI Integrated Planning → Settings for Lock Management (or transaction RSPLSE).