Sunday, May 31, 2009

Lock Concept and Lock Management

Use

When a user requests transaction data in change mode, this data has to be locked exclusively for the user. The data records that have to be locked are specified 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. It does not matter whether this data record is on the database.

The following rules apply:

All the 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.

Example

The 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, 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

Activities

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. For this reason, you have to make BI-specific settings for storing locks that are described by selection tables.

You access the BI lock management setting in the SAP Reference IMG (transaction SPRO) or in lock setting maintenance for planning (transaction RSPLSE). Sizing of the lock table used is necessary in order to use BI Integrated Planning. The sizing depends on the location of the lock table.


When implementing BI Integrated Planning, we recommend that you use an optimized lock concept for your planning application. This involves modeling selections in the components of the planning application in such a way that in change mode, different users can edit different objects.


Note that after you upgrade to SAP NetWeaver 7.0, BW-BPS also uses the lock settings of BI planning. This changes the setting for storing the lock table, making a sizing of the lock table necessary. Alternatively, you can store the lock table in the SAP lock server since the sizing of this lock table is performed 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.

1 comment:

seventyros said...

For a Excellent Online Resource for SAP EP and SAP Web Dynpro ABAP, Visit Learn SAP Online

Blog Archive