D81987 - Oracle Hyperion Planning 11.1.2 Create & Manage Applications

Oracle Hyperion Planning 11.1.
2: Create &
Manage Applications

Student Guide - Volume I
D63792GC31
Edition 3.1
May 2013
D81987

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

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

This document contains proprietary information and is protected by copyright and
other intellectual property laws. You may copy and print this document solely for your
own use in an Oracle training course. The document may not be modified or altered
in any way. Except where your use constitutes "fair use" under copyright law, you
may not use, share, download, upload, copy, print, display, perform, reproduce,
publish, license, post, transmit, or distribute this document in whole or in part without
the express authorization of Oracle.

The information contained in this document is subject to change without notice. If you
find any problems in the document, please report them in writing to: Oracle University,
500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using
the documentation on behalf of the United States Government, the following notice is
applicable:

U.S. GOVERNMENT RIGHTS
The U.S. Governments rights to use, modify, reproduce, release, perform, display, or
disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names
may be trademarks of their respective owners.

Authors
Lea Jensen
Sandy Krameisen
Theresa Songco

Technical Contr ibutors
and Reviewer s
Eleanor Salerno
Art Hetherington
Bernhard Kinkel
Faye Chan
Ron Reiley
Sergiy Pecherskyy
Vicki Hardiman
Emilya Altman
Sasha Ishenko
Krishnan Narasimha
Charitra Agrawal
Shankar Viswanathan
Gr aphic Designer
Seema Bopaiah

Editor s
Rashmi Rajagopal
Smita Kommini

Publisher s
Pavithran Adka
Srividya Rameshkumar

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

iii
Contents

1 Introduction to Planning
Course Objectives 1-2
Course Agenda: Day 1 1-3
Objectives 1-8
Oracle Hyperion Planning 1-9
Planning Components 1-10
Additional Planning Modules 1-11
Additional Planning-Based Products 1-12
Product Integration 1-13
Planning Architecture 1-14
Client Tier 1-15
Middle Tier 1-16
Data Tier 1-17
External Services 1-18
Oracle Exalytics: Overview 1-19
Planning on Oracle Exalytics: Benefits 1-20
Planning on Oracle Exalytics: Optimized Engine 1-21
Planning Business Process 1-22
Step 1: Entering Data 1-23
Step 2: Adjusting Data 1-24
Step 3: Calculating Data 1-25
Step 4: Annotating Data 1-26
Step 5: Reviewing and Approving Data 1-27
Step 6: Running and Publishing Financial Reports 1-28
Planning Business Scenario 1-29
Step 1: Creating the Application Shell Based On a Design Framework 1-31
Step 2: Managing and Loading Metadata 1-32
Step 3: Creating User-Defined Elements 1-33
Step 4: Setting Up Exchange Rates 1-34
Step 5: Loading and Calculating Data 1-35
Step 6: Setting Up Planning Security 1-36

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

iv
Step 7: Creating and Enhancing Forms 1-37
Step 8: Entering, Annotating, and Analyzing Data 1-38
Step 9: Managing Business Rules 1-39
Step 10: Setting Up and Managing the Approval Process 1-40
Step 11: Creating and Managing Task Lists 1-41
Training Environment 1-42
Quiz 1-43
Summary 1-47
Practice 1-1 Through 1-4 1-48

2 Navigating EPM Workspace
Objectives 2-2
EPM Workspace: Overview 2-3
Launching EPM Workspace 2-5
EPM Workspace User Interface 2-6
Setting General Preferences 2-7
EPM Workspace Navigate Menu 2-9
Opening Applications 2-11
Navigating in Planning 2-12
Quiz 2-16
Summary 2-19

3 Introduction to Applications and Dimensions
Objectives 3-2
Planning Application: Overview 3-3
Application Creation Process 3-4
Data and Metadata Storage: Overview 3-5
Application Framework 3-8
Calendar Structure 3-9
Currency Specifications 3-11
Plan Types 3-12
Planning Dimensions 3-14
Required Dimensions 3-15
User-Defined Dimensions 3-17
Dimension Hierarchies: Genealogy 3-18
Dimension Hierarchies: Generations and Levels 3-19
Drilldown Process 3-20
Dimensions and Data 3-21
Dimensions and Metadata 3-22
Data Block Creation Process 3-23

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

v
Determining the Number of Data Blocks 3-24
Creating Data Blocks and Retrieving Data 3-26
Aggregation, Storage, and Calculation Options 3-28
Aggregation Options 3-29
Data Storage Options 3-30
Calculation Options 3-32
Quiz 3-34
Summary 3-37
Practice 3-1 3-38

4 Creating Applications in Planning Administration
Objectives 4-2
Planning Administration: Overview 4-3
Application Creation Process 4-4
Creating Applications with Planning Application Administration 4-5
Selecting Application Information 4-7
Setting Up the Calendar 4-8
Setting Up Currencies 4-10
Selecting and Naming Plan Types 4-11
Reviewing Application Information 4-12
Modifying Application Registration 4-13
Managing Applications and Data Sources 4-15
Managing Data Sources 4-17
Managing Essbase Databases 4-19
Refreshing Essbase Databases 4-21
Quiz 4-23
Summary 4-26

5 Managing Dimensions
Objectives 5-2
Building Dimension Hierarchies 5-3
Setting Up Dimension Hierarchies 5-4
Modifying Member Properties 5-7
Property Value Inheritance 5-8
Alternate Hierarchies 5-9
Managing Member Hierarchies 5-10
Deleting Members 5-12
Finding Members 5-13
Sorting Members 5-14
Quiz 5-16

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

vi
Summary 5-19

6 Setting Up the Alias, Currency, Year, and Period Dimensions
Objectives 6-2
Creating Aliases 6-3
Adding Currencies 6-5
Customizing Time Periods 6-7
Period and Year Dimensions 6-9
Setting Up DTS Members 6-10
Quiz 6-12
Summary 6-15

7 Setting Up Scenarios and Versions
Objectives 7-2
Scenarios and Versions 7-3
Creating Scenarios 7-4
Creating Versions 7-7
Quiz 7-9
Summary 7-11

8 Loading Metadata
Objectives 8-2
Metadata Load Options 8-3
Loading Metadata with the Outline Load Utility 8-4
Creating Metadata Load Files 8-5
Common Member Properties 8-6
Testing and Loading Metadata Files 8-8
ERP Integrator Load Process 8-11
Lifecycle Management 8-12
Migrating Applications and Artifacts 8-14
Migration Guidelines 8-15
Migrating Applications and Artifacts to a File System 8-17
Migrating Artifacts from a File System to an Application 8-18
Displaying Migration Status Reports 8-20
Quiz 8-21
Summary 8-24

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

vii

9 Setting Up the Entity and Account Dimensions
Objectives 9-2
Entities: Overview 9-3
Entity Members and Plan Types 9-4
Currency Values for Entities 9-6
Adding Entities 9-7
Deleting Entities 9-8
Accounts: Overview 9-9
Account Types 9-10
Time Balance Properties 9-11
Saved Assumptions 9-13
Data Types and Exchange Rate Types 9-14
Adding Accounts 9-15
Aggregating Accounts 9-16
Quiz 9-17
Summary 9-21
Practice 9-1 9-22

10 Creating User-Defined Elements
Objectives 10-2
Creating Member Formulas 10-3
User-Defined Dimensions 10-5
Attribute Dimensions 10-6
Creating Attributes 10-7
Assigning Attribute Values 10-9
Adding User-Defined Attributes 10-10
Smart Lists: Overview 10-12
Creating Smart Lists 10-13
Associating Smart Lists with Members 10-15
Forms and Smart Lists 10-16
Quiz 10-17
Summary 10-21

11 Setting Up Exchange Rates
Objectives 11-2
Currencies and Exchange Rates 11-3
Creating Exchange Rate Tables 11-5
Entering Exchange Rates 11-6
Calculating Implied Rates Through Triangulation 11-8

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

viii
Exchange Rates and the HSP_Rates Dimension 11-10
Generating Currency Conversion Calculation Scripts 11-11
Quiz 11-13
Summary 11-16

12 Loading and Calculating Data
Objectives 12-2
Data Load Options 12-3
Loading Data Values with Administration Services 12-5
Requirements for Data Load Files 12-6
Multicurrency Application Data 12-7
Managing Data with the Outline Load Utility 12-8
Importing Data From Flat Files or RDMS 12-9
Exporting Application Data 12-12
ERP Integrator Data Load Process 12-13
ERP Integrator: Drilling Through and Writing Back Budget Data 12-14
Oracle Data Integrator Data Loads with ETL Tools 12-15
Data Calculations 12-16
Calculation Scripts in Essbase 12-18
Business Rules 12-19
Quiz 12-20
Summary 12-23

13 Setting Up Planning Security
Objectives 13-2
Planning Security: Overview 13-3
Planning Security Levels 13-4
User Authentication 13-6
Planning Roles in Shared Services 13-7
Data and Artifact Security 13-8
User and Group Provisioning in Shared Services 13-9
Provisioning Users and Groups 13-12
Generating Provisioning Reports 13-14
Assigning Access Permissions 13-15
Access Options 13-17
Inheritance Options 13-19
Precedence and Inheritance of Access Permissions 13-20
Reporting on Access Permissions 13-22
Exporting and Importing Access Permissions 13-24

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

ix
Exporting Access Permissions with ExportSecurity 13-27
Importing Access Permissions with ImportSecurity 13-29
Creating Security Filters 13-31
Quiz 13-33
Summary 13-37

14 Creating Forms
Objectives 14-2
Forms: Overview 14-3
Form Components 14-4
Creating Simple Forms 14-6
Setting Up the Form Layout 14-8
Setting Up Properties 14-10
Form Display and Printing Options 14-13
Managing Substitution and User Variables 14-15
Selecting Members 14-17
Setting Up Other Options 14-20
Assigning Business Rules 14-22
Creating Composite Forms 14-24
Setting Up Composite Forms 14-26
Setting POV and Page Properties 14-28
Setting Up Master Composite Forms 14-30
Reviewing Form Design 14-32
Exporting and Importing Forms 14-33
Quiz 14-35
Summary 14-39

15 Enhancing Forms
Objectives 15-2
Creating Rolling Forecasts 15-3
Modifying Rolling Forecast Variables 15-5
Creating Menus 15-7
Creating Formula Rows and Columns 15-10
Building Validation Rules 15-12
Processing Cells for Data Validation 15-15
Specifying Advanced Settings 15-17
Setting Application Defaults 15-19
Setting Up User Preferences 15-20
Setting Individual Display Options 15-22

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

x
Setting Printing Options 15-24
Performing Grid Diagnostics 15-25
Quiz 15-26
Summary 15-29

16 Entering Data in Planning
Objectives 16-2
Navigating Forms 16-3
Viewing Form Instructions 16-5
Data Entry Menus 16-6
Cell Detail Cues 16-7
Navigation Keys 16-9
Showing and Hiding Children 16-10
Viewing Member Detail 16-11
Navigating Forms with Menus 16-12
Submitting Data in Forms 16-13
Copying and Pasting Data 16-15
Saving and Refreshing Data 16-17
Viewing Member Formulas 16-18
Viewing Consolidation Operators 16-19
Selecting Dates 16-21
Entering Data with Smart Lists 16-22
Filtering Data 16-23
Sorting Data 16-25
Spreading Data 16-26
Time Balance Options 16-28
Spreading Data by Using Grid Spread 16-30
Spreading Data by Using Mass Allocate 16-32
Adjusting Plan Data 16-34
Performing Flexible Data Entry 16-35
Quiz 16-36
Summary 16-40

17 Annotating and Analyzing Data
Objectives 17-2
Adding Annotations to Plan Data 17-3
Adding Comments 17-4
Adding Supporting Detail 17-5
Attaching Documents to Cells 17-7

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

xi
Adding Account Annotations 17-9
Clearing Cell Details 17-10
Working with Ad Hoc Grids 17-12
Setting Ad Hoc Grid Options 17-16
Quiz 17-18
Summary 17-21

18 Managing Business Rules
Objectives 18-2
Business Rules: Overview 18-3
Calculation Manager: Overview 18-4
Business Rule Creation Process 18-5
Determining Calculation Requirements 18-6
Launching Calculation Manager 18-7
Rule Components 18-8
Formula Components 18-9
Variables 18-10
Script, Condition, and Loop Components 18-13
Templates: Overview 18-15
Creating Business Rules from Templates 18-17
Setting Up the Copy Data Template 18-19
Setting Up the AmountUnitRate Template 18-21
Setting Up the AllocateLevel to Level Template 18-22
Setting Up the Allocate Simple Template 18-24
Setting Up the Aggregation Template 18-27
SET Commands Template 18-29
Export-Import Data Template 18-30
Creating Custom-Defined Templates 18-31
Creating Business Rules and Rulesets 18-33
Validating and Deploying Rules 18-35
Assigning Business Rule Security 18-37
Launching Business Rules from Planning Forms 18-39
Launching Business Rules from the Planning Tools Menu 18-40
Quiz 18-41
Summary 18-45

19 Setting Up the Approval Process
Objectives 19-2
Approvals: Overview 19-3

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

xii
Creating Planning Unit Hierarchies 19-5
Setting Up Basic Characteristics for Planning Unit Hierarchies 19-6
Selecting Planning Unit Hierarchy Members 19-8
Assigning Planning Unit Owners and Reviewers 19-11
Assigning Scenario and Version Combinations 19-13
Synchronizing Planning Unit Hierarchies 19-15
Exporting and Importing Planning Unit Hierarchies 19-17
Updating the Promotional Path with Validation Rules 19-19
Quiz 19-22
Summary 19-26

20 Managing the Approval Process
Objectives 20-2
Approvals Dashboard 20-3
Planning Unit Approval States 20-5
Reviewer Actions 20-7
Impact of Entity Hierarchy on the Review Process 20-10
Managing the Review Cycle 20-11
Starting the Review Cycle 20-12
Checking the Status of Planning Units 20-15
Viewing the Details of Planning Units 20-17
Viewing and Adding Planning Unit Annotations 20-18
Changing the Status of Planning Units 20-20
Setting Up Out of Office Assistant 20-22
Viewing and Resolving Validation Errors 20-24
Copying Data Between Versions 20-27
Copying Data 20-29
Quiz 20-31
Summary 20-35

21 Creating Task Lists
Objectives 21-2
Task Lists: Overview 21-3
Navigating Task Lists 21-4
Task List Creation Process 21-6
Creating Task List Folders 21-7
Creating Task Lists 21-9
Adding Tasks to Task Lists 21-10
Setting Up Tasks 21-11

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

xiii
Setting Task Properties 21-13
Editing Task Lists 21-15
Assigning Access to Task Lists 21-16
Testing Task Lists 21-18
Printing Task List Reports 21-19
Quiz 21-21
Summary 21-24

A Creating Applications in Performance Management Architect
Objectives A-2
Application Creation Process A-3
Application Criteria A-4
Creating Applications with Application Creation Wizard A-5
Selecting Dimensions A-7
Configuring Application Settings A-9
Working in Shared Library A-10
Managing Dimensions A-12
Adding Dimensions to Shared Library A-13
Shared and Local Dimensions A-15
Creating Members in Dimension Library A-16
Modifying Member Properties A-18
Property Value Inheritance A-20
Alternate Hierarchies A-21
Inserting Members Based on Relationships A-22
Managing Members A-23
Finding Members A-25
Organizing Shared Library A-26
Creating Dimension Filters A-28
Sorting Dimensions in Shared Library A-29
Creating Associations Between Dimensions A-30
Working with Grid Editor A-32
Selecting Members and Properties in Grid Editor Wizard A-33
Saving Dimensions A-35
Adding Dimensions from Shared Library A-36
Synchronizing Local Dimensions with Shared Library A-38
Changing Local Dimensions to Shared Dimensions A-40
Excluding and Showing Members A-42
Overriding Property Settings A-43
Deployment Process A-45
Preparing for Application Deployment A-46

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

xiv
Adjusting Performance Settings A-47
Setting Up Data Type Evaluation Order A-49
Activating Dimension Associations A-51
Validating Applications A-52
Deploying Applications to a Planning Server A-54
Essbase Databases A-56
Planning Outlines A-57
Essbase Directory Structure A-58
Redeploying Applications A-59
Metadata Load Options A-61
Loading Metadata in Performance Management Architect A-62
Formatting Metadata Load Files A-63
Setting Up Dimensions A-65
Setting Up Dimension Associations A-67
Setting Up Parent-Child Relationships A-69
Managing Aliases A-71
Creating Import Profiles A-72
Mapping Dimensions A-74
Mapping Dimension Properties A-77
Running Import Profiles A-79
Viewing Job Statuses A-81
Viewing Import Errors A-82
Staging Data with Interface Tables A-83
Creating Interface Tables A-84
Loading Data by Using Interface Tables A-85
Summary A-87

B Sharing Data with Data Synchronization
Objectives B-2
Data Synchronizer B-3
Synchronization Source Types B-5
Synchronizing Multicurrency Planning Applications B-7
Creating Mapping Tables B-9
Creating Data Synchronizations B-11
Specifying Source Types B-12
Specifying a Destination B-13
Mapping Dimensions B-14
Filtering Dimensions B-15
Applying Filter Criteria B-17
Assigning Default Members B-18
Inserting Mapping Tables B-19

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

xv
Saving Synchronizations B-20
Editing Synchronizations and Mappings B-21
Duplicating Synchronizations and Mappings B-22
Deleting Synchronizations and Mappings B-23
Validating Data Synchronizations B-24
Executing Data Synchronizations B-26
Viewing Data Flows B-28
Summary B-29

C Entering Data with Smart View
Objectives C-2
Smart View: Overview C-3
Smart View Architecture C-4
Connection Types C-5
Setting Up a Shared Connection C-6
Creating Private Connections C-8
Connecting to Data Sources C-10
Setting Smart View Options C-11
Navigating Forms in Smart View C-13
Opening Forms in Smart View C-14
Data Entry in Smart View C-15
Form Formulas in Smart View C-17
Data Calculations in Smart View C-19
Performing Ad Hoc Analysis in Smart View C-20
Navigating Ad Hoc Grids C-21
Zooming In and Out on Dimension Members C-23
Pivoting Dimensions C-24
Keeping and Removing Dimension Members C-25
Saving Ad Hoc Grids C-26
Cascading Data Slices C-27
Adding Supporting Details C-28
Managing Approvals in Smart View C-30
Copying Versions in Smart View C-32
Managing Task Lists in Smart View C-34
Summary C-36

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

I t d ti t Pl i Introduction to Planning

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Course Objectives
After completing the course, you should be able to:
Create and deploy Planning applications
Manage metadata and data
Set up security for users groups and members Set up security for users, groups, and members
Create and customize forms, menus, and task lists
Migrate application artifacts
Verify application setup
Set up and test business rules p
Set up and manage the approval process
Oracle Hyperion Planning 11.1.2: Create & Manage Applications 1 - 2

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Course Agenda: Day 1
Lesson 1: Introduction to Planning
Lesson 2: Navigating EPM Workspace
Lesson 3: Introduction to Applications and Dimensions
Lesson 4: Creating Applications in Planning Administration Lesson 4: Creating Applications in Planning Administration
Lesson 5: Managing Dimensions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Lesson 6: Setting Up the Alias, Currency, Year, and Period
Dimensions
Lesson 7: Setting Up Scenarios and Versions
Lesson 8: Loading Metadata Lesson 8: Loading Metadata
Lesson 9: Setting Up the Entity and Account Dimensions
Lesson 10: Creating User-Defined Elements

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Lesson 11: Setting Up Exchange Rates
Lesson 12: Loading and Calculating Data
Lesson 13: Setting Up Planning Security
Lesson 14: Creating Forms Lesson 14: Creating Forms

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Lesson 15: Enhancing Forms
Lesson 16: Entering Data in Planning
Lesson 17: Annotating and Analyzing Data
Lesson 18: Managing Business Rules Lesson 18: Managing Business Rules

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Lesson 19: Setting Up the Approval Process
Lesson 20: Managing the Approval Process
Lesson 21: Creating Task Lists
Case Study Case Study
Appendix A: Creating Applications in Performance
Management Architect
Appendix B: Sharing Data with Data Synchronization
Appendix C: Entering Data with Smart View

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
After completing this lesson, you should be able to:
Describe Planning and its components
Identify the product components within the Planning
architecture architecture
Explain the Planning business process
Discuss a typical Planning business scenario

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Oracle Hyperion Planning
Streamlines data entry through web and Excel interfaces
Provides a calculation engine to promote business
modeling with complex business rules and allocations
Enables annotations at multiple levels to capture budget Enables annotations at multiple levels to capture budget
details
Accommodates potentially sophisticated budget review
processes
Facilitates dynamic reporting by using Financial Reporting
Oracle Hyperion Planning (Planning) is a budgeting and planning solution that provides
streamlined methods for entering data through web and Excel interfaces. Planning supports
driver-based plans that are based on global assumptions, such as interest rates and headcount,
and promotes modeling with complex business rules and allocations. It enables users to annotate
and justify data at multiple levels to capture budget details. It enables decision makers and
managers to collaborate with budget holders during potentially complex budget review processes,
and provides the tools to create and publish dynamic financial reports by using Oracle Hyperion
Financial Reporting (Financial Reporting).

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Components
Planning
Non-numeric
data
Application server
Planning
relational
database
Planning user
Essbase
databases
Numeric
data
The application server provides the environment for running Planning applications. Oracle
WebLogic Server is the application server provided with Planning. It facilitates user access to non-
numeric data in the Planning relational database and to numeric data in Oracle Essbase
databases.
Planning requires a system database and a database for each deployed application. The Planning
application database is used primarily to store the applications definition. Planning data and
metadata storage is covered in Lesson 3, Introduction to Applications and Dimensions.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Additional Planning Modules
Financial Reporting: Create highly formatted reports and
detailed budget books for offline approval and statutory
reporting purposes.
Smart View: Complete Planning tasks within a familiar p g
Excel interface and integrate Planning data with Outlook.
The following modules extend the Planning solution to address specific organizational needs:
Financial Reporting: Create highly formatted reports and detailed budget books for offline
approval and statutory reporting purposes.
pp y p g p p
Smart View: Complete Planning tasks within a familiar Excel interface and integrate
Planning data with Outlook.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Additional Planning-Based Products
Workforce Planning: Manage workforce, salary, and
compensation planning.
Capital Asset Planning: Plan for new asset purchases
and existing asset actions. g
Public Sector Planning and Budgeting: Develop
budgets for public sector and higher-education
organizations.
Project Financial Planning: Plan and allocate workforce
and asset resources to organization projects while and asset resources to organization projects, while
monitoring financial performance.
The following products extend the Planning solution to address specific organizational needs:
Oracle Hyperion Workforce Planning, Fusion Edition: Manage workforce, salary, and
compensation planning.
p p g
Oracle Hyperion Capital Asset Planning, Fusion Edition: Plan for new asset purchases
and existing asset actions.
Oracle Hyperion Public Sector Budgeting and Planning, Fusion Edition: Develop
comprehensive budgets for public sector and higher-education operations.
Oracle Project Financial Planning: Plan and allocate workforce and asset resources to
organization projects, while monitoring financial performance.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Product Integration
EPM System: Profitability and Cost Management, Oracle
Scorecard and Strategy Management, Strategic Finance,
Financial Management, and Financial Data Quality
Management
ERP systems: Oracle E-Business Suite, Oracle
PeopleSoft Enterprise, and Oracle Fusion Applications
Oracle Business Intelligence Suite, Enterprise Edition
Data management applications: Oracle Data Integrator
and ERP Integrator and ERP Integrator
Planning can be integrated with the following products:
Oracles Enterprise Performance Management System (EPM System) product suite,
including Oracle Hyperion Profitability and Cost Management, Fusion Edition, Oracle
g yp y g , ,
Scorecard and Strategy Management, Oracle Hyperion Strategic Finance, Fusion Edition,
Oracle Hyperion Financial Management, Fusion Edition, and Oracle Hyperion Financial Data
Quality Management, Fusion Edition (FDM)
Enterprise resource planning (ERP) systems, including Oracle E-Business Suite, Oracle
PeopleSoft Enterprise, and Oracle Fusion Applications
Oracle Business Intelligence Suite, Enterprise Edition
Data management applications including Oracle Data Integrator and Oracle Hyperion Data management applications, including Oracle Data Integrator and Oracle Hyperion
Financial Data Quality Management ERP Integration Adapter for Oracle Applications, Fusion
Edition (ERP Integrator; FDM module)

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Architecture
Middle Tier
Microsoft Office
Integration
Smart View
EPM Workspace:
Planning, EPMA,
Reporting and
Analysis
Administration
Services Console,
Essbase Studio
Client Tier
Web Analysis
Studio and
Reporting Studio
Clients
Web Server Application Server Services
Data Tier
Middle Tier
External
Services
ERP Systems
Oracle Data Integrator/
ERP Integrator
Relational Databases Essbase Databases
Planning is a multitier application that combines the advantages of Essbase (a multidimensional
database) and a relational database to optimize performance and maintenance.
The slide illustrates the client, middle, and data tiers as well as external services that integrate
, , g
with Planning.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Client Tier
EPM Workspace for accessing the Planning web interface,
Planning application administration, and Performance
Management Architect applications, and creating and
publishing reports
Smart View for entering Planning data in Excel
Administration Services Console and Essbase Studio for
modifying multidimensional outlines and calculation scripts
Reporting Studio for developing and running financial
reports reports
Microsoft Office
Integration
Smart View
EPM Workspace:
Planning,
Performance
Management
Architect, Reporting
and Analysis
Administration
Services Console,
Essbase Studio
Client Tier
Web Analysis
Studio and
Reporting Studio
Clients
The client tier contains Oracle Enterprise Performance Management Workspace (EPM
Workspace), Oracle Hyperion Smart View for Office (Smart View), Oracle Essbase Administration
Services Console (Administration Services Console), Oracle Essbase Studio (Essbase Studio),
Hyperion Web Analysis Studio, and Oracle Hyperion Financial Reporting Studio (Reporting
Studio).
You access and manage Planning applications, Oracle Hyperion Enterprise Performance
Management Architect (Performance Management Architect) applications, and reports in EPM
Workspace.
On the client tier, Planning administrators and users enter data, perform approvals tasks, manage
users and security launch business rules copy versions develop forms work with Financial users and security, launch business rules, copy versions, develop forms, work with Financial
Reporting, and perform other administrative tasks, such as updating Essbase outlines.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Middle Tier
Application server for running applications
Supported web servers for handling HTTP requests from
Planning
Services for Performance Management Architect Essbase Services for Performance Management Architect, Essbase
Studio, and Financial Reporting
Middle Tier
Web Server Application Server Services
The middle tier consists of Oracle WebLogic Server (the application server) for running Planning
applications, supported web servers for handling Hypertext Transfer Protocol (HTTP) requests
from Planning, and the required services for Performance Management Architect, Essbase Studio,
and Financial Reporting.
The web server can be on a separate machine or on the same machine as the Planning
application server. The web server enables you to access Planning applications from a web client
through a browser. The web server uses HTTP as the communications protocol.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Data Tier
Relational databases store data for Shared Services,
Performance Management Architect, Calculation Manager,
Reporting and Analysis, Administration Services, and
Planning.
Essbase databases store security, Planning data and
metadata, and calculation scripts.
Data Tier
Relational Databases Essbase Databases
The data tier consists of the relational (non-numeric) and Essbase (numeric) databases.
The following components require a relational database:
Oracle Hyperion Shared Services
Oracle Hyperion Shared Services
Oracle Hyperion Performance Management Architect
Oracle Hyperion Calculation Manager
Oracle Hyperion Reporting and Analysis
Oracle Essbase Administration Services
Oracle Hyperion Planning

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

