Planning- Oracle Bootcamp 1

Hyperion Planning 9.3.1: Create and Manage Applications

y m

Volume I • Student Guide

e d a

D52599GC10 Edition 1.0 December 2007 D53078

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I ®

c A

Author

Copyright © 2007, Oracle. All rights reserved.

Sandy Krameisen

Disclaimer

Technical Contributors and Reviewers Bryan Dehmler-Buckley Suzanne Gill Vicki Hardiman Art Hetherington Lea Jensen Sandy Krameisen Ronald Reiley Eleanor Salerno Theresa Songco Shankar Viswanathan Stuart Weiner

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:

Editor

U.S. GOVERNMENT RIGHTS The U.S. Government’s 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.

Susan Moxley

Trademark Notice

Graphic Designer

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

y m

Carisa Cannan

e d a

Publisher Judy Gaitan

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Table of Contents

1

Preface Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Course Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Course Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Student Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Activity Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Module 1: Getting Started Lesson 1: Planning Overview Oracle’s Enterprise Performance Management System . . . . . . . . . . . . . . . . . . . . . . . 1-2 Oracle Business Intelligence Suite Enterprise Edition Plus . . . . . . . . . . . . . . . . . . . . . 1-4 Hyperion Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Additional Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Planning Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Client Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Application Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 Database Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14 EPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Planning Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 Planning and Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 Planning Repository and Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18 Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19 Dimension Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20 Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21 Dimensions and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22 Multidimensional View of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23 Drill-Down Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24 Essbase Terminology—Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25 Essbase Terminology—Families . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26 Essbase Terminology—Generations and Levels . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Table of Contents

Lesson 2: Navigating Workspace System 9 Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Workspace Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Launching Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Workspace User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 Workspace Navigate Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Opening Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Navigating in Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11 Reviewing Available Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11 Basic and Advanced Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 View Pane and Content Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 Opening Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Module 2: Creating Application Structures Lesson 3: Creating Dimensions Overview Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Planning Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Required Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Period and Year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Scenario and Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 HSP_Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Alias and Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 User-Defined Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Dense Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Sparse Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Data Block Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Determining the Number of Data Blocks in a Database . . . . . . . . . . . . . . . . . . . .3-11 Creating Data Blocks and Retrieving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Determining Data Structure and Performance of Data Blocks. . . . . . . . . . . . . . . 3-14 Selecting Aggregation, Storage, and Calculation Options . . . . . . . . . . . . . . . . . . . . . 3-15 Selecting Aggregation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 Selecting Data Storage Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 Calculating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21 Using Two-Pass Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22 Determining Performance Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O iv

Planning: Create and Manage Applications

Table of Contents

Lesson 4: Managing Dimensions with EPM Architect About Dimension Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Master View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Application View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 EPM Architect Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Adding Dimensions to Master View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Organizing Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Filtering Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Sorting Dimensions and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11 Creating Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 Modifying Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 Property Value Inheritance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 Managing Property Value Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 Creating Alternate Rollups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18 Managing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19 Moving Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19 Deleting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20 Renaming Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20 Reordering Children. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20 Inserting Members Using Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21 Finding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23 Creating Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25 Adding Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27 Number Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27 Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28 Triangulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28 Reporting Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28 Creating Associations Between Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

Lesson 5: Setting Up the Period, Scenario, and Version Dimensions Time Periods Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Period and Year Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Dynamic Time Series Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Setting Up Dynamic Time Series Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Choosing How Data Is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Scenario Dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

e l c

a r O

Planning: Create and Manage Applications

v

Table of Contents

Creating Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exchange Rate Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use Beginning Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-12 5-12 5-13 5-13 5-13 5-13 5-14 5-16 5-18

Lesson 6: Setting Up the Entity Dimension Entities Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entity Members and Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying the Currency Value for Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding and Modifying Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-2 6-3 6-5 6-6 6-8 6-9

y m

e d a

Lesson 7: Setting Up the Account Dimension

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

e l c a r O ly & On l a e n r s e t U n I

c A

Lesson 8: Creating User-Defined Elements

User-Defined Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attributes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing, Aggregating, and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Attribute Crosstab Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

e l c

a r O vi

8-2 8-4 8-5 8-5 8-6 8-8

Planning: Create and Manage Applications

Table of Contents

Assigning Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9 Member Formulas Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11 Adding Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12 Adding User-Defined Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14 Smart Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16 Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18 Modifying Smart Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20 Associating Smart Lists with Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22 Setting Data Forms to Use Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23

Module 3: Loading Metadata Lesson 9: Loading Metadata from a File Metadata Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Formatting Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 Load File Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Formatting Dimensions Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Formatting Members Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Formatting Hierarchies Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9 Formatting DimensionAssociation Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10 Loading Metadata Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12 Creating Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13 Mapping Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15 Mapping Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17 Running Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 Viewing Job Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19 Viewing Import Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 Loading Metadata from Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21 Interface Tables Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21 Setting Up Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

Lesson 10: Creating Application Views

Creating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimension Library Panes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Dimensions to Application Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Excluding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

e l c

a r O

Planning: Create and Manage Applications

10-2 10-4 10-5 10-7 10-8

vii

Table of Contents

Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9 Configuring Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11 Specifying Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Setting Up Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14 Removing Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16 Setting Up Dimension Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17 Choosing Performance Settings for Optimal Performance . . . . . . . . . . . . . . . . . . . 10-19 Dimension Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21

Lesson 11: Deploying Applications Deploying Applications Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2 Deployment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3 Validating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4 Comparing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6 Deploying Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8 Creating Essbase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10 Reviewing Planning Outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-11 Essbase Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-12 Redeploying Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-13

y m

Lesson 12: Setting Up Exchange Rates

e d a

c A

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

e l c

e l c a r O ly & On l a e n r s e t U n I

a r O viii

Planning: Create and Manage Applications

Table of Contents

Module 4: Loading Data and Calculating the Database Lesson 13: Loading and Calculating Data Overview Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 Requirements for Data Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 Multicurrency Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6 Setting Up Data Load Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7 Staging Data Using Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9 Data Calculation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10 Calculations Within Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11 Calculations and Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12 Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14

Lesson 14: Loading Data Loading Data Using Administration Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2 Creating Data Load Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3 Opening Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4 Defining Header Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6 Associating Column Fields with Dimensions and Members . . . . . . . . . . . . . . . . 14-8 Replacing Text Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10 Validating and Saving Rules Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12 Fixing an Invalid Rules File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13 Loading Data Using Rules Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14 Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16 Creating Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17 Loading Data Using Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

Module 5: Setting Up Security

Lesson 15: Provisioning Users and Groups

Planning Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Levels of Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Object Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

e l c

a r O

Planning: Create and Manage Applications

15-2 15-3 15-4 15-5 15-6 15-7

ix

Table of Contents

User and Group Provisioning Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8 User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9 Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10 Unassigned Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-11 Provisioning Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12 User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14 Generating Provisioning Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16

Lesson 16: Setting Up Access Rights to Planning Applications Assigning Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2 Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3 Inheritance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5 Precedence and Inheritance of Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7 Reporting on Access Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9 Importing Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10 Creating the Secfile.txt File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-11 Importing Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14 Creating Security Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16

y m

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

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Data Forms and Folders Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2 Data Form Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3 Creating Folder Structures for Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5 Data Form Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6 Considerations for Setting up Data Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7 Setting Data Form Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9 Setting Row and Column Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10 Selecting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14 Creating Substitution and User Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16 Creating Asymmetric Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17 Setting Page and Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18 Setting Options on the Other Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19 Identifying Missing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21 Selecting Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22 Previewing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24

e l c

a r O x

Planning: Create and Manage Applications

Table of Contents

Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting Business Rules on Composite Data Forms . . . . . . . . . . . . . . . . . . . . Printing Data Form Definition Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Access Rights to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17-25 17-26 17-27 17-28 17-29

Lesson 18: Customizing Data Forms Exporting and Importing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4 Creating Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6 Associating Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10 Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-11 System Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12 Custom Tools Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12 Current Application Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13 Managing User Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14 Creating User Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-15 Applying User Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16 Setting Up User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17 Setting Up E-mail for Workflow Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18 Applying Alias Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18 Setting Member Selection and Workflow Options . . . . . . . . . . . . . . . . . . . . . . . 18-18 Setting Individual Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19 Setting Individual Printing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22 Setting Individual User Variable Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

Module 7: Entering Data in Planning Lesson 19: Entering Data

Submitting Data in Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2 Elements on the Enter Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3 Data-Entry Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5 Viewing Form Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6 Recognizing Cell Color Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7 Navigating Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9 Copying and Pasting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-11 Working with Non-Aggregated Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-13

e l c

a r O

Planning: Create and Manage Applications

xi

Table of Contents

Saving and Refreshing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spreading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Balance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spreading Data Using Grid Spreader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spreading Data Using Mass Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adjusting and Annotating Plan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Ad Hoc Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Data to Spreadsheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Cell Text and Account Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Planning Unit Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Supporting Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating Data in Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate Data Form Calculation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate Currencies Calculation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering Data with Smart Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigating Data Forms with Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19-14 19-15 19-17 19-19 19-20 19-22 19-23 19-24 19-25 19-26 19-27 19-28 19-30 19-32 19-33 19-34 19-35 19-36

y m

e d a

Lesson 20: Entering Data in Smart View

Smart View Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2 Integrating Smart View with Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3 Smart View Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4 Establishing Data Source Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5 Planning and Smart View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8 Opening Data Forms in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9 Navigating Data Forms in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10 Entering Data in Smart View Using Data Forms . . . . . . . . . . . . . . . . . . . . . . . . .20-11 Adding Formulas to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13 Calculating Data in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15 Offline Planning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16 Taking Data Forms Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17 Working with Planning Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-19 Synchronizing Data to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O xii

Planning: Create and Manage Applications

Table of Contents

Module 8: Adding Business Rules Lesson 21: Creating Business Rules Business Rules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2 Business Rules Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4 Prerequisites for Accessing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5 Navigating Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6 Components of Enterprise View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6 Components of BR Language Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7 Navigating the Rule Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8 Business Rules Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9 Setting a Plan for Developing Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9 Launching the Rule Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-11 Adding Actions to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-14 Selecting Members for Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-17 Assigning Access to Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19 Launching Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-21 Launching Business Rules from Administration Services Console . . . . . . . . . . 21-22 Launching Business Rules from Planning – Data Forms. . . . . . . . . . . . . . . . . . 21-23 Launching Business Rules from Planning – Tools Menu . . . . . . . . . . . . . . . . . . 21-24 Printing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-25

y m

e d a

c A

Lesson 22: Building Runtime Prompts for Business Rules

e l c a r O ly & On l a e n r s e t U n I

Runtime Prompts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2 Adding Runtime Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4 Setting Up Runtime Prompts as Global Variables . . . . . . . . . . . . . . . . . . . . . . . . 22-5 Applying Runtime Prompts as Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . 22-8 Setting Up Runtime Prompts as Local Variables . . . . . . . . . . . . . . . . . . . . . . . . . 22-9 Specifying Limits for Runtime Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10

Lesson 23: Adding Formulas to Business Rules

Business Rules Formula Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building Formulas for Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components for Pro-Rata Ratio Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Pro-Rata Ratio Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Units-Rates Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

e l c

a r O

Planning: Create and Manage Applications

23-2 23-3 23-4 23-5 23-8

xiii

Table of Contents

Setting Up Variable Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9 Setting Up Custom Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-10 Specifying Data Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-11 Managing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-12

Module 9: Managing the Planning Process Lesson 24: Managing the Approval Process Process Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2 Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3 Planning Units and Process States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4 Reviewer Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-6 Impact of Entity Hierarchy on the Review Process . . . . . . . . . . . . . . . . . . . . . . . 24-8 Managing the Review Cycle for Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-10 Starting or Excluding Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-11 Checking the Status of Planning Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-13 Viewing the Details of Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-14 Printing Planning Unit Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-17 Copying Data Between Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-19 Copying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-21

y m

e d a

Lesson 25: Creating Task Lists

e l c a r O ly & On l a e n r s e t U n I

c A

Task Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2 Navigating Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4 Navigating Task Lists in Basic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5 Navigating Task Lists in Advanced Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8 Task List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-11 Working with Task List Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12 Building Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-14 Adding Tasks to Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-16 Setting Up Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-17 Setting Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-19 Assigning Access to Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-21 Validating Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-22 Reporting on Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-23

e l c

a r O xiv

Planning: Create and Manage Applications

Table of Contents

Module 10: Analyzing Planning Data with Financial Reporting Lesson 26: Financial Reporting Overview Financial Reporting Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2 Workforce Planning and XBRL Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-3 Financial Reporting Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5 Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7 Users, Groups, and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-8 Data Sources for Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-10 Financial Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-12 Working with Financial Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-13 Financial Reporting Studio Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-14 Viewing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-16 Opening Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-18 Report Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-19 Changing the User Point of View Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-20 Previewing and Printing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-21

y m

Lesson 27: Navigating Reports in Workspace

e d a

Workspace Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-2 Workspace User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-4 Workspace Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-6 View Pane Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-7 Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-8 Setting General Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-8 Setting Authentication Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-9 Setting Explore Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-10 Setting Financial Reporting Studio Preferences . . . . . . . . . . . . . . . . . . . . . . . . .27-11 Setting Financial Reporting General Preferences . . . . . . . . . . . . . . . . . . . . . . . 27-12 Browsing the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-14 Searching for Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-16 Previewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-17 Changing the User Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-19 Previewing the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-21 Limiting User Point of View Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-22 Changing Page Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-26 Printing Reports and Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-27

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

xv

Table of Contents

Integrating Reports into Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . . . Exporting Reports to Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Reports to Word and PowerPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Reports to Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . .

27-28 27-29 27-31 27-33

Module 11: Appendices Appendix A: Sharing Data Using Data Synchronization About Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Creating Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Creating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Specifying Source and Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6 Linking Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7 Setting Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8 Applying Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9 Inserting Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10 Validating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 Viewing Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12 Executing Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

y m

Appendix B: Working with Classic Application Administration

e d a

c A

Classic Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 Processes in Creating Planning Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 Planning Application Creation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6 Planning Relational Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7 Configuring Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8 Creating Applications Using Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . B-10 Accessing Classic Application Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11 Selecting the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12 Setting Up the Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13 Setting Up Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15 Setting Up Plan Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16 Completing Application Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18 Creating Essbase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19 Reregistering Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20 Building Member Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21 Working with Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23 Creating Alias Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25

e l c

e l c a r O ly & On l a e n r s e t U n I

a r O xvi

Planning: Create and Manage Applications

Table of Contents

Smart Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Smart List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Associating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Member Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Integration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Adapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Planning Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Planning DSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating UDA Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading Metadata to Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Planning Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Session Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-27 B-28 B-29 B-31 B-32 B-34 B-35 B-36 B-37 B-38 B-39 B-40 B-42 B-43 B-44

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

xvii

Table of Contents

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O xviii

Planning: Create and Manage Applications

Preface

0

Welcome to Hyperion Planning 9.3.1: Create and Manage Applications! Before you begin, please take a moment to review this section. The preface presents an overview of the following information: • Course objectives • Structure of the course • Course materials used in the class • Conventions used in the book

y m

Course Objectives

e d a

After completing this course, you should be able to: • Create Planning applications • Load data into Planning applications

e l c a r O ly & On l a e n r s e t U n I

• Set up security for users, groups, and members

c A

• Create data forms and enter data by using data forms • Set and test business rules

• Review budget data by using process management • Analyze planning results in Financial Reporting

a r O

e l c

Preface

Course Structure Hyperion Planning 9.3.1: Create and Manage Applications is a 5-day, instructor-led training course consisting of lectures, demonstrations, and hands-on exercises. In this course, the instructor presents a topic conceptually by explaining its purpose, demonstrating how it works, and then guiding the students through the exercises. Demonstrations and hands-on exercises reinforce the concepts and skills introduced during lectures.

Course Materials You use two books in class—the student guide and the activity guide. The instructor may also give you handouts.

Student Guide The student guide is designed to be used by students and the instructor during lecture time. It has 11 modules: • Module 1 describes an overview of Planning and navigating Workspace.

y m

• Module 2 describes setting up dimensions and members. • Module 3 describes importing dimension members using EPM architect.

e d a

• Module 4 describes loading data and calculating the database. • Module 5 describes setting up security. • Module 6 describes designing data forms.

e l c a r O ly & On l a e n r s e t U n I

• Module 7 describes entering data in Planning.

c A

• Module 8 describes adding business rules.

• Module 9 describes managing the planning process.

• Module 10 describes analyzing data with Financial Reporting. • Module 11 contains appendices which provide additional information about Planning not covered in this course. Each module contains lessons. Each lesson begins with a list of objectives followed by the presentation of slides and accompanying text. The lesson ends with a summary of the topics covered in the lesson.

e l c

a r O xx

Planning: Create and Manage Applications

Preface

Activity Guide The activity guide has two sections—exercises and exercise solutions. Exercises A critical part of the learning process is the challenge of completing real tasks associated with each lesson. Each exercise is an opportunity to apply your new knowledge. Exercise Solutions The exercise solutions present the detailed steps to successfully complete the exercises.

Conventions The following text conventions are used in this course book: • Text to be typed, options to be selected, names of files and modules, and menu selections are displayed in bold type. Examples: - Select Clear Profile. - Click YES to clear the profile. • When available, figures are used to identify an object or task. Example:

e d a

Click Edit.

• Keyboard shortcuts are displayed as follows: Ctrl+Enter

e l c a r O ly & On l a e n r s e t U n I

y m

c A

• Alerts are used to direct your attention to different types of information. NOTE

A note provides related information, common mistakes, or cautions about the current topic.

TIP

A tip provides information that helps you work more efficiently.

e l c

a r O

Planning: Create and Manage Applications

xxi

Preface

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O xxii

Planning: Create and Manage Applications

M O D U L E

1

Getting Started

0

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

y m

• Navigating Workspace

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

L E S S O N

1

Planning Overview

1

Objectives At the end of this lesson, you should be able to: • Describe Oracle’s Enterprise Performance Management system • Describe Oracle Business Intelligence Suite Enterprise Edition Plus • Describe the main features of Planning • Describe the product architecture of Planning

y m

• Describe the relationship between Planning and Essbase

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 1 Getting Started Lesson 1 Planning Overview

Oracle’s Enterprise Performance Management System

Integrates transaction, intelligence, and financial systems

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

y m

e d a

c A

Oracle’s Enterprise Performance Management System Oracle Business Intelligence (BI) is a portfolio of technology and applications that provides the industry's first integrated, end-to-end Enterprise Performance Management (EPM) system, including category-leading financial performance management applications, operational BI applications, BI foundation and tools, and data warehousing. It is pervasive, comprehensive, and hot-pluggable:

• Pervasive—Delivers intuitive, role-based intelligence for everyone in an organization from front line employees to senior management to enable better decisions, actions, and business processes. There is a common workspace and a range of real-time and event-based capabilities. It also covers all styles of reporting and analysis needs.

e l c

• Comprehensive—Integrates information from your financial performance management, operational intelligence, and transactional applications. It has a single integrated platform architecture and a unified enterprise information model.

a r O 1-2

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview • Hot-Pluggable—Uses your existing transaction systems, databases, and middleware applications. Oracle BI products are hot-pluggable with Oracle and nonOracle environments.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

1-3

Module 1 Getting Started Lesson 1 Planning Overview

Oracle Business Intelligence Suite Enterprise Edition Plus

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Oracle Business Intelligence Suite Enterprise Edition Plus Oracle Business Intelligence Suite Enterprise Edition Plus (Oracle BI EE Plus) is a comprehensive suite of enterprise BI products that delivers a full range of analysis and reporting capabilities. Featuring a unified, highly scalable, modern architecture, Oracle BI EE Plus provides intelligence and analytics from data spanning enterprise sources and applications—empowering the largest communities with complete and relevant insight. Oracle BI EE Plus bundles key Oracle Hyperion reporting products for integrated reporting with Oracle’s Hyperion financial applications.

e l c

a r O 1-4

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Hyperion Product Components Financial Performance Management Applications Financial Management Planning Strategic Finance Performance Scorecard Essbase Essbase Administration Services Provider Services Integration Services Reporting and Analysis

Workspace

Interact ive Reporting Web Analysis Financial Reporting SQR Production Reporting Data Management Data Relat ionship Management

y m

Data Integration Management Financial Data Quality Management

e d a

Foundation Services Shared Services Smart View

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Hyperion Product Components

c A

Oracle BI Suite Enterprise Edition Plus is a combination of Oracle BI Suite Enterprise Edition and Hyperion product components. Primary components of Hyperion products:

• Financial Performance Management Applications—A modular suite of integrated applications that support the entire financial management cycle of goal-setting, modeling, planning, monitoring, analysis, and reporting • Essbase—The business analysis server technology that provides an environment for rapidly developing custom analytic and enterprise performance management applications

e l c

• Reporting and Analysis—A suite of tools that enable you to create analytical, financial, and production reports as well as dashboards

a r O

Planning: Create and Manage Applications

1-5

Module 1 Getting Started Lesson 1 Planning Overview • Data Management—A packaged solution that enables organizations to integrate disparate sources of data across an enterprise, map data, and manage change • Foundation Services—A single, standardized infrastructure that facilitates the deployment of Hyperion product solutions and simplifies ongoing maintenance • Workspace—The Web client for Reporting and Analysis, Planning, and Financial Management. It enables you to access and interact with Hyperion-authored content as well as third-party documents, such as Microsoft Word and Excel files

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 1-6

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Planning Planning has the following features: ƒ Multidimensional data structure ƒ Target setting and bottom-up planning ƒ Iterative planning cycles ƒ Complex business rules and allocations ƒ Web-based data entry; management of the planning cycle ƒ Currency conversion for multicurrency applications ƒ Headcount and salary expense modeling ƒ Metadata and data transfer between Planning applications and other Hyperion products

Copyright © 2007, Oracle. All rights reserved.

Planning

e l c a r O ly & On l a e n r s e t U n I

y m

e d a

c A

Planning is a Web-based budgeting and planning solution that drives collaborative, event-based, operational planning processes through the organization for a wide range of financial and operational needs. Planners have the flexibility to adapt rapidly to changes in direction, ensuring that plans are always current, relevant, and functional. Powered by Essbase, Planning uses a multidimensional data structure for flexible data collection and analysis. Planning also supports driver-based plans that are based on global assumptions, such as interest rates and head count.

e l c

a r O

Planning: Create and Manage Applications

1-7

Module 1 Getting Started Lesson 1 Planning Overview

Product Components ƒ Planning ƒ Essbase ƒ Administration Services ƒ Workspace ƒ Business Rules ƒ Smart View ƒ Financial Reporting ƒ Shared Services

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Product Components

e d a

c A

You use the Planning Web interface to deploy applications to planning organizations. To extend the power and flexibility of Planning, you use it with other Hyperion products. Product Essbase

Administration Services

e l c

Workspace

ra

Business Rules

O

1-8

Description

Enables you to store Planning application data (Planning runs on top of Essbase.) Interfaces to Essbase Server, using Essbase Administration Services Console, and enables you to design, develop, maintain, and manage multiple Essbase applications and databases. Enables you to navigate and manage Planning within Workspace Enables you to use a graphical user interface to create calculation scripts

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview Product

Description

Smart View

Enables you to enter Planning data in Microsoft Excel spreadsheets, using the same functionality as Planning, and to take Planning data offline to work disconnected from the data source

Financial Reporting

Enables you to create reports and charts for Web or print for analysis and distribution of budget plans

Shared Services

Enables you to provision users from external systems to Hyperion products and to share data and metadata among Planning applications or between Planning and other Hyperion products

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

1-9

Module 1 Getting Started Lesson 1 Planning Overview

Additional Product Components ƒ Workforce Planning ƒ Capital Expense Planning ƒ Performance Scorecard ƒ Strategic Finance ƒ Financial Management ƒ Web Analysis

Enterprise Performance Management Solutions Hyperion System 9 Applications

Dashboarding and Scorecarding Modeling

Planning, Budgeting, and Forec asting

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Additional Product Components

y m

Consolidation and Reporting

e d a

c A

Several complementary Hyperion products are integrated with Planning, completing the Hyperion Business Performance Management solution. Product

Description

Workforce Planning

Enables you to handle workforce, salary, and compensation planning

Capital Expense Planning

Enables you to plan for new asset purchases and existing asset actions

Performance Scorecard

Enables you to communicate strategy, set goals, and measure and monitor business performance

e l c

Strategic Finance

a r O 1-10

Enables you to easily test financial models, create contingency plans, and form alternative strategies

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview Product

Description

Financial Management

Enables you to consolidate results, reduce the cost of regulatory reporting compliance, and gain important insights into performance

Web Analysis

Enables you to transform data into insightful information through easy-to-use, highly graphical displays and robust analytics

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

1-11

Module 1 Getting Started Lesson 1 Planning Overview

Planning Architecture Client

Administrator Client

Workspace

Smart View Client

Application Financial Reporting Server

Shared Services, Java Application Server for Planning, EPM Architect, Administration Services

EPM Architect Dimension Server

Web Server

Database EPM Architect RDBMS

P lanni ng RDBMS

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Planning Architecture

y m

e d a

Essbase

c A

Planning is a multitier application that combines the advantages of Essbase (a multidimensional database) with the advantages of a relational database to optimize performance and maintenance.

Client Tier

The client tier contains the administrator client, Workspace, and the Smart View client. Planning administrators use the client tier to enter data, perform process management, manage users and security, launch business rules, copy versions, develop data forms, and perform other administrative tasks.

e l c

In the client tier, you can enter data through spreadsheets by using Smart View.

a r O 1-12

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Application Tier The application tier consists primarily of the following servers: • Financial Reporting server • Java Application server (for Planning, EPM Architect, and Essbase Administration Services) • EPM Architect Dimension Server • Shared Services server • Web server NOTE

The Web server can be on a separate machine or on the same machine as the Planning application server. The Web server enables you to access Planning applications from a Web client through a Web browser. The Web server uses Hypertext Transfer Protocol (HTTP) as the communications protocol.

y m

Database Tier

e d a

The database tier consists of a third-party relational database management system (RDBMS) and Essbase. The relational database is used primarily to store the application’s definition. The following information is stored in the RDBMS: • Application framework*

e l c a r O ly & On l a e n r s e t U n I

• Dimensions, dimension members, and properties*

c A

• Exchange rates*

• Member access (security filters)* • Data form design definitions • Planning units

• Annotations (planning unit, account, and cell text) • Supporting details

• Process management workflow status

e l c

NOTE

Items with an asterisk (*) are updated to the Essbase databases during application refreshes.

a r O

Planning: Create and Manage Applications

1-13

Module 1 Getting Started Lesson 1 Planning Overview

User Roles Shared Services Roles

Planning Roles

ƒ Administrator

ƒ Provisioning Manager

ƒ Dimension Editor

ƒ Administrator

ƒ Application Creator

ƒ Manage Models ƒ Interactive User ƒ Planner ƒ View User ƒ Offline User ƒ Mass Allocation

y m

ƒ Essbase Write Access

Copyright © 2007, Oracle. All rights reserved.

User Roles

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Planning meets the needs of multiple users within an enterprise-wide budgeting cycle. You can set up users with several different types of user profiles to reflect what access is needed. The following global Shared Services roles are also used in Planning: • Application Creator— Creates applications. This is a EPM Architect role. • Dimension Editor — Creates profiles and imports dimensions. This is an EPM Architect role. • Create Integrations — Creates Shared Services data integrations (the process of moving data between applications) using a wizard.

e l c

a r O

• Run Integrations — Views and runs Shared Services data integrations.

1-14

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

EPM Architect ƒ Create Metadata — Maintain a centralized collection of metadata for Hyperion products and add metadata to applications by using the EPMA interface — Load metadata by using flat files or metadata loaded and stored in interface tables — Build metadata by entering metadata directly into EPM Architect

ƒ Manage Applications — Create Planning applications — Create and work with Planning applications and dimensions, Smart Lists, UDAs, and member formulas

ƒ Synchronize data — Synchronizes data flow between Hyperion applications — Automate point-to-point transfer of data between Hyperion applications — Load data from an external flat file or a database table into Hyperion applications Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

EPM Architect

y m

e d a

c A

Enterprise Performance Management Architect (EPM Architect) is a feature set in Planning. EPM Architect enables budget administrators to manage, create, and deploy Hyperion applications within one interface. Using the Data Synchronization feature in EMP Architect, administrators can create data movement synchronizations between Hyperion applications, create data mappings for reuse, and create flat file and staging area mappings to import data into Hyperion applications.

e l c

a r O

Planning: Create and Manage Applications

1-15

Module 1 Getting Started Lesson 1 Planning Overview

Planning Interface ƒ Manage Planning components — Manage data forms, task lists, user variables, and Shared Services — Provision users and groups — Assign member access — Copy data (including supporting details) — View statistics and run administration reports

ƒ Enter data, supporting details, and annotations ƒ Run business calculations ƒ Manage Workflow — Managing the Planning process — Copying data between versions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Planning Interface

e d a

c A

Planning administrators use Workspace to access Planning. In Planning, Planning administrators can provide flexibility and user guidance to budget preparers (planners) by defining user variables and task lists. You can also define data forms for data entry and assign access to the appropriate users and groups. Budget administrators, budget analysts, and budget preparers can all enter and submit data for review and approval, run business calculations, and enter annotations.

e l c

a r O 1-16

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Planning and Essbase

EPM Architect Repository

Workspace Interface Planning Repository

Java Application Server

e d a

Essbase Server

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Planning and Essbase

y m

c A

Planning uses Essbase to store dimension hierarchies and consolidate data. When you deploy an application view, EPM Architect creates tables and appropriate values in your Planning relational database, creates an application and outline in Essbase without the need to refresh the cube from within the Planning Interface, and creates the HSP_Rates dimension for multi-currency applications. Planning stores the application definition in its own relational databases. It uses the definition information to create the necessary Essbase databases and security privileges for your application. The plan data that end users enter in a Planning application is stored in the Essbase databases created for the application.

e l c

Prior to application deployment, EPM Architect stores the application data in its own EPM Architect relational database.

a r O

Planning: Create and Manage Applications

1-17

Module 1 Getting Started Lesson 1 Planning Overview

Planning Repository and Essbase Planning Relational Database

Essbase

ƒ Security

ƒ Security

ƒ Metadata

ƒ Metadata

ƒ Foreign Exchange Rates

ƒ Foreign Exchange Rates

ƒ Process Management Details ƒ Annotations/ Cell Text/ Supporting Details ƒ Task Lists

ƒ Data

ƒ Preferences

ƒ Business Rules

ƒ Application Setup

ƒ Rule Files

ƒ Data Forms

ƒ Currency Calculation Scripts

ƒ User Variables

ƒ Substitution Variables

ƒ Smart Lists

ƒ Smart Lists (numerically) Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Planning Repository and Essbase

y m

e d a

c A

Dimensions and members are stored in the Essbase databases as well as the Planning repository. Data values are stored in Essbase. Some information is stored only in the Planning relational database. For example, planning unit annotations, account annotations, cell text, and supporting details are stored in the Planning relational database. You can report on these annotations and details with Financial Reporting. Smart list information is stored in both the relational database and the Essbase databases, however, smart list information is stored numerically in Essbase.

e l c

a r O 1-18

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Dimensions Structural elements of an application that describe and hold data. Account

Entity

Period

y m

Copyright © 2007, Oracle. All rights reserved.

Dimensions

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

1-19

Module 1 Getting Started Lesson 1 Planning Overview

Dimension Hierarchies Parent Child of GrossMargin; parent of Sales and OtherRevenues Descendants of GrossMargin

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Dimension Hierarchies

e d a

c A

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

e l c

a r O 1-20

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Metadata 3689.00 Net Sales Actual Final New York January

Data

Metadata

Alliance Merchandise

January Actual Final Net Sales for Alliance Merchandise in New York is 3689.00.

y m

Copyright © 2007, Oracle. All rights reserved.

Metadata

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Metadata is defined as the structural elements of an application that describe and hold data. Examples of metadata are dimension names, member names, properties, and security. For the example shown on the slide, the circled dimension member labels are the metadata. The metadata describes what the data value represents. The value for January Actual Final Net Sales for Alliance Merchandise for New York is $3,689.00.

e l c

a r O

Planning: Create and Manage Applications

1-21

Module 1 Getting Started Lesson 1 Planning Overview

Dimensions and Data Data aggregates to parents based on aggregation options. + Add

Data is input into base-level members.

- Subtract * Multiply / Divide ~ Ignore

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Dimensions and Data

e d a

c A

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

e l c

a r O 1-22

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Multidimensional View of Information Profit Total E xp. Margin Cogs East West Actual Budget Actual Budget TV

V CR

Jan Feb Mar Qtr 1 Jan Feb Mar Qtr 1

Denver LA SF West February March Actual Budget Actual Budget Sales

Camera TV VCR Audio Margin Camera TV VCR Audi o Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Multidimensional View of Information

y m

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

1-23

Module 1 Getting Started Lesson 1 Planning Overview

Drill-Down Process

Period

Entity

Account

Customer

Year

Worldwide

Profit

All Customers

Quarter

N America

Sales

Retail

Month

East

COGS

Sears

Week

New York

Expenses

Dept 10

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Drill-Down Process

y m

e d a

c A

Drilling down is a specific analytical technique by which you navigate through levels of data, ranging from the most summarized (top) to the most detailed (bottom).

e l c

a r O 1-24

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Essbase Terminology —Hierarchies

Outline

Dimensions Members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Essbase Terminology—Hierarchies

e d a

c A

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

Definition

Outline

Representation of the relationship among the members in the database

Dimension Member

e l c

Attribute

Attribute dimension

a r O

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

Planning: Create and Manage Applications

1-25

Module 1 Getting Started Lesson 1 Planning Overview

EssbaseTerminology —Families

Period Year Total Qtr1 Qtr2 Year Total April Qtr1 Qtr2 April

Dimension

Ancestors of April

Descendants of Year Total

Siblings

y m

Parent of April

e d a

Child of Qtr2

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Essbase Terminology—Families

c A

The following table summarizes the common familial terminology used in Essbase. Familial Term Parent

Definition

Member that has at least one child member immediately below it

Child

Member that has a parent immediately above it

Sibling

Child member at the same branch level as another child member with the same parent

Ancestor

e l c

Descendant

Any member in a branch above a member Any member below a parent

a r O 1-26

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

EssbaseTerminology —Generations and Levels Level 3 Level 2 Level 1

Gen 1 Gen 2 Gen 3 Gen 4

Level 0 Leaf Node

Level 0

Gen 3

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Essbase Terminology—Generations and Levels

e d a

c A

The following table summarizes the common generation terminology used in Essbase. Generation Term

Definition

Generation

Position within the hierarchy of a dimension, counted from top to bottom

Level

Position within the hierarchy of a dimension, counted from bottom to top

Leaf node

Member that has no children

The term generation describes a member’s location within the outline hierarchy from a particular perspective. The generation number identifies the branch on which the member lies in reference to its distance from its dimension name. Generations are counted from the top of their dimension down through their descendants.

e l c

a r O

Level describes a member’s location in the outline, counting from the bottom to the top. The example on the slide shows a portion of an outline labeled by both generation and level. Planning: Create and Manage Applications

1-27

Module 1 Getting Started Lesson 1 Planning Overview

Summary In this lesson, you should have learned to: • Describe Oracle’s Enterprise Performance Management system • Describe Oracle Business Intelligence Suite Enterprise Edition Plus • Describe the main features of Planning • Describe the product architecture of Planning • Describe the relationship between Planning and Essbase

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 1-28

Planning: Create and Manage Applications

L E S S O N

2

Navigating Workspace

2

Objectives At the end of this lesson, you should be able to: • Describe the user interface components • Access Planning through System 9 Workspace • Navigate Planning

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 1 Getting Started Lesson 2 Navigating Workspace

System 9 Workspace Workspace BI+

Planning

Manage E nterprise Financial Information

Hyperion Applications

e d a

Planning Output Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

System 9 Workspace

y m

c A

Workspace provides a centralized interface for viewing and interacting with content created using Hyperion System 9 financial applications, such as Planning and Financial Management, and reporting content. Workspace provides the following benefits:

• Single user logon: Users log on to Workspace to access both BI+ reporting content and Planning. • Single console for application management and creation: Users create, manage, and deploy applications from a single location. These applications are opened in Planning for data retrieval and data output.

e l c

• Centralized repository of key dimensional elements for Hyperion products

a r O

• Centralized console for controlling data flow between applications

• Audit logging and process controls

2-2

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace

Workspace Overview Manage applications

View reports

Work with Planning

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Workspace Overview

e d a

c A

Workspace provides a single EPM interface to users. From Workspace, you can perform the following tasks: • Build and manage applications

• Execute planning application tasks

• Perform consolidation application tasks

• Run or view highly formatted financial and operational reports from most data sources, including from Planning and Financial Management • Conduct high-performance, multidimensional modeling, analysis, and reporting with Analytic Services

