Hyperion Planning 9.3 Student - Guide - 1

Hyperion Planning 9.
3: Create and Manage Applications

Volume I Student Guide
D50751GC10 Edition 1.0 June 2007 D50934
Copyright 2007, Oracle. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Table of Contents
Preface
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Course Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Course Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Student Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Student Workbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Module 1: Getting Started Lesson 1: Planning Overview

Hyperion Business Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Hyperion System 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Hyperion System 9 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Hyperion System 9 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Additional Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Hyperion System 9 Planning Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11 Client Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11 Application Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Database Tier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Hyperion System 9 Planning User Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 Hyperion System 9 BPM Architect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Hyperion System 9 Planning Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 Planning and Analytic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 Planning Repository and Analytic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Analytic Services TerminologyHierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25 Analytic Services TerminologyFamilies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26 Analytic Services TerminologyGenerations and Levels . . . . . . . . . . . . . . . . . . 1-27
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 iv Planning: Create and Manage Applications
Table of Contents
Lesson 4: Managing Dimensions with BPM Architect

About Dimension Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Master View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Application View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 BPM Architect Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Adding Dimensions to Master View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Creating Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 Modifying Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Property Value Inheritance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11 Managing Property Value Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Creating Alternate Rollups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 Managing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 Moving Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 Deleting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15 Inserting Members Using Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 Finding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18 Creating Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19 Adding Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21 Number Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21 Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22 Triangulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22 Reporting Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22 Creating Associations Between Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Lesson 5: Setting Up the Period, Scenario, and Version Dimensions

Time Periods Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Period and Year Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Choosing How Data Is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Scenario Dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Creating Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Enable Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Exchange Rate Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Use Beginning Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Deleting Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Planning: Create and Manage Applications
Table of Contents
Version Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Creating Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
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
Lesson 7: Setting Up the Account Dimension

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

User-Defined Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Attributes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Viewing, Aggregating, and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5 Creating Attribute Crosstab Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5 Creating Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Examples of Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8 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
vi
Table of Contents
Associating Smart Lists with Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22 Setting Data Forms to Use Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Module 3: Loading Metadata Lesson 9: Loading Metadata from a File

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

Creating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Dimension Library Panes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4 Adding Dimensions to Application Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 Excluding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7 Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8 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
vii
Table of Contents
Lesson 11: Deploying Applications

Deploying Applications Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2 Deployment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3 Validating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4 Comparing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6 Choosing Performance Settings for Optimal Performance . . . . . . . . . . . . . . . . . . . . .11-8 Dimension Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10 Deploying Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-12 Creating Analytic Services Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-14 Reviewing Planning Outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-16 Analytic Services Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-17 Redeploying Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18
Lesson 12: Setting Up Exchange Rates

Currencies and Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2 Exchange Rates Tables Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3 Creating Exchange Rate Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4 Entering Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6 Types of Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6 Calculating Implied Rates Through Triangulation . . . . . . . . . . . . . . . . . . . . . . . . 12-8 Determining the Calculation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 Exchange Rates and the HSP_Rates Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10 Generating Currency Conversion Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . .12-11 Copy Rates Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12 Currency Conversion Calculation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12 Calculate Currencies Business Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Module 4: Loading Data and Calculating the Database Lesson 13: Loading and Calculating Data Overview
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 viii Planning: Create and Manage Applications
Table of Contents
Calculations and Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12 Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
Lesson 14: Loading Data

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

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

Assigning Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2 Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3 Inheritance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5 Precedence and Inheritance of Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7 Reporting on Access Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9 Importing Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10 Creating the Secfile.txt File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-11 Importing Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14 Creating Security Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16
Module 6: Designing Data Forms Lesson 17: Creating Data Forms and Folders
Data Forms and Folders Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2 Data Form Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3 Creating Folder Structures for Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5 Data Form Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6 Considerations for Setting up Data Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7 Setting Data Form Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9 Setting Row and Column Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10 Selecting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14 Creating Substitution and User Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16 Creating Asymmetric Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17 Setting Page and Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18 Setting Options on the Other Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19 Identifying Missing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21 Selecting Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22 Previewing Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24 Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25 Creating Composite Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26 Selecting Business Rules on Composite Data Forms . . . . . . . . . . . . . . . . . . . . 17-27 Printing Data Form Definition Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28 Assigning Access Rights to Data Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
Table of Contents
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-21 Setting Individual User Variable Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
Module 7: Entering Data in Hyperion System 9 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 Saving and Refreshing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14 Spreading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15 Time Balance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17 Spreading Data Using Grid Spreader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19 Spreading Data Using Mass Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20 Adjusting and Annotating Plan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21
xi
Table of Contents
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-22 19-23 19-24 19-25 19-26 19-27 19-29 19-31 19-32 19-33 19-34 19-35
Lesson 20: Entering Data Using 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
Module 8: Adding Business Rules Lesson 21: Creating Business Rules

Business Rules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Rules Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites for Accessing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigating Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components of Enterprise View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2 21-4 21-5 21-6 21-6
xii
Table of Contents
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 Analytic Administration Services Console . . . 21-22 Launching Business Rules from Planning Data Forms. . . . . . . . . . . . . . . . . . 21-23 Launching Business Rules from Planning Tools Menu . . . . . . . . . . . . . . . . . . 21-24 Printing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-25
Lesson 22: Building Runtime Prompts for Business Rules

Runtime Prompts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2 Adding Runtime Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4 Setting Up Runtime Prompts as Global Variables . . . . . . . . . . . . . . . . . . . . . . . . 22-5 Applying Runtime Prompts as Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . 22-8 Setting Up Runtime Prompts as Local Variables . . . . . . . . . . . . . . . . . . . . . . . . . 22-9 Specifying Limits for Runtime Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
Lesson 23: Adding Formulas to Business Rules

Business Rules Formula Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2 Building Formulas for Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3 Components for Pro-Rata Ratio Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4 Setting Up Pro-Rata Ratio Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-5 Setting Up Units-Rates Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-8 Setting Up Variable Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9 Setting Up Custom Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-10 Specifying Data Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-11 Managing Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-12
xiii
Table of Contents
Module 9: Managing the Planning Process Lesson 24: Managing the Approval Process
Process Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2 Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3 Planning Units and Process States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4 Reviewer Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-6 Impact of Entity Hierarchy on the Review Process . . . . . . . . . . . . . . . . . . . . . . . 24-8 Managing the Review Cycle for Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-10 Starting or Excluding Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-11 Checking the Status of Planning Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-13 Viewing the Details of Planning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-14 Printing Planning Unit Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-17 Copying Data Between Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-19 Copying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-21
Lesson 25: Creating Task Lists

Task Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2 Navigating Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4 Navigating Task Lists in Basic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5 Navigating Task Lists in Advanced Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-8 Task List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-11 Working with Task List Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-12 Building Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-14 Adding Tasks to Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-16 Setting Up Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-17 Setting Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-19 Assigning Access to Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-21 Validating Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-22 Reporting on Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-23
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
xiv
Table of Contents
Financial Reporting Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5 Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7 Users, Groups, and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-8 Data Sources for Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-10 Financial Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-12 Working with Financial Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-13 Financial Reporting Studio Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-14 Viewing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-16 Opening Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-18 Report Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-19 Changing the User Point of View Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-20 Previewing and Printing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-21
Lesson 27: Navigating Reports in Workspace

Workspace Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-2 Workspace User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-4 Workspace Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-6 View Pane Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-7 Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-8 Setting General Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-8 Setting Authentication Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-9 Setting Explore Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-10 Setting Financial Reporting Studio Preferences . . . . . . . . . . . . . . . . . . . . . . . . .27-11 Setting Financial Reporting General Preferences . . . . . . . . . . . . . . . . . . . . . . . 27-12 Browsing the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-14 Searching for Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-16 Previewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-17 Changing the User Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-19 Previewing the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-21 Limiting User Point of View Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-22 Changing Page Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-26 Printing Reports and Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-27 Integrating Reports into Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . . . 27-28 Exporting Reports to Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-29 Exporting Reports to Word and PowerPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-31 Importing Reports to Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . . 27-33
xv
Table of Contents
Module 11: Appendices Appendix A: Sharing Data Using Data Synchronization

About Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Creating Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Creating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Specifying Source and Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6 Linking Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7 Setting Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8 Applying Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9 Inserting Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10 Validating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 Viewing Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12 Executing Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Appendix B: Working with Classic Application Administration

Classic Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 Processes in Creating Planning Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 Hyperion System 9 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 Analytic Services Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19 Reregistering Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20 Building Member Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21 Working with Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23 Creating Alias Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25 Smart Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27 Smart List Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-28 Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29 Associating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-31 Setting Up UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32 xvi Planning: Create and Manage Applications
Table of Contents
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-34 B-35 B-36 B-37 B-38 B-39 B-40 B-42 B-43 B-44
xvii
Table of Contents
xviii
Preface
Welcome to Hyperion System 9 Planning: Create and Manage Applications! Before you begin, please take a moment to review this section. The preface presents an overview of the following information: Course objectives Structure of the course Course materials used in the class Conventions used in the book
Course Objectives
After completing this course, you should be able to: Create Planning applications Load data into Planning applications Set up security for users, groups, and members Create data forms and enter data by using data forms Set and test business rules Review budget data by using process management Analyze planning results in Financial Reporting
Preface
Course Structure
Hyperion System 9 Planning: Create and Manage Applications is a 5-day, instructor-led training course consisting of lectures, demonstrations, and hands-on exercises. In this course, the instructor presents a topic conceptually by explaining its purpose, demonstrating how it works, and then guiding the students through the exercises. Demonstrations and hands-on exercises reinforce the concepts and skills introduced during lectures.
Course Materials
You use two books in classthe student guide and the student workbook. The instructor may also give you handouts.
Student Guide
The student guide is designed to be used by students and the instructor during lecture time. It has 11 modules: Module 1 describes an overview of Planning and navigating Workspace. Module 2 describes setting up dimensions and members. Module 3 describes importing dimension members using BPM Architect. Module 4 describes loading data and calculating the database. Module 5 describes setting up security. Module 6 describes designing data forms. Module 7 describes entering data in Planning. Module 8 describes adding business rules. Module 9 describes managing the planning process. Module 10 describes analyzing data with Financial Reporting. Module 11 contains appendices which provide additional information about Planning not covered in this course. Each module contains lessons. Each lesson begins with a list of objectives followed by the presentation of slides and accompanying text. The lesson ends with a summary of the topics covered in the lesson.
xx
Preface
Student Workbook
The student workbook has two sectionsexercises and exercise solutions. Exercises A critical part of the learning process is the challenge of completing real tasks associated with each lesson. Each exercise is an opportunity to apply your new knowledge. Exercise Solutions The exercise solutions present the detailed steps to successfully complete the exercises.
Conventions
The following text conventions are used in this course book: Text to be typed, options to be selected, names of files and modules, and menu selections are displayed in bold type. Examples: - Select Clear Profile. - Click YES to clear the profile. When available, figures are used to identify an object or task. Example: Click Edit.
Keyboard shortcuts are displayed as follows: Ctrl+Enter Alerts are used to direct your attention to different types of information.
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.
xxi
Preface
xxii
M O D U L E
1
0
Getting Started
Overview
The aim of this module is to provide an overview of the product features, capabilities, components, and architecture of Hyperion System 9 Planning. You also learn about the relationship between Planning and Hyperion System 9 BI+ Analytic Services. You navigate the Hyperion System 9 Workspace and access Planning using Workspace. Lessons in this module include: Planning Overview Navigating Workspace
L E S S O N
1
1
Planning Overview
Objectives
At the end of this lesson, you should be able to: Describe the main features of Hyperion System 9 Planning Describe the product architecture of Planning Describe the relationship between Hyperion System 9 Planning and Hyperion System 9 BI+ Analytic Services
Module 1 Getting Started Lesson 1 Planning Overview
Hyperion Business Performance Management

Hyperion Business Performance Management (BPM) is a modular suite of packaged applications, built on a common Business Intelligence platform, covering the entire management cycle of goal setting, modeling, planning, monitoring, analysis, and reporting. By implementing Hyperions BPM system, you effectively link strategy to plans, monitor execution, and develop meaningful insights to support effective decision making, improved business performance, and compliance with corporate governance and regulatory requirements.
1-2
Hyperion System 9
Copyright 2007, Hyperion. All rights reserved.
Hyperion System 9
Hyperion System 9 is the first Business Performance Management system in the market. System 9 represents the convergence of disparate technologies and is a major milestone in the BPM category. System 9 provides an enterprise-class deployment foundation and a pervasive and personalized user experience. Hyperion System 9 enables companies to understand the past, monitor the present, and plan for future performance across the enterprise.
1-3
Hyperion System 9 Components

Hyperion System 9 Applications+ Financial Management Planning Strategic Finance Performance Scorecard Hyperion System 9 BI+ Interactive Reporting Enterprise Analytics Essbase Analytics Web Analysis Financial Reporting Production Reporting Enterprise Metrics Data Management Services Financial Data Quality Management Master Data Management Data Integration Management Hyperion System 9 Foundation Services Shared Services BPM Architect
Hyperion System 9 Workspace
Hyperion System 9 Components