External Services
Integration with Oracle and other systems
Oracle Data Integrator and ERP Integrator for data and
metadata integration
ERP systems integration for drill-back capabilities ERP systems integration for drill back capabilities
ERP Systems
External
Services
Oracle Data Integrator/
ERP Integrator
To load metadata and data from Oracle and other systems into Planning applications, you can
work with several external services, including Oracle Data Integrator, ERP Integrator, and Outline
Load Utility.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Oracle Exalytics: Overview
Oracle Exalytics consists of hardware and software engineered
to work together.
The Oracle Exalytics In-Memory Machine is the industrys first engineered in-memory analytics
machine that delivers no-limit, extreme performance for Business Intelligence and Enterprise
Performance Management applications.
The Oracle Exalytics In-Memory Machine hardware is a single server that is optimally configured
for in-memory analytics for business intelligence workloads and includes powerful compute
capacity, abundant memory, and fast networking options.
The Oracle Exalytics In-Memory Machine features an optimized Oracle BI Foundation Suite
(Oracle BI Foundation) and Oracle TimesTen In-Memory Database for Exalytics. Business
Intelligence Foundation takes advantage of large memory, processors, concurrency, storage,
networking operating system kernel and system configuration of the Oracle Exalytics hardware networking, operating system, kernel, and system configuration of the Oracle Exalytics hardware.
This optimization results in better query responsiveness, higher user scalability and markedly
lower total cost of ownership (TCO) compared to stand-alone software. The TimesTen In-Memory
Database for Exalytics is an optimized in-memory analytic database, with features exclusively
available on Oracle Exalytics platform.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning on Oracle Exalytics: Benefits
Reduced planning, budgeting, and forecasting cycle times
More complex planning models with finer grained detail
More users in the planning process and improved
accuracy of plans and forecasts accuracy of plans and forecasts
Optimized resource allocations and improved performance
Focused finance resources on value added analysis
Deployed quickly with prebuilt functionality
Planning running on Oracle Exalytics takes advantage of the following capabilities:
Enterprise-wide planning, budgeting, and forecasting involving hundreds to thousands of
users across an organization with speed-of-thought performance for complex calculations,
g p g p p ,
standard and ad hoc reporting and analysis
Detailed planning, budgeting, and forecasting across thousands of cost centers, millions of
customers or products, and multiple scenarios
Fast time to benefit and reduced TCO by supporting enterprise-scale planning and budgeting
and forecasting with a reduced number of server platforms

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning on Oracle Exalytics: Optimized Engine
Faster parallel load
Faster parallel export
Faster calculations
Faster cube restructuring Faster cube restructuring
Faster MDX queries
More concurrent users
Planning on Oracle Exalytics benefits from a number of optimizations for in-memory operations
including improvements to overall storage layer performance, enhancements to parallel
operations, enhanced MDX syntax and a high performance MDX query engine. Essbase on
Exalytics provides up to 16X faster query execution as well as up to 6X reduction in write-back
and calculation operations, including batch processes.
Essbase on Oracle Exalytics accomplishes the tasks in the slide as follows:
Indexes and data blocks are stored in memory.
There is better cache coherency.
Index navigation is improved.
Locking is improved.
There is better workload partitioning and distribution across threads.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Business Process
1 2 3
Enter data Adjust data Calculate data
Annotate data
Review and
approve data
Run and publish
financial reports
4 5 6
The Planning business process includes the following steps:
1. Enter data.
2 Adjust data
2. Adjust data.
3. Calculate data.
4. Annotate data.
5. Review and approve data.
6. Run and publish financial reports.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 1: Entering Data
Enter data by:
Adding it manually through forms or Smart View grids
Loading it through Essbase, Outline Load Utility, FDM, or
ERP Integrator ERP Integrator
Enter data
1
You enter data directly into Planning through forms or Smart View grids or you can load data
through Essbase, Outline Load Utility, FDM, or ERP Integrator.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 2: Adjusting Data
Adjust data:
Manually in Planning forms
By simultaneously spreading data values and percentages
across multiple dimensions across multiple dimensions
2
Adjust data
You adjust Planning data in forms manually or through the provided adjustment tools, Mass
Allocate and Grid Spread, which enable users to simultaneously spread data values across
multiple dimensions.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 3: Calculating Data
Calculate data by:
Applying provided business rules
Creating new business rules
Calculate data
3
You calculate Planning data through the provided business rules or through custom business rules
in Calculation Manager.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 4: Annotating Data
Annotate data by adding commentary at the following levels:
Account
Cell
Planning unit Planning unit
Supporting details
Annotate data
4
Planning annotations enable Planning users to justify and document details for data values. Users
enter annotations at the following levels in Planning: account, cell, planning unit, and supporting
details.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 5: Reviewing and Approving Data
Review and approve data by:
Setting up the approval process (Approvals)
Approving or rejecting budgets for your organizational
structure structure
Building validation rules in forms to identify exceptions
before the approval process begins
Review and
approve data
5
You review and approve data in Planning by setting up the approval process based on your
organizational structure. You can include validation rules in forms to identify exceptions before the
approval process begins.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 6: Running and Publishing
Financial Reports Financial Reports
Run and publish reports by:
Creating and running dynamic or static reports in Financial
Reporting
Producing reports in HTML and PDF Producing reports in HTML and PDF
Run and publish
financial reports
6
After entering, calculating, adjusting, and reviewing Planning data, you use Financial Reporting to
depict the results in static or dynamic reports in HTML or PDF.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Business Scenario
Create application shell based
on a design framework
Manage and load dimensions Create user-defined elements Set up exchange rates
1 2 3 4
Load and calculate data Set up Planning security Create and enhance forms
5 6 7
Enter, annotate, and
analyze data
Manage business rules Set up and manage
approval process
Create and manage
task lists
8 9 10 11
ABC Corporation manages its planning and budgeting processes with highly manual efforts and
minimal systems integration. These time-consuming processes do not meet the current
expectations and requirements of the management team. The company recently purchased
Oracle Enterprise Performance Management System and is in the process of implementing the
Oracle Hyperion Planning Suite and supporting tools. Oracle Hyperion Planning will enable the
company to validate forecasts, reduce budgeting and implementation time, and combine financial
and operational planning in one system.
As the application administrator, you are tasked with rolling out the Finbud Planning application to
the organizations 350 users. Together with an implementation consultant and an internal
implementation team, you identify the necessary requirements for the application and begin the
application creation process.
Mickey Smith, application administrator, is tasked with building the application based on the
requirements specified by the implementation team. As Mickey builds the application, he is
required to test and make sure each functionality is working.
Randy Jackson and Thomas Redford, budget administrators, are responsible for reviewing
and approving the budget.
Christian Carlucci Mary Woo and Kate Reilly planners are responsible for entering budget Christian Carlucci, Mary Woo, and Kate Reilly, planners, are responsible for entering budget
data and creating financial reports.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Budget Requirements for the Finbud Application
ABC Corporations budget requirements include the creation of the following plans:
Actual, Fiscal Year 2012 to 2013
Budget Fiscal Year 2013 to 2014 Budget, Fiscal Year 2013 to 2014
Forecast, Fiscal Year 2013 to 2014
The calendar and fiscal years start in the month of January. Data will be loaded from external
systems. The load files have been formatted by your implementation consultant.
Implementation Process
The classroom practices include tasks you need to perform to complete the development and
implementation of the organizations Finbud application.
Create the application shell based on the budget requirements.
Load and manage application metadata, including dimensions, alias tables, member
formulas, user-defined dimensions, attribute dimensions, user-defined attributes, and smart
lists.
Refresh the Essbase database Refresh the Essbase database.
Set up exchange rates.
Load and calculate application data.
Import user and group security.
Create and import forms, associated business rules, menus, formulas and rows, and
validation rules.
Assign dimension and object security Assign dimension and object security.
Set application, system, and user preferences.
Test data entry and ad hoc analysis features.
Set up and test the approval process.
Create and test task lists.
In addition to Finbud, the implementation team opted to create a smaller application, BudPlan,
using Planning application administration The BudPlan application will use the same criteria as using Planning application administration. The BudPlan application will use the same criteria as
Finbud, except for the following:
The application will use single currency.
The business entities will cover only North America.
Then, you will load forms and user-defined elements into BudPlan.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 1: Creating the Application Shell
Based On a Design Framework Based On a Design Framework
Create the application based on the following criteria:
Application name
Number and names of plan types
Calendar structure Calendar structure
Whether the application is a multicurrency application
Default currency
Create application shell based
on a design framework
1
After discussing Lessons 1 through 3, you begin the implementation process in Lesson 4,
Creating Applications in Planning Administration.
Consulting partners (such as implementation consultants) and the Planning administrator design
g p ( p ) g g
applications and create an application framework. In Lesson 4, you begin the administration
process by creating the application shell, setting the application framework based on your
organizations requirements.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 2: Managing and Loading Metadata
Set up and load the following metadata:
Alias tables
Currency dimension
Year dimension Year dimension
Period dimension
Scenario dimension
Version dimension
Entity dimension y
Account dimension
Manage and load dimensions
2
After the application shell is created and deployed, you set up and load metadata to your
application in Lessons 5 through 9.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 3: Creating User-Defined Elements
Create the following user-defined elements:
Member formulas
User-defined dimensions
Attributes Attributes
User-defined attributes
Smart lists
Create user-defined elements
3
After defining your base metadata, you create user-defined elements to your application in
Lesson 10, Creating User-Defined Elements.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 4: Setting Up Exchange Rates
Set up the following:
Exchange rates
Currency conversion calculation scripts
Set up exchange rates
4
In Lesson 11, Setting Up Exchange Rates, you set up exchange rates and generate currency
conversion calculation scripts.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 5: Loading and Calculating Data
Load and calculate data by using one of the following tools:
Essbase Administration Services Console
Outline Load Utility
Financial Data Quality Management and ERP Integrator Financial Data Quality Management and ERP Integrator
Oracle Data Integrator
Load and calculate data
5
In Lesson 12, Loading and Calculating Data, you learn about the tools used to load and calculate
Planning data.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 6: Setting Up Planning Security
Set up security based on the following levels:
Planning Roles in Shared Services
Data Security
Access Permissions Access Permissions
Security Filters
Set up Planning security
6
You set up role-based, data, and object-based security in Lesson 13, Planning Security.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 7: Creating and Enhancing Forms
Planning forms:
Simple forms
Composite forms
Create and enhance forms
7
In Lessons 14 and 15, you create and enhance simple forms and composite forms. You also learn
how to export and import forms into your application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 8: Entering, Annotating, and Analyzing Data
Perform the following data entry tasks:
Navigate and submit data in forms.
Enter data with smart lists.
Filter sort and spread data Filter, sort, and spread data.
Adjust plan data.
Add comments, supporting detail, documents, and account
annotations to form cells.
Clear cell details.
Perform ad hoc analysis in forms.
Enter, annotate, and
analyze data
8
In Lessons 16 and 17, you learn how to navigate in Planning forms, enabling you to enter, adjust,
analyze, and submit data. You also learn how to add annotations such as comments, supporting
detail, document attachments, and account annotations.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 9: Managing Business Rules
Create and manage business rules in Calculation Manager:
Adding rule components
Implementing system templates
Grouping rules into rulesets Grouping rules into rulesets
Validating and deploying rules and rulesets
Launching rules and rulesets
Manage business rules
9
You create and manage business rules in Lesson 18, Managing Business Rules.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 10: Setting Up and Managing
the Approval Process the Approval Process
Manage the approval process:
Set up Planning Unit Hierarchies
Build and implement validation rules
Start and manage the review cycle Start and manage the review cycle
Set up and manage
approval process
10
You set up the planning unit hierarchy used in the approval process and mange the review cycle
in lessons 19 and 20.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Step 11: Creating and Managing Task Lists
Guide users through the planning process:
Create and manage task lists
Assign access to task lists
Print task list reports Print task list reports
Create and manage
task lists
11
You create and manage task lists in Lesson 21, Creating Task Lists.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Training Environment
Web application
and web servers
Third-party software Data sources
Planning product
components
The training environment is a single-server configuration that combines all tiers on one machine.
Oracle recommends this configuration for a development environment or for customers who roll
out Planning to a very limited number of users.
For a list of products and modules that are included in the training environment, see Planning
Architecture in this lesson.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select three Planning components.
a. Dimension Services
b. Application Server
c Essbase databases c. Essbase databases
d. Relational databases
Answer: b, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You can load Planning data through Essbase, FDM, or ERP
Integrator.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You can only use the provided business rules to calculate data
in Planning.
a. True
b False b. False
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Public Sector Planning and Budgeting is an included module
with Planning.
a. True
b False b. False
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
In this lesson, you should have learned to:
Describe Planning and its components
Identify the product components within the Planning
architecture architecture
Explain the Planning business process
Discuss a typical Planning business scenario

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Practice 1-1 Through 1-4
The practice covers the following topics:
Starting EPM Services
Identifying Your Server Name
Preparing the Browser Preparing the Browser
Reviewing the Business Scenario, Users, and Roles

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

N i ti EPM W k Navigating EPM Workspace

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Describe the benefits of EPM Workspace
Launch EPM Workspace
Explain the user interface components Explain the user interface components
Set general preferences
Open applications
Navigate Planning

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

EPM Workspace: Overview
Planning
Performance
Management Architect EPM Workspace
Manage enterprise financial information Manage enterprise financial information
Oracle Hyperion applications Planning output
EPM Workspace provides a centralized interface for viewing and interacting with content that
was created with EPM System financial applications, such as Planning, Public Sector
Planning and Budgeting, Profitability and Cost Management, Financial Management, and
Financial Reporting.
Benefits of EPM Workspace
Single sign-on (users log on to EPM Workspace to access both Reporting and Analysis
content and Planning)
Single console for application management and creation (administrators create,
manage, and deploy applications from a single location. You open these applications in
f ) Planning for data retrieval and data output.)
Centralized repository of key dimensional elements for Oracle Hyperion products
Centralized console for controlling data flow between applications
Audit logging and process controls

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Tasks that you can perform in EPM Workspace
Build, migrate, and manage applications.
Manage data sources metadata and data.
Create rules with Calculation Manager Create rules with Calculation Manager.
Conduct high-performance, multidimensional modeling, analysis, and reporting with
Essbase.
Generate and manage book contents, and organize the table of contents with Financial
Reporting.
Report on data stored in ASO and BSO databases with Financial Reporting.
Use Interactive Reporting to generate ad hoc relational queries self service reports and Use Interactive Reporting to generate ad hoc relational queries, self-service reports, and
dashboards against open database connectivity (ODBC) data sources.
Use Web Analysis to perform interactive ad hoc analysis, presentations, and
multidimensional data reporting.
Generate enterprise metrics for management metrics and analysis, and present
information in interactive dynamic dashboards.
Access and interact with other published content, such as, Microsoft Word or Excel Access and interact with other published content, such as, Microsoft Word or Excel
documents.
Integrate metadata and data from an ERP source system into an EPM target
application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Launching EPM Workspace
To launch EPM Workspace:
1. In your web browser, enter http://<web server>:<port>/workspace/, where web server
is the web server machine host name and port is the web server port number (for
s t e eb se e ac e ost a e a d po t s t e eb se e po t u be ( o
example, http://myserver:9000/workspace/), and press Enter.
The EPM Workspace Log On page is displayed.
2. Enter your username and case-sensitive password, and click Log On.
The EPM Workspace user interface is displayed. :

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

EPM Workspace User Interface
Search field
Standard toolbar
Menu bar
Document
tab bar
Adjuster
Content area View pane
The EPM Workspace user interface includes the components listed in the following table:
Element Description
Adjuster Adjusts the size of the view pane and content area
Content area Displays active module items, tasks, or files
Document tab bar Displays information that is specific to the current module
Menu bar Provides commands that organize tasks and modules
Search field Enables searches for items in the repository Search field Enables searches for items in the repository
Standard toolbar Provides shortcuts for performing tasks
View pane Provides buttons that enable navigation between panels

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting General Preferences
You can set defaults for the general appearance of your EPM Workspace user interface, such
as the page to be displayed in the content area when you log on. The Content option
determines what other options are available. In the example in the slide, you open the Hyplan
application when you log on to EPM Workspace.
You can set up prompts to save unsaved files and you can show the document path. You
cannot update the email address because it is registered in the users security settings.
The Accessibility Mode section provides support for screen readers and magnifiers to access
and work with EPM Workspace.
Preference changes become effective the next time that you log on.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To set general preferences:
1. Select File, and then Preferences.
The General preferences dialog box is displayed.
2 In the Content drop down list select the page that you want to be displayed when you 2. In the Content drop-down list, select the page that you want to be displayed when you
log on:
- Select None to display a blank page.
- Select Application to open the selected application.
- Select Home Page to display the default home page.
- Select Explore to display the selected folder on the Explore page.
S l t D t t di l th l t d d t - Select Document to display the selected document.
- Select Favorite to display a selected favorites page or the My Personal Page.
3. Select Prompt to Save Unsaved Files to have EPM Workspace prompt you to save
unsaved files.
4. Select Show Path For Documents to display document file paths in the progress bar.
5. In the Accessibility Mode section, in the select Theme drop-down list, select Normal or
Hi h C t t t if th l d High Contrast to specify the color mode.
6. Click OK.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

EPM Workspace Navigate Menu
You use the Navigate menu to access the modules that are available within EPM Workspace.
The available modules depend on the access that is granted to users and the products that
are installed and configured. The example in the slide illustrates Administer menu options.
Use the Applications menu to access your Planning applications. Applications are
displayed only when a user has access permission to the applications.
Use Explore to view, manage, and secure repository items, such as Financial Reporting
reports and budget books.
Use the Administer menu to access administrator-related tasks, such as managing
users and groups, creating and managing applications, and setting up ERP integrations.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The following table describes some of the administration tasks:
Task Description
Shared Services Provision users and groups Shared Services
Console
Provision users and groups.
Configure user directories and single sign-on.
Create access assignment reports.
Access Lifecycle Management.
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.
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 Performance Management Architect applications in
one centralized location.
View data flows between applications.
Migrate applications to different servers.
Deploy applications for Planning, Financial Management,
P fit bilit d C t M t E b t Profitability and Cost Management, Essbase aggregate
storage (ASO), and Essbase block storage (BSO).
Data Synchronization Create data synchronizations between Oracle Hyperion
applications (for example, an administrator synchronizes data
between two Planning applications, between two Financial
Management applications, and between one Planning
application and one Financial Management application) application and one Financial Management application).
Create data mappings that can be reused.
Create flat file and interface table mappings to import data into
Hyperion applications.
Calculation Manager Create, validate, and deploy business rules and business
rulesets.
Transform Classic to
EPM Architect
Transform Planning applications to Performance Management
Architect applications.
Library Job Console View a summary of Dimension Library and application activities,
including imports, deployments, and data synchronizations.
Configure Interface
Data Source
Configure data sources for interface tables.
Planning
Administration
Create, delete, and register applications.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Opening Applications
After an application is created, you can open it by using the Navigate menu. The example in
the slide shows two Planning applications created in the system: Finbud and Hyplan.
To open applications:
To open applications:
1. Select Navigate, then Applications, and then Planning.
2. Select an application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Navigating in Planning
Planning
Open
application
Planning
menus Planning
toolbar
Form
folders
Content area View pane
Forms
Opened applications are displayed in the content area. Planning provides the following tools
for selecting tasks and documents:
Planning menus
a g e us
Planning toolbar
View pane and content area
Planning Menus
Your user profile determines your access to menu commands. For example, if you are
assigned the Administrator role, you have access to all functions in the Administration menu.
If you are assigned the Interactive User role you have limited access to the Administration If you are assigned the Interactive User role, you have limited access to the Administration
menu.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The following table describes the Planning menus:
Menu Description
Navigate Provides access to the modules that are available within EPM Navigate Provides access to the modules that are available within EPM
Workspace.
File Contains commands related to handling documents and pages, setting
preferences, and exiting EPM Workspace.
Edit Provides commands related to handling information, such as adjusting
data, adding comments and documents, adding planning unit
annotations and adding supporting detail annotations, and adding supporting detail.
View Provides commands related to viewing information, such as refreshing
the current view, and viewing task list information.
Favorites Provides commands for managing favorites and personal pages.
Tools Provides commands for additional tools, such as launching business
rules navigating to Job Console performing ad hoc actions and rules, navigating to Job Console, performing ad hoc actions, and
performing actions on Planning data, such as copying versions,
managing approvals, and running reports to review planning unit
annotations, and audit user actions.
Administration Provides access to administration tasks, such as managing application
objects, managing dimensions, setting up business rule security, setting
up approvals, managing data sources, and mapping reporting
Planning Toolbar
The following table describes the buttons on the toolbar:
applications.
Help Provides help for the currently selected task or document.
Button Button Name Description
Save Save data input on forms.
Refresh Refresh the form with data stored in the
database.
Print Print the current screen Print Print the current screen.
Adjust Data Increase or decrease values by a
percentage or by a value.
Grid Spread Spread data across dimensions on the form.
Mass Allocate Run a Mass Allocate calculation on the
form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Comment Add comments to a specific cell at any
level in forms.
Lock/Unlock Lock or unlock cells when spreading data
on forms.
Supporting Detail Add detail that aggregates the cell value
in forms.
Add/Edit Document Add or edit documents to provide
documentation for data in cells.
Instructions View form instructions.
Open in Smart View Open forms in Smart View.
Form Designer Open form for editing.
New Ad Hoc Grid Create ad hoc grids.
Analyze Start ad hoc analysis.
Save Ad Hoc Grid Save ad hoc grids Save Ad Hoc Grid Save ad hoc grids.
Ad Hoc Options Set display options and operational
behavior for ad hoc grids.
Zoom in Next Level, Zoom Zoom in on dimensions in ad hoc grids. Zoom in Next Level, Zoom
in All Levels, Zoom In
Bottom Level
Zoom in on dimensions in ad hoc grids.
Zoom Out Zoom out on dimensions in ad hoc grids.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Remove Only, Keep Only Remove only and keep only
View Pane and Content Area
Remove Only, Keep Only Remove only and keep only
dimension members in ad
hoc grids.
After you open a Planning application, the view pane and content area display your
selections.
For example, when you work with form and ad hoc grid management, the view pane lists form
folders, forms, and business rules. You can use the view pane to toggle from one folder or
form to another. After selecting a specific form, you see the contents of that form in the
content area.
If you select Business Rules from the Tools menu you see the Business Rules dialog box in If you select Business Rules from the Tools menu, you see the Business Rules dialog box in
the content area where you can launch business rules. However, the view pane lists form
folders and forms. After launching business rules, you can use the view pane to open a form.
Forms are contained within the folders. When you select a folder, a list of forms to which you
have access is displayed in the view pane and in the content area. When you select a form, it
is displayed in the content area.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that you can perform in EPM Workspace.
a. Create rules with Calculation Manager.
b. Design reports.
c Manage data sources metadata and data c. Manage data sources, metadata, and data.
d. Set preferences.
Answer: a, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the module that enables you to provision users and
groups.
a. Application Library
b Planning Administration b. Planning Administration
c. Calculation Manager
d. Shared Services Console
Answer: d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Users have access only to the menu commands to which they
are assigned access.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe the benefits of EPM Workspace
Launch EPM Workspace
Explain the user interface components Explain the user interface components
Set general preferences
Open applications
Navigate Planning

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Logging On to EPM Workspace
Opening Planning Applications
Accessing Planning Application Administration Accessing Planning Application Administration

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

I t d ti t A li ti d Di i Introduction to Applications and Dimensions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Describe applications and application framework
Identify required and user-defined dimensions in Planning
Describe the data block creation process Describe the data block creation process
Explain aggregation, data storage, and calculation options

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Application: Overview
Hyplan
Metadata
Security
Plan
types
Calendar
S y
Forms
Data
Business
rules
Currency
You develop your operational plan with Planning. You set up Planning applications to include the
appropriate structure for your business process. Each application has a specific framework with
the following structure:
Application name: Specify the name of the application.
Number and names of plan types: Select and name plan types to hold combinations of
metadata, forms, and business rules.
Calendar structure: Specify your organizations calendar, such as the first month and first
year for your fiscal year.
Currency: Identify whether multiple currencies are needed and define the default currency.
After the application framework is created, dimensions and members (metadata) are added to the
application and assigned to plan types. Security is assigned so that users and groups can access
the application. Access can be further defined to secure metadata, forms, task lists, and business
rules.
Before planners start to develop the budget, you load data into your application. For example,
actual plan data can be loaded so that budgets and forecasts can be based on that data. Forms
are created so that planners can both view data and enter data. p
To complete your Planning model, you include business rules to calculate key metrics within your
application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Application Creation Process
1
2 3
Load metadata
Create application
framework
Modify metadata
Assign security
Load data
4 5 6
Set up relational
metadata
Create and deploy
business rules
7
You set up Planning applications by completing the following tasks:
1. Create application framework.
2 Load metadata
2. Load metadata.
3. Modify metadata.
4. Set up relational metadata including planning unit hierarchy, report mappings, forms, and
task lists.
5. Assign security.
6. Load data.
7 Create and deploy business rules 7. Create and deploy business rules.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Data and Metadata Storage: Overview
Planning
Non-numeric
data
Application server
Planning
relational
database
Planning user
Essbase
databases
Numeric
data
Users access non-numeric data in the Planning relational database and numeric data in the
Essbase databases. Oracle WebLogic Server is the application server provided with Planning. It
facilitates user access to non-numeric data in the Planning relational database and to numeric
data in Essbase databases.
You must associate each Planning application with a system database and a relational database
schema:
To store an entry for each Planning application, you create a Planning system database. You
can have one system database for all Planning applications. For example, you can have
your Taxplan, Hyplan, and Finbud Planning applications in a single system database.
To maintain relational application data you set up a relational database You must have a To maintain relational application data, you set up a relational database. You must have a
relational database schema for each application.
Though data values are stored in Essbase databases, some information is stored only in the
Planning relational database schema. For example, planning unit annotations, account
annotations, comments, and supporting details are stored in the Planning relational database
schema. The procedure for creating relational databases is determined by the relational store that
your company uses (Oracle, Microsoft SQL Server, or IBM DB2).

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The following table shows where information is stored in the databases:
Information Planning
Relational Database
Essbase Databases
Security x x
Metadata x x
Foreign exchange rates x x
Smart lists x x (numeric values) Smart lists x x (numeric values)
Approvals hierarchies x
Approvals details x
Annotations, comments in cells, and
supporting details
x
Task lists x
Preferences x
Application setup x
Forms and validation rules x
User variables x
Decision package types x
Decision packages x
Budget requests x Budget requests x
Numeric data x
Non-numeric data x
Currency calculation scripts x
Substitution variables x

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

You configure data sources to establish the connection between the relational data source, the
relational database, and the Essbase database. You can configure data sources in Planning
Application Administration.
To configure data sources in Planning Application Administration:
1. Select Navigate, then Administer, and then Planning Administration.
The Manage Applications page is displayed.
2. In the left pane, click Manage Data Source.
The Manage Data Source page is displayed.
3. Click Action, and select Create.
The Create Data Source page is displayed. The Create Data Source page is displayed.
4. In the Data Source Name box, enter the data source name.
5. Optional: In the Data Source Description box, enter a description of the data source.
6. In the Database drop-down list, select the relational database platform.
7. Under Application Database, perform the following actions:
- Enter the relational database details: server, port, database, user, and password.
- Click Validate - Click Validate.
A message indicates a successful or failed connection to the relational database. You must
have a successful connection to create the data source.
8. Under Essbase Server, enter the Essbase server name, username, and password.
9. Optional: Select Unicode to indicate that the data source is unicode.
10. Under Essbase Server, click Validate.
A message indicates a successful or failed connection to the Essbase database You must A message indicates a successful or failed connection to the Essbase database. You must
11. Click Finish.
A message indicates that the data source was created successfully.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Application Framework
The application framework includes key components that describe how the application is set up. It
includes the application name and description, the data source you use to store relational data,
and other components that depict the applications structure, such as the base time periods,
definition of the first period in the fiscal year, the first fiscal year for the application, and total
number of years for the application. You also include in the framework the weekly distribution for
time periods, multicurrency, plan type, and calculation module selections. The Shared Services
Project in which the application is listed is also included in the application framework.
Note: Shared Services Projects are also referred to as Application Groups.
You set up your application to reflect your business model by selecting time period and currency
criteria as well as defining the number and names for the plan types included in the application criteria as well as defining the number and names for the plan types included in the application.
Before creating an application, determine the following application criteria:
Time periods (base time periods, fiscal start year and month, weekly distribution)
Currency specifications (default currency, multiple currencies)
Number of plan types and their names

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Calendar Structure
Base time period (months)
First fiscal year and fiscal year first month
Weekly distribution pattern (even, 4-4-5, 4-5-4, 5-4-4)
The calendar establishes the applications base time periods, first fiscal year and month, and total
number of years. You also define a monthly distribution pattern based on the number of fiscal
weeks in a month. You can enable the All Years parent member to view accumulated data across
multiple years.
Base Time Periods
The base time period options are the bottom-level time periods in the application. You can select
months, or quarters. You can create a custom base time period, such as weeks or days. Be aware
that you cannot change the selected base time periods after you create the application.
First Fiscal Year and Fiscal Year First Month
To determine the first fiscal year, consider your plans for loading either the current years budget
or actuals for comparison with the plan. Be aware that you cannot change it later. You must also
specify the fiscal year first month and number of years.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

For the fiscal year, you can set the fiscal year first month and specify whether the fiscal year starts
from the same calendar year or the previous calendar year. The following table provides examples
of how the Fiscal Year First Month and the Fiscal Start Year options affect the calendar for the
application, assuming the Fiscal Start Year is 2013:
Fiscal Year First
Month
Fiscal Start Year Year Period Year Dimension
January Same Calendar Year Jan 13 to Dec 13 FY13
July Same Calendar Year Jul 13 to Jun 14 FY13
July Previous Calendar Year Jul 12 to Jun 13 FY13
Weekly Distribution Pattern
The weekly distribution pattern is based on the number of fiscal weeks in a month. You set a
weekly distribution pattern for your application so that you can determine how to distribute
summary values within the budget.
If you select the 4-4-5 4-5-4 or 5-4-4 weekly distribution option Planning treats quarterly values
July Previous Calendar Year Jul 12 to Jun 13 FY13
If you select the 4-4-5, 4-5-4, or 5-4-4 weekly distribution option, Planning treats quarterly values
as if they were divided into 13 weeks, and distributes weeks according to the selected pattern. For
example, if you select 5-4-4, the first month has five weeks, and the next two months have four
weeks.
Be aware that you cannot change this option after you create the application.
All Years Parent Member
When you enable the All Years parent member, you can view the accumulated data across y p , y
multiple years (for example, a projects total cost up to its end date). The parent member does not
include the No Year member, if one is defined for the application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

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

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Plan Types
Budgeting
application
Capex Workforce
Plan
Type 1
Plan
Type 2
Plan
Type 3
Additional modules available for purchase
Human Capital
Planning
Project Financial
Planning
Plan types represent an Essbase database cube, each with their own dimensionality. An Essbase
database is created for each plan type.
Note: Ensure that you have the plan types that you want in your application when you create it,
y p yp y y pp y ,
because you cannot add plan types after creating an application, and you cannot change the
name of the plan types.
The number of plan types depends on the needs of your organization. For example, if your Sales
Department has a yearly revenue plan, and your finance department has a P&L plan, you can
define two plan typesRevenue and P&L.
You set plan types for applications, dimensions, and members, and you select one database for
data storage by selecting the source plan type The stored data values are shared between plan data storage by selecting the source plan type. The stored data values are shared between plan
types.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

As you create accounts, entities, and other elements of the application, you associate them with
the plan types. The association ensures that the database contains only relevant application
dimensions, members, and data values; and that application design, size, and performance are
optimized.
You can also share data between plan types, to ensure that the database remains small and
efficient. For example, the Revenue plan may include several sales detail accounts that roll up into
a Total Product Sales account. You configure the P&L plan to include the Total Product Sales
account and omit sales detail accounts. Then, you bring the data value for Total Product Sales
into your P&L plan without account details.
Note: You can add the Workforce Planning and Capital Asset Planning plan types to an existing
application if you purchased these modules. pp y p

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Dimensions
Periods Accounts Entities
Applications contain dimensions that represent the categories of data in your organization. For
example, you identify time periods, such as YearTotal, Q1, or Jan, in the Period dimension. You
identify budgeted items, such as SG&A for expenses, in the Account dimension, and you identify
departments for your organization in the Entity dimension.
Note: You can include up to 20 dimensions in Planning applications.
The elements that compose a dimension are called members. In the slide, Operating Margin,
Gross Profit, and 4400 are members of the Account dimension. The dimensions defined in a
Planning application become the dimensions in the Essbase databases.
You can assign alternative names, or aliases, to dimension members. You can create up to 10
aliases for each dimension member including the default alias For example members in the aliases for each dimension member, including the default alias. For example, members in the
Entity dimension may be identified by their number (220, 225, 230, and so on) or by their
descriptive alias (Georgia, Texas, and North Carolina). Members can also have aliases for
different languages.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Required Dimensions
Account
Scenario
Entity
Version
Period
Year
Currency and HSP_Rates
(for multicurrency applications)
All Planning applications must include the Account, Entity, Period, Scenario, Version, and Year
dimensions. Multicurrency applications require two other dimensions: Currency and HSP_Rates.
Note: Multicurrency applications include seven required dimensions because the HSP Rates
y pp q _
dimension is not counted as a Planning dimension though you can see that dimension in Essbase.
In addition to setting up required dimensions, you can also set up custom dimensions. You can set
up attribute, smart list, and UDA dimensions. For attribute dimensions, you must specify a base
dimension.
Period and Year
As the administrator, you specify base time periods (such as months) and distribution of weeks in
the Period dimension. You use the Year dimension to add years to the calendar.
Scenario and Version
The Scenario and Version dimensions represent the broadest categories of data in your
application. Scenario describes the type of data in a plan, such as budget, actual, or forecast, as
well as the plans time span.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Version allows for flexibility and iterative planning cycles. For example, your application can have
two versions, Working and Final, for each scenario.
You can also use versions to model possible outcomes based on different assumptions about
interest rates, growth rates, and so on. For example, your application can include a Best Case and
Worst Case version for each scenario.
Entity
The Entity dimension represents the flow of Planning information through your organization. For
example, you can establish a geographic entity for each responsibility center that submits a
budget plan.
Account
The Account dimension specifies the data to be collected from budget planners. You can establish
accounts for all budgeted items. Examples of accounts are Rent Expense and Cash on Hand.
Currency
The Currency dimension identifies the currency in which values are displayed. You can plan in
one or more currencies.
HSP_Rates
The HSP_Rates 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 HSP_Rates dimension for multicurrency applications. This
dimension is visible only in Essbase.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

User-Defined Dimensions
Planning applications can have up to 20 dimensions.
Examples:
Employee
Product Product
Channel
Project
Customer
Account Executive (attribute dimension) ( )
If your Account dimension does not provide sufficient plan detail, you can include user-defined
dimensions. Because you can have a total of 20 dimensions in Planning applications, you can
include up to 13 user-defined dimensions for multi-currency applications, or up to 14 user-defined
dimensions for single currency applications. Attribute dimensions do not count toward the total.
For example, if your application includes revenue accounts, you can define a Customer dimension
to budget revenue for each customer. You can also create an Account Executive dimension
(Attribute) to specify sales territory ownership for each customer.
You can perform the following tasks for user-defined dimensions:
Assign plan types at the dimension level, not at the member level (you cannot delete user-
defined dimensions ) defined dimensions.)
Rearrange the dimension hierarchy
Share members

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Dimension Hierarchies: Genealogy
The descendants of YearTotal include Q1, Q2, Q3, and Q4 and
all their children.
Ancestors of Apr:
Q2 and YearTotal
Parent of Apr, May,
and Jun: Q2
Children of Q2
Siblings:
Q3 and Q4
Siblings: Oct,
Nov, Dec
Members within dimensions have defined relationships with one another. There are three ways to
reference members: genealogy, generations, and levels.
In the slide, you can refer to members based on familial terms such as parent-child, siblings, or
, y p , g ,
ancestor-descendant.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Dimension Hierarchies: Generations and Levels
Level 3
Gen 1
Gen 2
Gen 3
Level 1
Level 2
Outline
Gen 4
Gen 3
Level 0
Level 0
Leaf Node
Attributes
Attribute
dimension
You can use numeric terms to reference members based on generations or levels. Generations
start at the number one at the dimension name and increase as you move down in the hierarchy.
The numeric values are absolute, and the generation value increases with each successive set of
descendants. In the slide, Customer is generation one, and All Customers is generation two.
Levels start at zero at the bottom of the hierarchy, also referred to as leaf nodes or base members,
and increase as you move up the hierarchy. Level numbers are relative, so to determine a level
number, you must know its relationship to other members. In the slide, both N002 and No
Customer are level 0 because they are both at the bottom of their respective hierarchies.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Drilldown Process
Period Entity Account Customer
M th
Quarter
Year
E t
N America
Worldwide
IBT
Net Income
Income
Statement
R001
Retail
All
Customers
Month
New York
East
Operating
Margin
IBT R001
Drilling down is an analytical technique for navigating through levels of data from the most
summarized (top) to the most detailed (bottom). In the Period dimension shown in the slide, you
can drill down from Year to Quarter to Month.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Dimensions and Data
Data is aggregated
to parents based on
aggregation options.
+ Add
Data is input
- Subtract
* Multiply
/ Divide
~ Ignore
^ Never
Data is input
into base-level
members.
Data is entered into the base-level members of the dimensions, not into the parent members,
unless you work with a target version. You use target versions to perform top-down budgeting by
setting targets at the parent level. The values for the parent-level members are aggregated from
the values of their children when the Planning database is calculated in Essbase.
For the example in the slide, the data values for the base-level members are rolled up to the
parent-level members. TotalRevenues (+) and TotalCosts (-) are then rolled up to their parent
(GrossMargin).
Data is aggregated to parents based on the following aggregation options: + (Add), - (Subtract), *
(Multiply), / (Divide), ~ (Ignore), and ^ (Never).

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Dimensions and Metadata
The data value for January, FY12, Actual, Final, Net Sales for
Alliance Merchandise in New York is 3689.00.
Data
3689 00
Data
Metadata
3689.00
Metadata are the structural elements of an application that describe and hold data such as
dimension names, member names, properties, and security. For the example in the slide, the
metadata are the dimension member labels Net Sales, Actual, Final, January, New York, FY12,
and Alliance Merchandise. These dimension members are the metadata and describe what data
values they represent.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

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

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Determining the Number of Data Blocks
Dense
Period
Jan to Dec
Dense
Account
Account1
Sparse
Version
1
st
Draft
Sparse
Entity
Corp
Sparse
Scenario
Budget
Sparse
Year
2013
Account2
Account3
Final
Each block contains 36 cells
(3 accounts * 12 time periods)
Multidimensional databases have sparse dimensions, which contain a low percentage of occupied
data values in each combination of dimensions. For example, each entity sells only to a subset of
customers, so most combinations of entity and customer have no associated data. By default,
Entity, Scenario, Version, and Year are sparse dimensions.
Multidimensional databases also have dense dimensions, which contain a high percentage of
occupied data values in each combination of dimensions. For example, when data exists for an
entity, it typically exists for most or all accounts and time periods. Account and Period are typically
dense dimensions and are set to be dense dimensions by default.
Dense dimensions determine the data block structure. A data block always includes all stored
members of all dense dimensions members of all dense dimensions.
Note: If your application uses currencies, the HSP_Rates dense dimension stores exchange
rates.
The data is stored at the intersections formed by the members of the dense dimensions. For
example, if the Account and Period dimensions are dense, the combination of one time period
(January) and one account (Sales) equals one cell of data within a data block.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

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. For applications that use
currencies, the Currency dimension is set to sparse.
Note: If you add other dimensions, such as Product or Customer, you can tag them as either
dense or sparse. The default is sparse.
The simple database in the slide has two data blocks, as follows:
Corp -> Budget -> 2013 -> 1st Draft
Corp -> Budget -> 2013 -> Final
Because the dense dimensions determine the data block structure, each data block contains 36
cells (3 accounts 12 time periods).

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

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

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Guidelines for Optimal Data Block Performance
The data structure can have a significant impact on data retrieval and calculation time. Although
design considerations can vary significantly between applications, use the following general
guidelines for performance:
Performance is typically best if the cells that need to be calculated or viewed are in the same
data block.
Considerations for dense and sparse settings apply to calculations.
The number of cells in a data block grows exponentially as dense dimensions are added to
the database.
Performance Efficiency
Performance efficiency is affected by dimension settings and data block size.
Considerations for dense and sparse settings apply to calculations. Here is a typical calculation in
the Account dimension: Net Profit = Gross Sales - Cost of Goods Sold.
If Account is tagged as dense, the data block includes the members that are needed for the
calculation.
If Account is tagged as sparse, data must be retrieved from three data blocks to perform the
l l ti lti i l ffi i t f calculation, resulting in less efficient performance.
The number of cells grows exponentially when dense dimensions are added to the database. For
example, if your database has 200 Account members and 12 Period members, it contains 2,400
cells. If you add the HSP_Rates dimension as a dense dimension, and it has 10 members for
currency rates, the number of cells jumps to 24,000 (200 12 10).
You maximize Planning application performance in Dimension Editor as follows:
Tag each dimension as dense or sparse in performance settings Tag each dimension as dense or sparse in performance settings.
Specify dimension evaluation order by plan type.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Aggregation, Storage, and Calculation Options
Aggregation options define calculations based on member
relationships in the hierarchy.
Storage options define if data is stored or calculated.
Calculations are performed in a specified order Calculations are performed in a specified order.
Planning data is stored in Essbase databases. Data storage in Essbase is different from data
storage in relational databases, so understanding how Essbase stores and retrieves data is
important for designing an application that functions efficiently.
Setup of dimension properties affects storage and calculation of information, display of information
in forms and reports, and database efficiency.
You set up aggregation, storage, and calculation options to define how data is calculated.
Aggregation options determine whether data is added, subtracted, multiplied, divided,
ignored, or treated as a percentage in relationship with other members in the hierarchy.
Storage options define how data is maintained; data can be stored or calculated.
The order in which calculations are performed affects calculation results.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Aggregation Options
You define calculations in the hierarchy based on parent-child
relations.
You define calculations within dimension hierarchies by using aggregation options. Aggregation
options determine how values of child members are aggregated to the parent value.
For example, Sales and Cost of Goods Sold (COGS) are children of the Net Income member. If
p , ( )
you set the aggregation option for the Sales member to addition and if you set the aggregation
option for COGS to subtraction, the aggregated value for the Net Income member represents
Sales minus COGS.
The following are the aggregation options:
+ Addition
- Subtraction
* Multiplication
/ Division
% Percentage
~ Ignore
^ Never
Note: Because dimension members can belong to more than one plan type, you can specify g p yp y p y
different aggregation options by plan type.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Data Storage Options
You use storage options to optimize performance and disk
usage:
Store
Dynamic Calc and Store Dynamic Calc and Store
Dynamic Calc
Shared
Never Share
Label Only
To optimize performance and disk usage, you use storage and calculation options for dimension
members.
The storage type for a member affects the size and calculation performance of your database. If
g yp p y
you control the number of members that store data, you can improve the performance of your
application.
You change Essbase storage options by setting the following member properties in the
application:
Store
The Store option stores the data values of members.
Dynamic Calc and Store
The Dynamic Calc and Store option calculates the data value the first time that the member is
retrieved, and then saves the value. Subsequent retrievals use the stored value. This option is
used infrequently.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Dynamic Calc
The Dynamic Calc option calculates the data values when the member is retrieved. The value is
not stored in the database. Dynamic Calc is most useful for parent-level dense dimension
members.
Because values for Dynamic Calc members are not stored, the reduced data block size improves
performance. However, retrieval time for the member is increased.
Share Data and Never Share
Typically, you use the Share Data option when you want to allow alternate rollup structures. You
can set members within the same dimension to share data values, enabling alternate rollup
structures within the application. You must set the data storage to Share Data so that the shared
b i dd d h th li ti i d l d member is added when the application is deployed.
Label Only
Label Only members are virtual members and have no associated data. Typically, you use Label
Only to group members and to navigate and report more easily from Financial Reporting or
Essbase Smart View Provider.
For example, a parent member named Statistical groups accounts such as Headcount and
Interest Rate Because these accounts are not aggregated to a meaningful total there is no need Interest Rate. Because these accounts are not aggregated to a meaningful total, there is no need
to calculate or store a value for the Statistical member.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Calculation Options
y Aspen Diet Cola Actual
January February March Q1
Sales 326.70 113.74 137.94 578.38
COGS 287.5 96.68 118.63 502.81
Margin 39.2 17.06 19.31 75.57

