Addressing levels in hierarchies #2

In the article (Addressing levels in hierarchies 1), I explained a few basic facts about addressing levels in a predefined hierarchy in TARGIT.

In this article I will take it a bit further – here’s the definition of a table with multiple attributes on the horizontal axis, none of them being a hierarchy – but together they make a custom hierarchy:


In terms of levels things are different now compared to a “real” hierarchy

  • Year – level 1 (now expressed(l(1,0))
  • Quarter – level 1 (now expressed(l(1,1))
    (but you don’t have to use any level parameters if you mean “the lowest level” – that’s default anyway)


The resulting table will look something like this:


So let’s make the same calculation as in the previous article (Addressing levels in hierarchies 1) and make a Year Growth calculation.

However the formula we used before (Sum(d2(l1),0,m1)-sum(d1(l1),0,m1)) will NOT work now. That’s because it’s a custom hierarchy.

The syntax will now be this: sum(d2(l(1,0)), 0, m1) - sum(d1(l(1,0)), 0, m1).

So what you can learn from this article and the previous one is that there’s a big difference between levels in predefined hierarchies and custom hierarchies.

More to come on addressing levels...

Was this article helpful?
1 out of 1 found this helpful



Please sign in to leave a comment.