We can get the data from lower level to higher level by applying SUM or LOOKUP.
But if we already have data at higher level and want to get at the lower hierarchical level, how should we do it?
@Soumyajaiswal
First, SUM is not required if you are aggregating the data from lower level of hierarchy to the Highest Level. It will auto aggregate.
Second: In order to do the Top down approach we generally use LOOKUP. But you need to set a logic right as in how are you going to dis aggregate the data . For example If you have one Region and under that region you have got 3 areas
A1
A2
A3
R1
Let's say Region has got 100 as a value in it. Now you need to figure out how are you going to dis-aggregate this 100 into 3 areas. You can use Prior year actual's ratio or you can set up your own distribution ratio. In your area module you use LOOKUP functionality and multiply that with your ratio.
Or else if you simply want to pull down 100 in each Area use Simple LOOKUP on your Region and it will pull the value 100 in each area
Hope that helps.
Misbah
Hello everyone, We are trying to use Anaplan Connect in order to push data from a dwh to Anaplan Data Hub. To do so, we need an authentication by token. We can't make it work, we receive the following error: ERROR 16020 |-- Anaplan API: Invalid key path Any suggestions? Thank you all in advance for the help! Michele
I am attempting to connect to an azure SQL database vis at the MSSQL connector in data orchestrator but am having issues and I believe it is due to hyphens in database name (which is a fairly standard naming convention I will note!) Example below (fake credentials) - has anyone else encountered similar and is there a way…
Has anyone found success using Anaplan XL with Polaris models in a shared drive with or without concurrent users? My team has experienced a variety of errors, login failures, etc. sometimes it works, sometimes it doesn't. We've been recommended to save and edit files locally, which helps but certainly with its limitations…