Before two-pass
Aspen Diet Cola Actual
January February March Q1
Margin Percent 12 15 14 41

After two-pass
Sales 326.70 113.74 137.94 578.38
COGS 287.5 96.68 118.63 502.81
Margin 39.2 17.06 19.31 75.57
Margin Percent 12 15 14 13

Essbase calculates the outline (dimensions) in the following order:
1. Account dimension
2 Time dimension
2. Time dimension
3. Other dense dimensions in top-down order
4. Other sparse dimensions in top-down order
5. Members that are tagged as Two-Pass Calculation
The calculation order in Essbase can affect the results. Calculation of a dimension member may
depend on the calculated results of another dimensions members when that dimension is
calculated after the first dimensions calculation.
In such situations, you can assign the Two-Pass Calculation option to a member. After Essbase
calculates the database, a second pass calculates the tagged members.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The Two-Pass Calculation option is used primarily for members of the Account dimension. For
other dimensions, the option is valid only for Dynamic Calc or Dynamic Calc and Store members.
For the example in the slide, calculation of the Margin Percent account for North America depends
on the aggregated value of the Gross Margin and Net Revenue accounts (Margin Percent = Gross
Margin / Net Revenue). Because the Entity dimension is calculated after the Account dimension,
the aggregated values are not available.
To calculate Margin Percent correctly:
1. Essbase aggregates the values for the children of North America to derive the totals for
Gross Margin and Net Revenue.
2. You select Two-Pass Calculation for the Margin Percent account for North America so that
Essbase can make a second pass Essbase can make a second pass.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the statements that are true about dimension
hierarchies.
a. All top-level members are called provisional members.
b All members below a parent are called descendants b. All members below a parent are called descendants.
c. The bottom-level members of a hierarchy are called base-
level members.
Answer: b, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Multidimensional databases contain sparse dimensions, which
contain a low percentage of occupied data values in each
combination of dimensions.
a. True
b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You use aggregation options to define calculations within
dimension hierarchies.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe applications and application framework
Identify required and user-defined dimensions in Planning
Describe the data block creation process Describe the data block creation process
Explain aggregation, data storage, and calculation options

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Practice 3-1
The practice covers the following topic: Accessing Essbase
Administration Console

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

C ti A li ti Creating Applications
in Planning Administration

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Describe Planning Administration and the application
creation process
Create applications in Planning Administration Create applications in Planning Administration
Manage Planning applications and data sources
Create and refresh Essbase databases

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Administration: Overview
Planning application administration:
Create applications with a wizard.
Modify dimensions and members in single applications on
the Dimensions page. p g
Set up business rules for complex calculations.
Performance Management Architect:
Create applications with a wizard.
Design applications graphically in a central library that
includes tools for auditing, tracking, and comparing includes tools for auditing, tracking, and comparing
information.
Set up business rules for complex calculations.
You create applications with Planning application administration or Performance Management
Architect. Different menus and options are available for each method. With both methods, you
create applications with a wizard to ensure that all required dimensions are included. For all
Planning applications, you use Calculation Manager to set up and modify business rules for
complex calculations.
Planning Application Administration
Planning application administration enables you to work with single applications. With Planning
application administration, you can create and delete applications, manage data sources, and
upgrade applications.
Aft ti th li ti dd d dif di i d b t f After creating the application, you can add and modify dimensions and members, set performance
options, and define the dimension evaluation order on the Dimensions page.
Performance Management Architect
Performance Management Architect enables you to manage, create, and deploy applications
within one interface. You create applications with Application Creation Wizard to ensure that all
required dimensions are included. Then, you work in a central (shared) library to modify
dimensions and metadata, and to audit, track, and compare information. dimensions and metadata, and to audit, track, and compare information.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Application Creation Process
1. Configure relational databases and data sources.
2. Use Planning application administration to create
applications:
Specify data source application name and type and Shared Specify data source, application name and type, and Shared
Services project.
Select calendar.
Specify currencies.
Set up and name plan types.
Verify application selections Verify application selections.
With Planning application administration, you create applications by using a wizard, which ensures
that you include all the required components needed for a successful deployment. The wizard
contains property and dimension information by application type.
You can create applications in Planning application administration if you are assigned two Shared
Services roles: Dimension Editor and Planning Application Creator. You can then administer
Planning on an application-by-application basis.
Here are the high-level steps for creating Planning applications:
Configure relational databases for Planning, and configure data sources.
Create applications, including selecting a data source, application name and type, Shared
S i j t l d i d l t Services project, calendars, currencies, and plan types.
When you create Planning applications, a folder and database are created on the Essbase server.
After adding any metadata to your application, you refresh the Planning application so that the
Essbase database is updated.
You register Planning applications with Shared Services when you create your Planning
application. The Shared Services project that you select in Planning application administration is
the project in which your application is registered. You can change the Shared Services project the project in which your application is registered. You can change the Shared Services project
after application creation.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Applications with
Planning Application Administration Planning Application Administration
Here are guidelines for creating applications:
You can upgrade an application created with Planning application administration to a
Performance Management Architect application, and you can change a Performance
g pp , y g
Management Architect application to one created with Planning application administration.
You can add or modify metadata in applications after those applications are created. You
can import metadata from a file or you can make changes manually in Dimension Editor.
You can modify or load metadata into dimensions. For example, you can add dimensions
and load metadata for user-defined dimensions, such as Customer.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To create applications with Planning application administration:
2 Click Action and select Create 2. Click Action, and select Create.
The Select page is displayed.
3. Complete the following actions:
- Select application information, such as data source, the application name, application
type, and Shared Services project.
- Set up the calendar.
- Set up currencies - Set up currencies.
- Specify plan types.
- Review application information.
4. Click Create.
The application is created.
5. Select Navigate, then Applications, and then Refresh to ensure that the application is
added to the Available Applications list added to the Available Applications list.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Selecting Application Information
Select a data source.
Enter an
application
name.
Select the application type.
Select a Shared Services project.
When you create a Planning application, you specify application information, such as the
application name and type. Your Planning application is registered with the selected Shared
Services project when the application is created. However, you can modify the registration after
the application is created.
To select application information:
1. In the Data Source drop-down list, select a data source.
2. In the Application box, enter an application name. It can be up to eight characters, and must
not be the same as an existing Essbase or Planning application.
3. Optional: In the Description box, enter a description.
4. In the Application Type list, select General.
5. In the Shared Services Project drop-down list, select a Shared Services project.
6. Click Next.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up the Calendar
Specify first fiscal
Specify
Specify first fiscal
year, number of fiscal
years, fiscal year first
month, fiscal year
start date, and
weekly distribution.
Specify
base time
period.
You set up the calendar to specify the base time periods, the first year you plan to store data, and
other details about your organizations calendar.
To set up the calendar:
p
1. For Base Time Period, select an option: 12 Months, Quarters, or Custom.
2. In the First Fiscal Year drop-down list, select the first fiscal year.
3. For Number of Fiscal Years, enter the total number of years for your application.
4. In the Fiscal Year First Month drop-down list, select the fiscal year first month.
5. Optional: If the fiscal year first month is a month other than January, select the fiscal year
start date from the drop-down list: p
- Select Same Calendar Year to select the same calendar year as the fiscal year. For
example, if the fiscal year starts in 2013 and the start month is April, then your
application start period and year is April 2013. This option is selected by default.
- Select Previous Calendar Year to select the previous calendar year as the fiscal year.
For example, if the fiscal year starts in 2013 and the start month is April, then your
application start period and year is April 2012.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

6. In the Weekly Distribution drop-down list, select one of the following options: Even
Distribution, 4-4-5 Distribution, 4-5-4 Distribution, or 5-4-4 Distribution.
7. For All Years parent, select Yes or No to specify whether you want to view the
accumulated data across multiple years.
8. Click Next.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Currencies
Select default
currency.
Indicate if the application
supports multiple
currencies.
When you create your application, you specify the currency settings, such as the default currency
for entities in the application, and establish whether the application supports currency conversions.
To set up currencies:
p
1. In the Default Application Currency drop-down list, select the currency.
2. For Will your application support multiple currencies? select Yes or No.
3. Click Next.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Selecting and Naming Plan Types
Select and name
plan types.
You specify one to three plan types for your application.
To specify plan types:
1 Under Standard Plan Types select one or more plan types
1. Under Standard Plan Types, select one or more plan types.
2. Optional: In the name boxes, enter names for the plan types.
3. Optional: Under Planning Specialized Modules, select one or more modules.
4. Click Next.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Reviewing Application Information
Review the application
settings before you
create it.
Before you finish the application creation process, you can review and modify application settings.
After creating applications, you cannot change some settings, such as the first fiscal year or
multicurrency selection.
To review application information:
1. On the Finish step, verify the selected settings.
2. Perform the following steps to modify a setting:
a. Select the area that you want to change.
b. Make the changes, and in the graphical path, select Finish.
3. Verify the selected settings, and click Create. y g ,

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Modifying Application Registration
The Shared Services project or application group is a container for EPM System applications.
Shared Services tracks registered EPM System applications (so you can use single sign-on,
provision users, and so on).
You will need to register/reregister a planning application if you restored it but it is not accessible
in the workspace.
If you created a new application and you selected a Shared Services project, your application is
automatically registered. However, if you need to move the application to another Shared Services
project, you can reregister the application.
To modify application registration:
1. Select Navigate, then Applications, then Planning and then, select an application.
The Planning application is opened.
2. Select Administration, then Application, and then Settings.
3. On the System Settings tab, in Shared Services URL, click Register Shared Services.
4. Select an option: New Application Group, or Existing Application Groups.
5. If you chose to create a new application group, in New Application Group, enter a group.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

6. If you want to register the application in an existing application group, in Existing Application
Groups, select an application group.
7. Click OK.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Managing Applications and Data Sources
Managing data sources
Creating Essbase databases
Refreshing Essbase databases
You configure data sources to establish the connection between the Planning system database (a
relational store), the application relational database, and the applications Essbase databases.
You can configure data sources in Planning application administration. You can also set the data
source for the application to Unicode mode. Unicode-mode applications support multiple character
sets. When Essbase works with Unicode-mode applications, it uses the UTF-8 encoding form to
interpret and store character text. Character-based artifacts in Unicode-mode applications, such
as member and alias names, can include characters from different languages.
The procedure for creating relational databases is determined by the relational store that your
company uses (Oracle, Microsoft SQL Server, or IBM DB2). For more information, see the Oracle
Essbase Database Administrators Guide.
When you create Planning applications, folders and files are created on the Essbase server to
store application data. To create an initial outline with the dimension structure, you must create the
databases from Planning.
After you update metadata or the dimensional structure within Planning, you refresh the Essbase
database to ensure that those changes are reflected in Essbase. You refresh Essbase databases
as a separate action within Planning.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

When you create or refresh the Essbase database, all other tasks are unavailable to other users,
including the application owner. All users must be logged off from the Planning application before
Essbase databases can be refreshed. Oracle recommends that administrators send a broadcast
message to all users, asking them to save their work and close the application before the Essbase
li ti i f h d Pl i d t l t d i f h application is refreshed. Planning does not log out users during refresh.
Application refresh time depends on factors such as the number of entities and users in the
application, and many users and security filters lengthens refresh time. To maximize system
availability, you can transfer access permissions information during nonpeak hours.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Managing Data Sources
System
Database
Taxplan
Hyplan
Applications
included in the
system database
Relational database
schema for Planning
li ti
Finbud
Taxplan Finbud Hyplan
applications
Although data values are stored in Essbase databases, some information is stored only in the
application relational database schema. For example, planning unit annotations, account
annotations, comments, and supporting details are stored in the Planning relational database
schema.
When you create applications, each Planning application is associated with a system database
and a relational database schema. In the slide, the Taxplan, Hyplan, and Finbud applications were
created and are associated with the system database. Each application has its own relational
database schema.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To configure data sources:
2 Click Manage Data Source 2. Click Manage Data Source.
The Manage Data Source page is displayed.
4. In the Data Source Name box, enter the data source name.
5. Optional: In the Data Source Description box, enter a description.
6. Under Application Database, perform the following actions:
a Select the relational database platform a. Select the relational database platform.
b. Specify relational database details (server, port, database, user, password).
7. Under Application Database, click Validate.
A message indicates a successful or failed connection to the relational database. You must
8. Under Essbase Server, specify the Essbase server name, username, and password.
9 Optional: Select Unicode Mode 9. Optional: Select Unicode Mode.
10. Under Essbase Server, click Validate.
A message indicates a successful or failed connection to the Essbase database. You must
11. Click Finish.
A message indicates that the data source was created successfully.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Managing Essbase Databases
Outline (OTL)
Calculation Script (CSC)
Report Script (REP)
When you create Planning applications, you create an initial outline with the dimension structure.
The folders and files needed to store the dimension structures are created on the Essbase server
as part of the creation process. The applications have their own folders. Server-based applications
f f f
are in a folder under user_projects in the oracle\middleware folder, for example:
c:\oracle\Middleware\user_projects\epmsystem1\EssbaseServer\
essbaseserver1\app\Hyplan
The databases associated with the application are in a folder under the applications folder, for
example:
EssbaseServer\essbaseserver1\app\Hyplan\Incstmt
This folder structure is located on the Essbase server This folder structure is located on the Essbase server.
Essbase objects, such as calculation scripts, load rules, and reports scripts are typically located in
the database folder with which they are associated. However, they can also be located in a client
folder on your local client machine, for example:
\Hyperion\Essbase\Client

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

You store the following objects in the Essbase folders:
Database outlines define the structure of the multidimensional database, including
dimensions and member hierarchies. The file extension is OTL.
Calculation scripts perform custom calculations, standard consolidations, and p p , ,
mathematical operations defined in the database outline. The file extension is CSC.
Report scripts define reports based on data in one or more databases. The file extension is
REP.
Note: You can later choose to manually create Essbase databases as a separate action within
Planning. Manually creating Essbase databases replaces the folders and files created when the
application was created. Keep in mind that you will need to update any customizations that were
overwritten by the manual create action such as calculation or report scripts or load rules that you overwritten by the manual create action such as calculation or report scripts, or load rules that you
added to your application.
While building your outline, you can transfer database changes and access permissions
separately to improve performance and make changes quickly available to users. When the
outline is complete, Oracle recommends that you include access permissions when refreshing
database information.
When you create or update security filters in Essbase, you can validate that the size of the security
filters does not exceed the Essbase limit of 64 KB per row.
You can generate security filters for all users or selected users. You can generate security filters
for all users in the application by not selecting the Validate Limit option.
You can evaluate and apply access permissions for all instances of the member (base and
shared) by selecting the Shared Members option. If you select this option, the least restrictive
access permissions are applied to all occurrences of the member. For example, if a shared
members parent has Write access assigned to all its children and another shared member under member s parent has Write access assigned to all its children, and another shared member under
another parent has Read access assigned to all its children, the base member and all its share
members are given Write access.
To create Essbase databases:
1. In Planning, select Administration, then Application, and then Create Database.
The Create Database page is displayed.
2. Select options: 2. Select options:
- Database: Creates an Essbase database for the application
- Update custom-defined functions: Updates Planning custom-defined functions for
the application when creating the application database
- Security Filters: Generates security filters in Essbase for use by third-party
applications. Stores access permissions in an encrypted file (essbase.sec)
Optional: Select Validate Limit to identify security filters that exceed the
Essbase security filter of 64 KB per row.
Optional: Select Shared Members to evaluate and apply the least restrictive
access to shared members.
3. Click Create.
4. At the Manage Database prompt, click Create to continue.
5. Click Finish.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Refreshing Essbase Databases
You must refresh the application database whenever you change the application structure.
Changes you make to applications are not reflected to users performing data entry and approvals
tasks until you refresh the Essbase database. For example, when you modify properties of an
entity member, add a scenario, or change access permissions, the changes are stored only in the
Planning relational database until you refresh the application database to update those changes in
Essbase.
You update the following components during a refresh of the database:
Essbase security filters
Members and associated properties
C t tt ib t Custom attributes
Exchange rate values
Member formulas
Additions or changes to alias tables
UDAs
When you refresh the Essbase database, it is restructured.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To refresh Essbase databases:
1. In Planning, select Administration, then Application, and then Refresh Database.
The Refresh Database page is displayed.
2 Select options: 2. Select options:
- Database: Refreshes an Essbase database for the application
- Update custom-defined functions: Updates Planning custom-defined functions for
the application when refreshing the application database
- Security Filters: Generates security filters in Essbase for use by third-party
applications. Stores access permissions in an encrypted file (essbase.sec)
Validate Limit: Identifies security filters that exceed the Essbase security filter of y y
64 KB per row
Shared Members: Evaluates and applies the least restrictive access to shared
members
3. Click Refresh.
4. At the Manage Database prompt, click Refresh to continue.
5. Click Finish.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that you can perform with Planning application
administration.
a. Create Planning applications.
b Delete Planning applications b. Delete Planning applications.
c. Convert Performance Management Architect applications
to applications created with Planning application
administration.
d. Register Planning applications with Shared Services.
Answer: a, b, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Planning application administration creates the following two
dimensions for multicurrency applications in Essbase: Currency
and HSP_Rates.
a. True
b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
When you create an application with Planning application
administration, and you select a Shared Services project, the
application is automatically registered.
a. True
b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe Planning Administration and the application
creation process
Create applications in Planning Administration Create applications in Planning Administration
Manage Planning applications and data sources
Create and refresh Essbase databases

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Applications in Planning Administration
Accessing Finbud in Workspace

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

