Hyperion Planning 9.3.1 (Guide) 2

Hyperion Planning 9.3.
1:
Create and Manage Applications
Volume II Student Guide
D52599GC10
Edition 1.0
December 2007
D53079

Copyright 2007, Oracle. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and
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
not use, share, download, upload, copy, print, display, perform, reproduce, publish,
license, post, transmit, or distribute this document in whole or in part without the
express authorization of Oracle.
The information contained in this document is subject to change without notice. If you
find any problems in the document, please report them in writing to: Oracle University,
500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using
the documentation on behalf of the United States Government, the following notice is
applicable:
U.S. GOVERNMENT RIGHTS
The U.S. Governments rights to use, modify, reproduce, release, perform, display, or
disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
names may be trademarks of their respective owners.
Author
Sandy Krameisen
Technical Contributors
and Reviewers
Bryan Dehmler-Buckley
Suzanne Gill
Vicki Hardiman
Art Hetherington
Lea Jensen
Sandy Krameisen
Ronald Reiley
Eleanor Salerno
Theresa Songco
Shankar Viswanathan
Stuart Weiner
Editor
Susan Moxley
Graphic Designer
Carisa Cannan
Publisher
Judy Gaitan

Table of Contents 1
Preface
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Course Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Course Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Student Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Activity Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Module 1: Getting Started
Lesson 1: Planning Overview
Oracles Enterprise Performance Management System . . . . . . . . . . . . . . . . . . . . . . . 1-2
Oracle Business Intelligence Suite Enterprise Edition Plus. . . . . . . . . . . . . . . . . . . . . 1-4
Hyperion Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Additional Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Planning Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Client Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Application Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Database Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
EPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Planning Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Planning and Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Planning Repository and Essbase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Dimension Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Dimensions and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Multidimensional View of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Drill-Down Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Essbase TerminologyHierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Essbase TerminologyFamilies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Essbase TerminologyGenerations and Levels . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

Table of Contents
iv Planning: Create and Manage Applications
Lesson 2: Navigating Workspace
System 9 Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Workspace Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Launching Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Workspace User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Workspace Navigate Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Opening Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Navigating in Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11
Reviewing Available Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11
Basic and Advanced Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
View Pane and Content Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Opening Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Module 2: Creating Application Structures
Lesson 3: Creating Dimensions Overview
Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Planning Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Required Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Period and Year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Scenario and Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
HSP_Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Alias and Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
User-Defined Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Dense Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Sparse Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Data Block Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Determining the Number of Data Blocks in a Database . . . . . . . . . . . . . . . . . . . .3-11
Creating Data Blocks and Retrieving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Determining Data Structure and Performance of Data Blocks. . . . . . . . . . . . . . . 3-14
Selecting Aggregation, Storage, and Calculation Options . . . . . . . . . . . . . . . . . . . . . 3-15
Selecting Aggregation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Selecting Data Storage Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Calculating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Using Two-Pass Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Determining Performance Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Table of Contents
Planning: Create and Manage Applications v
Lesson 4: Managing Dimensions with EPM Architect
About Dimension Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Master View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Application View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
EPM Architect Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Adding Dimensions to Master View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Organizing Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Filtering Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Sorting Dimensions and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11
Creating Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Modifying Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Property Value Inheritance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Managing Property Value Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Creating Alternate Rollups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Managing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Moving Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Deleting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Renaming Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Reordering Children. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Inserting Members Using Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Finding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Creating Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Adding Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Number Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Triangulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Reporting Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Creating Associations Between Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Lesson 5: Setting Up the Period, Scenario, and Version Dimensions
Time Periods Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Period and Year Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Dynamic Time Series Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Setting Up Dynamic Time Series Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Choosing How Data Is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Scenario Dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Table of Contents
vi Planning: Create and Manage Applications
Creating Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Enable Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Exchange Rate Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Use Beginning Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Deleting Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Version Dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Creating Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Lesson 6: Setting Up the Entity Dimension
Entities Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Entity Members and Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Identifying the Currency Value for Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Adding and Modifying Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Saving Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Deleting Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
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 Rates 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
Viewing, Aggregating, and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Creating Attribute Crosstab Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Creating Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Examples of Attribute Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

Table of Contents
Planning: Create and Manage Applications vii
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-20
Associating Smart Lists with Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Setting Data Forms to Use Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Module 3: Loading Metadata
Lesson 9: Loading Metadata from a File
Metadata Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Formatting Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Load File Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Formatting Dimensions Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Formatting Members Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Formatting Hierarchies Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Formatting DimensionAssociation Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Loading Metadata Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Creating Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Mapping Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Mapping Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Running Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Viewing Job Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Viewing Import Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Loading Metadata from Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Interface Tables Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Setting Up Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Lesson 10: Creating Application Views
Creating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Dimension Library Panes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Adding Dimensions to Application Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Excluding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8

Table of Contents
viii Planning: Create and Manage Applications
Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Configuring Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11
Specifying Currency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Setting Up Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Removing Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Setting Up Dimension Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Choosing Performance Settings for Optimal Performance . . . . . . . . . . . . . . . . . . . 10-19
Dimension Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Lesson 11: Deploying Applications
Deploying Applications Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
Deployment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3
Validating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
Comparing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6
Deploying Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
Creating Essbase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10
Reviewing Planning Outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-11
Essbase Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-12
Redeploying Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-13
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

Table of Contents
Planning: Create and Manage Applications ix
Module 4: Loading Data and Calculating the Database
Lesson 13: Loading and Calculating Data Overview
Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Requirements for Data Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Multicurrency Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Setting Up Data Load Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Staging Data Using Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Data Calculation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Calculations Within Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
Calculations and Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
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
Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
Creating Interface Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Loading Data Using Interface Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
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

Table of Contents
x Planning: Create and Manage Applications
User and Group Provisioning Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
Unassigned Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-11
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
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
Creating Folder Structures for Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Data Form Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
Considerations for Setting up Data Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Setting Data Form Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Setting Row and Column Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Selecting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Creating Substitution and User Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Creating Asymmetric Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Setting Page and Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Setting Options on the Other Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Identifying Missing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Selecting Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Previewing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24

Table of Contents
Planning: Create and Manage Applications xi
Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
Creating Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
Selecting Business Rules on Composite Data Forms . . . . . . . . . . . . . . . . . . . . 17-27
Printing Data Form Definition Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28
Assigning Access Rights to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
Lesson 18: Customizing Data Forms
Exporting and Importing Data Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Creating Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Associating Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Advanced Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-11
System Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Custom Tools Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Current Application Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Managing User Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
Creating User Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-15
Applying User Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16
Setting Up User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Setting Up E-mail for Workflow Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
Applying Alias Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
Setting Member Selection and Workflow Options . . . . . . . . . . . . . . . . . . . . . . . 18-18
Setting Individual Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Setting Individual Printing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
Setting Individual User Variable Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
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 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Viewing Form Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Recognizing Cell Color Cues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Navigating Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Copying and Pasting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-11
Working with Non-Aggregated Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-13

Table of Contents
xii Planning: Create and Manage Applications
Saving and Refreshing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
Spreading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Time Balance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
Spreading Data Using Grid Spreader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19
Spreading Data Using Mass Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20
Adjusting and Annotating Plan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-22
Performing Ad Hoc Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-23
Exporting Data to Spreadsheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-24
Adding Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25
Adding Cell Text and Account Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Adding Planning Unit Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Adding Supporting Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28
Calculating Data in Data Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-30
Calculate Data Form Calculation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32
Calculate Currencies Calculation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-33
Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-34
Entering Data with Smart Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-35
Navigating Data Forms with Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-36
Lesson 20: Entering Data in Smart View
Smart View Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Integrating Smart View with Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Smart View Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Establishing Data Source Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Planning and Smart View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
Opening Data Forms in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Navigating Data Forms in Smart View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
Entering Data in Smart View Using Data Forms . . . . . . . . . . . . . . . . . . . . . . . . .20-11
Adding Formulas to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
Calculating Data in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
Offline Planning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
Taking Data Forms Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
Working with Planning Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-19
Synchronizing Data to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21

Table of Contents
Planning: Create and Manage Applications xiii
Module 8: Adding Business Rules
Lesson 21: Creating Business Rules
Business Rules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Business Rules Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4
Prerequisites for Accessing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Navigating Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
Components of Enterprise View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
Components of BR Language Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
Navigating the Rule Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
Business Rules Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Setting a Plan for Developing Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Launching the Rule Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-11
Adding Actions to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-14
Selecting Members for Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-17
Assigning Access to Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19
Launching Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-21
Launching Business Rules from Administration Services Console . . . . . . . . . . 21-22
Launching Business Rules from Planning Data Forms. . . . . . . . . . . . . . . . . . 21-23
Launching Business Rules from Planning Tools Menu. . . . . . . . . . . . . . . . . . 21-24
Printing Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-25
Lesson 22: Building Runtime Prompts for Business Rules
Runtime Prompts Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Adding Runtime Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Setting Up Runtime Prompts as Global Variables . . . . . . . . . . . . . . . . . . . . . . . . 22-5
Applying Runtime Prompts as Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
Setting Up Runtime Prompts as Local Variables . . . . . . . . . . . . . . . . . . . . . . . . . 22-9
Specifying Limits for Runtime Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
Lesson 23: Adding Formulas to Business Rules
Business Rules Formula Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Building Formulas for Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3
Components for Pro-Rata Ratio Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4
Setting Up Pro-Rata Ratio Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-5
Setting Up Units-Rates Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-8

Table of Contents
xiv Planning: Create and Manage Applications
Setting Up Variable Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9
Setting Up Custom Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-10
Specifying Data Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-11
Managing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-12
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-11
Checking the Status of Planning Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-13
Viewing the Details of Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-14
Printing Planning Unit Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-17
Copying Data Between Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-19
Copying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-21
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-16
Setting Up Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-17
Setting Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-19
Assigning Access to Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-21
Validating Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-22
Reporting on Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-23

Table of Contents
Planning: Create and Manage Applications xv
Module 10: Analyzing Planning Data with Financial Reporting
Lesson 26: Financial Reporting Overview
Financial Reporting Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2
Workforce Planning and XBRL Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-3
Financial Reporting Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5
Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7
Users, Groups, and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-8
Data Sources for Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-10
Financial Reporting Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-12
Working with Financial Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-13
Financial Reporting Studio Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-14
Viewing Repository Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-16
Opening Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-18
Report Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-19
Changing the User Point of View Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-20
Previewing and Printing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-21
Lesson 27: Navigating Reports in Workspace
Workspace Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-2
Workspace User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-4
Workspace Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-6
View Pane Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-7
Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-8
Setting General Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-8
Setting Authentication Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-9
Setting Explore Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-10
Setting Financial Reporting Studio Preferences . . . . . . . . . . . . . . . . . . . . . . . . .27-11
Setting Financial Reporting General Preferences . . . . . . . . . . . . . . . . . . . . . . . 27-12
Browsing the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-14
Searching for Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-16
Previewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-17
Changing the User Point of View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-19
Previewing the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-21
Limiting User Point of View Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-22
Changing Page Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-26
Printing Reports and Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-27

Table of Contents
xvi Planning: Create and Manage Applications
Integrating Reports into Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . . . 27-28
Exporting Reports to Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-29
Exporting Reports to Word and PowerPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-31
Importing Reports to Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . . 27-33
Module 11: Appendices
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
Appendix B: Working with Classic Application Administration
Classic Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Processes in Creating Planning Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Planning Application Creation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Planning Relational Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Configuring Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Creating Applications Using Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . B-10
Accessing Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11
Selecting the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12
Setting Up the Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
Setting Up Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
Setting Up Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16
Completing Application Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Creating Essbase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19
Reregistering Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20
Building Member Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21
Working with Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23
Creating Alias Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25

Table of Contents
Planning: Create and Manage Applications xvii
Smart Lists Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27
Smart List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-28
Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Associating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-31
Setting Up UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32
Setting Up Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-34
Data Integration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-35
Planning Adapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Working with Planning Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37
Creating Planning DSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38
Importing Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-39
Creating UDA Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-40
Loading Metadata to Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-42
Creating Planning Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-43
Configuring Session Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44

Table of Contents
xviii Planning: Create and Manage Applications

Preface 0
Welcome to Hyperion Planning 9.3.1: 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 and test business rules
Review budget data by using process management
Analyze planning results in Financial Reporting

Preface
xx Planning: Create and Manage Applications
Course Structure
Hyperion Planning 9.3.1: 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 classthe 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 11 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 analyzing data with Financial Reporting.
Module 11 contains appendices which provide additional information about Planning
not covered in this course.
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.

Preface
Planning: Create and Manage Applications xxi
Activity Guide
The activity guide has two sectionsexercises 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.
N OT E
A note provides related information, common mistakes, or
cautions about the current topic.
T I P
A tip provides information that helps you work more
efficiently.

Preface
xxii Planning: Create and Manage Applications

M O D U L E 8
Adding Business Rules 20
Overview
The aim of this module is to create business rules to perform calculations,
and verify their results. You also define runtime prompts, and add them to
business rules as well as add actions and formulas to business rules. You
can organize your business rules into projects to make locating and
maintaining your business rules easier.
Lessons in this module include:
Creating Business Rules
Building Runtime Prompts for Business Rules
Adding Formulas to Business Rules

L E S S O N 2 1
Creating Business Rules 21
Objectives
At the end of this lesson, you should be able to:
Describe Business Rules and its capabilities
Navigate Administration Console to design business rules
Create business rules
Launch business rules
Print business rules

Module 8 Adding Business Rules
Lesson 21 Creating Business Rules
21-2 Planning: Create and Manage Applications
Business Rules Overview
In traditional multidimensional applications, your organization typically requires more
complicated calculations to be performed than can be defined within your dimension
hierarchies or with member formulas. For these more complex calculations, you can
create business rules. Business rules are integrated with Planning and leverage the
power of Essbase calculation scripts to let you create complex, multistep calculations
that are not possible with member formulas.
For example, you can calculate aggregated totals and allocate totals based on head
count. Business rules can also target specific slices of the database. For example, you
could create a rule to copy values for Product Sales, North America 2007 to Product
Sales, North America 2008 and increment the values by 10%.
Administrators and interactive users use the Administration Console in Administration
Services to create, edit, validate, launch, and maintain business rules and sequences.
Sequences group multiple business rules to launch them in a particular order at one
time.
Business Rules Overview
Business Rules enable you to:
Leverage the power of Administration Services to create complex
calculations
Build sophisticated business rules including those which:
Allocate costs among entities
Model Revenue
Model Expenses for:
Employee planning
Depreciation planning
Selling costs
Manufacturing costs
Choose graphical components to build rules
Store rules in a central repository where you can organize them into
projects

Planning: Create and Manage Applications 21-3
The graphical depiction of components, formulas, and processes makes it easy to
construct business rules for your planning application. You can work with macros,
variables, and predefined formulas as you set up business rules. As a business rule
designer, you can save time by using macros to reuse pieces of business rules in other
business rules or macros. You can use variables both when setting up a business rule
and when running a business rule. Several formulas are available and can save time in
the design of business rules.
Business rules are easy to use. Launching business rules can be done by business
users from several different places, including from within Analytic Administration
Services, the Business Rules Web Launcher, the Business Rules Command Line
Launcher, and Planning. Business rules with runtime prompts ensure valid inputs from
budget preparers. By enabling the entry of runtime prompts during launching, Business
Rules makes a single, centrally created business rule reusable by several users.
Business rules are stored in a central location, making them easier to maintain. Business
rules can be created, organized, and stored into projects, making locating and updating
business rules easier.

Business Rules Roles
You set up users and groups, and assign roles to them, in Shared Services User
Management Console.
After creating a business rule, you become the owner of the business rule, which writes
your user name in the Owner attribute field. As the owner of the rule, you can edit and
delete the business rule. The administrator must assign launch privileges to the rule for
the particular database location so that users can launch the rule.
Business Rules Roles
Roles