As shown in the slide, Hyperion Applications are an integral part of System 9: Hyperion System 9 Financial Management: A product that offers world-class financial consolidation, reporting, and analysis and that uses advanced technology but is built to be owned and maintained by finance departments. Planning: A centralized, Web-based planning, budgeting, and forecasting solution that is optimized for enterprise-class deployments. Hyperion System 9 Strategic Finance: A strategic financial modeling application that gives corporate development, finance, and treasury executives real-time information on alternative strategies, allowing them to analyze, evaluate, and choose the highest value strategic path to deliver continuous performance improvement.
1-4
Module 1 Getting Started Lesson 1 Planning Overview Hyperion System 9 Performance Scorecard: An application that aligns and focuses your enterprise on business objectives, plans, and actions; empowers your employees with clearly defined performance measures for success; and enables continuous performance monitoring, improvement, and agility across your enterprise. BI+ stores, protects, and delivers information for a companys extended enterprise (employees, customers, suppliers, and partners). It enables you to analyze, transform, and report data; search for, retrieve, and use documents; run queries, execute and schedule jobs, and distribute logs. Hyperion System 9 Data Management ServicesA family of products for managing financial and operational data, metadata, master data, and financial data quality associated with Business Performance Management (BPM) deployments. Hyperion System 9 Foundation Services supports functions that are common to all components. Hyperion System 9 Applications+ and BI+ communicate and share data through Foundation Services. Hyperion System 9 components can connect to a variety of data sources and are accessed through a common interface called Hyperion System 9 Workspace. Workspace enables you to access and interact with Hyperion-authored content by using BI+ tools as well as third-party documents such as Microsoft Word and Excel files.
1-5
Hyperion System 9 Planning

Hyperion System 9 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 Hyperion System 9 Planning applications and other Hyperion products
Hyperion System 9 Planning

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 Analytic Services, 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.
1-6
Product Components
Hyperion System 9 Planning Hyperion System 9 BI+ Analytic Services Hyperion System 9 BI+ Analytic Administration Services Hyperion System 9 BI+ Workspace Hyperion System 9 Business Rules Hyperion System 9 Smart View Hyperion System 9 BI+ Financial Reporting Hyperion System 9 Shared Services
Product Components
You use the Planning Web interface to deploy applications to planning organizations. To extend the power and flexibility of Planning, you use it with other Hyperion products.
Product Analytic Services Hyperion System 9 BI+ Analytic Administration Services Description Enables you to store Planning application data (Planning runs on top of Analytic Services.) Interfaces to Analytic Services Server, using Analytic Administration Services Console, and enables you to design, develop, maintain, and manage multiple Analytic Services applications and databases. Enables you to navigate and manage Hyperion Planning within Workspace Enables you to use a graphical user interface to create calculation scripts
Workspace Hyperion System 9 Business Rules
1-7

Product Hyperion System 9 Smart View Description 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 Enables you to create reports and charts for Web or print for analysis and distribution of budget plans 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
Hyperion System 9 BI+ Financial Reporting Hyperion System 9 Shared Services
1-8
Additional Product Components

Hyperion System 9 Workforce Planning Hyperion System 9 Capital Expense Planning Hyperion System 9 Performance Scorecard Hyperion System 9 Strategic Finance Hyperion System 9 Financial Management Hyperion System 9 BI+ Web Analysis
Business Performance Management Solutions Hyperion System 9 Applications

Dashboarding and Scorecarding Modeling Planning, Budgeting, and Forecasting Consolidation and Reporting
Additional Product Components

Several complementary Hyperion products are integrated with Hyperion System 9 Planning, completing the Hyperion Business Performance Management solution.
Product Hyperion System 9 Workforce Planning Hyperion System 9 Capital Expense Planning Performance Scorecard Strategic Finance Description Enables you to handle workforce, salary, and compensation planning Enables you to plan for new asset purchases and existing asset actions Enables you to communicate strategy, set goals, and measure and monitor business performance Enables you to easily test financial models, create contingency plans, and form alternative strategies
1-9

Product Financial Management Description Enables you to consolidate results, reduce the cost of regulatory reporting compliance, and gain important insights into performance Enables you to transform data into insightful information through easy-to-use, highly graphical displays and robust analytics
Hyperion System 9 BI+ Web Analysis
1-10
Hyperion System 9 Planning Architecture

Client
Administrator Client Workspace Smart View Client
Application
Hyperion System 9 BI+ Financial Reporting Server Hyperion System 9 Shared Services and License Server, Java Application Server for Hyperion System 9 Planning, BPM Architect, Analytic Administration Services Hyperion System 9 BPM Architect Dimension Server Web Server
Database
BPM Architect RDBMS Planning RDBMS Hyperion System 9 BI+ Analytic Services
Hyperion System 9 Planning Architecture

Planning is a multitier application that combines the advantages of Analytic Services (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. In the client tier, you can enter data through spreadsheets by using Smart View.
1-11
Application Tier
The application tier consists primarily of the following servers: Hyperion System 9 BI+ Financial Reporting server Java Application server (for Planning, Hyperion System 9 BPM Architect, and Analytic Administration Services) Hyperion System 9 BPM Architect Dimension Server Hyperion System 9 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.
Database Tier
The database tier consists of a third-party relational database management system (RDBMS) and Analytic Services. The relational database is used primarily to store the applications definition. The following information is stored in the RDBMS: Application framework* Dimensions, dimension members, and properties* Exchange rates* Member access (security filters)* Data form design definitions Planning units Annotations (planning unit, account, and cell text) Supporting details Process management workflow status
NOTE
Items with an asterisk (*) are updated to the Analytic Services databases during application refreshes.
1-12
Hyperion System 9 Planning User Roles

Planning Roles Provisioning Manager Administrator Manage Models Interactive User Planner View User Offline User Mass Allocation
Hyperion System 9 Planning User Roles

Planning meets the needs of multiple users within an enterprise-wide budgeting cycle. You can set up users with several different types of user profiles to reflect what access is needed. The following global Shared Services roles are also used in Planning: Application Creator Creates applications. This is a Hyperion System 9 BPM Architect role. Dimension Editor Creates profiles and imports dimensions. This is an BPM Architect role. Create Integrations Creates Shared Services data integrations (the process of moving data between applications) using a wizard. Run Integrations Views and runs Shared Services data integrations.
1-13
Module 1 Getting Started Lesson 1 Planning Overview The following table summarizes Planning user profiles.
User Profile Provisioning Manager Administrator Description Users who are assigned the Provisioning Manager role can provision users and groups to applications. 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. Users assigned the Manage Models role can export and import Shared Services models. 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. 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 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. 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.
Manage Models Interactive User
Planner
View User
Offline User
Mass Allocation
1-14
Hyperion System 9 BPM Architect

Create Metadata
Maintain a centralized collection of metadata for Hyperion products and add metadata to applications by using the BPMA interface Load metadata by using flat files or metadata loaded and stored in interface tables Build metadata by entering metadata directly into BPM 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
Hyperion System 9 BPM Architect

Business Performance Management Architect (BPM Architect) is a feature set in Planning. BPM Architect enables budget administrators to manage, create, and deploy Hyperion applications within one interface. Using the Data Synchronization feature in BMPA, 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.
1-15
Hyperion System 9 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
Hyperion System 9 Planning Interface

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.
1-16
Planning and Analytic Services
Hyperion System 9 BPM Architect Repository
Workspace Interface
Hyperion System 9 Planning Repository
Java Application Server
Hyperion System 9 BI+ Analytic Server

Planning and Analytic Services

Planning uses Analytic Services to store dimension hierarchies and consolidate data. When you deploy an application view, BPM Architect creates tables and appropriate values in your Planning relational database, creates an application and outline in Analytic Services 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 Analytic Services databases and security privileges for your application. The plan data that end users enter in a Planning application is stored in the Analytic Services databases created for the application. Prior to application deployment, BPM Architect stores the application data in its own BPMA relational database.
1-17
Planning Repository and Analytic Services

Planning Relational Database Security Metadata Foreign Exchange Rates Process Management Details Annotations/ Cell Text/ Supporting Details Task Lists Preferences Application Setup Data Forms User Variables Smart Lists
Analytic Services Security Metadata Foreign Exchange Rates
Data Business Rules Rule Files Currency Calculation Scripts Substitution Variables Smart Lists (numerically)
Planning Repository and Analytic Services

Dimensions and members are stored in the Analytic Services databases as well as the Planning repository. Data values are stored in Analytic Services. 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 Analytic Services databases, however, smart list information is stored numerically in Analytic Services.
1-18
Dimensions
Structural elements of an application that describe and hold data.
Account Entity Period
Dimensions
Dimensions are the structural elements of an application that describe and hold data. Examples of dimensions are Account, Entity, and Period. The elements that compose a dimension are called members. For example, California and Connecticut are members of the Entity dimension. The dimensions defined in a Planning application become the dimensions in the Analytic Services outlines and databases.
1-19
Dimension Hierarchies
Parent Child of GrossMargin; parent of Sales and OtherRevenues Descendants of GrossMargin
Dimension Hierarchies
Members of a dimension are arranged in hierarchies. Members in a hierarchy exist at different levels. Some members, siblings, are at same level and have relationships to other members of the hierarchy. Upper-level members are called parent members, and the members immediately below the parent members are referred to as their children. All members below a parent are referred to as descendants. The bottom-level members of a hierarchy are called 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.
1-20
Metadata
3689.00
Actual January Sales Manhattan Cola Metadata Data
January actual sales for cola in Manhattan are 3689.00.
Metadata
Metadata is defined as the structural elements of an application that describe and hold data. Examples of metadata are dimension names, member names, properties, and security. For the example shown on the slide, the circled dimension member labels are the metadata. The metadata describes what the data value represents. The value for Actual Sales for Cola in Manhattan is $3,689.00.
1-21
Dimensions and Data

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

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 Analytic Services. 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.
1-22
Multidimensional View of Information

Profit Total Exp. Margin Cogs East West Actual Budget Actual Budget TV Jan Feb Mar Qtr 1 Jan Feb Mar Qtr 1
VCR
Denver LA SF West February March Actual Budget Actual Budget Sales Camera TV VCR Audio Margin Camera TV VCR Audio
Multidimensional View of Information

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.
1-23
Drill-Down Process
Period Year Quarter Month Week
Entity Worldwide N America East New York
Account Profit Sales COGS Expenses
Customer All Customers Retail Sears Dept 10
Drill-Down Process
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).
1-24
Analytic Services TerminologyHierarchies
Outline
Dimensions Members
Analytic Services TerminologyHierarchies

Analytic Services 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 Outline Dimension Member Attribute Attribute dimension Definition Representation of the relationship among the members in the database 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
1-25
Analytic Services TerminologyFamilies

Dimension
Descendants of Year
Siblings
Year Qtr1 Qtr2 April
Year Qtr1 Qtr2 April

Parent of April Child of Qtr2
Ancestors of April
Analytic Services TerminologyFamilies

The following table summarizes the common familial terminology used in Analytic Services.
Familial Term Parent Child Sibling Ancestor Descendant Definition Member that has at least one child member immediately below it Member that has a parent immediately above it Child member at the same branch level as another child member with the same parent Any member in a branch above a member Any member below a parent
1-26
Analytic Services TerminologyGenerations and Levels

Gen 1 Gen 2 Gen 3 Gen 4 Level 3 Level 2 Level 1 Level 0 Leaf Node Level 0
Gen 3
Analytic Services TerminologyGenerations and Levels

The following table summarizes the common generation terminology used in Analytic Services.
Generation Term Generation Level Leaf node Definition Position within the hierarchy of a dimension, counted from top to bottom Position within the hierarchy of a dimension, counted from bottom to top Member that has no children
The term generation describes a members 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. Level describes a members 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
Summary
In this lesson, you should have learned to: Describe the main features of Hyperion System 9 Planning Describe the product architecture of Planning Describe the relationship between Hyperion System 9 Planning and Hyperion System 9 BI+ Analytic Services
1-28
L E S S O N
2
2
Navigating Workspace
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
Module 1 Getting Started Lesson 2 Navigating Workspace
System 9 Workspace
Workspace BI+ Planning
Manage Enterprise Financial Information
Hyperion Applications
Planning Output
System 9 Workspace
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. Centralized repository of key dimensional elements for Hyperion products Centralized console for controlling data flow between applications Audit logging and process controls 2-2 Planning: Create and Manage Applications
Workspace Overview
Manage applications View reports
Work with Planning
Workspace Overview
Workspace provides a single BPM 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 Using Hyperion System 9 BI+ Interactive Reporting, generate ad hoc relational queries, self-service reporting, and dashboards against ODBC data sources
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.
2-4
Launching Workspace
The password is case-sensitive.
Launching Workspace
You launch Workspace from a Web browser by using the following Uniform Resource Locator (URL) to display the logon page: http://<web server>:<port number>/workspace 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. 2. Enter your user name and password, and click Log On. The Workspace user interface is displayed.
2-5
Workspace User Interface

Navigate Menu Standard toolbar Module toolbar Standard toolbar
Menu bar
Process bar Buttons
Adjuster
Document tab bar
View pane
Content area
Workspace User Interface

Workspace includes the following elements:
Element Adjuster Buttons Content Area Document tab bar Menu bar Navigate menu Process bar Description Adjusts the size of the view pane and content area Navigates between view pane displays Displays active-module items, tasks, or files Displays information specific to the current module Provides commands that organize tasks and modules Provides access to Workspace modules Displays location of the current folder, item, or step
2-6

Element Standard toolbar View Pane Description Provides shortcuts for performing tasks Provides buttons that enable jumps between panels
2-7
Workspace Navigate Menu

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

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 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.)
2-8

