Lock Concept and Lock Management 
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. In this case it is irrelevant whether the data record exists in the database.
The following rules apply:
All records in the selection are locked.
If the selection table is empty, each data record is locked since no restrictions exist.
For characteristics outside the aggregation level, selection * (all) is always locked.
ExampleThe selection table is as follows:
Characteristic
Characteristic value
Fiscal Year
2006
Product
P1 - P10
This table describes a selection. All the records within this selection are locked. This includes the following for example:
Fiscal Year
Product
2006
P1
Both values are in the selection, so the record is locked.
2006
P20
P20 is not in the selection, so the record is not locked
2007
P1
2007 is not in the selection, so the record is not locked
2008
P11
Neither component is in the selection, so the record is not locked
End of the example.
Activities
The selection tables have to be stored and managed centrally for all users and application servers. The SAP standard lock server cannot manage locks that are based on selection tables. You therefore have to make BW-specific settings to store locks that are described by selection tables.
You access the BW lock management settings in the SAP Reference IMG (transaction SPRO) or in lock setting maintenance for planning (transaction RSPLSE). To use BW Integrated Planning, the used lock table needs to be sized. The sizing depends on the location of the lock table.
Recommendation
When implementing BW Integrated Planning, we recommend using an optimized lock concept for your planning application. This involves modeling selections in the components of the planning application in such a way that different users can edit different objects in change mode.
Note
After upgrading to SAP NetWeaver 7.0, BW-BPS also uses the lock settings from BW Integrated Planning. This changes the setting for storing the lock table, meaning that the lock table has to be sized. Alternatively, you can store the lock table in the SAP lock server since this lock table is sized in the BW-BPS implementation project. You must make all settings as described in SAP Note 635244 (such as selection of the relevant lock characteristics) using transaction RSPLSE.