1

Safe Harbor Statement

The following is intended to outline our general

product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracles
products remains at the sole discretion of Oracle.
 Oracle Training Materials Usage
Agreement
Use of this Site (Site) or Materials constitutes agreement with the following terms and conditions:

1. Oracle Corporation (Oracle) is pleased to allow its business partner (Partner) to download and
copy the information, documents, and the online training courses (collectively, Materials") found on this
Site. The use of the Materials is restricted to the non-commercial, internal training of the Partners
employees only. The Materials may not be used for training, promotion, or sales to customers or other
partners or third parties.

2. All the Materials are trademarks of Oracle and are proprietary information of Oracle. Partner or other
third party at no time has any right to resell, redistribute or create derivative works from the Materials.

3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any

Materials. Materials are provided "as is" without warranty of any kind, either express or implied,
including without limitation warranties of merchantability, fitness for a particular purpose, and non-
infringement.

4. Under no circumstances shall Oracle or the Oracle Authorized Delivery Partner be liable for any loss,
damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site
of Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against
any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys'
fees) arising out of Partners use of the Materials.

5. Reference materials including but not limited to those identified in the Boot Camp manifest can not be
redistributed in any format without Oracle written consent.
Qubix International Limited

2011 Qubix International Limited

Oracle Hyperion Planning
Implementation Boot Camp - Objectives

Overview of Oracle EPM System, Essbase and

Hyperion Planning - architecture, future direction,
components and common terminology
Understanding of what you need to know to implement
and manage Hyperion Planning applications
Focus on hands-on Lab Exercises and Implementation
Case Study to reinforce concepts and understanding
Deep dive discussions into the inner workings of
Essbase and Hyperion Planning
Collaboration and sharing of Best Practices
 Oracle Hyperion Planning
Implementation Boot Camp - Agenda

Day 1 Overview of EPM System, Planning and

Essbase, hands-on Essbase exercises
Day 2 Essbase Data Loads and Calculations
Day 3 Planning Application Set-up and Modeling
Day 4 Planning Data Form Design and related topics
Day 5 Security, PUH, Life Cycle Management
 Course Note Approach

The approach to teaching Planning is to familiarise

students first in multi-dimensional thinking.
Understanding the Essbase fundamentals is
essential.
Hands on learning during the course is through
practical real world scenarios and exercises.
This course does not address the installation of the
product or the operating system, server setup, and
network requirements involved in a typical
implementation.
 Course Note Course Material

The designed flow of this boot camp is to present the

content highlights in Powerpoint deck or via
demonstration and then to go to the software for
viewing, examination, and exercise
The exercises are structured, but additional time will
be provided to allow students to explore the topics
further as they see fit. An experienced consultant will
support the students in the various directions they go
and suggest practical solutions to address questions.
Software screen shots are included in the materials;
however, the students learning will progress by direct
usage of the software, not through reliance on just the
screen shots.
 Introductions

Name / Company / Location

Previous Experience with Hyperion/Oracle?

Specific Topics you want to make sure we cover?

Share something most people dont know about you.

 Oracle Hyperion Planning
Implementation Boot Camp
Discussion / Presentation

Presenters Name
Presenters Title
 Day 1 Objectives

Oracle EPM Overview & Essbase Architecture

Multidimensional/OLAP/Essbase concepts and
terminology
Building Essbase application
Reporting using Smart View for Office
Oracle EPM System
Architecture
Oracle EPM System
 Critical Components to Implement
Planning Best Practices

Predictive Modeling & Simulation

Functional Plans

Long-Term Project Operational

Workforce Capital Assets Planning
Financial Revenue & Cost
Planning Planning
Planning Modeling
Marketing
Planning

Planning, Budgeting & Forecasting

Forward-looking Analytic Engine

Financial Operational
Detail Detail

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Oracle BI Server Aggregate Persistence
Autogenerate Essbase and Oracle OLAP Cubes
HFM and Hyperion Planning as a
Source to OBIEE 11g
Application Integration Strategy
Oracle BI and Performance Management Applications
BI Tools Matrix
Best Fit Recommendations - 2008
BI Tools Matrix
Best Fit Recommendations With OBIEE11g
What is OLAP?
Essbase Basics
 What is OLAP, OLTP vs OLAP

OLTP OLAP
Purpose Automate the business Optimize the business
Reporting, Analysis, Modeling,
Use Transaction Processing Planning
Schema Two-dimensional, Normalized Multi-dimensional, Hierarchical
Based on way users perform
Navigation Based on transaction workflow analysis
Aggregation, Matrix, Cross-
dimensional, Formula,
Calculation Aggregation, Simple Matrix Procedural
Slow to deploy, and difficult to Fast to deploy, and easy to
Implementation change change
 What is OLAP? (cont.) Vocabulary

Dimension Cube

Member Slice and Dice

Hierarchy Cell

Attributes Calculations
What is OLAP? (cont.) Dimension
Dimension A data category used to organize
business data for retrieval and preservation of values.
Dimensions usually contain hierarchies of related
members grouped within them. For example, a Year
dimension often includes members for each time
period, such as quarters and months.
What is OLAP? (cont.) Member
Member A discrete component within a dimension.
A member identifies and differentiates the organization
of similar units.
What is OLAP? (cont.) Hierarchy
Hierarchies define member relationships and
consolidations of members in a dimension and an
intuitive path for drilling down into more detailed levels.
What is OLAP? (cont.) Attributes
Attribute Characteristic of a dimension member.
For example, Employee dimension members may
have attributes of Name, Age, or Address. Product
dimension members can have several attributes,
such as a size and flavor.
Flavor

Product Size

Income Package
Type
Customer Age

Gender Retail

Channel Web

Direct
What is OLAP? (cont.) Cube

Time
What is OLAP? (cont.) Slice and Dice
What is OLAP? (cont.) Cell
 Additional Terminology
Alias An alternative name. For example, for a more
easily identifiable column descriptor you can display
the alias instead of the member name. Aliases for
above members might be January, February, and
Quarter 1.
Outline The database structure of a
multidimensional database, including all dimensions,
members, aliases, tags, types, consolidations, and
mathematical relationships.
Shared Member - points to data in a base member of
the same name; shared member can be displayed in
multiple locations across different parents in a
dimension. Essbase stores the data value only once.
 Hierarchical Terminology
Generation A layer in a hierarchical tree structure that
defines member relationships in a database. Generations
are ordered incrementally from the top member of the
dimension (Gen1) down to the child members.
Level A layer in a hierarchical tree structure that
defines database member relationships. Levels are
ordered from the bottom dimension member (Lev0) up to
the parent members.
Alternate Hierarchy A hierarchy of shared members.
An alternate hierarchy allows the same data to be seen
from different points of view. Examples include Calendar
Year / Fiscal Year or Functional Org / Geographic Org.
Child, Parent, Sibling, Ancestors, Descendants
 Generations & Levels
Please note that it is possible to have Level 0 members
at any Generation of a hierarchy. In this case notice
that PeriodUnalloc is Generation 2, but Level 0,
whereas its siblings are Generation 2, and level 1
 Member Properties - Consolidation

Consolidation Options:
+ Add
- Subtract
* Multiply
/ Divide
% Percent
~ Ignore
^ Never
 Member Properties - Storage

Storage Options:
Store
Dynamic Calc
Dynamic Calc and Store
Label Only
Shared
Never Share
 Account Dimension Properties

Time Balance
None, First, Last, Average
Skip: None, Missing, Zeros, Missing and Zeros
Variance (Expense) Reporting
True, False
Currency Conversion
 Member Names and Aliases
Member Name is often an abbreviation or related to a
code in the source data, examples include:
Period Qtr1
Account A23-4831
Entity B312
Aliases Provide a more useful Description:
Period Quarter 1
Account Cost of Goods Sold
Entity Western Region
Up to 10 Alias tables allow for multiple languages
 Attribute Dimensions

Associated with a standard base dimension

Base dimension member can have many attributes,
but only one attribute from each attribute dimension
Attribute dimensions have 4 type settingsText
(default), Numeric, Boolean, or Date
Attribute dimensions and members are Dynamic Calc,
Essbase does attribute calculations at retrieval time
Attribute data is not stored in the database (We do not
reference them when loading data)
Attribute dimensions are last dimensions in outline
 Essbase
Architecture &
Components
Essbase Architecture and Components
 Essbase Components
Essbase Server (BSO/ASO) Smart View
Administration Services (EAS) Visual Explorer
Essbase Studio OBIEE+
Provider Services Web Analysis
Interactive Reporting
Essbase API
OBIEE
Application Builder .NET
Financial Reporting
MaxL/EssCmd SQR Production Reporting
MDX/XMLA BI Publisher
3rd Party Front-end Tools
 Outlines
Tree structure for dimension hierarchies
Consolidations and mathematical relationships
between members
Outline Editor
Case Study
Overview
 Hallsworth & Sons - Fashion Retailers

