Clarification on the Generation Level when Setting up Dynamic Time Series (DTS: YTD, QTD,..) for Hyperion Planning
Last updated on JULY 28, 2016
Applies to:Hyperion Planning - Version 22.214.171.124.00 to 126.96.36.199.000 [Release 9.3 to 11.1]
Information in this document applies to any platform.
YTD settings when made to Generation 3 for EPMA application or classic Planning application do not calculate properly:
In the Essbase Admin guide under 'Retrieving Period-to-Date Values' the following example is given:
Jan -> 10
Feb -> 100
Mar -> 100
Apr -> 8644
May -> 8929
Jun -> 9534
Q-T-D(May) displays the period-to-date value for May that is obtained by adding the values for Apr and May (8644 + 8929 = 17573).
In the Planning Admin guide section on Dynamic Time Series it states:
You can use Dynamic Time Series (DTS) members to create reports that show period-to-date
data, such as quarter-to-date expenses. DTS members are created automatically during
application creation, and can be used with members of the Period dimension. To set up DTS,
you enable a predefined DTS member and associate it with a generation number (and, optionally,
an alias table and alias name). For example, to calculate quarter-to-date values, you can enable
the Q-T-D member and associate it with generation number 2. You can then use the Q-T-D
DTS member to calculate monthly values up to the current month in the quarter.
However if the QTD is setup in Planning to generation 2 to calculate QTD(MAY), Planning adds all the months from Jan to May which seems to be wrong and in contradiction to what is stated in the Essbase admin guide.
So using QTD(MAY) will give in Planning Jan + Feb +...+May = 17783 instead of Apr + May = 17573
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms