Topics Map > University of Chicago > IT Services > Business Systems > Budget Planning & Mgmt > Delphi

Budget Planning and Management - Delphi Planning - Data and Dimensions

This article describes how Delphi (Hyperion) Planning uses Essbase to store data and metadata.

Dimensions and Data

Delphi Planning uses Hyperion Essbase to store planning data you enter, as well as metadata and business rules. Essbase is also the calculation engine for all of your Delphi Planning reporting and analysis activity.

Planning Repository and Essbase

Dimensions and members are stored in both the Essbase database and the Delphi Planning repository. Data values are only stored in Essbase.

Metadata and Dimensions

Metadata

Metadata are the structural elements of an application that describe and hold data. Examples of metadata are dimension names, member names, and properties.

Dimensions

Essbase stores data for Delphi Planning applications in a database defined by dimensions. A dimension is a structural way of storing data. Dimensions represent the core components of an application, and are used to categorize every line item and their aggregation. The UCSAL and UCBUD applications use many the same dimensions, but each also has some unique dimensions of its own. See below for a table that summarizes the dimensions.

Dimensions also represent the combination of all data elements. Therefore, one record equals the combination of all dimensions within an application. All data loaded must have each dimension represented in order load correctly. It is important that to always book all data to the correct dimensions combinations for accuracy and easy data drill-downs.

This is an estimated number based on a point in time before Go-Live as the structure will change for some dimensions as part of the ETL Process, such as Account6, SubAccount and Employee.

Summary of Delphi Planning Application Essbase Dimensions


UCBUD

UCSAL

of Members

Year

11

11

FY10 to FY19

Period

19

19

Qtr1, July

Version

27

8

1st Draft

Scenario

15

4

Actual, Budget

Account6

22550

2146

FAS_10, 457000_V01

Sub-Account

4248

129

SL1100

View

398


OBS View, Board View

Employee


10483

Employee Name & Number

Job Title

 

2282

Administrator

Measures

 

21

Ledger 5 Benefit Rate


These structural elements are the application's dimensions. The elements that comprise a dimension are called members. For example, Salary and Expenses are members of the Account 6 dimension. Data is always stored with a member from each dimension. For example, $10,000 in business meal expense for June 2014 might be stored with the following dimension representations in UCBUD Application:


UCBUDDimensions


Likewise, $15,000 in benefits expense for June 2014 might be stored with the following dimension representations in UCSAL Application:

UCSALDimensions

In some cases, if there is no appropriate dimension member from a particular dimension, a generic member option is available, e.g. No SubAccount

Data in Dimensions

Data is entered into the base-level members of the dimensions, not into the parent members. The values for the parent-level members aggregate from the values of their children. For the dimension above (the Period Dimension) data can only be entered for the months, Jan or Feb and then will aggregate to the Qtr or Year Level.

Period Dimension

YearTotal

  • Quarter 1
    • Jul
    • Aug
    • Sept
  • Quarter 2
    • Oct
    • Nov
    • Dec
  • Quarter 3
    • Jan
    • Feb
    • Mar
  • Quarter 4
    • Apr
    • May
    • Jun



Keywords:Hyperion, Essbase, UCSAL, UCBUD, Executive, Budget_Office   Doc ID:28587
Owner:Levita G.Group:University of Chicago
Created:2013-02-12 11:08 CDTUpdated:2017-03-15 15:23 CDT
Sites:University of Chicago, University of Chicago - Sandbox
Feedback:  0   0