"Lock" Actual Data in a forecast application

[RN4ever]

Hi all,

I developed a simple forecast application where I load actual data from data warehouse and I allow users to insert budget data in order to calculate forecast.

I know that is possible "lock" cells related to actual data but I can't find how I can obtain this (perhaps I don't know the correct keywords in my google search)

I also believe is a common requirement and probably you've talk about this in the forum.

Can you help me, please?

Many thanks in advance

[Wim Gielis]

It’s called ElementSecurity.

[tomok]

Element security is the most common way but if you want to protect Actuals from everything, including Admins and TI processes, then you can LOCK it. Open the dimension, select Actuals, right-click and select Security, Lock. Now no one will be able to change Actuals. BTW, you can also lock and unlock via a TI process.

[RN4ever]

Thank you so much for your replies.

[kangkc]

The usual way I do it is via cellsecurity with rule referencing a locking cube which manages which months are actuals for respective forecast scenario.
With that you have full flexibility of controlling.
Note that this will not work under TI which runs under Admin context and you will need to put in addition code in TI to check the locking cube.

[Wim Gielis]

The usual way I do it is via cellsecurity with rule referencing a locking cube

Indeed. Add to that a cell security cube with less (only the relevant) dimensions and you are good to go.

[jim wood]

The way I've done it in the past and do at the current client is to have actual and forecast as seperate versions. Have an actual flag on the time dimension, then pull via rules actual data in to forecast when the flag is set. This way you lock the actual periods via rules (no security needed) and you can complete a rolling forecast if your requirement changes. Just then set element security for the actual version to read and you're done. Doesn't involve any cell level security.