Option Administer > Dimension Library Description 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 Analytic Services 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.) Create data mappings that can be reused Create flat file and staging area mappings to import data into Hyperion Applications Administer > Application Upgrade Administer > Job Console Upgrade from previous Planning and Financial Management releases View a summary of Dimension Library and Application activities, including imports, deployments, and data synchronizations Manage jobs and schedule batches and events for automated processing Update Interactive Reporting documents when database structures, database connections, or links to external data sources change
Schedule Impact Manager
2-9
Opening Applications
Opening Applications
In Planning, all data is processed within applications. An application is a related set of dimensions and dimension members that meet a specific set of analytical or reporting requirements. For example, you can have an application named Test used for development and a separate application named 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.
2-10
Navigating in Planning
Planning Menus Planning toolbar
View Pane
Open Application
Content Area
Navigating in Planning
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

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.
2-11
Module 1 Getting Started Lesson 2 Navigating Workspace File Menu The following table describes the commands under the File menu:
New Open Close Save Print Workflow Spreadsheet Export Preferences Add a new document, data form, alias table, dimension member, report, task list, or user variable Open a new document, application, or URL Close current, others, or all Save data inputted to data forms Print the current screen Manage the Planning process or copy versions Export a data form to a spreadsheet Set general, authentication, explore, Web Analysis, Financial Reporting, Interactive Reporting, or Production Reporting preferences Log off Planning Exit Workspace
Log Off Exit
Edit Menu The following table describes the commands under the Edit menu:
Adjust Grid Spread Mass Allocate Increase or decrease data values by a percentage Spread data values across multiple dimensions on the grid Choose from allocation options: proportional, 4-4-5, evenly split 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 Add Row Launch Rules Cut, Copy, or Paste data from one or more cells into one or more cells Add rows to a data form on-the-fly, only available if the data form was defined to allow rows to be added dynamically Launch a Business Rule from a data form
2-12

Annotate Planning Unit Cell Text Supporting Detail Initialize Workforce Add comments to a planning unit; the comment can be plain text, a URL, or paths to servers Add comments to a specific cell at any level in a data form Add detail that will aggregate the cell value in a data form 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. 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.
Initialize Capex
View Menu The following table describes the commands under the View menu:
View Pane Refresh Instructions Currency View Account Annotations Edit Account Annotations Basic Mode Task List Toggle the view for tasks between Basic Mode and Advanced Mode View task lists to which you have access Hide or show the View Pane Refresh the current view to reflect what is stored in the database View instructions for a data form, available only if the data form includes instructions Look up a currency code Enter, edit, or view comments for a specific account, entity, scenario, and version combination
Administration Menu The following table describes the commands under the Administration menu:
Manage Data Forms Manage Task Lists Manage Menus Manage User Variables Create, edit, move, delete, and assign access to data forms Create, edit, move, delete, and assign access to task lists Create and edit menus Set up variables that are assigned to data forms by specifying the variables value
2-13

Manage Properties Dimensions Copy Data Reporting Set and change access for dimensions, such as account, entity, scenario, version, and user-defined custom dimensions Copy data, including supporting details, from one planning unit to another 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 information about the Planning application and its usage Set Planning application-wide preferences Create Classic applications Delete Classic applications Register Classic applications with Shared Services Link tasks in task lists to application pages Manage metadata modules by performing version tracking, maintaining access control, and renaming and deleting models Use the Data Load Administration page to set up the data to load directly into an Analytic Services database through Planning Adapter Create and refresh Analytic Services databases with changes made to relational databases, such as with exchange rates updates Create currency conversion calculation scripts Create and set up exchange rate tables and exchange rates and delete exchange rate tables Create security filters for users
View Statistics Application Settings Create Application Delete Application Register Application Copy Document Link Manage Models Data Load Administration Manage Database
Manage Currency Conversion Manage Exchange Rates Manage Security Filters
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:
Personalize Links Show subscribed items and manage personal pages Manage links to other Hyperion System 9 products or URLs
2-14

Install Business Rules Broadcast Message Install Interactive Reporting Web Client and Smart View Launch business rules Create and send broadcast messages
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 New Document Description Create Workspace document Collect Reports in a book Batch Reports for Scheduling Open Document Home Explore Save Refresh Print Adjust Grid Spread Open Workspace documents Workspace startup page Display Workspace Folders in View Pane Save data input on data forms Refresh the data form with data stored in the database Print the current screen Increase or decrease values by a percentage Spread data across dimensions on the data form
2-15

Button Purpose Mass Allocate Cut, Copy, Paste Cell Text Supporting Detail Spreadsheet Export Task List Status Logoff Help Maximize content pane (on far right of navigation path) Description Run a Mass Allocate calculation Cut, Copy, or Paste values from one or more cells to one or more other cells on data forms Add comments to a specific cell at any level in data forms Add detail that aggregates the cell value in data forms Export data forms to a spreadsheet Open task lists if task lists have been assigned to you Check task lists status Log off the application Access help for the currently selected task or document Maximize or restore the content pane.
2-16
Basic and Advanced Modes

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

Some users roles in the budgeting and planning cycle may require that the user only 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.
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.
2-18
View Pane and Content Area

View Data Forms buttons
View Pane
Business Rules
Content Area
View Pane and Content Area

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.
2-19
Opening Data Forms

Select Folder
Data Forms
Opening Data Forms

Data forms are contained within the folders. After you select a folder, a list of data forms within the selected folder is displayed on the View pane 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.
2-20
Summary
In this lesson, you should have learned to: Describe the user interface components Access Planning through Workspace Navigate Planning
2-21
2-22
M O D U L E
2
2
Creating Application Structures
Overview
The aim of this module is to create dimensions and members for a Planning application. First, you identify required and user-defined dimensions. Next, you describe dense and sparse dimensions and basic concepts of data blocks. Finally, you create the dimensions and dimension members for the databases for your Planning application. Lessons in this module include: Creating Dimensions Overview Managing Dimensions with BPM Architect Setting Up the Period, Scenario, and Version Dimensions Setting Up the Entity Dimension Setting Up the Account Dimension Creating User-Defined Elements
L E S S O N
3
3
Creating Dimensions Overview
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 Describe data block creation Set up aggregation, data storage, and calculation options
Module 2 Lesson 3 Creating Dimensions Overview
Plan Types
Analytic Services 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
Plan Types
An Analytic Services 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.
3-2
Module 2 Creating Application Structures Lesson 3 Creating Dimensions Overview
Planning Dimensions
Analytic Services
Planning Repository
Planning Dimensions
Planning data is stored in Analytic Services databases. Data storage in Analytic Services is different from data storage in relational databases. Understanding how Analytic Services 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. 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. Planning: Create and Manage Applications 3-3
Required Dimensions
Six Required Dimensions* Period Year Scenario Version Entity Account Other Dimensions Alias Smart Lists
*multicurrency applications require two additional dimensions Currency HSP_Rates
Required Dimensions
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.
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.
3-4
Version allows for flexibility and iterative planning cycles. For example, your application could have two versions, Working and Final, for each scenario. You can also use versions to model possible outcomes based on different assumptions about interest rates, growth rates, and so on. For example, your application can have a Best Case and Worst Case version for each scenario.
Entity
The Entity dimension represents the flow of Planning information through your organization. You can establish an entity for each group or responsibility center that submits a budget plan. These units could be geographic regions, departments, or divisions, depending on your requirements.
Account
The Account dimension specifies the data to be collected from budget planners. You can establish accounts for all budgeted items to the necessary level of detail. Examples of accounts are Rent Expense and Cash on Hand.
NOTE
For dimension member names and alias names, you can include up to 80 characters, and you must make the name unique across all dimensions. You can include the characters %, &, $, #, (), *, ^, - and _ in the member and alias names. You cannot include \ / : ? < > | in the member or alias names.
Currency
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
3-5
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 Analytic Services.
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.
3-6
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.
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 BPM 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 BPM Architect.
3-7
Dense Dimensions
Dense Dimensions
Dense Dimensions
Multidimensional databases contain dense dimensions. A dense dimension is a dimension that contains a high percentage of occupied data values in each combination of dimensions. For example, when data exists for an entity, it typically exists for most or all accounts and time periods. Account and Period are typically dense dimensions.
3-8
Sparse Dimensions
Sparse Dimensions
Sparse Dimensions
Multidimensional databases also contain sparse dimensions. Sparse dimensions contain a low percentage of occupied data values in each combination of dimensions. Sparse dimensions have these characteristics: Data values are not smoothly and randomly distributed throughout the database. Data values do not exist for the majority of member combinations in the database. For example, if each entity sells only to a subset of customers, most combinations of entity and customer have no associated data. Entity and Customer are typically sparse dimensions.
3-9
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
Data Block Creation

Analytic Services 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.
3-10
Determining the Number of Data Blocks in a Database

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

Account Account1 Account2 Account3 Period Jan to Dec
Each block contains 36 cells = (3 Accounts * 12 Time Periods)
Determining the Number of Data Blocks in a Database

The dense and sparse settings for dimensions determine the structure of the data blocks and the number of data blocks in the database. The dense dimensions determine the data block structure. A data block always includes all stored members of all dense dimensions. By default, Account and Period are dense dimensions in Planning applications.
NOTE
If your application uses currencies, the dense dimension HSP_Rates stores exchange rates. The data in a data block is stored at the intersections formed by the members of the dense dimensions. For example, if the Account and Period dimensions are dense, the combination of one time period (January) and one account (Sales) equals one cell of data within a data block.
3-11
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 -> 2003 -> 1st Draft Corp -> Budget -> 2003 -> Final The dense dimensions determine the data block structure, and so each data block has 36 cells (3 accounts 12 time periods).
3-12
Creating Data Blocks and Retrieving Data

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

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, Analytic Services 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, Analytic Services retrieves the entire data block into memory. For example, if a report or calculation requests the value in the cell for Corp -> Budget ->2003 -> 1st Draft -> Account2 -> Feb, Analytic Services first loads the Corp -> Budget -> 2003 -> 1st Draft data block into memory and then retrieves the value from the Account2 -> Feb cell for this block.
3-13
Determining Data Structure and Performance of Data Blocks

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

The dense and sparse settings for dimensions determine data structure. The data structure can have a significant impact on data retrieval and calculation time. Although design considerations can vary significantly between applications, follow the general guidelines for performance. When you view or calculate data, you typically experience the best performance if the cells that need to be calculated or viewed are in the same data block.
3-14
Selecting Aggregation, Storage, and Calculation Options

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

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.
3-15
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 (-)
Selecting Aggregation Options

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

Use storage options to optimize performance and disk usage. Storage options
StoreData (default) DynamicCalcAndStore DynamicCalc ShareData NeverShare LabelOnly
Selecting Data Storage Options

You select from several storage and calculation options for dimension members to optimize performance and disk usage. The following table describes these options:
StoreData DynamicCalcAndStore DynamicCalc Share Data Stores data values of members. This is the default value for all members. Calculates the data value the first time the member is retrieved and then saves the value. Calculates the data values each time the member is retrieved. The value is not stored in the database. Allows two or more members in the same dimension to share data values.
3-17

NeverShare LabelOnly
Prohibits two or more members in the same dimension from sharing a data value. 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. DynamicCalc If a member is set to DynamicCalc, Analytic Services does not calculate its data value during regular database calculation; for example, when the CALC ALL function is executed, Analytic Services calculates the data value upon retrieval; a specific example of this is data being calculated when it is retrieved into a data form. Advantages of DynamicCalc: Reduction in the regular calculation time of the database because Analytic Services has fewer member combinations to calculate. Reduction in disk usage because Analytic Services 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.
3-18
Module 2 Creating Application Structures Lesson 3 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. 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 Head Count 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. 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 Analytic Services Smart View Provider. LabelOnly guidelines: You cannot designate level 0 members as LabelOnly. 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. Creating Dimensions Overview
3-19
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.
3-20
Calculating Data
Analytic Services calculates the outline in the following order: 1. Account dimension 2. Time dimension 3. Other dense dimensions in top-down order 4. Other sparse dimensions in top-down order 5. Members that are tagged as Two-Pass Calculations
1st Pass 2nd Pass
Level 0 Data
Calculated Data (Before Two-Pass)
Calculated Data (After Two-Pass)
Calculating Data
The calculation order in Analytic Services can affect the result of a calculation. Analytic Services 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 Analytic Services calculates the database, a second pass calculates members tagged Two-Pass Calculation.
3-21
Using Two-Pass Calculations

Before Two-Pass
9
After Two-Pass
9 9
9
9 9
Using Two-Pass Calculations

A good example of two-pass calculation is the calculation for the Margin Percent account for North America. That calculation depends on the aggregated value of the Gross Margin and Net Revenue accounts (Margin Percent = Gross Margin / Net Revenue). Since the Entity dimension is calculated after the Account dimension, the aggregated values are not available. To calculate Margin Percent correctly, Analytic Services 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.
3-22
Determining Performance Efficiency
Sparse Dimensions
Determining Performance Efficiency

In a data form in which there is only one member from each sparse dimension, Analytic Services 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.
3-23
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.
3-24
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
3-25
3-26
L E S S O N
Managing Dimensions with BPM Architect
Objectives
At the end of this lesson, you should be able to: Describe BPM Architect Navigate BPM Architect Create dimension members Manage dimensions Modify member properties Set up alias tables Add and modify currencies Create property associations
Module 2 Lesson 4 Managing Dimensions with BPM Architect
About Dimension Management
Master view pane
Application view pane
About Dimension Management

