Handle Same Leaf values in different hierarchies of same dim

[David331]

Hi,

I have a dimension to handle which has the leaf level value E.g. XYZ present in both the hierarchies of same dimension. When I run the TI Process with the load file for a period, the measure value is getting doubled in the cube. The measure value is 47 in one hierarchy and value of 1 in other hierarchy. But in the Cube a total of 48 is getting populated in both the hierarchies.

Lets say the original hierarchy as (A -> B-> C) where C is the leaf level element in the dimension. I am thinking to create a new dimension for A and keep the rest hierarchy as ( B -> C), as the load file is now added with the column A. Will this approach solve my issue. Any ideas ??


Regards
David

[rmackenzie]

Perhaps you should post a picture of the cube view that shows the 1, 47 and 48 and both the dimension with multiple hierarchies and the measure dimension in the grid. A picture can speak a thousand words...

[Michel Zijlema]

Hi,

I have a dimension to handle which has the leaf level value E.g. XYZ present in both the hierarchies of same dimension. When I run the TI Process with the load file for a period, the measure value is getting doubled in the cube. The measure value is 47 in one hierarchy and value of 1 in other hierarchy. But in the Cube a total of 48 is getting populated in both the hierarchies.

Do you have a top level element grouping the two hierarchies and is it this top level you're looing at when you're mentioning the cube total? In that case the sum of both hierarchies is shown. If an element is used twice anywhere underneath the same node, the element will count twice in that total.
If you need to have a total top level element grouping two hierarchies, you could have a look at the weight of the elements in the consolidation - you could f.i. give the total element of hierarchy 1 a weight of 1 in the roll up to the overall top level element and the total element of the 2nd hierarchy a weight 0 in that consolidation. This way only the 1st hierarchy will consolidate it's value to the overall top level element.

As Robin mentioned, a screenshot of the regarding dimension would be helpful.

Michel

[Duncan P]

Are the two XYZ different leaves with the same name but distinguished by the hierarchy path in which they appear. TM1 does not naturally handle this. A name has to be unique across the whole dimension. So XYZ is in each case referring to the same leaf and the values are being added.

A way round this is to generate a unique element name based on the hierarchy path. So if you have

Code: Select all

US      Texas  Paris
Europe  France Paris

your element names could be US-Texas-Paris and Europe-France-Paris.

Another way is to assign modified names to elements the names of which appear in some other path, e.g. Paris and Paris~1.