Business Rules roles include Administrator, Interactive User, and Basic User. The
following table summarizes Business Rules roles and typical tasks performed:
Prerequisites for Accessing Business Rules
You log on to Administration Console, a component of Administration Services, to create,
edit, validate, launch, and organize business rules. You need to ensure that Shared
Services, the Administration Services Server, the Essbase Server, and the Planning
application server are all running before you launch Administration Console.
You log on to Administration Console and use variables, macros, commands, functions,
formulas, and actions to create a new business rule. You can launch business rules
directly from within Administration Console to execute your complex calculations. In
addition, you can launch rules from Planning.
Role Tasks That Can Be Performed
Administrator A user or group who has the role of Administrator can do any of the
following tasks:
Create, launch, edit, validate, and manage business rules, sequences,
macros, variables, and projects
Assign access privileges to business rules, sequences, macros, variables,
and projects
Provision users, groups, and roles
Set up the repository and log file
Interactive
User
A user or group who has the role of Interactive User can do any of the
following tasks:
Create, launch, edit, validate, and manage business rules, sequences,
macros, variables, and projects
Assign access privileges (with the exception of the ability to launch
business rules, which can only be assigned by an administrator) to
business rules, sequences, macros, variables, and projects
Basic User A user or group who has the role of Basic User can do any of the following
tasks:
Launch business rules and sequences to which the user has access
View business rules and sequences to which the user has access
View all variables and macros

Navigating Business Rules
You navigate Administration Console to build business rules. The type of information you
see on the screen depends on the selected tab.
Components of Enterprise View Tab
After logging on to Administration Console, you can expand the nodes under the
Business Rules node to view its contents. Business Rules nodes include:
My Projects
Repository View
Administration
Navigating Business Rules
Organizes business rules, sequences, macros,
and variables into logical groupings of information.
Lists all objects in the Business Rules repository including
business rules, sequences, macros, and variables.
Lists the properties of the client and server.
Access and work with Business Rules nodes.
Create and edit graphical business rules.
View the dat abase outline.
Lists all projects you use to organize your calculat ions.

Components of BR Language Tab
You edit or create rules by building a series of actions, formulas, variables, and custom
pieces, and setting up those components. The BR Language tab lists predefined actions
and formulas used to build business rules. You can access the actions and formulas
either on the BR Language tab or by right-clicking in the Rule Editor.
Components of BR Language Tab
Actions
Formulas

Navigating the Rule Editor
Select the BR Language tab to edit an existing rule or to create a new rule. The BR
Language tab consists of the navigation frame and the Rule Editor. From the navigation
frame, you select actions and formulas to include in your business rule. You use the Rule
Editor to associate an Essbase or Planning outline with your business rule and to set up
the details for your business rule.
Navigating the Rule Editor
Navigation
Frame
Select Act ions
and Formulas
Select
Outline
Build Rule
Select
Members

Business Rules Creation Process
Before creating business rules, you need to have an understanding of the calculations
that you want to set up. After you determine the requirements for your calculations, you
use the navigation frame to access the business rules repository.
Setting a Plan for Developing Business Rules
In order to plan for creating business rules, you need to consider the following:
Familiarize yourself with the database dimensionality and outline structure
Know where data is stored in the database, how data is stored and aggregated, and
at what level the data gets loaded into the database
Verify the order in which calculations will take place and the sequence of business
rules
Verify any key assumptions used to drive calculations
Business Rules Creation Process
Ensure that you do the following:
Do not include upper level members
that you do not really need.
Calculate portions of the database on
which your calculation is dependent.
Make your last step to aggregate data
affected by the rule.
25% 50 South
15% 30 Central
10% 20 West
50% 100 East
200 N. America
% of Sales Sales

In preparation for building business rules, ensure that you do the following:
Do not include upper-level members that you do not really need. For example, if you
include Q1 to be calculated by your formula, the values calculated by the business
rule are overwritten when the data is aggregated.
Calculate portions of the database on which your calculation is dependent. For
example, to calculate sales for each child of North America as a percentage of total
sales, you must first aggregate data to determine the value for sales for North
America.
Make your last step to aggregate data affected by the rule. Since the business rule
changes the value of level 0 members, the upper-level members need to be
calculated to reflect the latest data values.

Launching the Rule Editor
To create a business rule, you launch the Rule Editor from the Enterprise View tab in the
navigation frame. After expanding the Business Rules and Repository View nodes, you
can right-click the Rules node to create a new rule.
You navigate the tabs on the Rule Editor to build business rules. If you are creating a
new rule, you are initially placed on the Graphical tab. Associate a database outline to
refer to as you create the business rule. Next, specify global properties, including how
formula components are calculated and what dimensions are common to all the formula
components (also known as the global rule range).
N OT E
You must select a Planning outline if you want to set up your business rule to work
with Smart Lists.
\
Launching the Rule Editor
Creat e a new rule Select an outline
5
3
2
1
4

On the Overview tab, select a choice for intelligent calculation.
After setting global properties, you can set a range for each dimension by using the
Range tab. You can either type a value in the Selected Values text box or click the
magnifying glass icon to select members and variables.
To continue building graphical business rules:
1. Add actions and formulas to the Graphical tab by doing one of the following:
Select the BR Language tab and drag actions and formulas onto the Graphical tab
Right-click anywhere inside the Graphical tab to insert actions and formulas onto
the Graphical tab
2. Set up the details for each action and formula, including selecting members for each
component to set up calculations in both the source and the destination.
3. Optional: Set up local variables on the Local Variables tab.
4. Write a summary of what this business rule is used for on the Doc tab.
5. Type the name, description, and owner for the business rule on the Properties tab.
6. On the Location tab, select the location for which the calculation can be run.
You can select a specific database outline or select all locations to enable users to
run the business rule against any database.
7. As the administrator, you can grant or remove access to a business rule on the
Access Privileges tab.
If you are the owner, or you have been granted Modify access to the business rule,
you can grant or remove editing privileges for the business rule.
8. To save the business rule, click Save.
N OT E
Intelligent calculation calculates only the data blocks that need to be calculated,
making the calculation more efficient. Keep the default setting (Off) if you want to
calculate all data blocks.
N OT E
You must save the business rule before you can validate or launch that rule.

9. Click Validate to validate the rule.
10. Optional: Launch the business rule.

Adding Actions to Business Rules
While building your graphical business rule, you can choose to include the actions
Aggregate Data, Copy Data, Clear Data, and Create Blocks to your rule. All of these
actions can be added by selecting the BR Language tab and either double-clicking or
dragging the action onto the Graphical tab. You can also select to add an action to
business rules by right-clicking in the Rule Editor window.
Adding the Aggregate Data Action
There are several choices to set up the Aggregate Data action. On the Overview tab, you
choose a calculation option and method.
Adding Actions to Business Rules
Aggregate Data
Action
Calculation
Options and
Methods
Value type of User
defined can be
specified through
Member Selection
Member
Select ion
button

Calculation options include Calculate Entire Database, Calculate Entire Database with
Two Pass Calculation, and Calculate Portion of Database Specified Below, the default
selection. To calculate a portion of the database, you specify the section you want to
calculate by selecting a value type. If you selected User Defined for the value type, then
you select members to be included in the calculation.
Calculation methods include Aggregate Missing Values in the Database, Aggregate Data
Up to Local Currency, Optimize the Calculation of Formulas on Sparse Dimensions, and
Use Calculator Cache.
After you make your selections on the Overview tab, you can optionally use the Range
tab to restrict the aggregation to a range of members and variables in one or more
dimensions.
Adding the Copy Data Action
You use the Copy Data action to copy data from one part of the database to another in
the same database. Furthermore, you can perform mathematical operations on the
copied data. For example, to create your budget for the current year, you can start with a
copy of last years actuals and increase those values by a percentage to determine your
starting point for your budget.
To finish building the business rule:
1. On the Overview tab, enter a name in the Name text box. (The default name is
Destination.)
2. If blocks do not exist and you want to create them as part of the copy business rule,
select Create Blocks During Copy.
3. Select values in the Selected Values text box for the target values or destination.
4. Select values in the Selected Values text box for the source.
N OT E
If you do not choose to create blocks within the Copy Data action, and data blocks
do not exist in the destination but they do exist in the source, no data will be
copied for those members.
I
N OT E
If the source and destination are always the same, you can make the selection for
the destination, and the source is automatically inherited from the destination.

5. To apply a calculation, select Apply Calculation.
An operator and number component are added to the formula.
6. Select an operator: addition (+), subtraction (-), multiplication (x), or division (/).
7. Select the calculation to apply.
You can type a specific number, select a variable, or select values for each available
dimension.
8. Click Save.
Adding the Clear Data Action
You may want to clear data in a destination before applying an action or formula. You use
the Clear Data action to clear data from a specific portion of the database. You can
choose to clear individual cells or an entire block. Clearing data sets the data value to
#MISSING.
Adding the Create Blocks Action
You may want to ensure that blocks exist for sparse member combinations in a specified
slice of data. Remember that in order to store the result of business rule calculations, a
block must first exist before executing the calculation.
You can use the Create Blocks action to add blocks to the database. Before adding the
Create Blocks action, give some careful thought to whether it is really a necessary step
and for which portions of the database it is necessary. There is a potential for a large
increase in the database size. To assist you in your analysis, you can view a calculation
of the block size and maximum possible blocks that would exist for the specified data
slice after the calculation is run.
N OT E
You cannot use Create Blocks with Dynamic Calc or Label Only members.

Selecting Members for Business Rules
To set up business rules, you can use member selection to select members used in
global ranges, action, and formula components. You can select members for business
rules using the Multiple Select dialog box. On the Member tab, you can expand the
dimension outline and select members to include. You use the drop-down list below the
arrows to select members based on their relationship to a member. Next, you use the
right or left arrow to move the selection to or remove it from the Selected box. You use
the down or up arrow to move the selection to or remove it from the Excluded box.
In the example shown on the slide, you select Entity as your dimension and you want to
include all the descendants of North America except for those in the Central region. In
the Selected text box, you select to include the descendants of North America, while in
the Excluded text box you select to exclude the descendants, inclusive of Central.
Selecting Members for Business Rules
All descendants of
North America are
included with the
exception of
Central and its
descendants
2 5
7
4
1
3
6

To select some members and exclude other members:
1. Select the member to include.
2. From the drop-down list, select the relationship.
3. Click the right arrow.
The selection is moved to the Selected box.
4. Select the member to exclude.
5. From the drop-down list, select the relationship.
6. Click the down arrow.
The selection is moved to the Excluded box.
7. Click OK.
The Rule Editor window is displayed with your selection.

Assigning Access to Business Rules
You use the Access Privileges tab to grant or remove access to business rules. Access
privileges determine which users and groups can validate, launch, or modify business
rules and are assigned using the Privilege drop-down list. You can also specify whether
users can run the business rule against a specific database or against all databases
during validation and launch. You select valid locations from the Location drop-down list.
Assigning Access to Business Rules
To assign access to a user or
group:
1. Select the Access Privileges
tab.
2. Click Add.
3. From the drop-down list, select
a privilege.
4. From the drop-down list, select
a location.
5. Select the user or group.
6. Use the arrows to move users
and groups into the Selected
box.
7. Click OK.
8. Click Save.
2 1
5
3
6
7
8
4

Access privileges must be added one at a time. If you want to grant two different
privileges, such as Validate or launch and Modify rule repository objects to the same
user or group, you need to do this in two separate actions. However, you can grant the
same access to more than one user or group at the same time by using the Shift or Ctrl
key to select multiple users or groups.
N OT E
Before you assign access privileges to users or groups, you need to provision
those users or groups in Shared Services User Management Console.

Launching Business Rules
After business rules are created and validated, they can be run in either Essbase or
Planning. Business rules creators can launch business rules using Administration
Services Console in order to test the rules.
Launching Business Rules
You can launch business rules from:
Administration Services Console
Planning
Administration
Services
Console
Planning

Launching Business Rules from Administration Services Console
You can launch and test the business rules that you create in Administration Services
Console.
To launch a business rule in Administration Services, select the business rule from the
list of business rules under the Rules node, right-click the rule and select Launch. Enter
required runtime prompts, and click Launch.
Launching Business Rules from
Administration Services Console
2
4
1
3

Launching Business Rules from Planning Data Forms
After you create business rules, users can launch rules to which they have access.
Launching business rules can be done from Planning. The capability to launch rules
within Planning is convenient for planners who are already doing other work such as data
entry.
Data form designers can associate business rules with data forms. If a business rule is
associated with a data form, business users can launch the rule from within the data
form. To launch a business rule, select a rule and click Launch.
Business users can also launch business rules in Planning with context-sensitive menus.
To launch a business rule with a menu, select a data cell and right click to launch the
calculation.
The business rule may prompt you to enter information, called a runtime prompt. After
you successfully launch a business rule, the data is updated in the Essbase database. If
you are working on a data form when you launch the business rule, you can refresh the
data form to view the updated or new data.
Launching Business Rules from Planning
Data Forms
If a rule is associated with a data form,
do one of the following:
From t he view pane, click the rule,
and then follow the steps for launching
a rule from the Edit menu
From t he Edit menu,
select Launch Rules
1. Select a Rule
2. Click Launch
3. Click Close
To launch the rule from the Edit menu:
To launch the rule from the view pane:
2
1
3

Launching Business Rules from Planning Tools Menu
You can also run business rules which are not associated with the data form. After you
select Tools > Business Rules, the list of business rules for which you have access is
displayed. You can select a business rule and launch it. Refresh the data form after the
business rule calculation runs to display the updated results.
If a rule is not associated with a data form, then:
1. From the Tools menu, select Business Rules
2. Select a Plan Type
3. Select a Rule
4. Click Launch
Launching Business Rules from Planning
Tools Menu
3
2
4
1

Printing Business Rules
To document the contents of business rules, you can print the information contained in
business rules from the Administration Console of Administration Services. You can use
the Print Preview option to view the contents of the report on your screen. To print a
business rule, first open the rule in the Rule Editor. Then, from the File menu, you can
select to preview or print the report.
Printing Business Rules
Header
Business Rule
Properties
Business Rule
Documentation

Summary
In this lesson, you should have learned to:
Describe Business Rules and its capabilities
Navigate Administration Console to design business rules
Create business rules
Launch business rules
Print business rules

L E S S O N 2 2
Building Runtime Prompts for Business
Rules 22
Objectives
Describe runtime prompts
Create runtime prompts

Lesson 22 Building Runtime Prompts for Business Rules
Runtime Prompts Overview
You can set up business rules to include variables. Variables assume defined values. If
you set up a variable to be a runtime prompt type, then business users are prompted at
runtime to supply a single member, multiple members, a string, a number, or a
dimension. The value is then used to calculate the business rule. For example, if you
have a variable named CurrMonth, and the value May is supplied at runtime, then May is
substituted for CurrMonth.
Runtime Prompts Overview
In setting up business rules you can:
Enter variables that are resolved when a user launches a rule
Include default values to be used in runtime prompt
Set up limitations so that values are within a range you define

You can include default values in runtime prompts. You can set up default values when
you create a business rule so that no matter where the business rule is run, a default
value that you specify is used for the calculation. You also can set whether the default
members on the runtime prompt window match the members selected in the page and
POV axes.
To ensure that the user input is acceptable, you can set up limitations for the runtime
prompt so that users supply a value within a defined range.
N OT E
To set the default members for a business rule using runtime prompts to the page
and POV axes on a data form, you navigate to the Business Rules tab when
creating that data form. You then select to set the properties for that business rule,
indicating that the defaults are taken from the page and POV axes.

Adding Runtime Prompts
Runtime prompts are set up as either global or local variables within business rules. For
a variable to be a runtime prompt, the usage type Run-time prompt must be selected.
After you create global variables, users can select to add those variables to individual
business rules. Local variables are valid only for the business rule for which they were
created.
N OT E
In order to prompt users to select dimension members, you must associate an
outline and select a dimension as part of the setup for the variable.
Adding Runtime Prompts
Runtime Prompts as Global variables Runtime Prompts as Local Variables

Setting Up Runtime Prompts as Global Variables
You create global variables to be used as runtime prompts from the Enterprise View in
the Global Variable section. You create or edit global variables by expanding the
Business Rules and Repository View nodes and right-clicking Global Variables.
To set up global variables:
1. From the Associated Outline drop-down list, select an outline.
2. On the Variable tab, type a name and a description.
3. From the Type drop-down list, select a type:
Member or Members: Either a specific member or a range of members from the
dimension you select
Dimension: A dimension to be used for member selection
Setting Up Runtime Prompts as Global Variables

