Student Guide Vol I

Oracle University and Capitani IT Solutions E Informatica Ltda use only
Oracle® Hyperion Planning 11.1.1:

Create and Manage Applications
Volume I • Student Guide
D70015GC10
Edition 1.0
September 2008
D56305
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS
COMPUTER IS STRICTLY PROHIBITED
Authors Copyright © 2008, Oracle. All rights reserved.
Sandy Krameisen Disclaimer
Suzanne Gill This document contains proprietary information and is protected by copyright and
Theresa Songco other intellectual property laws. You may copy and print this document solely for your
own use in an Oracle training course. The document may not be modified or altered in
any way. Except where your use constitutes "fair use" under copyright law, you may
Technical Contributors not use, share, download, upload, copy, print, display, perform, reproduce, publish,
and Reviewers license, post, transmit, or distribute this document in whole or in part without the
express authorization of Oracle.

Emilya Altman
The information contained in this document is subject to change without notice. If you
Guillaume Arnaud find any problems in the document, please report them in writing to: Oracle University,
Jacob Bogitar 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Bryan Dehmler-Buckley
Suzanne Gill Restricted Rights Notice
Vicki Hardiman If this documentation is delivered to the United States Government or anyone using
Art Hetherington the documentation on behalf of the United States Government, the following notice is
applicable:
Janette Hollar
Sasha Ishenko U.S. GOVERNMENT RIGHTS
The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
Sandy Krameisen
disclose these training materials are restricted by the terms of the applicable Oracle
Diana Kravets license agreement and/or the applicable U.S. Government contract.
Robert Mead
Trademark Notice
Saju Philips
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
Ronald Reiley
names may be trademarks of their respective owners.
Eleanor Salerno
Theresa Songco
Shankar Viswanathan
Stuart Weiner
Editor
Susan Moxley
Graphic Designer
Asha Thampy
Publisher
Sandy Krameisen
Table of Contents 1
Module 1: Getting Started

Lesson 1: Planning Overview
Oracle’s Enterprise Performance Management System . . . . . . . . . . . . . . . . . . . . . . . 1-2
Planning Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Related Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Planning Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Client Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Web Application Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Database Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Planning Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Planning and Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Planning Repository and Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Dimension Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Dimensions and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Multidimensional View of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Drill-Down Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Essbase Terminology—Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Essbase Terminology—Families . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Essbase Terminology—Generations and Levels . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Lesson 2: Navigating Workspace

Workspace Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Launching Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Workspace User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Workspace Navigate Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Opening Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Navigating in Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Basic and Advanced Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Table of Contents
View Pane and Content Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Opening Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Module 2: Creating Application Structures
Lesson 3: Creating Dimensions Overview

Methods for Creating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Planning Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Required Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Period and Year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Scenario and Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
HSP_Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Other Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
User-Defined Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Dense Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Sparse Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
Creating Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Determining the Number of Data Blocks in a Database . . . . . . . . . . . . . . . . . . . 3-13
Creating Data Blocks and Retrieving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Determining Data Structure and Performance of Data Blocks. . . . . . . . . . . . . . . 3-16
Selecting Aggregation, Storage, and Calculation Options . . . . . . . . . . . . . . . . . . . . . 3-17
Selecting Aggregation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Selecting Data Storage Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Calculating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Calculating Data with Two-Pass Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Determining Performance Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Lesson 4: Managing Dimensions with Performance Management Architect

About Dimension Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Application Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Creating Applications Using Performance Management Architect . . . . . . . . . . . . . . . 4-4
Adding Dimensions to Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Working with Shared and Local Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Creating Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
ii Planning: Create and Manage Applications

Table of Contents
Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11

Modifying Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Property Value Inheritance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Alternate Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Inserting Members Using Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Managing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Reordering Children. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Deleting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Renaming Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Managing Orphan Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Finding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Creating Associations Between Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Organizing Shared Library with Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Filtering Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Sorting Dimensions in Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Working with Grid Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Selecting Members and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Creating Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Adding Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Number Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Triangulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Reporting Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Creating Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Automating Performance Management Architect Tasks . . . . . . . . . . . . . . . . . . . . . . 4-40
Lesson 5: Setting Up the Period, Year, Scenario, and Version Dimensions

Creating Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Period and Year Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Dynamic Time Series Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Setting Up DTS Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Creating Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Enable Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Use Beginning Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Exchange Rate Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Planning: Create and Manage Applications iii

Table of Contents
Creating Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Version Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Lesson 6: Setting Up the Entity Dimension

Entities Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Entity Members and Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Currency Value for Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Adding and Modifying Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Saving Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Deleting Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
Lesson 7: Setting Up the Account Dimension

Accounts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Account Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Time Balance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Saved Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Data Types and Exchange Rate Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Creating Account Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Adding and Modifying Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
Consolidation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Consolidation Order Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Lesson 8: Creating User-Defined Elements

User-Defined Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Attributes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Creating Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Attribute Values: Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Assigning Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Member Formulas Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
Adding Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Adding User-Defined Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Smart Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Modifying Smart Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Associating Smart Lists with Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Setting Data Forms to Use Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
iv Planning: Create and Manage Applications

Table of Contents
Module 3: Loading Metadata
Lesson 9: Loading Metadata from a File

Metadata Load Files Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Formatting Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Setting Up Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Setting Up Dimension Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Setting Up Parent-Child Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Setting Up Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11
Managing Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Loading Metadata Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Creating Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Mapping Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Mapping Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Running Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Viewing Job Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Viewing Import Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
Loading Metadata from Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
Lesson 10: Creating Applications

Application Creation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Plan for Application Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Currency Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Setting Up Application Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Selecting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Adding Dimensions from Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Changing Local Dimensions to Shared Dimensions . . . . . . . . . . . . . . . . . . . . . 10-19
Overriding Property Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Excluding and Showing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Filtering Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Synchronizing Local Dimensions with Shared Library . . . . . . . . . . . . . . . . . . . . 10-26
Activating Dimension Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28
Adjusting Performance Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Planning: Create and Manage Applications v

Table of Contents
Lesson 11: Deploying Applications

Deployment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
Validating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3
Comparing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5

Deploying Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7
Creating Essbase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-11
Reviewing Planning Outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-13
Essbase Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-14
Redeploying Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-15
Lesson 12: Setting Up Exchange Rates

Currencies and Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Exchange Rates Tables Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Creating Exchange Rate Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Entering Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Types of Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Calculating Implied Rates Through Triangulation . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Determining the Calculation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Exchange Rates and the HSP_Rates Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Generating Currency Conversion Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . .12-11
Copy Rates Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Currency Conversion Calculation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Calculate Currencies Business Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Module 4: Loading Data and Calculating the Database
Lesson 13: Loading and Calculating Data: Overview

Data Loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Requirements for Data Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Multicurrency Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Data Load Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Data Staging: Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Loading Data Using ETL Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Data Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
Calculations Within Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Calculations and Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
vi Planning: Create and Manage Applications

Table of Contents
Lesson 14: Loading Data

Loading Data Using Administration Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Creating Data Load Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Opening Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

Defining Header Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Associating Column Fields with Dimensions and Members . . . . . . . . . . . . . . . . 14-8
Replacing Text Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
Validating and Saving Rules Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
Fixing an Invalid Rules File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Loading Data Using Rules Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Staging Data with Interface Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
Creating Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Loading Data Using Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
Loading Data Using ETL Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-19
Module 5: Setting Up Security
Lesson 15: Provisioning Users and Groups

Planning Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Levels of Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Task Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Object Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
User and Group Provisioning Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Application Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
Provisioning Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Generating Provisioning Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
Lesson 16: Setting Up Access Rights to Planning Applications

Assigning Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Inheritance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Precedence and Inheritance of Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Planning: Create and Manage Applications vii

Table of Contents
Reporting on Access Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9

Importing Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Creating the Secfile.txt File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-11
Importing Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Creating Security Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16

Module 6: Designing Data Forms
Lesson 17: Creating Data Forms and Folders

Data Forms and Folders Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
Data Form Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Folder Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Data Form Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
Data Form Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Setting Up Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Setting Up Data Form Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Setting Row and Column Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Selecting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Creating Substitution and User Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Creating Asymmetric Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Setting Page and Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Setting Options on the Other Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Identifying Missing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Selecting Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Previewing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24
Creating Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
Selecting Business Rules on Composite Data Forms . . . . . . . . . . . . . . . . . . . . 17-27
Printing Data Form Definition Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28
Assigning Access Rights to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
Assigning Data Form Folder Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31
Lesson 18: Customizing Data Forms

Exporting and Importing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Creating Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Associating Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Setting Up Custom Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-11
viii Planning: Create and Manage Applications

Table of Contents
Specifying Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12

Specifying System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Setting Up Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Specifying Current Application Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
Managing User Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16

Creating User Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Applying User Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
Setting Up User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Setting Up E-mail for Workflow Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
Applying Alias Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
Setting Member Selection and Workflow Options . . . . . . . . . . . . . . . . . . . . . . . 18-20
Setting Individual Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
Setting Printing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
Setting User Variable Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
Module 7: Entering Data in Planning
Lesson 19: Entering Data

Submitting Data in Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Elements on the Enter Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Data-Entry Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Viewing Form Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Recognizing Cell Color Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Navigating Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
Copying and Pasting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Working with Non-Aggregated Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-13
Saving and Refreshing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
Viewing Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Selecting Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16
Launching Dimension Editor from Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
Spreading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18
Time Balance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20
Spreading Data by Using Grid Spreader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-22
Spreading Data by Using Mass Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-23
Adjusting and Annotating Plan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25
Performing Flexible Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Adding Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Planning: Create and Manage Applications ix

Table of Contents
Adding Cell Text and Account Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28

Attaching Documents to Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Adding Planning Unit Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-31
Adding Supporting Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32
Hiding and Showing Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-34

Calculating Data in Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-36
Calculate Data Form Calculation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-38
Calculate Currencies Calculation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-39
Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-40
Entering Data with Smart Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-41
Navigating Data Forms with Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-42
Lesson 20: Entering Data in Smart View

Smart View Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Integration of Smart View with Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Smart View Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Establishing Data Source Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Working with Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
Opening Data Forms in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Navigating Data Forms in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
Entering Data in Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-11
Adding Formulas to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
Calculating Data in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
Working with Ad Hoc Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
Navigating Ad Hoc Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
Zooming In and Out on Dimension Members . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
Pivoting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-19
Keeping and Removing Dimension Members . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21
Working with POVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-22
Smart View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
Submitting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
Working Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Taking Data Forms Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-28
Working with Planning Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-30
Synchronizing Data to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32
x Planning: Create and Manage Applications

Table of Contents
Module 8: Adding Business Rules
Lesson 21: Creating Business Rules

Business Rules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Calculation Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Business Rule Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Assigning Calculation Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
Determining Calculation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Launching Calculation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-11
Setting Up Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
Rule Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-16
Formula Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-17
Script and Condition Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19
Validating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-21
Deploying Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-23
Assigning Launch Access to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-25
Launching Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-27
Launching Business Rules—from Planning Data Forms . . . . . . . . . . . . . . . . . . 21-28
Launching Business Rules—from Planning Tools Menu . . . . . . . . . . . . . . . . . . 21-30
Lesson 22: Managing Business Rules

Templates Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Creating Custom-Defined Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Creating Business Rules with Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6
Setting Up the Copy Data Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
Setting Up the Amount–Unit–Rate Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
Setting Up the Allocate–Level to Level Template. . . . . . . . . . . . . . . . . . . . . . . . 22-12
Setting Up the Aggregation Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-14
Creating Rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-16
Validating Business Rulesets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-17
Deploying Business Rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-19
Lesson 23: Adding Variables and Formulas to Business Rules

Creating Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Setting Up Runtime Prompt Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4
Creating Formula Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9
Planning: Create and Manage Applications xi

Table of Contents
Adding Conditional Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-11

Creating Member Ranges in Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . 23-14
Designing Script Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-16
Creating Fixed Loops in Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-18

Module 9: Managing the Planning Process
Lesson 24: Managing the Approval Process

Process Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2
Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3
Planning Units and Process States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4
Reviewer Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-6
Impact of Entity Hierarchy on the Review Process . . . . . . . . . . . . . . . . . . . . . . . 24-8
Managing the Review Cycle for Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-10
Starting or Excluding Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-12
Checking the Status of Planning Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-14
Viewing the Details of Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-15
Changing the Status of Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-16
Printing Planning Unit Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-18
Copying Data Between Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-20
Clearing Cell Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-22
Copying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-25
Lesson 25: Creating Task Lists

Task Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2
Navigating Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4
Navigating Task Lists in Basic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5
Navigating Task Lists in Advanced Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8
Task List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-11
Working with Task List Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12
Building Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-14
Adding Tasks to Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-15
Setting Up Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-16
Setting Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-18
Assigning Access to Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-19
Using Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-20
Reporting on Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-21
xii Planning: Create and Manage Applications

Table of Contents
Lesson 26: Migrating Applications and Artifacts

Lifecycle Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2
Migration on Connected and Disconnected Environments . . . . . . . . . . . . . . . . . 26-3
Lifecycle Management Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-4

LCM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-6
Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7
Planning Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-8
Performance Management Architect Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . 26-10
Calculation Manager Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-11
Shared Services Artifacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-12
Viewing and Searching for Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-13
Process for Migrating Applications and Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-15
Migration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-16
Migration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-17
Migrating Directly from One Application to Another . . . . . . . . . . . . . . . . . . . . . . 26-19
Migrating Applications to an Intermediary File . . . . . . . . . . . . . . . . . . . . . . . . . . 26-21
Migrating Applications from an Intermediary File to a Destination Application . 26-23
Exporting and Importing Individual Artifacts for Editing . . . . . . . . . . . . . . . . . . . 26-25
Running the Lifecycle Management Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-27
Viewing LCM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-29
Migration Status Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-30
Artifact Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-32
Module 10: Creating Classic Applications
Lesson 27: Building Classic Applications

Classic Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-2
Classic Planning Application Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-3
Relational Databases for Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-5
Configuring Data Sources in Classic Application Wizard. . . . . . . . . . . . . . . . . . . . . . 27-6
Creating Applications Using Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . 27-8
Working with Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-9
Selecting the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-10
Setting Up the Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-11
Setting Up Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-13
Setting Up Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-15
Completing Application Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-16
Planning: Create and Manage Applications xiii

Table of Contents
Creating Essbase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-17

Reregistering Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-18
Lesson 28: Setting Up Classic Applications

Building Member Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-2
Modifying Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-4
Working with Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-6
Creating Alias Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-8
Smart List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-10
Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28-11
Associating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-13
Setting Up UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-14
Setting Up Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-16
Loading Metadata into Classic Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-17
Load File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-18
Running the Outline Load Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-20
Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-22
Exporting and Importing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-24
Lesson 29: Setting Up Business Rules for Classic Applications

Business Rules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-2
Business Rules Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Navigating Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-6
Components of Enterprise View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-6
Components of BR Language Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-7
Navigating the Rule Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-8
Business Rules Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-9
Creating Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-11
Building Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-12
Adding Actions to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-14
Adding the Aggregate Data Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-14
Adding the Copy Data Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-15
Adding the Clear Data Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-16
Adding the Create Blocks Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-16
Adding Formulas to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-17
Determining Components for Pro-Rata Ratio Formulas . . . . . . . . . . . . . . . . . . 29-18
Setting Up Pro-Rata Ratio Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-20
xiv Planning: Create and Manage Applications

Table of Contents
Setting Up Units-Rates Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-24

Setting Up Variable Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-25
Setting Up Custom Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-26
Specifying Data Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-27
Selecting Members for Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-28

Assigning Access to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-30
Starting Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-32
Starting Business Rules from Planning: Data Forms . . . . . . . . . . . . . . . . . . . . . 29-33
Starting Business Rules from Planning: Tools Menu . . . . . . . . . . . . . . . . . . . . . 29-34
Appendix A: Sharing Data Using Data Synchronization

About Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Creating Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Creating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Specifying Source and Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Linking Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Setting Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Applying Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Inserting Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Validating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Viewing Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Executing Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Planning: Create and Manage Applications xv

Table of Contents
xvi Planning: Create and Manage Applications

Preface 0

Welcome to Oracle® Hyperion Planning 11.1.1: Planning: Create and
Manage Applications!
Before you begin, please take a moment to review this section. The
preface presents an overview of the following information:
• Course objectives
• Structure of the course
• Course materials used in the class
• Conventions used in the book
Course Objectives
After completing this course, you should be able to:
• Create Planning applications
• Load data into Planning applications
• Set up security for users, groups, and members
• Create data forms and enter data by using data forms
• Set up and test business rules
• Review budget data by using process management
Preface
Course Structure
Oracle® Hyperion Planning 11.1.1: Planning: Create and Manage Applications is a 5-
day, instructor-led training course consisting of lectures, demonstrations, and hands-on
exercises. In this course, the instructor presents a topic conceptually by explaining its
purpose, demonstrating how it works, and then guiding the students through the

exercises. Demonstrations and hands-on exercises reinforce the concepts and skills
introduced during lectures.
Course Materials
You use two books in class—the student guide and the activity guide. The instructor may
also give you handouts.
Student Guide
The student guide is designed to be used by students and the instructor during lecture
time. It has 10 modules:
• Module 1 describes an overview of Planning and navigating Workspace.
• Module 2 describes setting up dimensions and members.
• Module 3 describes importing dimension members using EPM architect.
• Module 4 describes loading data and calculating the database.
• Module 5 describes setting up security.
• Module 6 describes designing data forms.
• Module 7 describes entering data in Planning.
• Module 8 describes adding business rules.
• Module 9 describes managing the planning process.
• Module 10 describes setting up Classic applications.
Each module contains lessons. Each lesson begins with a list of objectives followed by
the presentation of slides and accompanying text. The lesson ends with a summary of
the topics covered in the lesson.
xviii Planning: Create and Manage Applications

Preface
Activity Guide
The activity guide has two sections—exercises and exercise solutions.
Exercises

A critical part of the learning process is the challenge of completing real tasks associated
with each lesson. Each exercise is an opportunity to apply your new knowledge.
Exercise Solutions
The exercise solutions present the detailed steps to successfully complete the exercises.
Conventions
The following text conventions are used in this course book:
• Text to be typed, options to be selected, names of files and modules, and menu
selections are displayed in bold type. Examples:
- Select Clear Profile.
- Click YES to clear the profile.
• When available, figures are used to identify an object or task. Example:
Click Edit.
• Keyboard shortcuts are displayed as follows: Ctrl+Enter

• Alerts are used to direct your attention to different types of information.
NOTE
A note provides related information, common mistakes, or
cautions about the current topic.
TIP
A tip provides information that helps you work more
efficiently.
Planning: Create and Manage Applications xix

Preface
xx Planning: Create and Manage Applications

Preface 0

Welcome to Oracle® Hyperion Planning 11.1.1: Planning: Create and
Manage Applications!
Before you begin, please take a moment to review this section. The
preface presents an overview of the following information:
• Course objectives
• Structure of the course
• Course materials used in the class
• Conventions used in the book
Course Objectives
After completing this course, you should be able to:
• Create Planning applications
• Load data into Planning applications
• Set up security for users, groups, and members
• Create data forms and enter data by using data forms
• Set up and test business rules
• Review budget data by using process management
Preface
Course Structure
Oracle® Hyperion Planning 11.1.1: Planning: Create and Manage Applications is a 5-
day, instructor-led training course consisting of lectures, demonstrations, and hands-on
exercises. In this course, the instructor presents a topic conceptually by explaining its
purpose, demonstrating how it works, and then guiding the students through the

exercises. Demonstrations and hands-on exercises reinforce the concepts and skills
introduced during lectures.
Course Materials
You use two books in class—the student guide and the activity guide. The instructor may
also give you handouts.
Student Guide
The student guide is designed to be used by students and the instructor during lecture
time. It has 10 modules:
• Module 1 describes an overview of Planning and navigating Workspace.
• Module 2 describes setting up dimensions and members.
• Module 3 describes importing dimension members using EPM architect.
• Module 4 describes loading data and calculating the database.
• Module 5 describes setting up security.
• Module 6 describes designing data forms.
• Module 7 describes entering data in Planning.
• Module 8 describes adding business rules.
• Module 9 describes managing the planning process.
• Module 10 describes setting up Classic applications.
Each module contains lessons. Each lesson begins with a list of objectives followed by
the presentation of slides and accompanying text. The lesson ends with a summary of
the topics covered in the lesson.
xviii Planning: Create and Manage Applications

Preface
Activity Guide
The activity guide has two sections—exercises and exercise solutions.
Exercises

A critical part of the learning process is the challenge of completing real tasks associated
with each lesson. Each exercise is an opportunity to apply your new knowledge.
Exercise Solutions
The exercise solutions present the detailed steps to successfully complete the exercises.
Conventions
The following text conventions are used in this course book:
• Text to be typed, options to be selected, names of files and modules, and menu
selections are displayed in bold type. Examples:
- Select Clear Profile.
- Click YES to clear the profile.
• When available, figures are used to identify an object or task. Example:
Click Edit.
• Keyboard shortcuts are displayed as follows: Ctrl+Enter

• Alerts are used to direct your attention to different types of information.
NOTE
A note provides related information, common mistakes, or
cautions about the current topic.
TIP
A tip provides information that helps you work more
efficiently.
Planning: Create and Manage Applications xix

Preface
xx Planning: Create and Manage Applications

M O D U L E 1
Getting Started 1

Overview
The aim of this module is to provide an overview of the product features,
capabilities, components, and architecture of Planning. You also learn
about the relationship between Planning and Essbase. You navigate the
Workspace and access Planning using Workspace.
Lessons in this module include:
• Planning Overview
• Navigating Workspace
L E S S O N 1
Planning Overview 1

Objectives
At the end of this lesson, you should be able to:
• Explain Oracle’s Enterprise Performance Management system
• Describe Hyperion components
• List the main features of Planning
• Describe the product architecture of Planning
• Explain the relationship between Planning and Essbase
Module 1 Getting Started
Lesson 1 Planning Overview
Oracle’s Enterprise Performance Management

System

EPM Workspace
Performance Management
Applications BIBIApplications
Applications
Business Intelligence Foundation
Fusion Middleware
OLTP & OD S D ata Wa rehouse OLA P S AP, Or ac le , Siebe l, Ex ce l B usine ss

Sy ste ms D ata Ma rt Pe ople Soft, C us tom XML Pr oc es s
Copyright © 2008, Oracle. All rights reserved.
Oracle’s Enterprise Performance Management System

Oracle’s Enterprise Performance Management system is a portfolio of technology and
applications that include category-leading financial performance management
applications, operational BI applications, BI foundation and tools, and data warehousing.
It also leverages Oracle’s Fusion Middleware technologies, such as Oracle Application
Server and Oracle Identity Management.
It has these characteristics:
• Pervasive—It enables all levels of your organization to see information optimized for
their role.
• Comprehensive—It incorporates information from your financial performance
management, operational intelligence, and transactional applications.
1-2 Planning: Create and Manage Applications

• Hot-pluggable—It integrates with any data source, extraction, transformation and

load (ETL) tool, major business application, application server, security
infrastructure, portal technology, front-end and analytical tools, and database.
Performance Management Applications

Oracle’s performance management applications are a modular suite of integrated
applications that support the entire financial management cycle of goal setting, modeling,
planning, monitoring, analysis, and reporting. Applications include:
• Oracle® Hyperion Financial Management, Fusion Edition
• Oracle® Hyperion Performance Scorecard, Fusion Edition
• Oracle® Hyperion Strategic Finance, Fusion Edition
• Oracle® Hyperion Planning, Fusion Edition
• Oracle® Hyperion Capital Asset Planning, Fusion Edition
• Oracle® Hyperion Workforce Planning, Fusion Edition
• Oracle® Hyperion Profitability and Cost Management, Fusion Edition
• Oracle® Hyperion Financial Data Quality Management, Fusion Edition
• Oracle® Strategic Operational Planning, Fusion Edition
BI Applications
Oracle BI applications are pre-built vertical and horizontal analytic applications that
enable organizations to gain greater insight and value from a range of data sources and
applications, including Oracle E-Business Suite, PeopleSoft, Siebel (Customer
Relationship Management system), and third party systems such as SAP (Enterprise
Resource Planning system). Applications include:
• Oracle® Financial Analytics
• Oracle® HR Analytics
• Oracle® Order Management and Fulfillment Analytics
• Oracle® Supply Chain Analytics
• Oracle® Sales Analytics
• Oracle® Service Analytics
• Oracle® Contact Center Analytics
Planning: Create and Manage Applications 1-3

• Oracle® Marketing Analytics

• Oracle® Usage Accelerator Analytics for CRM
Business Intelligence Foundation

The core technology of Oracle’s EPM System is a highly scalable Business Intelligence
Foundation. This foundation utilizes a common enterprise information model as the
consistent semantic layer. This foundation has three specialized servers to meet your
reporting and analytical needs.
• Essbase – the leading OLAP Server for building forward-looking analytic applications
• BI Server – highly scalable federated query engine for aggregating disparate data
sources
• Predictive Analytics – Oracle Real-Time Decisions – a predictive analytics engine for
embedding BI into operational processes
Fusion Middleware
Fusion middleware provides an open, comprehensive, standards-based approach for
deploying service-oriented architectures (SOAs) using Web services, an enterprise
service bus, and Oracle BPEL (Business Process Execution Language) Process
Manager. Its portfolio includes products for integration, business process management,
business intelligence, and data management; developer tools for applications,
databases, and BI; and many other components. Examples include:
• Oracle Application Server (Java application server)
• Oracle Coherence (scaling)
• Oracle Master Data Management Suite (data management)
• Oracle Collaboration Suite (e-mail and content management)
• Oracle Identity and Access Management Suite (identity management)
• Oracle WebCenter Suite (context-rich user interface with Web 2.0)
• Oracle SOA Suite (business rules, process deployment, Java development, business
activity monitoring with dashboards and alerts, application integration over the
Internet and across other applications)
• Oracle Portal (out-of-the box enterprise portal)

Planning Features

Planning has the following features:
• Multidimensional data structure
• Target setting and bottom-up planning
• Iterative planning cycles
• Complex business rules and allocations
• Web-based data entry; management of the planning cycle
• Currency conversion for multicurrency applications
• Headcount and salary expense modeling
• Metadata and data transfer between Planning applications
and other Hyperion products
Planning Features
Planning is a Web-based budgeting and planning solution that drives collaborative,
event-based, operational planning processes through the organization for a wide range
of financial and operational needs. Planners have the flexibility to adapt rapidly to
changes in direction, ensuring that plans are always current, relevant, and functional.
Powered by Essbase, Planning uses a multidimensional data structure for flexible data
collection and analysis.
Planning also supports driver-based plans that are based on global assumptions, such
as interest rates and head count.

Product Components

• Planning
• Essbase
• Administration Services
• Workspace
• Performance Management Architect
• Calculation Manager
• Smart View
• Financial Reporting
• Shared Services
Product Components
You use the Planning Web interface to deploy applications to planning organizations. To
extend the power and flexibility of Planning, you use it with other Hyperion products.
Product Description
Essbase Enables you to store Planning application data (Planning
runs on top of Essbase.)
Administration Services Interfaces to Essbase Server, using Essbase
Administration Services Console, and enables you to
design, develop, maintain, and manage multiple Essbase
applications and databases.
Performance Management Enables you to manage dimensions and applications.
Architect
Workspace Enables you to navigate and manage Planning applications

Product Description
Calculation Manager Enables you to use a graphical user interface to create
calculation scripts
Smart View Enables you to enter Planning data in Microsoft Excel
spreadsheets, using the same functionality as Planning,

and to take Planning data offline to work disconnected from
the data source
Financial Reporting Enables you to create reports and charts for Web or print
for analysis and distribution of budget plans
Shared Services Enables you to provision users from external systems to
Hyperion products and to share data and metadata among
Planning applications or between Planning and other
Hyperion products

Related Products

• Workforce Planning
• Capital Asset Planning
• Performance Scorecard
• Strategic Finance
• Financial Management
• Web Analysis
E nterprise Performance Management Solutions
Dashboarding and Scorecarding

Planning, Budgeting, Consolidation
Modeling
and Forecasting and Reporting
Related Products
Several complementary Hyperion products are integrated with Planning, completing the
Financial Performance Management solution.
Product Description
Workforce Planning Enables you to handle workforce, salary, and compensation
planning
Capital Asset Planning Enables you to plan for new asset purchases and existing
asset actions
Performance Scorecard Enables you to communicate strategy, set goals, and
measure and monitor business performance
Strategic Finance Enables you to easily test financial models, create
contingency plans, and form alternative strategies

Product Description
Financial Management Enables you to consolidate results, reduce the cost of
regulatory reporting compliance, and gain important insights
into performance
Web Analysis Enables you to transform data into insightful information

through easy-to-use, highly graphical displays and robust
analytics

Planning Architecture
Client

Smart Vi ew Client Offline Client
Web
Application
Financial Shared Services, Java Performan ce Planning Web EPMA Web
Reporting Server App lication Server for Management Server Server
Planning , Perfo rmance Architect
Managemen t Architect, Dimension Server
Administration Services
Database
Performance Management Plann ing Essbase

Architect RDBMS RDBMS
Planning Architecture
Planning is a multitier application that combines the advantages of Essbase (a
multidimensional database) and a relational database to optimize performance and
maintenance.
Client Tier
The client tier contains the Smart View client and the Offline client.
Planning administrators use the client tier to enter data, perform process management,
manage users and security, launch business rules, copy versions, develop data forms,
and perform other administrative tasks.
In the client tier, you can enter data through spreadsheets by using Smart View.

Web Application Tier