You can view, create, and manage dimensions from a central location named the Dimension Library (Navigate > Administer > Dimension Library). The Dimension Library has two types of viewsMaster 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.
4-2
Module 2 Creating Application Structures Lesson 4 Managing Dimensions with BPM Architect
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.
4-3
BPM 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
2. Create application views

Budgeting Application View Accounts EntityBudgeting PeriodsTrimester
Dimension Server FM Consol Application View Accounts EntityConsol PeriodsStandard
3. Deploy application views from Dimension Server to product application servers
Planning Application Server

Financial Management Application Server
BPM Architect Process

You manage dimensions and create Planning applications in BPM 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.
4-4
Adding Dimensions to Master View
Dimension class
Adding Dimensions to Master View

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. 3. Optional: Enter a description.
4-5
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.
4-6
Creating Members
Creating Members
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 - Select As Sibling to add a member at the same level as the selected member 4. In the New Member dialog box, enter a name. 5. Click OK.
4-7
Guidelines for Member Names

Member names cannot contain these characters:
Period (.) Plus sign (+) Minus sign (-) Asterisk (*) Slash (/) Number (#) Braces ({}) Comma (,) Semicolon (;) At (@) Quotations ()
Guidelines for Member Names

Member names can be up to 50 characters in length. Certain character cannot be used in member names for Planning applications.
4-8
Modifying Member Properties

Property category Save
Defined
Default
Modifying Member Properties

You can modify properties for each dimension member. When the dimension is created, it takes on a default set of properties and property values. Properties are organized into categories based on the Hyperion products for which they are valid.
Property Category Essbase Planning Consolidation System Statistical Application Essbase Analytics Planning Financial Management All applications All applications
4-9
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.
4-10
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
Descendants of United Kingdom inherit GBP for Currency property
Property Value Inheritance

Inheritance allows high-level members to share their properties values with lower points in the hierarchy. It allows new members to automatically obtain their property values from the appropriate ancestors. Proper use of inheritance enhances the referential integrity of your application and reduces maintenance requirements. BPM Architect determines a property value in the following order: 1. BPM 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, BPM Architect searches the ancestors of the member for a value. The first entered value that BPM 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. 3. If no ancestor has an entered value, the system default value for the property is used. Planning: Create and Manage Applications 4-11
Managing Property Value Inheritance
Managing Property Value Inheritance

BPM Architect provides the following options for managing inherited properties: To lock a property at the ancestor level so that the inherited value cannot be overridden by its descendant members, right-click the property and select Lock 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. 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.
4-12
Creating Alternate Rollups

EastSales and WestSales occur in alternate rollups
Entity [None] Geographical UnitedStates California Plant1 WestSales Connecticut EastSales Activity Entity [None] Geographical Activity SalesServices WestSales EastSales EmeaSales EmeaServices Manufacturing Development
Creating Alternate Rollups

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 Share Data. 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.
4-13
Managing Members
Managing Members
You can change the order in which a member is displayed under a parent or move a member to another parent. You can delete a member from a single hierarchy or from all hierarchies.
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. 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.
4-14
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.
4-15
Inserting Members Using Relationships
Inserting Members Using Relationships

You can insert a group of members into a hierarchy based on a member relationship. For example, you could insert all base members beneath a selected parent member into an alternate hierarchy. To inser t 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: 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.
4-16
Module 2 Creating Application Structures Lesson 4 Managing Dimensions with BPM Architect 3. In the Insert member dialog box, select a member. 4. Right-click the member, and select an option:
Option Member Children Descendants Siblings Parent Ancestors Level 0 (Base) To insert Selected member All children of the currently selected member All members below the currently selected member All siblings of the selected member (Siblings are members that have the same parent member.) Parent of the currently select member All members above the currently selected member 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.
4-17
Finding Members
Finding Members
You can search for members within a dimension by using the Member Find dialog box. To access the Member Find dialog box, right-click a member in the dimension and select Find Members. You can use an asterisk (*) as a wildcard symbol in your search. You can search dimensions in Master View or in application views. The search results include all descendants of the currently selected member that match the search criteria. The results are displayed in the Member Find pane. You can doubleclick a member in the Member Find pane to jump to that member in the application view or Master View. If you want to add a found member to a hierarchy, you can drag the member from the Member Find pane to the application view.
4-18
Creating Aliases
Association
Create table
Creating Aliases
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 BPM Architect by creating an Alias dimension and then adding members to that dimension.
4-19
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. 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. To add aliases to dimension members: 1. Select the dimension member. 2. Double-click in the Alias field of the property grid. 3. Click the ellipsis button and enter aliases in the row representing the alias table.
4-20
Adding Currencies
Adding Currencies
You set up currencies by creating a dimension with the dimension class Currency. You create members in the Currency dimension for each currency needed in your application.
NOTE
A dimension association is required between the 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.
4-21
Scaling
You can specify that data values are scaled when they are displayed in certain currencies. For example, you might set the scaling for the Japanese yen to thousands. You could enter 10,000 as a value for Japan. When you select Japanese yen as the display currency, the scaling is applied and 10 is displayed as the value for Japan.
Triangulation
Planning supports currency conversion by triangulation through an interim currency, which is referred to as the triangulation currency. For example, if you know the European euro exchange rates for U.S. dollars and French francs, you can calculate the U.S. dollar/French franc exchange rate by using the European euro as the triangulation currency. You can also modify a currencys triangulation currency by reentering the exchange rates relative to the triangulation currency period and then refreshing the application so that the new exchange rates are transferred and stored.
NOTE
You cannot select the default currency as a triangulation currency.
Reporting Currency
Planning supports currency conversion from local currencies to one or more reporting currencies. The converted reporting currency values are stored and are read-only for all users. The application default currency is also the default reporting currency. When you add currencies, you specify whether they can be used as reporting currencies. For example, suppose your application contains the currencies Japanese yen, U.S. dollar, and European euro, with European euro specified as a reporting currency. When you create data forms and reports, Japanese yen and U.S. dollar values are converted to European euros and displayed. You can load values directly into Analytic Services (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.
4-22
Creating Associations Between Dimensions
Ellipsis indicates that an association exists.
Creating Associations Between Dimensions

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 Base Currency property of the Entity dimension and the Currency dimension, users can set the Base 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.
4-23
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 Account Entity Properties Requiring Associations Alias Attribute Alias Attribute Currency Period Year Alias SecurityClass
Scenario Generic
4-24
Summary
In this lesson, you should have learned to: Describe BPM Architect Navigate BPM Architect Create dimension members Manage dimensions Modify member properties Set up alias tables Add and modify currencies Create property associations
4-25
4-26
L E S S O N
Setting Up the Period, Scenario, and Version Dimensions
Objectives
At the end of this lesson, you should be able to: Describe Planning time periods Customize time periods Create scenarios Create versions
Module 2
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
Time Periods Overview

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 Change the description 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. The YearTotal member is a required member for Planning applications and must exist for successful deployment.
NOTE
The YearTotal member is the summary time period that aggregates all quarters or weeks (for custom time periods). The YearTotal member must have a Period Type property value of Year Time Period. You can add up to 100 calendar years and 500 time periods to an application. Depending on the number of time periods and years and whether your application uses multiple currencies, Hyperion recommends these practical limits: 400 time periods per year and 27 years 360 time periods per year and 30 years
5-3
Module 2
Period and Year Dimensions
Year
Period
Year
Period and Year Dimensions

The Year dimension contains a member for each year in the range of years for the application. The member identifies the year to which the data applies. The Period dimension is populated with base time periods for the application and is tagged with the Time property in Analytic Services. 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 Analytic Services outline displays the years and time periods.
5-4
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.
Choosing How Data Is Stored

By default, when new members are added to an outline, they automatically store data in the Analytic Services 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 Analytic Services 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 Analytic Administration Services Console to set storage options.
5-5
Module 2
Scenario Dimension
The Scenario dimension specifies a data classification.
Actual
Budget
Forecast
Scenario Dimension
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: Apply different planning methods Associate different scenarios with different time periods and exchange rates Create forecasts and budgets Enter data into scenarios 5-6 Planning: Create and Manage Applications
Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions 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. Scenarios are required for Planning applications, and must exist for successful deployment.
5-7
Module 2
Creating Scenarios
Creating Scenarios
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

In BPM 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.
5-8
Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions
Time Periods
In BPM 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 2006 as the start year and 2008 as the end year. At the beginning of the 2007 fiscal year, you could change the start year to 2007 and the end year to 2009, so that you can enter forecast data for 2009.
Exchange Rate Table

If your application uses currency conversion, you assign an exchange rate table to the scenario in BPM 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).
Use Beginning Balance

Select Use Beginning Balance in BPM 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.
5-9
Module 2
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.
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.
To create scenarios: 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 Data Storage Enable for Process Management Smart List
5-10
Module 2 Creating Application Structures Lesson 5 Setting Up the Period, Scenario, and Version Dimensions Data Type Start and End Year Start and End Period Use Beginning Balance Exchange Rate Table
5-11
Module 2
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
Version Dimension
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 You set up the Version dimension in BPM Architect. You can change the version name in BPM Architect and access permissions in Planning.
5-12
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.
5-13
Module 2
Creating Versions
Creating Versions
You create versions and set version properties in BPM 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.
5-14
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 Californias target for product sales. The budget preparer for California then enters values for the Retail, Wholesale, and Distributors children that total 10,000 in a bottom-up version to show how the target is met. The functionality available with target versions is for top-down budgeting. Guidelines for target versions: Workflow Tasks are not allowed for target versions. Children of target members must be blank (for example, #missing) for the data input to be allowed at the top level. Target members must be set to StoreData (DynamicCalc overrides data input with sum of children). To create versions: 1. Right-click the Version dimension, and select Create Member > As Child. 2. Enter a name and click OK. 3. Set the following properties for the version member: Valid for Plan UDA Member Formula Alias Data Storage Enable for Process Management
NOTE
Enable for Process Management can be selected only for bottom up versions. Smart List Data Type Version Type
5-15
Module 2
Summary
In this lesson, you should have learned to: Describe Planning time periods Customize time periods Create scenarios Create versions
5-16
L E S S O N
6
6
Setting Up the Entity Dimension
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
Module 2 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 entitys currency can be overwritten during data entry or data loads.
Entities Overview
The Entity dimension is a Planning dimension whose members can be loaded or manually added to an application. You can use parent-child relationships among entities to mirror your budget review structure. You can define the types of units that your organization requires, such as geographical regions, departments, or divisions. For example, your organization 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.
6-2
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
BalSheet
Revenue
Eastern US
Assigned
NY FL
Entity Members and Plan Types

A plan type is a classification mechanism for data. Your organization may require different entity members to prepare different plans. For example, all entity members in your organization may submit expense plans, but entity members that are cost centers do not submit revenue plans. When you define entity members, you specify the plan types for which they are valid. Because data forms are associated with plan types, they enable you to control which entity members can enter data for each plan type. For example, Eastern US may be a cost center, so you assign it as valid for the IncStmt plan type, but not for the Revenue plan type. When you create data forms for the Revenue plan type, Eastern US cannot be selected on those forms.
6-3
Selecting a plan type for an entity member involves specifying how the data values should roll up for that plan type. An entity members plan types may change when you promote or demote the member in the dimension hierarchy: If the new parents associated plan types are different from those of the moved member, the member becomes valid for the plan types of the new parent. If you move an entity member, and the new parent of that member is assigned to different plan types, the member remains assigned to the plan types that it has in common with the new parent.
6-4
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
Identifying the Currency Value for Entities

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 BPM 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 entitys 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 forms display currency is set to US dollars, Planning uses the rates in exchange rates table for the Yen to convert the values to US dollars.
6-5
Adding and Modifying Entities
Adding and Modifying Entities

You add and modify dimensions and members in the BPM Architect Dimension Library. You can also set the properties for dimensions and members. When you modify dimension and member properties, this information populates the BPM Architect relational database. For these changes to be reflected in the Analytic Services database, you can deploy the application in BPM 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. You modify members by selecting the member and then modifying the member properties.
6-6
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 to save the changes.
6-7
Saving Dimensions
Save changes to the relational database.
Saving Dimensions
When you add, modify, or delete dimensions and their members, you must save the changes before they take effect. When you save the changes, BPM 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.
6-8
Deleting Entities
Deleting Entities
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 entitys application membership in the Dimension Library, right-click an entity member and select Application Membership.
6-9
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
6-10
L E S S O N
7
7
Setting Up the Account Dimension
Objectives
At the end of this lesson, you should be able to: Describe account types and consolidation order Create account hierarchies
Module 2 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
BalSheet
Revenue
Detail Expense Accounts Assigned

Profit Total Revenues Total Expenses Salaries Rent
Accounts Overview
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.
7-2
Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension If an account is associated with more than one plan type, you must specify a source plan type for the account. The source plan type determines which plan types database stores the account value. For example, if the source plan type for the Total Product Sales account is IncStmt, the value displayed for the account on forms for the Revenue plan type is the value entered for the IncStmt plan type.
7-3
Account Types
Account Type Expense Revenue Asset Liability Equity Saved Assumption Variance Time Balance Skip Exchange Rate Type Currency Type
Expense NonExpense NonExpense NonExpense NonExpense NonExpense
Flow Flow Balance Balance Balance User-defined
N/A N/A None None None N/A
Average Average Ending Ending Ending None
Currency Currency Currency Currency Currency NonCurrency
Account Types
Account types define how an account's value flows over time. Account types also determine the sign behavior for variance reporting with Hyperion System 9 BI+ Analytic Services 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.
7-4
Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension
Time Balance Options

Flow and Balance examples
Jan Total Revenues Cash on Hand Revenue Asset 50 100
Feb 75 150
Mar 50 75
Quarter 1 175 75
Time Balance Options

Option Flow First Balance Average Description Uses an aggregate of all data values for a summary time period as a total for the period. Uses the beginning data value in a summary time period as the total for the period. Uses the ending value in a summary time period as the total for the period. Uses the average of all childrens data values in a summary time period as the total for the time period.
7-5

Option Weighted Average-Actual_Actual Description
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. Uses a weighted daily average based on 365 days in a year, assuming that February has 28 days; does not account for leap year.
Weighted Average-Actual_365
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 None Missing Zero Missing and Zeros Description Zeros and #MISSING values are considered when calculating the parent value. #MISSING values are excluded when calculating the parent values. Zero values are excluded when calculating the parent values. #MISSING and zero values are excluded when calculating the parent values.
NOTE
When the time balance is set to Flow, skip options are not available and default to None. An accounts variance reporting property determines if an account is tagged as an expense in Analytic Services member formulas or Financial Reporting variance functions. Here is how expense and nonexpense accounts behave for variance reporting: ExpenseThe actual amount is subtracted from the budgeted amount to determine the variance. NonexpenseThe budgeted amount is subtracted from the actual amount to determine the variance.
7-6
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 Define business rules that reference these saved assumptions such as: Calculate office supplies by entity based on headcount Calculate facilities expense based on square footage per location
Saved Assumptions
When you define a saved assumption account, you select the appropriate time balance and 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. 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.
7-7
Data Types and Exchange Rate Types

Data NonCurrency types
Date
Currency
Percentage
Smart List
Text
Exchange rate types
Average
Ending
Historical
Data Types and Exchange Rates Types

Data and exchange rate types determine how numeric values are stored and which exchange rate to use to calculate the value. Data type options: NonCurrencyStores and displays the value as a numeric value. CurrencyStores and displays the value in the default currency. PercentageStores and displays the value as a percentage. Smart ListStores and displays the value as a smart list. DateStores and displays the value as a date. TextStores and displays the value as text. For accounts whose data type is Currency, you select an exchange rate type:
7-8
Module 2 Creating Application Structures Lesson 7 Setting Up the Account Dimension AverageValid for any time period; uses the average rate for the account. EndingValid for any time period; uses the ending exchange rate for the account. HistoricalValid for any time period. Data types can have conflicting results on the face of a data form depending upon the cell intersections defined for the data form. For example, the intersection of a "percent" data type and a "currency" data type must be resolved based on how you define the order set. The Data Type Evaluation Order is the defined order. You set a dimension order by plan type to determine the precedence when multiple data types intersect. Data types associated with the first dimension in the list take precedence over data types associated with subsequent dimensions.
7-9
Creating Account Hierarchies
Creating Account Hierarchies

You create and modify account hierarchies in the Dimension Library. You access the Dimension Library through the Navigate menu in BPM Architect. After you save changes to the hierarchy, your changes are saved to the BPM Architect relational database. You must deploy the application in BPM Architect or refresh the database in Planning to update the Analytic Services databases. To create account members: 1. Right-click an account. 2. Select Create Member and one of the following: - As Child - As Sibling
7-10
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 - Account Type - Exchange Rate Type - Data Type - Source Plan Type
Adding and Modifying Accounts

In the Dimension Library, you can build the account hierarchy by adding children and sibling members. You can also change member properties.
NOTE
When assigning plan types, you must set the plan type property for a parent member before you can set the plan type for its children. You cannot select a plan type for a child member if the plan type is not valid for the parent.
7-11
Consolidation Order
Account (Never Share) Profit (+) 7 Margin (+) 10 Level 2 3 Level 1 1 2 4 5 Level 0
Sales (+) COGS (-) Expenses (-) 6 Marketing (+) Misc. (+)
Ratios (~) (Label Only) Margin % (+) (Two Pass Calc) Margin % Sales; Product Share (+) (Two Pass Calc) Sales % Sales -> Products;
8 9
Consolidation Order
After creating the Analytic Services 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 members aggregation option to addition, subtraction, multiplication, division, percent, or ignore. 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.
7-12
Consolidation Order Example

Consolidation order is defined by the order of members in the outline. Analytic Services calculates data in top-down order.
Parent Member 1 Member 2 Member 3 Member 4 Member 5 Member 6 Member 7 (+) (+) (-) (*) (%) (/) (~) 6.67 10 20 25 40 50 60 70 25 40 50 60
30 5 200 400 6.67
Consolidation Order Example

It is important to understand how members with different operators are calculated. When you use addition and subtraction operators, the order of members in the outline is irrelevant. However, when you use other operators, you must consider the member order and its impact on the consolidation. When siblings have different operators, the data calculates in top-down order. Analytic Services calculates Member1 through Member4 as follows: (((Member1 + Member2) + (-1)Member3) * Member4) = X(((10 + 20) + (-25)) * 40) = 200 If the result from Members 1-4 is X, then Member5 consolidates as follows: (X/Member5) * 100 = Y(200/50) * 100 = 400 If the result of Member5 is Y, then Member6 consolidates as follows: Y/Member6 = Z400/60 = 66.67 and Member7 is ignored in the consolidation.
7-13
Summary
In this lesson, you should have learned to: Describe account types and consolidation order Create account hierarchies
7-14
L E S S O N
8
8
Creating User-Defined Elements
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
Module 2 Lesson 8 Creating User-Defined Elements
User-defined dimensions require:
Unique values across databases Plan types assigned at the dimension level
Customer
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. Names and aliases can have up to 80 characters. Descriptions can have up to 255 characters.
8-2
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.
8-3
Attributes Overview
Base dimension
Customer
Attribute dimensions
Sales Rep Company Size
National Accounts
Assad Akili
Small
Your IT Source
Sandy Smith
Medium
ABC Company
Doug Nichols
Large
Software Company
Chris Jones
Attributes Overview
Attributes are characteristics of your data. For example, products can have attributes such as colors, sizes, or flavors. Attributes enable you to add another level of granularity to your data. You create attributes for a dimension when you want to group its members according to the same criteria. For example, you might have a Product dimension with members for three product lines, some of which are sold in retail outlets and some only by catalog. When you are analyzing or reporting your data, you might need separate totals for retail and catalog sales.
8-4
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.
NOTE
In order to assign attributes to a user-defined custom dimension, you must associate the attribute dimension to the user-defined custom dimension. For example, if you want to assign salesreps to the Customers dimension, you associate the Salesrep attribute dimension to the user-defined custom dimension named Customers.
8-5
Creating Attributes
Create Attribute
Create values for the attribute
Creating Attributes
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. 4. Right-click the attribute dimension, and select Create Member > As Child. 5. Enter the attribute value.
8-6
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.
8-7
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
Region (Attribute of the Customer dimension)

East South West North
Examples of Attribute Values

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.
8-8
Module 2 Creating Application Structures Lesson 8 Creating User-Defined Elements
Assigning Attribute Values
Assigning Attribute Values

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. 4. Perform a task: 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 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. .
8-10
Member Formulas Overview
Member Formulas Overview

So far you have set up calculations between members by using aggregation options. These aggregation calculations are built into the Analytic Services 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.
8-11
Adding Member Formulas
Adding Member Formulas

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, Analytic Services, and Hyperion System 9 BI+ 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 Gross Margin Percent, as in the following example: Gross Margin Pct = Gross Margin/Net Revenue;
8-12
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 for mulas: 1. Select a dimension member. The Member Formula property has the following categories: Planning, Enterprise Analytics, and Analytic Services. 2. In the Properties Grid for the member, double-click Member Formula. 3. Click . The Memo Editor dialog box is displayed. 4. Enter a formula. 5. Click Word Wrap to wrap the formula text. 6. Click OK.
8-13
Adding User-Defined Attributes
Adding User-Defined Attributes

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.
8-14
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 scrips, and reports that reference those UDAs.
8-15
Smart Lists Overview

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

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 Gold Silver Bronze
8-16
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.
8-17
Creating Smart Lists
Smart List Dimension
Smart List Values
Creating Smart Lists

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. Optionally, you can do any of the following tasks: - Enable smart lists for data forms if you want to use smart lists on those data forms. - Use smart lists values in member formulas and business rules. - Set how #Missing cells associated with smart lists are displayed in data forms. 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. To create smar t lists: 1. In the Dimension Library, select File > New > Dimension. The Add New Dimension dialog box is displayed. 2. Enter the name and description. 3. From the Type drop-down list, select SmartList. 4. Click OK. 5. In Master View, right-click the Smart List dimension and choose Create Member > As Child. The New Member dialog box is displayed. 6. Type the member name and click OK. 7. Create additional members, as necessary, for the dimension.
8-19
Modifying Smart Lists

Smart List Dimension Properties Smart List Value Properties
Modifying Smart Lists

You modify the following smart list properties in the property grid:
Property Label Description Enter what is displayed 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. 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.
Start Value Increment Display Order
8-20

Property #Missing Data Form Label #Missing Drop Down Label Description Select how #Missing values are represented in cells associated with the smart list. 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.
8-21
Associating Smart Lists with Members
Associating Smart Lists with Members

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.
8-22
Setting Data Forms to Use Smart Lists
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.
8-23
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
8-24
M O D U L E
3
8
Loading Metadata
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 Working with Application Views Deploying Applications Setting Up Exchange Rates
L E S S O N
Loading Metadata from a File
Objectives
After completing this lesson, you should be able to: Format metadata files Load and extract metadata from flat files Create profiles Map dimensions and dimension properties Load metadata from interface tables
Module 3 Lesson 9 Loading Metadata from a File
Loading Metadata
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
Metadata Load Files

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.
9-2
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= Products 'Name|MemberValidForPlan1|MemberValidForPlan2|MemberValidForPlan3 100|Y|Y|Y Tennis Rackets|Y|Y|N Tennis Balls|Y|Y|Y
Formatting Load Files

The section for each type of metadata can be displayed only once in a metadata file. You need not include a column for every 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. True and false values are represented as Y for true and N for false. You can use a semicolon (;), comma (,), space, or tab as the file delimiter.
9-3
Loading Metadata
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=Functional Entity 'Parent|Child #root|United States United States|California California|San Francisco
Add entries to the DimensionAssociations section for each property with an association to another dimension.
!Section=DimensionAssociations 'BaseDimension|Property|TargetDimension Entity|Currency|Currency
Load File Sections

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.
9-4
Formatting Dimensions Sections

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

Each dimension included in the load file must be identified in the Dimensions section as follows:
Column Name DimensionClass DimensionAlias Description Name of up to 50 characters (required) Type of dimension, such as account or entity (required) Alias or further descriptor for the dimension
9-5
Loading Metadata
Formatting Members Sections

Use a separate members section for each dimension. Use Y for Yes and N for No.
!Members=Scenario 'Name|MemberValidForPlan1|MemberValidForWorkforce|MemberValidForCapex|DataStorage| DataType|Start Year|End Year|Start Month,End Month|ExchangeRate Table Current|Y|N|N|StoreData|Unspecified|FY06|FY09|Jan|Dec|A_FXRate A_Scenario|Y|N|N|StoreData|Unspecified|FY06|FY09|Jan|Dec|A_FXRate B_Scenario|Y|N|N|StoreData|Unspecified|FY06|FY09|Jan|Dec|A_FXRate
Formatting Members Sections

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.
9-6
Module 3 Loading Metadata Lesson 9 Loading Metadata from a File Account Valid Planning properties for the Account dimension class: Name, MemberValidForPlan1, MemberValidForPlan2, MemberValidForPlan3, MemberValidForWorkforce, MemberValidForCapex, Plan1Aggregation, Plan2Aggregation, Plan3Aggregation, WorkforceAggregation, CapexAggregation, DataStorage, TimeBalance, SkipValue, VarianceReporting, AccountType, ExchangeRateType, DataType, SourcePlanType Entity Valid Planning properties for the Entity dimension class: Name,Currency,MemberValidForPlan1,MemberValidForPlan2, MemberValidForPlan3,MemberValidForWorkforce,MemberValidForCapex, Plan1Aggregation,Plan2Aggregation,Plan3Aggregation, WorkforceAggregation, CapexAggregation, DataStorage, DataType Scenario Valid Planning properties for the Scenario dimension class: Name,MemberValidForPlan1,MemberValidForWorkforce, MemberValidForCapex, DataStorage,DataType,Start Year,End Year, Start Period,End Period,ExchangeRate Table Version Valid Planning properties for the Version dimension class: Name,MemberValidForPlan1,MemberValidForPlan2,MemberValidForPlan3, MemberValidForWorkforce, MemberValidForCapex, DataStorage, DataType,VersionType Period Valid Planning properties for the Period dimension class: Name,MemberValidForPlan1, MemberValidForPlan2, MemberValidForPlan3, MemberValidForWorkforce, MemberValidForCapex, DataStorage, DataType
9-7
Module 3 Lesson 9 Loading Metadata from a File Year Valid Planning properties for the Year dimension class: Name,MemberValidForPlan1, MemberValidForPlan2, MemberValidForPlan3, MemberValidForWorkforce, MemberValidForCapex, DataStorage, DataType Currency Valid Planning properties for the Currency dimension class:
Loading Metadata
Name, Scale, MemberValidForPlan1, MemberValidForPlan2, MemberValidForPlan3, MemberValidForWorkforce, MemberValidForCapex, ThousandSep, DecimalSep, NegativeSign, NegativeColor, DataStorage, DataType, CurrencyCode, Symbol, ReptCurrency Generic Valid properties for Generic dimension class: Name, DataType
9-8
Formatting Hierarchies Sections

Use this format: <parent member>|<child member> Represent top-level members as children of #root: #root|<top-level member>
Entity Geographical UnitedStates California 1000
!HIERARCHIES=Entity #root|Geographical Geographical|UnitedStates Geographical|Europe UnitedStates|California California|1000 California|Plant1 California|WestSales
Plant1 WestSales Connecticut Massachusetts Europe
Formatting Hierarchies Sections

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.
9-9
Loading Metadata
Formatting DimensionAssociations Sections

!Section=DimensionAssociations 'BaseDimension|Property|TargetDimension Functional Entity|Currency|Currency
Formatting DimensionAssociation Sections

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 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
9-10
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 proper ties 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.
9-11
Loading Metadata
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
Loading Metadata Process

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

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. 4. Optional: Enter a description for the profile. 5. Perform an action: Flat files: Click Upload to browse for the flat file, select it, and click Upload again. Interface tables: From the Data Source drop-down list, select a database. Planning: Create and Manage Applications 9-13
Module 3 Lesson 9 Loading Metadata from a File 6. Click OK. 7. Follow the wizard to complete the profile setup:
Loading Metadata
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.
9-14
Mapping Dimensions
Mapping Dimensions
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. When you map a dimension in the load file to a dimension in Master View, you can merge or replace members: MergeUpdates members with the information in the file. New members are added to the application. Planning: Create and Manage Applications 9-15
Loading Metadata
ReplaceReplaces 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.
9-16
Mapping Properties
Mapping Properties
For each column for a dimension in the flat file, a drop-down list of properties for the same dimension class in 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.
9-17
Loading Metadata
Running Import Profiles
Running Import Profiles

After creating a profile, you are prompted to execute the profile. If you want to run it at another time, you can initiate the import from the Import Dimensions dialog box (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.
9-18
Viewing Job Status
Viewing Job Status

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.
9-19
Loading Metadata
Viewing Import Errors
Viewing Import Errors

You can view import errors on the Import Errors tab.
9-20
Loading Metadata from Interface Tables

Process before Interface Table Import Interface Table Import Process in Hyperion System 9
Interface Tables
BPMA
Financial Management
EPR System
Dimension Library ETL System Interface Tables
Data Synchronization Planning
BPMA Database General Ledger System

Analytic Services
Loading Metadata from Interface Tables

BPM 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. 2. Create a BPM Architect interface database by using a relational database such as MS SQL Server or Oracle. 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. Load metadata from the external systems into the tables.
3.
9-21
Module 3 Lesson 9 Loading Metadata from a File 4.
Loading Metadata
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 tablesUse these tables when you work with the import module for profile creation and execution. User-defined tablesUse 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.
9-22
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
9-23
Loading Metadata
9-24
L E S S O N
1 0
10
Working with Application Views
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 Set up dimension associations
Module 3 Lesson 10 Working with Application Views
Loading Metadata
Creating Application Views
Creating Application Views

An application view represents a selection of the Master View dimensions required for an application. Application view types:
Type Generic Description 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 Hyperion System 9 BI+ Enterprise Analytics application view Hyperion System 9 BI+ Essbase Analytics application view
Planning Consolidation Enterprise Analytics Essbase Analytics
10-2
Module 3 Loading Metadata Lesson 10 Working with Application Views The Application Library displays all application views in BPM 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 BPM 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. 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: 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.
10-3
Loading Metadata
Dimension Library Panes

Master View Application view Properties grid
Application Library
Dimension Library Panes

Pane Master View Application view Properties grid Description 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.
10-4
Module 3 Loading Metadata Lesson 10 Working with Application Views
Adding Dimensions to Application Views

You can drag dimensions from Master View to an application view.
Adding Dimensions to Application Views

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 Base Currency. The Scenario dimension requires an association with the Period and Year dimensions to enter starting and ending time period values.
10-5
Loading Metadata
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.
10-6
Excluding Members
Excluding Members
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: Right-click the dimension and select Show Excluded. A list of excluded members is displayed, and you can select members that you want to include in the dimension.
10-7
Loading Metadata
Member Properties
Inheritance from application view ancestor overrides inheritance from Master View.
Property values loaded or manually entered override both Master View and ancestor values.
Member Properties
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.
10-8
Configuring Application Settings

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

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 three valid plan types: Plan1, Plan2, Plan3, Workforce, and Capex. 4. Set up names for the plan types. Plan type names can contain up to 8 characters. 5. Specify the default currency and indicate whether the planning application contains multiple currencies.
10-9
Loading Metadata
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 proper ties: 1. In the application view pane, select an application. 2. From the Category drop-down list, select System. 3. View or modify the settings.
10-10
Configuring Plan Types

Analytic Services 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
Configuring Plan Types

In the Properties grid, you can indicate up to three plan types for the application view. An Analytic Services 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 typesRevenue 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.
10-11
Loading Metadata
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.
10-12
Specifying Currency
Set default currency for entities Specify whether multiple currencies are used
Specifying Currency
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 Analytic Services: Currency and HSP_Rates. You cannot change this option later.
10-13
Loading Metadata
Setting Up Time Periods
Setting Up Time Periods

You select the base time period and the monthly distribution pattern based on the number of fiscal weeks in a month. The base time period options are the bottom-level time periods in the application. Predefined options are months or quarters. You can create custom base time periods, such as weeks or days. You can select monthly distribution patterns to determine how data entered into a summary time period is distributed or spread among base time periods. During data entry, users can enter data into summary time periods, such as years or quarters. Planning distributes these values over the base time periods that constitute the summary time period.
10-14
Module 3 Loading Metadata Lesson 10 Working with 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.
10-15
Loading Metadata
Removing Dimensions
Removing Dimensions
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.
10-16
Setting Up Dimension Associations

Associate base currency 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
Setting Up Dimension Associations

In the Master Library, you create dimension associations for properties whose values refer to members of another dimension. Examples: You can associate the base currency member of the Entity dimension to the Currency dimension to ensure that the Currency dimension is accessed to retrieve the value for the base 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.
10-17
Loading Metadata
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.
10-18
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
10-19
Loading Metadata
10-20
L E S S O N
1 1
11
Deploying Applications
Objectives
At the end of this lesson, you should be able to: Validate application views Compare application views Adjust performance settings Deploy applications views Review Planning outlines in Analytic Administration Services Redeploy application views
Module 3 Lesson 11 Deploying Applications
Loading Metadata
Deploying Applications Overview
BPM Architect Dimension Server HYPlan application view HYPlan application
Planning Application Server
Deploying Applications Overview

In BPM 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 BPM Architect Application Library.
11-2
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
Deployment Process
In the BPM 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
11-3
Loading Metadata
Validating Application Views
Validating Application Views

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. The Start Month property is defined. The Default Alias Table property is defined. The Default Currency property is defined.
11-4
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: If validation errors occurred, proceed to step 4. If no validation errors occurred, skip to step 5. 4. Click Details to review the errors. 5. Click OK.
11-5
Loading Metadata
Comparing Application Views
Comparing Application Views

You can compare application views to determine how they differ from those stored elsewhere. Comparison methods: Compare to Master LibraryCompares the dimensions and members in an application view to the dimensions and members in Master View in the Dimension Library Compare to Deployed ApplicationCompares an application view to a deployed application Compare to Application As-OfCompares an application view to a prior version as of a specific date and time
11-6
Module 3 Loading Metadata Lesson 11 Deploying Applications The Compare window has three panes: Dimension Compare ResultsDisplays 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 SummaryDisplays 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 ResultsDisplays changed member properties for the selected member. To compare application views: 1. Right-click an application view, select Compare, and select a comparison method: Compare to Master Library Compare to Deployed Application Compare to Application As-Of 2. After the progress bar indicates 100% complete, click View Results. The Compare window is displayed. 3. In the Dimension Compare Results pane, perform an action: Select a dimension to view the results in the 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.
11-7
Loading Metadata
Choosing Performance Settings for Optimal Performance

Use Performance Settings to optimize the dimension order and set dense and sparse dimension settings.
Choosing Performance Settings for Optimal Performance

Before you load and calculate data, you can optimize the Analytic Services 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. The Plan Type Performance Settings dialog box is displayed.
11-8
Module 3 Loading Metadata Lesson 11 Deploying Applications 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: SparseSparse dimensions lack data values for the majority of member combinations. A sparse dimension is a dimension with a low percentage of available data positions filled. DenseFor dense dimensions, there is a high probability that one or more data points is occupied in every combination of dimensions.
11-9
Loading Metadata
Dimension Order
Most Dense Dense Dimensions
Least Dense
Smallest
Aggregating Sparse Dimensions

Largest
Smallest
Nonaggregating Sparse Dimensions

Largest
Dimension Order
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 Analytic Services 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).
11-10
Module 3 Loading Metadata Lesson 11 Deploying Applications 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.
11-11
Loading Metadata
Deploying Application Views
Deploying Application Views

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.
11-12
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 BPM Architect to a Planning Application Server. If you are deploying a Planning application view for the first time, select Create Outline to create the Analytic Services outline. 6. Click Deploy. In the Application Library, the status of the application view is updated to Deployment Pending. 7. Select Navigate > Administer > Job Console to view the status of the deployment. The 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.
11-13
Loading Metadata
Creating Analytic Services Databases
Outline .otl Calculation Script .csc Report Script .rep Load Rules .rul
Creating Analytic Services Databases

You can create Analytic Services 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 Analytic Services 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 Analytic Services database: Database outlinesDefine the structure of the multidimensional database consisting of dimensions and member hierarchies. The file extension is .otl. Calculation scriptsEnable 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.
11-14
Module 3 Loading Metadata Lesson 11 Deploying Applications Report scriptsDefine reports based on data in one or more databases. The file extension is .rep. Data load rulesDefine editing operations on data files that populate the database. The file extension is .rul.
11-15
Loading Metadata
Reviewing Planning Outlines
View Pane
Outline Editor
Reviewing Planning Outlines

After deploying Planning applications, you can perform the following tasks in Analytic 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
11-16
Module 3 Loading Metadata Lesson 11 Deploying Applications
Analytic Services Directory Structure

Analytic Services applications are stored in the following directory structure:
\Hyperion\AnalyticServices\App\<ApplicationName>\<DatabaseName>
CorpBud
Corporate Budgeting application
BalSheet
Balance Sheet database (plan type)
IncStmt
Income Statement database (plan type)
Revenue
Revenue database (plan type)
Analytic Services Directory Structure

Applications are created with their own directory with the same name as the application. Server-based applications are in a directory under the \Hyperion\AnalyticServices\App directory; for example, \Hyperion\AnalyticServices\App\CorpBud. The databases associated with the application are in a directory under the applications directory; for example, \Hyperion\AnalyticServices\App\CorpBud\BalSheet. This directory structure is located on the Analytic Services server. Analytic Services 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.
11-17
Loading Metadata
Redeploying Applications
Change in dimension hierarchy - Replace Change in properties - Merge
BPM Architect Dimension Server
Redeploy
Planning Application Server HYPlan application
HYPlan application view
Redeploying Applications
If you change the metadata, you should redeploy the application view to update the relational and Analytic Services 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. Type of calendar. For example, if you set base time period to 12 months, you cannot later change it to quarters.
11-18
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.
11-19
Loading Metadata
Summary
In this lesson, you should have learned to: Validate application views Compare application views Adjust performance settings Deploy applications views Review Planning applications in Analytic Administration Services Redeploy application views
11-20
L E S S O N
1 2
12
Setting Up Exchange Rates
Objectives
At the end of this lesson, you should be able to: Create exchange rate tables Enter exchange rates Generate currency conversion calculation scripts
Module 3 Lesson 12 Setting Up Exchange Rates
Loading Metadata
Currencies and Exchange Rates

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

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

You enter exchange rate values through exchange rate tables. You can create exchange rate tables to correspond to different business scenarios. 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.
12-3
Loading Metadata
Creating Exchange Rate Tables
5 4
Creating Exchange Rate Tables

You create exchange rate tables in BPM 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.
12-4
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.
12-5
Loading Metadata
Entering Exchange Rates
Application default currency
Entering Exchange Rates

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

There are three types of exchange rates associated with a currency: Historical Average Ending
12-6
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: To Currency Show Years Rate Table Name 5. From the Method drop-down list, select a method. 6. In the Historical, Beg Bal, Avg, and End columns, enter values. 7. Optional: Right-click to use the Fill Year or Fill Table option. 8. Click Save. Each exchange rate table spans all time periods of the application, so that you can apply exchange rates to all scenarios. If you create a table or modify one, you must refresh the application for the new exchange rates to be stored in the plan types.
12-7
Loading Metadata
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 European euros to U.S. dollar
1.4
1.4 / 1.2 = 1.16
1.2
Calculating Implied Rates Through Triangulation

You enter exchange rates for converting the currency values to the applications default currency, not to reporting currencies. Planning automatically derives the rates for converting to reporting currencies by triangulation through the application currency. For 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.
12-8
Module 3 Loading Metadata Lesson 12 Setting Up Exchange Rates When you set up currencies, you specify whether the currency has a triangulation currency that allows the currency to be translated to a different currency through a common third currencythe triangulation currency. You enter exchange rates for converting from the currency to its triangulation currency. The exchange rates between the currency and other currencies that triangulate through the triangulation currency are calculated automatically. These rates are called implied rates. For example, the British pound and the Danish krone might both be set to triangulate through the European euro. After rates are entered for converting between the British pound and the European euro and between the Danish krone and the European euro, the rates for converting from the British pound to the Danish krone and from the Danish krone to the British pound are automatically calculated.
NOTE
If you modify a currencys triangulation currency, you must reenter exchange rates for the triangulation currency property, and you must refresh the application so that the exchange rates are transferred and stored. You cannot select the applications default currency as a triangulation currency.
Determining the Calculation Method

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

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

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

1. Select Administration > Manage Currency Conversion. 2. Click Create.
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.
12-11
Loading Metadata
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.
Currency Conversion Calculation Script

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

In addition to generated currency conversion calculation scripts, a dynamically 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.
12-12
Summary
In this lesson, you should have learned to: Create exchange rate tables Enter exchange rates Generate currency conversion calculation scripts
12-13
Loading Metadata
12-14
M O D U L E
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 BPMA and using Analytic Services and calculate the database. Lessons in this module include: Loading and Calculating Data Overview Loading Data
L E S S O N
1 3
13
Loading and Calculating Data Overview
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
Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview
Loading Data
You can: Load data directly into the Analytic Administration Services database for each plan type. Use any of the following for loading data:
Analytic Administration Services BPM Architect Interface Tables
Loading Data
Planning creates an Analytic Services database for each plan type in your application. You can load data directly into the Analytic Services database that corresponds to the plan type in your application. When you create your Planning application, the Analytic Services databases do not contain data. You can load data values from external systems into your Planning application. For example, you might want to load data for actuals from your ERP system so that you can calculate variances. You can use the following methods to load data: Data can be extracted to ASCII text files (flat files) from external systems and loaded using Analytic Services data load rules. Data can be loaded with BPM Architect interface tables.
13-2
Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview To load data, you must have: An Analytic Services database into which you load the data or in which you build an outline A connection to the Analytic 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 - Analytic Services export files If you are not using a rules file for loading data, a data source correctly formatted for free-form data loading If you are using a rules file for loading data, a rules file validated for data loading
13-3
Requirements for Data Load Files

Use Analytic Services to load data from flat files into your Planning application.
Entity Account Scenario Version Period Year Data
EUROPE GROSS SALES EUROPE GROSS SALES EUROPE GROSS SALES ACTUAL EUROPE EUROPE ASIA ASIA FINAL GROSS SALES NET INCOME NET INCOME GROSS SALES
ACTUAL ACTUAL ACTUAL
FINAL FINAL FINAL
Jan Feb Mar
2006 2006 2006
1000 400 650
JAN FEB FEB JAN
2006 2006 2006 2006
1000 400 300 200
BUDGET DRAFT 2007 ENTITY PERIOD CUSTOMER EUROPE FEB MY COMPANY
4000-100 1500
4000-200 1700
4000-300 1200
Requirements for Data Load Files

The first graphic shown on the slide is an example of a data load file that loads data values for the first quarter of 2006 for the Europe entity and the Gross Sales account in the Actual scenario and the Final version. If a dimension has the same value for all rows, you can place it in the header as a page dimension, as shown in the second graphic on the slide. Requirements: Each data point must be tagged with a member from each dimension. Data must be for bottom-level members, unless you are loading data into a target version. Data is scanned from the top of the file and from left to right. Each field (item) in a record (row) must be separated by a delimiter.
13-4
Module 4 Loading Data and Calculating the Database Lesson 13 Loading and Calculating Data Overview A member name or alias must be enclosed in double quotation marks (" ") if it contains blanks, numeric characters (09), dashes, or unary operators. It must also be displayed exactly as it is in the outline. Members of the same dimension must be in the same column or row. Members of different dimensions can be together only on the page header. They cannot be used together in any other row or column.
13-5
Multicurrency Applications
The HSP_Rates Dimension has the following members: HSP_InputValue HSP_InputCurrency HSP_Rate_<XXX>
Multicurrency Applications
Applications that support multiple currencies include an additional dimension called HSP_Rates. This dimension is used to store exchange rates. The HSP_Rates dimension includes the following members: HSP_InputValueThis member stores data values. HSP_InputCurrencyThis member stores currency types for the data values. HSP_Rate_<XXX> 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, Analytic Administration Services can apply a different currency value to the data displayed for HSP_InputValue.
13-6
Setting Up Data Load Rules

Data load rules map the external data values to the Analytic Services database.
Raw data file
2007 2007 2007 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
Rules applied
Data Prep Editor
Setting Up Data Load Rules

You use data load rules to delineate how data is loaded into Analytic Services databases. Load rules can perform certain actions on the data originating from external data sources as it is loaded into the Analytic Services 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. Map the data in the data source to the database by changing strings. Change the data values in the data source by scaling the data values or adding them to existing values in the data source.
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 Analytic 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.
13-8
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
Staging Data Using Interface Tables

Interface tables in BPM Architect are database tables used to import data from external systems into BPM Architect. You can create multiple BPM Architect interface databases. The BPM Architect database type can be different than the database for the interface tables. For example, the BPM Architect database can be Microsoft SQL, and the BPM Architect interface tables can use Oracle.
13-9
Data Calculation Overview

There are three types of calculations in Planning: Calculations within dimensions Calculations and data blocks Calculation scripts
Data Calculation Overview

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.
13-10
Calculations Within Dimensions

Measures (Label Only) Profit (+) Margin (+) Sales (+) COGS (-) Expenses (-) Marketing (+) Misc. (+) Inventory (+) (Label Only) Opening (+) (TB First) Ending (+) (TB Last) Ratios (+) (Label Only) Margin % (+) (Two Pass Calc) Margin % Sales; 10 Product Share (+) (Two Pass Calc) Sales % Sales -> Products; 11 8 9 5 6 4 1 2 7 Level 2 3 Level 1 Level 0
Calculations Within Dimensions

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: Within the Margin branch: Sales and then COGS Within the Profit branch: Margin and then Expenses Within the Measures branch: Profit, then Inventory, and then Ratios
13-11
Calculations and Data Blocks
Sparse Dimension Calculation
Dense Dimension Calculation
Calculations and Data Blocks

Analytic Services 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.
13-12
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 Analytic Services 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. Analytic Services 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. When Analytic Services 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.
13-13
Calculation Scripts
Calculation scripts: Contain a series of calculation commands, equations, and formulas. Define calculations other than the calculations defined by the database outline. Specify how to calculate a database. The default calculation script calculates the entire database.
Calculation Scripts
Every database needs at least one calculation script to aggregate unary operators and execute formulas in the outline. For most database calculations, the default outline calculation script provides the required results. You can run the default outline calculation script from Analytic Administration Services. In certain cases, you may need to write a calculation script to control how Analytic Services calculates a database. You can use Business Rules as a graphical environment to create calculation scripts. You can also create native Analytic Services calculation scripts using a text editor or the calculation script editor provided by Analytic Services.
13-14
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
13-15
13-16
L E S S O N
1 4
14
Loading Data
Objectives
At the end of this lesson, you should be able to: Create load rules for data files for Analytic Administration Services Load data using interface tables
Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data
Loading Data Using Analytic Administration Services

1
Right-click database; Select Load data
2 Select the file to load
3 Optionally: Select the rules file
Click OK
Loading Data Using Analytic Administration Services

You use Analytic Administrative Services to load data values into Planning applications. You load data directly into the Analytic Services databases that correspond to the plan types in the application. To load data values: 1. In Analytic Administration Services, select the database where you want to load data, right-click, and select Load data. 2. Click Find Data File to select a file to load. 3. Optional: Click Find Rules File to select a rules file. 4. Click OK.
14-2
Creating Data Load Rules

1
Right-click database; Select Create > Rules file
2 From the View menu, select Data load fields
Creating Data Load Rules

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

1
Open a data file
Select a file
Click OK
Opening Data Sources

After you select to create a rules file, the Data Prep Editor is opened. Next, open data sources to see what data needs to be changed. The data source can be located on the Analytic 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 Analytic Services 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.
14-4
Module 4 Loading Data and Calculating the Database Lesson 14 Loading Data Associating Rules Files with Outlines You associate the rules file with an Analytic Services 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.
14-5
Defining Header Records

Headers in data source
Entity ... Jan 150 60 20 Feb ... 160 ... 60 ... 20 ...
New York ... Albany ... White Plains...
Headers in rules file

1st quarter Budget Data Jan Feb ... New York ... 150 160 ... Albany ... 60 60 ... White Plains... 20 20 ...
Skip two lines and map to Budget

Defining Header Records

You can use the Data Prep Editor to create header records in rules files. Data sources can contain data records and header records. Data records contain member and data fields. Header records describe the contents of the data source and how to load data values into the database. A rules file contains records that translate the data in the data source to the database. As part of that information, the rules file can also contain header records. Defining Header Information in Rules Files Headers are used only during data loads or dimension building. They do not change the data source. Header information in a rules file is not used if there is also a dynamic reference in the rules file pointing to a header record in the data source.
14-6
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 Analytic 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.
14-7
Associating Column Fields with Dimensions and Members

Use the Field Properties dialog box to map column fields to dimensions and members.
Manipulate column fields to create unique member names.

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:
14-8
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. If a field represents information that is not data and is extraneous to the outline, you can ignore the field by selecting the Ignore field during data load check box. You use the Data Load Properties area of the Field Properties dialog box to define field names for the columns of the rules file. Manipulating Column Fields Your data source may not always have columns in the correct sequential order, or you may need to manipulate column details such as duplicating, parsing, or concatenating columns to create unique member names.
Action Move Split Join Create Using Join Create Using Text Description Changes the sequential order of columns Parses fields; used for segregating columns where the source file has fields of variable length and does not have field delimiters Joins two or more columns Creates a column or set of columns; used to duplicate a column Creates a column that contains any text, including white spaces
14-9
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
Replacing Text Strings

You can use a rules file to replace text strings so that the fields map to Analytic Services 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 Case-Sensitive 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.
14-10
Option Match Whole Word Description Select Match Whole Word to indicate that Analytic Services 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. Select Replace All Occurrences to indicate that Analytic Services should replace all text strings that match the text string in the With field. By default, Analytic Services replaces the first occurrence. Click New to add a new line for additional changes entered in the Replace and With fields. Click Delete to remove items from action lists. Select Original to leave existing fields in their original case. By default, this option is selected. Select Lowercase to change all characters of the field to lowercase. Select Uppercase to change all characters of the field to uppercase. 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.) Use the Suffix field to enter a text string to be added to the end of the field values. 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.) Select Convert spaces to underscores to change white spaces in field values to underscores.
Replace All Occurrences New Delete Original Lowercase Uppercase Prefix
Suffix Drop leading/trailing spaces
Convert spaces to underscores
14-11
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 Analytic Server.
Validating and Saving Rules Files

