Diagnosis
If transaction data is requested in change mode, this data must beexclusively locked for a user. The lock server is currently processingother lock requests for planning area '&V1&' and can therefore notanswer the current lock request.
When this situaton occurs the system waits for a number of seconds andand then starts the lock request again. The lock server could still notanswer the request even after this waiting time.

System Response
The requested data cannot be edited in the change mode at present.

Procedure
If this lock message occurs often then this points to a general capacityoverload of the lock server.
As a rule, the situation can only be avoided by making selectionssimpler. Consult note 635244 on this.
Background Information on Locks
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 of the lock server.