M i Di i Managing Dimensions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Manage and organize dimensions
Sort members

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Building Dimension Hierarchies
Sample Entity
dimension hierarchy
Dimension hierarchies define relationships and consolidations between members in
applications. Relationships are represented in a graphical hierarchy diagram on the
Dimensions page. For example, the Period dimension contains the YearTotal member, which
contains the Q1, Q2, Q3, and Q4 members. The quarters contain members for the
corresponding months. Monthly data values roll up to the quarters, and quarterly data values
roll up to the year total. In the example in the slide, the Entity dimension includes the
Worldwide member and its descendants.
You create dimensions and members on the Dimensions page or you import them into the
application. More information about loading metadata is provided in a later lesson.
You can strategically classify and order dimensions to improve performance on the You can strategically classify and order dimensions to improve performance on the
Performance Settings tab. The Evaluation Order tab enables you to specify which data type
prevails when a data intersection has conflicting data types. For example, if Account members
are set to the Currency data type, and Product members are set to the Smart List data type,
you can set whether the Currency or Smart List data type prevails at an intersection.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Dimension Hierarchies
Add Child.
On the Dimensions page, you create and update dimensions and members, assign access
permissions to members, rearrange members, and modify member properties. In the example
in the slide, a child member, N006 (World of Computers), is added below the National
Accounts customer.
When you create or refresh the database, the Essbase outline is generated with members in
the order in which they are displayed on the Dimensions page.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Guidelines for Dimension and Member Names
Dimension and member names can be up to 80 characters in length. They cannot start with
the following characters:
Backslash (\) Backslash (\)
Comma (,)
Plus sign (+)
Minus sign (-)
Period (.)
Less than (<)
E l ( ) Equal (=)
At (@)
Underscore (_)
Brackets ([])
Pipe (|)
Quotation mark ()
Note: Do not use reserved Essbase words such as #Missing.
About Shared Members
Shared members allow alternate hierarchies (rollup paths) within the same dimension. You
can create multiple rollup paths for your data by placing child members under more than one
parent. Note the following points about shared members:
Shared members do not store data, but point to the data of stored members. , p
You must position shared members in the database outline below their stored members.
You create shared members as level-0 members that have the same name as their
stored members, and you set the data storage to Shared.
Shared members share some property definitions with their stored members, such as
member name, alias name, base currency, and plan types for which members are valid.
You can enter data in shared members, and the values are stored with the stored ,
members.
When you edit the properties of the stored member under one parent, its properties are
updated for all parents.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To set up dimension hierarchies:
1. Select Administration, then Manage, and then Dimensions.
The Dimensions page is displayed.
2 On the Dimensions tab select a dimension 2. On the Dimensions tab, select a dimension.
3. Select a dimension member.
4. Click Add Child or Add Sibling .
The Member Properties tab for Add Child or Add Sibling is displayed on the
Dimensions page.
5. Set up the member properties.
6 O ti l P f f th f ll i ti 6. Optional: Perform any of the following actions:
- On the Attribute Values tab, select attribute values to assign to the member. You
can assign attribute values to sparse dimension members.
- On the UDA tab, create and select UDAs for the member.
- On the Member Formula tab, define and validate formulas for the member.
7. Click Save.
8. Optional: To add user-defined dimensions, such as Product, perform the following
actions:
- Click Add Dimension .
- Set up the dimension properties, and click Save.
9. Optional: On the Performance Settings tab, perform any of the following actions:
- Click Move Up or Move Down to change the order in which dimensions
are displayed in the Essbase outline.
- For each dimension, select Dense or Sparse.
10. Optional: On the Evaluation Order tab, select the order in which the dimensions are
evaluated, as follows:
a. In the Select Plan Type drop-down list, select the plan type.
b. In the Available Dimensions section, select dimensions, and click Move to
move them to the Selected Dimensions section.
c. In the Selected Dimensions section, select a dimension, and click Move selected
items up one in list , Move selected items down one in list , Move
selected items to top of list , or Move selected items to bottom of list to
change the order in which dimensions are evaluated.
d. Click Save.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Modifying Member Properties
Account dimension member Customer dimension member
You can modify the properties of dimension members. Some properties are valid only for
certain dimensions. For example, you choose the account type, variance reporting, and time
balance options for Account members; however, you do not make selections for those
properties for Entity members.
To modify member properties:
2. On the Dimensions tab, select a dimension.
3. Select a member, and click Edit .. 3. Select a member, and click Edit ..
The Member Properties tab for Edit Member is displayed on the Dimensions page.
4. Modify member properties, and click Save.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Property Value Inheritance
Currency
property
is set to Euro.
Descendants of Europe
inherit EUR as the value inherit EUR as the value
for the Currency property.
Currency
property is set to
GBP, overriding
inherited value.
Descendants of United
Kingdom inherit GBP for
the Currency property. inherited value. y p p y
Inheritance allows high-level members to share their property values with lower-level
members in the hierarchy. It allows new members to automatically obtain their property values
from the appropriate ancestors. The example in the slide shows the Europe currency property
set to EUR. Therefore, Europes descendants inherit the euro currency property.
Proper use of inheritance enhances the referential integrity of your application and reduces
maintenance requirements.
Property value inheritance rules are processed in the following order:
1. If a user directly entered a value for the member, it uses that value.
2. It moves up the ancestral tree and uses the first entered value. Thus, a change to the p g
properties of an ancestor can affect descendant members that inherit its value.
3. It uses the system default value for the property.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Alternate Hierarchies
E200 occurs in an
alternate rollup.
The quarters
and months
occur in
alternate rollups.
You can create multiple rollup paths for your data by placing a child member under more than
one parent. The examples in the slide illustrate the following:
Jan, Feb, and Mar are members of a YearTotal rollup, with YearTotal as the top
, , p, p
member, and a Q1 rollup, with TotalYear as the top member.
Entities E200, S310, N400, and W560 are members of the TotalGeography hierarchy
and the Function hierarchy.
A member has the same property settings under all parents. However, one member has the
Store property, and additional members have the Shared property. If you edit the properties of
a stored member, its properties are updated for all parents.
Note: You can set different aggregation properties for shared and base members.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Managing Member Hierarchies
Manage member hierarchies by performing the following tasks:
Moving members
Renaming members
Deleting members Deleting members
Finding members
After your metadata is loaded into your application, you can make changes to the metadata.
You can reorder a parents children by moving members in the hierarchy. You can move one
member or a group of members in the same branch. If you move Account members whose
Valid For Plan Type settings differ from their new parent, the moved member settings change
to match the settings of the new parents. If you move members whose Source Plan Type
settings differ from their new parent, the moved member Source Plan Type is reset to match
the first valid plan type.
You can rename members. You can delete members.
Note: Remember that you must refresh the database so that Essbase is updated with your
changes changes.
To facilitate locating members in larger hierarchies, you can search for members in the
hierarchy.
To move members or branches among siblings:
3. Select a member or branch to move.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

4. Perform one of the following actions:
- Click Move Up to move the member up one position.
- Click Move Down to move the member down one position.
To move members including parents and children: To move members, including parents and children:
3. Select a member or branch to move.
4. Click Cut .
5. Click the destination level under which to move the members.
6. Click Paste .
7. In the confirmation message, click OK.
To rename members:
The Dimensions page is displayed The Dimensions page is displayed.
3. Select a member to rename.
4. Click Edit .
5. Change the member name and click Save.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Deleting Members
Before you delete members:
Research member usage
Delete that member throughout Planning artifacts
When you delete members the associated planning units When you delete members, the associated planning units
are also deleted.
You can delete members from applications but before you delete any members, you must
understand the impact of deleting those members. You can research where in the application
they are used (in which forms, planning units, exchange rates, and so on) by using Show
Usage.
For entities, you must delete the entity member throughout Planning before deleting it from
Dimensions. For example, if the entity member is used in a form, you must delete it from the
form before deleting it from Dimensions.
When deleting a large sub tree of entities, you can improve performance if you first exclude
planning units for the sub tree (by excluding the root member) for all scenarios and versions.
Note: Each data value is identified by a set of member values and a plan type Deleting Note: Each data value is identified by a set of member values and a plan type. Deleting
members or clearing the plan type results in data loss when refreshing applications. Deleting
entity members deletes all planning units (including data) associated with them.
To delete members:
2. On the Dimensions tab, select a dimension. ,
3. Select a member to delete.
4. Click Delete .
5. At the confirmation prompt, click Yes.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Finding Members
Enter search
text.
If you need to find a member quickly, you can search for it. You can find members by entering
the name or the alias in the search box. You can search by name, alias, or both name and
alias. You can enter a partial name for which to search.
To find members:
3. Select a member.
4 In Search select an option Name Alias or Both and enter the text by which to 4. In Search, select an optionName, Alias, or Bothand enter the text by which to
search.
5. Click an option Search Up , or Search Down .

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Sorting Members
You can sort members in your application. Sorting members affects the Essbase outline. You
can sort either the descendants or the children of the selected member in either ascending or
descending order. The next time you create or refresh the database, the Essbase outline is
generated with members in the order that is displayed.
To sort members:
3. Select a member. 3. Select a member.
4. In Sort, select an option: Descendants, or Children.
5. Click an option Sort Ascending , or Sort Descending .
You can use the Planning Sort Member utility to sort members. SortMember.cmd is similar to
sorting on the Dimensions tab in Planning. You can sort Entity, Account, Scenario, Versions,
and user-defined custom dimensions. You cannot sort Period, Year, or Currency members.
The utility is useful for sorting members after loading members into Planning. The y g g g
SortMember.cmd utility uses a command line interface. Only administrators can run it.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

You launch the SortMember.cmd utility from the planning1 directory on the server where
Planning is installed. Enter this syntax:
SortMember [-f:passwordFile] servername username application member
children|descendants ascend|descend: | |
Parameter Description
[-f:passwordFile] Optional: If an encrypted password file is set up, use as the
first parameter in the command line to read the password from
the full file path and name specified in passwordFile.
servername The server name where the Planning application resides
username The name of the Planning administrator
application The name of the Planning application containing the
dimension members to sort dimension members to sort
member The parent member whose children or descendants to sort
children|descendants Whether to sort by children or descendants. Sorting by
children affects only members in the level immediately below
the specified member; sorting by descendants affects all
d d t f th ifi d b
Example:
descendants of the specified member.
ascend|descend Whether to sort by ascending or descending order
SortMember localhost admin Hyplan Worldwide descendants ascend

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that you can perform when setting up
a. Assign access permissions to members.
b Create smart lists b. Create smart lists.
c. Create dimensions.
d. Modify member properties.
Answer: a, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Inheritance allows high-level members to share their property
values with lower-level members in a dimension hierarchy.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that you can perform when modifying
a. Reorder children within a parent.
b Sort members to the order in which you entered them b. Sort members to the order in which you entered them.
c. Delete members even if they are used on forms.
d. Rename members.
Answer: a, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
In this lesson, you should have learned how to:
Manage and organize dimensions
Sort members

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Accessing Dimension Editor
Reviewing Hyplan Dimensions and Dimension
Associations Associations
Reviewing and Applying Performance Settings
Refreshing Essbase Databases

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

S tti U th Ali C Setting Up the Alias, Currency,
Year, and Period Dimensions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Create alias tables
Define currency preferences
Customize time periods Customize time periods

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Aliases
Create up to 10 alias tables for alternate information.
Enter aliases for dimensions and members in the
dimension hierarchy.
Account Name Account Alias (Default) Account Alias (German)
Gross Profit Total Gross Profit Bruttogewinn
Net Sales Total Net Sales Nettoumsatz
5100 Salary Expense Gehaltskosten
5120 Commission Expense Provisionskosten
5130 Advertising Expense Werbekosten 5130 Advertising Expense Werbekosten
To improve outline, form, and report readability, you can assign alternative names, called aliases,
to dimensions and members. You can assign up to 10 aliases, including the default alias, for each
dimension and member.
Note the following points about alias tables:
When you create an application, Planning creates an empty default alias table in the
application. If you do not create other alias tables, all aliases are stored in this default table.
You cannot delete the default alias table.
Administrators can select a default alias table for the application.
When you add or change aliases or alias tables, you must refresh the application. Changes
are not in effect until the database is updated.
You can use only alias tables created in Planning. Alias tables created outside Planning are
deleted during application refresh.
Planners can set preferences for which alias table to use for displaying dimension and
member names.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To create alias tables:
1. Select Administration, then Manage, and then Alias Tables.
The Alias Tables page is displayed.
2 Click Actions and select Add 2. Click Actions, and select Add.
The Add Alias Table dialog box is displayed.
3. Enter the name for the alias table, and click OK.
To set up aliases for members:
Th Di i i di l d The Dimensions page is displayed.
3. Select a member in the hierarchy.
4. Click Action, and select Edit.
The Member Properties tab is displayed.
5. In the Alias Table drop-down list, select the alias table.
6. In the Alias text box, enter an alias value, and click Save.
To select the applications default alias table:
1. Select Administration, then Application, and then Settings.
2. Select the Current Application Defaults tab.
3. In the Alias Table drop-down list, select the alias table name, and click Save.
To select the planners default alias table:
1. While logged on to the application as a planner, select File, and then Preferences.
The Preferences dialog box is displayed.
2. Click Planning, and select the Application Settings tab.
3 Perform one of the following actions: 3. Perform one of the following actions:
- For the Alias Setting option, select Use Application Default to select the alias table
that is defined as the default alias table for the application.
- In the Alias Table drop-down list, select the alias table name.
4. Click Save, and then OK.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Adding Currencies
Example of adding
a standard currency
Currency
properties
You create members in the Currency dimension for each currency needed in your application.
To add currencies:
1 Select Administration then Manage and then Dimensions
2. On the Dimensions tab, select the Currency dimension.
3. Click Action, and select Add Currency.
The Currency tab is displayed.
4. In the Create Currency drop-down list, perform one of the following actions:
Select Select standard currencies and then in the Standard Currencies list select a - Select Select standard currencies, and then, in the Standard Currencies list, select a
currency.
- Select Create new currency, and then select or enter the code, description, symbol,
scale, precision, triangulation currency, alias table, and alias for the currency.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

5. Select or enter values for the following member properties:
- Reporting Currency
- Thousands Separator
- Decimal Separator - Decimal Separator
- Negative Sign
- Negative Color
- Data Storage
- Two Pass Calculation
- Data Type
6 Click Save 6. Click Save.
Number Formatting
You can set the number format for each currency. For example, for the European euro, you set the
dot as the thousands separator and the comma as the decimal separator to match the European
standard. You can also set the color of negative numbers.
S li Scaling
You can specify that data values are scaled when they are displayed in certain currencies. For
example, you set the scaling for the Japanese yen to thousands, and enter 10,000 as a value for
Japan. When you select the 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 that is called Planning supports currency conversion by triangulation through an interim currency that is called
the triangulation currency. For example, if you know the European euro exchange rates for U.S.
dollars and Swiss francs, you calculate the U.S. dollar and Swiss 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 refreshing the application so that the new exchange rates
are transferred and stored.
Note: You cannot select the default currency as a triangulation currency.
Reporting Currency
Planning supports currency conversion from local currencies to one or more reporting currencies.
The converted reporting currency values are stored as read-only for all users. The application
default currency is also the default reporting currency. When you add currencies, you specify
whether they can be used as reporting currencies.
For example your application contains the Japanese yen U S dollar and European euro and the For example, your application contains the Japanese yen, U.S. dollar, and European euro, and the
European euro is a reporting currency. When you create forms and reports, Japanese yen and
U.S. dollar values are converted to European euros.
You can load values directly into Essbase (from historical scenarios, for example) for reporting.
Note: Enable Reporting Currency only if necessary. It increases the size of the database and
adds complexity to the calculation scripts for currency conversion.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Customizing Time Periods
When creating an application, you can:
Add years
Create and modify summary time periods
Add or change aliases Add or change aliases
Add up to 100 calendar years and 500 time periods
After creating an application, you cannot:
Modify the start year
Reduce the number of years y
Change the calendar type
When creating applications, you add the Period and Year dimensions to represent time. You use
the Period dimension to view and change the yearly calendar rollup structure, and you specify
base time periods and distribution of weeks. You use the Year dimension to add years to the
calendar.
Base Time Periods
Base time periods are the bottom-level time periods in an application. Predefined options are
quarters or months. You can create a custom base time period, such as weeks or days.
You cannot skip or change the order of base time periods. You cannot extend the range beyond
the current fiscal year.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary Time Periods
In an application, summary time periods are the top-level time periods that base time periods roll
up to. You can customize summary time periods as follows:
Update the name Update the name.
Change the description.
Modify starting and ending periods.
Create summary time periods.
Add or change aliases.
When you create summary time periods, you must work from the top of the hierarchy to the
bottom Keep in mind the following requirements: bottom. Keep in mind the following requirements:
All base members must be the same number of levels from the root.
BegBalance and YearTotal are required members of Planning applications. The YearTotal
member is the summary time period that aggregates all quarters.
You can add up to 100 calendar years and 500 time periods to an application. Depending on the
number of time periods and years and whether your application uses multiple currencies, Oracle
recommends the following practical limits:
400 time periods per year and 27 years
360 time periods per year and 30 years
You can create alternate hierarchies, use shared descendants in the Period dimension, and set
data storage for all time periods to any valid data storage value. You can set the consolidation
operator for all scenarios, versions, and time periods (including BegBalance) to any valid
consolidation operator, for example, + (addition) instead of ~ (ignore).
After creating 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, but you cannot delete a year
after you add it.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Period and Year Dimensions
Periods
Years
The Year dimension contains a member for each year in the range of years for the application.
The members identify the fiscal year to which the data applies. During application setup, you
specify the first fiscal year and the number of fiscal years for the application, and you can create
an All Years parent member that includes all years. The All Years parent member enables you to
view the accumulated data across multiple years (for example, a projects total cost up to its end
date).
The Period dimension is populated with base and summary time periods and is tagged with the
Time property in Essbase. When used in combination with the Account dimension, a time
dimension has properties that enable you to control how data accumulates over time for an
account.
The slide shows an example of a Planning form, with year FY13 in the point of view, and quarters
and year total in the columns. The Essbase outline displays the years and time periods.
Note: For most applications, performance is improved if you set the data storage property to
Dynamic Calc for summary time periods in the Period dimension.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up DTS Members
DTS members are added as dynamic calculation functions. In
Essbase, they are not included as members in the Period
dimension.
You use predefined Dynamic Time Series (DTS) members with members of the Period dimension
to create reports that show period-to-date data. DTS members provide the following eight levels of
reporting:
Year-to-date (Y-T-D)
History-to-date (H-T-D)
Season-to-date (S-T-D)
Quarter-to-date (Q-T-D)
Period-to-date (P-T-D)
Month-to-date (M-T-D) ( )
Week-to-date (W-T-D)
Day-to-date (D-T-D)
Your database outline and data determine the members that you can use. For example, if the
database contains hourly, daily, weekly, monthly, quarterly, and yearly data, you can report
D-T-D, W-T-D, M-T-D, Q-T-D, and Y-T-D information.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

You enable DTS for members and assign a generation number. For the example in the slide, to
calculate quarter-to-date values, you enable the Q-T-D member, assign generation 3 to the
member, and then use the Q-T-D DTS member to calculate monthly values up to the current
month in the quarter.
Because DTS members are used as dynamic calculation functions, you cannot load them from
ADS files.
To set up DTS members:
2. On the Dimensions tab, select the Period dimension.
3. Click Action, and select DTS.
The Dimensions page with Periods: Dynamic Time Series is displayed.
4. For each of the DTS members that you want to enable, select Enabled.
5. In the Generation drop-down list, select a generation number.
6. Optional: Set up an alias.
7. Click Save.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You must refresh the application when you add or change
aliases or alias tables.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the properties that are available for currency members.
a. Description
b. Reporting Currency
c Smart Lists c. Smart Lists
d. Symbol
Answer: a, b, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the statements that are true about the Period and Year
dimensions.
a. The Year dimension contains a member for each year in
the range of years for the application. g y pp
b. The Period dimension is populated with base time periods
for the application and is tagged with the Time property in
Essbase.
c. You can use DTS members to create reports that show
period-to-date data such as quarter-to-date expenses period to date data, such as quarter to date expenses.
Answer: a, b, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Create alias tables
Define currency preferences
Customize time periods Customize time periods

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Aliases
Setting Up Currencies
Setting Up Periods Setting Up Periods
Setting Up Years
Updating the Essbase Database

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

S tti U S i d V i Setting Up Scenarios and Versions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Describe scenarios and versions
Create scenarios and versions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Scenarios and Versions
With scenarios and versions, you can:
Locate the budget process in the review cycle
Perform what-if analysis by comparing scenarios and
versions versions
Actual versus budget comparisons
Version comparisons
Scenarios are required for successful deployment of Planning applications. You create the
Scenario and Version dimensions to set up individual plans for review and approval. The scenario
and version combinations contain data for the accounts and other dimensions of each entity.
Scenario describes the type of data in a plan, such as budget, actual, or forecast, as well as the
plans time span. Version describes the possible outcomes within the context of a scenario of
data. For example, if the scenario is Budget, some of its versions could be Draft 1, Draft 2, and
Final.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Scenarios
Time period
properties
Scenarios enable you to perform the following tasks:
Apply planning methods.
Associate scenarios with time periods and exchange rates
Associate scenarios with time periods and exchange rates.
Create forecasts and budgets.
Enter data into scenarios.
Assign user access rights by scenario.
Report by scenario.
Compare and analyze different scenarios.
By creating scenarios you can group your data into separate plans with their own review cycles By creating scenarios, you can group your data into separate plans with their own review cycles.
Scenarios can also cover different time spans. For example, your organization creates one-year
and three-year revenue plans that are prepared by different users and follow different review
paths. For this purpose, you create two scenarios, Current Year Revenue and 3Year Forecast.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To create scenarios:
2 On the Dimensions tab select Scenario 2. On the Dimensions tab, select Scenario.
4. Click Action, and then Add Child or Add Sibling.
5. Set up the member properties, and click Save.
P t Ti P i d Property: Time Periods
Assign each scenario a range of years and time periods. The range of time periods has the
following effects in your application:
When you access a form, you can enter data only for the years and time periods within the
range. Years and time periods outside the range are displayed as read-only.
When you generate a currency conversion calculation script, the calculation script converts
currencies for the range of time periods that are valid for the selected scenarios. currencies for the range of time periods that are valid for the selected scenarios.
You modify the time range of scenarios as needed to allow for continuous planning. For example,
a scenario named 3Year Forecast has 2012 as the start year and 2014 as the end year. At the
beginning of the 2013 fiscal year, you change the start year to 2013 and the end year to 2015, so
that you can enter forecast data for 2015.
Property: Include BegBal as Time Period
Select Include BegBal as Time Period if you want to include the BegBalance time period in this
scenario for currency conversion.
Property: Enabled for Process Management
Select Enabled for Process Management to include this scenario in approvals. The scenario is
displayed in the Scenario drop-down list on the Manage Approvals. You can manage planning
units that contain this scenario member.
Property: Exchange Rate Table
If your multiple-currency application uses currency conversion, you assign an exchange rate table
to the scenario to model the effect of different assumptions on your business.
You must consider currency reporting needs when deciding which scenarios to create. For
example, you create scenarios associated with different exchange rate tables to eliminate the
effects of currency rate fluctuations from variances (such as Budget at Actual Rate).
Property: Plan Type
By default, all scenarios are available for all plan types that are enabled for the application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Access Rights
After creating applications, you assign Read, Write, or None access permission to Scenario
dimension members to determine whether users or groups can view or modify data.
Security is not associated with members of the Year and Period dimensions However you can Security is not associated with members of the Year and Period dimensions. However, you can
use the scenario start and end year and period properties to lock out time periods for data entry.
For example, set the properties so that users can enter data only in the current year. All time
periods that fall outside the start and end range are displayed as read-only.
You can also set the Start and End Period properties to allow a mix of actual and budget data in
the same scenario for forecasting purposes. For example, if you roll out your application in April,
the Forecast scenario contains actual data for January through March and forecast data for April
through December If you set the start period to April users can input forecast data for April through December. If you set the start period to April, users can input forecast data for April
through December, but they cannot edit the actual data in January, February, or March. At the end
of April, you load actual data for April and change the start period to May, so that you can create a
rolling forecast.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Versions
Type: Standard Type: Standard
Bottom Up or
Standard Target
Versions are required for successful deployment of Planning applications. Use the Version
dimension for the following purposes:
Allow multiple iterations of a plan, such as preliminary and final.
p p , p y
Model possible outcomes based on more optimistic or less optimistic assumptions, such as
Best Case and Worst Case.
Manage dissemination of plan data, such as Internal and External.
Facilitate target setting.
Permissions are independent of scenarios, so you could give users read-only access to the Final
version and 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. 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, the versions are displayed as read-only parents on forms.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To create versions:
2 On the Dimensions tab select Version 2. On the Dimensions tab, select Version.
4. Click Action, and then Add Child or Add Sibling.
Note: You can select Enabled for Process Management only for bottom-up versions.
T P t St d d B tt U Type Property: Standard Bottom Up
For standard bottom-up versions, enter data in 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 based on their consolidation operators.
For example, if you enter data for Northern Europe and Southern Europe, the total for Europe is
aggregated after the database is calculated.
Type Property: Standard Target Type Property: Standard Target
Standard target versions enable you to enter data for members at any level in the hierarchy, and
business rules enable you to distribute values from parent members to their descendants. For
example, you enter the target for Total Expenses into the Europe member and use a business rule
to distribute the target values to Northern and Southern Europe.
Target versions enable you to set high-level targets for your plan. Planners working with bottom-
up versions can reference the targets when they enter plan data. For example, the Total Product
Sales member has children named Retail, Wholesale, and Distributors. To set Californias target
for product sales, the budget manager enters 10,000 into Total Product Sales for the California
entity.
The functionality available with target versions is for top-down budgeting. You must set target
members to Store (Dynamic Calc overrides data input with the sum of the children).

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the dimension that you use to lock out time periods for
data entry.
a. Period
b Scenario b. Scenario
c. Version
d. Year
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You can use the Version dimension for which of the following
purposes?
a. Allow for multiple iterations of a plan.
b Model possible outcomes based on more optimistic or less b. Model possible outcomes based on more optimistic or less
optimistic assumptions.
c. Facilitate target setting.
Answer: a, b, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe scenarios and versions
Create scenarios and versions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Scenarios
Setting Up Versions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

