Required Dimensions for a Hyperion Planning Application

Some people who are new to Hyperion Planning but have a little experience of Essbase ask me ‘what are the required dimensions for a Hyperion Planning Application?’

This isn’t something that’s too difficult to find in the documentation, but just to make it a little easier for the lazier of us, I’m going to list here the required dimensions for a Hyperion Planning Application.

Required Dimensions*

  • Period
  • Year
  • Scenario
  • Version
  • Entity
  • Account

Other Dimensions

  • Alias
  • Smart Lists

*multicurrency applications require two additional dimensions

  • Currency
  • HSP_Rates

Period and Year

You specify a time period and year for each value. Base time periods, such as months, are automatically rolled up to summary time periods, such as quarters and total year. As administrators, you specify base time periods and distribution of weeks in the Period dimension when you create application views. You use the year dimension to add years to the calendar.

Scenario and Version

The Scenario and Version dimensions represent the broadest categories of data in your application. Scenario describes the type of data that a plan includes, such as budget, actual, or forecast, as well as the time span that the plan covers.

Version allows for flexibility and iterative planning cycles. For example, your application could have two versions, Working and Final, for each scenario. You can also use versions to model possible outcomes based on different assumptions about interest rates, growth rates, and so on. For example, your application an have a Best Case and Worst Case version for each scenario.

Entity

The Entity dimension represents the flow of Planning information through your organization. You can establish an entity for each group or responsibility center that submits a budget plan. These units could be geographic regions, departments, or divisions, depending on your requirements.

Account

The Account dimension specifies the data to be collected from budget planners. You can establish accounts for all budgeted items to the necessary level of detail. Examples of accounts are Rent Expense and Cash on Hand.

Currency

You can plan in one or more currencies. The Currency dimension identifies the currency in which values are displayed. In the Currency dimension, you set up the following categories:

  • Which currencies are used by applications and reporting
  • How currencies are displayed in reports and data forms
  • How currencies are translated into other currencies
  • When currency conversion occurs

HSP_Rates

This dimension contains a member to store exchange rate values for each currency. It also contains a member for input values and currency overrides.

Alias and Smart Lists

In addition to the required Planning dimensions, you must set up an Alias dimension if you want to assign aliases to dimensions such as Account or Entity. If you want to use Smart Lists in your application, you must set up a Smart List dimension.

Technorati Tags: , , , , , , , , , , , ,

About these ads

11 thoughts on “Required Dimensions for a Hyperion Planning Application

  1. Alias:
    You can assign alternate names, or aliases, to Planning Account, Currency, Entity, Scenario, Period, Version, Year, and user-defined dimension members. Planning allows up to 10 aliases per dimension member, including the default alias.

    You can set alias tables to display members in applications. Planners can set alias tables in preferences.

    Smart List:
    Smart Lists are used to create custom drop-down lists that users access from data form cells. When a cell is clicked (whose members are associated with a Smart List – this is set as a member property), users can select items from the drop-down lists instead of entering data. Users may not type in cells that contain Smart Lists.

  2. Hi Shehzad

    Great to see this blog , I am learning Hyperion Planning. Can you please explain me how the multi currency is implemented in Planning. If yu can explain with an example it will be really helpful for me . Specially I want to know , what is stored in Hyperion Essbase Outline , what we will do in Planing web to achieve the multy currency functionality.

    Thank You

    • Thanks Suhail,

      My suggestion would be to download the Hyperion Help Documentation. You will find the administrative guides and user guides very helpful in understanding how a multicurrency application works.

      You should also install it in a test environment where you can juggle around with it and get some experience with the product. It’s always helpful.

      Shehzad

    • An account dimension is where you store all the measure. Where else would you put your staff costs GL accounts, or store the headcounts, or store any other workforce related information.

      I think you would need to be a bit more specific by what you mean by employee details. If you mean information related to employees, then that goes into the account dimension like the employee status, workforce GL codes, attributes, employment start date and there is an endless list for that.

      • The default dimensions for workforce planning are:
        Account
        Entity
        Period
        Year
        Version
        Scenario
        Employee

        By employee details i mean general employee information, like ename, eid. we have employee dimension but it does not have these members.
        can you please give details about all dimensions only in terms of workforce. Like where the performance should be added.

        Thanks

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s