e l c

a r O

• Using Interactive Reporting, generate ad hoc relational queries, self-service reporting, and dashboards against ODBC data sources

Planning: Create and Manage Applications

2-3

Module 1 Getting Started Lesson 2 Navigating Workspace • Run high-volume, enterprise-wide reporting for production reporting • Using Web Analysis, perform interactive ad hoc analysis, presentations, and reporting of multidimensional data • Generate enterprise metrics for management metrics and analysis and present information in easy-to-use, personalized, interactive dynamic dashboards • In addition, Workspace provides access to and interaction with other published content, like Word or Excel documents. Access to Workspace menus and toolbar features are based on which roles are assigned to and which modules are provisioned for the user.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 2-4

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace

Launching Workspace

The password is case-sensitive.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Launching Workspace

e d a

c A

You launch Workspace from a Web browser by using the following Uniform Resource Locator (URL) to display the logon page: http://:/workspace

You can obtain the Web server name and port number from the system administrator. To launch Workspace:

1. In your web browser, enter the Workspace URL, and press Enter. The Workspace Logon screen is displayed.

e l c

2. Enter your user name and password, and click Log On.

ra

The Workspace user interface is displayed.

O

Planning: Create and Manage Applications

2-5

Module 1 Getting Started Lesson 2 Navigating Workspace

Workspace User Interface Navigate Menu

Menu bar

Standard toolbar

Module toolbar

Standard toolbar

Process bar Buttons

Adjuster

y m

Document tab bar

View pane

Content Area Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Workspace User Interface

e d a

c A

Workspace includes the following elements: Element Adjuster Buttons Content Area

Description

Adjusts the size of the view pane and content area Navigates between view pane displays

Displays active-module items, tasks, or files

Document tab bar

Displays information specific to the current module

Menu bar

Provides commands that organize tasks and modules

e l c

Navigate menu Process bar

a r O 2-6

Provides access to Workspace modules

Displays location of the current folder, item, or step

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace Element

Description

Standard toolbar

Provides shortcuts for performing tasks

View Pane

Provides buttons that enable jumps between panels

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

2-7

Module 1 Getting Started Lesson 2 Navigating Workspace

Workspace Navigate Menu To Access EPM Architect modules, select Navigate > Administer

y m

BPM Architect Menu

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Workspace Navigate Menu

e d a

c A

The Navigate menu enables you to select to navigate to the different modules available within Workspace. The following table describes the options on the Navigate menu: Option Explore Applications

e l c

Description

List and navigate through repository content and manage and control files and folders Access Hyperion System 9 Planning and Hyperion System 9 Financial Management applications (Applications are displayed only when a user has rights and applications are available.)

a r O 2-8

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace Option

Description

Administer > Dimension Library

• Manage dimensions from a centralized location • Create dimension import profiles for flat files and staging areas • Add, delete, and modify dimension members • Modify dimension and member properties

Administer > Application Library

• Create Planning, Financial Management, and Essbase applications that are based on Planning and Financial Management dimension sets • Manage all applications in one centralized location • View the data flow between applications • Migrate applications to different servers

Administer > Data Synchronization

• Create data movement synchronizations between Hyperion Applications (For example, an administrator can synchronize data in one Planning application to data in another Planning application. Administrators can also synchronize data from one Financial Management application to data in another Financial Management application and from a Planning application to a Financial Management application.)

y m

e d a

• Create data mappings that can be reused

• Create flat file and staging area mappings to import data into Hyperion Applications

c A

Administer > Application Upgrade

Upgrade from previous Planning and Financial Management releases

Administer >Library Job Console

View a summary of Dimension Library and Application activities, including imports, deployments, and data synchronizations

Schedule

Manage jobs and schedule batches and events for automated processing

Impact Manager

e l c a r O ly & On l a e n r s e t U n I

Administer > Classic Application Administration

e l c

Update Interactive Reporting documents when database structures, database connections, or links to external data sources change Create, delete, and register classic applications.

a r O

Planning: Create and Manage Applications

2-9

Module 1 Getting Started Lesson 2 Navigating Workspace

Opening Applications

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Opening Applications

e d a

c A

In Planning, all data is processed within applications. An application is a related set of dimensions and dimension members that meet a specific set of analytical or reporting requirements. For example, you can have an application named Test used for development and a separate application named Production to roll out to end users. To access Planning applications, select Navigate > Applications > Planning, and then select the application that you want to open. You can select Preferences from the File menu to make the application that is currently open the default application. When you log on, the default application is opened automatically.

e l c

a r O 2-10

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace

Navigating in Planning Planning Menus

Planning toolbar

View Pane

Open Application

e d a

Content Area

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Navigating in Planning

y m

c A

After you access Planning from the Navigate menu, the application displays in a window with a tab at the bottom left. Planning provides several tools for selecting tasks and documents: • Planning menus

• Planning toolbar • The View pane

Reviewing Available Menu Options

e l c

You have access to only those menu options to which you are assigned access based on your user profile. For example, users who are assigned the administrator role have access to all functions on the Administration menu. Users who are assigned the interactive user role have limited access to the Administration menu.

a r O

Planning: Create and Manage Applications

2-11

Module 1 Getting Started Lesson 2 Navigating Workspace File Menu The following table describes the commands under the File menu: New

Add a new document, personal page, data form, report, task list, or user variable

Open

Open a new document, application, or URL

Close

Close current, others, or all

Save

Save data inputted to data forms

Print

Print the current screen

Workflow

Manage the Planning process or copy versions

Spreadsheet Export

Export a data form to a spreadsheet

Preferences

Set general, authentication, explore, Web Analysis, Financial Reporting, Interactive Reporting, or Production Reporting preferences

Log Off

Log off Planning

Exit

Exit Workspace

e d a

Edit Menu The following table describes the commands under the Edit menu:

c A

Adjust

Increase or decrease data values by a percentage

Grid Spread

Spread data values across multiple dimensions on the grid

e l c a r O ly & On l a e n r s e t U n I

y m

Choose from allocation options: proportional, 4-4-5, evenly split

Mass Allocate

Allocate data values across multiple dimensions Choose from allocation options: proportional and relational spread, fill, 4-4-5, evenly split After the calculation executes, refresh the grid to see the result of the mass allocation Allocate data beyond what is displayed on data forms

Cut, Copy, Paste

Cut, Copy, or Paste data from one or more cells into one or more cells

Add Row

Add rows to a data form on-the-fly, only available if the data form was defined to allow rows to be added dynamically

e l c

Launch Rules

a r O 2-12

Launch a Business Rule from a data form

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace Annotate Planning Unit

Add comments to a planning unit; the comment can be plain text, a URL, or paths to servers

Cell Text

Add comments to a specific cell at any level in a data form

Lock/Unlock Cells

Lock cells to ignore cells when spreading data

Supporting Detail

Add detail that will aggregate the cell value in a data form

Initialize Workforce

Load predefined dimensions and members, data forms, smart lists, member formulas, business rules, and menus to prepare plans for workforce resources. Members, forms and business rules can be customized.

Initialize Capex

Load predefined dimensions and members, data forms, smart lists, member formulas, business rules, and menus to prepare plans for capital expenditures. Members, forms and business rules can be customized.

View Menu The following table describes the commands under the View menu:

y m

View Pane

Hide or show the View Pane

Refresh

Refresh the current view to reflect what is stored in the database

Instructions

View instructions for a data form, available only if the data form includes instructions

Currency

Look up a currency code

View Account Annotations

Enter, edit, or view comments for a specific account, entity, scenario, and version combination

Edit Account Annotations Basic Mode Task List

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Toggle the view for tasks between Basic Mode and Advanced Mode View task lists to which you have access; View task status and create a task list report

Administration Menu The following table describes the commands under the Administration menu:

e l c

Manage Data Forms

Create, edit, move, delete, and assign access to data forms

Manage Task Lists

Create, edit, move, delete, and assign access to task lists

Manage Menus

Create and edit menus

a r O

Planning: Create and Manage Applications

2-13

Module 1 Getting Started Lesson 2 Navigating Workspace Manage User Variables

Set up variables that are assigned to data forms by specifying the variable’s value

Manage Properties

Manage application and system properties

Dimensions

Set and change access for dimensions, such as account, entity, scenario, version, and user-defined custom dimensions

Copy Data

Copy data, including supporting details, from one planning unit to another

Reporting

Print data form definitions, user and group report lists, access assignments for dimensions, and planning unit annotations and process status lists and activate application auditing

View Statistics

View information about the Planning application and its usage

Application Settings

Set Planning application-wide preferences

Create Application

Create Classic applications

Delete Application

Delete Classic applications

Register Application

Register Classic applications with Shared Services

Copy Document Link

Link tasks in task lists to application pages

Manage Models

Manage metadata modules by performing version tracking, maintaining access control, and renaming and deleting models

Data Load Administration

Use the Data Load Administration page to set up the data to load directly into an Essbase database through Planning Adapter

Manage Database

Create and refresh Essbase databases with changes made to relational databases, such as with exchange rates updates

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

Manage Currency Conversion

Create currency conversion calculation scripts

Manage Exchange Rates

Create and set up exchange rate tables and exchange rates and delete exchange rate tables

Manage Security Filters

Create security filters for users

Favorites Menu You use the Favorites menu to select which favorites to show on the favorites menu. Tools Menu The following table describes the commands under the Tools menu:

e l c

Personalize

Show subscribed items and manage personal pages

Links

Manage links to other products or URLs

a r O 2-14

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace Install

Install Interactive Reporting Web Client and Smart View

Business Rules

Launch business rules

Broadcast Message

Create and send broadcast messages

Business Rules Status

View the status of business rules currently executing

Help Menu You can access help on the currently selected task or document. Planning Toolbar The toolbar buttons open dialog boxes that you can use to manage documents, task lists, and favorites and provide shortcuts to planning tasks.

The following table describes the buttons on the toolbar: Button

Purpose

Description

New Document

• Create Workspace document

y m

e d a

• Collect Reports in a book • Batch Reports for Scheduling Open Document

e l c a r O ly & On l a e n r s e t U n I

c A

Home

Workspace startup page

Explore

Display Workspace Folders in View Pane

Save

Save data input on data forms

Refresh

Refresh the data form with data stored in the database

Print

Print the current screen

e l c

ra

Open Workspace documents

Adjust

Increase or decrease values by a percentage

Lock/Unlock Cells

Lock or unlock cells when spreading data

O

Planning: Create and Manage Applications

2-15

Module 1 Getting Started Lesson 2 Navigating Workspace Button

Purpose

Description

Grid Spread

Spread data across dimensions on the data form

Mass Allocate

Run a Mass Allocate calculation

Cut, Copy, Paste

Cut, Copy, or Paste values from one or more cells to one or more other cells on data forms

Cell Text

Add comments to a specific cell at any level in data forms

Supporting Detail

Add detail that aggregates the cell value in data forms

Spreadsheet Export

Export data forms to a spreadsheet

Task List

Open task lists if task lists have been assigned to you

Status

Check task lists status

Logoff

Log off the application

Help

Access help for the currently selected task or document

Maximize content pane (on far right of navigation path)

Maximize or restore the content pane.

e l c

e l c a r O ly & On l a e n r s e t U n I

y m

e d a

c A

a r O 2-16

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Basic and Advanced Modes

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

2-17

Module 1 Getting Started Lesson 2 Navigating Workspace When you navigate in Advanced mode, you have access to all tasks, through menus and toolbars, to which you are assigned based on your role. You are not guided through a predefined list of tasks; you navigate freely to perform your tasks. When you switch between modes, you return to the activity that you were performing before you switched. For example, if you are working in a data form when you switch to Basic mode, you are returned to the same form when you return to that mode. To switch from Advanced Mode to Basic Mode: 1. Select View > Basic Mode. The View Pane is displayed listing task lists to which you have access. To switch from Basic Mode to Advanced Mode: 1. Select View > Advanced Mode. You have all menu functionality for your role and all functionality to which you are provisioned available to you.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 2-18

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace

View Pane and Content Area View Data Forms buttons

View Pane

y m

Business Rules

e d a

Content Area Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

View Pane and Content Area

c A

After you open a planning application, you see a View pane and a Content area. What is displayed in the View Pane and Content area depends on what selections you make. For example, when you work with data form management, the View pane lists form folders, data forms, and business rules. You can use the View pane to navigate from one folder or data form to another. After selecting a specific data form, you see the contents of that data form in the content area. If you select the launch business rules option from the Tools menu, you see the launch business rules dialog box in the Content area. However, the View pane lists form folders, data forms, and business rules. After you launch business rules, you can use the View pane to navigate away from the launch business rules dialog box and open a data form.

e l c

a r O

Planning: Create and Manage Applications

2-19

Module 1 Getting Started Lesson 2 Navigating Workspace

Opening Data Forms Select Folder

y m

e d a

Data Forms Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Opening Data Forms

c A

Data forms are contained within the folders. After you select a folder, a list of data forms within the selected folder is displayed on the View pane as well as in the content area. Only those forms to which you have access are displayed. You can select a data form from this list. After you select a data form, it is displayed in the content area.

e l c

a r O 2-20

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 2 Navigating Workspace

Summary In this lesson, you should have learned to: • Describe the user interface components • Access Planning through Workspace • Navigate Planning

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

2-21

Module 1 Getting Started Lesson 2 Navigating Workspace

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 2-22

Planning: Create and Manage Applications

M O D U L E

2

Creating Application Structures

2

Overview The aim of this module is to create dimensions and members for a Planning application. First, you identify required and user-defined dimensions. Next, you describe dense and sparse dimensions and basic concepts of data blocks. Finally, you create the dimensions and dimension members for the databases for your Planning application. Lessons in this module include: • Creating Dimensions Overview

y m

• Managing Dimensions with EPM Architect

e d a

• Setting Up the Period, Scenario, and Version Dimensions • Setting Up the Entity Dimension • Setting Up the Account Dimension

e l c a r O ly & On l a e n r s e t U n I

• Creating User-Defined Elements

a r O

e l c

c A

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

L E S S O N

3

Creating Dimensions Overview

3

Objectives At the end of this lesson, you should be able to: • Describe plan types • Identify required dimensions • Identify user-defined dimensions • Describe dense and sparse dimensions

y m

• Describe data block creation • Set up aggregation, data storage, and calculation options

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

Plan Types ƒ Essbase database created for each plan type ƒ Three customizable plan types ƒ Data sharing between plan types ƒ Set plan types for application views, dimensions and members

Budgeting Application

=

Plan Type 1

Plan Type 2

Plan Type 3

Workforce

Capex

Additional modules available for purchase

Copyright © 2007, Oracle. All rights reserved.

Plan Types

e l c a r O ly & On l a e n r s e t U n I

y m

e d a

c A

An Essbase database is created for each plan type. Plan types initially are set at the application level. You also select plan types for dimensions and members. You select one database in which to store data. Data values stored in one database are referenced by another databases, by sharing data for those members.

e l c

a r O 3-2

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

Planning Dimensions

Essbase

y m

Planning Repository Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Planning Dimensions

e d a

c A

Planning data is stored in Essbase databases. Data storage in Essbase is different from data storage in relational databases. Understanding how Essbase stores and retrieves data is important for designing an application that functions efficiently. Planning applications are organized by dimension. The dimensions in your application represent the categories of data in your organization. For example, when you enter data in a plan, you must identify what item you are budgeting. Budget items such as travel expense and salary expense are in the Account dimension. You also need to identify the time period for the item, such as current quarter or next quarter, located in the Period dimension.

e l c

How you set up dimension properties affects the storage and calculation of information, the efficiency of the database, and the display of information in data forms and reports. You can define aliases for dimension members and select to view either the alias or the member name in data forms and reports.

a r O

Planning: Create and Manage Applications

3-3

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

Required Dimensions Six Required Dimensions*

Other Dimensions

ƒ Period

ƒ Alias

ƒ Year

ƒ Smart Lists

ƒ Scenario ƒ Version ƒ Entity ƒ Account

*multicurrency applications require two additional dimensions ƒ Currency ƒ HSP_Rates

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Required Dimensions

y m

e d a

c A

A Planning application has six required dimensions.

Period and Year

You specify a time period and year for each value. Base time periods, such as months, are automatically rolled up to summary time periods, such as quarters and total year. As administrators, you specify base time periods and distribution of weeks in the Period dimension when you create application views. You use the Year dimension to add years to the calendar.

e l c

Scenario and Version

The Scenario and Version dimensions represent the broadest categories of data in your application. Scenario describes the type of data that a plan includes, such as budget, actual, or forecast, as well as the time span that the plan covers.

a r O 3-4

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

Version allows for flexibility and iterative planning cycles. For example, your application could have two versions, Working and Final, for each scenario. You can also use versions to model possible outcomes based on different assumptions about interest rates, growth rates, and so on. For example, your application can have a Best Case and Worst Case version for each scenario.

Entity The Entity dimension represents the flow of Planning information through your organization. You can establish an entity for each group or responsibility center that submits a budget plan. These units could be geographic regions, departments, or divisions, depending on your requirements.

Account The Account dimension specifies the data to be collected from budget planners. You can establish accounts for all budgeted items to the necessary level of detail. Examples of accounts are Rent Expense and Cash on Hand.

y m

NOTE

For dimension member names and alias names, you can include up to 80 characters, and you must make the name unique across all dimensions. You can include the characters %, &, $, #, (), *, ^, - and _ in the member and alias names. You cannot include \ / : ? < > | in the member or alias names.

e d a

Currency

e l c a r O ly & On l a e n r s e t U n I

c A

You can plan in one or more currencies. The Currency dimension identifies the currency in which values are displayed. In the Currency dimension, you set up the following categories: • Which currencies are used by applications and reporting • How currencies are displayed in reports and data forms • How currencies are translated into other currencies • When currency conversions occur

e l c

a r O

Planning: Create and Manage Applications

3-5

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

HSP_Rates This dimension contains a member to store exchange rate values for each currency. It also contains a member for input values and currency overrides. NOTE

The system generates the dimension HSP_Rates for multicurrency applications. This dimension is visible only in Essbase.

Alias and Smart Lists In addition to the required Planning dimensions, you must set up an Alias dimension if you want to assign aliases to dimensions such as Account or Entity. If you want to use Smart Lists in your application, you must set up a Smart List dimension.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 3-6

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

User-Defined Dimensions 14 User-Defined Dimensions* For example: ƒ Employee ƒ Product ƒ Channel ƒ Project ƒ Customer *A Planning application can have a total of 20 dimensions. The number of user-defined dimensions available varies between multicurrency and noncurrency applications.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

User-Defined Dimensions

e d a

c A

If your organization requires further levels of plan detail than is provided in the Account dimension, you can include user-defined dimensions or custom dimensions. For example, your application can have a group of revenue accounts for revenue planning. It can have a dimension called Customer that you can use with the revenue accounts to budget revenue on a per-customer basis. An application can have up to 14 user-defined dimensions. Using EPM Architect, you assign valid plan types for user-defined dimensions at the dimension level, not the member level. You cannot delete user-defined dimensions after you create them. You can assign access permissions to members in Planning. You can rearrange the dimension hierarchy, and share members of user-defined dimensions just as you can with other dimensions by using EPM Architect.

e l c

a r O

Planning: Create and Manage Applications

3-7

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

Dense Dimensions

Dense Dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Dense Dimensions

e d a

c A

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

e l c

a r O 3-8

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

Sparse Dimensions

Sparse Dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Sparse Dimensions

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

3-9

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

Data Block Creation ƒ Data is stored in data blocks. ƒ Data blocks are the cells formed by the intersection of selected dimension members. Members of Dimension A

Members of Dimension B

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Data Block Creation

e d a

c A

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

e l c

a r O 3-10

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

Determining the Number of Data Blocks in a Database Entity (Sparse)

Scenario (Sparse)

Year (Sparse)

Version (Sparse)

Entity Corp

Scenario Budget

Year 2007

Version 1 st Draft Final

Account (Dense) Period (Dense) Account Account1 Account2 Account3

Period Jan to Dec

y m

Each block contains 36 cells = (3 Accounts * 12 Time Periods)

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Determining the Number of Data Blocks in a Database

The dense and sparse settings for dimensions determine the structure of the data blocks and the number of data blocks in the database. The dense dimensions determine the data block structure. A data block always includes all stored members of all dense dimensions. By default, Account and Period are dense dimensions in Planning applications. NOTE

If your application uses currencies, the dense dimension HSP_Rates stores exchange rates.

e l c

The data in a data block is stored at the intersections formed by the members of the dense dimensions. For example, if the Account and Period dimensions are dense, the combination of one time period (January) and one account (Sales) equals one cell of data within a data block.

a r O

Planning: Create and Manage Applications

3-11

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview Sparse dimensions determine the number of data blocks in a database. There is the potential of having a data block for each unique combination of sparse dimension members. By default, Entity, Scenario, Version, and Year are sparse dimensions. For an application that uses currencies, the Currency dimension is set to sparse. NOTE

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

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 3-12

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Data Blocks and Retrieving Data

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

3-13

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Determining Data Structure and Performance of Data Blocks The dense and sparse settings for dimensions determine data structure. The data structure can have a significant impact on data retrieval and calculation time. Although design considerations can vary significantly between applications, follow the general guidelines for performance. When you view or calculate data, you typically experience the best performance if the cells that need to be calculated or viewed are in the same data block.

e l c

a r O 3-14

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

3-15

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

Selecting Aggregation Options Define calculations in the hierarchy based on parent-child relations. ƒ Aggregation options — — — — — —

+ Addition - Subtraction * Multiplication / Division % Percentage ~ Ignore

Net Income Sales (+) COGS (-)

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Selecting Aggregation Options

e d a

c A

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

Because dimension members can belong to more than one plan type, you can specify different aggregation options by plan type.

e l c

a r O 3-16

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

Selecting Data Storage Options Use storage options to optimize performance and disk usage. ƒ Storage options — — — — — —

StoreData (default) DynamicCalcAndStore DynamicCalc ShareData NeverShare LabelOnly

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Selecting Data Storage Options

e d a

c A

You select from several storage and calculation options for dimension members to optimize performance and disk usage. The following table describes these options: StoreData

Stores data values of members. This is the default value for all members.

DynamicCalcAndStore

Calculates the data value the first time the member is retrieved and then saves the value.

DynamicCalc

Calculates the data values each time the member is retrieved. The value is not stored in the database.

Share Data

e l c

Allows two or more members in the same dimension to share data values.

a r O

Planning: Create and Manage Applications

3-17

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview NeverShare

Prohibits two or more members in the same dimension from sharing a data value.

LabelOnly

Has no data associated with the member.

DynamicCalcAndStore With DynamicCalcAndStore, on the first retrieval, the data value is calculated and then stored. Subsequent retrievals use the stored value. The DynamicCalcAndStore option is used infrequently. In most cases, you can optimize your calculation and lower disk usage by using DynamicCalc when you calculate members of sparse dimensions. Use DynamicCalcAndStore for members of sparse dimensions in the following situations: • A sparse member with a complex formula • A sparse member that users retrieve frequently For members of dense dimensions, use Dynamic Calc for calculations. Using Dynamic Calc and Store increases retrieval time and regular calculation time. In addition, disk usage is not lowered significantly.

y m

DynamicCalc If a member is set to DynamicCalc, Essbase does not calculate its data value during regular database calculation; for example, when the CALC ALL function is executed, Essbase calculates the data value upon retrieval; a specific example of this is data being calculated when it is retrieved into a data form.

e d a

Advantages of DynamicCalc:

e l c a r O ly & On l a e n r s e t U n I

c A

• Reduction in the regular calculation time of the database because Essbase has fewer member combinations to calculate. • Reduction in disk usage because Essbase stores fewer data values. Database size and index size are reduced. DynamicCalc is most useful for parent-level dense dimension members. Since values for DynamicCalc members are not stored, the data block size is reduced, which improves performance. However, retrieval time for the member is increased. DynamicCalc should be used sparingly with sparse dimension members. Because each member of a sparse dimension references a separate data block, a dynamic calculation that includes many sparse members must retrieve data from a large number of data blocks. Retrieving data from many data blocks can reduce performance. As a rule of thumb, use DynamicCalc for upper-level members of sparse dimensions only if those upper-level members have six or fewer children.

e l c

a r O 3-18

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

DynamicCalc guidelines: • Do not use DynamicCalc for base-level members for which users enter data. Data values are not saved for DynamicCalc members. • Do not use DynamicCalc for a parent member if you enter data for that member in a target version. Parent members set to DynamicCalc are read-only in target versions. • Do not set a parent member to Stored if its children are set to DynamicCalc. With this combination, when a user saves and refreshes a data form, the new total for the parent is not calculated. ShareData and NeverShare Use ShareData when you want to allow for alternate rollup structures. You can set members within the same dimension to share data values, enabling alternate rollup structures within the application. For shared members, you must set the data storage to Share Data so that the shared member is added when the Application View is deployed. Use NeverShare when a parent has a single child that aggregates to the parent. In this case, set the parent to NeverShare. You can set appropriate security to the child member. Typically, you set the currency, entity, version, and any custom dimensions to NeverShare. Members within the currency, entity, version, and any custom dimensions are not set to NeverShare, and typically are set to either StoreData or DynamicCalc.

y m

e d a

c A

LabelOnly Data Storage LabelOnly members are virtual members; they are typically used for navigation and have no associated data. For example, you might have a parent member named Statistical that groups statistical accounts such as Headcount and Interest Rate. Because these accounts do not aggregate to a meaningful total, there is no need to calculate or store a value for the member Statistical.

e l c a r O ly & On l a e n r s e t U n I

Making a dimension member LabelOnly helps minimize database space by decreasing block size, which improves performance. LabelOnly members can also be used to group members or to navigate and report more easily from Financial Reporting or Essbase Smart View Provider. LabelOnly guidelines:

• You cannot designate level 0 members as LabelOnly.

e l c

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

a r O

Planning: Create and Manage Applications

3-19

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview • In single-currency applications, LabelOnly is the default data storage type for all root dimensions. In multicurrency applications, LabelOnly is the default data storage type for HSP_Rates, Account, Period, Year, and Scenario. • You cannot assign attributes to LabelOnly members. • In multicurrency applications, you cannot apply the LabelOnly storage option to members of the following dimensions: Entity, Version, Currency, and user-defined dimensions. If you want to store exchange rates, you must set them to NeverShare. • The data storage option for children of LabelOnly parents is set to StoreData by default.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 3-20

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

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

Level 0 Data

2nd Pass

Calculated Data (Before Two-Pass)

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculating Data

Calculated Data (After Two-Pass)

y m

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

3-21

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

Using Two-Pass Calculations ƒ Before Two-Pass

9

9 9 8

9

9 9 9

ƒ After Two-Pass

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Using Two-Pass Calculations

y m

e d a

c A

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

e l c

a r O 3-22

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

Determining Performance Efficiency

Sparse Dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Determining Performance Efficiency

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

3-23

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview Another important factor for performance is the number of cells per data block. Because there is a multiplier effect between dense dimensions, the number of cells in a data block grows exponentially when dense dimensions are added to the database. For example, your database might have 200 account members and 12 period members, resulting in 2,400 cells. If the HSP_Rates dimensions is added as a dense dimension with 10 members for currency rates, the number of cells jumps to 24,000 (200 × 12 × 10). As a general rule, smaller data blocks give better performance than larger data blocks.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 3-24

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 3

Creating Dimensions Overview

Summary In this lesson, you should have learned to: • Describe plan types • Identify required dimensions • Identify user-defined dimensions • Describe dense and sparse dimensions • Describe data block creation • Describe aggregation, data storage, and calculation options

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

3-25

Module 2

Creating Application Structures

Lesson 3 Creating Dimensions Overview

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 3-26

Planning: Create and Manage Applications

L E S S O N

4

Managing Dimensions with EPM Architect

4

Objectives At the end of this lesson, you should be able to: • Describe EPM Architect • Navigate EPM Architect • Create dimension members • Manage dimensions

y m

• Modify member properties • Set up alias tables

e d a

• Add and modify currencies • Create property associations

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

About Dimension Management

Master view pane

Application view pane

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

About Dimension Management

e d a

c A

You can view, manage, create, and deploy Hyperion applications within a single interface, the Dimension Library. The Dimension Library has two types of views—Master View and Application View.

Master View

Master View is a central repository that contains all dimensions and dimension members for Planning and Financial Management applications. All dimensions and dimension members are created in Master View or imported into Master View. Master View can contain more than one dimension of the same type. For example, it could contain two Period dimensions, with the names Quarterly Calendar and Trimester Calendar, that are used in different Planning applications.

e l c

a r O 4-2

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect To Work in the Master View: 1. Select Navigate > Administer > Dimension Library.

Application View An application view represents a selection of dimensions required by an application. You cannot create dimensions or dimension members in application views. Instead, you create them in Master View and then assign them to application views. To Work in the Application View: 1. Select Navigate > Administer > Application Library. 2. Right-click on an application view, and select Edit. The application view is displayed.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

4-3

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

EPM Architect Process 1. Import from flat file into Dimension Library Master View !Members ‘Name, MemberValidForPlan1;TimeBalance Travel;Y;Flow New Computers;Y;Balance

MasterView Accounts EntityBudgeting EntityConsol PeriodsStandard PeriodsTrimesters Dimension Server

2. Create application views Budgeting Application View Accounts EntityBudgeting PeriodsTrimester

FM Consol Application View Accounts EntityConsol PeriodsStandard

3. Deploy application views from Dimension Server to product application servers

Planning Application Server Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

EPM Architect Process

y m

e d a

Financial Management A ppli cation Server

c A

You manage dimensions and create Planning applications in EPM Architect: 1. Add dimensions to Master View. You can import them from formatted flat files, or you can create them manually in the dimension editor. 2. Create application views for Hyperion applications by selecting application types and assigning dimensions. 3. Create Planning applications by deploying application views with the Planning type to Planning application servers.

e l c

a r O 4-4

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Adding Dimensions to Master View

y m

e d a

Dimension class

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Dimensions to Master View

c A

You can add dimensions to the Master View. Dimension names must be unique and can contain up to 50 characters (including spaces). To add dimensions to Master View: 1. Select File > New > Dimension.

The Add New Dimension dialog box is displayed. 2. Enter a dimension name.

Dimension names must be unique and can contain up to 50 characters, including spaces.

e l c

a r O

3. Optional: Enter a description.

Planning: Create and Manage Applications

4-5

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect 4. In the Type drop-down list, assign a dimension class to determine the properties that are available to the dimension members. • Account • Entity • Generic (custom Planning dimension) 5. Click OK. TIP

After you have added a dimension to Master View, you can copy the dimension or delete the dimension by right-clicking the dimension and selecting Copy or Delete from the menu.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 4-6

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Organizing Dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Organizing Dimensions

e d a

c A

You can organize dimensions by creating folders and copying or moving the dimensions into the folders. Dimensions can exist in more than one location. For example, you can organize dimensions and have the Account dimension exist in multiple folders or have the Account dimension exist at the highest level and also within a folder. You can rename folders. You can move dimensions. You can drag dimensions to move them from their original location into a folder. You can move multiple dimensions at the same time by using the [ctrl] key to select more than one dimension to move. You can delete folders that you create in the Dimension Library. When deleting folders, you have two options: 1) to delete only the folder, or 2) to delete the folder and content.

e l c

a r O

Planning: Create and Manage Applications

4-7

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect To create folders: 1. In Master View, select File > New > Folder. The Create New Folder dialog box is displayed. 2. Enter the name and description, and then click OK. To copy dimensions into folders: 1. In Master View, right-click the folder and select Add Dimensions. The Add Dimensions to Folder dialog box is displayed. 2. Perform one or more actions: • Enter the name of the dimension to add or enter a wildcard, such as A* to add all dimensions beginning with an “A”. • Using the [Ctrl] key, select one of more dimensions in the list. • Enter the name or group that owns the dimension.

y m

• Click OK.

e d a

To delete folders:

1. Right-click the folder, and select Delete and one of the following options: • Only Folder

e l c a r O ly & On l a e n r s e t U n I

• Folder with Content

c A

2. At the confirmation dialog box, click Yes. 3. Click OK to confirm. NOTE

If you select the option to delete only folders, then only the folders are deleted. Any dimensions within the folder are not deleted and sub-folders are not deleted. Those dimensions and sub-folders are moved to the root of the Dimension Library. If you select to delete only a sub-folder, then only the sub-folder is deleted. Dimensions are not deleted, rather they are moved to the root folder.

e l c

a r O 4-8

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Filtering Dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Filtering Dimensions

e d a

c A

You can filter the dimensions you see in the Dimension Library. Filtering only applies to dimensions, and not folders. NOTE

If you create a dimension and have a filter applied that does not include the new dimension, the dimension will not display in the Master View until you remove the filter.

To filter dimensions:

e l c

1. Select View > Filter Dimensions.

ra

The Dimension Filtering dialog box is displayed.

O

Planning: Create and Manage Applications

4-9

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect 2. Enter the name, select the type, or enter the name of the user or group who owns the dimensions. 3. Click OK. A filter icon is displayed in the Master View pane indicating that dimensions are filtered. TIP

You can remove filter criteria by selecting Edit > Clear Filter Criteria. You can only filter dimensions in the 'root' Dimension Library. Dimensions in folders are not filtered.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 4-10

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Sorting Dimensions and Folders

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Sorting Dimensions and Folders

e d a

c A

You can sort dimensions and folders in ascending or descending order. You can sort by dimension class, name, description, or owner. When dimensions are sorted, a sort icon is displayed in the Master View pane.

e l c

a r O

Planning: Create and Manage Applications

4-11

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

Creating Members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Members

e d a

c A

You can add members to dimensions in the Dimension Library. To add members to dimensions:

1. In the dimension hierarchy, right-click a member. 2. Select Create Member. 3. Select an option:

• Select As Child to add a member below the selected member

e l c

• Select As Sibling to add a member at the same level as the selected member

a r O

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

5. Click OK.

4-12

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Guidelines for Member Names Member names cannot contain these characters: ƒ Period (.)

ƒ Braces ({})

ƒ Plus sign (+)

ƒ Comma (,)

ƒ Minus sign (-)

ƒ Semicolon (;)

ƒ Asterisk (*)

ƒ At (@)

ƒ Slash (/)

ƒ Quotations (“)

