Show TOC

Selecting Lock CharacteristicsLocate this document in the navigation structure

Use
On the Lock Characteristics tab page, you can specify which characteristics are used for the lock check.
  • In the default setting, all the characteristics and the artificial characteristic 1KYFNM, for a real-time InfoCube and for a local provider in BW Workspace, are relevant for the lock check.
  • In a DataStore object for direct updates in planning mode, all the characteristics in the default setting for the lock check are also relevant. However, the artificial characteristic 1KYFNM is not available. This means that data in DataStore objects in BW-integrated planning is always locked, regardless of the key figures used in the planning function or input-ready query.

To reduce the size of the lock table, you can exclude characteristics that do not divide lock selections from the lock check. These include characteristics that are the same for all users or have overlapping values.

If no characteristics are selected as relevant, the whole InfoProvider is locked.

Activities

Select lock characteristics

  1. To switch to change mode, choose .

  2. Select an InfoProvider. In the default setting, the Lock Characteristic Selection is empty, as all the characteristics are relevant.

  3. Press Enter. Under Lock Characteristics, the system displays all lock characteristics that are currently selected.

  4. Remove any characteristics that are not relevant for the lock check from Lock Characteristics .

    Example

    In cost center planning, the Fiscal Year, Version, Cost Center and Cost Element characteristics are used. If a number of users are performing planning for the same year and the same cost elements, the Cost Center and Version characteristics are sufficient to ensure that different users' selections do not overlap. Only set these characteristics as relevant for locking.

Select navigation attributes as lock characteristics

In the default settings, navigation attributes are not relevant for lock checks. This means that they are always completely locked. In some cases, setting navigation attributes as lock characteristics can reduce the size of the selection tables. You could use selections based on a product group for example instead of selections based on an extensive list of products belonging to the product group.

In expert mode, you can add navigation attributes to the list of lock characteristics.

Note

You use ok_code EXPERT to activate expert mode and NOEXPERT deactivate it.

Caution

Make sure that no navigation attribute values are changed during planning. Otherwise, two different users can both edit the same values of the related basic characteristic, thus writing new delta records.

User 1 plans product P1, which is in product group (navigation attribute) PG1. PG1 is selected in the selection table, and no restriction has been set for Product. If the product group is used to set the lock, the following situation might arise: User 2 plans product group PG2: User 1 starts planning first; the system locks the data. During this time, the attribute of product P1 is changed from PG1 to PG2. User 2 starts planning. Since PG2 is now technically different to PG1, there is no lock conflict. Both users can plan key figure values for product P1.