Simple, logical and efficient Anaplan models contain hierarchies which are natural, intuitive and robust. Why then do we see so many that are overextended, too long and clunky?
Hierarchies in your Anaplan modelling allow your to formalise relationships between lists and dimensions. They enable you to declare and solidify parent and child mappings between adjacent dimensions and use these structures to create far more intuitive modelling processes, data flows and end user reporting.
Workspace capacity constraints are major issue for most Anaplan model designs. So, what can we do to minimise or mitigate the issue?
Here are a few design ideas we have implemented while working to redesign, redevelop and rebuild several large enterprise wide FP&A models for some of our global clients.
Twins are pretty rare. But we find they come in handy in our Anaplan modelling.
Twin lists or sometimes referred to as aliases or parallel lists are multiple individual lists which share a set of common properties and are therefore connected.
We have found that the most common uses for twin lists are the following…
Anaplan projects for FP&A fail when the model infrastructure has not been designed to be a natural fit with the model import data.
Anaplan projects for FP&A fail when the model infrastructure has not been designed to be a natural fit with the model import data. We have learnt this over the course of many health checks and model refurbs having seen the same mistakes made repeatedly across all sectors.
When building your lists and hierarchies in Anaplan what types should you use - flat, ragged or balanced?
When building your lists and hierarchies in Anaplan what types should you use - flat, ragged or balanced?
All of them!