String, Integer, Real, or Percent: A text string, an integer, (the default selection),
a real number, or a percentage
StringAsNumber: A text string (Available only if you selected a Planning outline.)
DateAsNumber: A date (Available only if you selected a Planning outline.)
4. Optional: Select the Smart List check box and enter the name of the Smart List in
the Smart List text box.
5. If you selected Member or Members in the Type text box, select the dimension from
which you want users to select a member or members.
6. Optional: In the Limits text box, perform one of the following actions:
If you specified Member or Members in the Type drop-down list, either type the
names of the members in the Limits text box, or use the lookup button to search for
a range of members against which users can validate the variable.
If you specified Real, Integer, or Percent, type minimum and maximum values in
the Limits text box.
If you specified a Smart List, either enter the limits for the Smart List, or use the
lookup button to select limits.
7. Optional: Select Allow #Missing to enable business users to specify #Missing or
blank as the default value for the variable.
8. If you want to provide a default value, type or select a value in the Value text box.
T I P
You can search for a Smart List name by clicking the lookup button.
N OT E
If you selected Dimension or String for the type, the Limits text box and lookup
button are disabled.
N OT E
The Allow #Missing option is available only when the type is numeric.
N OT E
If you selected Smart List, you must enter a default value for the Smart List.

9. In the Usage Type drop-down list, select Run-time prompt.
10. In the Prompt String text box, type the text of the prompt to be displayed when the
business rule is launched.
11. Optional: Select Do not save value entered during validation and launch as the default value.
Each time the runtime prompt is executed, the default value from
the Default Value text box is used rather than the last value that
the business user entered.
12. On the Properties tab, type the name of the variable owner, and specify whether the
variable should be locked to prevent users from opening it for editing.
13. On the Access Privileges tab, grant or delete access to the variable.
14. Click Save.
N OT E
You can include unlimited text as the runtime prompt text; however, the
runtime prompt text that is displayed is truncated. The display limits vary
depending on the application that displays the runtime prompt.
N OT E
If you are the owner, or have been granted Modify access to the variable, you can
grant users editing privileges for the variable.

Applying Runtime Prompts as Global Variables
If you use global variables for runtime prompts, you can assign variables to your
business rules as you make your dimension selections.
For example, if you want to prompt a user to enter a North American entity, you first set
up a global variable that defines the acceptable entities. The global variable is called
NAmericanEntity. Next, in the business rule editor, you navigate to member selection for
the Entity dimension, and then navigate to the Global Variables tab. Finally, you select
the global variable that you want to use and use the arrows to move the variable to the
Selected box. After you complete your selection, the Entity dimension lists the global
variable in the Selected Values text box.
Applying Runtime Prompts as Global Variables
1
5
2
3
4

Setting Up Runtime Prompts as Local Variables
Local variables work in the same way as global variables, except that local variables
affect only the business rule for which you create them. You can add, modify, or delete a
local variable on the Local Variables tab of the rule for which it is created. Local variables
assume the access privileges of the rule with which they are associated. If you create or
modify a local variable, that variable is added, modified, or deleted when the business
rule is saved.
To create or edit a local variable, you open the rule for which the local variable applies,
and then navigate to the Local Variables tab. You use the Add, Edit, and Delete buttons
to create, modify, and delete local variables. You follow the same steps to set up local
variables as runtime prompts as you did to set up global variables as runtime prompts.
However, because local variables are part of business rules, you use the Apply button to
associate the runtime prompt with the business rule, and then save the business rule.
Setting Up Runtime Prompts as Local Variables

Specifying Limits for Runtime Prompts
In addition to setting up the type of input you want users to provide, you can focus user
input, narrowing the scope to acceptable values. For example, in your runtime prompt
string, you prompt users to enter a value between 1 and 10. You select an integer for the
type of input, but you want to ensure that the value entered is within your acceptable
range. Therefore, you set limits by indicating both minimum (1) and maximum (10)
values in the Limits text box.
You can also assign limits for member selection. For example, in your runtime prompt
string, you prompt users to select a North American entity. You select Member or
Members for the type of input. To ensure that the entity or entities selected is within your
acceptable range, you either enter the names of the members in the Limits text box or
use the lookup button to select a range of members against which users can validate the
variable.
Specifying Limits for Runtime Prompts

Summary
Describe runtime prompts
Create runtime prompts


L E S S O N 2 3
Adding Formulas to Business Rules 23
Objectives
Identify the four formulas included with Business Rules
Add formulas to business rules
Manage business rules

Lesson 23 Adding Formulas to Business Rules
Business Rules Formula Overview
You can set up formulas to calculate data. You can choose from four formulas to insert
into your business rules: Pro Ratio, Units-Rates, Variable, and Custom.
Each formula has a Formula tab, a Formula Range tab, and a Data Condition tab.
Typically, you first specify the destination and sources for the calculation. Next, you
specify the formula range. Finally, you specify data conditions under which the formula is
calculated.
Business Rules Formula Overview
Specify certain criteria that
must be met before the
business rule calculates
data.
Enter destination and
source details for each
part of a formula.
Narrowly define the
business rule range by
setting up the range of
members, functions, or
runtime prompts.
Add additional sources,
calculation functions,
numeric operands,
operators

Building Formulas for Business Rules
Formulas can be added by selecting the BR Language tab and dragging the formula to a
location in the business rule on the Graphical tab. You can also select to add formulas to
business rules by right-clicking in the Rules Editor window. After you select a formula,
you set up the components of the formula.
Building Formulas for Business Rules
2
1
Units-Rates formula is
added to Graphical tab
5
4 3
6 7

Components for Pro-Rata Ratio Formulas
Pro-Rata Ratio formulas calculate data based on the results of a ratio of values. You can
use the Pro-Rata Ratio formula for profitability analysis, or for budgeting and planning
purposes to allocate expenses to various cost centers based on an inferred level of
usage. For example, consider that you have advertising expenses of $100,000 that you
want to allocate to various departments. You decide to use headcount as the criterion to
allocate the appropriate portion of the expense to each department.
Several components make up this allocation calculation. First, you determine the total
advertising expenses. Next, you calculate the total headcount for your organization and
the headcount for each department. To obtain the total headcount, you use the
Aggregate Data action to calculate the headcount account. You use total headcount for
the denominator in the first part of your pro-rata ratio calculation. You use the headcount
for each department as the numerator. Finally, you multiply the ratio of headcount per
department divided by total headcount by the total advertising expense to calculate the
allocated expense per department based on headcount.
Components for Pro-Rata Ratio Formulas
Advertising Expense
Allocation proportionally
based on headcount
$100,000
Advertising
Expenses
Department 1
$50,000
Department 2
$30,000
Department 1
$20,000
Total Headcount
for the company
is 1,000 people
Department 1 has
500 employees
Department 2 has
300 employees
Department 3 has
200 employees
(500/1000) * $100,000 =
(200/1000) * $100,000 =
(300/1000) * $100,000 =
Pro-Rata Business
Rule Calculation

Setting Up Pro-Rata Ratio Formulas
After you determine the components of the pro-rata ratio calculation, you can use the
Rule Editor to set up your calculation. You set up a destination, a source, and the pro-
rata ratio component.
You can choose from the following types of Pro-Rata Ratio formulas:
Formula Type Description
User Defined Calculates data based on the result of a ratio of defined values.
% to Total Calculates data based on the total value of a selected dimension. The total
value is stored in the generation 1 member or top member of the dimension.
The default calculation is Destination = Source X (% to Total).
Setting Up Pro-Rata Ratio Formulas
The destination is the portion of the
database where you plan to store the
results of your calculation.
In the source, you select the portion of
the database that you want to
reference to obtain data.
You set up the pro-rata ratio
component to reflect the type of
calculation you want to make.
Select
Numerator
Total
Advertising
Expense
Advertising
Expense
Allocation
=
x Select
Denominator
Pro-Rata Ratio Component Destination Source
.
.

Setting Up the Destination
The destination is the portion of the database where the result of the calculation is
stored. If you specify dimension values in the business rule range or the formula range,
those values are locked for the destination and are displayed in italics in the member
selection box. For example, you want to select an account and the departments for which
this calculation is executed. Specifically, for department, you can select the level 0
descendants of North America because department is represented in the Entity
dimension.
Setting Up the Source
The source is the portion of the database referenced in the calculation. You can set up
source values as members, expressions, or runtime prompts. You can change the
inherited values for a source by selecting a single member, a function, or a member
runtime prompt. You can customize the source values further. You can use the following
source types to set up source values:
% to Parent Calculates data based on the value of the members parent within a
specified dimension. You can select any generation or level of the
dimension to represent the parent. The default calculation is Destination =
Source X (% to Parent).
% to Member Calculates data based on the value of a specific member within a
dimension. You can select any dimension or member. The default
calculation is Destination = Source X (% to Member).
Source Type Description
Typical You select the dimension to be used in the calculation. Typical is the
default value.
Percent to Total You select the dimension to be used in the denominator of the
calculation.
Percent to Parent You select the dimension plus either the generation or the level to be
used in the denominator of the calculation.
Percent to Member You select the dimension and specific member to be used in the
denominator of the calculation.
Evenly Split by
Selected Members
This is a two-part selection. First, you select the dimension and specific
members to be used in the calculation. Second, you select to divide the
parent by the total number, by selected members, or by the number of
selected members with data.
Formula Type Description

To set up the destination or source:
1. Select Destination or Source to set up the destination or source.
2. To help document and maintain the business rule, in the Destination or Source, change
the default name to something that describes what the calculation does.
3. For each available dimension, perform an action:
Click the Member Selection button and use Multiple Member Selection to select
members and variables for the destination.
Type a value in the Selected Values text box.
Leave the value set to <All> to use all members for that dimension.
Setting Up the Pro-Rata Ratio Component
You set up the pro-rata ratio component to reflect the type of calculation that you want to
make. For example, if you choose to add the Percent to Member Pro-Rata Ratio formula
to your business rule, you need to set up how the percentage is determined. If you want
to calculate a ratio that determines how the number of people in each department
compares with all the people in a certain region within your organization, you can set up
your ratio to divide each departments headcount by the total headcount for a certain
region.
Evenly Split by
Children
This is a two-part selection. First, you select the dimension to be used
in the calculation. Second, you select to divide the total value by the
total number of children or by the number of children with data.
remote source
(XREF)
You select a remote source to reference data.
N OT E
Inherited values in member expressions are displayed in italics. The values are
inherited from the business rule range or the formula range. For destination
values, you can change or delete these values only in the business rule range or
formula range.
Source Type Description

Setting Up Units-Rates Formulas
Units-Rates formulas perform calculations based on designated unit, rate, and amount
values. The three types of Units-Rates formulas are:
Types of Units-Rates formulas:
Amount = Units x Rates, where the default calculation is Destination = Unit x Rate
Rates = Amount / Units, where the default calculation is Amount / Unit
Units = Amount / Rates, where the default calculation is Destination = Amount / Rate
After selecting a type of Units-Rates formula, you set up the dimension values for the
Amount, Units, and Rates components, and you can replace the default name with a
more descriptive name.
Setting Up Units-Rates Formulas

Setting Up Variable Formulas
Variable formulas store intermediary results of calculations in business rules. You can
define multiple variables within a business rule. However, a variable must be defined
before it can be used in another component, and it represents a single numeric value
that is either specified directly or derived from a calculation.
Setting Up Variable Formulas

Setting Up Custom Formulas
You can use custom formulas to build your own formulas. After adding a custom formula
to your business rule, you can set up the details starting with the default Destination =
Source. You can create any type of mathematical expression to suit your business
needs. You use the Custom Toolbar to add sources, functions, number, operands, or
parentheses to custom formulas.
Setting Up Custom Formulas

Specifying Data Conditions
You can specify that certain data conditions are met prior to executing a calculation. You
can indicate specific criteria on the Data Condition tab. You can specify data conditions in
a formula or in the Copy Data action. If the conditions or criteria you specify are met, the
formula or Copy Data action performs the calculation successfully. If the conditions are
not met, the calculation is not performed.
You can use the Custom Toolbar on the Data Conditions tab to build expressions to use
as the data conditions. You can use any of the following operators to define data
conditions: addition, subtraction, multiplication, division, less than, greater than, equal to,
less than or equal to, greater than or equal to, and Boolean AND, OR, and NOT.
D
N OT E
Data conditions are performed against data values only, not against user-defined
attributes or member names.
Specifying Data Conditions
Custom Toolbar
Available Operators

Managing Business Rules
Business rules are stored in a single repository. You can create projects to organize
business rules, sequences, macros, and variables into logical groupings within the
repository. For example, you might group business rules into projects to help identify and
manage which rules are used for each Essbase server, or you might group business
rules by type, such as grouping your rules by the type of formula used.
You can use descriptive names for your projects to make finding the business rules and
other objects that belong to them easier. In order to add a project, you select those
business rules, macros, variables, or sequences to include in the project. The members
that you select for the project are listed on the Contents tab. On the Project Info tab, you
enter a name, description, and owner for the project. You can also indicate whether to
lock the project from editing. Finally, you assign access to the project and define the
locations for this project for which users can validate or launch business rules and
sequences.
Managing Business Rules
1
2
7
5 6
4
3

Summary
Identify the four formulas included with Business Rules
Add formulas to business rules
Manage business rules


M O D U L E 9
Managing the Planning Process 23
Overview
The aim of this module is to manage the planning cycle through process
management. You also copy data between versions and use the Copy
Data task to seed the start of the next planning cycle. You create task lists
to guide budget preparers through the planning cycle.
Managing the Approval Process
Creating Task Lists

L E S S O N 2 4
Managing the Approval Process 24
Objectives
Explain the planning process
Define a planning unit
Manage the review cycle for a planning unit
Copy data between versions
Copy data

Module 9 Managing the Planning Process
Lesson 24 Managing the Approval Process
Process Management Overview
Planning process management enables you to track the progress of your budget, identify
problems in the review process, view status information, quickly identify ownership of
budget planning units, and change the budget status.
The Manage Process function is designed to reduce budget cycle time by enabling you
to perform the following key actions:
Approve a planning unit from any process state
Follow an approval path that is independent of organizational structure
Emphasize exceptions and problem areas
Provide audit information through annotations and process status
Annotate at each pass through the review process
Establish accountability through ownership
Process Management Overview
Use process management to promote, review, sign off, reject, and
approve planning units.
Review Sign Off Approve
Reject
Promote

Planning Units
Planning tracks budgets by planning units, which consist of a scenario, a version, and an
entity. Scenarios and versions are the basis of the planning review cycle. Entities provide
planning data for a particular scenario and version. When you access the process
management feature of Planning, you select a scenario and version for which you want
to view the status. You then see a list of the entities to which you have access. You can
track the status of each entity as it moves through the review cycle from first pass to
approval. After planning data is submitted and approved for all entities, the planning
cycle is complete for the scenario and version.
Scenario : Budget Version : Draft1 Entity : Calif ornia
+ +
Planning Units
Planning Unit =

Planning Units and Process States
Planning units pass through a number of process states during the review cycle. A
planning unit is always in one of six process states:
State Description
Not Started The initial state of all planning units. The budget administrator initiates the
review process by using the Start action.
First Pass The first state for planning units selected for the budget review process.
Planning units have no owner during First Pass. Any user with data access
can enter data into and promote a planning unit in the First Pass state.
Under Review The state of a promoted planning unit. This state signifies that a planning
unit is being reviewed by someone in the organization. Only the current
owner or the budget administrator can modify data or perform an action on
a planning unit that is in the Under Review state.
Planning Units and Process States
Each planning unit completes this process.
Sign Of f
First
Pass
Under
Review
Signed
Off
Under
Review
Start Promote Promote
Not
Signed Off
Reject Approve
Not
Started
Approved