For many years entering plans in ERP System

Roll-up from Excel Spreadsheets throughout company
Inconsistent and error prone, no process management
Minimal review and no reconciliation between top
down and bottom up plans
Doesnt reflect most current market intelligence
Budget data worthless 3 months into year
Commitment by Hallsworth executives to improve
budget process and value and move to rolling forecast
Purchased Hyperion Planning 11.1.2 for 500 users
We will be progressively working through our
laboratory exercises
The first exercises will focus around getting
services started, and then we will move on
to creating our first Essbase model.
Smart View for
Office
 Objectives

Provide Introduction to Smart View for Office

Understand differences between Smart View for
Office versus Spreadsheet Add-in
Hands-on exercise using Smart View to do ad hoc
analysis and create report templates with Microsoft
Excel
 Smart View for Office Introduction

Common Microsoft Office interface for Hyperion

Planning as well as Essbase, Hyperion Financial
Management, Hyperion Enterprise, and Oracle BI EE
Import documents from Financial Reporting,
Interactive Reporting, Production Reporting and Web
Analysis
Integrate data into PowerPoint and Word and refresh
the content when the underlying data changes
 Unified Microsoft Office Interface
Smart View for Office
Adhoc Reporting
Stylized Output:
Formats
Tables
Charts
Formulae
Data Entry and
Apps Processing
Word and PPT
Now works with
OBIEE as source
 Hyperion Smart View for Office

Use MS Office to enter,

analyze and report budget
data
MS Excel add-in allowing
access on or off-line
Users download forms to
Excel
Manipulate data just like
the full web client
Synchronize to server
when ready
 Unique Features

Point of view (POV)

Smart View toolbar, different for
Planning, HFM and Essbase
Functions
Oracle BI+ integration
Updated styles
Precedence
Impacted cells
Data adjustment
Scaling
Customizable undo buffer
 Integrating with Microsoft Office
Excel:
Ad hoc
Functions
Oracle BI+ content
Word, PowerPoint, and Outlook:
Functions
Oracle BI+ content
Smart Tag alternative
Oracle BI+ content:
Financial Reporting
Web Analysis
Production Reporting
Interactive Reporting
 Configuring Data Sources
Hyperion Provider Essbase Servers
Services

Server 1:
Halswrth
Fin

SmartView Connection to
Client Halswrth Fin
Server 2:
2 Sample Basic
Dev Finance

1
Server 3:
Test Finance
SmartView Connection to Test Sales
Client Sample Basic Administrator
(EAS Client)
 Connecting to Essbase Databases
2
1

3 4
 Creating Ad Hoc Reports

In Smart View, all Essbase analysis is done in

Ad Hoc mode:
Default ad hoc grid
Double-click
Refresh Rows

Default layout (varies by database) Columns

POV
 Setting Ad Hoc Options

Common options:
Suppression options
Indentation options
Navigate without data options
Mouse operation options
Zoom options

Unique options:
Undo and redo customization
Formatting Data Cells
Properties
to Modify Control Precedence
Formatting Data Cells
 Setting the Point of View
Default

Customized
 Selecting Dimension Members
1

2 4

5
 Smart Slices

Smart Slices are reusable views of an Essbase,

Planning, or Oracle BI EE data source with predefined
boundaries for use in Smart View
Select Enable Smart Slice in Data Form Properties
Smart View users can view and work with any data
within the boundaries of a Smart Slice, but not with
data outside its boundaries
Smart Slices are stored in Provider Services, and
available to all users with the proper privileges
Smart Slice preferences can be specified and are
stored with the Smart Slice definition
 Report Designer

Report Designer is used to design and manage

reports based on Smart Slices
Report Designer can be used with Essbase, Planning,
or Oracle BI EE data sources
Report Designer interface is displayed when user
inserts Smart Slice query from Data Source Manager
Reports can exist in Excel, Word, or PowerPoint
Report Types are Function Grid, Table, and Chart
Slider control can be added to control query POV
 Oracle Hyperion Planning
Implementation Boot Camp Day 2

Title of Presentation
 Day 1 Review

The trainer will facilitate a Pop quiz based on the

previous days work.
So grab a cup of coffee to get the brain functioning and
well begin.
Essbase Dimension
Build and Data
Load Rules
Dimension Build Load Rule Overview

Essbase Database

Data Source Load Rules Hierarchy

 Procedure for Creating
Dimension Build Rules
General 1. Open a sample data source.
Setup
2. Set data source properties.
3. Hide raw data (optional).
4. Set the view to dimension build fields.
5. Associate the rule with a database outline.
6. If necessary, format the file.
Actions 7. If necessary, create a dimension.
8. Select the dimension build method.
9. Define field properties.
Completion 10. Validate the rule.
11. Save the rule.
12. Execute the rule.
 General Setup

Provide yourself with samples of data on which to

base your rule
Define correct file delimiters
Identify and ignore header records
Set the Data Prep Editor view to the correct mode for
dimension building
Create an association between the rule and the
database outline that you want to update
 Creating Dimensions

1 2

3
 Selecting the Dimension Build Method

Generation references
Level references 2
Parent-child references
3

4
 Defining Field Properties

Dimension
Field type 2

Field number

1
3
 Validating the Load Rule

Common validation errors:

There is an unknown member or no member in
the field name.

The field type for this field is not valid for the
build method associated with this fields
dimension.

The LEVEL number for this field is not

contiguous (starting with 0) with other fields
LEVEL values.
 Completing the Load Rule
Save the rule
Save to Essbase Server
Save to file system 2

Update the outline

Dynamically in Outline Editor 3
Run Data Load in Administration
Services console
Automatically with MaxL

4
1
5
 Manipulating Fields
Arranging fields: Group Model ID Line Type
Move Performance 365-15-150 Lightbolt ATA
Join Performance 540-01-100 Lightbolt SCSI
Split
Create using join
Create using text

Altering fields:
Replace text
Add prefixes and suffixes
Ignore fields
 Arranging Fields
Arrange fields by using field menu options.
Data Source
Group Model ID Line Type
Performance 365-15-150 Lightbolt ATA
Performance 540-01-100 Lightbolt SCSI

Final Arrangement After Load Rule Processing

Family Total Group Line Line Mod Type el ID
Family Total Performance Lightbolt Lightbolt 365 ATA -15-150
Family Total Performance Lightbolt Lightbolt 540 SCSI -01-100

Altering and Ignoring Fields

Alter fields by using Field

Properties dialog box options.

Replaced Text
Ignored Field

Family Total Group Line Line Mod Type el ID

Family Total Performance Lightbolt Lightbolt 365 A -15-150
Family Total Performance Lightbolt Lightbolt 540 S -01-100

 Data Load Overview

Load data:
Without rules
With rules

Data Source Load Rules Essbase Database

 General Setup

Provide yourself with samples of data on which to

base your rule.
Define correct file delimiters.
Identify and ignore header records.
Set Data Prep Editor to the correct mode for Data
Loading.
Create an association between the rule and the
database outline that you want to update.
 Defining Field Properties

For each field, define a data load method and a field name
2

1
 Setting Data Load Values Options

Overwrite, add to, or subtract

from existing data values
Change sign on load
 Validating the Load Rule

Common validation error:

There is an unknown member (or
no member) in the field name.
 Completing the Load Rule

Save the rule: Execute the rule:

Save to Essbase Server Run Data Load in Administration
Save to file system Services Console
Automatically with MaxL
Dense/Sparse and
Block Storage
Architecture
 Dense and Sparse Dimensions

Dense dimensions are likely to contain data values for

most combinations of dimension members
Sparse dimensions lack data values for most
combinations of dimension members
Essbase optimises performance by only calculating
occupied data values in sparse dimension
combinations. This improves query time while
reducing calculation time and minimising hardware
disk and memory requirements.
 Dense and Sparse Dimensions

Essbase requires at least one dense dimension

By default, the Account and Period dimensions are
dense, and remaining dimensions are sparse
Attribute dimensions can only be associated with
sparse dimensions
Review Dimension Evaluation Order to maximize
performance
The Index and Data Blocks
Ideal Configuration
The Index and Data Blocks
Suboptimal Configurations
Database Properties

2
 Dimension Properties

Dense-sparse
configuration
Members in
dimension
Stored members in
dimension

Attribute
Dimension
 Number of Members in Dimension vs.
Number of Members Stored
Why are these values often different?
1) They exclude Dynamic Calc members
(we will discuss more about Dynamic Calculations later)
2) They exclude Shared members in Alternate Hierarchies
3) They exclude Implied Shared members members with
one or more children, but only one is consolidated, so the
parent and child share a value.
4) They exclude Attribute Dimension members which are
always calculated dynamically
 Statistics

Benchmark dense-sparse configuration and storage efficiency

 Calculation
