Beruflich Dokumente
Kultur Dokumente
1:
Create and Manage Applications
m y
Volume I Student Guide
d e
ca
e A
c l
r a
O ly
l & On
D70015GC10
n a e
Edition 1.0
September 2008
t e r U s
D56305
I n
c l e
r a
O
Authors Copyright 2008, Oracle. All rights reserved.
Suzanne Gill This document contains proprietary information and is protected by copyright and
Theresa Songco other intellectual property laws. You may copy and print this document solely for your
own use in an Oracle training course. The document may not be modified or altered in
any way. Except where your use constitutes "fair use" under copyright law, you may
Technical Contributors not use, share, download, upload, copy, print, display, perform, reproduce, publish,
and Reviewers license, post, transmit, or distribute this document in whole or in part without the
express authorization of Oracle.
Emilya Altman
The information contained in this document is subject to change without notice. If you
Guillaume Arnaud find any problems in the document, please report them in writing to: Oracle University,
Jacob Bogitar 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Bryan Dehmler-Buckley
Suzanne Gill Restricted Rights Notice
Vicki Hardiman If this documentation is delivered to the United States Government or anyone using
Art Hetherington the documentation on behalf of the United States Government, the following notice is
applicable:
Janette Hollar
Sasha Ishenko U.S. GOVERNMENT RIGHTS
The U.S. Governments rights to use, modify, reproduce, release, perform, display, or
Sandy Krameisen
disclose these training materials are restricted by the terms of the applicable Oracle
Diana Kravets license agreement and/or the applicable U.S. Government contract.
Robert Mead
Trademark Notice
Saju Philips
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
Ronald Reiley
names may be trademarks of their respective owners.
Eleanor Salerno
Theresa Songco
m y
Shankar Viswanathan
Stuart Weiner
d e
Editor
c a
Susan Moxley
e A
Graphic Designer
c l
Asha Thampy
r a
Publisher
O ly
Sandy Krameisen
l & On
n a e
t e r U s
I n
c l e
r a
O
Table of Contents 1
m
Planning and Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 y
d e
Planning Repository and Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
c a
Dimension Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
e A
Dimensions and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Multidimensional View of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
l
Drill-Down Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
c
r a
Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Essbase TerminologyHierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
O ly
Essbase TerminologyFamilies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
& On
Essbase TerminologyGenerations and Levels . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
l
Lesson 2: Navigating Workspace
n a e
e r s
Workspace Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
t U
I n
Launching Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Workspace User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
l e
Workspace Navigate Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
c
Opening Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
r a
Navigating in Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
O Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Basic and Advanced Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Table of Contents
l
Selecting Aggregation, Storage, and Calculation Options . . . . . . . . . . . . . . . . . . . . . 3-17
c
r a
Selecting Aggregation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Selecting Data Storage Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
O ly
Calculating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
l & On
Calculating Data with Two-Pass Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Determining Performance Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
n a e
t r U s
Lesson 4: Managing Dimensions with Performance Management Architect
e
About Dimension Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
I n
Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
c l e
Application Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Applications Using Performance Management Architect . . . . . . . . . . . . . . .
4-3
4-4
r a
Adding Dimensions to Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Shared and Local Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-5
4-7
OCreating Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
m y
Adding Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
d e
Number Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
c a
Triangulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
A
Reporting Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Creating Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
e
l
Automating Performance Management Architect Tasks . . . . . . . . . . . . . . . . . . . . . . 4-40
c
r a
Lesson 5: Setting Up the Period, Year, Scenario, and Version Dimensions
O ly
Creating Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
l & On
Period and Year Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
a e
Dynamic Time Series Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
n
t e r
Setting Up DTS Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
s
Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
U
I n
Creating Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Enable Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
l e
Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
c
Use Beginning Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
r a
Exchange Rate Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
O ly
Creating Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
l & On
Attribute Values: Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Assigning Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
a e
Member Formulas Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
n
t e r U s
Adding Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Adding User-Defined Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
I n
Smart Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
l e
Modifying Smart Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
c
Associating Smart Lists with Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
O
iv Planning: Create and Manage Applications
Table of Contents
d
Lesson 10: Creating Applications
c a
e A
Application Creation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Plan for Application Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
c l
Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
r a
Currency Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
O ly
Setting Up Application Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
l & On
Selecting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
n a e
Adding Dimensions from Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
t e r U s
Changing Local Dimensions to Shared Dimensions . . . . . . . . . . . . . . . . . . . . . 10-19
Overriding Property Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
I n
Excluding and Showing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
l e
Filtering Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Synchronizing Local Dimensions with Shared Library . . . . . . . . . . . . . . . . . . . . 10-26
c
r a
Activating Dimension Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28
Adjusting Performance Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
O
Planning: Create and Manage Applications v
Table of Contents
c a
Copy Rates Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
e A
Currency Conversion Calculation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Calculate Currencies Business Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
c l
r a
Module 4: Loading Data and Calculating the Database
O ly
Lesson 13: Loading and Calculating Data: Overview
l & On
Data Loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
n a e
Requirements for Data Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
t e r U s
Multicurrency Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Data Load Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
I n
Data Staging: Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Loading Data Using ETL Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
l e
Data Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
c
r a
Calculations Within Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Calculations and Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
c a
Levels of Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
A
Task Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
e
c l
Object Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
r a
User and Group Provisioning Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
O ly
User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Application Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
& On
Provisioning Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
l
n a e
User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Generating Provisioning Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
t e r U s
Lesson 16: Setting Up Access Rights to Planning Applications
I n
Assigning Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
l e
Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
c 16-3
r a
Inheritance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Precedence and Inheritance of Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . .
16-5
16-7
O
Planning: Create and Manage Applications vii
Table of Contents
A
Setting Options on the Other Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Identifying Missing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
e
l
Selecting Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
c
r a
Previewing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24
Creating Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
O ly
Selecting Business Rules on Composite Data Forms . . . . . . . . . . . . . . . . . . . . 17-27
l & On
Printing Data Form Definition Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28
Assigning Access Rights to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
a e
Assigning Data Form Folder Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31
n
t e
Lesson 18: Customizing Data Formsr U s
I n
Exporting and Importing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
l e
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
c
Creating Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
c a
Data-Entry Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
A
Viewing Form Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Recognizing Cell Color Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
e
l
Navigating Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
c
r a
Copying and Pasting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Working with Non-Aggregated Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-13
O ly
Saving and Refreshing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
l & On
Viewing Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Selecting Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16
a e
Launching Dimension Editor from Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
n
t e r U s
Spreading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18
Time Balance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20
I n
Spreading Data by Using Grid Spreader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-22
Spreading Data by Using Mass Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-23
l e
Adjusting and Annotating Plan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25
c
Performing Flexible Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
r a
Adding Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
O
Planning: Create and Manage Applications ix
Table of Contents
c a
Entering Data in Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-11
Adding Formulas to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
A
Calculating Data in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
e
c l
Working with Ad Hoc Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
Navigating Ad Hoc Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
r a
Zooming In and Out on Dimension Members . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
O ly
Pivoting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-19
Keeping and Removing Dimension Members . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21
l & On
Working with POVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-22
a e
Smart View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
n
t e r
Submitting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
s
Working Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
U
I n
Taking Data Forms Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-28
Working with Planning Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-30
l e
Synchronizing Data to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32
c
r a
O
x Planning: Create and Manage Applications
Table of Contents
d e
Lesson 22: Managing Business Rules
c a
e A
Templates Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Creating Custom-Defined Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
c l
Creating Business Rules with Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6
r a
Setting Up the Copy Data Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
Setting Up the AmountUnitRate Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
O ly
Setting Up the AllocateLevel to Level Template. . . . . . . . . . . . . . . . . . . . . . . . 22-12
l & On
Setting Up the Aggregation Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-14
Creating Rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-16
n a e
Validating Business Rulesets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-17
t e r U s
Deploying Business Rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-19
I n
Lesson 23: Adding Variables and Formulas to Business Rules
l e
Creating Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
c
Setting Up Runtime Prompt Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4
r a
Creating Formula Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9
O
Planning: Create and Manage Applications xi
Table of Contents
c a
Clearing Cell Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-22
A
Copying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-25
e
Lesson 25: Creating Task Lists
c l
r a
Task Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2
O ly
Navigating Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4
Navigating Task Lists in Basic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5
& On
Navigating Task Lists in Advanced Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8
l
n a e
Task List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-11
Working with Task List Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12
e r s
Building Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-14
t U
Adding Tasks to Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-15
I n
Setting Up Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-16
l e
Setting Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-18
c
Assigning Access to Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-19
r a
Using Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-20
Reporting on Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-21
O
xii Planning: Create and Manage Applications
Table of Contents
d e
Viewing LCM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-29
c a
Migration Status Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-30
Artifact Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-32
e A
Module 10: Creating Classic Applications
c l
Lesson 27: Building Classic Applications
r a
O ly
Classic Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-2
& On
Classic Planning Application Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-3
l
n a e
Relational Databases for Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-5
Configuring Data Sources in Classic Application Wizard. . . . . . . . . . . . . . . . . . . . . . 27-6
e r s
Creating Applications Using Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . 27-8
t U
Working with Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-9
I n
Selecting the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-10
l e
Setting Up the Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-11
c
Setting Up Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-13
r a
Setting Up Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-15
Completing Application Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-16
O
Planning: Create and Manage Applications xiii
Table of Contents
e A
Business Rules Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4
Navigating Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-6
c l
Components of Enterprise View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-6
r a
Components of BR Language Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-7
Navigating the Rule Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-8
O ly
Business Rules Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-9
l & On
Creating Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-11
Building Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-12
n a e
Adding Actions to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-14
t e r U s
Adding the Aggregate Data Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-14
Adding the Copy Data Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-15
I n
Adding the Clear Data Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-16
c l e
Adding the Create Blocks Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-16
Adding Formulas to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-17
y
Setting Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Applying Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
m
d e
Inserting Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Validating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
c a
Viewing Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Executing Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications xv
Table of Contents
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
xvi Planning: Create and Manage Applications
Preface 0
m y
Course Objectives
After completing this course, you should be able to:
d e
Create Planning applications
ca
Load data into Planning applications
e A
c l
Set up security for users, groups, and members
r a
Create data forms and enter data by using data forms
O ly
Set up and test business rules
l & On
Review budget data by using process management
n a e
t e r U s
I n
c l e
r a
O
Preface
Course Structure
Oracle Hyperion Planning 11.1.1: Planning: Create and Manage Applications is a 5-
day, instructor-led training course consisting of lectures, demonstrations, and hands-on
exercises. In this course, the instructor presents a topic conceptually by explaining its
purpose, demonstrating how it works, and then guiding the students through the
exercises. Demonstrations and hands-on exercises reinforce the concepts and skills
introduced during lectures.
Course Materials
You use two books in 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 10 modules:
Module 1 describes an overview of Planning and navigating Workspace.
Module 2 describes setting up dimensions and members.
m y
Module 3 describes importing dimension members using EPM architect.
d e
Module 4 describes loading data and calculating the database.
c a
Module 5 describes setting up security.
e A
l
Module 6 describes designing data forms.
c
a
Module 7 describes entering data in Planning.
r
O ly
Module 8 describes adding business rules.
& On
Module 9 describes managing the planning process.
l
a e
Module 10 describes setting up Classic applications.
n
t e r s
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
U
n
the topics covered in the lesson.
I
c l e
r a
O
xviii Planning: Create and Manage Applications
Preface
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.
m y
When available, figures are used to identify an object or task. Example:
d e
Click Edit.
c a
e
Keyboard shortcuts are displayed as follows: Ctrl+Enter A
c l
Alerts are used to direct your attention to different types of information.
NOTE
r a
O ly
A note provides related information, common mistakes, or
& On
cautions about the current topic.
l
n a e
TIP
t e r s
A tip provides information that helps you work more
U
n
efficiently.
I
c l e
r a
O
Planning: Create and Manage Applications xix
Preface
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
xx Planning: Create and Manage Applications
M O D U L E 1
Getting Started 1
Overview
The aim of this module is to provide an overview of the product features,
capabilities, components, and architecture of Planning. You also learn
about the relationship between Planning and Essbase. You navigate the
Workspace and access Planning using Workspace.
Lessons in this module include:
Planning Overview
Navigating Workspace
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
L E S S O N 1
Planning Overview 1
Objectives
At the end of this lesson, you should be able to:
Explain Oracles Enterprise Performance Management system
Describe Hyperion components
List the main features of Planning
Describe the product architecture of Planning
Explain the relationship between Planning and Essbase
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 1 Getting Started
Lesson 1 Planning Overview
EPM Workspace
Performance Management
Applications BIBIApplications
Applications
Fusion Middleware
m y
OLTP & OD S
Sy ste ms
D ata Wa rehouse
D ata Ma rt
OLA P S AP, Or ac le , Siebe l,
Pe ople Soft, C us tom
Ex ce l
XML
e
B usine ss
d
Pr oc es s
r a
Oracles Enterprise Performance Management system is a portfolio of technology and
applications that include category-leading financial performance management
O ly
applications, operational BI applications, BI foundation and tools, and data warehousing.
l & On
It also leverages Oracles Fusion Middleware technologies, such as Oracle Application
Server and Oracle Identity Management.
It has these characteristics:
n a e
t e r U s
PervasiveIt enables all levels of your organization to see information optimized for
their role.
I n
c l e
ComprehensiveIt incorporates information from your financial performance
management, operational intelligence, and transactional applications.
r a
O
1-2 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
r a
Relationship Management system), and third party systems such as SAP (Enterprise
O ly
Resource Planning system). Applications include:
Oracle Financial Analytics
l & On
Oracle HR Analytics
n a e
t e r U s
Oracle Order Management and Fulfillment Analytics
Oracle Supply Chain Analytics
I n
Oracle Sales Analytics
l e
Oracle Service Analytics
c
r a
Oracle Contact Center Analytics
O
Planning: Create and Manage Applications 1-3
Module 1 Getting Started
Lesson 1 Planning Overview
Fusion Middleware
Fusion middleware provides an open, comprehensive, standards-based approach for
deploying service-oriented architectures (SOAs) using Web services, an enterprise
service bus, and Oracle BPEL (Business Process Execution Language) Process
m y
d e
Manager. Its portfolio includes products for integration, business process management,
O ly
Oracle Collaboration Suite (e-mail and content management)
& On
Oracle Identity and Access Management Suite (identity management)
l
a e
Oracle WebCenter Suite (context-rich user interface with Web 2.0)
n
t e r U s
Oracle SOA Suite (business rules, process deployment, Java development, business
activity monitoring with dashboards and alerts, application integration over the
I n
Internet and across other applications)
l e
Oracle Portal (out-of-the box enterprise portal)
c
r a
O
1-4 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Planning Features
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Planning Features
c l
r a
Planning is a Web-based budgeting and planning solution that drives collaborative,
event-based, operational planning processes through the organization for a wide range
O ly
of financial and operational needs. Planners have the flexibility to adapt rapidly to
& On
changes in direction, ensuring that plans are always current, relevant, and functional.
l
collection and analysis.
n a e
Powered by Essbase, Planning uses a multidimensional data structure for flexible data
t e r U s
Planning also supports driver-based plans that are based on global assumptions, such
n
as interest rates and head count.
I
c l e
r a
O
Planning: Create and Manage Applications 1-5
Module 1 Getting Started
Lesson 1 Planning Overview
Product Components
Planning
Essbase
Administration Services
Workspace
Performance Management Architect
Calculation Manager
Smart View
Financial Reporting
Shared Services
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Product Components
c l
r a
You use the Planning Web interface to deploy applications to planning organizations. To
extend the power and flexibility of Planning, you use it with other Hyperion products.
O ly
Product
Essbase
l & On
Description
Enables you to store Planning application data (Planning
c l
Architect e
Performance Management Enables you to manage dimensions and applications.
O ra
Workspace Enables you to navigate and manage Planning applications
Product Description
Calculation Manager Enables you to use a graphical user interface to create
calculation scripts
Smart View Enables you to enter Planning data in Microsoft Excel
spreadsheets, using the same functionality as Planning,
and to take Planning data offline to work disconnected from
the data source
Financial Reporting Enables you to create reports and charts for Web or print
for analysis and distribution of budget plans
Shared Services Enables you to provision users from external systems to
Hyperion products and to share data and metadata among
Planning applications or between Planning and other
Hyperion products
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 1-7
Module 1 Getting Started
Lesson 1 Planning Overview
Related Products
Workforce Planning
Capital Asset Planning
Performance Scorecard
Strategic Finance
Financial Management
Web Analysis
Modeling
Planning, Budgeting,
and Forecasting
Consolidation
and Reporting
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Related Products
c l
r a
Several complementary Hyperion products are integrated with Planning, completing the
Financial Performance Management solution.
Product O ly
Description
Workforce Planning
l & On
Enables you to handle workforce, salary, and compensation
n a e
planning
Capital Asset Planning
t e r s
Enables you to plan for new asset purchases and existing
asset actions
U
Performance Scorecard
c l e
Strategic Finance Enables you to easily test financial models, create
contingency plans, and form alternative strategies
r a
O
1-8 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Product Description
Financial Management Enables you to consolidate results, reduce the cost of
regulatory reporting compliance, and gain important insights
into performance
Web Analysis Enables you to transform data into insightful information
through easy-to-use, highly graphical displays and robust
analytics
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 1-9
Module 1 Getting Started
Lesson 1 Planning Overview
Planning Architecture
Web
Application
Financial Shared Services, Java Performan ce Planning Web EPMA Web
Reporting Server App lication Server for Management Server Server
Planning , Perfo rmance Architect
Managemen t Architect, Dimension Server
Administration Services
Database
m y
Performance Management
Architect RDBMS
Plann ing
RDBMS
Essbase
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Planning Architecture
c l
r a
Planning is a multitier application that combines the advantages of Essbase (a
multidimensional database) and a relational database to optimize performance and
maintenance.
O ly
l & On
Client Tier
n a e
t e r
The client tier contains the Smart View client and the Offline client.
U s
Planning administrators use the client tier to enter data, perform process management,
I n
manage users and security, launch business rules, copy versions, develop data forms,
and perform other administrative tasks.
c l e
In the client tier, you can enter data through spreadsheets by using Smart View.
r a
O
1-10 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Database Tier
The database tier consists of a third-party relational database management system
(RDBMS) and Essbase. The relational database is used primarily to store the
m y
applications definition. The following information is stored in the RDBMS:
d e
Application framework*
c a
Dimensions, dimension members, and properties*
e A
Exchange rates*
c l
Member access (security filters)*
Data form design definitions r a
Planning units O ly
l & On
Annotations (planning unit, account, and cell text)
Supporting details*
n a e
t e r s
Process management workflow status
U
Job Status
I n
l
NOTE
c e
Items with an asterisk (*) are updated to the Essbase databases during
r a application refreshes.
O
Planning: Create and Manage Applications 1-11
Module 1 Getting Started
Lesson 1 Planning Overview
User Roles
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
User Roles
c l
r a
Planning meets the needs of multiple users within an enterprise-wide budgeting cycle.
You can set up users with several different types of user profiles to reflect the necessary
access.
O ly
& On
The following global Shared Services roles are also used in Planning:
l
a e
Application Creator Creates applications. This is a Performance Management
n
Architect role.
t e r U s
LCM Administrator Runs the Artifact Lifecycle Management utility to promote
I n
artifacts or data across product environments and operating systems. You can work
with Lifecycle Management to move artifacts between development, test, and
l e
production environments. Information on Lifecycle Management will be covered in
c
another lesson.
r a
O
1-12 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 1-13
Module 1 Getting Started
Lesson 1 Planning Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Performance Management Architect
c l
r a
Performance Management Architect is a feature set in Planning that enables budget
administrators to view, manage, create, validate, and deploy applications within one
O ly
interface. You maintain metadata and applications in a central repository. To populate
& On
dimensional metadata, you can import the metadata from flat files or interface tables.
l
n a e
Using the Data Synchronization feature in Performance Management Architect,
administrators can create data movement synchronizations between Hyperion
t e r U s
applications, create data mappings for reuse, and create flat file and staging area
mappings to import data into Hyperion applications.
I n
You create and manage business rules with Performance Management Architects
l e
graphical rule designer - Calculation Manager. You can design, validate, and administer
c
business rules in a central repository for use in Planning, and Financial Management
r a
applications. You can set up reusable components that can be used by different
applications. Predefined templates are provided for frequently used calculations.
O
1-14 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Planning Interface
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Planning Interface
c l
r a
You use Workspace to access Planning. Administrators and Interactive Users can
provide flexibility and user guidance to budget preparers (planners) by defining user
O ly
variables and task lists. You can also define data forms for data entry and assign access
& On
to the appropriate users and groups.
l
n a e
Budget administrators, budget analysts, and budget preparers can all enter and submit
data for review and approval, run business calculations, and enter annotations.
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 1-15
Module 1 Getting Started
Lesson 1 Planning Overview
Performance
Management
Architect Repository
Workspace
Interface Pl anni ng
Repository
Java Application
Ser ver
m y
e
Essbase Server
d
Copyright 2008, Oracle. All rights reserved.
c a
e A
Planning and Essbase
c l
r a
Planning uses Essbase to store data, metadata, and as a rules engine. To store the data,
you also store the dimension hierarchies in Essbase so that Essbase maintains the
relationships for the data values.
O ly
l & On
When you deploy an application, Performance Management Architect creates tables and
n a e
appropriate values in your Planning relational database, creates an application and
outline in Essbase without the need to refresh the cube within the Planning Interface,
e r s
and creates the HSP_Rates dimension for multicurrency applications.
t U
I n
Planning stores the application definition in its own relational databases. It uses the
definition information to create the necessary Essbase databases and security privileges
l e
for your application. The plan data that end users enter in a Planning application is
c
stored in the Essbase databases created for the application.
r a
Prior to application deployment, Performance Management Architect stores the
Data Forms
User Variables
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Planning Repository and Essbase
c l
r a
Dimensions and members are stored in the Essbase databases as well as the Planning
repository. Data values are stored in Essbase. Some information is stored only in the
O ly
Planning relational database. For example, planning unit annotations, account
l & On
annotations, cell text, and supporting details are stored in the Planning relational
database. You can report on these annotations and details with Financial Reporting.
n a e
Smart list information is stored in the relational database. After you enter a smart list
t
member is stored in Essbase.e r U s
value into Planning and save the data, the numeric value associated with that smart list
I n
c l e
r a
O
Planning: Create and Manage Applications 1-17
Module 1 Getting Started
Lesson 1 Planning Overview
Dimensions
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Dimensions
c l
r a
Dimensions are the structural elements of an application that describe and hold data.
Examples of dimensions are Account, Entity, and Period.
O ly
The elements that compose a dimension are called members. For example, California
& On
and Connecticut are members of the Entity dimension.
l
a e
The dimensions defined in a Planning application become the dimensions in the
n
t e r
Essbase outlines and databases.
U s
I n
c l e
r a
O
1-18 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Dimension Hierarchies
Parent
Child of GrossMargin;
parent of Sales and
OtherRevenues
Descendants
of GrossMargin
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Dimension Hierarchies
c l
r a
Members of a dimension are arranged in hierarchies. Members in a hierarchy exist at
different levels. Some members, siblings, are at same level and have relationships to
other members of the hierarchy.
O ly
& On
Upper-level members are called parent members, and the members immediately below
l
n a e
the parent members are referred to as their children. All members below a parent are
referred to as descendants. The bottom-level members of a hierarchy are called base-
level members.
t e r U s
I n
The graphic on the slide shows a part of the dimension hierarchy of the Account
dimension. In this hierarchy, the TotalRevenues member is a child of GrossMargin. Sales
l e
and OtherRevenues are children of TotalRevenues and descendants of GrossMargin.
c
Sales and OtherRevenues are also base-level members.
r a
O
Planning: Create and Manage Applications 1-19
Module 1 Getting Started
Lesson 1 Planning Overview
Data aggregated
to parents based on
aggregation options.
+ Add
Data is input
into base-level - Subtract
members. * Multiply
/ Divide
~ Ignore
Never
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Dimensions and Data
c l
r a
Data is entered into the base-level members of the dimensions, not into the parent
members, unless you are working with a target version. You use target versions to
O ly
perform top-down budgeting by setting targets at the parent level. The values for the
l & On
parent-level members are aggregated from the values of their children when the
Planning database is calculated in Essbase.
n a e
For the example shown on the slide, the data values from the base-level members are
t e r U s
rolled up to the parent-level members. TotalRevenues (+) and TotalCosts (-) are then
rolled up to their parent GrossMargin.
I n
c l e
r a
O
1-20 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
m y
d e
c a
e A
Multidimensional View of Information
c l
r a
For the example shown on the slide, each cube represents a different view of a five-
dimensional database. The highlighted portion in each cube indicates the same data
value.
O ly
& On
Data is represented in multidimensional form, and hierarchies are represented within
l
another form of the data.
n a e
each dimension. As your analytical needs change, you can switch easily from one to
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 1-21
Module 1 Getting Started
Lesson 1 Planning Overview
Drill-Down Process
Income All
Year Worldwide
Statement Customers
O perating
New York
Margin
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Drill-Down Process
c l
r a
Drilling down is an analytical technique by which you navigate through levels of data,
ranging from the most summarized (top) to the most detailed (bottom).
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
1-22 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Metadata
3689.00 Data
Metadata
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Metadata
c l
r a
Metadata is defined as the structural elements of an application that describe and hold
data. Examples of metadata are dimension names, member names, properties, and
security.
O ly
& On
For the example shown on the slide, the circled dimension member labels are the
l
a e
metadata. The metadata describes what the data value represents.
n
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 1-23
Module 1 Getting Started
Lesson 1 Planning Overview
Essbase TerminologyHierarchies
Outline
Dimensions
Members
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Essbase TerminologyHierarchies
c l
r a
Essbase uses hierarchical and familial terms to describe the roles and relationships of
members in an outline. Within the tree structure of the database outline, a consolidation
O ly
is a group of members in a branch of the tree.
Hierarchical Term
l & On
Definition
Outline
n a e
Representation of the relationship among the members in the
Dimension
t e r U s
database
Perspective on the data being analyzed
Member
I n Discrete component making up a dimension
Attribute
c l e
Attribute dimension
Characteristic of a member in an outline
Dimension tagged as an attribute that contains members that
O
1-24 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Essbase TerminologyFamilies
Dimension Period
Year Total
Qtr1 Ancestors of April
Siblings
Descendants of Qtr2 Parent of April
Year Total
April Child of Qtr2
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Essbase TerminologyFamilies
c l
a
The following table summarizes the common familial terminology used in Essbase.
r
Familial Term
O ly
Definition
Descendant
& On
Any member in a branch below a member
l
Ancestor
a e
Any member in a branch above a member
n
Parent
Child
t e r
Member that is the immediate ancestor of a member
U s
Member that is the immediate descendant of a member
Sibling
I n Child member with the same parent as another member
c l e
r a
O
Planning: Create and Manage Applications 1-25
Module 1 Getting Started
Lesson 1 Planning Overview
Gen 1 Level 3
Gen 2 Level 2
Gen 3 Level 1
Gen 4 Level 0
Leaf Node
Gen 3 Level 0
n
Leaf node
t e r U s
Member that has no children
The term generation describes a members location within the outline hierarchy from a
I n
particular perspective. The generation number identifies the branch on which the
e
member lies in reference to its distance from its dimension name. Generations are
l
absolute and are determined by counting from the top of their dimension to their
c
descendants.
r a
O
1-26 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 1 Planning Overview
Level describes a members location in the outline, counting from the bottom to the top.
Levels are a relative and the level depends on the starting point in the hierarchy. The
example on the slide shows a portion of an outline labeled by both generation and level.
Customer is always generation 1, while its level changes based on the starting point in
the hierarchy. For example, if N002 is the starting point for determining the level,
Customer is level 3 whereas if No Customer is the starting point for determining the level,
Customer is level 2.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 1-27
Module 1 Getting Started
Lesson 1 Planning Overview
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
1-28 Planning: Create and Manage Applications
L E S S O N 2
Navigating Workspace 2
Objectives
At the end of this lesson, you should be able to:
Launch Workspace
Describe the user interface components
Open applications
Navigate Planning
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 1 Getting Started
Lesson 2 Navigating Workspace
Workspace Overview
Workspace
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Workspace Overview
c l
r a
Workspace provides a centralized interface for viewing and interacting with content
created using Hyperion financial applications, such as Planning and Financial
Management, and reporting content.
O ly
& On
Workspace provides the following benefits:
l
a e
Single user logon: Users log on to Workspace to access both reporting and analysis
n
content and Planning.
t e r U s
Single console for application management and creation: Users create, manage, and
I n
deploy applications from a single location. These applications are opened in
Planning for data retrieval and data output.
c l e
Centralized repository of key dimensional elements for Hyperion products
r a
Centralized console for controlling data flow between applications
e
l
Migrate entire applications or individual application artifacts to different servers
c
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 2-3
Module 1 Getting Started
Lesson 2 Navigating Workspace
Launching Workspace
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Launching Workspace
c l
r a
You launch Workspace from a Web browser by using the following Uniform Resource
Locator (URL) to display the logon page:
O ly
http://<web server>:<port number>/workspace
l & On
To launch Workspace:
n a e
t e r U s
1. In your web browser, enter the Workspace URL, and press Enter.
The Workspace Logon screen is displayed.
I n
2. Enter your user name and password, and click Log On.
c l e
The Workspace user interface is displayed.
r a
O
2-4 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 2 Navigating Workspace
Process bar
Adjuster
Document
tab bar
m y
View pane Content area
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Workspace User Interface
Workspace includes the following elements:
c l
r a
Element
Adjuster
Description
O ly
Adjusts the size of the view pane and content area
Content Area
l & On
Displays active-module items, tasks, or files
Document tab bar
n a e
Displays information specific to the current module
Menu bar
e r s
Provides commands that organize tasks and modules
t U
Navigate menu
Process bar I n
Provides access to Workspace modules
c l e
Standard toolbar Provides shortcuts for performing tasks
Ora
View Pane Provides buttons that enable jumps between panels
P erformance
Management
Architect menu
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Workspace Navigate Menu
c l
The Navigate menu enables you to navigate to the modules available within Workspace.
r a
The following table describes the commands on the Navigate menu:
Command O ly Description
Applications
l & On Access Planning and Financial Management
Administration
t e r
Administer > Classic Application
I n
c l e
r a
O
2-6 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 2 Navigating Workspace
Command Description
Administer > Dimension Library Manage dimensions and dimension properties from a
centralized location
Create dimension import profiles enabling dimension
updates from flat files and relational database
interface tables
Add, delete, and modify dimension members
Modify dimension and member properties
Administer > Application Library Create Planning, Financial Management, Profitability
and Cost Management, and Essbase applications that
are based on Planning and Financial Management
dimension sets
Manage all applications in one centralized location
View the data flow between applications
Migrate applications to different servers
Deploy applications to Planning, Financial
Management, Profitability and Cost Management,
c a
applications, and between one Planning application
and one Financial Management application.)
A
Create data mappings that can be reused
e
c l
Create flat file and interface table mappings to import
data into Hyperion applications
Administer > Application Upgrade
r a
Transfer Planning applications from Planning to EPMA
Administer >Library Job Console
O ly
View a summary of Dimension Library and application
Datasources
n a e
Administer > Managing Planning Create, edit, and delete Planning datasources
t e r
Administer > Calculation Manager
U s Create, validate, and deploy business rules and
business rules sets
I n
c l e
r a
O
Planning: Create and Manage Applications 2-7
Module 1 Getting Started
Lesson 2 Navigating Workspace
Opening Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Opening Applications
c l
r a
In Planning, all data is processed within applications. An application is a related set of
dimensions and dimension members that meet a specific set of analytical or reporting
O ly
requirements. For example, you can have an application named Test used for
& On
development and a separate application named Training to roll out to end users.
l
a e
To access Planning applications
n
e r s
1. Select Navigate > Applications > Planning.
t U
n
2. Select an application.
I
c l e
r a
O
2-8 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 2 Navigating Workspace
Navigating in Planning
Planning m enus Planning toolbar
V iew
pane
m y
Open application Content area
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Navigating in Planning
c l
r a
After you access Planning from the Navigate menu, the application is displayed in a
window with a tab at the bottom left. Planning provides several tools for selecting tasks
and documents:
O ly
Planning menus
l & On
Planning toolbar
n a e
The View pane
t e r U s
Menus
I n
l e
You have access to only menu commands to which you are assigned access based on
c
your user profile. For example, users who are assigned the administrator role have
r a
access to all functions on the Administration menu. Users who are assigned the
interactive user role have limited access to the Administration menu.
O
Planning: Create and Manage Applications 2-9
Module 1 Getting Started
Lesson 2 Navigating Workspace
File Menu
The following table describes the commands under the File menu:
a
Choose from allocation options: proportional, evenly split, and fill
r
Mass Allocate
O ly
Allocate data values across multiple dimensions
Choose from allocation options: proportional, evenly split, and fill
l & On
Allocate data beyond what is displayed on data forms
Cut, Copy, Paste
a e
Cut, Copy, or Paste data from one or more cells into one or more
n
Add Row
t e r cells
U s
Add rows to a data form on-the-fly, only available if the data form
c l e
Annotate Planning Unit Add comments to a planning unit
Ora
Cell Text Add comments to a specific cell or range of cells at any level in a
data form
Supporting Detail Add detail that will aggregate the cell value in a data form
Lock/Unlock Cells Lock cells to ignore cells when spreading data
Initialize Workforce Load predefined dimensions and members, data forms, smart
lists, member formulas, business rules, and menus to prepare
plans for workforce resources. Members, forms and business
rules can be customized.
Note: Initialize Workforce is displayed only if the option was
selected and configured during the configuration of Planning.
Initialize Capex Load predefined dimensions and members, data forms, smart
lists, member formulas, business rules, and menus to prepare
plans for capital expenditures. Members, forms and business
rules can be customized.
Note: Initialize Capex is displayed only if the option was selected
and configured during the configuration of Planning.
View Menu
The following table describes the commands under the View menu:
m y
Refresh
Instructions
d e
Refresh the current view to reflect what is stored in the database
View instructions for a data form, available only if the data form
includes instructions
c a
Currency
View Account
Look up a currency code
e A
Enter, edit, or view comments for a specific account, entity,
Annotations
l
scenario, and version combination
c
Edit Account
Annotations
r a
Basic Mode
O ly
Toggle the view for tasks between Basic Mode and Advanced
Mode
Task List
l & On
View task lists to which you have access; View task status and
n a e
create a task list report. You must be in Basic Mode to create a
task list report.
t e r U s
Administration Menu
I n
The following table describes the commands under the Administration menu:
c l e
Manage Data Forms Create, edit, move, delete, and assign access to data forms
r a
Manage Task Lists Create, edit, move, delete, and assign access to task lists
O
Planning: Create and Manage Applications 2-11
Module 1 Getting Started
Lesson 2 Navigating Workspace
c a
Register Application
Manage Data Source
e A
Register Classic applications with Shared Services
Create data sources for classic Planning applications
Copy Document Link
c l
Link tasks in task lists to application pages
Data Load
Administration r a
Use the Data Load Administration page to set up the data to load
directly through the Planning Adapter or through flat files
Manage Database O ly
Create and refresh Essbase databases with changes made to
& On
relational databases, such as with exchange rates updates
l
Manage Currency
Conversion a e
Create currency conversion calculation scripts
n
Manage Exchange Rates
t e r s
Create and set up exchange rate tables and exchange rates and
U
delete exchange rate tables
I n
Manage Security Filters Create security filters for users
c l e
Favorites Menu
r a
You use the Favorites menu to select which favorites to show on the favorites menu.
O
2-12 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 2 Navigating Workspace
Tools Menu
The following table describes the commands under the Tools menu:
Help Menu
You can access help on the currently selected task or document.
Planning Toolbar
The toolbar buttons open dialog boxes that you can use to manage documents, task
lists, and favorites and provide shortcuts to planning tasks.
The following table describes the buttons on the toolbar:
m y
Button Purpose Description
d e
Save Save data input on data forms
c a
Refresh A
Refresh the data form with data stored in the database
e
c l
Print
a
Print the current screen
r
Adjust O ly
Increase or decrease values by a percentage or by a
l & On
value
Lock/Unlock Cells
Grid Spread
I n
Mass Allocate Run a Mass Allocate calculation
c l e
Cut, Copy, Paste Cut, Copy, or Paste values from one or more cells to one
O
Planning: Create and Manage Applications 2-13
Module 1 Getting Started
Lesson 2 Navigating Workspace
Supporting Detail Add detail that aggregates the cell value in data forms
Task List Open task lists if task lists are assigned to you
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
2-14 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 2 Navigating Workspace
Basic mode limits users to the tasks and documents in the task
lists to which they have access.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Basic and Advanced Modes
c l
r a
Some users roles in the budgeting and planning cycle may require that the user only
perform a limited number of tasks and that those tasks be performed in a specified order.
O ly
Budget administrators and interactive users can set up task lists to help planners
& On
navigate through their required tasks.
l
Advanced mode.
n a e
If task lists are assigned to you, you can choose to work with it in either Basic or
e r s
When you navigate in Basic mode, you use the view pane to select a task list to which
t U
I n
you have access. The task list page helps you focus on your predefined tasks. A
progress bar and navigation features are displayed to help you move between tasks and
l e
monitor your status.
c
r a
O
Planning: Create and Manage Applications 2-15
Module 1 Getting Started
Lesson 2 Navigating Workspace
When you navigate in Advanced mode, you have access to all tasks, through menus and
toolbars, to which you are assigned based on your role. You are not guided through a
predefined list of tasks; you navigate freely to perform your tasks.
When you switch between modes, you return to the activity that you were performing
before you switched. For example, if you are working in a data form when you switch to
Basic mode, you are returned to the same form when you return to that mode.
To switch modes:
Perform an action:
Select View > Basic Mode.
The view pane shows task lists to which you have access.
Select View > Advanced Mode.
All menu functionality for your role and all functionality to which
you are provisioned are available.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
2-16 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 2 Navigating Workspace
View
pane
m y
Business rules Content area
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
View Pane and Content Area
c l
After you open a Planning application, the view pane and content area display your
selections.
r a
O ly
For example, when you work with data form management, the View pane lists form
l & On
folders, data forms, and business rules. You can use the View pane to navigate from one
folder or data form to another. After selecting a specific data form, you see the contents
a e
of that data form in the content area.
n
t e r U s
If you select Business Rules from the Tools menu, you see the Display Launchable
Rule/Rule Sets/ Script Only dialog box in the Content area. However, the view pane lists
I n
form folders, and data forms. After you launch business rules, you can use the view pane
to navigate from the launch business rules dialog box and open a data form.
c l e
r a
O
Planning: Create and Manage Applications 2-17
Module 1 Getting Started
Lesson 2 Navigating Workspace
m y
Data forms
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Opening Data Forms
c l
Data forms are contained within the folders. After you select a folder, a list of data forms
r a
within the selected folder is displayed on the view pane and in the content area. Only
O ly
those forms to which you have access are displayed. After you select a data form, it is
displayed in the content area.
l & On
n a e
t e r U s
I n
c l e
r a
O
2-18 Planning: Create and Manage Applications
Module 1 Getting Started
Lesson 2 Navigating Workspace
Summary
In this lesson, you should have learned to:
Launch Workspace
Describe the user interface components
Open applications
Navigate Planning
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 2-19
Module 1 Getting Started
Lesson 2 Navigating Workspace
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
2-20 Planning: Create and Manage Applications
M O D U L E 2
Overview
The aim of this module is to create dimensions and members for a
Planning application. First, you identify required and user-defined
dimensions. Next, you describe dense and sparse dimensions and basic
concepts of data blocks. Finally, you create the dimensions and dimension
members for the databases for your Planning application.
Lessons in this module include:
Creating Dimensions Overview
Managing Dimensions with Performance Management Architect
m y
e
Setting Up the Period, Year, Scenario, and Version Dimensions
d
Setting Up the Entity Dimension
c a
Setting Up the Account Dimension
e
Creating User-Defined Elements A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
L E S S O N 3
Objectives
At the end of this lesson, you should be able to:
List two methods for creating applications
Describe plan types
Identify required dimensions
Identify user-defined dimensions
Describe dense and sparse dimensions
Create data blocks
m y
d
Set up aggregation, data storage, and calculation options e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
EPMA
Create applications using a wizard
Modify applications by dragging and dropping
Design applications graphically in a central library which
includes tools for auditing, tracking and comparing information
Duplicate applications for testing or what-if analyses
Use dimensions and attributes across multiple applications
Design graphical business rules in Calculation Manager
Graphically manage data flows
Classic
Create applications using a wizard
Modify single applications using Dimension Editor
m y
Set up graphical business rules for complex calculations
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Methods for Creating Applications
c l
r a
You can create applications using Enterprise Performance Management Architect
(EPMA) or Classic application administration. Different menus and options are available
O ly
for each type of application. For example, for applications created with Performance
l & On
Management Architect, you manage Smart Lists within EPMA. For applications created
with Classic administration, you can select Administration, then Smart Lists to use the
feature within Planning.
n a e
t e r U s
EPMA enables administrators to manage, create, and deploy Hyperion applications
within one interface. You create applications using an application creation wizard which
I n
ensures that all required dimensions are included. Then you can work in a central library
to modify dimensions and metadata. For EPMA applications, you can use tools within the
l e
central library to audit, track and compare information.
c
r a
EPMA includes Calculation Manager which enables you to create, validate, and deploy
sophisticated calculations to solve Financial Management and Planning business
Oproblems. Rules can be shared easily between applications.
You can use classic application administration to work with single Planning applications.
For Classic Planning applications, use the Classic Application Wizard to create and
delete applications, and register with Shared Services. You use the wizard to ensure that
all required dimensions are included in your classic application. Then you can modify
dimensions using Dimension Editor and can import metadata using an ETL tool. You can
load data either using a tool or using Essbase Administration Console. You can set up
complex calculations in Business Rules within Essbase Administration Console.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 3-3
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Plan Types
Bud geting
Ap plicatio n = Plan T yp e 1 Plan Type 2 Plan Type 3 Workforce
m
Capital Asset y
d e
Additional modules
available for purchase
n
t e r U s
I n
c l e
r a
O
3-4 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Planning Dimensions
Essbase
m y
Planning Repository
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Planning Dimensions
c l
r a
Planning data is stored in Essbase databases. Data storage in Essbase is different from
data storage in relational databases. Understanding how Essbase stores and retrieves
O ly
data is important for designing an application that functions efficiently.
l & On
Planning applications are organized by dimension. The dimensions in your application
represent the categories of data in your organization. For example, when you enter data
n a e
in a plan, you must identify what item you are budgeting. Budget items such as travel
t e r U s
expense and salary expense are in the Account dimension. You also need to identify the
time period for the item, such as current quarter or next quarter, in the Period dimension.
I n
How you set up dimension properties affects the storage and calculation of information,
c l e
the efficiency of the database, and the display of information in data forms and reports.
You can define aliases for dimension members and view either the alias or the member
a
name in data forms and reports.
r
O
Planning: Create and Manage Applications 3-5
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Required Dimensions
O ly
attributes (UDAs) for EPMA generated applications, you must set up a UDA dimension.
t e r U s
are automatically rolled up to summary time periods, such as quarters and total year. As
the administrator, you specify base time periods and distribution of weeks in the Period
I n
dimension when you create applications. You use the Year dimension to add years to the
calendar.
c l e
r a
O
3-6 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Entity
The Entity dimension represents the flow of Planning information through your
organization. You can establish an entity for each group or responsibility center that
submits a budget plan. These units could be geographic regions, departments, or
divisions, depending on your requirements.
Account
m
The Account dimension specifies the data to be collected from budget planners. You can y
accounts are Rent Expense and Cash on Hand.
d e
establish accounts for all budgeted items to the necessary level of detail. Examples of
NOTE
c a
e A
For dimension member names and alias names, you can include up to 80
characters, and you must make the name unique across all dimensions. You
c l
cannot include the characters \ , or < > in the dimension name.
r a
Currency O ly
l & On
The Currency dimension identifies the currency in which values are displayed. You can
a e
plan in one or more currencies by setting up the following categories:
n
t e r U s
Which currencies are used by applications and reporting
How currencies are displayed in reports and data forms
I n
How currencies are translated into other currencies
c l e
When currency conversions occur
r a
O
Planning: Create and Manage Applications 3-7
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
HSP_Rates
This dimension contains a member to store exchange rate values for each currency. It
also contains a member for input values and currency overrides.
NOTE
The system generates the dimension HSP_Rates for multicurrency applications.
This dimension is visible only in Essbase.
Other Dimensions
In addition to the required Planning dimensions, you must set up an Alias dimension in
order to assign aliases to dimensions such as Account or Entity for EPMA applications. If
you want to use Smart Lists in your application, you must set up a Smart List dimension
for EPMA applications. For EPMA applications, you must set up a UDA dimension if you
want to associate UDAs to members.
NOTE
For Planning, you must include an Alias member named Default in the Alias
dimension.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
3-8 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
User-Defined Dimensions
14 User-Defined Dimensions*
For example:
Employee
Product
Channel
Project
Customer
Salesrep attribute dimension
l & On
You can define a Customer dimension that you can use with the revenue accounts to
budget revenue on a per-customer basis. An application can have up to 14 user-defined
dimensions.
n a e
e r s
In Performance Management Architect, you can perform the following tasks:
t U
I n
Assign plan types for user-defined dimensions at the dimension level, not the
member level. (You cannot delete user-defined dimensions.)
c l e
Rearrange the dimension hierarchy
r a
Share members of user-defined dimensions
O
Planning: Create and Manage Applications 3-9
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Dense Dimensions
Dense
Dimensions
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Dense Dimensions
c l
r a
Multidimensional databases contain dense dimensions. A dense dimension is a
dimension that contains a high percentage of occupied data values in each combination
O ly
of dimensions. For example, when data exists for an entity, it typically exists for most or
& On
all accounts and time periods. Account and Period are typically dense dimensions.
l
n a e
t e r U s
I n
c l e
r a
O
3-10 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Sparse Dimensions
Sparse
Dimensions
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Sparse Dimensions
c l
r a
Multidimensional databases also contain sparse dimensions. Sparse dimensions contain
a low percentage of occupied data values in each combination of dimensions. Sparse
O ly
dimensions have these characteristics:
& On
Data values are not smoothly and randomly distributed throughout the database.
l
a e
Data values do not exist for the majority of member combinations in the database.
n
t e r U s
For example, if each entity sells only to a subset of customers, most combinations of
entity and customer have no associated data. Entity and Customer are typically sparse
dimensions.
I n
c l e
r a
O
Planning: Create and Manage Applications 3-11
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Members of
Dimension B
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Data Blocks
c l
r a
Essbase stores data in data blocks, rather than in records or rows. You can think of a
data block as a grid or spreadsheet with the dimension members on the rows and
O ly
columns. Data is stored in the cells formed by the intersection of the members of different
dense dimensions.
l & On
For the example two-dimension data block on the slide, Dimension A and Dimension B,
n a e
have five members each, and 25 cells are created for storing data.
t e r U s
I n
c l e
r a
O
3-12 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c l
Determining the Number of Data Blocks in a Database
The dense and sparse settings for dimensions determine the structure of the data blocks
r a
and the number of data blocks in the database. The dense dimensions determine the
O ly
data block structure. A data block always includes all stored members of all dense
dimensions. By default, Account and Period are dense dimensions in Planning
applications.
l & On
NOTE
n a e
t
exchange rates.
e r U s
If your application uses currencies, the dense dimension HSP_Rates stores
I n
l e
The data in a data block is stored at the intersections formed by the members of the
c
dense dimensions. For example, if the Account and Period dimensions are dense, the
r a
combination of one time period (January) and one account (Sales) equals one cell of
data within a data block.
O
Planning: Create and Manage Applications 3-13
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Sparse dimensions determine the number of data blocks in a database. You could
potentially have a data block for each unique combination of sparse dimension
members. By default, Entity, Scenario, Version, and Year are sparse dimensions. For an
application that uses currencies, the Currency dimension is set to sparse.
NOTE
If you add additional dimensions, such as Product or Customer, you can tag them
as either dense or sparse. The default is sparse.
Consider the simple database shown on the slide. There is potential for two data blocks
in the database:
Corp -> Budget -> 2009 -> 1st Draft
Corp -> Budget -> 2009 -> Final
The dense dimensions determine the data block structure, and so each data block has
36 cells (3 accounts 12 time periods).
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
3-14 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c
Creating Data Blocks and Retrieving Data
l
r a
After you enter data in a data block, the data block is created. When data is posted to a
data block cell, Essbase first checks to see whether the data block exists. If it does not
O ly
exist, Essbase creates it. Because data blocks are based on unique sparse dimension
n a e
Data is retrieved by data block. If a report or data form requests data from a data block
t e r U s
cell, Essbase retrieves the entire data block into memory. For example, if a report or
calculation requests the value in the cell for Corp -> Budget ->2009 -> 1st Draft ->
I n
Account2 -> Feb, Essbase loads the Corp -> Budget -> 2009 -> 1st Draft data block into
memory and then retrieves the value from the Account2 -> Feb cell for this block.
c l e
r a
O
Planning: Create and Manage Applications 3-15
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c l
Determining Data Structure and Performance of Data Blocks
The dense and sparse settings for dimensions determine data structure. The data
r a
structure can have a significant impact on data retrieval and calculation time. Although
O ly
design considerations can vary significantly between applications, follow the general
guidelines for performance.
l & On
When you view or calculate data, you typically experience the best performance if the
a e
cells are in the same data block.
n
t e r U s
I n
c l e
r a
O
3-16 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
l
Selecting Aggregation, Storage, and Calculation Options
c
r a
A number of factors impact calculations in a database. You set up aggregation, storage,
and calculation options to define how data is calculated. Aggregation options determine
O ly
whether data is added, subtracted, multiplied, divided, ignored, or treated as a
l & On
percentage. Storage options define whether data is stored or calculated when requested.
Understanding the order in which the calculations are performed is important. This order
impacts calculation results.
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 3-17
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Selecting Aggregation Options
c l
You define calculations within dimension hierarchies using aggregation options.
r a
Aggregation options determine how values of child members are aggregated to the
parent value.
O ly
l & On
For example, Sales and COGS might be children of the member Net Income. If you set
the aggregation option for the Sales member to addition and the aggregation option for
a e
COGS to subtraction, then the aggregated value for the Net Income member represents
n
NOTE
t e r
the Sales member minus the COGS member.
U s
I n
Because dimension members can belong to more than one plan type, you can
c l e
specify different aggregation options by plan type.
r a
O
3-18 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Selecting Data Storage Options
c l
r a
To optimize performance and disk usage, you select from the following storage and
calculation options for dimension members.
O ly
Store Data
& On
Stores data values of members.
l
Dynamic Calc and
Store
n a e
Calculates the data value the first time the member is retrieved and
then saves the value.
Dynamic Calc
t e r U s
Calculates the data values each time the member is retrieved. The
value is not stored in the database.
I n
c l e
r a
O
Planning: Create and Manage Applications 3-19
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Share Data Allows two or more members in the same dimension to share data
values.
Note: For EPMA applications, this option is automatically assigned
when you use insert shared member to create a shared member in
the hierarchy.
For classic applications, the data storage option is called Shared.
Shared is set automatically if you create a member with the same
name as another member in the hierarchy.
Never Share Prohibits two or more members in the same dimension from
sharing a data value.
Label Only Has no data associated with the member.
e A
Dynamic Calc
c l
If a member is set to Dynamic Calc, Essbase does not calculate its data value during
r a
regular database calculation; for example, when the CALC ALL function is executed,
O ly
Essbase calculates the data value upon retrieval; for example, Essbase calculates data
when it is retrieved into a data form.
Advantages of Dynamic Calc:
l & On
n a e
Reduction in the regular calculation time of the database because Essbase has
t e r U s
fewer member combinations to calculate.
I n
Reduction in disk usage because Essbase stores fewer data values. Database size
and index size are reduced.
l e
Dynamic Calc is most useful for parent-level dense dimension members. Since values
c
r a
for Dynamic Calc members are not stored, the data block size is reduced, which
improves performance. However, retrieval time for the member is increased.
O
3-20 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Use Dynamic Calc sparingly with sparse dimension members. Because each member of
a sparse dimension references a separate data block, a dynamic calculation that
includes many sparse members must retrieve data from a large number of data blocks.
Retrieving data from many data blocks can reduce performance. As a rule of thumb, use
Dynamic Calc for upper-level members of sparse dimensions only if those upper-level
members have six or fewer children.
Dynamic Calc guidelines:
Do not use Dynamic Calc for base-level members for which users enter data. Data
values are not saved for Dynamic Calc members.
Do not use Dynamic Calc for a parent member if you enter data for that member in a
target version. Parent members set to Dynamic Calc are read-only in target versions.
Do not set a parent member to Stored if its children are set to Dynamic Calc. With
this combination, when a user saves and refreshes a data form, the new total for the
parent is not calculated.
c a
Use Never Share when a parent has a single child that is aggregated to the parent. In
A
this case, set the parent to Never Share. You can set appropriate security for the child
e
c l
member. Typically, you set the Currency, Entity, Version, and any custom dimensions to
Never Share. You typically set those dimensions members to Store Data or Dynamic
Calc instead of Never Share.
r a
Label Only Data Storage O ly
l & On
Label Only members are virtual members; they are typically used for navigation and
have no associated data. For example, you might have a parent member named
n a e
Statistical that groups statistical accounts such as Headcount and Interest Rate.
t e r U s
Because these accounts are not aggregated to a meaningful total, there is no need to
calculate or store a value for the member Statistical.
I n
Making a dimension member Label Only helps minimize database space by decreasing
c l e
block size, which improves performance. You can also use Label Only members to group
members or to navigate and report more easily from Financial Reporting or Essbase
a
Smart View Provider.
r
O
Planning: Create and Manage Applications 3-21
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
3-22 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Calculating Data
d
Copyright 2008, Oracle. All rights reserved.
c a
e A
Calculating Data
c l
The calculation order in Essbase can affect the result of a calculation. Essbase
r a
calculates the Account members first, the Period members second, and the remaining
O ly
dimensions according to their order in the database outline.
l & On
Sometimes the calculation of a member in one dimension depends on the calculated
result of members in a dimension that is not calculated until after the first dimensions
a e
calculation. You can assign the Two-Pass Calculation option to a member in such
n
t e r
situations. After Essbase calculates the database, a second pass calculates members
tagged Two-Pass Calculation.
U s
I n
c l e
r a
O
Planning: Create and Manage Applications 3-23
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Before Two-Pass
9 9 9 8
After Two-Pass
9 9 9 9
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c l
Calculating Data with Two-Pass Calculations
A good example of two-pass calculation is the calculation for the Margin Percent account
r a
for North America. That calculation depends on the aggregated value of the Gross
O ly
Margin and Net Revenue accounts (Margin Percent = Gross Margin / Net Revenue).
Since the Entity dimension is calculated after the Account dimension, the aggregated
l & On
values are not available. To calculate Margin Percent correctly, Essbase must first
aggregate the values for the children of North America to derive the totals for Net
n a e
Revenue and Gross Margin. After these totals are calculated, a second pass is needed
t e r U s
to calculate the Margin Percent account for North America. To accomplish this task, you
select the Two-Pass Calculation option for the Margin Percent account.
I n
The Two-Pass Calculation option is used primarily for members of the Account
c l e
dimension. For other dimensions, the Two-Pass Calculation option is valid only for
Dynamic Calc or Dynamic Calc and Store members.
r a
O
3-24 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Sparse
Dimensions
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Determining Performance Efficiency
c l
For a data form that contains only one member from each sparse dimension, Essbase
r a
must retrieve only one data block to populate the form. Because the Account and Period
O ly
dimensions are dense, the cells for the account and time period members are already in
that data block.
l & On
If the Period dimension were tagged as sparse, data would need to be retrieved from 17
a e
different data blocks to populate the form, and 17 members of Period are displayed,
n
apply to calculations.
t e r
resulting in less efficient performance. Considerations for dense and sparse settings
U s
I n
For example, a typical calculation in the Account dimension is Net Profit = Gross Sales -
Cost of Goods Sold. If Account is tagged as a dense dimension, the data block includes
l e
the members needed for this calculation. If it is tagged as a sparse dimension, data must
c
be retrieved from three data blocks to perform the calculation.
r a
O
Planning: Create and Manage Applications 3-25
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Another important factor for performance is the number of cells per data block. Because
there is a multiplier effect between dense dimensions, the number of cells in a data block
grows exponentially when dense dimensions are added to the database.
For example, your database might have 200 account members and 12 period members,
resulting in 2,400 cells. If the HSP_Rates dimension is added as a dense dimension with
10 members for currency rates, the number of cells jumps to 24,000 (200 12 10). As
a general rule, smaller data blocks give better performance than larger data blocks.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
3-26 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 3-27
Module 2 Creating Application Structures
Lesson 3 Creating Dimensions Overview
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
3-28 Planning: Create and Manage Applications
L E S S O N 4
Objectives
At the end of this lesson, you should be able to:
Navigate Performance Management Architect
Manage dimensions and members
Create alternate hierarchies
Create property associations
Organize Shared Library
Create members in Grid Editor
m y
Add and modify currencies
d e
Set up aliases
ca
Automate Performance Management Architect tasks
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Shared Application
Library pane pane
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
About Dimension Management
c l
r a
You can view, manage, create, and deploy Hyperion applications within a single
interface. Shared Library can include both shared and non-shared (local) dimensions.
O ly
You maintain shared dimensions and all properties in Shared Library. All updates are
& On
automatically updated in the applications that contain those shared dimensions.
l
Shared Library
n a e
e r s
Shared Library is a central repository that contains all dimensions and dimension
t U
members for Planning and Financial Management applications. All dimensions and
I n
dimension members are created in Shared Library or they are imported into either the
c l e
application or Shared Library. Shared Library can contain more than one dimension of
the same type. For example, it could contain two Period dimensions, with the names
r a
Quarterly Calendar and Trimester Calendar, that are used in different Planning
applications.
O
4-2 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Application Pane
Applications listed in the application pane represent a selection of dimensions required
by an application. You can create local dimensions that are used solely by that
application. However, you can share or copy local dimensions so that other applications
can include those dimensions.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-3
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Planning Consolidation
application application
Dimension
Server
Planni ng Consolidation
application
Application
application
Application
m y
Server Server
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c l
Creating Applications Using Performance Management
Architect
r a
O ly
You manage dimensions and create Planning applications in Performance Management
Architect:
l & On
1. Create applications in the Application Library.
n a e
2. Add dimensions to Shared Library. You can import them from formatted flat files, or
t e r U s
you can create them manually in the dimension editor. You also can import
dimension information from interface tables.
I n
3. Set up applications by selecting application types, adding dimensions, and setting up
l e
other application specific details such as default currency and start month.
c
4. Create Planning applications by deploying applications with the Planning type to
r a
Planning application servers.
O
4-4 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Dimension class
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Adding Dimensions to Shared Library
c l
r a
You can add dimensions to Shared Library. The dimension class determines the
properties that are available to the dimension members. For example, the Account
O ly
dimension includes the time balance property, which is not present in the Entity
dimension type.
l & On
n a e
To add dimensions to Shared Librar y:
e r s
1. Select File > New > Dimension.
t U
I n
The Add New Dimension dialog box is displayed.
c l e
2. Enter a dimension name.
Dimension names must be unique and can contain up to 80
O
Planning: Create and Manage Applications 4-5
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
4-6 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Synchronize local
dimensions with
dim ensions in S hared
Library.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c
Working with Shared and Local Dimensions l
r a
Shared dimensions are dimensions that are linked in Shared Library and inherit any
changes that are made to that dimension. You must make all changes to shared
O ly
dimensions from Shared Library. Shared dimensions can be used by multiple
applications.
l & On
n a e
Local dimensions are detached, independent dimensions that only exist in one
application. You can create a local dimension by copying a shared dimension to an
e r s
application. You can also create a local dimension when you are running an import
profile.
t U
I n
After you define a dimension to be local, that dimension does not inherit changes made
l e
to the dimension in Shared Library. To make changes to the local dimension, you must
c
perform these changes within the application. If you make changes to the original shared
r a
dimension, you can merge changes to the dimension at the application level.
O
Planning: Create and Manage Applications 4-7
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
With shared dimensions, you can detach the dimension, making it a local dimension.
With local dimensions you can:
Copy dimensions to Shared Library or to an application
Synchronize between dimensions in Shared Library and dimensions in the
application
Share dimensions changing a local dimension to be a shared dimension in an
application
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
4-8 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Creating Members
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Creating Members
c l
r a
You create hierarchical relationships within dimensions by creating and organizing
members. You can add dimension members individually or by using import profiles. You
O ly
can add members to dimensions in Shared Library or locally to dimensions that are
within an application.
l & On
n
To add members to dimensions:a e
e r s
1. In the dimension hierarchy, right-click a member.
t U
I n
2. Select Create Member.
l e
3. Select an option:
c
Select As Child to add a member below the selected member
r a
Select As Sibling to add a member at the same level as the selected member
O
Planning: Create and Manage Applications 4-9
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
4-10 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
O ly
If you use an invalid character in a member name, an error message is displayed when
you validate the application.
l & On
NOTE
n a e
t e r U s
Do not use reserved Essbase words such as #missing in member names.
I n
c l e
r a
O
Planning: Create and Manage Applications 4-11
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Defined
Derived
Default
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Modifying Member Properties
c l
r a
You can modify properties for each dimension member. When the dimension is created,
it takes on a default set of properties and property values. Properties are organized into
O ly
categories based on the products for which they are valid.
Property Category
l & On
Application
Planning
n a e
Used for Planning applications
System
t e r U s
Used to identify characteristics of a member, such as name,
description, and member status (inactive or active)
Consolidation
I n Used for Financial Management applications
c l e
Profitability
Essbase (BSO)
Used for Profitability and Cost Management applications
r a
O
4-12 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Property fields are color-coded based on what you can do with that property. Consider
the following characteristics when working with properties:
Properties that can be modified display a white background.
Properties that are read-only display a grey background.
Properties that are modified display a yellow background.
Modified properties, called defined properties, are not saved until you click the Save
button in the upper-right corner of the properties pane.
Defined properties display the following icon: .
Derived properties are those determined by logical relationships. Derived properties
display the following icon .
Inherited properties display the following icon . An example of an inherited property
m y
wold be the Account Type property for account members.
d e
Unmodified properties display a check mark
setting. a
. These properties keep their default
c
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-13
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Currency
property is set to
GBP, overriding
Descendants of United
Kingdom inherit GBP for
Currency property.
m y
inherited value.
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Property Value Inheritance
c l
r a
Inheritance allows high-level members to share their properties values with lower points
in the hierarchy. It allows new members to automatically obtain their property values from
O ly
the appropriate ancestors. Proper use of inheritance enhances the referential integrity of
& On
your application and reduces maintenance requirements.
l
a e
Performance Management Architect determines a property value in the following order:
n
t e r
member, it uses that value.
U s
1. It looks for a value entered at the member. If a user directly entered a value at the
I n
2. If a value does not exist, it moves up the ancestral tree and uses the first entered
value that it finds. Thus, a change to the properties of an ancestor can affect
l e
descendant members that inherit its value.
c
r a
3. If no ancestor has an entered value, it uses the system default value for the property.
O
4-14 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-15
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Alternate Hierarchies
d
Copyright 2008, Oracle. All rights reserved.
c a
e A
Alternate Hierarchies
c l
r a
You can create multiple rollup paths for your data by placing a child member under more
than one parent. In the slide illustration, Jan and Feb are members of a YearTotal rollup,
O ly
with YearTotal as the top member, and a Q1 rollup, with Total Year as the top member.
Function hierarchy.
l & On
Entity E01_101_1110 is a member of the TotalGeography hierarchy, and the Sales
n a e
A member has the same property settings under all parents in which it occurs, with one
t e r U s
exception. One member has the property StoreData. Any additional members have their
property storage set to ShareData. Editing the properties of the stored member under
I n
one parent updates it properties for all parents.
l
NOTE
c e
You can set the aggregation property of a shared member to be different from the
O
4-16 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Inserting
members creates
shared members.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Inserting Members Using Relationships
c l
r a
You can insert a group of members into a hierarchy based on a member relationship. For
example, you could insert all base members beneath a selected parent member into an
alternate hierarchy.
O ly
l & On
To insert members using relationships:
n a e
1. Right-click a member and select Insert Shared Member.
2. Select an option:
t e r U s
I n
Select Child to add the member as a child of the currently selected member.
l e
Select Sibling to add the member at the same level as the currently selected
c
member.
r a
3. Select a member and click Add.
O
Planning: Create and Manage Applications 4-17
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Managing Members
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Managing Members
c l
r a
You can change the order in which a member is displayed under a parent or move a
member to another parent. You can delete a member from a single hierarchy or from all
hierarchies.
O ly
l & On
Reordering Children
n a e
t e r
You can change the order of children within the hierarchy.
U s
n
To reorder children in Shared Librar y:
I
c l e
1. Right-click a dimension or member, and select Reorder Children.
The Reorder Children dialog box is displayed.
r a
2. Click on the up or down arrows to change the order of the children.
O 3. Click OK.
Deleting Members
You can delete members from the current hierarchy only or from the dimension. When
you delete a member from the dimension, the member is removed from all hierarchies in
Shared Library and from all applications containing that member if the dimension is a
shared dimension.
To delete members:
To delete a member from a hierarchy, right-click the member and select Remove
Member.
To delete a member from the dimension, select the member in any hierarchy in
Shared Library, and select Delete Member.
Renaming Members
You can rename members in Shared Library. You cannot rename system members
members displayed in brackets [ ]. After Planning application deployment, you should not
rename the Period members. For Planning applications, you cannot rename Currency or
Year members.
m y
Managing Orphan Members
d e
c a
An orphan is a member that does not have a location in the dimension hierarchy. An
Orphan member is created during metadata import when the Hierarchy section of the
A
metadata load file does not contain information for the member. Orphan members are
e
c l
also created when you use the Remove option to delete a child member from a parent
and the child member does not exist under another parent in the dimension.
n a e
To delete orphan members:
t e r U s
n
In the Orphan Members list, right-click the member and select Delete Orphan Member.
I
c l e
The orphan member is permanently deleted.
r a
O
Planning: Create and Manage Applications 4-19
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Finding Members
Double-click
a member to
locate it in
the outline.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Finding Members
c l
r a
You can search for dimension members in Shared Library or in applications. You can
search on the member name, member description (alias), or a member property. The
O ly
search operation finds all members that meet the specific search criteria.
To find members:
l & On
n a e
1. Right-click a dimension, and select Find Members.
t e r U s
The Member Find dialog box is displayed.
I n
2. Select to search by the member: Name, Alias, or Property.
l e
3. If you selected Property, then in the Property Name list, select a property by which to
c
search.
r a
4. Enter the value for which to search, using an asterisk (*) as a wildcard if necessary.
O
4-20 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-21
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
Ellipses indicate dimension association.
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c
Creating Associations Between Dimensions l
r a
You can associate a property in one dimension with the members of another dimension.
End users can set the value for the property by selecting from a pick list of members from
the associated dimension.
O ly
l & On
For example, if you create an association between the Currency property of the Entity
n a e
dimension and the Currency dimension, users can set the Currency property of an entity
member by selecting from a pick list of members in the Currency dimension.
t e r U s
After you create an association for a property, users must select a member from the pick
n
list to set the property value; no other entries are valid.
I
c l e
You can create an association for any dimension property, but some dimension
properties require a dimension association. Values cannot be entered for these
a
properties until an association exists.
r
O
4-22 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-23
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Chart of
Create folders Accounts
Add dimensions to
those folders
HP _Accounts
Hyplan_Account
Finbud_Account
SME_Account
m y
FM_Accounts
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Organizing Shared Library with Folders
c l
r a
You can organize dimensions by creating folders and copying or moving the dimensions
into the folders. Dimensions can exist in more than one folder. For example, you can
O ly
organize dimensions and have the Account dimension exist in multiple folders or have
l & On
the Account dimension exist at the highest level and also within a folder. Changes made
to the Account dimension in one folder update the Account dimension in all folders.
n a e
How to organize Shared Library:
Rename folders
t e r U s
I n
Drag dimensions from their original location to a folder
l e
Move multiple dimensions at the same time
c
a
Copy dimensions into folders
r
O
4-24 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
To create folders:
1. In Shared Library, select File > New > Folder.
The Create New Folder dialog box is displayed.
2. Enter the name and description, and then click OK.
To delete folders:
1. Right-click the folder, and select Delete and one of the following options:
m y
Folder with Content
Only Folder
d e
c a
If you select the option to delete only folders, then only the folders
e A
are deleted. Any dimensions within the folder are not deleted and
sub-folders are not deleted. Those dimensions and sub-folders
c l
are moved to the root of Shared Library. If you select to delete
only a sub-folder, then only the sub-folder is deleted. Dimensions
r a
are not deleted, rather they are moved to the root folder.
O ly
2. At the confirmation dialog box, click Yes.
3. Click OK to confirm.
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-25
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Filtering Shared Library
c l
r a
You can filter the dimensions you see in Shared Library. Filtering applies to dimensions
both in the root directory and in folders. If you create a dimension and have a filter
O ly
applied that does not include the new dimension, the dimension is not displayed in
l & On
Shared Library until you remove the filter. In the illustration, Shared Library is filtered to
show only dimensions whose name start with the characters HP.
n a e
t e r
To create dimension filters:
U s
1. In Shared Library, select View > Filter Dimensions.
I n
The Dimension Filtering dialog box is displayed.
c l e
2. Enter the dimension name, or select the dimension type, or enter the owner.
r a
O
4-26 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
3. Click OK.
A filter icon displayed in the Shared Library pane indicates that
dimensions are filtered.
TIP
You can remove filter criteria by selecting Edit > Clear Filter Criteria.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-27
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Sorting Dimensions in Shared Library
c l
r a
You can sort dimensions in Shared Library in ascending or descending order. You can
sort by dimension class, name, description, or owner. When dimensions are sorted, a
O ly
sort icon is displayed in the Shared Library pane.
To sort dimensions:
l & On
n a e
1. In the Dimension Library, select View > Sort Dimensions.
t e r U s
The Dimension Sorting dialog box is displayed.
I n
2. Select the property to sort by (Dimension Class, Name, Description, or Owner).
l e
3. Select the sort order (Ascending or Descending).
c
r a
O
4-28 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
4. Click OK.
TIP
You can remove the sort by selecting Edit > Clear Sort Criteria.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-29
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Visual
cues
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Working with Grid Editor
c l
r a
You can work with the Grid Editor to maintain member information. The Grid Editor
enables you to work with multiple dimensions and members in a grid format, so that you
O ly
can set properties for groups of members at the same time. You can also create and
& On
delete members. Visual cues identify the types of changes that you made.
l
n a e
Members are displayed in the rows, with member names shown in the first column on the
left-hand side of the grid. Properties are displayed in the columns with the property name
t e r U s
displayed as the second row in the column heading. Each corresponding property value
is displayed as cell data. You select which members and properties are displayed in the
grid.
I n
l e
You can filter what is displayed by selecting a category. You can navigate to a different
c
page either by using the arrows or by selecting a page.
r a
O
4-30 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Add
Remove
Remove All
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Selecting Members and Properties
c l
You select the members and properties that you want to display in the Grid Editor by
using the grid editor wizard.
r a
To select members and properties: O ly
l & On
1. Right-click a dimension and select Grid Editor.
n a e
The EPMA Grid Editor Wizard dialog box is displayed.
t
2. Select a dimension.
e r U s
I n
3. Move the members that you want to edit from the Members list to the Selection list.
l e
4. Repeat step 2-3 to select additional dimensions and members.
c
a
5. Click Next.
r
O The Select Properties tab is displayed.
6. Select the category that includes the properties you want to add.
7. Move the properties you want to edit from the Properties list to the Selections list.
8. Repeat steps 6-7 to select additional categories and properties.
9. Click Finish.
The Grid Editor is displayed.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
4-32 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Creating Members
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Creating Members
c l
You can create members using the Grid Editor. By creating new members, you add rows
r a
to the grid for the new member and its properties. You can create children or sibling
members.
O ly
l & On
You can change the dimension that is displayed in the Grid Editor. You use the Grid
Editor Wizard to select a different dimension, as well as members and properties for that
dimension.
n a e
t e r U s
You can use the Grid Editor to add, remove, and delete members from all views. If you
add a member, a row is added in Grid Editor. If you remove a member, the row is
I n
removed from the grid. If you delete a member, the member is deleted from all views and
is deleted from the Dimension Server after you save your changes.
c l e
You also can add or remove properties for a member using the Grid Editor.
r a
O
Planning: Create and Manage Applications 4-33
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
To create members:
1. Right-click a row and select Create Member.
2. Select one of the following options:
As Child
As Sibling
3. Enter the member name and click OK.
The member is displayed in the Grid Editor.
You can set changes to be saved immediately after each individual change, by selecting
AutoCommit. Otherwise, data is saved only when you click the Save button. You see
visual cues when you modify members or properties. Cells are shaded with color
indicating that you modified data.
Yellow A cell that is yellow indicates that the values has been updated but not yet
saved. After you save the changes, the value is changed in Shared Library and the
cell color changes in the grid to the default color.
you save the changes, the row color changes in the grid to the default color.
m y
Green A row that is green indicates that it is a newly added row to the grid. After
d e
Red A row that is red indicates that it is marked for deletion. After a row is marked
c a
for deletion, you cannot edit those cells. After you save the changes, the members
are deleted from Shared Library, removed from the application, and the rows are
deleted from the current page of the grid.
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
4-34 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Adding Currencies
m y
Create new currencies. Set properties for currencies.
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Adding Currencies
c l
r a
You set up currencies by creating a dimension with the dimension class Currency. You
create members in the Currency dimension for each currency needed in your application.
NOTE O ly
l & On
A dimension association is required between the Currency property of the Entity
a e
dimension and the Currency dimension.
n
t e r U s
Number Formatting
I n
You can set the number format for each currency. For example, for the European euro,
l e
you can set the dot as the thousands separator and the comma as the decimal separator
c
to match the European standard. You can also set the color of negative numbers.
r a
O
Planning: Create and Manage Applications 4-35
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Scaling
You can specify that data values are scaled when they are displayed in certain
currencies. For example, you might set the scaling for the Japanese yen to thousands.
You could enter 10,000 as a value for Japan. When you select Japanese yen as the
display currency, the scaling is applied and 10 is displayed as the value for Japan.
Triangulation
Planning supports currency conversion by triangulation through an interim currency,
which is referred to as the triangulation currency. For example, if you know the European
euro exchange rates for U.S. dollars and French francs, you can calculate the U.S.
dollar/French franc exchange rate by using the European euro as the triangulation
currency.
You can also modify a currencys triangulation currency by reentering the exchange rates
relative to the triangulation currency period and then refreshing the application so that
the new exchange rates are transferred and stored.
NOTE
You cannot select the default currency as a triangulation currency.
m y
d e
Reporting Currency
c a
Planning supports currency conversion from local currencies to one or more reporting
e A
currencies. The converted reporting currency values are stored and are read-only for all
users. The application default currency is also the default reporting currency. When you
c l
add currencies, you specify whether they can be used as reporting currencies.
r a
For example, suppose your application contains the currencies Japanese yen, U.S.
O ly
dollar, and European euro, with European euro specified as a reporting currency. When
you create data forms and reports, Japanese yen and U.S. dollar values are converted to
European euros and displayed.
l & On
a e
You can load values directly into Essbase (from historical scenarios, for example) for
n
reporting.
NOTE
t e r U s
I n
Each reporting currency is added to the Currency dimension, increasing the size
c l e
of the database and adding complexity to the currency conversion calculation
scripts. Only enable Reporting Currency if required.
r a
O
4-36 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Creating Aliases
Create
association.
m y
d
Enter alias for member.
e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Aliases
c l
r a
To improve outline and report readability, you can assign one or more alternate names,
or aliases, to dimension members. Aliases enable you to create unique sets of identifiers
O ly
when working with dimensions and members. You can assign up to 10 aliases per
l & On
dimension and dimension member, including the default alias. You create alias tables in
Performance Management Architect by creating an Alias dimension and then adding
members to that dimension.
n a e
t e r U s
After you create an association with the Alias property of the base dimension to an alias
dimension, you can assign alias values to members.
I n
c l e
r a
O
Planning: Create and Manage Applications 4-37
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
For example, you can set up alias dimensions to store information for different
languages. If you want to include account names in English, French, and German, you
create members in the Alias dimension named English, French, and German. Then you
create an association between the Alias property in the base dimension and the alias
dimension. In addition to associating aliases to the Account dimension, you can create
associations with the Entity, Scenario, Version, Period, or Year dimensions or user-
defined dimensions.
r a
2. Keep the default selection of Existing Property and select Alias from the Property
drop-down list.
O ly
& On
3. Select the alias dimension from the dimension drop-down list.
l
n a e
To add aliases to dimension members:
t e r
1. Select the dimension member.
U s
I n
2. Double-click in the Alias field of the property grid.
l e
3. Click the ellipsis button and enter aliases in the row representing the alias table.
c
a
4. Click OK.
r
O
4-38 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-39
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
l
Automating Performance Management Architect Tasks
c
r a
You can schedule tasks to run during off peak times. You can combine processes such
as data exports, metadata loads, refresh operations, security updates, data loads, and
O ly
calculations, and kickoff these operations during your normal nightly or weekly load
process.
l & On
With the batch client, you can initiate processes using external scheduling tools. The
n a e
batch client provides status updates and error information to external scheduling tools.
t e r U s
You work with the batch client in script mode to schedule tasks.
I n
c l e
r a
O
4-40 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
Summary
In this lesson, you should have learned to:
m y
Automate Performance Management Architect tasks
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 4-41
Module 2 Creating Application Structures
Lesson 4 Managing Dimensions with Performance Management Architect
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
4-42 Planning: Create and Manage Applications
L E S S O N 5
Objectives
At the end of this lesson, you should be able to:
Describe Planning time periods
Customize time periods
Create scenarios
Create versions
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
O ly
and you specify base time periods and distribution of weeks. You use the Year dimension
to add years to the calendar.
l & On
You can customize summary time periods in these ways:
n a e
Update the name
t e
Change the description
r U s
I n
Modify starting and ending periods
l e
Change the range
c
a
Create new summary time periods
r
O
5-2 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
If you create a new summary time period, you must work from the top of the hierarchy to
the bottom. The Period Type property for a summary time period is Summary Time
Period.
Keep in mind the following requirements:
All base members must be the same number of levels from the root.
Base members must have a Period Type property value of Base Time Period.
BegBalance and YearTotal are required members for successful deployment of
Planning applications.
NOTE
The YearTotal member is the summary time period that aggregates all quarters or
weeks (for custom time periods).
m y
d e
c a
The YearTotal member must have a Period Type property value of Year Time Period.
e A
You can add up to 100 calendar years and 500 time periods to an application. Depending
on the number of time periods and years and whether your application uses multiple
c l
currencies, Hyperion recommends these practical limits:
r a
400 time periods per year and 27 years
O ly
360 time periods per year and 30 years
l & On
You can enable Dynamic Time Series (DTS) for Period dimension members. For DTS
Alias.
n a e
members, you can set the following properties: DTS Enabled, DTS Generation, and
t e r U s
You can create alternate hierarchies and use shared descendants in the Period
I n
dimension. Data Storage for all time periods can be set to any valid data storage value.
You can set the consolidation operator for all scenarios, versions, and time periods
l e
(including BegBalance) to any valid consolidation operator. For example, it can be set to
c
+ (addition), instead of ~ (ignore).
r a
O
Planning: Create and Manage Applications 5-3
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
After deploying the application and setting the calendar, you cannot change the type of
base periods, or reduce the number of years. If you selected a weekly distribution
pattern, you cannot change the pattern.
You can add more years to the Year dimension. However, you cannot delete a year after
it is added.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
5-4 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
Period
Year
Year
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Period and Year Dimensions
c l
r a
The Year dimension contains a member for each year in the range of years for the
application. The member identifies the year to which the data applies.
O ly
The Period dimension is populated with base time periods for the application and is
& On
tagged with the Time property in Essbase. When used in combination with the Account
l
n a e
dimension, a time dimension has properties that enable you to control how data
accumulates over time for an account.
e r s
The slide shows a typical example of a Planning data form, with Year FY07 in the point of
t U
periods.
I n
view and months in the columns. The Essbase outline displays the years and time
c l e
r a
O
Planning: Create and Manage Applications 5-5
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Dynamic Time Series Members
c l
r a
You can use Dynamic Time Series (DTS) members to create reports that show period-to-
date data, such as quarter-to-date expenses. DTS members can be used with members
O ly
of the Period dimension. You can enable DTS for members, and assign a generation
l & On
number. For example, to calculate quarter-to-date values, you can enable the Q-T-D
member and associate it with generation 2. You can then use the Q-T-D DTS member to
a e
calculate monthly values up to the current month in the quarter.
n
t e r U s
I n
c l e
r a
O
5-6 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
O ly
contains hourly, daily, weekly, monthly, quarterly, and yearly data, you can report day-to
l & On
date (D-T-D), week-to-date (W-T-D), month-to-date (M-T-D), quarter-to-date (Q-T-D), and
year-to-date (Y-TD) information. If the database contains monthly data for the past 5
a e
years, you can report year-to-date (Y-T-D) and history-to-date (H-T-D) information, up to a
n
t e r
specific year. If the database tracks data for seasonal time periods, you can report period-
s
to-date (P-T-D) or season-to-date (S-T-D) information.
U
I n
You can add DTS members to applications in the Dimension Library by using the DTS
Manager. Since DTS members are exposed as dynamic calculation functions, you cannot
l e
load DTS members from ADS files.
c
r a
O
Planning: Create and Manage Applications 5-7
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
5-8 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
Data Storage
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Data Storage
c l
r a
By default, when new members are added to an outline, they automatically store data in
the Essbase database. In some cases, data for a member does not need to be stored in
O ly
the database. By decreasing the number of members that store data, you can improve
l & On
the performance of your application. You can specify whether data is stored for a
member by using Essbase storage options (see screenshot in slide).
n a e
For most applications, setting the summary time periods in the Period dimension to
t e r U s
Dynamic Calc results in improved performance.
n
You can change storage options by setting member properties in the application.
I
c l e
r a
O
Planning: Create and Manage Applications 5-9
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
Creating Scenarios
m y
S elect Start and End Year, and
Start and End Period
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Scenarios
c l
r a
You create the Scenario and Version dimensions to set up individual plans to be
reviewed and approved. For each entity, the scenario and version combination contains
O ly
its own set of data for the accounts and other dimensions.
l & On
After entering entity data for a scenario and version, you can submit or promote the data
to other users for review and approval. The intersection of entity, scenario, and version is
n a e
referred to as a planning unit. Planning tracks the status or planning units as you move
t e r U s
them through the planning process.
I n
Scenarios enable you to perform these tasks:
Apply different planning methods
c l e
Associate different scenarios with different time periods and exchange rates
r a
Create forecasts and budgets
O
5-10 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
To create scenarios:
1. Right-click the Scenario dimension or scenario member, and select Create Member >
As Child.
2. Enter a name and click OK.
m y
3. Set the following properties for the scenario member:
d e
Alias
c a
Valid for Plan
e A
Aggregation
c l
UDA
Member Formula r a
O ly
Data Storage
Two Pass Calc l & On
n a e
Smart List
t e r
Enable Process Management
U s
Data Type
I n
l e
Start and End Year
c
r a
Start and End Period
O
Planning: Create and Manage Applications 5-11
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
Time Periods
In Performance Management Architect, assign each scenario a range of years and time
periods for which it is valid. The range of time periods selected for a scenario has the
following effects in your application:
When you access a data form, you are able to enter data into that scenario for only
the years and time periods within the range. Years and time periods outside the
range are displayed as read-only.
m y
d e
When you generate a currency conversion calculation script, the calculation script
converts currencies for the range of time periods that are valid for the scenarios
selected for the script.
c a
e A
You can modify the time range of scenarios as needed to allow for continuous planning.
For example, you might have a scenario named 3Year Forecast that has 2008 as the
l
start year and 2010 as the end year. At the beginning of the 2009 fiscal year, you could
c
data for 2011.
r a
change the start year to 2009 and the end year to 2011, so that you can enter forecast
O ly
Use Beginning Balance
l & On
n a e
Select Use Beginning Balance in Performance Management Architect as a time period
option if you want to include the BegBalance time period in this scenario for currency
conversion.
t e r U s
I
Exchange Rate Table n
l e
In Performance Management Architect, if your application uses currency conversion, you
c
assign an exchange rate table to the scenario. The table is applicable only to multiple-
r a
currency applications.
O
5-12 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
By assigning different exchange rate tables to scenarios, you can model the effect of
different assumptions on your business. You must consider currency reporting needs
when deciding which scenarios to create.
For example, you may need to create scenarios associated with different exchange rate
tables to eliminate the effects of currency rate fluctuations from variances (such as
Budget at Actual Rate).
Access Rights
You can specify access permissions for Scenario dimension members to determine
whether groups or users can view or modify data. A user or group can have only one of
the following access rights: Read, Write, or None. You assign access rights for scenarios
in Planning after application deployment.
Members of the Year and Period dimensions do not have security associated with them.
However, you can use the scenario start and end year and period properties to lock time
periods out for data entry. For example, you could set the properties so that users can
enter data only into the current year.
m
can also set the Start and End Period properties to allow a mix of actual and budget datay
All time periods that fall outside the start and end range are displayed as read-only. You
e A
December. If you set the start period to April, users can input forecast data for April, May,
through December, but they cannot edit the actual data in January, February or March.
c l
At the end of April, you load actual data for April, and change the start period to May, so
a
that you can create a rolling forecast.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 5-13
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
Creating Versions
m y
d e
Version Type BottomUp or Target
l & On
Allow multiple iterations of a plan; for example, preliminary and final.
a e
Model possible outcomes based on more optimistic or less optimistic assumptions;
n
t e r U s
for example, Best Case and Worst Case.
Manage dissemination of plan data; for example, Internal and External.
I n
Facilitate target setting
c l e
You set up the Version dimension in Performance Management Architect. You can
r a
change the version name in Performance Management Architect and access
permissions in Planning.
O
5-14 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
The permissions are independent of scenarios, so you could give users read-only access
to the Final version but write access to the Working version. Then, if users want to enter
data for Budget Final intersections, they cannot write to that intersection even though the
Budget scenario may have write access. The read access to the Final version prevents
write access to that intersection of data.
You can create hierarchies and use shared members in the Version dimension. If you
assign children to bottom-up versions, these versions are displayed as read-only parents
on data forms.
Version Types
There are two types of versions, Bottom-Up or Target.
For Bottom-Up versions, you enter data into the bottom level members. The parent-level
members are read-only. When you calculate the database, the values of parent
members are aggregated from the bottom-level members. For example, if you enter data
for Northern Europe and Southern Europe, the total for Europe is aggregated after the
database is calculated.
Target versions allow you to enter data for members at any level in the hierarchy. You
can use business rules to distribute values from parent members to their descendants.
m y
d e
For example, you can enter the target for Total Expenses into the Europe member and
use a business rule to distribute the target values to Northern and Southern Europe.
c a
Target versions enable you to set high-level targets for your plan. Planners working with
e A
bottom-up versions can then reference these targets when they enter plan data. For
example, the Total Product Sales member has Retail, Wholesale, and Distributors for its
l
children. A budget manager enters 10,000 into Total Product Sales for the California
c
r a
entity in a target version. This target sets Californias target for product sales. The budget
preparer for California then enters values for the Retail, Wholesale, and Distributors
O ly
children that total 10,000 in a bottom-up version to show how the target is met.
& On
The functionality available with target versions is for top-down budgeting.
l
a e
Guidelines for target versions:
n
t e r U s
Workflow Tasks are not allowed for target versions.
Children of target members must be blank (for example, #missing) for the data input
I n
to be allowed at the top level.
l e
Target members must be set to StoreData (DynamicCalc overrides data input with
c
sum of children).
r a
O
Planning: Create and Manage Applications 5-15
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
To create versions:
1. Right-click the Version dimension or member, and select Create Member > As Child.
2. Enter a name and click OK.
3. Set the following properties for the version member:
Alias
Valid for Plan
Aggregation
UDA
Member Formula
Data Storage
Two Pass Calc
Enable Process Management
NOTE
Enable for Process Management can be selected only for bottom up versions.
m y
d e
Smart List
c a
Data Type
e A
Version Type
c l
4. Click Save.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
5-16 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 5-17
Module 2 Creating Application Structures
Lesson 5 Setting Up the Period, Year, Scenario, and Version Dimensions
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
5-18 Planning: Create and Manage Applications
L E S S O N 6
Objectives
At the end of this lesson, you should be able to:
Add members to the Entity dimension
Modify members in the Entity dimension
Delete members in the Entity dimension
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
Entities Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Entities Overview
c l
manually added to an application. r a
The Entity dimension is a Planning dimension whose members can be loaded or
O ly
You can use parent-child relationships among entities to mirror your budget review
l & On
structure. You can define the types of units that your organization requires, such as
a e
geographical regions, departments, or divisions.
n
t e r U s
For example, your organizations regional centers may prepare budgets that are
reviewed at the country headquarters. The country headquarters may, in turn, prepare a
I n
plan that is reviewed at the corporate headquarters. To match this structure, you can
create members for the regions, countries, and headquarters. You can set up the regions
l e
as children of the country members, and the country members as children of the
c
headquarters member.
r a
O
6-2 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
Assigned NY
m y
d e FL
l & On
members that are cost centers do not submit revenue plans. When you define entity
a e
members, you specify the plan types for which they are valid.
n
t e r U s
Because data forms are associated with plan types, they enable you to control which
entity members can enter data for each plan type. For example, Eastern US may be a
I n
cost center, so you assign it as valid for the IncStmt plan type, but not for the Revenue
plan type. When you create data forms for the Revenue plan type, Eastern US cannot be
l e
selected on those forms.
c
r a
O
Planning: Create and Manage Applications 6-3
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
Selecting a plan type for an entity member involves specifying how the data values should
roll up. An entity members plan types may change when you promote or demote the
member in the dimension hierarchy: If the new parents associated plan types are
different from those of the moved member, the member becomes valid for the plan types
of the new parent.
If you move an entity member, and the new parent of that member is assigned to different
plan types, the member remains assigned to the plan types that it has in common with the
new parent.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
6-4 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
The default currency is the currency that you specify when you
create the application.
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Currency Value for Entities
c l
r a
Entity dimensions require an association with the Currency dimension to be able to enter
a value for the Base Currency. If your application is set up for multiple currencies, you
O ly
must associate the Currency dimension with the base entity dimension and specify a
l & On
currency for each entity. The default currency for all entities is the currency that you
specify when you create your application in Performance Management Architect.
n a e
The currency property value identifies the local currency in which data for the entity is
e r s
entered. When you run a currency conversion calculation script or the Convert
t U
Currencies business rule, Planning uses the exchange rates entered for that entitys
I n
currency to convert the local currency to the reporting currency. You can override the
c l e
currency property during data entry or during a data load.
r a
O
Planning: Create and Manage Applications 6-5
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
For example, you might specify Yen as the currency for the Japan entity, and US dollars
for the United States entity. When you view a data form that has values on it for the
Japan entity, if the forms display currency is set to US dollars, Planning uses the rates in
exchange rates table for the Yen to convert the values to US dollars.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
6-6 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Adding and Modifying Entities
c l
r a
You add and modify dimensions and members in Shared Library. You can also set the
properties for dimensions and members. When you modify dimension and member
O ly
properties, this information populates the Performance Management Architect relational
l & On
database. For these changes to be reflected in the Essbase database, you can deploy
the application in Performance Management Architect or you can select the Manage
a e
Database option in the Administration menu in Planning.
n
To add members:
t e r U s
I n
1. In Shared Library, right-click a dimension or dimension member.
l e
2. Select Create Member, and add the member as a child or sibling.
c
r a
O
Planning: Create and Manage Applications 6-7
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
To modify members:
1. Select the member.
m y
The properties pane is displayed.
d e
2. Modify properties and save your changes.
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
6-8 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
Saving Dimensions
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Saving Dimensions
c l
r a
When you add, modify, or delete dimensions and their members, you must save the
changes before they take effect. When you save the changes, Performance
O ly
Management Architect performs a validation check. Some of the items that validation
& On
checks for include the following:
l
a e
To prevent two users from saving the same dimension or member at the same time.
n
t e r U s
To prevent a user from assigning a member to a plan type for which it is not valid.
To prevent a user from using the same name for different dimensions or members.
I n
To ensure that member names do not contain invalid characters.
c l e
To validate that the period dimension is correctly balanced.
r a
To ensure that member properties are set to valid values.
O
Planning: Create and Manage Applications 6-9
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
To verify that attributes from the same dimension are assigned to members at the
same level.
If the validation check fails, an error message is displayed.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
6-10 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
Deleting Entities
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Deleting Entities
c l
r a
You can delete entities from applications. When you delete entities in an EPMA
application and the application is deployed to Planning, the entity is deleted from the
O ly
Planning application even if it is used in data forms or in a started planning unit.
l & On
After you delete an entity, you should remove it from data forms that contain the entity.
t e r U s
To show an entitys application membership in the Shared Library, right-click an entity
n
member and select Application Membership.
I
c l e
r a
O
Planning: Create and Manage Applications 6-11
Module 2 Creating Application Structures
Lesson 6 Setting Up the Entity Dimension
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
6-12 Planning: Create and Manage Applications
L E S S O N 7
Objectives
At the end of this lesson, you should be able to:
Describe account types and consolidation order
Create account hierarchies
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
Accounts Overview
type. 9
Source Plan
Use aggregation options to
define calculations in the Detail Expense Accounts
account hierarchy. Profit
Total Revenue
m y
T otal Expenses
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Accounts Overview
c l
r a
You use the Account dimension to specify the information gathered from budget
planners. Accounts typically represent an accounting container that identifies the primary
nature of the data.
O ly
l & On
Accounts are organized into hierarchies. You can create an account structure that lets
budget preparers input data for budget items to the appropriate level of detail.
n a e
You can define calculations in your hierarchies. For example, your detailed operating
e r s
expense accounts can automatically aggregate to Total Expenses, and Total Expenses
t U
can be subtracted from Total Revenue.
I n
When you define an account member, you assign a plan type. If you promote or demote
l e
a member, and the new parent of the member has different associated plan types, then
c
the member remains assigned to the plan types that it has in common with the new
a
parent.
r
O
7-2 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
If an account is associated with more than one plan type, you must specify a source plan
type for the account. The source plan type determines which plan types database stores
the account value. For example, if the source plan type for the Total Product Sales
account is IncStmt, the value displayed for the account on forms for the Revenue plan
type is the value entered for the IncStmt plan type.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 7-3
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
Account Types
Account Type Expense Time Balance Skip Exchange Rate Type Data Type
Repor ting
Expense Expense Flow N/A Average Currency
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Account Types
c l
r a
Account types define how an account's value flows over time. Account types also
determine the sign behavior for expense reporting with Essbase member formulas.
O ly
All account types have predefined settings for expense reporting and time balance
l & On
behavior except for the Saved Assumption account type, which is user-defined. When
n a e
you select an account type and save the member, the Expense Reporting and Time
Balance list boxes are populated with predefined settings.
t e r U s
On the slide, the expense, time balance, skip, exchange rate type, and data type are the
n
default selections. You can override the defaults, if required.
I
c l e
r a
O
7-4 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Time Balance Options
c l
options:
r a
Time Balance specifies how account data flows over time. You can use the following
O ly
Option
Flow
l & On Description
Uses an aggregate of all data values for a summary time
r a
O
Planning: Create and Manage Applications 7-5
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
Option Description
Weighted Average-Actual_Actual Uses a weighted daily average, based on the actual
number of days in a year, to account for leap year when
February has 29 days.
Weighted Average-Actual_365 Uses a weighted daily average based on 365 days in a
year, assuming that February has 28 days; does not
account for leap year.
Property Description
None Zeros and #MISSING values are considered.
Missing #MISSING values are excluded.
Zero Zero values are excluded.
Missing and Zeros #MISSING and zero values are excluded.
m y
e
NOTE
None.
a d
When the time balance is set to Flow, skip options are not available and default to
A c
l e
An accounts expense reporting property determines if an account is tagged as an
expense in Essbase member formulas or Financial Reporting variance functions. Here is
c
r a
how expense and nonexpense accounts behave for expense reporting:
ExpenseThe actual amount is subtracted from the budgeted amount to determine
the variance. O ly
l & On
NonexpenseThe budgeted amount is subtracted from the actual amount to
determine the variance.
n a e
t e r U s
I n
c l e
r a
O
7-6 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
Saved Assumptions
O ly
expense reporting properties are used with saved assumption accounts:
& On
You may create a saved assumption of an expense type for expense reporting. It
l
n a e
assumes that the actual amount you spent on head count is less than the amount
you budgeted. To determine the expense, Planning subtracts the actual amount from
the budgeted amount.
t e r U s
I n
You make an assumption on the square footage of an office and you determine the
square footage of the office for the time period by using a value for the end of the
l e
time period.
c
You make an assumption about the number of product units sold at the end of the
r a
time period. You determine the final value for the time period by aggregating the
Currency
Exchange
rate types Average Ending Historical
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Data Types and Exchange Rate Types
c l
r a
Data and exchange rate types determine how numeric values are stored and which
exchange rate to use to calculate the value.
Data types: O ly
l & On
CurrencyStores and displays the value in the default currency.
n a e
NonCurrencyStores and displays the value as a numeric value.
t e r s
PercentageStores and displays the value as a percentage.
U
I n
Smart ListStores and displays the value as a smart list.
l e
DateStores and displays the value as a date.
c
r a
TextStores and displays the value as text.
Unspecified Stores and displays the value as unspecified.
O
7-8 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
For accounts whose data type is Currency, you select an exchange rate type:
AverageValid for any time period; uses the average rate for the account.
EndingValid for any time period; uses the ending exchange rate for the account.
HistoricalValid for any time period.
Data types can have conflicting results on the face of a data form depending upon the
cell intersections defined for the data form. For example, the intersection of a "percent"
data type and a "currency" data type must be resolved based on how you define the
order set. The Data Type Evaluation Order is the defined order. You set a dimension
order by plan type to determine the precedence when multiple data types intersect. Data
types associated with the first dimension in the list take precedence over data types
associated with subsequent dimensions.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 7-9
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Account Hierarchies
c l
r a
You create and modify account hierarchies in the Dimension Library. After you save
changes to the hierarchy, your changes are saved to the Performance Management
O ly
Architect relational database. You must deploy the application in Performance
databases.
l & On
Management Architect or refresh the database in Planning to update the Essbase
n a e
To create account members:
t e r U s
I n
1. In Performance Management Architect, right-click an account.
2. Select Create Member and one of the following:
c l e
- As Child
r a
- As Sibling
O
7-10 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
m y
Data Type
Source Plan Type d e
c a
Adding and Modifying Accounts
e A
c l
In the Dimension Library, you can build the account hierarchy by adding children and
sibling members. You can also change member properties.
NOTE
r a
O ly
When assigning plan types, you must set the plan type property for a parent
l & On
member before you can set the plan type for its children. You cannot select a plan
type for a child member if the plan type is not valid for the parent.
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 7-11
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
Consolidation Order
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Consolidation Order
c l
r a
After creating the Essbase database outline, you should review the order of the
dimensions and members. For each plan type, data is consolidated based on the order
O ly
of the dimensions and members in the outline.
& On
The order of calculation within each dimension depends on the relationships between
l
n a e
members in the database outline. Within each branch of a dimension, level 0 values are
calculated first, followed by their level 1, parent value. The level 0 values of the next
t e r U s
branch are calculated, followed by their level 1, parent value. The calculation continues
in this way until all levels are calculated.
I n
By default, the outline is consolidated based on addition. You can set any members
l e
aggregation option to addition, subtraction, multiplication, division, percent, or ignore.
c
When a new operator is set, the operation designates how a member is consolidated to
r a
its parent. For example, you may want to subtract a member from its sibling, such as
Osubtracting COGS (Cost Of Good Sold) from Sales, to define the value for Margin.
Member 1 (+) 10
30
Member 2 (+) 20 5
Member 3 (-) 25 25 200
Member 4 (*) 40 40 400
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Consolidation Order Example
c l
r a
It is important to understand how members with different operators are calculated. When
you use addition and subtraction operators, the order of members in the outline is
O ly
irrelevant. However, when you use other operators, you must consider the member order
n a e
Essbase calculates Member1 through Member4 as follows:
e r s
(((Member1 + Member2) + (-1)Member3) * Member4) = X(((10 + 20) + (-25)) * 40) = 200
t U
I n
If the result from Members 1-4 is X, then Member5 consolidates as follows:
l e
(X/Member5) * 100 = Y(200/50) * 100 = 400
c
r a
If the result of Member5 is Y, then Member6 consolidates as follows:
Y/Member6 = Z400/60 = 6.67 and Member7 is ignored in the consolidation.
O
Planning: Create and Manage Applications 7-13
Module 2 Creating Application Structures
Lesson 7 Setting Up the Account Dimension
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
7-14 Planning: Create and Manage Applications
L E S S O N 8
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
User-Defined Dimensions
Customer
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
User-Defined Dimensions
c l
planning. r a
User-defined dimensions help you capture categories that your organization uses for
O ly
For example, you may have a group of accounts for operating expenses. You may
l & On
decide to add a dimension called Project so that you can budget operating expenses on
a project basis.
n a e
Guidelines:
t e r U s
Names must be unique and use proper naming conventions.
I n
Names and aliases can have up to 80 characters.
c l e
Descriptions can have up to 255 characters.
r a
O
8-2 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
For user-defined dimensions, you assign valid plan types at the dimension level, not at
the member level. All members of custom dimensions are valid for plan types assigned
at the dimension level.
You assign the Generic dimension type to user-defined custom dimensions. You set up
user-defined custom dimensions by defining the following dimension properties: Name,
Alias, Valid for Plan, Aggregation for Plan, UDA, Member Formula, Data Storage, Two
Pass Calc, Smart List, Data Type, and Attributes.
NOTE
In order to assign access to members in a custom dimension, you must select
Apply Security at the dimension level. You assign access in Planning.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 8-3
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
Attributes Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Attributes Overview
c l
r a
Attributes are characteristics of your data. For example, products can have attributes
such as colors, sizes, or flavors. Attributes enable you to add another level of granularity
O ly
to your data. You create attributes for a dimension when you want to group its members
according to the same criteria.
l & On
n a e
For example, you might have a Product dimension with members for three product lines,
some of which are sold in retail outlets and some only by catalog. When you are
e r s
analyzing or reporting your data, you might need separate totals for retail and catalog
sales.
t U
I n
Attribute dimensions can have a data type of text, numeric, Boolean, or date. The
l e
attribute type applies only to level 0 members of the attribute dimension.
c
r a
O
8-4 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
You can use date attributes to specify the date with a format as month-day-year or day-
month-year, and sequence information accordingly. You can use date attributes in
calculations, for example, comparing dates in a calculation that selects product sales
since 12-22-1998. You can set the date format in Application Settings.
To show relationships between members, you can set up hierarchies within attribute
dimensions. If an attribute is numeric, only the level zero attribute members must be
numeric. For example, you could set up an attribute dimension that has a text parent
called Total with numeric children 1, and 2. You can also include aliases for attribute
members.
You can add attributes to sparse dimensions such as the Entity dimension and User-
Defined dimensions. You can add attributes to the Account dimension if it is designated
as a sparse dimension in all plan types.
NOTE
You can assign attributes only to sparse dimensions. For dense dimensions, you
must change them to sparse for all plan types. When changing dimensions to
dense, all attributes and attribute values for the dimension are automatically
deleted. You cannot assign attributes to label-only members.
m y
d e
You use attributes to view, aggregate, and report on data. For example, you can view net
sales by customer and sales rep.
c a
In many ways, attribute dimensions behave like regular dimensions: You can retrieve,
A
pivot, and drill on attribute members. You can use them to create crosstab reports of
e
c l
attribute data for multiple attributes in the same dimension, or for attribute data from
multiple dimensions. For example, Sales Reps are attributes of the Customer dimension.
NOTE
r a
O ly
In order to assign attributes to a user-defined custom dimension, you must
l & On
associate the attribute dimension to the user-defined custom dimension. For
example, if you want to assign salesreps to the Customer dimension, you
a e
associate the Salesrep attribute dimension to the user-defined custom dimension
n
named Customer.
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 8-5
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
Creating Attributes
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Attributes
c l
r a
You create attribute dimensions, assign attribute types, and add attribute values in
Dimension Library. You can then assign attribute values to dimension members. When
O ly
you create forms and reports, you can filter dimension members by their attribute values.
U s
2. Enter a name and description for the dimension.
I n
3. From the Type drop-down list, select Attribute and click OK.
l e
4. In Dimension Library, select the attribute dimension you just created.
c
r a
5. In the Properties pane, set the value of the Attribute Type to either Text, Boolean,
Date, or Numeric.
O
8-6 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
6. Right-click the attribute dimension, and select Create Member > As Child.
7. Enter the attribute value.
8. Repeat steps 6 and 7 to enter other attribute values for the attribute dimension.
NOTE
Only sparse dimensions can contain attributes. To display the sparse/dense
settings for dimensions, right-click the application name and select Performance
Settings.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 8-7
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Attribute Values: Examples
c l
r a
For an entity dimension with the members Acquisition date, Strategic Y/N, and Desc, you
could create corresponding date, boolean, and text attributes. After creating the attribute
O ly
and attribute values, you can assign a value to each member.
l & On
When assigning attribute values to dimension members, you must assign all of them at
a e
the same level in the hierarchy, or an error occurs during the application refresh.
n
t e r U s
I n
c l e
r a
O
8-8 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Assigning Attribute Values
c l
r a
You use Dimension Library to assign and view attribute values. After creating attribute
dimensions and values, you must associate them with a dimension (at the dimension
O ly
level) before you can assign attribute values to a dimension member.
l & On
To associate dimensions with attribute values:
n a e
t e r
1. In Dimension Library, select a dimension.
U s
2. Right-click the dimension and select Create Association.
I n
3. Select Existing Property or New Property.
l e
4. Perform a task:
c
r a
If you selected Existing Property, select the property from the Property drop-down
list.
O If you selected New Property, enter the new property.
5. Enter a description.
6. From the Dimension drop-down list, select a dimension where that attribute is located.
7. Click OK.
The attribute dimension associated with a user-defined dimension
is displayed as a property in the property grid.
8. Right-click a dimension and select View Associations to verify dimension associations.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
8-10 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Member Formulas Overview
c l
r a
So far you have set up calculations between members by using aggregation options.
These aggregation calculations are built into the Essbase outline. The aggregation
O ly
calculations are generally intuitive as you can drill down to see how a member is derived.
l & On
Calculation through aggregation operators has some limitations:
a e
You can create calculations only between children of a common parent.
n
e r s
You must store results of the calculation in the parent member.
t U
I n
You can use member formulas as an alternative method of calculation. Member formulas
are attached directly to dimension members. They go beyond aggregation logic by letting
l e
you reference values in members anywhere in the outline, including in other dimensions
c
or other databases. Member formulas also provide a wider range of operators.
r a
O
Planning: Create and Manage Applications 8-11
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Adding Member Formulas
c l
r a
You use the Memo Editor in Dimension Library to create and save member formulas. You
can define member formulas in the Properties Grid for Planning, Essbase, and
Enterprise Analytics categories.
O ly
& On
When adding a formula to a member, you edit the Member Formula property for an
l
n
as in the following example:a e
account. Using the Memo Editor, you could create a member formula for Profit Percent,
t e r s
Profit Percent = Gross Profit%Net Sales;
U
I n
c l e
r a
O
8-12 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
When creating member formulas, you can combine the following items to perform
calculations on members:
Operators, calculation functions, dimension and member names, and numeric
constants
Operator type, function, value, member name, UDA, and so on that are allowed in
Essbase formulas
Predefined formula expressions, including smart list values, that expand into a
formula or value upon database refresh
Use these buttons to create member formulas:
Button Description
Inserts a function and its parameters.
Inserts a variable.
m y
Finds a text or phrase in the member
formula.
d e
Replaces a text or phrase in the member
formula.
c a
e A
To add member formulas:
c l
1. Select a dimension member.
r a
2. In the Properties pane for the member, double-click Member Formula.
O ly
3. Click .
l & On
The Member Formula dialog box is displayed.
n a e
4. Enter a formula.
5. Click OK.
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 8-13
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Adding User-Defined Attributes
c l
r a
You create user-defined attributes (UDAs) in Dimension Library to describe
characteristics of other dimension members. You can use UDAs within calculation
O ly
scripts, member formulas, and reports. UDAs are words or phrases that describe a
within Markets.
l & On
member. For example, you can apply a UDA such as New Market to selected members
n a e
UDAs enable you to calculate and report on specific subsets of data. They essentially
t e r U s
provide a way to group members. For example, in a report or calculation, you can
request all states with a New Market UDA.
I n
You can share UDAs across applications. You can also assign a UDA to one or more
l e
dimension members.
c
r a
O
8-14 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
5. Click Save.
d e
6. Save the member properties.
ca
A
TIP
You can manually enter, edit, and delete assigned UDAs in the UDA text box. Use
l e
a comma to separate multiple UDAs for a member.
c
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 8-15
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
4000-100 (Network
Sales), and 4000-200
(Chip Sales), use data
values.
Customer_Service_Class
uses a smart list.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Smart Lists Overview
c l
r a
Smart lists are custom drop-down lists that you can access from data form cells in
Planning applications. You can select an item from the list instead of entering data
O ly
manually. You cannot type in cells that contain smart lists.
l & On
For example, you can create a smart list for customer service level with the following
values:
n a e
Platinum
Gold
t e r U s
Silver I n
c
Bronzel e
r a
O
8-16 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
You can associate the Customer Service Level smart list with the Customer Service
Class account member. On a data form, if you click in the account named Customer
Service Class (which is associated with the Customer Service Level smart list), you can
choose from a drop-down list with these selections: Platinum, Gold, Silver, and Bronze.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 8-17
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Smart Lists
c l
properties to smart lists. r a
In Dimension Library, you create smart list dimensions and members, and assign
n a e
Create members in the dimension. (The members are the items that are displayed in
e r s
the drop-down list, data form, or grid.)
t U
n
Assign properties to the smart list dimension and members.
I
c l e
Optional: Perform any of the following tasks:
- Set up smart lists on data forms
r a
- Use smart lists values in member formulas and business rules.
O - Set how #Missing cells associated with smart lists are displayed in data forms.
Guidelines:
Smart lists are associated with dimension members. Typically, the Account
dimension is used to associate smart lists with members.
After associating smart lists with dimension members, reserve those members to
store only smart list values. These members should not be used to store other data
values.
Consider creating new members and setting up a separate rollup with the dimension.
You can create reports to capture the smart list information. You must use planning
details as your data source to report on smart list data.
Smart lists can be associated with more than one member, but those members must
be level 0 members.
Smart lists are not specific to a plan type.
Smart list names and aliases must begin with a letter, and can contain letters,
numbers, underscore, and dollar sign characters. Smart list names cannot contain
spaces, or be Java reserved words.
m y
To create smart lists:
d e
1. In Dimension Library, select File > New > Dimension.
The Add New Dimension dialog box is displayed. c a
2. Enter the name and description.
e A
c l
3. From the Type drop-down list, select SmartList.
4. Click OK.
r a
O ly
5. In Dimension Library, select the Smart List dimension.
l & On
6. In Properties pane, from Category, select System.
n a e
7. Enter a Dimension Alias for the Smart List dimension.
8. Click Save Property.
t e r U s
I n
9. In Properties pane, from Category, select Planning.
c l e
10. Enter a label for the Smart List dimension.
11. Click Save Property.
r a
O
Planning: Create and Manage Applications 8-19
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
12. In Dimension Library, right-click the Smart List dimension and choose Create Member >
As Child.
The New Member dialog box is displayed.
13. In the Name text box, enter a name and click OK.
14. In Dimension Library, select the member name.
15. In the properties pane, from the category drop-down list, select Planning.
16. In the Label text box, type a label and click Save Property.
17. Create additional members, as necessary, for the dimension.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
8-20 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Modifying Smart Lists
c l
a
You modify the following smart list properties in the property grid:
r
Property
O ly
Description
Label
& On
Enter the text to display when the smart list is selected. Spaces
l
and special characters are allowed. Smart list labels can
n a e
reference a resource, which can be translated into different
languages.
Start Value
t e r s
Populates the value property of the first member in the smart
U
list.
Increment
I n Enter the value that is appended to the value of the last member
c l e
Display Order
in the list to determine the value for the selected member.
Select to sort the smart list by ID, Name, or Label.
r a
O
Planning: Create and Manage Applications 8-21
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
Property Description
#Missing Data Form Label Select how #Missing values are represented in cells
associated with the smart list.
#Missing Drop Down Label Enter a label to be displayed as an entry in the smart list whose
value is #Missing.
Administrators can set the values that are displayed in smart lists and data cells,
including what is displayed when no data is in the cell. When no data is in a cell, the cell
can display no value, #Missing, or another specified value.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
8-22 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Associating Smart Lists with Members
c l
r a
You associate smart lists with members in the property grid. You can create a dimension
member or you can use an existing member, and then assign the smart list as a member
O ly
property. Keep in mind that for the member whose member properties includes a smart
& On
list, you cannot enter values in the cells.
l
a e
To associate smart lists with members:
n
1. Select the member.
t e r U s
n
2. In the property pane, from Data Type, select SmartList.
I
c l e
3. In Properties, from Smart List, select the Smart List.
4. Click Save Property.
r a
O
Planning: Create and Manage Applications 8-23
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
Account 6060
has the alias
Customer
Service Class.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Setting Data Forms to Use Smart Lists
c l
r a
In order to work with smart lists on data forms, you must select the dimension member so
that it is displayed on the data form. You must also set the data form properties so that
O ly
you can work with smart lists on that data form.
l & On
Keep in mind the following key points:
n a e
You can assign smart lists to rows or columns.
e r s
You cannot use smart lists in pages.
t U
I n
You must assign smart lists to level 0 members.
c l e
r a
O
8-24 Planning: Create and Manage Applications
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 8-25
Module 2 Creating Application Structures
Lesson 8 Creating User-Defined Elements
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
8-26 Planning: Create and Manage Applications
M O D U L E 3
Loading Metadata 8
Overview
The aim of this module is to load metadata used by Planning applications.
Then you create applications and deploy those applications to the Planning
server. You also set up Exchange Rates.
Lessons in this module include:
Loading Metadata from a File
Creating Applications
Deploying Applications
Setting Up Exchange Rates m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
L E S S O N 9
Objectives
At the end of this lesson, you should be able to:
Format metadata files
Load and extract metadata from flat files
Create profiles
Map dimensions and dimension properties
Explain best practices for loading metadata
Load metadata from interface tables
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Metadata Load Files Overview
c l
r a
You can load metadata into the Shared Library or directly into applications from interface
tables or from flat files. If you load metadata from interface tables, you load metadata
O ly
from a specific database. If you load metadata from flat files, you can include any
l & On
combination of dimensions in the load file, and you can have multiple load files. For
example, you could have one load file for the Account, Scenario, and Version
a e
dimensions and another load file for the Entity dimension.
n
e r s
You can import metadata into either shared or local dimensions. If you import into shared
t U
dimensions, you can update properties but cannot make any structural changes. If you
I n
import into local dimensions, you can change both properties and make structural
changes.
c l e
r a
O
9-2 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
During the import process, you can move members or create shared members. If you
select the option, Merge As Shared, then multiple instances of a member are processed
as shared members. If you do not select the option Merge As Shared, then the primary
member is moved to the specified parent.
NOTE
To load metadata into classic applications, you work with the classic Planning
adapter. There are a number of different Planning adapters to load metadata. The
adaptor that you use depends on the tool you use to import the metadata. Tools to
import metadata into classic Planning applications include Oracle Data Integrator
(ODI), Data Integration Management (DIM), Hyperion Application Link (HAL) and
the OutlineLoad utility. You can also use a flat file adapter to import metadata.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-3
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
!Members= Products
'Name|DataType|SmartList|UDA|Description|Salesrep
Tennis Rackets|Unspecified||||Thomas Brown
Tennis Balls|Unspecified||||Sandy Spencer
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Formatting Load Files
c l
r a
The section for each type of metadata can be displayed only once in a metadata file. You
need not include a column for every dimension member property. Properties for omitted
O ly
columns are set to their default value. Do not use a character included in the actual
metadata as the delimiter.
l & On
a e
If you load metadata from flat files, keep the following points in mind:
n
t e r U s
A line starting with an exclamation point (!) indicates the beginning of a new section
in the flat file and must be followed by a valid section name (for example, Dimensions
n
or DimensionAssociations).
I
c l e
A line starting with an apostrophe (') sets the column order for the section.
True and false values are represented as Y for true and N for false.
r a
You can use a pipe (|), semicolon (;), comma (,), space, or tab as the file delimiter.
O
9-4 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
You specify the dimensions represented in the load file in the Dimensions section. To set
up members with the load file, you create a Members section for each dimension. You
specify the member and the member hierarchy for a dimension.
If some properties have dimension associations, you specify them in the
DimensionAssociations section. To set up aliases, you include a Property Array section.
If you are creating new dimensions by importing metadata, you must include the
Dimensions, Dimension Associations, and Hierarchies sections. In this scenario, the
Members section is an optional section. You can include members and global property
values in the Hierarchy section.
NOTE
For global properties, the value of the property is the same for a member of a
dimension under any parent. An example of a global property is the data type
property. For local properties, the value of the property can differ for a member for
each parent. If a member is in multiple places in the dimension, and that member
has different values for each relationship, then that value is local. The value is
"local" to the relationship in the dimension versus "global" to the member in the
dimension. An example of a local property is the data storage property.
m y
e
If you are creating a new dimension by importing metadata, the Property Array section is
d
Hierarchies section.
c a
optional. You can define Property Array values such as the alias property, in the
A
If you import into existing dimensions, you only have to include a Hierarchies section. All
e
other sections are optional.
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-5
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Setting Up Dimensions
t U
DimensionAlias
n
System property and the name of the dimension in Planning and Essbase
I
l e
You set system properties for dimensions in the Dimensions section. For example, to
c
select Apply Security for a custom dimension, you include the apply security property in
r a
the header and indicate whether to apply security to each dimension by entering a Y for
!Section=DimensionAssociations
'BaseDimension|Property|TargetDimension
Entity|Alias|HP_Alias
Entity|Currency|Currency
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Setting Up Dimension Associations
c l
r a
You use the DimensionAssociations section to identify which member properties have
associations. End users can then set property values by selecting from a pick list of
O ly
members for the associated dimension.
& On
Required columns for the DimensionAssociations section:
l
Column
n a e
Description
BaseDimension
t e r s
Dimension for which you want to set up the association
U
Property
TargetDimension I n Property that you want to link to another dimension
Dimension to which to link the property
c l e
r a
O
Planning: Create and Manage Applications 9-7
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
You can automate property association assignments by indicating the associations in the
load file. The example on the slide is a sample section from a file that you can use to load
metadata.
NOTE
If you indicate associations in the load file, you need to ensure that the
dimensions, both the base dimension and the associated dimensions (target
dimensions), exist in the Dimension Library. For example, if you associate the size
attribute dimension to the product dimension, you must ensure that both the size
and product dimensions already exist in the Dimension Library, or are defined in
the Dimensions section of the load file.
You can also add property associations later by creating lists in Dimension Library. The
illustration on the slide is one such example. Association-setting privileges are
determined by role. For example, administrators set associations for Currency, Start and
End Period, and Start and End Year. Business users can set associations for smart lists.
!HIERARCHIES=Entity Plant1
'Parent|Child
#root|Geographical WestSales
Geographical|UnitedStates
Geographical|Europe Connecticut
United States|California
California|1000
California|Plant1
Mass
m y
California|WestSales
Europe
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Setting Up Parent-Child Relationships
c l
r a
You define parent-child relationships within dimensions in the Hierarchies sections. You
begin the section by entering the following line, replacing the angle brackets (<>) with
the dimension name:
O ly
!HIERARCHIES=<>
l & On
n a e
The Hierarchies section is required for new and existing dimensions that use the replace
t e r U s
method. It is optional for existing dimensions that use the merge method. Parent and
Child properties are required. You can control the member order in a dimension based
I n
on the order in which members exist in the source. Members of existing dimension are
reordered during a merge or replace import.
c l e
r a
O
Planning: Create and Manage Applications 9-9
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Optionally, you can include member properties in the Hierarchies section, as in the
following example:
!Hierarchies=Entity
'Parent|Child|Data Storage|Currency|Valid For Plan1|Valid For
Plan2|Aggregation for Plan1|Aggregation for Plan2
#root|Canada|StoreData|CAD|Y|Y|+|+
#root|United States|StoreData|USD|Y|Y|+|+
United States|Oregon|StoreData|USD|Y|Y|+|+
United States|California|StoreData|USD|Y|Y|+|+
California|San Francisco|StoreData|USD|Y|Y|+|+
United States|Washington|StoreData|USD|Y|Y|+|+
If you include the member properties in the Hierarchies section, you should omit the
Members section.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
9-10 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Setting Up Members
!Members=Scenario
'Name|Data Type|Start Year|End Year|Start Period|End
Period|Use Beginning Balance|Enable Process Management|Smart
List|ExchangeRate Table
Current|Unspecified|FY07|FY10|Jan|Dec|N|N||A_FXRate
Actual|Unspecified|FY08|FY08|Jan|Dec|N|N||A_FXRate
Budget|Unspecified|FY09|FY11|Jan|Dec|Y|Y||B_FXRate
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Setting Up Members
c l
r a
You set up members for a dimension in a Members section. You begin the section by
entering the following line, replacing the angle brackets (<>) with the dimension name:
!Members=<> O ly
l & On
You need not include columns for all member properties for the dimension class, and you
n a e
can set up the columns in any order.
e r s
Here are the valid Planning properties for the following dimension classes:
t U
I n
c l e
r a
O
Planning: Create and Manage Applications 9-11
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Account
Name,Use application distribution, DataType, Valid for
Plan1,Valid for Plan2, Valid for Plan3, Valid for Wrkforce, Valid
for Capex, Aggregation for Plan1, Aggregation for Plan2,
Aggregation for Plan3, Aggregation for Wrkforce, Aggregation for
Capex, UDA, Member Formula, Data Storage, Two Pass Calc, Smart
List, Time Balance, Skip Value, Expense Reporting, Account Type,
ExchangeRate Type, Data Type, Source Plan Type
Entity
Name, Currency, Valid for Plan1,Valid for Plan2, Valid for Plan3,
Valid for Wrkforce, Valid for Capex, Aggregation for Plan1,
Aggregation for Plan2, Aggregation for Plan3, Aggregation for
Wrkforce, Aggregation for Capex, UDA, Member Formula, Data
Storage, Two Pass Calc, Smart List, Data Type
Scenario
Name, Valid for Plan1,Valid for Plan2, Valid for Plan3, Valid for
Wrkforce, Valid for Capex, Aggregation for Plan1, Aggregation for
Plan2, Aggregation for Plan3, Aggregation for Wrkforce,
Aggregation for Capex, UDA, Member Formula, Data Storage, Two
m y
Pass Calc, Enable Process Management, Smart List, Data Type,
Start Year, End Year, Start Period, End Period, Use Beginning
d e
Balance, ExchangeRate Table
c a
Version
e A
l
Name, Valid for Plan1, Valid for Plan2, Valid for Plan3, Valid for
c
r a
Wrkforce, Valid for Capex, Aggregation for Plan1, Aggregation for
Plan2, Aggregation for Plan3, Aggregation for Wrkforce,
O ly
Aggregation for Capex, UDA, Member Formula, Data Storage, Two
Pass Calc, Enable Process Management, Smart List, Data Type,
Version Type
l & On
Period
n a e
t e r U s
Name, Valid for Plan1,Valid for Plan2, Valid for Plan3, Valid for
Wrkforce, Valid for Capex, Aggregation for Plan1, Aggregation for
I n
Plan2, Aggregation for Plan3, Aggregation for Wrkforce,
Aggregation for Capex, UDA, Member Formula, Data Storage, Two
l e
Pass Calc, Smart List, Data Type, Period Type
c
r a
O
9-12 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Year
Name, Valid for Plan1,Valid for Plan2, Valid for Plan3, Valid for
Wrkforce, Valid for Capex, UDA, Member Formula, Data Storage, Two
Pass Calc, Smart List, Data Type
Currency
Name, Scale, Valid for Plan1,Valid for Plan2, Valid for Plan3,
Valid for Wrkforce, Valid for Capex, Thousands Separator, Decimal
Separator, Negative Sign, Negative Color, UDA, Member Formula,
Data Storage, Two Pass Calc, Smart List, Data Type, Currency Code,
Symbol, Triangulation Currency, Reporting Currency
Generic
Name, Two Pass Calculation, Valid for Plan1,Valid for Plan2,
Valid for Plan3, Valid for Wrkforce, Valid for Capex, Data
Storage, Apply Security
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-13
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Managing Aliases
!Members=HP_Account
'Name|Alias=English|Alias=German|Data Type|Source Plan Type|Account Type
Gross Profit|Total Gross Profit|Bruttogewinn|Currency|Plan1|Revenue
Net Sales|Total Net Sales|Nettoumsatz|Currency|Plan1|Revenue
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Managing Aliases
c l
r a
Aliases are alternate names for members. For numeric member names, you can include
an alphanumeric alias so that you recognize what the number represents. For example,
O ly
the entity 400 could have an alias of London.
& On
If an application uses multiple languages for member descriptions, you add properties to
l
format:
n a e
the Members section header for each language set up in the Alias dimension. Use this
Alias=<Language>
t e r U s
I n
In the slide example, the member section header includes properties for descriptions in
c l e
English and German.
r a
O
9-14 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
You can also add properties to either the Hierarchies or PropertyArray section headers
for each language set up in the Alias dimension. Since only the Hierarchies section is
required when you import into existing dimensions, including aliases in the Hierarchies
section is more efficient than maintaining a separate PropertyArray or Members section.
If you are creating a new dimension, you can also maintain aliases in the Hierarchies
section, since the Members section is not required.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-15
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Loading Metadata Process
c l
r a
You load metadata by creating and running import profiles. Profiles include important
information about the dimensions to be imported, such as new dimensions, whether to
O ly
merge or replace dimensions, dimension and member properties, and relationships
between members.
l & On
n a e
t e r U s
I n
c l e
r a
O
9-16 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Creating Import Profiles
c l
r a
You create profiles to import metadata from flat files or interface tables. You can import
metadata into Shared Library or directly into an application.
O ly
To create import profiles:
l & On
a e
1. Select File > Import > Create Profile.
n
t e r U
2. Enter a name for the profile.
s
The New Profile dialog box is displayed.
I n
3. From the Import Type drop-down list, select FlatFile or Interface Tables.
c l e
4. Optional: Enter a description for the profile.
r a
5. In the Application list, select either an application or Shared Library as the
O destination.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
9-18 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Mapping Dimensions
Source File HyPlan2 ap plication
SME_Currency Currency
SME_Alias Alias
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Mapping Dimensions
c l
r a
You can create dimensions, or you can map a dimension in the load file to an existing
dimension. For each dimension in the flat file, a drop-down list displays dimensions of the
O ly
same dimension type in the destination application. You can select New Dimension, or
& On
you can select an existing dimension to which you want to map the flat file dimension.
l
NOTE
n a e
If a dimension name in the destination exactly matches a dimension name of the
selection.
t e r U s
same dimension type in the load file, the matching dimension is the default
I n
c l e
r a
O
Planning: Create and Manage Applications 9-19
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
When you map a dimension in the load file to an existing dimension in the Dimension
Library, you can merge or replace members:
The Merge option updates members that exist in the application with the information
in the file. If the file contains members that do not exist in the application, the missing
members are added.
The Replace option replaces the existing metadata with the metadata in the file. If a
dimension member that exists in the application is not present in the metadata file
that you are loading, the Replace option removes the member from the application.
The Merge as Shared option determines how to process a member if the parent
specified in the load file is different than its parent or parents in the application. If you
select Merge as Shared, the member is added as a shared member to the parent
specified in the load file. If you do not select Merge as Shared, the member is
removed from its current parents in the application and added to the parent specified
in the load file.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
9-20 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Mapping Properties
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Mapping Properties
c l
r a
For each column for a dimension in the flat file, a drop-down list of properties for the
same dimension class in Dimension Library is displayed. You select the property to
which to map the column.
O ly
NOTE
l & On
n a e
If a property name in Dimension Library exactly matches a property name in the
load file, that property is mapped by default.
t e r U s
I n
Select Ignore Nulls if you want blank values for a record in the load file to be ignored.
Otherwise, blank values are treated as data, and the property status is changed from
l e
default to defined. A status of defined prevents the property from inheriting values from
c
ancestors.
r a
O
Planning: Create and Manage Applications 9-21
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Running Import Profiles
c l
r a
After creating a profile, you are prompted to execute the profile. If you want to run it at
another time, you can initiate the import from the Import Dimensions dialog box.
O ly
& On
To access the Import Dimensions dialog box:
l
a e
1. Select File > Import > Import Dimensions.
n
Flat File
t e r U s
2. Select one of the following options:
Interface File I n
c l e
r a
O
9-22 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
You can view, edit, or delete import profiles after you select a file to upload.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-23
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Viewing Job Status
c l
r a
You view the status of the metadata load in the Job Console. The Job Console shows the
current job status and the percent completion. You can click the Import Results link to
O ly
view an error log for each dimension included in the load.
l & On
To view the status of the metadata load:
n a e
Select Navigate > Administer > Library Job Console
t e r U s
After the import job runs, you can select the click here to navigate to jobs link to
n
see the job status for your job.
I
c l e
r a
O
9-24 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Viewing Import Errors
c l
r a
You can view import errors by selecting a job and clicking on the link for Import Results.
You can select a specific error and view the details. After you correct the error, you can
import the file again.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-25
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Best Practices
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Best Practices
c l
a
Consider the following recommendations for maintaining dimension metadata:
r
O ly
Rather than maintaining a separate Members section, you can manage your property
values by including them in the Hierarchies section. Keep in mind that if you need to
l & On
include the member name, then you need to include a Members section.
a e
Since the syntax for member formulas includes a semicolon and since the content for
n
t e r U s
member formulas can be quite extensive, the recommendation is that member
formula property is placed as the last column.
I n
Instead of creating an import file by hand, you can work with the EPMA File
c l e
Generator, a file generating utility to generate an initial file that you can modify as
needed. You can generate ads files from the following sources:
r a
- existing Planning applications as long as they are version 9.3 or later
O
9-26 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-27
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Interface tables
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Loading Metadata from Interface Tables
c l
r a
Performance Management Architect interface tables are database tables used to import
metadata from external systems into Shared Library. They represent an alternative to flat
files.
O ly
l & On
For details on using interface tables to load metadata, see the Oracle Hyperion
a e
Enterprise Performance Management Architect Administrators Guide.
n
t e r U s
I n
c l e
r a
O
9-28 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 9-29
Module 3 Loading Metadata
Lesson 9 Loading Metadata from a File
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
9-30 Planning: Create and Manage Applications
L E S S O N 1 0
Creating Applications 10
Objectives
At the end of this lesson, you should be able to:
Set up application name, plan types, time periods, and currency
Select dimensions
Configure application settings
Add dimensions to applications from Shared Library
Activate dimension associations
Adjust Performance Settings
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Application Creation Process
c l
r a
You create applications with the Application Wizard. The wizard enables you to create
applications with all the required components to ensure successful deployment. The
O ly
wizard contains applicable property and dimension information by application type. For
l & On
example, you make the designation for plan types for Planning applications but you
would not select plan types for Financial Management applications.
n a e
After you create the basic application structure, you can add dimensions and further
e r
customize the application.
t U s
I n
c l e
r a
O
10-2 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
Plan types
Currency specifications
Time periods
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Plan for Application Setup
c l
a
Before initiating the Application Wizard, you determine the following application criteria:
r
O ly
Number of plan types and their names
& On
Default currency and whether or not the application is a multicurrency application
l
a e
Base time periods, weekly distribution, start year, and start month
n
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-3
Module 3 Loading Metadata
Lesson 10 Creating Applications
Plan Types
Additional m odules
available for
purchase
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Plan Types
c l
r a
You can indicate up to five plan types for an application. An Essbase database is created
for each plan type. After creating an application, you cannot change the name or number
of plan types.
O ly
& On
The number of plan types depends on the needs of your organization. For example, if the
l
n a e
Sales Department has a yearly revenue plan, and the finance department has a P&L
plan, you can define two plan typesRevenue and P&L.
e r s
As you create accounts, entities, and other elements of the application, you associate
t U
I n
them with plan types. The association ensures that the database contains only relevant
application dimensions, members, and data values, and that application design, size,
l e
and performance are optimized.
c
r a
O
10-4 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
You can also share data between plan types, to ensure that the database remains small
and efficient. For example, the Revenue plan may include several sales detail accounts
that roll up into a Total Product Sales account. You can configure the P&L plan to include
the Total Product Sales account, omitting sales detail accounts. Then, you can bring the
data value for Total Product Sales into your P&L plan without account details.
NOTE
You can add WFP (Workforce Planning) and CAPEX (Capital Asset Planning)
plan types to an existing application if you purchased these modules.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-5
Module 3 Loading Metadata
Lesson 10 Creating Applications
Currency Specifications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Currency Specifications
c l
r a
You specify the default currency for entities in the application and establish if the
application supports currency conversions.
O ly
Multiple currency support (also known as currency overrides) is available for level 0
& On
members, regardless of their base currency. If you select multiple currencies, two
l
option later.
n a e
dimensions are created in Essbase: Currency and HSP_Rates. You cannot change this
t e r U s
I n
c l e
r a
O
10-6 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
Time Periods
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Time Periods
c l
r a
You select the base time period and the monthly distribution pattern based on the
number of fiscal weeks in a month. The base time period options are the bottom-level
O ly
time periods in the application. Predefined options are months or quarters. You can
& On
create custom base time periods, such as weeks or days.
l
n a e
You can select monthly distribution patterns to determine how data entered into a
summary time period is distributed or spread among base time periods. During data
t e r U s
entry, users can enter data into summary time periods, such as years or quarters.
Planning distributes these values over the base time periods that constitute the summary
time period.
I n
l e
You can select a weekly distribution pattern other than Even Distribution. In that case,
c
Planning treats quarterly values as if they were divided into 13 weeks and distributes
r a
weeks according to the selected pattern. For example, if you select the 5-4-4 pattern,
Planning treats the first month in a quarter as if it has five weeks, and the last two months
Oin the quarter as if they have four weeks. The options for the weekly distribution pattern
are available only if you select the 12 Months base time period option.
Planning: Create and Manage Applications 10-7
Module 3 Loading Metadata
Lesson 10 Creating Applications
You specify the fiscal start year, the fiscal start month, and the total number of years in
the application. The fiscal start year determines the starting fiscal year for the application.
You cannot change the option later. When specifying the fiscal start year, consider how
much historical data your organization needs in the application.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
10-8 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Setting Up Application Components
c l
r a
You set up the application name, application type, and application characteristics in the
first step of the Application Wizard. You can create applications in Application Library or
O ly
Shared Library provided that you are assigned the application creator role. Application
& On
Library displays all applications in Performance Management Architect.
l
Application types:
n a e
Type
t e r s
Description
U
Generic
c
Planning l e Planning application
O ra
Consolidation Financial Management application
Type Description
Profitability Profitability and Cost Management application
Essbase Essbase application
d e
8. Optional: If you are creating a year dimension, select Create A New Year Dimension and
proceed to step 11.
ca
and proceed to step 12.
e A
9. Optional: If you are creating a multicurrency application, select Use Multiple Currencies
c l
10. In the Planning Period section, enter the details for the new period dimension.
Field r
Actiona
New Period Dimension O ly
Enter the name of the period
Name
l & On
dimension
Base Time Period
n a e
Select the type of base time
periods from 12 Months,
t
Fiscal Start Month
e r U s
Quarters, or Custom
Select the fiscal start month
I n
Weekly Distribution Select the weekly distribution
r a
O
10-10 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
Field Action
Prefix If you selected Custom for base
time periods, enter a prefix
Periods Per Year If you selected Custom for the
base time periods, enter the
number of custom periods per
year
11. In the Planning Year section, enter the details for the new period dimension.
Field Action
New Year Dimension Enter the name of the year
Name dimension
Fiscal Start Year Enter the fiscal start year
Total Year Enter the total number of years
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-11
Module 3 Loading Metadata
Lesson 10 Creating Applications
Selecting Dimensions
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Selecting Dimensions
c l
r a
The Dimension Selection page displays all required dimensions for a Planning
application. Dimension types are automatically categorized and displayed with a gray
O ly
shaded heading. For example, the sections include: All Plan Types, Custom Dimensions,
and Other Dimensions.
l & On
n a e
When selecting dimensions, you can either select an existing dimension from Shared
library, or create a dimension. You must select dimensions for each dimension in the
e r s
Dimension List before you can advance in the wizard. The Application Wizard
t U
automatically creates the required dimension associations.
I n
c l e
r a
O
10-12 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
Dimensions within an application are either local or shared. Local dimension are
maintained within the application. Adding or removing dimension members or changing
member properties has no effect on dimensions in other applications or in Shared
Library. For example, two applications have an account dimension named HY_Accounts
designated as a local dimension. Modification to members of HY_Accounts in one
application has no effect on the HY_Accounts dimension in the other application.
You cannot add members, delete members, or change the hierarchy structure of shared
dimensions within an application. Instead, you maintain shared dimensions centrally in
Shared Library. You can, however, override the property settings for members of shared
dimensions within an application. For example, in Shared Library, the Draft 2 member of
the HP_Version dimension has the Enable for Process Management property enabled. A
particular application that shares HP_Version requires that Draft 2 member not be
enabled for process management. You can override the Enable for Process
Management property for the Draft 2 member of HP_Version in the application.
You cannot associate a local dimension with a shared dimension. For example, if you
have an attribute dimension in the Shared Library called Colors, you cannot associate it
with a local dimension in an application called Products.
e
2. In the Dimension list, select a dimension from Shared Library. A
c l
3. Optional: Select Local Dimension if you want to create a local copy of the dimension
r a
from Shared Library, instead of sharing the dimension.
4. Click Next.
O ly
& On
The Application Settings pane is displayed.
l
To create dimensions:
n a e
t e r U s
1. In the Dimension list, double-click a dimension.
I n
A list of dimensions in Shared Library that have the same
c l e
dimension type as the selected dimension is displayed.
2. In the Dimension list, select Create New Dimension.
O
Planning: Create and Manage Applications 10-13
Module 3 Loading Metadata
Lesson 10 Creating Applications
3. Enter a name.
4. Click OK.
The dimension is added to the dimension list. Local Dimension is
selected automatically because the dimension does not exist in
Shared Library.
5. Click Next.
The Application Settings screen is displayed.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
10-14 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
Planning properties.
Select the
application label
to configure the
application
settings.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Configuring Application Settings
c l
a
You configure application-wide settings in the properties grid.
r
To configure application settings: O ly
l & On
1. Select the Planning application name to display its dimension properties in the
a e
Properties grid. Properties that you set at the highest level apply to all dimensions in
n
the application.
t e r U
2. Select the Planning category.s
I n
3. Indicate up to five valid plan types: Plan1, Plan2, Plan3, Workforce, and Capex.
l e
4. Set up names for the plan types. Plan type names can contain up to 8 characters.
c
r a
5. Select a date format.
O
Planning: Create and Manage Applications 10-15
Module 3 Loading Metadata
Lesson 10 Creating Applications
6. Specify the default currency and indicate whether the planning application contains
multiple currencies.
7. Set the base time periods (monthly, quarterly, or custom), weekly distribution, and
starting fiscal year and month.
NOTE
You cannot change the Start Year. The value for Start Year corresponds to the first
year in the Year dimension.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
10-16 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Adding Dimensions from Shared Library
c l
r a
An application in Shared Library shows a selection of dimensions required for that
application. After you create an application, it is displayed in the Application pane in
Shared Library.
O ly
l & On
You can add dimensions to applications from Shared Library as local copies or as shared
copies:
n a e
application.
t e r U s
LocalChanges that you make to the original do not affect the copy in the
I n
SharedThe copy is linked to the original in Shared Library. Member and member
c l e
property changes made in Shared Library are automatically propagated to the
application.
r a
Planning application requirements:
O
Planning: Create and Manage Applications 10-17
Module 3 Loading Metadata
Lesson 10 Creating Applications
Required dimensions are determined by the application type. For the Planning
application type, an application requires one dimension from each of these
dimension classes: Account, Entity, Scenario, Version, Period, Year, Currency (for
multicurrency applications).
The Entity dimension requires an association with the Currency dimension to enter a
value for the currency property.
The Scenario dimension requires an association with the Period and Year
dimensions to enter starting and ending time period values.
If you want to assign attribute values, aliases, or UDAs to dimension members, you
must associate the Attribute, Alias, or UDA dimensions with those base dimensions.
For example, if you want to assign attributes, aliases, or UDAs to the Entity and
Account dimensions, you must associate the Attribute, Alias, and UDA dimensions
with their respective properties in the base dimensions, Entity and Account.
Dimension association guidelines:
You need not associate a smart list with a main dimension to select a smart list in the
Smart List property field.
Dimensions created in Shared Library do not have default associations. You
m y
associate local dimensions in the application.
d e
associate shared dimensions in Shared Library, not in applications. However, you
c
Within an application, local dimensions cannot be associated with shareda
dimensions.
e A
l
For dimensions loaded from flat files, you must specify associations in the flat file.
c
a
If you upgrade an application, the associations may already be assigned.
r
To add dimensions to applications:O ly
l & On
1. In the Shared Library pane, select a dimension.
n a e
2. Drag the selected dimension to the application pane.
e r s
The Dimension Status Selection dialog box is displayed.
t U
n
3. Select Local or Shared.
I
c l e
4. Click OK.
r a
O
10-18 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c l
Changing Local Dimensions to Shared Dimensions
r a
You can change a local dimension to a shared dimension. When you share a local
dimension, you can either replace the members of the dimension in the Shared Library
O ly
with the members from the local dimension, or merge the local dimension members with
l & On
the members in the Shared Library. When you select merge, members present in the
local dimension but not in the Shared Library are added to the dimension in the Shared
Library.
n a e
t e r U s
To change local dimensions to shared dimensions:
I n
1. Right-click a local dimension in an application and select Share Dimension.
c l e
The Share Dimension dialog box is displayed.
a
2. Perform an action:
r
O
Planning: Create and Manage Applications 10-19
Module 3 Loading Metadata
Lesson 10 Creating Applications
If the dimension does not currently exist in Shared Library and you want to add it,
proceed to step 3.
If the dimension exists in the Shared Library and you want to link the local
dimension to it, proceed to step 4.
3. Select Create a New Shared Dimension, and click OK to add a dimension.
4. In the Dimension list, select the dimension that you want to share with the local
dimension.
5. Select Merge to add the members of the dimension in the application to those in the
Shared Library, or Replace to replace the members in Shared Library with the
members in the application.
6. Click OK.
NOTE
If the name of the dimension you selected from Shared Library is different
than the name of the local dimension, the local dimension is renamed to
match the dimension in Shared Library.
m y
d e
TIP
c a
To change a shared dimension to a local dimension, right-click the dimension and
select Detach.
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
10-20 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
Property values loaded or m anually entered
override both Shared Library and ancestor values.
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Overriding Property Settings
c l
r a
Member property settings for shared dimensions in applications are inherited from the
Shared Library. If you modify a members properties in Shared Library, that members
O ly
properties are also updated in all applications that share the dimension. However, from
l & On
within an application, you can override the settings inherited from Shared Library. If you
edit a member property in an application, the Shared Library property setting is
a e
overridden for that application. Updates to the property setting in Shared Library no
n
TIP
t e r
longer update the property setting in the application.
U s
I n
To return a member property that has an override value to its default state, so that
c l e
it inherits from Shared Library, right-click the member and select Remove Value.
r a
O
Planning: Create and Manage Applications 10-21
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Excluding and Showing Members
c l
r a
You can exclude selected members from shared dimensions for individual applications.
For example, for a revenue forecasting application, you could exclude all the balance
O ly
sheet accounts from the Account dimension. You can also show excluded members.
To exclude members:
l & On
n a e
In a shared dimension, right-click a member and select Exclude Member.
t e r U s
If you exclude a parent member, its descendants are excluded as
well.
I n
c l e
r a
O
10-22 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-23
Module 3 Loading Metadata
Lesson 10 Creating Applications
Filtering Members
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Filtering Members
c l
r a
You can filter shared dimensions for individual applications to include only a subset of the
members from Shared Library. For example, an application shares the Entity dimension
O ly
in Shared Library. You could filter the Entity dimension to include only members of Entity
& On
that are descendants of the North America member.
l
To filter shared dimensions:
n a e
e r s
1. Right-click a shared dimension in an application and select Filter Members.
t U
n
The Member Selector dialog box is displayed.
I
c l e
2. In the list of members on the left, select a member to which to apply a filter and move
it to the Selections list.
r a
O
10-24 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
3. In the Selections list, right-click the member and select a filter option:
Option Description
Member Includes the selected member
only.
Children Includes the children of the
selected member.
Descendants Includes the descendants of the
selected member.
Siblings Includes the siblings of the
selected member.
Parent Includes the parent of the selected
member.
Ancestors Includes the ancestors of the
selected member.
Inclusive Combines with other filters to
include the selected member. For
example, if you select Descen-
dants and Inclusive, you include
the selected member and its
m y
descendants.
d e
4. Repeat steps 2 and 3 to create as many filters as required.
c a
5. Click OK.
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-25
Module 3 Loading Metadata
Lesson 10 Creating Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c l
Synchronizing Local Dimensions with Shared Library
r a
If you are maintaining a dimension locally, you can use the Synchronize command to
copy members to or from a dimension in Shared Library. Synchronization does not
O ly
create a permanent link between the dimensions. For example, you synchronize an
l & On
account dimension in Shared Library with a local account dimension in an application.
Afterwards, you add 10 new accounts to the dimension in Shared Library. The new
a e
accounts are not added to the dimension in the application until you synchronize again.
n
t e r U s
To synchronize local dimensions with shared librar y:
I n
1. Right-click a local dimension and select Synchronize.
l e
2. Perform an action:
c
a
Select To Shared Library to copy members from the local dimension to Shared Library.
r
O
10-26 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
Select From Shared Library to copy members from Shared Library to the local
dimension.
The Synchronize Dimension dialog box is displayed.
3. In the Dimension list, select the dimension in Shared Library with which to
synchronize the local dimension.
4. Perform an action:
Select Merge to add the members of the dimension in the source dimension to
those in the destination dimension.
Select Replace to replace the members in the destination dimension with the
members in the source dimension.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-27
Module 3 Loading Metadata
Lesson 10 Creating Applications
Add button
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Activating Dimension Associations
c l
r a
After adding a dimensions from Shared Library to an application, you must activate the
required dimension associations for each dimension.
O ly
& On
To activate all dimension associations in the application:
l
a e
Right-click the application name and select Activate all associations.
n
t e r U s
To activate dimension associations for a selected dimension:
I n
1. In the application, right-click a dimension and select Dimension Associations.
c l e
The Edit Dimension Association dialog box is displayed. The
Master Associations list shows all dimension associations defined
O
10-28 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
2. Select the dimension associations required for the application, and click Add.
The dimension associations are added to the Active Associations
list.
3. Click OK.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-29
Module 3 Loading Metadata
Lesson 10 Creating Applications
Most Dense
Dense
Dimensions
Least Dense
Smallest
Aggregating
Sparse
Dimensions
Largest
Smallest
Nonaggregating
Sparse
Dimensions
m y
Largest
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Adjusting Performance Settings
c l
r a
Before loading and calculating data, you can optimize the Essbase database outline
settings to analyze their effect on block size. You can modify a dimensions sparse and
O ly
dense settings and its order in the outline.
l & On
The order of dimensions is critical to the structure and performance of Essbase
n a e
databases. Dense dimensions calculate faster than sparse dimensions, so dimensions
should be in order of most to lease dense.
t e r U s
I n
To adjust performance settings:
1. In the application pane, right-click an application and select Performance settings.
c l e
The Plan Type Performance Settings dialog box is displayed.
r a
O
10-30 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 10 Creating Applications
3. In the Density column, double-click a cell and select one of the following:
SparseSparse dimensions lack data values for the majority of member
combinations. A sparse dimension is a dimension with a low percentage of
available data positions filled.
DenseFor dense dimensions, there is a high probability that one or more data
points is occupied in every combination of dimensions.
4. You can optimize performance by ordering dimensions according to the following
guidelines:
Make Period and Account dense.
m y
d e
Order dense dimensions from the most to least dense. The most dense is usually
Account, followed by Period (Time).
c a
A
Separate sparse dimensions into aggregating and nonaggregating dimensions.
Place aggregating dimensions before nonaggregating dimensions. Order sparse
e
c l
dimensions from smallest to largest. (The aggregating dimensions aggregate
children into the parent to create new data; the nonaggregating dimensions do not
r a
create new data by the hierarchies; for example, a Scenario or Version dimension.)
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 10-31
Module 3 Loading Metadata
Lesson 10 Creating Applications
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
10-32 Planning: Create and Manage Applications
L E S S O N 1 1
Deploying Applications 11
Objectives
At the end of this lesson, you should be able to:
Validate applications
Compare applications
Deploy applications
Review Planning outlines in Essbase Administration Services
Redeploy applications
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Deployment Process
Validate applications.
Deploy applications to a Planning
server.
Create the application files in
relational and OLAP databases.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Deployment Process
c l
r a
In Performance Management Architect, you create applications to describe the
dimensionality and other information required for an application. To create the application
O ly
itself, you first validate, and then deploy the application to a Planning server. The
l & On
deployment process automatically creates an application on the application server. You
validate and deploy applications from the Performance Management Architect
Application Library.
n a e
t e r U s
I n
c l e
r a
O
11-2 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Validating Applications
Review the
Validation
Log.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Validating Applications
c l
r a
You validate applications before deploying them to ensure that applications meet certain
requirements. Some of the items validated include the following:
O ly
The Start Year property is defined and contains four digits (for example, 2007).
l & On
Members in Year dimensions start with FY, followed by a two-digit year (for example,
FY07).
n a e
e r s
The Start Year property and first year in the Year dimension describe the same year
t U
in different formats. For example, if the Start Year is 2007, the first year must be
FY07.
I n
l e
The Start Month property is defined.
c
a
The Default Alias Table property is defined.
r
O The Default Currency property is defined.
To validate applications:
1. In Workspace, select Navigate > Administer > Application Library.
2. Right-click an application and select Validate > Application (V).
The Job Task box indicates that a job was submitted.
3. Select Click here to navigate to jobs.
4. Review the job summary section.
5. Perform an action:
m y
log.
d e
If validation errors occurred, click on the link for the validation log and review the
c
If no validation errors occurred, close the Library Job Console window.a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
11-4 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Comparing Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Comparing Applications
c l
a
You can compare applications to determine how they differ from those stored elsewhere.
r
Comparison methods:
O ly
l & On
Compare to Shared LibraryCompares the dimensions and members in an
application to the dimensions and members in Shared Library View in the Dimension
Library
n a e
e r s
Compare to Deployed ApplicationCompares an application to a deployed
application
t U
I n
c l e
r a
O
Planning: Create and Manage Applications 11-5
Module 3 Loading Metadata
Lesson 11 Deploying Applications
To compare applications:
1. Right-click an application, select Compare, and select a comparison method:
m y
Compare to Shared Library
d e
Compare to Deployed Application
c a
A
2. After the progress bar indicates 100% complete, click View Results.
e
The Compare window is displayed.
c l
a
3. In the Dimension Compare Results pane, perform an action:
r
O ly
Select a dimension to view the results in the Application Compare Summary pane.
& On
Select a member to view the results in the Property Compare Results pane.
l
NOTE
n a e
t e r
When a member is added or deleted from a shared dimension, the application
s
inherits the changes from Shared Library. You can determine that changes were
U
I n
made by noting the sync status, and you can run one of the comparison reports to
determine the differences.
c l e
r a
O
11-6 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Deploying Applications
The deployment process creates a Planning application.
Select Shared
Services project.
Select a Data
Create an Source or create
Essbase a new one.
outline.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Deploying Applications
c l
r a
In order to work with Planning applications, after you set up your application in
Performance Management Architect, you deploy the application to the Planning
application server and Essbase.
O ly
l & On
You cannot change the following properties and application characteristics after you
n a e
deploy an application. Therefore, before deploying an application, ensure that the
properties and characteristics are set correctly.
t e r U s
Whether the application uses a single currency or multiple currencies. For example,
I n
after deploying with multiple currencies, you cannot later use a single currency.
Likewise, with a single-currency application, you cannot later select Multiple
l e
Currency.
c
r a
Default application currency. Data values might not be correct because existing
currency values are not converted to the new currency.
O
Planning: Create and Manage Applications 11-7
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Type of calendar. For example, if you set base time period to 12 months, you cannot
later change it to quarters.
Fiscal start month.
Start year. For example, if you set the start year to 2007, you cannot change it to
2006. You can, however, add years after the first year.
Added years. For example, if the deployed application includes FY09, you cannot
remove this year.
Weeks distribution pattern. For example, if you set weeks distribution to 445, you
cannot later change it to 544 or Even.
Plan type, such as Valid For Plan1. You can add only the Workforce and Capex plan
types to deployed applications. You cannot remove plan types. For example, if you
deploy an application with the properties Valid For Plan1 and Valid For Plan2, you
can later add a property named Valid for Workforce. However, you cannot later
remove Valid for Plan2 or Valid for Workforce.
Added dimensions. You can add up to 20 dimensions, including the required
dimensions. You can rename dimensions.
Required dimensions. Single-currency applications require these dimensions:
m y
d e
Scenario, Version, Entity, Account, Period, and Year. Multicurrency applications
Currency.
ca
require these dimensions: Scenario, Version, Entity, Account, Period, Year, and
e A
To deploy applications:
c l
r a
1. Ensure that the Planning Application Server is started.
2. In Workspace, select Navigate > Administer > Application Library.
O ly
3. Right-click an application and select Deploy.
l & On
4. If validation errors occur, view the validation error details.
n a e
t e r
a. Click View Errors to view the number of errors.
U s
b. Click Details to view the list of errors.
I n
c l e
r a
O
11-8 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Option Description
Instance Name Select the Planning instance for which the application should
be deployed. Instances are used to link Performance
Management Architect to a Planning application server.
Application Server Select the Planning Web application server to which the
application is deployed.
Shared Services Project Select the Shared Services project for the application.
Purge Transaction Select this option to delete the transaction history after a
history on success successful deployment.
Data Source Either select the data source for the application or create a
data source. Data sources link the relational database and the
Essbase server. For Planning, each application must be
associated with a data source.
Create Outline Select this option to deploy an application for the first time or
to recreate the Essbase outline.
Refresh Outline Select this option to refresh the Essbase outline. You use this
option to refresh or update the Essbase outline for an
application that was already deployed.
m y
Create Security Filters
e
Optional: Select this option to generate security filters for all
users in the application.
d
Shared Members
c a
Optional: Select this option to apply access permissions to
Security Filters
Validate Security Filter
shared members.
e A
Optional: Select this option to identify security filters that
Limit
c l
exceed the Essbase security filter limit of 64 kb per row.
Deploy Rules
a
Select this option to deploy rules defined in Calculation
r
Manager.
O ly
Reminder:
l & On
n a e
If you are deploying a Planning application for the first time, select Create Outline
to create the Essbase outline.
6. Click Deploy.
t e r U s
I n
The application is deployed to the Planning Web application
c l e
server as a Planning application.
r a
O
Planning: Create and Manage Applications 11-9
Module 3 Loading Metadata
Lesson 11 Deploying Applications
7. Select Navigate > Administer > Library Job Console to view the status of the deployment.
The Library Job Console displays the current job status and the
percent completion. You can click the Attachment link to view an
error log. Should deployment of the application fail, the error log
contains valuable information about the reasons for the failure.
When the deployment is completed, the status and deployment
timestamp are updated in the Application Library, and the
application is deployed to the Planning Web application server as
a Planning application.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
11-10 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Outline .otl
Calculation Script .csc
Report Script .rep
Load Rules .rul
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Essbase Databases
c l
r a
You can create Essbase databases either at the time of deployment or as a separate
action. To create the database outline, you select the Create Outline option when you
deploy the application.
O ly
& On
An Essbase database is created for each plan type defined in a Planning application to
l
a e
store and calculate its data. You can store the following objects in an Essbase database:
n
t e r s
Database outlinesDefine the structure of the multidimensional database
consisting of dimensions and member hierarchies. The file extension is .otl.
U
I n
Calculation scriptsEnable you to perform custom calculations in addition to the
standard consolidations and the standard mathematical operations defined in the
l e
database outline. The file extension is .csc.
c
r a
Report scriptsDefine reports based on data in one or more databases. The file
extension is .rep.
O
Planning: Create and Manage Applications 11-11
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Data load rulesDefine editing operations on data files that populate the database.
The file extension is .rul.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
11-12 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 11 Deploying Applications
V iew
pane
Outline
E ditor
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Reviewing Planning Outlines
c l
Administration Services Console:
r a
After deploying Planning applications, you can perform the following tasks in
c l e
r a
O
Planning: Create and Manage Applications 11-13
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Co rpBud
Corporate Budgeting application
BalSheet
Balance Sheet database (plan type)
In cStmt
Incom e Statement database (plan type)
Revenue
m y
Revenue database (plan type)
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Essbase Directory Structure
c l
r a
Applications are created with their own directory with the same name as the application.
Server-based applications are in a directory under the
O ly
\Hyperion\Essbase\EssbaseServer\App directory; for example,
l & On
\Hyperion\Essbase\EssbaseServer\App\CorpBud. The databases associated with the
application are in a directory under the applications directory; for example,
a e
\Hyperion\Essbase\EssbaseServer\App\CorpBud\BalSheet. This directory structure is
n
t e r
located on the Essbase server.
U s
Essbase objects such as calculation scripts, load rules, and reports scripts are typically
I n
located in the database directory to which they are associated. However, they can also
be located in a client directory on your local client machine; for example,
l e
\Hyperion\Essbase\Client.
c
r a
O
11-14 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Redeploying Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Redeploying Applications
c l
r a
If you change the metadata, you should redeploy the application to update the relational
and Essbase databases. Redeploying performs a merge or a replace of the application
O ly
metadata based on the types of changes you made since the last deployment. For
l & On
example, if you moved or deleted members in any hierarchy in the application,
redeployment of the application performs a replace for the metadata changes. If you
a e
made only property value changes to the application since the last deployment,
n
t e r U s
redeployment of the application performs a merge for the metadata changes.
I n
c l e
r a
O
Planning: Create and Manage Applications 11-15
Module 3 Loading Metadata
Lesson 11 Deploying Applications
Summary
In this lesson, you should have learned to:
Validate applications
Compare applications
Deploy applications
Review Planning applications in Essbase Administration Services
Redeploy applications
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
11-16 Planning: Create and Manage Applications
L E S S O N 1 2
Objectives
At the end of this lesson, you should be able to:
Create exchange rate tables
Enter exchange rates
Generate currency conversion calculation scripts
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Currencies and Exchange Rates
c l
r a
You can plan, forecast, and analyze financial information in single or multiple currencies.
If your application is enabled for multiple currencies, users can see values converted
O ly
from the local currency to a reporting currency.
n a e
currencies
t e r
Enable budget preparers in various countries to create plans in their native
U s
I n
Show summary data in reports in a particular currency
l e
Summarize values from multiple currencies into a single currency
c
For example, the base currency for Japan is the Japanese yen and that for the United
r a
States is the U.S. dollar. When you view a data form that contains values for Japan, if the
Odisplay currency is set to U.S. dollars, the exchange rate for the Japanese yen is used to
convert the values to U.S. dollars.
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Exchange Rates Tables Overview
c l
r a
You enter exchange rate values through exchange rate tables. You can create exchange
rate tables to correspond to different business scenarios.
O ly
For example, you can create an exchange rate table named Actual Rates and another
l & On
named Budget Rates. You can then associate the Actual Rates table with the Actual
scenario, and associate the Budget Rates table with the scenarios Forecast and Budget.
n a e
in Planning.
t e r
After you create the exchange rate tables in EPMA, you can enter exchange rate values
U s
I n
Calculation scripts run business calculations for your application. Typically, you create
calculation scripts for your application using Business Rules. However, Planning
l e
automatically generates the calculation scripts needed for currency conversion.
c
r a
O
Planning: Create and Manage Applications 12-3
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
Properties of Budget
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Exchange Rate Tables
c l
r a
You create exchange rate tables in Performance Management Architect by associating
them with scenarios. After you deploy the application, the exchange rate tables are
O ly
created in the Planning relational database, and users can enter exchange rate values in
Planning.
l & On
You can create as many exchange rate tables as the application requires, each
n a e
representing a different business scenario. For example, you can name the tables
t e r U s
Forecast, Actual, and Budget, and associate them with multiple scenarios. Each
scenario can be associated with only one exchange rate table. After creating a scenario,
I n
you can select the exchange rate table to use for currency conversion.
c l e
r a
O
12-4 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 12-5
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
Enter Exchange
Rates
Application
default currency
m y
Shortc ut m enu options
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Entering Exchange Rates
c l
You can enter conversion values between the default currency and all currencies set up
r a
in the currency module. When you set up exchange rate tables, only the default currency
O ly
and triangulation currencies are available as destination currencies. You can enter
exchange rates from all source currencies to the default or triangulation currencies.
l & On
Types of Exchange Rates
n a e
Historical
t e r U s
Three types of exchange rates are associated with a currency:
Average
I n
Ending
c l e
r a
O
12-6 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
You specify the exchange rate type used for each account when you set up accounts in
EPMA. For average and ending rates, you can enter rates for each time period. For the
historical rate type, you enter a single rate that is used for all time periods.
l & On
exchange rates to all scenarios. If you create a table or modify one, you must refresh the
application for the new exchange rates to be stored in the plan types.
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 12-7
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
Assumptions:
U.S. dollar is the default application currency.
Euro is a reporting currency.
British pound is a local currency available in the application.
Rate
British pounds to U.S.dollar 1.4
r a
currency, not to reporting currencies. Planning automatically derives the rates for
O ly
converting to reporting currencies by triangulation through the application currency.
l & On
For example, suppose the U.S. dollar is the application currency and the European euro
is a reporting currency. You enter 1.4 as the rate for converting British pounds to U.S.
a e
dollars and 1.2 as the rate for converting European euros to U.S. dollars. To determine
n
t e r
the rate for converting British pounds to European euros, Planning divides the British
s
pound rate by the European euro rate: 1.4/1.2 = 1.16.
U
I n
c l e
r a
O
12-8 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
When you set up currencies, you specify whether the currency has a triangulation
currency that allows the currency to be translated to a different currency through a
common third currencythe triangulation currency. You enter exchange rates for
converting from the currency to its triangulation currency. The exchange rates between
the currency and other currencies that triangulate through the triangulation currency are
calculated automatically. These rates are called implied rates.
For example, the British pound and the Danish krone might both be set to triangulate
through the European euro. After rates are entered for converting between the British
pound and the European euro and between the Danish krone and the European euro,
the rates for converting from the British pound to the Danish krone and from the Danish
krone to the British pound are automatically calculated.
NOTE
If you modify a currencys triangulation currency, you must reenter exchange rates
for the triangulation currency property, and you must refresh the application so
that the exchange rates are transferred and stored. You cannot select the
applications default currency as a triangulation currency.
m y
Determining the Calculation Method
d e
When you enter exchange rates for converting from one currency to another, you select
c a
either Multiply or Divide as the calculation method. For example, if you enter 2 as the rate
for converting British pounds to U.S. dollars, and you select Multiply as the calculation
method, 1 British pound is converted to 2 U.S. dollars.
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 12-9
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
100.00 USD
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
l
Exchange Rates and the HSP_Rates Dimension
c
r a
Multicurrency applications store exchange rates in the HSP_Rates dimension. The
HSP_Rates dimension is created in the Essbase databases for multicurrency
O ly
applications and is not available in Planning. The HSP_Rates dimension has two sets of
l & On
members: input members and currency rate members.
The input members are HSP_InputValue and HSP_InputCurrency. HSP_InputValue
n a e
stored data values, and HSP_InputCurrency stores currency types for those data values.
t e r U s
When you enter or load a data value in a cell for the local currency, it is stored at the
intersection Local -> HSP_InputValue. The intersection Local -> HSP_InputCurrency
I n
stores the currency code for that value.
c l e
The currency members of the HSP_Rates dimension store the exchange rates for each
currency. There is an HSP_Rates member for each currency added to the application.
r a
O
12-10 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
Generating Currency
Conversion Calculation Scripts
Select Administration > Manage Currency Conversion
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
l
Generating Currency Conversion Calculation Scripts
c
r a
Two types of calculation scripts are associated with currency conversion: one that copies
exchange rates to account members and one that executes the currency conversion. To
O ly
generate these calculation scripts, you select options on the Manage Currency
Planning.
l & On
Conversion window. You run calculation scripts using the Launch Business Rules task in
n a e
When you generate the calculation script, you select the reporting currencies, scenarios,
t e r U s
and versions for which you want the calculation to run. You can generate currency
conversion calculation scripts to correspond to different business processing scenarios.
I n
Typically, you create a separate calculation script for each scenario.
c l e
r a
O
Planning: Create and Manage Applications 12-11
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
converted values.
e A
versions, you must run an aggregation to populate upper-level members with the new
c l
Because the Currency Conversion calculation script runs for all entities and accounts in
r a
your application, it typically is run by budget administrators rather than end users. If end
users need to see their data converted to a reporting currency, they should use the
O ly
Calculate Currencies business rules associated with data forms.
l & On
a e
Calculate Currencies Business Rule
n
t e r
In addition to generated currency conversion calculation scripts, a dynamically system-
s
generated business rule is associated with data forms. It converts data from the local
U
I n
currency to the reporting currency for only the members currently displayed on the data
form. This business rule enables planners to view converted values for the entered data.
c l e
r a
O
12-12 Planning: Create and Manage Applications
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
Summary
In this lesson, you should have learned to:
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 12-13
Module 3 Loading Metadata
Lesson 12 Setting Up Exchange Rates
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
12-14 Planning: Create and Manage Applications
M O D U L E 4
Overview
The aim of this module is to discuss the requirements for data load files,
and when to use data load rules to load data into Essbase. You also see
how data is calculated within a dimension, data blocks calculation order,
and discuss calculation scripts. You load data using Administration
Services. You calculate the database to calculate data for upper level
members in the hierarchy.
Lessons in this module include:
Loading and Calculating Data: Overview
Loading Data
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
L E S S O N 1 3
Objectives
At the end of this lesson, you should be able to:
Define the requirements for data load files
Describe the setup for data load rules
Describe the setup for data staging using interface tables
Describe loading data using ETL tools
Identify how data is calculated within dimensions
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Data Loads
You can:
Load data directly into the Essbase database for each plan
type.
Use any of the following for loading data:
Administration Services
Performance Management Architect interface tables
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Data Loads
c l
r a
Planning creates an Essbase database for each plan type in your application. You can
load data directly into the Essbase database that corresponds to the plan type in your
O ly
application. When you create your Planning application, the Essbase databases do not
contain data.
l & On
n a e
You can load data values from external systems into your Planning application. For
example, you might want to load data for actuals from your ERP system so that you can
calculate variances.
t e r U s
n
You can use the following methods to load data:
I
c l e
Data can be extracted to ASCII text files (flat files) from external systems and loaded
using Essbase data load rules.
r a
Data can be loaded with Performance Management Architect interface tables.
O Data can be loaded with an ETL tool using Essbase and Planning adapters.
d e
If you are using a rules file for loading data, a rules file validated for data loading
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 13-3
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Use Essbase to load data from flat files into your Planning application.
ACTUAL FINAL
EUROPE GROSS SALES JAN 2008 1000
EUROPE NET INCOME FEB 2008 400
ASIA NET INCOME FEB 2008 300
ASIA GROSS SALES JAN 2008 200
O ly
the Actual scenario and the Final version. If a dimension has the same value for all rows,
the slide.
l & On
you can place it in the header as a page dimension, as shown in the second graphic on
Requirements:
n a e
e r s
Each data point must be tagged with a member from each dimension.
t U
I n
Data must be for bottom-level members, unless you are loading data into a target
version.
c l e
Data is scanned from the top of the file and from left to right.
r a
Each field (item) in a record (row) must be separated by a valid delimiter.
O
13-4 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
A member name or alias must be enclosed in double quotation marks (" ") if it
contains blanks, numeric characters (09), dashes, or unary operators. It must also
be displayed exactly as it is in the outline.
Members of the same dimension must be in the same column or row.
Members of different dimensions can be together only on the page header. They
cannot be used together in any other row or column.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 13-5
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Multicurrency Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Multicurrency Applications
c l
r a
Applications that support multiple currencies include an additional dimension called
HSP_Rates to store exchange rates. The HSP_Rates dimension includes the following
members:
O ly
& On
HSP_InputValueThis member stores data values.
l
a e
HSP_InputCurrencyThis member stores currency types for the data values.
n
t e r U s
HSP_Rate_<XXX> This member stores currency for multicurrency applications
(XXX represents the currency).
I n
You load data to the HSP_InputValue member and the local currency. The
l e
HSP_InputCurrency member is not displayed in Planning. However, if the default
c
currency is overridden, the new currency is stored along with its value in the database.
r a
By storing the new currency, Essbase can apply a different currency value to the data
displayed for HSP_InputValue.
O
13-6 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Data load rules map external data values to the Essbase database
2009 Budget Dr aft 1 USREG L ocal 210-MI CH N001 HSP_I nputValue Jan
2009 Budget Dr aft 1 USREG L ocal 210-MI CH N001 HSP_I nputValue Feb
2009 Budget Dr aft 1 USREG L ocal 210-MI CH N001 HSP_I nputValue Mar
Rules applied
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Data Load Rules
c l
r a
You use data load rules to delineate how data is loaded into Essbase databases. Load
rules can perform certain actions on the data originating from external data sources as it
O ly
is loaded into the Essbase database. For example, if the data file contains fields that are
& On
not needed, you can ignore those fields during the data load.
l
data load:
n a e
You create data load rules when any of the following criteria need to be applied during a
e r s
Ignore fields or strings in the data source.
t U
I n
Change the order of fields by moving, joining, splitting, or creating them.
l e
Map the data in the data source to the database by changing strings.
c
r a
Change the data values in the data source by scaling the data values or adding them
to existing values in the data source.
O
Planning: Create and Manage Applications 13-7
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
13-8 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Data Staging: Interface Tables
c l
r a
In Performance Management Architect, interface tables are database tables used to
import data from external systems into Performance Management Architect.
O ly
You can create multiple interface databases, and the database type can be different than
& On
the database for the interface tables; for example, a Microsoft SQL database, and Oracle
l
interface tables.
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 13-9
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Loading Data Using ETL Tools
c l
r a
You can load data into Planning using ETL tools such as Oracle Data Integrator, and
Data Integration Management. In order to use any ETL tool, you need to have the
corresponding Planning adapter.
O ly
& On
Oracle Data Integrator (ODI) enables you to connect and integrate Planning with any
l
n a e
database by using the Oracle Data Integrator Adapter for Planning. The adapter provides
a set of modules for loading metadata and data into Planning, Workforce Planning, and
Capital Asset Planning.
t e r U s
I n
c l e
r a
O
13-10 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Data Calculations
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Data Calculations
c l
calculate the database. r a
Typically, you load data into the level 0 members of a database. After loading data, you
n a e
Member formulas defined in the outline are applied.
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 13-11
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
m y
d e
c a
e A
Calculations Within Dimensions
c l
r a
The calculation of a dimension follows the outline structure. The order in which members
are calculated follows the order in the outline:
O ly
Calculations start at the lowest level of a branch from top to bottom.
l & On
Calculations move up to the next level when the end of a subbranch is reached.
n a e
The example on the slide depicts the order of a calculation in the Account dimension.
t e r U s
Selected calculations occur in the following order:
n
Within the Margin branch: Sales and then COGS
I
c l e
Within the Profit branch: Margin and then Expenses
Within the Measures branch: Profit, then Inventory, and then Ratios
r a
O
13-12 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
S parse dimension
calculation
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Calculations and Data Blocks
c l
r a
Essbase databases are organized into data blocks. As you recall, a data block consists
of all dense dimensions members in the outline for a unique combination of sparse
O ly
dimension members. There is potentially a data block for each unique combination of
sparse dimension members.
l & On
n a e
The order in which the data blocks are calculated follows the order in which the sparse
dimensions are listed on the Performance Settings screen. The data blocks for the
t e r U s
members of the first sparse dimension listed on the Performance Settings screen of the
Planning Dimension Editor are calculated first, and so on down the list.
I n
c l e
r a
O
Planning: Create and Manage Applications 13-13
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Calculation begins with level 0 data blocks. Level 0 data blocks are those for which each
sparse dimension member is a level 0 member. To calculate the values for a data block,
the Essbase Server calculates the dense dimension members of the data block. After
calculating the values for the level 0 blocks, it aggregates them to derive the value for the
upper-level blocks. This process is repeated for each level of data blocks until the top is
reached.
The graphic shown in the slide depicts the following example:
There are level 0 data blocks for the Los Angeles and San Francisco sparse
dimension members, and an upper-level data block for California, their parent.
The data blocks each have Account and Period dimensions as dense dimensions.
Essbase calculates the Account members and the Period members for the Los
Angeles and San Francisco data blocks, based on the outline structure for the
Account and Period dimensions.
Essbase aggregates the Los Angeles and San Francisco data blocks to derive the
values for the California data block. If the California data block exists, the current
values are overwritten. If it does not exist, the data block is created.
When Essbase calculates the dense dimension members for a data block, it first
m y
d
dimensions are then calculated based on their order on the Performance Settings e
calculates the Account dimension, and then the Period dimension. The remaining dense
screen.
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
13-14 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Calculation Scripts
Calculation scripts:
Contain a series of calculation commands, equations, and
formulas.
Define calculations other than the calculations defined by
the database outline.
Specify how to calculate a database.
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Calculation Scripts
c l
r a
Every database needs at least one calculation script to aggregate unary operators and
execute formulas in the outline. For most database calculations, the default outline
O ly
calculation script provides the required results. You can run the default outline calculation
& On
script from Administration Services Console.
l
calculates a database:
n a e
In certain cases, you may need to write a calculation script to control how Essbase
e r s
You can use Business Rules as a graphical environment .
t U
I n
You can create native Essbase calculation scripts by using a text editor or the
Essbase calculation script editor.
c l e
r a
O
Planning: Create and Manage Applications 13-15
Module 4 Loading Data and Calculating the Database
Lesson 13 Loading and Calculating Data: Overview
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
13-16 Planning: Create and Manage Applications
L E S S O N 1 4
Loading Data 14
Objectives
At the end of this lesson, you should be able to:
Describe data load rules
Create load rules for Administration Services
Load data using Administration Services
Load data using rules files
Load data using interface tables
Describe loading data using ETL Tools
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
c
Loading Data Using Administration Services l
r a
You use Administration Services to load data values into Planning applications. You load
data directly into the Essbase databases that correspond to the plan types in the
application.
O ly
To load data values: l & On
n a e
t e r
1. In Administration Services, select a database, right-click, and select Load data.
U s
2. Click Find Data File to select a file to load.
I n
3. Optional: Click Find Rules File to select a rules file.
l e
4. Click OK.
c
r a
O
14-2 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
Creating Data Load Rules
c l
r a
Data load rules are sets of operations that are performed on data from external data
sources when the data is loaded into an Essbase database. Data load rules map
O ly
external data values to the Essbase database.
l & On
You specify these options when you create data load rules:
Set file delimiters
n a e
e r s
Associate the rules file with an outline
t U
n
Define header information
I
c l e
Map fields to member names and column fields
Manipulate column fields and replace text strings
r a
O
Planning: Create and Manage Applications 14-3
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
Opening Data Sources
c l
r a
After you select to create a rules file, the Data Prep Editor is opened. Next, open data
sources to see what data needs to be changed. The data source can be located on the
O ly
Essbase Server, locally, or on the network. Examples of valid data source files are
& On
Microsoft Excel and Lotus 1-2-3 spreadsheets, plain text files, and Essbase export files.
l
Setting File Delimiters
n a e
t e r U s
File delimiters are the characters that separate fields in the data source. By default, the
rules file separates fields using tabs. You can set the file delimiter to be a comma, tab,
I n
space, fixed-width column, or custom value. Usually, you set the file delimiter
immediately after opening a data source.
c l e
r a
O
14-4 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 14-5
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
Skip tw o lines and map to Budget
O ly
fields. Header records describe the contents of the data source and how to load data
values into the database.
l & On
n a e
A rules file contains records that translate the data in the data source to the database. As
part of that information, the rules file can also contain header records.
t e r U s
Defining Header Information in Rules Files
I n
Headers are used only during data loads or dimension building. They do not change the
c l e
data source. Header information in a rules file is not used if a dynamic reference in the
rules file points to a header record in the data source.
r a
O
14-6 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 14-7
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
c l
Associating Column Fields with Dimensions and Members
r a
When loading data from a data source file, you must specify how the fields in the data
source file map to the dimensions in the database. Data load rules refer to columns in the
O ly
data source file. When setting up a data load rule, you must match each column of
l & On
information to a specific dimension or dimension member. Each column of information
contains either a member label or a data element. In a data load, you must specify every
a e
dimension in the database in either the data source or the rules file. If the data source
n
t e r
does not identify every dimension in the database, you must identify the missing
dimensions in the rules file.
U s
I n
Mapping Fields to Member Names
l e
When the data source is loaded, a rules file can translate fields in the data source to
c
match member names without changing the data source. The rules file performs the
r a
following tasks:
O
14-8 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
If a field represents information that is not data and is extraneous to the outline, you can
ignore the field by selecting the Ignore field during data load check box. You use the
e A
Manipulating Column Fields
c l
Your data source may not always have columns in the correct sequential order, or you
r a
may need to manipulate column details such as duplicating, parsing, or concatenating
O ly
columns to create unique member names.
Action
& On
Description
l
Move
a e
Changes the sequential order of columns
n
Split
t e r s
Parses fields; used for segregating columns where the source file has
fields of variable length and does not have field delimiters
U
Join
Create Using JoinI n Joins two or more columns
Creates a column or set of columns; used to duplicate a column
c l e
Create Using Text Creates a column that contains any text, including white spaces
r a
O
Planning: Create and Manage Applications 14-9
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
You can:
Use a rules file to replace
text strings so that fields
map to Essbase member
names during a data load
Replace text strings without
changing the data source
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Replacing Text Strings
c l
r a
You can use a rules file to replace text strings so that the fields map to Essbase member
names during a data load. The data source is not changed. For example, if the data
O ly
source abbreviates New York to NY, you can have the rules file replace each NY with
New York while loading the data.
l & On
Replace options:
n a e
Option
Replace
t e r U s
Description
Use to enter the text string to be replaced.
With
I n Use to enter the text string to replace the one in the Replace text
c l e
Case-Sensitive
box.
Select to construct a condition based on a case-sensitive string.
r a
O
14-10 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
Option Description
Match Whole Word Select to indicate that Essbase should replace the text string only
when it occurs as an entire word. If the text string is embedded in
another word, it is not replaced.
Replace All Select to indicate that Essbase should replace all text strings that
Occurrences match the text string in the With field. By default, Essbase replaces
the first occurrence.
New Click to add a new line for additional changes entered in the Replace
and With fields.
Delete Click to remove items from action lists.
Original Select to leave existing fields in their original case. By default, this
option is selected.
Lowercase Select to change all characters of the field to lowercase.
Uppercase Select to change all characters of the field to uppercase.
Prefix Use to enter a text string to be added at the beginning of the field
values. (You cannot use parentheses in the Prefix text box.)
Suffix
Drop leading/trailing
Use to enter a text string to be added to the end of the field values.
Select to remove leading and trailing white spaces around fields. (A
m y
spaces
e
field with leading or trailing white spaces does not map to a member
d
even if the name within the white spaces is an exact match.)
Convert spaces to
underscores a
Select to change white spaces in field values to underscores.
c
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 14-11
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Validating and Saving Rules Files
c l
r a
You can validate a rules file to ensure that the member and dimension mapping defined
in the rules file maps to the outline. However, validation does not ensure that the data
source is loaded properly.
O ly
& On
The rules file is validated against the associated outline. When the Essbase Server
l
n a e
finishes the validation, the Validate Rules dialog box is displayed. It contains information
about the validation process, including fields that did not map to the outline. If the rules
t e r U s
file is validated without problems, you can use it to load data.
I n
After validating the rules file, save it to the Essbase Server or locally. The name must be
a valid name in your operating system. In addition, the rules file name that you specify
l e
must be eight or fewer alphanumeric characters in length. Essbase automatically adds
c
the .rul extension.
r a
O
14-12 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 14-13
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
Loading Data Using Rules Files
c l
a
After the rules file is generated, you can load data using the rules file.
r
To load data using rules files: O ly
l & On
1. From the Administration Services Console, Enterprise View or a custom view, select
a e
the database. Right-click and select Load data.
n
t e r U s
The Data Load dialog box is displayed.
2. Select one or more data sources.
I n
3. Click the Find Rules File button and select the rules file name.
c l e
The rules you selected are displayed on the Data Load dialog box
O
14-14 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 14-15
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
Interface tables
ETL Planning
Performance
Management
Architect
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Staging Data with Interface Tables
c l
r a
You use Interface tables to create a staging area for loading data from outside systems
(ERP, ETL, GL, and so on) into Performance Management Architect for use in Planning.
O ly
Using interface tables to load data helps you to streamline the data load process. You
any time.
l & On
can predefine a data set that you want to import into Planning and stage it for loading at
n a e
You can create multiple Interface Tables for staging data.
NOTE
t e r U s
I n
Before you can load data from interface tables, you must first have a relational
database set up to store the information in the tables, and then you must run the
l e
configuration utility to configure the tables in the new relational database.
c
r a
O
14-16 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Interface Tables
c l
Management Architect.
r a
You create Interface Tables within the Data Synchronization module of Performance
O ly
You can load data as well as metadata into Shared Library using interface tables.
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 14-17
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
Interface Performance
ETL
Tables Management Architect
System
Plan ning
Data
Synchronizatio n
General
Flat File
m y
e
Ledger
System
a d
Copyright 2008, Oracle. All rights reserved.
A c
Loading Data Using Interface Tables
c l e
r a
In EPMA, you can load data into Planning selecting either a flat file or interface tables.
After you stage data in your ETL system and you create interface tables, you can use the
O ly
interface tables to load data into Planning. The data remains in the interface tables so
l & On
that you can repeat the process to load data into another application or into the same
application at another time. Data is loaded directly into Essbase which you can use in
a e
Planning. You do not load data to the Planning relational database using this method.
n
t e r U s
To load data using interface tables:
I n
1. In Performance Management Architect, select a Planning application.
l e
2. Right-click and select Action > Import.
c
r a
O
14-18 Planning: Create and Manage Applications
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Loading Data Using ETL Tools
c l
r a
You can use ETL tools to load data into Planning applications. If you have a simple data
load, you can load a flat file. However, if you have a complex data load, you can use an
O ly
ETL tool such as Oracle Data Integrator (ODI). You also can schedule an ODI data load
& On
to occur during an off peak time.
l
n a e
ODI is a graphical tool for loading data into your Planning environment. For applications
managed using Performance Management Architect, you can load data into Planning
e r s
and Essbase by using the Planning adapter.
t U
I n
Adapters depict the structure of the database into which you are loading data. Adapters
are populated with the relevant metadata relationships for a dimension. Therefore,
l e
before loading data into Planning you must ensure that the metadata (dimension
c
members) exist in both the Planning relational database and Essbase database. If
r a
necessary, refresh the Essbase database to synchronize your changes.
O
Planning: Create and Manage Applications 14-19
Module 4 Loading Data and Calculating the Database
Lesson 14 Loading Data
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
14-20 Planning: Create and Manage Applications
M O D U L E 5
Setting Up Security 14
Overview
The aim of this module is to provide an overview of security in Planning.
You learn how to provision users and user groups in Shared Services for
your Planning application. You also learn how to assign access rights to
elements of your Planning application.
Lessons in this module include:
Provisioning Users and Groups
Setting Up Access Rights to Planning Applications
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
L E S S O N 1 5
Objectives
At the end of this lesson, you should be able to:
Describe security in Planning
Describe user provisioning in Shared Services
Provision users and groups for Planning
Generate provisioning reports
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Planning Security Overview
c l
r a
Security in Planning is based on user privileges. User privileges are system roles and
access rights that can be assigned to users or to groups.
O ly
Groups are sets of users who need similar access rights. After users and groups are
l & On
defined, you can assign the users and groups access rights to application elements. For
example, you can assign a user or a group access to Entity dimension members or data
forms.
n a e
e r s
Access rights for users and groups can vary by application and can be assigned for the
t U
following application elements:
I n
Scenario, Version, Account, Entity, and user-defined custom dimension members
c l e
Data forms and business rules
r a
Task lists
OAfter you establish or update user and group security and assign member access, you
must refresh the Planning application to update to the Essbase security filters.
Levels of Security
Data forms
and task lists
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Levels of Security
c l
Planning provides security at four levels:
r a
Users must provide a valid ID and password to log on to the system.
O ly
Users can launch only those tasks to which they have been given access. For
& On
example, you can give users the ability to create data forms but not dimension
l
members.
n a e
been granted access.
t e r
Users can open only those data forms and task lists (objects) to which they have
U s
I n
Users can view and modify data only for dimension members to which they have
been granted access.
c l e
r a
O
Planning: Create and Manage Applications 15-3
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
User Authentication
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
User Authentication
c l
r a
User login information for Hyperion applications is stored outside the applications in an
authentication directory. The information is maintained by a central authentication directory.
O ly
An authentication directory is a centralized store of users and passwords, user groups, and
& On
perhaps corporate information, such as employee IDs or job tiles. The following types of
l
a e
authentication directories are supported:
n
2003
t e r U s
Windows NT LAN Manager (NTLM) on NT 4.0 or higher, Windows 2000, and Windows
I n
Lightweight Directory Access Protocol (LDAP) version 3 or later
l e
Microsoft Active Directory (MSAD) server, Windows 2000 SP3 or later
c
r a
You can grant access to your Planning applications to any user or group in an
authentication directory. When you grant a group access to an application, the users in the
Task Security
Administration menu,
m y
Administration menu,
administrators view interactive users view
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Task Security
c l
Task security determines the tasks in an application that a user can access. You assign
r a
task security by assigning a role to a user. Each role is associated with a set of tasks. For
O ly
example, interactive users cannot change dimension members, so the dimension
change option is not available to interactive members.
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 15-5
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
Object Security
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Object Security
c l
Within your Planning application, you can assign security to specific objects, such as data
r a
forms and task lists. For example, you can allow all users to access the standard
O ly
expenses data form but allow only payroll managers to use the salary expense data form.
l & On
n a e
t e r U s
I n
c l e
r a
O
15-6 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
Data Security
RJackson
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Data Security
c l
Setting up data security enables you to protect data and prevent unauthorized users from
r a
changing data. For example, you can restrict access to certain data elements in an
application.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 15-7
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
User and Group Provisioning Overview
c l
r a
User provisioning enables centralized management of users, their role assignments and
their access rights to applications created under various application groups of various
O ly
products. To perform provisioning for Planning applications, you use Shared Services
Console.
l & On
Any user with the Provisioning Manager or Administrator role in an application can
perform provisioning.
n a e
e r s
The main nodes of the Shared Services Console:
t U
I
User Directories
n
l e
Application Groups
c
r a
O
15-8 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
User Directories
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
User Directories
c l
In Shared Services Console, you view user directories that consist of users and groups.
r a
User directories can be provided (set up) natively or externally. External directories
O ly
(LDAP, NTLM, and MSAD) hold users and groups in each directory. External directories
& On
are typically corporate directories.
l
n a e
You provision users and groups by assigning user roles in an application. A user can
receive a combination of individual and group role assignments.
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 15-9
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
Application Groups
Application groups bundle instances of Hyperion products that
compose an implementation.
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Application Groups
c l
Before you can provision users or groups for a Planning application, the application must
r a
be registered in Shared Services and belong to an application group.
O ly
An application group is an instance of Hyperion products that are grouped to compose an
l & On
implementation. For example, a Planning application group may consist of a Planning
application, an Essbase application, and a Financial Reporting Server instance. You can
a e
add one or more applications to an application group.
n
t e r U s
When you create a Planning application, it is automatically registered with Shared
Services and assigned to the Default Application group. You can move applications to
I n
application groups, as needed.
l
NOTE
c e
An application can be associated with only one application group.
r a
O
15-10 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
To create an application group, right-click Application Groups, and select New. You then
give the application group a name and description and assign applications as required.
TIP
In a practical sense, you can think of an application group as a type of folder.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 15-11
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
m y
d e
c a
e A
Provisioning Users and Groups
c l
r a
Within a user directory, you provision users and groups to your Planning application. You
provision users to enable them to access applications and perform application tasks. You
O ly
can select Provision from the Administration menu, or you can right-click the user and
select Provision.
l & On
To provision users or groups
n a e
e r s
1. To open the User Directories within Shared Services, select Start > Programs > Hyperion >
t U
Foundation Services > Shared Services.
I n
2. Log onto Shared Services.
c l e
Shared Services Console is displayed.
r a
3. In the view pane, expand User Directories.
O
15-12 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
4. Select and expand Users, to provision and assign roles to users, or Groups, to
provision and assign roles to groups.
5. Click Search to display a list of all users or groups.
6. Select the user or group that you want to provision.
7. Select Administration > Provision, or right-click a user or group and select Provision.
8. Expand the application group that contains the application for which you want to
provision the user or group and for which you want to assign roles.
9. Expand the application for which you want to provision the user or group and for
which you want to assign roles.
10. Select the role or roles that you want to assign to the user.
11. Click Add.
12. Click Save.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 15-13
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
User Roles
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
User Roles
c l
r a
You assign user roles to users and groups based on the tasks that users need to perform
in applications. Planning provides user roles that can be assigned to users and groups.
O ly
The following global Shared Services roles are also used in Planning:
l & On
Application Creator Creates applications. This is a Performance Management
Architect role.
n a e
e r s
Project Manager Creates and manages application groups in Shared Services.
t U
I n
Dimension Editor Creates profiles and imports dimensions. This is a Performance
Management Architect role.
c l e
Create Integrations Creates Shared Services data integrations (the process of
r a
moving data between applications) using a wizard.
m y
Planner
e
Planners enable e-mail notification; input, submit, and view data; use
d
reports that have been built by others; run data integration routines
c a
designed by others; execute business rules and other processes
associated with validating and preparing data; view and use task
lists; use Smart View; and submit information and data for approval.
View User A
View users have limited access to view data in a Planning
e
c l
application. Typically, the view user is an executive who wants to see
business plans during and at the end of the budget process.
Offline User
r a
Offline users can take Planning data forms offline and work with
them in Smart View.
Mass Allocation O ly
Users assigned the Mass Allocation role can spread data by using
l & On
the Mass Allocation function. Mass Allocation spreads data either
proportionally or relatively to other members in the outline. Even
a e
though you run Mass Allocation from data forms, data is spread to
n
t e r
members even if they are not displayed on the data form. This role
s
only should be assigned to a select few people because there is no
U
undo functionality after spreading data by using Mass Allocation.
I n
Analytic Services Write Users assigned the Analytic Services Write Access role can lock and
Access
c l e send with write access to Essbase. If you assign this role to planners
and interactive users, you give them write access directly to planning
data in Essbase.
r a
O
Planning: Create and Manage Applications 15-15
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
m y
d e
c a
e A
Generating Provisioning Reports
c l
that are provisioned.
r a
You can generate provisioning reports to list the details of the users, groups, and roles
O ly
& On
To generate provisioning reports:
l
a e
Select Administration > View Report
n
t e r U s
I n
c l e
r a
O
15-16 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 15-17
Module 5 Setting Up Security
Lesson 15 Provisioning Users and Groups
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
15-18 Planning: Create and Manage Applications
L E S S O N 1 6
Objectives
At the end of this lesson, you should be able to:
Assign access rights
Import access rights
Create security filters
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Assign access
Add access
View
access
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
Assigning Access Rights
e A
c l
You assign access rights to Planning application elements to protect data from
r a
unauthorized users or groups. The level of security is determined by the access option
that you assign to a user. You can assign access by using dimension member
O ly
relationships or by assigning access directly to individual dimension members. You can
l & On
define unique access rights for each Planning application.
You can assign access rights to the following application elements:
n a e
Scenario, Version, Account, and Entity dimension members
e r s
User-defined custom dimension members, if the Apply Security dimension property
is selected
t U
I n
Data form folders, data forms, and business rules
l e
Task lists
c
You can use the dimension editor to assign access to dimension members, or you can
r a
use the ImportSecurity utility to import access rights information from a flat file.
OYou assign access to data forms in Form Management and to task lists in Task
Management.
Access Options
r a
determine which access option to assign for each user or group. By default, for
interactive users and planners, access is denied to all dimension members, data forms,
and task lists.
O ly
l & On
The following table describes the access options for dimension members and data forms.
Option
n a e
Description
Read
t e r s
Enables users to view the dimension member or data form
U
Write
I n Enables users to view and modify access to the dimension
member or data form
None
r a
O
Planning: Create and Manage Applications 16-3
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Option Description
Assign Enables users to view and use the task list
Manage Enables users to modify the task list
Manage and Assign Enables users to modify, view, and use the task list
None Prevents users from viewing the task list
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
16-4 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Inheritance Options
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Inheritance Options
c l
You can assign access rights to individual dimension members, or you can use an
r a
inheritance option to assign rights to multiple members.
O ly
It is more efficient to assign access rights through an inheritance option. You should
l & On
assign access to individual members only on an exception basis. For example, for the
North America Sales group, you could assign Write access to North America and its
a e
descendants and Read access to North America Headquarters.
n
t e r U s
The following table summarizes the available inheritance options for a selected member:
Option
I n Description
Member
c
Childrenl e The access right is assigned only to the member.
The access right is assigned to all child members of the
r a member.
O
Planning: Create and Manage Applications 16-5
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Option Description
iChildren The access right is assigned to the member and to all of its
child members.
Descendants The access right is assigned to all descendant members of
the member.
iDescendants The access right is assigned to the member and to all of its
descendant members.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
16-6 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
c l
Precedence and Inheritance of Access Rights
You can assign access rights to a member in the following ways:
r a
The user can be assigned direct access to a member.
O ly
The group can be assigned direct access to a member.
l & On
The user or group can be assigned access to a member by relationship, through an
inheritance option.
n a e
t e r U s
Access rights from different sources can conflict with each other. For example, you might
be assigned direct Read access to a member and Write access to the same member
I n
through membership in a group. The following sections explain the rules of precedence.
c l e
r a
O
Planning: Create and Manage Applications 16-7
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Group Precedence
A user might belong to several groups that have conflicting access rights to a member. In
this case, None access take precedence over Write or Read access. Write access takes
precedence over Read access. Here are some examples:
If you have Write access to the Budget member from one group and None access to
Budget from another group, you have None access to Budget.
If you have Read access to the Budget member from one group and Write access to
Budget from another group, you have Write access to Budget.
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
16-8 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
m y
d e
c a
e A
Reporting on Access Assignments
c l
To help you effectively view the current access assignments in an application, you can
r a
generate assigned access reports. You can also generate effective access reports to
help resolve inheritance or precedence conflicts. You generate these reports from
Shared Services Console. O ly
l & On
When you generate an assigned access or an effective access report, you specify what
a e
information to include, as follows:
n
t e r
Specific users and groups or all user and groups
U s
Specific dimensions or all dimensions
Data forms
I n
c l e
Matching access types: Read, Write, or None
You can group results by users or by objects. You also can report on assigned access by
r a
access relationship and inherited group or by effective access, including effective access
origin.
O
Planning: Create and Manage Applications 16-9
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Importing Security Overview
c l
r a
You can load access rights from a text file into Planning by using the ImportSecurity
utility, which enables you to quickly assign access for many members, users, and
O ly
groups. When you import access rights for a member, existing rights assigned to that
l & On
member are overridden. Access to other members is not affected unless you specify the
parameter (SL_CLEARALL) that clears all existing access assignments. You can use
a e
this parameter alone to clear all existing access assignments, or you can use it with other
n
assignments.
t e r
ImportSecurity parameters to replace all existing access assignments with the import file
U s
I n
For example, Joe currently has Write access to OLAP Sales. The import file contains the
following line:
c l e
Joe,eBusiness,write
r a
After importing, Joe has Write access to both OLAP and eBusiness Sales.
O
16-10 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
ca
e A
Creating the Secfile.txt File
c l
a
When creating the import security text file, consider the following points:
r
O ly
The name of the text file must be Secfile.txt, and the file must be saved in the
C:\Hyperion\products\Planning\bin folder.
l & On
All users, user groups, and members must be defined in the application.
n a e
When importing access permissions, only existing access assignments for imported
t e r
permissions remain intact.
U s
members, data forms, and task lists are overwritten. All other existing access
I n
Before importing security for a user-defined custom dimension, you must enable the
l e
Apply Security option. You do that on the Property tab.
c
When importing access rights for many users, you can improve performance by
r a
making sure that users full names are not used in Planning preferences.
O
Planning: Create and Manage Applications 16-11
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Item Description
User name or group The name of a user or user group that is provisioned for
Member name
the Planning application
A member (Account, Entity, user-defined custom
m y
Access rights
d e
dimension, Scenario, or Version) in the application
Read, Write, or None (None is ignored. If there are
c
member name, the line with Write access takes a
duplicate lines for a combination of user name and
precedence.)
e A
Inheritance options
l
@CHILDREN, @ICHILDREN, @DESCENDANTS,
c
@IDESCENDANTS, and MEMBER.
r a
For example, the Secfile.txt file might contain the following lines:
O ly
User1,Account1,read,@CHILDREN
l & On
User2,Entity2,write,@DESCENDANTS
User3,Version_1,write,MEMBER
n a e
Group1,Account101,write,@ICHILDREN
NOTE
t e r U s
I n
If a member, user, or user group name contains a character that you are using as
the delimiter, enclose the name in double quotation marks. For example, if you are
l e
using a space as the delimiter, enclose the name North America in double
c
quotation marks (North America).
r a
O Inheritance options must be in all capital letters.
If you need to import security information into a group that has the same name as a user,
in the Secfile.txt file, append the sl_group parameter to the line that pertains to the
group.
For example:
admin,member1,read,MEMBER
admin,member1,read,MEMBER,sl_group
The first line imports security for a user named admin. The second line imports security
for a group named admin. If you omit sl_group, security information is imported only for
the user named admin.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 16-13
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Syntax: ImportSecurity.cmd
appname,username,password,[delimiter],
[run_silent], [SL_CLEARALL]
Example: ImportSecurity.cmd HYPlan,trnadmin,hyperion
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Importing Access Rights
c l
To import access rights r a
O ly
1. From the Windows task bar, select Start > All Programs > Accessories > Command Prompt.
l & On
2. Navigate to the C:\Hyperion\products\Planning\bin folder.
n a e
t e r U s
I n
c l e
r a
O
16-14 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
3. At the command prompt, type the following command and required parameters,
separating the parameters with commas:
ImportSecurity.cmd appl,admin,password, SL_TAB,1
Parameter Description
delimiter Optional: SL_TAB, SL_COMMA, SL_PIPE, SL_SPACE,
SL_COLON, SL_SEMI-COLON
If no delimiter is specified, the comma default is assumed
to be the delimiter.
run_silent Optional: Whether to execute the utility silently or with
progress messages:
0 = Execute with messages
1 = Execute silently, with no messages
If this parameter is not included in the command line, the
value is assumed to be 0, to display progress messages
during execution.
[SL_CLEARALL] Optional: Whether to clear all existing access
assignments when importing the new access
assignments
This option must be in uppercase.
m y
d e
4. In the bin folder, view the importsecurity.log file to verify the results.
c a
The new security information is now accessible from the
Dimensions task on the Administration menu in Planning.
e A
c l
5. Optional: To see the new security information reflected on the Enter Data page,
a
select the Security Filters option, and refresh the application databases.
r
O ly
You do not need to restart the application server.
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 16-15
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
m y
d e
Copyright 2008, Oracle. All rights reserved.
c a
e A
Creating Security Filters
c l
r a
Data access rights for data forms, task lists, and process management are read from the
Planning relational database and take effect immediately. Essbase databases do not
need to be refreshed.
O ly
l & On
If you have a very large number of users who need security filter updates, you can use
the Manage Database task to update all filters at once. If you have one or just a few
n a e
users who need security filter updates, you can use the Manage Security Filters task. For
t e r U s
example, when you promote an employee, the employees access rights may change. In
that case, you need to update only one security filter rather than all security filters.
I n
When you update security filters using the Manage Database task, you can select
c l e
Shared Members, Validate Limit, or both:
r a
O
16-16 Planning: Create and Manage Applications
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Select Shared Members if you want to create security filters for shared members in
Essbase. Access rights for shared members and their base members may be
different. For example, user MSmith may not have access to the base entity London
for the regional process management hierarchy but may have Read access to the
shared entity London in the alternate corporate reporting hierarchy.
Select Validate Limit if you want to identify any security filter that exceeds the
Essbase security filter limit of 64 KB per row. The names of users who exceed the
limit are displayed in a pop-up window.
NOTE
To validate security filters before updating Essbase, select only Validate Limit only.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Planning: Create and Manage Applications 16-17
Module 5 Setting Up Security
Lesson 16 Setting Up Access Rights to Planning Applications
Summary
In this lesson, you should have learned to:
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
16-18 Planning: Create and Manage Applications