You can validate a rules file to ensure that the member and dimension mapping defined in the rules file maps to the outline. However, validation does not ensure that the data source will be loaded properly. The rules file is validated against the associated outline. When the Analytic 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 Analytic 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. Analytic Services automatically adds the .rul extension.
14-12
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? After making the corrections, run the validation again.
14-13
Loading Data Using Rules Files
4 2 3
Loading Data Using Rules Files

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. The rules you selected are displayed on the Data Load dialog box in the Rules File column.
14-14
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. Analytic Services 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.
14-15
Interface Tables
Interface Tables ETL BPMA Planning
Interface Tables
You use Interface tables to create a staging area for loading data from outside systems (EPR, ETL, GL, and so on) into BPM 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.
14-16
Creating Interface Tables
Creating Interface Tables

You create Interface Tables within the Data Synchronization module of BPM Architect. You can load data into the Dimension Library using interface tables.
14-17
Loading Data Using Interface Tables

Process before Interface Table Import
EPR System
Interface Table Import Process in Hyperion System 9

Interface Tables Financial Management
ETL System
BPMA Planning
Dimension Library
Data Synchronization
General Ledger System

Interface Tables
BPMA DB
Analytic Services
Loading Data Using Interface Tables

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 BMP Architect, select a Planning application. 2. Right-click and select Action > Import.
14-18
Summary
In this lesson, you should have learned to: Create load rules for data files for Analytic Administration Services Load data using interface tables
14-19
14-20
M O D U L E
5
14
Setting Up Security
Overview
The aim of this module is to provide an overview of security in Hyperion System 9 Planning. You learn how to provision users and user groups in the User Management Console of Hyperion System 9 Shared Services for your Planning application. You also learn how to assign access rights to elements of your Planning application. Lessons in this module include: Provisioning Users and Groups Setting Up Access Rights to Planning Applications Applications
L E S S O N
1 5
15
Provisioning Users and Groups
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 Provision users for Offline Planning Generate provisioning reports
Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups
Planning Security Overview

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