Fundamentals
 Calculation Overview

Database values:
Input data
Calculated data
Calculation options:
Outline calculations
Calculation script calculations

Calculated
Calculation Database Report
Input Data
 Outline-Based Calculations

Used for less complex calculations

Follow outline relationships or formulas
Calculate entire database

Calculated
Input Database
Data
CALC ALL;

Default Calc Script

Outline
 Calculation Scripts

Calculate all or a portion of the database

Control the order in which dimensions are calculated
Perform complex calculations

Calculated
Database
Input
Data

Custom Calculation Script

 Order of Outline Calculations
1. Dimension tagged Accounts

CALC ALL; 2. Dimension tagged Time

calculates the
outline in the
following order: 3. Dense Dimensions Optimal Order:
(outline order) Largest to
Smallest

Optimal Order:
Smallest to 4. Sparse Dimensions
Largest (outline order)

5. Two-Pass Calculations
 Dynamic
Calculations
 Dynamic Calculations

Dynamically Calculated Members are only calculated

at retrieval time instead of during a batch calculation
Dynamic Calcs can improve database performance:
Reduces overall batch calculation time for database
Reduces disk usage, smaller database page/index files
Faster or No database restructures
Use for upper level members of dense dimensions
Use as appropriate for upper level member of sparse
dimensions only with 6 or fewer children
Avoid using Dynamic Calc and Store in most cases
Order of Dynamic Calculations
1. Sparse Dimension tagged
Time if database uses Time-
Series calculations

2. Sparse Dimensions
(outline order)

3. Dimension tagged Accounts if Dense

4. Dimension tagged Time if Dense
5. Time-Series Calculations

6. Dense Dimensions
(outline order)
7. Two-Pass Calculations
8. Attribute Calculations
Calculation Best
Practices
 Pre-Calculation Combinations of
Accounts - Dense
Periods - Dense
Dense Dimensions
Scenario - Sparse
e.g. Version Sparse
Unit Sales Jan Organisation - Sparse
Unit Sales Feb Product - Sparse
Unit Sales Mar

Combos of Dense
ENTITY
Empty

Combos of Dense Combos of Dense Combos of Dense Combos of Dense

UK USA Australia Europe
Empty Empty Empty Empty

Combos of Dense Combos of Dense Combos of Dense Combos of Dense Combos of Dense
LONDON LEEDS MANCHESTER EDINBURGH BELFAST
Populated Populated Populated Populated Populated
 Accounts - Dense
Dense-Calculation Combinations of
Dense Dimensions
Periods - Dense
Scenario - Sparse
Sales Jan Version Sparse
Sales Feb Organisation - Sparse
Sales Mar
Q1-Q4
Product - Sparse
Sales
Sales Total Year

Combos of Dense
ENTITY
Empty

Combos of Dense Combos of Dense Combos of Dense Combos of Dense

UK USA Australia Europe
Empty Empty Empty Empty

Combos of Dense Combos of Dense Combos of Dense Combos of Dense Combos of Dense
LONDON LEEDS MANCHESTER EDINBURGH BELFAST
Populated Populated Populated Populated Populated
 Sparse-Calculation Combinations of
Accounts - Dense
Periods - Dense
Dense Dimensions
Scenario - Sparse
Sales Jan Version Sparse
Sales Feb Organisation - Sparse
Sales Mar
Product - Sparse
Sales Q1-Q4
Sales Total Year

Combos of Dense
ENTITY
Populated

Combos of Dense Combos of Dense Combos of Dense Combos of Dense

UK USA Australia Europe
Populated Populated Populated Populated

Combos of Dense Combos of Dense Combos of Dense Combos of Dense Combos of Dense
LONDON LEEDS MANCHESTER EDINBURGH BELFAST
Populated Populated Populated Populated Populated
 Upper-Level Data Loads

Three methods to address:

Do not aggregate missing values
Load to leaf nodes
Allocate data before consolidation
 Aggregating Missing Values

Aggregate missing values ON: Before After

Calculation Calculation
Overwrites upper-level data loads
Improves calculation performance
Recommended setting

Aggregate missing values OFF: Before After

Calculation Calculation
Protects upper-level data loads
Slows calculation performance
Default setting for new databases
Loading to Leaf Nodes

Avoids upper-level input issues

Requires additional members in the outline

Level 0 placeholder
for Family Total
input data

Level 0 placeholder
for Channel Total
input data
 Oracle Hyperion Planning
Implementation Boot Camp Day 3

Title of Presentation
 Day 2 Review

How is Block Size calculated?

What is optimum block size?
How can you handle issue where ratios/percentages
consolidate incorrectly?
How can you handle issue where prices/rates
consolidate incorrectly?
 Day 3 Objectives

Hyperion Planning Overview, Architecture and

Components
Create Plan Database and Data Source
Review and Create Planning Application, Base
Dimensions, Custom Dimension and Attribute
Dimension
Review Plan Types, Currency and other Planning
Application considerations
Review Options for loading Metadata and Data
Review and Use Outline Load Utility
Hyperion Planning
Overview,
Architecture and
Components
Introduction to Hyperion Planning

Oracle Hyperion Planning is a centralized,

Excel and Web-based planning, budgeting
and forecasting solution that integrates
financial and operational planning
processes and improves business
predictability. With Oracle Hyperion Planning
you can meet your immediate financial
planning needs while enabling a platform for
future cross-functional expansion and
automated process integration.
Hyperion Planning
Market Leading Planning, Budgeting and Forecasting product

#1 Centralized, not distributed

Short budget cycles
Planning and
Budgeting Collaboration across organization
Consistent assumptions and
calculations
Accurate data and plans
Accountability
Align top-down with bottom-up
Driver-based planning
Rolling forecasting
 The Enterprise Planning Process
Re-forecast key areas of
Develop multi-year strategic business performance in the
plan for organic growth, short and medium term and
corporate development and re-align resources and
treasury management budgets to meet changing
Create operational business needs
plans for HR, Sales,
Marketing, etc. to align
with the targets
communicated from
the Financial Plan

Short and
Financial LOB Periodic Management
Long Term Strategic Medium Term
Planning and Operational Variance Reporting and
Planning Re-
Budgeting Planning Analysis Analysis
forecasting

Create annual
plan and budget
using strategic Collect business data
plan as a top for the period just
down target and passed and compare
operational plans with the plan/forecast
as bottoms up to generate variance Create management
inputs report. Drill down into reports to analyze
root causes for performance against
variance the strategic goals,
annual targets and
quarterly/monthly
plans
 Enterprise Planning Applications
Integrated Suite of Best-of-Breed Modules
Strategic Planning and Modeling Planning, Budgeting and
Forecasting
Develop long term strategic plans for
the business Create financial plans, budgets and
forecasts including operational plans
Develop financial models to such as workforce and capital
compare treasury strategies around expenditures plans
funding alternatives
Hyperion Planning
Simulate M&A and divestitures
Workforce Capital Asset
Strategic Finance & Crystal Ball Planning Planning

Profitability & Cost Management Management Reporting

Conduct cost analysis using robust
modeling and analysis with integrated
drill down
Visibility into cost and revenue drivers
through traceability maps
Compare plan, budget and actuals,
report variances, drill down into root
causes of variances by comparing
performance across geographies,
product lines etc.
Essbase

Profitability and Cost Management OBIEE

Single Centralized Planning Platform

EPM Workspace

CORE FINANCIAL PLANS SPECIALIZED MODULES CUSTOM BUILT

Sales Marketing
Planning Planning
Income Balance Workforce CapEx
Statement Sheet Cashflow Planning Planning

Projects Production
Planning Planning

Hyperion Planning Application

Essbase Business Analytics Server

Data Warehouses Transactional Systems Performance Management

Applications
 Hyperion Planning Functional View
Workforce Capital Asset Integrated Custom Planning
End Users P&L Planning
Planning Planning Margin Planning Application

Web and MS Office Multi Currency

Task List Modeling

Application
Annotations and Packaged
Budget Process
Supporting Detail Financial
Management
Reporting

Multi Dimensional Modeling Formulaic Calculations

OLAP
Allocations / Aggregations Calculations Financial Semantics
Essbase

Common Meta data repository User and Security Management

Admin
Common Calculation Management Application Lifecycle Management
EPM Architect and
Shared Services
Hyperion Planning Technical View
 Hyperion Planning Admin/User Tools

Planning Web Client creates and administers

applications without installing software on client PCs
Many administrative features that were formerly in the
Planning Desktop are now available through Planning Web
Client
EPM Workspace is a web client and common user
interface for viewing and interacting with Oracle EPM
reporting and analysis content and financial
applications, including data forms and task lists,
providing access to many of same functions as
Planning Web Client
 Hyperion Planning User Tools

Smart View for Office provides ad-hoc analysis

