Hello,
I have a time dimension with the following structure; Year - Qtr - Months. The other years have the same level of detail as does 2011. I'd like to now have YTD rollup's. Is it best practice to have the YTD's within each year? And would the "YTD's" be at the same level as the Qtr's?
2010
2011
Q1
Jan
Feb
Mar
Q2
Apr
May
Jun
Q3
Jul
Aug
Sep
Q4
Oct
Nov
Dec
Proposed change;
2011
+Q1
+Q2
+Q3
+Q4
YTD Jan
Jan
YTD Feb
Jan
Feb
YTD Mar
Jan
Feb
Mar
+YTD Apr
+YTD May
+YTD Jun
+YTD Jul
+YTD Aug
+YTD Sep
+YTD Oct
+YTD Nov
+YTD Dec
Thanks,
Tony
YTD in TM1 Time Dimension
-
- Community Contributor
- Posts: 211
- Joined: Tue Sep 15, 2009 11:13 pm
- OLAP Product: IBMPA
- Version: PA 2.0 Cloud
- Excel Version: 2010
Re: YTD in TM1 Time Dimension
If you are using Report Studio C8 then I prefer the levels to be balanced, therefore your leaf node members will only be at the lowest level. In TM1 level 0 is always leaf node, while in C8 level 0 is your top node and you count down from there
GG
-
- Posts: 59
- Joined: Mon Jun 02, 2008 8:49 pm
- OLAP Product: TM1 Palo
- Version: TM1 9.x Palo 3.2
- Excel Version: 2003 2007 2010
Re: YTD in TM1 Time Dimension
Cardantim,
In TM1 all dimension members need to be unique. Therefore in order to have year specific YTD roll ups you need to have year specific months & quarters.
E.g.
2011
----2011-Q1
--------2011-Jan
--------2011-Feb
--------2011-Mar
2012
----2012-Q1
--------2012-Jan
--------2012-Feb
--------2012-Mar
Your users might (mine do) find it easier to see the months once they expand the YTD roll up, instead of a long chain of YTDs rolloing up.
2012-Mar-YTD
----2012-Jan
----2012-Feb
----2012-Mar
2012-Mar-YTD
----2012-Mar
--------2012-Feb-YTD
------------2012-Feb
----------------2012-Jan-YTD
--------------------2012-Jan
YTD roll ups do not have to be at the same level as Qtr roll ups. However, once again this depends on your reporting requirements and reporting tools.
In TM1 all dimension members need to be unique. Therefore in order to have year specific YTD roll ups you need to have year specific months & quarters.
E.g.
2011
----2011-Q1
--------2011-Jan
--------2011-Feb
--------2011-Mar
2012
----2012-Q1
--------2012-Jan
--------2012-Feb
--------2012-Mar
Your users might (mine do) find it easier to see the months once they expand the YTD roll up, instead of a long chain of YTDs rolloing up.
2012-Mar-YTD
----2012-Jan
----2012-Feb
----2012-Mar
2012-Mar-YTD
----2012-Mar
--------2012-Feb-YTD
------------2012-Feb
----------------2012-Jan-YTD
--------------------2012-Jan
YTD roll ups do not have to be at the same level as Qtr roll ups. However, once again this depends on your reporting requirements and reporting tools.
-
- MVP
- Posts: 3701
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: YTD in TM1 Time Dimension
To lend some weight to the above although it might be "easier" to build YTD rollups by adding each prior YTD plus the current period as children this is bad practice as it results in hierarchies that are non-intuitive for end users to navigate and for weekly or daily time dimensions it results in an extremely deep structure in terms of the number of levels. Also most other reporting tools require balanced hierarchies which IMO makes goods sense to adopt for time dimensions as it is certainly one (or more) dimension(s) where the level (at least within a hierarchy) can and should have a relative meaning.