hello i wanna ask ... like Fact table logic in click view... can we do that in IBM COGNOS TM 1 ?
thank you
fact table
-
BariAbdul
- Regular Participant
- Posts: 424
- Joined: Sat Mar 10, 2012 1:03 pm
- OLAP Product: IBM TM1, Planning Analytics, P
- Version: PAW 2.0.8
- Excel Version: 2019
Re: fact table
I honestly don't know what you are asking here.Fact table is one of the data warehousing concept which holds the measures or metrics,Similarly we have measure dimension where we usually have measures and it is mostly last dimension of the cube.Other than that,Please elaborate your question ,which is quite vague and generic.Thanks
"You Never Fail Until You Stop Trying......"
-
Duncan P
- MVP
- Posts: 600
- Joined: Wed Aug 17, 2011 1:19 pm
- OLAP Product: TM1
- Version: 9.5.2 10.1 10.2
- Excel Version: 2003 2007
- Location: York, UK
Re: fact table
So if you are talking about a star-schema structured fact table in a dimensionally modeled relational warehouse (Kimball style) then TM1 does most of this intrinsically.
A Dimension in TM1 corresponds to the dimension table in the star schema. The key difference is that whereas the individual levels of the star schema dimension are represented as separate fields of the table, in TM1 the only thing we have are items and parent-child relationships, and so all members of all levels are individual items. If you search around, particularly in packages like Bedrock, you will find turbo-integrator scripts that will convert a relational star schema dimension to a TM1 Dimension. Furthermore the TI wizard is designed to facilitate this. Whether it succeeds or not is a matter of debate.
A Cube in TM1 corresponds to a star-schema fact table. The members of the last Dimension of the cube are special. They represent the facts of the fact table. The other dimensions should be the normal dimensions of the star-schema. Time is also different. You need to decide at what grain to aggregate time and represent those periods in a dimension, again with the hierarchical structure as part of the dimension.
The data is held sparsely in the cube and aggregation to each level is done automatically when reading from the cube. It is useful to define subsets on the dimensions to represent the levels of the hierarchy. This will allow easy querying of the data aggregated to any combination of levels on the dimensions.
Hope this helps.
A Dimension in TM1 corresponds to the dimension table in the star schema. The key difference is that whereas the individual levels of the star schema dimension are represented as separate fields of the table, in TM1 the only thing we have are items and parent-child relationships, and so all members of all levels are individual items. If you search around, particularly in packages like Bedrock, you will find turbo-integrator scripts that will convert a relational star schema dimension to a TM1 Dimension. Furthermore the TI wizard is designed to facilitate this. Whether it succeeds or not is a matter of debate.
A Cube in TM1 corresponds to a star-schema fact table. The members of the last Dimension of the cube are special. They represent the facts of the fact table. The other dimensions should be the normal dimensions of the star-schema. Time is also different. You need to decide at what grain to aggregate time and represent those periods in a dimension, again with the hierarchical structure as part of the dimension.
The data is held sparsely in the cube and aggregation to each level is done automatically when reading from the cube. It is useful to define subsets on the dimensions to represent the levels of the hierarchy. This will allow easy querying of the data aggregated to any combination of levels on the dimensions.
Hope this helps.
-
David Usherwood
- Site Admin
- Posts: 1453
- Joined: Wed May 28, 2008 9:09 am
Re: fact table
Without breaching the commercial promotion rules, there are at least two products in the marketplace which will make TM1 data available to Qlik.