capabilities to design worksheets in Microsoft Excel to
enter, format, analyze, and report on data in a
Planning application. With Release 11.1.1:
Smart Slice - a reusable subset of a data form enabled for ad
hoc analysis, can be access by Smart View users
Offline Planning - planners retrieve data forms from Planning,
load them into Smart View, take them offline, and later can
enter and save data
PowerPoint and Word to present Planning content
Excel Spreadsheet Add-in
EPM Workspace with access to Data Forms, Task
Lists, Workflow, Reporting and Analysis
 One Window, not Multiple
Oracle EPM Workspace
Self-service Personalization

Contextual navigation

OBIEE and BI Publisher integration

WebCenter integration

Spans all solutions in EPM System

 Hyperion Planning Admin Tools

Business Rules perform calculations through defined

formulas, variables, calculation scripts, macros and
sequences
Financial Reporting Studio allows designers to
produce formatted, book-quality financial and
management reports viewed online or printed
Web Analysis Studio allows designers to produce
web-based interactive analytics with a highly
graphical and easy-to-use interactive interface
 Hyperion Planning Admin Tools

Essbase Administration Services (EAS) for

additional Essbase administrative functions not
available with Planning Web Client
Essbase Studio (new with Release 11.1.1)
Enterprise Performance Management Architect
(EPMA) unifies and aligns processes EPM
applications. You use it to create and work with
Planning applications and dimensions, Smart Lists,
member formulas, business rules and other features.
Calculation Manager to create, validate, deploy and
administer calculations for Planning applications.
 Hyperion Planning Web Tier

Web Application Server

Oracle Weblogic is the embedded Java container that is
installed automatically
Oracle Application Server, WebLogic or IBM WebSphere can
be licensed for applications with large number of users or
requiring high availability
Web Server
HTTP Server (Weblogic, Oracle, IBM) or Microsoft IIS
 Hyperion Planning Database Tier
Relational Database stores the application definition,
metadata and security definitions, and creates
Essbase databases and security privileges for
applications
Essbase stores the application data and leverages
Essbase analytic and calculation capabilities, security
filters, APIs, prebuilt financial intelligence, and
calculation functions
A Data Source must be configured for the Planning
application linking the relational database and the
Essbase server
 Application Components

Data Forms are grids for entering data

Task Lists guide users through the planning process
by listing tasks, instructions, and due dates
Workflow allows viewing a planning units status:
Entity
Process Status
Current Owner
Action
 Creating New
Hyperion Planning
Application
 Steps to create new Planning Application

Setup Relational Database Repository

Use EPM Workspace to Creating Application and
Configure Data Source
Define Application Calendar, Currencies and Plan
Types
Register Application with Shared Services
Create Database(s)
Model Planning Dimensions and Members
 Hyperion Planning Dimensions

6 (8) core dimensions included with Planning:

Period
Year
Currency (Only if Currency Conversion is required)

HSP Rates (Only if Currency Conversion is required)

Account
Scenario
Version
Entity
Up to 13 user-defined custom dimensions
 Planning Calendar

Select Base Period typically 12 Months, could be

custom time period, such as weeks or days
Select Fiscal Start Year typically 1 or 2 years prior
to budget/forecast year
note: can NOT change after creating application
Select Fiscal Start Month
Weekly Distribution Option Even, 445, 454, 544
Select Total Years
Creates Period and Year dimensions
 Currency

Select Default Currency, e.g. USD, CAN, EUR

Select Yes for multi-currency applications, or No for
single-currency applications
note: can NOT change selection after creating
application
If multi-currency application, additional exchange rate
dimension (HSP-Rates) is created
Works in conjunction with Account Data Type of
Currency and Account Exchange Rate Type
(Average, Ending, Historical, None) and Entity Base
Currency
 Plan Type

Specify Plan Types for the Application

e.g. P&L, BalSheet, CashFlow [max 8 characters]
note: can NOT change name or number of Plan Types after
creating Application
Plan Type is NOT a dimension, a separate Essbase
Database within Essbase Application is created for
each Plan Type
All Plan Types will have same Periods, Years,
Scenarios and Versions members
Entities and Accounts can have members that are
only valid for specific Plan Types
Create Planning Application

2011 Qubix International Limited

Create Planning Application

2011 Qubix International Limited

Create Planning Application

2011 Qubix International Limited

Create Planning Application

2011 Qubix International Limited

Create Planning Application

2011 Qubix International Limited

Hyperion Planning
Dimensional
Design
 Planning Units

Standard Planning Units are combinations of

Scenario, Version and Entity (with 11.1.2 we are no longer
constrained by this though, being able to incorporate other
dimensionality into our Planning Unit this is called Custom )
For example, Entity (IT Cost Center) submits data for
a Scenario (Plan) and a Version (Best Case)
Process Management (PUH) allows starting, viewing,
and promoting planning units, and viewing history of
the review process and user annotations
Planning units have six states: Not Started, First
Pass, Under Review, Signed Off, Not Signed Off, and
Approved
 Scenario

Examples include: Actual, Plan, Forecast, What-If

Select range of years and periods for each Scenario
member. Users can update data within range, data
outside of range is Read Only
For multi-currency application, assign Exchange Rate
table to Scenario member allowing comparison of
effects of various currency rate assumptions
Specify access rights to Scenario member to define
users or groups that can view or modify data
Optional: Select Enabled for Process Management
 Version

Examples include: Best Case, Worst Case,

Preliminary, Working, Final, Internal, External
Version Types:
Standard Target - Values entered from parent level and
allocated downward
Standard Bottom Up Values entered at the lowest member
level and aggregated upward
Optional: Select Enabled for Process Management
note: not available for Standard Target Version Type
 Entity (sometimes called the Responsibility dimension)

Core organization structure, typically cost centers,

departments, geographical regions, and/or divisions
Create entity members for each group that submits
plans for approval
Select valid Plan Types for each Entity member, e.g.
West Region Sales Revenue, P&L
Facilities Department P&L, Balance Sheet
For multi-currency applications, select each Entity
members base currency (default is the Default
Currency specified for application)
 Account

Dimension type that provide accounting intelligence:

Account Type: Revenue, Expense, Asset, Liability & Equity,
Saved Assumption (for drivers, e.g. tax rate)
Variance Reporting Property: Expense/Non-Expense
Time Balance Property:
Revenue/Expense Flow (= Time Balance None)
Asset/Liability/Equity Balance (=Last, First, Average )
Data Type: Currency, Non-currency, %, Date, Text
Exchange Rate Type: Average, Ending, Historical, None
Plan Type: e.g. P&L, Balance Sheet, Cashflow
Source Plan Type to load from another Plan Type
 Custom Dimensions

Up to 13 additional user-defined dimensions

note: can NOT delete custom dimensions after
created
Examples include Product, Project, Segment
Plan Type assigned at dimension level, not by
member (all or nothing)
Carefully consider whether Custom Dimensions
required for planning process:
May add unnecessary complexity
Will increase time to calculate, report, back-up,
Easy to include outside of Planning application for expanded
reporting and analysis
 Attribute Dimensions

Attribute dimensions are associated with base

dimensions and group and analyze members of base
dimensions based on the member characteristics
(attributes)
Attribute Data Type: Text, Numeric, Date, Boolean
Examples:
Entity - Number of Employees
Product - Intro Date, Color, Package Type, Package Size
Aggregations dynamically calculated by Essbase
Only available on Sparse dimensions
 Security inside Dimensions

You can assign access permissions to:

Scenario members
Version members
Account members
Entity members
User-defined custom dimension members
Access permissions for the specified user or group to
the dimension member include:
Read: Allow view access
Write: Allow view and modify access
None: Prohibit access; the default access is None

Slide Content
Contributed by:
 Refreshing Databases

Refreshing from Planning to Essbase

 Hyperion Planning
Other Considerations
 Dimension Evaluation Order
Dense dimensions should be first, ordered from most
to least dense (usually Period, followed by Account)
Aggregating dimensions aggregate data from children
into parents creating new data; no new data is
created by non-aggregating hierarchies (such as
Scenario and Version). Place sparse aggregating
dimensions before sparse non-aggregating
dimensions and order sparse dimensions based on
number of members, from least to most.
Position Attribute dimensions at end
 Smart Lists and User Defined Attributes
Smart Lists - custom drop-down lists that users
access from data form cells. If a cell contains a
dimension that is linked to a Smart List, is
displayed. When clicking into cells whose members
are associated with a Smart List (as a member
property), users select items from drop-down lists.
User Defined Attributes (UDAs) are associated with
members and describe member characteristics. Used
in calculation scripts, member formulas and reports to
return list of members that have specified UDA.
HSP_UDF UDA prevents member formula from being
overwritten when application refreshed
HSP_NOLINK UDA prevents @XREF function from being
created on all plan types that are not the source plan type
 Other Considerations