The application tier consists primarily of the following servers:
• Financial Reporting server
• Shared Services, Java Application server (for Planning, Performance Management

Architect, and Essbase Administration Services)
• Performance Management Architect Dimension Server
• Web servers for Planning and Enterprise Performance Management Architect (EPMA)
NOTE
The Web server can be on a separate machine or on the same machine as the
Planning application server. The Web server enables you to access Planning
applications from a Web client through a Web browser. The Web server uses
Hypertext Transfer Protocol (HTTP) as the communications protocol.
Database Tier
The database tier consists of a third-party relational database management system
(RDBMS) and Essbase. The relational database is used primarily to store the
application’s definition. The following information is stored in the RDBMS:
• Application framework*
• Dimensions, dimension members, and properties*
• Exchange rates*
• Member access (security filters)*
• Data form design definitions
• Planning units
• Annotations (planning unit, account, and cell text)
• Supporting details*
• Process management workflow status
• Job Status
NOTE
Items with an asterisk (*) are updated to the Essbase databases during
application refreshes.

User Roles

Shared Services Roles
• Administrator
• LCM Administrator
• Dimension Editor
• Application Creator
• Calculation Manager
Administrator
User Roles
Planning meets the needs of multiple users within an enterprise-wide budgeting cycle.
You can set up users with several different types of user profiles to reflect the necessary
access.
The following global Shared Services roles are also used in Planning:
• Application Creator— Creates applications. This is a Performance Management
Architect role.
• LCM Administrator— Runs the Artifact Lifecycle Management utility to promote
artifacts or data across product environments and operating systems. You can work
with Lifecycle Management to move artifacts between development, test, and
production environments. Information on Lifecycle Management will be covered in
another lesson.

• Dimension Editor — Creates profiles and imports dimensions. This is a Performance

Management Architect role.
• Create Integrations — Creates Shared Services data integrations (the process of
moving data between applications) using a wizard.

• Run Integrations — Views and runs Shared Services data integrations.
• Calculation Manager Administrator — Administers calculation manager functions in
Planning.

Performance Management Architect

• Create metadata and manage applications
– Maintain a centralized repository
– Load metadata by using flat files or interface tables
– Create Planning applications
– Create and work with Planning applications and dimensions
• Synchronize data
• Create and maintain business rules
– Design, validate, and administer business rules
– Set up reusable components that can be shared
in different applications
Performance Management Architect

Performance Management Architect is a feature set in Planning that enables budget
administrators to view, manage, create, validate, and deploy applications within one
interface. You maintain metadata and applications in a central repository. To populate
dimensional metadata, you can import the metadata from flat files or interface tables.
Using the Data Synchronization feature in Performance Management Architect,
administrators can create data movement synchronizations between Hyperion
applications, create data mappings for reuse, and create flat file and staging area
mappings to import data into Hyperion applications.
You create and manage business rules with Performance Management Architect’s
graphical rule designer - Calculation Manager. You can design, validate, and administer
business rules in a central repository for use in Planning, and Financial Management
applications. You can set up reusable components that can be used by different
applications. Predefined templates are provided for frequently used calculations.

Planning Interface

• Manage Planning components
– Manage data forms, task lists, user variables
– Assign member access
– Copy data (including supporting details)
– View statistics and run administration reports
• Enter data, supporting details, and annotations
• Run business calculations
• Manage workflow
– Manage the Planning process
– Copy data between versions
Planning Interface
You use Workspace to access Planning. Administrators and Interactive Users can
provide flexibility and user guidance to budget preparers (planners) by defining user
variables and task lists. You can also define data forms for data entry and assign access
to the appropriate users and groups.
Budget administrators, budget analysts, and budget preparers can all enter and submit
data for review and approval, run business calculations, and enter annotations.

Planning and Essbase

Performance
Management
Architect Repository
Workspace
Interface Pl anni ng
Repository
Java Application
Ser ver
Essbase Server
Planning and Essbase

Planning uses Essbase to store data, metadata, and as a rules engine. To store the data,
you also store the dimension hierarchies in Essbase so that Essbase maintains the
relationships for the data values.
When you deploy an application, Performance Management Architect creates tables and
appropriate values in your Planning relational database, creates an application and
outline in Essbase without the need to refresh the cube within the Planning Interface,
and creates the HSP_Rates dimension for multicurrency applications.
Planning stores the application definition in its own relational databases. It uses the
definition information to create the necessary Essbase databases and security privileges
for your application. The plan data that end users enter in a Planning application is
stored in the Essbase databases created for the application.
Prior to application deployment, Performance Management Architect stores the
application data in its own Performance Management Architect relational database.

Planning Repository and Essbase

Planning Relational Database Essbase
Security Security
Metadata Metadata
Foreign Exchange Rates Foreign Exchange Rates
Smart Lists Smart Lists (numeric values after data save)

Process Management Details Data
Annotations/ Cell Text/ Supporting Details Business Rules
Task Lists Rules Files
Preferences Currency Calculation Scripts
Application Setup Substitution Variables
Data Forms
User Variables
Planning Repository and Essbase

Dimensions and members are stored in the Essbase databases as well as the Planning
repository. Data values are stored in Essbase. Some information is stored only in the
Planning relational database. For example, planning unit annotations, account
annotations, cell text, and supporting details are stored in the Planning relational
database. You can report on these annotations and details with Financial Reporting.
Smart list information is stored in the relational database. After you enter a smart list
value into Planning and save the data, the numeric value associated with that smart list
member is stored in Essbase.

Dimensions

Structural elements of an application that describe and hold
data.
Account Entity Period
Dimensions
Dimensions are the structural elements of an application that describe and hold data.
Examples of dimensions are Account, Entity, and Period.
The elements that compose a dimension are called members. For example, California
and Connecticut are members of the Entity dimension.
The dimensions defined in a Planning application become the dimensions in the
Essbase outlines and databases.

Dimension Hierarchies

Parent
Child of GrossMargin;
parent of Sales and
OtherRevenues
Descendants
of GrossMargin
Dimension Hierarchies
Members of a dimension are arranged in hierarchies. Members in a hierarchy exist at
different levels. Some members, siblings, are at same level and have relationships to
other members of the hierarchy.
Upper-level members are called parent members, and the members immediately below
the parent members are referred to as their children. All members below a parent are
referred to as descendants. The bottom-level members of a hierarchy are called base-
level members.
The graphic on the slide shows a part of the dimension hierarchy of the Account
dimension. In this hierarchy, the TotalRevenues member is a child of GrossMargin. Sales
and OtherRevenues are children of TotalRevenues and descendants of GrossMargin.
Sales and OtherRevenues are also base-level members.

Dimensions and Data

Data aggregated
to parents based on
aggregation options.
+ Add
Data is input
into base-level - Subtract
members. * Multiply
/ Divide
~ Ignore
Never
Dimensions and Data

Data is entered into the base-level members of the dimensions, not into the parent
members, unless you are working with a target version. You use target versions to
perform top-down budgeting by setting targets at the parent level. The values for the
parent-level members are aggregated from the values of their children when the
Planning database is calculated in Essbase.
For the example shown on the slide, the data values from the base-level members are
rolled up to the parent-level members. TotalRevenues (+) and TotalCosts (-) are then
rolled up to their parent GrossMargin.


Multidimensional View of Information
For the example shown on the slide, each cube represents a different view of a five-
dimensional database. The highlighted portion in each cube indicates the same data
value.
Data is represented in multidimensional form, and hierarchies are represented within
each dimension. As your analytical needs change, you can switch easily from one to
another form of the data.

Drill-Down Process

Period E ntity Account Customer
Income All
Year Worldwide
Statement Customers
Quarter N America Net Income Retai l
Month East IBT R001
O perating
New York
Margin
Drill-Down Process
Drilling down is an analytical technique by which you navigate through levels of data,
ranging from the most summarized (top) to the most detailed (bottom).

Metadata

3689.00 Data
Metadata
January FY08 Actual Final Net Sales for Alliance Merchandise in

New York is 3689.00.
Metadata
Metadata is defined as the structural elements of an application that describe and hold
data. Examples of metadata are dimension names, member names, properties, and
security.
For the example shown on the slide, the circled dimension member labels are the
metadata. The metadata describes what the data value represents.

Essbase Terminology—Hierarchies

Outline
Dimensions
Members
Essbase Terminology—Hierarchies
Essbase uses hierarchical and familial terms to describe the roles and relationships of
members in an outline. Within the tree structure of the database outline, a consolidation
is a group of members in a branch of the tree.
Hierarchical Term Definition

Outline Representation of the relationship among the members in the
database
Dimension Perspective on the data being analyzed
Member Discrete component making up a dimension
Attribute Characteristic of a member in an outline
Attribute dimension Dimension tagged as an attribute that contains members that
help to describe another dimension in the outline

Essbase Terminology—Families

Dimension Period
Year Total
Qtr1 Ancestors of April
Siblings
Descendants of Qtr2 Parent of April
Year Total
April Child of Qtr2
Essbase Terminology—Families
The following table summarizes the common familial terminology used in Essbase.
Familial Term Definition

Descendant Any member in a branch below a member
Ancestor Any member in a branch above a member
Parent Member that is the immediate ancestor of a member
Child Member that is the immediate descendant of a member
Sibling Child member with the same parent as another member

Essbase Terminology—Generations and Levels

Gen 1 Level 3
Gen 2 Level 2
Gen 3 Level 1
Gen 4 Level 0
Leaf Node
Gen 3 Level 0
• Generate reports using dynamic member selection.

• Include level and generation references in calculation
scripts.
• Load metadata into Essbase loading by level or generation.
• Create Web Analysis documents by level or generation.
Essbase Terminology—Generations and Levels

The following table summarizes the common generation terminology used in Essbase.
Generation
Term Definition
Generation Position within the hierarchy of a dimension, counted from top to bottom
Level Position within the hierarchy of a dimension, counted from bottom to top
Leaf node Member that has no children
The term generation describes a member’s location within the outline hierarchy from a
particular perspective. The generation number identifies the branch on which the
member lies in reference to its distance from its dimension name. Generations are
absolute and are determined by counting from the top of their dimension to their
descendants.

Level describes a member’s location in the outline, counting from the bottom to the top.
Levels are a relative and the level depends on the starting point in the hierarchy. The
example on the slide shows a portion of an outline labeled by both generation and level.
Customer is always generation 1, while its level changes based on the starting point in
the hierarchy. For example, if N002 is the starting point for determining the level,

Customer is level 3 whereas if No Customer is the starting point for determining the level,
Customer is level 2.

Summary

In this lesson, you should have learned to:
• Explain Oracle’s Enterprise Performance Management system

• Describe Hyperion components
• Describe the main features of Planning
• Describe the product architecture of Planning
• Explain the relationship between Planning and Essbase

L E S S O N 2
Navigating Workspace 2

Objectives
• Launch Workspace
• Describe the user interface components
• Open applications
• Navigate Planning
Lesson 2 Navigating Workspace
Workspace Overview

Workspace
Performance Management Architect Planning
Manage E nterprise Financial

information
Oracle Hyperion applications Planning output
Workspace Overview
Workspace provides a centralized interface for viewing and interacting with content
created using Hyperion financial applications, such as Planning and Financial
Management, and reporting content.
Workspace provides the following benefits:
• Single user logon: Users log on to Workspace to access both reporting and analysis
content and Planning.
• Single console for application management and creation: Users create, manage, and
deploy applications from a single location. These applications are opened in
Planning for data retrieval and data output.
• Centralized repository of key dimensional elements for Hyperion products
• Centralized console for controlling data flow between applications
• Audit logging and process controls

From Workspace, you can perform the following tasks:

• Build and manage applications
• Manage data sources and manage metadata and data

• Perform planning and consolidation application tasks
• Create rules with Calculation Manager
• Upgrade applications so that you can manage them in Shared Library
• Run or view highly formatted financial and operational reports from most data
sources, including from Planning and Financial Management
• Conduct high-performance, multidimensional modeling, analysis, and reporting with
Essbase
• Use Interactive Reporting to generate ad hoc relational queries, self-service reports,
and dashboards against ODBC data sources
• Run high-volume, enterprise-wide reporting for production reporting
• Use Web Analysis to perform interactive ad hoc analysis, presentations, and
multidimensional data reporting
• Generate enterprise metrics for management metrics and analysis and present
information in easy-to-use, personalized, interactive dynamic dashboards
• Access and interact with other published content, like Word or Excel documents
• Migrate entire applications or individual application artifacts to different servers

Launching Workspace

The password is case-sensitive.
Launching Workspace
You launch Workspace from a Web browser by using the following Uniform Resource
Locator (URL) to display the logon page:
http://<web server>:<port number>/workspace
To launch Workspace:
1. In your web browser, enter the Workspace URL, and press Enter.
The Workspace Logon screen is displayed.
2. Enter your user name and password, and click Log On.
The Workspace user interface is displayed.

Workspace User Interface

Navigate menu Menu bar Standard toolbar

Process bar
Adjuster
Document
tab bar
View pane Content area
Workspace User Interface

Workspace includes the following elements:
Element Description
Adjuster Adjusts the size of the view pane and content area
Content Area Displays active-module items, tasks, or files
Document tab bar Displays information specific to the current module
Menu bar Provides commands that organize tasks and modules
Navigate menu Provides access to Workspace modules
Process bar Displays location of the current folder, item, or step
Standard toolbar Provides shortcuts for performing tasks
View Pane Provides buttons that enable jumps between panels

Workspace Navigate Menu

P erformance
Management
Architect menu
Workspace Navigate Menu

The Navigate menu enables you to navigate to the modules available within Workspace.
The following table describes the commands on the Navigate menu:
Command Description
Applications Access Planning and Financial Management
applications (Applications are displayed only when a
user has rights and applications are available.)
Administer > Classic Application Create, delete, and register classic applications.
Administration

Command Description
Administer > Dimension Library • Manage dimensions and dimension properties from a
centralized location
• Create dimension import profiles enabling dimension
updates from flat files and relational database

interface tables
• Add, delete, and modify dimension members
• Modify dimension and member properties
Administer > Application Library • Create Planning, Financial Management, Profitability
and Cost Management, and Essbase applications that
are based on Planning and Financial Management
dimension sets
• Manage all applications in one centralized location
• View the data flow between applications
• Migrate applications to different servers
• Deploy applications to Planning, Financial
Management, Profitability and Cost Management,
Enterprise Analytics, or Essbase Analytics
Administer > Data Synchronization • Create data movement synchronizations between
Hyperion Applications (For example, an administrator
can synchronize data between two Planning
applications; between two Financial Management
applications, and between one Planning application
and one Financial Management application.)
• Create data mappings that can be reused
• Create flat file and interface table mappings to import
data into Hyperion applications
Administer > Application Upgrade Transfer Planning applications from Planning to EPMA
Administer >Library Job Console View a summary of Dimension Library and application
activities, including imports, deployments, and data
synchronizations
Administer > Managing Planning Create, edit, and delete Planning datasources
Datasources
Administer > Calculation Manager Create, validate, and deploy business rules and
business rules sets

Opening Applications

Opening Applications
In Planning, all data is processed within applications. An application is a related set of
dimensions and dimension members that meet a specific set of analytical or reporting
requirements. For example, you can have an application named Test used for
development and a separate application named Training to roll out to end users.
To access Planning applications

1. Select Navigate > Applications > Planning.
2. Select an application.

Navigating in Planning
Planning m enus Planning toolbar

V iew
pane
Open application Content area
Navigating in Planning
After you access Planning from the Navigate menu, the application is displayed in a
window with a tab at the bottom left. Planning provides several tools for selecting tasks
and documents:
• Planning menus
• Planning toolbar
• The View pane
Menus
You have access to only menu commands to which you are assigned access based on
your user profile. For example, users who are assigned the administrator role have
access to all functions on the Administration menu. Users who are assigned the
interactive user role have limited access to the Administration menu.

File Menu
The following table describes the commands under the File menu:
New Create new documents, personal pages, workspace pages, data

forms, reports, task lists, user variables, smart lists, or menus

Open Open a new document, application, or URL
Close Close current, others, or all
Save Save data input to data forms
Print Print the current screen
Workflow Manage the Planning process or copy versions
Spreadsheet Export Export a data form to a spreadsheet
Open in Smart View Open the current data form in Smart View
Preferences Set general, authentication, explore, Web Analysis, Financial
Reporting, Interactive Reporting, Planning, or SQR Production
Reporting preferences
Log Off Log off Planning
Exit Exit Workspace
Edit Menu
The following table describes the commands under the Edit menu:
Adjust Increase or decrease data values by a percentage

Grid Spread Spread data values across multiple dimensions on the grid
Choose from allocation options: proportional, evenly split, and fill
Mass Allocate Allocate data values across multiple dimensions
Choose from allocation options: proportional, evenly split, and fill
Allocate data beyond what is displayed on data forms
Cut, Copy, Paste Cut, Copy, or Paste data from one or more cells into one or more
cells
Add Row Add rows to a data form on-the-fly, only available if the data form
was defined to allow rows to be added dynamically
Launch Rules Launch a Business Rule from a data form
Annotate Planning Unit Add comments to a planning unit
Cell Text Add comments to a specific cell or range of cells at any level in a
data form

Supporting Detail Add detail that will aggregate the cell value in a data form
Lock/Unlock Cells Lock cells to ignore cells when spreading data
Initialize Workforce Load predefined dimensions and members, data forms, smart
lists, member formulas, business rules, and menus to prepare

plans for workforce resources. Members, forms and business
rules can be customized.
Note: Initialize Workforce is displayed only if the option was
selected and configured during the configuration of Planning.
Initialize Capex Load predefined dimensions and members, data forms, smart
lists, member formulas, business rules, and menus to prepare
plans for capital expenditures. Members, forms and business
rules can be customized.
Note: Initialize Capex is displayed only if the option was selected
and configured during the configuration of Planning.
View Menu
The following table describes the commands under the View menu:
View Pane Hide or show the View Pane

Refresh Refresh the current view to reflect what is stored in the database
Instructions View instructions for a data form, available only if the data form
includes instructions
Currency Look up a currency code
View Account Enter, edit, or view comments for a specific account, entity,
Annotations scenario, and version combination
Edit Account
Annotations
Basic Mode Toggle the view for tasks between Basic Mode and Advanced
Mode
Task List View task lists to which you have access; View task status and
create a task list report. You must be in Basic Mode to create a
task list report.
Administration Menu
The following table describes the commands under the Administration menu:
Manage Data Forms Create, edit, move, delete, and assign access to data forms
Manage Task Lists Create, edit, move, delete, and assign access to task lists

Manage Menus Create and edit menus

Manage User Variables Set up variables that are assigned to data forms by specifying
the variable’s value
Manage Smart Lists Create smart lists and smart list members for classic Planning

applications
Manage Properties Manage application and system properties
Dimensions Set and change access for dimensions, such as Account, Entity,
Scenario, Version, and UDAs (user-defined custom dimensions)
Copy Data Copy data, including supporting details, from one planning unit
to another
Clear Cell Details Clear cell details
Reporting Print Planning information including form definitions, user and
group report lists, access assignments for dimensions, planning
unit annotations, process status lists, and active application
auditing
View Statistics View information about the Planning application and its usage
Application Settings Set Planning application-wide preferences
Business Rule Security Assign launch security to business rules
Create Application Create Classic applications
Delete Application Delete Classic applications
Register Application Register Classic applications with Shared Services
Manage Data Source Create data sources for classic Planning applications
Copy Document Link Link tasks in task lists to application pages
Data Load Use the Data Load Administration page to set up the data to load
Administration directly through the Planning Adapter or through flat files
Manage Database Create and refresh Essbase databases with changes made to
relational databases, such as with exchange rates updates
Manage Currency Create currency conversion calculation scripts
Conversion
Manage Exchange Rates Create and set up exchange rate tables and exchange rates and
delete exchange rate tables
Manage Security Filters Create security filters for users
Favorites Menu
You use the Favorites menu to select which favorites to show on the favorites menu.

Tools Menu
The following table describes the commands under the Tools menu:
Advanced Search Search the Workspace for documents

Install Interactive Reporting Web Client and Smart View

Install
Links Manage links to other products or URLs
Business Rules Launch business rules
Broadcast Message Create and send broadcast messages
Job Console View job status
Help Menu
You can access help on the currently selected task or document.
Planning Toolbar
The toolbar buttons open dialog boxes that you can use to manage documents, task
lists, and favorites and provide shortcuts to planning tasks.
The following table describes the buttons on the toolbar:
Button Purpose Description

Save Save data input on data forms
Refresh Refresh the data form with data stored in the database
Print Print the current screen
Adjust Increase or decrease values by a percentage or by a

value
Lock/Unlock Cells Lock or unlock cells when spreading data
Grid Spread Spread data across dimensions on the data form
Mass Allocate Run a Mass Allocate calculation
Cut, Copy, Paste Cut, Copy, or Paste values from one or more cells to one
or more cells on data forms

Button Purpose Description

Cell Text Add comments to a specific cell at any level in data forms
Add/Edit Document Add or edit documents to provide documentation for data

in cells
Supporting Detail Add detail that aggregates the cell value in data forms
Open in Smart View Open data forms in Smart View
Task List Open task lists if task lists are assigned to you
Status Check task lists status
Logoff Log off the application
Help Access help for the currently selected task or document

Basic and Advanced Modes

Basic mode limits users to the tasks and documents in the task
lists to which they have access.
Basic and Advanced Modes

Some users’ roles in the budgeting and planning cycle may require that the user only
perform a limited number of tasks and that those tasks be performed in a specified order.
Budget administrators and interactive users can set up task lists to help planners
navigate through their required tasks.
If task lists are assigned to you, you can choose to work with it in either Basic or
Advanced mode.
When you navigate in Basic mode, you use the view pane to select a task list to which
you have access. The task list page helps you focus on your predefined tasks. A
progress bar and navigation features are displayed to help you move between tasks and
monitor your status.

When you navigate in Advanced mode, you have access to all tasks, through menus and
toolbars, to which you are assigned based on your role. You are not guided through a
predefined list of tasks; you navigate freely to perform your tasks.
When you switch between modes, you return to the activity that you were performing
before you switched. For example, if you are working in a data form when you switch to

Basic mode, you are returned to the same form when you return to that mode.
To switch modes:
Perform an action:
• Select View > Basic Mode.
The view pane shows task lists to which you have access.
• Select View > Advanced Mode.
All menu functionality for your role and all functionality to which
you are provisioned are available.

View Pane and Content Area

Data form

View
pane
Business rules Content area
View Pane and Content Area

After you open a Planning application, the view pane and content area display your
selections.
For example, when you work with data form management, the View pane lists form
folders, data forms, and business rules. You can use the View pane to navigate from one
folder or data form to another. After selecting a specific data form, you see the contents
of that data form in the content area.
If you select Business Rules from the Tools menu, you see the Display Launchable
Rule/Rule Sets/ Script Only dialog box in the Content area. However, the view pane lists
form folders, and data forms. After you launch business rules, you can use the view pane
to navigate from the launch business rules dialog box and open a data form.

Opening Data Forms

Folder

Data forms
Opening Data Forms

Data forms are contained within the folders. After you select a folder, a list of data forms
within the selected folder is displayed on the view pane and in the content area. Only
those forms to which you have access are displayed. After you select a data form, it is
displayed in the content area.

Summary

• Launch Workspace
• Describe the user interface components
• Open applications
• Navigate Planning


M O D U L E 2
Creating Application Structures 2

Overview
The aim of this module is to create dimensions and members for a
Planning application. First, you identify required and user-defined
dimensions. Next, you describe dense and sparse dimensions and basic
concepts of data blocks. Finally, you create the dimensions and dimension
members for the databases for your Planning application.
• Creating Dimensions Overview
• Managing Dimensions with Performance Management Architect
• Setting Up the Period, Year, Scenario, and Version Dimensions
• Setting Up the Entity Dimension
• Setting Up the Account Dimension
• Creating User-Defined Elements
L E S S O N 3
Creating Dimensions Overview 3

Objectives
• List two methods for creating applications
• Describe plan types
• Identify required dimensions
• Identify user-defined dimensions
• Describe dense and sparse dimensions
• Create data blocks
• Set up aggregation, data storage, and calculation options
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Methods for Creating Applications
EPMA

• Create applications using a wizard
• Modify applications by dragging and dropping
• Design applications graphically in a central library which
includes tools for auditing, tracking and comparing information
• Duplicate applications for testing or what-if analyses
• Use dimensions and attributes across multiple applications
• Design graphical business rules in Calculation Manager
• Graphically manage data flows
Classic
• Create applications using a wizard
• Modify single applications using Dimension Editor
• Set up graphical business rules for complex calculations
Methods for Creating Applications

You can create applications using Enterprise Performance Management Architect
(EPMA) or Classic application administration. Different menus and options are available
for each type of application. For example, for applications created with Performance
Management Architect, you manage Smart Lists within EPMA. For applications created
with Classic administration, you can select Administration, then Smart Lists to use the
feature within Planning.
EPMA enables administrators to manage, create, and deploy Hyperion applications
within one interface. You create applications using an application creation wizard which
ensures that all required dimensions are included. Then you can work in a central library
to modify dimensions and metadata. For EPMA applications, you can use tools within the
central library to audit, track and compare information.
EPMA includes Calculation Manager which enables you to create, validate, and deploy
sophisticated calculations to solve Financial Management and Planning business
problems. Rules can be shared easily between applications.

You can use classic application administration to work with single Planning applications.
For Classic Planning applications, use the Classic Application Wizard to create and
delete applications, and register with Shared Services. You use the wizard to ensure that
all required dimensions are included in your classic application. Then you can modify
dimensions using Dimension Editor and can import metadata using an ETL tool. You can

load data either using a tool or using Essbase Administration Console. You can set up
complex calculations in Business Rules within Essbase Administration Console.

Plan Types

• Essbase database created for each plan type
• Three customizable plan types
• Data sharing between plan types
• Plan types set for applications, dimensions, and members
Bud geting
Ap plicatio n = Plan T yp e 1 Plan Type 2 Plan Type 3 Workforce Capital Asset
Additional modules
available for purchase
Plan Types
Plan types represent an Essbase database cube, each with their own dimensionality.
When creating an Essbase database for each plan type, you initially set them at the
application level. You also select plan types for dimensions and members. You select
one database in which to store data. Data values stored in one database are referenced
by another database, by sharing data for those members.

Planning Dimensions

Essbase
Planning Repository
Planning Dimensions
Planning data is stored in Essbase databases. Data storage in Essbase is different from
data storage in relational databases. Understanding how Essbase stores and retrieves
data is important for designing an application that functions efficiently.
Planning applications are organized by dimension. The dimensions in your application
represent the categories of data in your organization. For example, when you enter data
in a plan, you must identify what item you are budgeting. Budget items such as travel
expense and salary expense are in the Account dimension. You also need to identify the
time period for the item, such as current quarter or next quarter, in the Period dimension.
How you set up dimension properties affects the storage and calculation of information,
the efficiency of the database, and the display of information in data forms and reports.
You can define aliases for dimension members and view either the alias or the member
name in data forms and reports.

Required Dimensions

Six Required Dimensions* Other Dimensions
• Period • Alias
• Year • Smart Lists
• Scenario • UDA
• Version
• Entity
• Account
*Multicurrency applications require two additional dimensions

• Currency
• HSP_Rates
Required Dimensions
A Planning application has six required dimensions. For EPMA generated applications,
Aliases and Smart Lists are represented as dimensions. If you plan to use user defined
attributes (UDAs) for EPMA generated applications, you must set up a UDA dimension.
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
the administrator, you specify base time periods and distribution of weeks in the Period
dimension when you create applications. 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 in a plan, such as budget, actual, or
forecast, as well as the plan’s time span.

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 can 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.
NOTE
For dimension member names and alias names, you can include up to 80
characters, and you must make the name unique across all dimensions. You
cannot include the characters \ , or < > in the dimension name.
Currency
The Currency dimension identifies the currency in which values are displayed. You can
plan in one or more currencies by setting 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 conversions occur

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.
NOTE

The system generates the dimension HSP_Rates for multicurrency applications.
This dimension is visible only in Essbase.
Other Dimensions
In addition to the required Planning dimensions, you must set up an Alias dimension in
order to assign aliases to dimensions such as Account or Entity for EPMA applications. If
you want to use Smart Lists in your application, you must set up a Smart List dimension
for EPMA applications. For EPMA applications, you must set up a UDA dimension if you
want to associate UDAs to members.
NOTE
For Planning, you must include an Alias member named Default in the Alias
dimension.

User-Defined Dimensions

14 User-Defined Dimensions*
For example:
• Employee
• Product
• Channel
• Project
• Customer
• Salesrep –attribute dimension
*A Planning application can have a total of 20 dimensions.

Attribute, Alias, Smart List, and UDA dimensions are not
included towards the total of 20 dimensions.
If your organization requires further levels of plan detail than is provided in the Account
dimension, you can include user-defined dimensions or custom dimensions. For
example, your application can have a group of revenue accounts for revenue planning.
You can define a Customer dimension that you can use with the revenue accounts to
budget revenue on a per-customer basis. An application can have up to 14 user-defined
dimensions.
In Performance Management Architect, you can perform the following tasks:
• Assign plan types for user-defined dimensions at the dimension level, not the
member level. (You cannot delete user-defined dimensions.)
• Rearrange the dimension hierarchy
• Share members of user-defined dimensions

Dense Dimensions

Dense
Dimensions
Dense Dimensions
Multidimensional databases contain dense dimensions. A dense dimension is a
dimension that contains a high percentage of occupied data values in each combination
of dimensions. For example, when data exists for an entity, it typically exists for most or
all accounts and time periods. Account and Period are typically dense dimensions.

