Diagnosis
If transaction data is requested in change mode, this data must beexclusively locked for a user. The data currently requested forplanning area '&V1&' (planning level '&V3&', planning package '&V4&')is already locked by user '&V2&'.
Background Information
The system locks the data that is described by the selection of theplanning package. However, the following rules apply in addition formanual planning:

• The selection comes from the planning layout for data columns and
individually defined rows in the planning layout.

• In the remaining cases the selection comes from the planning package.

If variables are contained in the planning level or planning layout,these are replaced for the determination of the selection.
Note that in Customizing, for variables of the type hierarchy node,attribute, and authorization, the replacement of variables can lead tomany individual characteristic values:

• For hierarchy nodes the system determines all characteristic values for
the hierarchy defining characteristic, which are contained in thesubtree and puts these in the selection.

• For attribute values the system reads the master data for the attribute
and puts this in the selection.

• For authorizations, the authorization object is read and the related
master data is read with the selection options of the authorizationobject. The master data is then transferred into the selection.
Very complex selections can be formed in this way, which lead to a highload on the lock server.

System Response
The requested data cannot be changed as long as another user has anexclusive lock on this data.

Procedure
Contact user '&V2&' if necessary, so that this user can leave theplanning transaction and thus release the locks.