Data Slice and Distribution

[georg_meier]

I very often here that customer want to lock data but still want to distribute.

E.g. lets say you plan your sales for Region Europe and than distribute according to last years history down to the countries (UK, Sweden, Germany ...).

In the plan you lock Sweden using a data slide for some reason but the other countries are still open.

If you then change the plan on the level region and want to distubute accorting to the plan values without touching Sweden, it doesn't work because one member (sweden) is locked.

Any Idea or workaround?

thx

Georg

[former_member93896]

Hello Georg,

If you lock Sweden, then nothing can change Sweden data. I would say the data slice is working as designed.

So what is the business rule? Is it that some users are allowed to change Sweden data (using top down distribution) and other are not? What are the Swedish users saying when their data is changed by someone in the region? Do they want this? Do they allow this? How owns the data? Region or country?

Regards,

Marc

SAP NetWeaver RIG

[georg_meier]

it not the data for Sweden, that should still be locked. but the region distribution to all the other members should still be possible..

Lets say you plan for Region 100 and then distribute evenly to sweden25, germany25, france 25 and. denmark. 25. so for some reason you lock now sweden. Assume you overplan now the Region - 100 is now 130 - I would like now to distribute the delta (30) to germany france and denmark. so you will end up with sweden 25, germany 35 , france 35 and denmark 35.

As far as I understand a distribution funciton, they do not work if any characteristic in the selection is locked. So that would not work then.

[gregor_dieckmann]

Hi Georg,

I think here two concepts are mixed that should be clearly separated:

1. Protect a data area from being changed

2. Fix key figure values for algorithms as in a top-down distribution

The second point is natural in a UI with automatic top-down distribution and might be extended also to (some) planning function types. In the latter case it is unclear if to fix the value is a local (user specific and/or not persistent) or global setting. Maybe one needs both.

For scenario 1 dataslices can be used. If for the second scenario dataslices are the right design is unclear to me. If yes, one would need some flag in the planning function what to do if part of the selection is protected by a dataslice. It is obvious that this depends of the algorithm.

For scenario 2 there is nothing available yet. Of course, you can try to exclude 'Sweden' from the selection, but depending on the special application this may not be easy.

Regards,

Gregor

[georg_meier]

Hi,

that is exactly my issue. the combination of both. With a desired frontend locking (similar to BPS ) it would be able to temporary protect these value, even for just on kpi but I do not see a standard/unkomplex way to fullfill the requirement on the backend sind.

Thx

Georg