Data Locks

[Former Member]

Hi ,

We have two Planners, X planner uses different key figures than Y Planner, but when X selects a very high level selection like sales org level, Planner Y cannot go into change mode and do his forecasting.

I was thinking if having two planning areas (Same planning Object structure)will help reduce such data locks. Or will that increase memory to a very large extent.

Another point is that if the third person wants to view a small selection he might also get into the same trouble.

Please suggest if there is any simple way that we prevent data locks between people.

Thanks,

My

[Former Member · Accepted solution]

If you are using SCM 5.0..

Please check following details is useful for you..

Locking Logic in Demand Planning (DP) (Enhanced)

Use

As of SAP SCM 5.0, the new locking logic liveCache Lock is available in Demand Planning (DP). The system can use this logic to more precisely lock data you are accessing than it can with the aggregated and detailed locks. The liveCache lock takes intervals into account during selection and evaluates for single values the first wildcard character (*) or the first placeholder for each value. You can activate the liveCache lock in planning area maintenance on the Locking Logic tab page. You can activate the liveCache lock together with the key figure-specific lock.

[Former Member]

if you are going to use the same planning area.....

use livecache level locks and use the option that says " do not lock read only KF"

now in the design of the planning book make both the KF read only

use a macro to make the KF editable (KF X or Y only depending on the book) and only just before you do some activity of say entering data

[srinivas_krishnamoorthy]

Unlike SNP, DP uses exclusive Lock logic. I would suggest to first try of Key-Figure specific lock setup in the Locking Logic section of planning area design works for you. I am honestly uncertain if this will work. However, I am still not sure about the design. When you say different key figures at different level - are you saying even history key figures are different ? The locking is usually placed at CVC level for DP to work correctly. A CVC lock would logically include lock on History and Forecast key figures. History key figure can aggregate up to higher level and hence at higher level it may not be possible to place a lock for doing forecasting if someone else is forecasting at lower level.

I doubt there is a easy way around it. However you can introduce little business process change by asking planners to look into Lock Entries on the Planning book menu bar to make sure there are none in their area.

A little messier way would be to introduce another characteristic like PLanner ID or higher level aggregation characteristic with which CVC specific lock should work.