Security in Planning is based on user privileges. User privileges are system roles and access rights that can be assigned to users or to groups. Groups are sets of users who need similar access rights. After users and groups are defined, you can assign the users and groups access rights to application elements. For example, you can assign a user or a group access to Entity dimension members or data forms. Access rights for users and groups can vary by application and can be assigned for the following application elements: Scenario, Version, Account, Entity, and user-defined custom dimension members Data forms 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 Analytic Services security filters. 15-2 Planning: Create and Manage Applications
Levels of Security
There are four levels of security in Planning.
Data forms and task lists
User authentication
Task security
Object security
Data security
Levels of Security
Planning provides security at four levels: Users must provide a valid ID and password to log on to the system. Users can launch only those tasks to which they have been given access. For example, you can give users the ability to create data forms but not dimension members. Users can open only those data forms and task lists (objects) to which they have been granted access. Users can view and modify data only for dimension members to which they have been granted access.
15-3
User Authentication
Users must provide a valid user name and password to access an application. Planning leverages external authentication providers such as LDAP, Microsoft Active Directory, and NTLM. Users and groups must exist in the authentication directory before they can be granted access to a Planning application.
User Authentication
User login information for Hyperion applications is stored outside the applications in an authentication directory. The information is maintained by a central authentication directory. An authentication directory is a centralized store of users and passwords, user groups, and perhaps corporate information, such as employee IDs or job tiles. The following types of authentication directories are supported: Windows NT LAN Manager (NTLM) on NT 4.0 or higher, Windows 2000, and Windows 2003 Lightweight Directory Access Protocol (LDAP) version 3 or later Microsoft Active Directory (MSAD) server, Windows 2000 SP3 or later You can grant access to your Planning applications to any user or group in an authentication directory. When you grant a group access to an application, the users in the group are also granted access to the application. You grant access in the Shared Services User Management Console. 15-4 Planning: Create and Manage Applications
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, administrators view