L di M t d t Loading Metadata

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Identify metadata load options
Load metadata with the Outline Load utility
Describe the ERP Integrator metadata load process Describe the ERP Integrator metadata load process
Migrate application metadata with Lifecycle Management

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Metadata Load Options
Metadata load options:
Outline Load utility
ERP Integrator
Lifecycle Management Lifecycle Management
Data Integrator Adapter for Planning
DIM Adapter for Planning
You can load metadata into Planning Administration applications with the following options:
ERP Integrator
ERP Integrator
Oracle Hyperion Enterprise Performance Management System Lifecycle Management
(Lifecycle Management)
Oracle Data Integrator Adapter for Planning
Oracle Hyperion Data Integration Management Adapter for Planning (DIM Adapter for
Planning)
For information about DIM Adapter for Planning, see the Oracle Hyperion Data Integration p g, yp g
Management Adapter for Planning Online Help.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Loading Metadata with the Outline Load Utility
1. Create a load file for each
dimension that you want to load.
2. Test the load file.
3. Load records with the
4. Repeat steps 1
through 3 for each
dimension.
Outline Load utility.
5. Refresh the database.
You can use the Outline Load utility to load metadata for all dimensions, attributes, UDAs,
exchange rates, smart lists, and planning unit hierarchies.
You repeat the metadata load for each dimension that you want to load.
p y

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Metadata Load Files
Header record
Sample metadata load file for the Entity dimension
Sample metadata load file for a smart list
The comma-separated value (CSV) load file must contain a header record with column headers
for the dimension name and the member properties for the subsequent metadata records. The
column headers are case-sensitive and can appear in any order. Parent members in the load file
must exist in the application or must be loaded before their children.
The first example in the slide shows a section of a load file for the Entity dimension. In the header
record, the first column header is the dimension name, Entity, and other column headers refer to
member properties (Parent, Alias: Default, Data Storage, Base Currency, and Plan Type). The
required member properties are different for each dimension.
The next lines in the load file contain metadata records. Each metadata record contains a list of
property values that correspond to the column headers When members are added unspecified property values that correspond to the column headers. When members are added, unspecified
properties assume the default value or they inherit the parent members property, as appropriate.
If a member exists and no property value is specified, the property is left as is.
The second example in the slide shows a load file for a smart list. The second line in the file loads
the smart list, Service_Level (note that Operation is set to addsmartlist). The subsequent lines in
the file load the smart list entries (note that Operation is set to addentry).

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Common Member Properties
Some member properties that are common to several
dimensions:
Parent
Alias: Default Alias: Default
Data Storage
Description
Data Type
Plan Type (<plan-type-name>)
Aggregation (<plan-type-name>)
Operation
Each metadata record in the load file contains a comma-separated list of member property values
that correspond to the header record entries. The following table describes some of the member
properties that are common to several dimensions:
Property Description
Parent The parent of the member being loaded to create the dimension hierarchy.
When you load a member and specify a parent member that is different
from the parent member in the application, the member is updated with
the new parent value. the new parent value.
Alias: Default The alias defined for the member in the Default alias table. If you do not
specify a value, the alias is not changed in the application. If you specify
<none> as the value, the alias in the application is deleted.
Data Storage The storage attribute for the member being loaded. Valid values: Store,
Dynamic Calc, Dynamic Calc and Store, Shared, Never Share, and Label
Only
Only.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Description Description for the member being loaded. If you do not enter
a value new members are loaded without descriptions and a value, new members are loaded without descriptions, and
descriptions of existing members are unchanged. If you use
<none> as the value, any existing description for that
member is deleted.
Data Type The data storage value. Valid values: Currency,
Non-currency, Percentage, Smart List, Date, Text, and
Unspecified.
Play Type (Plan1, Plan2,
Plan3)
A Boolean value that indicates whether the member being
loaded is used in the specified plan. Valid values: 0 for False,
or any other number for True. The default is True.
Aggregation (Plan1, Plan2,
Plan3)
The aggregation option for the member being loaded, as
related to the specified plan. This is available only if the
application is valid for this plan type. Valid values are + pp p yp
(addition), - (subtraction), * (multiplication), / (division, %
(percent), ~ (ignore during consolidation), Never (do not
aggregate).
Operation Operation to perform when loading the member. Valid values:
Update, Delete Level 0, Delete Idescendants, and Delete
Descendants.
U ti h d l ti b thi d l t th
To review the complete set of common member properties and the properties specific for certain
dimensions, see the Oracle Hyperion Planning Administrators Guide Release 11.1.2.2.
Use caution when deleting members; this deletes the
member, its data, and any associated planning units.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Testing and Loading Metadata Files
The default location for the Outline Load utility is
oracle/middleware/user_projects/epmsystem1/
Planning/planning1.
Sample command to verify the result of loading entities
OutlineLoad /A:Plan /U:admin /M /N
/I:d:/entity1.csv /D:Entity
/L:d:entity1.log /X:d:/entity1.exc
p y g
into the Plan application:
/ y g / / y
The Outline Load utility loads one record at a time. If a record fails to load, a message is written to
the exception file, and the load process resumes with the next record. You can test load files to
verify that the files parse without any errors. Running the Outline Load utility with the /N parameter
does not load the metadata, but ensures that the load files parse successfully.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The following table describes some of the command parameters for the Outline Load utility:
/A:application name Application name to which you are loading the metadata /A:application name Application name to which you are loading the metadata
/U:user name Username with which to log on to the application
/M When you load files, the properties that you can load for each
dimension are displayed in the log file. Use /-M if you do not
want to display this information (default). The parameter does
not affect the actual metadata load.
/N Dry run that is performed to test the load file without loading
the metadata
/I:input file name Name of the load file that contains the header record and
metadata records in CSV format. You must also specify a
load dimension (/D).
/D:dimension name Dimension to be loaded /D:dimension name Dimension to be loaded
/DU: dimension name User-defined dimension to be loaded. A dimension with this
name is created if it does not exist.
/L:log file name Name of the log file that contains status and informational
messages
/X:exception file name Name of the file that contains exceptions which occur during p p g
the metadata load
/S:server name Planning server name on which the application resides. If it is
not specified, localhost is used.
/C Cube refresh that is performed after the metadata load
/DS:HSP_SMARTLISTS Smart list dimension to be loaded with the smart list
To review the complete set of command parameters, see the Oracle Hyperion Planning
Administrators Guide, Release 11.1.2.2.
To test and load metadata files with the Outline Load utility:
dimension entries
/? Displayed usage text
1. Select Start, then Programs, then Accessories, and then Command Prompt.
The command prompt window is displayed.
2. Enter CD
x:/oracle/Middleware/user_projects/epmsystem1/Planning/planning1 to
navigate to the default folder that contains the Outline Load utility.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

3. Enter the following case-sensitive command syntax to test the load file:
OutlineLoad /A:applicationName /U:userName /I:inputFileName
/D:loadDimensionName /L:logFileName /N [/S:serverName] [/M]
/X:exceptionFileName
Note: Running the utility with /N does not load metadata, but it verifies that the load file
is parsed successfully.
4. Open the log file, and verify that no error messages were generated.
5. Enter the following case-sensitive command syntax to load metadata:
/D:loadDimensionName /L:logFileName [/S:serverName] [/M] [/C]
/X ti Fil N /X:exceptionFileName
6. Review the exception and log files, and perform one of the following actions:
- If no errors are reported, proceed to step 7.
- If errors are reported, fix the errors, and repeat steps 5 and 6.
7. Refresh the database to update the Essbase database:
a. Select Administration, then Application, and then Refresh Database.
b. Select Database, and click Refresh.
c. In the Refresh Database dialog box, click Refresh.
d. When the status is Succeeded, click Finish.
You can now access the imported metadata in the application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

ERP Integrator Load Process
EPM
Applications
Planning
Smart
View
Oracle EPM System
E-Business
Suite
Generic Data
Sources
ODBC
Files
Excel
FDM
Classic FDM
E-Business
Suite
Data Sources
PeopleSoft
Financials and HCM
EBS GL
FDM ERPI
EPM
Financial
Reports
Financial
Management
ARM
Essbase
Fusion GL
Files
EPM
Architect
SAP FI / CO
JDE EnterpriseOne
Open Interface Table
Metadata and Data Load
Data Load
Drill Through
Write Back
ERP Integrator architecture for loading metadata and data:
As a module of FDM, ERP Integrator is the key application for integrating ERP systems with
EPM applications. ERP Integrator fits within the EPM System architecture and is accessed
pp g y
through EPM Workspace, which uses Shared Services to authenticate users. The key to its
integration is its underlying engine, Oracle Data Integrator.
ERP Integrator sits on top of Oracle Data Integrator and enables the movement of data and
metadata into Oracle Hyperion EPM applications.
If you use FDM and ERP Integrator together:
- Metadata is loaded through the Planning application administration application or
through Performance Management Architect through Performance Management Architect.
- Data is loaded in FDM through ERP Integrator, and then the flat files in FDM push the
data to the EPM target application.
For additional information about ERP Integrator, see the Oracle Hyperion Financial Data Quality
Management ERP Integration Adapter for Oracle Applications Administrators Guide Release
11.1.2.2, the Oracle Hyperion Financial Data Quality Management 11.1.2 Administration course,
and the FDM ERP Integrator 11.1.1.3 Module Overview tutorial.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Lifecycle Management
After successfully creating an application in an environment,
you can use Lifecycle Management to migrate applications,
artifacts, and users across product environments and operating
systems.
Development Test Production
After successfully creating an application in an environment, you can use Lifecycle Management
to migrate applications, artifacts, and users across product environments and operating systems.
Migration is the process of copying all or part of an application from one environment to another.
For example, you can migrate an application from development to test or from test to production.
With Lifecycle Management, you can perform the following tasks:
View applications and directories and search for artifacts.
Migrate to and from the file system.
View selected artifacts.
Import and export individual artifacts for quick changes.
Audit migrations and view the status of migrations.
Migrate complete application suites by selecting all the related artifacts at once and
migrating them.
Migrate multiple applications with a single migration definition.
Create migration definitions to run migrations in Shared Services Console or in Lifecycle
Management.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

You must be provisioned with the following roles to use Lifecycle Management with Planning:
Administrator (for Planning)
LCM Administrator
Application Creator (only for Performance Management Architect applications) Application Creator (only for Performance Management Architect applications)
Note: LCM Designer, an additional Shared Services role, enables users to define migrations and
perform export operations, but not perform import operations.
Artifacts are individual application or repository items, such as forms, dimensions, and members,
access permissions, rules files, documents, and financial reports. Application and repository
artifacts are organized into categories by product.
Note: For a complete list of artifacts, see the Oracle Enterprise Performance Management System p , p g y
Lifecycle Management Guide, Release 11.1.2.2.
Planning Artifacts:
You use Lifecycle Management to migrate the following types of Planning artifacts:
Configuration (application settings, data load settings, user preferences, and user variables)
Global artifacts (such as business rules, composite forms, smart lists, substitution variables,
task lists, and decision packages) p g )
Plan types
Relational data (account annotations, cell texts, planning units, supporting detail, text values)
Security (access permissions for groups and users)
Foundation Services Artifacts:
The Foundation category includes the following artifacts:
Calculation Manager (formulas rules scripts and templates) Calculation Manager (formulas, rules, scripts, and templates)
Deployment Metadata
EPM Architect (dimensions and members)
Shared Services (native directory groups, users, and roles, and task flows)
Reporting and Analysis Artifacts:
The Reporting and Analysis category contains the reports for Planning applications.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Migrating Applications and Artifacts
E t i t
Launch Shared
Services Console.
Select the artifacts
for migration.
Export or import
artifacts to or from
the file system.
View the migration
status report.
The following steps summarize the process for migrating applications and artifacts:
1. Start Shared Services Console.
2 Select the source artifacts for migration
2. Select the source artifacts for migration.
3. Export artifacts to the file system or import artifacts from the file system.
4. View the migration status report.
You can save a migration definition to a file for reuse, and specify multiple tasks to migrate
multiple applications together. Migration definition files are saved in XML format. You can also use
the migration XML file with the command-line utility to perform batch processing.
When you perform a migration in Shared Services Console, the system creates migration When you perform a migration in Shared Services Console, the system creates migration
definition files (in XML format) in the File System folder. The migration definition files contain
information about the migration (source, destination, and artifacts for migration). You can modify
the migration definition files to define migrations. For example, you can specify multiple tasks to
migrate multiple applications together. You can also create the migration definition files from the
beginning by using sample files that are provided. You can use migration definition files to run
migrations in Shared Services Console or in Lifecycle Management Utility.
For more information about migration definition files the provided sample files and Planning
For more information about migration definition files, the provided sample files, and Planning
examples, see the Oracle Enterprise Performance Management System Lifecycle Management
Guide, Release 11.1.2.2.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Migration Guidelines
Consider the following cross-product artifact dependencies
when migrating Planning Administration applications and
artifacts to another environment:
Shared Services Native Directory (users, groups, and y ( , g p ,
provisioning)
Calculation Manager
Essbase (rule files, calculation scripts, and substitution
variables)
Reporting and Analysis (Financial Reporting) Reporting and Analysis (Financial Reporting)
There are cross-product artifact dependencies when you migrate Planning applications and
artifacts to another environment. You must migrate artifacts from other products along with the
Planning-specific artifacts.
Planning Administration applications require the following cross-product artifacts:
Shared Services Native Directory (users, groups, and provisioning)
Calculation Manager
Essbase (rule files, calculation scripts, and substitution variables)
Reporting and Analysis (Financial Reporting and Web Analysis)
For information about cross-product artifact dependencies for Performance Management Architect For information about cross product artifact dependencies for Performance Management Architect
applications, see the Oracle Enterprise Performance Management System Lifecycle Management
Guide Release 11.1.2.2.
The following are considerations for Planning artifact migrations:
The source and destination applications must have the same settings for plan type, calendar,
and single or multiple currencies.
If the Planning application does not exist in the target environment, Lifecycle Management
creates an application shell.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

During import, Planning artifacts replace any existing artifacts in the destination environment.
There is no option to merge or delete artifacts during an import.
Some Planning artifacts have dependencies. (For example, forms have dimension
dependencies.) Instead of migrating only the dimension members required for a form,
Lifecycle Management migrates the entire dimension. You must manually select any
necessary dependencies.
Essbase must be in Shared Services mode to use Lifecycle Management.
Essbase artifacts, such as calculation scripts and substitution variables, are displayed under
the Planning application node.
Planning data migrations are not supported in Lifecycle Management.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Migrating Applications
and Artifacts to a File System and Artifacts to a File System
You can use Shared Services Console to migrate applications and artifacts to a file system. The
file system location is on the Shared Services web application server computer.
To migrate applications and artifacts to a file system:
g pp y
1. Log on to Shared Services Console.
2. Expand Application Groups, and then a group name, and select an application.
3. Select the application artifacts, and click Export.
The Export to Filesystem dialog box is displayed.
4. In the File System Folder box, enter the folder name. The maximum length for the folder
name is 255 characters.
The folder is created in the following location:
/Oracle/Middleware/user_projects/epmsystem1/import_export.
5. Click Export.
The Migration Status Report page is displayed.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Migrating Artifacts from a
File System to an Application File System to an Application
You can use Lifecycle Management to migrate artifacts from a
file system to an application.
After migrating applications and artifacts from the source application to the file system, you can
migrate the file system artifacts to a destination application.
To migrate artifacts from a file system to an application:
g y pp
1. Back up the destination environment.
Note: Many products provide their own data backup and recovery solutions. These solutions
are documented in the Oracle Enterprise Performance Management System Backup and
Recovery Guide, Release 11.1.2.2.
2. Copy or transfer the exported files from the source file system to the destination file system.
The exported artifact folders are saved in the following location:
Oracle/Middleware/user_projects/epmsystem1/import_export. You should
copy the artifact file system folders to the same directory in the destination environment.
3. In the destination environment, log on to Shared Services Console.
4. Expand File System.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

5. Expand the file system folder that you created in the source environment, and select the
artifact name.
The artifacts in the file system folder are displayed on the Artifact List tab.
6. Select the artifacts that you want to migrate. y g
7. Click Import.
The Import to Application dialog box is displayed.
8. In the Applications drop-down list, select the application name, and click Import.
The Migration Status Report page is displayed.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Displaying Migration Status Reports
When you execute a migration, you can immediately view its status in the migration status report.
You also can review migrations at a later time.
To display migration status reports:
p y g p
1. In Shared Services Console, select Administration, and then Migration Status Report.
2. Optional: Click Refresh to update the report status.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the metadata that you can load with the Outline Load
utility.
a. Attributes
b Dimensions b. Dimensions
c. Planning unit hierarchies
d. Smart lists
Answer: a, b, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
With which roles must you be provisioned to use Lifecycle
Management with Planning applications?
a. Administrator
b Application Creator b. Application Creator
c. LCM Administrator
d. Provisioning Administrator
Answer: a, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Direct application-to-application migrations can occur between
any Hyperion applications that are registered with Shared
Services.
a. True
b. False
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Identify metadata load options
Load metadata with Outline Load Utility
Describe the ERP Integrator metadata load process Describe the ERP Integrator metadata load process
Migrate application metadata with Lifecycle Management

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Reviewing Outline Load Files
Importing Periods, Scenarios, and Versions
Reviewing Imported Periods Scenarios and Versions Reviewing Imported Periods, Scenarios, and Versions
Updating the Essbase Databases

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up the Entity and Setting Up the Entity and
Account Dimensions

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Describe entities and accounts
Add and delete entities
Explain account member properties Explain account member properties
Add accounts
Describe account aggregation

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Entities: Overview
Entities enable you to model the flow of budget information
through your organization.
You can create an entity for each group or responsibility
center that submits a plan for approval. p pp
You can load or manually add Entity dimension members to an application. You use parent-child
relationships among entities to mirror your budget review structure, and you define the types of
units for your organization, such as geographical regions, departments, or divisions.
For example, your organizations regional centers prepare budgets for country headquarters that,
in turn, prepare a plan for corporate headquarters. To match this structure, you create members
for the regions, countries, and headquarters, and you set up the regions as children of the country
members, and the country members as children of the headquarters member.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Entity Members and Plan Types
When you define an entity member, you assign plan types.
If you do not assign a plan type to a parent, its descendants
do not have access to the plan type.
Revenue Balsheet Incstmt
Plan types Form
Eastern US
NY
FL
Assigned
A plan type is a classification mechanism for data.
Your organization may require different entity members to prepare different plans. When you
define entity members, you specify the plan types for which they are valid. Because forms are
y , y p y p yp y
associated with plan types, they enable you to control the entity members that can enter data for
each plan type.
For example, all entity members in your organization may submit expense plans, but entity
members that are cost centers do not submit revenue plans. The example in the slide shows that
you assign the Eastern U.S. cost center to the Incstmt plan type but not to the Balsheet or
Revenue plan types. Eastern U.S. cannot be selected on forms that were created for the Balsheet
or Revenue plan types or Revenue plan types.
In another scenario, your organization may want to separate entities into different plan types, such
as a Corporate plan type and a Legal plan type. You can store sensitive information that is specific
to law suits, patents, and so on, in detail accounts in the Legal plan type. You can then report on
summary budget information about pending or ongoing lawsuits or patent royalties.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

When you select a plan type for an entity member, you specify how the data values 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 new parents plan types.
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.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Currency Values for Entities
The default currency is the currency that you specify when you
create the application.
New York London
Tokyo
If you set up your application for multiple currencies, you specify a currency for each entity. The
default currency for all entities is the currency that you specify when you create your application. If
you do not define a currency, the applications default currency is used.
The currency property value identifies the local currency in which data is entered for the entity.
When you run a currency conversion calculation script or the Convert Currencies business rule,
Planning uses the exchange rates entered for that entitys currency to convert the local currency to
the reporting currency.
For example, you specify yen as the currency for the Japan entity, and the U.S. dollar for the
United States entity. You view a form that includes values for the Japan entity, but the display
currency is set to U S dollars Planning uses the rates in the yen exchange rates table to convert currency is set to U.S. dollars. Planning uses the rates in the yen exchange rates table to convert
the values to U.S. dollars.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Adding Entities
Add Sibling
Entity dimension
member properties
You add entities and set their properties on the Dimensions page.
To add entities:
1 Select Administration then Manage and then Dimensions
The Dimensions tab is displayed on the Dimensions page.
2. In the Dimension drop-down list, select Entity.
4. Click Action, and select Add Child or Add Sibling.
5 Set up the member properties and click Save 5. Set up the member properties, and click Save.
Note: After adding entities, refresh the database in Planning to update the Essbase outline with
members in the order that is displayed on the Dimensions page.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Deleting Entities
Delete the entity from the dimension on the Dimensions
page.
Update the Essbase databases.
Update and validate impacted forms business rules Update and validate impacted forms, business rules,
reports, and adapter processes.
You must delete the entity member throughout your Planning application before deleting it on the
Dimensions page. For example, if the entity is used in a form, you must delete it from the form
before deleting it on the Dimensions page.
When you delete entity members, the data and all associated planning units are also deleted.
To delete entities:
2. In the dimensions drop-down list, select Entity.
3. Select a member in the hierarchy. 3. Select a member in the hierarchy.
4. Click Action, and select Delete.
5. At the confirmation prompt, click Yes.
Note: After deleting entities, refresh the database in Planning to update the Essbase outline.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Accounts: Overview
Assign plan types to accounts.
Use aggregation properties to define calculations in the
account hierarchy.
Profit
Balsheet Incstmt
Detail expense accounts

Profit
Total Revenue
Total Expenses
Source plan Form
The Account dimension categorizes data in an account structure (hierarchy). When you define an
account member, you assign a plan type.
If you associate an account with multiple plan types, such as Incstmt and Revenue, you
y p p yp , , y
designate a source plan type to store the account value. For example, if Total Product Sales
is associated with both the Incstmt and Revenue plan types, and Incstmt is the source plan
type, the displayed value for Total Product Sales for the Revenue plan type is the same
value entered for the Incstmt plan type. The value is stored in the Incstmt plan type and
cross-referenced to the Revenue plan type.
If you promote or demote a member, and the new parent is associated with different plan
types, the members assignment remains with the plan types that it has in common with the yp , g p yp
new parent.
You can also define calculations in the hierarchies so that, for example, operating expense
accounts are automatically aggregated to Total Expenses, and Total Expenses is subtracted from
Total Revenue.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Account Types
Account
Type
Variance
Reporting
Property
Time
Balance
Property
Skip
Property
Exchange
Rate Type
Property
Data Type
Property
Expense Expense Flow N/A Average Currency
Revenue Nonexpense Flow N/A Average Currency
Asset
Nonexpense
Balance None Ending Currency
Liability
Nonexpense
Equity
Nonexpense
Saved
Assumption
User-defined
User-defined N/A No Rate Noncurrency
Account types define how an accounts value flows over time. They also determine the sign
behavior for expense reporting with Essbase member formulas.
With one exception, all account types have predefined properties for expense reporting and time
p , yp p p p p p g
balance behavior. The exception is the Saved Assumption account type, which is user-defined.
The table in the slide shows the default properties for variance reporting, time balance, skip,
exchange rate type, and data type. You can override the defaults, if required.
Note: For accounts, if Data Type is set to any value except Currency, you must set the Exchange
Rate Type to No Rate.
Variance Reporting Properties
An accounts variance reporting property determines if an account is tagged as an expense in
Essbase member formulas or Financial Reporting variance functions.
The following are the expense reporting properties:
Expense The actual amount is subtracted from the budgeted amount to determine the
variance.
Nonexpense The budgeted amount is subtracted from the actual amount to determine the
variance.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Time Balance Properties
Flow and Balance examples:
Revenue
Asset
50 75 50 175
100 150 75 75
Jan Feb Mar
Total Revenues
Cash on Hand
Quarter 1
Asset 100 150 75 75 Cash on Hand
Time balance specifies how account data flows over time. Use the properties described in the
following table:
Fill Uses the parent time period value for all descendants
Flow Uses an aggregate of all data values in a summary time period as the total
for the period
First Uses the beginning data value in a summary time period as the total for
the period
Balance Uses the ending value in a summary time period as the total for the period
Average Uses the average of all childrens data values in a summary time period as
the total for the period

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Weighted Average Uses a weighted daily average based on the actual number of 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
Calculation Properties for Missing Values
If you set the time balance property to First, Balance, or Average, you must specify how Planning
handles zeros and missing values when it calculates the parent value. Use the properties listed in
the following table:
None Zeros and missing values are considered
Missing Missing values are excluded
Note: When you set time balance to Flow, skip options are not available and default to None.
Zeroes Zero values are excluded
Missing And Zeroes Missing and zero values are excluded

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Saved Assumptions
Use saved assumptions to perform these tasks:
Centralize planning assumptions.
Identify key business drivers.
Ensure consistency across the application Ensure consistency across the application.
Define business rules that reference the saved assumptions:
Calculate office supplies by entity based on headcount.
Calculate facilities expense based on square footage per
location.
Saved assumptions enable you to centralize planning and maintain consistency in Planning. You
can also create business rules that reference the key business drivers as saved assumptions. For
example, you calculate office supplies by entity based on headcount or facilities expenses based
on the square footage of each location.
When you define a saved assumption account, you select variance reporting and time balance
properties. The following examples show how to use these properties with saved assumptions:
You make an assumption that actual headcount is less than budgeted headcount, and you
determine the expense by subtracting the actual amount from the budgeted amount.
You make an assumption about the square footage of an office, and you determine the
square footage for the time period by using a value for the end of the time period square footage for the time period by using a value for the end of the time period.
You make an assumption about the number of product units sold at the end of the time
period, and you determine the final value for the time period by aggregating the number of
units sold across a range of time periods.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Data Types and Exchange Rate Types
Currency
Average Ending Historical
Exchange rate types
Data types and exchange rate types determine how numeric values are stored and which
exchange rate to use to calculate the value.
Data types store and display values as currency or noncurrency numeric values; percentage
yp p y y y ; p g
values; smart lists, date, or text values.
For accounts whose data type is Currency, you select one of the following exchange rate types:
Average Valid for any time period; uses the average rate for the account
Ending Valid for any time period; uses the ending exchange rate for the account
Historical Valid for any time period; uses the historical exchange rate for the account
Depending on the cell intersections of the form data types can have conflicting results For Depending on the cell intersections of the form, data types can have conflicting results. For
example, you resolve the intersection of a percent data type and a currency data type based on
your definition of the order set.
The Evaluation Order specifies which data type prevails when a data intersection has conflicting
data types. You set a dimensions order by plan type to determine the precedence when multiple
data types intersect. Data types that are associated with the first dimension in the list take
precedence over data types that are associated with subsequent dimensions.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Adding Accounts
Add Child
Account dimension
member properties
You add accounts and set their properties on the Dimensions page.
When assigning plan types, you must set the plan type property for a parent member before you
set the plan type for its children. You cannot select a plan type for a child member if the plan type
p yp p yp p yp
is not valid for the parent.
To add accounts:
2. In the Dimension drop-down list, select Account.
4. Click Action, and select Add Child or Add Sibling.
Note: After adding accounts, refresh the database in Planning to update the Essbase outline with
members in the order that is displayed on the Dimensions page.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Aggregating Accounts
Aggregation order is determined by the order of members
in the outline.
Essbase calculates data in top-down order.
Parent
Member 1 (+) 10
Member 2 (+) 20
Member 3 (-) 25
Member 4 (*) 40
30
5
200
200
25
40
3.33
Member 5 (~) 50
Member 6 (/) 60
Member 7 (^) 70
3.33
~
60
Aggregation options
After creating the Essbase database outline, you should review the order of the dimensions and
members. For each plan type, data is aggregated based on the order of the dimensions and
members in the outline.
The default aggregation is addition. The order of calculation within each dimension depends on
the relationships between members in the database outline. Within each branch of a dimension,
level 0 values are calculated first, followed by their level 1 parent values. The calculation
continues in this way until all levels are calculated.
When you use addition and subtraction operators, the order of members in the outline is irrelevant.
However, when you use other operators, you must consider member order and its effect on the
aggregation When siblings have different operators Essbase calculates the data in top-down aggregation. When siblings have different operators, Essbase calculates the data in top down
order.
For the example in the slide, Essbase calculates the data as follows:
1. Member 1 through Member 4 calculate as ((Member 1 + Member 2 - Member 3) * (Member
4)) = ((10 + 20 - 25) * 40)) = 200.
2. Member 5 is ignored in the aggregation.
3. When the result of Member 1 through Member 4 is 200, Member 6 aggregates as g , gg g
(200/Member 6) = (200/60) = 3.33.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
If you do not assign a plan type to a parent entity, its
descendants do not have access to the plan type.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
If more than one plan type is assigned to an account, select the
plan type that you must designate.
a. Base plan type
b Source plan type b. Source plan type
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the time balance option that uses the ending value in a
summary time period as the total for the period.
a. Average
b First b. First
c. Flow
d. Balance
Answer: d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
The order of calculations within each dimension depends on
the relationships between members in the Essbase database
outline. Within each branch of a dimension, level-0 values are
calculated first.
a. True
b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe entities and accounts
Add and delete entities
Explain account member properties Explain account member properties
Add accounts
Describe account aggregation

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Practice 9-1
The practice covers the following topic: Reviewing Entity and
Account Load Files

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

C ti U D fi d El t Creating User-Defined Elements

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Create member formulas
Describe user-defined dimensions
Create attributes and assign attribute values Create attributes and assign attribute values
Add user-defined attributes
Create and manage smart lists

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Member Formulas
Member Formula tab
Edit the selected
member.
So far you have set up calculations between members by using aggregation options. These
aggregation calculations are built into the Essbase outline. However, performing calculations
through aggregation operations has the following limitations:
You can create calculations only between children of a common parent.
You must store the results of the calculation in the parent member.
You can use member formulas as an alternative method of calculation. Member formulas are
attached directly to dimension members. They go beyond aggregation logic by letting you
reference values in members anywhere in the outline, including other dimensions or databases.
Member formulas also provide a wider range of operators.
F th l i th lid t th f ll i b f l f P fit P t For the example in the slide, you create the following member formula for Profit Percent:
Profit Percent = Gross Profit % Net Sales;

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

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, user-defined attribute, and other items that
are allowed in Essbase formulas
Predefined formula expressions, including smart list values, that expand into a formula or
value upon a database refresh
To create member formulas:
The Dimensions page is displayed. The Dimensions page is displayed.
2. In the Dimension drop-down list, select a dimension.
5. Select the Member Formula tab.
6 Enter a formula 6. Enter a formula.
7. Click Validate to check the formula syntax.
8. If there are any errors, fix the formula, and repeat step 7.
9. Click Save.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

User-Defined Dimensions
User-defined dimensions require these items:
Unique values across databases
Plan types assigned at the dimension level
Customer
User-defined dimensions help you capture categories that your organization uses for budgets and
planning. For example, you add a dimension named Project so that you can budget operating
expenses on a project basis.
Consider the following guidelines:
Names must be unique and use proper naming conventions.
Names and aliases can have up to 80 characters.
Descriptions can have up to 255 characters.
You assign valid plan types at the dimension level, not at the member level. All members of
custom dimensions are valid for plan types that are assigned at the dimension level.
To assign security to user-defined dimensions, you must select the Apply Security option in
the dimension properties.
For additional information about creating dimensions, see the Setting Up Dimension Hierarchies
topic in the Managing Dimensions lesson.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Attribute Dimensions
Customer
Account
Executive
Company
Size
Base dimension Attributes
Doug Nichols
National Accounts
Ann Smith
Assad Akili
Your IT Source
ABC Company
Large
Small
Medium
oug c o s
Chris Jones
Software Company
Large
Attributes are characteristics of your data. For example, products can have attributes of color, size,
or flavor. You use attributes to view, aggregate, and report on data. For the example in the slide,
you define the attributes, Account Executive and Company Size, for the Customer dimension so
that you can assign the account executive attribute, Doug Nichols, and the company size attribute,
Large, to the ABC Company customer.
Consider the following guidelines:
Attribute dimensions can have a data type of text, date, Boolean, or numeric. The data type
applies only to level-0 members of the attribute dimension.
Attribute names must be unique.
Y i tt ib t l t di i h th E tit di i d You can assign attributes only 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.
If you change sparse dimensions to dense dimensions, all attributes and attribute values for
the dimension are automatically deleted.
You cannot assign attributes to label-only members. You cannot assign attributes to label only members.
You must assign attributes at the same level in the base dimension.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Attributes
Create the
attribute.
Create values for
the attribute.
Add Child or
Add Sibling.
Attribute values
You create attributes and add attribute values on the Dimensions page. You can then assign
attribute values to dimension members. When you create forms and reports, you can filter
dimension members by their attribute values.
For the example in the slide, you create an attribute called Account Executive and add an attribute
value for each account executive in your organization. You can then assign an account executive
to each Customer dimension member to manage sales plans.
To create attributes and attribute values:
2. In the Dimension drop-down list, select a sparse dimension.
3. Select the top-level member in the hierarchy.
4. Click Action, and select Custom Attributes.
The Create Attribute dialog box is displayed.
6. For Name, enter a name for the attribute.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

7. For Data Type, select Text, Date, Boolean, or Numeric, and click Save.
8. In the right pane, select the attribute name, and perform the following actions to add attribute
values:
a. Click Action, and select Add Child. ,
b. For Name, enter a name for the attribute value, and click Save.
c. Select an attribute value, click Action, and select Add Child or Add Sibling to add
another attribute value.
d. Repeat step c to add other attribute values for the selected attribute.
e. Click Close.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Assigning Attribute Values
Assign Tom Baker as the
account executive for the
N001 customer.
After creating attribute values, you assign them to dimension members. You must assign attribute
values at the same level in the hierarchy; otherwise, an error occurs during the application refresh.
For the example in the slide, you assign the Tom Baker account executive attribute value to the
p , y g
N001 customer to specify that Tom Baker manages that customer.
To assign attribute values:
2. In the Dimension drop-down list, select a sparse dimension.
5. Select the Attribute Values tab.
6. Expand the attribute name, and select an attribute value.
7. Click Add to assign the attribute value to the member.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Adding User-Defined Attributes
Assign Southwest
as the UDA for
customer N003.
User-defined attributes (UDAs) describe the characteristics of dimension members. The example
in the slide shows region UDAs, such as North, South, East, and West to categorize customers by
geography. After creating the UDAs, you assign the appropriate region to customer members.
You can assign UDAs to members in dense or sparse dimensions. You can use UDAs in
calculation scripts, member formulas, and reports to return lists of members that are associated
with the UDA. For example, you can create a UDA called New Products and assign it to new
product members in the Product dimension. You can then create calculations only for products
designated as New Products.
UDAs are specific to dimensions. For example, creating a UDA for an Account member makes it
available for nonshared Account members Deleting it removes it for all Account members To available for nonshared Account members. Deleting it removes it for all Account members. To
make UDAs available for multiple dimensions, create the same UDA for multiple dimensions.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To create UDAs:
2 In the Dimension drop-down list select a dimension 2. In the Dimension drop-down list, select a dimension.
5. Select the UDA tab.
The Create a UDA dialog box is displayed The Create a UDA dialog box is displayed.
7. Enter a UDA name, and click Save.
To assign UDAs to members:
5. Select the UDA tab.
6. In the left pane, select one or more UDAs, and click Add .
7. Click Save.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Smart Lists: Overview
Enter data values for
Headcount and T&E.
Select smart list entries for
Customer Service Class.
In Planning applications, smart lists are custom drop-down lists in form cells, member formulas,
and business rules. Smart lists streamline data entry because Planning users can select items
instead of entering data manually.
For the example in the slide, you create a smart list with entries of Platinum, Gold, Silver, and
Bronze, and you associate the smart list with the Customer Service Class account member. In a
form, when you click in a form cell for the Customer Service Class account, you choose its value
from a drop-down list.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Smart Lists
Add smart list entries.
Create the smart list and
specify its properties.
Preview the smart
list entries.
You create smart lists, define their properties, and add smart list entries.
Keep the following smart list guidelines in mind:
You associate smart lists with dimension members
You associate smart lists with dimension members.
After associating smart lists with dimension members, you reserve those members to store
only smart list values. Do not use those members to store other data values.
You should 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.
You can associate smart lists with more than one member, but those members must be
level-0 members.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