Modifications to dimensions, members, aliases,
properties, etc. will NOT be reflected in the Essbase
outline until administrator does Create or Refresh from
Manage Database page
Essbase Database should be backed up before doing
Refresh
All users should log off before doing Refresh as
Refresh does not automatically log off users
Administrator should send broadcast message
beforehand warning users to save their work and log off
Hyperion Planning
Metadata/Data
Load Options
 Hyperion Planning Data Integration

Hyperion Planning Outline Load Utility

Oracle Data Integrator (ODI) Adapter for Planning
Hyperion Data Integration Management (DIM)
[Informatica PowerCenter] Adapter for Planning
Enterprise Performance Management Arch (EPMA)
Oracle Essbase Data Load Rules
Oracle Hyperion Financial Data Quality Management
(FDM) Adapter for Planning
Hyperion Data Relationship Manager (DRM)
 Outline Load Utility
Set Planning System Properties: Administration >
Manage Properties System Properties tab
DIRECT_DATA_LOAD True (default) / False
DATA_LOAD_FILE_PATH
Restart Planning Application Server
Generate .CSV load file with appropriate format
Utility located in HYPERION_HOME/products/Planning/bin
Run utility with /N parameter to confirm load file
parses without errors
Run utility without /N parameter
See hp_admin.pdf for details on appropriate file
format and command line parameters
 Oracle Hyperion Planning
Implementation Boot Camp Day 4

Title of Presentation
 Day 3 Review

What are key steps to creating a new Planning

application?
What is the purpose of the Data Source?
What 6 dimensions are in every Planning application?
What can you do if you add a Custom Dimension and
later decide you no longer want to include it?
 Day 4 Objectives

Learn the components that comprise a Data Form

Construct Basic and Intermediate level Data Forms
Understand common options used with Data Forms
Create Business Rules used in conjunction with Data
Forms
Learn design Best Practices for Data Forms
Designing Data
Forms
Data Entry Forms are Centrally Maintained
and Consistent Across Web and Excel

Form layout
Display options
Form contents
Access permissions
Business rules
 Data Forms - Definitions
Data Form A grid display that enables users to enter
data into the database from an interface such as a Web
browser, and to view and analyze data or related text.
Point of View (POV) One or more fixed dimension
member values that determine context for Data Form
pages, rows, and columns. All data in the Data Form is
constrained by the Point of View.
Page Axis Combination of dimension member values
that determine context for Data Form rows and
columns. Users switch between dimension member
combinations by selecting Page values using drop-
down lists from the page axis.
 Data Forms Plan Types

Specify Plan Types for the Application:

Fin
HR
Associate Data Form with a plan type, this determines
the data form's valid Account and Entity members.
Entered data is saved to the selected plan type's
database.
Note: can NOT change the plan type for Data Form
after it is assigned
 Data Forms - Versions

Version Types:
Standard Target - Values entered from parent level and
allocated downward
Standard Bottom Up Values entered at the lowest member
level and aggregated upward
Bottom Up versions only allow data entry for rows and
columns with level 0 members. Rows and columns
set to parent members are read-only.
Target versions allow data entry in parent members
 Creating Data Forms

Select Data Form folder

Assign Data Form Name and Description
Assign Data Form Plan Type
Assign dimensions to Rows and Columns
Select Row and Column dimension members
Add Segments for separator borders and hidden or
read-only data
Define Page and Point of View dimension members
Optional: Composite Forms
Data Forms - Layout
Data Forms - Validation

New with the latest version of Planning is the ability to create

validation in the web forms.
Web form validation can be applied to:
The whole Grid
Column(s)
Row(s)
Cell(s)
Validation can be against member or value criteria, and can simply
provide warnings to the user or affect data submission and work
flow. A comprehensive lab will clearly demonstrate this.

2011 Qubix International Limited

 Data Forms - Precision

Set the number of decimal positions displayed for

Currency, Non-Currency, and Percentage Values:
Minimum Precision to add zeros to numbers with a small
number of decimals
Maximum Precision to truncate and round the decimal portion
of longer numbers
Examples:
Value -123 and Minimum Precision - 3 123.000
Value - 123.4567 and Maximum Precision - 2 123.46
Business Rules
 Business Rules with Calculation
Manager for Classic

Graphical mode vs Enhanced (Source) mode

Calculation Manager from Workspace
for EPMA or Classic applications
 Business Rules Overview

Business Rules vs Calculations

Run-time Prompts
 Business Rules Overview

Business rules perform calculations through pre-

defined functions, commands, variables, and macros
Business rules are associated with data forms by Plan
Type
Users launch associated business rules from the Data
Form to calculate and allocate values
Calculate Data Form and Calculate Currencies
business rules are automatically created
Business rules can be set to launch automatically with
Run on Load or Run on Save
Business Rules and Data Forms
 Business Rule Runtime Prompts

Runtime prompts are variables such as members,

text, dates, or numbers that users enter or select
before a business rule is run
Use Members in Form option will use the current
members selected in the POV and Page Axis as the
default members in business rules runtime prompts,
they can be changed before launching business rule
Hide Prompt option (valid only when Use Members in
Form option selected) will hide runtime prompts if all
variables can be read from the POV and Page Axis
 Business Rule Runtime Prompts

By default, the values for processed runtime prompts

are stored in the database and can be viewed from
the Job Console
If many users run business rules with runtime
prompts, tracking these values uses significant
system resources. To improve performance, you can
turn Off function to capture runtime prompt values by
adding CAPTURE_RTP_ON_JOB_CONSOLE
property to the properties table, with value of FALSE
(to turn On, change value to TRUE).
 Business Rules Further Details

For discussion of how settings and conditions affect

the display and values of runtime prompts, see
Understanding Runtime Prompts in Hyperion
Planning Administrators Guide
For creating business rules and additional
information, see Hyperion Business Rules
Administrators Guide
 Additional Data
Form Components
 Data Forms Adjusting Data

Increase/Decrease values By Value (a specific

amount) or By Percent
Adjust data for multiple cells simultaneously if cells
are at same dimension level (e.g. Jan, Feb, Mar)
Adjust data by typing an operator in a cell ( +, , *, /,
or %), followed by entering a number
 Data Forms Spreading Data

Options to distribute or spread values:

Spread value in a summary time period back to its base time
periods
Spread values among children and parents proportionally,
based on existing distribution
Spread values based on weekly distribution
(4-4-5, 5-4-4, 4-5-4, or None, as set in application)
Fill the parent's value to its descendants
Spread value over time periods while temporarily locking
certain cell values
 Data Forms Spreading Data

Account Type, Time Balance property, Data Type,

dimension hierarchies and the existing distribution of
data determine how values are spread
See How Spreading Works in Hyperion Planning
Users Guide for specific details and examples
Use Grid Spread to increase or decrease values
across multiple dimensions ON the data form
Use Mass Allocate to spread data to member
descendants including those NOT ON the data form
note: use requires Mass Allocate role and property
 Data Forms Mass Allocation

With Mass Allocate role and Mass Allocate enabled

as the Data Form property, you can spread data using
Mass Allocate, which:
Allocates data to all the source cell's descendants even to
cells not displayed on the Data Form
Allocates across multiple dimensions
Does not require that you have access to the target cells
Cannot be undone after you Mass Allocate values
Is processed with dynamically-created calc scripts
Executes the calc scripts against the Essbase server, against
all dimension combinations
 Data Forms - Supporting Detail

Supporting detail helps you build and communicate

bottom-up values with details not included in the
database outline. It also provides a way to drill down
into data, to better understand how it was derived. For
example, you may want to add line items for
employees in a department to more accurately plan
travel expense.
Supporting detail can include text, values, and
operators that define how data aggregates.
Supporting Detail Rules

Supporting detail does not change members in outline

You must have cell write access to create, change, or
delete supporting detail
You must have cell read access to view supporting
detail
You cannot update data into aggregate values with
supporting detail
You can only add supporting detail to base time periods
Number and Precision formatting is not reflected in the
Supporting Detail window
 Data Forms Annotations

Annotations are comments, notes, explanations, or other types

of external remarks that can be attached to a Web document or
a selected part of the document.
With appropriate access, users can add or view annotations
which can be plain text or include URL link to a comment or URL
of up to1,500 characters. URL links can be to .TXT, .DOC, .XLS,
and .PDF files.
Account Annotations
Planning Unit Annotations (According to Planning Unit
Hierarchy)
 Data Forms Cell Text Annotations

With appropriate write access, users can add

annotations called cell text to the cell at any level:
Non-level 0 members, Calculated members, Dynamic
calc members, read-only members
Cell Text can be up to 1,500 characters
If users selects cell range, they can enter same cell
text for all cells in range
Cell Text is stored on server and can be viewed by all
users with read access to data cell
 Data Forms Cell-Level Documents

If administrator selects the Enable Cell-Level