Signed Off The state of a planning unit that was signed off. Only the current owner or
the budget administrator can modify data or perform an action on a
planning unit that is in the Signed Off state. Ownership does not change
when a planning unit is signed off.
Not Signed Off The state of a planning unit that was rejected. The current owner or the
budget administrator can modify data or perform an action on a planning
unit that is in a Not Signed Off state.
Approved The state of a planning unit that was approved. After a planning unit is
approved, a budget administrator becomes the owner of the planning unit.
Only the budget administrator can modify data or perform an action on a
planning unit that is in an Approved state. After all planning units are
approved, the budgeting cycle is complete.
State Description

Reviewer Actions
The action a reviewer performs on a planning unit changes the status of the planning
unit, as summarized in the graphic in the slide.
Administrator Approved Approve Under Review
New owner Not Signed Off Reject Under Review
Same owner Signed Off Sign Off Under Review
New owner Under Review Promote Under Review
First owner Under Review Promote First Pass
Everyone with rights First Pass Start Not Started
Current Owner End Status Reviewer Action Start Status
Reviewer Actions

The following table describes reviewer actions:
Start The Start action changes the state of the planning unit from Not Started to
First Pass. Any user with Write access to the planning unit data can modify
data during the First Pass state. Only budget administrators can start a
planning unit.
Exclude The Exclude action excludes a planning unit from the review process even
after the planning unit is started and moved through several iterations. When
you exclude a planning unit from the review process, all annotations and
history associated with the planning unit are discarded. The planning unit
status is returned to Not Started and the owner is set to No Owner. Only
budget administrators can exclude a planning unit.
Promote The Promote action submits the plan data to a reviewer for review. The user to
whom you submit the planning unit for review becomes the owner of the
planning unit. After you promote a planning unit, its status changes from First
Pass to Under Review. When a planning unit is under review, you can no
longer enter data for the planning unit unless you are the owner or the budget
administrator.
Sign Off The Sign Off action allows a reviewer to sign off a planning unit without
promoting it to another user for review. This action changes the status of the
planning unit from Under Review to Signed Off.This feature is useful when
you are reviewing several planning units, and you want to promote them as a
group for review.
Reject The Reject action returns the planning unit to its original owner or a new
owner for further adjustments prior to being approved. This action changes
the status of the planning unit to Not Signed Off.
Approve The Approve action indicates that the planning unit passed through all
required levels of review and that the planning cycle for the unit is complete.
When a planning unit is approved, its status changes from Under Review to
Approved, and the budget administrator becomes the owner. Only the budget
administrator can modify data for a planning unit after it is approved. Typically,
a planning unit is approved only once, but an administrator can reject a
previously approved planning unit if necessary.

Impact of Entity Hierarchy on the Review Process
The parent-child relationships between entities affect the movement of entities through
the review process. The following rules apply:
When you promote or reject a parent, its children are automatically promoted or
rejected, unless they are in the Approved state. The owner selected for a parent
becomes the owner of the children.
When you approve a parent, its children are automatically approved.
After all children of a parent are promoted, the parent is automatically promoted to
the same owner.
*
*
*
*
=
=
=
=
All childrens statuses
are automatically
updated to Under
Review, Not Signed
Off, Signed Off, or
Approvedthe same
as their parents.
The parents status is
automatically updated
to Under Review, Not
Signed Off, Signed
Off, or Approvedthe
same as its childrens.
Promote, Reject,
Sign Off , or Approve
All Children
Promote, Reject,
Sign Off , or Approve
Parent
Impact of Entity Hierarchy on the Review Process

After all children of a parent are signed off, the parents status automatically changes
to Signed Off.
N OT E
You cannot change the status of a parent if the children of the parent are owned
by different users. If the children of a parent are promoted to different users or
signed off by different users, the parent has no owner, and its status can be
changed only by the budget administrator.

Managing the Review Cycle for Planning Units
You manage the review cycle for planning units on the Check Status and Manage
Process page.
What is shown on the Check Status and Manage Process page depends on your user
type: administrator, interactive user, or planner. As an administrator, you see all planning
units in the current application organized in a hierarchical form. You can expand and
collapse parent members to view their children. You can start or exclude planning units,
view status and owner, view or add annotations, and view history, as well as perform any
reviewer actions under the Change Status option.
Interactive users and planners see the planning units to which they have read or write
access. They can only view status and owner, view or add annotations, and view history.
Interactive users and planners can promote a planning unit if it is in the First Pass state.
They cannot perform actions on planning units that are not in the First Pass state unless
they own the planning unit.
Managing the Review Cycle for Planning Units
File > Workflow > Manage Process
Start or exclude planning units
Change or view the status of planning units
Identify the ownership of or assign new ownership for planning units
Add and view any annotations associated with planning units
View the history of planning units

Starting or Excluding Planning Units
After a scenario and version are selected, the members of the Entity dimension become
available for processing. As the budget administrator, you can choose between tree view
(hierarchical) and flat view to display entities. The Check Status and Manage Process
page shows the plan cycle status, the process status, and the current owner of planning
units for the selected scenario and version.
The plan cycle status is visible only to budget administrators. The Start and Exclude
columns contain option buttons that enable you to either begin the review process or
remove an entity from the review process. Start and Exclude change the process state of
the affected planning unit. Selecting Start changes the state to First Pass, whereas
selecting Exclude reverts the state to Not Started.
Choose to start or exclude
the entit y for your planning unit .
Select
the scenario
and version
for your
planning
unit .
1
2
Starting or Excluding Planning Units

Starting the Planning Cycle
As the budget administrator, you begin the review process by selecting a planning unit
and starting it. You can choose to start all entities or a subset of entities for a scenario
and version. When the Entity list is hierarchical and you start a parent, all children of the
parent entity are also started.
Excluding Planning Units
As the budget administrator, you can exclude a planning unit from the review process
even after the planning unit is started and moved through several iterations. When you
exclude a planning unit from the review process, all annotations and history associated
with the planning unit are discarded. The planning unit status is returned to Not Started
and the owner is set to No Owner.

Checking the Status of Planning Units
The Process Status column reflects the stage of a planning unit as it moves through the
budget review process. Process states are changed when a review action is taken on a
planning unit.
Checking the Status of Planning Units
Select the
Details
link to view
the details of
a planning
unit.

Viewing the Details of Planning Units
You navigate to the Details page by clicking a Details link on the Check Status and
Manage Process page. From the Details page, you can complete the following tasks:
Check the status of a planning unit
Add or view annotations for a planning unit
Change the status of a planning unit
Viewing the Details of Planning Units
Select Change
Status to
perf orm a
reviewer action
on a planning
unit.

Changing the Status of Planning Units
You use the Change Status dialog box to select a reviewer action and the next reviewer
to move your planning unit to the next step in the process management cycle. You can
also add an annotation regarding the action you are taking for the next reviewer.
Actions
Actions are the operations available to change the status of a planning unit and direct its
movement through the budget review process. The options vary depending on the
current status of the planning unit.
Changing the Status of Planning Units
Select
a reviewer action
to perf orm on the
planning unit.
Select the next
reviewer / owner.
Enter an annotation
regarding your action.
1
2
3

The following table summarizes the actions available based on a planning units status:
Next Owner
Select the next reviewer in the process management cycle based on the action selected.
Only individuals with Read or Write access to the planning unit are available for
selection.
Annotate
Annotations associated with a planning unit provide guidelines to planners. You can also
add annotations to explain to budget reviewers the assumptions that you made in the
plan. You must have a minimum of Read access to the planning unit to view or add an
annotation.
Planning Unit Status Actions Available
First Pass Promote
Approve
Under Review Promote
Sign Off
Reject
Approve
Not Signed Off Promote
Sign Off
Reject
Approve
Signed Off Promote
Reject
Approve
Approved Reject (budget administrators)

Printing Planning Unit Annotations
As the budget administrator, you can check the current status of planning units by
creating a report on all planning unit annotations for a selected set of scenarios,
versions, and entities. You set the options for creating a PDF file that reports planning
unit annotations.
Some points to keep in mind when creating a planning unit annotation report:
The title, author, date, and annotation text of the planning unit are automatically
displayed.
Annotation text, not data that may be associated with the planning unit, is displayed.
Planning unit annotations are displayed chronologically, with the most recent entry
displayed first.
Printing Planning Unit Annotations
Select Administrat ion > Reporting >
Planning Unit Annotations

The report includes the following information about the planning unit:
Name of the application
Selected set of scenarios, versions, and entities
Planning unit title and status
Date of origin
Author
Content of the annotation
When you create the report, you can select the following report options:
ScenarioAll or Custom (select by name)
VersionAll or Custom (select by name)
EntityAll or Custom (select by name)
Process Status
- First Pass
- Under Review
- Approved
- Signed Off
- Not Signed Off

Copying Data Between Versions
You use the Copy Versions task in the Workflow section of the File menu to copy data
from one version of a scenario to another version within the same scenario. When you
copy data for a version, you can select the entity for which you want to copy data. When
you copy data to a target version, the parent-level entities are available to be copied.
When you copy data to a bottom-up version, level 0 entities are available.
For example, you can create a First Pass version and copy data for some or all of the
entities in that version to a Second Pass version. Thus, you quickly create a starting
point for the Second Pass version.
N OT E
When you copy a version, data for all years, accounts, and periods for the source
version are copied to the destination version. Be sure that you do not
inadvertently overwrite data for prior years.
Copying Data Between Versions
File > Workflow > Copy Versions

When you copy versions, you have the option to copy the account annotations, cell text,
and supporting detail for the planning units.
The Copy Versions task does not perform the following tasks:
Create an entry in the planning unit history
Copy or change planning unit status
Copy or change planning unit ownership
If you want to create a copy of your plan so that you can compare it to the approved
version, ask the budget administrator to set up a personal bottom-up version for you.
Before you promote your data, you can copy it (using Copy Versions) to your personal
version. This gives you a record of the data before you promote it.
You can use the copy versions option if you want to create:
A copy of the data for your own records. For example, you could use the copy as a
baseline to compare against future versions of data.
A starting point for subsequent bottom-up versions.
N OT E
Do not stop or load another Web page until the Copy Versions process is
complete. If you stop or load before the process is complete, you cannot verify
that the copy process has been completed successfully.

Copying Data
When you copy data from one version to another for the same scenario and entities, you
can select the option to include supporting detail. As a budget administrator, you can also
support the planning effort by using the Copy Data command to copy all relational data
and data values, including supporting detail, from one dimensional intersection to
another dimensional intersection.
For example, you can copy Budget, FY07, Final to Forecast, FY08, First Draft. You can
also copy data from FY07 to FY08 to help planners prepare a budget, or you can copy
data from one business unit to another.
Copying Data
Administration > Copy Data

Summary
Explain the planning process
Define a planning unit
Manage the review cycle for a planning unit
Copy data between versions
Copy data

L E S S O N 2 5
Creating Task Lists 25
Objectives
Define task list capabilities
Navigate task lists in Basic and Advanced modes
Create task lists
Assign access to task lists
Validate task lists
Report on task lists

Lesson 25 Creating Task Lists
Task Lists Overview
Task lists provide a powerful method of managing and guiding budget preparers through
a planning process by providing lists of specific activities to complete within and outside
Planning. Your organizations plan or forecast may require budget preparers to perform
multiple activities, some of which may be performed infrequently. Task lists provide
guidance in completing these activities.
Task lists guide budget preparers by taking them through a step-by-step wizard. Not only
are individual steps mapped out with instructions, but the sequence and due dates of
steps are identified as well.
As the budget administrator, you and interactive users can create task lists for a single
user or group of users. Examples of tasks include reviewing instructions, entering data in
appropriate data forms, running required business rules, using process management to
submit numbers for approval, and running reports to review information.
Task Lists Overview
Manage and guide users through the planning process
Navigate using a step-by-step wizard in Basic mode
Consist of one or more tasks
URL Task
Data Form
Business Rule
Workflow
Descriptive
Created by administrators or interactive users

Depending on how you set up tasks in the task list, you can view due dates, alerts, and
instructions.
If you set up due dates and alerts, you provide a visual cue for the budget preparers to
see their progress in completing tasks.
Due dateA task can display a due date that shows when it must be completed.
AlertsA task can e-mail an alert, a visual cue, about your progress in completing
tasks:
- GreenThe task is on schedule; the due date is not yet approaching.
- YellowThe task is approaching the due date.
- RedThe task is overdue; the due date has passed, but the task is not complete.
InstructionsA task can include instructions. You can click the View link to view the
instructions.
If you set up e-mail alerts, the budget preparers receive e-mail reminders that help them
keep track of their tasks. Depending on how the e-mail alerts are set up, e-mail
messages remind the budget preparers of tasks that are approaching their due date or
those that are past their due date. You also determine the timing and frequency of
messages. After budget preparers complete the requirements for a task, they can mark
the task as complete; the alert changes to a date stamp that shows the date and time of
completion.

Navigating Task Lists
If task lists are assigned to you, you can choose to work with the task list in Basic mode
or Advanced mode. Basic mode provides a wizard to guide you through the sequenced
steps in the task list. Advanced mode provides the flexibility of working with all Planning
functions to which you have access, along with the task lists to which you have access.
The way that you view task lists depends on the mode that you are working in and how
you want to work.
The way that you complete a task depends on the type of task on which you are working.
A data form task can require that you open a data form, add data, and then click Save. A
business rule task can require that you launch a business rule. A workflow task can
display a planning unit for you to promote. A descriptive task can display read-only
material, such as a reminder to send a fax. After completing the requirements for a task,
you can mark it as complete. If a task has dependent tasks, you must complete
dependent tasks before you can complete the primary task.
Navigating Task Lists
Basic mode:
Select View > Basic Mode.
Select task list from quick launch list.
Focus on your predefined tasks in a task list page.
Navigate between tasks using the task list wizard.
Advanced mode:
Select View > Advanced Mode.
Access other Planning features while you work with tasks.
View task lists assigned to you.
View the status of the tasks and any instructions included with the task.

Navigating Task Lists in Basic Mode
In Basic mode, a quick launch list is displayed at the top of the page. The list shows the
task lists that are assigned to you. From the quick launch list, you can select the task list
with which you want to work.
After you select the task list, the tasks contained in the list are displayed in the View
pane. In the content area, the status of the task list is displayed.
You can choose to view the tasks within the task list to review due dates and instructions,
or you can proceed to the first incomplete task in the task list.
Navigating Tasks Lists in Basic Mode
Select task list from View pane.
View tasks listed in View pane.
View tasks details or advance to next incomplete task.
View task
list details.
View tasks
listed in
View pane
Advance to next
incomplete task.

Navigating Task Lists in Basic Mode (Cont.)
You can choose to view the tasks in the task list while in Basic mode. This enables you to
review the status and due date of tasks and to view any instructions associated with a
task.
After reviewing the tasks, you can click the Incomplete link to return to the wizard and
proceed to the next incomplete task in the task list.
View due date
and status.
View
instructions.
Launch task list wizard / next
incomplete task.
View tasks in task list.
View due date and status.
View instructions.

After you select to proceed to the next incomplete task, that task is presented for you to
perform. The sequence in the task list and the type of task defined determines what is
presented to you.
When you have finished working with the task list, you can access other Planning
functionality by returning to Advanced mode (View > Advanced Mode).
Mark task as
completed.
Proceed
to next task.
Perform task.
Mark task as completed.
Navigate to next task or next incomplete task.

Navigating Task Lists in Advanced Mode
To access task lists in Advanced mode, you select View > Task Lists > Task List. The
Task List dialog box contains the following tabs:
Available Task ListsListing of tasks to which you have access. Select the task list to
work with.
Task ListView the tasks in the selected task list, due dates, task status, and
instructions.
StatusView the status of the task list.
You can view task instructions, launch tasks, view task status, or mark a task as
completed. While working in Advanced mode, you can perform all Planning tasks to
which you have access.
Task list(s) to which
you have access
Navigating Task Lists in Advanced Mode
View > Task Lists > Task List or Task List toolbar icon