Sparse Dimensions

Sparse
Dimensions
Sparse Dimensions
Multidimensional databases also contain sparse dimensions. Sparse dimensions contain
a low percentage of occupied data values in each combination of dimensions. Sparse
dimensions have these characteristics:
• Data values are not smoothly and randomly distributed throughout the database.
• Data values do not exist for the majority of member combinations in the database.
For example, if each entity sells only to a subset of customers, most combinations of
entity and customer have no associated data. Entity and Customer are typically sparse
dimensions.

Creating Data Blocks

• Data is stored in data blocks.
• Data blocks are the cells formed by the intersection of
selected dimension members.
Mem bers of Dimension A
Members of
Dimension B
Creating Data Blocks

Essbase stores data in data blocks, rather than in records or rows. You can think of a
data block as a grid or spreadsheet with the dimension members on the rows and
columns. Data is stored in the cells formed by the intersection of the members of different
dense dimensions.
For the example two-dimension data block on the slide, Dimension A and Dimension B,
have five members each, and 25 cells are created for storing data.

Determining the Number

of Data Blocks in a Database

Entity (Sparse) Scenario (Sparse) Year (Sparse) Version (Sparse)
Entity Scenario Year Version
Corp Budget 2009 1st Draft
Final
Account (Dense) Period (Dense)

Account Period
Account1 Jan to Dec
Account2
Account3
Each block contains 36 cells

= (3 Accounts * 12 Time Periods)
Determining the Number of Data Blocks in a Database

The dense and sparse settings for dimensions determine the structure of the data blocks
and the number of data blocks in the database. The dense dimensions determine the
data block structure. A data block always includes all stored members of all dense
dimensions. By default, Account and Period are dense dimensions in Planning
applications.
NOTE
If your application uses currencies, the dense dimension HSP_Rates stores
exchange rates.
The data in a data block is stored at the intersections formed by the members of the
dense dimensions. For example, if the Account and Period dimensions are dense, the
combination of one time period (January) and one account (Sales) equals one cell of
data within a data block.

Sparse dimensions determine the number of data blocks in a database. You could
potentially have a data block for each unique combination of sparse dimension
members. By default, Entity, Scenario, Version, and Year are sparse dimensions. For an
application that uses currencies, the Currency dimension is set to sparse.

NOTE
If you add additional dimensions, such as Product or Customer, you can tag them
as either dense or sparse. The default is sparse.
Consider the simple database shown on the slide. There is potential for two data blocks
in the database:
• Corp -> Budget -> 2009 -> 1st Draft
• Corp -> Budget -> 2009 -> Final
The dense dimensions determine the data block structure, and so each data block has
36 cells (3 accounts × 12 time periods).

Creating Data Blocks and Retrieving Data

• A data block is not created until you enter data in a cell.
• Essbase checks to see whether the block exists.
• If a block does not exist, Essbase creates it.
• Data is retrieved by data block.
Creating Data Blocks and Retrieving Data

After you enter data in a data block, the data block is created. When data is posted to a
data block cell, Essbase first checks to see whether the data block exists. If it does not
exist, Essbase creates it. Because data blocks are based on unique sparse dimension
combinations, which typically do not have data for all members, this strategy helps
reduce database size.
Data is retrieved by data block. If a report or data form requests data from a data block
cell, Essbase retrieves the entire data block into memory. For example, if a report or
calculation requests the value in the cell for Corp -> Budget ->2009 -> 1st Draft ->
Account2 -> Feb, Essbase loads the Corp -> Budget -> 2009 -> 1st Draft data block into
memory and then retrieves the value from the Account2 -> Feb cell for this block.

Determining Data Structure

and Performance of Data Blocks

• Performance is typically best if the cells that need to be
calculated or viewed are in the same data block.
• Considerations for dense and sparse settings apply to
calculations.
• The number of cells in a data block grows exponentially as
dense dimensions are added to the data base.
Determining Data Structure and Performance of Data Blocks

The dense and sparse settings for dimensions determine data structure. The data
structure can have a significant impact on data retrieval and calculation time. Although
design considerations can vary significantly between applications, follow the general
guidelines for performance.
When you view or calculate data, you typically experience the best performance if the
cells are in the same data block.

Selecting Aggregation, Storage,

and Calculation Options

• Aggregation involves defining calculations based on
relationships in the hierarchy.
• Storage options define how data is maintained in the
database.
• Calculations are performed in a specified order.
Selecting Aggregation, Storage, and Calculation Options

A number of factors impact calculations in a database. You set up aggregation, storage,
and calculation options to define how data is calculated. Aggregation options determine
whether data is added, subtracted, multiplied, divided, ignored, or treated as a
percentage. Storage options define whether data is stored or calculated when requested.
Understanding the order in which the calculations are performed is important. This order
impacts calculation results.

Selecting Aggregation Options

Define calculations in the hierarchy based on parent-child
relations.
Aggregation options
• + Addition Net Income
Sales (+)
• - Subtraction COGS (-)
• * Multiplication
• / Division
• % Percentage
• ~ Ignore
• Never
Selecting Aggregation Options

You define calculations within dimension hierarchies using aggregation options.
Aggregation options determine how values of child members are aggregated to the
parent value.
For example, Sales and COGS might be children of the member Net Income. If you set
the aggregation option for the Sales member to addition and the aggregation option for
COGS to subtraction, then the aggregated value for the Net Income member represents
the Sales member minus the COGS member.
NOTE
Because dimension members can belong to more than one plan type, you can
specify different aggregation options by plan type.

Selecting Data Storage Options

Use storage options to optimize performance and disk usage.
Storage Option EPMA Application Classic Application

Store Data StoreData Store
Dynamic Calc and Store DynamicCalcAndStore Dynamic Calc and Store
Dynamic Calc DynamicCalc Dynamic Calc
Share Data ShareData Shared
Never Share NeverShare Never Share
Label Only LabelO nly Label Only
Selecting Data Storage Options

To optimize performance and disk usage, you select from the following storage and
calculation options for dimension members.
Store Data Stores data values of members.

Dynamic Calc and Calculates the data value the first time the member is retrieved and
Store then saves the value.
Dynamic Calc Calculates the data values each time the member is retrieved. The
value is not stored in the database.

Share Data Allows two or more members in the same dimension to share data
values.
Note: For EPMA applications, this option is automatically assigned
when you use insert shared member to create a shared member in
the hierarchy.

For classic applications, the data storage option is called Shared.
Shared is set automatically if you create a member with the same
name as another member in the hierarchy.
Never Share Prohibits two or more members in the same dimension from
sharing a data value.
Label Only Has no data associated with the member.
Dynamic Calc and Store

On the first retrieval, the data value is calculated and then stored. Subsequent retrievals
use the stored value. The Dynamic Calc and Store option is used infrequently. In most
cases, you can optimize your calculation and lower disk usage by using Dynamic Calc
when you calculate members of sparse dimensions. Use Dynamic Calc and Store for
members of sparse dimensions in the following situations:
• A sparse member with a complex formula
• A sparse member that users retrieve frequently
For members of dense dimensions, use Dynamic Calc for calculations to increase
retrieval time and regular calculation time. Disk usage is not lowered significantly.
Dynamic Calc
If a member is set to Dynamic Calc, Essbase does not calculate its data value during
regular database calculation; for example, when the CALC ALL function is executed,
Essbase calculates the data value upon retrieval; for example, Essbase calculates data
when it is retrieved into a data form.
Advantages of Dynamic Calc:
• Reduction in the regular calculation time of the database because Essbase has
fewer member combinations to calculate.
• Reduction in disk usage because Essbase stores fewer data values. Database size
and index size are reduced.
Dynamic Calc is most useful for parent-level dense dimension members. Since values
for Dynamic Calc members are not stored, the data block size is reduced, which
improves performance. However, retrieval time for the member is increased.

Use Dynamic Calc sparingly with sparse dimension members. Because each member of
a sparse dimension references a separate data block, a dynamic calculation that
includes many sparse members must retrieve data from a large number of data blocks.
Retrieving data from many data blocks can reduce performance. As a rule of thumb, use
Dynamic Calc for upper-level members of sparse dimensions only if those upper-level

members have six or fewer children.
Dynamic Calc guidelines:
• Do not use Dynamic Calc for base-level members for which users enter data. Data
values are not saved for Dynamic Calc members.
• Do not use Dynamic Calc for a parent member if you enter data for that member in a
target version. Parent members set to Dynamic Calc are read-only in target versions.
• Do not set a parent member to Stored if its children are set to Dynamic Calc. With
this combination, when a user saves and refreshes a data form, the new total for the
parent is not calculated.
Share Data and Never Share

Use Share Data when you want to allow for alternate rollup structures. You can set
members within the same dimension to share data values, enabling alternate rollup
structures within the application. For shared members, you must set the data storage to
Share Data so that the shared member is added when the Application is deployed.
Use Never Share when a parent has a single child that is aggregated to the parent. In
this case, set the parent to Never Share. You can set appropriate security for the child
member. Typically, you set the Currency, Entity, Version, and any custom dimensions to
Never Share. You typically set those dimensions’ members to Store Data or Dynamic
Calc instead of Never Share.
Label Only Data Storage

Label Only members are virtual members; they are typically used for navigation and
have no associated data. For example, you might have a parent member named
Statistical that groups statistical accounts such as Headcount and Interest Rate.
Because these accounts are not aggregated to a meaningful total, there is no need to
calculate or store a value for the member Statistical.
Making a dimension member Label Only helps minimize database space by decreasing
block size, which improves performance. You can also use Label Only members to group
members or to navigate and report more easily from Financial Reporting or Essbase
Smart View Provider.

Label Only guidelines:

• You cannot designate level 0 members as Label Only.
• Even though a Label Only member has no data associated with it, it can still display a
value. A parent member set to LabelOnly displays the value of its first child member.

• In single-currency applications, Label Only is the default data storage type for all root
dimensions. In multicurrency applications, LabelOnly is the default data storage type
for HSP_Rates, Account, Period, Year, and Scenario.
• You cannot assign attributes or member formulas to Label Only members.
• In multicurrency applications, you cannot apply the Label Only storage option to
members of the following dimensions: Entity, Version, Currency, and user-defined
dimensions. If you want to store exchange rates, you must set them to Never Share.
• The data storage option for children of Label Only parents is set to Never Share by
default.

Calculating Data

Essbase calculates the outline in the following order:
1. Account dimension
2. Time dimension
3. Other dense dimensions in top-down order
4. Other sparse dimensions in top-down order
5. Members that are tagged as Two-Pass Calculations
1st Pass 2nd Pass
Level 0 Data Calculated Data Calculated Data

(Before Two-Pass) (After Two-Pass)
Calculating Data
The calculation order in Essbase can affect the result of a calculation. Essbase
calculates the Account members first, the Period members second, and the remaining
dimensions according to their order in the database outline.
Sometimes the calculation of a member in one dimension depends on the calculated
result of members in a dimension that is not calculated until after the first dimension’s
calculation. You can assign the Two-Pass Calculation option to a member in such
situations. After Essbase calculates the database, a second pass calculates members
tagged Two-Pass Calculation.

Calculating Data with Two-Pass Calculations

Before Two-Pass
   
After Two-Pass
   
Calculating Data with Two-Pass Calculations

A good example of two-pass calculation is the calculation for the Margin Percent account
for North America. That calculation depends on the aggregated value of the Gross
Margin and Net Revenue accounts (Margin Percent = Gross Margin / Net Revenue).
Since the Entity dimension is calculated after the Account dimension, the aggregated
values are not available. To calculate Margin Percent correctly, Essbase must first
aggregate the values for the children of North America to derive the totals for Net
Revenue and Gross Margin. After these totals are calculated, a second pass is needed
to calculate the Margin Percent account for North America. To accomplish this task, you
select the Two-Pass Calculation option for the Margin Percent account.
The Two-Pass Calculation option is used primarily for members of the Account
dimension. For other dimensions, the Two-Pass Calculation option is valid only for
Dynamic Calc or Dynamic Calc and Store members.

Determining Performance Efficiency

Sparse
Dimensions
Determining Performance Efficiency

For a data form that contains only one member from each sparse dimension, Essbase
must retrieve only one data block to populate the form. Because the Account and Period
dimensions are dense, the cells for the account and time period members are already in
that data block.
If the Period dimension were tagged as sparse, data would need to be retrieved from 17
different data blocks to populate the form, and 17 members of Period are displayed,
resulting in less efficient performance. Considerations for dense and sparse settings
apply to calculations.
For example, a typical calculation in the Account dimension is Net Profit = Gross Sales -
Cost of Goods Sold. If Account is tagged as a dense dimension, the data block includes
the members needed for this calculation. If it is tagged as a sparse dimension, data must
be retrieved from three data blocks to perform the calculation.

Another important factor for performance is the number of cells per data block. Because
there is a multiplier effect between dense dimensions, the number of cells in a data block
grows exponentially when dense dimensions are added to the database.
For example, your database might have 200 account members and 12 period members,
resulting in 2,400 cells. If the HSP_Rates dimension is added as a dense dimension with

10 members for currency rates, the number of cells jumps to 24,000 (200 × 12 × 10). As
a general rule, smaller data blocks give better performance than larger data blocks.

Summary

• List two methods for creating applications

• Describe plan types
• Identify required dimensions
• Identify user-defined dimensions
• Describe dense and sparse dimensions
• Create data blocks
• Set up aggregation, data storage, and calculation options


L E S S O N 4
Managing Dimensions with Performance

Management Architect 4

Objectives
• Navigate Performance Management Architect
• Manage dimensions and members
• Create alternate hierarchies
• Create property associations
• Organize Shared Library
• Create members in Grid Editor
• Add and modify currencies
• Set up aliases
• Automate Performance Management Architect tasks
Lesson 4 Managing Dimensions with Performance Management Architect
About Dimension Management

Shared Application
Library pane pane
About Dimension Management

You can view, manage, create, and deploy Hyperion applications within a single
interface. Shared Library can include both shared and non-shared (local) dimensions.
You maintain shared dimensions and all properties in Shared Library. All updates are
automatically updated in the applications that contain those shared dimensions.
Shared Library
Shared Library is a central repository that contains all dimensions and dimension
members for Planning and Financial Management applications. All dimensions and
dimension members are created in Shared Library or they are imported into either the
application or Shared Library. Shared Library can contain more than one dimension of
the same type. For example, it could contain two Period dimensions, with the names
Quarterly Calendar and Trimester Calendar, that are used in different Planning
applications.

To work in Shared Librar y:

• Select Navigate > Administer > Dimension Library.
Application Pane

Applications listed in the application pane represent a selection of dimensions required
by an application. You can create local dimensions that are used solely by that
application. However, you can share or copy local dimensions so that other applications
can include those dimensions.
To work with the application pane:

1. Select Navigate > Administer > Application Library.
2. Right-click an application, and select Edit.
The application pane is displayed.

Creating Applications Using Performance

Management Architect

• Create applications in the dimension server.
• Set up dimension metadata.
• Deploy applications from the dimension server
to Planning and Financial Management application servers.
Planning Consolidation
application application
Dimension
Server
Planni ng Consolidation
Application Application
Server Server
Creating Applications Using Performance Management

Architect
You manage dimensions and create Planning applications in Performance Management
Architect:
1. Create applications in the Application Library.
2. Add dimensions to Shared Library. You can import them from formatted flat files, or
you can create them manually in the dimension editor. You also can import
dimension information from interface tables.
3. Set up applications by selecting application types, adding dimensions, and setting up
other application specific details such as default currency and start month.
4. Create Planning applications by deploying applications with the Planning type to
Planning application servers.

Adding Dimensions to Shared Library

Dimension class
Adding Dimensions to Shared Library

You can add dimensions to Shared Library. The dimension class determines the
properties that are available to the dimension members. For example, the Account
dimension includes the time balance property, which is not present in the Entity
dimension type.
To add dimensions to Shared Librar y:

1. Select File > New > Dimension.
The Add New Dimension dialog box is displayed.
2. Enter a dimension name.
Dimension names must be unique and can contain up to 80
characters (including spaces).

3. Optional: Enter a description.

4. In the Type drop-down list, assign a dimension class.
Examples of dimension classes used by Planning applications
include Account, Alias, Attribute, Currency, Entity, Generic,

Period, Scenario, SmartList, Version, and Year.
You select the Generic dimension class for custom dimensions
such as Product or Customer.
5. Click OK.
TIP
After adding dimensions to Shared Library, you can copy or delete them:
Copy dimensions: Right-click it, select Copy Dimension To, and select either
Shared Library or Application.
Delete dimension: Right-click it and select Delete Dimension.

Working with Shared and Local Members

Synchronize local
dimensions with
dim ensions in S hared
Library.
Working with Shared and Local Dimensions

Shared dimensions are dimensions that are linked in Shared Library and inherit any
changes that are made to that dimension. You must make all changes to shared
dimensions from Shared Library. Shared dimensions can be used by multiple
applications.
Local dimensions are detached, independent dimensions that only exist in one
application. You can create a local dimension by copying a shared dimension to an
application. You can also create a local dimension when you are running an import
profile.
After you define a dimension to be local, that dimension does not inherit changes made
to the dimension in Shared Library. To make changes to the local dimension, you must
perform these changes within the application. If you make changes to the original shared
dimension, you can merge changes to the dimension at the application level.

With shared dimensions, you can detach the dimension, making it a local dimension.
With local dimensions you can:
• Copy dimensions to Shared Library or to an application

• Synchronize between dimensions in Shared Library and dimensions in the
application
• Share dimensions changing a local dimension to be a shared dimension in an
application

Creating Members

• You can add members to dimensions by right-clicking the
member and selecting Create Member.
• You create members by selecting one of the following
options:
– As Child
– As Sibling
Creating Members
You create hierarchical relationships within dimensions by creating and organizing
members. You can add dimension members individually or by using import profiles. You
can add members to dimensions in Shared Library or locally to dimensions that are
within an application.
To add members to dimensions:

1. In the dimension hierarchy, right-click a member.
2. Select Create Member.
3. Select an option:
• Select As Child to add a member below the selected member
• Select As Sibling to add a member at the same level as the selected member

4. In the New Member dialog box, enter a name.

5. Click OK.
NOTE
Adding members by using import profiles is covered in more detail in a later

lesson.

Guidelines for Member Names

Member names cannot contain these characters:
• Backward slash (\)
• Double quote character (“)
Member names cannot start with the following characters:

• Backward slash (\) • Equal (=)
• Comma (,) • At (@)
• Plus sign (+) • Underscore (_)
• Minus sign (-) • Braces ({ })
• Period (.) • Pipe (|)
• Less than (<) • Double quote character (“)
• Apostrophe (‘)
Guidelines for Member Names

Member names can be up to 80 characters in length. Certain characters cannot be used
in member names for Planning applications.
If you use an invalid character in a member name, an error message is displayed when
you validate the application.
NOTE
Do not use reserved Essbase words such as #missing in member names.

Modifying Member Properties

Property category Save

Defined
Derived
Default
Modifying Member Properties

You can modify properties for each dimension member. When the dimension is created,
it takes on a default set of properties and property values. Properties are organized into
categories based on the products for which they are valid.
Property Category Application

Planning Used for Planning applications
System Used to identify characteristics of a member, such as name,
description, and member status (inactive or active)
Consolidation Used for Financial Management applications
Profitability Used for Profitability and Cost Management applications
Essbase (BSO) Used for Essbase reporting cubes

Property Category Application

Essbase (ASO) Used for Essbase reporting cubes
Statistical Provide statistical information about a member such as
number of children and number of siblings

Property fields are color-coded based on what you can do with that property. Consider
the following characteristics when working with properties:
• Properties that can be modified display a white background.
• Properties that are read-only display a grey background.
• Properties that are modified display a yellow background.
Modified properties, called defined properties, are not saved until you click the Save
button in the upper-right corner of the properties pane.
Defined properties display the following icon: .
Derived properties are those determined by logical relationships. Derived properties
display the following icon .
Inherited properties display the following icon . An example of an inherited property
wold be the Account Type property for account members.
Unmodified properties display a check mark . These properties keep their default
setting.

Property Value Inheritance

• Descendant members inherit property values from

ancestors.
• Updating the property value for an ancestor automatically
updates the value for its descendants.
• Modifying a property of a descendant directly prevents it
from inheriting that property from an ancestor.
Currency
property
is set to Euro. Descendants of Europe
inherit Euro as value for
Currency property.
Currency
property is set to Descendants of United
GBP, overriding Kingdom inherit GBP for
inherited value. Currency property.
Property Value Inheritance

Inheritance allows high-level members to share their properties’ values with lower points
in the hierarchy. It allows new members to automatically obtain their property values from
the appropriate ancestors. Proper use of inheritance enhances the referential integrity of
your application and reduces maintenance requirements.
Performance Management Architect determines a property value in the following order:
1. It looks for a value entered at the member. If a user directly entered a value at the
member, it uses that value.
2. If a value does not exist, it moves up the ancestral tree and uses the first entered
value that it finds. Thus, a change to the properties of an ancestor can affect
descendant members that inherit its value.
3. If no ancestor has an entered value, it uses the system default value for the property.

Performance Management Architect provides the following options for managing

inherited properties:
• Remove Value-Clears a property value for an individual member, so that it reverts to
the value inherited from its nearest ancestor.

• Remove Descendant Values-Clears all property value overrides by descendants,
so that all descendants revert to the value set at the ancestor level.

Alternate Hierarchies

Jan and Feb
occur in alternate E01_101_1110
rollups. occurs in an
alternate rollup.
Alternate Hierarchies
You can create multiple rollup paths for your data by placing a child member under more
than one parent. In the slide illustration, Jan and Feb are members of a YearTotal rollup,
with YearTotal as the top member, and a Q1 rollup, with Total Year as the top member.
Entity E01_101_1110 is a member of the TotalGeography hierarchy, and the Sales
Function hierarchy.
A member has the same property settings under all parents in which it occurs, with one
exception. One member has the property StoreData. Any additional members have their
property storage set to ShareData. Editing the properties of the stored member under
one parent updates it properties for all parents.
NOTE
You can set the aggregation property of a shared member to be different from the
aggregation property of the base member.

Inserting Members Using Relationships

Inserting
members creates
shared members.
Inserting Members Using Relationships

You can insert a group of members into a hierarchy based on a member relationship. For
example, you could insert all base members beneath a selected parent member into an
alternate hierarchy.
To insert members using relationships:

1. Right-click a member and select Insert Shared Member.
2. Select an option:
• Select Child to add the member as a child of the currently selected member.
• Select Sibling to add the member at the same level as the currently selected
member.
3. Select a member and click Add.

Managing Members

Managing Members
You can change the order in which a member is displayed under a parent or move a
member to another parent. You can delete a member from a single hierarchy or from all
hierarchies.
Reordering Children
You can change the order of children within the hierarchy.
To reorder children in Shared Librar y:

1. Right-click a dimension or member, and select Reorder Children.
The Reorder Children dialog box is displayed.
2. Click on the up or down arrows to change the order of the children.
3. Click OK.

Deleting Members
You can delete members from the current hierarchy only or from the dimension. When
you delete a member from the dimension, the member is removed from all hierarchies in
Shared Library and from all applications containing that member if the dimension is a
shared dimension.

To delete members:
• To delete a member from a hierarchy, right-click the member and select Remove
Member.
• To delete a member from the dimension, select the member in any hierarchy in
Shared Library, and select Delete Member.
Renaming Members
You can rename members in Shared Library. You cannot rename system members —
members displayed in brackets [ ]. After Planning application deployment, you should not
rename the Period members. For Planning applications, you cannot rename Currency or
Year members.
Managing Orphan Members

An orphan is a member that does not have a location in the dimension hierarchy. An
Orphan member is created during metadata import when the Hierarchy section of the
metadata load file does not contain information for the member. Orphan members are
also created when you use the Remove option to delete a child member from a parent
and the child member does not exist under another parent in the dimension.
To view orphan members:

• Right-click a dimension and select Orphan Members.
The Orphan Members list replaces the Properties Grid.
To delete orphan members:

• In the Orphan Members list, right-click the member and select Delete Orphan Member.
The orphan member is permanently deleted.

Finding Members

Double-click
a member to
locate it in
the outline.
Finding Members
You can search for dimension members in Shared Library or in applications. You can
search on the member name, member description (alias), or a member property. The
search operation finds all members that meet the specific search criteria.
To find members:
1. Right-click a dimension, and select Find Members.
The Member Find dialog box is displayed.
2. Select to search by the member: Name, Alias, or Property.
3. If you selected Property, then in the Property Name list, select a property by which to
search.
4. Enter the value for which to search, using an asterisk (*) as a wildcard if necessary.

5. Select an option to view the results:

• List View —replaces the Properties Grid and lists all members in the Member Find
pane. You can double-click a member in the Member Find pane to select that
member in the dimension library.

• Navigation Button —displays the first member in the Library pane. You can use
navigation buttons on the Standard toolbar to move to the next or previous
member.
6. Click OK.
7. Close the Member Find dialog box.

Creating Associations Between Dimensions

Ellipses indicate dimension association.
Creating Associations Between Dimensions

You can associate a property in one dimension with the members of another dimension.
End users can set the value for the property by selecting from a pick list of members from
the associated dimension.
For example, if you create an association between the Currency property of the Entity
dimension and the Currency dimension, users can set the Currency property of an entity
member by selecting from a pick list of members in the Currency dimension.
After you create an association for a property, users must select a member from the pick
list to set the property value; no other entries are valid.
You can create an association for any dimension property, but some dimension
properties require a dimension association. Values cannot be entered for these
properties until an association exists.

Properties that require an association:
Dimension Type Properties

Account Alias
Attribute [Note: only if Account dimensions is set to sparse]

Entity Alias
Attribute
Currency
Scenario Alias
Start Period
End Period
Start Year
End Year
Version Alias
Currency Alias
Period Alias
Year Alias
Smart Lists Alias
Generic Alias
Attribute

Organizing Shared Library with Folders

• Create folders Chart of
Accounts
• Add dimensions to
those folders
HP _Accounts
Hyplan_Account
Finbud_Account
SME_Account
FM_Accounts
Organizing Shared Library with Folders

You can organize dimensions by creating folders and copying or moving the dimensions
into the folders. Dimensions can exist in more than one folder. For example, you can
organize dimensions and have the Account dimension exist in multiple folders or have
the Account dimension exist at the highest level and also within a folder. Changes made
to the Account dimension in one folder update the Account dimension in all folders.
How to organize Shared Library:
• Rename folders
• Drag dimensions from their original location to a folder
• Move multiple dimensions at the same time
• Copy dimensions into folders

To create folders:
1. In Shared Library, select File > New > Folder.
The Create New Folder dialog box is displayed.
2. Enter the name and description, and then click OK.

To copy dimensions into folders:
1. In Shared Library, right-click a folder and select Add Dimensions.
The Add Dimensions to Folder dialog box is displayed.
2. Select one or more dimensions and click OK.
NOTE
Press the Ctrl key, and select one of more dimensions in the list.
To delete folders:
1. Right-click the folder, and select Delete and one of the following options:
• Folder with Content
• Only Folder
If you select the option to delete only folders, then only the folders
are deleted. Any dimensions within the folder are not deleted and
sub-folders are not deleted. Those dimensions and sub-folders
are moved to the root of Shared Library. If you select to delete
only a sub-folder, then only the sub-folder is deleted. Dimensions
are not deleted, rather they are moved to the root folder.
2. At the confirmation dialog box, click Yes.
3. Click OK to confirm.

Filtering Shared Library

Filter icon indicates that

dim ensions are filtered.
• Filter dimensions by name,
type, or owner.
• Visually recognize that
filtering is enabled.
Filtering Shared Library

You can filter the dimensions you see in Shared Library. Filtering applies to dimensions
both in the root directory and in folders. If you create a dimension and have a filter
applied that does not include the new dimension, the dimension is not displayed in
Shared Library until you remove the filter. In the illustration, Shared Library is filtered to
show only dimensions whose name start with the characters ‘HP’.
To create dimension filters:

1. In Shared Library, select View > Filter Dimensions.
The Dimension Filtering dialog box is displayed.
2. Enter the dimension name, or select the dimension type, or enter the owner.

3. Click OK.
A filter icon displayed in the Shared Library pane indicates that
dimensions are filtered.
TIP

You can remove filter criteria by selecting Edit > Clear Filter Criteria.

Sorting Dimensions in Shared Library

Sort icon indicates that

dimensions are sorted.
• Sort dimensions by
dimension class, name,
or owner.
• Visually recognize that
dimensions are sorted.
Sorting Dimensions in Shared Library

You can sort dimensions in Shared Library in ascending or descending order. You can
sort by dimension class, name, description, or owner. When dimensions are sorted, a
sort icon is displayed in the Shared Library pane.
To sort dimensions:
1. In the Dimension Library, select View > Sort Dimensions.
The Dimension Sorting dialog box is displayed.
2. Select the property to sort by (Dimension Class, Name, Description, or Owner).
3. Select the sort order (Ascending or Descending).

4. Click OK.
TIP
You can remove the sort by selecting Edit > Clear Sort Criteria.

Working with Grid Editor