Document data form property, users can associate
EPM Workspace documents to the cell
Documents can be a URL or any file type
Files must exist in the Workspace repository before
beings associated with a cell in data form
As with Cell Text, Cell-level documents can only be
updated by users with write access to data cell and
viewed by all users with read access to data cell
 Data Form Cell Background Colors

White: default
Yellow: dirty cells, whose values changed but are
not yet saved
Light blue: read-only cells
Tan: locked cells
Teal: cells having supporting detail
 Customizing Data Forms with
JavaScript
Appendix A in Hyperion Planning Administrators
Guide describes using JavaScript to customize data
forms. Programmers familiar with JavaScript can
customize Planning data forms in these ways:
Add buttons to link to web pages or run JavaScript code
Modify behavior when users save data forms
Modify behavior when the focus enters or leaves a cell
 Additional Data Form components
Menus: Shortcut menus accessed by right-clicking
that can open URLs, data forms, workflow, or
business rules.
User Preferences: options for e-mail, aliases, member
selection, offline planning, workflow, display, printing
and user variables
User variables: Selectable members on the row,
column, page, or POV. Before you can open a data
form having a user variable, you must select a value
in preferences. After that, you can change the
variable on the data form or in preferences.
Workflow and
Task Lists
 Planning Unit

Planning tracks budgets by Planning Units a

specific scenario, version, and entity combination.
Scenarios and versions are the basis of the review
cycle. For example, IT Cost Center (an entity)
submits data for Plan (a scenario) and Best Case (a
version). You start, view, and promote planning units,
and can view history of the budget review process
and user annotations by planning unit.
Planning units are in one of six states: Not Started,
First Pass, Under Review, Signed Off, Not Signed Off,
and Approved
 Planning Unit - States
Not Started: Budget administrators initiate the review
process using the Start action
First Pass: Users with access permissions can enter
data and promote planning units and assign owner
Under Review: Only the current owner or budget
administrators can modify data or perform actions
Signed Off: Only the current owner or budget
administrators can modify data or perform actions
Not Signed Off: Rejected, only the current owner or
budget administrators can modify data or perform actions
Approved: After approved, the budget administrator
becomes the sole owner and can modify data or perform
actions.
 Planning Unit - Status Actions

Promote: For planning units in First Pass, changes

the state to Under Review and assigns ownership to
another user. Subsequent promotions transfers
ownership from one reviewer to another.
Sign Off: Changes state to Signed Off, but doesnt
transfer ownership of the planning unit
Reject: Changes state to Not Signed Off and requires
the previous owner, or another selected owner, to
make another iteration of plan
Approve: Changes state to Approved
 Planning Unit Entity Hierarchy

Entity hierarchy relationships affect review process:

Promote or Reject action to parent results in Promote or
Reject action to the descendants (unless previously
Approved), the parents owner becomes the descendants
owner
Approve action to parent results in Approve action to the
children
When all children are promoted to the same owner, the parent
is promoted to the owner
After Sign Off action to all the children, the parent status
changes to Signed Off
 Planning Unit E-mail Alerts

Application owners must 1st specify a valid e-mail

server in order to enable e-mail notification
In User Preferences, users can then select to Enable
E-mail Notification and Copy the Application Owner
After e-mail notification is configured, users receive e-
mail from application owner when they become the
planning unit owner Subject: NEW OWNER: Plan
(Scenario, Version, Entity)
 Planning Unit Annotations

After a planning unit has been started, users with read

access to planning unit can add or view annotations
about the data in a planning unit.
Administrators can report on annotations to check
planning unit status for a set of scenarios, versions,
and entities. Reports can be based on process status
and displays the planning unit title, author, date, and
annotations with the most recent annotation first.
 Task Lists

Administrators and interactive users create

and manage task folders and task lists,
detailed lists of tasks to guide users through
the planning process by listing tasks,
instructions, and due dates.
 Task Lists

Users can view:

Task Name, Status and View link (if instructions for
completing task are provided)
Due date - When tasks must be completed
Alerts - Visual cues about your progress, and the
completion date and time:
Green: On schedule
Yellow: Approaching due date
Red: Past-due
E-mail alerts - Notification of upcoming and past-
due tasks
 Task Lists
Completing tasks depends on the task type.
Tasks can include URLs, data forms, workflow,
business rules, or descriptive tasks. For
example, a task can require a user to view a web
page, enter data, promote a planning unit,
launch a business rule or read information, such
as reminders or instructions.
After completing task, users mark the task as
complete. The alert changes to a datetime stamp
reflecting completion date and time. Dependent
tasks must completed before the primary task.
 Task List Type

URL Task: opens a specified web page

Web Data Form: opens a specified Data Form
in a specified Data Form Folder
Business Rule: launches a specified Business
Rule Name for a specified Plan Type
Workflow: starts the workflow process with a
specified Scenario and Version
Descriptive: provides text of descriptive tasks
 Task Lists e-mail Alerts

Adminstrators can send e-mail notification to

users for tasks that are past due and/or past a
defined alert date and before due date,
specifying the timing and frequency of alerts
(e.g. every 2 days or every 4 hours)
Administrator must configure an valid SMTP
e-mail server using System Settings
Users can also select to be notified by e-mail
from Job Console Notification when a job they
launch (e.g., a business rule) completes or
generates errors
 Oracle Hyperion Planning
Implementation Boot Camp Day 5

Title of Presentation
 Day 4 Review

What are steps to create a new Data Form?

What are reasons for using Business Rules instead of
standard Essbase Calc Scripts?
What are 5 ways users can add additional information
related to Data Forms?
Hyperion Planning
Metadata/Data
Load Options
 Hyperion Planning Data Integration

Hyperion Planning Outline Load Utility

Oracle Data Integrator (ODI) Adapter for Planning
Hyperion Data Integration Management (DIM)
[Informatica PowerCenter] Adapter for Planning
Enterprise Performance Management Arch (EPMA)
Oracle Essbase Data Load Rules
Oracle Hyperion Financial Data Quality Management
(FDM) Adapter for Planning
Hyperion Data Relationship Manager (DRM)
Hyperion Application Link (HAL)
Metadata Load Tools
Metadata Load Tools - continued
Data Load Tools
Data Load Tools - continued
 Oracle EPM Data Integration Tools
DRM
Think Enterprise master data
management
Scope Hyperion to Hyperion,
transactional systems and
data warehouse
Focus Synchronize across EPM
System, Data Warehouse &
Transactional Systems
Users Business & IT
Key Manage change in versions,
Features hierarchies,
Version control & roll back
Validations, verifications
Configurable attributes &
exports
History & audit trail
Query, comparison of
structures & attributes
Importing, blending,
automating changes
FDM
Financial data quality
GL, flat files, Excel to Hyperion
Financial Applications
Validate, verify, document, audit
and support compliance
Finance Users
Audit Trail
Trial Balance to Report
Data Reconciliation
Data Accuracy
Data Completeness
Internal Audit Controls
COSO Repository
ODI/DIM
Enterprise data integration
Any source, any data to EPM
System
Access ERP & mainframe data,
transform, cleanse, consolidate,
move
IT
Complete enterprise and custom
solution
Any Source
Certified pre-defined ERP/CRM
adapters
Structured, semi-structured and
unstructured data
Bi-directional data flow
Scheduling & automation
Move terabytes
 Oracle Data Integrator
Oracle Data Integrator is a comprehensive data
integration platform that covers all data integration
requirements:
high-volume, high-performance batches
event-driven, trickle-feed integration processes
SOA-enabled data services
Key Benefits
Lower TCO
No middle tier for ETL
Performance
Database guarantees scalability
Productivity
Declarative design
 Differentiator: E-LT Architecture
High Performance
Conventional ETL
Transform in Separate ETL Server Architecture
Proprietary Engine Extract
Transform
Load
Poor Performance
High Costs
IBM & Informaticas approach

Transform in Existing RDBMS

Leverage Resources Next Generation
Efficient Architecture
High Performance
E-LT
Benefits Extract Load
Optimal Performance & Scalability
Easier to Manage & Lower Cost Transform Transform
 Differentiator: Declarative Design
Developer Productivity
Specify ETL Data Flow Graph Conventional ETL Design
Developer must define every step of
Complex ETL Flow Logic
Traditional approach requires
specialized ETL skills
And significant development and
maintenance efforts
Declarative Set-based Design
Simplifies the number of steps ODI Declarative Design
Automatically generates the Data Flow
whatever the sources and target DB 1 2
Define Automatically
Benefits Generate
What
Significantly reduce the learning curve Dataflow
You Want
Shorter implementation times
Streamline access to non-IT pros Define How: Built-in Templates
 Differentiator: Knowledge Modules
Hot-Pluggable: Modular, Flexible, Extensible
Pluggable Knowledge Modules Architecture
Reverse Journalize Load Check Integrate Service
Engineer Metadata Read from CDC From Sources to Constraints before Transform and Move Expose Data and
Source Staging Load to Targets Transformation
Services
Reverse
W
W S W
S S