Navigating Task Lists in Advanced Mode (Cont.)
On the Task List panel, you can view task instructions, launch tasks, view task status, or
mark a task as completed.
View tasks in task list and select task to perform.
View due date and status.
View instructions.
View
Instructions.
Select the task
to perform.
View due dates
and status.

You can view the overall status and progress of a task list by selecting the Status tab.
You can see what percentage of the task list is complete, how many tasks are still
incomplete, how many tasks are overdue or due soon, and the date the next task is due.
When you have finished working with task lists, close the Task List dialog box.
View the status of a task list.

Task List Creation Process
Before you create task lists, you can create folders for your task lists to organize them.
Then, you create the task lists, define the tasks that comprise the task list, set task
properties, assign access rights to the task lists, and, finally, test the task lists.
Task List Creation Process
1. In Advanced mode, select Administration > Manage Task Lists.
2. Create task list folders.
3. Create a task list.
4. Edit the task list to add specific tasks.
Add tasks to task list.
Define individual tasks further by adding instructions, due dates, and alerts.
Complete task creation by setting the properties for tasks.
Assign access to task lists.
Validate task lists.

Working with Task List Folders
You can create folders to organize and keep track of task lists that are used for different
purposes. Use the Task List Folders area on the left of the Task List page to set up task
list folders. You can change the name of task list folders and as well as the order that the
folders are displayed on the screen.
To create task list folders:
1. Click Create.
2. Type the name of the folder
3. Click OK.
Working with Task List Folders
1
2
3

To rename task list folders:
1. Select the task list folder that you want to move.
2. Click Rename.
3. Type the name of the folder and click OK.
To move task list folders:
1. Select a task list folder.
2. Click Move.
3. From the Select the destination folder drop-down list, select the folder where you
want to move the selected folder.
4. Click OK.

Building Task Lists
You identify tasks that users need to perform. You then determine a sequence and
hierarchy to organize the tasks into a task list.
To create a task list, first you decide the location and name of the task list. For example,
to create a new task list in the Expense Budgeting folder, select the Expense Budgeting
folder, and clicking Create.
You can rename task lists by selecting the task and clicking Rename. You can move the
task list to a different folder by using the Move button.
Select Edit to add tasks to task lists. You can delete tasks by selecting the task and
clicking Delete.
You assign access to task lists so that business users can use the task list by selecting
the task list and clicking Assign Access.
Building Task Lists
1
2
3

To create new task lists, do one of the following:
Selecting Administration > Manage Task Lists.
Select File > New > Task List.

Adding Tasks to Task Lists
After creating a task list, you set up task titles and determine the hierarchy of the tasks.
You also define task properties and add instructions to the task list or to individual tasks
to help users complete the tasks.
Adding Tasks to Task Lists
Use Add Child or Add Sibling
to add tasks to the task list
and define the hierarchy.

Setting Up Tasks
After creating task lists and adding task names, you define the individual tasks. To do so,
you must navigate to the folder that contains the task list and select the task.
You can specify the name of the task and the type of task and add instructions for users
by using the Edit Task dialog box. You can select from the following types:
URL Task
Data Form
Business Rule
Workflow
Descriptive
Setting Up Tasks
Specify name of task.
Specify type of task.
Add instructions.
Set task due date and time.
Set alert due date and time.
Indicate any dependency.

Additionally, you can set the due date and time for completing the task. You can also set
an alert date to alert the business user about an upcoming due date. You can also
determine whether the task is dependent on another task.
If you set a completion date for a task, traffic light indicators are displayed on the task to
alert users when the due date is approaching or when the due date has passed. You can
also set up two types of e-mail messages to be sent to users. A due-date message can
be sent to notify the user that a task is overdue, or an alert message can be sent to
remind the user about an approaching due date.

Setting Task Properties
After adding a task, you must set up properties for all tasks except descriptive tasks. The
tasks for which you must set up properties include:
Data FormSelect the form folder that contains the form, and then select the form.
Business RuleFrom the Plan Type drop-down list, select the plan type associated
with the business rule, and then, from the Business Rule Name drop-down list, select
the business rule.
WorkflowFrom the Scenario drop-down list, select the associated scenario, and
then, from the Version drop-down list, select the associated version.
You can set up a task to launch other applications such as MS Word, MS Excel, or PDFs.
URL TaskEnter the fully qualified URL that you want to associate with the task.
Types of tasks to set properties for:
Data Form
Business Rule
Workflow
URL Task
Setting Task Properties

N OT E
For URL Task properties, you must enter a fully qualified URL to associate with
the task. An example of a fully qualified URL is http://www.hyperion.com. In
addition, you have the option of using single sign-on, so that users can sign on to
other Hyperion products without signing on multiple times.

Assigning Access to Task Lists
You can assign various types of access to task lists, and you can assign access to
individual users or user groups. By assigning access to task lists, you determine who can
view and modify task lists. By default, administrators have Manage and Assign access to
all task lists for design modifications and use. Interactive users and planners have
access to certain task lists, as determined by their access rights. There are four types of
access that you can assign to a task list.
Assigning Access to Task Lists
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 the task list and to see and
use the task list.
None prevents users from seeing the task list.

Validating Task Lists
After defining task lists, you should test them to validate that the task properties are
correct, that the tasks within the task list are sequenced properly, and that the task lists
are accessible to relevant users.
Validating Task Lists
Ensure that you are in Basic mode.
Select the task list from the quick launch list.
Use the wizard to advance to the next task.
Complete the activities for the task.
Mark the task as completed.

Reporting on Task Lists
You can create reports to review the task lists created for your application. You run task
list reports from the View menu by selecting View > Task List > Report. You can produce
a report as either a PDF file or an Excel worksheet. The status report contains the task
lists, task list owners, due dates, completion dates, and status of the task.
N OT E
You must be in Basic mode to view task list reports.
Reporting on Task Lists

Summary
Define task list capabilities
Navigate task lists in Basic and Advanced modes
Create task lists
Assign access to task lists
Validate task lists
Report on task lists

M O D U L E 1 0
Analyzing Planning Data with Financial
Reporting 25
Overview
The aim of this module is to navigate Financial Reporting and analyze plan
data.
Financial Reporting Overview
Navigating Reports in Workspace

L E S S O N 2 6
Financial Reporting Overview 26
Objectives
Describe Financial Reporting
Review data sources
Navigate Financial Reporting Studio
Log on to Financial Reporting Studio
Identify portions of the Financial Reporting Studio workspace
Open, preview, and print reports
Identify report components
Change the user point of view

Module 10 Analyzing Planning Data with Financial Reporting
Lesson 26 Financial Reporting Overview
Financial Reporting Features
With Financial Reporting, you can graphically design and present analytic data. You can
design traditional financial report formats, such as cash management reports, profit and
loss statements, and balance sheets. You can also design nontraditional formats for
financial or analytic data that includes text and graphics.
Key features of Financial Reporting:
Flexible range of output options
Scalable, cross-platform, server-based report generation
Graphical, object-based report creation with simultaneous access to multiple
Hyperion data sources
Objects that are reusable across multiple reports
Book creation for similar reports
Dynamic scheduling that enables automated reporting
Financial Reporting Features
Batches and
books
Asymmetric
reporting
PDF & HTML
reports
Printing Grids Charts Scheduling
Conditional
formatting
Guided
analysis
Reusable
objects
Access
security
Financial Reporting functionality
Report designers
and viewers
Reports and books

Workforce Planning and XBRL Functionality
Workforce Planning is an add-on module for Hyperion Planning 4.0 and Hyperion
System 9 Planning. Using Workforce Planning, you can define a dimension with attribute
associations that change across time periods or other dimensions. For example, you
may have a Status attribute dimension associated with an Employee dimension. This
allows you to change the employee status over time. In January, John Smith might have
the status of full time; in March his status might change to part time. You can use
Financial Reporting to report on Workforce Planning applications and display the results
of these slowly changing attributes.
XBRL (Extensible Business Reporting Language) is an XML-based (Extensible Markup
Language) framework. It provides you with a standards-based method to prepare,
publish, reliably extract, and automatically exchange financial statements. XBRL makes
it easier for you to produce financial statements for various audiences, such as investors,
regulators, and creditors.
Workforce Planning and XBRL Functionality
Display the results of these slowly changing attributes Using Financial Reporting
Define a dimension with attributes that change across time
periods or other dimensions
Using Workforce Planning
Attach XBRL metadata to an existing report as an XBRL
instance document
Using Financial Reporting
Prepare and publish financial statements for various groups Using XBRL
Workforce Planning and Financial Reporting
XBRL Functionality and Financial Reporting

With the XBRL functionality in Financial Reporting, you can create XBRL instance
documents. You attach XBRL metadata to an existing report and then export the report
as an instance document. You can create XBRL instance documents using Essbase,
Planning, or Financial Management data sources.

Financial Reporting Architecture
Financial Reporting is based on a three-tiered architecture that contains the client,
application, and database tiers.
Client Tier
The client tier refers to the local interfaces used to author, analyze, present, report, and
distribute content.
With Hyperion System 9 BI+ Financial Reporting Studio , you connect to a Report
Server to design reports, snapshot reports, and report objects, and to view reports.
You use the Financial Reporting Web client in the Microsoft Internet Explorer Web
browser to view reports and books, design and run books and batches, and manage the
repository and security.
Through Smart View, you can import Financial Reporting report images into Word and
PowerPoint. You can also import Financial Reporting report grids into Excel.
Financial Reporting Architecture
Database
tier
Web Server
Financial Reporting
Web application
Workspace Web
application
Core Services
Financial Reporting
services
Smart View
Office Add-in
Financial
Reporting Studio
Financial Reporting
Web client
Application
tier
Client
tier
Repository
SAP/ BW Financial
Management
Planning Essbase

Application Tier
The application tier is a middle tier that retrieves the requested information and manages
security, communication, and integration. The Web server, Financial Reporting Web
application, Workspace Web application, Financial Reporting services, and Core
services are on the application tier.
The Financial Reporting Web application and Workspace Web application rely on the
Web server to send and receive content from Web clients.
Financial Reporting services support Financial Reporting functionality by processing
batch requests, generating output, and distributing Financial Reporting client content.
Core services provide mandatory services for storing and retrieving objects in the
repository, authenticating users, managing roles, and managing sessions.
Database Tier
The database tier contains the relational database repository and the Essbase or
Planning data sources.
The repository stores Hyperion system data, such as security information, reports, and
report objects. The following relational databases are supported:
Microsoft SQL Server 2000 Service Pack 3a (Enterprise or Standard Edition)
Oracle 9i - 9.2.0.1 or 10g - 10.1.3.0
IBM DB2 Release 8.2
The Essbase and Planning data sources contain the data for your reports. Financial
Reporting supports the following data sources:
Essbase 7.1.x or System 9
Planning 4.0.5 or 9.3
Financial Management 4.0.5 or 9.3
SAP BW 3.1 or 3.5
Microsoft SQL Server 2000 or 2005 Analysis Services

Security Overview
Hyperion System 9 BI+ uses common user provisioning for centralized user
administration. Common user provisioning resolves the issue in Hyperion applications of
configuring the same user multiple times for each Hyperion product and application. You
manage users in Shared Services and specify to apply either native or external
authentication when users log on to Hyperion products.
The security environment consists of authenticating users during the logon process,
authorizing users to perform certain actions, and allowing access to objects and folders
in the repository.
When you create users, you specify how they are authenticated when they log on to
Financial Reporting and what actions they can perform. For example, you define which
users can design reports and which users can only view reports. After creating objects in
the repository, you assign the access rights that define which users can view or modify
the objects. For example, you can specify that jsmith can view all reports in the Sales
Reports folder.
Security Overview
Common user provisioning managed by Shared Services
Native and external authentication of users
Authorization of actions that users can perform in Financial Reporting
Access privileges for report objects

Users, Groups, and Roles
Users, groups, and roles are part of the security system. You assign roles to users to
determine the type of user they are and the actions that they can perform.
A role is specific to a products application and it is defined based on product functions.
For example, a user with the report designer role can access Financial Reporting Studio
and create reports. A user with the scheduler role can schedule and manage batches in
Financial Reporting.
A group is a collection of related users with similarities such as a geographical location, a
department within an organization, or a need to share the same information. A user can
belong to multiple groups. You can assign roles through groups. The users in the group
inherit the roles assigned to the group.
Users, Groups, and Roles
Provisioning
manager
Users Groups Roles
Report
designer
Explorer
Development
P. Frank
V. Yu
Global
administrator
A. Smith
Marketing
F. Jones
J. Doe

The following table describes the available roles for Financial Reporting:
Role Description
Directory manager Create and manage users and groups
Explorer Access the Explore module to search for repository content
Global administrator Access all resources and all functionality
Provisioning manager Provision users and groups to applications
Report designer Access Financial Reporting Studio, create report objects, and
import and export Financial Reporting content
Scheduler Schedule batches and manage batch output

Data Sources for Financial Reporting
To analyze your plan data using Financial Reporting, you can access information using
the Planning ADM (Planning Details) or Essbase ADM driver. The type of information
you want to report on determines which ADM should be used to access the data source.
The Planning Details data source should be used only when the report needs to contain
Supporting Details or Planning Unit Annotations.
Consider the following points when using the Planning Details data source:
Attributes are not represented as dimensions; use the Member Property function for
attribute member selection. By default, member properties are in the order of the
outline of the base dimension; use the OrderBy member selection function to sort the
report in order of the properties. There is no ability to group or subtotal attribute
values automatically.
The HSP_Rates dimension is not visible.
Data Sources for Financial Reporting
Budgeting Application
Plan Type 3
Plan Type 2
Plan Type 1

Linked reporting objects (LROs) are not supported.
Metadata security is first checked on the relational database, and then the request
for data is made to Essbase accordingly.

Financial Reporting Studio
Financial Reporting Studio is a report designer in which you create the structure, layout,
and format of a report and specify the data sources from which the report retrieves its
data. No data is shown in the report design window. During report design, you can add
objects to the report, dynamically change the data that is displayed, and preview and
print the report.
Financial Reporting Studio

Working with Financial Reporting Studio
Before launching Financial Reporting Studio, you must start the Essbase Server. You
must have a valid administrator or designer user ID and password to log on to Financial
Reporting. The user ID is authenticated by Financial Reporting or by an external source,
such as Essbase or Windows NT LAN Manager.
Working with Financial Reporting Studio
Select Start > All Programs > Hyperion System 9 BI+ > Financial
Reporting Studio.
Enter user ID
Select the server
Enter password
Click OK

Financial Reporting Studio Workspace
When you first log on to Financial Reporting Studio, you see a workspace area with a list
of report objects. From this workspace, you can create a new report or open an existing
report.
Standard Toolbar
The standard toolbar provides the following alternatives to menu commands:
Button Description
Opens a new report workspace
Opens the Open dialog box to select a report
Saves a report or object in the repository
Financial Reporting Studio Workspace
Standard
Toolbar
Repository
Toolbar

Repository Toolbar
The repository toolbar provides the following alternatives to menu commands that
manage the repository:
Opens the repository
Opens the Print dialog box
Displays the active report in the Print Preview window
Displays the active report in the Web browser
Button Description
Deletes the selected object
Refreshes the repository display of objects
Button Description

Viewing Repository Objects
The Financial Reporting repository is the object management tool that functions like
Windows Explorer. You save all report objects in the repository and can then use the
same object in more than one report.
The following table describes the object types:
Object Type Description
Batch Container that processes groups of reports and books.
Book Container that holds a group of similar reports.
Grid Report object that contains data from external data sources.
Image Report object that contains a graphic or an image file.
Report Layout that dynamically identifies the content and formatting of a report. A
report becomes populated with data when you run it.
Viewing Repository Objects
Object name Object type