ƒ Number (#)

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Guidelines for Member Names

e d a

c A

Member names can be up to 50 characters in length. Certain character cannot be used in member names for Planning applications.

e l c

a r O

Planning: Create and Manage Applications

4-13

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

Modifying Member Properties Property category

Save

Defined

Default

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Modifying Member Properties

e d a

c A

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

Application

Planning

Used for Planning applications

System Consolidation

e l c

Essbase Analytics

a r O 4-14

Identify characteristics of a member, such as name, description, and if the member is inactive Used for Financial Management applications Used for Oracle's Hyperion Essbase System 9 reporting cubes only

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect Property Category

Application

Enterprise Analytics

Used for Essbase reporting cubes

Statistical

Provide statistical information about a member such as number of children and number of siblings

Property fields are color-coded based on what is done with that property. Consider the following characteristics when working with properties: • Properties that can be modified display a white background. • Properties that are read-only display a grey background. • Modified properties change to yellow. Modified properties, called defined properties, are not saved until you click the Save button in the upper-right corner of the properties pane. Defined properties display the following icon: . Unmodified properties display a check mark.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

4-15

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

Property Value Inheritance ƒ Descendant members inherit property values from ancestors. ƒ Updating the property value for an ancestor automatically updates the value for its descendants. ƒ Modifying a property of a descendant directly prevents it from inheriting that property from an ancestor. Currency property is set to Euro Descendants of Europe inherit Euro as value for Currency property

Currency property is set to GBP, overriding inherited value

y m

Descendants of United K ingdom inherit GBP for Currency property

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Property Value Inheritance

e d a

c A

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

e l c

a r O

3. If no ancestor has an entered value, the system default value for the property is used.

4-16

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Managing Property Value Inheritance

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Managing Property Value Inheritance

e d a

c A

EPM Architect provides the following options for managing inherited properties: • To clear a property value for an individual member, so that it reverts to the value inherited from its nearest ancestor, right-click the property for the member and select Remove Value. • To clear all property value overrides by descendants, so that all descendants revert to the value set at the ancestor level, right-click the property at the ancestor level and select Remove Descendant Values.

e l c

a r O

Planning: Create and Manage Applications

4-17

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

Creating Alternate Rollups EastSales and W estSales occur in alternate rollups Entity

Entity [No ne]

[None]

Geo graphical

Ge ographical U nited Sta tes

Activity C alifornia

SalesSer vices Plant1

WestSales

WestSales

EastSales

C onnecticut

EmeaSales Ea stSales

Activity

Manufacturing

e d a

D evelopme nt

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Alternate Rollups

y m

Emea Ser vices

c A

You can create multiple rollup paths for your data by placing a child member under more than one parent. In the slide illustration, EastSales and WestSales are members of a geographical rollup, with Geographical as the top member, and a functional rollup, with Activity as the top member. A member has the same property settings under all parents in which it occurs, with one exception. One member has the property StoreData. Any additional members have their property storage set to ShareData. Editing the properties of the stored member under one parent updates it properties for all parents. To place a member in an alternate hierarchy, you use the menu to copy the member and paste it to the new location.

e l c

a r O 4-18

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Managing Members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Managing Members

e d a

c A

You can change the order in which a member is displayed under a parent or move a member to another parent. You can delete a member from a single hierarchy or from all hierarchies.

Moving Members

You can move a member to a new location in the hierarchy:

• To change the order in which children are displayed under a parent, drag members to another location.

e l c

• To move a child to another parent, right-click the member and select Cut. Right-click the member that you want as the new parent, and select Paste > As Child.

a r O

Planning: Create and Manage Applications

4-19

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

Deleting Members You can delete members from the current hierarchy only or from the dimension. When you delete a member from the dimension, the member is removed from all hierarchies in Master View and from all application views. • To delete a member from a hierarchy, right-click the member and select Remove Member. • To delete a member from the dimension, select the member in any hierarchy in Master View, and select Delete Member.

Renaming Members You can rename members in the Dimension Library. You cannot rename system members. For Planning members, you cannot rename Currency or Year members.

Reordering Children You can reorder children in the Dimension Library.

y m

To reorder children:

e d a

1. Right-click a dimension or member that has children, and select Reorder Children. The Reorder Children dialog box is displayed.

c A

2. Click on the up or down arrows to change the order of the children. 3. Click OK.

e l c

e l c a r O ly & On l a e n r s e t U n I

a r O 4-20

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Inserting Members Using Relationships

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Inserting Members Using Relationships

e d a

c A

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

1. Right-click a member that you want as the parent or sibling of the inserted members, and select Insert Member. 2. Select an option:

e l c

• Select Child to add the member as a child of the currently selected member. • Select Sibling to add the member at the same level as the currently selected member.

a r O

Planning: Create and Manage Applications

4-21

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect 3. In the Insert member dialog box, select a member. 4. Right-click the member, and select an option: Option

To insert

Member

Selected member

Children

All children of the currently selected member

Descendants

All members below the currently selected member

Siblings

All siblings of the selected member (Siblings are members that have the same parent member.)

Parent

Parent of the currently select member

Ancestors

All members above the currently selected member

Level 0 (Base)

All base members beneath the currently selected member

5. Optional: Select Inclusive to include the selected member. For example, if you select the Inclusive option with the Children option, the selected member and its children are inserted into the hierarchy.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 4-22

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Finding Members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Finding Members

e d a

c A

You can search for members in the Dimension LIbrary. To find members:

1. Right-click a dimension, and select Find Members.

2. Select to search by the member: Name, Alias, or Property. 3. Enter the value.

4. Select an option to view the results:

e l c

• List View —replaces the Properties Grid and lists all members in the Member Find pane.

a r O

• Navigation Button —displays the first member in the Master View pane. You can use navigation buttons on the Standard toolbar to move to the next or previous member.

Planning: Create and Manage Applications

4-23

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect • Click OK. • Close the Member Find dialog box.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 4-24

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Creating Aliases Association

Create table

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Aliases

e d a

c A

If you want to improve outline and report readability, you can assign one or more alternate names, or aliases, to dimension members. Aliases enable you to create unique sets of identifiers when working with dimensions and members. You can assign up to 10 aliases per dimension and dimension member, including the default alias. You create alias tables in EPM Architect by creating an Alias dimension and then adding members to that dimension.

e l c

a r O

Planning: Create and Manage Applications

4-25

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect For example, you can set up alias tables to store information for different languages. If you want to include account names in English, French, and German, you create members in the Alias dimension named English, French, and German. Then you create an association between the Alias property in the base dimension and the alias dimension. In addition to associating aliases to the Account dimension, you can create associations with the Entity, Scenario, Version, Period, or Year dimensions or userdefined dimensions. NOTE

For Planning, you must include an Alias member named Default.

To create alias tables in the Dimension Librar y: 1. Select File > New > Dimension. 2. In the Add New Dimension dialog box, enter the Name and Description of the alias table. 3. Select Alias from the Type drop-down list.

y m

4. Click OK. To create members in the Alias dimension: 1. Right click Alias and then select Create Member > As Child. 2. Type the Name for the alias table, for example German. 3. Click OK.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

To add aliases to dimension members: 1. Select the dimension member.

2. Double-click in the Alias field of the property grid.

3. Click the ellipsis button and enter aliases in the row representing the alias table.

e l c

a r O 4-26

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Adding Currencies

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Currencies

e d a

c A

You set up currencies by creating a dimension with the dimension class Currency. You create members in the Currency dimension for each currency needed in your application. NOTE

A dimension association is required between the Base Currency property of the Entity dimension and the Currency dimension.

Number Formatting

You can set the number format for each currency. For example, for the European euro, you can set the dot as the thousands separator and the comma as the decimal separator to match the European standard. You can also set the color of negative numbers.

e l c

a r O

Planning: Create and Manage Applications

4-27

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

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

Triangulation Planning supports currency conversion by triangulation through an interim currency, which is referred to as the triangulation currency. For example, if you know the European euro exchange rates for U.S. dollars and French francs, you can calculate the U.S. dollar/French franc exchange rate by using the European euro as the triangulation currency. You can also modify a currency’s triangulation currency by reentering the exchange rates relative to the triangulation currency period and then refreshing the application so that the new exchange rates are transferred and stored. NOTE

y m

You cannot select the default currency as a triangulation currency.

e d a

Reporting Currency

c A

Planning supports currency conversion from local currencies to one or more reporting currencies. The converted reporting currency values are stored and are read-only for all users. The application default currency is also the default reporting currency. When you add currencies, you specify whether they can be used as reporting currencies.

e l c a r O ly & On l a e n r s e t U n I

For example, suppose your application contains the currencies Japanese yen, U.S. dollar, and European euro, with European euro specified as a reporting currency. When you create data forms and reports, Japanese yen and U.S. dollar values are converted to European euros and displayed. You can load values directly into Essbase (from historical scenarios, for example) for reporting. NOTE

Each reporting currency is added to the Currency dimension, increasing the size of the database and adding complexity to the currency conversion calculation scripts. Only enable Reporting Currency if required.

e l c

a r O 4-28

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Creating Associations Between Dimensions

y m

Ellipsis indicates that an association exists.

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Associations Between Dimensions

e d a

c A

You can associate a property in one dimension with the members of another dimension so that end users can set the value for the property by selecting from a pick list of members from the associated dimension. For example, if you create an association between the Currency property of the Entity dimension and the Currency dimension, users can set the Currency property of an entity member by selecting from a pick list of members in the Currency dimension. After you create an association for a property, users must select a member from the pick list to set the property value; no other entries are valid.

e l c

a r O

Planning: Create and Manage Applications

4-29

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect You can create an association for any dimension property, but some dimension properties require that a dimension association be created. Values cannot be entered for these properties until an association exists. The following table shows the properties that require an association: Dimension Type

Properties Requiring Associations

Account

Alias

Entity

Alias Attribute Currency

Scenario

Alias Start Period End Period Start Year End Year

Version

Alias

Currency

Alias

Period

Alias

Year

Alias

Smart Lists

Alias

Generic

Alias Attribute

e l c

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 4-30

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 4 Managing Dimensions with EPM Architect

Summary In this lesson, you should have learned to: • Describe EPM Architect • Navigate EPM Architect • Create dimension members • Manage dimensions • Modify member properties • Set up alias tables • Add and modify currencies

y m

• Create property associations

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

4-31

Module 2

Creating Application Structures

Lesson 4 Managing Dimensions with EPM Architect

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 4-32

Planning: Create and Manage Applications

L E S S O N

5

Setting Up the Period, Scenario, and Version Dimensions

5

Objectives At the end of this lesson, you should be able to: • Describe Planning time periods • Customize time periods • Create scenarios • Create versions

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 2

Creating Application Structures

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

Time Periods Overview The Year and Period dimensions represent time. You can: ƒ Add years ƒ Create new summary time periods or change the name of summary time periods ƒ Add or change the aliases ƒ Add up to 100 calendar years and 500 time periods to an application You cannot: ƒ Modify the Start Year after the application is deployed ƒ Reduce the number of years without creating a database ƒ Change the base time periods

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Time Periods Overview

y m

e d a

c A

When creating application views, you add the Year and Period dimensions to represent time. You use the Period dimension to view and change the yearly calendar rollup structure, and you specify base time periods and distribution of weeks. You use the Year dimension to add years to the calendar. After creating the application view and setting the calendar, you cannot change base time periods or reduce the number of years. You can, however, change the rollup structure of the Period dimension. You can also add more years to the Year dimension. You can customize summary time periods in these ways: • Update the name

e l c

• Change the description

a r O

• Modify starting and ending periods • Change the range

5-2

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions • Create new summary time periods • Add or change the aliases NOTE

You cannot skip or change the order of base time periods. You cannot extend the range beyond the current fiscal year. If you create new summary time period, you must work from the top of the hierarchy to the bottom. The Period Type property for a summary time period is Summary Time Period. Keep in mind the following requirements: • All base members must be the same number of levels from the root. • Base members must have a Period Type property value of Base Time Period. • The BegBalance member is a required member for Planning applications and must exist for successful deployment.

y m

• The YearTotal member is a required member for Planning applications and must exist for successful deployment.

e d a

NOTE

c A

The YearTotal member is the summary time period that aggregates all quarters or weeks (for custom time periods).

e l c a r O ly & On l a e n r s e t U n I

• The YearTotal member must have a Period Type property value of Year Time Period. You can add up to 100 calendar years and 500 time periods to an application. Depending on the number of time periods and years and whether your application uses multiple currencies, Hyperion recommends these practical limits: • 400 time periods per year and 27 years • 360 time periods per year and 30 years

You can enable Dynamic Time Series (DTS) for Period dimension members. For DTS members, you can set the following properties: DTS Enabled, DTS Generation, and Alias.

e l c

a r O

Planning: Create and Manage Applications

5-3

Module 2

Creating Application Structures

Lesson 5 Setting Up the Period, Scenario, and Version Dimensions You can create alternate hierarchies and use shared descendants in the Period dimension. Data Storage for all time periods can be set to any valid Data Storage value. The Consolidation operator for all scenarios, versions, and time periods (including BegBalance) can be set to any valid consolidation operator. For example, it can be set to + instead of ~ (ignore).

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 5-4

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions

Period and Year Dimensions

Year

Period

Year

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Period and Year Dimensions

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

5-5

Module 2

Creating Application Structures

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

Dynamic Time Series Members Predefined DTS Member

Description

H-T-D

History-to-date

Y-T-D

Year-to-date

S-T-D

Season-to-date

P-T-D

Period-to-date

Q-T-D

Quarter-to-date

M-T-D

Month-to-date

W-T-D

Week-to-date

D-T-D

Day-to-date

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Dynamic Time Series Members

e d a

c A

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

e l c

a r O 5-6

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions

Setting Up Dynamic Time Series Members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Up Dynamic Time Series Members

e d a

c A

The DTS members provide up to eight levels of period-to-date reporting. Your data and database outline determine which members you can use. For example, if the database contains hourly, daily, weekly, monthly, quarterly, and yearly data, you can report day-to date (D-T-D), week-to-date (W-T-D), month-to-date (M-T-D), quarter-to-date (Q-T-D), and year-to-date (Y-TD) information. If the database contains monthly data for the past 5 years, you can report year-to-date (Y-T-D) and history-to-date (H-T-D) information, up to a specific year. If the database tracks data for seasonal time periods, you can report periodto-date (P-T-D) or season-to-date (S-T-D) information. You can import DTS members from .ads files, or add them manually to Application Views. After you add DTS members, you must enable them by selecting members and setting these options in the Properties Grid: DTSEnabled, DTSGeneration, and Alias. (Setting the DTS properties for non-DTS members has no effect.) Additional Period properties are not applicable to DTS members.

e l c

a r O

Planning: Create and Manage Applications

5-7

Module 2

Creating Application Structures

Lesson 5 Setting Up the Period, Scenario, and Version Dimensions Follow these guidelines for using DTS members with Performance Management Architect: • DTS members must be level 0 members and children of the root member (such as Period). • The PeriodType property for DTS members is Dynamic Time Period. • For members enabled as DTS, a DTSGeneration must be selected. • If you are using Y-T-D, the Year dimension cannot be named Year. • If you are using P-T-D, the Period dimension cannot be named Period.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 5-8

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions

Choosing How Data Is Stored

The storage type for a member has a major impact on the size and calculation performance of your database.

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Choosing How Data Is Stored

y m

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

5-9

Module 2

Creating Application Structures

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

Scenario Dimension The Scenario dimension specifies a data classification.

Actual

Budget

Forecast

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Scenario Dimension

e d a

c A

You can use the Scenario and Version dimensions to create individual plans. You create the Scenario and Version dimensions to set up individual plans to be reviewed and approved. For each entity, the scenario and version combination contains its own set of data for the accounts and other dimensions. After entering entity data for a scenario and version, you can submit or promote the data to other users for review and approval. The intersection of entity, scenario, and version is referred to as a planning unit. Planning tracks the status or planning units as you move them through the planning process. Scenarios enable you to:

e l c

• Apply different planning methods

• Associate different scenarios with different time periods and exchange rates

a r O

• Create forecasts and budgets

5-10

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions • Enter data into scenarios • Assign user access rights by scenario • Report by scenario • Compare and analyze different scenarios Creating scenarios enables you to group your data into separate plans with their own review cycles. Scenarios can also cover different time spans. For example, your organization might create one-year and three-year revenue plans that are prepared by different users and follow different review paths. For this purpose, you could create two scenarios, Current Year Revenue and 3Year Forecast. You can create hierarchies and use shared members in the Scenario dimension. Scenarios are required for Planning applications, and must exist for successful deployment.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

5-11

Module 2

Creating Application Structures

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

Creating Scenarios

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Scenarios

e d a

c A

When you create a scenario you define these properties: • Enable Process Management

• Start and End Years and Periods • Exchange Rate Table

• Use Beginning Balance • Access rights

Enable Process Management

e l c

In EPM Architect, select Enable Process Management if you want to include this scenario in process management. If you select this check box, this scenario is displayed in the scenario drop-down list on the Check Status and Manage Process page.

a r O 5-12

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions

Time Periods In EPM Architect, you assign each scenario a range of years and time periods for which it is valid. The range of time periods you select for a scenario has the following effects in your application: • When you access a data form, you are able to enter data into that scenario for only the years and time periods within the range. Years and time periods outside the range are displayed as read-only. • When you generate a currency conversion calculation script, the calculation script converts currencies for the range of time periods that are valid for the scenarios selected for the script. You can modify the time range of scenarios as needed to allow for continuous planning. For example, you might have a scenario named 3Year Forecast that has 2007 as the start year and 2009 as the end year. At the beginning of the 2008 fiscal year, you could change the start year to 2008 and the end year to 2010, so that you can enter forecast data for 2010.

y m

Exchange Rate Table

If your application uses currency conversion, you assign an exchange rate table to the scenario in EPM Architect. By assigning different exchange rate tables to scenarios, you can model the effect of different assumptions on your business. You must consider currency reporting needs when deciding which scenarios to create. For example, you may need to create scenarios associated with different exchange rate tables to eliminate the effects of currency rate fluctuations from variances (such as Budget at Actual Rate).

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

Use Beginning Balance

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

Access Rights

You can specify access permissions for Scenario dimension members to determine whether groups or users can view or modify data. A user or group can have only one of the following access rights: Read, Write, or None. You assign access rights for scenarios in Planning.

e l c

a r O

Planning: Create and Manage Applications

5-13

Module 2

Creating Application Structures

Lesson 5 Setting Up the Period, Scenario, and Version Dimensions Members of the Year and Period dimensions do not have security associated with them. However, you can use the scenario start and end year and period properties to lock time periods out for data entry. For example, you could set the properties so that users can enter data only into the current year. All time periods that fall outside the start and end range are displayed as read-only. You can also set the Start and End Period properties to allow a mix of actual and budget data in the same scenario for forecasting purposes. For example, if you are rolling out your application in quarter 2, the Forecast scenario could contain actual data for quarter 1 and forecast data for quarters 2, 3, and 4. If you set the start period to quarter 2, users can input forecast data for quarters 2, 3, and 4, but not edit the actual data in quarter 1. At the end of quarter 2, you load actual data for quarter 2, and change the start period to quarter 3, so that you can create a rolling forecast.

Deleting Scenarios When you delete scenarios, all planning units that use the scenario (including data) are deleted.

y m

NOTE

You cannot delete scenarios that are used in planning units and that are started or assigned to axes on data forms. You must first remove references to scenarios from data forms and assign different scenarios.

e d a

To create scenarios:

e l c a r O ly & On l a e n r s e t U n I

c A

1. Right-click the Scenario dimension, and select Create Member > As Child. 2. Enter a name and click OK.

3. Set the following properties for the scenario member: • Valid for Plan • UDA

• Member Formula • Alias

e l c

• Data Storage

• Two Pass Calc

a r O

• Enable for Process Management

5-14

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions • Smart List • Data Type • Start and End Year • Start and End Period • Use Beginning Balance • Exchange Rate Table

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

5-15

Module 2

Creating Application Structures

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

Version Dimension ƒ Versions provide process flexibility by providing iterative planning cycles. ƒ Versions are independent of individual scenarios. For example, Preliminary and Final versions could be associated with any scenario. ƒ There are 2 version types: —Standard Bottom-Up —Standard Target

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Version Dimension

e d a

c A

Versions are required for Planning applications, and must exist for successful deployment. You can create, for example, Best Case and Worst Case versions for use with any scenario. You can use the Version dimension for these purposes: • Allow multiple iterations of a plan; for example, Preliminary and Final. • Model possible outcomes based on more optimistic or less optimistic assumptions; for example, Best Case and Worst Case. • Manage dissemination of plan data; for example, Internal and External. • Facilitate target setting

e l c

You set up the Version dimension in EPM Architect. You can change the version name in EPM Architect and access permissions in Planning.

a r O 5-16

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions The permissions are independent of scenarios, so you could give users read-only access to the Final version but write access to the Working version. Then, if users want to enter data for Budget Final intersections, they cannot write to that intersection even though the Budget scenario may have write access. The read access to the Final version prevents write access to that intersection of data. NOTE

You cannot delete versions that are used in planning units and that are started or assigned to axes on data forms. You must first remove references to versions from data forms and assign different versions. You must have at least one version in the application view. You can create hierarchies and use shared members in the Version dimension. If you assign children to bottom-up versions, these versions display as read-only parents on data forms.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

5-17

Module 2

Creating Application Structures

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

Creating Versions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Versions

e d a

c A

You create versions and set version properties in EPM Architect. There are two types of versions, Bottom-Up or Target. For Bottom-Up versions, you enter data into the bottom level members. The parent-level members are read-only. When you calculate the database, the values of parent members are aggregated from the bottom-level members. For example, if you enter data for Northern Europe and Southern Europe, the total for Europe is aggregated after the database is calculated. Target versions allow you to enter data for members at any level in the hierarchy. You can use business rules to distribute values from parent members to their descendants. For example, you can enter the target for Total Expenses into the Europe member and use a business rule to distribute the target values to Northern and Southern Europe.

e l c

a r O 5-18

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions Target versions enable you to set high-level targets for your plan. Planners working with bottom-up versions can then reference these targets when they enter plan data. For example, the Total Product Sales member has Retail, Wholesale, and Distributors for its children. A budget manager enters 10,000 into Total Product Sales for the California entity in a target version. This target sets California’s target for product sales. The budget preparer for California then enters values for the Retail, Wholesale, and Distributors children that total 10,000 in a bottom-up version to show how the target is met. The functionality available with target versions is for top-down budgeting. Guidelines for target versions: • Workflow Tasks are not allowed for target versions. • Children of target members must be blank (for example, #missing) for the data input to be allowed at the top level. • Target members must be set to StoreData (DynamicCalc overrides data input with sum of children).

y m

To create versions: 1. Right-click the Version dimension, and select Create Member > As Child.

e d a

2. Enter a name and click OK. 3. Set the following properties for the version member: • Valid for Plan • UDA

e l c a r O ly & On l a e n r s e t U n I

c A

• Member Formula • Alias

• Data Storage

• Two Pass Calc

• Enable Process Management NOTE

Enable for Process Management can be selected only for bottom up versions.

e l c

a r O

• Smart List

Planning: Create and Manage Applications

5-19

Module 2

Creating Application Structures

Lesson 5 Setting Up the Period, Scenario, and Version Dimensions • Data Type • Version Type

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 5-20

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions

Summary In this lesson, you should have learned to: • Describe Planning time periods • Customize time periods • Create scenarios • Create versions

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

5-21

Module 2

Creating Application Structures

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

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 5-22

Planning: Create and Manage Applications

L E S S O N

6

Setting Up the Entity Dimension

6

Objectives At the end of this lesson, you should be able to: • Add members to the Entity dimension • Modify members in the Entity dimension • Delete members in the Entity dimension

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 2

Creating Application Structures

Lesson 6 Setting Up the Entity Dimension

Entities Overview ƒ Entities allow you to model the flow of budget information through your organization. ƒ You can create an entity for each group or responsibility center that submits a plan for approval. ƒ You can assign plan types to entities. ƒ Entities can have a currency property. — If no currency is defined, the application default currency is used. — The entity’s currency can be overwritten during data entry or data loads.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Entities Overview

e d a

c A

The Entity dimension is a Planning dimension whose members can be loaded or manually added to an application. You can use parent-child relationships among entities to mirror your budget review structure. You can define the types of units that your organization requires, such as geographical regions, departments, or divisions. For example, your organization may have regional centers that prepare budgets that are reviewed at the country headquarters. The country headquarters may, in turn, prepare a plan that is reviewed at the corporate headquarters. To match this structure, you can create members for the regions, countries, and headquarters. You can set up the regions as children of the country members, and the country members as children of the headquarters member.

e l c

a r O 6-2

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 6 Setting Up the Entity Dimension

Entity Members and Plan Types ƒ When you define an entity member you assign plan types. ƒ If you do not assign a plan type to a parent, its children do not have access to that plan type. Data Form

Plan Types

IncStmt

9

BalSheet

Revenue

Eastern US

Assigned

de FL

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Entity Members and Plan Types

y m

NY

a c A

A plan type is a classification mechanism for data.

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

e l c

a r O

Planning: Create and Manage Applications

6-3

Module 2

Creating Application Structures

Lesson 6 Setting Up the Entity Dimension Selecting a plan type for an entity member involves specifying how the data values should roll up for that plan type. An entity member’s plan types may change when you promote or demote the member in the dimension hierarchy: If the new parents’ associated plan types are different from those of the moved member, the member becomes valid for the plan types of the new parent. If you move an entity member, and the new parent of that member is assigned to different plan types, the member remains assigned to the plan types that it has in common with the new parent.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 6-4

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 6 Setting Up the Entity Dimension

Identifying the Currency Value for Entities The default currency is the currency that you specify when you create the application view.

New York

London

Tokyo

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Identifying the Currency Value for Entities

e d a

c A

If your application is set up for multiple currencies, you must specify a currency for each entity. The default currency for all entities is the currency that you specify when you create your application view in EPM Architect. The currency property value identifies the local currency in which data for the entity is entered. When you run a currency conversion calculation script or the Convert Currencies business rule, Planning uses the exchange rates entered for that entity’s currency to convert the local currency to the reporting currency. The currency property can be overridden during data entry or during a data load. For example, you might specify Yen as the currency for the Japan entity, and US dollars for the United States entity. When you view a data form that has values on it for the Japan entity, if the form’s display currency is set to US dollars, Planning uses the rates in exchange rates table for the Yen to convert the values to US dollars.

e l c

a r O

Planning: Create and Manage Applications

6-5

Module 2

Creating Application Structures

Lesson 6 Setting Up the Entity Dimension

Adding and Modifying Entities

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding and Modifying Entities

e d a

c A

You add and modify dimensions and members in the EPM Architect Dimension Library. You can also set the properties for dimensions and members. When you modify dimension and member properties, this information populates the EPM Architect relational database. For these changes to be reflected in the Essbase database, you can deploy the application in EPM Architect or you can select the Manage Database option in the Administration menu in Planning. You create members in the Dimension Library by right-clicking a dimension or dimension member and selecting Create Member. You can add a member as a child or sibling of the selected member.

e l c

You modify members by selecting the member and then modifying the member properties.

a r O 6-6

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 6 Setting Up the Entity Dimension To modify members: 1. Select the member. The properties pane is displayed. 2. Set up the following properties for entities: • Valid plan types • Aggregation and storage options • UDA and member formula • Alias • Two-pass calculation • Smart lists • Currency • Data type 3. Click

y m

to save the changes.

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

6-7

Module 2

Creating Application Structures

Lesson 6 Setting Up the Entity Dimension

Saving Dimensions Save changes to the relational database.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Saving Dimensions

e d a

c A

When you add, modify, or delete dimensions and their members, you must save the changes before they take effect. When you save the changes, EPM Architect performs a validation check for the following reasons: • To prevent two users from saving the same dimension or member at the same time. • To prevent a user from assigning a member to a plan type for which it is not valid. • To prevent a user from using the same name for different dimensions or members. If the validation check fails, an error message is displayed.

e l c

a r O 6-8

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 6 Setting Up the Entity Dimension

Deleting Entities

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Deleting Entities

e d a

c A

When you delete entities, remember the following points:

• If the entity member is used elsewhere, such as an application view, you must delete it there first. • You must update and validate business rules, reports, and Hyperion Application Link adapter processes to reflect the deleted entity. • Before you can delete an entity, you must remove it from data forms that contain the entity. To show an entity’s application membership in the Dimension Library, right-click an entity member and select Application Membership.

e l c

a r O

Planning: Create and Manage Applications

6-9

Module 2

Creating Application Structures

Lesson 6 Setting Up the Entity Dimension

Summary In this lesson, you should have learned to: • Add entity members to the Entity dimension • Modify entity members in the Entity dimension • Delete entity members in the Entity dimension

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 6-10

Planning: Create and Manage Applications

L E S S O N

7

Setting Up the Account Dimension

7

Objectives At the end of this lesson, you should be able to: • Describe account types and consolidation order • Create account hierarchies

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 2

Creating Application Structures

Lesson 7 Setting Up the Account Dimension

Accounts Overview ƒ You assign plan types to accounts. — If more than one plan type is assigned to an account, designate a source plan type. — Other plan types pull their values from the source plan type.

ƒ Use aggregation options to define calculations in the account hierarchy. Data Form

Plan Types

IncStmt

9

BalSheet

Revenue

Detail Expense Accounts Assigned

Profit

y m

Total Revenues Total Expenses

e d a Salaries Rent

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Accounts Overview

c A

The Account dimension is used to specify the information gathered from budget planners. Accounts typically represent an accounting container that identifies the primary nature of the data. Accounts are organized into hierarchies. You can create an account structure that lets budget preparers input data for budget items to the appropriate level of detail. You can define calculations in your hierarchies. For example, your detailed operating expense accounts can automatically aggregate to Total Expenses, and Total Expenses can be subtracted from Total Revenue. When you define an account member, you assign a plan type. If you promote or demote a member, and the new parent of the member has different associated plan types, then the member acquires the same plan types as the new parent.

e l c

a r O 7-2

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension If an account is associated with more than one plan type, you must specify a source plan type for the account. The source plan type determines which plan type’s database stores the account value. For example, if the source plan type for the Total Product Sales account is IncStmt, the value displayed for the account on forms for the Revenue plan type is the value entered for the IncStmt plan type.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

7-3

Module 2

Creating Application Structures

Lesson 7 Setting Up the Account Dimension

Account Types Account Type

Variance

Time Balance

Skip

Exchange Rate Type

Currency Type

Expense

Expense

Flow

N/A

Average

Currency

Revenue

NonExpense

Flow

N/A

Average

Currency

Asset

NonExpense

Balance

None

Ending

Currency

Liability

NonExpense

Balance

None

Ending

Currency

Equity

NonExpense

Balance

None

Ending

Currency

Saved Assumption

NonExpense

User-defined

N/A

None

NonCurrency

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Account Types

e d a

c A

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

e l c

a r O 7-4

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension

Time Balance Options Flow and Balance examples

Total Revenues Cash on Hand

Revenue Asset

Jan

Feb

Mar

Quarter 1

50

75

50

175

100

150

75

75

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Time Balance Options Option Flow

e d a

c A

Description

Uses an aggregate of all data values for a summary time period as a total for the period.

First

Uses the beginning data value in a summary time period as the total for the period.

Balance Average

e l c

Uses the ending value in a summary time period as the total for the period. Uses the average of all children’s data values in a summary time period as the total for the time period.

a r O

Planning: Create and Manage Applications

7-5

Module 2

Creating Application Structures

Lesson 7 Setting Up the Account Dimension Option

Description

Weighted Average-Actual_Actual

Uses a weighted daily average, based on the actual number of days in a year, to account for leap year when February has 29 days.

Weighted Average-Actual_365

Uses a weighted daily average based on 365 days in a year, assuming that February has 28 days; does not account for leap year.

Skip Options for Missing Values If you set the Time Balance property to First, Balance, or Average, you must specify how Planning should handle zeros and missing values: Property

Description

None

Zeros and #MISSING values are considered when calculating the parent value.

Missing

#MISSING values are excluded when calculating the parent values.

Zero

Zero values are excluded when calculating the parent values.

Missing and Zeros

#MISSING and zero values are excluded when calculating the parent values.

y m

e d a

NOTE

c A

When the time balance is set to Flow, skip options are not available and default to None.

e l c a r O ly & On l a e n r s e t U n I

An account’s variance reporting property determines if an account is tagged as an expense in Essbase member formulas or Financial Reporting variance functions. Here is how expense and nonexpense accounts behave for variance reporting: • Expense—The actual amount is subtracted from the budgeted amount to determine the variance. • Nonexpense—The budgeted amount is subtracted from the actual amount to determine the variance.

e l c

a r O 7-6

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension

Saved Assumptions Use Saved Assumptions to: ƒ Centralize planning assumptions ƒ Identify key business drivers ƒ Ensure consistency across the application Examples of Saved Assumption accounts include: ƒ Headcount ƒ Square footage

y m

Define business rules that reference these saved assumptions such as: ƒ Calculate office supplies by entity based on headcount

e d a

ƒ Calculate facilities expense based on square footage per location Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Saved Assumptions

c A

When you define a saved assumption account, you select the appropriate time balance and variance reporting properties. The following examples show how time balance and variance reporting properties are used with saved assumption accounts: • You may create a saved assumption of an expense type for variance reporting. It assumes that the actual amount you spent on head count is less than the amount you budgeted. To determine the variance, Planning subtracts the actual amount from the budgeted amount. • You make an assumption on the square footage of an office and you determine the square footage of the office for the time period by using a value for the end of the time period.

e l c

• You make an assumption about the number of product units sold at the end of the time period. You determine the final value for the time period by aggregating the number of units sold across the range of time periods.

a r O

Planning: Create and Manage Applications

7-7

Module 2

Creating Application Structures

Lesson 7 Setting Up the Account Dimension

Data Types and Exchange Rate Types Data NonCurrency types

Exchange rate types

Date

Average

Currency

Percentage

Ending

Smart List

Text

Historical

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Data Types and Exchange Rate Types

e d a

c A

Data and exchange rate types determine how numeric values are stored and which exchange rate to use to calculate the value. Data type options:

• NonCurrency—Stores and displays the value as a numeric value. • Currency—Stores and displays the value in the default currency. • Percentage—Stores and displays the value as a percentage. • Smart List—Stores and displays the value as a smart list.

e l c

• Date—Stores and displays the value as a date.

a r O

• Text—Stores and displays the value as text. • Unspecified —Stores and displays the value as unspecified.

7-8

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension For accounts whose data type is Currency, you select an exchange rate type: • Average—Valid for any time period; uses the average rate for the account. • Ending—Valid for any time period; uses the ending exchange rate for the account. • Historical—Valid for any time period. Data types can have conflicting results on the face of a data form depending upon the cell intersections defined for the data form. For example, the intersection of a "percent" data type and a "currency" data type must be resolved based on how you define the order set. The Data Type Evaluation Order is the defined order. You set a dimension order by plan type to determine the precedence when multiple data types intersect. Data types associated with the first dimension in the list take precedence over data types associated with subsequent dimensions.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

7-9

Module 2

Creating Application Structures

Lesson 7 Setting Up the Account Dimension

Creating Account Hierarchies

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Account Hierarchies

e d a

c A

You create and modify account hierarchies in the Dimension Library. You access the Dimension Library through the Navigate menu in EPM Architect. After you save changes to the hierarchy, your changes are saved to the EPM Architect relational database. You must deploy the application in EPM Architect or refresh the database in Planning to update the Essbase databases. To create account members: 1. Right-click an account.

2. Select Create Member and one of the following:

e l c

- As Child

a r O

- As Sibling

7-10

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension 3. In the properties pane, set up the account properties. You can set up the following properties: • Valid for plan type • Aggregation options • UDA, Member Formula • Alias • Data Storage • Two Pass Calc • Smart List • Time Balance • Skip Value • Variance Reporting

y m

• Account Type

e d a

• Exchange Rate Type • Data Type • Source Plan Type

e l c a r O ly & On l a e n r s e t U n I

Adding and Modifying Accounts

c A

In the Dimension Library, you can build the account hierarchy by adding children and sibling members. You can also change member properties. NOTE

When assigning plan types, you must set the plan type property for a parent member before you can set the plan type for its children. You cannot select a plan type for a child member if the plan type is not valid for the parent.

e l c

a r O

Planning: Create and Manage Applications

7-11

Module 2

Creating Application Structures

Lesson 7 Setting Up the Account Dimension

Consolidation Order Account (Never Share) Profit (+)

10 Level 2

7 Margin (+)

3

Level 1

Sales (+)

1

COGS (-)

2

Expenses (-)

Level 0

6

Marketing (+)

4

Misc. (+)

5

Ratios (~) (Label Only) Margin % (+) (Two Pass Calc) Margin % Sales; Product Share (+) (Two Pass Calc) Sales % Sales -> Products;

8

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Consolidation Order

y m

9

e d a

c A

After creating the Essbase database outline, you should review the order of the dimensions and members. For each plan type, data is consolidated based on the order of the dimensions and members in the outline. The order of calculation within each dimension depends on the relationships between members in the database outline. Within each branch of a dimension, level 0 values are calculated first, followed by their level 1, parent value. The level 0 values of the next branch are calculated, followed by their level 1, parent value. The calculation continues in this way until all levels are calculated. By default, the outline consolidates based on addition. You can set any member’s aggregation option to addition, subtraction, multiplication, division, percent, or ignore.

e l c

When a new operator is set, the operation designates how a member consolidates to its parent. For example, you may want to subtract a member from its sibling, such as subtracting COGS (Cost Of Good Sold) from Sales, to define the value for Margin.

a r O 7-12

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension

Consolidation Order Example ƒ Consolidation order is defined by the order of members in the outline. ƒ Essbase calculates data in top-down order. 6.67

Parent Member 1

(+)

10

Member 2

(+)

20

Member 3

(-)

25

Member 4

(*)

40

Member 5

(%)

50

Member 6

(/)

60

Member 7

(~)

70

30 5 25

200 400

40

6.67

50

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Consolidation Order Example

60

y m

e d a

c A

It is important to understand how members with different operators are calculated. When you use addition and subtraction operators, the order of members in the outline is irrelevant. However, when you use other operators, you must consider the member order and its impact on the consolidation. When siblings have different operators, the data calculates in top-down order. Essbase calculates Member1 through Member4 as follows:

(((Member1 + Member2) + (-1)Member3) * Member4) = X(((10 + 20) + (-25)) * 40) = 200 If the result from Members 1-4 is X, then Member5 consolidates as follows:

e l c

(X/Member5) * 100 = Y(200/50) * 100 = 400

a r O

If the result of Member5 is Y, then Member6 consolidates as follows: Y/Member6 = Z400/60 = 66.67 and Member7 is ignored in the consolidation.

Planning: Create and Manage Applications

7-13

Module 2

Creating Application Structures

Lesson 7 Setting Up the Account Dimension

Summary In this lesson, you should have learned to: • Describe account types and consolidation order • Create account hierarchies

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 7-14

Planning: Create and Manage Applications

L E S S O N

8

Creating User-Defined Elements

8

At the end of this lesson, you should be able to: • Create user-defined dimensions • Create attributes and assign attribute values • Describe member formulas • Add member formulas • Create smart lists

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

User-Defined Dimensions ƒ User-defined dimensions require: — Unique values across databases — Plan types assigned at the dimension level

Customer

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

User-Defined Dimensions

e d a

c A

You can add user-defined custom dimensions to meet the needs of your organization. User-defined dimensions can help you capture categories that your organization uses for planning. For example, you may have a group of accounts for operating expenses. You may decide to add a dimension called Project so that you can budget operating expenses on a project basis. Guidelines:

• Names must be unique and use proper naming conventions.

e l c

• Names and aliases can have up to 80 characters.

a r O

• Descriptions can have up to 255 characters.

8-2

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements For user-defined dimensions, you assign valid plan types at the dimension level, not at the member level. All members of custom dimensions are valid for plan types assigned at the dimension level. You assign the Generic dimension type to user-defined custom dimensions. You set up user-defined custom dimensions by defining the following dimension properties: Name, Valid for Plan, Aggregation for each valid plan, UDA, Member Formula, Alias, Data Storage, Two Pass Calc, Smart List, Data Type, and Attributes. NOTE

In order to assign access to members in a custom dimension, you must select Apply Security at the dimension level.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

8-3

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Attributes Overview Base dimension

Attribute dimensions Sales Rep

Customer

Company Size

Assad Akili

Small

Your IT Source

Sandy Smith

Medium

ABC Company

Doug Nichols

Large

National Accounts

Software Company

Chris Jones

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Attributes Overview

e d a

c A

Attributes are characteristics of your data. For example, products can have attributes such as colors, sizes, or flavors. Attributes enable you to add another level of granularity to your data. You create attributes for a dimension when you want to group its members according to the same criteria. For example, you might have a Product dimension with members for three product lines, some of which are sold in retail outlets and some only by catalog. When you are analyzing or reporting your data, you might need separate totals for retail and catalog sales.

e l c

a r O 8-4

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements You can add attributes to sparse dimensions such as the Entity dimension and UserDefined dimensions. You can add attributes to the Account dimension if it is designated as a sparse dimension in all plan types. NOTE

You can assign attributes only to sparse dimensions. For dense dimensions, you must change them to sparse for all plan types. When changing dimensions to dense, all attributes and attribute values for the dimension are automatically deleted. You cannot assign attributes to label-only members.

Viewing, Aggregating, and Reporting You use attributes to view, aggregate, and report on data. For example, you can view net sales by customer and sales rep.

Creating Attribute Crosstab Reports In many ways, attribute dimensions behave like regular dimensions: You can retrieve, pivot, and drill on attribute members. You can use them to create crosstab reports of attribute data for multiple attributes in the same dimension, or for attribute data from multiple dimensions. For example, Sales Reps are attributes of the Customer dimension.

y m

e d a

NOTE

c A

In order to assign attributes to a user-defined custom dimension, you must associate the attribute dimension to the user-defined custom dimension. For example, if you want to assign salesreps to the Customers dimension, you associate the Salesrep attribute dimension to the user-defined custom dimension named Customers.

e l c

e l c a r O ly & On l a e n r s e t U n I

a r O

Planning: Create and Manage Applications

8-5

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Creating Attributes

Create Attribute

Create values for the attribute

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Attributes

e d a

c A

You create attribute dimensions and add attribute values in the Dimension Library. You can then assign attribute values to dimension members. When you create forms and reports, you can filter dimension members by their attribute values. To create attributes:

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

e l c

4. Right-click the attribute dimension, and select Create Member > As Child.

a r O

5. Enter the attribute value.

8-6

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements 6. Repeat steps 4 and 5 to enter attribute values for the attribute dimension. NOTE

Only sparse dimensions can contain attributes. If the dimension you select is not a sparse dimension, the Custom Attributes button is not available. To display the sparse/dense settings for dimensions, select the Performance Settings tab.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

8-7

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Examples of Attribute Values The following are examples of attributes and their possible values. ƒ Channel (Attribute of the Product dimension) — Retail — Catalog sales

ƒ Size (Attribute of the Product dimension) — Small — Medium — Large

ƒ Sales Rep (Attribute of the Customer dimension) — John Brown — Sandy Kennedy

y m

ƒ Region (Attribute of the Customer dimension) — — — —

East South West North Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Examples of Attribute Values

e d a

c A

For a Product dimension with the members Sodas, Juices, and Coffees, you could create a Size attribute with the following attribute values: Small, Medium, and Large. After creating the attribute and attribute values, you can assign a value to each member of the Product dimension. When assigning attribute values to dimension members, you must assign all of them at the same level in the hierarchy, or an error occurs during the application refresh.

e l c

a r O 8-8

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements

Assigning Attribute Values

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Assigning Attribute Values

e d a

c A

You use the Dimension Library to assign and view attribute values. After creating attribute dimensions and values, you must associate it with a dimension (at the dimension level) before you can assign attribute values to a dimension member. To associate dimension with attributes: 1. In Master View, select a dimension.

2. Right-click the dimension and select Create Association. 3. Select Existing Property or New Property.

e l c

4. Perform a task:

a r O

• If you selected Existing Property in step 3, select the property from the Property drop-down list. • If you selected New Property in step 3, enter the new property.

Planning: Create and Manage Applications

8-9

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements 5. Enter a description. 6. From the Dimension drop-down list, select a dimension where that attribute is located. 7. Click OK. The attribute dimension associated with a user-defined dimension is displayed as a property in the property grid. 8. Right-click a dimension and select View Associations to verify dimension associations. To assign attribute values to dimension members: 1. Select the dimension member. The properties pane is displayed. 2. Select the property for the attribute dimension, and click the ellipsis button

.

3. From the Member Selector list, select an attribute value.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 8-10

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements

Member Formulas Overview

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Member Formulas Overview

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

8-11

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Adding Member Formulas

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Member Formulas

e d a

c A

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

e l c

a r O 8-12

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements When creating member formulas, you can combine the following items to perform calculations on members: • Operators, calculation functions, dimension and member names, and numeric constants • Operator type, function, value, member name, UDA, and so on that are allowed in Analytic Services formulas • Predefined formula expressions, including smart list values, that expand into a formula or value upon database refresh To add member formulas: 1. Select a dimension member. The Member Formula property has the following categories: Planning, Enterprise Analytics, and Essbase. 2. In the Properties Grid for the member, double-click Member Formula. 3. Click

y m

. The Memo Editor dialog box is displayed.

e d a

4. Enter a formula. 5. Click Word Wrap to wrap the formula text. 6. Click Validate and click OK. 7. Click OK.

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

8-13

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Adding User-Defined Attributes

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding User-Defined Attributes

e d a

c A

You define user-defined attributes (UDAs) for members to further describe characteristics of those members. You can use UDAs within calculation scripts, member formulas, and reports. UDAs are words or phrases that describes a member. For example, you can apply a UDA such as New Market to selected members within Markets. You create, change, and select UDAs in the Dimension Library properties grid. UDAs enable you to calculate and report on specific subsets of data. They essentially provide a way to group members. For example, in a report or calculation, you can request all states with a New Market UDA. UDAs are specific to dimensions. For example, if you create a UDA for an Account member, that UDA is available only for nonshared Account members. If you delete the UDA, then it is removed for all Account members. If you want to make the UDAs available for multiple dimensions, you must create the same UDA for each dimension in which it is used.

e l c

a r O 8-14

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements To associate UDAs with members: 1. Select the dimension whose members you want to associate with the UDA. 2. Select a member in the dimension. 3. In the Property Grid for the member, double-click UDA. 4. Click

.

5. Enter the UDA. TIP

Use a comma to separate multiple UDAs for a member. You can change a UDA by double-clicking the UDA and retyping the name. You can delete the UDA by double-clicking the UDA and deleting the entry. NOTE

If you delete UDAs, you must update all member formulas, calculation scripts, and reports that reference those UDAs.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

8-15

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Smart Lists Overview ƒ Customer_Service_Class uses a smart list ƒ Network Sales, Chip Sales, and Computer Sales use data values

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Smart Lists Overview

e d a

c A

Smart lists are custom drop-down lists that you can access from data form cells in Planning applications. If a data cell is assigned a smart list, you can click on an arrow in the data cell to see a pick list of values. When you click in data form cells that contain members associated with smart lists, you can select an item from the drop-down list instead of entering data manually. You cannot type in cells that contain smart lists. For example, you can create a smart list for customer service levels with the following values: • Platinum

e l c

• Gold

• Silver

a r O

• Bronze

8-16

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements You can associate the Customer Service Levels smart list with the Customer Service Class account member. On a data form, if you click in the account named Customer Service Class (which is associated with the Customer Service Levels smart list), you can choose from a drop-down list with these selections: Platinum, Gold, Silver, and Bronze.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

8-17

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Creating Smart Lists

Smart List Dimension

Smart List Values

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Smart Lists

e d a

c A

You create smart list dimensions and members in the Dimension Library. You also assign properties to smart lists in the Dimension Library. Smart list creation process:

• Create a new dimension with Smart List selected as the dimension type. • Create members in the dimension. (The members are the items that are displayed in the drop-down list, data form, or grid.) • Assign properties to the smart list dimension and members.

e l c

• Optionally, you can do any of the following tasks: - Set up smart lists on data forms

a r O

- Use smart lists values in member formulas and business rules. - Set how #Missing cells associated with smart lists are displayed in data forms.

8-18

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements Guidelines: • Smart lists are associated with dimension members. Typically, the Account dimension is used to associate smart lists with members. • After associating smart lists with dimension members, reserve those members to store only smart list values. These members should not be used to store other data values. • Consider creating new members and setting up a separate rollup with the dimension. • You can create reports to capture the smart list information. You must use planning details as your data source to report on smart list data. • Smart lists can be associated with more than one member, but those members must be level 0 members. • Smart lists are not plan type specific. • Smart List names and aliases must begin with a letter, and can contain letters, numbers, underscore, and dollar sign characters. Smart List names cannot contain spaces, or be Java reserved words.

y m

e d a

To create smart lists: 1. In the Dimension Library, select File > New > Dimension. The Add New Dimension dialog box is displayed. 2. Enter the name and description.

e l c a r O ly & On l a e n r s e t U n I

c A

3. From the Type drop-down list, select SmartList. 4. Click OK.

5. In Master View, right-click the Smart List dimension and choose Create Member > As Child. The New Member dialog box is displayed.

6. In the Name text box, enter a name and click OK. 7. In Master View, select the member name.

8. In the Property Grid, from the category drop-down list, select Planning.

e l c

9. In the Label text box, type a label and click Save.

a r O

10. Create additional members, as necessary, for the dimension.

Planning: Create and Manage Applications

8-19

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Modifying Smart Lists Smart List Dimension Properties

Smart List Value Properties

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Modifying Smart Lists

e d a

c A

You modify the following smart list properties in the property grid: Property Label

Enter the text to display when the Smart List is selected. Spaces and special characters are allowed. Smart List labels can reference a resource, which can be translated into different languages.

Start Value Increment

e l c

Display Order

a r O 8-20

Description

Populates the value property of the first member in the smart list. Enter the value that is appended to the value of the last member in the list to determine the value for the selected member. Select to sort the smart list by ID, Name, or Label.

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements Property

Description

#Missing Data Form Label

Select how #Missing values are represented in cells associated with the smart list.

#Missing Drop Down Label

Enter a label to be displayed as an entry in the smart list whose value is #Missing.

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

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

8-21

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Associating Smart Lists with Members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Associating Smart Lists with Members

e d a

c A

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

e l c

a r O 8-22

Planning: Create and Manage Applications

Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements

Setting Data Forms to Use Smart Lists

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Setting Data Forms to Use Smart Lists

In order to work with smart lists on data forms, you must select the dimension member so that it is displayed on the data form. You must also set the data form properties so that you can work with smart lists on that data form. Keep in mind the following key points:

• You can assign smart lists to the rows or columns. • You cannot use smart lists in the pages.

• You must assign smart lists to level 0 members.

e l c

a r O

Planning: Create and Manage Applications

8-23

Module 2

Creating Application Structures

Lesson 8 Creating User-Defined Elements

Summary In this lesson, you should have learned to: • Create user-defined dimensions • Create attributes and assign attribute values • Describe member formulas • Add member formulas • Create Smart Lists

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 8-24

Planning: Create and Manage Applications

M O D U L E

3

Loading Metadata

8

Overview The aim of this module is to load metadata used by Planning applications. Then you create application views and deploy those application views to the Planning server. You also set up Exchange Rates. Lessons in this module include: • Loading Metadata from a File • Creating Application Views

y m

• Deploying Applications • Setting Up Exchange Rates

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

e d a

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

L E S S O N

9

Loading Metadata from a File

9

Objectives At the end of this lesson, you should be able to: • Format metadata files • Load and extract metadata from flat files • Create profiles • Map dimensions and dimension properties

y m

• Load metadata from interface tables

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

Metadata Load Files ƒ You can load data from flat files or interface tables (staging area) ƒ Load files can contain metadata for: — Account, Entity, Scenario, Version, and Custom dimensions — Period, Year dimensions — Currency dimension

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Metadata Load Files

e d a

c A

You can load metadata into the Dimension Library from interface tables or from flat files. If you load data from interface tables, you load data from a specific database. If you load metadata from flat files, you can include any combination of dimensions in the load file, and you can have multiple load files. For example, you could have one load file for the Account and Custom dimensions and another load file for the Entity dimension.

e l c

a r O 9-2

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Formatting Load Files ƒ Load files are divided into sections with an exclamation point as the section delimiter. ƒ Load files sections can be in any order: Dimensions, Dimension Associations, Dimension Members, Dimension Hierarchies. ƒ The line defining the column names for the section begins with an apostrophe immediately under the section header. ƒ You can place the column names in any order.

!Members= P roducts 'Name|DataT ype|SmartList|TwoPassCalc|UDA|Salesrep|Description| MemberFormula Tennis Rac kets|Unspecified||||Thomas Brown||| Tennis Bal ls|Unspecified||||Sandy Spencer|||

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Formatting Load Files

y m

e d a

c A

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

e l c

• True and false values are represented as Y for true and N for false.

a r O

• You can use a pipe (|), semicolon (;), comma (,), space, or tab as the file delimiter.

Planning: Create and Manage Applications

9-3

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

Load File Sections For each dimension: ƒ Add an entry to the Dimensions section to define the dimension. ƒ Add a !Members section to specify members and their properties. ƒ Add a !Hierarchies section to specify parent-child relationships. !Hierarchies=F unctional Entity 'Parent|Child| DataStorage|MemberValidForPlan1|Plan1Aggregation #root|United S tates|StoreData|Y|+| United States| California|StoreData|Y|+| California|San Francisco|StoreData|Y|+|

ƒ Add entries to the DimensionAssociations section for each property with an association to another dimension. !Section=Dimen sionAssociations 'BaseDimension |Property|TargetDimension Functional Ent ity|Currency|Currency

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Load File Sections

e d a

c A

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

e l c

a r O 9-4

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Formatting Dimensions Sections ƒ Add an entry for each dimension in the load file. ƒ The required columns are Name, DimensionClass and DimensionAlias. !Section= Dimensions 'Name|Dim ensionClass|DimensionAlias|DimDa taStorage HP Accoun ts|Account|HP Accounts|NeverShar e Calendar Months|Period|Calendar Months|Ne verShare Standard Year|Year|Standard Year|NeverSha re Version|V ersion|Version|NeverShare Scenario| Scenario|Scenario|NeverShare Currency| Currency|Currency|NeverShare Functiona l Entity|Entity|Functional Entit y|NeverShare

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Formatting Dimensions Sections

e d a

c A

Each dimension included in the load file must be identified in the Dimensions section as follows: Column Name

Description

Name of up to 50 characters (required)

DimensionClass DimensionAlias

e l c

Type of dimension, such as account or entity (required) Alias or further descriptor for the dimension

a r O

Planning: Create and Manage Applications

9-5

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

Formatting Members Sections ƒ Use a separate members section for each dimension. ƒ Use Y for Yes and N for No. !Members=Scenario 'Name|DataType|StartYear|EndYear|StartPeriod|EndPeriod|UseBegBalance|EnableProcess Management|SmartList|ExchangeRateTable|TwoPassCalc|UDA|Description|MemberFormula Current|Unspecified|FY06|FY09|Jan|Dec|N|N||A_FXRate|N|||| Actual|Unspecified|FY07|FY07|Jan|Dec|N|N||A_FXRate|||| Budget|Unspecified|FY08|FY10|Jan|Dec|Y|Y||B_FXRate||||

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Formatting Members Sections

e d a

c A

You set up the metadata dimension members in a members section. You begin a members section by entering the following line, replacing the angle brackets () with the dimension name: !Members=

You need not include columns for all member properties for the dimension class, and you can set up the columns in any order.

e l c

a r O 9-6

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File Account Valid Planning properties for the Account dimension class: Name,DataType,SourcePlanType,AccountType,ExchangeRateType, VarianceReporting,TimeBalance,SmartList,UDA,TwoPassCalc, SkipValue,WeeksDistribution,MemberFormula,DataStorage, MemberValidForPlan1,MemberValidForPlan2,MemberValidForPlan3, MemberValidForWorkforce,MemberValidForCapex,Plan1Aggregation, Plan2Aggregation,Plan3Aggregation,WorkforceAggregation, CapexAggregation Entity Valid Planning properties for the Entity dimension class: Name,DataType,Currency,MemberValidForPlan1,MemberValidForPlan2, MemberValidForPlan3,MemberValidForWorkforce,MemberValidForCapex, Plan1Aggregation,Plan2Aggregation,Plan3Aggregation, WorkforceAggregation,CapexAggregation,DataStorage

y m

Scenario Valid Planning properties for the Scenario dimension class:

e d a

Name,DataType,StartYear,EndYear,StartPeriod,EndPeriod, UseBegBalance,EnableProcessManagement,SmartList,ExchangeRateTable TwoPassCalc,UDA,Description,MemberFormula,MemberValidForPlan1, MemberValidForPlan2, MemberValidForPlan3,MemberValidForWorkforce, MemberValidForCapex,DataStorage

e l c a r O ly & On l a e n r s e t U n I

c A

Version Valid Planning properties for the Version dimension class:

Name,DataType,VersionType,EnableProcessManagement,SmartList, TwoPassCalc,UDA,Description,MemberFormula,MemberValidForPlan1,Mem berValidForPlan2,MemberValidForPlan3, MemberValidForWorkforce, MemberValidForCapex,DataStorage Period Valid Planning properties for the Period dimension class:

Name,DataType,SmartList,TwoPassCalc,DTSGeneration,DTSEnabled, UDA,Description,MemberFormula,DataStorage,MemberValidForPlan1, MemberValidForPlan2, MemberValidForPlan3,MemberValidForWorkforce, MemberValidForCapex,Plan1Aggregation,Plan2Aggregation, Plan3Aggregation,WorkforceAggregation,CapexAggregation,PeriodType

e l c

a r O

Planning: Create and Manage Applications

9-7

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File Year Valid Planning properties for the Year dimension class: Name,DataType,SmartList,TwoPassCalc,UDA,Description,MemberFormula MemberValidForPlan1,MemberValidForPlan2,MemberValidForPlan3, MemberValidForWorkforce,MemberValidForCapex,DataStorage Currency Valid Planning properties for the Currency dimension class: Name,DataType,Symbol,Scale,ThousandSep,DecimalSep,NegativeSign,Ne gativeColor,ReptCurrency,TriangulationCurrency,CurrencyCode,Smart List,TwoPassCalc,UDA,Description,MemberFormula, MemberValidForPlan1,MemberValidForPlan2,MemberValidForPlan3, MemberValidForWorkforce,MemberValidForCapex,DataStorage Generic Valid properties for Generic dimension class: Name,DataType,SmartList,TwoPassCalc,UDA,DataStorage,Description,M emberFormula,MemberValidForPlan1,MemberValidForPlan2, MemberValidForPlan3,MemberValidForWorkforce,MemberValidForCapex, Plan1Aggregation,Plan2Aggregation,Plan3Aggregation, WorkforceAggregation,CapexAggregation

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 9-8

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Formatting Hierarchies Sections ƒ Use this format: | ƒ Represent top-level members as children of #root: #root|

Entity Geographical UnitedStates Cal ifornia

!HIERARCHIES=Entity Parent|Child|DataStorage|MemberValidForPlan1|Plan1Aggregation

1000

#root|Geographical|StoreData|Y|+| Geographical|United States|StoreData|Y|+| Geographical|Europe|StoreData|Y|+| UnitedStates|California|StoreData|Y|+| California|1000|StoreData|Y|+| California|Plant1|StoreData|Y|+| California|WestSales|StoreData|Y|+|

Plant1 WestSales Connecticut

y m

Massachusetts

e d a

Europe Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Formatting Hierarchies Sections

c A

Hierarchies sections define parent-child relationships within dimensions. You begin the section by entering the following line, replacing the angle brackets () with the dimension name: !HIERARCHIES= NOTE

The Hierarchies section is required for new and existing dimensions that use the replace method. It is optional for existing dimensions that use the merge method. Parent and Child properties are required.

e l c

a r O

Planning: Create and Manage Applications

9-9

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

Formatting DimensionAssociations Sections !Section=Dimen sionAssociations 'BaseDimension |Property|TargetDimension Functional Ent ity|Currency|Currency

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Formatting DimensionAssociation Sections

e d a

c A

You can associate dimension properties with members of another dimension. By setting dimension associations, you enable end users to set property values by selecting members from the associated dimension. Required columns for the DimensionAssociation section: Column BaseDimension Property TargetDimension

e l c

Description

Dimension for which you want to set up the association Property that you want to link to another dimension Dimension to which to link the property

a r O 9-10

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File You can automate property association assignments by indicating the associations in the load file. The text on the slide is a sample section from a file that you can use to load metadata. You can also add property associations later by creating lists in the Dimension Library. The illustration on the slide is one such example. Association-setting privileges are determined by role. For example, administrators set associations for Currency, Start and End Period, and Start and End Year. Business users can set associations for smart lists. To associate dimension properties in the Dimension Librar y 1. Right-click a dimension and select Create Association. The Create New Association dialog box is displayed. 2. Select options, enter text, and click OK.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

9-11

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

Loading Metadata Process You perform the following tasks to load metadata: ƒ Create an import profile ƒ Specify load options ƒ Map dimensions in the load file to dimensions in the Master View ƒ Map fields for the load file to dimension properties in Master View ƒ Run the profile

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Loading Metadata Process

e d a

c A

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

e l c

a r O 9-12

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Creating Import Profiles

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Import Profiles

e d a

c A

You create profiles to import metadata from flat files or interface tables. To create import profiles:

1. Select File > Import > Create Profile.

The New Profile dialog box is displayed. 2. Enter a name for the profile.

3. From the Import Type drop-down list, select FlatFile or Interface Tables.

e l c

4. Optional: Enter a description for the profile. 5. Perform an action:

a r O

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

Planning: Create and Manage Applications

9-13

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File 6. Click OK. 7. Follow the wizard to complete the profile setup: • Load files: Select options for column delimiters, removal of single quotation marks from strings, and removal of spaces from load files. • Flat files and interface tables: Map dimensions and properties.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 9-14

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Mapping Dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Mapping Dimensions

e d a

c A

You map the dimensions in the load file to dimensions in Master View. For each dimension in the flat file, a drop-down list of dimensions of the same dimension class in Master View is displayed. You select the Master View dimension to which you want to map the flat file dimension. NOTE

If a dimension name in Master View exactly matches a dimension name of the same dimension class in the load file, the matching dimension is the default selection.

e l c

When you map a dimension in the load file to a dimension in Master View, you can merge or replace members:

a r O

• Merge—Updates members with the information in the file. New members are added to the application.

Planning: Create and Manage Applications

9-15

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File • Replace—Replaces metadata with the metadata in the file. Removes members from the application if they are not present in the metadata file. You can also choose to create a new dimension rather than map to an existing dimension.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 9-16

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Mapping Properties

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Mapping Properties

e d a

c A

For each column for a dimension in the flat file, a drop-down list of properties for the same dimension class in Master View is displayed. You select the property to which to map the column. NOTE

If a property name in Master View exactly matches a property name in the load file, that property is mapped by default. Select Ignore Nulls if you want blank values for a record in the load file to be ignored. Otherwise, blank values are treated as data, and the property status is changed from default to defined. A status of defined prevents the property from inheriting values from ancestors.

e l c

a r O

Planning: Create and Manage Applications

9-17

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

Running Import Profiles

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Running Import Profiles

e d a

c A

After creating a profile, you are prompted to execute the profile. If you want to run it at another time, you can initiate the import from the Import Dimensions dialog box (File > Import > Import Dimensions). You must select a file to upload each time you run an import. The file you select populates the Name field. You also select the application into which to import the metadata. You can select Master View or an application view. If you select an application view, you can update existing members properties, but you cannot create new members. All new members must be added to Master View.

e l c

a r O 9-18

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Viewing Job Status

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Viewing Job Status

e d a

c A

You can view job status by navigating to the Job Status page. After the import job runs, you can select the click here to navigate to jobs link. You can navigate to the Job Status page at any time by selecting Running Jobs from the File menu.

e l c

a r O

Planning: Create and Manage Applications

9-19

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

Viewing Import Errors

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Viewing Import Errors

e d a

c A

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

e l c

a r O 9-20

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Loading Metadata from Interface Tables Process before Interface Table Import

Interface Table Import Process in Hyperion System 9

Interface Tables

EPM Arcitect Fi nancial Management

EPR System

Dimension Library

Data Synchronization Planning

ETL System Interface Tables E PM Architect Database

e d a Essbase

G eneral Ledger System Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Loading Metadata from Interface Tables

y m

c A

EPM Architect interface tables are database tables used to import metadata from external systems into the Dimension Library. They represent an alternative to flat files.

Interface Tables Process 1.

Create a EPM Architect interface database by using a relational database such as MS SQL Server or Oracle.

2.

In the interface database, create tables that correspond to the sections in a metadata flat file. For example, you could create a database table for dimension associations, with fields for Base Dimension, Property, and Target dimension (similar to the DimensionAssociations section of a flat file). A database template script assists in creating the required tables.

e l c

a r O 3.

Load metadata from the external systems into the tables.

Planning: Create and Manage Applications

9-21

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File 4.

Import the metadata from the interface database into the Dimension Library by using an import profile and following the same procedure as flat files.

Setting Up Interface Tables To import from Interface Tables, from the Import Type drop-down list, select Interface Tables. You can set up two types of interface tables: • System tables—Use these tables when you work with the import module for profile creation and execution. • User-defined tables—Use these tables when you load dimensions, members, member properties, and member hierarchies. At a minimum, you must set up Member and Hierarchy tables. In the Member table, Name is required. In the Hierarchy table, Parent and Child are required. If you no longer need the stored metadata, you can clear the information from the tables.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 9-22

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 9 Loading Metadata from a File

Summary In this lesson, you should have learned to: • Format metadata files • Load and extract metadata from flat files • Create profiles • Map dimensions and dimension properties • Load metadata from interface tables

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

9-23

Module 3

Loading Metadata

Lesson 9 Loading Metadata from a File

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 9-24

Planning: Create and Manage Applications

L E S S O N

1 0

Creating Application Views

10

Objectives At the end of this lesson, you should be able to: • Create application views • Add dimensions to application views • Configure application settings • Remove dimensions

y m

• Set up dimension associations • Adjust performance settings

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

e d a

Module 3

Loading Metadata

Lesson 10 Creating Application Views

Creating Application Views

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Application Views

e d a

c A

An application view represents a selection of the Master View dimensions required for an application. Application view types: Type

Description

Generic

Planning

e l c

Consolidation

a r O

A template that enables you to create an application view without assigning a specific product. A generic application view displays properties for all products. Planning application view

Financial Management application view

Enterprise Analytics

Enterprise Analytics application view

Essbase Analytics

Essbase application view

10-2

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views The Application Library displays all application views in EPM Architect. You can create application views in the Application Library or Dimension Library provided you have been assigned the application creator role. To create application views: 1. In EPM Architect, select Navigate > Administer > Application Library. 2. In the File menu, select New > Application View. 3. Enter the name for the application view. Although the name can contain up to 50 characters, Planning application names can contain only 8 characters. Therefore, if you use the same name for the application view and the Planning application, the application view name can contain only 8 characters. 4. From the Type drop-down list, select Planning. 5. Optional: Enter a description for the application.

y m

6. Click OK. The Dimension Library is displayed with the application view in the middle pane. The application view does not contain dimensions. After creating application views, you can perform these actions:

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

• Open views (In the Application Library, select File > Open Application View.) • Display the application as an additional pane to the right of the Master View pane. • Only display the application view pane by closing the Master View pane.

e l c

a r O

Planning: Create and Manage Applications

10-3

Module 3

Loading Metadata

Lesson 10 Creating Application Views

Dimension Library Panes Master view

Application view

Properties grid

y m

e d a

Application Library Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Dimension Library Panes Pane

c A

Description

Master View Application view Properties grid

Lists all dimensions and members available in the Master Library Lists all dimensions and members that comprise the application view Shows the properties for the selected dimension or member

You can navigate to the Application Library by selecting the tab located at the bottom of the window.

e l c

a r O 10-4

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Adding Dimensions to Application Views You can drag dimensions from Master View to an application view.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Dimensions to Application Views

e d a

c A

After creating an application view, you can add dimensions by dragging them from the Master View pane to the application view pane. Planning application view requirements:

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

e l c

• The Scenario dimension requires an association with the Period and Year dimensions to enter starting and ending time period values.

a r O

Planning: Create and Manage Applications

10-5

Module 3

Loading Metadata

Lesson 10 Creating Application Views • If you want to assign attribute values or aliases to dimension members, you must associate the Attribute and Alias dimensions with those base dimensions. For example, if you want to assign attributes or aliases to the Entity and Account dimensions, you must associate the Attribute and Alias dimensions with their respective properties in the base dimensions, Entity and Account. Dimension association guidelines: • You need not associate a smart list with a main dimension to select a smart list in the Smart List property field. • Dimensions created in the Dimension Library do not have default associations. You associate dimensions in Master View, not in application views. • For dimensions loaded from flat files, you must specify associations in the flat file. • If you upgrade an application to Planning 9.3, the associations may already be assigned.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 10-6

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Excluding Members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Excluding Members

e d a

c A

After adding dimensions to application views, you can exclude selected members from the dimensions. For example, for a revenue forecasting application, you could exclude all accounts except revenue accounts from the Account dimensions. To exclude members from dimensions:

• Right-click a member and select Exclude Member.

If you exclude a parent member from a dimension, its descendants are excluded as well. To show excluded members:

e l c

• Right-click the dimension and select Show Excluded Members.

a r O

A list of excluded members is displayed, and you can select members that you want to include in the dimension.

Planning: Create and Manage Applications

10-7

Module 3

Loading Metadata

Lesson 10 Creating Application Views

Member Properties Inheritance from application view ancestor overrides inheritance from Master View.

e d a

Property values loaded or manually entered override both Master View and ancestor values.

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Member Properties

y m

c A

When you add dimensions from Master View to application views, the member property values are inherited from Master View. If you modify member properties in Master View, the properties are also updated in all application views containing that member. Member property rules:

• If you edit member properties in the application views, the Master View property values are overridden. Updates to member property values in Master View no longer update property values in the application views. • If a member inherits a property value from Master View and from an ancestor in an application view, the ancestor value overrides the value inherited from Master View.

e l c

a r O 10-8

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

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

System properties

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Configuring Application Settings

e d a

c A

You configure application-wide settings in the application view. Application-setting configuration process:

1. Select the Planning application view name to display its dimension properties in the Properties grid. Properties that you set at the highest level apply to all dimensions in the application view. 2. Select the Planning category.

3. Indicate up to five valid plan types: Plan1, Plan2, Plan3, Workforce, and Capex.

e l c

4. Set up names for the plan types. Plan type names can contain up to 8 characters. 5. Specify the default currency and indicate whether the planning application contains multiple currencies.

a r O

Planning: Create and Manage Applications

10-9

Module 3

Loading Metadata

Lesson 10 Creating Application Views 6. Set the base time periods (monthly, quarterly, or custom), weekly distribution, starting fiscal year and month, and total number of years. 7. Specify the default Alias Table for the application view. You can also view or modify system properties for application views. To view or modify system properties: 1. In the application view pane, select an application. 2. From the Category drop-down list, select System. 3. View or modify the settings.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 10-10

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Configuring Plan Types ƒ Essbase database created for each plan type ƒ Three customizable plan types ƒ Data sharing between plan types

Budgeting Application

=

Plan Type 1

Plan Type 2

Plan Type 3

Workforce

Capex

Additional modules available for purchase

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Configuring Plan Types

y m

e d a

c A

In the Properties grid, you can indicate up to five plan types for the application view. An Essbase database is created for each plan type. After creating an application view, you cannot change the name or number of plan types. The number of plan types depends on the needs of your organization. For example, if the Sales Department has a yearly revenue plan, and the finance department has a P&L plan, you can define two plan types—Revenue and P&L. As you create accounts, entities, and other elements of the application, you associate them with plan types. The association ensures that the database contains only relevant application dimensions, members, and data values, and that application design, size, and performance are optimized.

e l c

a r O

Planning: Create and Manage Applications

10-11

Module 3

Loading Metadata

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

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

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 10-12

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Specifying Currency ƒ Set default currency for entities ƒ Specify whether multiple currencies are used

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Specifying Currency

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

10-13

Module 3

Loading Metadata

Lesson 10 Creating Application Views

Setting Up Time Periods

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Up Time Periods

e d a

c A

You select the base time period and the monthly distribution pattern based on the number of fiscal weeks in a month. The base time period options are the bottom-level time periods in the application. Predefined options are months or quarters. You can create custom base time periods, such as weeks or days. You can select monthly distribution patterns to determine how data entered into a summary time period is distributed or spread among base time periods. During data entry, users can enter data into summary time periods, such as years or quarters. Planning distributes these values over the base time periods that constitute the summary time period.

e l c

a r O 10-14

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views You can select a weekly distribution pattern other than Even Distribution. In that case, Planning treats quarterly values as if they were divided into 13 weeks and distributes weeks according to the pattern you selected. For example, if you select the 5-4-4 pattern, Planning treats the first month in a quarter as if it has five weeks, and the last two months in the quarter as if they have four weeks. The options for the weekly distribution pattern are available only if you select the 12 Months base time period option. You specify the fiscal start year, the fiscal start month, and the total number of years in the application view. The fiscal start year determines the starting fiscal year for the application view. You cannot change the option later. When specifying the fiscal start year, consider how much historical data your organization needs in the application view.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

10-15

Module 3

Loading Metadata

Lesson 10 Creating Application Views

Removing Dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Removing Dimensions

e d a

c A

If you do not want to include dimensions in application views, you can remove them only before deploying the application views for the first time. To remove dimensions from application views:

• In the application view pane, right-click the dimension, and select Remove Dimension. The dimension is removed from the application view.

e l c

a r O 10-16

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Setting Up Dimension Associations ƒ Associate currency property for the Entity dimension with the Currency dimension ƒ Associate Alias dimension with the alias property of a base dimension such as the Account or the Entity dimensions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Up Dimension Associations

e d a

c A

In the Master Library, you create dimension associations for properties whose values refer to members of another dimension. Examples:

• You can associate the currency property of the Entity dimension to the Currency dimension to ensure that the Currency dimension is accessed to retrieve the value for the currency members in the Entity dimension. • When you assign Alias values to dimension members, you create Alias information in the Master Library and associate the Alias property member of the dimension (for example, the Alias property in the Account dimension with the Alias dimension.

e l c

a r O

Planning: Create and Manage Applications

10-17

Module 3

Loading Metadata

Lesson 10 Creating Application Views To set up dimension associations, you first create the association in the Master Library. Next, you activate the association within the application view. Because you activate the dimension associations for each application view for which it is valid, you can have different Planning application views set up with different dimension associations, and you can have some Planning application views set up with specific dimension associations that are different from the dimension associations set up for Financial Management application views. NOTE

You can turn on all associations within an application view with one command. Select the application view, right-click, and select Activate all associations.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 10-18

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Choosing Performance Settings for Optimal Performance Use Performance Settings to optimize the dimension order and set dense and sparse dimension settings.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Choosing Performance Settings for Optimal Performance Before you load and calculate data, you can optimize the Essbase database outline settings. Optimizing means analyzing the dense and sparse settings for dimensions to see their effect on block size. Use Performance Settings to make adjustments. You can modify the sparse and dense setting for a dimension and its order in the outline. To categorize dimensions as dense or sparse and set evaluation order: 1. From the Application Library, right-click an application view and select Performance settings.

e l c

The Plan Type Performance Settings dialog box is displayed.

a r O

Planning: Create and Manage Applications

10-19

Module 3

Loading Metadata

Lesson 10 Creating Application Views 2. From the drop-down list, select a plan type. Dimensions belonging to the plan type are displayed with the number of dimensions for the plan type. NOTE

Applications can have up to five plan types. If applications are created with a single currency, the HSP_Rates dimension is not displayed.

3. In the Density column, double-click a cell and select one of the following: • Sparse—Sparse dimensions lack data values for the majority of member combinations. A sparse dimension is a dimension with a low percentage of available data positions filled. • Dense—For dense dimensions, there is a high probability that one or more data points is occupied in every combination of dimensions.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 10-20

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Dimension Order Most Dense Dense Dimensions Least Dense

Smallest Aggregating Sparse Dimensions Largest

Smallest

y m

Nonaggregating Sparse Dimensions

e d a

Largest

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Dimension Order

c A

On the Plan Type Performance Settings screen, you can view and modify the order of the dimensions in the outline. The order of dimensions is critical in the structure and performance of Essbase databases. Dense dimensions calculate faster than sparse dimensions, so dimensions should be in order of most to least dense. You can speed calculation time by changing the order for calculating dimensions. Separate sparse dimensions into aggregating and nonaggregating dimensions, with aggregating dimensions before non-aggregating dimensions. NOTE

Aggregating dimensions aggregate children into the parent to create new data; non-aggregating dimensions do not create new data by the hierarchies (for example, a Scenario or Version dimension).

e l c

a r O

Planning: Create and Manage Applications

10-21

Module 3

Loading Metadata

Lesson 10 Creating Application Views You can optimize performance by ordering dimensions according to the following guidelines: • Make Period and Account dense. • Order dense dimensions from the most to least dense. The most dense is usually Period (Time), followed by Account. Separate sparse dimensions into aggregating and nonaggregating dimensions. Place aggregating dimensions before nonaggregating dimensions. Order sparse dimensions from smallest to largest.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 10-22

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 10 Creating Application Views

Summary In this lesson, you should have learned to: • Create application views • Add dimensions to application views • Configure application settings • Remove dimensions • Set up dimension associations • Adjust performance settings

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

10-23

Module 3

Loading Metadata

Lesson 10 Creating Application Views

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 10-24

Planning: Create and Manage Applications

L E S S O N

1 1

Deploying Applications

11

Objectives At the end of this lesson, you should be able to: • Validate application views • Compare application views • Deploy applications views • Review Planning outlines in Administration Services

y m

• Redeploy application views

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 3

Loading Metadata

Lesson 11 Deploying Applications

Deploying Applications Overview

EPM Architect Dimension Server

Planning Application Server

HYPlan application view

HYPlan application

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Deploying Applications Overview

e d a

c A

In EPM Architect, you create application views to describe the dimensionality and other information required for an application. To create the application itself, you first validate, and then deploy the application view to a Planning server. The deployment process automatically creates an application on the application server. You validate and deploy application views from the EPM Architect Application Library.

e l c

a r O 11-2

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 11 Deploying Applications

Deployment Process ƒ Validating application views ƒ Deploying application views to Hyperion products ƒ Creating the application files in relational and OLAP databases

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Deployment Process

e d a

c A

In the EPM Architect Application Library, you deploy application views as follows: • Validate application views

• Compare application views

• Deploy application views to a Planning server

• Create application files in relational and OLAP databases

e l c

a r O

Planning: Create and Manage Applications

11-3

Module 3

Loading Metadata

Lesson 11 Deploying Applications

Validating Application Views

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Validating Application Views

e d a

c A

You validate application views before deploying them to ensure that the following conditions are met: • The Start Year property is defined and contains four digits (for example, 2006). • Members in Year dimensions start with FY, followed by a two-digit year (for example, FY06). • The Start Year property and first year in the Year dimension describe the same year in different formats. For example, if the Start Year is 2006, the first year must be FY06.

e l c

• The Start Month property is defined.

a r O

• The Default Alias Table property is defined. • The Default Currency property is defined.

11-4

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 11 Deploying Applications • Application view include predefined dimensions. Single-currency application views require Scenario, Version, Entity, Account, Period, and Year. Multicurrency application views require Scenario, Version, Entity, Account, Period, Year, and Currency. • The Base Time Period and Weeks Distribution properties are defined. • At least one plan type is set up. You can add plan types later and redeploy the application views; however, you cannot delete plan types after deploying the application views. To validate application views: 1. In Workspace, select Navigate > Administer > Application Library. 2. Right-click an application view and select Validate. The Validation Summary dialog box is displayed. 3. Perform an action:

y m

• If validation errors occurred, proceed to step 4. • If no validation errors occurred, skip to step 5.

e d a

4. Click Details to review the errors. 5. Click OK.

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

11-5

Module 3

Loading Metadata

Lesson 11 Deploying Applications

Comparing Application Views

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Comparing Application Views

e d a

c A

You can compare application views to determine how they differ from those stored elsewhere. Comparison methods:

• Compare to Master Library—Compares the dimensions and members in an application view to the dimensions and members in Master View in the Dimension Library • Compare to Deployed Application—Compares an application view to a deployed application

e l c

• Compare to Application As-Of—Compares an application view to a prior version as of a specific date and time

a r O 11-6

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 11 Deploying Applications The Compare window has three panes: • Dimension Compare Results—Displays dimensions and members that were added or deleted. The Master View items are displayed in the left column, and the application view items are displayed in the right column. The number of differences (at or below the selected level) is displayed in parentheses. You can expand and collapse the dimensions as necessary. When you select an item, additional details are displayed in the panes on the right. • Application Compare Summary—Displays a summary of all changes between the application views or between the application view and Master View, including Total Member Count, Total Differences, Additions, Removes, and Filters. The summary displayed depends on what you selected in the Dimension Compare Results pane. • Property Compare Results—Displays changed member properties for the selected member. To compare application views: 1. Right-click an application view, select Compare, and select a comparison method:

y m

• Compare to Master Library

e d a

• Compare to Deployed Application • Compare to Application As-Of

c A

2. After the progress bar indicates 100% complete, click View Results.

e l c a r O ly & On l a e n r s e t U n I

The Compare window is displayed.

3. In the Dimension Compare Results pane, perform an action: • Select a dimension to view the results in the Compare Summary pane. • Select a member to view the results in the Property Compare pane NOTE

When a member is added or deleted within Master View, the application view inherits the changes from Master View. You can determine that changes were made by noting the sync status, and you can run one of the comparison reports to determine the differences.

e l c

a r O

Planning: Create and Manage Applications

11-7

Module 3

Loading Metadata

Lesson 11 Deploying Applications

Deploying Application Views

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Deploying Application Views

e d a

c A

To deploy application views:

1. Ensure that the Planning Application Server is started.

2. In Workspace, select Navigate > Administer > Application Library. 3. Right-click an application view and select Deploy. NOTE

Ensure that the Planning Application Server is started before you deploy any Planning application views.

e l c

a r O 11-8

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 11 Deploying Applications 4. Optional: If validation errors occur, then you can view validation error details. To view the number of errors, click View Errors. Then to view the list of errors, click Details. 5. Enter the requested information. Reminders: • Planning instances are used to link EPM Architect to a Planning Application Server. • If you are deploying a Planning application view for the first time, select Create Outline to create the Essbase outline. 6. Click Deploy. In the Application Library, the status of the application view is updated to Deployment Pending. 7. Select Navigate > Administer > Library Job Console to view the status of the deployment. The Library Job Console displays the current job status and the percent completion. You can click the Attachment link to view an error log. Should deployment of the application view fail, the error log contains value information about the reasons for the failure. When the deployment is completed, the status and deployment timestamp are updated in the Application Library, and the application view is deployed to the Planning Web application server as a Planning application.

e l c

e l c a r O ly & On l a e n r s e t U n I

y m

e d a

c A

a r O

Planning: Create and Manage Applications

11-9

Module 3

Loading Metadata

Lesson 11 Deploying Applications

Creating Essbase Databases

Outline .otl Calculation Script .csc Report Script .rep

y m

Load Rules .rul

Copyright © 2007, Oracle. All rights reserved.

Creating Essbase Databases

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

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

e l c

• Report scripts—Define reports based on data in one or more databases. The file extension is .rep.

a r O

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

11-10

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 11 Deploying Applications

Reviewing Planning Outlines

View Pane

Outline Editor

y m

Copyright © 2007, Oracle. All rights reserved.

Reviewing Planning Outlines

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

After deploying Planning applications, you can perform the following tasks in Administration Services Console: • View the database outline

• Add formulas to members in the outline • Create load rules for loading data • Load data into databases

• Calculate databases (aggregate data)

• View log reports and other database server information for troubleshooting

e l c

a r O

Planning: Create and Manage Applications

11-11

Module 3

Loading Metadata

Lesson 11 Deploying Applications

Essbase Directory Structure Essbase applications are stored in the following directory structure: \Hyperion\AnalyticServices\App\\

CorpBud

Corporate Budgeting application

BalSheet

IncStmt

Revenue

Balance Sheet database (plan type)

Income Statement database (plan type)

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Essbase Directory Structure

y m

e d a

Revenue database (plan type)

c A

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

e l c

a r O 11-12

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 11 Deploying Applications

Redeploying Applications ƒ Change in dimension hierarchy - Replace ƒ Change in properties - Merge

EPM Architect Dimension Server

Planning Application Server

Redeploy

HYPlan application view

HYPlan application

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Redeploying Applications

e d a

c A

If you change the metadata, you should redeploy the application view to update the relational and Essbase databases. After deploying Planning application views, you cannot change the following properties: • Whether the application view uses a single currency or multiple currencies. For example, after deploying with multiple currencies, you cannot later use a single currency. Likewise, with a single-currency application view, you cannot later select Multiple Currency. • Default application currency. Data values might not be correct because existing currency values are not converted to the new currency.

e l c

• Type of calendar. For example, if you set base time period to 12 months, you cannot later change it to quarters.

a r O

Planning: Create and Manage Applications

11-13

Module 3

Loading Metadata

Lesson 11 Deploying Applications • Fiscal start month. After setting the start month, you cannot change it. • Start year. For example, if you set the start year to 2006, you cannot change it to 2005. You can, however, add years after the first year. • Added years. After adding years, you cannot remove them. For example, if the deployed application view includes FY06, you cannot remove this year. • Weeks distribution pattern. For example, if you set weeks distribution to 445, you cannot later change it to 544 or Even. • Plan type, such as Valid For Plan1. You can add plan types, but you cannot remove them. For example, if you deploy an application view with the properties Valid For Plan1 and Valid For Plan2, you can later add a property named Valid For Plan3. However, you cannot later remove Valid for Plan2. • Added dimensions. You can add up to 20 dimensions, including the required dimensions. You can rename dimensions, but you cannot delete them. • Required dimensions. You cannot delete required dimensions. Single-currency application views require these dimensions: Scenario, Version, Entity, Account, Period, and Year. Multicurrency application views require these dimensions: Scenario, Version, Entity, Account, Period, Year, and Currency.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 11-14

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 11 Deploying Applications

Summary In this lesson, you should have learned to: • Validate application views • Compare application views • Deploy applications views • Review Planning applications in Administration Services • Redeploy application views

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

11-15

Module 3

Loading Metadata

Lesson 11 Deploying Applications

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 11-16

Planning: Create and Manage Applications

L E S S O N

1 2

Setting Up Exchange Rates

12

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

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 3

Loading Metadata

Lesson 12 Setting Up Exchange Rates

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Currencies and Exchange Rates

e d a

c A

You can plan, forecast, and analyze financial information in single or multiple currencies. If your application is enabled for multiple currencies, users can see values converted from the local currency to a reporting currency. You use exchange rates to convert values from one currency to another. You can plan in a variety of currencies to: • Enable budget preparers in various countries to create plans in their native currencies • Show summary data in reports in a particular currency

e l c

• Summarize values from multiple currencies into a single currency For example, the base currency for Japan is the Japanese yen and that for the United States is the U.S. dollar. When you view a data form that contains values for Japan, if the display currency is set to U.S. dollars, the exchange rate for the Japanese yen is used to convert the values to U.S. dollars.

a r O 12-2

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 12 Setting Up Exchange Rates

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Exchange Rates Tables Overview

e d a

c A

You enter exchange rate values through exchange rate tables. You can create exchange rate tables to correspond to different business scenarios. Each table is typically associated with one or more scenarios. However, each scenario can be associated with only one exchange rate table. For example, you can create exchange rate tables named Actual Rates and Budget Rates. You can then associate the Actual Rates table with the scenarios Actual and Budget at Actual Rates, and associate the Budget Rates table with the scenarios Forecast and Budget at Budget Rates. Calculation scripts run business calculations for your application. Typically, you create calculation scripts for your application using Business Rules. However, Planning automatically generates the calculation scripts needed for currency conversion.

e l c

a r O

Planning: Create and Manage Applications

12-3

Module 3

Loading Metadata

Lesson 12 Setting Up Exchange Rates

Creating Exchange Rate Tables

2 1

3

y m

e d a

5

4

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Exchange Rate Tables

c A

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

e l c

a r O 12-4

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 12 Setting Up Exchange Rates To create exchange rate tables: 1. From Workspace, select Navigate > Dimension Library and create or open a Scenario dimension. 2. Create or select a scenario. 3. In the Exchange Rate Table properties field, enter the Exchange Rate table associated with this Scenario and save your changes. 4. In Planning, select Administration > Manage Exchange Rates. The Manage Exchange Rates page is displayed. 5. Select the newly created Exchange Rate table and click Edit. You can now enter exchange rate values into the Exchange Rate table.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

12-5

Module 3

Loading Metadata

Lesson 12 Setting Up Exchange Rates

Entering Exchange Rates

Application default currency

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Entering Exchange Rates

e d a

c A

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

Types of Exchange Rates

There are three types of exchange rates associated with a currency: • Historical • Average

e l c

• Ending

a r O 12-6

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 12 Setting Up Exchange Rates You specify the exchange rate type used for each account in the Planning dimension editor when you set up accounts. For average and ending rates, you can enter rates for each time period. For the historical rate type, you enter a single rate that is used for all time periods. To enter exchange rate values: 1. Select the Exchange Rate table, and click Edit. 2. On the Rate Table tab, select values for the following display options: • Average • Ending • BegBalance • Historical • Method 3. Click Next. 4. On the Exchange Rate tab, select values for the following options:

e d a

• To Currency • Show Years • Rate Table Name

e l c a r O ly & On l a e n r s e t U n I

5. From the Method drop-down list, select a method.

y m

c A

6. In the Historical, Beg Bal, Avg, and End columns, enter values. 7. Optional: Right-click to use the Fill Year or Fill Table option. 8. Click Save.

Each exchange rate table spans all time periods of the application, so that you can apply exchange rates to all scenarios. If you create a table or modify one, you must refresh the application for the new exchange rates to be stored in the plan types.

e l c

a r O

Planning: Create and Manage Applications

12-7

Module 3

Loading Metadata

Lesson 12 Setting Up Exchange Rates

Calculating Implied Rates Through Triangulation Assumptions: ƒ U.S. dollar is the default application currency. ƒ Euro is a reporting currency. ƒ British pound is a local currency available in the application.

Rate British pounds to U.S.dollar

1.4

European euros to U.S. dollar

1.2

1.4 / 1.2 = 1.16

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculating Implied Rates Through Triangulation

e d a

c A

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

e l c

a r O 12-8

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 12 Setting Up Exchange Rates When you set up currencies, you specify whether the currency has a triangulation currency that allows the currency to be translated to a different currency through a common third currency—the triangulation currency. You enter exchange rates for converting from the currency to its triangulation currency. The exchange rates between the currency and other currencies that triangulate through the triangulation currency are calculated automatically. These rates are called implied rates. For example, the British pound and the Danish krone might both be set to triangulate through the European euro. After rates are entered for converting between the British pound and the European euro and between the Danish krone and the European euro, the rates for converting from the British pound to the Danish krone and from the Danish krone to the British pound are automatically calculated. NOTE

If you modify a currency’s triangulation currency, you must reenter exchange rates for the triangulation currency property, and you must refresh the application so that the exchange rates are transferred and stored. You cannot select the application’s default currency as a triangulation currency.

y m

Determining the Calculation Method

e d a

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

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

12-9

Module 3

Loading Metadata

Lesson 12 Setting Up Exchange Rates

Exchange Rates and the HSP_Rates Dimension Input members

Draft 1 100.00

USD

Currency (Rate) members

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Exchange Rates and the HSP_Rates Dimension

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

e l c

The currency members of the HSP_Rates dimension store the exchange rates for each currency. There is an HSP_Rates member for each currency added to the application.

a r O 12-10

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 12 Setting Up Exchange Rates

Generating Currency Conversion Calculation Scripts 1. Select Administration > Manage Currency Conversion. 2. Click Create.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

12-11

Module 3

Loading Metadata

Lesson 12 Setting Up Exchange Rates

Copy Rates Calculation Scripts The Copy Rates calculation script copies the appropriate exchange rate to the individual account members based on their exchange rate type. Performance is improved because Planning can retrieve the conversion rate for the account directly, without looking up the rate type. Separate copy rate calculation scripts are generated for bottom-up and target versions. The name of the script is HspCRtB for bottom-up versions and HspCRtT for target versions. You run these scripts after you enter exchange rates and before you run the currency conversion calculation script for the first conversion. Subsequently, you run the copy rates calculation scripts only under these conditions: • Exchange rates change. • Account exchange rate types change. • The exchange rate table assignment for a scenario changes. • The metadata changes; for example, a new currency or account is added.

y m

Currency Conversion Calculation Script

Planning generates a calculation script to convert values for local currencies to one or more reporting currencies. The calculation script converts values for all accounts and entities. The currency conversion calculation script generated by Planning converts only level 0 members for bottom-up versions and all levels for target versions. For bottom-up versions, you must run an aggregation to populate upper-level members with the new converted values.

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

Because the Currency Conversion calculation script runs for all entities and accounts in your application, it typically is run by budget administrators rather than end users. If end users need to see their data converted to a reporting currency, they should use the Calculate Currencies business rules associated with data forms.

Calculate Currencies Business Rule

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

e l c

a r O 12-12

Planning: Create and Manage Applications

Module 3 Loading Metadata Lesson 12 Setting Up Exchange Rates

Summary In this lesson, you should have learned to: • Create exchange rate tables • Enter exchange rates • Generate currency conversion calculation scripts

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

12-13

Module 3

Loading Metadata

Lesson 12 Setting Up Exchange Rates

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 12-14

Planning: Create and Manage Applications

M O D U L E

4

Loading Data and Calculating the Database

12

Overview The aim of this module is to discuss the requirements for data load files, when to use data load rules, and how data is calculated within a dimension, data blocks calculation order, and using calculation scripts. You also load data using EPM Architect and using Administration Services and calculate the database. Lessons in this module include: • Loading and Calculating Data Overview

y m

• Loading Data

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

L E S S O N

1 3

Loading and Calculating Data Overview

13

Objectives At the end of this lesson, you should be able to: • Define the requirements for data load files • Set up data load rules and load data using data load rules • Set up the data staging area using interface tables • Identify how data is calculated within dimensions

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Loading Data You can: ƒ Load data directly into the Essbase database for each plan type. ƒ Use any of the following for loading data: — Administration Services — EPM Architect Interface Tables

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Loading Data

e d a

c A

Planning creates an Essbase database for each plan type in your application. You can load data directly into the Essbase database that corresponds to the plan type in your application. When you create your Planning application, the Essbase databases do not contain data. You can load data values from external systems into your Planning application. For example, you might want to load data for actuals from your ERP system so that you can calculate variances. You can use the following methods to load data:

e l c

• Data can be extracted to ASCII text files (flat files) from external systems and loaded using Essbase data load rules.

a r O

• Data can be loaded with EPM Architect interface tables.

13-2

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview To load data, you must have: • 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: - Microsoft Excel files (Version 4.0 and later) with the .xls extension (You must load Microsoft Excel files of Version 5.0 and later as client objects or files in the file system.) - Lotus 1-2-3 files with the .wks, .wk1, .wk3, or .wk4 extension - Spreadsheet audit log files - Flat files from ASCII backups or external sources - Essbase export files • If you are not using a rules file for loading data, a data source correctly formatted for free-form data loading

y m

• If you are using a rules file for loading data, a rules file validated for data loading

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

13-3

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Requirements for Data Load Files Use Essbase to load data from flat files into your Planning application. Entity

Account

Scenario

Version

Period

EUROPE GROSS SALES EUROPE GROSS SALES EUROPE GROSS SALES

ACTUAL ACTUAL ACTUAL

FINAL FINAL FINAL

Jan Feb Mar

ACTUAL EUROPE EUROPE ASIA ASIA

JAN FEB FEB JAN

2007 2007 2007 2007

FINAL GROSS SALES NET INCOME NET INCOME GROSS SALES

BUDGET DRAFT 2008 ENTITY PERIOD CUSTOMER EUROPE FEB MY COMPANY

4000-100 1500

Year

Data

2007 2007 2007

1000 400 650

1000 400 300 200

4000-200 1700

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Requirements for Data Load Files

4000-300 1200

y m

e d a

c A

The first graphic shown on the slide is an example of a data load file that loads data values for the first quarter of 2007 for the Europe entity and the Gross Sales account in the Actual scenario and the Final version. If a dimension has the same value for all rows, you can place it in the header as a page dimension, as shown in the second graphic on the slide. Requirements:

• Each data point must be tagged with a member from each dimension. • Data must be for bottom-level members, unless you are loading data into a target version.

e l c

• Data is scanned from the top of the file and from left to right.

a r O

• Each field (item) in a record (row) must be separated by a delimiter.

13-4

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview • A member name or alias must be enclosed in double quotation marks (" ") if it contains blanks, numeric characters (0–9), dashes, or unary operators. It must also be displayed exactly as it is in the outline. • Members of the same dimension must be in the same column or row. • Members of different dimensions can be together only on the page header. They cannot be used together in any other row or column.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

13-5

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Multicurrency Applications The HSP_Rates Dimension has the following members: ƒ HSP_InputValue ƒ HSP_InputCurrency ƒ HSP_Rate_

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Multicurrency Applications

e d a

c A

Applications that support multiple currencies include an additional dimension called HSP_Rates. This dimension is used to store exchange rates. The HSP_Rates dimension includes the following members: • HSP_InputValue—This member stores data values.

• HSP_InputCurrency—This member stores currency types for the data values. • HSP_Rate_ —XXX represents a currency in a multicurrency application. You load data to the HSP_InputValue member and the local currency. The HSP_InputCurrency member is not displayed in Planning. However, if the default currency is overridden, the new currency is stored along with its value in the database. By storing the new currency, Essbase can apply a different currency value to the data displayed for HSP_InputValue.

e l c

a r O 13-6

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Setting Up Data Load Rules Data load rules map the external data values to the Essbase database. Raw data file

2008 2008 2008

Budget Budget Budget

Draft 1 USREG Local 210-MICH N001 HSP_InputValue Jan Draft 1 USREG Local 210-MICH N001 HSP_InputValue Feb Draft 1 USREG Local 210-MICH N001 HSP_InputValue Mar

Data Prep Editor Rules applied

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Up Data Load Rules

e d a

c A

You use data load rules to delineate how data is loaded into Essbase databases. Load rules can perform certain actions on the data originating from external data sources as it is loaded into the Essbase database. For example, if the data file contains fields that are not needed, you can ignore those fields during the data load. Create data load rules when any of the following criteria need to be applied during a data load: • Ignore fields or strings in the data source.

• Change the order of fields by moving, joining, splitting, or creating them.

e l c

• Map the data in the data source to the database by changing strings.

a r O

• Change the data values in the data source by scaling the data values or adding them to existing values in the data source.

Planning: Create and Manage Applications

13-7

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview • Set header records for missing values. • Reject invalid records and continue loading data. Data Prep Editor You can use the Data Prep Editor to create data load rules. You access the Data Prep Editor from the Administration Services Console. The Data Prep Editor contains two areas. The upper area provides a view of the data source, called the raw data source. The lower area contains a grid showing the appearance of records after rules are applied (that is, as they will be loaded into the database). Data load rules do not modify the content of the raw data source. The Data Prep Editor displays two fields: Data Load and Dimension Build. Opening a Data Source After you open the Data Prep Editor, you can open data sources such as flat files, spreadsheet files, and SQL data sources.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 13-8

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Staging Data Using Interface Tables

e d a

c A

Interface tables in EPM Architect are database tables used to import data from external systems into EPM Architect. You can create multiple EPM Architect interface databases. The EPM Architect database type can be different than the database for the interface tables. For example, the EPM Architect database can be Microsoft SQL, and the EPM Architect interface tables can use Oracle.

e l c

a r O

Planning: Create and Manage Applications

13-9

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Data Calculation Overview There are three types of calculations in Planning: ƒ Calculations within dimensions ƒ Calculations and data blocks ƒ Calculation scripts

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Data Calculation Overview

e d a

c A

Typically, you load data into the level 0 members of a database. After loading data, you calculate the database. When you calculate the database, child member values are aggregated to derive parent member values. Calculating the database also applies member formulas defined in the outline.

e l c

a r O 13-10

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Calculations Within Dimensions Measures (Label Only) P rofit (+)

7 Margin (+)

Level 2 3

Sales (+)

1 6 4

Marketing (+) Misc. (+)

Level 0 2

COGS (-) Expenses (-)

Level 1

5

Inventory (+) (Label Only) Opening (+) (TB First) Ending (+) (TB Last)

8 9

Ratios (+) (Label Only) Margin % (+) (Two Pass Calc) Margin % Sales;

10

y m

Product Share (+) (Two Pass Calc) Sales % S ales -> P roducts; 11

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculations Within Dimensions

e d a

c A

The calculation of a dimension follows the outline structure. Values for upper-level members are calculated based on values of lower-level members as defined by the parent-child relationships in the outline. The order in which members are calculated follows the order in the outline: • Calculations start at the lowest level of a branch from top to bottom. • Calculations move up to the next level when the end of a subbranch is reached. The example on the slide depicts the order of a calculation in the Account dimension. Selected calculations occur in the following order:

e l c

• Within the Margin branch: Sales and then COGS

a r O

• Within the Profit branch: Margin and then Expenses • Within the Measures branch: Profit, then Inventory, and then Ratios

Planning: Create and Manage Applications

13-11

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Calculations and Data Blocks

Sparse Dimension Calculation

Dense Dimension Calculation

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculations and Data Blocks

e d a

c A

Essbase databases are organized into data blocks. As you recall, a data block consists of all dense dimensions members in the outline for a unique combination of sparse dimension members. There is potentially a data block for each unique combination of sparse dimension members. The order in which the data blocks are calculated follows the order in which the sparse dimensions are listed on the Performance Setting screen. You can view the performance settings for dimensions in an application view by right-clicking the application view, and selecting Performance Settings. The data blocks for the members of the first sparse dimension listed on the Performance Settings screen of the Planning Dimension Editor are calculated first, and so on down the list.

e l c

a r O 13-12

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview Calculation begins with level 0 data blocks. Level 0 data blocks are those for which each sparse dimension member is a level 0 member. To calculate the values for a data block, the Essbase Server calculates the dense dimension members of the data block. After calculating the values for the level 0 blocks, it aggregates them to derive the value for the upper-level blocks. This process is repeated for each level of data blocks until the top is reached. The graphic shown in the slide depicts the following example: • There are level 0 data blocks for the Los Angeles and San Francisco sparse dimension members, and an upper-level data block for California, their parent. • The data blocks each have Account and Period dimensions as dense dimensions. • Essbase calculates the Account members and the Period members for the Los Angeles and San Francisco data blocks, based on the outline structure for the Account and Period dimensions. • Next, it 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.

y m

When Essbase calculates the dense dimension members for a data block, it first calculates the Account dimension, and then the Period dimension. The remaining dense dimensions are then calculated based on their order on the Performance Settings screen.

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

13-13

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Calculation Scripts Calculation scripts: ƒ Contain a series of calculation commands, equations, and formulas. ƒ Define calculations other than the calculations defined by the database outline. ƒ Specify how to calculate a database. The default calculation script calculates the entire database.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculation Scripts

e d a

c A

Every database needs at least one calculation script to aggregate unary operators and execute formulas in the outline. For most database calculations, the default outline calculation script provides the required results. You can run the default outline calculation script from Administration Services Console. In certain cases, you may need to write a calculation script to control how Essbase calculates a database. You can use Business Rules as a graphical environment to create calculation scripts. You can also create native Essbase calculation scripts using a text editor or the calculation script editor provided by Essbase.

e l c

a r O 13-14

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

Summary In this lesson, you should have learned to: • Define the requirements for data load files • Set up data load rules and load data using data load rules • Set up the data staging area using interface tables • Identify how data is calculated within dimensions

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

13-15

Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 13-16

Planning: Create and Manage Applications

L E S S O N

1 4

Loading Data

14

Objectives At the end of this lesson, you should be able to: • Create load rules for data files for Administration Services • Load data using Administration Services • Load data using interface tables

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Loading Data Using Administration Services 1

Right-click database; Select Load data

2 Select the file to load

3 Optionally: Select the rules file

4

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Loading Data Using Administration Services

y m

Click OK

e d a

c A

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

1. In Administration Services, select the database where you want to load data, rightclick, and select Load data. 2. Click Find Data File to select a file to load.

e l c

3. Optional: Click Find Rules File to select a rules file. 4. Click OK.

a r O 14-2

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Creating Data Load Rules 1

Right-click database; Select Create > Rules file

y m

2 From the View menu, select Data load fields

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Data Load Rules

e d a

c A

Data load rules are sets of operations that are performed on data from external data sources when the data is loaded into an Essbase database. Data load rules map external data values to the Essbase database. You specify these options when you create data load rules: • Set file delimiters

• Associate the rules file with an outline • Define header information

e l c

• Map fields to member names and column fields

• Manipulate column fields and replace text strings

a r O

Planning: Create and Manage Applications

14-3

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Opening Data Sources 1

Open a data file

2

Select a file

3

Click OK

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Opening Data Sources

e d a

c A

After you select to create a rules file, the Data Prep Editor is opened. Next, open data sources to see what data needs to be changed. The data source can be located on the Essbase Server, locally, or on the network. Examples of valid data source files are Microsoft Excel and Lotus 1-2-3 spreadsheets, plain text files, and Essbase export files. Setting File Delimiters File delimiters are the characters that separate fields in the data source. By default, the rules file separates fields using tabs. You can set the file delimiter to be a comma, tab, space, fixed-width column, or custom value. Usually, the first thing you do after opening a data source is set the file delimiter.

e l c

a r O 14-4

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data Associating Rules Files with Outlines You associate the rules file with an Essbase database outline in order to populate list boxes with dimension and member names. Typically, you select the outline of the database into which you load the data. The rules file is not permanently associated with that outline, and you can associate it with another outline later. The rules file must be associated with an outline before you can validate the rules file.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

14-5

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Defining Header Records ƒ Headers in data source Entity

...

Jan

Feb ...

New York ... Albany ... White Plains...

150 60 20

160 ... 60 ... 20 ...

ƒ Headers in rules file 1st quarter Budget Data Jan Feb ... New York ... 150 160 ... Albany ... 60 60 ... White Plains... 20 20 ...

e d a

Skip two lines and map to Budget Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Defining Header Records

y m

c A

You can use the Data Prep Editor to create header records in rules files. Data sources can contain data records and header records. Data records contain member and data fields. Header records describe the contents of the data source and how to load data values into the database. A rules file contains records that translate the data in the data source to the database. As part of that information, the rules file can also contain header records. Defining Header Information in Rules Files Headers are used only during data loads or dimension building. They do not change the data source. Header information in a rules file is not used if there is also a dynamic reference in the rules file pointing to a header record in the data source.

e l c

a r O 14-6

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data Defining Header Information in Data Sources If the data source contains header information, you can specify its location in the rules file. The rules file then passes information to the Essbase Server to read the header information as a header record and not as a data record. You can also specify the type of header information in the header record. For example, the header record can contain data load field names. If the data source does not have header information, you can add it to the data source by using a text editor or spreadsheet and then identifying those records as the header information in the rules file. Placing header information in the data source makes it possible to use the same rules file for multiple data sources with different formats: The data source format is specified in the data source header, not in the rules file. NOTE

Header information defined in the data source takes precedence over header information defined in the rules file.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

14-7

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Associating Column Fields with Dimensions and Members ƒ Use the Field Properties dialog box to map column fields to dimensions and members.

e d a

ƒ Manipulate column fields to create unique member names. Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

y m

c A

Associating Column Fields with Dimensions and Members When loading data from a data source file, you must specify how the fields in the data source file map to the dimensions in the database. Data load rules refer to columns in the data source file. When setting up a data load rule, you must match each column of information to a specific dimension or a member within a dimension. Each column of information contains either a member label or a data element. In a data load, you must specify every dimension in the database in either the data source or the rules file. If the data source does not identify every dimension in the database, you must identify the missing dimensions in the rules file. Mapping Fields to Member Names A rules file can translate fields in the data source to match member names each time the data source is loaded without changing the data source. The rules file performs the following tasks:

e l c

a r O 14-8

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data • Maps member fields in the data source to members in the database • Maps data fields in the data source to member names or member combinations (such as Jan, Actual) in the database You can also define rules for these purposes: • Name, or translate, the fields in the data source to match members in the database • Replace strings or translate the fields in the data source to match members in the database Mapping Column Fields A column field can contain the name of a valid dimension member or an alias. Use one of the following methods to specify a field name: • On the Data Load Properties tab of the Field Properties dialog box, in the Field name text box, enter the member name or member combination to which the current field maps. From the Dimension node, select the field name that displays the names of the dimensions and members in the associated outline.

y m

e d a

If a field represents information that is not data and is extraneous to the outline, you can ignore the field by selecting the “Ignore field during data load” check box. You use the Data Load Properties area of the Field Properties dialog box to define field names for the columns of the rules file.

e l c a r O ly & On l a e n r s e t U n I

c A

Manipulating Column Fields Your data source may not always have columns in the correct sequential order, or you may need to manipulate column details such as duplicating, parsing, or concatenating columns to create unique member names. Action Move

Description

Changes the sequential order of columns

Split

Parses fields; used for segregating columns where the source file has fields of variable length and does not have field delimiters

Join

Joins two or more columns

Create Using Join

Creates a column or set of columns; used to duplicate a column

Create Using Text

Creates a column that contains any text, including white spaces

e l c

a r O

Planning: Create and Manage Applications

14-9

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Replacing Text Strings

e d a

c A

You can use a rules file to replace text strings so that the fields map to Essbase member names during a data load. The data source is not changed. For example, if the data source abbreviates New York to NY, you can have the rules file replace each NY with New York while loading the data. Replace options: Option Replace With

e l c

Case-Sensitive

a r O 14-10

Description

Use the Replace text box to enter the text string to be replaced. Use the With text box to enter the text string to replace the one in the Replace text box. Select Case-Sensitive to construct a condition based on a casesensitive string.

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data Option

Description

Match Whole Word

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

Replace All Occurrences

Select Replace All Occurrences to indicate that Essbase should replace all text strings that match the text string in the With field. By default, Essbase replaces the first occurrence.

New

Click New to add a new line for additional changes entered in the Replace and With fields.

Delete

Click Delete to remove items from action lists.

Original

Select Original to leave existing fields in their original case. By default, this option is selected.

Lowercase

Select Lowercase to change all characters of the field to lowercase.

Uppercase

Select Uppercase to change all characters of the field to uppercase.

Prefix

Use the Prefix field to enter a text string to be added at the beginning of the field values. (You cannot use parentheses in the Prefix text box.)

Suffix

Use the Suffix field to enter a text string to be added to the end of the field values.

Drop leading/trailing spaces

Select “Drop leading/trailing spaces” to remove leading and trailing white spaces around fields. (A field with leading or trailing white spaces does not map to a member even if the name within the white spaces is an exact match.)

Convert spaces to underscores

Select “Convert spaces to underscores” to change white spaces in field values to underscores.

e l c

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

14-11

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Validating and Saving Rules Files

e d a

c A

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

e l c

a r O 14-12

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Fixing an Invalid Rules File If the rules file does not validate, you must fix it before loading data. Go to the field specified in the Validate Rules dialog box that did not pass validation. Check the following items: • Is the field name spelled correctly? • Are the file delimiters placed correctly? • Is there a member name in the field name? • Is the dimension name used in another field name or the header? • Is a member used as a member combination in one place and as a single member in another? • Is more than one field defined as a data field? • Is the dimension used for transposing signs in the associated outline? • Is the rules file associated with the correct outline?

y m

After making the corrections, run the validation again.

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

14-13

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Loading Data Using Rules Files

4 2

3

5

1

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Loading Data Using Rules Files

e d a

c A

After the rules file is generated, you can load data using the rules file. To load data:

1. From Enterprise View or a custom view, select the database. Right-click and select Load data. The Data Load dialog box is displayed. 2. Select one or more data sources.

3. Click the Find Rules File button and select the rules file name.

e l c

a r O 14-14

The rules you selected are displayed on the Data Load dialog box in the Rules File column.

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data 4. Optional: Specify where errors should be written. By default, errors are written to the Hyperion\AnalyticServices\client directory. 5. Click OK to load the data. Essbase runs the data load. 6. Check errors and status messages that are displayed in the Messages panel at the bottom of the console window as well as those written to the error file.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

14-15

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Interface Tables

Interface Tables ETL

Planning EPM Architect

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Interface Tables

e d a

c A

You use Interface tables to create a staging area for loading data from outside systems (EPR, ETL, GL, and so on) into EPM Architect for use in Planning. Using interface tables to load data helps you to streamline the data load process. You can predefine a data set that you want to import into Planning and stage it for loading at any time. You can create multiple Interface Tables for staging data. NOTE

Before you can load data from interface tables, you must first have a relational database set up to store the information in the tables, and then you must run the Hyperion Configuration Utility to configure the tables in the new relational database.

e l c

a r O 14-16

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Creating Interface Tables

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Interface Tables

e d a

c A

You create Interface Tables within the Data Synchronization module of EPM Architect. You can load data into the Dimension Library using interface tables.

e l c

a r O

Planning: Create and Manage Applications

14-17

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Loading Data Using Interface Tables Process before Interface Table Import EPR System

Interface Table Import Process in Hyperion System 9 Financial Management

Interface Tables

EPM Architect

ETL System

Planning

Dimension Library

General Ledger System

Interface Tables

Data Synchronization

e d a

EPM Architect DB

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Loading Data Using Interface Tables

y m

Analytic Services

c A

Once you stage data in your ETL system and you create interface tables, you can use the interface tables to load data into Planning. To load data:

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

e l c

a r O 14-18

Planning: Create and Manage Applications

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

Summary In this lesson, you should have learned to: • Create load rules for data files for Administration Services • Load data using Administration Services • Load data using interface tables

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

14-19

Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 14-20

Planning: Create and Manage Applications

M O D U L E

5

Setting Up Security

14

Overview The aim of this module is to provide an overview of security in Planning. You learn how to provision users and user groups in the User Management Console of Shared Services for your Planning application. You also learn how to assign access rights to elements of your Planning application. Lessons in this module include: • Provisioning Users and Groups

y m

• Setting Up Access Rights to Planning Applications Applications

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

L E S S O N

1 5

Provisioning Users and Groups

15

Objectives At the end of this lesson, you should be able to: • Describe security in Planning • Describe user provisioning in Shared Services • Provision users and groups for Planning • Generate provisioning reports

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Planning Security Overview In Planning, you can perform the following security-related tasks: ƒ Determine user privileges

ƒ Assign access rights to application elements

ƒ Create security filters

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Planning Security Overview

e d a

c A

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

e l c

• Data forms

a r O

• Task lists

After you establish or update user and group security and assign member access, you must refresh the Planning application to update to the Essbase security filters.

15-2

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Levels of Security There are four levels of security in Planning. Data forms and task lists

User authentication

Task security

Object security

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Levels of Security

Data security

y m

e d a

c A

Planning provides security at four levels:

• Users must provide a valid ID and password to log on to the system. • Users can launch only those tasks to which they have been given access. For example, you can give users the ability to create data forms but not dimension members. • Users can open only those data forms and task lists (objects) to which they have been granted access. • Users can view and modify data only for dimension members to which they have been granted access.

e l c

a r O

Planning: Create and Manage Applications

15-3

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

User Authentication ƒ Users must provide a valid user name and password to access an application. ƒ Planning leverages external authentication providers such as LDAP, Microsoft Active Directory, and NTLM. ƒ Users and groups must exist in the authentication directory before they can be granted access to a Planning application.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

User Authentication

e d a

c A

User login information for Hyperion applications is stored outside the applications in an authentication directory. The information is maintained by a central authentication directory. An authentication directory is a centralized store of users and passwords, user groups, and perhaps corporate information, such as employee IDs or job tiles. The following types of authentication directories are supported: • Windows NT LAN Manager (NTLM) on NT 4.0 or higher, Windows 2000, and Windows 2003 • Lightweight Directory Access Protocol (LDAP) version 3 or later • Microsoft Active Directory (MSAD) server, Windows 2000 SP3 or later

e l c

You can grant access to your Planning applications to any user or group in an authentication directory. When you grant a group access to an application, the users in the group are also granted access to the application.

a r O

You grant access in the Shared Services User Management Console.

15-4

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Task Security With task security, you can perform the following tasks: ƒ Specify the tasks that users and groups are authorized to perform ƒ Assign roles to users to implement task security ƒ Remove or disable menu items for certain users

Administration menu, administrator’s view

e d a

Administration menu, interactive user’s view

Copyright © 2007, Oracle. All rights reserved.

Task Security

y m

e l c a r O ly & On l a e n r s e t U n I

c A

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

e l c

a r O

Planning: Create and Manage Applications

15-5

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Object Security You can assign security to specific objects in your application.

Data form

Task list

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Object Security

y m

e d a

c A

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

e l c

a r O 15-6

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Data Security You can assign users or groups read, write, or none access to data for specified dimension members.

Entity Members

ƒ ƒ ƒ ƒ

East Region West Region United Kingdom Singapore

Assigned Access Level

ƒ ƒ ƒ ƒ

Write Read Read None

RJackson

y m

Copyright © 2007, Oracle. All rights reserved.

Data Security

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Setting up data security enables you to protect data and prevent unauthorized users from changing data. For example, you can restrict access to certain data elements in an application.

e l c

a r O

Planning: Create and Manage Applications

15-7

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

User and Group Provisioning Overview

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

User and Group Provisioning Overview

e d a

c A

User provisioning enables centralized management of users, their role assignments and their access rights to applications created under various projects of various products. To perform provisioning for Planning applications, you use User Management Console. The provisioning process enables you to associate applications to projects. Then, users and groups, with their applicable roles, are associated to the applications. To access User Management Console, select Start > Programs > Hyperion > Foundation Services > User Management. Any user with the Provisioning Manager or Administrator role in an application can perform provisioning. The three main nodes of User Management Console:

e l c

• User Directories

a r O

• Projects

• Unassigned Applications

15-8

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

User Directories User Directories list users from native and external directories. User Directories: Native and NTLM

y m

e d a

User list for selected directory Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

User Directories

c A

In User Management Console, you view user directories that consist of users and groups. User directories can be provided (set up) natively or externally. External directories (LDAP, NTLM, and MSAD) hold users and groups in each directory. External directories are typically corporate directories. You provision users and groups by assigning user roles in an application. A user can receive a combination of individual and group role assignments.

e l c

a r O

Planning: Create and Manage Applications

15-9

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Projects Projects group instances of Hyperion products that compose an implementation.

y m

Copyright © 2007, Oracle. All rights reserved.

Projects

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Before you can provision users or groups for a Planning application, the application must be registered in Shared Services and belong to a project. A project is an instance of Hyperion products that are grouped to compose an implementation. For example, a Planning project may consist of a Planning application, an Essbase application, and a Financial Reporting Server instance. You can add one or more applications to a project. You can add applications at the time the project is created or at a later time. NOTE

An application can be associated with only one project.

e l c

To create a project, right-click Projects, and select New > Project. You then give the project a name and description and assign applications as required.

ra

TIP

O

15-10

In a practical sense, you can think of a project as a type of folder.

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Unassigned Applications Before you can provision users or groups to an application, you must assign the application to a project.

y m

Planning application that has been registered with Shared Services but not yet assigned to a project Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Unassigned Applications

e d a

c A

When you log on to your Planning application for the first time, you are prompted to register the application with Shared Services. When you register your application, you can assign it to an existing project, create a project and assign the application to it, or leave it as an unassigned application to be assigned to a project at a later time. You need to create at least one project in Shared Services and add your application to it before you can provision users and groups to the application.

e l c

a r O

Planning: Create and Manage Applications

15-11

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Provisioning Users and Groups 8

Expand an application

9 Select a role

10 Click Add Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Provisioning Users and Groups

y m

e d a

11

Click Save

c A

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

1. Select Start > Programs > Hyperion > Foundation Services > User Management. 2. Log onto User Management.

e l c

User Management Console is displayed.

3. In the view pane, expand User Directories.

a r O 15-12

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups 4. Select and expand Users, to provision and assign roles to users, or Groups, to provision and assign roles to groups. 5. Click Show All to display a list of users or groups. 6. Select the user or group that you want to provision. 7. Select Administration > Provision, or right-click a user or group and select Provision. 8. Expand the project that contains the application for which you want to provision the user or group and for which you want to assign roles. 9. Expand the application for which you want to provision the user or group and for which you want to assign roles. 10. Select the role or roles that you want to assign to the user. 11. Click Add. 12. Click Save. 13. Select File > Exit to return to Planning.

y m

TIP

Users that are provisioned for a Planning application as either Administrator or Interactive User do not need to be provisioned separately for Business Rules.

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

15-13

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

User Roles

y m

Copyright © 2007, Oracle. All rights reserved.

User Roles

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

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

e l c

• Run Integrations — Views and runs Shared Services data integrations.

a r O 15-14

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups The following table summarizes Planning user profiles. User Profile

Description

Provisioning Manager

Users who are assigned the Provisioning Manager role can provision users and groups to applications.

Administrator

Administrators can create applications; manage security; maintain metadata; initiate and manage the budget process; create and maintain Web-based data forms; create and manage task lists; create and maintain Smart View worksheets; create and launch business rules by using Business Rules; and enter, view, and delete data.

Manage Models

Users assigned the Manage Models role can export and import Shared Services models.

Interactive User

Interactive users can enable e-mail notification; create and maintain Web-based data forms; create and manage task lists; create and maintain Smart View worksheets; create and launch business rules by using Business Rules; enter, view, and delete data; and submit information and data for approval.

Planner

Planners enable e-mail notification; input, submit, and view data; use reports that have been built by others; run data integration routines designed by others; execute business rules and other processes associated with validating and preparing data; view and use task lists; use Smart View; and submit information and data for approval.

View User

View users have limited access to view data in a Planning application. Typically, the view user is an executive who wants to see business plans during and at the end of the budget process.

Offline User

Mass Allocation

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

Essbase Write Access

e l c

a r O

c A

Users assigned the Offline User role can take planning data offline, work with data offline, and then synchronize data back to the planning server. Offline users can work offline only if the administrator has enabled Offline in Application Settings for the application. Users assigned the Mass Allocation role can spread data by using the Mass Allocation function. Mass Allocation spreads data either proportionally or relatively to other members in the outline. Even though you run Mass Allocation from data forms, data is spread to members even if they are not displayed on the data form. This role only should be assigned to a select few people because there is no undo functionality after spreading data by using Mass Allocation. Users assigned the Essbase Write Access role can lock and send with write access to Essbase. If you assign this role to planners and interactive users, you give them write access directly to planning data in Essbase.

Planning: Create and Manage Applications

15-15

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups P

Generating Provisioning Reports Generate a provisioning report to list the provisioned users and groups.

1

Specify a specific user, group, a role or all three. Group results by application or user.

2

Specify one 3 or more items. 4

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Generating Provisioning Reports

Generate the report.

y m

e d a

c A

You can generate provisioning reports to list the details of the users, groups, and roles that are provisioned. To generate the report, in User Management Console, select Administration > View Report.

e l c

a r O 15-16

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

Summary In this lesson, you should have learned to: • Describe security in Planning • Describe user provisioning in Shared Services • Provision users and groups for Planning • Generate provisioning reports

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

15-17

Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 15-18

Planning: Create and Manage Applications

L E S S O N

1 6

Setting Up Access Rights to Planning Applications

16

Objectives At the end of this lesson, you should be able to: • Assign access rights • Import access rights • Create security filters

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Assigning Access Rights Use access rights to prevent unauthorized access to data.

Assign access

Add access View access

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Assigning Access Rights

y m

e d a

c A

You assign access rights to Planning application elements to protect data from unauthorized users or groups. The level of security is determined by the access option that you assign to a user. You can assign access by using dimension member relationships or by assigning access directly to individual dimension members. You can define unique access rights for each Planning application. You can assign access rights to the following application elements: • Scenario, Version, Account, and Entity dimension members • User-defined custom dimension members, if the Apply Security dimension property is selected • Data forms

e l c

• Task lists

You can use the dimension editor to assign access to dimension members, or you can use the ImportSecurity utility to import access rights information from a flat file.

a r O

You assign access to data forms in Form Management and to task lists in Task Management.

16-2

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Access Options ƒ Member and data form access rights consist of the following options: — Read — Write — None

ƒ Task list access rights consist of the following options: — — — —

Assign Manage Manage and Assign None

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Access Options

e d a

c A

When you assign access rights to a dimension member, data form, or task list, you determine which access option to assign for each user or group. By default, for interactive users and planners, access is denied to all dimension members, data forms, and task lists. The following table describes the access options for dimension members and data forms. Option Read

Definition

Enables users to view the dimension member or data form

Write

e l c

None

a r O

Enables users to view and modify access to the dimension member or data form Prevents users from accessing the dimension member or data form

Planning: Create and Manage Applications

16-3

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications The following table describes access options for task lists. Option

Description

Assign

Enables users to view and use the task list

Manage

Enables users to modify the task list

Manage and Assign

Enables users to modify, view, and use the task list

None

Prevents users from viewing the task list

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 16-4

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Inheritance Options The following inheritance options are available: ƒ Member ƒ Children ƒ iChildren ƒ Descendants ƒ iDescendants

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Inheritance Options

e d a

c A

You can assign access rights to individual dimension members, or you can use an inheritance option to assign rights to multiple members. It is more efficient to assign access rights by using an inheritance option. You should assign access to individual members only on an exception basis. For example, for the North America Sales group, you could assign Write access to North America and its descendants and Read access to North America Headquarters. The following table summarizes the available inheritance options. Option

e l c

Member

a r O

Children

Result

The access right is assigned only to the currently selected member. The access right is assigned to all child members of the currently selected member.

Planning: Create and Manage Applications

16-5

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications Option

Result

iChildren

The access right is assigned to the currently selected member and to all of its child members.

Descendants

The access right is assigned to all descendant members of the currently selected member.

iDescendants

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

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 16-6

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Precedence and Inheritance of Access Rights ƒ Individual rights override group rights

ƒ For group rights, no access overrides write or read access. Write access overrides read access.

ƒ Direct member rights override relationship rights LA

United States

y m

e d a

United States Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Precedence and Inheritance of Access Rights

c A

You can assign access rights to a member in the following ways: • The user can be assigned direct access to a member.

• The group can be assigned direct access to a member.

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

e l c

a r O

Planning: Create and Manage Applications

16-7

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications Individual Rights Over Group Rights Access rights that are assigned directly to a user override access rights that are inherited from associated groups. For example, if, for the Budget member, you inherit Read access through a group and are assigned direct Write access, you have Write access to the Budget member. Group Precedence A user might belong to several groups that have conflicting access rights to a member. In this case, None access take precedence over Write or Read access. Write access takes precedence over Read access. Here are some examples: • If you have Write access to the Budget member from one group and None access to Budget from another group, you have None access to Budget. • If you have Read access to the Budget member from one group and Write access to Budget from another group, you have Write access to Budget. Direct Member Rights Over Relationship Rights You can assign access rights to members indirectly through relationships to a parent or ancestor member. Rights that are assigned directly to a member override rights that are derived from a member relationship. Here are some examples:

y m

e d a

• You are assigned None access to children of the United States. You are assigned direct Read access to LA. You have Read access to LA.

c A

• You are individually assigned Write access to children of the United States. Your group is assigned direct Read access to LA. You have Read access to LA.

e l c

e l c a r O ly & On l a e n r s e t U n I

a r O 16-8

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Reporting on Access Assignments 1 2

3

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Reporting on Access Assignments

e d a

c A

To help you effectively view the current access assignments in an application, you can generate assigned access reports. You can also generate effective access reports to help resolve inheritance or precedence conflicts. You generate these reports from User Management Console. When you generate an assigned access or an effective access report, you specify what information to include. You can specify whether to include the following information: • Specific users and groups or all user and groups • Specific dimensions or all dimensions • Data forms

e l c

• Matching access types: Read, Write, or None

You can choose to group results by users or by objects. You also can choose to report on assigned access by access relationship and inherited group or on effective access, including effective access origin.

a r O

Planning: Create and Manage Applications

16-9

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

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

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Importing Security Overview

e d a

c A

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

e l c

Joe, eBusiness Sales, Write

a r O

After importing, Joe has Write access to both OLAP and eBusiness Sales.

16-10

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Creating the Secfile.txt File Use a text editor to create the Secfile.txt file with the following syntax: ,,,

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating the Secfile.txt File

e d a

c A

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

e l c

a r O

Planning: Create and Manage Applications

16-11

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications • Items within lines must be separated by one of the following delimiters: - Comma ( , )—the default - Tab - Semi-colon ( ; ) - Pipe ( | ) - Colon ( : ) - Space • Items within lines cannot have any extra spaces between them. • The import file cannot contain any blank lines. • Each line must contain the items described in the following table: Item

Description

User name or group

The name of a user or user group that is provisioned for the Planning application

Member name

A member (Account, Entity, user-defined custom dimension, Scenario, or Version) in the application

Access rights

Read, Write, or None (None is ignored. If there are duplicate lines for a combination of user name and member name, the line with Write access takes precedence.)

y m

e d a

e l c a r O ly & On l a e n r s e t U n I

Inheritance options

c A

@CHILDREN, @ICHILDREN, @DESCENDANTS, @IDESCENDANTS, and MEMBER.

For example, the Secfile.txt file might contain the following lines: User1,Account1,read,@CHILDREN User2,Entity2,write,@DESCENDANTS User3,Version_1,write,MEMBER Group1,Account101,write,@ICHILDREN NOTE

If a member, user, or user group name contains a character that you are using as the delimiter, enclose the name in double quotation marks. For example, if you are using a space as the delimiter, enclose the name North America in double quotation marks (“North America”).

e l c

a r O

• Inheritance options must be in all capital letters.

16-12

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications If you need to import security information into a group that has the same name as a user, in the Secfile.txt file, append the sl_group parameter to the line that pertains to the group. For example: admin,member1,read,MEMBER admin,member1,read,MEMBER,sl_group The first line imports security for a user named admin. The second line imports security for a group named admin. If you omit sl_group, security information is imported only for the user named admin.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

16-13

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Importing Access Rights ƒ Run the ImportSecurity utility from the command prompt. ƒ The file is located in the Hyperion\Planning\bin folder. ƒ The syntax is ImportSecurity.cmd “appname,username,password,[delimiter],[run_silent], [SL_CLEARALL]. For example: ImportSecurity.cmd “HYPlan,trnadmin,hyperion”

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Importing Access Rights

e d a

c A

Use the following procedure to import access rights from the security file (Secfile.txt). To import access rights

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

e l c

a r O 16-14

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications 3. At the command prompt, type the following command and required parameters, separating the parameters with commas: ImportSecurity.cmd “appl”,admin,password, SL_TAB,1 Parameter

Description

delimiter

Optional: SL_TAB, SL_COMMA, SL_PIPE, SL_SPACE, SL_COLON, SL_SEMI-COLON If no delimiter is specified, the comma default is assumed to be the delimiter.

run_silent

Optional: Whether to execute the utility silently or with progress messages: 0 = Execute with messages 1 = Execute silently, with no messages If this parameter is not included in the command line, the value is assumed to be 0, to display progress messages during execution.

[SL_CLEARALL]

Optional: Whether to clear all existing access assignments when importing the new access assignments This option must be in uppercase.

y m

e d a

4. After you execute the utility, view the importsecurity.log file in the bin folder to verify the results.

c A

The new security information is now accessible from the Dimensions task on the Administration menu in Planning.

e l c a r O ly & On l a e n r s e t U n I

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

e l c

a r O

Planning: Create and Manage Applications

16-15

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Creating Security Filters Create security filters to provide access to Planning data.

Create security filters for all users.

Create security filters for one or a few users.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Security Filters

e d a

c A

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

e l c

a r O 16-16

Planning: Create and Manage Applications

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications • Select Shared Members if you want to create security filters for shared members in Essbase. Access rights for shared members and their base members may be different. For example, user MSmith may not have access to the base entity London for the regional process management hierarchy but may have Read access to the shared entity London in the alternate corporate reporting hierarchy. • Select Validate Limit if you want to identify any security filter that exceeds the Essbase security filter limit of 4 KB per row. The names of users who exceed the limit are displayed in a pop-up window. NOTE

To validate security filters before updating Essbase, select only Validate Limit only.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

16-17

Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications

Summary In this lesson, you should have learned to: • Assign access rights • Import access rights • Create security filters

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 16-18

Planning: Create and Manage Applications

M O D U L E

6

Designing Data Forms

16

Overview The aim of this module is to define and manage data forms. You set user preferences, manage user variables, and create menus. Lessons in this module include: • Creating Data Forms and Folders • Customizing Data Forms

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

L E S S O N

1 7

Creating Data Forms and Folders

17

Objectives At the end of this lesson, you should be able to: • Manage data forms and folders • Set up row and column properties • Set up page and POV properties • Assign business rules to data forms

y m

• Set up display and precision options • Create composite data forms

e d a

• Print data form definition reports • Assign access rights to data forms

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Data Forms and Folders Overview ƒ Each data form is associated with a plan type. ƒ You assign access to data forms. ƒ Data forms with target versions enable data entry into parent members.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Data Forms and Folders Overview

e d a

c A

Data forms are spreadsheet-like grids with rows and columns for entering data. You can create as many data forms as required to meet the needs of budget preparers. For example, you can create a data form that budget preparers in the finance department use for fixed assets and a separate data form that line managers use for expense accounts. You manage data forms and folders by using the Data Form Management page. You can perform the following tasks from the Data Form Management page: • Create, move, delete, or rename folders • Create, edit, move, or delete data forms

e l c

• Create composite data forms

a r O

• Assign access to data forms

17-2

Planning: Create and Manage Applications

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

Data Form Elements Page Columns

Rows

Point of View

y m

e d a

Currency = Local Customer = No Customer Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Data Form Elements

c A

You create a data form by selecting point of view, page, row, and column elements. You create, edit, and manage data forms in the Manage Data Forms page. You can navigate to the page from the Administration menu. The members you select for the dimensions that are assigned to the POV determine the context for the pages, rows, and columns. For example, if the Scenario dimension is set to Budget in the POV, then all of the data entered in the pages, rows, and columns goes into the Budget scenario. For each POV dimension, only one member can be selected. You cannot change the member selected for the POV. For the data form shown in the slide, the POV is set to Local for the Currency dimension and to No Customer for the Customer dimension.

e l c

a r O

Planning: Create and Manage Applications

17-3

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders 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. Each item on the page axis can have members selected from one dimension or from multiple dimensions. For example, you can assign the Version and Scenario dimensions to the page axis. For Version, you select the Worst Case and Best Case members. For Scenario, you select the Budget and Forecast members. You can then switch members by selecting them from the page axis. Rows and columns define the grid into which you enter data. For example, you can assign Unit Sales to the row axis and January to the column axis. When you access data forms through Planning, you can enter data into the cell where the row for Unit Sales intersects with the column for January. By default, data forms have a single row and column. You can add rows and columns to create data forms with asymmetrical combinations of row and column members.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 17-4

Planning: Create and Manage Applications

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

Creating Folder Structures for Data Forms Remember the following points when working with folders: ƒ Move folders within the hierarchy as needed. ƒ Rename folders, including the top-level folder, called Forms. ƒ Access rights are not assigned to folders. ƒ Only empty folders can be deleted. ƒ You cannot move or delete the top-level folder, called Forms.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Folder Structures for Data Forms

e d a

c A

You use folders to help you organize your data forms. You can create as many folders as needed, and you can arrange the folders in a hierarchy. After you create folders, you can create data forms in those folders. To create a data form, you can build a data form with requirements that you specify, or you can edit an existing data form and then save it as a separate form. TIP

You can search to find a data form on the Data Form Management page.

e l c

a r O

Planning: Create and Manage Applications

17-5

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Data Form Requirements

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Data Form Requirements

e d a

c A

To create data forms, you need to define data form properties, row and column layout, page and point of view (POV) definitions, other options, business rules, and access rights. When you create a data form, you assign it to a plan type. Only members that are valid for that plan type can be included on the data form. For example, if you assign a data form to the Revenue plan type, you cannot add accounts that are not valid for the Revenue plan type. When you save data in a form, it is saved to the database that is associated with the data form’s plan type. NOTE

e l c

You cannot change the plan type for a data form.

a r O 17-6

Planning: Create and Manage Applications

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

Considerations for Setting up Data Forms In order for a cell on a data form to accept data entry: ƒ All members in the POV and pages list must be bottom-level members (except with target versions). ƒ All members in the rows or columns must be bottom-level members (except with target versions). ƒ The Currency dimension must be set to the Local member. ƒ The user must have Write access to all members of the cell.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Considerations for Setting up Data Forms

e d a

c A

Prior to creating data forms, data form designers need to consider several factors. Most data forms are used for entering values; therefore, you set up most data forms to permit data entry. However, you can set up forms at a more summarized level, for example, to view the results of calculations. If you want to enter data into the intersections of a data form, then you must set up the data form to meet certain conditions. For bottom-up versions, to permit data entry, dimensions on rows and columns must be set to bottom-level members. A bottom-level member is a member that has no child members below it. If a dimension on a row or column is set to a parent member, the row or column is read-only. If a dimension in the point of view or the Pages drop-down list is set to a parent member, all rows and columns on the data form are read-only.

e l c

Target versions allow data entry in both parent and bottom-level members.

a r O

Planning: Create and Manage Applications

17-7

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders You can use member relationships to select shared members. For example, to include all members of a rollup on a data form, you can select an alternate, functional rollup. Values entered into rows or columns that display shared members are saved to the base members in the database. Another factor to consider in the setup of data forms is how to represent the Currency dimension. You set up the Currency dimension on a data form to determine how currency values are displayed. If a row or column on a data form has the Local member selected for the Currency dimension, no currency conversion takes place for the row or column, and you can enter data for the entities on the row or column in their native currency. If you set a data form’s Currency member to something other than Local, then data values are displayed as converted to the selected currency, assuming that the currency calculation script has been run. The data form is read-only. In target versions, you can enter data in rows or columns that have Currency or Local as the selected member. For applications that use a single currency, the currency selected when you created the application is used as the currency member for all entities.

y m

To allow users to enter data in currencies other than an entity’s base currency, when selecting data-form members, you must perform one of the following actions:

e d a

• Select members from at least two currencies, in order to compare converted currencies.

c A

• Assign the Currency dimension to the page axis, and select reporting currencies as members. To convert currencies for all members in the data form, you can select the Currency member from the page axis and then launch the Calculate Currencies business rule to view all values in the currency of the selected Currency member.

e l c

e l c a r O ly & On l a e n r s e t U n I

a r O 17-8

Planning: Create and Manage Applications

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

Setting Data Form Properties

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Data Form Properties

e d a

c A

You set basic characteristics for data forms on the Properties tab. On the Properties tab, you assign the data form name and description and determine whether the data form permits data entry or is hidden from view. You prevent data entry by making a data form read-only. To work with forms offline, you must select Enable Offline Usage. You also can include instructions for business users who need to use the data form. You can hide data forms by selecting the “Make data forms hidden” option. If you hide a data form, then business users cannot select the data form from the view pane. You may want to hide a data form that is part of a composite form or a data form that is displayed by a right-click menu.

e l c

a r O

Planning: Create and Manage Applications

17-9

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Setting Row and Column Layout

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Row and Column Layout

e d a

c A

You assign dimensions to the columns and rows of data forms by selecting the dimensions from the drop-down lists of the Row/Column Layout tab. For each dimension, you select the preferred members. You then set the properties of the dimensions and members on the columns and rows. For row and column members, you can select segment properties. Column and row properties include showing a member name or alias, starting with the hierarchy expanded, suppressing missing data, and setting column width. For rows, you can also select to suppress missing blocks, suppress missing data, and allow users to add rows dynamically. When you are setting the data form layout, keep the following items in mind: • You must select at least one member for each dimension.

e l c

• A data form must have at least one dimension assigned to the row axis and one dimension assigned to the column axis.

a r O 17-10

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders • You cannot select the same dimension for more than one axis. • To move a dimension from one axis to another, delete it from the source axis and select it for the destination axis. Data form designers, when considering how to set up data forms, need to consider dimension composition. For columns, data form designers should use dimensions and members that business users are most likely to need to view. For example, the Period dimension—which represents months, quarters, years, or custom time periods—is typically set up on the columns. For rows, data form designers should use dimensions and members that contain a more expansive list of members. For example, the Account, Customer, and Product dimensions typically work well on the rows. Setting Up Segment Properties Segments are areas of data forms with special properties, such as separator lines for columns and rows and hidden or read-only data. You can define segments for asymmetric rows and columns. For example, you can set segment properties in an asymmetric row or column to read-only or to hide members. You can also suppress the hierarchy so row definitions are not indented and columns do not include line breaks.

y m

You can select options for segment properties as described in the following table:

e d a

Option

Description

Hide

Hide the segment so it is not displayed on the data form

Suppress Hierarchy

For columns, do not display line breaks For rows, do not display indentation

Read only Show Separator

e l c a r O ly & On l a e n r s e t U n I

Apply to All Segments

c A

Create a read-only segment in the data form to enable comparison of old, read-only data with new, editable data Create a bold border before the segment to visually distinguish parts of the data form Apply these settings to all columns in segments

Setting Column Properties The following table shows the options for column width on a data form: Column Width

e l c

Small

Medium

a r O

Description

Displays columns 50 pixels wide (approximately 7 decimal places) Displays columns 75 pixels wide (approximately 10 decimal places)

Planning: Create and Manage Applications

17-11

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders Column Width

Description

Large

Displays columns 100 pixels wide (approximately 13 decimal places)

Size-to-Fit

Forces all column headings to fit in the displayed space

Custom

Enables you to enter a pixel width value of up to 999 (greater than 13 decimal places)

If the selected column width is less than the width of the column contents, the excess data is hidden from view until the column is widened. While hidden, the data is stored and calculated in the data form in the same way as data that is not hidden. Regardless of the column width setting that is selected in the data form properties, you can adjust column width while you are viewing a data form. Saving or refreshing the data form saves the adjusted column width for the remainder of the session. When you print from the data form page, all columns, including minimized columns, regardless of their width setting, are printed at a width that is based on the printing options that are selected for page size and columns per page.

y m

The following table describes column width tasks that are available for data forms when you are using Microsoft Internet Explorer:

e d a

Task

Action

Resize column width

Drag the column heading.

Minimize column width

Click the column heading and select Minimize, or double-click the column heading.

Restore a minimized column

Right-click the minimized column heading and select Restore, or double-click the minimized column heading.

Restore all minimized columns

Right-click any column heading, and select Restore All.

Reset all column widths to the data form definition default property setting

Right-click any column heading, and select Reset All to Default.

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 17-12

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders Setting Row Properties You can set row properties for data form rows. The following table describes the options that you can set on rows in data forms: Option

Description

Suppress missing blocks

When suppressing a large number of rows, such as 90% or more, select this option to enhance performance of the “Suppress missing data” setting. If few or no rows are suppressed, the “Suppress missing blocks” setting can degrade performance. Hyperion recommends that you test data forms before and after using this setting to determine whether performance is improved. You should also test data forms whenever you make significant changes to your application. With this setting, data forms may not display attributes. Also, certain suppressed blocks may ignore Dynamic Calc members.

Suppress missing data

Select this option to suppress missing data. Selecting this option hides rows without data. If at least one cell of a row has a data value, then the row is not suppressed. Clear this option to display rows that contain only cells for which data is missing; the cells display #missing. You cannot simultaneously select “Suppress missing data” and “Allow users to dynamically add rows.”

y m

Allow users to dynamically add rows

e l c

e d a

Select this option to enable users who have Write access to the data form to dynamically change and refresh the data form’s definition by adding rows. Members that users can access are displayed on the data form. You cannot simultaneously select “Allow users to dynamically add rows” and “Suppress missing data.”

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

17-13

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Selecting Members

Member Des cendants Des cendants (Inc)

Desc endants plus North America

Ancestors

Worldwide

Ancestors (Inc)

Worldwide plus North America

Siblings

Europe, PacRim, Corporate

Siblings (Inc)

Europe, PacRim, Corporate, North America

Parent

Worldwide

Parent (Inc)

Worldwide and North Americ a

Children

Central, South, East, West

Children (Inc)

Central, South, East, West, North America

Level 0 Descendants

200, 205, 210, 220, 225, 230, 240, 245, 250, 255, 270, 275, 280

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Selecting Members

y m

e d a

c A

You select members for the current dimension on the Member Selection page. You can select specific members, or you can select members based on relationships. The following table describes the existing relationships and the members that are included on the data form for each relationship: Relationship Member Descendants

Members Included on the Data Form The selected member

All members below the selected member, excluding the selected member

Descendants (Inc)

The selected member and all of its descendants

Ancestors

All members above the selected member, excluding the selected member

e l c

a r O

Ancestors (Inc)

17-14

The selected member and all of its ancestors

Planning: Create and Manage Applications

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

Members Included on the Data Form

Siblings

All members in the level of the selected member, excluding the selected member

Siblings (Inc)

The selected member and all of its siblings

Parent

The member in the level above the selected member, excluding the selected member

Parent (Inc)

The selected member and its parent

Children

All members in the level immediately below the selected member, excluding the selected member

Children (Inc)

The selected member and all of its children

Level 0 Descendants

All descendants of the selected member that have no children

TIP

You can search to find a specific member to include on your data form.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

17-15

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Creating Substitution and User Variables ƒ Substitution variables are created in Administration Services Console and reference a member that is assigned to a variable value; for example: — BudYear = FY08 — ActYear = FY07 — CurrMonth = March

ƒ User variables filter members displayed in data forms; for example MYCostCenter = East (Descendants inclusive).

e d a

User variable

No user variable Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Substitution and User Variables

y m

c A

Administrators can create and define substitution variables (references to values). Typically, you use substitution variables for financial reporting. Substitution variables are commonly used in situations where a value (such as current month) references a member name (such as Mar) across multiple data form references. The benefit of using substitution variables is that the variable is maintained in one place at one time, rather than across the multiple data form references. Similarly, you can set up user variables to filter members in data forms, thus enabling planners to view only the dimension members with which they are working. User variables can be created by administrators and interactive users. You can navigate to the Manage User Variables page from the Administration menu. After a variable is created, it must be selected as a member in the data form layout. If a user variable is assigned to a data form, business users cannot access the data form until they select a member for the user variable. This task is performed in User Variable Options, accessed from the Preferences option of the File menu.

e l c

a r O 17-16

Planning: Create and Manage Applications

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

Creating Asymmetric Columns and Rows Example of asymmetric columns:

ƒ Column A: Scenario = Actual, Time Period = Q1 ƒ Column B: Scenario = Budget, Time Period = Q2, Q3, Q4

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Asymmetric Columns and Rows

e d a

c A

You can create data forms with asymmetric columns or rows. Asymmetric columns or rows contain different sets of members selected across the same dimension. You create asymmetric columns or rows by using the Add Row or Add Column button on the Data Form Layout page.

e l c

a r O

Planning: Create and Manage Applications

17-17

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Setting Page and Point of View

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Page and Point of View

e d a

c A

On the Page/Point of View Layout tab, you set up dimension members for pages and point of view. You can select dimensions and members for the page axis. You can choose to display member names or aliases, and you can define the POV dimensions and members for any dimension that is valid for the data form plan type and that is not assigned to a page, column, or row axis. The POV toolbar enables you to set the unique set of dimension members that defines specific intersections of data. You can clear the Visible option for the dimensions on the point of view so that members for the POV dimension are not displayed on the data form. Not showing dimensions in the point of view is especially helpful if the member for the point of view is No Customer, No Scenario, or something similar.

e l c

You can select the option Enable Dynamic User Variables to prompt the user to select the POV member to use on the data form.

a r O 17-18

Planning: Create and Manage Applications

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

Setting Options on the Other Options Tab

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Options on the Other Options Tab

e d a

c A

On the Other Options tab, you can set options for the data form’s display, functionality, and printing. For example, you can select to display missing values as blank rather than as #missing. Enable account annotations You can enable account-level annotations. In a data form, users can add annotations to accounts. However, a user must have Write access to the individual Account, Entity, Scenario, and Version members. Account-level annotations can vary, as combinations of Scenario, Version, and Entity dimensions vary. To enable annotations for the account dimension, you must follow these rules:

e l c

• Account must be selected as a row dimension.

a r O

• Scenario and Version must be selected as page or POV dimensions.

Planning: Create and Manage Applications

17-19

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders • Entity must be selected as a page, POV, or row dimension. • The Scenario, Version, Account, and Entity dimensions cannot be selected as a column dimensions, because the annotation is unique to scenario, version, account, and entity. Allow multiple currencies per entity For applications that support multiple currencies, you select this option to allow entities to support multiple currencies, regardless of base currency. Then, within data forms, business users can select the currency in which cell values are displayed. Enable mass allocation In order to ensure that business users can spread data across dimensions, you select the “Enable Mass Allocate” option. Selection of this option enables business users to use the Mass Allocation option for the data form. Enable grid spreading In order to ensure that business users can spread data across dimensions, you select the “Enable Grid Spread” option. Selection of this option enables business users to use the Grid Spreader option for the data form.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 17-20

Planning: Create and Manage Applications

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

Identifying Missing Values ƒ Cells with #missing have no data value. ƒ Write #missing to the database in one of three ways: — Leaving cells blank — Deleting contents of cells — Entering #missing

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Identifying Missing Values

e d a

c A

You can write #missing to the database from a data form. Instead of entering a number, enter #missing; or delete the contents of the cell, leaving it empty. When you save the data form, the cells are set to #missing in Essbase. Data entry cells that are blank or that contain the term #missing have no data value. In certain cases, when conversion to a selected currency is attempted, parent entities display #missing. On a data form or report, make sure that a currency rate is entered for each combination of local currencies and selected currencies. Also make sure that currency combinations exist for all mixed-currency child entities and their parent members.

e l c

NOTE

When a data form that is designed to suppress missing data is reloaded, rows that contains only cells with #missing are not displayed.

a r O

Planning: Create and Manage Applications

17-21

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Selecting Business Rules

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Selecting Business Rules

e d a

c A

You can create business rules by using a graphical user interface in Administration Services. These business rules can be launched directly from Planning, or they can be associated with data forms. Both designers of data forms and users entering data into data forms can see and launch only business rules to which they have access. Administrators and interactive users can define business rules that prompt users for input when the rules are launched. Planning includes two default business rules: Calculate Data Form and Calculate Currencies. Calculate Data Form is programatically created for each data form, to calculate subtotals. Calculate Currencies is created for data forms that include multiple currencies, to enable the conversion of values among the available currencies.

e l c

a r O 17-22

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders By default, the Calculate Data Form and Calculate Currencies business rules are selected. In the Business Rule Properties dialog box, you can set whether or not each business rule that is associated with a data form is automatically launched when data is saved. If a business rule has runtime prompts, you can also set whether or not the default member selection in the runtime prompt window matches the current member selection in the page and POV axes. After you enter data in a data form (or through a data form in Hyperion Smart View), you must calculate new totals for parent members, using the Calculate Data Form business rule. The rule calculates totals only for the members in the data form. For example, if West and its children California and Oregon are in a data form, after you save, calculate, and refresh the data form, a new total is displayed for West. Because North America, the parent of West, is not in the data form, a new total for North America is not calculated. Administrators and interactive users can set up business rules that, when launched from Planning, prompt users for such variables as members, text, or numbers. Here are some examples of runtime prompts:

y m

• Please select an account. • Select a month.

e d a

• Enter the expected number of customer visits per quarter.

c A

• What percentage change in earnings do you expect next month?

Create prompts that are specific and that let the user know what type of data is expected. NOTE

e l c a r O ly & On l a e n r s e t U n I

When launching a business rule with a runtime prompt, Planning validates the value entered, but it does not validate the business rule.

NOTE

The order in which business rules are launched is important and may affect the data. If you are launching both conversion and subtotal business rules, the currency conversion rules must be run before the subtotal rules.

e l c

a r O

Planning: Create and Manage Applications

17-23

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Previewing Data Forms

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Previewing Data Forms

e d a

c A

You can review the data form on the Preview tab. During the design of a data form, you can preview its structure and continue to make changes. The preview shows which dimensions are assigned to the POV, column, row, and page axes. Preview does not display data associated with the data form, member attributes, or aliases.

e l c

a r O 17-24

Planning: Create and Manage Applications

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

Composite Data Forms

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Composite Data Forms

e d a

c A

You can create composite data forms to view several data forms, even forms associated with different plan types, simultaneously. Business users can perform data entry and see the results aggregated to an upper-level intersection, such as Total Revenue, Total Departmental Expenses, or Net Income. You can use composite data forms to accomplish the following tasks: • Combine two or more data forms on one screen

• Perform real-time impact analysis by entering data in one data form (for one plan type) and viewing calculated results in another data form (for the same or another plan type)

e l c

• Choose the order that data forms are displayed on the screen and whether to combine the POV and page dimensions

a r O

Planning: Create and Manage Applications

17-25

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Creating Composite Data Forms

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Composite Data Forms

e d a

c A

Some of the tasks for creating composite data forms are the same as for creating regular data forms. You set up the following parameters: • Data form properties

• Row and column layout

• Business rules selection and properties • Access permissions

You create composite data forms from the Manage Data Forms option on the Administration menu. To create a composite data form, you select Create Composite.

e l c

You can set options for the POV, the pages, and the number and layout of columns and rows. You also select the data forms to display on the composite data form.

a r O 17-26

Planning: Create and Manage Applications

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

Selecting Business Rules on Composite Data Forms

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Selecting Business Rules on Composite Data Forms

You select business rules for composite forms on the Business Rules tab. You can include all business rules of the base forms or specific business rules. If you select an individual business rule, you can click Properties to set the properties for that rule. On the Business Rules properties screen, you set whether the business rule runs when the data form is loaded; whether the rule runs when data is saved; whether, if the rule contains a prompt, the members on the data form are used; and whether to hide prompts, if the rule contains any.

e l c

a r O

Planning: Create and Manage Applications

17-27

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

Printing Data Form Definition Reports

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Printing Data Form Definition Reports

e d a

c A

To enable better data form management, administrators can print a data form definition report. The report can include information on dimension members, business rules, and access rights associated with the data form, as well as other standard data form components.

e l c

a r O 17-28

Planning: Create and Manage Applications

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

Assigning Access Rights to Data Forms

ƒ Read: Enables users to view and use the data form for data entry. ƒ Write: Enables users to change the data form’s design and to view and use the data form for data entry. ƒ None: Prevents users from viewing the data form. Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Assigning Access Rights to Data Forms

y m

T o get the latest set of users and groups from the User Management Console, click Migrate Identities.

e d a

c A

By assigning access to a data form, you control which users can access and change the data form design (for example, data form properties such as formats, layout, and instructions), and which users can access the data form for data input. A user or group can have only one of the following access rights: Read, Write, or None. However, the access rights for a user can be combined with the user’s group rights. You create and change data form designs by using the Manage Data Forms option on the Administration menu. Administrators and interactive users have access to this task. When you are designing a data form in Planning, the selection list to set properties is filtered based on access rights. For example, when you set up the data form layout for page, column, row, and point of view, you select from the list of dimension members to which you have Read or Write access.

e l c

a r O

Planning: Create and Manage Applications

17-29

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders Access to specific data forms created by administrators or interactive users is based on access rights. For example, if you have Read access to a data form, you can view the data form in a list and select it. Whether you can change data in a data form depends on whether you have access to the members of the form. In order to edit a data form, you must have access to at least one member of each secured dimension on the form. For example, if you have Read access to the Europe entity, all rows and columns on the data form that include the Europe entity are displayed in read-only format. By assigning access to data forms, administrators and interactive users determine the following access rights: • Who can view and change various data form designs. By default, administrators have Write access to all data forms. Based on access rights, interactive users have Write access to certain data forms. • Who can access data forms for view or data input. By default, administrators have Write access to all data forms. Based on access rights, interactive users and planners have access to certain data forms. Whether users have access to the data in a data form depends on whether they have access to the members of the form..

y m

e d a

NOTE

Access rights are assigned to data forms, not to data form folders. You can assign access to only one data form at a time.

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 17-30

Planning: Create and Manage Applications

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

Summary In this lesson, you should have learned to: • Manage data forms and folders • Set up row and column properties • Set up page and POV properties • Assign business rules to data forms • Set up display and precision options • Manage data forms • Create composite data forms

y m

• Print data form definition reports

e d a

• Assign access rights to data forms

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

17-31

Module 6

Designing Data Forms

Lesson 17 Creating Data Forms and Folders

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 17-32

Planning: Create and Manage Applications

L E S S O N

1 8

Customizing Data Forms

18

Objectives At the end of this lesson, you should be able to: • Export and import data forms • Create menus • Specify application default settings • Manage user variables

y m

• Set up user preferences

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Exporting and Importing Data Forms ƒ To export a single form to an *.xml file, type FormDefUtil.cmd export ƒ To import a single form from an *.xml file, type FormDefUtil.cmd import ƒ To export all data form definitions, type FormDefUtil.cmd export -all ƒ To import all data form definitions, type FormDefUtil.cmd import -all> Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Exporting and Importing Data Forms

y m

e d a

c A

You can use the FormDefUtil.cmd Planning utility to export and import a data form definition from and into an XML-based file. You can move data form definitions from one Planning application to another. For example, use the FormDefUtil utility to move data forms from a development environment to a production environment. Planning includes the FormDefUtil.cmd utility for use through a command line interface. This utility is installed in the bin directory. NOTE

If you installed Planning to the default location, the bin directory is located in the following path: x:\Hyperion\HyperionPlanning\bin.

e l c

a r O

Only administrators can run this utility.

18-2

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms The following table describes the parameters of the utility: Parameter

Description

import or export

Specify whether to import or export the data form definition.

file name or data form name

Use file name to specify the name of the XML file to import into the Planning application.

planning server name

Specify the name of the application server that Planning is using (for example, localhost).

user name

Enter the name that you use to log on to the Planning application (for example, smith).

password

Enter the password that you use to log on to the Planning application (for example, pass1).

application

Enter the name of the Planning application (for example, FYPlan).

Use data form name to specify the Planning data form to export to XML.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

18-3

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Menus 1. Create the menu. 2. Set up menu Item properties for the menu. 3. Associate the menu with data forms.

y m

Copyright © 2007, Oracle. All rights reserved.

Menus

e l c a r O ly & On l a e n r s e t U n I

e d a

c A

Menus are displayed when business users right-click data-form rows or columns. Business users can use right-click menus to perform separate and distinct actions. For example, after entering data, a business user can move to the Manage Process page by using a right-click menu. A predefined scenario and version can be passed for use on the Manage Process page. Administrators create right-click menus and associate them with data forms. By creating right-click menus, administrators enable business users to click rows, columns or pages in a data form and select menu items to accomplish various tasks: • Launch another application, URL, or business rule, with or without runtime prompts

e l c

• Move to another data form

a r O

• Move directly to the Manage Process page, with a predefined scenario and version

18-4

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms To support context-sensitive actions, the context of the right-click is relayed to the next action. Planning passes this context: the POV and the page, the member on which the user clicked, and the members to the left (if a row was clicked), or the members above (if a column was clicked).

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

18-5

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Creating Menus

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating Menus

e d a

c A

Administrators use the Manage Menus page to create, edit, and delete menus. The Manage Menus page lists menus defined in the application. To create menus:

1. Select Administration > Manage Menus. 2. Click Create.

3. Enter a name for the menu, and then click OK.

4. To further define the menu, select the menu, and click Edit.

e l c

5. To add the first item to the menu, click Add Child, and Save.

a r O 18-6

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms 6. Continue building the menu by selecting a menu item and performing one of the following actions: • To add menu items below the selected item, click Add Child (available for Menu Header menu types). • To add menu items at the same level as the selected item, click Add Sibling. • To edit menu items, click Edit, and then follow step 8 to set up menu item properties. • To delete menu items, click Delete. • To change the order of menu items within the same level, select one or more items, and click the up or down arrow. 7. Set up the menu items. The following table describes the choices that you can apply for each item.

y m

Item

Description

Menu Item

Enter a unique name that contains only alphanumeric and underscore characters (for example: Position) and no extended characters, special characters, or spaces.

e d a

Note: Labels can contain spaces, special characters, and extended characters. Label

Icon

e l c

c A

Enter the text to be displayed when the menu is selected. Spaces and special characters are allowed. Menu labels are displayed on the user interface. Labels can be text or they can reference a resource variable by name. For example, to set a menu’s label to File, set it to File directly or set it to the name of a resource—such as LABEL_FILE.

e l c a r O ly & On l a e n r s e t U n I

Optional: In context of the Planning server, enter the path to and name of a graphic (for example, /Planning/Images/globe.gif),to be displayed next to the menu.

a r O

Planning: Create and Manage Applications

18-7

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms Item

Description

Type

Select the menu item type. Your selection determines the available properties. For example, no properties are available for the Menu Header type. Choose from the following types: • Data Form—Launch a selected data form. When users rightclick in the source data form, the member selection context for the member, page, and POV is retained. If the target data form contains the dimension members identified by the context, the target data form’s page is set to match the context. • URL—Navigate to the specified URL. • Business Rule—Launch the selected business rule. • Workflow—Move to the Manage Process page to work with a planning unit. • Menu Header—Create a menu under which you can create child menu items. To distinguish the header from other menu items, insert a separator bar by entering one hyphen as the label for the header item. For menu headers, the Required Dimension list is not available.

Required Dimension

y m

Select the dimension for which the menu item is displayed. For example, if, for a menu item, you select Account, when users rightclick Account members, the menu item is available. Selecting No Required Dimension makes the menu available wherever the user right-clicks in the data form.

e d a

c A

8. To set up characteristics for menu items, select the menu item, and click Edit. Menu item properties differ, depending upon the menu item’s type. The following table describes the choices that you can apply for each item. Item Data Form

URL

e l c

e l c a r O ly & On l a e n r s e t U n I Description

a. From Data Form Folder, select the folder that contains the destination data form. b. From Data Form, select the data form. a. In URL, enter the complete URL to which to direct the user. b. Select Use Single Sign-on to append the SSO token to the URL. c. Select Launch in a Separate Window to launch the URL in window other than the Planning main window.

a r O 18-8

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms Item

Description

Business Rule

a. From Plan Type, select the plan type for which the business rule is available. b. From Business Rules, select the business rule to launch. c. From View Type, select how to display runtime prompt pages: • Classic View—Use the default Planning view. • Streamline View—Display each runtime prompt on a different line, instead of in a different section; eliminate icons; and reduce screen text. d. Optional: In Window Title, enter a title to be displayed, instead of Runtime Prompts. e. Optional: In OK Button Label, enter the text to be displayed for the OK button. f. Optional: In Cancel Button Label, enter the text to be displayed for the Cancel button. g. Optional: Select Launch in a Separate Window to launch the business rule in window other than the Planning main window.

Workflow

Specify the planning unit to which the user is directed by selecting a scenario and a version.

y m

9. Click Save.

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

18-9

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Associating Menus

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Associating Menus

e d a

c A

When designing a data form, use the Other Options tab to select which menus are available for the data form. As you update applications, update the appropriate menus. For example, if you delete a business rule that a menu references, remove it from the menu.

e l c

a r O 18-10

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Advanced Settings

y m

e d a

Only administrators and application owners can view and set Advanced Settings. Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Advanced Settings

c A

Administrators have access to Advanced Settings, which includes the System Settings and Custom Tools tabs. The Show drop-down list has a second option which lists the current application defaults for application settings and display options. The Advanced Settings options are available through the Administration menu. Administrators can specify settings to use across the current application. Nonadministrators cannot access application-wide settings. Because application owners must set up certain options before business users can make their selections, the Application Settings tab is displayed differently for the application owner than for other application users. For example, before users can enable an e-mail notification, the application owner must set up the application's e-mail server. Only the application owner can set two of the system settings: E-mail Server and Password for Synchronizing With Essbase.

e l c

a r O

Business users can override the application-wide default settings by setting preferences.

Planning: Create and Manage Applications

18-11

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

System Settings Tab The following table describes the options on the System Settings tab: Component

Description

E-mail Server

Type the name of the server that hosts e-mail services for the application users; for example, mail.hyperion.com. Available only to the application owner.

E-mail Character Set

Specify the character set used for e-mail messages: • UTF-8: Use the Unicode encoding format (the default). • Regional Setting: Use the system's regional setting.

Shared Services URL

Type the URL for the Shared Services server, and click Register Shared Services.

Display Users’ Full Names

Select Yes to show the users’ full names (for example, John Smith) in addition to their user names (for example, JSmith). Select No to suppress the display of the users’ full names. Note: If the Display Users' Full Names check box is selected, you cannot have two users with identical full names. If you try to add a user with the same full name as an existing user, an error message is displayed.

y m

Enable Use of the Application for

Specify whether users can access the application when it is in maintenance mode, such as during backups. Select Owner, Administrators, or All Users to give access to the application owner, to administrators, or to all users.

Enable display option of Substitution Variables

Set how substitution variables display in the Member Selection dialog box when users respond to runtime prompts in business rules:

e d a

e l c a r O ly & On l a e n r s e t U n I • Display All: Display all substitution variables

c A

• Display None: Do not display substitution variables • Enable Filtering: Display only substitution variables that are valid for the runtime prompt

Select User

Assign an administrator to be the application owner. (By default, the person who creates the application is the application owner. However, the owner may grant ownership to another administrator.)

Custom Tools Tab

You can customize Planning to include links to commonly used tools for analyzing, tracking, and reporting on planning data. Users can access these links from the Planning Tools menu.

e l c

a r O 18-12

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Current Application Defaults

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Current Application Defaults

e d a

c A

Select Current Application Defaults, and click Go to access the Application Settings tab and the Display Options tab. When you save, the values specified in these tabs become the application defaults. Other users can override the defaults and revert to the defaults—by selecting the Use Application Defaults check box on the Preferences tabs.

e l c

a r O

Planning: Create and Manage Applications

18-13

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Managing User Variables Here is the typical sequence of steps to set up and use user variables: 1. Create the appropriate parent-level members in the dimension outline (if they do not already exist). For example, the parent levels could correspond to the business unit divisions. 2. Create user variables for each dimension that you want planners to be able to filter. 3. When designing the data form, associate the user variables with the data form.

y m

4. Notify planners that they can select members for the user variables that are associated with the data form.

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Managing User Variables

e d a

c A

You can limit the number of dimension members that are displayed on a data form by setting user variables. Using user variables increases performance and enables planners to focus on those members with which they want to work. For example, for the Entity dimension, you can set up a user variable called Division, and then, for Division, planners can select the members that represent their specific division. You can set up as many user variables as you want for each dimension. User variables can be selected for any axis in the data form: row, column, page, or point of view (POV).

e l c

a r O 18-14

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Creating User Variables 2 1

3

4

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Creating User Variables

y m

5

e d a

c A

You add or delete user variables from the Manage User Variables option on the Administration menu or from the New User Variable option on the File menu. You select the dimension for which the user variable will be used and then create a user variable name.

e l c

a r O

Planning: Create and Manage Applications

18-15

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Applying User Variables

2

1

3

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Applying User Variables

e d a

c A

After you create a user variable, you associate the new user variable with a data form. You can either create a new data form or edit an existing data form and select the member relationship for the dimension that contains the new user variable. In the example shown in the slide, the Division user variable is in the Entity dimension, which is placed on the Pages drop-down list for this data form. Furthermore, you select the descendants inclusive option for Division. To associate a user variable with a data form:

1. In the Member Selection dialog box, select a user variable.

e l c

2. From the relationship drop-down list, select the relationship, and then use the right arrow to move the user variable to the Selected Members list.

a r O

When a user variable is selected, it is preceded by an ampersand.

3. Click Submit.

18-16

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Setting Up User Preferences

y m

e d a

All users can set preferences. Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Up User Preferences

c A

On the Preferences page, for the current application, all users can set individual preferences. Administrators and application owners can also specify certain global settings for the current application. Non-administrators do not have access to application-wide settings. Only the application owner can set the following system settings: E-mail Server and Password for Synchronizing with Essbase. All users have access to a Preferences page that has four tabs: Application Settings, Display Options, Printing Options, and User Variable Options. Each preference can be enabled and configured. In the Application Settings tab, you configure e-mail notification, select the alias setting, and set workflow options.

e l c

a r O

Planning: Create and Manage Applications

18-17

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Setting Up E-mail for Workflow Notifications When e-mail is set up and notification is enabled, Planning notifies users when they become the new owner of a planning unit. The subject of the e-mail is in the format NEW OWNER: XYZ Plan (Scenario, Version, Entity).

Applying Alias Tables You can assign alternate names, or aliases, for Account, Entity, and user-defined dimensions and members. You can select aliases for displaying member and dimension names. For example, an alias table called French could display members in French, and another alias table called German could display members in German.

Setting Member Selection and Workflow Options In the Member Selection Options area, you can set whether aliases and descriptions are displayed in the Member Selection dialog box. In the Workflow Options area, you can control the following aspects in Process Management:

y m

e d a

• Whether to display members’ actual names or aliases, if they have them

• Whether planning units that are not started are displayed with those that are started

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 18-18

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Setting Individual Display Options

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Individual Display Options

e d a

c A

You set individual display options on the Display Options tab.

Your number-format selections apply to all currency values that are displayed in all data forms that are within the current application and that you can access. These selections can override default settings. If you select Currency Setting, the currency values in the data form are displayed using the formatting initially set for each individual currency. If you select any other option, your selection applies to all currency values that are displayed in all data forms that are within the current application and that you can access. Use the Display Options tab to perform the following tasks:

e l c

• Change how numerical values are displayed in the data form

a r O

• Enable retention of page dimensions

Planning: Create and Manage Applications

18-19

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms • Set the indentation of members on a page • Set aspects of page selection, such as remembering the last page selected when navigating among data forms and allowing a search facility when the number of pages exceeds a certain number • Enable warning for large data forms • Set how many members to be displayed on each page • Increase the contrast of the Planning interface • Set the date format Keep in mind the following points about display options: • The options listed on the Display Options tab depend on the type of user. Only administrators can set the number of members to be displayed on each page. • Formatting selections take effect when you leave the data cell. • If you select a setting other than the Use Application Default setting for either the thousands separator or the decimal separator, then you must change both separators from the Use Application Default setting option. However, you cannot select the same option for both the thousands and decimal separators.

y m

e d a

Page Selection Options The most recently used dimension members from the page of the last data form that you used are remembered and compared to the members of each data form that you select. If there is a match, that member name is displayed in the drop-down list of the new data form that you select. NOTE

e l c a r O ly & On l a e n r s e t U n I

c A

For the current application, the “Page retention” setting applies both within a session and between sessions. When you are working with a large number of pages, you can select among the pages more easily by using a Search drop-down list that Planning adds to the data form when the number of pages exceeds a value that you specify.

e l c

a r O 18-20

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms Warning on Large Data Forms Unusually large data forms with numerous cells may require significant time to open. You can choose to display a warning when data forms that are larger than a specified number of cells are opened. When you try to open a data form that exceeds the specified size limit, a warning is displayed about the time needed to open the data form, so that you can choose whether or not to open it.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

18-21

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

Setting Individual Printing Options

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Individual Printing Options

e d a

c A

You set printing options directly from the data form when you are ready to print; or you can use Preferences to set printing options. The options that you set from the Preferences page apply to all data forms to which you have access. NOTE

You can accept the default settings or set your own options for creating PDF files. To print to a PDF file, you must have Adobe Acrobat Reader 4.0 or later installed. Printing options for a data form are set by the data form designer when the data form is created.

e l c

a r O 18-22

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Setting Individual User Variable Options

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Setting Individual User Variable Options

e d a

c A

By acting as filters that reduce the number of members that are displayed on a form, user variables help you to open and navigate large data forms that contain many members. You can select dimension members, such as entities in your own region, on which to focus. If a data form contains a user variable, you must select a value for the variable on the User Variable Options tab before you can open the data form. If you do not set the user variable, you receive an error message when you attempt to open the data form. User variables are not related to security. If you want to see different members on your data forms, you can change the user variable at any time.

e l c

a r O

Planning: Create and Manage Applications

18-23

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms For example, if your company has many cost centers, you can create a data form that includes a user variable called MyRegion. Then, by selecting a member for MyRegion, you can limit the number of pages that are displayed in the Page drop-down list. In this case, before you can open the data form, you must select a value, such as Central, for MyRegion. At any time, you can select a different value, such as South, for MyRegion.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 18-24

Planning: Create and Manage Applications

Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Summary In this lesson, you should have learned to: • Export and import data forms • Create menus • Specify application default settings • Manage user variables • Set up user preferences

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

18-25

Module 6

Designing Data Forms

Lesson 18 Customizing Data Forms

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 18-26

Planning: Create and Manage Applications

M O D U L E

7

Entering Data in Planning

18

Overview The aim of this module is to provide an overview of how to enter and adjust plan data in Planning and Smart View. You learn how to enter, adjust, annotate, and calculate data using data forms in Planning as well as in Smart View. In addition, you learn how to take Planning data offline, work with data offline and then synchronize data to the server. Lessons in this module include: • Entering Data

y m

• Entering Data in Smart View

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

L E S S O N

1 9

Entering Data

19

Objectives At the end of this lesson, you should be able to: • Submit data in data forms • Adjust and annotate plan data • Calculate data in data forms • Enter data with smart lists

y m

• Navigate data forms with menus

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 7 Entering Data in Planning Lesson 19 Entering Data

Submitting Data in Data Forms

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Submitting Data in Data Forms

e d a

c A

You use Planning to enter plan data in data forms. You can enter data from the start page in Advanced mode by selecting forms in the view pane to work on in the content area. In Basic mode, you can enter data only if your administrator sets up a task that includes a form. In both modes, you can enter and edit only data to which you have access. These are the data-entry tasks that you can perform: • Type data directly into cells on a data form

• Spread data from summary to base periods automatically • Adjust existing data and add supporting details

e l c

• Annotate planning units, accounts, or cells • Export data to a spreadsheet

a r O

• Launch business rules to perform predefined calculations on data that you enter

19-2

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Elements on the Enter Data Page Row Headings

Point of View

Toolbar Icons

Page List Column Headings

View Pane

y m

e d a

Content Area Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Elements on the Enter Data Page

c A

There are several areas on the enter data page that assist you with navigation, data selection, and data entry. View Pane The view pane lists the form folders that are set up for your application. Data forms are contained within the folders. After you select a folder, a list of data forms within the selected folder is displayed on the view pane as well as in the content area. You can select a data form from this list. After you select a data form, it is displayed in the content area. Content Area Data forms are displayed in the Planning content area. A data form provides an intuitive layout for you to work with the data in your plan from the Web. Data forms displayed in the content area reflect the access rights that you have to the dimension members on the data forms.

e l c

a r O

Planning: Create and Manage Applications

19-3

Module 7 Entering Data in Planning Lesson 19 Entering Data Elements of the Content Area for Data Entry The following table summarizes elements of the content area for data entry: Element

Description

Toolbar icons

The toolbar includes icons to save, refresh, print, adjust, lock cells, grid spread, mass allocate, cut, copy, and paste data. The toolbar provides a quick way of entering cell text and supporting detail as well as exporting spreadsheets and logging off.The toolbar also provides immediate access to task lists, task list status, and help.

Row and column headings

Row and column headings show the members available on a data form. To make the data form easier to work with, you can choose to hide or view the children of a parent member.

Point of view

Across the top of the data form is the point of view (POV) for the form. The members displayed in the point of view show the context of the data in the pages, rows, and columns.

Page list

The page list is a drop-down list of members from one or more dimensions to be selected for data entry. The rows and columns on the form show values for the currently selected page member.

Data-entry cells

You enter data in the cells at the intersection of rows and columns. Cells with existing data display data values. You can enter data in cells that are not shaded, whereas shaded cells are read-only.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 19-4

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Data-Entry Menu Options

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Data-Entry Menu Options

e d a

c A

From the File menu, you can save data values or print data forms. You can also export data values to spreadsheets. You can use the Edit menu to adjust, grid spread, mass allocate, cut, copy, and paste data values. From the Edit menu, you can also launch business rules associated with the data form, annotate planning units, add or view cell text, add or view supporting detail, and lock or unlock cells. If you have purchased workforce and capex, you can initialize workforce and capex from the Edit menu. From the View menu, you can refresh data values, view data form instructions, view currencies for data forms that allow currency overrides, and edit account annotations. You can use the View menu to switch between Basic and Advanced modes and work with task lists.

e l c

a r O

From the Tools menu, you can launch business rules to which you have access.

Planning: Create and Manage Applications

19-5

Module 7 Entering Data in Planning Lesson 19 Entering Data

Viewing Form Instructions

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Viewing Form Instructions

e d a

c A

When you define a data form, you can include information to help planners use the form to prepare plan data. You can access the form instructions in two ways: • Select a data form from the list of forms contained within a selected folder in the content area. Then you can select the link to view form instructions. You see the instructions view link only if there are instructions for the form. • Select View > Instructions when working with an open data form.

e l c

a r O 19-6

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Recognizing Cell Color Cues

Cell with Modified Data Locked Cell

Cell with Cell T ext

Cells with Supporting Details

y m

e d a

Display Only Cells Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Recognizing Cell Color Cues

c A

You enter data in Planning applications by typing values into the cells of a data form. Cells in which you can enter data do not have a shaded background. If data exists for a cell, it is displayed in the cell, and you can type over it. If data does not exist for the cell, the cell displays the text #missing, and you can replace the text with a value. When you define data forms, you have the option of displaying cells containing no data as blank. Planning data forms use color cues to indicate whether a specific action was performed on a cell. Color cues are provided for cells when: • Data was modified since the last save. • The cells are locked.

e l c

• The cells are read-only.

a r O

• The cells contain supporting details. • The cells contain cell text.

Planning: Create and Manage Applications

19-7

Module 7 Entering Data in Planning Lesson 19 Entering Data Calculated Cells The values for some cells are calculated automatically. When you enter a value into a bottom-level period, the totals for summary periods are updated immediately. For example, when you enter a value into the cell for a month, the totals for the quarter and year are updated immediately. When you enter values into children of a parent member for dimensions other than Period, the updated totals for the parent are not calculated until you save the data or calculate the data form. For example, if you enter values for Sales and Cost of Goods Sold, you do not see updated totals for their parent Gross Margin until you save the data. Display-Only Cells Cells that are display-only are shaded. You cannot type values in display-only cells. The following conditions can cause cells to be display-only: • One of the dimension members associated with the cell is a parent. Because parent values are calculated from child values, you cannot enter values for parents unless the version is a target version.

y m

• You do not have write access to one of the members associated with the cell. • The currency for the cell is not set to Local.

e d a

• The planning unit associated with the cell may be under review and owned by another user. You cannot modify data for a planning unit that is under review unless you are the current owner of the planning unit or a budget administrator.

c A

• The periods may be outside the range that is valid for the current scenario. NOTE

e l c a r O ly & On l a e n r s e t U n I

Administrators can set up members so that text can be entered into cells on data forms. In EPM Architect, administrators can set up members as a data type of Currency to enable business users to key numerical values. In addition, administrators can set up members to enable the input of percentages, smart lists, date, or text values.

e l c

a r O 19-8

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Navigating Data Forms Special Keys:

Expand and Collapse:

ƒ Enter ƒ Tab

Expanded

Collapsed

Q1

Q1

ƒ Shift +Tab ƒ Esc ƒ Ctrl + z ƒ Ctrl + c

Jan

Feb

Mar

30000

30000

30000

90000

30000

90000

1000

1000

1000

3000

1000

3000

#missing

#missing

#missing

#missing

#missing

#missing

ƒ Ctrl + x

Apr

Hiding children

Showing children

ƒ Ctrl + v

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Navigating Data Forms

e d a

c A

The following table summarizes the special keys that you can use during data entry. Key

Result

Enter

Enters the value that you typed and moves the cursor to the cell below the current cell

Tab

Enters the value that you typed and moves the cursor to the next cell in the row

Shift+Tab

Enters the value that you typed and moves the cursor to the previous cell in the row

Esc

Cancels the value that you typed and restores the previous value

Ctrl+z

Cancels the value that you typed and restores the previous value

e l c

Ctrl+c

Copies the selected range of cells to the clipboard

a r O

Planning: Create and Manage Applications

19-9

Module 7 Entering Data in Planning Lesson 19 Entering Data Key

Result

Ctrl+x

Cuts the selected range of cells to the clipboard

Ctrl+v

Pastes content from the clipboard

You can choose to hide or view children of parent members. Showing and hiding children enables you to navigate forms more easily when the data forms contain a large number of members in the rows or columns.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 19-10

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Copying and Pasting Data ƒ Copy and paste data values from within one data form to another data form. ƒ Copy and paste data values from other applications such as Excel to a data form.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Copying and Pasting Data

e d a

c A

If your Web browser is Microsoft Internet Explorer 5.5 or later, you can copy and paste data values from one data form to another data form or from another application such as Microsoft Excel. The following rules apply when you paste data into a form: • If the size of the selected destination area is an exact multiple of the size of the copied area, data is repeatedly pasted into the destination area. For example, if you copy the contents of two rows and then select six rows to paste the data into, Planning pastes the contents of the two rows three times, to fill the six destination rows. • You cannot paste data in display-only cells.

• Planning copies and pastes the actual stored values of cells, not the values that are displayed based on the precision setting.

e l c

a r O

• Data that is copied and pasted from Excel to Planning retains the formatting that is set up in Excel.

Planning: Create and Manage Applications

19-11

Module 7 Entering Data in Planning Lesson 19 Entering Data • When you paste data to summary periods, Planning applies spreading rules for each cell in succession, starting from left to right and top to bottom. So, the data resulting from a paste operation may not match the original copied data.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 19-12

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Working with Non-Aggregated Data

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Working with Non-Aggregated Data

e d a

c A

Administrators can flag members as non-aggregating. If you flag members so that they do not aggregate, then totals are not calculated on data forms. In addition to being able to set members for input of numerical values, you can set members for input of text or date input. For example, you can flag Asset Description, Asset Units, and Asset Rate members as non-aggregating members and therefore totals will not appear for those cells. You flag cells by selecting the non-aggregating option property 'Never' in EPM Architect.

e l c

a r O

Planning: Create and Manage Applications

19-13

Module 7 Entering Data in Planning Lesson 19 Entering Data

Saving and Refreshing Data

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Saving and Refreshing Data

e d a

c A

After entering or editing values in a data form, you save the information to the Planning application database. After you save the data, the form totals are recalculated to reflect the new data for members that are calculated dynamically. If you want to clear entered values without saving them, you use the Refresh button. When you click the Refresh button, the form is refreshed with the last saved values from the applications database; the last saved values replace all values that you entered but did not save.

e l c

a r O 19-14

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Spreading Data You can spread data from summary periods to base periods Jan

Feb

Mar

Q1

Revenue or Expense (Flow)

1000

1000

1000

3000

Asset, Liability, or Equity (Balance)

1000

1000

1000

1000

25

25

25

25

923

923

1154

3000

Percentage W eekly Distribution (4-4-5)

Type ! (Shift + 1) to lock or unlock a cell or group of cells. Jan Cell Locked

Jan

Feb

Mar

Q1

Jan Cell Not Locked

Jan

Feb

Mar

Q1

Before

100

100

200

400

Before

100

100

200

400

After

100

300

600

1000

After

250

250

500

1000

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Spreading Data

y m

e d a

c A

To make data entry more efficient, Planning automatically distributes values from summary periods to base periods. Base periods are the bottom-level members of the Period dimension. When you enter a value into the Year Total member, it is automatically distributed to the quarters and months. When you enter a value into a quarter, it is automatically spread to the months. How values are spread depends on the account type and the data type. Revenue and Expense Accounts If no data currently exists or if data is all zeros, a value entered in a summary period is divided evenly among the children of the summary period. For example, if you enter 300 into Year Total, the quarters in the year are automatically set to 75, and the months in each quarter are automatically set to 25.

e l c

a r O

Planning: Create and Manage Applications

19-15

Module 7 Entering Data in Planning Lesson 19 Entering Data If values exist for the base time periods, the existing proportional spread is preserved. For example, your current distribution might be January=100, February=100, March=200, and Q1=400. If you change the value of Q1 to 200, the new monthly values are January=50, February=50, and March=100. Asset, Liability, and Equity Accounts If no data currently exists or if data is all zeros, the value entered in a summary period is set for each of the base periods. For example, if you enter 1000 into Q1, then January, February, and March are set to 1000. If values exist for the base periods and you enter a new value for the summary period, the base period affected is determined by the time balance option associated with the account. The time balance options available are First, Average, Balance, Weighted Average-Actual_365, and Weighted Average-Actual_Actual. The time balance options and their effect on spreading data values is covered in greater detail in the next topic in this lesson. Percentages Some accounts have the data type Percentage. For these accounts, the value is allocated to each base time period, regardless of the account type or of whether data exists. For example, if you enter 25 in quarter 1, January, February, and March are all set to 25.

y m

e d a

c A

Weekly Distribution Some accounts in your application might be set up to use the weekly distribution option. When the weekly distribution option is selected for an account, Planning treats quarterly values as if they were divided into 13 weeks and, using the pattern specified by your budget administrator, distributes values to the weeks. For example, if the 5-4-4 distribution option is selected, Planning treats the first month in a quarter as if it has five weeks and the last two months as if they have four weeks. NOTE

e l c a r O ly & On l a e n r s e t U n I

You can temporarily lock the values of one or more cells to preserve existing values when spreading data, during which time Planning calculates and fills in values for the remaining base period cells. You can spread data across periods based on various calculations and visually review the changes before saving them to the database.

e l c

a r O 19-16

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Time Balance Options Jan

Feb

Mar

Q1

Flow

100

150

200

450

First

100

150

200

100

Balance

100

150

200

200

Average

100

300

200

200

Weighted Average-Actual_365

100

150

200

150

Weighted Average-Actual_Actual

100

150

200

150

Weighted Average-Actual_365 (100*31 + 150*28 + 200*31)/90 = 150 Weighted Average-Actual_Actual* (100*31 + 150*29 + 200*31)/91 = 150

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Time Balance Options

y m

*29 Days in Feb during a leap year

e d a

c A

The following time balance options can be used with Asset, Liability, and Equity account types: Balance, First, Average, Weighted Average-Actual_Actual, and Weighted Average-Actual_365. Revenue and Expense account types typically use the time balance option of Flow. Balance The Balance time balance option (also referred to as time balance last) displays the value of a summary period equal to the value of the last base period. For example, if the balance for Inventory for March is 200, the Quarter 1 balance is 200.

e l c

a r O

Planning: Create and Manage Applications

19-17

Module 7 Entering Data in Planning Lesson 19 Entering Data First The First time balance option displays the value of a summary time period equal to the value of the first base period. For example, if the balance for Inventory for January is 100, the Quarter 1 balance is 100. Average The Average time balance option displays the value of a summary period equal to the average of the base periods. For example, if the Inventory values are January=100, February=300 and March=200, the Quarter 1 balance is 200—the average of the three months’ balances. Weighted Average-Actual_365 and Weighted Average-Actual_Actual There are also weighted average time balance options. If you select Weighted AverageActual_365, each month assumes the actual days of a non-leap year. February always has 28 days and Year always has 365 days. If you select Weighted AverageActual_Actual, each month assumes the actual days of the current year. When Weighted Average-Actual_Actual is selected and the year is a leap year, February has 29 days.

y m

Flow The Flow time balance option displays an aggregate of all data values for a summary time period as a total for the period. For example, if the sales for January is 100, February is 150, and March is 200, the Quarter 1 balance is 450.

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 19-18

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Spreading Data Using Grid Spreader Enable Grid Spreader on the Other Options tab of Data Forms

FY07 Jan

Feb

Mar

Q1

Catalog

272.73

272.73

272.73

818.18

Commercial

272.73

272.73

272.73

818.18

Direct

272.73

272.73

272.73

818.18

Distributor

272.73

272.73

272.73

818.18

Education

272.73

272.73

272.73

818.18

Government

272.73

272.73

272.73

818.18

Indirect

272.73

272.73

272.73

818.18

Mail Order

272.73

272.73

272.73

818.18

Online

272.73

272.73

272.73

818.18

Retail

272.73

272.73

272.73

818.18

Special Events

272.73

272.73

272.73

818.18

All Channels

#missing

#missing

#missing

#missing

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Spreading Data Using Grid Spreader

y m

e d a

c A

Using Grid Spreader, business users can specify an amount or percentage by which Planning increases or decreases values across multiple dimensions on data forms. The spread is based on the existing values in the targeted cells. After you run grid spread, the grid is reloaded with the changed cells displayed. You have the option to view and validate results before saving data. Keep the following points in mind when using the Grid Spreader: • Grid Spread must be enabled on the data form in order to use it. • Grid Spreader supports proportional spreads, evenly split and fill.

e l c

• The Grid Spreader ignores read-only, locked, and supporting detail cells.

a r O

• Users can use the Grid Spreader only to spread data to the cells to which they have access.

Planning: Create and Manage Applications

19-19

Module 7 Entering Data in Planning Lesson 19 Entering Data

Spreading Data Using Mass Allocation

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Spreading Data Using Mass Allocation

e d a

c A

Mass Allocation enables predefined users (in Shared Services) to allocate across multiple dimensions. Mass Allocation executes calculation scripts and business rules against the Essbase server and all dimension combinations. After the rule is run, the grid is reloaded, and the mass allocation results are displayed. The results are saved to the database. Keep the following points in mind when using Mass Allocation:

• In order for users to spread data using Mass Allocate, the data form property for Mass Allocate must be enabled.

e l c

• Mass Allocation supports proportional and relational spreads.

a r O

• With updates to the spread pattern table, Mass Allocation supports fill; 4-4-5; and evenly split, pattern-based allocation.

19-20

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data • Mass Allocation security is based on roles similar to business rules. • Mass Allocate spreads data to all the source cell’s descendants, even those descendants that are not displayed on the data form. • You do not need to have access to target cells in order to use Mass Allocate. • After you spread data using Mass Allocate, you cannot undo this action. • Mass Allocate is processed with dynamically-created calculation scripts.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

19-21

Module 7 Entering Data in Planning Lesson 19 Entering Data

Adjusting and Annotating Plan Data ƒ Increase or decrease plan data by a percentage or value ƒ Perform ad hoc analysis — Spread data with cell locking — Use flexible data-entry operators

ƒ Add annotations — Cell text — Account annotation — Planning unit annotation

ƒ Enter supporting detail

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adjusting and Annotating Plan Data

e d a

c A

After entering your starting point plan data, you may need to adjust data values due to a change in market conditions, revised performance expectations, or new corporate assumptions. You may need to document these changes in the form of annotations or supporting details. Planning provides several options to assist you with this task. You can adjust data values by percentages, perform ad hoc analysis through flexible data-entry commands or by locking data values when you spread data, and enter supporting details. You can also annotate your assumptions at three levels: cell, account, and planning unit. During the data-entry and review process, you may need to adjust some values on a percentage basis, perhaps due to a change in market conditions or due to revised performance expectations. You can use the Adjust Data feature to increase or decrease by a percentage or value the current value in any cell or range of cells that contains data.

e l c

a r O 19-22

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Performing Ad Hoc Analysis ƒ Ad hoc analysis is especially useful for manipulating values in specific accounts to produce desired results. ƒ Before committing data: — Perform what-if calculations and visually review the changes. — See the impact of various scenarios before saving the data. Operation

Flexible Data Entry

Initial Value

Input Text

Result

Add +

100

+50

150

Subtract + -

100

+-50

50

Multiply *

100

*5

500

Divide /

100

/5

20

Percentage %

100

%25

25

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Performing Ad Hoc Analysis

y m

e d a

c A

You can apply what-if scenarios to existing values to see the impact of various conditions before saving data. This capability is especially useful for manipulating values in specific accounts to produce desired results. You can manipulate and experiment with data values in one of the following ways: • Lock a value when you spread data

• Change existing values by entering an operator (flexible data entry) • Export data to a spreadsheet

e l c

Before committing data by saving it, you can perform various what-if calculations and visually review the changes. You can change an existing value by using the operators: Add +, Subtract + -, Multiply *, Divide /, and Percentage %. The table shown in the slide provides examples of the impact of using the flexible data-entry operators.

a r O

Planning: Create and Manage Applications

19-23

Module 7 Entering Data in Planning Lesson 19 Entering Data

Exporting Data to Spreadsheets

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Exporting Data to Spreadsheets

e d a

c A

You can export data from a Planning data form to Excel to explore what-if scenarios in Excel before copying and pasting values back to Planning. Keep in mind the following information about exporting data from a form: • Planning does not export numerical formatting to Excel. Also, the application name, user name, form folder name, member aliases, dimension attributes, account annotations, currency tags, and percentages are not exported to Excel. • Values pasted back to Planning from Excel must be nonformatted data. • Excel supports the Internet Explorer browser.

e l c

• Every time you click Spreadsheet Export, a new instance of Excel is opened in the browser. Use the Close button to close any instances that you do not need.

a r O 19-24

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Adding Annotations ƒ Cell text ƒ Account annotations ƒ Planning unit annotations ƒ Supporting details

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Annotations

e d a

c A

You can add documentation to your plan in the form of annotations. You can add annotations at different levels depending on how general or specific the explanation needs to be. For example, very specific annotations can be entered at the cell level; this is referred to as cell text. General comments can be added at the Planning Unit level; this is referred to as a Planning Unit annotation. Annotations and supporting details are stored in the Planning relational repository; they are not refreshed in the Essbase database. You can print the data contained in a data form, including cell text, account annotations, and supporting detail. Planning unit annotations can be printed by budget administrators through Administration > Reporting or through Financial Reporting.

e l c

a r O

Planning: Create and Manage Applications

19-25

Module 7 Entering Data in Planning Lesson 19 Entering Data

Adding Cell Text and Account Annotations

y m

Account Annotation Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Cell Text and Account Annotations

e d a

c A

If you have read access to a cell, you can add annotations called cell text to the cell at any level. You can add cell text at the summary time period level and across multiple dimensions at any level. You can also add cell text for non-level-zero members (in bottom-up versions), calculated cells (Dynamic Calc), and read-only cells. You can use supporting detail and account annotations in addition to cell text to add comments to data. With supporting detail, you can build and communicate bottom-up values; with account annotations, you can add comments to accounts. You can add account annotations or comments during data entry. You can view comments that other users have entered. Account annotations are displayed in a column on the data-entry form.

e l c

Account annotations are associated with a specific account for a planning unit.

a r O 19-26

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Adding Planning Unit Annotations

Section

Description

Scenario, Version, Entity

Select the scenario, version, and entity that compose the planning unit for which you want to add or view annotations.

Enter Title

Enter a name for the annotation.

Enter Text

Enter and submit the text for the new annotation for the planning unit.

Existing Annotations

View the existing record of annotations associated with the planning unit Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Planning Unit Annotations

y m

e d a

c A

You can add annotations to a planning unit. A planning unit is a combination of a scenario, a version, and an entity member. Planning unit annotations are general comments that pertain to the planning unit as a whole, rather than to individual rows, columns, or cells on the data form. The table on the slide summarizes the sections on the Annotations window.

e l c

a r O

Planning: Create and Manage Applications

19-27

Module 7 Entering Data in Planning Lesson 19 Entering Data

Adding Supporting Detail

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Supporting Detail

e d a

c A

You can use supporting detail as a built-in calculator for developing data that is not in the member outline. It also provides a way for you to drill down into data and to better understand the basis of the data. Supporting detail helps you build and communicate bottom-up values when planning corporate expenses, such as travel, salary, and projects, for which you need to calculate aggregate values. Supporting detail can include text, values, and operators that define how data is aggregated. Additional information about supporting detail:

• Supporting detail does not change members in the Essbase outline structure.

e l c

• To create, change, or delete supporting detail, you must have write access to cells. You must have read access to view supporting detail.

a r O 19-28

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data • To protect values, you cannot enter, adjust, spread, or save data in aggregate values (summary periods) that have supporting detail. The aggregate values are read-only. You can add supporting detail only to base periods. • You can add supporting detail to both target and bottom-up versions. • Any number and precision formatting that is set up is not reflected in the Supporting Detail window. • The sequence of operators in supporting detail follows the logic that Essbase uses to process multiple operators in a complex calculation. • When you use Copy Versions, you can copy supporting detail from one version to another. You can also copy supporting detail using the Copy Data task. • When you delete supporting detail for a cell, you can set how the information is synchronized with Essbase. The information can be set in Essbase to #MISSING or left it as it was before the supporting detail was deleted. • When you enter or change supporting detail, you can copy and paste the information to multiple cells simultaneously.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

19-29

Module 7 Entering Data in Planning Lesson 19 Entering Data

Calculating Data in Data Forms Edit > Launch Rules (associated with data form)

Tools > Business Rules

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculating Data in Data Forms

e d a

c A

After you enter data in data forms, new totals need to be calculated for parent members. By default, two calculation scripts are associated with data forms—Calculate Data Form and Calculate Currencies calculation scripts. In addition to these two default calculation scripts, you can launch any business rule to which you have access. You can associate user-defined business rules with a data form. The following points describe how values are subtotaled and totalled in data forms: • Dimension member subtotals are calculated based on factors such as the hierarchies and logic of the Essbase outline and the member properties.

e l c

• When data is saved, Essbase automatically calculates members that are set to be calculated dynamically. Parent members that are not set to be calculated dynamically are not updated.

a r O 19-30

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data • For calculated parent members on a data form that are not set to be calculated dynamically, you need to run the Calculate Form calculation script. All subtotals in the data form are recalculated based on their member’s aggregation properties and the form’s design and layout. • Calculations are based on stored values, which are not necessarily the same as the displayed values. For example, the values that you see on the form might be based on scaling or precision settings.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

19-31

Module 7 Entering Data in Planning Lesson 19 Entering Data

Calculate Data Form Calculation Script Data Saved Before Parent Member Not Updated

After Parent Member Updated

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculate Data Form Calculation Script

e d a

c A

Launching the Calculate Data Form calculation script from Planning requests that an Essbase calculation script calculate new totals for just the members displayed on the data form. For example, if Northern Europe and its children Germany and Nordics are on a data form, when you save the data and launch the Calculate Data Form calculation script, a new total is displayed for Northern Europe. Since Europe, the parent of Northern Europe, is not on the data form, a new total for Europe is not calculated The Calculate Data Form calculation script can be set to automatically run when you save data. NOTE

e l c

If you have read but not write access to some members, subtotals correctly include the members’ values even if the members are read-only.

a r O 19-32

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Calculate Currencies Calculation Script Data Saved Before Reporting Currencies Not Converted

After Reporting Currencies Converted

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculate Currencies Calculation Script

e d a

c A

If the data form includes base and reporting currencies, you need to run the Calculate Currencies calculation script to convert base currency values to reporting currency values. Launching the Calculate Currencies calculation script from Planning requests that Essbase run a calculation script to convert base currency values to reporting currencies only for members displayed on the form. For example, if the reporting currencies USD and EUR are on a data form, when you save the data and launch the Calculate Currencies calculation script, the converted values for USD and EUR are calculated. If you also have JPY defined as a reporting currency, its values are not calculated because it is not on the form.

e l c

The Calculate Currencies calculation script can be set to automatically run when you save data.

a r O

Planning: Create and Manage Applications

19-33

Module 7 Entering Data in Planning Lesson 19 Entering Data

Business Rules

Price per New Computer

X

Headcount of New Employees

=

New Computer Expense

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Business Rules

e d a

c A

If you need to allocate or calculate values based on drivers or assumptions, you can set up business rules. You must have access rights to the business rule to be able to launch it. You can launch business rules by selecting Tools > Business Rules if you are in Advanced Mode. If you are in Basic Mode, you have access to business rules only if they are defined in your task list. Business rules can also be associated with data forms. To launch business rules associated with a data form, select Edit > Launch Rules. Business rules associated with data forms can be set to automatically run when you save data. You can also launch business rules associated with a data form by clicking on the business rules listed in the view pane.

e l c

NOTE

ra

Creating business rules is covered in detail in a subsequent lesson.

O

19-34

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Entering Data with Smart Lists ƒ Customer_Service_Class uses a smart list

ƒ Network Sales, Chip Sales, and Computer Sales use data values

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Entering Data with Smart Lists

e d a

c A

Smart lists are custom drop-down lists that you can access from data form cells. For cells whose members are associated with smart lists, data cannot be entered by typing a value. Instead, you select a value from a drop-down list. After you click in a cell that is associated with a smart list, you can click the arrow to expand the smart list. You can then select one of the smart list options as the value for the cell. After setting up smart lists and associating them with data forms, you can enter data on data forms by selecting from a drop-down menu. Remember that if you use smart lists to choose values from a drop-down list for certain data cells, no data values can be keyed into those cells.

e l c

a r O

Planning: Create and Manage Applications

19-35

Module 7 Entering Data in Planning Lesson 19 Entering Data

Navigating Data Forms with Menus 1. Add Headcount (Account 6000) 2. Enter T&E Rate (Account 6010) 3. Enter Software Rate (Account 6020)

4 5

4. Right-click on the Account column 5. Click Headcount business rule to 1 calculate accounts 2 3 5240 and 5350

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Navigating Data Forms with Menus

e d a

c A

After creating a menu and associating the menu with a data form, you can use the menu by right-clicking on the data form. If you specified a required dimension for your menu item, you can right-click in the area on the data form that contains that dimension. For example, if you select Account as the required dimension, then the menu is available when you click on Account members on the data form. Selecting none as the required dimension makes the menu available when you right-click in the data form.

e l c

a r O 19-36

Planning: Create and Manage Applications

Module 7 Entering Data in Planning Lesson 19 Entering Data

Summary In this lesson, you should have learned to: • Submit data in data forms • Adjust and annotate plan data • Calculate data in a data form • Enter data with smart lists • Navigate data forms with menus

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

19-37

Module 7 Entering Data in Planning Lesson 19 Entering Data

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 19-38

Planning: Create and Manage Applications

L E S S O N

2 0

Entering Data in Smart View

20

Objectives At the end of this lesson, you should be able to: • Describe Smart View • Enter, adjust, calculate, and analyze Planning data using Smart View • Work with Planning data

y m

e d a

a r O

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Smart View Overview

Planning

Financial Management

Essbase

Hyperion System 9 Applications+

Interactive Reporting Production Reporting Financial Reporting Web Analysis

Hyperion System 9 BI+

y m

e d a

Smart View Client Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Smart View Overview

c A

You can use Smart View to enter and analyze data from a single Excel interface. Smart View provides integration with Microsoft Office not only for Planning but also for Financial Management, Essbase, Web Analysis, Financial Reporting, Interactive Reporting, and Production Reporting. Tasks that previously were repeated across products are now performed only once. The use of a single interface enables you to utilize multiple products simultaneously. Tight integration of Smart View enables you to perform the following tasks: • Import content into the Microsoft products Excel, Word, PowerPoint, and Outlook • Utilize Office smart tags to add single data values and import reports

e l c

• Distribute and share Office documents by logging on only once to the data source

a r O

• Expose functions for Financial Management and Essbase content in Word, PowerPoint, and Outlook

20-2

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Integrating Smart View with Office Excel:

ƒ Data-entry forms ƒ Ad hoc analysis ƒ Functions ƒ BI+ content Word, PowerPoint, and Outlook:

ƒ Functions ƒ BI+ content

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Integrating Smart View with Office

e d a

c A

You can use Smart View to import BI+ content from Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis into Excel, Word, or PowerPoint. BI+ content can consist of reports, dashboards, and charts from the following products: • From Financial Reporting and Web Analysis, you can import reports. • From Interactive Reporting, you can import charts, dashboards, and reports (first page only). • From Production Reporting, you can import reports. Importing charts is not supported in Release 9.0.

e l c

a r O

Planning: Create and Manage Applications

20-3

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Smart View Architecture Smart View Client Data Source

Connection

Data Model

Client Tier

XML HTTP(s) Analytic Provider Servic e

Planning Provider

Financial Management Provider

Web Tier

Java API

Planning Application Server

Financial Management Application Server

Application Tier

Infrastructure

TCPIP / DCOM

Essbase

RDBMS

Data Tier

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Smart View Architecture

y m

e d a

c A

Smart View incorporates powerful architectural features to handle a wide range of analytic applications across large multiple-user environments. The slide provides a highlevel view of the integrated information flow between source data and the Smart View client. The slide shows that Planning and Financial Management have their own Web servers built into the application tier. Essbase does not have its own application server. As a result, Essbase requires a separate installation for Smart View Provider.

e l c

a r O 20-4

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Establishing Data Source Connections 1

2

y m

3

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Establishing Data Source Connections

e d a

c A

Before you can analyze data using Smart View, you must establish connections to your data sources. To manage your data source connections, use Connection Manager. You can add, delete, and modify connections per Excel instance. The connections managed by Connection Manager have no relationship to worksheets. You can establish multiple connections per Excel instance. After you add data sources in Connection Manager and they are displayed, you can use Connection Manager to connect to the data sources. You can add data sources for Planning, Financial Management, Essbase, Financial Reporting, Web Analysis, Interactive Reporting, and Production Reporting. You can connect to a data source directly, if you know the URL, or you can use Shared Services, which displays a list of providers to which you have access.

e l c

a r O

Planning: Create and Manage Applications

20-5

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View You can see whether a data source is connected or disconnected by viewing the icon next to the data source name in Connection Manager. If you try to connect to a data source that is disconnected, you are prompted to log on. If you are authenticated by external authentication, you are not prompted to log on. To add a data source connection: 1. In Office, select Hyperion > Connection Manager. The Connection Manager dialog box is displayed. 2. Click Add, and select URL Provider. The Add Data Source dialog box is displayed. 3. Perform the following actions: a. From the Provider drop-down list, select Hyperion Provider. b. From the Location drop-down list, select the Smart View provider URL. Alternatively, enter the URL in the list, using the following format:

y m

Analytic Services - http(s)://:/aps/SmartView

e d a

Planning - http(s)://:/HyperionPlanning/SmartView NOTE

c A

The default URL is http://localhost:13080/aps/SmartView.

e l c a r O ly & On l a e n r s e t U n I

c. Optional: Select Create as default connection to make this connection your default database connection. d. Click Next.

The Connect to Data Source dialog box is displayed.

e l c

a r O 20-6

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Establishing Data Source Connections (Cont.) 4

5

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Establishing Data Source Connections (Cont.)

e d a

c A

4. Enter your user name and password, and click Connect.

The Select Database or Repository dialog box is displayed. 5. Select a database from the list, and click Next.

The Add a Connection Name dialog box is displayed.

6. Enter a name and description for the connection, and click Finish. The connection is now available for selection in Connection Manager.

e l c

a r O

Planning: Create and Manage Applications

20-7

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Planning and Smart View ƒ Open Planning data forms in Excel ƒ Work online or offline — Use Planning data forms even when disconnected from the Planning server — Synchronize data back to the Planning server with validity checks

ƒ View instructions ƒ Adjust data ƒ Enter cell text ƒ Lock and spread values to base periods ƒ Enter supporting detail ƒ Calculate data

y m

ƒ Enter and preserve formulas

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Planning and Smart View

e d a

c A

You can work with Planning features when using Smart View. You can open Planning data forms in Excel, and you can work with online data forms while connected to the Planning server or offline data forms for additional flexibility. When you use data forms with Smart View, you have the same functionality as you have with data forms in Planning. You can view form instructions, adjust data, manipulate data by using ad hoc adjustments, lock and spread values to base periods, enter supporting detail and cell text, and launch business rules. The Planning server performs validity checks involving user security, metadata access, and form definition changes in order to synchronize data. The server then saves only incremental changes to the cells that were changed or modified after the data form was opened in Excel.

e l c

a r O 20-8

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Opening Data Forms in Smart View To open a Planning data form in Smart View, select Hyperion > Forms > Select Form

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Opening Data Forms in Smart View

e d a

c A

After connecting to a Planning data source, you can select a data form to work within Excel to enter and adjust data using Smart View. Many functions that you use during data entry in Planning are also available when you work with data forms in Smart View. You have access to the same data forms that you have access to in Planning.

e l c

a r O

Planning: Create and Manage Applications

20-9

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Navigating Data Forms in Smart View

Toolbar Page List

Point of View Column Headings Data Input Cells Cells with Supporting Detail

Row Headings

y m

Parent Member

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Navigating Data Forms in Smart View

e d a

c A

After you open a data form in Smart View, you can use the arrow keys to move forward, backward, up, or down. Press Tab to move to the next cell in a row. Press Shift+Tab to move to the previous cell in the row. Press Enter to move to the next cell in a column and Shift+Enter to move to the previous cell in the column. If you want to work with a specific slice of data, you can change the page selections and then click Go in the same manner as you would in Planning. Functions are available from the Hyperion menu, and there are shortcuts on the Smart View toolbar.

e l c

a r O 20-10

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Entering Data in Smart View Using Data Forms ƒ Utilize full Excel functionality. ƒ Set up customized areas of the spreadsheet. ƒ Add or modify data values. ƒ Spread data values. ƒ Adjust, copy, and paste data values. ƒ Add or view cell text and supporting detail.

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Entering Data in Smart View Using Data Forms

e d a

c A

You can utilize the full functionality of Excel with Planning data forms both online and offline when you work in Smart View. You can use Excel functionality to view data and text, create formulas, and format data. You cannot modify the structure of a Planning data form, but you can set up usermodified areas on a spreadsheet. This customization is not lost when you refresh the data form or when you open a new Planning data form in Excel. You can define and save numeric analyses and calculations for the data in a Planning data form. In other words, you have greater analytic capability on the fly, especially when data forms are offline.

e l c

a r O

Planning: Create and Manage Applications

20-11

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View Entering Data You can add data values by entering them in input cells. You can modify data values by typing over existing values. You can spread values from summary periods to base periods. The same rules apply when you spread values using Smart View as when you use Planning. You cannot use cell locking when you spread data in Smart View. Adjusting Data To adjust values in Smart View, you use the Adjust Data dialog box. Flexible data-entry operators are not available in Smart View. You can increase or decrease values by a percentage or numeric value as well as multiply or divide by a fixed value. In Smart View, you cannot adjust a data value if a cell is read-only or contains supporting detail. If you want to eliminate data from a cell that has a data value, replace the data value with #missing. Another way to replace a data value with #missing is to select the cells that you want to replace with #MISSING and press the Delete key. You can select a range of cells by using the same techniques that you use for data entry in Planning. You can also copy and paste data values in a grid. The rules for copying and pasting apply in all situations in grids except one: If you copy and paste a value with supporting detail, only the value—not the supporting detail—is copied and pasted.

y m

e d a

Annotating Plan Data You can add cell text to a cell at any level. You can also add supporting detail to build and communicate bottom-up values. You cannot add account annotations or annotate planning units from Smart View.

e l c a r O ly & On l a e n r s e t U n I

c A

Submitting Plan Data After entering and adjusting data, you need to save your changes in the Planning application. You do this by selecting Hyperion > Submit Data. Data values are updated directly to the Essbase database; supporting detail and cell text are updated directly to the Planning application relational database.

e l c

a r O 20-12

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Adding Formulas to Data Forms ƒ You can create formulas — inside or outside data form grids — on cells that contain cell text

ƒ You cannot create formulas — on read-only cells or cells that are locked — on cells that have supporting detail

ƒ Formulas are preserved even when you — refresh data forms — open saved .xls worksheets in the future — expand or collapse rows or columns

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Adding Formulas to Data Forms

e d a

c A

You can create Excel formulas to manipulate or analyze the data in data forms. You can save the formulas with the Excel workbook so that they are preserved when you use the workbook again. Formulas interact with other functionality in the following ways:

• You can spread data values using a formula in a summary parent cell. Spreading logic ignores formulas in child cells. For example, you could enter a formula in Q1 whose calculated value is spread over Jan, Feb, and March. However, if you enter a formula in Feb, that cell is ignored when the value for Q1 is spread. • If you move a referential formula, its cell references are updated to reflect its new location.

e l c

a r O

• If you use the Suppress #Missing Rows feature on a cell that has a referential formula, the cell references are not updated; the cell relationship is absolute, not relative.

Planning: Create and Manage Applications

20-13

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View If you create formulas in a data form, you are prompted to save the workbook as an .xls file with the new formulas under the following conditions: • You change the current page. • You take the data form offline. • You select a different data form. • You connect to a different data source. You lose temporary access to the formulas even if you save the formulas with the workbook when: • You change the current page, data form, or data source. • You take the data form offline.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 20-14

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Calculating Data in Smart View Hyperion > Calculation Options > Rules on Form

y m

e d a

Hyperion > Calculation Options > Business Rules Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Calculating Data in Smart View

c A

After entering data in a data form, you need to calculate new totals for parent members. You have the same data calculations options available to you in Smart View as you have during data entry in Planning. You can launch business rules and calculation scripts that recalculate data in Essbase. The data form in Excel is updated with the new data. You see the calculation scripts that you have access to listed by plan type. If a runtime prompt is part of a business rule, you are prompted to enter information. After the business rule is executed, the values in the Essbase database reflect the results of the calculation.

e l c

a r O

Planning: Create and Manage Applications

20-15

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Offline Planning Overview ƒ Offline Planning - work with data while not connected to the Planning application ƒ Work with Offline MyAnalytics cube ƒ Robust support for Web-based Planning functionality, including offline calculations and business rules

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Offline Planning Overview

e d a

c A

You can work with Planning data forms from remote locations when you are not connected to a Planning server. You can disconnect from the Planning server and work offline and still be able to use comparable online functionality. Working offline, you can enter and save data to the Planning server. For example, you can take data forms offline, enter and adjust data, view instructions, add supporting detail, run business rules, and create formulas to manipulate data. Working offline allows you to take a Planning data form in Excel and establish an impromptu local connection to a data source without being connected to the Planning server. Thus, you can continue to work on plan data and perform what-if scenarios when you do not have access to the Planning server. When you take a data form offline, the Planning server flags the data form status as offline. Data forms associated with a connection are saved locally on your hard drive. By synchronizing the locally saved data with the server, you ensure that the data form uses the most recent information.

e l c

a r O 20-16

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Taking Data Forms Offline

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Taking Data Forms Offline

e d a

c A

You use the Take Offline Wizard to take data forms offline. To take data forms offline:

1. Select Hyperion > Forms > Take Offline.

The Take Offline Wizard is launched.

2. Select the data forms to take offline, and click Next.

3. Select the dimensions and members to take offline.

e l c

The dimensions and members are those displayed in the Page drop-down lists of the forms you take offline.

a r O

Planning: Create and Manage Applications

20-17

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View 4. Create an offline connection, giving it a unique name, and click Finish. NOTE

To take a data form or group of data forms offline, you must select them and give them an offline connection name. You can select the offline connection name over multiple Excel sessions. The Download Status window displays the names of the outline, forms, dimensions, and members that are being downloaded for the offline connection. When the download process is complete, the message “Forms are successfully downloaded,” is displayed. 5. Click OK. 6. Close Excel.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 20-18

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Working with Planning Offline

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Working with Planning Offline

e d a

c A

You can work within Excel using the offline connection that you created. Most client-side capabilities, such as viewing form instructions, adjusting data, entering cell text, and adding supporting detail, remain available when you work offline. There are some differences in the capabilities for performing some tasks. For example, to add supporting detail, you can select a range of contiguous cells in a row or column if you are working online. (You cannot select a section of cells that include a combination of rows and columns.) However, in offline mode, to add supporting detail, you can select cells only on a cell-by-cell basis. To work with Planning offline:

e l c

1. Launch Excel.

a r O

2. Select Hyperion > Connection Manager, and select the offline connection.

Planning: Create and Manage Applications

20-19

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View 3. Select the data forms and members with which you want to work. 4. Select Hyperion > Submit Data to save the changed data to your computer. NOTE

Saving data forms using an offline connection saves the changes locally to your computer. If you also save the Excel workbook, you save only the data at the currently selected dimension member combination. You can save data forms in the local data source when you work offline. You have the option of saving a single worksheet or multiple worksheets when you work offline. Whether you are working offline or online, it is recommended that you submit data to the data source so that the server is updated with the latest data from the worksheet. The following rules apply when data is submitted: • Dimensions must be displayed in the axis in which they were displayed before the data was synchronized. This stipulation is true for all axes (rows, columns, pages, and points of view).

y m

• Pages must be displayed in the order in which they were displayed when the form was loaded.

e d a

• The order of the dimensions in the rows or columns can be changed. NOTE

c A

If some submitted cells are no longer on the data form, only the cells to which you have write access and that exist on the new data form definition are saved.

e l c

e l c a r O ly & On l a e n r s e t U n I

a r O 20-20

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Synchronizing Data to the Server

y m

Copyright © 2007, Oracle. All rights reserved.

e l c a r O ly & On l a e n r s e t U n I

Synchronizing Data to the Server

e d a

c A

You can save changed data to the Planning server by synchronizing your data. When you synchronize your data, you can synchronize at the workbook level or at the worksheet level. Synchronization is important because updated data is sent back to the server so that the Planning application reflects the work performed remotely. To synchronize data to the ser ver:

1. Use Connection Manager to connect to the same offline connection. 2. Select Hyperion > Forms > Sync Back To Server to save the changed data to the Planning server.

e l c

a r O

The Sync Back Wizard dialog box is displayed.

3. Log on to the server by typing your login ID and password, and click Next.

Planning: Create and Manage Applications

20-21

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View 4. Select the data forms whose data you want to save to the Planning server, and click Next. 5. Select the page members to synchronize back to the server, and click Next. 6. Optional: Select to delete offline data and application after synchronization, and click Finish. A message, “Sync back to server was successful,” confirms that your changed data was saved to the Planning application. NOTE

If someone else changed data for the same cells, only the most recent data is saved. 7. Click Done.

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 20-22

Planning: Create and Manage Applications

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

Summary In this lesson, you should have learned to: • Describe Smart View • Enter, adjust, calculate, and analyze Planning data using Smart View • Work with Planning data

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O

Planning: Create and Manage Applications

20-23

Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data in Smart View

y m

e d a

e l c

e l c a r O ly & On l a e n r s e t U n I

c A

a r O 20-24

Planning: Create and Manage Applications