Staging Tables
Load Integrate
Services
CDC Target Tables
Journalize Check
Sources
Error Tables

Sample out-of-the-box Knowledge Modules

SQL Server Oracle Check MS TPump/ Oracle Web
SAP/R3 Log Miner JMS Queues Oracle Merge
Triggers DBLink Excel Multiload Services

Oracle Check Siebel EIM DB2 Web

Siebel DB2 Journals DB2 Exp/Imp Type II SCD
SQL*Loader Sybase Schema Services

Benefits
Tailor to existing best practices
Ease administration work
Reduce cost of ownership
 Oracle Data Integrator Terminology
DataStore relational table, file, or other data structure that describes data
as a table of columns
Data Servers - database or file server that contains datastores
Physical Architecture allows dividing Data Server that can store different
information according to a business logic into separate physical schemas
Logical Architecture allows grouping physical schemas with datastores in
separate physical locations into logical schemas
Sunopsis Memory Engine staging area to manipulate data before loading
Project - integration project made up of interfaces
Knowledge Modules (KMs) imported into Projects and contain knowledge
required by ODI to perform a specific tasks against a specific technology
Model set of datastores included in Projects
Interface - rules that define the loading of a target datastore from one or
more source datastores
 Steps to Build Project to Load dimension
ODI Topology Manager
Define Logical Schema for Planning
Define Physical Schema for Planning
Define Logical Schema for Source data
Define Physical Schema for Source data
Define Logical Schema for Sunopsis Memory Engine
Define Physical Schema for Sunopsis Memory Engine
ODI Designer
Create Project and Import necessary Knowledge Modules
Create Models for Source data and Planning dimension
Create Interface between Models and Sunopsis Memory Engine
Execute Interface
Validate Interface Execution
 Project

Setting up a Project
Knowledge Modules
Models
Interface
Data Integration Management (DIM)
Oracle EPM Applications

Financial Management
EPM Adapters Essbase / Planning
Performance Scorecard

Team Based Development Option

Data Integration Management Server Partitioning Option
Real-Time Option
Server Grid Option
SAP R/3
ERP / CRM Adapters SAP BW
PeopleSoft
Siebel

ERP Relational Files Legacy Other

 Hyperion Data Relationship Management
Hyperion DRM is a change management platform to

Simplify master data change

Enable change originators (business users, end users) to
become direct contributors to master data change
Enhance data governance across the enterprise
Automate the process of updating master data changes
across multiple systems with powerful, configurable
business rules
Improve total cost of ownership (TCO) of enterprise and EPM
systems with streamlined maintenance
Dramatically reduce costly reconciliation time attempting to
balance reports across systems
 The Master Data Business Problem
Different people
involved
Inevitable manual Oracle EPM System Essbase
Admin
process Planning Essbase
Essbase
Essbase
Error-prone, Planning
Admin DW
inconsistent
Accounts
No way to audit Entity
Project
No way to rollback Product
Oracle ETL
EAI
Admin
changes Location Spreadsheet

Time and resource Channel

consuming Peoplesoft
Oracle
SAP Custom
Financials
Updates
interpreted by Review
systems experts Spreadsheet

Business
IT Admin
User E-Mail
 Hyperion DRM Solution
Combine separate
structures into a
single maintenance Oracle EPM System

structure Planning Essbase

Essbase
Streamline change
Essbase
DW
management
Accounts
Immediate feedback Entity
to business users to Project Hyperion DRM ETL
enforce system Product EAI
constraints, Location
business rules Channel

Publish changes for Peoplesoft

Oracle
Financials
SAP Custom
each specific
consuming system
as needed, when
needed
Business
User
 Financial Data Quality Management

The only data quality solution that can.

Be deployed and maintained by Finance users

Speed financial reporting and planning cycles
Load, review, and correction cycles
Deployments and migrations to new applications
Provide visibility into financial data management processes
Audit trail
Map changes
Data quality checking
Error identification, notification, and investigation
 Financial Data Quality Management

Guided Workflow User Interface

Source
Systems Data EPM EPM
Preparation
Adapters Systems
Server

Excel Data cleansing and Prepackaged Oracle EPM System

G/L transformation integration HFM
Task scheduling Data loading including Planning
ERP
supplemental data, line Essbase
Flat files Text and document
item detail Hyperion
archive
ETL Dimensional mapping Enterprise
Repositories Audit review
verification Data Marts
Data staging
Process management
Drill-through To Transactional Detail
Budget vs Actuals

Audit Trail

Ledger Detail
ERP Integrator Architecture
 Hyperion Application Link

Data integration product OEMd from Vignette

Single user, client-based tool to move data and
metadata between external system and EPM apps
Sold in two versions:
HAL Basic bundled with Planning, HFM and HPS
HAL Advanced separately priced option including complete
set of transformation and automation capabilities. Supports
using adapters (at additional cost) for ERP and CRM systems
such as SAP R/3, Siebel, PeopleSoft and JDE One World.
No longer marketed or sold after April 2007
Sustaining Support ends June 2010
 Enterprise
Performance
Management
Architect
Build and Deploy Applications Fast
EPM Architect - Single Administration Portal
Dimension Library
Local and shared dimensions
Application build wizard
Reuse building blocks

Calculation Manager
Visual design of business rules
Share rules across all applications
Reuse calculation components

Life Cycle Manager

Move between Dev, Test and Production
Application migration wizard
Comparison and audit reporting
 EPM Architect Components

Performance Management Architect Modules:

Dimension Library
Application Library
Calculation Manager
Data Synchronization
Application Upgrade
Library Job Console
Performance Management Architect Utilities:
Batch Client
File Generator
EPM Architect: Functional Architecture
 Common Business Rules
Ensure Consistency of Calculations and Allocations
Calculation Manager
Single interface for Hyperion
Planning and Financial
Management
Graphical flow provides better
understanding of calculation
process
Re-usable rules to share among
applications
Central repository of all
calculation objects
Lowers the barrier for users to
define and maintain business
logic
 Calculation Manager Objects
Rulesets contain rules (or other rulesets) that can be
calculated simultaneously or sequentially
Rules contain components and templates
Components include objects such as formulas,
scripts, conditions, loops, member ranges, templates,
and variables, including runtime prompt variables.
formula and script components are independent of the rules
and templates they are used in and can be opened, edited
conditions, ranges, and loop components must be created
within rules and templates to which they belong.
Templates perform calculations in a business rule.
Calculation Manager includes System templates to
allocate data, aggregate data, copy data, clear data
Administrator can create Custom defined templates.
Planning Security and
Administration
 Planning Security and Administration

Shared Services
Provisioning Users/Groups
Primary Planning Roles
Object access Forms and Tasks
Data level access across dimensions
Essential Dimensions
Precedence rules when conflicts arise
Lifecycle Management
Automations
Backup/Recovery
Shared Services for Security Management
Provisioning Users and Groups
Provisioning by Application and Role
 Primary Planning Roles

Administrator/Owner open ended access for top

level developers, Owner is original creator of Planning
application and only user that can delete application
Interactive User for developers and plan
administrators to manage Forms, Task Lists and User
Variables
Planners end-users who will enter data into forms,
run business rules they are authorized for and access
Workflow in order to promote completed budgets
 Assign Access to Forms
Granted by Form or Form Folder
No Access to Form for Planners or Interactive Users
unless Administrator specifically assigns access
Form Access Types Read, Write and None
Scenario has role in access to data in forms:
For Bottom-Up Scenario, Planner with Write access will only
be able to enter data for Level 0 members of dimensions
Start/End Year/Month controls Years and Months that Planner
with Write access can update
Data Access Planners can select only members to
which they have read or write access and can edit
data forms only if they have access to at least one
member of each secured dimension.
 Data Access
Primarily determined by Essbase filters automatically
created as part of Create/Refresh process
For new user, default filter assigned provides access of
None for all dimensions
Data Access granted by individual Planning dimensions
Must be defined for Planning Unit (Scenario-Version-
Entity) and Accounts dimensions
Period and Year access controlled by Scenario Start/End
Year/Month
Custom dimensions default to access all members
unless Apply Security checkbox selected in Dimension
Properties, then access must be defined
 Planning Administration
Automations
Life Cycle Management
Backup/Recovery
Automating Hyperion Planning Processes

Metadata Loading
Data Loading
Copy Data Utility
Cube Refresh Utility
Calculation Manager Command Line Launch Utility
Lifecycle Management Migrations between
environments (Development Test
Production) or between operating systems
(Windows Unix)
 Automating Metadata and Data Loading

Outline Load Utility

Essbase Load Rules
Oracle Data Integrator (ODI)
Data Integration Manager (DIM)
Performance Management Architect (EPMA)
Financial Data Quality Manager (FDM)
 Outline Load Utility