View and maintain dimensions in a grid format.
Visual
cues
Working with Grid Editor

You can work with the Grid Editor to maintain member information. The Grid Editor
enables you to work with multiple dimensions and members in a grid format, so that you
can set properties for groups of members at the same time. You can also create and
delete members. Visual cues identify the types of changes that you made.
Members are displayed in the rows, with member names shown in the first column on the
left-hand side of the grid. Properties are displayed in the columns with the property name
displayed as the second row in the column heading. Each corresponding property value
is displayed as cell data. You select which members and properties are displayed in the
grid.
You can filter what is displayed by selecting a category. You can navigate to a different
page either by using the arrows or by selecting a page.

Selecting Members and Properties

Add
Remove
Remove All
Selecting Members and Properties

You select the members and properties that you want to display in the Grid Editor by
using the grid editor wizard.
To select members and properties:

1. Right-click a dimension and select Grid Editor.
The EPMA Grid Editor Wizard dialog box is displayed.
2. Select a dimension.
3. Move the members that you want to edit from the Members list to the Selection list.
4. Repeat step 2-3 to select additional dimensions and members.
5. Click Next.
The Select Properties tab is displayed.

6. Select the category that includes the properties you want to add.
7. Move the properties you want to edit from the Properties list to the Selections list.
8. Repeat steps 6-7 to select additional categories and properties.

9. Click Finish.
The Grid Editor is displayed.

Creating Members

Actions you can perform to change what is displayed
in Grid Editor:
• Change dimensions
• Add, remove, and delete members
• Add and remove properties
• Create members
• Copy, paste, and save data
Creating Members
You can create members using the Grid Editor. By creating new members, you add rows
to the grid for the new member and its properties. You can create children or sibling
members.
You can change the dimension that is displayed in the Grid Editor. You use the Grid
Editor Wizard to select a different dimension, as well as members and properties for that
dimension.
You can use the Grid Editor to add, remove, and delete members from all views. If you
add a member, a row is added in Grid Editor. If you remove a member, the row is
removed from the grid. If you delete a member, the member is deleted from all views and
is deleted from the Dimension Server after you save your changes.
You also can add or remove properties for a member using the Grid Editor.

To create members:
1. Right-click a row and select Create Member.
2. Select one of the following options:

• As Child
• As Sibling
3. Enter the member name and click OK.
The member is displayed in the Grid Editor.
You can set changes to be saved immediately after each individual change, by selecting
AutoCommit. Otherwise, data is saved only when you click the Save button. You see
visual cues when you modify members or properties. Cells are shaded with color
indicating that you modified data.
• Yellow — A cell that is yellow indicates that the values has been updated but not yet
saved. After you save the changes, the value is changed in Shared Library and the
cell color changes in the grid to the default color.
• Green — A row that is green indicates that it is a newly added row to the grid. After
you save the changes, the row color changes in the grid to the default color.
• Red — A row that is red indicates that it is marked for deletion. After a row is marked
for deletion, you cannot edit those cells. After you save the changes, the members
are deleted from Shared Library, removed from the application, and the rows are
deleted from the current page of the grid.

Adding Currencies

Create new currencies. Set properties for currencies.
Adding Currencies
You set up currencies by creating a dimension with the dimension class Currency. You
create members in the Currency dimension for each currency needed in your application.
NOTE
A dimension association is required between the Currency property of the Entity
dimension and the Currency dimension.
Number Formatting
You can set the number format for each currency. For example, for the European euro,
you can set the dot as the thousands separator and the comma as the decimal separator
to match the European standard. You can also set the color of negative numbers.

Scaling
You can specify that data values are scaled when they are displayed in certain
currencies. For example, you might set the scaling for the Japanese yen to thousands.
You could enter 10,000 as a value for Japan. When you select Japanese yen as the
display currency, the scaling is applied and 10 is displayed as the value for Japan.

Triangulation
Planning supports currency conversion by triangulation through an interim currency,
which is referred to as the triangulation currency. For example, if you know the European
euro exchange rates for U.S. dollars and French francs, you can calculate the U.S.
dollar/French franc exchange rate by using the European euro as the triangulation
currency.
You can also modify a currency’s triangulation currency by reentering the exchange rates
relative to the triangulation currency period and then refreshing the application so that
the new exchange rates are transferred and stored.
NOTE
You cannot select the default currency as a triangulation currency.
Reporting Currency
Planning supports currency conversion from local currencies to one or more reporting
currencies. The converted reporting currency values are stored and are read-only for all
users. The application default currency is also the default reporting currency. When you
add currencies, you specify whether they can be used as reporting currencies.
For example, suppose your application contains the currencies Japanese yen, U.S.
dollar, and European euro, with European euro specified as a reporting currency. When
you create data forms and reports, Japanese yen and U.S. dollar values are converted to
European euros and displayed.
You can load values directly into Essbase (from historical scenarios, for example) for
reporting.
NOTE
Each reporting currency is added to the Currency dimension, increasing the size
of the database and adding complexity to the currency conversion calculation
scripts. Only enable Reporting Currency if required.

Creating Aliases

Create
association.
April is the Default

and English alias
Create Alias dimension and add
members to Alias dimension.
Enter alias for member.
Creating Aliases
To improve outline and report readability, you can assign one or more alternate names,
or aliases, to dimension members. Aliases enable you to create unique sets of identifiers
when working with dimensions and members. You can assign up to 10 aliases per
dimension and dimension member, including the default alias. You create alias tables in
Performance Management Architect by creating an Alias dimension and then adding
members to that dimension.
After you create an association with the Alias property of the base dimension to an alias
dimension, you can assign alias values to members.

For example, you can set up alias dimensions to store information for different
languages. If you want to include account names in English, French, and German, you
create members in the Alias dimension named English, French, and German. Then you
create an association between the Alias property in the base dimension and the alias
dimension. In addition to associating aliases to the Account dimension, you can create

associations with the Entity, Scenario, Version, Period, or Year dimensions or user-
defined dimensions.
To create alias dimensions in Shared Librar y:

1. Select File > New > Dimension.
2. In the Add New Dimension dialog box, enter the Name and Description of the alias
dimension.
3. Select Alias from the Type drop-down list.
4. Click OK.
To create members in the Alias dimension:

1. Right click Alias and then select Create Member > As Child.
2. Type the Name for the alias dimension, for example German.
3. Click OK.
To associate a base dimension with the Alias dimension:

1. Right-click a base dimension such as Period and select Create Association.
2. Keep the default selection of Existing Property and select Alias from the Property
drop-down list.
3. Select the alias dimension from the dimension drop-down list.
To add aliases to dimension members:

1. Select the dimension member.
2. Double-click in the Alias field of the property grid.
3. Click the ellipsis button and enter aliases in the row representing the alias table.
4. Click OK.

5. Save the member property change.

NOTE
To ensure that aliases are displayed in the member’s property pane, select a
member in the Default Member field of the system properties for the Alias

dimension.

Automating Performance Management

Architect Tasks

Command-line interface allows tasks to be scripted,
such as:
• Incremental changes to data objects (application,
dimension, member, property)
• Running jobs (imports, deployments,
dimension/data synchronizations)
Two modes of operation:
• Command-line mode, where user enters
interactively
• Scripting mode, where user intervention is not
required
Automating Performance Management Architect Tasks

You can schedule tasks to run during off peak times. You can combine processes such
as data exports, metadata loads, refresh operations, security updates, data loads, and
calculations, and kickoff these operations during your normal nightly or weekly load
process.
With the batch client, you can initiate processes using external scheduling tools. The
batch client provides status updates and error information to external scheduling tools.
You work with the batch client in script mode to schedule tasks.

Summary

• Navigate Performance Management Architect

• Manage dimensions and members
• Create alternate hierarchies
• Create property associations
• Organize Shared Library
• Create members in Grid Editor
• Add and modify currencies
• Set up aliases
• Automate Performance Management Architect tasks


L E S S O N 5
Setting Up the Period, Year,

Scenario, and Version Dimensions 5

Objectives
• Describe Planning time periods
• Customize time periods
• Create scenarios
• Create versions
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
Creating Time Periods

The Year and Period dimensions represent time.
You can:
• Add years
• Create summary time periods or change the name of
summary time periods
• Add or change the aliases
• Add up to 100 calendar years and 500 time periods to an
application
After the application is deployed, you cannot:
• Modify the start year
• Reduce the number of years
• Change the type of calendar
Creating Time Periods

When creating applications, you add the Year and Period dimensions to represent time.
You use the Period dimension to view and change the yearly calendar rollup structure,
and you specify base time periods and distribution of weeks. You use the Year dimension
to add years to the calendar.
You can customize summary time periods in these ways:
• Update the name
• Change the description
• Modify starting and ending periods
• Change the range
• Create new summary time periods

• Add or change the aliases

NOTE
You cannot skip or change the order of base time periods. You cannot extend the
range beyond the current fiscal year.

If you create a new summary time period, you must work from the top of the hierarchy to
the bottom. The Period Type property for a summary time period is Summary Time
Period.
Keep in mind the following requirements:
• All base members must be the same number of levels from the root.
• Base members must have a Period Type property value of Base Time Period.
• BegBalance and YearTotal are required members for successful deployment of
Planning applications.
NOTE
The YearTotal member is the summary time period that aggregates all quarters or
weeks (for custom time periods).
• The YearTotal member must have a Period Type property value of Year Time Period.
You can add up to 100 calendar years and 500 time periods to an application. Depending
on the number of time periods and years and whether your application uses multiple
currencies, Hyperion recommends these practical limits:
• 400 time periods per year and 27 years
• 360 time periods per year and 30 years
You can enable Dynamic Time Series (DTS) for Period dimension members. For DTS
members, you can set the following properties: DTS Enabled, DTS Generation, and
Alias.
You can create alternate hierarchies and use shared descendants in the Period
dimension. Data Storage for all time periods can be set to any valid data storage value.
You can set the consolidation operator for all scenarios, versions, and time periods
(including BegBalance) to any valid consolidation operator. For example, it can be set to
+ (addition), instead of ~ (ignore).

After deploying the application and setting the calendar, you cannot change the type of
base periods, or reduce the number of years. If you selected a weekly distribution
pattern, you cannot change the pattern.
You can add more years to the Year dimension. However, you cannot delete a year after
it is added.

Period and Year Dimensions

Period
Year
Year
Period and Year Dimensions

The Year dimension contains a member for each year in the range of years for the
application. The member identifies the year to which the data applies.
The Period dimension is populated with base time periods for the application and is
tagged with the Time property in Essbase. When used in combination with the Account
dimension, a time dimension has properties that enable you to control how data
accumulates over time for an account.
The slide shows a typical example of a Planning data form, with Year FY07 in the point of
view and months in the columns. The Essbase outline displays the years and time
periods.

Dynamic Time Series Members

Predefined DTS Description
Member
H-T-D History-to-date
Y-T-D Year-to-date
S-T-D Season-to-date
P-T-D Period-to-date
Q-T-D Quarter-to-date
M-T-D Month-to-date
W-T-D Week-to-date
D-T-D Day-to-date
Dynamic Time Series Members

You can use Dynamic Time Series (DTS) members to create reports that show period-to-
date data, such as quarter-to-date expenses. DTS members can be used with members
of the Period dimension. You can enable DTS for members, and assign a generation
number. For example, to calculate quarter-to-date values, you can enable the Q-T-D
member and associate it with generation 2. You can then use the Q-T-D DTS member to
calculate monthly values up to the current month in the quarter.

Setting Up DTS Members

• Access the DTS Manager
– Enable the DTS
functions
– Select a generation
– Select an alias
• DTS members are

exposed as dynamic
calculation functions.
In Essbase, they are
not added as members
to the Period dimension.
Setting Up DTS Members

The DTS members provide up to eight levels of period-to-date reporting. Your data and
database outline determine which members you can use. For example, if the database
contains hourly, daily, weekly, monthly, quarterly, and yearly data, you can report day-to
date (D-T-D), week-to-date (W-T-D), month-to-date (M-T-D), quarter-to-date (Q-T-D), and
year-to-date (Y-TD) information. If the database contains monthly data for the past 5
years, you can report year-to-date (Y-T-D) and history-to-date (H-T-D) information, up to a
specific year. If the database tracks data for seasonal time periods, you can report period-
to-date (P-T-D) or season-to-date (S-T-D) information.
You can add DTS members to applications in the Dimension Library by using the DTS
Manager. Since DTS members are exposed as dynamic calculation functions, you cannot
load DTS members from ADS files.

To set up DTS members:

1. In Dimension Library, right-click Period.
The DTS Manager dialog box is displayed.
2. For each of the DTS members you want to enable, select Enabled.

3. Select a generation.
4. Optional: Set up an alias.
5. Click Save.

Data Storage

The storage type for a
member has a major
impact on the size and
calculation performance
of your database.
Data Storage
By default, when new members are added to an outline, they automatically store data in
the Essbase database. In some cases, data for a member does not need to be stored in
the database. By decreasing the number of members that store data, you can improve
the performance of your application. You can specify whether data is stored for a
member by using Essbase storage options (see screenshot in slide).
For most applications, setting the summary time periods in the Period dimension to
Dynamic Calc results in improved performance.
You can change storage options by setting member properties in the application.

Creating Scenarios

You can create hierarchies and shared members in the
Scenario dimension.
S elect Start and End Year, and

Start and End Period
Creating Scenarios
You create the Scenario and Version dimensions to set up individual plans to be
reviewed and approved. For each entity, the scenario and version combination contains
its own set of data for the accounts and other dimensions.
After entering entity data for a scenario and version, you can submit or promote the data
to other users for review and approval. The intersection of entity, scenario, and version is
referred to as a planning unit. Planning tracks the status or planning units as you move
them through the planning process.
Scenarios enable you to perform these tasks:
• Apply different planning methods
• Associate different scenarios with different time periods and exchange rates
• Create forecasts and budgets

• Enter data into scenarios

• Assign user access rights by scenario
• Report by scenario

• Compare and analyze different scenarios
By creating scenarios, you can group your data into separate plans with their own review
cycles. Scenarios can also cover different time spans. For example, your organization
might create one-year and three-year revenue plans that are prepared by different users
and follow different review paths. For this purpose, you could create two scenarios,
Current Year Revenue and 3Year Forecast.
You can create hierarchies and use shared members in the Scenario dimension.
Scenarios are required for successful deployment of Planning applications.
To create scenarios:
1. Right-click the Scenario dimension or scenario member, and select Create Member >
As Child.
2. Enter a name and click OK.
3. Set the following properties for the scenario member:
• Alias
• Valid for Plan
• Aggregation
• UDA
• Member Formula
• Data Storage
• Two Pass Calc
• Enable Process Management
• Smart List
• Data Type
• Start and End Year
• Start and End Period

• Use Beginning Balance

• Exchange Rate Table
4. Click Save.

Enable Process Management
In Performance Management Architect, select Enable Process Management if you want
to include this scenario in process management. If you select this check box, this
scenario is displayed in the scenario drop-down list on the Check Status and Manage
Process page, and you can manage planning units that contain this scenario member.
Time Periods
In Performance Management Architect, assign each scenario a range of years and time
periods for which it is valid. The range of time periods selected for a scenario has the
following effects in your application:
• When you access a data form, you are able to enter data into that scenario for only
the years and time periods within the range. Years and time periods outside the
range are displayed as read-only.
• When you generate a currency conversion calculation script, the calculation script
converts currencies for the range of time periods that are valid for the scenarios
selected for the script.
You can modify the time range of scenarios as needed to allow for continuous planning.
For example, you might have a scenario named 3Year Forecast that has 2008 as the
start year and 2010 as the end year. At the beginning of the 2009 fiscal year, you could
change the start year to 2009 and the end year to 2011, so that you can enter forecast
data for 2011.
Use Beginning Balance

Select Use Beginning Balance in Performance Management Architect as a time period
option if you want to include the BegBalance time period in this scenario for currency
conversion.
Exchange Rate Table

In Performance Management Architect, if your application uses currency conversion, you
assign an exchange rate table to the scenario. The table is applicable only to multiple-
currency applications.

By assigning different exchange rate tables to scenarios, you can model the effect of
different assumptions on your business. You must consider currency reporting needs
when deciding which scenarios to create.
For example, you may need to create scenarios associated with different exchange rate
tables to eliminate the effects of currency rate fluctuations from variances (such as

Budget at Actual Rate).
Access Rights
You can specify access permissions for Scenario dimension members to determine
whether groups or users can view or modify data. A user or group can have only one of
the following access rights: Read, Write, or None. You assign access rights for scenarios
in Planning after application deployment.
Members of the Year and Period dimensions do not have security associated with them.
However, you can use the scenario start and end year and period properties to lock time
periods out for data entry. For example, you could set the properties so that users can
enter data only into the current year.
All time periods that fall outside the start and end range are displayed as read-only. You
can also set the Start and End Period properties to allow a mix of actual and budget data
in the same scenario for forecasting purposes.
For example, if you are rolling out your application in April, the Forecast scenario could
contain actual data for January through March and forecast data for April through
December. If you set the start period to April, users can input forecast data for April, May,
through December, but they cannot edit the actual data in January, February or March.
At the end of April, you load actual data for April, and change the start period to May, so
that you can create a rolling forecast.

Creating Versions

You can create hierarchies and shared members in the Version
dimension.
Version Type – BottomUp or Target
Creating Versions
Versions are required for successful deployment of Planning applications. You can
create, for example, Best Case and Worst Case versions for use with any scenario. You
can use the Version dimension for these purposes:
• Allow multiple iterations of a plan; for example, preliminary and final.
• Model possible outcomes based on more optimistic or less optimistic assumptions;
for example, Best Case and Worst Case.
• Manage dissemination of plan data; for example, Internal and External.
• Facilitate target setting
You set up the Version dimension in Performance Management Architect. You can
change the version name in Performance Management Architect and access
permissions in Planning.

The permissions are independent of scenarios, so you could give users read-only access
to the Final version but write access to the Working version. Then, if users want to enter
data for Budget Final intersections, they cannot write to that intersection even though the
Budget scenario may have write access. The read access to the Final version prevents
write access to that intersection of data.

