COGNOiSe.com - The IBM Cognos Community

Planning & Consolidation => TM1 => Topic started by: DavidSmith on 13 Jul 2010 12:55:25 PM

Title: YTD concept in TM1
Post by: DavidSmith on 13 Jul 2010 12:55:25 PM
HI
As a TM1 newbie I wondered how you get a YTD value in a cube

Assume I have a cube with the following dimensions, (which is a very common occurance):

P&L (Elements - Sales, Costs, Margin)
Months (Elements - Jan-Dec)
Versions (Elements - Actual, Budget, Variance)
YTD (Elements - Mth, YTD)

How do I get my months to Cumulate into YTD as EP would?

Cheers
David

Title: Re: YTD concept in TM1
Post by: MichelZ on 13 Jul 2010 02:10:06 PM
Hi David,

A common way to model this in TM1 is to create the YTD periods as rollups in the time dimension.
If you add roll-ups like Ytd Feb (consisting of Jan and Feb), Ytd Mar (consisting of Jan to Mar or consisting of Ytd Feb and Mar), etc. then the Ytd values will be automatically calculated from the data on the Jan to Dec elements.

Michel
Title: Re: YTD concept in TM1
Post by: DavidSmith on 13 Jul 2010 02:19:23 PM
Thanks Michel
So in effect you have a bigger dimension like:

Jan, Feb, ... Dec, Full Year, Jan Ytd, Feb Ytd ... Dec Ytd

One question though, how would you display something like this for Jan:

                  Mth                           YTD
          Act    Bud    Var          Act    Bud    Var
Sales
Costs
Margin

I suppose you could set up subsets and views, just with Jan Mth and Jan YTD, but that seems a bit fiddly
Cheers
David

Title: Re: YTD concept in TM1
Post by: raviB on 14 Jul 2010 05:12:54 AM
hI

Eeasiest (and most efficient) is to have 12 n type elements for the months.

Then you add consolidations for the YTD's.

YTD Jan is the sum of Jan.
YTD Feb is the sum of Feb and YTD Jan.
YTD Mar is the sum of Mar and YTD Feb.
And so on.
A TI process could create the structure but in the end, doing this manually is not the end of the world

You could also stick with 12 simple elements for the months, and use another dimension to have a Cumul element (calculated with rules). It's more heavy because of the rules. Yet, comparing months and YTD's is easier in a view if you do it like this.

Regards,
Ravi
Title: Re: YTD concept in TM1
Post by: DavidSmith on 14 Jul 2010 01:14:51 PM
Hi Ravi
Thanks for the reply
Yes, I understand that hierarchy is more efficient than rules

Assuming I did want to go the rules route, is there some kind of clever rule that can be used rather than coding each Cumul month to be the sum of the preceding months?

Thanks
David
Title: Re: YTD concept in TM1
Post by: Mehul on 15 Jul 2010 06:24:33 AM
Hi David,

You can use function like DIMNM & DIMIX for YTD.
For eg., you have a cube which have 2 dimensions
1 Months
2 Measures (Input & Result)

you can use the rule as

['Result']  = N: IF (DIMIX('Months_T', !Months_T) = 1, ['Input'], DB('YTD',DIMNM('Months_T',DIMIX('Months_T', !Months_T)-1), 'Result')+['Input']);

Mehul
Title: Re: YTD concept in TM1
Post by: dusherwo on 15 Jul 2010 07:31:35 AM
Dimix is not a good idea unless you can guarantee that you will be able to keep your elements in the order you expect. Next and Prior attributes are sounder.