Run using Command Line and Parameters

Schedule using standard 3rd party tools
See details in Hyperion Planning Admistrators Guide:
Working with the Outline Load Utility
 Essbase Load Rules

Essbase Data Load MaxL

Pass MaxL statements to Essbase Server using MaxL Shell
(essmsh) or customized Perl program that uses the MaxL Perl
Module (essbase.pm)
See details in Essbase Administrators Guide: Using MaxL
Data Definition Language, Oracle Essbase Technical
Reference: MaxL Data Definition Language (DDL) and the
README file in the PERLMOD directory of Essbase
installation
Write MaxL scripts with variables to make them flexible and
reusable
 Oracle Data Integrator (ODI)

ODI Package
Chaining interfaces into packages so that you can run the
interfaces in a single process
ODI Scenario
Scenario is used to operate completed components including
packages
ODI Scheduling Agent
 Performance Management Architect

Task Automation allows linking a series of individual

actions/stages into a taskflow to automate commonly
performed EPMA tasks such as:
Data Synchronizations Scan (test) or Load
Import dimensions from flat file or interface table
Redeploy Planning Application
Taskflows can be scheduled to run at a specific time
and Links control execution of subsequent actions
See details in EPMA Administrators Guide chapter:
Using Task Automation
 Performance Management Architect

EPMA Batch Client provides a command-line

interface that allows tasks to be scripted and run
during nightly or weekly load process using external
scheduling tools
You can run the Performance Management Architect
batch client in two modes:
Command line mode to enter commands interactively
Script mode to executes a series of commands without your
interaction by specifying a command file and optionally a
result log file and trace log file
See EPMA Batch Client Users Guide
 Financial Data Quality Manager (FDM)

FDM Workbench (Windows client) includes Batch

Processing setup and monitoring
Batch files processed by Batch Loader are either:
StandardText files that can contain only one month and that
are usually loaded through the Import screen
MultiloadText or Excel files that can contain multiple
periods and locations
FDM Web client includes Task Manager component
to run scheduled tasks (FDM scripts) and to add,
modify, and delete tasks
 Copy Data Utility

Copy Data is used in initiating a budget cycle

You can copy from one plan type at a time
Dimensions fall into two categories:
Static Dimensions with same Source and Destination
members
Dimensions with different Source and Destination members
In addition to copying the Essbase data, Copy Data
Options also allow you to select and copy Account
Annotations, Supporting Detail, and/or Cell Text
 Copy Data Utility - Guidelines

Data must be copied into cells that can accept data,

you cant copy data into read-only or dynamic cells
Must select at least one member for Account, Entity,
Period, Scenario, and Version dimensions
You can copy account annotations, supporting detail,
and cell text, you cant copy planning unit annotations
Planning assumes you have access to data you copy
You are not prevented from copying to planning units
that are approved
Copied dimension members must be present in the
selected plan types
 Copy Data Background Processing

Copy Data job can be set to execute in the

background after a specified period of time, the
frequency used to check job status can also be set
In Application Properties, add Property Name/Value:
COPY_DATA_MAX_WAIT
Default and minimum value is 180000 milliseconds (3
minutes). If this property is not set, Copy Data jobs do not run
in the background.
COPY_DATA_MONITOR_DELAY
Default and minimum value is 180000 milliseconds (3
minutes)
 Hyperion Planning CubeRefresh Utility

CubeRefresh utility creates or refreshes database

Before it runs, it ensures that the application is not
locked. While it runs, the application is locked when
metadata is updated in the database.
Utility must be run on the same machine as the
Planning server, not remote server
Default location for CubeRefresh.cmd utility file is
HYPERION_HOME/products/Planning/bin
See Refreshing Application Databases Using a
Utility in Hyperion Planning Administrators Guide for
command parameters
 CalcMgrCmdLineLauncher Utility

Administrators can launch business rules created with

Calculation Manager from Command Prompt
For business rule with runtime prompts, create a
runtime prompt values file before running utility or
default values will be used; create text file manually,
or automatically using option to Create Runtime
Prompt Values File on the Runtime Prompts page
See Launching Business Rules With a Utility in
Hyperion Planning Administrators Guide for details
on runtime prompt values file and command
parameters
 EPM Life Cycle Management

Lifecycle Management provides a consistent way to

migrate EPM applications, repositories, or individual
artifacts across product environments and operating
systems
Lifecycle Management Utility is command-line utility
that provides an alternate method to do migrations
that can be used with 3rd party scheduling tools such
as Windows Task Scheduler or Oracle Enterprise
Manager
 Life Cycle
Management
 Life Cycle Management Utility

Lifecycle Management Utility is installed with Shared

Services
Components of Lifecycle Management Utility are
installed to LCM_HOME -
hyperion_home/common/utilities/LCM/<release#>
Directory contains all files needed to execute utility, to
use utility on another computer, copy directory.
 Using Life Cycle Management Utility

Create Migration Definition file manually or using

Migration Wizard
Connections Element one of 3 types: HSS, FileSystem, or
Application
Task Element defines sequence if more than one source
and one target
Source Element
Target Element
Review/Update migration.properties file
Run the Utility
 Lifecycle Management API

The Lifecycle Management API provides API to

execute migrations, obtain status and IDs associated
with a migration, enabling users to customize and
extend the Lifecycle Management functionality.
The Lifecycle Management API consists of:
LCMClient Class
LCMHandle Class
See details in EPM System Lifecycle Management
API Reference
 Planning Migration Considerations

Migration of Planning Data is not supported

Some Planning artifacts have dependencies (e.g. forms
have dimension dependencies), you must manually
select any necessary dependencies
Migrations are long-running operations
Essbase and the Business Rules artifacts display under
the Planning application node
The source and destination applications must have the
same settings for Plan Type, Start Year, and Currency
 Database Backup Types

Physical Backup copies physical data files

Hot users can make changes to DB during backup
Cold users can not make changes to DB during backup
Full copies full database
Incremental captures only changes after last full backup
Logical Backup copies data, not files
Recommended - Weekly or biweekly cold full physical
backup and periodic cold incremental physical
backups if downtime allowed. Periodic logical export
backups in case physical backups fail or the database
machine becomes unavailable.
 Databases to backup

Shared Services databases

Database containing Shared Services Registry
Shared Services Native Directory
Oracle Hyperion Planning
Other repository databases as applicable
External Directory
Database used to extract or store data related to
Hyperion Planning or other EPM applications
 Essbase Backup and Recovery

Backup and restore block storage databases using

automated or manual method
Transaction logging captures post-backup
transactions which can be replayed to most recent
state before interruption occurred
To back up and restore aggregate storage app
lications, you must use manual procedures
Do not use the file system to copy, move, rename, or
delete applications and databases as Essbase
security file is unable to recognize the files
 File System Backup Types

Complete - includes an entire file system directory

Post-installation for directories created or modified if
you reconfigure products
Daily incremental - new directories or files or those
modified since the previous day
Weekly full - All files in the directories for which you
perform daily incremental backups
As needed for data modified infrequently
 Files Systems to backup

Oracle Hyperion Planning

Other file systems as applicable
HYPERION_HOME/common/config
HYPERION_HOME/products
HYPERION_HOME/deployments
for products requiring Web Application Server
Windows registry: HKEY_LOCAL_MACHINE and all
of its subkeys
%USERPROFILE%//hyperion.products
 Hyperion Planning components to backup

Planning relational database

Windows registry keys for Planning:
HKLM/Software/Hyperion* nodes
HKLM/System/CurrentControlSet/Services/
Essbase outline files for your applications
Essbase data full export
Essbase Calc scripts and substitution variables
Business Rules .properties file in the WEB-
INF/classes directory, e.g.
HYPERION_HOME/deployments/AppServer/Hyperio
nPlanning/webapps/
 Hyperion Planning components to backup

HyperionPlanning/WEB-INF/classes.
Back up the file system folder that contains Planning
Shared Libraries, such as C:/Windows/System32
Ensure that the backup of
HYPERION_HOME/products/Planning directory
includes these files, and back them up manually if it
does not:
PlanningCalcMgrLog4j.properties
PlanningSystemDB.properties
HBRServer.properties
essbase.properties
 Additional Backup Recommendations

Back up your applications and application databases

on a daily basis. Also back up before:
Refreshing applications
Moving applications to another server
Upgrading applications
Key planning milestones
 Recovery After Failure

Stop all product and related services

Replace backed up files and directories in the original
locations
Restore Planning relational databases
Restore Planning Essbase databases
Restart all servers and services
 Backup & Recovery - Further Information

For further information, including details on backup

and recovery of Essbase databases, see the Oracle
Hyperion Enterprise Performance Management
System Backup and Recovery Guide
The preceding is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracles
products remains at the sole discretion of Oracle.