Essbase ASO Version of BSO Dynamic Time Series

ASO does not provide an out-of-the-box version of dynamic-time-series (DTS) like its partner in crime, BSO. However, one straightforward approach to achieving this functionality is to implement a time aggregation dimension and leverage MDX functionality.  In this example, we will house the Time Periods/Months (i.e.:  Mar, Apr, May, etc.) and the Years dimensions into two separate dimensions.  We then add an additional dimension called “Time Series” to the outline to support our ASO version of DTS.

The Time Series dimension will consist of three sibling members: MTD, QTD, and YTD.  The data being loaded into our cube is always at the monthly/period level of granularity so for the MTD member no formula is required.  In the load rule file for the data load this column can load the simple value of ‘MTD’ since all data is loaded in at that level.

By adding in the MDX formulas below for the other two members, QTD and YTD, the final Time Series dimension should look like this:

MDX Forumulas

/*QTD*/
CASE WHEN IsLevel([Time Periods].CurrentMember, 0)
THEN
/* Add all values from the first sibling of the member to itself */
sum(PeriodsToDate ([Time Periods].levels(2),[time periods].currentmember), [scenarios].currentmember )
ELSE
/* Meaningless to ask for QTD for any other [Year].dimension member. */
Missing
END

/*YTD*/
CASE WHEN IsLevel([Time Periods].CurrentMember, 0)
THEN
/* Add all values from the first sibling of the member to itself from the first fiscal period */
Sum( [Mar]:[Time Periods].CurrentMember, [Scenarios].CurrentMember)
ELSE
/* Meaningless to ask for QTD foranyother [Year].dimension member. */
Missing
END

Conclusion

By leveraging an additional “Time Series” dimension we free up our cube to be completely sliceable and not restricted to a particular scenario or multiplied time dimension members in our time period dimension like some old-hat solutions.