You cannot delete the highest-level folder named Root. In the Financial Reporting Web
client, you can add additional folders and categorize them to suit your needs. For
example, you can create specific folders for batch jobs, books, images, or reports, or
separate folders for different departments.
To display repository objects:
1. Select File > Explore.
A list of repository objects is displayed.
2. Select View > Display Items of Type and select one of the following options to display
only selected object types:
All Items
Report
Snapshot
Book
Snapshot Book
Batch
Saved Report Object
Snapshot Generated report that contains static data from a specific point in time.
Subsequent changes of the data in the data source do not affect the report
content.
Text Report object that contains text or functions.
Object Type Description

Opening Reports
You open reports to design, preview, or print them. You can display both dynamic reports
and snapshot reports. A dynamic report is opened in the report workspace. A snapshot
report is opened in the Web preview window.
If you want to design, view, or print dynamic reports, you must be connected to an
Essbase or Planning database. Otherwise, you can view only snapshot reports.
Opening Reports
1. Select File > Explore to display the repository objects.
2. Expand the repository folders to find the report.
3. Double-click the report to open it.

Report Components
Reports contain report objects such as text boxes, grids, images, and charts.
When you design a report, you add report objects to the report workspace. As you select
each report object, its property sheet is displayed in the workspace frame on the right.
You use property sheets to customize report objects.
Report Components
Image Text Box
Grid
Chart

Changing the User Point of View Members
The user point of view (POV) bar displays members that are not defined in the grid. The
bar is specific to a database for a single user, but not specific to any report or grid in a
report. In the user POV, you change the default values for all grids in the report
simultaneously. By changing the user POV, you dynamically change the data that is
displayed and calculated in the report.
When you select a dimension on the user POV bar, the Select Members dialog box is
displayed. You can change the selected member for each dimension and attribute
dimension that is not defined in the grid. In the POV, you can select only one member for
each dimension.
Changing the User Point of View Members
User POV bar
Dimension name Member name

Previewing and Printing Reports
While designing a report, you preview it to check the result of the structure, layout, and
format of the report. You can preview a report in two ways:
Print Preview: Displays the report with data as it appears when printed.
Web Preview: Opens a Web browser window and displays the report with data as
it appears in the Financial Reporting Web client.
The Print Preview window includes a toolbar for printing, navigating, zooming in, and
zooming out.
Previewing and Printing Reports
Print
Preview
Web Preview

You can print dynamic and snapshot reports. For example, you might print end-of-month
reports for all regions. You can open a report and then print it, or you can print the report
from the Explore window without opening it. When you print the report, you can select
the printer, print range, and number of copies.

Summary
Describe Financial Reporting
Review data sources
Navigate Financial Reporting Studio
Log on to Financial Reporting Studio
Identify portions of the Financial Reporting Studio workspace
Open, preview, and print reports
Identify report components
Change the user Point of View (POV)


L E S S O N 2 7
Navigating Reports in Workspace 27
Objectives
Identify interface elements in Workspace
Set preferences
Set the user point of view
Limit the user POV member selections
Integrate reports into Microsoft Office applications

Lesson 27 Navigating Reports in Workspace
Workspace Overview
Workspace provides a single point of access to BI+ content and authoring tools. You can
access the following content in Workspace:
Financial Reportingfor scheduled or on-demand highly formatted financial and
operational reporting
Web Analysisfor interactive ad hoc analysis, presentation, and reporting of
multidimensional data
Interactive Reportingfor ad hoc relational query, self-service reporting, and
dashboards against any ODBC data source
Production Reportingfor high-volume enterprise-wide production reporting
Depending on your assigned roles and security access, you can use Workspace to
perform the following tasks related to Financial Reporting:
Workspace Overview
Set preferences
View reports
Create books

View and print reports and books
Create and modify books
Create and schedule batches
Assign access to repository items
Set preferences
Perform administrative tasks such as managing users

Workspace User Interface
In Workspace, you can open and work with the following Workspace elements.:
Element Name Description
Adjuster Adjusts the size of the view pane and content area
Buttons Enables performance of module tasks
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 the location of the current folder, item, or step
Workspace User Interface
Standard
toolbar
Menu
bar
Content area
View
pane
Buttons
Document
tab bar
Navigate
menu
Process
bar
Adjuster

Standard toolbar Provides shortcut buttons for performing tasks
View pane Provides buttons that enable jumps between panels
Element Name Description

Workspace Modules
You use Workspace modules to perform the following tasks:
Module Name Description
Explore View, manage, and secure repository items
Applications Access and view applications such as Planning and Financial
Management
Administer Manage users, groups, roles, and authentication methods
Schedule Schedule batch jobs for automated processing
Impact Manager Update Interactive Reporting documents when database
structures change
Open Items View all documents or items opened in Workspace
Workspace Modules

View Pane Buttons
When you select a module, context-sensitive buttons are displayed at the top of the view
pane.
Button Description
Tips Displays shortcuts to actions (Tasks) and links to online help instructions
(Tips) for tasks, tips, and file details relevant to the current item
Folders Displays the Root folder and the folders and repository items below it
View Pane Buttons
Tips button Folders button

Setting Preferences
You can set preferences for the Workspace user interface, user authentication, the
Explore module, and Financial Reporting Studio. Preference changes become effective
the next time that you log on.
Setting General Preferences
You can set defaults for the general appearance of your Workspace user interface.
You can select the page to be displayed in the content area. The Content option
determines what other options are available. For the example shown on the slide, you
select Explore and then select the FR/Qtr Reports folder.
You can set up prompts to save unsaved files. You can also show the document path
and the Tips tab. You cannot update the e-mail address because it is registered in the
users security settings.
Setting Preferences
Select File > Preferences.
Options:
None
Explore
Document
Favorite
Application

Setting Authentication Preferences
If you are a native user in Workspace, you can change your password. Native users are
authenticated by Shared Services, rather than by external sources, such as Essbase or
Windows NT LAN Manager (NTLM).
Setting Authentication Preferences
Select File > Preferences > Authentication.

Setting Explore Preferences
You can set Explore preferences to define default folders in Workspace. If you do not
select default folders, they are set to the top-most or root folder (denoted by /).
Default folders:
DefaultFolder displayed when you select the Explore module; typically the folder
that you access most often
New DocumentFolder in which the new document wizard searches for Web
Analysis database connection files and Interactive Reporting documents
You can also specify the default file permissions assigned to items you create or import
into the repository. Permissions define the level of access that you grant to other users.
Setting Explore Preferences
Select File > Preferences > Explore.

Setting Financial Reporting Studio Preferences
You can set the following preferences for Financial Reporting Studio:
Language
XBRL Editing
Color, style, and distance between guide lines
Select Dot
or Line
Select Inches or
Centimeters
Setting Financial Reporting Studio Preferences
Select File > Preferences > Financial Reporting, and then select the
Financial Reporting Studio tab.

Setting Financial Reporting General Preferences
You can define preferences and formatting options for the Financial Reporting module:
Default mode for previewing reports and books
User POV preview, location, and member selections
Microsoft Office application to which reports are exported
Behavior of prompts
Setting Financial Reporting General Preferences
Select File > Preferences > Financial Reporting.

Separators for formatting numbers in a grid
The separators for formatting numbers in a grid apply only if you select the Defined
by Preference option during report design.

Browsing the Repository
In the Explore module, you can browse the repository and perform these actions:
Open reports and books
Edit books and batches
Export and import items
Set security access
When you select a repository folder in the view pane, the folder items to which you have
access are displayed in the content area. By default, each item displays name, type, date
modified, and description. You can sort the list of items by clicking the column headings.
You can also change the column order by sliding the column headings to the right or left.
Browsing the Repository
AnalyticServices folder Items in the AnalyticServices folder
Sort the list by clicking
a column header

On the View menu, you can change the display by showing or hiding columns and
setting the width of each column. You can also limit the display to a particular type of
item, such as displaying only a list of books.
You can also use the Viewer module to access repository items located on your desktop.
You specify your default desktop folder in the Explore preferences. When you select
Desktop, the repository items in the specified folder are displayed as icons in the content
pane. When you open reports and books, their names are listed in the Viewer module.

Searching for Items
In the Explore module, you can search for items based on keywords. By default,
keywords are generated for repository items and include the words in the item name and
description.
You can narrow your search by specifying item location, date, and type.
Search rules:
The search is not case-sensitive.
Wildcards are not supported in the Keywords box.
Multiple keywords are separated by a space.
The search starts in the folder specified in the Look in box and proceeds through all
subfolders.
Search
criteria
Search
results
Searching for Items
In the Explore module, select Tools > Search.

Previewing Reports
In the Explore module, you can preview reports in two formats:
Hypertext Markup Language (HTML)Preview reports or snapshots
Portable Document Format (PDF)Preview or print reports or snapshots that are
displayed in the Web browser in Adobe Acrobat Reader
N OT E
Before previewing reports in PDF, ensure that a PDF writer (Adobe
Acrobat Distiller, GNU Ghostscript, or AFPL Ghostscript) is installed with
your print server.
Previewing Reports
User POV
Page selector

Essbase Server must be started so that you can view dynamic reports. When you view a
dynamic report, the user POV is displayed. When you change the user POV, the report is
automatically refreshed to display current data for the new member selection.
When you view a snapshot report, you see data for a specific point in time. Because the
POV is fixed with static data when it is created, the user POV is not displayed when you
view it. A snapshot report is disconnected from the data source and is not updated when
data changes.
From the Financial Reporting general preferences, you can select the default preview
mode for reports. When you double-click a report name in the repository, the report is
displayed in the default preview mode. The selected setting remains in effect until you
change it.
To preview reports or snapshots:
1. In the repository, right-click a report or snapshot.
2. Select Open In > HTML Preview or Open In > PDF Preview.
The report is displayed in the content area.

Changing the User Point of View
When you preview a dynamic report, the user POV bar is displayed in the view pane or
above the report. You change the user POV member selections to dynamically change
what data is displayed and calculated in the report. When you change the POV, the
report runs and displays the data for the new POV member selection.
You can search for a specific member to display in the user POV. For the example
shown on the slide, you search for all names that begin with LOC. You can then select
the member for the user POV from the Search Result dialog box.
Changing the User Point of View
Wildcard search for entity names
that begin with 2
Search results

The following table describes the options in the Member Selection dialog box:
Option Description
Show Properties Select the properties to display, such as Name, Description,
Generation, and Level.
Expand All Rows Expand the dimension hierarchy.
Collapse All Rows Collapse the dimension hierarchy.
Rows Per Page Specify the number of rows displayed on a page. If more
members are available than the number of rows specified, Next
Page and Previous Page buttons enable you to scroll through the
rows.
Find list Select the option on which to base the search, such as Name,
Description, Generation, and Level.
Find box Enter the characters for a search:
Partial text with wildcard symbols
Exact characters (Enclose the characters and the blank spaces
between them in quotation marks.)
Find Find the items that match the search criteria.
Use Wildcards Search by text and wildcard symbols:
? represents one character
* represents multiple characters

Previewing the Point of View
When you view a report in Workspace, the report displays the current data. If the POV is
not the one that you want, you must change it and rerun the report. A second query of
the database is created. If you are working with a large database, this process is time-
consuming.
Workspace enables you to preview and select the user POV before it queries the
database. When you preview the user POV, you make your POV selections before the
report runs.
Previewing the Point of View
Select the POV before
the data is retrieved.
Select On to preview
the user POV.
Open the report in
HTML or PDF mode.

Limiting User Point of View Selections
By default, all dimension members are available when you access the user POV. For
Essbase or Planning databases, dimensions may contain members that you never
access.You can limit dimension members by creating a choices list, so that only listed
members are displayed for all reports that retrieve data from the same database
connection.
For the example shown on the slide, you specify that available members for the Scenario
dimension are Actual, Budget, and Forecast. For all other dimensions, you may select
any member.
Go to Member
Selection button
Member label
options
Limiting User Point of View Selections
Select File > Preferences > Financial Reporting > Setup Members.

When setting up members for the user POV, you can define the display of member
names in the user POV bar. You can select to view dimension name, member name,
alias, or both member name and alias.

To set up user POV member selections:
1. Select File > Preferences, click Financial Reporting, and click Setup Members.
The Setup User POV dialog box is displayed.
2. From the Database Connection list, select a database connection.
The dialog box displays the database dimensions.
3. To the right of the dimension for which you want to create a choices list, click Go to
Member Selection: <dimension name>.
A Members tab is displayed in the Setup User POV dialog box.
Dimension name and member
name are displayed.
Member alias is displayed.

4. In the Available area on the left, select the members that you want to include in the
choices list, and click the add button .
The members are displayed in the Selected area.
5. Click OK to save the member selections.
The Setup User POV dialog box is displayed with the selected
members listed in the Choices List column.
6. Repeat steps 3 through 5 for any dimension for which you want to create a choices
list.
7. Optional: To the right of the dimension for which you want to change the member
selection, click the ALL button to set the choices list back to All Members.
8. From the Display Member Label as drop-down list, select to display the member
name, the alias, or both the member name and alias.
9. From the Dimension Labels are drop-down list, select whether dimension labels are
Included or Not Included in the user POV bar.
10. From the Member Selection Displays drop-down list, select to filter members
according to access privileges.
Options:
Only Members I Can Access: Only members to which the user has access are
displayed in a flat list.

All Members Regardless of Access: All members, regardless of the users access
privilege, are displayed in a hierarchy.
11. Click OK to save your changes and return to the Preferences dialog box.
N OT E
The Member Selection Displays drop-down list is available only for Planning
database connections. This option is displayed only if the
DisplayFilterBySecurity flag in the hr_webapp.properties file is turned on.

Changing Page Members
You can change a page member only if you assigned multiple members to the page axis
during the report design. You must view the report in HTML to select different page
members. After you change a page member, the report is refreshed, and the data for the
selected members is displayed.
When you view a report with multiple page members in PDF, the data for the page
members is displayed on different pages.
Changing Page Members
Qtr 1 page selection Qtr 2 page selection

Printing Reports and Snapshots
You can print reports or snapshots in HTML or PDF mode:
HTMLIf a report or snapshot has multiple page members, only the displayed page
member is printed. The browser print capabilities determine how the report is printed.
PDFIf a report or snapshot has multiple page members, all page members are
printed. PDF printing ensures that the report or snapshot is properly formatted and
paginated; PDF printing provides better quality than does HTML.
Printing Reports and Snapshots
1. Open the report in either HTML or PDF preview mode.
2. Select File > Print > HTML or File > Print > PDF.

Integrating Reports into Microsoft Office Applications
You can move reports and snapshots into Microsoft Office applications in the following
ways:
Export from WorkspaceYou can export report content as an image into
supported Microsoft Office applications. After inserting the content, you can query
the corresponding Web application to refresh the image in Smart View.
Import to Microsoft OfficeWhen logged on to a supported Microsoft Office
application, you can import reports and snapshots from the Workspace repository
into Word, PowerPoint, and Excel. This feature is provided through Smart View,
which provides integration with Microsoft Office for Financial Reporting, Web
Analysis, Financial Management, and Planning.
Integrating Reports
into Microsoft Office Applications

Exporting Reports to Excel
After previewing a report in HTML or PDF mode, you can export the report to a Microsoft
Excel spreadsheet.
When you export a report to Excel, you must choose one of the following options:
Fully-Formatted Grids and TextThe current page of the report is exported to
Excel in a format that is similar to its format in Financial Reporting. The report is
converted to HTML with the Hyperion formatting definitions and calculated numbers.
Charts in the report are exported as images. To export multiple pages, you display
and export one page at a time.
N OT E
If you are using Microsoft Office 2000, only the grid and text objects of the
report are exported into Excel. Charts and images are not exported.
Exporting Reports to Excel