You can create hierarchies and use shared members in the Version dimension. If you
assign children to bottom-up versions, these versions are displayed as read-only parents
on data forms.
Version Types
There are two types of versions, Bottom-Up or Target.
For Bottom-Up versions, you enter data into the bottom level members. The parent-level
members are read-only. When you calculate the database, the values of parent
members are aggregated from the bottom-level members. For example, if you enter data
for Northern Europe and Southern Europe, the total for Europe is aggregated after the
database is calculated.
Target versions allow you to enter data for members at any level in the hierarchy. You
can use business rules to distribute values from parent members to their descendants.
For example, you can enter the target for Total Expenses into the Europe member and
use a business rule to distribute the target values to Northern and Southern Europe.
Target versions enable you to set high-level targets for your plan. Planners working with
bottom-up versions can then reference these targets when they enter plan data. For
example, the Total Product Sales member has Retail, Wholesale, and Distributors for its
children. A budget manager enters 10,000 into Total Product Sales for the California
entity in a target version. This target sets California’s target for product sales. The budget
preparer for California then enters values for the Retail, Wholesale, and Distributors
children that total 10,000 in a bottom-up version to show how the target is met.
The functionality available with target versions is for top-down budgeting.
Guidelines for target versions:
• Workflow Tasks are not allowed for target versions.
• Children of target members must be blank (for example, #missing) for the data input
to be allowed at the top level.
• Target members must be set to StoreData (DynamicCalc overrides data input with
sum of children).

To create versions:
1. Right-click the Version dimension or member, and select Create Member > As Child.
3. Set the following properties for the version member:

• Alias
• Valid for Plan
• Aggregation
• UDA
• Member Formula
• Data Storage
• Two Pass Calc
• Enable Process Management
NOTE
Enable for Process Management can be selected only for bottom up versions.
• Smart List
• Data Type
• Version Type
4. Click Save.

Summary

• Describe Planning time periods

• Customize time periods
• Create scenarios
• Create versions


L E S S O N 6
Setting Up the Entity Dimension 6

Objectives
• Add members to the Entity dimension
• Modify members in the Entity dimension
• Delete members in the Entity dimension
Lesson 6 Setting Up the Entity Dimension
Entities Overview

• Entities allow you to model the flow of budget information
through your organization.
• You can create an entity for each group or responsibility
center that submits a plan for approval.
• You can assign plan types to entities.
• Entities can have a currency property.
– If no currency is defined, the application default currency is
used.
– The entity’s currency can be overwritten during data entry or
data loads.
Entities Overview
The Entity dimension is a Planning dimension whose members can be loaded or
manually added to an application.
You can use parent-child relationships among entities to mirror your budget review
structure. You can define the types of units that your organization requires, such as
geographical regions, departments, or divisions.
For example, your organization’s regional centers may prepare budgets that are
reviewed at the country headquarters. The country headquarters may, in turn, prepare a
plan that is reviewed at the corporate headquarters. To match this structure, you can
create members for the regions, countries, and headquarters. You can set up the regions
as children of the country members, and the country members as children of the
headquarters member.

Entity Members and Plan Types

• When you define an entity member, you assign plan types.
• If you do not assign a plan type to a parent, its children do not
have access to that plan type.
Data Form Plan Types
IncStmt BalSheet Revenue


Eastern US
Assigned NY
FL
Entity Members and Plan Types

A plan type is a classification mechanism for data.
Your organization may require different entity members to prepare different plans. For
example, all entity members in your organization may submit expense plans, but entity
members that are cost centers do not submit revenue plans. When you define entity
members, you specify the plan types for which they are valid.
Because data forms are associated with plan types, they enable you to control which
entity members can enter data for each plan type. For example, Eastern US may be a
cost center, so you assign it as valid for the IncStmt plan type, but not for the Revenue
plan type. When you create data forms for the Revenue plan type, Eastern US cannot be
selected on those forms.

Selecting a plan type for an entity member involves specifying how the data values should
roll up. An entity member’s plan types may change when you promote or demote the
member in the dimension hierarchy: If the new parents’ associated plan types are
different from those of the moved member, the member becomes valid for the plan types
of the new parent.

If you move an entity member, and the new parent of that member is assigned to different
plan types, the member remains assigned to the plan types that it has in common with the
new parent.

Currency Value for Entities

The default currency is the currency that you specify when you
create the application.
New York London Tokyo
Currency Value for Entities

Entity dimensions require an association with the Currency dimension to be able to enter
a value for the Base Currency. If your application is set up for multiple currencies, you
must associate the Currency dimension with the base entity dimension and specify a
currency for each entity. The default currency for all entities is the currency that you
specify when you create your application in Performance Management Architect.
The currency property value identifies the local currency in which data for the entity is
entered. When you run a currency conversion calculation script or the Convert
Currencies business rule, Planning uses the exchange rates entered for that entity’s
currency to convert the local currency to the reporting currency. You can override the
currency property during data entry or during a data load.

For example, you might specify Yen as the currency for the Japan entity, and US dollars
for the United States entity. When you view a data form that has values on it for the
Japan entity, if the form’s display currency is set to US dollars, Planning uses the rates in
exchange rates table for the Yen to convert the values to US dollars.

Adding and Modifying Entities

Adding and Modifying Entities

You add and modify dimensions and members in Shared Library. You can also set the
properties for dimensions and members. When you modify dimension and member
properties, this information populates the Performance Management Architect relational
database. For these changes to be reflected in the Essbase database, you can deploy
the application in Performance Management Architect or you can select the Manage
Database option in the Administration menu in Planning.
To add members:
1. In Shared Library, right-click a dimension or dimension member.
2. Select Create Member, and add the member as a child or sibling.

3. Set up the following properties for entities:

• Alias
• Valid for Plan

• Aggregation
• UDA
• Member Formula
• Data Storage
• Smart List
• Data Type
• Attribute Values
4. Click to save the changes.
To modify members:
1. Select the member.
The properties pane is displayed.
2. Modify properties and save your changes.

Saving Dimensions

Save changes to the relational database.
Saving Dimensions
When you add, modify, or delete dimensions and their members, you must save the
changes before they take effect. When you save the changes, Performance
Management Architect performs a validation check. Some of the items that validation
checks for include the following:
• To prevent two users from saving the same dimension or member at the same time.
• To prevent a user from assigning a member to a plan type for which it is not valid.
• To prevent a user from using the same name for different dimensions or members.
• To ensure that member names do not contain invalid characters.
• To validate that the period dimension is correctly balanced.
• To ensure that member properties are set to valid values.

• To verify that attributes from the same dimension are assigned to members at the
same level.
If the validation check fails, an error message is displayed.

Deleting Entities

Deleting Entities
You can delete entities from applications. When you delete entities in an EPMA
application and the application is deployed to Planning, the entity is deleted from the
Planning application even if it is used in data forms or in a started planning unit.
After you delete an entity, you should remove it from data forms that contain the entity.
You also must update and validate business rules, reports, and adapter processes to
reflect the deleted entity.
To show an entity’s application membership in the Shared Library, right-click an entity
member and select Application Membership.

Summary

• Add entity members to the Entity dimension

• Modify entity members in the Entity dimension
• Delete members in the Entity dimension

L E S S O N 7
Setting Up the Account Dimension 7

Objectives
• Describe account types and consolidation order
• Create account hierarchies
Lesson 7 Setting Up the Account Dimension
Accounts Overview

• Assign plan types to accounts. Data Form
– If more than one plan type
is assigned to an account,
designate a source plan Plan Types
type.
– Other plan types pull their
values from the source plan In cStmt BalSheet
type. 
Source Plan
• Use aggregation options to
define calculations in the Detail Expense Accounts
account hierarchy. Profit
Total Revenue
T otal Expenses
Accounts Overview
You use the Account dimension to specify the information gathered from budget
planners. Accounts typically represent an accounting container that identifies the primary
nature of the data.
Accounts are organized into hierarchies. You can create an account structure that lets
budget preparers input data for budget items to the appropriate level of detail.
You can define calculations in your hierarchies. For example, your detailed operating
expense accounts can automatically aggregate to Total Expenses, and Total Expenses
can be subtracted from Total Revenue.
When you define an account member, you assign a plan type. If you promote or demote
a member, and the new parent of the member has different associated plan types, then
the member remains assigned to the plan types that it has in common with the new
parent.

If an account is associated with more than one plan type, you must specify a source plan
type for the account. The source plan type determines which plan type’s database stores
the account value. For example, if the source plan type for the Total Product Sales
account is IncStmt, the value displayed for the account on forms for the Revenue plan
type is the value entered for the IncStmt plan type.

Account Types

Account Type Expense Time Balance Skip Exchange Rate Type Data Type
Repor ting
Expense Expense Flow N/A Average Currency
Revenue NonExpense Flow N/A Average Currency
Asset NonExpense Balance None Ending Currency
Liability NonExpense Balance None Ending Currency
Equity NonExpense Balance None Ending Currency
Saved User-defined User-defined N/A None NonCurrency

Assum ption
Account Types
Account types define how an account's value flows over time. Account types also
determine the sign behavior for expense reporting with Essbase member formulas.
All account types have predefined settings for expense reporting and time balance
behavior except for the Saved Assumption account type, which is user-defined. When
you select an account type and save the member, the Expense Reporting and Time
Balance list boxes are populated with predefined settings.
On the slide, the expense, time balance, skip, exchange rate type, and data type are the
default selections. You can override the defaults, if required.

Time Balance Options

Flow and Balance examples:
Jan Feb Mar Quarter 1

Total Revenues Revenue 50 75 50 175
Cash on Hand Asset 100 150 75 75
Time Balance Options

Time Balance specifies how account data flows over time. You can use the following
options:
Option Description
Flow Uses an aggregate of all data values for a summary time
period as a total for the period.
First Uses the beginning data value in a summary time period
as the total for the period.
Balance Uses the ending value in a summary time period as the
total for the period.
Average Uses the average of all children’s data values in a
summary time period as the total for the time period.

Option Description
Weighted Average-Actual_Actual Uses a weighted daily average, based on the actual
number of days in a year, to account for leap year when
February has 29 days.
Weighted Average-Actual_365 Uses a weighted daily average based on 365 days in a

year, assuming that February has 28 days; does not
account for leap year.
Skip Options for Missing Values

If you set the Time Balance property to First, Balance, or Average, you must specify how
Planning should handle zeros and missing values when calculating the parent value:
Property Description
None Zeros and #MISSING values are considered.
Missing #MISSING values are excluded.
Zero Zero values are excluded.
Missing and Zeros #MISSING and zero values are excluded.
NOTE
When the time balance is set to Flow, skip options are not available and default to
None.
An account’s expense reporting property determines if an account is tagged as an

expense in Essbase member formulas or Financial Reporting variance functions. Here is
how expense and nonexpense accounts behave for expense reporting:
• Expense—The actual amount is subtracted from the budgeted amount to determine
the variance.
• Nonexpense—The budgeted amount is subtracted from the actual amount to
determine the variance.

Saved Assumptions

Use saved assumptions to perform these tasks:
• Centralize planning assumptions
• Identify key business drivers
• Ensure consistency across the application
Examples of saved assumption accounts:
• Headcount
• Square footage
Define business rules that reference the saved assumptions:
• Calculate office supplies by entity based on headcount
• Calculate facilities expense based on square footage per
location
Saved Assumptions
When you define a saved assumption account, you select the appropriate time balance
and expense reporting properties. The following examples show how time balance and
expense reporting properties are used with saved assumption accounts:
• You may create a saved assumption of an expense type for expense reporting. It
assumes that the actual amount you spent on head count is less than the amount
you budgeted. To determine the expense, Planning subtracts the actual amount from
the budgeted amount.
• You make an assumption on the square footage of an office and you determine the
square footage of the office for the time period by using a value for the end of the
time period.
• You make an assumption about the number of product units sold at the end of the
time period. You determine the final value for the time period by aggregating the
number of units sold across a range of time periods.

Data Types and Exchange Rate Types

Currency
Exchange
rate types Average Ending Historical
Data Types and Exchange Rate Types

Data and exchange rate types determine how numeric values are stored and which
exchange rate to use to calculate the value.
Data types:
• Currency—Stores and displays the value in the default currency.
• NonCurrency—Stores and displays the value as a numeric value.
• Percentage—Stores and displays the value as a percentage.
• Smart List—Stores and displays the value as a smart list.
• Date—Stores and displays the value as a date.
• Text—Stores and displays the value as text.
• Unspecified —Stores and displays the value as unspecified.

For accounts whose data type is Currency, you select an exchange rate type:
• Average—Valid for any time period; uses the average rate for the account.
• Ending—Valid for any time period; uses the ending exchange rate for the account.

• Historical—Valid for any time period.
Data types can have conflicting results on the face of a data form depending upon the
cell intersections defined for the data form. For example, the intersection of a "percent"
data type and a "currency" data type must be resolved based on how you define the
order set. The Data Type Evaluation Order is the defined order. You set a dimension
order by plan type to determine the precedence when multiple data types intersect. Data
types associated with the first dimension in the list take precedence over data types
associated with subsequent dimensions.

Creating Account Hierarchies

Creating Account Hierarchies

You create and modify account hierarchies in the Dimension Library. After you save
changes to the hierarchy, your changes are saved to the Performance Management
Architect relational database. You must deploy the application in Performance
Management Architect or refresh the database in Planning to update the Essbase
databases.
To create account members:

1. In Performance Management Architect, right-click an account.
2. Select Create Member and one of the following:
- As Child
- As Sibling

3. In the properties pane, set up the account properties:

• Alias
• Valid for plan type

• Aggregation options
• UDA, Member Formula
• Data Storage
• Two Pass Calc
• Smart List
• Time Balance
• Skip Value
• Expense Reporting
• Account Type
• Exchange Rate Type
• Data Type
• Source Plan Type
Adding and Modifying Accounts

In the Dimension Library, you can build the account hierarchy by adding children and
sibling members. You can also change member properties.
NOTE
When assigning plan types, you must set the plan type property for a parent
member before you can set the plan type for its children. You cannot select a plan
type for a child member if the plan type is not valid for the parent.

Consolidation Order

Account (Never Share)
Level 2
Profit (+)
Level 1
Margin (+)
Sales (+) Level 0
COGS (-)
Exp enses (-)
Marketing (+)
Misc. (+)
Ratios (~) (Label Only)

Margin % (+) (Two Pass Calc) Margin % Sales;
Prod uct Share (+) (Two Pass Calc) Sales % Sales -> Pro ducts;
Consolidation Order
After creating the Essbase database outline, you should review the order of the
dimensions and members. For each plan type, data is consolidated based on the order
of the dimensions and members in the outline.
The order of calculation within each dimension depends on the relationships between
members in the database outline. Within each branch of a dimension, level 0 values are
calculated first, followed by their level 1, parent value. The level 0 values of the next
branch are calculated, followed by their level 1, parent value. The calculation continues
in this way until all levels are calculated.
By default, the outline is consolidated based on addition. You can set any member’s
aggregation option to addition, subtraction, multiplication, division, percent, or ignore.
When a new operator is set, the operation designates how a member is consolidated to
its parent. For example, you may want to subtract a member from its sibling, such as
subtracting COGS (Cost Of Good Sold) from Sales, to define the value for Margin.

Consolidation Order Example

• Consolidation order is defined by the order of members in the
outline.
• Essbase calculates data in top-down order.
Par ent 6.67
Member 1 (+) 10
30
Member 2 (+) 20 5
Member 3 (-) 25 25 200
Member 4 (*) 40 40 400
Member 5 (%) 50 50 6.67

Member 6 (/) 60 60
Member 7 (~) 70
Consolidation Order Example

It is important to understand how members with different operators are calculated. When
you use addition and subtraction operators, the order of members in the outline is
irrelevant. However, when you use other operators, you must consider the member order
and its impact on the consolidation. When siblings have different operators, the data
calculates in top-down order.
Essbase calculates Member1 through Member4 as follows:
(((Member1 + Member2) + (-1)Member3) * Member4) = X(((10 + 20) + (-25)) * 40) = 200
If the result from Members 1-4 is X, then Member5 consolidates as follows:
(X/Member5) * 100 = Y(200/50) * 100 = 400
If the result of Member5 is Y, then Member6 consolidates as follows:
Y/Member6 = Z400/60 = 6.67 and Member7 is ignored in the consolidation.

Summary

• Describe account types and consolidation order

• Create account hierarchies

L E S S O N 8
Creating User-Defined Elements 8

• Create user-defined dimensions
• Create attributes and assign attribute values
• Describe member formulas
• Add member formulas
• Create Smart Lists
Lesson 8 Creating User-Defined Elements

User-defined dimensions require these items:
• Unique values across databases
• Plan types assigned at the dimension level
Customer
User-defined dimensions help you capture categories that your organization uses for
planning.
For example, you may have a group of accounts for operating expenses. You may
decide to add a dimension called Project so that you can budget operating expenses on
a project basis.
Guidelines:
• Names must be unique and use proper naming conventions.
• Names and aliases can have up to 80 characters.
• Descriptions can have up to 255 characters.

For user-defined dimensions, you assign valid plan types at the dimension level, not at
the member level. All members of custom dimensions are valid for plan types assigned
at the dimension level.
You assign the Generic dimension type to user-defined custom dimensions. You set up
user-defined custom dimensions by defining the following dimension properties: Name,

Alias, Valid for Plan, Aggregation for Plan, UDA, Member Formula, Data Storage, Two
Pass Calc, Smart List, Data Type, and Attributes.
NOTE
In order to assign access to members in a custom dimension, you must select
Apply Security at the dimension level. You assign access in Planning.

Attributes Overview

Base dimension Att ributes
Customer Sales Rep Company Size
National Accounts Assad Akili Small
Your IT Source Sandy Smith Medium
ABC Company Doug Nichols Large
Software Company Chri s Jones
Attributes Overview
Attributes are characteristics of your data. For example, products can have attributes
such as colors, sizes, or flavors. Attributes enable you to add another level of granularity
to your data. You create attributes for a dimension when you want to group its members
according to the same criteria.
For example, you might have a Product dimension with members for three product lines,
some of which are sold in retail outlets and some only by catalog. When you are
analyzing or reporting your data, you might need separate totals for retail and catalog
sales.
Attribute dimensions can have a data type of text, numeric, Boolean, or date. The
attribute type applies only to level 0 members of the attribute dimension.

You can use date attributes to specify the date with a format as month-day-year or day-
month-year, and sequence information accordingly. You can use date attributes in
calculations, for example, comparing dates in a calculation that selects product sales
since 12-22-1998. You can set the date format in Application Settings.
To show relationships between members, you can set up hierarchies within attribute

dimensions. If an attribute is numeric, only the level zero attribute members must be
numeric. For example, you could set up an attribute dimension that has a text parent
called Total with numeric children 1, and 2. You can also include aliases for attribute
members.
You can add attributes to sparse dimensions such as the Entity dimension and User-
Defined dimensions. You can add attributes to the Account dimension if it is designated
as a sparse dimension in all plan types.
NOTE
You can assign attributes only to sparse dimensions. For dense dimensions, you
must change them to sparse for all plan types. When changing dimensions to
dense, all attributes and attribute values for the dimension are automatically
deleted. You cannot assign attributes to label-only members.
You use attributes to view, aggregate, and report on data. For example, you can view net
sales by customer and sales rep.
In many ways, attribute dimensions behave like regular dimensions: You can retrieve,
pivot, and drill on attribute members. You can use them to create crosstab reports of
attribute data for multiple attributes in the same dimension, or for attribute data from
multiple dimensions. For example, Sales Reps are attributes of the Customer dimension.
NOTE
In order to assign attributes to a user-defined custom dimension, you must
associate the attribute dimension to the user-defined custom dimension. For
example, if you want to assign salesreps to the Customer dimension, you
associate the Salesrep attribute dimension to the user-defined custom dimension
named Customer.

Creating Attributes

Create the attribute.
Create values for the

attribute.
Creating Attributes
You create attribute dimensions, assign attribute types, and add attribute values in
Dimension Library. You can then assign attribute values to dimension members. When
you create forms and reports, you can filter dimension members by their attribute values.
To create attributes:
1. In Dimension Library, from the File menu, select New > Dimension.
2. Enter a name and description for the dimension.
3. From the Type drop-down list, select Attribute and click OK.
4. In Dimension Library, select the attribute dimension you just created.
5. In the Properties pane, set the value of the Attribute Type to either Text, Boolean,
Date, or Numeric.

6. Right-click the attribute dimension, and select Create Member > As Child.
7. Enter the attribute value.
8. Repeat steps 6 and 7 to enter other attribute values for the attribute dimension.

NOTE
Only sparse dimensions can contain attributes. To display the sparse/dense
settings for dimensions, right-click the application name and select Performance
Settings.

Attribute Values: Examples

Create and assign attribute types:
• Text
• Date
• Boolean
• Numeric
Attribute Values: Examples

For an entity dimension with the members Acquisition date, Strategic Y/N, and Desc, you
could create corresponding date, boolean, and text attributes. After creating the attribute
and attribute values, you can assign a value to each member.
When assigning attribute values to dimension members, you must assign all of them at
the same level in the hierarchy, or an error occurs during the application refresh.

Assigning Attribute Values

Assigning Attribute Values

You use Dimension Library to assign and view attribute values. After creating attribute
dimensions and values, you must associate them with a dimension (at the dimension
level) before you can assign attribute values to a dimension member.
To associate dimensions with attribute values:

1. In Dimension Library, select a dimension.
2. Right-click the dimension and select Create Association.
3. Select Existing Property or New Property.
4. Perform a task:
• If you selected Existing Property, select the property from the Property drop-down
list.
• If you selected New Property, enter the new property.

5. Enter a description.
6. From the Dimension drop-down list, select a dimension where that attribute is located.
7. Click OK.

The attribute dimension associated with a user-defined dimension
is displayed as a property in the property grid.
8. Right-click a dimension and select View Associations to verify dimension associations.
To assign attribute values to dimension members:

1. Select the dimension member.
The properties pane is displayed.
2. Select the property for the attribute dimension, and click the ellipsis button .
3. From the Member Selector list, select an attribute value.

Member Formulas Overview

Member Formulas Overview

So far you have set up calculations between members by using aggregation options.
These aggregation calculations are built into the Essbase outline. The aggregation
calculations are generally intuitive as you can drill down to see how a member is derived.
Calculation through aggregation operators has some limitations:
• You can create calculations only between children of a common parent.
• You must store results of the calculation in the parent member.
You can use member formulas as an alternative method of calculation. Member formulas
are attached directly to dimension members. They go beyond aggregation logic by letting
you reference values in members anywhere in the outline, including in other dimensions
or other databases. Member formulas also provide a wider range of operators.

Adding Member Formulas

Adding Member Formulas

You use the Memo Editor in Dimension Library to create and save member formulas. You
can define member formulas in the Properties Grid for Planning, Essbase, and
Enterprise Analytics categories.
When adding a formula to a member, you edit the Member Formula property for an
account. Using the Memo Editor, you could create a member formula for Profit Percent,
as in the following example:
Profit Percent = “Gross Profit”%”Net Sales”;

When creating member formulas, you can combine the following items to perform
calculations on members:
• Operators, calculation functions, dimension and member names, and numeric
constants

• Operator type, function, value, member name, UDA, and so on that are allowed in
Essbase formulas
• Predefined formula expressions, including smart list values, that expand into a
formula or value upon database refresh
Use these buttons to create member formulas:
Button Description
Inserts a function and its parameters.
Inserts selected members.
Inserts a variable.
Finds a text or phrase in the member

formula.
Replaces a text or phrase in the member
formula.
To add member formulas:

1. Select a dimension member.
2. In the Properties pane for the member, double-click Member Formula.
3. Click .
The Member Formula dialog box is displayed.
4. Enter a formula.
5. Click OK.

Adding User-Defined Attributes

Adding User-Defined Attributes

You create user-defined attributes (UDAs) in Dimension Library to describe
characteristics of other dimension members. You can use UDAs within calculation
scripts, member formulas, and reports. UDAs are words or phrases that describe a
member. For example, you can apply a UDA such as New Market to selected members
within Markets.
UDAs enable you to calculate and report on specific subsets of data. They essentially
provide a way to group members. For example, in a report or calculation, you can
request all states with a New Market UDA.
You can share UDAs across applications. You can also assign a UDA to one or more
dimension members.

To create UDAs with members:

1. In Dimension Library, from the File menu, select New > Dimension.
2. Enter a name and description for the dimension.
3. From the Type drop-down list, select UDA and click OK.

4. In Dimension Library, right-click the UDA dimension you just created.
5. Select Create Member > As Child.
To assign UDAs to members:

1. In Dimension Library, select the dimension whose members you want to associate
with UDAs.
2. Select a dimension member.
3. In the member properties, double-click UDA, then click .
4. In the left pane, select UDA members and click (Add).
5. Click Save.
6. Save the member properties.
TIP
You can manually enter, edit, and delete assigned UDAs in the UDA text box. Use
a comma to separate multiple UDAs for a member.

Smart Lists Overview

4000-100 (Network
Sales), and 4000-200
(Chip Sales), use data
values.
Customer_Service_Class
uses a smart list.
Smart Lists Overview

Smart lists are custom drop-down lists that you can access from data form cells in
Planning applications. You can select an item from the list instead of entering data
manually. You cannot type in cells that contain smart lists.
For example, you can create a smart list for customer service level with the following
values:
• Platinum
• Gold
• Silver
• Bronze

You can associate the Customer Service Level smart list with the Customer Service
Class account member. On a data form, if you click in the account named Customer
Service Class (which is associated with the Customer Service Level smart list), you can
choose from a drop-down list with these selections: Platinum, Gold, Silver, and Bronze.

Creating Smart Lists

Smart list dimension
Smart list values
Creating Smart Lists

In Dimension Library, you create smart list dimensions and members, and assign
properties to smart lists.
Smart list creation process:
• Create a dimension with Smart List selected as the dimension type.
• Create members in the dimension. (The members are the items that are displayed in
the drop-down list, data form, or grid.)
• Assign properties to the smart list dimension and members.
• Optional: Perform any of the following tasks:
- Set up smart lists on data forms
- Use smart lists values in member formulas and business rules.
- Set how #Missing cells associated with smart lists are displayed in data forms.

Guidelines:
• Smart lists are associated with dimension members. Typically, the Account
dimension is used to associate smart lists with members.
• After associating smart lists with dimension members, reserve those members to

store only smart list values. These members should not be used to store other data
values.
• Consider creating new members and setting up a separate rollup with the dimension.
• You can create reports to capture the smart list information. You must use planning
details as your data source to report on smart list data.
• Smart lists can be associated with more than one member, but those members must
be level 0 members.
• Smart lists are not specific to a plan type.
• Smart list names and aliases must begin with a letter, and can contain letters,
numbers, underscore, and dollar sign characters. Smart list names cannot contain
spaces, or be Java reserved words.
To create smart lists:

1. In Dimension Library, select File > New > Dimension.
The Add New Dimension dialog box is displayed.
2. Enter the name and description.
3. From the Type drop-down list, select SmartList.
4. Click OK.
5. In Dimension Library, select the Smart List dimension.
6. In Properties pane, from Category, select System.
7. Enter a Dimension Alias for the Smart List dimension.
8. Click Save Property.
9. In Properties pane, from Category, select Planning.
10. Enter a label for the Smart List dimension.

12. In Dimension Library, right-click the Smart List dimension and choose Create Member >
As Child.
The New Member dialog box is displayed.
13. In the Name text box, enter a name and click OK.

14. In Dimension Library, select the member name.
15. In the properties pane, from the category drop-down list, select Planning.
16. In the Label text box, type a label and click Save Property.
17. Create additional members, as necessary, for the dimension.

Modifying Smart Lists

S mart list dimension
properties
S mart list value

properties
Modifying Smart Lists

You modify the following smart list properties in the property grid:
Label Enter the text to display when the smart list is selected. Spaces
and special characters are allowed. Smart list labels can
reference a resource, which can be translated into different
languages.
Start Value Populates the value property of the first member in the smart
list.
Increment Enter the value that is appended to the value of the last member
in the list to determine the value for the selected member.
Display Order Select to sort the smart list by ID, Name, or Label.

#Missing Data Form Label Select how #Missing values are represented in cells
associated with the smart list.
#Missing Drop Down Label Enter a label to be displayed as an entry in the smart list whose
value is #Missing.

Administrators can set the values that are displayed in smart lists and data cells,
including what is displayed when no data is in the cell. When no data is in a cell, the cell
can display no value, #Missing, or another specified value.

Associating Smart Lists with Members

Associating Smart Lists with Members

You associate smart lists with members in the property grid. You can create a dimension
member or you can use an existing member, and then assign the smart list as a member
property. Keep in mind that for the member whose member properties includes a smart
list, you cannot enter values in the cells.
To associate smart lists with members:

1. Select the member.
2. In the property pane, from Data Type, select SmartList.
3. In Properties, from Smart List, select the Smart List.

Setting Data Forms to Use Smart Lists

Account 6060
has the alias
Customer
Service Class.
Setting Data Forms to Use Smart Lists

In order to work with smart lists on data forms, you must select the dimension member so
that it is displayed on the data form. You must also set the data form properties so that
you can work with smart lists on that data form.
Keep in mind the following key points:
• You can assign smart lists to rows or columns.
• You cannot use smart lists in pages.
• You must assign smart lists to level 0 members.

Summary

• Create user-defined dimensions

• Create attributes and assign attribute values
• Describe member formulas
• Add member formulas
• Create Smart Lists


M O D U L E 3
Loading Metadata 8

Overview
The aim of this module is to load metadata used by Planning applications.
Then you create applications and deploy those applications to the Planning
server. You also set up Exchange Rates.
• Loading Metadata from a File
• Creating Applications
• Deploying Applications
• Setting Up Exchange Rates
L E S S O N 9
Loading Metadata from a File 9

Objectives
• Format metadata files
• Load and extract metadata from flat files
• Create profiles
• Map dimensions and dimension properties
• Explain best practices for loading metadata
• Load metadata from interface tables
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Metadata Load Files Overview

You can load data from flat files or interface tables.
Load files can contain metadata for:
• Account, Entity, Scenario, Version
• Period, Year dimensions
• Currency dimension
• Generic dimensions (User-defined dimensions)
• Attribute, Alias, UDA, and Smart List dimensions
Metadata Load Files Overview

You can load metadata into the Shared Library or directly into applications from interface
tables or from flat files. If you load metadata from interface tables, you load metadata
from a specific database. If you load metadata from flat files, you can include any
combination of dimensions in the load file, and you can have multiple load files. For
example, you could have one load file for the Account, Scenario, and Version
dimensions and another load file for the Entity dimension.
You can import metadata into either shared or local dimensions. If you import into shared
dimensions, you can update properties but cannot make any structural changes. If you
import into local dimensions, you can change both properties and make structural
changes.

During the import process, you can move members or create shared members. If you
select the option, Merge As Shared, then multiple instances of a member are processed
as shared members. If you do not select the option Merge As Shared, then the primary
member is moved to the specified parent.

NOTE
To load metadata into classic applications, you work with the classic Planning
adapter. There are a number of different Planning adapters to load metadata. The
adaptor that you use depends on the tool you use to import the metadata. Tools to
import metadata into classic Planning applications include Oracle Data Integrator
(ODI), Data Integration Management (DIM), Hyperion Application Link (HAL) and
the OutlineLoad utility. You can also use a flat file adapter to import metadata.

Formatting Load Files

• Load files are divided into sections with an exclamation
point as the section delimiter.
• Load files sections can be in any order.
• The line defining the column names for the section begins
with an apostrophe immediately under the section header.
• You can place the column names in any order.
Section header Column names
!Members= Products
'Name|DataType|SmartList|UDA|Description|Salesrep
Tennis Rackets|Unspecified||||Thomas Brown
Tennis Balls|Unspecified||||Sandy Spencer
Formatting Load Files

The section for each type of metadata can be displayed only once in a metadata file. You
need not include a column for every dimension member property. Properties for omitted
columns are set to their default value. Do not use a character included in the actual
metadata as the delimiter.
If you load metadata from flat files, keep the following points in mind:
• A line starting with an exclamation point (!) indicates the beginning of a new section
in the flat file and must be followed by a valid section name (for example, Dimensions
or DimensionAssociations).
• A line starting with an apostrophe (') sets the column order for the section.
• True and false values are represented as Y for true and N for false.
• You can use a pipe (|), semicolon (;), comma (,), space, or tab as the file delimiter.

You specify the dimensions represented in the load file in the Dimensions section. To set
up members with the load file, you create a Members section for each dimension. You
specify the member and the member hierarchy for a dimension.
If some properties have dimension associations, you specify them in the
DimensionAssociations section. To set up aliases, you include a Property Array section.

If you are creating new dimensions by importing metadata, you must include the
Dimensions, Dimension Associations, and Hierarchies sections. In this scenario, the
Members section is an optional section. You can include members and global property
values in the Hierarchy section.
NOTE
For global properties, the value of the property is the same for a member of a
dimension under any parent. An example of a global property is the data type
property. For local properties, the value of the property can differ for a member for
each parent. If a member is in multiple places in the dimension, and that member
has different values for each relationship, then that value is local. The value is
"local" to the relationship in the dimension versus "global" to the member in the
dimension. An example of a local property is the data storage property.
If you are creating a new dimension by importing metadata, the Property Array section is
optional. You can define Property Array values such as the alias property, in the
Hierarchies section.
If you import into existing dimensions, you only have to include a Hierarchies section. All
other sections are optional.

Setting Up Dimensions

• Add an entry for each dimension in the load file.
• The required columns are Name, DimensionClass, and
DimensionAlias.
!Section=Dimensions
'Name|DimensionClass|DimensionAlias|DimDataStorage
HP Accounts|Account|HP Accounts|NeverShare
Calendar Months|Period|Calendar Months|NeverShare
Standard Year|Year|Standard Year|NeverShare
Version|Version|Version|NeverShare
Scenario|Scenario|Scenario|NeverShare
Currency|Currency|Currency|NeverShare
Functional Entity|Entity|Functional Entity|NeverShare
• DimensionAlias is required for the Essbase dimension

name.
Setting Up Dimensions
You must identify each dimension included in the load file in the Dimensions section. A
load file can have only one Dimensions section. The columns for the Dimensions section
have the following characteristics:
Column Description
Name Name of up to 80 characters (required)
DimensionClass Type of dimension, such as account or entity (required)
DimensionAlias System property and the name of the dimension in Planning and Essbase
You set system properties for dimensions in the Dimensions section. For example, to
select Apply Security for a custom dimension, you include the apply security property in
the header and indicate whether to apply security to each dimension by entering a Y for
Yes or N for No.

Setting Up Dimension Associations

!Section=DimensionAssociations
'BaseDimension|Property|TargetDimension
Entity|Alias|HP_Alias
Entity|Currency|Currency
Setting Up Dimension Associations

You use the DimensionAssociations section to identify which member properties have
associations. End users can then set property values by selecting from a pick list of
members for the associated dimension.
Required columns for the DimensionAssociations section:
Column Description
BaseDimension Dimension for which you want to set up the association
Property Property that you want to link to another dimension
TargetDimension Dimension to which to link the property

You can automate property association assignments by indicating the associations in the
load file. The example on the slide is a sample section from a file that you can use to load
metadata.
NOTE

If you indicate associations in the load file, you need to ensure that the
dimensions, both the base dimension and the associated dimensions (target
dimensions), exist in the Dimension Library. For example, if you associate the size
attribute dimension to the product dimension, you must ensure that both the size
and product dimensions already exist in the Dimension Library, or are defined in
the Dimensions section of the load file.
You can also add property associations later by creating lists in Dimension Library. The
illustration on the slide is one such example. Association-setting privileges are
determined by role. For example, administrators set associations for Currency, Start and
End Period, and Start and End Year. Business users can set associations for smart lists.
To associate dimension properties in Shared Librar y

1. Right-click a dimension and select Create Association.
The Create New Association dialog box is displayed.
2. Select options, enter text, and click OK.

Setting Up Parent-Child Relationships

• The !HIERARCHIES section defines the Entity
parent-child relationships within
dimensions. Geographical
• Use this format:

Uni tedStates
<parent member>|<child member>.
• Represent top-level members as Cali fornia
children of #root:
#root|<top-level member>. 1000
!HIERARCHIES=Entity Plant1
'Parent|Child
#root|Geographical WestSales
Geographical|UnitedStates
Geographical|Europe Connecticut
United States|California
California|1000
Mass
California|Plant1
California|WestSales
Europe
Setting Up Parent-Child Relationships

You define parent-child relationships within dimensions in the Hierarchies sections. You
begin the section by entering the following line, replacing the angle brackets (<>) with
the dimension name:
!HIERARCHIES=<>
The Hierarchies section is required for new and existing dimensions that use the replace
method. It is optional for existing dimensions that use the merge method. Parent and
Child properties are required. You can control the member order in a dimension based
on the order in which members exist in the source. Members of existing dimension are
reordered during a merge or replace import.

Optionally, you can include member properties in the Hierarchies section, as in the
following example:
!Hierarchies=Entity
'Parent|Child|Data Storage|Currency|Valid For Plan1|Valid For

Plan2|Aggregation for Plan1|Aggregation for Plan2
#root|Canada|StoreData|CAD|Y|Y|+|+
#root|United States|StoreData|USD|Y|Y|+|+
United States|Oregon|StoreData|USD|Y|Y|+|+
United States|California|StoreData|USD|Y|Y|+|+
California|San Francisco|StoreData|USD|Y|Y|+|+
United States|Washington|StoreData|USD|Y|Y|+|+
If you include the member properties in the Hierarchies section, you should omit the
Members section.

Setting Up Members

• Use a separate Members section for each dimension.
• Use Y for Yes and N for No.
!Members=Scenario
'Name|Data Type|Start Year|End Year|Start Period|End
Period|Use Beginning Balance|Enable Process Management|Smart
List|ExchangeRate Table
Current|Unspecified|FY07|FY10|Jan|Dec|N|N||A_FXRate
Actual|Unspecified|FY08|FY08|Jan|Dec|N|N||A_FXRate
Budget|Unspecified|FY09|FY11|Jan|Dec|Y|Y||B_FXRate
Setting Up Members
You set up members for a dimension in a Members section. You begin the section by
entering the following line, replacing the angle brackets (<>) with the dimension name:
!Members=<>
You need not include columns for all member properties for the dimension class, and you
can set up the columns in any order.
Here are the valid Planning properties for the following dimension classes:

Account
Name,Use application distribution, DataType, Valid for
Plan1,Valid for Plan2, Valid for Plan3, Valid for Wrkforce, Valid
for Capex, Aggregation for Plan1, Aggregation for Plan2,
Aggregation for Plan3, Aggregation for Wrkforce, Aggregation for

Capex, UDA, Member Formula, Data Storage, Two Pass Calc, Smart
List, Time Balance, Skip Value, Expense Reporting, Account Type,
ExchangeRate Type, Data Type, Source Plan Type
Entity
Name, Currency, Valid for Plan1,Valid for Plan2, Valid for Plan3,
Valid for Wrkforce, Valid for Capex, Aggregation for Plan1,
Aggregation for Plan2, Aggregation for Plan3, Aggregation for
Wrkforce, Aggregation for Capex, UDA, Member Formula, Data
Storage, Two Pass Calc, Smart List, Data Type
Scenario
Name, Valid for Plan1,Valid for Plan2, Valid for Plan3, Valid for
Wrkforce, Valid for Capex, Aggregation for Plan1, Aggregation for
Plan2, Aggregation for Plan3, Aggregation for Wrkforce,
Aggregation for Capex, UDA, Member Formula, Data Storage, Two
Pass Calc, Enable Process Management, Smart List, Data Type,
Start Year, End Year, Start Period, End Period, Use Beginning
Balance, ExchangeRate Table
Version
Name, Valid for Plan1, Valid for Plan2, Valid for Plan3, Valid for
Pass Calc, Enable Process Management, Smart List, Data Type,
Version Type
Period
Pass Calc, Smart List, Data Type, Period Type

Year
Wrkforce, Valid for Capex, UDA, Member Formula, Data Storage, Two
Pass Calc, Smart List, Data Type

Currency
Name, Scale, Valid for Plan1,Valid for Plan2, Valid for Plan3,
Valid for Wrkforce, Valid for Capex, Thousands Separator, Decimal
Separator, Negative Sign, Negative Color, UDA, Member Formula,
Data Storage, Two Pass Calc, Smart List, Data Type, Currency Code,
Symbol, Triangulation Currency, Reporting Currency
Generic
Name, Two Pass Calculation, Valid for Plan1,Valid for Plan2,
Valid for Plan3, Valid for Wrkforce, Valid for Capex, Data
Storage, Apply Security

Managing Aliases

Manage aliases in the Members section
!Members=HP_Account
'Name|Alias=English|Alias=German|Data Type|Source Plan Type|Account Type
Gross Profit|Total Gross Profit|Bruttogewinn|Currency|Plan1|Revenue
Net Sales|Total Net Sales|Nettoumsatz|Currency|Plan1|Revenue
Manage aliases in the Hierarchies section

!Hierarchies=Account
'Parent|Child|Alias=English|Alias=German|DataStorage|MemberValidForPlan1
Operating Margin|Gross Profit|Total Gross Profit|Bruttogewinn|DynamicCalc|Y
Gross Profit|Net Sales|Total Net Sales|Nettoumsatz|DynamicCalc|Y
Manage aliases in the PropertyArray section

!PropertyArray=Account
'Property|Name|Key|Value
Alias|Gross Profit|English|Total Net Sales
Alias|Gross Profit|German|Nettoumsatz
Managing Aliases
Aliases are alternate names for members. For numeric member names, you can include
an alphanumeric alias so that you recognize what the number represents. For example,
the entity 400 could have an alias of London.
If an application uses multiple languages for member descriptions, you add properties to
the Members section header for each language set up in the Alias dimension. Use this
format:
Alias=<Language>
In the slide example, the member section header includes properties for descriptions in
English and German.

You can also add properties to either the Hierarchies or PropertyArray section headers
for each language set up in the Alias dimension. Since only the Hierarchies section is
required when you import into existing dimensions, including aliases in the Hierarchies
section is more efficient than maintaining a separate PropertyArray or Members section.
If you are creating a new dimension, you can also maintain aliases in the Hierarchies

section, since the Members section is not required.

Loading Metadata Process

You perform the following tasks to load metadata:
1. Create an import profile
2. Specify load options
3. Map dimensions in the load file to dimensions in the
Dimension Library
4. Map fields for the load file to dimension properties in
Dimension Library
5. Run the import profile
Loading Metadata Process

You load metadata by creating and running import profiles. Profiles include important
information about the dimensions to be imported, such as new dimensions, whether to
merge or replace dimensions, dimension and member properties, and relationships
between members.

Creating Import Profiles

Creating Import Profiles

You create profiles to import metadata from flat files or interface tables. You can import
metadata into Shared Library or directly into an application.
To create import profiles:

1. Select File > Import > Create Profile.
The New Profile dialog box is displayed.
2. Enter a name for the profile.
3. From the Import Type drop-down list, select FlatFile or Interface Tables.
4. Optional: Enter a description for the profile.
5. In the Application list, select either an application or Shared Library as the
destination.

6. In the File Name box, perform an action:

• Flat files: Click Upload to browse for the flat file, select it, and click Upload again.
• Interface tables: From the Data Source drop-down list, select a database.

7. Click OK.
8. Follow the wizard to complete the profile setup:
• Load files: Select options for column delimiter, removal of double quotes on
strings, removal of white space from load files, and suppression of transaction
logs.
• Flat files and interface tables: Map dimensions and properties.

Mapping Dimensions
Source File HyPlan2 ap plication

SME_Currency Currency
SME_Alias Alias
Mapping Dimensions
You can create dimensions, or you can map a dimension in the load file to an existing
dimension. For each dimension in the flat file, a drop-down list displays dimensions of the
same dimension type in the destination application. You can select New Dimension, or
you can select an existing dimension to which you want to map the flat file dimension.
NOTE
If a dimension name in the destination exactly matches a dimension name of the
same dimension type in the load file, the matching dimension is the default
selection.

When you map a dimension in the load file to an existing dimension in the Dimension
Library, you can merge or replace members:
• The Merge option updates members that exist in the application with the information
in the file. If the file contains members that do not exist in the application, the missing
members are added.

• The Replace option replaces the existing metadata with the metadata in the file. If a
dimension member that exists in the application is not present in the metadata file
that you are loading, the Replace option removes the member from the application.
• The Merge as Shared option determines how to process a member if the parent
specified in the load file is different than its parent or parents in the application. If you
select Merge as Shared, the member is added as a shared member to the parent
specified in the load file. If you do not select Merge as Shared, the member is
removed from its current parents in the application and added to the parent specified
in the load file.

Mapping Properties

Mapping Properties
For each column for a dimension in the flat file, a drop-down list of properties for the
same dimension class in Dimension Library is displayed. You select the property to
which to map the column.
NOTE
If a property name in Dimension Library exactly matches a property name in the
load file, that property is mapped by default.
Select Ignore Nulls if you want blank values for a record in the load file to be ignored.
Otherwise, blank values are treated as data, and the property status is changed from
default to defined. A status of defined prevents the property from inheriting values from
ancestors.

Running Import Profiles

Running Import Profiles

After creating a profile, you are prompted to execute the profile. If you want to run it at
another time, you can initiate the import from the Import Dimensions dialog box.
To access the Import Dimensions dialog box:

1. Select File > Import > Import Dimensions.
2. Select one of the following options:
• Flat File
• Interface File

3. Select a file to upload.

NOTE
You must select a file to upload each time you run an import.

You can view, edit, or delete import profiles after you select a file to upload.
To edit the Import Profile:

1. Select File > Import > Import Dimensions.
2. Right-click a profile, and select Edit Profile.

Viewing Job Status

Viewing Job Status

You view the status of the metadata load in the Job Console. The Job Console shows the
current job status and the percent completion. You can click the Import Results link to
view an error log for each dimension included in the load.
To view the status of the metadata load:

• Select Navigate > Administer > Library Job Console
After the import job runs, you can select the click here to navigate to jobs link to
see the job status for your job.

Viewing Import Errors

Viewing Import Errors

You can view import errors by selecting a job and clicking on the link for Import Results.
You can select a specific error and view the details. After you correct the error, you can
import the file again.

Best Practices

Recommendations for efficient importing and easier
maintenance include the following guidelines:
• Populate the Hierarchies section with all the member
properties.
• Place the member formula property as the last column.
• Work with the file-generating utility to create an initial file.
• Load multiple dimensions using one file.
Best Practices
Consider the following recommendations for maintaining dimension metadata:
• Rather than maintaining a separate Members section, you can manage your property
values by including them in the Hierarchies section. Keep in mind that if you need to
include the member name, then you need to include a Members section.
• Since the syntax for member formulas includes a semicolon and since the content for
member formulas can be quite extensive, the recommendation is that member
formula property is placed as the last column.
• Instead of creating an import file by hand, you can work with the EPMA File
Generator, a file generating utility to generate an initial file that you can modify as
needed. You can generate ads files from the following sources:
- existing Planning applications as long as they are version 9.3 or later

- existing Performance Management Architect applications including Planning,

Consolidation, Generic, and Master application types as long as they are version
9.3.1 or later
- Excel file

- existing Financial Management files such as .per, .sec and .xml metadata files
- existing Financial Management applications as long as they are version 9.3 or later
• Since you are populating either Shared Library or a specific application with
dimension information, you can have metadata for several dimensions within one file.
You do not have to execute individual imports for each dimension.
• Consider the sequence of information contained in the load file. If you are associating
an attribute dimension to a base dimension, be sure to create new properties prior to
associating the attribute dimension to the base dimension.

Loading Metadata from Interface Tables

Relational database Perform ance Management Architect
Interface tables
Loading Metadata from Interface Tables

Performance Management Architect interface tables are database tables used to import
metadata from external systems into Shared Library. They represent an alternative to flat
files.
For details on using interface tables to load metadata, see the Oracle Hyperion
Enterprise Performance Management Architect Administrator’s Guide.

Metadata loading process:

1. Create a Performance Architect interface database using a relational database such
as Oracle or MS SQL Server.
2. In the interface database, you create tables that correspond to the sections in a

metadata flat file. For example, you would create a database table for dimension
associations with fields for Base Dimension, Property, and Target dimension, similar
to the DimensionAssociations section of a flat file.
3. Load data from your external systems into the tables.
4. Import the data from the interface tables into Shared Library by using an import
profile, following the same procedure as with flat files.

Summary

• Format metadata files

• Load and extract metadata from flat files
• Create profiles
• Map dimensions and dimension properties
• Explain best practices for loading metadata
• Load metadata from interface tables

L E S S O N 1 0
Creating Applications 10

Objectives
• Set up application name, plan types, time periods, and currency
• Select dimensions
• Configure application settings
• Add dimensions to applications from Shared Library
• Activate dimension associations
• Adjust Performance Settings
Lesson 10 Creating Applications
Application Creation Process

Use Application Wizard to create applications:
• Determining application criteria
• Setting up application name, plan types, and default currency
• Selecting dimensions
• Configuring application setting s
• Adding dimensions from Shared Library
• Activating dimension associations
• Choosing performance settings
Application Creation Process

You create applications with the Application Wizard. The wizard enables you to create
applications with all the required components to ensure successful deployment. The
wizard contains applicable property and dimension information by application type. For
example, you make the designation for plan types for Planning applications but you
would not select plan types for Financial Management applications.
After you create the basic application structure, you can add dimensions and further
customize the application.

Plan for Application Setup

• Plan types
• Currency specifications
• Time periods
Incstmt Balsheet Plan 3
Plan for Application Setup

Before initiating the Application Wizard, you determine the following application criteria:
• Number of plan types and their names
• Default currency and whether or not the application is a multicurrency application
• Base time periods, weekly distribution, start year, and start month

Plan Types

Budgeting = Plan P lan Plan
application Type 1 Type 2 Type 3 Workforce Capex
Additional m odules
available for
purchase
Plan Types
You can indicate up to five plan types for an application. An Essbase database is created
for each plan type. After creating an application, you cannot change the name or number
of plan types.
The number of plan types depends on the needs of your organization. For example, if the
Sales Department has a yearly revenue plan, and the finance department has a P&L
plan, you can define two plan types—Revenue and P&L.
As you create accounts, entities, and other elements of the application, you associate
them with plan types. The association ensures that the database contains only relevant
application dimensions, members, and data values, and that application design, size,
and performance are optimized.

You can also share data between plan types, to ensure that the database remains small
and efficient. For example, the Revenue plan may include several sales detail accounts
that roll up into a Total Product Sales account. You can configure the P&L plan to include
the Total Product Sales account, omitting sales detail accounts. Then, you can bring the
data value for Total Product Sales into your P&L plan without account details.

NOTE
You can add WFP (Workforce Planning) and CAPEX (Capital Asset Planning)
plan types to an existing application if you purchased these modules.

Currency Specifications

• Set default currency for entities
• Specify whether multiple currencies are used
Currency Specifications
You specify the default currency for entities in the application and establish if the
application supports currency conversions.
Multiple currency support (also known as currency overrides) is available for level 0
members, regardless of their base currency. If you select multiple currencies, two
dimensions are created in Essbase: Currency and HSP_Rates. You cannot change this
option later.

Time Periods

• Choose Base Time Period–Months, Quarters, Custom
• Select Weeks Distribution–Even, 445, 454, 544
• Select Start Year and Start Month
Time Periods
You select the base time period and the monthly distribution pattern based on the
number of fiscal weeks in a month. The base time period options are the bottom-level
time periods in the application. Predefined options are months or quarters. You can
create custom base time periods, such as weeks or days.
You can select monthly distribution patterns to determine how data entered into a
summary time period is distributed or spread among base time periods. During data
entry, users can enter data into summary time periods, such as years or quarters.
Planning distributes these values over the base time periods that constitute the summary
time period.
You can select a weekly distribution pattern other than Even Distribution. In that case,
Planning treats quarterly values as if they were divided into 13 weeks and distributes
weeks according to the selected pattern. For example, if you select the 5-4-4 pattern,
Planning treats the first month in a quarter as if it has five weeks, and the last two months
in the quarter as if they have four weeks. The options for the weekly distribution pattern
are available only if you select the 12 Months base time period option.
You specify the fiscal start year, the fiscal start month, and the total number of years in
the application. The fiscal start year determines the starting fiscal year for the application.
You cannot change the option later. When specifying the fiscal start year, consider how
much historical data your organization needs in the application.

Setting Up Application Components

Setting Up Application Components

You set up the application name, application type, and application characteristics in the
first step of the Application Wizard. You can create applications in Application Library or
Shared Library provided that you are assigned the application creator role. Application
Library displays all applications in Performance Management Architect.
Application types:
Type Description
Generic A template that enables you to create an application without assigning
a specific product. A generic application displays properties for all
products.
Planning Planning application
Consolidation Financial Management application

Type Description
Profitability Profitability and Cost Management application
Essbase Essbase application

To create planning applications:
1. Select File > New > Application.
The New Application Wizard is displayed.
2. In the Name text box, enter the application name.
3. In the Type drop-down list, select Planning.
4. Optional: Add a description.
5. Select plan types and enter names for plan types.
6. In the Currency text box, enter the default currency for the application. (This must be
a member present in the application’s currency dimension).
7. Optional: If you are creating a period dimension, select Create A New Period Dimension
and proceed to step 10.
8. Optional: If you are creating a year dimension, select Create A New Year Dimension and
proceed to step 11.
9. Optional: If you are creating a multicurrency application, select Use Multiple Currencies
and proceed to step 12.
10. In the Planning Period section, enter the details for the new period dimension.
Field Action
New Period Dimension Enter the name of the period
Name dimension
Base Time Period Select the type of base time
periods from 12 Months,
Quarters, or Custom
Fiscal Start Month Select the fiscal start month
Weekly Distribution Select the weekly distribution
from EVEN, 445, 454, or 544

Field Action
Prefix If you selected Custom for base
time periods, enter a prefix
Periods Per Year If you selected Custom for the
base time periods, enter the

number of custom periods per
year
11. In the Planning Year section, enter the details for the new period dimension.
Field Action
New Year Dimension Enter the name of the year
Name dimension
Fiscal Start Year Enter the fiscal start year
Total Year Enter the total number of years
12. Click Next.

Selecting Dimensions

Selecting Dimensions
The Dimension Selection page displays all required dimensions for a Planning
application. Dimension types are automatically categorized and displayed with a gray
shaded heading. For example, the sections include: All Plan Types, Custom Dimensions,
and Other Dimensions.
When selecting dimensions, you can either select an existing dimension from Shared
library, or create a dimension. You must select dimensions for each dimension in the
Dimension List before you can advance in the wizard. The Application Wizard
automatically creates the required dimension associations.

Dimensions within an application are either local or shared. Local dimension are
maintained within the application. Adding or removing dimension members or changing
member properties has no effect on dimensions in other applications or in Shared
Library. For example, two applications have an account dimension named HY_Accounts
designated as a local dimension. Modification to members of HY_Accounts in one

application has no effect on the HY_Accounts dimension in the other application.
You cannot add members, delete members, or change the hierarchy structure of shared
dimensions within an application. Instead, you maintain shared dimensions centrally in
Shared Library. You can, however, override the property settings for members of shared
dimensions within an application. For example, in Shared Library, the Draft 2 member of
the HP_Version dimension has the Enable for Process Management property enabled. A
particular application that shares HP_Version requires that Draft 2 member not be
enabled for process management. You can override the Enable for Process
Management property for the Draft 2 member of HP_Version in the application.
You cannot associate a local dimension with a shared dimension. For example, if you
have an attribute dimension in the Shared Library called Colors, you cannot associate it
with a local dimension in an application called Products.
To select dimensions from Shared Librar y:

1. In the Dimension list, double-click a dimension.
A list of dimensions in Shared Library that have the same
dimension type as the selected dimension is displayed.
2. In the Dimension list, select a dimension from Shared Library.
3. Optional: Select Local Dimension if you want to create a local copy of the dimension
from Shared Library, instead of sharing the dimension.
4. Click Next.
The Application Settings pane is displayed.
To create dimensions:
1. In the Dimension list, double-click a dimension.
A list of dimensions in Shared Library that have the same
dimension type as the selected dimension is displayed.
2. In the Dimension list, select Create New Dimension.
The New Dimension dialog box is displayed.

3. Enter a name.
4. Click OK.
The dimension is added to the dimension list. Local Dimension is
selected automatically because the dimension does not exist in

Shared Library.
5. Click Next.
The Application Settings screen is displayed.

Configuring Application Settings

Planning properties.
Select the
application label
to configure the
application
settings.
Configuring Application Settings

You configure application-wide settings in the properties grid.
To configure application settings:

1. Select the Planning application name to display its dimension properties in the
Properties grid. Properties that you set at the highest level apply to all dimensions in
the application.
2. Select the Planning category.
3. Indicate up to five valid plan types: Plan1, Plan2, Plan3, Workforce, and Capex.
4. Set up names for the plan types. Plan type names can contain up to 8 characters.
5. Select a date format.

6. Specify the default currency and indicate whether the planning application contains
multiple currencies.
7. Set the base time periods (monthly, quarterly, or custom), weekly distribution, and
starting fiscal year and month.

NOTE
You cannot change the Start Year. The value for Start Year corresponds to the first
year in the Year dimension.
8. Specify the default Alias Table for the application.

9. Optional: View or modify system properties as follows:
a. In the application pane, select an application.
b. In the Category drop-down list, select System, and then view or modify the settings.
10. Click Finish.
The Application is displayed in Shared Library.

Adding Dimensions from Shared Library

You can drag dimensions from Shared Library to an application.
Shared Applica tion
Library
Adding Dimensions from Shared Library

An application in Shared Library shows a selection of dimensions required for that
application. After you create an application, it is displayed in the Application pane in
Shared Library.
You can add dimensions to applications from Shared Library as local copies or as shared
copies:
• Local—Changes that you make to the original do not affect the copy in the
application.
• Shared—The copy is linked to the original in Shared Library. Member and member
property changes made in Shared Library are automatically propagated to the
application.
Planning application requirements:

• Required dimensions are determined by the application type. For the Planning
application type, an application requires one dimension from each of these
dimension classes: Account, Entity, Scenario, Version, Period, Year, Currency (for
multicurrency applications).
• The Entity dimension requires an association with the Currency dimension to enter a

value for the currency property.
• The Scenario dimension requires an association with the Period and Year
dimensions to enter starting and ending time period values.
• If you want to assign attribute values, aliases, or UDAs to dimension members, you
must associate the Attribute, Alias, or UDA dimensions with those base dimensions.
For example, if you want to assign attributes, aliases, or UDAs to the Entity and
Account dimensions, you must associate the Attribute, Alias, and UDA dimensions
with their respective properties in the base dimensions, Entity and Account.
Dimension association guidelines:
• You need not associate a smart list with a main dimension to select a smart list in the
Smart List property field.
• Dimensions created in Shared Library do not have default associations. You
associate shared dimensions in Shared Library, not in applications. However, you
associate local dimensions in the application.
• Within an application, local dimensions cannot be associated with shared
dimensions.
• For dimensions loaded from flat files, you must specify associations in the flat file.
• If you upgrade an application, the associations may already be assigned.
To add dimensions to applications:

1. In the Shared Library pane, select a dimension.
2. Drag the selected dimension to the application pane.
The Dimension Status Selection dialog box is displayed.
3. Select Local or Shared.
4. Click OK.

Changing Local Dimensions

to Shared Dimensions

Changing Local Dimensions to Shared Dimensions

You can change a local dimension to a shared dimension. When you share a local
dimension, you can either replace the members of the dimension in the Shared Library
with the members from the local dimension, or merge the local dimension members with
the members in the Shared Library. When you select merge, members present in the
local dimension but not in the Shared Library are added to the dimension in the Shared
Library.
To change local dimensions to shared dimensions:

1. Right-click a local dimension in an application and select Share Dimension.
The Share Dimension dialog box is displayed.
2. Perform an action:

• If the dimension does not currently exist in Shared Library and you want to add it,
proceed to step 3.
• If the dimension exists in the Shared Library and you want to link the local
dimension to it, proceed to step 4.

3. Select Create a New Shared Dimension, and click OK to add a dimension.
4. In the Dimension list, select the dimension that you want to share with the local
dimension.
5. Select Merge to add the members of the dimension in the application to those in the
Shared Library, or Replace to replace the members in Shared Library with the
members in the application.
6. Click OK.
NOTE
If the name of the dimension you selected from Shared Library is different
than the name of the local dimension, the local dimension is renamed to
match the dimension in Shared Library.
TIP
To change a shared dimension to a local dimension, right-click the dimension and
select Detach.

Overriding Property Settings

Inheritance from application ancestor
overrides inheritance from Shared Library.
Property values loaded or m anually entered

override both Shared Library and ancestor values.
Overriding Property Settings

Member property settings for shared dimensions in applications are inherited from the
Shared Library. If you modify a member’s properties in Shared Library, that member’s
properties are also updated in all applications that share the dimension. However, from
within an application, you can override the settings inherited from Shared Library. If you
edit a member property in an application, the Shared Library property setting is
overridden for that application. Updates to the property setting in Shared Library no
longer update the property setting in the application.
TIP
To return a member property that has an override value to its default state, so that
it inherits from Shared Library, right-click the member and select Remove Value.

Excluding and Showing Members

Excluding and Showing Members

You can exclude selected members from shared dimensions for individual applications.
For example, for a revenue forecasting application, you could exclude all the balance
sheet accounts from the Account dimension. You can also show excluded members.
To exclude members:
• In a shared dimension, right-click a member and select Exclude Member.
If you exclude a parent member, its descendants are excluded as
well.

To show excluded members:

1. Right-click the shared dimension and select Show Excluded.
A list of excluded members is displayed.
2. Select the members that you want to include in the dimension, and click OK.

Filtering Members

Filtering Members
You can filter shared dimensions for individual applications to include only a subset of the
members from Shared Library. For example, an application shares the Entity dimension
in Shared Library. You could filter the Entity dimension to include only members of Entity
that are descendants of the North America member.
To filter shared dimensions:

1. Right-click a shared dimension in an application and select Filter Members.
The Member Selector dialog box is displayed.
2. In the list of members on the left, select a member to which to apply a filter and move
it to the Selections list.

3. In the Selections list, right-click the member and select a filter option:
Option Description
Member Includes the selected member
only.

Children Includes the children of the
selected member.
Descendants Includes the descendants of the
selected member.
Siblings Includes the siblings of the
selected member.
Parent Includes the parent of the selected
member.
Ancestors Includes the ancestors of the
selected member.
Inclusive Combines with other filters to
include the selected member. For
example, if you select Descen-
dants and Inclusive, you include
the selected member and its
descendants.
4. Repeat steps 2 and 3 to create as many filters as required.

5. Click OK.

Synchronizing Local Dimensions

with Shared Library

Synchronizing Local Dimensions with Shared Library

If you are maintaining a dimension locally, you can use the Synchronize command to
copy members to or from a dimension in Shared Library. Synchronization does not
create a permanent link between the dimensions. For example, you synchronize an
account dimension in Shared Library with a local account dimension in an application.
Afterwards, you add 10 new accounts to the dimension in Shared Library. The new
accounts are not added to the dimension in the application until you synchronize again.
To synchronize local dimensions with shared librar y:

1. Right-click a local dimension and select Synchronize.
• Select To Shared Library to copy members from the local dimension to Shared Library.

• Select From Shared Library to copy members from Shared Library to the local
dimension.
The Synchronize Dimension dialog box is displayed.
3. In the Dimension list, select the dimension in Shared Library with which to

synchronize the local dimension.
• Select Merge to add the members of the dimension in the source dimension to
those in the destination dimension.
• Select Replace to replace the members in the destination dimension with the
members in the source dimension.

Activating Dimension Associations

Add button
Activating Dimension Associations

After adding a dimensions from Shared Library to an application, you must activate the
required dimension associations for each dimension.
To activate all dimension associations in the application:

• Right-click the application name and select Activate all associations.
To activate dimension associations for a selected dimension:

1. In the application, right-click a dimension and select Dimension Associations.
The Edit Dimension Association dialog box is displayed. The
Master Associations list shows all dimension associations defined
for the dimension in Shared Library.

2. Select the dimension associations required for the application, and click Add.
The dimension associations are added to the Active Associations
list.
3. Click OK.

Adjusting Performance Settings

Most Dense
Dense
Dimensions
Least Dense
Smallest
Aggregating
Sparse
Dimensions
Largest
Smallest
Nonaggregating
Sparse
Dimensions
Largest
Adjusting Performance Settings

Before loading and calculating data, you can optimize the Essbase database outline
settings to analyze their effect on block size. You can modify a dimension’s sparse and
dense settings and its order in the outline.
The order of dimensions is critical to the structure and performance of Essbase
databases. Dense dimensions calculate faster than sparse dimensions, so dimensions
should be in order of most to lease dense.
To adjust performance settings:

1. In the application pane, right-click an application and select Performance settings.
The Plan Type Performance Settings dialog box is displayed.

2. In the drop-down list, select a plan type.

Dimensions belonging to the plan type are displayed with the
number of dimensions for the plan type.
NOTE

Applications can have up to five plan types. If applications are created with a
single currency, the HSP_Rates dimension is not displayed.
3. In the Density column, double-click a cell and select one of the following:
• Sparse—Sparse dimensions lack data values for the majority of member
combinations. A sparse dimension is a dimension with a low percentage of
available data positions filled.
• Dense—For dense dimensions, there is a high probability that one or more data
points is occupied in every combination of dimensions.
4. You can optimize performance by ordering dimensions according to the following
guidelines:
• Make Period and Account dense.
• Order dense dimensions from the most to least dense. The most dense is usually
Account, followed by Period (Time).
• Separate sparse dimensions into aggregating and nonaggregating dimensions.
Place aggregating dimensions before nonaggregating dimensions. Order sparse
dimensions from smallest to largest. (The aggregating dimensions aggregate
children into the parent to create new data; the nonaggregating dimensions do not
create new data by the hierarchies; for example, a Scenario or Version dimension.)

Summary

• Set up application name, plan types, time periods, and currency

• Select dimensions
• Configure application settings
• Add dimensions to applications from Shared Library
• Activate dimension associations
• Adjust Performance Settings

L E S S O N 1 1
Deploying Applications 11

Objectives
• Validate applications
• Compare applications
• Deploy applications
• Review Planning outlines in Essbase Administration Services
• Redeploy applications
Lesson 11 Deploying Applications
Deployment Process

• Validate applications.
• Deploy applications to a Planning
server.
• Create the application files in
relational and OLAP databases.
Deployment Process
In Performance Management Architect, you create applications to describe the
dimensionality and other information required for an application. To create the application
itself, you first validate, and then deploy the application to a Planning server. The
deployment process automatically creates an application on the application server. You
validate and deploy applications from the Performance Management Architect
Application Library.

Validating Applications

• Validate applications from the Application Library.
• Review the validation job in the Job Console.
• If there are validation errors, review the validation log.
Review the
Validation
Log.
Validating Applications
You validate applications before deploying them to ensure that applications meet certain
requirements. Some of the items validated include the following:
• The Start Year property is defined and contains four digits (for example, 2007).
• Members in Year dimensions start with FY, followed by a two-digit year (for example,
FY07).
• The Start Year property and first year in the Year dimension describe the same year
in different formats. For example, if the Start Year is 2007, the first year must be
FY07.
• The Start Month property is defined.
• The Default Alias Table property is defined.
• The Default Currency property is defined.

• Applications include predefined dimensions. Single-currency applications require

Scenario, Version, Entity, Account, Period, and Year. Multicurrency applications
require Scenario, Version, Entity, Account, Period, Year, and Currency.
• The Base Time Period and Weeks Distribution properties are defined.

• At least one plan type is set up. You can add plan types for workforce and capex later
and redeploy the applications; however, you cannot delete plan types after deploying
the applications.
To validate applications:
1. In Workspace, select Navigate > Administer > Application Library.
2. Right-click an application and select Validate > Application (V).
The Job Task box indicates that a job was submitted.
3. Select Click here to navigate to jobs.
4. Review the job summary section.
• If validation errors occurred, click on the link for the validation log and review the
log.
• If no validation errors occurred, close the Library Job Console window.

Comparing Applications

• Comparing applications helps you determine how the
deployed application differs from the one you modified.
• You can review the changes made within dimensions as
well as the overall application changes.
• You can compare property changes since you last
deployed the application.
Comparing Applications
You can compare applications to determine how they differ from those stored elsewhere.
Comparison methods:
• Compare to Shared Library—Compares the dimensions and members in an
application to the dimensions and members in Shared Library View in the Dimension
Library
• Compare to Deployed Application—Compares an application to a deployed
application

The Compare window has three panes:

• Dimension Compare Results—Displays dimensions and members that were added
or deleted. The dimension and members are displayed in the left column, and the
application items are displayed in the right column. The number of differences (at or
below the selected level) is displayed in parentheses. You can expand and collapse

the dimensions as necessary. When you select an item, additional details are
displayed in the panes on the right. Artifacts were removed from the application are
displayed with a strike through. Artifacts with property differences are displayed in
bold.
• Application Compare Summary—Displays a summary of all changes between the
applications or between the application and Shared Library, including Total Member
Count, Total Differences, Additions, Removes, and Filters. The summary displayed
depends on what you selected in the Dimension Compare Results pane.
• Property Compare Results—Displays changed member properties for the selected
member.
To compare applications:
1. Right-click an application, select Compare, and select a comparison method:
• Compare to Shared Library
• Compare to Deployed Application
2. After the progress bar indicates 100% complete, click View Results.
The Compare window is displayed.
3. In the Dimension Compare Results pane, perform an action:
• Select a dimension to view the results in the Application Compare Summary pane.
• Select a member to view the results in the Property Compare Results pane.
NOTE
When a member is added or deleted from a shared dimension, the application
inherits the changes from Shared Library. You can determine that changes were
made by noting the sync status, and you can run one of the comparison reports to
determine the differences.

Deploying Applications
The deployment process creates a Planning application.

Select Shared
Services project.
Select a Data
Create an Source or create
Essbase a new one.
outline.
Deploying Applications
In order to work with Planning applications, after you set up your application in
Performance Management Architect, you deploy the application to the Planning
application server and Essbase.
You cannot change the following properties and application characteristics after you
deploy an application. Therefore, before deploying an application, ensure that the
properties and characteristics are set correctly.
• Whether the application uses a single currency or multiple currencies. For example,
after deploying with multiple currencies, you cannot later use a single currency.
Likewise, with a single-currency application, you cannot later select Multiple
Currency.
• Default application currency. Data values might not be correct because existing
currency values are not converted to the new currency.

• Type of calendar. For example, if you set base time period to 12 months, you cannot
later change it to quarters.
• Fiscal start month.
• Start year. For example, if you set the start year to 2007, you cannot change it to

2006. You can, however, add years after the first year.
• Added years. For example, if the deployed application includes FY09, you cannot
remove this year.
• Weeks distribution pattern. For example, if you set weeks distribution to 445, you
cannot later change it to 544 or Even.
• Plan type, such as Valid For Plan1. You can add only the Workforce and Capex plan
types to deployed applications. You cannot remove plan types. For example, if you
deploy an application with the properties Valid For Plan1 and Valid For Plan2, you
can later add a property named Valid for Workforce. However, you cannot later
remove Valid for Plan2 or Valid for Workforce.
• Added dimensions. You can add up to 20 dimensions, including the required
dimensions. You can rename dimensions.
• Required dimensions. Single-currency applications require these dimensions:
Scenario, Version, Entity, Account, Period, and Year. Multicurrency applications
require these dimensions: Scenario, Version, Entity, Account, Period, Year, and
Currency.
To deploy applications:
1. Ensure that the Planning Application Server is started.
2. In Workspace, select Navigate > Administer > Application Library.
3. Right-click an application and select Deploy.
4. If validation errors occur, view the validation error details.
a. Click View Errors to view the number of errors.
b. Click Details to view the list of errors.

5. Set the deploy options:
Option Description
Instance Name Select the Planning instance for which the application should
be deployed. Instances are used to link Performance

Management Architect to a Planning application server.
Application Server Select the Planning Web application server to which the
application is deployed.
Shared Services Project Select the Shared Services project for the application.
Purge Transaction Select this option to delete the transaction history after a
history on success successful deployment.
Data Source Either select the data source for the application or create a
data source. Data sources link the relational database and the
Essbase server. For Planning, each application must be
associated with a data source.
Create Outline Select this option to deploy an application for the first time or
to recreate the Essbase outline.
Refresh Outline Select this option to refresh the Essbase outline. You use this
option to refresh or update the Essbase outline for an
application that was already deployed.
Create Security Filters Optional: Select this option to generate security filters for all
users in the application.
Shared Members Optional: Select this option to apply access permissions to
Security Filters shared members.
Validate Security Filter Optional: Select this option to identify security filters that
Limit exceed the Essbase security filter limit of 64 kb per row.
Deploy Rules Select this option to deploy rules defined in Calculation
Manager.
Reminder:
• If you are deploying a Planning application for the first time, select Create Outline
to create the Essbase outline.
6. Click Deploy.
The application is deployed to the Planning Web application
server as a Planning application.

7. Select Navigate > Administer > Library Job Console to view the status of the deployment.
The Library Job Console displays the current job status and the
percent completion. You can click the Attachment link to view an
error log. Should deployment of the application fail, the error log
contains valuable information about the reasons for the failure.

When the deployment is completed, the status and deployment
timestamp are updated in the Application Library, and the
application is deployed to the Planning Web application server as
a Planning application.

Creating Essbase Databases

Outline .otl
Calculation Script .csc
Report Script .rep
Load Rules .rul
Creating Essbase Databases

You can create Essbase databases either at the time of deployment or as a separate
action. To create the database outline, you select the Create Outline option when you
deploy the application.
An Essbase database is created for each plan type defined in a Planning application to
store and calculate its data. You can store the following objects in an Essbase database:
• Database outlines—Define the structure of the multidimensional database
consisting of dimensions and member hierarchies. The file extension is .otl.
• Calculation scripts—Enable you to perform custom calculations in addition to the
standard consolidations and the standard mathematical operations defined in the
database outline. The file extension is .csc.
• Report scripts—Define reports based on data in one or more databases. The file
extension is .rep.

• Data load rules—Define editing operations on data files that populate the database.
The file extension is .rul.

Reviewing Planning Outlines

V iew
pane
Outline
E ditor
Reviewing Planning Outlines

After deploying Planning applications, you can perform the following tasks in
Administration Services Console:
• View the database outline
• Create load rules for loading data
• Load data into databases
• Calculate databases (aggregate data)
• View log reports and other database server information for troubleshooting

Essbase Directory Structure

Essbase applications are stored in the following directory
structure:
C:\Hyperion\products\Essbase\EssbaseServer\App\
<ApplicationName>\<DatabaseName>
Co rpBud
Corporate Budgeting application
BalSheet
Balance Sheet database (plan type)
In cStmt
Incom e Statement database (plan type)
Revenue
Revenue database (plan type)
Essbase Directory Structure

Applications are created with their own directory with the same name as the application.
Server-based applications are in a directory under the
\Hyperion\Essbase\EssbaseServer\App directory; for example,
\Hyperion\Essbase\EssbaseServer\App\CorpBud. The databases associated with the
application are in a directory under the application’s directory; for example,
\Hyperion\Essbase\EssbaseServer\App\CorpBud\BalSheet. This directory structure is
located on the Essbase server.
Essbase objects such as calculation scripts, load rules, and reports scripts are typically
located in the database directory to which they are associated. However, they can also
be located in a client directory on your local client machine; for example,
\Hyperion\Essbase\Client.

Redeploying Applications

Change in dimension hierarchy - Replace
Change in properties - Merge
Perform ance Redeploy Planning

Management Application Server
Architect
Dimension
Server HYPlan HYPlan
Redeploying Applications
If you change the metadata, you should redeploy the application to update the relational
and Essbase databases. Redeploying performs a merge or a replace of the application
metadata based on the types of changes you made since the last deployment. For
example, if you moved or deleted members in any hierarchy in the application,
redeployment of the application performs a replace for the metadata changes. If you
made only property value changes to the application since the last deployment,
redeployment of the application performs a merge for the metadata changes.

Summary

• Validate applications
• Compare applications
• Deploy applications
• Review Planning applications in Essbase Administration Services
• Redeploy applications

L E S S O N 1 2
Setting Up Exchange Rates 12

Objectives
• Create exchange rate tables
• Enter exchange rates
• Generate currency conversion calculation scripts
Lesson 12 Setting Up Exchange Rates
Currencies and Exchange Rates

• Enter values in local currency
• Use exchange rates to convert values from one currency
to another
• Set up currency conversions by:
– Entering exchange rates for converting to reporting
currencies
– Generating currency conversion calculation scripts
Currencies and Exchange Rates

You can plan, forecast, and analyze financial information in single or multiple currencies.
If your application is enabled for multiple currencies, users can see values converted
from the local currency to a reporting currency.
You use exchange rates to convert values from one currency to another. You can plan in
a variety of currencies to:
• Enable budget preparers in various countries to create plans in their native
currencies
• Show summary data in reports in a particular currency
• Summarize values from multiple currencies into a single currency
For example, the base currency for Japan is the Japanese yen and that for the United
States is the U.S. dollar. When you view a data form that contains values for Japan, if the
display currency is set to U.S. dollars, the exchange rate for the Japanese yen is used to
convert the values to U.S. dollars.

Exchange Rates Tables Overview

To use exchange rates:
• Select multiple currencies when creating applications
• Specify base currency, currency code, and symbol
• Specify triangulation currency and reporting currency
• Set the exchange rate type
Exchange Rates Tables Overview

You enter exchange rate values through exchange rate tables. You can create exchange
rate tables to correspond to different business scenarios.
For example, you can create an exchange rate table named Actual Rates and another
named Budget Rates. You can then associate the Actual Rates table with the Actual
scenario, and associate the Budget Rates table with the scenarios Forecast and Budget.
After you create the exchange rate tables in EPMA, you can enter exchange rate values
in Planning.
Calculation scripts run business calculations for your application. Typically, you create
calculation scripts for your application using Business Rules. However, Planning
automatically generates the calculation scripts needed for currency conversion.

Creating Exchange Rate Tables

Properties of Budget
Add Exchange Rate Table
Creating Exchange Rate Tables

You create exchange rate tables in Performance Management Architect by associating
them with scenarios. After you deploy the application, the exchange rate tables are
created in the Planning relational database, and users can enter exchange rate values in
Planning.
You can create as many exchange rate tables as the application requires, each
representing a different business scenario. For example, you can name the tables
Forecast, Actual, and Budget, and associate them with multiple scenarios. Each
scenario can be associated with only one exchange rate table. After creating a scenario,
you can select the exchange rate table to use for currency conversion.

To create exchange rate tables:

1. From Workspace, select Navigate > Dimension Library and create or open a Scenario
dimension.
2. Create or select a scenario.

3. In the Exchange Rate Table properties field, enter the Exchange Rate table associated
with this Scenario and save your changes.
4. Deploy or redeploy the application.
5. In Planning, select Administration > Manage Exchange Rates.
The Manage Exchange Rates page is displayed.
6. Select the newly created Exchange Rate table and click Edit.
You can now enter exchange rate values into the Exchange Rate
table.

Entering Exchange Rates

Select the type
of rates to enter
Enter Exchange
Rates
Application
default currency
Shortc ut m enu options
Entering Exchange Rates

You can enter conversion values between the default currency and all currencies set up
in the currency module. When you set up exchange rate tables, only the default currency
and triangulation currencies are available as destination currencies. You can enter
exchange rates from all source currencies to the default or triangulation currencies.
Types of Exchange Rates

Three types of exchange rates are associated with a currency:
• Historical
• Average
• Ending

You specify the exchange rate type used for each account when you set up accounts in
EPMA. For average and ending rates, you can enter rates for each time period. For the
historical rate type, you enter a single rate that is used for all time periods.
To enter exchange rate values:

1. Select the Exchange Rate table, and click Edit.
2. On the Rate Table tab, select values for the following display options:
• Average
• Ending
• BegBalance
• Historical
• Method
3. Click Next.
4. On the Exchange Rate tab, select values for the following options:
• To Currency
• Show Years
5. From the Method drop-down list, select a method.
6. In the Historical, Beg Bal, Avg, and End columns, enter values.
7. Optional: Right-click to use the Fill Year or Fill Table option.
8. Click Save.
Each exchange rate table spans all time periods of the application, so that you can apply
exchange rates to all scenarios. If you create a table or modify one, you must refresh the
application for the new exchange rates to be stored in the plan types.

Calculating Implied Rates Through Triangulation

Assumptions:
• U.S. dollar is the default application currency.
• Euro is a reporting currency.
• British pound is a local currency available in the application.
Rate
British pounds to U.S.dollar 1.4
European euros to U.S. dollar 1.2
1.4 / 1.2 = 1.16
Calculating Implied Rates Through Triangulation

You enter exchange rates for converting the currency values to the application’s default
currency, not to reporting currencies. Planning automatically derives the rates for
converting to reporting currencies by triangulation through the application currency.
For example, suppose the U.S. dollar is the application currency and the European euro
is a reporting currency. You enter 1.4 as the rate for converting British pounds to U.S.
dollars and 1.2 as the rate for converting European euros to U.S. dollars. To determine
the rate for converting British pounds to European euros, Planning divides the British
pound rate by the European euro rate: 1.4/1.2 = 1.16.

When you set up currencies, you specify whether the currency has a triangulation
currency that allows the currency to be translated to a different currency through a
common third currency—the triangulation currency. You enter exchange rates for
converting from the currency to its triangulation currency. The exchange rates between
the currency and other currencies that triangulate through the triangulation currency are

calculated automatically. These rates are called implied rates.
For example, the British pound and the Danish krone might both be set to triangulate
through the European euro. After rates are entered for converting between the British
pound and the European euro and between the Danish krone and the European euro,
the rates for converting from the British pound to the Danish krone and from the Danish
krone to the British pound are automatically calculated.
NOTE
If you modify a currency’s triangulation currency, you must reenter exchange rates
for the triangulation currency property, and you must refresh the application so
that the exchange rates are transferred and stored. You cannot select the
application’s default currency as a triangulation currency.
Determining the Calculation Method

When you enter exchange rates for converting from one currency to another, you select
either Multiply or Divide as the calculation method. For example, if you enter 2 as the rate
for converting British pounds to U.S. dollars, and you select Multiply as the calculation
method, 1 British pound is converted to 2 U.S. dollars.

Exchange Rates and the HSP_Rates Dimension

Input members Draft 1
100.00 USD
Currency (Rate) members
Exchange Rates and the HSP_Rates Dimension

Multicurrency applications store exchange rates in the HSP_Rates dimension. The
HSP_Rates dimension is created in the Essbase databases for multicurrency
applications and is not available in Planning. The HSP_Rates dimension has two sets of
members: input members and currency rate members.
The input members are HSP_InputValue and HSP_InputCurrency. HSP_InputValue
stored data values, and HSP_InputCurrency stores currency types for those data values.
When you enter or load a data value in a cell for the local currency, it is stored at the
intersection Local -> HSP_InputValue. The intersection Local -> HSP_InputCurrency
stores the currency code for that value.
The currency members of the HSP_Rates dimension store the exchange rates for each
currency. There is an HSP_Rates member for each currency added to the application.

Generating Currency
Conversion Calculation Scripts

Select Administration > Manage Currency Conversion
Generating Currency Conversion Calculation Scripts

Two types of calculation scripts are associated with currency conversion: one that copies
exchange rates to account members and one that executes the currency conversion. To
generate these calculation scripts, you select options on the Manage Currency
Conversion window. You run calculation scripts using the Launch Business Rules task in
Planning.
When you generate the calculation script, you select the reporting currencies, scenarios,
and versions for which you want the calculation to run. You can generate currency
conversion calculation scripts to correspond to different business processing scenarios.
Typically, you create a separate calculation script for each scenario.

Copy Rates Calculation Scripts

The Copy Rates calculation script copies the appropriate exchange rate to the individual
account members based on their exchange rate type. Performance is improved because
Planning can retrieve the conversion rate for the account directly, without looking up the
rate type.

Separate copy rate calculation scripts are generated for bottom-up and target versions.
The name of the script is HspCRtB for bottom-up versions and HspCRtT for target
versions. You run these scripts after you enter exchange rates and before you run the
currency conversion calculation script for the first conversion. Subsequently, you run the
copy rates calculation scripts only when the following conditions change:
• Exchange rates
• Account exchange rate types
• Exchange rate table assignment for a scenario
• Metadata (For example, a new currency or account is added.)
Currency Conversion Calculation Script

Planning generates a calculation script to convert values for local currencies to one or
more reporting currencies. The calculation script converts values for all accounts and
entities. The currency conversion calculation script generated by Planning converts only
level 0 members for bottom-up versions and all levels for target versions. For bottom-up
versions, you must run an aggregation to populate upper-level members with the new
converted values.
Because the Currency Conversion calculation script runs for all entities and accounts in
your application, it typically is run by budget administrators rather than end users. If end
users need to see their data converted to a reporting currency, they should use the
Calculate Currencies business rules associated with data forms.
Calculate Currencies Business Rule

In addition to generated currency conversion calculation scripts, a dynamically system-
generated business rule is associated with data forms. It converts data from the local
currency to the reporting currency for only the members currently displayed on the data
form. This business rule enables planners to view converted values for the entered data.

Summary

• Create exchange rate tables

• Enter exchange rates
• Generate currency conversion calculation scripts


M O D U L E 4
Loading Data and

Calculating the Database 12

Overview
The aim of this module is to discuss the requirements for data load files,
and when to use data load rules to load data into Essbase. You also see
how data is calculated within a dimension, data blocks calculation order,
and discuss calculation scripts. You load data using Administration
Services. You calculate the database to calculate data for upper level
members in the hierarchy.
• Loading and Calculating Data: Overview
• Loading Data
L E S S O N 1 3
Loading and Calculating Data: Overview 13

Objectives
• Define the requirements for data load files
• Describe the setup for data load rules
• Describe the setup for data staging using interface tables
• Describe loading data using ETL tools
• Identify how data is calculated within dimensions
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Data Loads

You can:
• Load data directly into the Essbase database for each plan
type.
• Use any of the following for loading data:
– Administration Services
– Performance Management Architect interface tables
Data Loads
Planning creates an Essbase database for each plan type in your application. You can
load data directly into the Essbase database that corresponds to the plan type in your
application. When you create your Planning application, the Essbase databases do not
contain data.
You can load data values from external systems into your Planning application. For
example, you might want to load data for actuals from your ERP system so that you can
calculate variances.
You can use the following methods to load data:
• Data can be extracted to ASCII text files (flat files) from external systems and loaded
using Essbase data load rules.
• Data can be loaded with Performance Management Architect interface tables.
• Data can be loaded with an ETL tool using Essbase and Planning adapters.

• Data can be loaded using Financial Data Quality Management (FDM)

To load data, you must have these items:
• An Essbase database into which you load the data or in which you build an outline

• A connection to the Essbase Server
• Any of the following valid data sources:
- Flat files from text backups or external sources
- Relational database data sources such as SQL or Oracle
- Essbase export files
- Microsoft Excel spreadsheet files with the .xls extension (When using spreadsheet
files to load data or build an outline in Essbase, the spreadsheet files must reside
on a Windows computer, regardless of the tool you use.
- Lotus 1-2-3 files with the .wks, .wk1, .wk3, or .wk4 extension
- Spreadsheet audit log files
• If you are not using a rules file for loading data, a data source correctly formatted for
free-form data loading
• If you are using a rules file for loading data, a rules file validated for data loading

Requirements for Data Load Files

Use Essbase to load data from flat files into your Planning application.
Entity A ccou nt Scenario Version Period Year Data
EUROPE GROSS SALES ACTUAL FINAL Jan 2008 1000

EUROPE GROSS SALES ACTUAL FINAL Feb 2008 400
EUROPE GROSS SALES ACTUAL FINAL Mar 2008 650
ACTUAL FINAL
EUROPE GROSS SALES JAN 2008 1000
EUROPE NET INCOME FEB 2008 400
ASIA NET INCOME FEB 2008 300
ASIA GROSS SALES JAN 2008 200
BUDGET DRAFT 2009

ENTITY PERIOD CUSTOMER 40 00-100 4000-200 4000-300
EUROPE FEB MY COMPANY 15 00 1700 1200
Requirements for Data Load Files

The first graphic shown on the slide is an example of a data load file that loads data
values for the first quarter of 2008 for the Europe entity and the Gross Sales account in
the Actual scenario and the Final version. If a dimension has the same value for all rows,
you can place it in the header as a page dimension, as shown in the second graphic on
the slide.
Requirements:
• Each data point must be tagged with a member from each dimension.
• Data must be for bottom-level members, unless you are loading data into a target
version.
• Data is scanned from the top of the file and from left to right.
• Each field (item) in a record (row) must be separated by a valid delimiter.

• A member name or alias must be enclosed in double quotation marks (" ") if it
contains blanks, numeric characters (0–9), dashes, or unary operators. It must also
be displayed exactly as it is in the outline.
• Members of the same dimension must be in the same column or row.

• Members of different dimensions can be together only on the page header. They
cannot be used together in any other row or column.

Multicurrency Applications

The HSP_Rates dimension has the following members:
• HSP_InputValue
• HSP_InputCurrency
• HSP_Rate_<XXX>
Multicurrency Applications
Applications that support multiple currencies include an additional dimension called
HSP_Rates to store exchange rates. The HSP_Rates dimension includes the following
members:
• HSP_InputValue—This member stores data values.
• HSP_InputCurrency—This member stores currency types for the data values.
• HSP_Rate_<XXX> —This member stores currency for multicurrency applications
(XXX represents the currency).
You load data to the HSP_InputValue member and the local currency. The
HSP_InputCurrency member is not displayed in Planning. However, if the default
currency is overridden, the new currency is stored along with its value in the database.
By storing the new currency, Essbase can apply a different currency value to the data
displayed for HSP_InputValue.

Data Load Rules

Data load rules map external data values to the Essbase database
2009 Budget Dr aft 1 USREG L ocal 210-MI CH N001 HSP_I nputValue Jan
2009 Budget Dr aft 1 USREG L ocal 210-MI CH N001 HSP_I nputValue Feb
2009 Budget Dr aft 1 USREG L ocal 210-MI CH N001 HSP_I nputValue Mar
Raw data file
Rules applied
Data Load Rules

You use data load rules to delineate how data is loaded into Essbase databases. Load
rules can perform certain actions on the data originating from external data sources as it
is loaded into the Essbase database. For example, if the data file contains fields that are
not needed, you can ignore those fields during the data load.
You create data load rules when any of the following criteria need to be applied during a
data load:
• Ignore fields or strings in the data source.
• Change the order of fields by moving, joining, splitting, or creating them.
• Map the data in the data source to the database by changing strings.
• Change the data values in the data source by scaling the data values or adding them
to existing values in the data source.

• Set header records for missing values.

• Reject invalid records and continue loading data.
You can use the Data Prep Editor to create data load rules. The Data Prep Editor
contains two window sections:

• The top text window provides a view of the data source, called the raw data source.
• The bottom text window contains a grid showing the appearance of records after
rules are applied (that is, as they will be loaded into the database).
Data load rules do not modify the content of the raw data source.
The Data Prep Editor displays two fields: Data Load and Dimension Build.
After you open the Data Prep Editor from the Administration Services Console, you can
open data sources such as flat files, spreadsheet files, and SQL data sources.

Data Staging: Interface Tables

Interface tables enable you to:
• Stage data for import
into Planning.
• Create multiple tables
for data import.
• Reuse staging areas
for data loading.
Data Staging: Interface Tables

In Performance Management Architect, interface tables are database tables used to
import data from external systems into Performance Management Architect.
You can create multiple interface databases, and the database type can be different than
the database for the interface tables; for example, a Microsoft SQL database, and Oracle
interface tables.

Loading Data Using ETL Tools

• Connect and integrate Planning with any database through
the Oracle Data Integrator Adapter for Planning.
• Set up workflows in Data Integration Management to load
Planning data

You can load data into Planning using ETL tools such as Oracle Data Integrator, and
Data Integration Management. In order to use any ETL tool, you need to have the
corresponding Planning adapter.
Oracle Data Integrator (ODI) enables you to connect and integrate Planning with any
database by using the Oracle Data Integrator Adapter for Planning. The adapter provides
a set of modules for loading metadata and data into Planning, Workforce Planning, and
Capital Asset Planning.

Data Calculations

There are three types of calculations in Planning:
• Calculations within dimensions
• Calculations and data blocks
• Calculation scripts
Data Calculations
Typically, you load data into the level 0 members of a database. After loading data, you
calculate the database.
When you calculate the database:
• Child member values are aggregated to derive parent member values.
• Member formulas defined in the outline are applied.


Calculations Within Dimensions
The calculation of a dimension follows the outline structure. The order in which members
are calculated follows the order in the outline:
• Calculations start at the lowest level of a branch from top to bottom.
• Calculations move up to the next level when the end of a subbranch is reached.
The example on the slide depicts the order of a calculation in the Account dimension.
Selected calculations occur in the following order:
• Within the Margin branch: Sales and then COGS
• Within the Profit branch: Margin and then Expenses
• Within the Measures branch: Profit, then Inventory, and then Ratios

Calculations and Data Blocks

S parse dimension
calculation
Dense dimension calculation
Calculations and Data Blocks

Essbase databases are organized into data blocks. As you recall, a data block consists
of all dense dimensions members in the outline for a unique combination of sparse
dimension members. There is potentially a data block for each unique combination of
sparse dimension members.
The order in which the data blocks are calculated follows the order in which the sparse
dimensions are listed on the Performance Settings screen. The data blocks for the
members of the first sparse dimension listed on the Performance Settings screen of the
Planning Dimension Editor are calculated first, and so on down the list.

Calculation begins with level 0 data blocks. Level 0 data blocks are those for which each
sparse dimension member is a level 0 member. To calculate the values for a data block,
the Essbase Server calculates the dense dimension members of the data block. After
calculating the values for the level 0 blocks, it aggregates them to derive the value for the
upper-level blocks. This process is repeated for each level of data blocks until the top is

reached.
The graphic shown in the slide depicts the following example:
• There are level 0 data blocks for the Los Angeles and San Francisco sparse
dimension members, and an upper-level data block for California, their parent.
• The data blocks each have Account and Period dimensions as dense dimensions.
• Essbase calculates the Account members and the Period members for the Los
Angeles and San Francisco data blocks, based on the outline structure for the
Account and Period dimensions.
• Essbase aggregates the Los Angeles and San Francisco data blocks to derive the
values for the California data block. If the California data block exists, the current
values are overwritten. If it does not exist, the data block is created.
When Essbase calculates the dense dimension members for a data block, it first
calculates the Account dimension, and then the Period dimension. The remaining dense
dimensions are then calculated based on their order on the Performance Settings
screen.

Calculation Scripts

Calculation scripts:
• Contain a series of calculation commands, equations, and
formulas.
• Define calculations other than the calculations defined by
the database outline.
• Specify how to calculate a database.
The default calculation script calculates the entire database.
Calculation Scripts
Every database needs at least one calculation script to aggregate unary operators and
execute formulas in the outline. For most database calculations, the default outline
calculation script provides the required results. You can run the default outline calculation
script from Administration Services Console.
In certain cases, you may need to write a calculation script to control how Essbase
calculates a database:
• You can use Business Rules as a graphical environment .
• You can create native Essbase calculation scripts by using a text editor or the
Essbase calculation script editor.

Summary

• Define the requirements for data load files

• Describe the setup for data load rules
• Describe the setup for data staging using interface tables
• Describe loading data using ETL tools
• Identify how data is calculated within dimensions

L E S S O N 1 4
Loading Data 14

Objectives
• Describe data load rules
• Create load rules for Administration Services
• Load data using Administration Services
• Load data using rules files
• Load data using interface tables
• Describe loading data using ETL Tools
Lesson 14 Loading Data

Loading Data Using Administration Services
You use Administration Services to load data values into Planning applications. You load
data directly into the Essbase databases that correspond to the plan types in the
application.
To load data values:

1. In Administration Services, select a database, right-click, and select Load data.
2. Click Find Data File to select a file to load.
3. Optional: Click Find Rules File to select a rules file.
4. Click OK.


Creating Data Load Rules
Data load rules are sets of operations that are performed on data from external data
sources when the data is loaded into an Essbase database. Data load rules map
external data values to the Essbase database.
You specify these options when you create data load rules:
• Set file delimiters
• Associate the rules file with an outline
• Define header information
• Map fields to member names and column fields
• Manipulate column fields and replace text strings


Opening Data Sources
After you select to create a rules file, the Data Prep Editor is opened. Next, open data
sources to see what data needs to be changed. The data source can be located on the
Essbase Server, locally, or on the network. Examples of valid data source files are
Microsoft Excel and Lotus 1-2-3 spreadsheets, plain text files, and Essbase export files.
Setting File Delimiters

File delimiters are the characters that separate fields in the data source. By default, the
rules file separates fields using tabs. You can set the file delimiter to be a comma, tab,
space, fixed-width column, or custom value. Usually, you set the file delimiter
immediately after opening a data source.

Associating Rules Files with Outlines

You associate the rules file with an Essbase database outline in order to populate list
boxes with dimension and member names. Typically, you select the outline of the
database into which you load the data. The rules file is not permanently associated with
that outline, and you can associate it with another outline later. The rules file must be

associated with an outline so that you can validate it.

Defining Header Records

Headers in data source
Entity ... Jan Feb ...
New York ... 150 160 ...

Albany ... 60 60 ...
White Plains... 20 20 ...
Headers in rules file
1st quarter Budget Data

Jan Feb ...
New York ... 150 160 ...
Albany ... 60 60 ...
White Plains... 20 20 ...
Skip tw o lines and map to Budget
Defining Header Records

You can use the Data Prep Editor to create header records in rules files. Data sources
can contain data records and header records. Data records contain member and data
fields. Header records describe the contents of the data source and how to load data
values into the database.
A rules file contains records that translate the data in the data source to the database. As
part of that information, the rules file can also contain header records.
Defining Header Information in Rules Files

Headers are used only during data loads or dimension building. They do not change the
data source. Header information in a rules file is not used if a dynamic reference in the
rules file points to a header record in the data source.

Defining Header Information in Data Sources

If the data source contains header information, you can specify its location in the rules
file. The rules file then passes information to the Essbase Server to read the header
information as a header record and not as a data record. You can also specify the type of
header information in the header record. For example, the header record can contain

data load field names.
If the data source does not have header information, you can add it to the data source by
using a text editor or spreadsheet and then identifying those records as the header
information in the rules file. Placing header information in the data source makes it
possible to use the same rules file for multiple data sources with different formats: The
data source format is specified in the data source header, not in the rules file.
NOTE
Header information defined in the data source takes precedence over header
information defined in the rules file.

Associating Column Fields

with Dimensions and Members

Associating Column Fields with Dimensions and Members

When loading data from a data source file, you must specify how the fields in the data
source file map to the dimensions in the database. Data load rules refer to columns in the
data source file. When setting up a data load rule, you must match each column of
information to a specific dimension or dimension member. Each column of information
contains either a member label or a data element. In a data load, you must specify every
dimension in the database in either the data source or the rules file. If the data source
does not identify every dimension in the database, you must identify the missing
dimensions in the rules file.
Mapping Fields to Member Names

When the data source is loaded, a rules file can translate fields in the data source to
match member names without changing the data source. The rules file performs the
following tasks:

• Maps member fields in the data source to members in the database

• Maps data fields in the data source to member names or member combinations
(such as Jan, Actual) in the database
You can also define rules for these purposes:

• Name, or translate, the fields in the data source to match members in the database
• Replace strings or translate the fields in the data source to match members in the
database
Mapping Column Fields

A column field can contain the name of a valid dimension member or an alias. Use one of
the following methods to specify a field name:
• On the Data Load Properties tab of the Field Properties dialog box, in the Field name
text box, enter the member name or member combination to which the current field
maps.
From the Dimension node, select the field name that displays the names of the
dimensions and members in the associated outline.
If a field represents information that is not data and is extraneous to the outline, you can
ignore the field by selecting the “Ignore field during data load” check box. You use the
Data Load Properties area of the Field Properties dialog box to define field names for the
columns of the rules file.
Manipulating Column Fields

Your data source may not always have columns in the correct sequential order, or you
may need to manipulate column details such as duplicating, parsing, or concatenating
columns to create unique member names.
Action Description
Move Changes the sequential order of columns
Split Parses fields; used for segregating columns where the source file has
fields of variable length and does not have field delimiters
Join Joins two or more columns
Create Using Join Creates a column or set of columns; used to duplicate a column
Create Using Text Creates a column that contains any text, including white spaces

Replacing Text Strings

You can:
• Use a rules file to replace
text strings so that fields
map to Essbase member
names during a data load
• Replace text strings without
changing the data source
Replacing Text Strings

You can use a rules file to replace text strings so that the fields map to Essbase member
names during a data load. The data source is not changed. For example, if the data
source abbreviates New York to NY, you can have the rules file replace each NY with
New York while loading the data.
Replace options:
Option Description
Replace Use to enter the text string to be replaced.
With Use to enter the text string to replace the one in the Replace text
box.
Case-Sensitive Select to construct a condition based on a case-sensitive string.

Option Description
Match Whole Word Select to indicate that Essbase should replace the text string only
when it occurs as an entire word. If the text string is embedded in
another word, it is not replaced.
Replace All Select to indicate that Essbase should replace all text strings that

Occurrences match the text string in the With field. By default, Essbase replaces
the first occurrence.
New Click to add a new line for additional changes entered in the Replace
and With fields.
Delete Click to remove items from action lists.
Original Select to leave existing fields in their original case. By default, this
option is selected.
Lowercase Select to change all characters of the field to lowercase.
Uppercase Select to change all characters of the field to uppercase.
Prefix Use to enter a text string to be added at the beginning of the field
values. (You cannot use parentheses in the Prefix text box.)
Suffix Use to enter a text string to be added to the end of the field values.
Drop leading/trailing Select to remove leading and trailing white spaces around fields. (A
spaces field with leading or trailing white spaces does not map to a member
even if the name within the white spaces is an exact match.)
Convert spaces to Select to change white spaces in field values to underscores.
underscores

Validating and Saving Rules Files

• You should validate the rules file before saving it.
• You can save the rules file to a local file system or network
or to the Essbase Server.
Validating and Saving Rules Files

You can validate a rules file to ensure that the member and dimension mapping defined
in the rules file maps to the outline. However, validation does not ensure that the data
source is loaded properly.
The rules file is validated against the associated outline. When the Essbase Server
finishes the validation, the Validate Rules dialog box is displayed. It contains information
about the validation process, including fields that did not map to the outline. If the rules
file is validated without problems, you can use it to load data.
After validating the rules file, save it to the Essbase Server or locally. The name must be
a valid name in your operating system. In addition, the rules file name that you specify
must be eight or fewer alphanumeric characters in length. Essbase automatically adds
the .rul extension.

Fixing an Invalid Rules File

If the rules file does not pass validation, you must fix it before loading data. Go to the field
specified in the Validate Rules dialog box, and check the following items:
• Is the field name spelled correctly?

• Are the file delimiters placed correctly?
• Is there a member name in the field name?
• Is the dimension name used in another field name or the header?
• Is a member used as a member combination in one place and as a single member in
another?
• Is more than one field defined as a data field?
• Is the dimension used for transposing signs in the associated outline?
• Is the rules file associated with the correct outline?
After making the corrections, run the validation again.


Loading Data Using Rules Files
After the rules file is generated, you can load data using the rules file.
To load data using rules files:

1. From the Administration Services Console, Enterprise View or a custom view, select
the database. Right-click and select Load data.
The Data Load dialog box is displayed.
2. Select one or more data sources.
3. Click the Find Rules File button and select the rules file name.
The rules you selected are displayed on the Data Load dialog box
in the Rules File column.

4. Optional: Under Error File, specify where errors should be written.

By default, errors are written to the
Hyperion\AnalyticServices\client directory.
5. Click OK to load the data.

Essbase runs the data load.
6. Check errors and status messages that are displayed in the Messages panel at the
bottom of the console window as well as those written to the error file.

Staging Data with Interface Tables

Interface tables
ETL Planning
Performance
Management
Architect
Staging Data with Interface Tables

You use Interface tables to create a staging area for loading data from outside systems
(ERP, ETL, GL, and so on) into Performance Management Architect for use in Planning.
Using interface tables to load data helps you to streamline the data load process. You
can predefine a data set that you want to import into Planning and stage it for loading at
any time.
You can create multiple Interface Tables for staging data.
NOTE
Before you can load data from interface tables, you must first have a relational
database set up to store the information in the tables, and then you must run the
configuration utility to configure the tables in the new relational database.

Creating Interface Tables

Creating Interface Tables

You create Interface Tables within the Data Synchronization module of Performance
Management Architect.
You can load data as well as metadata into Shared Library using interface tables.

Loading Data Using Interface Tables

Process before Interface Table Import Process
Interface Table Import
ERP F inancial
System Manag ement
Interface Performance
ETL
Tables Management Architect
System
Plan ning
Data
Synchronizatio n
General
Ledger Flat File
System
Loading Data Using Interface Tables

In EPMA, you can load data into Planning selecting either a flat file or interface tables.
After you stage data in your ETL system and you create interface tables, you can use the
interface tables to load data into Planning. The data remains in the interface tables so
that you can repeat the process to load data into another application or into the same
application at another time. Data is loaded directly into Essbase which you can use in
Planning. You do not load data to the Planning relational database using this method.
To load data using interface tables:

1. In Performance Management Architect, select a Planning application.
2. Right-click and select Action > Import.


• Load data using flat files
• Load data using ETL process

You can use ETL tools to load data into Planning applications. If you have a simple data
load, you can load a flat file. However, if you have a complex data load, you can use an
ETL tool such as Oracle Data Integrator (ODI). You also can schedule an ODI data load
to occur during an off peak time.
ODI is a graphical tool for loading data into your Planning environment. For applications
managed using Performance Management Architect, you can load data into Planning
and Essbase by using the Planning adapter.
Adapters depict the structure of the database into which you are loading data. Adapters
are populated with the relevant metadata relationships for a dimension. Therefore,
before loading data into Planning you must ensure that the metadata (dimension
members) exist in both the Planning relational database and Essbase database. If
necessary, refresh the Essbase database to synchronize your changes.

Summary

• Describe data load rules

• Create load rules for Administration Services
• Load data using Administration Services
• Load data using rules files
• Load data using interface tables
• Describe loading data using ETL Tools

M O D U L E 5
Setting Up Security 14

Overview
The aim of this module is to provide an overview of security in Planning.
You learn how to provision users and user groups in Shared Services for
your Planning application. You also learn how to assign access rights to
elements of your Planning application.
• Provisioning Users and Groups
• Setting Up Access Rights to Planning Applications
L E S S O N 1 5
Provisioning Users and Groups 15

Objectives
• Describe security in Planning
• Describe user provisioning in Shared Services
• Provision users and groups for Planning
• Generate provisioning reports
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
Planning Security Overview

In Planning, you can perform the following security-related
tasks:
• Determine user privileges
• Assign access rights to application elements
• Create security filters
Planning Security Overview

Security in Planning is based on user privileges. User privileges are system roles and
access rights that can be assigned to users or to groups.
Groups are sets of users who need similar access rights. After users and groups are
defined, you can assign the users and groups access rights to application elements. For
example, you can assign a user or a group access to Entity dimension members or data
forms.
Access rights for users and groups can vary by application and can be assigned for the
following application elements:
• Scenario, Version, Account, Entity, and user-defined custom dimension members
• Data forms and business rules
• Task lists
After you establish or update user and group security and assign member access, you
must refresh the Planning application to update to the Essbase security filters.

Levels of Security

There are four levels of security in Planning.
Data forms
and task lists
User Task Object Data

authentication security securit y security
Levels of Security
Planning provides security at four levels:
• Users must provide a valid ID and password to log on to the system.
• Users can launch only those tasks to which they have been given access. For
example, you can give users the ability to create data forms but not dimension
members.
• Users can open only those data forms and task lists (objects) to which they have
been granted access.
• Users can view and modify data only for dimension members to which they have
been granted access.

User Authentication

• Users must provide a valid user name and password to
access an application.
• Planning leverages external authentication providers such
as LDAP, Microsoft Active Directory, and NTLM.
• Users and groups must exist in the authentication
directory before they can be granted access to a Planning
application.
User Authentication
User login information for Hyperion applications is stored outside the applications in an
authentication directory. The information is maintained by a central authentication directory.
An authentication directory is a centralized store of users and passwords, user groups, and
perhaps corporate information, such as employee IDs or job tiles. The following types of
authentication directories are supported:
• Windows NT LAN Manager (NTLM) on NT 4.0 or higher, Windows 2000, and Windows
2003
• Lightweight Directory Access Protocol (LDAP) version 3 or later
• Microsoft Active Directory (MSAD) server, Windows 2000 SP3 or later
You can grant access to your Planning applications to any user or group in an
authentication directory. When you grant a group access to an application, the users in the
group are also granted access to the application.
You grant access in Shared Services Console.
Task Security

Administration menu, Administration menu,
administrator’s view interactive user’s view
Task Security
Task security determines the tasks in an application that a user can access. You assign
task security by assigning a role to a user. Each role is associated with a set of tasks. For
example, interactive users cannot change dimension members, so the dimension
change option is not available to interactive members.

Object Security

You can assign security to specific objects in your application.
Data form Task list
Object Security
Within your Planning application, you can assign security to specific objects, such as data
forms and task lists. For example, you can allow all users to access the standard
expenses data form but allow only payroll managers to use the salary expense data form.

Data Security

You can assign users or groups Read, Write, or None access
to data for specified dimension members.
Entity Members Assigned Access Level
• East Region • Write

• West Region • Read
• United Kingdom • Read
• Singapore • None
RJackson
Data Security
Setting up data security enables you to protect data and prevent unauthorized users from
changing data. For example, you can restrict access to certain data elements in an
application.

User and Group Provisioning Overview

User and Group Provisioning Overview

User provisioning enables centralized management of users, their role assignments and
their access rights to applications created under various application groups of various
products. To perform provisioning for Planning applications, you use Shared Services
Console.
Any user with the Provisioning Manager or Administrator role in an application can
perform provisioning.
The main nodes of the Shared Services Console:
• User Directories
• Application Groups

User Directories

User Directories list users from native and external directories
User directories: Native and NTLM
User list for the selected directory
User Directories
In Shared Services Console, you view user directories that consist of users and groups.
User directories can be provided (set up) natively or externally. External directories
(LDAP, NTLM, and MSAD) hold users and groups in each directory. External directories
are typically corporate directories.
You provision users and groups by assigning user roles in an application. A user can
receive a combination of individual and group role assignments.

Application Groups
Application groups bundle instances of Hyperion products that

compose an implementation.
Application Groups
Before you can provision users or groups for a Planning application, the application must
be registered in Shared Services and belong to an application group.
An application group is an instance of Hyperion products that are grouped to compose an
implementation. For example, a Planning application group may consist of a Planning
application, an Essbase application, and a Financial Reporting Server instance. You can
add one or more applications to an application group.
When you create a Planning application, it is automatically registered with Shared
Services and assigned to the Default Application group. You can move applications to
application groups, as needed.
NOTE
An application can be associated with only one application group.

To create an application group, right-click Application Groups, and select New. You then
give the application group a name and description and assign applications as required.
TIP
In a practical sense, you can think of an application group as a type of folder.


Provisioning Users and Groups
Within a user directory, you provision users and groups to your Planning application. You
provision users to enable them to access applications and perform application tasks. You
can select Provision from the Administration menu, or you can right-click the user and
select Provision.
To provision users or groups

1. To open the User Directories within Shared Services, select Start > Programs > Hyperion >
Foundation Services > Shared Services.
2. Log onto Shared Services.
Shared Services Console is displayed.
3. In the view pane, expand User Directories.

4. Select and expand Users, to provision and assign roles to users, or Groups, to
provision and assign roles to groups.
5. Click Search to display a list of all users or groups.
6. Select the user or group that you want to provision.

7. Select Administration > Provision, or right-click a user or group and select Provision.
8. Expand the application group that contains the application for which you want to
provision the user or group and for which you want to assign roles.
9. Expand the application for which you want to provision the user or group and for
which you want to assign roles.
10. Select the role or roles that you want to assign to the user.
11. Click Add.
12. Click Save.

User Roles

User Roles
You assign user roles to users and groups based on the tasks that users need to perform
in applications. Planning provides user roles that can be assigned to users and groups.
The following global Shared Services roles are also used in Planning:
• Application Creator— Creates applications. This is a Performance Management
Architect role.
• Project Manager— Creates and manages application groups in Shared Services.
• Dimension Editor — Creates profiles and imports dimensions. This is a Performance
Management Architect role.
• Create Integrations — Creates Shared Services data integrations (the process of
moving data between applications) using a wizard.
• Run Integrations — Views and runs Shared Services data integrations.

• Planning Calculation Manager Administrator— Administers calculation manager

functions in Planning.
The following table summarizes Planning user profiles.

User Profile Description
Provisioning Manager Users who are assigned the Provisioning Manager role can
provision users and groups to applications.
Administrator Administrators can create applications; manage security; maintain
metadata; initiate and manage the budget process; create and
maintain Web-based data forms; create and manage task lists;
create and maintain Smart View worksheets; create and launch
business rules by using Business Rules; and enter, view, and delete
data.
Manage Models Users assigned the Manage Models role can export and import
Shared Services models.
Interactive User Interactive users can enable e-mail notification; create and maintain
Web-based data forms; create and manage task lists; create and
maintain Smart View worksheets; create and launch business rules
by using Business Rules; enter, view, and delete data; and submit
information and data for approval.
Planner Planners enable e-mail notification; input, submit, and view data; use
reports that have been built by others; run data integration routines
designed by others; execute business rules and other processes
associated with validating and preparing data; view and use task
lists; use Smart View; and submit information and data for approval.
View User View users have limited access to view data in a Planning
application. Typically, the view user is an executive who wants to see
business plans during and at the end of the budget process.
Offline User Offline users can take Planning data forms offline and work with
them in Smart View.
Mass Allocation Users assigned the Mass Allocation role can spread data by using
the Mass Allocation function. Mass Allocation spreads data either
proportionally or relatively to other members in the outline. Even
though you run Mass Allocation from data forms, data is spread to
members even if they are not displayed on the data form. This role
only should be assigned to a select few people because there is no
undo functionality after spreading data by using Mass Allocation.
Analytic Services Write Users assigned the Analytic Services Write Access role can lock and
Access send with write access to Essbase. If you assign this role to planners
and interactive users, you give them write access directly to planning
data in Essbase.


Generating Provisioning Reports
You can generate provisioning reports to list the details of the users, groups, and roles
that are provisioned.
To generate provisioning reports:

• Select Administration > View Report

Summary

• Describe security in Planning

• Describe user provisioning in Shared Services
• Provision users and groups for Planning
• Generate provisioning reports


L E S S O N 1 6
Setting Up Access Rights to

Planning Applications 16

Objectives
• Assign access rights
• Import access rights
Lesson 16 Setting Up Access Rights to Planning Applications
Assigning Access Rights

Use access rights to prevent unauthorized access to data.
Assign access
Add access
View
access
Assigning Access Rights

You assign access rights to Planning application elements to protect data from
unauthorized users or groups. The level of security is determined by the access option
that you assign to a user. You can assign access by using dimension member
relationships or by assigning access directly to individual dimension members. You can
define unique access rights for each Planning application.
You can assign access rights to the following application elements:
• Scenario, Version, Account, and Entity dimension members
• User-defined custom dimension members, if the Apply Security dimension property
is selected
• Data form folders, data forms, and business rules
• Task lists
You can use the dimension editor to assign access to dimension members, or you can
use the ImportSecurity utility to import access rights information from a flat file.
You assign access to data forms in Form Management and to task lists in Task
Management.

Access Options

Member and data form access rights consist of the following
options:
• Read
• Write
• None
Task list access rights consist of the following options:

• Assign
• Manage
• Manage and Assign
• None
Access Options
When you assign access rights to a dimension member, data form, or task list, you
determine which access option to assign for each user or group. By default, for
interactive users and planners, access is denied to all dimension members, data forms,
and task lists.
The following table describes the access options for dimension members and data forms.
Option Description
Read Enables users to view the dimension member or data form
Write Enables users to view and modify access to the dimension
member or data form
None Prevents users from accessing the dimension member or
data form

The following table describes access options for task lists.
Option Description
Assign Enables users to view and use the task list

Manage Enables users to modify the task list
Manage and Assign Enables users to modify, view, and use the task list
None Prevents users from viewing the task list

Inheritance Options

The following inheritance options are available:
• Member
• Children
• iChildren
• Descendants
• iDescendants
Inheritance Options
You can assign access rights to individual dimension members, or you can use an
inheritance option to assign rights to multiple members.
It is more efficient to assign access rights through an inheritance option. You should
assign access to individual members only on an exception basis. For example, for the
North America Sales group, you could assign Write access to North America and its
descendants and Read access to North America Headquarters.
The following table summarizes the available inheritance options for a selected member:
Option Description
Member The access right is assigned only to the member.
Children The access right is assigned to all child members of the
member.

Option Description
iChildren The access right is assigned to the member and to all of its
child members.
Descendants The access right is assigned to all descendant members of
the member.

iDescendants The access right is assigned to the member and to all of its
descendant members.

Precedence and Inheritance

of Access Rights

• Individual rights override group rights.
• For group rights, no access overrides write or read access.

Write access overrides read access.
• Direct member rights override relationship rights
United States United States

LA
Precedence and Inheritance of Access Rights

You can assign access rights to a member in the following ways:
• The user can be assigned direct access to a member.
• The group can be assigned direct access to a member.
• The user or group can be assigned access to a member by relationship, through an
inheritance option.
Access rights from different sources can conflict with each other. For example, you might
be assigned direct Read access to a member and Write access to the same member
through membership in a group. The following sections explain the rules of precedence.

Individual Rights Over Group Rights

Access rights that are assigned directly to a user override access rights that are inherited
from associated groups. For example, if, for the Budget member, you inherit Read
access through a group and are assigned direct Write access, you have Write access to
the Budget member.

Group Precedence
A user might belong to several groups that have conflicting access rights to a member. In
this case, None access take precedence over Write or Read access. Write access takes
precedence over Read access. Here are some examples:
• If you have Write access to the Budget member from one group and None access to
Budget from another group, you have None access to Budget.
• If you have Read access to the Budget member from one group and Write access to
Budget from another group, you have Write access to Budget.
Direct Member Rights Over Relationship Rights

You can assign access rights to members indirectly through relationships to a parent or
ancestor member. Rights that are assigned directly to a member override rights that are
derived from a member relationship. Here are some examples:
• You are assigned None access to children of the United States. You are assigned
direct Read access to LA. You have Read access to LA.
• You are individually assigned Write access to children of the United States. Your
group is assigned direct Read access to LA. You have Read access to LA.


Reporting on Access Assignments
To help you effectively view the current access assignments in an application, you can
generate assigned access reports. You can also generate effective access reports to
help resolve inheritance or precedence conflicts. You generate these reports from
Shared Services Console.
When you generate an assigned access or an effective access report, you specify what
information to include, as follows:
• Specific users and groups or all user and groups
• Specific dimensions or all dimensions
• Data forms
• Matching access types: Read, Write, or None
You can group results by users or by objects. You also can report on assigned access by
access relationship and inherited group or by effective access, including effective access
origin.

Importing Security Overview

• You can use the ImportSecurity utility to load access rights
information.
• You create a text file named SecFile.txt and locate the
file in the C:\Hyperion\products\Planning\bin
folder.
Importing Security Overview

You can load access rights from a text file into Planning by using the ImportSecurity
utility, which enables you to quickly assign access for many members, users, and
groups. When you import access rights for a member, existing rights assigned to that
member are overridden. Access to other members is not affected unless you specify the
parameter (SL_CLEARALL) that clears all existing access assignments. You can use
this parameter alone to clear all existing access assignments, or you can use it with other
ImportSecurity parameters to replace all existing access assignments with the import file
assignments.
For example, Joe currently has Write access to OLAP Sales. The import file contains the
following line:
Joe,eBusiness,write
After importing, Joe has Write access to both OLAP and eBusiness Sales.

Creating the Secfile.txt File

Use a text editor to create the Secfile.txt file with the
following syntax:
<User or Group Name>,<Member Name>,<Access Right>,<Inheritance
Option>
Creating the Secfile.txt File

When creating the import security text file, consider the following points:
• The name of the text file must be Secfile.txt, and the file must be saved in the
C:\Hyperion\products\Planning\bin folder.
• All users, user groups, and members must be defined in the application.
• When importing access permissions, only existing access assignments for imported
members, data forms, and task lists are overwritten. All other existing access
permissions remain intact.
• Before importing security for a user-defined custom dimension, you must enable the
Apply Security option. You do that on the Property tab.
• When importing access rights for many users, you can improve performance by
making sure that users’ full names are not used in Planning preferences.

• Items within lines must be separated by one of the following delimiters:

- Comma ( , )—the default
- Tab

- Semi-colon ( ; )
- Pipe ( | )
- Colon ( : )
- Space
• Items within lines cannot have any extra spaces between them.
• The import file cannot contain any blank lines.
• Each line must contain the items described in the following table:
Item Description
User name or group The name of a user or user group that is provisioned for
the Planning application
Member name A member (Account, Entity, user-defined custom
dimension, Scenario, or Version) in the application
Access rights Read, Write, or None (None is ignored. If there are
duplicate lines for a combination of user name and
member name, the line with Write access takes
precedence.)
Inheritance options @CHILDREN, @ICHILDREN, @DESCENDANTS,
@IDESCENDANTS, and MEMBER.
For example, the Secfile.txt file might contain the following lines:
User1,Account1,read,@CHILDREN
User2,Entity2,write,@DESCENDANTS
User3,Version_1,write,MEMBER
Group1,Account101,write,@ICHILDREN
NOTE
If a member, user, or user group name contains a character that you are using as
the delimiter, enclose the name in double quotation marks. For example, if you are
using a space as the delimiter, enclose the name North America in double
quotation marks (“North America”).
• Inheritance options must be in all capital letters.

If you need to import security information into a group that has the same name as a user,
in the Secfile.txt file, append the sl_group parameter to the line that pertains to the
group.
For example:

admin,member1,read,MEMBER
admin,member1,read,MEMBER,sl_group
The first line imports security for a user named admin. The second line imports security
for a group named admin. If you omit sl_group, security information is imported only for
the user named admin.

Importing Access Rights

• Run the ImportSecurity utility from the command prompt.
• The file is located in the
C:\Hyperion\products\Planning\bin folder.
Syntax: ImportSecurity.cmd
“appname,username,password,[delimiter],
[run_silent], [SL_CLEARALL]”
Example: ImportSecurity.cmd “HYPlan,trnadmin,hyperion”
Importing Access Rights
To import access rights

1. From the Windows task bar, select Start > All Programs > Accessories > Command Prompt.
2. Navigate to the C:\Hyperion\products\Planning\bin folder.

3. At the command prompt, type the following command and required parameters,
separating the parameters with commas:
ImportSecurity.cmd appl,admin,password, SL_TAB,1
Parameter Description

delimiter Optional: SL_TAB, SL_COMMA, SL_PIPE, SL_SPACE,
SL_COLON, SL_SEMI-COLON
If no delimiter is specified, the comma default is assumed
to be the delimiter.
run_silent Optional: Whether to execute the utility silently or with
progress messages:
0 = Execute with messages
1 = Execute silently, with no messages
If this parameter is not included in the command line, the
value is assumed to be 0, to display progress messages
during execution.
[SL_CLEARALL] Optional: Whether to clear all existing access
assignments when importing the new access
assignments
This option must be in uppercase.
4. In the bin folder, view the importsecurity.log file to verify the results.
The new security information is now accessible from the

Dimensions task on the Administration menu in Planning.
5. Optional: To see the new security information reflected on the Enter Data page,
select the Security Filters option, and refresh the application databases.
You do not need to restart the application server.

Creating Security Filters

Create security filters to provide access to Planning data.
Create security filters

for all users.
Create security filters

for one or a few users.
Creating Security Filters

Data access rights for data forms, task lists, and process management are read from the
Planning relational database and take effect immediately. Essbase databases do not
need to be refreshed.
If you have a very large number of users who need security filter updates, you can use
the Manage Database task to update all filters at once. If you have one or just a few
users who need security filter updates, you can use the Manage Security Filters task. For
example, when you promote an employee, the employee’s access rights may change. In
that case, you need to update only one security filter rather than all security filters.
When you update security filters using the Manage Database task, you can select
Shared Members, Validate Limit, or both:

• Select Shared Members if you want to create security filters for shared members in
Essbase. Access rights for shared members and their base members may be
different. For example, user MSmith may not have access to the base entity London
for the regional process management hierarchy but may have Read access to the
shared entity London in the alternate corporate reporting hierarchy.

• Select Validate Limit if you want to identify any security filter that exceeds the
Essbase security filter limit of 64 KB per row. The names of users who exceed the
limit are displayed in a pop-up window.
NOTE
To validate security filters before updating Essbase, select only Validate Limit only.

Summary


• Import access rights


Student Guide Vol I

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Student Guide Vol I

Uploaded by

Copyright:

Available Formats

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Oracle® Hyperion Planning 11.1.1:

Volume I • Student Guide

Sandy Krameisen Disclaimer

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Module 1: Getting Started

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 2: Navigating Workspace

View Pane and Content Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Module 2: Creating Application Structures

Lesson 3: Creating Dimensions Overview

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 4: Managing Dimensions with Performance Management Architect

ii Planning: Create and Manage Applications

Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 5: Setting Up the Period, Year, Scenario, and Version Dimensions

Planning: Create and Manage Applications iii

Creating Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Lesson 6: Setting Up the Entity Dimension

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 7: Setting Up the Account Dimension

Lesson 8: Creating User-Defined Elements

iv Planning: Create and Manage Applications

Module 3: Loading Metadata

Lesson 9: Loading Metadata from a File

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 10: Creating Applications

Planning: Create and Manage Applications v

Lesson 11: Deploying Applications

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 12: Setting Up Exchange Rates

Module 4: Loading Data and Calculating the Database

Lesson 13: Loading and Calculating Data: Overview

vi Planning: Create and Manage Applications

Lesson 14: Loading Data

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Module 5: Setting Up Security

Lesson 15: Provisioning Users and Groups

Lesson 16: Setting Up Access Rights to Planning Applications

Planning: Create and Manage Applications vii

Reporting on Access Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 17: Creating Data Forms and Folders

Lesson 18: Customizing Data Forms

viii Planning: Create and Manage Applications

Specifying Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Module 7: Entering Data in Planning

Lesson 19: Entering Data

Planning: Create and Manage Applications ix

Adding Cell Text and Account Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 20: Entering Data in Smart View

x Planning: Create and Manage Applications

Module 8: Adding Business Rules

Lesson 21: Creating Business Rules

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 22: Managing Business Rules

Lesson 23: Adding Variables and Formulas to Business Rules

Planning: Create and Manage Applications xi

Adding Conditional Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-11

Oracle University and Capitani IT Solutions E Informatica Ltda use only

Lesson 24: Managing the Approval Process