"Lock" Actual Data in a forecast application

Post Reply
RN4ever
Posts: 3
Joined: Thu Oct 03, 2019 10:44 am
OLAP Product: Planning Analtycs
Version: 2.0.8
Excel Version: 2013

"Lock" Actual Data in a forecast application

Post by RN4ever » Sat Oct 05, 2019 6:09 am

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
MVP
Posts: 2259
Joined: Mon Dec 29, 2008 6:26 pm
OLAP Product: TM1
Version: PAL 2.0.8
Excel Version: Office 365 - latest
Location: Brussels, Belgium
Contact:

Re: "Lock" Actual Data in a forecast application

Post by Wim Gielis » Sat Oct 05, 2019 8:35 am

It’s called ElementSecurity.
Best regards,

Wim Gielis

Excel Most Valuable Professional, 2011-2014
http://www.wimgielis.com ==> 109 TM1 articles and a lot of custom code
Newest blog article: Set up a TM1 model with AutoHotKey as a service or application

tomok
MVP
Posts: 2631
Joined: Tue Feb 16, 2010 2:39 pm
OLAP Product: TM1, Palo
Version: Beginning of time thru 10.2
Excel Version: 2003-2007-2010-2013
Location: Atlanta, GA
Contact:

Re: "Lock" Actual Data in a forecast application

Post by tomok » Sat Oct 05, 2019 11:39 am

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.
Tom O'Kelley - Manager Finance Systems
American Tower
http://www.onlinecourtreservations.com/

RN4ever
Posts: 3
Joined: Thu Oct 03, 2019 10:44 am
OLAP Product: Planning Analtycs
Version: 2.0.8
Excel Version: 2013

Re: "Lock" Actual Data in a forecast application

Post by RN4ever » Wed Oct 09, 2019 12:50 pm

Thank you so much for your replies.

kangkc
Community Contributor
Posts: 194
Joined: Fri Oct 17, 2008 2:40 am
OLAP Product: TM1
Version: 9.x
Excel Version: 200x
Location: Singapore

Re: "Lock" Actual Data in a forecast application

Post by kangkc » Thu Oct 10, 2019 12:13 am

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
MVP
Posts: 2259
Joined: Mon Dec 29, 2008 6:26 pm
OLAP Product: TM1
Version: PAL 2.0.8
Excel Version: Office 365 - latest
Location: Brussels, Belgium
Contact:

Re: "Lock" Actual Data in a forecast application

Post by Wim Gielis » Thu Oct 10, 2019 9:35 pm

kangkc wrote:
Thu Oct 10, 2019 12:13 am
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.
Best regards,

Wim Gielis

Excel Most Valuable Professional, 2011-2014
http://www.wimgielis.com ==> 109 TM1 articles and a lot of custom code
Newest blog article: Set up a TM1 model with AutoHotKey as a service or application

User avatar
jim wood
Site Admin
Posts: 3748
Joined: Wed May 14, 2008 1:51 pm
OLAP Product: TM1
Version: TM1 10.2.2
Excel Version: 2007
Location: 1639 Route 10, Suite 107, Parsippany, NJ, USA
Contact:

Re: "Lock" Actual Data in a forecast application

Post by jim wood » Fri Oct 11, 2019 10:48 am

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.
Struggling through the quagmire of life to reach the other side of who knows where.
Application Consulting Group (ACG) TM1 Consulting
OS: Windows 10 64-bit. TM1 Version: 10.2.2

Post Reply