Thursday, April 17, 2008

Hyperion Planning tips: entry 1

From time to time I stumble upon little tweaks that greatly affect deliverable functionality in planning. This is the first blurb in a series that will be updated over time. These apply to hyperion planning p1. Most of these tips probably work with 9.2 as well but I can't confirm or deny.

  1. -enabling YTD dynamic time series in planning
  2. -creating alternate period rollups
  3. -use of substitution variables
  4. -top of dimension properties in planning
    1. storage properties can be set
1. enabling YTD dynamic time series in planning:
In order to use ytd dynamic time series you must first rename the year dimension to something else. I tend to use Years. Year is a reserved word and using this as your dimension name will prevent you from being able to perform dynamic time series.

2.creating alternate period rollups:
If you'd like to create your own alternate period rollups you can now do this on the planning side and push them into essbase. You could make your own ytd rollups, qtd rollups or what ever you dream up. While adding them in the web interface it's a little painful as it's not too easy to reorder the members but it does work.

3.use of substitution variables:
We can now use substitution variables inside of member formulas. This applies to essbase as well as planning and probably came out with maybe system 9. This is a huge step forward and might effect every business rule you develop going forward. It could be used for the processing of the current budgeting period, forecast year, or anything you can dream up. I'm a little embarrased that I didn't stumble upon this (co worker tried it and told me it worked. I still didn't believe him) earlier. I need to spend more time reading the release notes.

4. top of dimension properties in planning:
storage properties can be set:
Now you can utilize some of those essbase skills in tuning a database. We can now set the storage property of the top dimension nodes. While we've probably all created our own work arounds to reduce blocks, this makes it a lot easier to "tighten up" our databases while working within the planning infrastructure.

as always feel free to correct me or better yet, send in some tips that you've stumbled upon..

you can contact me anonymously at



Anatoliy said...

I need an efficient way of extracting the Essbase outline and wotk on it.

Is there a tool that can allow this ?

thank you

Naresh Yeddula said...

Hi Anatoliy,

you can get a good Essbase Outline Extractor from Applied OLAP below is the link

g said...

Yes, we have a tool called Essbase Outline Extractor to extract the essbase outlines.

Its very good tool to extract.

It will extract all members, properties, consolidation operators,storage properties, etc