Administration menu, interactive users view
Task Security
Task security determines the tasks in an application that a user can access. You assign task security by assigning a role to a user. Each role is associated with a set of tasks. For example, interactive users cannot change dimension members, so the dimension change option is not available to interactive members.
15-5
Object Security
You can assign security to specific objects in your application.
Data form
Task list
Object Security
Within your Planning application, you can assign security to specific objects, such as data forms and task lists. For example, you can allow all users to access the standard expenses data form but allow only payroll managers to use the salary expense data form.
15-6
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
Data Security
Setting up data security enables you to protect data and prevent unauthorized users from changing data. For example, you can restrict access to certain data elements in an application.
15-7
User and Group Provisioning Overview
User and Group Provisioning Overview

User provisioning enables centralized management of users, their role assignments and their access rights to applications created under various 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 from Workspace, select Administration > 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: User Directories Projects Unassigned Applications
15-8
User Directories
User Directories list users from native and external directories.
User Directories: Native and NTLM
User list for selected directory
User Directories
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.
15-9
Projects
Projects group instances of Hyperion products that compose an implementation.
Projects
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 Analytic Services 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. 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.
TIP
In a practical sense, you can think of a project as a type of folder.
15-10
Unassigned Applications
Before you can provision users or groups to an application, you must assign the application to a project.
Planning application that has been registered with Shared Services but not yet assigned to a project
Unassigned Applications
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.
15-11

