Adhoc Analysis within Hyperion Planning

I was trying to be creative and think up of ways to show the analytical capabilities of the Hyperion Planning system to demonstrate to a client (who had strongly suggested that these capabilities would play a very important role in their evaluation of a budgeting and planning solution) and came up with one approach that I’d like to share here.

The overall scenario is as follows:
The business user goes to the specific what if analysis form where they can select an account for analysis. The selected account is basically the parent account for the hierarchy that needs to be analysed.
From there they can punch in their percentage variances for each of the Level 0 accounts that are within the hierarchy of the selected account to see the impact of the each of each across the entire hierarchy.

Implementation:
I created the following structures

Scenario

  • Actual
  • Budget
  • What If Scenarios
    • Budget for What If
    • Worst Case
    • Average Case
    • Best Case

There is another dimension that is important here is to be able to identify the account types. I already had an AccountType dimension within my demo application structure. The following structure was introduced in the AccountType dimension

AccountType

  • NoAccountType
  • What If Types
    • Percentage Change {StoreData,Percentage}
    • Calculated Value {DynamicCalc,Undefined,”Budget for What If”->NoAccountType * (1 + “Percentage Change”)}
    • Percentage Variance {DynamicCalc,Percentage,(“Calculated Value” – “Budget for What If”->NoAccountType) / “Budget for What If”->NoAccountType}

The form for the What If analysis is a composite form consisting of an input form for the percentage change input and the variance analysis.

Input Form:
The row for Input Form contains Level 0 account members with suppress missing values
The col for Input Form contains Budget for What If->AUD, Worst Case->Percentage Change, Worst Case->Calculated Value, Avg Case->Percentage Change, Avg Case->Calculated Value, Best Case->Percentage Change, Best Case->Calculated Value

Analysis Form:
The row for Input Form contains top member of the account hierarchy with suppress missing values and expandable
The col for Input Form contains Budget for What If->AUD, Worst Case->Percentage Variance, Worst Case->Calculated Value, Avg Case->Percentage Variance, Avg Case->Calculated Value, Best Case->Percentage Variance, Best Case->Calculated Value

To support all this a few Business Rules are in place

Set Target Account
Prompts
The BR prompts the user for selecting target account(s).
Business Logic:
Set all level 0 accounts for “Budget for What If” as #missing
Copy value from “Budget” into “Budget for What If” for @RELATIVE(TargetAccount,0)

Clear Analysis
Prompts
The BR prompts the user for selecting scenario(s) {Member(s): Worst Case, Avg Case, Best Case}.
Business Logic:
For all selected scenario(s) use CLEARDATA

Accept Analysis
Prompts
The BR prompts the user for selecting scenario {Member(s): Worst Case, Avg Case, Best Case}
Business Logic:
For selected scenario and Level 0 Accounts
“Budget” = selected scenario->Calculated Value

Advertisements

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