Query-Ready Grids and TextThe first grid in the report is exported to Excel. The
grid is converted to HTML, and Hyperion-specific formatting is removed. Images and
charts in the report are not exported. After the grid is exported, you connect to an
Essbase server and use Smart View to perform ad hoc analysis.
To export a report to Microsoft Excel:
1. In the Explore module, open the report in either HTML Preview or PDF Preview
mode.
2. Select File > Export > Excel > Fully-Formatted Grids and Text or Query-Ready Grids and Text.
The File Download dialog box is displayed.
3. Perform an action:
Click Open to open the report in an Excel spreadsheet and then save the
spreadsheet.
Click Save to save the report as an Excel worksheet that you can open at a later
time.
N OT E
If you have set Excel files to open as a browser preference, the file may open
automatically in the browser window, without showing the File Download
dialog box.

Exporting Reports to Word and PowerPoint
After previewing a report in the Explore module, you can export the report as an image to
Word or PowerPoint. You can export reports if you are using Microsoft Office 2002 or
later.
To export a report to Word or PowerPoint:
1. In the Explore module, open a report.
The report is displayed in HTML or PDF mode.
2. Select File > Export > Word or File > Export > PowerPoint.
The File Download dialog box is displayed.
Click Open to open the report in Word or PowerPoint.
Exporting Reports to Word and PowerPoint

Click Save to save the report as a Word or PowerPoint document that you can open
later.
T I P
After importing the image, you can use the Microsoft Office Format Picture
option to further format the object; for example, to crop and resize the image.

Importing Reports to Microsoft Office Applications
You can import Financial Reporting reports to Microsoft Office applications through
Smart View:
Word and PowerPointThe report is imported as an image.
ExcelThe report is imported based on the selected method (Fully Formatted Grids
and Text or Query-Ready Grids and Text).
In Microsoft Office, you must connect to a Workspace repository that contains the reports
that you want to import. You log on to the data source only once. For example, you can
log on to a data source connection in Word and use the connection to access data in
Excel or PowerPoint.
Importing Reports
to Microsoft Office Applications

To import reports to Microsoft Word, PowerPoint, or Excel:
1. Launch Microsoft Word, PowerPoint, or Excel.
2. Select Hyperion > Connection Manager.
The Connection Manager dialog box is displayed.
3. Select the data source, and click Connect.
The Connection credentials dialog box is displayed.
4. Enter the user name and password, click Connect, and then click Close.
5. Select Hyperion > Reporting and Analysis Document > Import.
The Import Workspace Document dialog box is displayed.
6. Expand a repository folder, select a report, and click OK.
The Import Workspace Document dialog box displays the report.
7. Optional: To change the user POV, in the POV, select a dimension.
8. Optional: To import all pages of the report, select All Pages.
9. Optional: To refresh the image by using the Workspace POV, select Refresh Using
Workspace Point of View.
Word or PowerPointTo import the report as an image, in the Import Document
As list, select Image.
ExcelTo place pages on separate worksheets, in the Import Document As list,
select Fully Formatted or Query-Ready, and select Split Pages across worksheets.
The report is imported into the Microsoft application.
11. Click Finish.
12. Optional: Save the report as a Microsoft Office document that you can open later.

Summary
Identify interface elements in Workspace
Set preferences
Set the user point of view
Limit the user POV member selections
Integrate reports into Microsoft Office applications


M O D U L E 1 1
Appendices 27
Overview
This module contains appendices to provide information about additional
features of Planning not covered in this course.
Appendices includes:
Sharing Data Using Data Synchronization
Working with Classic Application Administration

A P P E N D I X A
Sharing Data Using Data
Synchronization A
Objectives
Describe data synchronization
Create mapping tables and data synchronizations
Set data synchronization filters
View data flows
Execute synchronizations

Module 11 Appendices
Appendix A Sharing Data Using Data Synchronization
A-2 Planning: Create and Manage Applications
About Data Synchronization
You use data synchronization to transfer data automatically from a source application to
a destination application. Data synchronization provides filters for selecting data needed
for other applications. You can schedule data synchronization to run during off-peak
business hours, and you can view data flows between applications after a data
synchronization has occurred.
For the example shown on the slide, HYPlan is the master (source) application that
contains both balance sheet and income statement actuals. Finbud is the destination
application that contains financial budgeting plans. You use data synchronization to
transfer the data from the Net Income hierarchy of the HYPlan application to the Net
Income hierarchy of the Finbud application.
About Data Synchronization
Finbud application HYPlan application
Actuals
Budgeting plans
Mapping table

Planning: Create and Manage Applications
A-3
Creating Mapping Tables
In order for the data synchronization to transfer dimension data between two
applications, the dimension member names must match. If the member names do not
match, you must create a mapping table to map members in the source application to
members in the destination application. For example, you could map data from the
Account member in the source application to the Revenue member in the destination
application.
After creating a mapping table, you insert it into a data synchronization. You can use the
same mapping table in many data synchronizations.
Creating Mapping Tables
To create a mapping table, you specify source and destination
dimensions.
Source application is where
the data is retrieved from.
Destination application is the
application that receives the
data.

To create mapping tables:
1. Determine which dimension members must be mapped due to mismatched member
names.
2. Select File > New > Mapping Table.
The Mapping Table Designer is displayed.
3. On the Setup page, specify the source application, destination application, and the
dimension for which you want to map data.
4. On the Map Data page, specify how each member is mapped:
a. Select the member from the source dimension.
b. Select the member in the destination dimension to which it should be mapped.
5. Repeat step 4 for each member that must be mapped.
6. Validate the mapping.
7. Save the mapping table.

A-5
Creating Data Synchronizations
You create a data synchronization by performing the following tasks in the New
Synchronization wizard:
1. Specify the data source and the destination application.
2. Link source dimensions to destination dimensions.
3. Create filters for source dimensions.
Creating Data Synchronizations
You use a wizard to create a data synchronization.
Insert Mapping
Table
Execute
Synchronization
Data Synchronization Toolbar
Validate
Synchronization

Specifying Source and Destination
You use the New Synchronization wizard to specify the data source and destination for a
synchronization.
Data source types:
Flat file
Interface table
Planning or Financial Management application
Specifying Source and Destination
The Data Synchronization Wizard has three pages:
Application that is receiving the data. The target application can be a
Planning or Financial Management application.
Select Destination
Object or application that is receiving the data. Select Source
Data source type that is sending the data. Source Type
Description Data Synchronization Page

A-7
Linking Dimensions
After specifying the data source and destination, you specify a matching dimension in the
destination application for each source dimension. For example, you map the data for
the GL_Accounts dimension in the source to the GAAP_Accounts dimension in the
destination application.
To link dimensions:
Drag a dimension from the source application to the destination application.
A link is displayed as a line connecting the source dimension to
the destination dimension.
Linking Dimensions
Insert mapping tables in Data Synchronization to ensure correct data
linking between members.
Source application is where
the data is retrieved from

Setting Filters
By default, data for all dimension members of each dimension is transferred when you
execute a data synchronization. You can create filters so that only member data needed
in the destination application is transferred from the source.
For instance, the Finbud application must receive data from the HYPlan application.
However, the Finbud application needs data only from the West entity. By applying a filter
to the Entity dimension in the HYPlan application, you transfer data only from West.
To create filters:
1. On the Link Dimensions page, right-click a dimension and select Create Filter.
The Member Selector dialog box is displayed.
2. Select members and click the right arrow button.
Setting Filters
You select filters using the
Member Selector dialog box.

A-9
Applying Filter Criteria
You can set criteria to refine a filter:
Filter Criteria Description
Equal Filters what is equal to the dimension name in the selector field
Like Filters to perform pattern-matching functionality on partial dimension
names
N OT E
After the filter is applied to the dimension, a filter icon is inserted next to the
dimension name on the Link Dimension page.
Applying Filter Criteria
A filter was applied to the source
entity.

Inserting Mapping Tables
Inserting mapping tables is the last step before validating a data synchronization. Not all
data synchronizations require mapping tables. Mapping tables are inserted for those
applications that are not able to link dimension to dimension, because the dimensions
members have different names in both applications.
To insert mapping tables:
1. On the Data Synchronization toolbar, select Insert Mapping Table.
2. From the mapping table list, select a table and click OK.
A dashed line is displayed to indicate that a mapping table was
inserted. (A solid line indicates that dimension members are
linked without inserted mapping tables.)
Inserting Mapping Tables
Insert Mapping Table button

A-11
Validating Data Synchronizations
When you validate a synchronization, the source and destination process the request
and resulting data and generate errors without writing the data to the destination
application. You can quickly rectify synchronization issues.
To validate synchronizations:
1. Right-click the synchronization and select Validate Synchronization.
The Data Sync Validation Options dialog box is displayed.
2. Optional: Define a calculation to perform on the data.
a. In the Operator text box, enter a standard mathematical operator.
b. Optional: In the Value text box, enter a numeric value.
3. Click OK.
Validating Data Synchronizations
Validate Synchronization button

Viewing Data Flows
After setting up data synchronization between applications, you can view the applications
in a graphical representation that shows the data flow from the source application to the
destination application.
You can access Data Flow from the Application Library by right-clicking the application
and selecting Data Flow. You can view data flows from either the source application or
the destination application.
Viewing Data Flows

A-13
Executing Data Synchronizations
When you execute a data synchronization, the data is retrieved from the source
application, transformed according to mapping rules, and pushed to the destination
application. You can specify a calculation to apply to the data being transferred. For
example, if you are transferring data from Actual to Budget, you could specify that the
values should be increased by 10%.
To execute synchronizations:
1. Right-click the synchronization and select Execute.
The Data Sync Execution Options dialog box is displayed.
2. Optional: Define a calculation to perform on the data.
a. In the Operator text box, enter a standard mathematical operator.
b. Optional: In the Value text box, enter a numeric value.
3. Click OK.
Executing Data Synchronizations
Execute Synchronization button

Summary
Describe data synchronization
Create mapping tables and data synchronizations
Set data synchronization filters
View data flows
Execute synchronizations

A P P E N D I X B
Working with Classic Application
Administration B
Objectives
Describe classic administration
List the steps for creating Planning applications
Create Planning applications using classic application administration
Set up dimensions and members in Planning
Load metadata files

Appendix B Working with Classic Application Administration
B-2 Planning: Create and Manage Applications
Classic Administration Overview
An application is a related set of dimensions and dimension members that you use to
meet a specific set of planning needs. Each application has its own accounts, entities,
scenarios, and other dimensions. For example, you could create an application for your
cost centers for budgeting operating expenses and a separate application for the finance
department for revenue planning.
You can create applications using either EPM Architect or Classic application
administration. Classic administration enables you to administer Planning on an
application-by-application basis. To use Classic application administration, you must be
assigned the Shared Services roles of Dimension Editor and Planning Application
Creator. Different menus and options are available for each type of application. This
appendix describes Classic administration tasks.
Classic Administration Overview

B-3
You create applications by using the Classic Application Wizard. To set up your
applications dimension, you use the Planning Dimension editor. You can add
dimensions and dimension members or modify existing members characteristics by
working with the Planning Dimension editor. You can load metadata by using Data
Integration Manager (DIM).

Processes in Creating Planning Applications
Setting up an application requires many steps. First, you create an application using the
Classic Application Wizard. By using the Classic Application Wizard, you set up the
application calendar, default currency, and plan types.
After you establish the application, you can set up your application even further. If you set
up your application to support multiple currencies, you establish currencies and
corresponding exchange rates. If your organization has custom summary time periods,
you modify the calendar to include them.
You then create the scenarios and versions that you will use in your application. You
create entities to reflect your organizations budget review structure. You also create the
accounts and additional dimensions that you require to gather planning data. You use
Data Integration Manager to load metadata into your application.
Processes in Creating Planning Applications
Create an application using Classic Application Wizard
Establish the currencies and corresponding exchange rates
Modify the calendar with the custom summary time periods
Create scenarios and versions
Create entities to reflect your organizations budget review structure
Create the accounts and additional dimensions
Use DIM to load metadata and data
Assign access rights to users and user groups
Create appropriate data-entry forms
Use Business Rules to build customized calculations and allocations
Identify review and approval process, its requirements, and its
participants

B-5
After you finalize your dimension structure, you are at a good point to assign access
rights to users and user groups. Next, you create appropriate data entry forms to meet
the needs of your users and groups. As you continue to set up your application, you
create customized business rules to run calculations and allocations specific to your
organization. Finally, you identify the review and approval process, its requirements, and
its participants.

Planning Application Creation Overview
Before you create a Planning application, you need to create and configure a relational
database to work with Planning. You then need to establish connectivity between
Planning, the relational data source, and Essbase. To create an application, you
complete the following steps:
Create a relational database.
Configure the relational database using the Configuration Utility.
Create application using Classic Application Wizard.
Create Essbase databases.
Register the data source name (DSN) using the Classic Application Wizard.
Planning Application Creation Overview
Create
relat ional
database
Conf igure
relat ional
database
Create
application
Creat e
Essbase
databases
Register dat a source

B-7
Planning Relational Databases
Planning requires one relational database for each application as well as one defined as
the Planning system database, which stores an entry for each Planning application that
is created.
The procedures for creating relational databases vary depending on which relational
store your company uses: Microsoft SQL Server, Oracle, or IBM DB2. Once the relational
database is created, connectivity between Planning, the relational database, and
Essbase databases needs to be established by registering data source names.
N OT E
Creating relational databases is typically the responsibility of a system
administrator.
Planning Relational Databases
Create and define a Planning system database and a relational database
for each Planning application.
CorpPlan
TaxPlan
Finbud HPSystem
CorpPlan
TaxPlan
Finbud

Configuring Data Sources
You configure data sources using the Configuration Utility. Configuring the data source
establishes the connection between the relational data source, the relational database
and the Essbase database.
To Configure Data Sources:
1. Select Start > Programs > Hyperion > Foundation Services > Configuration Utility.
2. Confirm the language.
3. At the Welcome message, click Next.
4. On the Select the products to configure page, select Planning and Data Source
Configuration, and click Next.
Configuring Data Sources

B-9
5. On the Select the options for managing the Data Source page, select Create Data
source and click Next.
6. On the Enter Details for creating Data source page, enter the Data source Name and
description, and click Next.
7. From the Instance Name drop-down list, select an instance, and click Next.
8. On the Select the database page, select the relational database, and click Next.
9. On the Enter the Relational Storage Configuration Details page, enter the Server
name, User and Password, and click Next.
10. On the Enter Essbase Server Information page, enter the Server, User and
Password, and click Next.
11. At the successful message, click Next.
12. At the Do you want to go back to the Product Selection Panel message, select No,
and click Next.
13. Click Finish.

Creating Applications Using Classic Application Wizard
You use the Classic Application Wizard to create, and delete Planning applications, and
to register applications with Shared Services. The Classic Application Wizard guides you
through the process of creating a new Planning application. Creating an application and
databases involves the following steps:
Select the data source
Create the calendar
- Select the base time period and weekly distribution options
- Set up the calendar range
Choose the base currency and whether the application supports multiple currencies
Set up plan types
Creating Applications Using
Classic Application Wizard
Use Classic Application Wizard to initialize an application
Data Source
Calendar
Currencies
Plan Types

B-11
Accessing Classic Application Wizard
You access the Classic Application Wizard by selecting Planning Administration from the
Classic Application Administration menu. To create a new application and initiate the
Classic Application Wizard, click Create Application.
Accessing Classic Application Wizard

Selecting the Data Source
On the Select tab, you specify the application name and description, and register the
application with Shared Services by selecting the Shared Services project. You also
select a data source and instance for the application.
The application name can be up to eight characters and must not be the same as an
existing Essbase application.
N OT E
Data sources and instances are set up when you install and configure Planning.
For Classic applications, you must select the instance whenever the instance
changes in the Configuration Utility.
Selecting the Data Source

B-13
Setting Up the Calendar
You set up the calendar to establish the applications base time periods (12 months,
quarters, or custom), starting fiscal year and month, and total number of years. You
select the base time periods and monthly distribution pattern based on the number of
fiscal weeks in a month.
Base time periods are the bottom-level periods in the application. You can select from
the predefined options of either months or quarters, or set up custom base time periods
such as weeks or days. You can select a distribution pattern to determine how data
entered in summary time periods is distributed or spread among the base time periods.
If you select 12 months for base time periods:
four quarters are created per year
months roll up into parent quarters
quarters roll up into years
Setting Up the Calendar

