I'm looking at whether I can lock down a previous Version/s within Anaplan but continue to run multiple live versions, this would normally be where we have 1 standard live version but there may be a request for a scenario analysis off this live version. The process for a FP&A model would be:
- Create a Plan version before the beginning of the financial year which is allocated the 'Current Version' item and all formulas in Modules are set to 'Current Version' where appropriate
- Once the financial year has begun a rolling forecast version is created and the Current Version is switched to this version and the Plan version 'Edit From' & 'Edit To' are both set to 'None'. This effectively locks down the plan version & retains all the original values
- Management may request a scenario analysis at this point that branches off the current rolling forecast.
My understanding is that if you wish to lock down previous versions using the Formula Scope 'Current Version' method then effectively you can only ever have 1 live version at any moment (the Current Version) but I would require 2 live versions and also a locked down plan version.
I would imagine dynamic cell access is a perfect fit for this. Also, ideally you would never change the current version in Anaplan; this is a setting unavailable to users who are not workspace admins. So the rolling forecast/live forecast is always the Anaplan Current Version. Import actions can then update the other versions (again an option available to all users instead of just workspace admins). To 'lock down' the values, a simple checkbox with no dimensions providing only read access to the 2 Plan versions
Ok - so you are saying to keep the version 'Live' as in all the formulas are still operational but they will be protected by DCA? My definition of locked down is that the data no longer has formulas but the values remain
I think your idea is fine but it means you must have Version as a dimension on every driver (because it needs to remain static for the Plan version) and also you cannot really use List Properties as you require the ability to hold some data constant while others remain dynamic
@MarkTurkenburg I think the confusion here is that the solution that I and @ArunManickam are suggesting assume that you import the data from your rolling forecast version into the 2 other versions; the versions are then DCA controlled by a centralised DCA module
In other words, calculations do not run at all in the other 2 versions. This can be done using the formula scope on the driver modules by restricting to just Current Version
Thanks but I don't think that is relevant for my query. I'm wanting to lock down/hard code values in a version & I can't see how using a Fake Version dimension would assist in accomplishing that as you essentially you end up with the same problems as with the native Version dimension (see my last post to Arun)
I might be over-thinking it but I would imagine that a locked down/hard coded Plan/Budget version and then a Rolling Forecast version and possibly additional scenario analysis versions are required for a high percentage of FP&A models within the AP ecosystem. It obviously works fine if you only require 1 Live model as you can set the Formula scope to Current Version but once you move to greater than 1 live version it seems to become very difficult
What would be fantastic is the Formula Scope option to be able to set to a number of Versions, possibly referenced by a Boolean like with DCA. This would by-pass all of this
If my only option is DCA then I think it is better to create copies of the relevant modules, rename them Plan, remove the Version dimension and import the data from the Plan Version & then apply DCA. You can then to create modules for Variance analysis between the Version being analysed and your Plan but at least there is no chance that the plan numbers will change. It is far from ideal but currently that is my only solution
Just another point but very important, using DCA/Fake versions etc to lockdown a version means that you can not change the model structure - e.g. formula adjustments at any point will drive movements in your Plan version. Our models are constantly evolving as we seek to improve them and hence you need to be able to hard code your Plan version that may of been created 10 months ago, before multiple model adjustments have been made