Multiple hierarchy in TM1 dimension

[ralph007]

Hi All,

We using in company Cognos Express 10.1.1 version. For now we using TM1 and reporting using excel. I was asked to used some TM1 cube and rebuild one report for mobile customers in Report Studio (Active Report). I've done some training from IBM and practise on samples but in real data I have a problem in multiple hierarchy in dimensions. My actual 'Sales' cube we reporting to excel has 13 dimension (one measure and one time dim) almost all have multiple hierarchy. Could you please someone will suggest me how to best prepare TM1 cube to have clear and good structured data for build report in Report Studio please. For this report I need to build I don't need multiple hierarchies in the dimensions. Is the best way will be to build new dimension special for Report Studio reporting with one hierarchy and a new cube with only dimensions I need to specifies in Active Report? Or maybe I can use my actual 'Sales' cube and it's some other way to clear and prepare data for using it in Report Studio. 'Sales' cube structure attached.

Many thanks in advance for any suggestions.

Regards

Rafal

[jim wood]

Firstly I would define your hierarchy levels within TM1. Do this in the control cube: }HierarchyProperties

You'll also need to maintain it going forward. To do use the function outlined here:
http://pic.dhe.ibm.com/infocenter/ctm1/ ... N0274.html

[lotsaram]

For BI compatibility I always make sure that 1/ there is an overall "top element" for the dimension that all the actual top nodes of all the alternate hierarchies roll into and 2/ always have a hierarchy of "BI Rollups" under which are flat rollups of lists of elements to use in BI reports.

This makes the reports in BI much more efficient and easier to construct as you just point the row, column or filter list at the appropriate hierarchy rather than manual hunt and choose or some complex MDX.

The "BI Rollups" really serve the same purpose as a subset in a native TM1 interface. But as BI doesn't support subsets it is the best available workaround. Now WHY Cognos BI can't manage to support TM1 subsets some 6 or 7 years post acquisition is a good question.

[ralph007]

Hi,

Thanks guys for yours help. I've used }HierarchyProperties to define default members and levels.

Regards

Rafal