After you create an application, the starting fiscal year for the application cannot be
changed. Weekly distribution sets the monthly distribution pattern, based on the number
of fiscal weeks in a month. If you select a weekly distribution pattern other than Even,
Planning treats quarterly values as if they were divided into 13 weeks and distributes
weeks according to the selected pattern.
You can select the Total Years to be included in the application. You can add more years
to the calendar after the application is created.

B-15
Setting Up Currencies
You use the Currencies window to specify the default currency for the entities in your
application and to establish whether your application supports currency conversion. You
cannot change these settings after you have created the application.
Multiple-currency support is available for level 0 members, regardless of their base
currency. The Classic Application Wizard creates two additional dimensions for multiple-
currency applications. The dimensions are:
Currency Stores the application currency, local currency, and reporting currency
members.
HSP_Rates Stores the input value, input currency, and exchange rate members.
Setting Up Currencies

Setting Up Plan Types
You can include up to three plan types in your application. Separate Essbase databases
are created for each plan type. As you create the accounts, entities, and other
dimensions and members of your application, you associate them with plan types, so
that the database for each plan type contains just the dimensions, members, and data
values relevant to that plan type. This allows for improved system performance.
The number of plan types included in an application depends on your organizations
needs. For example, the sales department might be responsible for a yearly revenue
plan and the finance department for a Profit and Loss plan. You could define two plan
types: Revenue and PandL.
Setting Up Plan Types

B-17
Data can be shared between the plan types. For example, the Revenue plan might
include a number of sales detail accounts that roll up to a Total Product Sales account.
You can set up the P&L plan to include the Total Product Sales account, but to omit the
sales detail accounts. This enables you to bring the data value for Total Product Sales
into your P&L plan, without all of the account details. This creates a smaller, more
efficient database for your P&L plan.
N OT E
You cannot change the number of plan types or the plan type labels after you
create the application. Plan type labels can be up to eight characters long.

Completing Application Setup
You can review the application settings you selected on the Finish window. Before you
create the application, you can modify your settings on any of the other windows by
returning to the appropriate window and making the adjustments. To create the
application with the application settings listed on the Finish window, click Finish.
After you receive a successful message, you can use the Navigate menu to log onto the
Planning application. If you do not see the application listed, you can refresh the
Application menu.
Completing Application Setup

B-19
Creating Essbase Databases
Creating the application, creates a folder in Essbase with the application name and two
files in the application directory a .app file and a .log file. In order to create an initial
outline with the dimension structure, you select to create the databases from the
Administration > Manage Database window.
Creating Essbase Databases

Reregistering Applications
Your Planning applications definition is stored in a relational database, but its data is
stored in Essbase. To bridge the communication between the relational database and
Essbase, you need to register a DSN for each application.
If you created a new application and selected a Shared Services project, your application
is registered. You can use the Classic Application Wizard to reregister an application with
Shared Services.
Reregistering Applications

B-21
Building Member Hierarchies
You can create and update dimensions by using the Dimension Editor. You can assign
access rights to members, rearrange members in the dimension hierarchy, and change
characteristics of dimension members. You use the Member Property tab to set and
change member characteristics.
To Add Dimension Members:
1. Select Administration > Dimensions.
2. From the Dimensions drop-down list, select the dimension.
3. Click Add Child or Add Sibling.
4. Set up the member properties, and then click Save.
Building Member Hierarchies

The next time you create or refresh the database, the Essbase outline is generated with
members in the order that is displayed on the Dimensions window.
You can add custom dimensions such as Customer or Product by selecting Add
Dimension. You can add dimension members to custom dimensions the same way that
you add members to Planning required dimensions.

B-23
Working with Attributes
You can set up attributes to add another level of granularity to your data. You create
attributes for a dimension to group its members according to the same criterion. You
create attribute values which are assigned to dimension members.
For example, you can create an attribute called Channel for the Product dimension.
Channel can have values of retail outlets, catalog, and internet. You then assign the
values of either retail outlets, catalog, or internet to members of the Product dimension.
You can filter members by their attribute values when creating data forms and reports.
N OT E
Only sparse dimensions can contain attributes. You must assign attribute values
to dimension members at the same level within a dimension. Data values for
attribute values are dynamically calculated and not stored.
Working with Attributes

To Set Up Attributes:
2. From the Dimension drop-down list, select the dimension for which to create
attributes.
3. Select the dimension name, such as Customer or Product.
4. Click Custom Attributes.
5. By the Attributes in dimension column, Click Create.
6. Enter the name of the attribute.
7. Optionally, press Enter if you have more attributes to enter.
8. Click Save when you are finished adding attributes.
9. When done saving new attributes click Cancel to close the Create Attributes dialog
box.
10. Select the attribute for which you want to enter values, and click Create above the
attribute values column.
11. Enter the value for the attribute.
12. Optionally, press Enter if you have more values to enter.
13. Click Save when you are finished adding attribute values.
14. When done saving new attribute values click Cancel to close the Create Attribute
Value dialog box.
15. Click Close to close the Manage Attributes and Values window.
To Assign Attribute to Members:
1. From the Dimension drop-down list, select the dimension for whose member you
want to assign an attribute value.
2. Select the member to which to assign an attribute value.
3. Click Edit.
4. Select Attribute Values.
5. From the Attribute Values list, select the attribute value to assign to the member and
then click Add and Save.

B-25
Creating Alias Tables
You can assign one or more alternate names, or aliases, to Planning Account, Currency,
Entity, Scenario, Period, Version, Year, and user-defined dimension members. You can
create up to ten aliases per dimension member, including the default alias.
For example, members in the Account dimension may be identified by their number (100,
200, 300, and so on) or by their descriptive alias (Travel Expenses, Office Supplies,
Consulting Fees). Members could also have aliases for different languages.
You create alias tables from the Administration menu. You set up aliases for members on
the Member Properties tab in the Dimension Editor. If you add or change aliases or alias
tables, you must refresh the application.
Administrators can set which alias table to display by default for the application in
Application Settings. Business users can override the default selection by choosing the
alias table from the Preferences option on the File menu.
Creating Alias Tables

To Create Alias Tables:
1. Select Administration > Alias Tables.
2. Click Add.
3. Enter the name for the alias table, and click OK.
To Set Up Aliases for Members:
2. From the Dimension drop-down list, select a dimension.
3. Select the member in the hierarchy for which you want to set up an alias.
4. Click Edit.
5. On the Member Properties tab, from the Alias drop-down list, select the alias table.
6. For the alias value, enter a value.
7. Click Save.

B-27
Smart Lists Overview
Administrators use Smart Lists to create custom drop-down lists that business users
access from data form cells. For cells whose members are associated with smart lists,
data cannot be entered by typing a value. Instead, you select a value from a drop-down
list.
After you click in a cell that is associated with a smart list, you can click on the arrow to
expand the smart list. You can then select one of the Smart List options as the value for
the cell.
You can create reports to capture the smart list information entered. You need to use
planning details as your data source to report on smart list data.
Smart Lists Overview

Smart List Creation Process
Administrators can set up smart lists. After you create the smart list, you assign the smart
list to dimension members as a member property.
After the smart list has been created and assigned to the dimension member, you can
use smart lists on data forms, by selecting the dimension member for the data form.
For example, if you have an account called ProjectCat to represent project categories
and you assigned a smart list (Project_Category) to that account, you would select
ProjectCat as the account member to show on the data form.
Smart List Creation Process
1. Create the Smart List:
1. Set up Smart List properties.
2. Set up Smart List entries.
2. From the Dimension Editor, create a new member or use an existing
member:
1. Set the Member Properties for the member and associate the new member
with the Smart List.
2. Refresh the Planning Database.
3. Set up the Smart List to work on a data form

B-29
Creating Smart Lists
You use the Smart Lists page to create, edit, and delete Smart Lists. You create smart
lists by assigning values on the Properties, and Entries tabs and can review your smart
list by selecting the Preview tab. You add values on the Entries tab to define the
selections in the Smart List.
To create Smart Lists:
1. Select Administration > Manage Smart Lists.
2. Click Create, enter a name, and click OK.
Creating Smart Lists

To Set Up Smart Lists:
1. Select the Smart List, and click Edit.
2. Set up the Smart List properties.
3. Select Entries.
4. Click Add.
5. If you selected to automatically generate the numeric ID then do the following:
Type the Name
Type the Label
6. If you did not select to automatically generate the numeric ID then do the following:
Type the ID
Type the Name
Type the Label
7. Select the Preview tab to review your smart list.
8. To save the smart list, click Save.

B-31
Associating Smart Lists
After you create and set up Smart Lists, you associate Smart Lists to members as a
member property. You then modify data forms to include the member. Business users
working with the data form click into cells whose members are associated with a Smart
List, and select from a drop-down list instead of entering data.
Associating Smart Lists
Smart lists are associated
with members from a
dimension, typically the
Account dimension
Reserve the member to
store smart list values and
do not use that member to
enter any regular data
values
Consider setting up a
separate rollup within the
dimension for the
members for which smart
lists are assigned
Place the member
representing the Smart
List onto data forms

Setting Up UDAs
You can use user-defined attributes (UDAs)words or phrases describing a
characteristic of memberswithin calc scripts, member formulas, and reports to return
lists of members associated with the specified UDA. For example, say you have a
Product dimension Using Smart Lists, UDAs, and Member Formulas with various
product members. You could create a UDA called New Products and base certain
calculations only on new products.
UDAs are specific to dimensions. For example, creating a UDA for an Account member
makes it available for non-shared Account members. Deleting it removes it for all
Account members.
To make UDAs available for multiple dimensions, create the same UDA for multiple
dimensions. For example, create a UDA named New for Account and Entity dimensions
to make the UDA named New available for Account and Entity members.
You create, change, and select UDAs for members from the UDA tab.
Setting Up UDAs
Set up UDAs to group members
Create and Assign UDAs
in the Dimension Editor

B-33
To Create UDAs:
2. In the Dimensions drop-down list, select the dimension for whose member to create
the UDA.
3. From the dimension hierarchy, select a member, and click Edit.
4. Navigate to the UDA tab.
5. On the UDA tab, click Add.
6. Enter a name and click Save.
To Select UDAs for members:
1. Select the UDAs for the member and move them to the Selected UDA window.
2. Click Save.

Setting Up Member Formulas
You use the Member Formula tab to set up formulas to combine operators, calculation
functions, dimension and member names, and numeric constants to perform calculations
on members. You can set up member formulas to calculate data differently than what is
represented in the outline structure.
For example, gross profit and net sales are calculated by accumulating data from
members in the Essbase outline. In order to calculate profit percent, you create a
member formula which uses the gross profit and net sales members.
N OT E
You must place a semicolon at the end of each member formula.
Setting Up Member Formulas
Profit Percent = Gross Profit%Net Sales;

B-35
Data Integration Management
Data Integration Management provides bi-directional data movement from ERP and
CRM applications to multiple applications, such as Essbase, Planning, Financial
Management, and query and reporting applications.
Data Integration Management
Integrate ERP and transaction
processing applications with
analytic applications
Link relational databases,
applications, and text files with
EPM Architect applications
Ensure data consistency

Planning Adapter Overview
The Planning adapter enables you to connect between the PowerCenter server and the
Planning Server. It is compatible with all Planning modules including Workforce Planning
and Capital Expense Planning.
The Planning Adapter enables you to perform the following tasks:
Load metadata into attribute and custom dimensions in Planning
Create UDA (User Defined Attribute) dimension targets
N OT E
You can use the Essbase adapter to extract data and metadata from Planning
dimensions.
Planning
Planning Adapter Overview
Repository
Workf low Manager
Workflow Monitor
Designer
Essbase Adapter
Source/Target
DSN
Repository
Server
PowerCenter
Server
Planning Adapt er

B-37
Working with Planning Targets
You create a Planning target to specify where and how to load information into Planning.
For example, you can specify a target to load metadata into the Account dimension
within Planning.
Working with Planning Targets
You must configure the following objects before you can import
Planning targets:
Planning data source names
Planning target definitions
User defined attribute targets

Creating Planning DSNs
Before you can import Planning targets into a Data Integration Management repository,
you must create a data source name (DSN) to connect to Planning.
DSNs are records that store sets of information. The information is used to query data
from Planning databases. DSNs store elements such as Planning Server names and
user IDs and passwords of Planning users who can access the data of the queried
databases.
DSNs are part of Planning target definitions. You can use one DSN to create multiple
source or target definitions.
Creating Planning DSNs
2
3
1

B-39
Importing Target Definitions
After you create a Planning DSN, you use Warehouse Designer to import Planning target
definitions. The Import from Hyperion Planning command enables you to identify the
Planning tables that you will load information into.
Each target table has specific ports for loading data into Planning. For example, in the
Entities table, you use the Entity port to specify the entity that you are loading, the Parent
port to specify the entity parent, and the Default Alias port to specify an alternate name.
The Planning Adapter enables you to write to the following table types:
Accounts
Employees
Entities
Attributes
UDAs
Importing Target Definitions

Creating UDA Targets
You can import User Defined Attribute (UDA) targets into Planning. When you create a
Planning UDA target, the default table name is Planning_UDA.
UDAs are associated with members of an outline to describe a characteristic of the
members. Users can specify UDAs within calculation scripts and reports so that they
return lists of members that have the specified UDA associated with them.
The UDA table ports are Dimension (required), UDA, and Operation.
In the Dimension port, you enter the dimension name for the UDA. When you load
metadata to a planning database, If the UDA already exists, its properties are modified,
otherwise the record is added.
The UDA port value must meet the following requirements:
Alphanumeric
80 characters or less
Creating UDA Targets

B-41
Not a word reserved for Essbase
UDA name:
- No tabs, double quotation marks (), or backlash (\) characters
- Cannot start with the following characters: \ < , = @ _ + - { } ( )
The Operation port defaults to the Update value, but you can use the following values as
well:
Update - Adds, updates, or moves the member being loaded.
Delete Level 0 - Deletes the member being loaded if it does not have children.
Delete Idescendants - Deletes the member being loaded and its descendants.
Delete Descendants - Deletes the descendants of the member being loaded, but
does not delete the member.

Loading Metadata to Planning
After you define Planning targets, you can use them to load metadata to Planning. To do
this, in Designer, create a mapping that includes a Planning target. In Workflow Manager,
create a Planning application connection and Planning workflow, and configure the
workflow session task.
Loading Metadata to Planning
To load metadata to Planning, you perform the following tasks:
In Designer, create a mapping
In Workflow Manager:
Create a Planning connection
Create a workflow and configure the session task

B-43
Creating Planning Connections
Using the Hyperion Planning connection type, you create runtime Planning application
connection objects. You use these objects when you map a session.
To create a Planning connection:
1. In the Workflow Designer, select the Application connection type.
2. In the Application Connection Browser, select the Planning connection type.
3. In the Application Connection Editor, enter Planning connection attributes.
Creating Planning Connections
1
3
2

Configuring Session Tasks
Once you have mapped a session task within a workflow, you must configure the task
with the proper connections. In this example, the target connection type is Hyperion
Planning Application connection.
To configure session tasks:
1. In Workflow Designer, create a workflow.
2. Right-click the session task and select Edit.
The Edit Tasks window is displayed.
3. Select the Mapping tab to ensure that the correct connections are specified for the
target and source.
4. Click OK.
Configuring Session Tasks
1
2
3

B-45
Summary
Describe classic administration
List the steps for creating Planning applications
Create Planning applications using classic application administration
Set up dimensions and members in Planning
Load metadata files


Hyperion Planning 9.3.1 (Guide) 2

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Hyperion Planning 9.3.1 (Guide) 2

Enviado por

Direitos autorais:

Formatos disponíveis

Hyperion Planning 9.3.

Você também pode gostar