When creating or modifying smart lists, you define the following smart list properties:
Smart List Unique name that begins with a letter, and can contain only alphanumeric and
underscore characters and no special characters, spaces, or Java-reserved words. Smart list
names can be referenced in formula expressions.
Label Text to display when the smart list is selected. Spaces and special characters are
allowed. Smart list labels can reference a resource, which can be translated into different
languages.
Display Order Order by which to sort the smart list (ID, Name, or Label).
#Missing Drop Down Label Label to be displayed as an entry in the smart list whose
value is #Missing.
#Mi i F L b l H i i l t d i ll th t i t d #Missing Form Label How missing values are represented in cells that are associated
with the smart list:
- Drop Down Setting displays the value you specified in the #Missing Drop Down Label
property.
- Form Setting displays the value based on the form display option for missing data
(blank or #Missing).
Automatically generate ID Automatically generate a numeric ID (sequence number) for Automatically generate ID Automatically generate a numeric ID (sequence number) for
each smart list entry. If you do not select this property, you can enter the ID values manually.
To create smart lists and smart list entries:
1. Select Administration, then Manage, and then Smart Lists.
The Mange Smart Lists page is displayed.
2. Click Actions, and select Create.
The Properties tab for Create Smart List is displayed. The Properties tab for Create Smart List is displayed.
3. Enter or select the smart list properties.
4. Select the Entries tab.
5. Click Actions, and select Add.
6. Enter the name and label for the smart list entry.
7. Repeat steps 5 and 6 to add other smart list entries.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Associating Smart Lists with Members
Select the SmartList data type
and the name of the smart list.
You associate smart lists with dimension members. Keep in mind that you cannot enter values in
form cells for members that you associate with smart lists.
To associate smart lists with members:
The Member Properties tab is displayed The Member Properties tab is displayed.
5. In the Data Type drop-down list, select SmartList.
6. In the Smart Lists drop-down list, select the smart list.
7. Click Save.
Note: After associating smart lists with members, refresh the database in Planning to update the
Essbase outline.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Forms and Smart Lists
Smart list entries
in a form
Account 6060 is associated
with a smart list.
To work with smart lists on forms, you must add the member that is associated with the smart list
to the form. For the example in the slide, you create a form that includes an account
(6060:Customer Service Class) that is associated with the smart list, Customer_Service_Level.
Keep in mind the following key points:
You can assign members associated with smart lists to rows or columns.
You cannot use smart lists in pages.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the descriptions that are applicable to user-defined
dimensions.
a. They help you capture the categories that your
organization uses for budgeting and planning. g g g p g
b. They must have unique names.
c. You must assign valid plan types at the dimension level.
Answer: a, b, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You create attributes for a dimension to further define member
characteristics.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You can create user-defined attributes (UDAs) to further define
Entity dimension members.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that smart lists enable you to perform in
Planning.
a. Select an item from a predefined list instead of entering
data manually. y
b. Create lists of data for a form cell on an ad hoc basis.
c. Enter data directly into cells.
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Create member formulas
Describe user-defined dimensions
Create attributes and assign attribute values Create attributes and assign attribute values
Add user-defined attributes
Create and manage smart lists

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Importing Currencies
Importing Attribute Dimensions
Importing the Customer Dimension Members Importing the Customer Dimension Members
Importing Smart Lists
Importing Entity Dimension Members
Importing Accounts
Adding Member Formulas g
Verifying System Properties
Updating the Essbase Database
Setting Account Members to Dynamically Calculate
Applying Performance Settings

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

S tti U E h R t Setting Up Exchange Rates

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
At the end of this lesson, you should be able to:
Describe currencies and exchange rates
Create exchange rate tables
Generate currency conversion calculation scripts Generate currency conversion calculation scripts

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Currencies and Exchange Rates
Enter values in local currency.
Use exchange rates to convert values from one currency
to another.
Set up currency conversions: Set up currency conversions:
Enter exchange rates for converting to reporting currencies.
Generate currency conversion calculation scripts.
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 that were converted
from local currencies to reporting currencies.
You use exchange rates to convert values from one currency to another, and you plan in a
variety of currencies to perform the following tasks:
Enable budget preparers to create plans in their native currencies.
Show summary data in reports in a particular currency.
Summarize values from multiple currencies into a single currency.
When you create Planning applications you indicate whether the application has multiple When you create Planning applications, you indicate whether the application has multiple
currencies, and you specify a base currency. You enter exchange rate values in Planning
through exchange rate tables that correspond to different business scenarios. For example,
you create exchange rate tables named Actual Rates and Budget Rates.
You assign a currency code and symbol to each currency, and you specify a triangulation
currency and reporting currencies when you set up the Currency dimension.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

After you create and populate exchange rate tables, you can display converted currency data
in forms. For example, the base currency for Japan is the Japanese yen, and the base
currency for the United States is the U.S. dollar. When you view a form that contains values
for Japan, if the display currency is set to U.S. dollars, the exchange rate for the Japanese
yen is used to convert the values to U.S. dollars.
The currency conversion calculations are run as calculation scripts. Planning automatically
generates the calculation scripts that are needed for currency conversion. Multicurrency
applications store exchange rates with the HSP_Rates dimension, which includes these
members and others that store currency rates:
HSP_InputValue Stores data values
HSP I tC St t f d t l HSP_InputCurrency Stores currency types for data values
When generating reports or loading data, you must refer to the HSP_InputValue member.
When loading data, you must load data against the local currency. You need not refer to the
HSP_InputCurrency member. By default, the HSP_Rates dimension is set to Dense.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Exchange Rate Tables
Add an exchange rate table. g
You create exchange rate tables in Planning. Exchange rate values are stored in the Planning
relational database.
You can create as many exchange rate tables as the application requires. Each table
You can create as many exchange rate tables as the application requires. Each table
represents a different business scenario. For example, you name the tables Forecast, Actual,
and Budget.
Administrators assign exchange rate tables to scenarios when creating or modifying scenario
metadata. For example, the Forecast scenario has the Budget and Forecast exchange rate
table assigned to it.
To create exchange rate tables:
1. In a Planning application, select Administration, then Manage, and then Exchange
Rates.
The Manage Exchange Rates page is displayed.
2. Click Actions, and select Create.
3. Enter a name and optional description for the exchange rate table.
4. Click Save.
Note: You do not have to refresh Essbase.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Entering Exchange Rates
Select currency
options.
Enter rates.
You can enter conversion values between the default currency and all currencies that are set
up in the Currency application. When you set up exchange rate tables, only the default
currency and triangulation currencies are available as destination currencies. You can enter
exchange rates from all source currencies to the default or triangulation currencies.
Three types of exchange rates are associated with a currency: historical, average, and
ending. You specify the exchange rate type used for each account when you set up accounts
in Planning. For average and ending rates, enter rates for each time period. For the historical
rate type, enter a single rate that is used for all time periods.
When you enter exchange rates, you select either multiply or divide as the calculation
th d F l if t 2 th t f ti B iti h d t U S d ll 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, one British pound is converted to two U.S.
dollars.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To enter exchange rates:
1. In Planning, select Administration, then Manage and then Exchange Rates.
The Manage Exchange Rates page is displayed.
2 Select the exchange rate table click Actions and select Edit 2. Select the exchange rate table, click Actions, and select Edit.
3. In the Currency To drop-down list, select a currency value.
4. In the Year drop-down list, select a year for which to enter currency conversion rates.
5. For the first currency listed, in the Edit column, click Exchange Rates .
The Exchange Rate dialog box is displayed.
6. Choose a method: Multiply or Divide.
7. Optional: Enter an exchange rate value for Historical.
8. Optional: Enter an exchange rate value for BegBalance.
9. For the first time period, enter an average and ending value.
10. In the Average column, perform one action: Click Fill Year , or Fill Table .
11. In the Ending column, perform one action: Click Fill Year , or Fill Table .
12. Click OK.
13. Repeat steps 5 through 12 for each currency in your application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Calculating Implied Rates Through Triangulation
Assumptions:
U.S. dollar is the default application currency.
Euro is a reporting currency.
British pound is a local currency that is available in the British pound is a local currency that is available in the
application.
Currency Rate
British pound to U.S. dollar 1.4
European euro to U.S. dollar 1.2
1.4 / 1.2 = 1.16
You enter exchange rates for converting the currency values to the applications default
currency, not to reporting currencies. Planning automatically derives the rates for converting
to reporting currencies by triangulation through the application currency.
For the example in the slide, suppose the U.S. dollar is the application currency and the
European euro is a reporting currency. You enter 1.4 as the rate for converting British pounds
to U.S. dollars and 1.2 as the rate for converting European euros to U.S. dollars. To
determine the rate for converting British pounds to European euros, Planning divides the
British pound rate by the European euro rate to derive 1.16 as the rate.
When you set up currencies, you specify whether the currency has a triangulation currency
th th th d f lt A t i l ti ll th t b t l t d other than the default currency. A triangulation currency allows the currency to be translated
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.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

For example, the British pound and the Danish krone are both 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.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Exchange Rates and the HSP_Rates Dimension
Input members:
Draft 1
100.00 USD
Currency (Rate) members:
Multicurrency applications store exchange rates in the HSP_Rates dimension, which is
created in Essbase databases and has two sets of members (input and currency rate).
The input members are HSP InputValue for storing data values and HSP InputCurrency for
The input members are HSP_InputValue for storing data values and HSP_InputCurrency for
storing currency types for the data values. When you enter or load a data value in a cell for
the local currency, it is stored at the intersection Local -> HSP_InputValue. The
intersection Local -> HSP_InputCurrency stores the currency code for that value. For
the example in the slide, the input value is 100.00 and the input currency is USD.
The currency rate members store the exchange rates for each currency. Each currency added
to the application has an HSP_Rates member.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Generating Currency Conversion
Calculation Scripts Calculation Scripts
Two types of calculation scripts are associated with currency conversion: one that copies
exchange rates to account members and another that executes the currency conversion. To
generate these calculation scripts, you select options on the Currency Conversions page. You
run calculation scripts by launching business rules in Planning.
For the example in the slide, you create the PlanCurB script to generate currency conversion
calculation scripts for the USD and EUR currencies, Budget and Forecast scenarios, and for
the bottom-up versions Draft 1, Draft 2, and Final.
When you generate the calculation script, you select the reporting currencies, scenarios, and
versions for which you want the calculation to run. You can generate currency conversion
l l ti i t t d t diff t b i i i T i ll calculation scripts to correspond to different business processing scenarios. Typically, you
create a separate calculation script for each scenario.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To generate currency conversion calculation scripts:
1. Select Administration, then Manage, and then Currency Conversions.
The Currency Conversion Script File page is displayed.
2 In Calculation Script File enter the name and description for the calculation script 2. In Calculation Script File, enter the name and description for the calculation script.
3. In Calculation Script Details, enter or select the currencies and scenarios that you want
to include in the currency conversion calculation script.
4. Select one of the following version types:
- Bottom-up
- Target
5 E t l t th i t i l d i th i l l ti i t 5. Enter or select the versions to include in the currency conversion calculation script.
6. Click Save.
Copy Rates Calculation Scripts
The Copy Rates calculation script copies the appropriate exchange rate to the individual
account members based on their exchange rate type. Performance is improved because
Planning can retrieve the conversion rate for the account directly, without looking up the rate
ttype.
Separate copy rate calculation scripts are generated for bottom-up and target versions. The
name of the script is HspCRtB for bottom-up versions and HspCRtT for target versions. You
run these scripts after entering exchange rates and before running the currency conversion
calculation script for the first conversion. Subsequently, you run the copy rates calculation
scripts only when the following conditions change:
Exchange rates Exchange rates
Account exchange rate types
Exchange rate table assignment for a scenario
Metadata (for example, you add a new currency or account with a data type Currency.)
Currency Conversion Calculation Scripts
Planning generates a calculation script to convert values for local currencies to one or more
reporting currencies The calculation script converts values for all accounts and entities The reporting currencies. The calculation script converts values for all accounts and entities. The
currency conversion calculation script generated by Planning converts only level 0 members
for bottom-up versions and all levels for target versions. For bottom-up versions, you must run
an aggregation to populate upper-level members with the new converted values.
Because the currency conversion calculation script runs for all entities and accounts in your
application, it is typically run by budget administrators rather than end users. If end users
need to see their data converted to a reporting currency, they should use the calculate
currencies business rules that are associated with forms.
Calculate Currencies Business Rules
In addition to generated currency conversion calculation scripts, a dynamically system-
generated business rule is associated with forms. It converts data from the local currency to
the reporting currency only for the members currently displayed on the form. This business
rule enables planners to view converted values for the entered data.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the objects for which you can generate a calculation
script.
a. Entities
b Reporting currencies b. Reporting currencies
c. Scenarios
d. Versions
Answer: b, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Which statements describe how exchange rate tables impact
how users work with Planning:
a. Planners can create plans in their native currencies.
b Planners must key data in the application default currency b. Planners must key data in the application default currency.
c. Planners can view summary data in reports in a particular
currency.
d. Planners can summarize values from multiple currencies
into a single currency.
Answer: a, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
All except one exchange rate type is associated with a
currency. Identify the odd one.
a. Beginning
b Historical b. Historical
c. Average
d. Ending
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe currencies and exchange rates
Create exchange rate tables
Generate currency conversion calculation scripts Generate currency conversion calculation scripts

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Loading Exchange Rates
Associating Exchange Rates with Scenarios
Creating the Currency Conversion Scripts Creating the Currency Conversion Scripts
Verifying Currency Conversion Scripts in Essbase

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

L di d C l l ti D t Loading and Calculating Data

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Describe data load options
Load data values with Administration Services
Describe the Outline Load utility Describe the Outline Load utility
Describe data loading with ERP Integrator
Describe data load options with ODI
Perform data calculations after loading data

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Data Load Options
You can use any of the following to load data:
Administration Services
ERP Integrator ERP Integrator
Financial Data Quality Management
Planning creates an Essbase database for each plan type in your application. You can load
data directly into the Essbase database that corresponds to the plan type in your application.
When you create your Planning application, the Essbase databases do not contain data.
You can load data values from external systems into your Planning application. For example,
you load data for actuals from your ERP system to Planning so that you can calculate
variances.
You can use the following methods to load data:
Extract data to ASCII text files (flat files) from external systems and load it by using
Administration Services with or without Essbase data load rules.
Load data with the Outline Load utility. This utility uses text load files to load data into
applications.
Load data from source GL and HR systems with ERP Integrator. To review the
supported sources for GL and HR data, see the Oracle Enterprise Performance
Management System Supported Platform Matrix.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Load data with an extraction, transformation, and loading (ETL) tool by using Planning
and Essbase adapters. You can use an ETL tool, such as Oracle Data Integrator to
import data into Planning Administration applications.
Load data with Oracle Hyperion Financial Data Quality Management Adapter for yp y g p
Planning.
To load data, you must have the following items:
An Essbase database into which you load the data or in which you build an outline
A connection to the Essbase Server
Any of the following valid data sources:
- Flat files from text backups or external sources - Flat files from text backups or external sources
- Relational database data sources, such as Oracle or SQL
- Essbase export files
- Microsoft Excel spreadsheet files with the XLS or XLSX file types (When you use
spreadsheet files to load data or build an outline in Essbase, the spreadsheet files
must reside on a Windows computer, regardless of the tool.)
- Spreadsheet audit log files Spreadsheet audit log files
A data source that is correctly formatted for free-form data loading, if you are not using a
rules file for loading data
A rules file that is validated for data loading, if you are using a rules file for loading data

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Loading Data Values
with Administration Services with Administration Services
Right-click a
database, and
select Load data.
Select a data file to load.
Optional: Select a rules file.
Click OK.
You can use Administration Services to load data flat files directly into the Essbase databases
that correspond to the plan types in the application. You can extract data to flat files from
external systems so that you can load it into Essbase. Data is scanned from the top of the file
and from left to right.
To load data with Administration Services:
1. In Administration Services, right-click a database, and select Load data.
2. Click Find Data File to select a data file to load.
3. Optional: Click Find Rules File to select a rules file.
4. Optional: Change the default error file name and path. 4. Optional: Change the default error file name and path.
5. Click OK.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Requirements for Data Load Files
Use Essbase to load data from flat files into your Planning
application.
EUROPE GROSS SALES ACTUAL FINAL Jan FY12 1000
Data Entity Account Scenario Version Period Year
EUROPE GROSS SALES ACTUAL FINAL Feb FY12 400
EUROPE GROSS SALES ACTUAL FINAL Mar FY12 650
ACTUAL FINAL
EUROPE GROSS SALES JAN FY12 1000
EUROPE NET INCOME FEB FY12 400
ASIA NET INCOME FEB FY12 300 ASIA NET INCOME FEB FY12 300
ASIA GROSS SALES JAN FY12 200
BUDGET DRAFT FY13
ENTITY PERIOD CUSTOMER 4000-100 4000-200 4000-300
EUROPE FEB MY COMPANY 1500 1700 1200
Keep the following requirements for data load files in mind:
Define each data point with a member from each dimension.
Ensure that data is for bottom-level members unless you are loading data into a target
Ensure that data is for bottom-level members, unless you are loading data into a target
version.
Separate each field (item) in a record (row) with a valid delimiter.
Enclose member names or aliases in double quotation marks () if they contain blanks,
numeric characters (09), dashes, or unary operators. Be sure to display them exactly
as they appear in the outline.
Place members of the same dimension in the same column or row.
Place members of different dimensions only on the page header. Do not place them
together in any row or column.
The slide illustrates examples of how to format a data load file:
The first sample data load file loads data values for the first quarter of FY12 for the
Europe entity and the Gross Sales account in the Actual scenario and the Final version.
If a dimension has the same value for all rows, you can place it in the header as a page
If a dimension has the same value for all rows, you can place it in the header as a page
dimension, as shown in the second and third samples.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Multicurrency Application Data
The HSP_Rates dimension has the following members:
HSP_InputValue
HSP_InputCurrency
HSP Rate <XXX> HSP_Rate_ XXX
Applications that support multiple currencies have an additional dimension named
HSP_Rates to store exchange rates. The HSP_Rates dimension includes the following
members:
The HSP_InputValue member stores data values.
The HSP_InputCurrency member stores currency types for the data values.
The HSP_Rate_<XXX> member stores currency for multicurrency applications (XXX
represents the currency).
You load data to the HSP_InputValue member and the local currency. The
HSP_InputCurrency member is not displayed in Planning. However, if the default currency is y y g y
overridden, the new currency and its value are stored in the database.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Managing Data with the Outline Load Utility
To load data with the Outline Load utility, follow these steps:
1. Create a load file for each dimension or set of data you
want to load.
2 Test the load files 2. Test the load files.
3. Load the files with the Outline Load utility
4. Repeat steps 1 through 3.
You can use the Outline Load utility to load data for the Account, Period, Year, Scenario,
Version, Currency, Entity, and user-defined dimensions. You also can use the Outline Load
utility to load attributes, UDAs, exchange rates, Smart Lists, and planning unit hierarchies.
You can optimize command lines by storing command line arguments in a command
properties file (.properties), then use the /CP: parameter in the command line to refer to
that file when you execute the Outline Load utility. For example, you can use a command
properties file to run the same commands on multiple applications. You would only need to
change the /A parameter in the command line for each import.
You create a load file for each dimension or set of data that you want to load. For example, if
t t l d tit d t t CSV l d fil t l d titi you want to load entity data, create a CSV load file to load entities.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Importing Data From Flat Files or RDMS
Test data load files to verify that the files parse without any
errors.
Use the /N parameter to test load files without loading the
data.
Sample command to verify the result of loading entity
information into the Hyplan application:
OutlineLoad /A:Hyplan /U:admin /M /N
/I:d:/data/Entity.csv /D:Entity /X:d:/log/Entity.exc
/L:d:/log/Entity.log
You can test load files to verify that the files parse without any errors. Running the Outline
Load utility with the /N parameter does not load data, but ensures that the load files parse
successfully.
To import data from flat files:
The command-prompt window is displayed.
2. Enter CD
x:/oracle/Middleware/user_projects/epmsystem1/Planning/planning1
to navigate to the default folder that contains the Outline Load utility. g y
3. Enter the following case-sensitive command syntax to test the load file:
/D:loadDimensionName /L:logFileName /N [/S:serverName] [/M]

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

4. Open the log file and verify that no error messages were generated.
5. Enter the following case-sensitive command syntax to load data:
/D:loadDimensionName /L:logFileName [/S:serverName] [/M] g
6. Review the exception and log files, and perform one of the following actions:
- If no errors are reported, you loaded data successfully.
- If errors are reported, fix the errors and repeat steps 5 and 6.
You can also import data from a relational database source. The import of data contained in a
relational database is achieved by supplying a query on the external database that returns a y pp y g q y
result set equivalent to the flat file input format. A query and database connection information
needs to be provided.
Oracle recommends that users employing this functionality are familiar with relational
databases, the SQL query language, and JDBC connection properties. For Planning
applications, examples of these properties can be found in the HSPSYS_DATASOURCE table in
the system database, which by default is located in the relational database that you create
when selecting the Configure Database task under Planning in EPM System Configurator when selecting the Configure Database task under Planning in EPM System Configurator.
These command-line parameters are available for users using the Outline Load utility to
import from a relational data source:
l /IR[:RDBConnectionPropertiesFileName]
l /IRA
l /RIQ:inputQueryOrKey
l /RIC:catalog
l /RID:driver
l /RIR:url
l /RIU:userName
l /RIP:password
N t Th /IR d /RIQ t l i Note: The /IR and /RIQ parameters are exclusive.
The following table describes the parameters for loading data from a relational database:
/IR[:RDBConnectionPr Specifies that the input records will come from a relational /IR[:RDBConnectionPr
opertiesFileName]
Specifies that the input records will come from a relational
database source. Specifying the optional properties file
designates that some or all of the required relational
connection switch properties (/RIQ, /RIC, /RID, /RIR, /RIU,
/RIP) can be found within the properties file.
A data load dimension (/D option) must be specified as well.
The /ICB switch can be specified to clear Essbase data.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

/IRA Identical to the /IR switch except that the required RDB JDBC
connection properties (/RIQ, /RIC, /RID, /RIR, /RIU, /RIP
switch values) are obtained from the currently connected switch values) are obtained from the currently connected
applications RDB data source
A data load dimension (/D option) must be specified as well.
The /ICB switch can be specified to clear Essbase data.
/RIQ:inputQueryOrKey An SQL query or a key in the command arguments properties
file (/CP switch) in which the value is a SQL query that is
executed to produce input for an import operation executed to produce input for an import operation
The /IR switch must be set for this to be used, and if it is used,
the /RIC, /RID, /RIR, /RIU, and /RIP switches must also be set.
/RIC:catalog An RDB JDBC catalog name for the input RDB connection.
The /IR switch must be set for this to be used, and if it is used,
the /RIQ, /RID, /RIR, /RIU, and /RIP switches must also be set.
If the /IRA switch is used this switch does not need to be If the /IRA switch is used, this switch does not need to be
specified.
/RID:driver An RDB JDBC driver name for the input RDB connection. The
/IR switch must be set for this to be used, and if it is used, the
/RIQ, /RIC, /RIR, /RIU, and /RIP switches must also be set.
If the /IRA switch is used, this switch does not need to be
specified. specified.
/RIR:url An RDB JDBC URL for the input RDB connection. The /IR
switch must be set for this to be used, and if it is used, the
/RIQ, /RIC, /RID, /RIU, and /RIP switches must also be set.
specified.
/RIU:userName An RDB JDBC username for the input RDB connection The /RIU:userName An RDB JDBC username for the input RDB connection. The
/IR switch must be set for this to be used, and if it is used, the
/RIQ, /RIC, /RID, /RIR, and /RIP switches must also be set.
specified.
/RIP:password An RDB JDBC password for the input RDB connection. The
/IR switch must be set for this to be used and if it is used the /IR switch must be set for this to be used, and if it is used, the
/RIQ, /RIC, /RID, /RIR, and /RIU switches must also be set.
If the /IRA switch is used, the /RIP switch is not required.
Enter the password in its unencrypted form when specifying it
for the first time in the .properties file. When the Outline Load
utility is run, the properties file will be rewritten with an
encrypted value for the /RIP password. If this value is not
specified in the properties file, a command line prompt will be
issued to obtain the password.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Exporting Application Data
Set the properties file with the following details:
Server name
Application
Username Username
Output file
Data intersection
Run the command-line utility:
OutlineLoad /CP:d:/myprop_dataexport.properties
The output file:
Account, Jan, Feb, Mar, Point-of-View, Data Load Cube Name
4000,10, 250, 300, "FY13, Budget, Working, Local, South, N001", Plan1
You can run the Outline Load utility with the myprop_dataexport.properties file to
export data from an application into a flat file. You set the server, application, username,
name of the output file, and intersection of data to export in the properties file. For example,
the properties file is set to the following:
/S:localhost
/A:Hyplan
/U:admin
/ED:d:/output_file
/EDD:data export specification p p
You indicate the POV selections by placing double-quotes around it.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

ERP Integrator Data Load Process
.
ERP EPM
ERP Integrator
1
ERP
source
system
EPM
target
application
2
3
4
Here is a high-level overview of the ERP Integrator data load process:
1. Extract GL data from the ERP source system into the EPM target application.
2 Drill through from the EPM target application to view data in the ERP GL source system
2. Drill through from the EPM target application to view data in the ERP GL source system.
3. Write back budget data from the EPM target application to the GL source system.
4. Extract HR data from the ERP source system to the EPM target application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

ERP Integrator:
Drilling Through and Writing Back Budget Data Drilling Through and Writing Back Budget Data
E-Business
Suite
Performance
Management
Applications
FDM
E-Business
Suite
E-Business
Suite
E-Business
Suite General
Ledger
1 1
Planning
Financial
Management
ERP Integrator
Smart
View
Financial
Reporting
PeopleSoft
Enterprise
Financial
Management
1 1
1
Oracle Data
I t t
Drill
through
Drill
th h
Essbase
PeopleSoft
Financials
E-Business
Suite General
Ledger
2
2
Integrator through
Write
back
You can drill through and write back budget data as follows:
1. You can drill through to the source GL data from Planning, Financial Management,
Smart View, Financial Reporting, and Hyperion Enterprise (Release 6.5.1 or later) to the
S a t e , a c a epo t g, a d ype o te p se ( e ease 6 5 o ate ) to t e
source ERP systems to further analyze the data and examine transactional details.
Note: For Smart View and Financial Reporting, you can drill through only if the data
source is Planning, Essbase, or Financial Management.
2 You can write back budget data from the EPM target system (Planning, Essbase BSO,
and Essbase ASO) to your GL source system (E-Business Suite and PeopleSoft, which
includes standard budgets and commitment control). You cannot write back data to SAP
GL F i Fi i l P l S ft H C it l M t) GL, Fusion Financials, or PeopleSoft Human Capital Management).
For detailed information about ERP Integrator, see the Oracle Hyperion Financial Data
Quality Management ERP Integration Adapter for Oracle Applications Administrators Guide,
Release 11.1.2.2.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Oracle Data Integrator Data Loads with ETL Tools
You can integrate Planning with any database through the
Oracle Data Integrator Adapter for Planning.
You can use ETL tools to load data into Planning applications. If you have a simple data load,
you can load a flat file. However, if you have a complex data load, you can use an ETL tool,
such as Oracle Data Integrator.
Oracle Data Integrator is a graphical tool for loading data into your Planning environment. For
applications that you manage with Planning application administration, you can load data into
Planning and Essbase by using 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.
Adapters depict the structure of the database into which you are loading data. They are
l t d ith th l t t d t l ti hi f di i Th f b f l di populated with the relevant metadata relationships for a dimension. Therefore, before loading
data into Planning, you must ensure that the metadata (dimension members) exists in the
Planning relational database and the Essbase database. If necessary, refresh the Essbase
database to synchronize your changes. You can schedule an Oracle Data Integrator data load
to occur during off-peak hours.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Data Calculations
Measures (Label Only)
Profit (+)
Margin (+)
Sales (+)
Level 2
Level 1
Level 0
COGS (-)
Expenses (-)
Marketing (+)
Misc (+)
Typically, you load data into the level 0 members of a database. After loading data, you
calculate the database as follows:
Aggregate child member values to derive parent member values
gg egate c d e be a ues to de e pa e t e be a ues
Apply member formulas that are defined in the outline
The following types of calculations in Planning are covered in this lesson:
Dimension calculations that follow the outline structure in Essbase
Calculations of data blocks within the Essbase database
Calculations that are executed from calculation scripts
B i l i C l l ti M Business rules in Calculation Manager
Dimension calculations follow the order in the outline when determining the order in which
members are calculated:
Calculations start at the lowest level of a branch from top to bottom.
Calculations move up to the next level when the end of a subbranch is reached.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The example in the slide depicts the order of a calculation in the Account dimension. Selected
calculations occur in the following order:
Within the Margin branch: Sales and then COGS (steps 1, 2, and 3)
Within the Profit branch: Margin and then Expenses (steps 1 2 3 and then 4 5 and Within the Profit branch: Margin and then Expenses (steps 1, 2, 3, and then 4, 5, and
6)
Essbase databases are organized into data blocks. Each data block consists of all dense
dimension members in the outline for a unique combination of sparse members. Each unique
combination of sparse members determines the potential data blocks.
The data blocks for the members of the first sparse dimension are calculated first, and
proceed down the list from the order listed in Performance Settings.
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.
When Essbase calculates the dense dimension members for a data block, it calculates the
A t di i fi t d th th P i d di i Th i i d di i Account dimension first and then the Period dimension. The remaining dense dimensions are
then calculated based on their order in Performance Settings.
The example in the slide shows the following:
The Los Angeles and San Francisco sparse dimension members have level 0 data
blocks, and California (the parent) has an upper-level data block.
The data blocks each have Account and Period dense dimensions.
F th L A l d S F i d t bl k E b b th l l ti f For the Los Angeles and San Francisco data blocks, Essbase bases the calculation of
the Account and Period members 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.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Calculation Scripts in Essbase
The default calculation script calculates the entire database.
Calculation scripts can include calculation commands, equations, and formulas. Calculation
scripts also define how databases are calculated.
Every database needs at least one calculation script to aggregate unary operators and
Every database needs at least one calculation script to aggregate unary operators and
execute formulas in the outline. For most database calculations, the default calculation script
provides the required results. You can run the default outline calculation script from
Administration Services.
The default calculation script calculates an Essbase database in its entirety.
If multiple currencies are enabled for the Planning application when you create a currency
conversion, a currency conversion calc script is created, based on selected scenarios,
versions, and currencies. For the example in the slide, PlanCurB and PlanCurT are the
currency conversion calculation scripts created in the Hyplan application.
A second calc script is generated by Planning, which copies appropriate exchange rates to
the account, based on account rate types. For currency conversion, the Account type always
takes precedence. Data type evaluation order is not considered. The copy calc script is
named HspCrtB.csc for bottom-up versions and HspCrtT.csc for target versions.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Business Rules
Execute complex calculations that do not follow the
hierarchical aggregation.
Design business rules in Calculation Manager.
In traditional multidimensional applications, your organization typically requires calculations
that cannot be calculated through a hierarchical aggregation. For these more complex
calculations, you can create business rules, which are integrated with Planning and leverage
Essbase calculation scripts. For example, you calculate aggregated totals and allocate totals
based on headcount.
You can also use business rules to target specific slices of the database. For example, you
copy values for Product Sales, Europe 2012 to Product Sales, Europe 2013, and increment
the values by 8%.
You use Calculation Manager to create business rules. Business rules are stored in a central
it th b i l t ithi lti l li ti Y repository, so you can reuse the business rule components within multiple applications. You
can easily edit a business rule in one application and use it in another application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
When you create a Planning application, the Essbase
databases do not contain data for it.
a. True
b False b. False
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select three data load options for Planning applications created
with Planning application administration.
a. Administration Services
b Data Load utility b. Data Load utility
c. ERP Integrator
d. Outline Load utility
Answer: a, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the descriptions that are applicable to calculation scripts.
a. They contain a series of calculation commands, equations,
and formulas.
b They define calculations other than the calculations b. They define calculations other than the calculations
defined by the database outline.
c. They specify how to calculate a database.
Answer: a, b, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe data load options
Load data values with Administration Services
Describe the Outline Load utility
y
Describe the Outline Load utility
Describe data loading with ERP Integrator
Describe data load options with ODI
Perform data calculations after loading data

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Loading Data and Test Forms
Verifying Data and Form Loads

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

S tti U Pl i S it Setting Up Planning Security

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
Describe security in Planning
Provision users and groups in Shared Services
Assign access permissions to artifacts in Planning Assign access permissions to artifacts in Planning
Export and import access permissions
Create security filters

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Security: Overview
You perform the following security-related tasks:
Determine user roles.
Assign access permissions.
Create security filters.
Security in Planning is based on user privileges. User privileges are system roles and access
permissions that you assign to users or to groups. Groups are sets of users who need similar
access permissions.
After establishing or updating user and group security and assigning member access in Planning,
you must refresh the Planning application to update Essbase security filters.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Security Levels
Access permissions Planning roles in Shared Services
Data
security
Artifact
security
User
authentication
Provisioning
security security authentication
Planning provides security at the following levels:
Planning roles in Shared Services
- Users must provide a valid ID and password to log on to Planning applications
Users must provide a valid ID and password to log on to Planning applications.
- Users can launch only those tasks to which they have access. For example, you can
allow users to create forms but not dimension members. You provision users and
groups by assigning roles to a user or group. Each role is associated with a set of
tasks.
Access permissions
- Users can view and modify data only for dimensions and members to which they have
access.
- Users can open only those artifacts, such as forms and task lists, to which they have
access.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

By default, users and groups do not have access to the application artifacts. You assign access
permissions to application artifacts in Planning. Access permissions can vary by application and
can be assigned for the following artifacts:
Members Assign access to the Scenario, Version, Account, Entity, Period, Year, and user-
defined custom dimension members so that planners can view and change only the data for
their own departments.
Forms Assign appropriate access to forms based on their relevance to users.
Task lists Assign appropriate access to task lists based on their relevance to users. For
example, allow all planners access to the Budget Preparation task list, but allow only
administrators access to the Budget Administration task list.
Business rules Selectively assign users access to business rules Business rules Selectively assign users access to business rules.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

User Authentication
Users must provide a valid username and password to
access an application.
Planning leverages external authentication providers,
such as LDAP and MSAD.
Users and groups must exist in the authentication
directory before they can be granted access to a Planning
application.
User login information for Oracle Hyperion applications is stored outside the applications in an
authentication directory. An authentication directory is a centralized store of users and passwords,
user groups, and corporate information, such as employee IDs or job titles. Users must enter a
valid username and password to access an application.
The following types of authentication directories are supported:
Native Directory
Lightweight Directory Access Protocol (LDAP)
Microsoft Active Directory (MSAD) server
Relational databases such as Oracle DB2 and SQL Server
For additional details on the supported authentication providers, see the Oracle Enterprise
Performance Management System Supported Platform Matrix.
You can grant access to your Planning applications to any user or group in an authentication
directory. When you grant group access, the users in the group are also granted access to the
application.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planning Roles in Shared Services
Administrators view of the
Administration menu
Interactive users view of
the Administration menu
Available Manage menu
commands for administrators
Available Manage menu
commands for interactive users
Planning roles determine the application tasks that a user can access. Administrators assign
access to tasks by assigning a role to a user or group. Each role is associated with a set of tasks.
For example, because interactive users cannot change dimension members, the dimension
change option is not available.
For the example in the slide, the Administration and Manage menus contain many more menu
commands for the Administrator role than they do for Interactive User role.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Data and Artifact Security
You assign users and groups read, write, or none access
to data for specified dimension members.
Entity Members Assigned Access Level
East Region
West Region
United Kingdom
Singapore
Write
Read
Read
None
RJackson
You can assign security to specific artifacts in Planning
applications.
By setting up access permissions for dimension members, you protect data and prevent
unauthorized users or groups from changing data. For the example in the slide, RJacksons
assigned access to entity members is restricted in an application.
You can assign security to specific artifacts, such as task lists, business rules, and forms. For
example, you can allow all users to open the standard expenses form, but allow only payroll
managers to open the salary expense form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

User and Group Provisioning in Shared Services
Provisioning enables centralized management of users, their role assignments, and their access
permissions to applications. You provision users for Planning applications in Shared Services
Console.
You assign user roles to users and groups based on the tasks that users need to perform in
applications. Planning provides user roles that you can assign to users and groups. A user can
receive a combination of individual and group role assignments.
Administrators group users based on similar access requirements for selected artifacts. To reduce
the maintenance required for user security, define access at the group level rather than at the user
level. For example, create a group for planners and a group for administrators and assign access
accordingly accordingly.
The following list summarizes Planning user roles:
Administrator Create applications; manage security; maintain metadata; create and
maintain web-based forms; create and manage task lists; create and maintain Smart View
worksheets; create and launch business rules; initiate the approval process, and enter, view,
copy, modify, and delete data.
Interactive User Enable email notification; create and maintain web-based forms; create
and manage task lists; create and maintain Smart View worksheets; create and launch
business rules; enter, view, and delete data; and submit information and data for approval.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Planner Enable email notification; input, submit, and view data; use reports that were built
by others; run data integration routines that were designed by others; execute business rules
and other processes that are associated with validating and preparing data; view and use
task lists; use Smart View; and submit information and data for approval.
View User View limited data in Planning applications. Typically, the view user is an
executive who wants to see business plans during and at the end of the approval process.
Provisioning Manager Provision users and groups for applications.
Mass Allocation Spread data by using the Mass Allocation function. This role should be
assigned to select users because it has no undo functionality.
Essbase Write Access Submit data directly to Essbase. If you assign this role to planners
and interactive users you give them write access to Planning data through the Smart View and interactive users, you give them write access to Planning data through the Smart View
Essbase interface when they refresh the database security filters. If you do not specify this
role, planners and interactive users are given only read access to Planning data through the
Smart View Essbase interface, no matter what their data access is through Planning directly.
Approvals Administrator Control the approval process; perform actions for the planning
units for which write access is assigned; assign owners and reviewers to planning units, and
update validation rules that affect the approval process. The Approvals Administrator role
consists of the following roles: consists of the following roles:
- Approvals Ownership Assigner Assign owners and reviewers to planning units for
which write access is assigned. Includes Planner responsibilities.
- Approvals Process Designer Modify planning unit hierarchy secondary dimensions
and entity members for which write access is assigned; modify scenarios and versions
that are assigned to planning unit hierarchies, and edit validation rules on forms for
which access is assigned. Includes Planner and Ownership Assigner responsibilities.
- Approvals Supervisor Stop and start planning units and take any action on planning
units for which write access is assigned.
Ad Hoc Grid Creator Create and save ad hoc grids and perform ad hoc operations.
Ad Hoc User View ad hoc grids and perform ad hoc operations.
Task List Access Manager Assign task lists and tasks to users.
.The following global Shared Services roles are also used in Planning:
Administrator Perform all administrative tasks in Shared Services for products that
integrate with it. The Administrator role consists of the following roles:
- Create Integrations Create Shared Services data integrations (the process of
moving data between applications) by using a wizard.
- Directory Manager Create and manage Native Directory users and groups.
- LCM Administrator Run Lifecycle Management to promote artifacts or data across
product environments and operating systems product environments and operating systems.
- Manage Taskflows Create, edit, view, schedule, and run taskflows for any EPM
System product.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

- Run Taskflows View, schedule, and run taskflows for any EPM System product.
- Project Manager Create and manage application groups in Shared Services.
- Run Integrations View and run Shared Services data integrations. For Performance
Management Architect, execute data synchronizations. g , y
Calculation Manager Administrator Administer and manage Calculation Manager
functions. The role comprises the Financial Management Calculation Manager Administrator
role and the Planning Calculation Manager Administrator role.
EPMA Administrator Create and deploy Performance Management Architect
applications. The EPMA Administrator role consists of the following roles:
- Application Creator Create applications and own all dimensions in nondeployed
li ti A li ti t t di i b t h l th applications. Application creators can create dimensions, but can change only the
dimensions to which they have access.
- Dimension Editor Create profiles and import dimensions. Required, in addition to
the Application Creator role, to navigate to the Planning Administration menu.
The following ERP Integrator roles are also used to enable drill-through from outside systems
(such as GL) into Planning:
Create Integration Create ERP Integrator metadata and data rules. Create Integration Create ERP Integrator metadata and data rules.
Run Integration Run existing ERP Integrator metadata and data rule and enter runtime
parameters; view transaction logs.
Drill-Through Drill-through to outside source systems.
GL Write Back Write back to the ERP source system.
For a complete list of user roles, see the Oracle Enterprise Performance Management System
User and Role Security Guide Release 11.1.2.2. y

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Provisioning Users and Groups
Selected
l
Available
Planning
roles
roles
You provision users and groups to enable users to access applications and perform application
tasks.
To provision users and groups:
p g p
1. In EPM Workspace, select Navigate, then Administer, and then Shared Services
Console.
Shared Services Console is displayed.
2. In the view pane, expand User Directories, and then Native Directory.
- Select Users to provision and assign roles to users. p g
- Select Groups to provision and assign roles to groups.
4. Click Search to display a list of all users or groups.
5. Right-click a user or group, and select Provision.
6. Expand the application group and application for which you want to provision the user or
group.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

7. Select the role or roles that you want to assign to the user or group.
8. Click Add .
9. Click Save, and then OK.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Generating Provisioning Reports
Select Roles, Users, or
Groups.
Group results by users,
groups, or application.
Select one or more
applications.
Generate the report.
You can generate provisioning reports to list the provisioning details for users, groups, and roles.
To generate provisioning reports:
1 In Shared Services Console select Administration and then View Provisioning Report
1. In Shared Services Console, select Administration, and then View Provisioning Report.
2. In the Find All drop-down list, select Roles, Users, or Groups. If you select Roles, then in
the For drop-down list, select Users or Groups.
3. For Filter By, enter the criterion to use to filter the report data.
4. In the Show Effective Roles drop-down list, select Yes to report on all effective roles
(inherited as well as directly assigned) or No to report only on directly assigned roles.
5. In the Group By drop-down list, select Application, Group, or User. The available drop- p y p , pp , p, p
down list selections depend on the selection in the Find All and For drop-down lists.
6. Optional: In the Results Per Page drop-down list, select the number of results to display per
page.
7. In the In Application area, select one or more applications or Select All.
8. Click Create Report.
The report is displayed.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Assigning Access Permissions
Assign Access icon
View access. View access.
Add access.
You assign access permissions to Planning application artifacts to protect data from unauthorized
users or groups. The level of security is determined by the users assigned access.
You can manually assign access permissions to the following Planning application artifacts within
y g p g g pp
Planning:
Form folders and forms
Task lists
Business rules
Scenario, Version, Account, Entity, Period, and Year dimension members
User-defined custom dimension members (if the Apply Security dimension property is ( pp y y p p y
selected)

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To assign access permissions:
1. In a Planning application, select Administration, and then Manage.
- For form folders and forms select Forms and Ad Hoc Grids to display the Form and - For form folders and forms, select Forms and Ad Hoc Grids to display the Form and
Ad Hoc Grid Management page.
- For task lists, select Task Lists to display the Task List page.
- For business rules, select Business Rule Security to display the Business Rule
Folders page.
- For dimension members, select Dimensions to display the Dimensions page.
3. Select the folder, form, task list, business rule, or dimension and member for which you want , , , , y
to assign access.
4. Click Assign Access .
The Assign Access for <object-name> dialog box is displayed.
5. Optional: Click Migrate Identities to display the user and group names, and click OK at the
confirmation message.
6. Click Action, and select Add Access.
The Add Access for <object-name> dialog box is displayed.
7. On the Users or Groups tab, select the user or group names for which you want to assign
access.
8. For type of access, perform one of the following actions:
- For form folders, forms, and dimension members, select Read, Write, or None.
- For task lists, select Assigned, Manage, Manage and Assign, or None.
- For business rules, select Launch or No Launch.
9. Optional: For dimension members, select an inheritance option: Member, Children,
Children (inclusive), Descendants, or Descendants (inclusive).
10. Click Add.
11. Click Close twice.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Access Options
Member, form, and form folder access options:
Read
Write
None None
Task list access options:
Assigned
Manage
Manage and Assign
None None
Business rule access options
Launch
No Launch
When you assign access permissions to members, forms, form folders, task lists, or business
rules, you determine which access option to assign for each user or group. By default, for
interactive users and planners, access is denied to all dimension members, forms, task lists, and
business rules.
The following table describes the access options for dimension members, forms, and form folders:
Access Option Description
Read Enables users to view the dimension member or form
W it E bl t i d dif d t f th di i b d Write Enables users to view and modify data for the dimension member and
modify the form design
None Prevents users from accessing the dimension member or form

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The following table describes access options for task lists:
Assigned Enables users to view and use the task list Assigned 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
The following table describes access options for business rules:
Launch Enables users to launch the business rule
No Launch Prevents users from launching the business rule

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Inheritance Options
The following inheritance options are available:
Member
Children
Children (inclusive) Children (inclusive)
Descendants
Descendants (inclusive)
Instead of assigning access permissions to individual dimension members, you can use the more
efficient inheritance option to assign permissions to multiple members.
Note: Assign access to individual members only on an exception basis. For example, for the North
g y p p ,
America Sales group, you assign write access to North America and its descendants, and read
access to one of its children, the North America Headquarters entity.
The following table summarizes the available inheritance options:
Inheritance Option Access Permission
Member Assigned only to the member
Children Assigned to all child members of the member
Children (inclusive) Assigned to the member and its child members
Descendants Assigned to all descendant members of the member
Descendants (inclusive) Assigned to the member and its descendant members
Descendants (inclusive) Assigned to the member and its descendant members

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Precedence and Inheritance
of Access Permissions of Access Permissions
Individual permissions override
group permissions.
For group permissions, no
access overrides write or read
access. Write access overrides
read access.
Direct member permissions
override relationship
permissions.
You can assign access permissions to a member in the following ways:
The user or group can be assigned direct access to a member.
The user or group can be assigned access to a member by relationship through an
The user or group can be assigned access to a member by relationship, through an
inheritance option.
Access permissions from different sources can conflict with each other. For example, you might be
assigned direct read access to a member and write access to the same member through
membership in a group. The following sections explain the rules of precedence.
Individual Permissions Over Group Permissions
Access permissions that are assigned directly to a user override access permissions that are p g y p
inherited from associated groups. For example, if, for the Budget member, you inherit read access
through a group and are assigned direct write access, you have write access to the Budget
member.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Group Precedence
A user might belong to several groups that have conflicting access permissions to a member. In
this case, none access takes precedence over write or read access. Write access takes
precedence over read access. Here are some examples:
If you have write access to the Budget member from one group and none access to Budget
from another group, you have none access to Budget.
If you have read access to the Budget member from one group and write access to Budget
from another group, you have write access to Budget.
Direct Member Permissions Over Relationship Permissions
You can assign access permissions to members indirectly through relationships to a parent or
ancestor member. Permissions that are assigned directly to a member override permissions that
are derived from a member relationship. Here are some examples:
You are assigned none access to children of the United States entity. You are assigned
direct read access to one of the children, GA. You have read access to GA.
You are individually assigned write access to children of the United States entity. Your group
is assigned direct read access to one of the children, GA. You have read access to GA.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Reporting on Access Permissions
Select the users and groups. Select the objects.
Select the
report options.
To help you effectively view the current access permissions in an application, you can generate
assigned access reports. You can also generate effective access reports to help resolve
inheritance or precedence conflicts.
To report on access permissions:
1. Select Navigate, then Administer, and then Shared Services Console.
2. Expand Application Groups, and then the group that contains the Planning application.
3. Right-click the Planning application name, and select Access Control Report.
4. In the drop-down list on the Select User or Group panel, select Available Users, Available
Groups, or Available Users and Groups.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

5. In the left available panel, select one or more users and groups, and click Add to move
them to the Selected Users and Groups panel.
6. Click Next.
7. On the Select Objects panel, select the Planning artifacts (for example, Account, Entity, j p , g ( p , , y,
Forms) on which to report, and click Add to move them to the Selected Objects panel.
8. Click Next.
9. On the Report Options panel, for Show matching access of type, select one or more
access options (Read, Write, None).
10. For Group the results by, select Users or Objects.
11. In the Report Type area, perform one of the following actions:
- Select Assigned Access to summarize access permissions that administrators assign,
and proceed to step 12.
- Select Effective Access to summarize access permissions as Planning evaluates
them, and skip to step 13.
12. Perform the following actions:
- For Show matching access of relation, select one or more relationships (Member,
Child Child (i l i ) D d t D d t (i l i )) Children, Children (inclusive), Descendants, Descendants (inclusive)).
- Optional: Select the Show inherited from group option to show access permissions
inherited by users in a group.
13. Optional: Select the Show effective access origin option to display the origin of the
effective access.
14. Click Finish.
The report is displayed The report is displayed.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Exporting and Importing Access Permissions
Use Lifecycle Management to migrate access permissions
as security artifacts between applications and file systems.
Run the following command prompt utilities to export or
import access permissions: p p
ExportSecurity utility Exports access permissions from a
Planning application to a Secfile.txt file.
ImportSecurity utility Imports access permissions from a
Secfile.txt file to a Planning application.
You can use Lifecycle Management to migrate access permissions (Security artifacts) between file
systems and Planning applications.
You can export access permissions from Planning applications to a Secfile.txt text file with
p p g pp
the ExportSecurity utility. You cannot use this utility to export task list permissions for
administrators. You must manually add these permissions to Secfile.txt.
You can load access permissions from Secfile.txt into Planning applications with the
ImportSecurity utility, which enables you to quickly assign access for many members, users, and
groups. When you import access permissions, only existing access permissions for imported
members, forms, folders, task lists, and business rules are overwritten. Access to other artifacts is
not affected unless you specify the parameter that clears all existing access permissions not affected unless you specify the parameter that clears all existing access permissions
(SL_CLEARALL).
The name of the import text file must be Secfile.txt, and the file must be saved in the
MIDDLEWARE_HOME\user_projects\epmsystem1\Planning\planning1 folder.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

The text file contains a line for each access permission, and each line must contain the items
described in the following table:
Item Description
Username or group The name of a user or group that is provisioned for the Planning
application
Artifact name The named artifact (member, form, folder, task list, or business
rule) in the application
Access permissions For members and forms: Read, ReadWrite, or None
For task lists: Read, Write, ReadWrite, or None correspond to
Assigned, Manage, Manage and Assign, and None
For business rules and folders: Launch or None
None is ignored. If there are duplicate lines for a combination of
username and member name, the line with ReadWrite access
takes precedence
Essbase access flags
(inheritance options)
@CHILDREN, @ICHILDREN, @DESCENDANTS,
@IDESCENDANTS, MEMBER; Essbase access flags must be in
all capital letters.
Note:
For task lists, you can specify only MEMBER.
For folders you can specify only @IDESCENDANTS For folders, you can specify only @IDESCENDANTS.
Artifact type For artifacts other than members, specify the artifact type:
SL_CALCFOLDER (folders containing business rules)
SL_CALCRULE (business rules)
SL_COMPOSITE (composite forms)
SL FORM (forms) S _ O ( o s)
SL_FORMFOLDER (form folders)
SL_TASKLIST (task lists)
Artifact types must be in all capital letters.
Note:
The ExportSecurity utility automatically adds the required
artifact type in the SecFile txt file If you manually create artifact type in the SecFile.txt file. If you manually create
the SecFile.txt file, you must add the artifact type.
The ExportSecurity utility does not support the export of task list
access permissions for administrators. You must manually add
such records to the SecFile.txt file before you can import
them.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

For example, the Secfile.txt file might contain the following lines:
User1,Target,ReadWrite,MEMBER
User2,Europe,Read,@IDESCENDANTS
User2 Calc Expenses Launch MEMBER SL CALCRULE User2,Calc Expenses,Launch,MEMBER,SL_CALCRULE
User5,Customer Sales,ReadWrite,MEMBER,SL_COMPOSITE
Group1,Verify App,Read,MEMBER,SL_FORM
Group2,Verify BR,Read,@IDESCENDANTS,SL_FORMFOLDER
Group3,NA Expenses,ReadWrite,MEMBER,SL_TASKLIST
Note: Items within lines cannot have extra spaces between them.
To migrate access permissions with Lifecycle Management:
2. Perform one of the following actions to select the access permissions to be included in the
migration:
- Expand Application Groups, then an application group, and select a Planning p pp p , pp g p, g
application.
- Expand File System, then a file system name, and select a migration.
3. On the Artifact List tab, expand the nodes for Security.
- Select Security to migrate all users and groups.
- Select Groups, individual group names, or Users to migrate the selected artifacts. p g p g
- Click Export, specify the files system folder name, and click Export.
- Click Import, select the application name, and click Import.
The migration status report is displayed.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Exporting Access Permissions
with ExportSecurity with ExportSecurity
At the command prompt, run the ExportSecurity utility to
export access permissions.
The access permissions are exported by default to a text
file named SecFile.txt in the /oracle/middleware/ / / /
user_projects/epmsystem1/Planning/planning1
folder.
Example:
ExportSecurity /A Hyplan /U admin /S GROUP Sales ExportSecurity /A=Hyplan,/U=admin,/S_GROUP=Sales
For the example in the slide, you export access permissions from the Hyplan application for a
group named Sales.
To export access permissions with the ExportSecurity utility:
p p p y y
1. On the Windows taskbar, select Start, then Programs, then Accessories, and then
Command Prompt.
2. Enter oracle\middleware\user_projects\epmsystem1\Planning\planning1,
and press Enter to navigate to the planning1 folder.
3. At the command prompt, enter the following case-sensitive command and the required
parameters, separating the parameters with commas. If you specify only mandatory (not
ti l) t ll i i t ll tif t f ll d optional) parameters, all access permissions to all artifacts for all users and groups are
exported:
ExportSecurity /A=appname,/U=username,
[/S=searchCriteria| /S_USER=user| /S_GROUP=group], [/S_MEMBER=member|
/S_MEMBER_ID=member| /S_MEMBER_D=member| /S_MEMBER_IC=member|
/S_MEMBER_C=member],[/DELIM=delim],
[/DEBUG=true|false],[/TO_FILE=fileName]

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

/A=appname The name of the Planning application from which you are exporting
access permissions.
/U=username The administrators ID for logging into the application.
/S=searchCriteria Optional: The user or group name.
You cannot use this option with /S_USER or /S_GROUP.
/S_USER=user Optional: A specific username.
You cannot specify multiple users or use this option with
/S_GROUP or /S=searchCriteria.
/S_GROUP=group Optional: A specified group. Only matching groups, not matching
usernames, are exported.
You cannot specify multiple groups or use this option with
/S_USER or /S=searchCriteria.
/S MEMBER=Member Optional: A specified member You can specify only one /S_MEMBER=Member Optional: A specified member. You can specify only one
member-based parameter.
/S_MEMBER_ID=Member Optional: A specified member and its descendants.
/S_MEMBER_D=Member Optional: A specified members descendants.
/S MEMBER IC=Member Optional: A specified member and its children. _ _ p p
/S_MEMBER_C=Member Optional: A specified members children.
/DELIM=delim Optional: SL_TAB, SL_COMMA, SL_PIPE, SL_SPACE,
SL_COLON, SL_SEMI-COLON. If no delimiter is specified, comma
is the default.
/TO_FILE= Optional: Enter the path to the Secfile.txt file. By default, the file is
in the planning1 directory.
If you specify another path, use double backslashes; for example:
C:\\Oracle\\Secfile.txt.
/DEBUG=true|false Specify true to display the utilitys performed steps; false is the
default
4. At the password prompt, enter the password.
The access permissions are exported to the Secfiile.txt file.
default.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Importing Access Permissions
with ImportSecurity with ImportSecurity
Export or create a text file named SecFile.txt and save
the file in the /oracle/middleware/user_projects/
epmsystem1/Planning/planning1 folder.
At the command prompt, run the ImportSecurity utility to p p , p y y
load access permissions.
Example:
ImportSecurity.cmd Hyplan,admin,SL_CLEARALL
For the example in the slide, you clear all existing access permissions in the Hyplan application,
and import the access permissions to the application from the Secfile.txt file.
To import access permissions with the ImportSecurity utility:
p p p y y
1. On the Windows task bar, select Start, then Programs, then Accessories, and then
Command Prompt.
2. Enter
cd\oracle\middleware\user_projects\epmsystem1\Planning\planning1, and
press Enter to navigate to the planning1 folder.
3. At the command prompt, enter the following case-sensitive command and required
t ti th t ith d th E t parameters, separating the parameters with commas, and then press Enter:
ImportSecurity appname,username,[delimiter],[RUN_SILENT],[SL_
CLEARALL]
Note: Enclose the parameters with double quotation marks.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

delimiter Optional: SL_TAB, SL_COMMA, SL_PIPE, SL_SPACE, SL_COLON,
SL SEMI-COLON _
Comma is the default when no delimiter is specified.
RUN_SILENT Optional: Whether to execute the utility silently or with progress
messages, as follows:
0 = Execute with progress messages
1 = Execute silently, with no messages
If this parameter is not included in the command line the value is assumed
4 A h d h d
If this parameter is not included in the command line, the value is assumed
to be 0.
SL_CLEARALL Optional: Whether to clear all existing access permissions when importing
the new access permissions. This option must be in uppercase characters.
4. At the password prompt, enter the password.
The access permissions are imported into the Planning application.
5. At the command prompt, type exit, and press Enter to close the command prompt.
6. In Windows Explorer, navigate to the
oracle\middleware\user_projects\epmsystem1\diagnostics\logs\planning
folder.
7 Open the importsecuritylog txt file to display the log file and verify the results 7. Open the importsecuritylog.txt file to display the log file and verify the results.
9. Select the Database, Security Filters, and Shared Members options, and click Refresh.
A warning message is displayed.
10. Click Refresh.
A progress bar and status message are displayed.
11 Cli k Fi i h 11. Click Finish.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Security Filters
Create security
filters for all
users.
Create security
filters for a small
number of users.
Access permissions in Planning are stored in the relational database. If you use other products
outside of Planning, such as Financial Reporting, to access Planning data directly in Essbase, you
must push Planning access permissions to Essbase by generating security filters. Security
permissions for Planning are defined in Essbase security filters.
If a very large number of users need security filters, use the Refresh Database task to create all
filters at once.
If one or a few users need security filters, use the Security Filters task. For example, when you
promote an employee, the employees access permissions may change. In that case, create only
one security filter rather than all security filters.
To create security filters for all users: To create security filters for all users:
2. Select the Database and Security Filters options.
3. Select the Shared Members option to enable shared members to inherit the highest access
permission from the combination of access assigned to the base member and parent
member. If you do not select the Shared Members option, shared members inherit access
permissions from their base member. p

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

4. Click Refresh.
A warning message is displayed.
5. Click Refresh.
6 When the refresh is completed click Finish 6. When the refresh is completed, click Finish.
To create security filters for selected users:
1. Select Administration, then Manage, and then Security Filters.
2. Select one or more users.
3. Click Create .
4. At the confirmation prompt, click OK.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that planners can perform in Planning.
a. View and submit data.
b. Create and launch business rules.
c View and use task lists c. View and use task lists.
d. Create and maintain forms.
Answer: a, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the valid access permissions options for dimension
members, forms, and form folders.
a. Read
b View b. View
c. None
d. Write
Answer: a, c, d

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
In Planning, group permissions override individual permissions.
a. True
b. False
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that you must perform when you create an
import security text file.
a. Name the file Secfile.txt.
b Define all application users user groups and members in b. Define all application users, user groups, and members in
the file.
c. Insert blank lines between each section.
Answer: a

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe security in Planning
Provision users and groups in Shared Services
Assign access permissions to artifacts in Planning Assign access permissions to artifacts in Planning
Export and import access permissions
Create security filters

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Provisioning Users
Importing User and Group Security
Importing Forms and Artifact Security Settings Importing Forms and Artifact Security Settings
Verifying Imported Artifacts and Security Settings
Updating Security Filters

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

C ti F Creating Forms

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Objectives
At the end of this lesson, you should be able to:
Describe and manage simple forms
Describe and manage composite forms
Export and import forms Export and import forms

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Forms: Overview
Simple forms displayed as
tabs in a composite form
Simple forms
displayed as charts
Forms are spreadsheet-like grids with rows and columns for entering data. Forms are associated
with plan types and are stored in form folders. You can create as many forms as are needed, for
example, one form for standard expenses and another form for sales data.
To create forms, you define form properties and layout, other options, and business rules. You can
also assign access permissions to forms.
There are two types of forms:
The simple form displays a single form.
The composite form displays multiple forms simultaneously.
Folder Structures
Form folders enable you to organize forms. You can create as many folders as are needed, and
you can arrange the folders in a hierarchy.
Remember the following points when you manage form folders:
Do not move or delete the top-level folder named Forms. However, you can rename the
folder.
Move folders within the hierarchy as needed.
Assign access permissions to folders and forms.
Delete only empty folders.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Form Components
POV Page Columns
Rows Data Validation
Messages pane
You create forms by selecting dimensions and members for the point of view (POV), pages, rows,
and columns.
The members that you select in the POV determine the context for the pages, rows, and columns.
y p g , ,
For example, if the Scenario dimension is set to Budget in the POV, then data entered in the
pages, rows, and columns goes into the Budget scenario. For the example shown in the slide, the
POV includes the Currency and Customer dimensions.
For each POV dimension, you can select only one member, and you cannot change the selection.
However, you can use a dynamic user variable to change the POV if that option is enabled for the
form.
The page axis enables you to set up combinations of members that may span dimensions so that The page axis enables you to set up combinations of members that may span dimensions so that
you can work with data in smaller, logical views. For example, you assign the Entity and Version
dimensions to the page axis. For Entity, you select the children of South, such as the Georgia and
Texas members. For Version, you select the children of Version, such as the Draft 1 and Final
members. You can then switch members by selecting them from the page axis.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Rows and columns define the grid in which you enter data. For example, you assign the
descendants of Total Expenses to the row axis and descendants of YearTotal to the column axis.
When you open the form, you can enter data into the cell where the row for Advertising Expense
intersects with the column for Jan.
Composite forms are organized in sections. You can include multiple forms in a section and
display them as tabs. You can also display forms as charts.
You can specify cell colors and data validation messages that are generated on the form if entered
data violates a validation rule. Users can view validation messages in the Data Validation
Messages pane.
Form Requirements
Wh t th f ti k th f ll i it i i d di l t When you set the form properties, keep the following items in mind regarding plan types:
You must assign a plan type to the form.
You can include only members that are valid for that plan type in the form.
After creating a form, you cannot change its plan type.
When you save data in the form, the data is saved to the database that is associated with the
forms plan type.
When you set the form layout, keep the following rules in mind:
You must select at least one member for each dimension.
You must assign at least one dimension to the row axis and one dimension to the column
axis.
You cannot select the same dimension for more than one axis.
In order for a cell on a form to accept data entry:
All members in the POV, page, row, and column must be bottom-level members (except for
target versions)
For multicurrency applications, you must set the Currency dimension to the Local member
The user must have Write access to all members of the cell

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Simple Forms
Properties tab
Form plan type
Instructions for
the form
You create forms by selecting properties and business rules and by setting up the form layout.
On the Properties tab, you set basic characteristics for forms (name, description, and plan type).
You can also include instructions for planners who need to use the form.
p
To create simple forms:
1. Select Administration, then Manage, and then Forms and Ad Hoc Grids.
The Form and Ad Hoc Grid Management page is displayed.
2. In the view pane, select the folder where you want to store the form.
3. Click Actions, and select Create simple form.
The Properties tab is displayed The Properties tab is displayed.
4. For Form, enter a form name of up to 80 characters.
5. Optional: For Description, enter a description up to 255 characters.
6. For Plan Type, select the plan type to associate with the form.
7. Optional: Enter and format the form instructions.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

8. Click Next.
The Layout tab is displayed.
9. Set up the form layout, and select dimension members.
10 Define grid row column and dimension properties 10. Define grid, row, column, and dimension properties.
11. Define form display properties and printing options.
12. Optional: Define the Smart View option and form validation rules.
13. Optional: Perform the following actions:
- Click Next to display the Other Options tab.
- Select precision options, context menus, and dynamic user variables.
Click Next to display the Business Rules tab - Click Next to display the Business Rules tab.
- Assign business rules and properties to the form.
14. Click Finish to save and close the form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up the Form Layout
Property panel Layout tab
You assign dimensions to the POV, page, rows, and columns of forms on the Layout tab.
For each dimension, you select the members, and set the properties of the dimensions and
members in the POV, page, columns, and rows.
, p g , ,
For row and column members, you select properties, such as member name or alias,
hierarchy status (expanded or collapsed), and the display of missing data.
For rows, you can suppress missing blocks and missing data.
For rows, columns, pages, and POV, you can hide dimensions. For example, you can hide
dimensions on the point of view so that members for the POV dimension are not displayed
on the form. Hiding dimensions is especially helpful if the member for the point of view is No
Customer No Scenario or something similar Customer, No Scenario, or something similar.
Initially, all dimensions are in the form Point of View area. You can drag dimensions from the Point
of View area to the Page, Rows, or Columns area. You can also drag dimensions from any area in
the grid (Point of View, Page, Rows, or Columns) to any other area. When creating or editing
forms, you can add rows and columns to the form, as necessary.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To set up the form layout:
1. Create a form or open a form in the form designer, and select the Layout tab.
- For new forms drag dimensions from the Point of View area to the Rows and Columns - For new forms, drag dimensions from the Point of View area to the Rows and Columns
areas and (optionally) to the Page area.
- For existing forms, drag dimensions from any area in the grid to any other area.
3. Select members for each dimension.
4. Optional: Right-click in a row or column header, and perform an action:
- Select Add Row or Add Column to add rows and columns to the form.
- Select Delete Row or Delete Column to remove rows and columns from the form - Select Delete Row or Delete Column to remove rows and columns from the form.
- Select Move Row Up or Move Row Down to reorder rows in the form.
- Select Move Column Left or Move Column Right to reorder columns in the form.
Note: The available options depend on the number of rows and columns in the form and
on the row or column header that you select.
5. Optional: In a row or column with multiple dimensions, right-click the dimension name ,
and select Move Dimension Up or Move Dimension Down to reorder the dimensions in p
rows or columns.
6. Select the grid, rows, columns, and dimension properties.
7. Optional: Select Smart View and printing options, display properties, and set up validation
rules.
8. Click Save to save your work and continue, or click Finish to save your work and close the
form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Properties
You select grid, row, column, and dimension properties in the
Property panel.
When you set up the form layout, you can define grid, row, column, and dimension properties. You
can also select display properties, printing options, a Smart View option, and validation rules for
the form.
To set up properties:
2. In the Grid Properties area, select the general row and column properties for the grid.
3. Perform an action to display properties in the Property panel:
- Select a dimension in any area of the form to display the dimension properties.
- Select a row number or a column letter to display the segment properties. p y g p p
- Expand Display Properties to set the display properties for the form.
- Expand Smart View Option to display the option that enables the form to be used
offline.
- Expand Printing Options to display the printing options for the form.
4. Select or deselect properties in each property area.
5. Click Save to save your work and continue, or click Finish to save your work and close the y , y
form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Grid Properties
Form grid properties set the general form row and column display. Grid property options for rows
and columns are described in the following table:
Option Description
Suppress missing
blocks
(Rows only) Select this option to enhance performance of the Suppress
missing data setting. Use this option when you need to suppress a
large number of rows (90% or more).
If a few or no rows are suppressed, this option can degrade
performance.
Suppress missing data Select this option to hide rows or columns that have no data. If at least
one cell of a row or column has a data value, then the row or column is
not suppressed.
Clear this option to display rows or columns that contain only cells for
which data is missing; the cells display #missing or blank
If the selected column width is less than the width of the column contents, the excess data is
hidd f i til th l i id d Whil hidd th d t i t d d l l t d i
which data is missing; the cells display #missing or blank.
Default column width Select a column width (Small, Medium, Large, Size-to-Fit, or Custom).
Default row height Select a row height (Medium, Size-to-Fit, or Custom).
hidden from view until the column is widened. While hidden, the data is stored and calculated in
the form in the same way as data that is not hidden.
Regardless of the selected column width setting, you can adjust column width while you view a
form. Saving or refreshing the form saves the adjusted column width for the remainder of the
session.
Printed column widths are determined by the options that you select for page size and columns
per page. p p g
Segment Properties for Rows and Columns
Row and column properties define how rows and columns are displayed in forms. These
properties add to row and column display specifications that you define in the grid properties.
Options for row and column properties are described in the following table:
O ti D i ti Option Description
Apply to all rows or
Apply to all columns
Apply settings to all rows or columns; available when there are two or
more rows or columns. Clear this option to set different properties for
each row or column.
Hide Hide the row or column on the form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Option Description
Read-only Create a read-only row or column to enable comparison of old,
read-only data with new, editable data. y ,
Show separator Create a bold border before the row or column to visually distinguish
parts of the form.
Suppress hierarchy For columns, do not display line breaks. For rows, do not display
indentation.
Suppress missing data Hide rows or columns without data.
Row height or Column
width
For rows, select Default, Medium, Size-to-Fit, or Custom.
For columns, select Default, Small, Medium, Large, Size-to-Fit, or
Custom.
Default refers to the column width or row height that is defined at the
grid level.
Dimension Properties
You define dimension properties for dimensions in any area of the form. Options for dimension
properties are described in the following table:
Option Description
Apply to all row dimensions Apply properties to all row dimensions.
Apply to all column dimensions Apply properties to all column dimensions.
Apply to all page dimensions Apply properties to all page dimensions.
Apply to all POV dimensions Apply properties to all POV dimensions Apply to all POV dimensions Apply properties to all POV dimensions.
Member name Display the member name.
Alias Display the member alias.
Member Formula Display member formulas.
Hide dimension Hide the dimension.
Show consolidation operators Display consolidation operators.
Start expanded Initially expand the row or column member list.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Form Display and Printing Options
You select display properties and printing options in the
Property panel.
When you set up the form layout, you can also select display properties and printing options for
the form.
Display Properties
p y p
Form display properties are described in the following table:
Option Description
Make form read-only Ensure that data cannot be entered in the form. You
cannot set this option for composite forms.
Hide Form Hide the form so that users cannot select it in the view
pane. You may want to hide forms that are part of a
composite form or that you access from menus or task
lists.
Display missing values as blank Leave form cells empty where data does not exist. If
this option is not selected, empty cells display
#missing.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Option Description
Enable account annotations Enable users to add annotations to accounts if they have write
access to the individual Account, Entity, Scenario, and Version access to the individual Account, Entity, Scenario, and Version
members.
Allow multiple currencies
per entity
If the application supports multiple currencies, allow entities to
support multiple currencies regardless of the base currency.
Users can select the currency for displayed cell values in the
form.
Enable Mass Allocate Enable users to spread data across dimensions. Enable Mass Allocate Enable users to spread data across dimensions.
Enable Grid Spread Enable users to spread data across dimensions.
Enable cell-level document Enable users to add, edit, and view documents in form cells,
depending on access permissions.
Message for forms with no
data
Enter a specific message to indicate that the form contains no
data. Leave blank to display the following default text: There
To enable annotations for the account dimension, you must select:
Account as a row dimension
Scenario and Version as page or POV dimensions
Entity as a page, POV, or row dimension
Printing Options
p y g
are no valid rows of data for this form.
Printing Options
Printing options are described in the following table:
Option Description
Include supporting detail Include supporting detail in normal or reverse order as extra rows
in PDF files in PDF files.
Show comments Display text notes associated with cells.
Format data Apply number format settings from the form to the displayed data.
Show attribute members Display attribute members in PDF files.
A l i i A l f i i tti t th di l d d t i PDF fil Apply precision Apply form precision settings to the displayed data in PDF files.
Show currency codes If the form supports multiple currencies, display the currency
codes in the form and in PDF files.
Show account annotations If account annotations are enabled for the form, display them in
PDF files.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Managing Substitution and User Variables
Administrators define
substitution variables.
Planners select user variable
values in Preferences.
User variable
in the POV
Substitution variables
in the Page axis
Substitution variables act as global placeholders for information that changes regularly. Typically,
planners use substitution variables in forms and Financial Reporting reports when a value
references a member name across multiple forms or reports.
User variables enable selectable members on the row, column, page, or POV of forms. Before
planners can open a form that contains a user variable, they must select a value for the user
variable in Preferences.
The form in the slide shows the user variable, MyDivision (South), in the POV and the substitution
variable, BudYear (FY13), in the Page axis. Because dynamic user variables are enabled in the
form, you can change the selection for the user variable directly on the form or in Preferences.
Administrators create substitution variables Administrators and interactive users create user Administrators create substitution variables. Administrators and interactive users create user
variables.
To create substitution variables:
1. Select Administration, then Manage, and then Variables.
The Variables page is displayed.
2. Select the Substitution Variables tab.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

3. Click Action, and select Add.
The Add Substitution Variable dialog box is displayed.
4. In the Plan Type drop-down list, select All Plan Types or an individual plan type in the
application. pp
5. For Name, enter the substitution variable name.
6. For Value, enter the value for the substitution variable.
7. Click OK.
To modify to substitution variables:
The Variables page is displayed The Variables page is displayed.
2. Select the Substitution Variables tab.
3. Select a substitution variable.
The Edit Substitution Variable dialog box is displayed.
5. For Name, enter the substitution variable name.
6 F V l t th l f th b tit ti i bl 6. For Value, enter the value for the substitution variable.
7. Click OK.
Note: You can also create and modify substitution variables that apply to all applications by using
Administration Services.
To create user variables:
Th U V i bl i di l d The User Variables page is displayed.
2. Click Action, and then Add.
The User Variables dialog box is displayed.
3. In the Dimension Name drop-down list, select a dimension.
4. For User Variable Name, enter the user variable name.
5. Optional: Select Use Context to permit user variables to be used in form POVs. With this
tti l t d th l f th i bl h d i ll b d th t t f setting selected, the value of the user variable changes dynamically based on the context of
a form.
6. Click OK.
To select members for user variables:
1. Select File, and then Preferences.
The Preferences dialog box is displayed.
2 f 2. In the left pane, click Planning.
3. Select the User Variable Options tab.
4. For each user variable, select a member, click Save, and then OK.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Selecting Members
Display Properties
Keep Only options
Search
options
Selected members
For rows, columns, pages, and the POV, you select specific members and variables, or you select
members and variables based on relationships, attributes, levels or generations. You can perform
the following actions for available members:
Expand and collapse member hierarchies.
Search for members by member name, alias, description, and UDA.
Display member properties, such as member name, alias, description, and count.
Keep members based on functions, attributes, levels, or generations.
When you select members for rows and columns, you can place the members on separate rows or
columns so that you can reference them when you create formulas.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

When you select members based on relationships, you select the members dynamically by using
hierarchical and familial history terms to describe the roles and relationships of the members. The
following table describes some member relationship terms:
M b R l ti hi D i ti Member Relationship Description
Parents The member in the level above the selected member
Children All members in the level immediately below the selected
member
Siblings All members from the same level in the hierarchy that share the Siblings All members from the same level in the hierarchy that share the
same parent as the selected member
Children (inc) The selected member and its children
Ancestors All members above the selected member
Descendants All members below the selected member
Y l M b S l ti f th f ll i
Descendants All members below the selected member
Descendants (inc) The selected member and its descendants
Level 0 Descendants All descendants of the selected member that have no children
You can also use Member Selection for the following purposes:
Select members for ad hoc grids; for the mass allocate and grid spread tasks; for planning
unit hierarchies, validation rules, and financial reports; and for ASO database and BSO
database Integration.
Select members to copy or clear data.
Choose members for runtime prompts in business rules.
To select members: To select members:
2. In any area of the form, click Member Selector to the right of a dimension name.
The Member Selection dialog box is displayed.
3. Perform one or more of the following actions to view members in the Member Name pane:
- Expand the hierarchy as needed.
S l t di l ti - Select display properties.
- Keep only by functions, such as by descendants.
- Keep only by attribute, such as by Account Executive.
- Keep only by levels or generations, such as by level 1.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

4. In the Members Name pane on the left, select one or more members.
5. Perform one of the following actions to add members to the selected members list on the
right:
- Click Add to add the members.
- Click Function Selector and select a relationship option, such as Children or
Level 0 Descendants, to add the selected members and their related members.
6. Optional: Select members with user and substitution variables:
a. Select the Variables tab.
b. Select one or more user variables, or expand Substitution Variables, and select one
or more substitution variables.
c. Click Add or click Function Selector and select a relationship option to add the
variables.
7. Optional: Select members with attributes:
a. Select the Variables tab.
b. Expand Attributes, and select one or more attributes.
c. Click Add to add the attributes.
8. Optional: For separate member selections, select Place selections in separate rows or
Place selections in separate columns.
9. Click OK to return to the form layout.
To enter data in a form, you must ensure that the form meets certain conditions:
- Bottom-up versions Set dimensions on rows and columns to level-0 members, and
set the Currency member to Local. If you set a dimension in the POV or the page axis
to a parent member, all rows and columns are read-only.
- Target versions You can enter data in both parent and level-0 members. You must
set the Currency dimension in the rows and columns to the Currency or Local member.
Keep the following points in mind when selecting members for forms:
The order of members in the selected members list determines the order on forms.
By default, selected members are placed in one row or column in the form. You can place
b t d l t f th i f l t l diff t members on separate rows and columns to reference them in formulas or to apply different
properties to the rows or columns. For example, you make one row read only and suppress
missing data in another row.
For multiple dimensions in a row or column, you can set member selection options for a
dimension by selecting that dimension from the Dimensions drop-down list.
Values entered into shared members are saved to the base members in the database.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Other Options
On the Other Options tab, you can set the forms precision, context menus, and dynamic user
variables.
Form precision defines the minimum and maximum values for the number of decimal positions to
p p
display in a cell. For currency values, you can specify the values or use the precision setting
defined for Currency dimension members.
You can associate menus with forms. If you select multiple menus, you can set the order in which
they are displayed. Multiple menus are displayed sequentially, with separators between them.
You can enable dynamic user variables in forms. User variables are selectable members on the
row, column, page, or POV of the form. For example, for the Current Scenario variable, you select
the Actual member to view actual data and the Budget member to enter budget values the Actual member to view actual data and the Budget member to enter budget values.
Before you can open forms that contain user variables, you must select the values for the user
variables in Preferences.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To set up other options:
1. Create a form or open a form in the form designer, and select the Other Options tab.
2. In the Precision area, perform the following actions:
- For Currency values select minimum and maximum values for the number of decimal - For Currency values, select minimum and maximum values for the number of decimal
positions to display in a cell, or select Use Currency member precision setting.
- For Non-currency values and Percentage values, select minimum and maximum
values for the number of decimal positions to display in a cell.
3. In the Available Menus list in the Context Menus area, select one or more menus, and click
Move to move them to the Selected Menus list.
4. Expand Dynamic User Variables, and perform the following actions to allow dynamic user
variables in the form:
- Select Enable dynamic user variables.
- In the Available User Variables list, select one or more user variables, and click Move
to move them to the Selected User Variables list.
form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Assigning Business Rules
Selected business
rules for the form
You create business rules by using the Calculation Manager graphical user interface. You launch
the business rules directly from Planning or you associate them with forms. The example in the
slide shows three business rules that are assigned to the Standard Expenses form.
Both designers of forms and planners who enter data in forms can see and launch only the
business rules to which they have access.
Planning includes two business rules that are selected by default:
Calculate Form Automatically created to calculate subtotals in forms. Clear the rule to
prevent planners from calculating data.
Calculate Currencies Created for forms that include multiple currencies in a row, column,
t bl th i f l th il bl i Cl th l if or page to enable the conversion of values among the available currencies. Clear the rule if
you use customized scripts to calculate currency conversions.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

After entering data in a form, you must calculate new totals for parent members for sparse
dimensions (use the Calculate Form business rule). The rule calculates totals only for the
members that are visible on the form. For example, if the North America entity and its descendents
are part of the page axis, and the form displays the South entity, after you save, run the Calculate
F b i l d f h th f t t l di l d f S th B N th Form business rule, and refresh the form, new totals are displayed for South. Because North
America, the parent of South, is not displayed in the form, a new total for North America is not
calculated.
Administrators and interactive users can define business rules that prompt users for such
variables as members, text, or numbers. Create prompts that are specific and that let the user
know what type of data is expected. Here are examples of runtime prompts:
Enter position name. p
Enter start date.
Select a parent entity.
Be aware of the following:
When you launch a business rule with a runtime prompt, Planning validates the entered
value, but it does not validate the business rule.
The order in which business rules are launched is important and may affect the data. If you p y y
launch conversion and subtotal business rules, you must run the currency conversion rules
before the subtotal rules.
To assign business rules:
1. Create a form or open a form in the form designer, and select the Business Rules tab.
2. In the Plan Type drop-down list, select the plan type.
3. In the Business Rules list, select the business rules to assign to the form, and click Add to
move them to the Selected Business Rules list.
4. Optional: In the Selected Business Rules list, select a business rule and click
Move Up or Move Down to change the order of the business rules.
5. Optional: Expand Business Rule Properties, and perform one or more of the following
options for each business rule:
- Select Run on Load to launch business rules automatically when you open the form.
S l t R S t l h b i l t ti ll h th f - Select Run on Save to launch business rules automatically when you save the form.
- If the business rules has runtime prompts, select Use Members on Form to match the
default member selection in the runtime prompt window to the current members in the
page and POV axes of the form.
- Select Hide Prompt to hide the runtime prompt value from the user.
This selection automatically selects the Use Members on Form property.
6 Click Save to save your work and continue or click Finish to save your work and close the 6. Click Save to save your work and continue, or click Finish to save your work and close the
form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Composite Forms
Enter the form name,
description, and instructions
on the Properties tab.
Select the form layout
on the Layout tab.
2-Row
Layout
2-Column
Layout
Custom
Layout
You can create composite forms to view several forms simultaneously and perform the following
tasks:
Display two or more forms on one screen, and select whether to display the forms as charts.
p y , p y
Perform real-time impact analysis by entering data in one form (for one plan type) and
viewing calculated results in another form (for the same or another plan type).
Choose the order that forms are displayed on the screen and whether to display the forms as
tabs.
Choose whether to combine the POV and page dimensions.
You create composite forms by selecting properties and business rules and by setting up the form
layout.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To create composite forms:
1. Select Administration, then Manage, and then Forms and Ad Hoc Grids.
The Form and Ad Hoc Grid Management page is displayed.
2 Select the folder where you want to store the form 2. Select the folder where you want to store the form.
3. Click Actions, and select Create composite form.
The Properties tab is displayed.
4. For Form, enter a form name up to 80 characters.
5. Optional: Perform one or more of the following actions:
- For Description, enter a description up to 255 characters.
Select Hide Form to hide the form in the view pane - Select Hide Form to hide the form in the view pane.
- For Enter Instructions, enter form instructions, and format the text.
6. Click Next.
The Layout tab is displayed.
7. In the Select Layout area, select one of the following layout options:
- Select Custom Layout to create your own composite form layout.
S l 2 R li h f i i f h h d - Select 2-Row Layout to split the form into two sections, one on top of the other and
divided by a horizontal line.
- Select 2-Column Layout to split the form into two side-by-side sections divided by a
vertical line.
8. At the confirmation prompt, click OK.
The selected layout is displayed on the Layout tab.
9 Select forms for each section of the composite form 9. Select forms for each section of the composite form.
10. Set section, POV, and page properties.
11. Optional: Perform the following actions to add business rules to the form:
- Click Next to display the Business Rules tab.
- Assign business rules and properties to the form.
12. Click Save to save your work and continue, or click Finish to save and close the form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Composite Forms
Display Forms
as Tabs.
2-Row Layout splits
composite form into top
and bottom sections.
You add one or more simple forms to each section of the composite form. When you split a
section that contains simple forms, the forms remain in the original section. For example, if you
split a section vertically, the original section is divided into two side-by-side sections. The forms in
the split section are included in the left section, and the right section is empty.
When you delete a section, its simple forms are also deleted from the composite form, unless they
are included in other sections of the composite form.
After adding simple forms to a section, you can set the form to display as a chart and define the
chart properties, such as the type of chart and the position of the chart legend.
The example in the slide shows the Layout tab of a composite form. The form is set up to display a
two row layout that is split into top and bottom sections The Section Properties are displayed for two-row layout that is split into top and bottom sections. The Section Properties are displayed for
the top section, which includes two forms. The option to display the two forms as tabs is selected.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To set up composite forms:
1. Create a composite form or open a form in the form designer, and select the Layout tab.
2. In each section of the form, click Show Menu , and select Add Form.
The Form Selector dialog box is displayed The Form Selector dialog box is displayed.
3. Select one or more forms, and click OK to add them to the section.
4. Optional: Right-click a form, and perform the following actions to display the form as a chart:
- Select Display as Chart.
The Chart Properties dialog box is displayed.
- On the Chart Type tab, select the type of chart: Bar, Horizontal Bar, Line, Area, Pie, or
Scatter Scatter.
- Select the Options tab.
- Select the location of the chart legend and label.
- Click OK.
5. Optional: In a section of the form, click Show Menu , and select the following layout
options to control form display:
- Split Horizontally Split the section into two sections one above the other Split Horizontally Split the section into two sections, one above the other.
- Split Vertically Split the section into two side-by-side sections.
- Delete Section Delete the section from the form.
- Group as Tabs Display the forms in that section as tabs.
- Ungroup Tabs Clear the Group as Tabs option.
6. Optional: Expand Section Properties, select a form, and perform any of the following
actions: actions:
- Click Move to Top , Move Up , Move Down , or
Move to Bottom to change the position of the form.
- Click Edit Form Label to change the label of the form.
- Click Remove Forms to delete the form from the section.
7 Optional: Expand Section Properties and perform any of the following actions: 7. Optional: Expand Section Properties, and perform any of the following actions:
- Define the name, height, width, and number of forms per row or column.
- Select Set scope for all common dimensions as global to set Global as the scope
for all common dimensions.
form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting POV and Page Properties
Global Layout Dimensions area Common Dimensions area
The composite form POV and Page Dimensions properties specify where each dimension name is
displayed in a composite form. When you select a section in a composite form, the Property panel
displays the following options:
Set scope for all common dimensions as global (in Section Properties) Sets Global as
the scope for all common dimensions. The Common dimensions drop-down lists are set to
Global, and are not selectable for each dimension common to all forms in the section.
Global Layout Dimensions Lists the POV and Page dimensions that are displayed in the
composite form heading.
Common Dimensions Lists the POV and Page dimensions that are common to simple
forms in the selected section Sets the level of sharing of the dimensions to Local Section forms in the selected section. Sets the level of sharing of the dimensions to Local, Section,
or Global.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

You specify where common dimensions are displayed in composite forms. Common dimension
display options are described in the following table:
Option Location of Dimension Name
Local Simple form heading
Section Section heading
Only dimensions that are common to all simple forms in a
section and that contain the same members can be displayed in
Note: Only dimensions that are common to all simple forms in all sections of the composite form
and that contain the same members can be designated as Global.
To set POV and Page properties:
the section heading.
Global Composite form heading
2. Expand Common Dimensions.
3. For POV Dimensions and Page Dimensions, select Local, Section, or Global to specify
where the dimension name is displayed in the composite form.
4. Optional: In the Label column for a common dimension, enter a label for the dimension.
form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Setting Up Master Composite Forms
Simple forms refresh with
data for the relevant
member selections.
Apply context for the
N002 row from the
master composite form.
You can design composite forms that have one master form and multiple simple forms. When you
open this form for data entry or review, you can apply the context of the member selection in the
master composite form to the simple forms. The simple forms display only the details that are
relevant to the members selected in the master form.
For the example in the slide, the composite form includes a master composite form in the top
section. The master composite form displays the customer sales data for the total year for
Georgia. When you select the N002-Aspen National customer row in the master composite form
and apply its context to other forms on the page, the forms in the bottom section refresh with data
for the N002-Aspen National customer and the Georgia entity. The bottom forms are designed to
display additional detail for the selected customer, such as data for each period.
Note: You can have only one master composite form across all sections of the composite form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To set up master composite forms:
2. Right-click a form in one of the sections, and select Tag as Master Composite Form.
3 Click Save to save your work and continue or click Finish to save your work and close the 3. Click Save to save your work and continue, or click Finish to save your work and close the
form.
To filter data in simple forms that is relevant to the master composite form:
1. Open a composite form that includes a form designated as the master composite form.
2. Select the POV and page members for the master composite form and refresh the page.
3. Right-click a row in the master composite form, and select Apply Context.
The simple forms are refreshed with data that corresponds to the context of the data The simple forms are refreshed with data that corresponds to the context of the data
selected in the master composite form.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Reviewing Form Design
Close the preview.
While you design forms, you can review the dimensions that are assigned to the POV, columns,
rows, and page axes. The form displays member attributes, aliases, and data that are associated
with the form, although you cannot enter new data.
To review form design:
1. Open a form for editing.
2. Click Preview.
3. Review the POV, page, row, and column selections.
4. Optional: Select different members for the pages.
5. Close the form preview. p

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Exporting and Importing Forms
Use the FormDefUtil utility to export and import forms as
XML-based files between Planning applications.
Use Lifecycle Management to export and import forms by
plan type between applications and file systems. p yp pp y
FormDefUtil Lifecycle Management
You can use the FormDefUtil utility to export and import form definitions from and to XML-based
files and between Planning applications. For example, you can move forms from a development
environment to a production environment.
You run the utility in a command-line interface from the
MIDDLEWARE_HOME\user_projects\epmsystem1\Planning\planning1 directory.
Note: You cannot import form XML files into Planning 11.1.2.x if the files were exported from
earlier Planning versions.
With Lifecycle Management, you can migrate forms (Plan Type artifacts) between applications and
file systems. Keep in mind that any form dependencies, including dimensions, menus, user
variables and business rules must be met before you migrate forms variables, and business rules, must be met before you migrate forms.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

To export and import forms with FormDefUtil:
The command prompt window is displayed.
2 Enter CD 2. Enter CD
x:/oracle/Middleware/user_projects/epmsystem1/Planning/planning1 to
navigate to the folder that contains the utility.
3. Enter the FormDefUtil command to export or import forms, for example:
- formdefutil import -all <server-name> <user-name> <application-
name>
- formdefutil export -all <server-name> <user-name> <application-
name>
Note: Use all to import or export all XML files or form definitions in the current
application. You can also specify the name of the form or XML file to export or import.
4. For Enter password, enter your password.
The XML files are created in or imported from the Planning1 folder.
To migrate forms with Lifecycle Management:
2. Perform one of the following actions to select the forms to include in the migration:
- Expand Application Groups, select an application group, and then a Planning
application.
- Expand File System, and then a migration, and select a file system.
3. On the Artifact List tab, expand Plan Type, and then the plan type name.
- Select Data Forms to select all forms.
- Expand Data Forms, and select a folder name to migrate all forms in the folder.
- Expand Data Forms, then a folder name, and select the forms that you want to
migrate.
- Click Export to export the migration to the file system.
- Click Import to import the migration from the file system.
The migration status report is displayed.

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the tasks that you must perform to set up a form.
a. Select at least one member for each dimension.
b. Assign at least one member to the row and column axes.
c Assign at least two members to the column axis c. Assign at least two members to the column axis.
Answer: a, b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Composite forms can include multiple master composite forms.
a. True
b. False
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
Select the descriptions that are applicable to the page axis of a
form.
a. It enables you to set up combinations of members that
may span multiple dimensions. y p p
b. It may have members selected from a single dimension.
c. It may have members selected from multiple dimensions.
Answer: a, b, c

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Quiz
You can use the FormDefUtil utility to import simple and
composite form definitions from previous Planning releases into
Planning 11.1.2.x.
a. True
b. False
Answer: b

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Summary
Describe and manage simple forms
Describe and manage composite forms
Export and import forms Export and import forms

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

Creating Form Folders
Creating Simple Forms
Moving Forms and Deleting Folders Moving Forms and Deleting Folders
Creating Composite Forms
Setting Up Master Composite Forms and Charts
Reviewing Form Folder Access
Creating Forms to Convert Currencies (Optional) g ( p )
Performing Grid Diagnostics

O
r
a
c
l
e

I
n
t
e
r
n
a
l

&

O
r
a
c
l
e

A
c
a
d
e
m
y

U
s
e

O
n
l
y

D81987 - Oracle Hyperion Planning 11.1.2 Create & Manage Applications

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

D81987 - Oracle Hyperion Planning 11.1.2 Create & Manage Applications

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle Hyperion Planning 11.1.

Plan types Form

Detail expense accounts

Das könnte Ihnen auch gefallen

D81987 - Oracle Hyperion Planning 11.1.2 Create &amp; Manage Applications

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

D81987 - Oracle Hyperion Planning 11.1.2 Create &amp; Manage Applications

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle Hyperion Planning 11.1.

Plan types Form

Detail expense accounts

Das könnte Ihnen auch gefallen

D81987 - Oracle Hyperion Planning 11.1.2 Create & Manage Applications

D81987 - Oracle Hyperion Planning 11.1.2 Create & Manage Applications