8 Expand an application
9 Select a role
10 Click Add
11 Click Save

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. From Planning, select Administration > User Management. User Management Console is displayed. 2. In the view pane, expand User Directories. 3. Select and expand Users, to provision and assign roles to users, or Groups, to provision and assign roles to groups.
15-12
Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups 4. Click Show All to display a list of users or groups. 5. Select the user or group that you want to provision. 6. Select Administration > Provision, or right-click a user or group and select Provision. 7. 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. 8. Expand the application for which you want to provision the user or group and for which you want to assign roles. 9. Select the role or roles that you want to assign to the user. 10. Click Add. 11. Click Save. 12. Select File > Exit to return to Planning.
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.
15-13
Provisioning Offline Planning Users
Assign Offline User role in User Management Console
Enable Offline Mode in Planning application settings
Provisioning Offline Planning Users

You can use Offline Planning to work with data forms offline and to synchronize information back to the Planning server when you are connected again. To set up Offline Planning users: 1. In Planning, select Administration > Application Settings. The System Settings page is displayed. 2. From the Enable Use of the Offline Mode drop-down list, select Yes, and click Save. 3. In Planning, select File > Preferences. The Application Settings page is displayed. 4. Verify that the User Offline Enabled drop-down list is set to Yes.
15-14
Module 5 Setting Up Security Lesson 15 Provisioning Users and Groups 5. In Planning, select Administration > User Management. User Management Console is displayed. 6. In User Management Console, provision the user with the Offline User role.
NOTE
Offline Planning must be enabled in your license file, located at Hyperion\Common\LicenseServer\LicensesOffline, before users can work in disconnected mode.
15-15
Generating Provisioning Reports

Generate a provisioning report to list the provisioned users and groups.
Specify a specific user, group, a role or all three. Group results by application or user.
Specify one 3 or more items: user, group, or role. 4
Generate the report.
Generating Provisioning Reports

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.
15-16
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 Provision users for Offline Planning Generate provisioning reports
15-17
15-18
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
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
Assigning Access Rights

You assign access rights to Planning application elements to protect data from unauthorized users or groups. The level of security is determined by the access option that you assign to a user. You can assign access by using dimension member relationships or by assigning access directly to individual dimension members. You can define unique access rights for each Planning application. You can assign access rights to the following application elements: Scenario, Version, Account, and Entity dimension members User-defined custom dimension members, if the Apply Security dimension property is selected Data forms Task lists You can use the dimension editor to assign access to dimension members, or you can use the ImportSecurity utility to import access rights information from a flat file. You assign access to data forms in Form Management and to task lists in Task Management. 16-2 Planning: Create and Manage 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
Access Options
When you assign access rights to a dimension member, data form, or task list, you determine which access option to assign for each user or group. By default, for interactive users and planners, access is denied to all dimension members, data forms, and task lists. The following table describes the access options for dimension members and data forms.
Option Read Write None Definition Enables users to view the dimension member or data form Enables users to view and modify access to the dimension member or data form Prevents users from accessing the dimension member or data form
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 Assign Manage Manage and Assign None Description Enables users to view and use the task list Enables users to modify the task list Enables users to modify, view, and use the task list Prevents users from viewing the task list
16-4
Inheritance Options
The following inheritance options are available: Member Children iChildren Descendants iDescendants
Inheritance Options
You can assign access rights to individual dimension members, or you can use an inheritance option to assign rights to multiple members. It is more efficient to assign access rights 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 Member 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.
16-5

Option iChildren Descendants iDescendants Result The access right is assigned to the currently selected member and to all of its child members. The access right is assigned to all descendant members of the currently selected member. The access right is assigned to the currently selected member and to all of its descendant members.
16-6
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 United States
Precedence and Inheritance of Access Rights

You can assign access rights to a member in the following ways: The user can be assigned direct access to a member. The group can be assigned direct access to a member. The user or group can be assigned access to a member by relationship, 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.
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: You are assigned None access to children of the United States. You are assigned direct Read access to LA. You have Read access to LA. You are individually assigned Write access to children of the United States. Your group is assigned direct Read access to LA. You have Read access to LA.
16-8
Reporting on Access Assignments

1 2
Reporting on Access Assignments

To help you effectively view the current access assignments in an application, you can generate assigned access reports. You can also generate effective access reports to help resolve inheritance or precedence conflicts. You generate these reports from 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 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.
16-9
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\Utils folder.
Importing Security Overview

You can load access rights from a text file into Planning by using the ImportSecurity utility, which enables you to quickly assign access for many members, users, and groups. When you import access rights for a member, existing rights assigned to that member are overridden. Access to other members is not affected unless you specify the parameter 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: Joe, eBusiness Sales, Write After importing, Joe has Write access to both OLAP and eBusiness Sales.
16-10
Creating the Secfile.txt File

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

When creating the import security text file, consider the following points: The name of the text file must be Secfile.txt, and the file must be saved in the Hyperion\Planning\Utils 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. Items within lines must be separated by one of the following delimiters:
16-11
Module 5 Setting Up Security Lesson 16 Setting Up Access Rights to Planning Applications - 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 User name or group Member name Access rights Description The name of a user or user group that is provisioned for the Planning application A member (Account, Entity, user-defined custom dimension, Scenario, or Version) in the application 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.) @CHILDREN, @ICHILDREN, @DESCENDANTS, @IDESCENDANTS, and MEMBER.
Inheritance options
For example, the Secfile.txt file might contain the following lines: User1,Account1,read,@CHILDREN User2,Entity2,write,@DESCENDANTS User3,Version_1,write,MEMBER Group1,Account101,write,@ICHILDREN
NOTE
If a member, user, or user group name contains a character that you are using as the delimiter, enclose the name in double quotation marks. For example, if you are using a space as the delimiter, enclose the name North America in double quotation marks (North America). Inheritance options must be in all capital letters.
16-12
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.
16-13
Importing Access Rights

Run the ImportSecurity utility from the command prompt. The file is located in the Hyperion\Planning\Utils folder. The syntax is ImportSecurity.cmd appname,username,password,[delimiter],[run_silent], [SL_CLEARALL]. For example:
ImportSecurity.cmd HYPlan,trnadmin,hyperion
Importing Access Rights

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\Utils folder.
16-14
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 delimiter Description Optional: SL_TAB, SL_COMMA, SL_PIPE, SL_SPACE, SL_COLON, SL_SEMI-COLON If no delimiter is specified, the comma default is assumed to be the delimiter. run_silent Optional: Whether to execute the utility silently or with progress messages: 0 = Execute with messages 1 = Execute silently, with no messages If this parameter is not included in the command line, the value is assumed to be 0, to display progress messages during execution. [SL_CLEARALL] Optional: Whether to clear all existing access assignments when importing the new access assignments This option must be in uppercase.
4. After you execute the utility, view the importsecurity.log file in the Utils folder to verify the results. The new security information is now accessible from the Dimensions task on the Administration menu in Planning. 5. Optional: To see the new security information reflected on the Enter Data page, select the Security Filters option, and refresh the application databases. You do not need to restart the application server.
16-15
Creating Security Filters

Create security filters to provide access to Planning data.
Create security filters for all users.
Create security filters for one or a few users.
Creating Security Filters

Data access rights for data forms, task lists, and process management are read from the Planning relational database and take effect immediately. Analytic Services 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 employees 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:
16-16
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 Analytic Services. 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 Analytic Services 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 Analytic Services, select only Validate Limit only.
16-17
Summary
In this lesson, you should have learned to: Assign access rights Import access rights Create security filters
16-18

Hyperion Planning 9.3 Student - Guide - 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hyperion Planning 9.3 Student - Guide - 1

Uploaded by

Copyright:

Available Formats

Hyperion Planning 9.

3: Create and Manage Applications

D50751GC10 Edition 1.0 June 2007 D50934

Module 1: Getting Started Lesson 1: Planning Overview

Lesson 2: Navigating Workspace

Module 2: Creating Application Structures Lesson 3: Creating Dimensions Overview

Lesson 4: Managing Dimensions with BPM Architect

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

Planning: Create and Manage Applications

Version Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Creating Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Lesson 6: Setting Up the Entity Dimension

Lesson 7: Setting Up the Account Dimension

Lesson 8: Creating User-Defined Elements

Planning: Create and Manage Applications

Module 3: Loading Metadata Lesson 9: Loading Metadata from a File

Lesson 10: Working with Application Views

Planning: Create and Manage Applications

Lesson 11: Deploying Applications

Lesson 12: Setting Up Exchange Rates

Calculations and Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12 Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14

Lesson 14: Loading Data

Module 5: Setting Up Security Lesson 15: Provisioning Users and Groups

Planning: Create and Manage Applications

Lesson 16: Setting Up Access Rights to Planning Applications

Planning: Create and Manage Applications

Lesson 18: Customizing Data Forms

Planning: Create and Manage Applications

Lesson 20: Entering Data Using Smart View

Module 8: Adding Business Rules Lesson 21: Creating Business Rules

Planning: Create and Manage Applications

Lesson 22: Building Runtime Prompts for Business Rules

Lesson 23: Adding Formulas to Business Rules

Planning: Create and Manage Applications

Lesson 25: Creating Task Lists

Planning: Create and Manage Applications

Lesson 27: Navigating Reports in Workspace

Planning: Create and Manage Applications

Module 11: Appendices Appendix A: Sharing Data Using Data Synchronization

Appendix B: Working with Classic Application Administration

Planning: Create and Manage Applications

Planning: Create and Manage Applications

Planning: Create and Manage Applications

A tip provides information that helps you work more efficiently.

Planning: Create and Manage Applications

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Hyperion Business Performance Management

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Copyright 2007, Hyperion. All rights reserved.

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Hyperion System 9 Components

Hyperion System 9 Workspace

Hyperion System 9 Components

Planning: Create and Manage Applications

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Hyperion System 9 Planning

Hyperion System 9 Planning

Planning: Create and Manage Applications

Module 1 Getting Started Lesson 1 Planning Overview

Copyright 2007, Hyperion. All rights reserved.