UDA vs Attribute Dimensions vs Alternate Hierarchies
We’ve all come across this question before as part of the Planning requirements and design – we have some additional information for a base dimension member, but which is the best way to represent this in our EPM Planning system?? All of the options are great, which makes it more difficult sometimes… so this blog will go through a few different example scenarios, which will hopefully help when deciding whether a UDA, attribute dimension or alternate hierarchy fits best. Firstly, let’s make sure we’re clear on the definitions of each option: UDA (User Defined Attribute) – an attribute which is tagged as a member property, which can then be referenced in other areas of the system. Attribute Dimension – a special type of dimension, which is tagged onto a base dimension, to provide additional information about each bottom level member for cross-reporting. Alternate Hierarchy – an alternate hierarchy sits within the main dimension, consisting of subtotals for each attribute which then ...