Hyperion Planning Student Guide

Hyperion Planning 9.
3: Create and Manage Applications

Volume II Student Guide
D50751GC10 Edition 1.0 June 2007 D50935
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
6
16
Designing Data Forms
Overview
The aim of this module is to define and manage data forms. You set user preferences, manage user variables, and create custom menus. Lessons in this module include: Creating Data Forms and Folders Customizing Data Forms
L E S S O N
1 7
17
Creating Data Forms and Folders
Objectives
After completing this lesson, you should be able to: Manage data forms and folders Set up row and column properties Set up page and POV properties Assign business rules to data forms Set up display and precision options Create composite data forms Print data form definition reports Assign access rights to data forms
Module 6 Lesson 17 Creating Data Forms and Folders
Data Forms and Folders Overview

Each data form is associated with a plan type. You assign access to data forms. Data forms with target versions enable data entry into parent members.
Data Forms and Folders Overview

Data forms are spreadsheet-like grids with rows and columns for entering data. You can create as many data forms as required to meet the needs of budget preparers. For example, you can create a data form that budget preparers in the finance department use for fixed assets and a separate data form that line managers use for expense accounts. You manage data forms and folders by using the Data Form Management page. You can perform the following tasks from the Data Form Management page: Create, move, delete, or rename folders Create, edit, move, or delete data forms Create composite data forms Assign access to data forms
17-2
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
Data Form Elements
Page Columns
Rows
Point of View
Currency = Local Customer = No Customer
Data Form Elements

You create a data form by selecting point of view, page, row, and column elements. You create, edit, and manage data forms in the Manage Data Forms page. You can navigate to the page from the Administration menu. The members you select for the dimensions that are assigned to the POV determine the context for the pages, rows, and columns. For example, if the Scenario dimension is set to Budget in the POV, then all of the data entered in the pages, rows, and columns goes into the Budget scenario. For each POV dimension, only one member can be selected. You cannot change the member selected for the POV. For the data form shown in the slide, the POV is set to Local for the Currency dimension and to No Customer for the Customer dimension.
17-3
The page axis enables you to set up combinations of members that may span dimensions so that you can work with data in smaller, logical views. Each item on the page axis can have members selected from one dimension or from multiple dimensions. For example, you can assign the Version and Scenario dimensions to the page axis. For Version, you select the Worst Case and Best Case members. For Scenario, you select the Budget and Forecast members. You can then switch members by selecting them from the page axis. Rows and columns define the grid into which you enter data. For example, you can assign Unit Sales to the row axis and January to the column axis. When you access data forms through Planning, you can enter data into the cell where the row for Unit Sales intersects with the column for January. By default, data forms have a single row and column. You can add rows and columns to create data forms with asymmetrical combinations of row and column members.
17-4
Creating Folder Structures for Data Forms

Remember the following points when working with folders: Move folders within the hierarchy as needed. Rename folders, including the top-level folder, called Forms. Access rights are not assigned to folders. Only empty folders can be deleted. You cannot move or delete the top-level folder, called Forms.
Creating Folder Structures for Data Forms

You use folders to help you organize your data forms. You can create as many folders as needed, and you can arrange the folders in a hierarchy. After you create folders, you can create data forms in those folders. To create a data form, you can build a data form with requirements that you specify, or you can edit an existing data form and then save it as a separate form.
TIP
You can search to find a data form on the Data Form Management page.
17-5
Data Form Requirements
Data Form Requirements

To create data forms, you need to define data form properties, row and column layout, page and point of view (POV) definitions, other options, business rules, and access rights. When you create a data form, you assign it to a plan type. Only members that are valid for that plan type can be included on the data form. For example, if you assign a data form to the Revenue plan type, you cannot add accounts that are not valid for the Revenue plan type. When you save data in a form, it is saved to the database that is associated with the data forms plan type.
NOTE
You cannot change the plan type for a data form.
17-6
Considerations for Setting up Data Forms

In order for a cell on a data form to accept data entry: All members in the POV and pages list must be bottom-level members (except with target versions). All members in the rows or columns must be bottom-level members (except with target versions). The Currency dimension must be set to the Local member. The user must have Write access to all members of the cell.
Considerations for Setting up Data Forms

Prior to creating data forms, data form designers need to consider several factors. Most data forms are used for entering values; therefore, you set up most data forms to permit data entry. However, you can set up forms at a more summarized level, for example, to view the results of calculations. If you want to enter data into the intersections of a data form, then you must set up the data form to meet certain conditions. For bottom-up versions, to permit data entry, dimensions on rows and columns must be set to bottom-level members. A bottom-level member is a member that has no child members below it. If a dimension on a row or column is set to a parent member, the row or column is read-only. If a dimension in the point of view or the Pages drop-down list is set to a parent member, all rows and columns on the data form are read-only. Target versions allow data entry in both parent and bottom-level members.
17-7
You can use member relationships to select shared members. For example, to include all members of a rollup on a data form, you can select an alternate, functional rollup. Values entered into rows or columns that display shared members are saved to the base members in the database. Another factor to consider in the setup of data forms is how to represent the Currency dimension. You set up the Currency dimension on a data form to determine how currency values are displayed. If a row or column on a data form has the Local member selected for the Currency dimension, no currency conversion takes place for the row or column, and you can enter data for the entities on the row or column in their native currency. If you set a data forms Currency member to something other than Local, then data values are displayed as converted to the selected currency, assuming that the currency calculation script has been run. The data form is read-only. In target versions, you can enter data in rows or columns that have Currency or Local as the selected member. For applications that use a single currency, the currency selected when you created the application is used as the currency member for all entities. To allow users to enter data in currencies other than an entitys base currency, when selecting data-form members, you must perform one of the following actions: Select members from at least two currencies, in order to compare converted currencies. Assign the Currency dimension to the page axis, and select reporting currencies as members. To convert currencies for all members in the data form, you can select the Currency member from the page axis and then launch the Calculate Currencies business rule to view all values in the currency of the selected Currency member.
17-8
Setting Data Form Properties
Setting Data Form Properties

You set basic characteristics for data forms on the Properties tab. On the Properties tab, you assign the data form name and description and determine whether the data form permits data entry or is hidden from view. You prevent data entry by making a data form read-only. You also can include instructions for business users who need to use the data form. You can hide data forms by selecting the Make data forms hidden option. If you hide a data form, then business users cannot select the data form from the view pane. You may want to hide a data form that is part of a composite form or a data form that is displayed by a right-click menu.
17-9
Setting Row and Column Layout
Setting Row and Column Layout

You assign dimensions to the columns and rows of data forms by selecting the dimensions from the drop-down lists of the Row/Column Layout tab. For each dimension, you select the preferred members. You then set the properties of the dimensions and members on the columns and rows. For row and column members, you can select segment properties. Column and row properties include showing a member name or alias, starting with the hierarchy expanded, suppressing missing data, and setting column width. For rows, you can also select to suppress missing blocks, suppress missing data, and allow users to add rows dynamically. When you are setting the data form layout, keep the following items in mind: You must select at least one member for each dimension. A data form must have at least one dimension assigned to the row axis and one dimension assigned to the column axis.
17-10
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders You cannot select the same dimension for more than one axis. To move a dimension from one axis to another, delete it from the source axis and select it for the destination axis. Data form designers, when considering how to set up data forms, need to consider dimension composition. For columns, data form designers should use dimensions and members that business users are most likely to need to view. For example, the Period dimensionwhich represents months, quarters, years, or custom time periodsis typically set up on the columns. For rows, data form designers should use dimensions and members that contain a more expansive list of members. For example, the Account, Customer, and Product dimensions typically work well on the rows. Setting Up Segment Properties Segments are areas of data forms with special properties, such as separator lines for columns and rows and hidden or read-only data. You can define segments for asymmetric rows and columns. For example, you can set segment properties in an asymmetric row or column to read-only or to hide members. You can also suppress the hierarchy so row definitions are not indented and columns do not include line breaks. You can select options for segment properties as described in the following table:
Option Hide Suppress Hierarchy Read only Show Separator Apply to All Segments Description Hide the segment so it is not displayed on the data form For columns, do not display line breaks For rows, do not display indentation Create a read-only segment in the data form to enable comparison of old, read-only data with new, editable data Create a bold border before the segment to visually distinguish parts of the data form Apply these settings to all columns in segments
Setting Column Properties The following table shows the options for column width on a data form:
Column Width Small Medium Description Displays columns 50 pixels wide (approximately 7 decimal places) Displays columns 75 pixels wide (approximately 10 decimal places)
17-11

Column Width Large Size-to-Fit Custom Description
Displays columns 100 pixels wide (approximately 13 decimal places) Forces all column headings to fit in the displayed space Enables you to enter a pixel width value of up to 999 (greater than 13 decimal places)
If the selected column width is less than the width of the column contents, the excess data is hidden from view until the column is widened. While hidden, the data is stored and calculated in the data form in the same way as data that is not hidden. Regardless of the column width setting that is selected in the data form properties, you can adjust column width while you are viewing a data form. Saving or refreshing the data form saves the adjusted column width for the remainder of the session. When you print from the data form page, all columns, including minimized columns, regardless of their width setting, are printed at a width that is based on the printing options that are selected for page size and columns per page. The following table describes column width tasks that are available for data forms when you are using Microsoft Internet Explorer:
Task Resize column width Minimize column width Restore a minimized column Restore all minimized columns Reset all column widths to the data form definition default property setting Action Drag the column heading. Click the column heading and select Minimize, or double-click the column heading. Right-click the minimized column heading and select Restore, or double-click the minimized column heading. Right-click any column heading, and select Restore All. Right-click any column heading, and select Reset All to Default.
17-12
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders Setting Row Properties You can set row properties for data form rows. The following table describes the options that you can set on rows in data forms:
Option Suppress missing blocks Description When suppressing a large number of rows, such as 90% or more, select this option to enhance performance of the Suppress missing data setting. If few or no rows are suppressed, the Suppress missing blocks setting can degrade performance. Hyperion recommends that you test data forms before and after using this setting to determine whether performance is improved. You should also test data forms whenever you make significant changes to your application. With this setting, data forms may not display attributes. Also, certain suppressed blocks may ignore Dynamic Calc members. Suppress missing data Select this option to suppress missing data. Selecting this option hides rows without data. If at least one cell of a row has a data value, then the row is not suppressed. Clear this option to display rows that contain only cells for which data is missing; the cells display #missing. You cannot simultaneously select Suppress missing data and Allow users to dynamically add rows. Select this option to enable users who have Write access to the data form to dynamically change and refresh the data forms definition by adding rows. Members that users can access are displayed on the data form. You cannot simultaneously select Allow users to dynamically add rows and Suppress missing data.
Allow users to dynamically add rows
17-13
Selecting Members
Member Descendants Descendants (Inc) Ancestors Ancestors (Inc) Siblings Siblings (Inc) Parent Parent (Inc) Children Children (Inc) Level 0 Descendants Descendants plus North America Worldwide Worldwide plus North America Europe, PacRim, Corporate Europe, PacRim, Corporate, North America Worldwide Worldwide and North America Central, South, East, West Central, South, East, West, North America 200, 205, 210, 220, 225, 230, 240, 245, 250, 255, 270, 275, 280
Selecting Members
You select members for the current dimension on the Member Selection page. You can select specific members, or you can select members based on relationships. The following table describes the existing relationships and the members that are included on the data form for each relationship:
Relationship Member Descendants Descendants (Inc) Ancestors Ancestors (Inc) Members Included on the Data Form The selected member All members below the selected member, excluding the selected member The selected member and all of its descendants All members above the selected member, excluding the selected member The selected member and all of its ancestors
17-14
Relationship Siblings Siblings (Inc) Parent Parent (Inc) Children Children (Inc) Level 0 Descendants Members Included on the Data Form All members in the level of the selected member, excluding the selected member The selected member and all of its siblings The member in the level above the selected member, excluding the selected member The selected member and its parent All members in the level immediately below the selected member, excluding the selected member The selected member and all of its children All descendants of the selected member that have no children
TIP
You can search to find a specific member to include on your data form.
17-15
Creating Substitution and User Variables

Substitution variables are created in Analytic Administration Services Console and reference a member that is assigned to a variable value; for example:
BudYear = FY08 ActYear = FY07 CurrMonth = March
User variables filter members displayed in data forms; for example MYCostCenter = Central (Descendants inclusive).
No user variable
User variable
Creating Substitution and User Variables

Administrators can create and define substitution variables (references to values). Typically, you use substitution variables for financial reporting. Substitution variables are commonly used in situations where a value (such as current month) references a member name (such as Mar) across multiple data form references. The benefit of using substitution variables is that the variable is maintained in one place at one time, rather than across the multiple data form references. Similarly, you can set up user variables to filter members in data forms, thus enabling planners to view only the dimension members with which they are working. User variables can be created by administrators and interactive users. You can navigate to the Manage User Variables page from the Administration menu. After a variable is created, it must be selected as a member in the data form layout. If a user variable is assigned to a data form, business users cannot access the data form until they select a member for the user variable. This task is performed in User Variable Options, accessed from the Preferences option of the File menu.
17-16
Creating Asymmetric Columns and Rows

Example of asymmetric columns: Column A: Scenario = Actual, Time Period = Q1 Column B: Scenario = Budget, Time Period = Q2, Q3, Q4
Creating Asymmetric Columns and Rows

You can create data forms with asymmetric columns or rows. Asymmetric columns or rows contain different sets of members selected across the same dimension. You create asymmetric columns or rows by using the Add Row or Add Column button on the Data Form Layout page.
17-17
Setting Page and Point of View
Setting Page and Point of View

On the Page/Point of View Layout tab, you set up dimension members for pages and point of view. You can select dimensions and members for the page axis. You can choose to display member names or aliases, and you can define the POV dimensions and members for any dimension that is valid for the data form plan type and that is not assigned to a page, column, or row axis. The POV toolbar enables you to set the unique set of dimension members that defines specific intersections of data. You can clear the Visible option for the dimensions on the point of view so that members for the POV dimension are not displayed on the data form. Not showing dimensions in the point of view is especially helpful if the member for the point of view is No Customer, No Scenario, or something similar. You can select the option Enable Dynamic User Variables to prompt the user to select the POV member to use on the data form.
17-18
Setting Options on the Other Options Tab
Setting Options on the Other Options Tab

On the Other Options tab, you can set options for the data forms display, functionality, and printing. For example, you can select to display missing values as blank rather than as #missing. Enable account annotations You can enable account-level annotations. In a data form, users can add annotations to accounts. However, a user must have Write access to the individual Account, Entity, Scenario, and Version members. Account-level annotations can vary, as combinations of Scenario, Version, and Entity dimensions vary. To enable annotations for the account dimension, you must follow these rules: Account must be selected as a row dimension. Scenario and Version must be selected as page or POV dimensions.
17-19
Module 6 Lesson 17 Creating Data Forms and Folders Entity must be selected as a page, POV, or row dimension.
The Scenario, Version, Account, and Entity dimensions cannot be selected as a column dimensions, because the annotation is unique to scenario, version, account, and entity. Allow multiple currencies per entity For applications that support multiple currencies, you select this option to allow entities to support multiple currencies, regardless of base currency. Then, within data forms, business users can select the currency in which cell values are displayed. Enable grid spreading for this form In order to ensure that business users can spread data across dimensions, you select the Enable grid spreading for this form option. Selection of this option enables business users to use the Grid Spreader and Mass Allocate options for the data form. Enable Smart Lists for this form You select the option to Enable Smart Lists for this form so that business users can select cell values from a drop-down list rather than enter values into cells.
17-20
Identifying Missing Values

Cells with #missing have no data value. Write #missing to the database in one of three ways:
Leaving cells blank Deleting contents of cells Entering #missing
Identifying Missing Values

You can write #missing to the database from a data form. Instead of entering a number, enter #missing; or delete the contents of the cell, leaving it empty. When you save the data form, the cells are set to #missing in Analytic Services. Data entry cells that are blank or that contain the term #missing have no data value. In certain cases, when conversion to a selected currency is attempted, parent entities display #missing. On a data form or report, make sure that a currency rate is entered for each combination of local currencies and selected currencies. Also make sure that currency combinations exist for all mixed-currency child entities and their parent members.
NOTE
When a data form that is designed to suppress missing data is reloaded, rows that contains only cells with #missing are not displayed.
17-21
Selecting Business Rules
Selecting Business Rules

You can create business rules by using a graphical user interface in Analytic Administration Services. These business rules can be launched directly from Planning, or they can be associated with data forms. Both designers of data forms and users entering data into data forms can see and launch only business rules to which they have access. Administrators and interactive users can define business rules that prompt users for input when the rules are launched. Planning includes two default business rules: Calculate Data Form and Calculate Currencies. Calculate Data Form is programatically created for each data form, to calculate subtotals. Calculate Currencies is created for data forms that include multiple currencies, to enable the conversion of values among the available currencies.
17-22
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders By default, the Calculate Data Form and Calculate Currencies business rules are selected. In the Business Rule Properties dialog box, you can set whether or not each business rule that is associated with a data form is automatically launched when data is saved. If a business rule has runtime prompts, you can also set whether or not the default member selection in the runtime prompt window matches the current member selection in the page and POV axes. After you enter data in a data form (or through a data form in Hyperion Smart View), you must calculate new totals for parent members, using the Calculate Data Form business rule. The rule calculates totals only for the members in the data form. For example, if West and its children California and Oregon are in a data form, after you save, calculate, and refresh the data form, a new total is displayed for West. Because North America, the parent of West, is not in the data form, a new total for North America is not calculated. Administrators and interactive users can set up business rules that, when launched from Planning, prompt users for such variables as members, text, or numbers. Here are some examples of runtime prompts: Please select an account. Select a month. Enter the expected number of customer visits per quarter. What percentage change in earnings do you expect next month? Create prompts that are specific and that let the user know what type of data is expected.
NOTE
When launching a business rule with a runtime prompt, Planning validates the value entered, but it does not validate the business rule.
NOTE
The order in which business rules are launched is important and may affect the data. If you are launching both conversion and subtotal business rules, the currency conversion rules must be run before the subtotal rules.
17-23
Previewing Data Forms
Previewing Data Forms

You can review the data form on the Preview tab. During the design of a data form, you can preview its structure and continue to make changes. The preview shows which dimensions are assigned to the POV, column, row, and page axes. Preview does not display data associated with the data form, member attributes, or aliases.
17-24
Composite Data Forms
Composite Data Forms

You can create composite data forms to view several data forms, even forms associated with different plan types, simultaneously. Business users can perform data entry and see the results aggregated to an upper-level intersection, such as Total Revenue, Total Departmental Expenses, or Net Income. You can use composite data forms to accomplish the following tasks: Combine two or more data forms on one screen Perform real-time impact analysis by entering data in one data form (for one plan type) and viewing calculated results in another data form (for the same or another plan type) Choose the order that data forms are displayed on the screen and whether to combine the POV and page dimensions
17-25
Creating Composite Data Forms
Creating Composite Data Forms

Some of the tasks for creating composite data forms are the same as for creating regular data forms. You set up the following parameters: Data form properties Row and column layout Business rules selection and properties Access permissions You create composite data forms from the Manage Data Forms option on the Administration menu. To create a composite data form, you select Create Composite. You can set options for the POV, the pages, and the number and layout of columns and rows. You also select the data forms to display on the composite data form.
17-26
Selecting Business Rules on Composite Data Forms
Selecting Business Rules on Composite Data Forms

You select business rules for composite forms on the Business Rules tab. You can include all business rules of the base forms or specific business rules. If you select an individual business rule, you can click Properties to set the properties for that rule. On the Business Rules properties screen, you set whether the business rule runs when the data form is loaded; whether the rule runs when data is saved; whether, if the rule contains a prompt, the members on the data form are used; and whether to hide prompts, if the rule contains any.
17-27
Printing Data Form Definition Reports
Printing Data Form Definition Reports

To enable better data form management, administrators can print a data form definition report. The report can include information on dimension members, business rules, and access rights associated with the data form, as well as other standard data form components.
17-28
Assigning Access Rights to Data Forms
Read: Enables users to view and use the data form for data entry. Write: Enables users to change the data forms design and to view and use the data form for data entry. None: Prevents users from viewing the data form.
To get the latest set of users and groups from the User Management Console, click Refresh User/Group lists.
Assigning Access Rights to Data Forms

By assigning access to a data form, you control which users can access and change the data form design (for example, data form properties such as formats, layout, and instructions), and which users can access the data form for data input. A user or group can have only one of the following access rights: Read, Write, or None. However, the access rights for a user can be combined with the users group rights. You create and change data form designs by using the Manage Data Forms option on the Administration menu. Administrators and interactive users have access to this task. When you are designing a data form in Planning, the selection list to set properties is filtered based on access rights. For example, when you set up the data form layout for page, column, row, and point of view, you select from the list of dimension members to which you have Read or Write access.
17-29
Access to specific data forms created by administrators or interactive users is based on access rights. For example, if you have Read access to a data form, you can view the data form in a list and select it. Whether you can change data in a data form depends on whether you have access to the members of the form. In order to edit a data form, you must have access to at least one member of each secured dimension on the form. For example, if you have Read access to the Europe entity, all rows and columns on the data form that include the Europe entity are displayed in read-only format. By assigning access to data forms, administrators and interactive users determine the following access rights: Who can view and change various data form designs. By default, administrators have Write access to all data forms. Based on access rights, interactive users have Write access to certain data forms. Who can access data forms for view or data input. By default, administrators have Write access to all data forms. Based on access rights, interactive users and planners have access to certain data forms. Whether users have access to the data in a data form depends on whether they have access to the members of the form..
NOTE
Access rights are assigned to data forms, not to data form folders. You can assign access to only one data form at a time.
17-30
Summary
In this lesson, you should have learned to: Manage data forms and folders Set up row and column properties Set up page and POV properties Assign business rules to data forms Set up display and precision options Manage data forms Create composite data forms Print data form definition reports Assign access rights to data forms
17-31
17-32
L E S S O N
1 8
18
Customizing Data Forms
Objectives
After completing this lesson, you should be able to: Export and import data forms Create menus Specify application default settings Manage user variables Set up user preferences
Module 6 Lesson 18 Customizing Data Forms
Exporting and Importing Data Forms

To export a single form to an *.xml file, type FormDefUtil export <data form name> <planning server name> <user name> <password> <application> To import a single form from an *.xml file, type FormDefUtil import <file name.xml> <planning server name> <user name> <password> <application> To export all data form definitions, type FormDefUtil export -all <planning server name> <user name> <password> <application> To import all data form definitions, type FormDefUtil import -all> <planning server name> <user name> <password> <application>
Copyright 2007, Hyperion. All rights reserved.
Exporting and Importing Data Forms

You can use the FormDefUtil.cmd Planning utility to export and import a data form definition from and into an XML-based file. You can move data form definitions from one Planning application to another. For example, use the FormDefUtil utility to move data forms from a development environment to a production environment. Planning includes the FormDefUtil.cmd utility for use through a command line interface. This utility is installed in the Utils directory.
NOTE
If you installed Planning to the default location, the Utils directory is located in the following path: x:\Hyperion\HyperionPlanning\Utils. Only administrators can run this utility.
18-2
Module 6 Designing Data Forms Lesson 18 Customizing Data Forms The following table describes the parameters of the utility:
Parameter import or export file name or data form name planning server name user name password application Description Specify whether to import or export the data form definition. Use file name to specify the name of the XML file to import into the Planning application. Use data form name to specify the Planning data form to export to XML. Specify the name of the application server that Planning is using (for example, localhost). Enter the name that you use to log on to the Planning application (for example, smith). Enter the password that you use to log on to the Planning application (for example, pass1). Enter the name of the Planning application (for example, FYPlan).
18-3
Menus
1. Create the menu. 2. Set up menu Item properties for the menu. 3. Associate the menu with data forms.
Menus
Menus are displayed when business users right-click data-form rows or columns. Business users can use right-click menus to perform separate and distinct actions. For example, after entering data, a business user can move to the Manage Process page by using a right-click menu. A predefined scenario and version can be passed for use on the Manage Process page. Administrators create right-click menus and associate them with data forms. By creating right-click menus, administrators enable business users to click rows or columns in a data form and select menu items to accomplish various tasks: Launch another application, URL, or business rule, with or without runtime prompts Move to another data form Move directly to the Manage Process page, with a predefined scenario and version
18-4
Module 6 Designing Data Forms Lesson 18 Customizing Data Forms To support context-sensitive actions, the context of the right-click is relayed to the next action. Planning passes this context: the POV and the page, the member on which the user clicked, and the members to the left (if a row was clicked), or the members above (if a column was clicked).
18-5
Creating Menus
Creating Menus
Administrators use the Manage Menus page to create, edit, and delete menus. The Manage Menus page lists menus defined in the application. To create menus: 1. Select Administration > Manage Menus. 2. Click Create. 3. Enter a name for the menu, and then click OK. 4. To further define the menu, select the menu, and click Edit. 5. To add the first item to the menu, click Add Child, and Save.
18-6
Module 6 Designing Data Forms Lesson 18 Customizing Data Forms 6. Continue building the menu by selecting a menu item and performing one of the following actions: To add menu items below the selected item, click Add Child (available for Menu Header menu types). To add menu items at the same level as the selected item, click Add Sibling. To edit menu items, click Edit, and then follow step 8 to set up menu item properties. To delete menu items, click Delete. To change the order of menu items within the same level, select one or more items, and click the up or down arrow. 7. Set up the menu items. The following table describes the choices that you can apply for each item.
Item Menu Item Description Enter a unique name that contains only alphanumeric and underscore characters (for example: Position) and no extended characters, special characters, or spaces. Note: Labels can contain spaces, special characters, and extended characters. Label Enter the text to be displayed when the menu is selected. Spaces and special characters are allowed. Menu labels are displayed on the user interface. Labels can be text or they can reference a resource variable by name. For example, to set a menus label to File, set it to File directly or set it to the name of a resourcesuch as LABEL_FILE. Optional: In context of the Planning server, enter the path to and name of a graphic (for example, /Planning/Images/globe.gif),to be displayed next to the menu.
Icon
18-7

Item Type Description
Select the menu item type. Your selection determines the available properties. For example, no properties are available for the Menu Header type. Choose from the following types: Data FormLaunch a selected data form. When users rightclick in the source data form, the member selection context for the member, page, and POV is retained. If the target data form contains the dimension members identified by the context, the target data forms page is set to match the context. URLNavigate to the specified URL. Business RuleLaunch the selected business rule. WorkflowMove to the Manage Process page to work with a planning unit. Menu HeaderCreate a menu under which you can create child menu items. To distinguish the header from other menu items, insert a separator bar by entering one hyphen as the label for the header item. For menu headers, the Required Dimension list is not available.
Required Dimension
Select the dimension for which the menu item is displayed. For example, if, for a menu item, you select Account, when users rightclick Account members, the menu item is available. Selecting No Required Dimension makes the menu available wherever the user right-clicks in the data form.
8. To set up characteristics for menu items, select the menu item, and click Edit. Menu item properties differ, depending upon the menu items type. The following table describes the choices that you can apply for each item.
Item Data Form Description a. From Data Form Folder, select the folder that contains the destination data form. b. From Data Form, select the data form. a. In URL, enter the complete URL to which to direct the user. b. Select Use Single Sign-on to append the SSO token to the URL. c. Select Launch in a Separate Window to launch the URL in window other than the Planning main window.
URL
18-8
Module 6 Designing Data Forms Lesson 18 Customizing Data Forms

Item Business Rule Description a. From Plan Type, select the plan type for which the business rule is available. b. From Business Rules, select the business rule to launch. c. From View Type, select how to display runtime prompt pages: Classic ViewUse the default Planning view. Streamline ViewDisplay each runtime prompt on a different line, instead of in a different section; eliminate icons; and reduce screen text. d. Optional: In Window Title, enter a title to be displayed, instead of Runtime Prompts. e. Optional: In OK Button Label, enter the text to be displayed for the OK button. f. Optional: In Cancel Button Label, enter the text to be displayed for the Cancel button. g. Optional: Select Launch in a Separate Window to launch the business rule in window other than the Planning main window. Workflow Specify the planning unit to which the user is directed by selecting a scenario and a version.
9. Click Save.
18-9
Associating Menus
Associating Menus
When designing a data form, use the Other Options tab to select which menus are available for the data form. As you update applications, update the appropriate menus. For example, if you delete a business rule that a menu references, remove it from the menu.
18-10
Advanced Settings
Only administrators and application owners can view and set Advanced Settings.
Advanced Settings
Administrators have access to Advanced Settings, which includes the System Settings and Custom Tools tabs. The Show drop-down list has a second option which lists the current application defaults for application settings and display options. The Advanced Settings options are available through the Administration menu. Administrators can specify settings to use across the current application. Nonadministrators cannot access application-wide settings. Because application owners must set up certain options before business users can make their selections, the Application Settings tab is displayed differently for the application owner than for other application users. For example, before users can enable an e-mail notification, the application owner must set up the application's e-mail server. Only the application owner can set two of the system settings: E-mail Server and Password for Synchronizing With Analytic Services. Business users can override the application-wide default settings by setting preferences.
18-11
System Settings Tab

The following table describes the options on the System Settings tab:
Component E-mail Server Description Type the name of the server that hosts e-mail services for the application users; for example, mail.hyperion.com. Available only to the application owner. Specify the character set used for e-mail messages: UTF-8: Use the Unicode encoding format (the default). Regional Setting: Use the system's regional setting. Task List Date Format Set the date format for tasks in a task list: MM-DD-YYYY or DD-MMYYYY. Note: This setting changes the date display format only in the Edit Task dialog box. On all task list pages, the date display depends on the local settings of your system. Shared Services URL Display Users Full Names Type the URL for the Shared Services server, and click Register Shared Services. Select Yes to show the users full names (for example, John Smith) in addition to their user names (for example, JSmith). Select No to suppress the display of the users full names. Note: If the Display Users' Full Names check box is selected, you cannot have two users with identical full names. If you try to add a user with the same full name as an existing user, an error message is displayed. Enable Use of the Application for Specify whether users can access the application when it is in maintenance mode, such as during backups. Select Owner, Administrators, or All Users to give access to the application owner, to administrators, or to all users. Select this option to enable users to use Smart View to take Planning data forms offline, work with data while disconnected from the Internet, and later save the data to the Planning server. Assign an administrator to be the application owner. (By default, the person who creates the application is the application owner. However, the owner may grant ownership to another administrator.)
E-mail Character Set
Enable Offline Planning Select User
Custom Tools Tab

You can customize Planning to include links to commonly used tools for analyzing, tracking, and reporting on planning data. Users can access these links from the Planning Tools menu.
18-12
Current Application Defaults
Current Application Defaults

Select Current Application Defaults, and click Go to access the Application Settings tab and the Display Options tab. When you save, the values specified in these tabs become the application defaults. Other users can override the defaults and revert to the defaultsby selecting the Use Application Defaults check box on the Preferences tabs.
18-13
Managing User Variables

Here is the typical sequence of steps to set up and use user variables: 1. Create the appropriate parent-level members in the dimension outline (if they do not already exist). For example, the parent levels could correspond to the business unit divisions. 2. Create user variables for each dimension that you want planners to be able to filter. 3. When designing the data form, associate the user variables with the data form. 4. Notify planners that they can select members for the user variables that are associated with the data form.
Managing User Variables

You can limit the number of dimension members that are displayed on a data form by setting user variables. Using user variables increases performance and enables planners to focus on those members with which they want to work. For example, for the Entity dimension, you can set up a user variable called Division, and then, for Division, planners can select the members that represent their specific division. You can set up as many user variables as you want for each dimension. User variables can be selected for any axis in the data form: row, column, page, or point of view (POV).
18-14
Creating User Variables

2 1
Creating User Variables

You add or delete user variables from the Manage User Variables option on the Administration menu or from the New User Variable option on the File menu. You select the dimension for which the user variable will be used and then create a user variable name.
18-15
Applying User Variables
Applying User Variables

After you create a user variable, you associate the new user variable with a data form. You can either create a new data form or edit an existing data form and select the member relationship for the dimension that contains the new user variable. In the example shown in the slide, the Division user variable is in the Entity dimension, which is placed on the Pages drop-down list for this data form. Furthermore, you select the descendants inclusive option for Division. To associate a user variable with a data for m: 1. In the Member Selection dialog box, select a user variable. 2. From the relationship drop-down list, select the relationship, and then use the right arrow to move the user variable to the Selected Members list. When a user variable is selected, it is preceded by an ampersand. 3. Click Submit. 18-16 Planning: Create and Manage Applications
Setting Up User Preferences
All users can set preferences.
Setting Up User Preferences

On the Preferences page, for the current application, all users can set individual preferences. Administrators and application owners can also specify certain global settings for the current application. Non-administrators do not have access to application-wide settings. Only the application owner can set the following system settings: E-mail Server and Password for Synchronizing with Analytic Services. All users have access to a Preferences page that has four tabs: Application Settings, Display Options, Printing Options, and User Variable Options. Each preference can be enabled and configured. In the Application Settings tab, you configure e-mail notification, select the alias setting, and set workflow options.
18-17
Setting Up E-mail for Workflow Notifications

When e-mail is set up and notification is enabled, Planning notifies users when they become the new owner of a planning unit. The subject of the e-mail is in the format NEW OWNER: XYZ Plan (Scenario, Version, Entity).
Applying Alias Tables

You can assign alternate names, or aliases, for Account, Entity, and user-defined dimensions and members. You can select aliases for displaying member and dimension names. For example, an alias table called French could display members in French, and another alias table called German could display members in German.
Setting Member Selection and Workflow Options

In the Member Selection Options area, you can set whether aliases and descriptions are displayed in the Member Selection dialog box. In the Workflow Options area, you can control the following aspects in Process Management: Whether to display members actual names or aliases, if they have them Whether planning units that are not started are displayed with those that are started
18-18
Setting Individual Display Options
Setting Individual Display Options

You set individual display options on the Display Options tab. Your number-format selections apply to all currency values that are displayed in all data forms that are within the current application and that you can access. These selections can override default settings. If you select Currency Setting, the currency values in the data form are displayed using the formatting initially set for each individual currency. If you select any other option, your selection applies to all currency values that are displayed in all data forms that are within the current application and that you can access. Use the Display Options tab to perform the following tasks: Change how numerical values are displayed in the data form Enable retention of page dimensions
18-19
Set aspects of page selection, such as remembering the last page selected when navigating among data forms and allowing a search facility when the number of pages exceeds a certain number Enable warning for large data forms Set how many members to be displayed on each page Increase the contrast of the Planning interface Keep in mind the following points about display options: The options listed on the Display Options tab depend on the type of user. Only administrators can set the number of members to be displayed on each page. Formatting selections take effect when you leave the data cell. If you select a setting other than the Use Application Default setting for either the thousands separator or the decimal separator, then you must change both separators from the Use Application Default setting option. However, you cannot select the same option for both the thousands and decimal separators. Page Selection Options The most recently used dimension members from the page of the last data form that you used are remembered and compared to the members of each data form that you select. If there is a match, that member name is displayed in the drop-down list of the new data form that you select.
NOTE
For the current application, the Page retention setting applies both within a session and between sessions. When you are working with a large number of pages, you can select among the pages more easily by using a Search drop-down list that Planning adds to the data form when the number of pages exceeds a value that you specify. Warning on Large Data Forms Unusually large data forms with numerous cells may require significant time to open. You can choose to display a warning when data forms that are larger than a specified number of cells are opened. When you try to open a data form that exceeds the specified size limit, a warning is displayed about the time needed to open the data form, so that you can choose whether or not to open it.
18-20
Setting Individual Printing Options
Setting Individual Printing Options

You set printing options directly from the data form when you are ready to print; or you can use Preferences to set printing options. The options that you set from the Preferences page apply to all data forms to which you have access.
NOTE
You can accept the default settings or set your own options for creating PDF files. To print to a PDF file, you must have Adobe Acrobat Reader 4.0 or later installed. Printing options for a data form are set by the data form designer when the data form is created.
18-21
Setting Individual User Variable Options
Setting Individual User Variable Options

By acting as filters that reduce the number of members that are displayed on a form, user variables help you to open and navigate large data forms that contain many members. You can select dimension members, such as entities in your own region, on which to focus. If a data form contains a user variable, you must select a value for the variable on the User Variable Options tab before you can open the data form. If you do not set the user variable, you receive an error message when you attempt to open the data form. User variables are not related to security. If you want to see different members on your data forms, you can change the user variable at any time. For example, if your company has many cost centers, you can create a data form that includes a user variable called MyRegion. Then, by selecting a member for MyRegion, you can limit the number of pages that are displayed in the Page drop-down list. In this case, before you can open the data form, you must select a value, such as Central, for MyRegion. At any time, you can select a different value, such as South, for MyRegion. 18-22 Planning: Create and Manage Applications
Summary
In this lesson, you should have learned to: Export and import data forms Create menus Specify application default settings Manage user variables Set up user preferences
18-23
18-24
M O D U L E
Entering Data in Hyperion System 9 Planning
18
Overview
The aim of this module is to provide an overview of how to enter and adjust plan data in Planning and Smart View. You learn how to enter, adjust, annotate, and calculate data using data forms in Planning as well as in Smart View. In addition, you learn how to take Planning data offline, work with data offline and then synchronize data to the server. Lessons in this module include: Entering Data Entering Data Using Smart View
L E S S O N
1 9
19
Entering Data
Objectives
At the end of this lesson, you should be able to: Submit data in data forms Adjust and annotate plan data Calculate data in data forms Enter data with smart lists Navigate data forms with menus
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data
Submitting Data in Data Forms
Submitting Data in Data Forms

You use Planning to enter plan data in data forms. You can enter data from the start page in Advanced mode by selecting forms in the view pane to work on in the content area. In Basic mode, you can enter data only if your administrator sets up a task that includes a form. In both modes, you can enter and edit only data to which you have access. These are the data-entry tasks that you can perform: Type data directly into cells on a data form Spread data from summary to base periods automatically Adjust existing data and add supporting details Annotate planning units, accounts, or cells Export data to a spreadsheet Launch business rules to perform predefined calculations on data that you enter
19-2
Elements on the Enter Data Page

Row Headings Point of View Toolbar Icons
Page List Column Headings
View Pane
Content Area
Elements on the Enter Data Page

There are several areas on the enter data page that assist you with navigation, data selection, and data entry. View Pane The view pane lists the form folders that are set up for your application. Data forms are contained within the folders. After you select a folder, a list of data forms within the selected folder is displayed on the view pane as well as in the content area. You can select a data form from this list. After you select a data form, it is displayed in the content area. Content Area Data forms are displayed in the Planning content area. A data form provides an intuitive layout for you to work with the data in your plan from the Web. Data forms displayed in the content area reflect the access rights that you have to the dimension members on the data forms.
19-3
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data Elements of the Content Area for Data Entry The following table summarizes elements of the content area for data entry:
Element Toolbar icons Description The toolbar includes icons to save, refresh, print, adjust, grid spread, mass allocate, cut, copy, and paste data. The toolbar provides a quick way of entering cell text and supporting detail as well as exporting spreadsheets and logging off.The toolbar also provides immediate access to task lists, task list status, and help. Row and column headings show the members available on a data form. To make the data form easier to work with, you can choose to hide or view the children of a parent member. Across the top of the data form is the point of view (POV) for the form. The members displayed in the point of view show the context of the data in the pages, rows, and columns. The page list is a drop-down list of members from one or more dimensions to be selected for data entry. The rows and columns on the form show values for the currently selected page member. You enter data in the cells at the intersection of rows and columns. Cells with existing data display data values. You can enter data in cells that are not shaded, whereas shaded cells are read-only.
Row and column headings Point of view
Page list
Data-entry cells
19-4
Data-Entry Menu Options
Data-Entry Menu Options

From the File menu, you can save data values or print data forms. You can also export data values to spreadsheets. You can use the Edit menu to adjust, grid spread, mass allocate, cut, copy, and paste data values. From the Edit menu, you can also launch business rules associated with the data form, annotate planning units, add or view cell text, and add or view supporting detail. From the View menu, you can refresh data values, view data form instructions, view currencies for data forms that allow currency overrides, and edit account annotations. You can use the View menu to switch between Basic and Advanced modes and work with task lists. From the Tools menu, you can launch business rules to which you have access.
19-5
Viewing Form Instructions
Viewing Form Instructions

When you define a data form, you can include information to help planners use the form to prepare plan data. You can access the form instructions in two ways: Select a data form from the list of forms contained within a selected folder in the content area. Then you can select the link to view form instructions. You see the instructions view link only if there are instructions for the form. Select View > Instructions when working with an open data form.
19-6
Recognizing Cell Color Cues
Cell with Modified Data Cell with Cell Text Locked Cell
Cells with Supporting Details
Display Only Cells

Recognizing Cell Color Cues

You enter data in Planning applications by typing values into the cells of a data form. Cells in which you can enter data do not have a shaded background. If data exists for a cell, it is displayed in the cell, and you can type over it. If data does not exist for the cell, the cell displays the text #missing, and you can replace the text with a value. When you define data forms, you have the option of displaying cells containing no data as blank. Planning data forms use color cues to indicate whether a specific action was performed on a cell. Color cues are provided for cells when: Data was modified since the last save. The cells are locked. The cells are read-only. The cells contain supporting details. The cells contain cell text. Planning: Create and Manage Applications 19-7
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data Calculated Cells The values for some cells are calculated automatically. When you enter a value into a bottom-level period, the totals for summary periods are updated immediately. For example, when you enter a value into the cell for a month, the totals for the quarter and year are updated immediately. When you enter values into children of a parent member for dimensions other than Period, the updated totals for the parent are not calculated until you save the data or calculate the data form. For example, if you enter values for Sales and Cost of Goods Sold, you do not see updated totals for their parent Gross Margin until you save the data. Display-Only Cells Cells that are display-only are shaded. You cannot type values in display-only cells. The following conditions can cause cells to be display-only: One of the dimension members associated with the cell is a parent. Because parent values are calculated from child values, you cannot enter values for parents unless the version is a target version. You do not have write access to one of the members associated with the cell. The currency for the cell is not set to Local. The planning unit associated with the cell may be under review and owned by another user. You cannot modify data for a planning unit that is under review unless you are the current owner of the planning unit or a budget administrator. The periods may be outside the range that is valid for the current scenario.
NOTE
Administrators can set up members so that text can be entered into cells on data forms. In BPM Architect, administrators can set up members as a data type of Currency to enable business users to key numerical values. In addition, administrators can set up members to enable the input of percentages, smart lists, date, or text values.
19-8
Navigating Data Forms

Special Keys: Enter Tab Shift +Tab Esc Ctrl + z Ctrl + c Ctrl + x Ctrl + v
Jan 30000 1000 #missing Feb 30000 1000 #missing Mar 30000 1000 #missing 90000 3000 #missing Expanded Q1 Apr 30000 1000 #missing 90000 3000 #missing Hiding children Collapsed Q1
Expand and Collapse:
Showing children
Navigating Data Forms

The following table summarizes the special keys that you can use during data entry.
Key Enter Tab Shift+Tab Esc Ctrl+z Ctrl+c Ctrl+x Ctrl+v Result Enters the value that you typed and moves the cursor to the cell below the current cell Enters the value that you typed and moves the cursor to the next cell in the row Enters the value that you typed and moves the cursor to the previous cell in the row Cancels the value that you typed and restores the previous value Cancels the value that you typed and restores the previous value Copies the selected range of cells to the clipboard Cuts the selected range of cells to the clipboard Pastes content from the clipboard
19-9
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data You can choose to hide or view children of parent members. Showing and hiding children enables you to navigate forms more easily when the data forms contain a large number of members in the rows or columns.
19-10
Copying and Pasting Data

Copy and paste data values from within one data form to another data form. Copy and paste data values from other applications such as Excel to a data form.
Copying and Pasting Data

If your Web browser is Microsoft Internet Explorer 5.5 or later, you can copy and paste data values from one data form to another data form or from another application such as Microsoft Excel. The following rules apply when you paste data into a form: If the size of the selected destination area is an exact multiple of the size of the copied area, data is repeatedly pasted into the destination area. For example, if you copy the contents of two rows and then select six rows to paste the data into, Planning pastes the contents of the two rows three times, to fill the six destination rows. You cannot paste data in display-only cells. Planning copies and pastes the actual stored values of cells, not the values that are displayed based on the precision setting. Data that is copied and pasted from Excel to Planning retains the formatting that is set up in Excel.
19-11
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data When you paste data to summary periods, Planning applies spreading rules for each cell in succession, starting from left to right and top to bottom. So, the data resulting from a paste operation may not match the original copied data.
19-12
Working with Non-Aggregated Data
Working With Non-Aggregated Data

Administrators can flag members as non-aggregating. If you flag members so that they do not aggregate, then totals are not calculated on data forms. In addition to being able to set members for input of numerical values, you can set members for input of text or date input. For example, you can flag Asset Description, Asset Units, and Asset Rate members as non-aggregating members and therefore totals will not appear for those cells. You flag cells by selecting the non-aggregating option property 'Never' in BPM Architect.
19-13
Saving and Refreshing Data
Saving and Refreshing Data

After entering or editing values in a data form, you save the information to the Planning application database. After you save the data, the form totals are recalculated to reflect the new data for members that are calculated dynamically. If you want to clear entered values without saving them, you use the Refresh button. When you click the Refresh button, the form is refreshed with the last saved values from the applications database; the last saved values replace all values that you entered but did not save.
19-14
Spreading Data
You can spread data from summary periods to base periods
Jan Revenue or Expense (Flow) Asset, Liability, or Equity (Balance) Percentage Weekly Distribution (4-4-5) 1000 1000 25 923 Feb 1000 1000 25 923 Mar 1000 1000 25 1154 Q1 3000 1000 25 3000
Type ! (Shift + 1) to lock or unlock a cell or group of cells. Jan Cell Locked Before After Jan 100 100 Feb 100 300 Mar 200 600 Q1 400 1000 Jan Cell Not Locked Before After Jan 100 250 Feb 100 250 Mar 200 500 Q1 400 1000
Spreading Data
To make data entry more efficient, Planning automatically distributes values from summary periods to base periods. Base periods are the bottom-level members of the Period dimension. When you enter a value into the Year Total member, it is automatically distributed to the quarters and months. When you enter a value into a quarter, it is automatically spread to the months. How values are spread depends on the account type and the data type. Revenue and Expense Accounts If no data currently exists or if data is all zeros, a value entered in a summary period is divided evenly among the children of the summary period. For example, if you enter 300 into Year Total, the quarters in the year are automatically set to 75, and the months in each quarter are automatically set to 25.
19-15
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data If values exist for the base time periods, the existing proportional spread is preserved. For example, your current distribution might be January=100, February=100, March=200, and Q1=400. If you change the value of Q1 to 200, the new monthly values are January=50, February=50, and March=100. Asset, Liability, and Equity Accounts If no data currently exists or if data is all zeros, the value entered in a summary period is set for each of the base periods. For example, if you enter 1000 into Q1, then January, February, and March are set to 1000. If values exist for the base periods and you enter a new value for the summary period, the base period affected is determined by the time balance option associated with the account. The time balance options available are First, Average, Balance, Weighted Average-Actual_365, and Weighted Average-Actual_Actual. The time balance options and their effect on spreading data values is covered in greater detail in the next topic in this lesson. Percentages Some accounts have the data type Percentage. For these accounts, the value is allocated to each base time period, regardless of the account type or of whether data exists. For example, if you enter 25 in quarter 1, January, February, and March are all set to 25. Weekly Distribution Some accounts in your application might be set up to use the weekly distribution option. When the weekly distribution option is selected for an account, Planning treats quarterly values as if they were divided into 13 weeks and, using the pattern specified by your budget administrator, distributes values to the weeks. For example, if the 5-4-4 distribution option is selected, Planning treats the first month in a quarter as if it has five weeks and the last two months as if they have four weeks.
NOTE
You can temporarily lock the values of one or more cells to preserve existing values when spreading data, during which time Planning calculates and fills in values for the remaining base period cells. You can spread data across periods based on various calculations and visually review the changes before saving them to the database.
19-16
Time Balance Options

Jan Flow First Balance Average Weighted Average-Actual_365 Weighted Average-Actual_Actual Weighted Average-Actual_365 (100*31 + 150*28 + 200*31)/90 = 150 Weighted Average-Actual_Actual* (100*31 + 150*29 + 200*31)/91 = 150 100 100 100 100 100 100 Feb 150 150 150 300 150 150 Mar 200 200 200 200 200 200 Q1 450 100 200 200 150 150
*29 Days in Feb during a leap year
Time Balance Options

The following time balance options can be used with Asset, Liability, and Equity account types: Balance, First, Average, Weighted Average-Actual_Actual, and Weighted Average-Actual_365. Revenue and Expense account types typically use the time balance option of Flow. Balance The Balance time balance option (also referred to as time balance last) displays the value of a summary period equal to the value of the last base period. For example, if the balance for Inventory for March is 200, the Quarter 1 balance is 200.
19-17
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data First The First time balance option displays the value of a summary time period equal to the value of the first base period. For example, if the balance for Inventory for January is 100, the Quarter 1 balance is 100. Average The Average time balance option displays the value of a summary period equal to the average of the base periods. For example, if the Inventory values are January=100, February=300 and March=200, the Quarter 1 balance is 200the average of the three months balances. Weighted Average-Actual_365 and Weighted Average-Actual_Actual There are also weighted average time balance options. If you select Weighted AverageActual_365, each month assumes the actual days of a non-leap year. February always has 28 days and Year always has 365 days. If you select Weighted AverageActual_Actual, each month assumes the actual days of the current year. When Weighted Average-Actual_Actual is selected and the year is a leap year, February has 29 days. Flow The Flow time balance option displays an aggregate of all data values for a summary time period as a total for the period. For example, if the sales for January is 100, February is 150, and March is 200, the Quarter 1 balance is 450.
19-18
Spreading Data Using Grid Spreader

Enable Grid Spreader on the Other Options tab of Data Forms
FY07 Jan Catalog Commercial Direct Distributor Education Government Indirect Mail Order Online Retail Special Events All Channels
272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 #missing
Feb
272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 #missing
Mar
272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 272.73 #missing
Q1
818.18 818.18 818.18 818.18 818.18 818.18 818.18 818.18 818.18 818.18 818.18 #missing
Spreading Data Using Grid Spreader

Using Grid Spreader, business users can specify a value that is proportionally spread across multiple dimensions on a data form. The spread is based on the existing values in the targeted cells. After grid spread is run, the grid is reloaded with the changed cells displayed. The user has the option to view and validate results before saving data. Keep the following points in mind when using the Grid Spreader: Grid Spreader supports proportional spreads. With updates to the spread pattern table, the Grid Spreader can also be used to run fill; 4-4-5; and evenly split, pattern-based allocation. The Grid Spreader ignores read-only, locked, and supporting detail cells. Users can use the Grid Spreader only to spread data to the cells to which they have access.
19-19
Spreading Data Using Mass Allocation
Spreading Data Using Mass Allocation

Mass Allocation enables predefined users (in Shared Services) to allocate across multiple dimensions. Mass Allocation executes calculation scripts and business rules against the Analytic Services server and all dimension combinations. After the rule is run, the grid is reloaded, and the mass allocation results are displayed. The results are saved to the database. Keep the following points in mind when using Mass Allocation: Mass Allocation supports proportional and relational spreads. With updates to the spread pattern table, Mass Allocation supports fill; 4-4-5; and evenly split, pattern-based allocation. Mass Allocation security is based on roles similar to business rules.
19-20
Adjusting and Annotating Plan Data

Increase or decrease plan data by a percentage Perform ad hoc analysis
Spread data with cell locking Use flexible data-entry operators
Add annotations
Cell text Account annotation Planning unit annotation
Enter supporting detail
Adjusting and Annotating Plan Data

After entering your starting point plan data, you may need to adjust data values due to a change in market conditions, revised performance expectations, or new corporate assumptions. You may need to document these changes in the form of annotations or supporting details. Planning provides several options to assist you with this task. You can adjust data values by percentages, perform ad hoc analysis through flexible data-entry commands or by locking data values when you spread data, and enter supporting details. You can also annotate your assumptions at three levels: cell, account, and planning unit. During the data-entry and review process, you may need to adjust some values on a percentage basis, perhaps due to a change in market conditions or due to revised performance expectations. You can use the Adjust Data feature to increase or decrease by a percentage the value in any cell or range of cells that contains data.
19-21
Performing Ad Hoc Analysis

Ad hoc analysis is especially useful for manipulating values in specific accounts to produce desired results. Before committing data:
Perform what-if calculations and visually review the changes. See the impact of various scenarios before saving the data.
Operation Add + Subtract + Initial Value 100 100 100 100 100 Input Text +50 +-50 *5 /5 %25 Result 150 50 500 20 25
Flexible Data Entry
Multiply * Divide / Percentage %
Performing Ad Hoc Analysis

You can apply what-if scenarios to existing values to see the impact of various conditions before saving data. This capability is especially useful for manipulating values in specific accounts to produce desired results. You can manipulate and experiment with data values in one of the following ways: Lock a value when you spread data Change existing values by entering an operator (flexible data entry) Export data to a spreadsheet Before committing data by saving it, you can perform various what-if calculations and visually review the changes. You can change an existing value by using the operators: Add +, Subtract + -, Multiply *, Divide /, and Percentage %. The table shown in the slide provides examples of the impact of using the flexible data-entry operators.
19-22
Exporting Data to Spreadsheets
Exporting Data to Spreadsheets

You can export data from a Planning data form to Excel to explore what-if scenarios in Excel before copying and pasting values back to Planning. Keep in mind the following information about exporting data from a form: Planning does not export numerical formatting to Excel. Also, the application name, user name, form folder name, member aliases, dimension attributes, account annotations, currency tags, and percentages are not exported to Excel. Values pasted back to Planning from Excel must be nonformatted data. Excel supports the Internet Explorer browser. Every time you click Spreadsheet Export, a new instance of Excel is opened in the browser. Use the Close button to close any instances that you do not need.
19-23
Adding Annotations
Cell text Account annotations Planning unit annotations Supporting details
Adding Annotations
You can add documentation to your plan in the form of annotations. You can add annotations at different levels depending on how general or specific the explanation needs to be. For example, very specific annotations can be entered at the cell level; this is referred to as cell text. General comments can be added at the Planning Unit level; this is referred to as a Planning Unit annotation. Annotations and supporting details are stored in the Planning relational repository; they are not refreshed in the Analytic Services database. You can print the data contained in a data form, including cell text, account annotations, and supporting detail. Planning unit annotations can be printed by budget administrators through Administration > Reporting or through Financial Reporting.
19-24
Adding Cell Text and Account Annotations
Account Annotation
Adding Cell Text and Account Annotations

If you have read access to a cell, you can add annotations called cell text to the cell at any level. You can add cell text at the summary time period level and across multiple dimensions at any level. You can also add cell text for non-level-zero members (in bottom-up versions), calculated cells (Dynamic Calc), and read-only cells. You can use supporting detail and account annotations in addition to cell text to add comments to data. With supporting detail, you can build and communicate bottom-up values; with account annotations, you can add comments to accounts. You can add account annotations or comments during data entry. You can view comments that other users have entered. Account annotations are displayed in a column on the data-entry form. Account annotations are associated with a specific account for a planning unit.
19-25
Adding Planning Unit Annotations
Section
Description
Scenario, Version, Entity Enter Title Enter Text Existing Annotations
Select the scenario, version, and entity that compose the planning unit for which you want to add or view annotations. Enter a name for the annotation. Enter and submit the text for the new annotation for the planning unit. View the existing record of annotations associated with the planning unit
Adding Planning Unit Annotations

You can add annotations to a planning unit. A planning unit is a combination of a scenario, a version, and an entity member. Planning unit annotations are general comments that pertain to the planning unit as a whole, rather than to individual rows, columns, or cells on the data form. The table on the slide summarizes the sections on the Annotations window.
19-26
Adding Supporting Detail
Adding Supporting Detail

You can use supporting detail as a built-in calculator for developing data that is not in the member outline. It also provides a way for you to drill down into data and to better understand the basis of the data. Supporting detail helps you build and communicate bottom-up values when planning corporate expenses, such as travel, salary, and projects, for which you need to calculate aggregate values. Supporting detail can include text, values, and operators that define how data is aggregated. Additional information about supporting detail: Supporting detail does not change members in the Analytic Services outline structure. To create, change, or delete supporting detail, you must have write access to cells. You must have read access to view supporting detail.
19-27
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data To protect values, you cannot enter, adjust, spread, or save data in aggregate values (summary periods) that have supporting detail. The aggregate values are read-only. You can add supporting detail only to base periods. You can add supporting detail to both target and bottom-up versions. Any number and precision formatting that is set up is not reflected in the Supporting Detail window. The sequence of operators in supporting detail follows the logic that Analytic Services uses to process multiple operators in a complex calculation. When you use Copy Versions, you can copy supporting detail from one version to another. You can also copy supporting detail using the Copy Data task. When you delete supporting detail for a cell, you can set how the information is synchronized with Analytic Services. The information can be set in Analytic Services to #MISSING or left it as it was before the supporting detail was deleted. When you enter or change supporting detail, you can copy and paste the information to multiple cells simultaneously.
19-28
Calculating Data in Data Forms

Edit > Launch Rules (associated with data form)
Tools > Business Rules
Calculating Data in Data Forms

After you enter data in data forms, new totals need to be calculated for parent members. By default, two calculation scripts are associated with data formsCalculate Data Form and Calculate Currencies calculation scripts. In addition to these two default calculation scripts, you can launch any business rule to which you have access. You can associate user-defined business rules with a data form. The following points describe how values are subtotaled and totalled in data forms: Dimension member subtotals are calculated based on factors such as the hierarchies and logic of the Analytic Services outline and the member properties. When data is saved, Analytic Services automatically calculates members that are set to be calculated dynamically. Parent members that are not set to be calculated dynamically are not updated.
19-29
Module 7 Entering Data in Hyperion System 9 Planning Lesson 19 Entering Data For calculated parent members on a data form that are not set to be calculated dynamically, you need to run the Calculate Form calculation script. All subtotals in the data form are recalculated based on their members aggregation properties and the forms design and layout. Calculations are based on stored values, which are not necessarily the same as the displayed values. For example, the values that you see on the form might be based on scaling or precision settings.
19-30
Calculate Data Form Calculation Script

Data Saved Before <Calculate Data Form> Parent Member Not Updated
After <Calculate Data Form> Parent Member Updated
Calculate Data Form Calculation Script

Launching the Calculate Data Form calculation script from Planning requests that an Analytic Services calculation script calculate new totals for just the members displayed on the data form. For example, if Northern Europe and its children Germany and Nordics are on a data form, when you save the data and launch the Calculate Data Form calculation script, a new total is displayed for Northern Europe. Since Europe, the parent of Northern Europe, is not on the data form, a new total for Europe is not calculated The Calculate Data Form calculation script can be set to automatically run when you save data.
NOTE
If you have read but not write access to some members, subtotals correctly include the members values even if the members are read-only.
19-31
Calculate Currencies Calculation Script

Data Saved Before <Calculate Currencies> Reporting Currencies Not Converted
After <Calculate Currencies> Reporting Currencies Converted
Calculate Currencies Calculation Script

If the data form includes base and reporting currencies, you need to run the Calculate Currencies calculation script to convert base currency values to reporting currency values. Launching the Calculate Currencies calculation script from Planning requests that Analytic Services run a calculation script to convert base currency values to reporting currencies only for members displayed on the form. For example, if the reporting currencies USD and EUR are on a data form, when you save the data and launch the Calculate Currencies calculation script, the converted values for USD and EUR are calculated. If you also have JPY defined as a reporting currency, its values are not calculated because it is not on the form. The Calculate Currencies calculation script can be set to automatically run when you save data.
19-32
Business Rules
Price per New Computer
Headcount of New Employees
New Computer Expense
Business Rules
If you need to allocate or calculate values based on drivers or assumptions, you can set up business rules. You must have access rights to the business rule to be able to launch it. You can launch business rules by selecting Tools > Business Rules if you are in Advanced Mode. If you are in Basic Mode, you have access to business rules only if they are defined in your task list. Business rules can also be associated with data forms. To launch business rules associated with a data form, select Edit > Launch Rules. Business rules associated with data forms can be set to automatically run when you save data. You can also launch business rules associated with a data form by clicking on the business rules listed in the view pane.
NOTE
Creating business rules is covered in detail in a subsequent lesson.
19-33
Entering Data with Smart Lists

Customer_Service_Class uses a smart list.
Network Sales, Chip Sales, and Computer Sales use data values.
Entering Data with Smart Lists

Smart lists are custom drop-down lists that you can access from data form cells. For cells whose members are associated with smart lists, data cannot be entered by typing a value. Instead, you select a value from a drop-down list. After you click in a cell that is associated with a smart list, you can click the arrow to expand the smart list. You can then select one of the smart list options as the value for the cell. After setting up smart lists and associating them with data forms, you can enter data on data forms by selecting from a drop-down menu. Remember that if you use smart lists to choose values from a drop-down list for certain data cells, no data values can be keyed into those cells.
19-34
Navigating Data Forms with Menus

1. Add Headcount (Account 6000) 2. Enter T&E Rate (Account 6010) 3. Enter Software Rate (Account 6020) 4. Right-click on the Account column 5. Click Headcount business rule to 1 calculate accounts 2 3 5240 and 5350
5 4
Navigating Data Forms with Menus

After creating a menu and associating the menu with a data form, you can use the menu by right-clicking on the data form. If you specified a required dimension for your menu item, you can right-click in the area on the data form that contains that dimension. For example, if you select Account as the required dimension, then the menu is available when you click on Account members on the data form. Selecting none as the required dimension makes the menu available when you right-click in the data form.
19-35
Summary
In this lesson, you should have learned to: Submit data in data forms Adjust and annotate plan data Calculate data in a data form Enter data with smart lists Navigate data forms with menus
19-36
L E S S O N
2 0
20
Entering Data Using Smart View
Objectives
At the end of this lesson, you should be able to: Describe Smart View Enter, adjust, calculate, and analyze Planning data using Smart View Work with Planning data
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
Smart View Overview
Planning
Financial Management
Analytic Services
Hyperion System 9 Applications+
Interactive Reporting Production Reporting Financial Reporting Web Analysis
Hyperion System 9 BI+
Smart View Client

Smart View Overview

You can use Smart View to enter and analyze data from a single Excel interface. Smart View provides integration with Microsoft Office not only for Planning but also for Financial Management, Analytic Services, Web Analysis, Financial Reporting, Interactive Reporting, and Hyperion System 9 BI+ Production Reporting . Tasks that previously were repeated across products are now performed only once. The use of a single interface enables you to utilize multiple products simultaneously. Tight integration of Smart View with Office enables you to perform the following tasks: Import content into the Microsoft products Excel, Word, PowerPoint, and Outlook Utilize Office smart tags to add single data values and import reports Distribute and share Office documents by logging on only once to the data source Expose functions for Financial Management and Analytic Services content in Word, PowerPoint, and Outlook
20-2
Integrating Smart View with Office

Excel: Data-entry forms Ad hoc analysis Functions BI+ content Word, PowerPoint, and Outlook: Functions BI+ content
Integrating Smart View with Office

You can use Smart View to import Hyperion System 9 BI+ content from Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis into Excel, Word, or PowerPoint. BI+ content can consist of reports, dashboards, and charts from the following products: From Financial Reporting and Web Analysis, you can import reports. From Interactive Reporting, you can import charts, dashboards, and reports (first page only). From Production Reporting, you can import reports. Importing charts is not supported in Release 9.0.
20-3
Smart View Architecture

Smart View Client Data Source Connection XML HTTP(s) Analytic Services Provider Java API Infrastructure Planning Provider Planning Application Server TCPIP / DCOM Financial Management Provider Financial Management Application Server Data Model
Client Tier
Web Tier Application Tier
Analytic Services
RDBMS
Data Tier
Smart View Architecture

Smart View incorporates powerful architectural features to handle a wide range of analytic applications across large multiple-user environments. The slide provides a highlevel view of the integrated information flow between source data and the Smart View client. The slide shows that Planning and Financial Management have their own Web servers built into the application tier. Analytic Services does not have its own application server. As a result, Analytic Services requires a separate installation for Smart View Provider.
20-4
Establishing Data Source Connections

1
Establishing Data Source Connections

Before you can analyze data using Smart View, you must establish connections to your data sources. To manage your data source connections, use Connection Manager. You can add, delete, and modify connections per Excel instance. The connections managed by Connection Manager have no relationship to worksheets. You can establish multiple connections per Excel instance. After you add data sources in Connection Manager and they are displayed, you can use Connection Manager to connect to the data sources. You can add data sources for Planning, Financial Management, Analytic Services, Financial Reporting, Web Analysis, Interactive Reporting, and Production Reporting. You can connect to a data source directly, if you know the URL, or you can use Shared Services, which displays a list of providers to which you have access.
20-5
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View You can see whether a data source is connected or disconnected by viewing the icon next to the data source name in Connection Manager. If you try to connect to a data source that is disconnected, you are prompted to log on. If you are authenticated by external authentication, you are not prompted to log on. To add a data source connection: 1. In Office, select Hyperion > Connection Manager. The Connection Manager dialog box is displayed. 2. Click Add, and select URL Provider. The Add Data Source dialog box is displayed. 3. Perform the following actions: a. From the Provider drop-down list, select Hyperion Provider. b. From the Location drop-down list, select the Smart View provider URL. Alternatively, enter the URL in the list, using the following format: Analytic Services - http(s)://<servername>:<portnumber>/aps/SmartView Planning - http(s)://<servername>:<portnumber>/HyperionPlanning/SmartView
NOTE
The default URL is http://localhost:13080/aps/SmartView. c. Optional: Select Create as default connection to make this connection your default database connection. d. Click Next. The Connect to Data Source dialog box is displayed.
20-6
Establishing Data Source Connections (Cont.)

4
Establishing Data Source Connections (Cont.)

4. Enter your user name and password, and click Connect. The Select Database or Repository dialog box is displayed. 5. Select a database from the list, and click Next. The Add a Connection Name dialog box is displayed. 6. Enter a name and description for the connection, and click Finish. The connection is now available for selection in Connection Manager.
20-7
Planning and Smart View

Open Planning data forms in Excel Work online or offline
Use Planning data forms even when disconnected from the Planning server Synchronize data back to the Planning server with validity checks
View instructions Adjust data Enter cell text Lock and spread values to base periods Enter supporting detail Calculate data Enter and preserve formulas
Planning and Smart View

You can work with Planning features when using Smart View. You can open Planning data forms in Excel, and you can work with online data forms while connected to the Planning server or offline data forms for additional flexibility. When you use data forms with Smart View, you have the same functionality as you have with data forms in Planning. You can view form instructions, adjust data, manipulate data by using ad hoc adjustments, lock and spread values to base periods, enter supporting detail and cell text, and launch business rules. The Planning server performs validity checks involving user security, metadata access, and form definition changes in order to synchronize data. The server then saves only incremental changes to the cells that were changed or modified after the data form was opened in Excel.
20-8
Opening Data Forms in Smart View

To open a Planning data form in Smart View, select Hyperion > Forms > Select Form
Opening Data Forms in Smart View

After connecting to a Planning data source, you can select a data form to work with in Excel to enter and adjust data using Smart View. Many functions that you use during data entry in Planning are also available when you work with data forms in Smart View. You have access to the same data forms that you have access to in Planning.
NOTE
Smart View does not support Hyperion System 9 Workforce Planning.
20-9
Navigating Data Forms in Smart View
Toolbar Page List
Point of View Column Headings Data Input Cells
Row Headings
Cells with Supporting Detail Parent Member
Navigating Data Forms in Smart View

After you open a data form in Smart View, you can use the arrow keys to move forward, backward, up, or down. Press Tab to move to the next cell in a row. Press Shift+Tab to move to the previous cell in the row. Press Enter to move to the next cell in a column and Shift+Enter to move to the previous cell in the column. If you want to work with a specific slice of data, you can change the page selections and then click Go in the same manner as you would in Planning. Functions are available from the Hyperion menu, and there are shortcuts on the Smart View toolbar.
20-10
Entering Data in Smart View Using Data Forms

Utilize full Excel functionality. Set up customized areas of the spreadsheet. Add or modify data values. Spread data values. Adjust, copy, and paste data values. Add or view cell text and supporting detail.
Entering Data in Smart View Using Data Forms

You can utilize the full functionality of Excel with Planning data forms both online and offline when you work in Smart View. You can use Excel functionality to view data and text, create formulas, and format data. You cannot modify the structure of a Planning data form, but you can set up usermodified areas on a spreadsheet. This customization is not lost when you refresh the data form or when you open a new Planning data form in Excel. You can define and save numeric analyses and calculations for the data in a Planning data form. In other words, you have greater analytic capability on the fly, especially when data forms are offline.
20-11
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View Entering Data You can add data values by entering them in input cells. You can modify data values by typing over existing values. You can spread values from summary periods to base periods. The same rules apply when you spread values using Smart View as when you use Planning. You cannot use cell locking when you spread data in Smart View. Adjusting Data To adjust values in Smart View, you use the Adjust Data dialog box. Flexible data-entry operators are not available in Smart View. You can increase or decrease values by a percentage or numeric value as well as multiply or divide by a fixed value. In Smart View, you cannot adjust a data value if a cell is read-only or contains supporting detail. If you want to eliminate data from a cell that has a data value, replace the data value with #missing. Another way to replace a data value with #missing is to select the cells that you want to replace with #MISSING and press the Delete key. You can select a range of cells by using the same techniques that you use for data entry in Planning. You can also copy and paste data values in a grid. The rules for copying and pasting apply in all situations in grids except one: If you copy and paste a value with supporting detail, only the valuenot the supporting detailis copied and pasted. Annotating Plan Data You can add cell text to a cell at any level. You can also add supporting detail to build and communicate bottom-up values. You cannot add account annotations or annotate planning units from Smart View. Submitting Plan Data After entering and adjusting data, you need to save your changes in the Planning application. You do this by selecting Hyperion > Submit Data. Data values are updated directly to the Analytic Services database; supporting detail and cell text are updated directly to the Planning application relational database.
20-12
Adding Formulas to Data Forms

You can create formulas
inside or outside data form grids on cells that contain cell text
You cannot create formulas

on read-only cells or cells that are locked on cells that have supporting detail
Formulas are preserved even when you

refresh data forms open saved .xls worksheets in the future expand or collapse rows or columns
Adding Formulas to Data Forms

You can create Excel formulas to manipulate or analyze the data in data forms. You can save the formulas with the Excel workbook so that they are preserved when you use the workbook again. Formulas interact with other functionality in the following ways: You can spread data values using a formula in a summary parent cell. Spreading logic ignores formulas in child cells. For example, you could enter a formula in Q1 whose calculated value is spread over Jan, Feb, and March. However, if you enter a formula in Feb, that cell is ignored when the value for Q1 is spread. If you move a referential formula, its cell references are updated to reflect its new location. If you use the Suppress #Missing Rows feature on a cell that has a referential formula, the cell references are not updated; the cell relationship is absolute, not relative. Planning: Create and Manage Applications 20-13
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View If you create formulas in a data form, you are prompted to save the workbook as an .xls file with the new formulas under the following conditions: You change the current page. You take the data form offline. You select a different data form. You connect to a different data source. You lose temporary access to the formulas even if you save the formulas with the workbook when: You change the current page, data form, or data source. You take the data form offline.
20-14
Calculating Data in Smart View

Hyperion > Calculation Options > Rules on Form
Hyperion > Calculation Options > Business Rules

Calculating Data in Smart View

After entering data in a data form, you need to calculate new totals for parent members. You have the same data calculations options available to you in Smart View as you have during data entry in Planning. You can launch business rules and calculation scripts that recalculate data in Analytic Services. The data form in Excel is updated with the new data. You see the calculation scripts that you have access to listed by plan type. If a runtime prompt is part of a business rule, you are prompted to enter information. After the business rule is executed, the values in the Analytic Services database reflect the results of the calculation.
20-15
Offline Planning Overview

Offline Planning - work with data while not connected to the Planning application Work with Offline MyAnalytics cube Robust support for Web-based Planning functionality, including offline calculations and business rules
Offline Planning Overview

You can work with Planning data forms from remote locations when you are not connected to a Planning server. You can disconnect from the Planning server and work offline and still be able to use comparable online functionality. Working offline, you can enter and save data to the Planning server. For example, you can take data forms offline, enter and adjust data, view instructions, add supporting detail, run business rules, and create formulas to manipulate data. Working offline allows you to take a Planning data form in Excel and establish an impromptu local connection to a data source without being connected to the Planning server. Thus, you can continue to work on plan data and perform what-if scenarios when you do not have access to the Planning server. When you take a data form offline, the Planning server flags the data form status as offline. Data forms associated with a connection are saved locally on your hard drive. By synchronizing the locally saved data with the server, you ensure that the data form uses the most recent information.
20-16
Taking Data Forms Offline
Taking Data Forms Offline

You use the Take Offline Wizard to take data forms offline. To take data forms offline: 1. Select Hyperion > Forms > Take Offline. The Take Offline Wizard is launched. 2. Select the data forms to take offline, and click Next. 3. Select the dimensions and members to take offline. The dimensions and members are those displayed in the Page drop-down lists of the forms you take offline.
20-17
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View 4. Create an offline connection, giving it a unique name, and click Finish.
NOTE
To take a data form or group of data forms offline, you must select them and give them an offline connection name. You can select the offline connection name over multiple Excel sessions. The Download Status window displays the names of the outline, forms, dimensions, and members that are being downloaded for the offline connection. When the download process is complete, the message Forms are successfully downloaded, is displayed. 5. Click OK. 6. Close Excel.
20-18
Working with Planning Offline
Working with Planning Offline

You can work within Excel using the offline connection that you created. Most client-side capabilities, such as viewing form instructions, adjusting data, entering cell text, and adding supporting detail, remain available when you work offline. There are some differences in the capabilities for performing some tasks. For example, to add supporting detail, you can select a range of contiguous cells in a row or column if you are working online. (You cannot select a section of cells that include a combination of rows and columns.) However, in offline mode, to add supporting detail, you can select cells only on a cell-by-cell basis. To work with Planning offline: 1. Launch Excel. 2. Select Hyperion > Connection Manager, and select the offline connection.
20-19
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View 3. Select the data forms and members with which you want to work. 4. Select Hyperion > Submit Data to save the changed data to your computer.
NOTE
Saving data forms using an offline connection saves the changes locally to your computer. If you also save the Excel workbook, you save only the data at the currently selected dimension member combination. You can save data forms in the local data source when you work offline. You have the option of saving a single worksheet or multiple worksheets when you work offline. Whether you are working offline or online, it is recommended that you submit data to the data source so that the server is updated with the latest data from the worksheet. The following rules apply when data is submitted: Dimensions must be displayed in the axis in which they were displayed before the data was synchronized. This stipulation is true for all axes (rows, columns, pages, and points of view). Pages must be displayed in the order in which they were displayed when the form was loaded. The order of the dimensions in the rows or columns can be changed.
NOTE
If some submitted cells are no longer on the data form, only the cells to which you have write access and that exist on the new data form definition are saved.
20-20
Synchronizing Data to the Server
Synchronizing Data to the Server

You can save changed data to the Planning server by synchronizing your data. When you synchronize your data, you can synchronize at the workbook level or at the worksheet level. Synchronization is important because updated data is sent back to the server so that the Planning application reflects the work performed remotely. To synchronize data to the ser ver: 1. Use Connection Manager to connect to the same offline connection. 2. Select Hyperion > Forms > Sync Back To Server to save the changed data to the Planning server. The Sync Back Wizard dialog box is displayed. 3. Log on to the server by typing your login ID and password, and click Next.
20-21
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View 4. Select the data forms whose data you want to save to the Planning server, and click Next. 5. Select the page members to synchronize back to the server, and click Next. 6. Optional: Select to delete offline data and application after synchronization, and click Finish. A message, Sync back to server was successful, confirms that your changed data was saved to the Planning application.
NOTE
If someone else changed data for the same cells, only the most recent data is saved. 7. Click Done.
20-22
Summary
In this lesson, you should have learned to: Describe Smart View Enter, adjust, calculate, and analyze Planning data using Smart View Work with Planning data
20-23
20-24
M O D U L E
8
20
Adding Business Rules
Overview
The aim of this module is to create business rules to perform calculations, and verify their results. You also define runtime prompts, and add them to business rules as well as add actions and formulas to business rules. You can organize your business rules into projects to make locating and maintaining your business rules easier. Lessons in this module include: Creating Business Rules Building Runtime Prompts for Business Rules Adding Formulas to Business Rules
L E S S O N
2 1
21
Creating Business Rules
Objectives
At the end of this lesson, you should be able to: Describe Business Rules and its capabilities Navigate Administration Console to design business rules Create business rules Launch business rules Print business rules
Module 8 Adding Business Rules Lesson 21 Creating Business Rules
Business Rules Overview

Business Rules enable you to: Leverage the power of Analytic Administration Services to create complex calculations Build sophisticated business rules including those which:
Allocate costs among entities Model Revenue Model Expenses for: Employee planning Depreciation planning Selling costs Manufacturing costs
Choose graphical components to build rules Store rules in a central repository where you can organize them into projects
Business Rules Overview

In traditional multidimensional applications, your organization typically requires more complicated calculations to be performed than can be defined within your dimension hierarchies or with member formulas. For these more complex calculations, you can create business rules. Business rules are integrated with Planning and leverage the power of Analytic Services calculation scripts to let you create complex, multistep calculations that are not possible with member formulas. For example, you can calculate aggregated totals and allocate totals based on head count. Business rules can also target specific slices of the database. For example, you could create a rule to copy values for Product Sales, North America 2007 to Product Sales, North America 2008 and increment the values by 10%. Administrators and interactive users use the Administration Console in Analytic Administration Services to create, edit, validate, launch, and maintain business rules and sequences. Sequences group multiple business rules to launch them in a particular order at one time. 21-2 Planning: Create and Manage Applications
Module 8 Adding Business Rules Lesson 21 Creating Business Rules The graphical depiction of components, formulas, and processes makes it easy to construct business rules for your planning application. You can work with macros, variables, and predefined formulas as you set up business rules. As a business rule designer, you can save time by using macros to reuse pieces of business rules in other business rules or macros. You can use variables both when setting up a business rule and when running a business rule. Several formulas are available and can save time in the design of business rules. Business rules are easy to use. Launching business rules can be done by business users from several different places, including from within Analytic Administration Services, the Business Rules Web Launcher, the Business Rules Command Line Launcher, and Planning. Business rules with runtime prompts ensure valid inputs from budget preparers. By enabling the entry of runtime prompts during launching, Business Rules makes a single, centrally created business rule reusable by several users. Business rules are stored in a central location, making them easier to maintain. Business rules can be created, organized, and stored into projects, making locating and updating business rules easier.
21-3
Business Rules Roles
Roles
Business Rules Roles

You set up users and groups, and assign roles to them, in Hyperion System 9 Shared Services User Management Console . After creating a business rule, you become the owner of the business rule, which writes your user name in the Owner attribute field. As the owner of the rule, you can edit and delete the business rule. The administrator must assign launch privileges to the rule for the particular database location so that users can launch the rule.
21-4
Module 8 Adding Business Rules Lesson 21 Creating Business Rules Business Rules roles include Administrator, Interactive User, and Basic User. The following table summarizes Business Rules roles and typical tasks performed:
Role Administrator Tasks That Can Be Performed A user or group who has the role of Administrator can do any of the following tasks: Create, launch, edit, validate, and manage business rules, sequences, macros, variables, and projects Assign access privileges to business rules, sequences, macros, variables, and projects Provision users, groups, and roles Set up the repository and log file Interactive User A user or group who has the role of Interactive User can do any of the following tasks: Create, launch, edit, validate, and manage business rules, sequences, macros, variables, and projects Assign access privileges (with the exception of the ability to launch business rules, which can only be assigned by an administrator) to business rules, sequences, macros, variables, and projects Basic User A user or group who has the role of Basic User can do any of the following tasks: Launch business rules and sequences to which the user has access View business rules and sequences to which the user has access View all variables and macros
Prerequisites for Accessing Business Rules

You log on to Administration Console, a component of Analytic Administration Services, to create, edit, validate, launch, and organize business rules. You need to ensure that Shared Services, the Analytical Administration Services Server, the Analytic Server, and the Planning application server are all running before you launch Administration Console. You log on to Administration Console and use variables, macros, commands, functions, formulas, and actions to create a new business rule. You can launch business rules directly from within Administration Console to execute your complex calculations. In addition, you can launch rules from Planning.
21-5
Navigating Business Rules

Organizes business rules, sequences, macros, and variables into logical groupings of information.
Lists all objects in the Business Rules repository including business rules, sequences, macros, and variables.
Lists all projects you use to organize your calculations.
Lists the properties of the client and server.
Access and work with Business Rules nodes. Create and edit graphical business rules. View the database outline.
Navigating Business Rules

You navigate Administration Console to build business rules. The type of information you see on the screen depends on the selected tab.
Components of Enterprise View Tab

After logging on to Administration Console, you can expand the nodes under the Business Rules node to view its contents. Business Rules nodes include: My Projects Repository View Administration
21-6
Components of BR Language Tab

Actions
Formulas
Components of BR Language Tab

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

Select the BR Language tab to edit an existing rule or to create a new rule. The BR Language tab consists of the navigation frame and the Rule Editor. From the navigation frame, you select actions and formulas to include in your business rule. You use the Rule Editor to associate an Analytic Services or Planning outline with your business rule and to set up the details for your business rule.
21-8
Business Rules Creation Process

Ensure that you do the following: Do not include upper level members that you do not really need. Calculate portions of the database on which your calculation is dependent. Make your last step to aggregate data affected by the rule.
N. America East West Central South Sales 200 100 20 30 50 50% 10% 15% 25% % of Sales
Business Rules Creation Process

Before creating business rules, you need to have an understanding of the calculations that you want to set up. After you determine the requirements for your calculations, you use the navigation frame to access the business rules repository.
Setting a Plan for Developing Business Rules

In order to plan for creating business rules, you need to consider the following: Familiarize yourself with the database dimensionality and outline structure Know where data is stored in the database, how data is stored and aggregated, and at what level the data gets loaded into the database Verify the order in which calculations will take place and the sequence of business rules Verify any key assumptions used to drive calculations Planning: Create and Manage Applications 21-9
Module 8 Adding Business Rules Lesson 21 Creating Business Rules In preparation for building business rules, ensure that you do the following: Do not include upper-level members that you do not really need. For example, if you include Q1 to be calculated by your formula, the values calculated by the business rule are overwritten when the data is aggregated. Calculate portions of the database on which your calculation is dependent. For example, to calculate sales for each child of North America as a percentage of total sales, you must first aggregate data to determine the value for sales for North America. Make your last step to aggregate data affected by the rule. Since the business rule changes the value of level 0 members, the upper-level members need to be calculated to reflect the latest data values.
21-10
Launching the Rule Editor

Create a new rule Select an outline
2 3 5
Launching the Rule Editor

To create a business rule, you launch the Rule Editor from the Enterprise View tab in the navigation frame. After expanding the Business Rules and Repository View nodes, you can right-click the Rules node to create a new rule. You navigate the tabs on the Rule Editor to build business rules. If you are creating a new rule, you are initially placed on the Graphical tab. Associate a database outline to refer to as you create the business rule. Next, specify global properties, including how formula components are calculated and what dimensions are common to all the formula components (also known as the global rule range).
NOTE
You must select a Planning outline if you want to set up your business rule to work with Smart Lists.
\
21-11
Module 8 Adding Business Rules Lesson 21 Creating Business Rules On the Overview tab, select a choice for intelligent calculation.
NOTE
Intelligent calculation calculates only the data blocks that need to be calculated, making the calculation more efficient. Keep the default setting (Off) if you want to calculate all data blocks. After setting global properties, you can set a range for each dimension by using the Range tab. You can either type a value in the Selected Values text box or click the magnifying glass icon to select members and variables. To continue building graphical business rules: 1. Add actions and formulas to the Graphical tab by doing one of the following: Select the BR Language tab and drag actions and formulas onto the Graphical tab Right-click anywhere inside the Graphical tab to insert actions and formulas onto the Graphical tab 2. Set up the details for each action and formula, including selecting members for each component to set up calculations in both the source and the destination. 3. Optional: Set up local variables on the Local Variables tab. 4. Write a summary of what this business rule is used for on the Doc tab. 5. Type the name, description, and owner for the business rule on the Properties tab. 6. On the Location tab, select the location for which the calculation can be run. You can select a specific database outline or select all locations to enable users to run the business rule against any database. 7. As the administrator, you can grant or remove access to a business rule on the Access Privileges tab. If you are the owner, or you have been granted Modify access to the business rule, you can grant or remove editing privileges for the business rule. 8. To save the business rule, click Save.
NOTE
You must save the business rule before you can validate or launch that rule.
21-12
Module 8 Adding Business Rules Lesson 21 Creating Business Rules 9. Click Validate to validate the rule. 10. Optional: Launch the business rule.
21-13
Adding Actions to Business Rules
Aggregate Data Action
Calculation Options and Methods Value type of User defined can be specified through Member Selection
Member Selection button
Adding Actions to Business Rules

While building your graphical business rule, you can choose to include the actions Aggregate Data, Copy Data, Clear Data, and Create Blocks to your rule. All of these actions can be added by selecting the BR Language tab and either double-clicking or dragging the action onto the Graphical tab. You can also select to add an action to business rules by right-clicking in the Rule Editor window. Adding the Aggregate Data Action There are several choices to set up the Aggregate Data action. On the Overview tab, you choose a calculation option and method.
21-14
Module 8 Adding Business Rules Lesson 21 Creating Business Rules Calculation options include Calculate Entire Database, Calculate Entire Database with Two Pass Calculation, and Calculate Portion of Database Specified Below, the default selection. To calculate a portion of the database, you specify the section you want to calculate by selecting a value type. If you selected User Defined for the value type, then you select members to be included in the calculation. Calculation methods include Aggregate Missing Values in the Database, Aggregate Data Up to Local Currency, Optimize the Calculation of Formulas on Sparse Dimensions, and Use Calculator Cache. After you make your selections on the Overview tab, you can optionally use the Range tab to restrict the aggregation to a range of members and variables in one or more dimensions. Adding the Copy Data Action You use the Copy Data action to copy data from one part of the database to another in the same database. Furthermore, you can perform mathematical operations on the copied data. For example, to create your budget for the current year, you can start with a copy of last years actuals and increase those values by a percentage to determine your starting point for your budget. To finish building the business rule: 1. On the Overview tab, enter a name in the Name text box. (The default name is Destination.) 2. If blocks do not exist and you want to create them as part of the copy business rule, select Create Blocks During Copy.
NOTE
If you do not choose to create blocks within the Copy Data action, and data blocks do not exist in the destination but they do exist in the source, no data will be copied for those members. 3. Select values in the Selected Values text box for the target values or destination. 4. Select values in the Selected Values text box for the source.
NOTE
If
If the source and destination are always the same, you can make the selection for the destination, and the source is automatically inherited from the destination.
21-15
Module 8 Adding Business Rules Lesson 21 Creating Business Rules 5. To apply a calculation, select Apply Calculation. An operator and number component are added to the formula. 6. Select an operator: addition (+), subtraction (-), multiplication (x), or division (/). 7. Select the calculation to apply. You can type a specific number, select a variable, or select values for each available dimension. 8. Click Save. Adding the Clear Data Action You may want to clear data in a destination before applying an action or formula. You use the Clear Data action to clear data from a specific portion of the database. You can choose to clear individual cells or an entire block. Clearing data sets the data value to #MISSING. Adding the Create Blocks Action You may want to ensure that blocks exist for sparse member combinations in a specified slice of data. Remember that in order to store the result of business rule calculations, a block must first exist before executing the calculation. You can use the Create Blocks action to add blocks to the database. Before adding the Create Blocks action, give some careful thought to whether it is really a necessary step and for which portions of the database it is necessary. There is a potential for a large increase in the database size. To assist you in your analysis, you can view a calculation of the block size and maximum possible blocks that would exist for the specified data slice after the calculation is run.
NOTE
You cannot use Create Blocks with Dynamic Calc or Label Only members.
21-16
Selecting Members for Business Rules
4 All descendants of North America are included with the exception of Central and its descendants
1 3 6
Selecting Members for Business Rules

To set up business rules, you can use member selection to select members used in global ranges, action, and formula components. You can select members for business rules using the Multiple Select dialog box. On the Member tab, you can expand the dimension outline and select members to include. You use the drop-down list below the arrows to select members based on their relationship to a member. Next, you use the right or left arrow to move the selection to or remove it from the Selected box. You use the down or up arrow to move the selection to or remove it from the Excluded box. In the example shown on the slide, you select Entity as your dimension and you want to include all the descendants of North America except for those in the Central region. In the Selected text box, you select to include the descendants of North America, while in the Excluded text box you select to exclude the descendants, inclusive of Central.
21-17
Module 8 Adding Business Rules Lesson 21 Creating Business Rules To select some members and exclude other members: 1. Select the member to include. 2. From the drop-down list, select the relationship. 3. Click the right arrow. The selection is moved to the Selected box. 4. Select the member to exclude. 5. From the drop-down list, select the relationship. 6. Click the down arrow. The selection is moved to the Excluded box. 7. Click OK. The Rule Editor window is displayed with your selection.
21-18
Assigning Access to Business Rules

1 2
To assign access to a user or group: 1. Select the Access Privileges tab. 2. Click Add. 3. From the drop-down list, select a privilege. 4. From the drop-down list, select a location. 5. Select the user or group. 6. Use the arrows to move users and groups into the Selected box. 7. Click OK. 8. Click Save.
3 4
Assigning Access to Business Rules

You use the Access Privileges tab to grant or remove access to business rules. Access privileges determine which users and groups can validate, launch, or modify business rules and are assigned using the Privilege drop-down list. You can also specify whether users can run the business rule against a specific database or against all databases during validation and launch. You select valid locations from the Location drop-down list.
21-19
Module 8 Adding Business Rules Lesson 21 Creating Business Rules Access privileges must be added one at a time. If you want to grant two different privileges, such as Validate or launch and Modify rule repository objects to the same user or group, you need to do this in two separate actions. However, you can grant the same access to more than one user or group at the same time by using the Shift or Ctrl key to select multiple users or groups.
NOTE
Before you assign access privileges to users or groups, you need to provision those users or groups in Shared Services User Management Console.
21-20
Launching Business Rules

You can launch business rules from: Analytic Administration Services Console Planning
Analytic Administration Services Console
Planning
Launching Business Rules

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

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

If a rule is associated with a data form, do one of the following: From the view pane, click the rule, and then follow the steps for launching a rule from the Edit menu From the Edit menu, select Launch Rules To launch the rule from the view pane:
To launch the rule from the Edit menu: 1. Select a Rule 2. Click Launch 3. Click Close 1
2
Launching Business Rules from Planning Data Forms

After you create business rules, users can launch rules to which they have access. Launching business rules can be done from Planning. The capability to launch rules within Planning is convenient for planners who are already doing other work such as data entry. Data form designers can associate business rules with data forms. If a business rule is associated with a data form, business users can launch the rule from within the data form. To launch a business rule, select a rule and click Launch. Business users can also launch business rules in Planning with context-sensitive menus. To launch a business rule with a menu, select a data cell and right click to launch the calculation. The business rule may prompt you to enter information, called a runtime prompt. After you successfully launch a business rule, the data is updated in the Analytic Services database. If you are working on a data form when you launch the business rule, you can refresh the data form to view the updated or new data. Planning: Create and Manage Applications 21-23
Launching Business Rules from Planning Tools Menu

If a rule is not associated with a data form, then: 1. From the Tools menu, select Business Rules 2. Select a Plan Type 3. Select a Rule 4. Click Launch
2 1
Launching Business Rules from Planning Tools Menu

You can also run business rules which are not associated with the data form. After you select Tools > Business Rules, the list of business rules for which you have access is displayed. You can select a business rule and launch it. Refresh the data form after the business rule calculation runs to display the updated results.
21-24
Printing Business Rules

Header
Business Rule Properties Business Rule Documentation
Source
Valid Locations Access Assigned

Printing Business Rules

To document the contents of business rules, you can print the information contained in business rules from the Administration Console of Analytic Administration Services. You can use the Print Preview option to view the contents of the report on your screen. To print a business rule, first open the rule in the Rule Editor. Then, from the File menu, you can select to preview or print the report.
21-25
Summary
In this lesson, you should have learned to: Describe Business Rules and its capabilities Navigate Administration Console to design business rules Create business rules Launch business rules Print business rules
21-26
L E S S O N
2 2
Building Runtime Prompts for Business Rules
22
Objectives
At the end of this lesson, you should be able to: Describe runtime prompts Create runtime prompts
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
Runtime Prompts Overview

In setting up business rules you can: Enter variables that are resolved when a user launches a rule Include default values to be used in runtime prompt Set up limitations so that values are within a range you define
Runtime Prompts Overview

You can set up business rules to include variables. Variables assume defined values. If you set up a variable to be a runtime prompt type, then business users are prompted at runtime to supply a single member, multiple members, a string, a number, or a dimension. The value is then used to calculate the business rule. For example, if you have a variable named CurrMonth, and the value May is supplied at runtime, then May is substituted for CurrMonth.
22-2
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules You can include default values in runtime prompts. You can set up default values when you create a business rule so that no matter where the business rule is run, a default value that you specify is used for the calculation. You also can set whether the default members on the runtime prompt window match the members selected in the page and POV axes.
NOTE
To set the default members for a business rule using runtime prompts to the page and POV axes on a data form, you navigate to the Business Rules tab when creating that data form. You then select to set the properties for that business rule, indicating that the defaults are taken from the page and POV axes. To ensure that the user input is acceptable, you can set up limitations for the runtime prompt so that users supply a value within a defined range.
22-3
Adding Runtime Prompts

Runtime Prompts as Global variables Runtime Prompts as Local Variables
Adding Runtime Prompts

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

You create global variables to be used as runtime prompts from the Enterprise View in the Global Variable section. You create or edit global variables by expanding the Business Rules and Repository View nodes and right-clicking Global Variables. To set up global variables: 1. From the Associated Outline drop-down list, select an outline. 2. On the Variable tab, type a name and a description. 3. From the Type drop-down list, select a type: Member or Members: Either a specific member or a range of members from the dimension you select Dimension: A dimension to be used for member selection
22-5
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules String, Integer, Real, or Percent: A text string, an integer, (the default selection), a real number, or a percentage StringAsNumber: A text string (Available only if you selected a Planning outline.) DateAsNumber: A date (Available only if you selected a Planning outline.) 4. Optional: Select the Smart List check box and enter the name of the Smart List in the Smart List text box.
TIP
You can search for a Smart List name by clicking the lookup button. 5. If you selected Member or Members in the Type text box, select the dimension from which you want users to select a member or members. 6. Optional: In the Limits text box, perform one of the following actions: If you specified Member or Members in the Type drop-down list, either type the names of the members in the Limits text box, or use the lookup button to search for a range of members against which users can validate the variable. If you specified Real, Integer, or Percent, type minimum and maximum values in the Limits text box. If you specified a Smart List, either enter the limits for the Smart List, or use the lookup button to select limits.
NOTE
If you selected Dimension or String for the type, the Limits text box and lookup button are disabled. 7. Optional: Select Allow #Missing to enable business users to specify #Missing or blank as the default value for the variable.
NOTE
The Allow #Missing option is available only when the type is numeric. 8. If you want to provide a default value, type or select a value in the Value text box.
NOTE
If you selected Smart List, you must enter a default value for the Smart List.
22-6
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules 9. In the Usage Type drop-down list, select Run-time prompt. 10. In the Prompt String text box, type the text of the prompt to be displayed when the business rule is launched.
NOTE
You can include unlimited text as the runtime prompt text; however, the runtime prompt text that is displayed is truncated. The display limits vary depending on the application that displays the runtime prompt. 11. Optional: Select Do not save value entered during validation and launch as the default value. Each time the runtime prompt is executed, the default value from the Default Value text box is used rather than the last value that the business user entered. 12. On the Properties tab, type the name of the variable owner, and specify whether the variable should be locked to prevent users from opening it for editing. 13. On the Access Privileges tab, grant or delete access to the variable.
NOTE
If you are the owner, or have been granted Modify access to the variable, you can grant users editing privileges for the variable. 14. Click Save.
22-7
Applying Runtime Prompts as Global Variables
Applying Runtime Prompts as Global Variables

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

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

In addition to setting up the type of input you want users to provide, you can focus user input, narrowing the scope to acceptable values. For example, in your runtime prompt string, you prompt users to enter a value between 1 and 10. You select an integer for the type of input, but you want to ensure that the value entered is within your acceptable range. Therefore, you set limits by indicating both minimum (1) and maximum (10) values in the Limits text box. You can also assign limits for member selection. For example, in your runtime prompt string, you prompt users to select a North American entity. You select Member or Members for the type of input. To ensure that the entity or entities selected is within your acceptable range, you either enter the names of the members in the Limits text box or use the lookup button to select a range of members against which users can validate the variable.
22-10
Summary
In this lesson, you should have learned to: Describe runtime prompts Create runtime prompts
22-11
22-12
L E S S O N
2 3
23
Adding Formulas to Business Rules
Objectives
At the end of this lesson, you should be able to: Identify the four formulas included with Business Rules Add formulas to business rules Manage business rules
Module 8 Adding Business Rules Lesson 23 Adding Formulas to Business Rules
Business Rules Formula Overview

Enter destination and source details for each part of a formula. Narrowly define the business rule range by setting up the range of members, functions, or runtime prompts.
Add additional sources, calculation functions, numeric operands, operators
Specify certain criteria that must be met before the business rule calculates data.
Business Rules Formula Overview

You can set up formulas to calculate data. You can choose from four formulas to insert into your business rules: Pro Ratio, Units-Rates, Variable, and Custom. Each formula has a Formula tab, a Formula Range tab, and a Data Condition tab. Typically, you first specify the destination and sources for the calculation. Next, you specify the formula range. Finally, you specify data conditions under which the formula is calculated.
23-2
Building Formulas for Business Rules
Units-Rates formula is added to Graphical tab
5 2
Building Formulas for Business Rules

Formulas can be added by selecting the BR Language tab and dragging the formula to a location in the business rule on the Graphical tab. You can also select to add formulas to business rules by right-clicking in the Rules Editor window. After you select a formula, you set up the components of the formula.
23-3
Components for Pro-Rata Ratio Formulas

Total Headcount for the company is 1,000 people Department 1 has 500 employees Pro-Rata Business Rule Calculation Advertising Expense Allocation proportionally based on headcount Department 1 $50,000
(500/1000) * $100,000 =
$100,000 Advertising Expenses
Department 2 has 300 employees
(300/1000) * $100,000 =
Department 2 $30,000
Department 3 has 200 employees
(200/1000) * $100,000 =
Department 1 $20,000
Components for Pro-Rata Ratio Formulas

Pro-Rata Ratio formulas calculate data based on the results of a ratio of values. You can use the Pro-Rata Ratio formula for profitability analysis, or for budgeting and planning purposes to allocate expenses to various cost centers based on an inferred level of usage. For example, consider that you have advertising expenses of $100,000 that you want to allocate to various departments. You decide to use headcount as the criterion to allocate the appropriate portion of the expense to each department. Several components make up this allocation calculation. First, you determine the total advertising expenses. Next, you calculate the total headcount for your organization and the headcount for each department. To obtain the total headcount, you use the Aggregate Data action to calculate the headcount account. You use total headcount for the denominator in the first part of your pro-rata ratio calculation. You use the headcount for each department as the numerator. Finally, you multiply the ratio of headcount per department divided by total headcount by the total advertising expense to calculate the allocated expense per department based on headcount.
23-4
Setting Up Pro-Rata Ratio Formulas

Destination Advertising Expense Allocation Source Total Advertising Expense Pro-Rata Ratio Component . .
Select Numerator
Select Denominator
The destination is the portion of the database where you plan to store the results of your calculation. In the source, you select the portion of the database that you want to reference to obtain data. You set up the pro-rata ratio component to reflect the type of calculation you want to make.
Setting Up Pro-Rata Ratio Formulas

After you determine the components of the pro-rata ratio calculation, you can use the Rule Editor to set up your calculation. You set up a destination, a source, and the prorata ratio component. You can choose from the following types of Pro-Rata Ratio formulas:
Formula Type User Defined % to Total Description Calculates data based on the result of a ratio of defined values. Calculates data based on the total value of a selected dimension. The total value is stored in the generation 1 member or top member of the dimension. The default calculation is Destination = Source X (% to Total).
23-5

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

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

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

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

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

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

5 6 2
7 1
3 4
Managing Business Rules

Business rules are stored in a single repository. You can create projects to organize business rules, sequences, macros, and variables into logical groupings within the repository. For example, you might group business rules into projects to help identify and manage which rules are used for each Analytic Services server, or you might group business rules by type, such as grouping your rules by the type of formula used. You can use descriptive names for your projects to make finding the business rules and other objects that belong to them easier. In order to add a project, you select those business rules, macros, variables, or sequences to include in the project. The members that you select for the project are listed on the Contents tab. On the Project Info tab, you enter a name, description, and owner for the project. You can also indicate whether to lock the project from editing. Finally, you assign access to the project and define the locations for this project for which users can validate or launch business rules and sequences.
23-12
Summary
In this lesson, you should have learned to: Identify the four formulas included with Business Rules Add formulas to business rules Manage business rules
23-13
23-14
M O D U L E
9
23
Managing the Planning Process
Overview
The aim of this module is to manage the planning cycle through process management. You also copy data between versions and use the Copy Data task to seed the start of the next planning cycle. You create task lists to guide budget preparers through the planning cycle. Lessons in this module include: Managing the Approval Process Creating Task Lists
L E S S O N
2 4
24
Managing the Approval Process
Objectives
At the end of this lesson, you should be able to: Explain the planning process Define a planning unit Manage the review cycle for a planning unit Copy data between versions Copy data
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
Process Management Overview

Use process management to promote, review, sign off, reject, and approve planning units.
Promote
Review
Sign Off
Approve
Reject
Process Management Overview

Planning process management enables you to track the progress of your budget, identify problems in the review process, view status information, quickly identify ownership of budget planning units, and change the budget status. The Manage Process function is designed to reduce budget cycle time by enabling you to perform the following key actions: Approve a planning unit from any process state Follow an approval path that is independent of organizational structure Emphasize exceptions and problem areas Provide audit information through annotations and process status Annotate at each pass through the review process Establish accountability through ownership
24-2
Planning Units
Planning Unit =
Scenario : Budget
Version : Draft1
Entity : California
Planning Units
Planning tracks budgets by planning units, which consist of a scenario, a version, and an entity. Scenarios and versions are the basis of the planning review cycle. Entities provide planning data for a particular scenario and version. When you access the process management feature of Planning, you select a scenario and version for which you want to view the status. You then see a list of the entities to which you have access. You can track the status of each entity as it moves through the review cycle from first pass to approval. After planning data is submitted and approved for all entities, the planning cycle is complete for the scenario and version.
24-3
Planning Units and Process States

Each planning unit completes this process.
Not Started Start First Pass Promote Under Review Promote Under Review Sign Off Signed Off
Reject Not Signed Off
Approve
Approved
Planning Units and Process States

Planning units pass through a number of process states during the review cycle. A planning unit is always in one of six process states:
State Not Started First Pass Description The initial state of all planning units. The budget administrator initiates the review process by using the Start action. The first state for planning units selected for the budget review process. Planning units have no owner during First Pass. Any user with data access can enter data into and promote a planning unit in the First Pass state. The state of a promoted planning unit. This state signifies that a planning unit is being reviewed by someone in the organization. Only the current owner or the budget administrator can modify data or perform an action on a planning unit that is in the Under Review state.
Under Review
24-4
State Signed Off Description The state of a planning unit that was signed off. Only the current owner or the budget administrator can modify data or perform an action on a planning unit that is in the Signed Off state. Ownership does not change when a planning unit is signed off. The state of a planning unit that was rejected. The current owner or the budget administrator can modify data or perform an action on a planning unit that is in a Not Signed Off state. The state of a planning unit that was approved. After a planning unit is approved, a budget administrator becomes the owner of the planning unit. Only the budget administrator can modify data or perform an action on a planning unit that is in an Approved state. After all planning units are approved, the budgeting cycle is complete.
Not Signed Off
Approved
24-5
Reviewer Actions
Start Status Not Started First Pass Under Review Under Review Under Review Under Review
Reviewer Action Start Promote Promote Sign Off Reject Approve
End Status First Pass Under Review Under Review Signed Off
Current Owner Everyone with rights First owner New owner Same owner
Not Signed Off New owner Approved Administrator
Reviewer Actions
The action a reviewer performs on a planning unit changes the status of the planning unit, as summarized in the graphic in the slide.
24-6
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process The following table describes reviewer actions:
Start The Start action changes the state of the planning unit from Not Started to First Pass. Any user with Write access to the planning unit data can modify data during the First Pass state. Only budget administrators can start a planning unit. The Exclude action excludes a planning unit from the review process even after the planning unit is started and moved through several iterations. When you exclude a planning unit from the review process, all annotations and history associated with the planning unit are discarded. The planning unit status is returned to Not Started and the owner is set to No Owner. Only budget administrators can exclude a planning unit. The Promote action submits the plan data to a reviewer for review. The user to whom you submit the planning unit for review becomes the owner of the planning unit. After you promote a planning unit, its status changes from First Pass to Under Review. When a planning unit is under review, you can no longer enter data for the planning unit unless you are the owner or the budget administrator. The Sign Off action allows a reviewer to sign off a planning unit without promoting it to another user for review. This action changes the status of the planning unit from Under Review to Signed Off.This feature is useful when you are reviewing several planning units, and you want to promote them as a group for review. The Reject action returns the planning unit to its original owner or a new owner for further adjustments prior to being approved. This action changes the status of the planning unit to Not Signed Off. The Approve action indicates that the planning unit passed through all required levels of review and that the planning cycle for the unit is complete. When a planning unit is approved, its status changes from Under Review to Approved, and the budget administrator becomes the owner. Only the budget administrator can modify data for a planning unit after it is approved. Typically, a planning unit is approved only once, but an administrator can reject a previously approved planning unit if necessary.
Exclude
Promote
Sign Off
Reject
Approve
24-7
Impact of Entity Hierarchy on the Review Process

*
Promote, Reject, Sign Off, or Approve Parent All childrens statuses are automatically updated to Under Review, Not Signed Off, Signed Off, or Approvedthe same as their parents.
= = =
= * * *
Promote, Reject, Sign Off, or Approve All Children
The parents status is automatically updated to Under Review, Not Signed Off, Signed Off, or Approvedthe same as its childrens.
Impact of Entity Hierarchy on the Review Process

The parent-child relationships between entities affect the movement of entities through the review process. The following rules apply: When you promote or reject a parent, its children are automatically promoted or rejected, unless they are in the Approved state. The owner selected for a parent becomes the owner of the children. When you approve a parent, its children are automatically approved. After all children of a parent are promoted, the parent is automatically promoted to the same owner.
24-8
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process After all children of a parent are signed off, the parents status automatically changes to Signed Off.
NOTE
You cannot change the status of a parent if the children of the parent are owned by different users. If the children of a parent are promoted to different users or signed off by different users, the parent has no owner, and its status can be changed only by the budget administrator.
24-9
Managing the Review Cycle for Planning Units

File > Workflow > Manage Process Start or exclude planning units Change or view the status of planning units Identify the ownership of or assign new ownership for planning units Add and view any annotations associated with planning units View the history of planning units
Managing the Review Cycle for Planning Units

You manage the review cycle for planning units on the Check Status and Manage Process page. What is shown on the Check Status and Manage Process page depends on your user type: administrator, interactive user, or planner. As an administrator, you see all planning units in the current application organized in a hierarchical form. You can expand and collapse parent members to view their children. You can start or exclude planning units, view status and owner, view or add annotations, and view history, as well as perform any reviewer actions under the Change Status option. Interactive users and planners see the planning units to which they have read or write access. They can only view status and owner, view or add annotations, and view history. Interactive users and planners can promote a planning unit if it is in the First Pass state. They cannot perform actions on planning units that are not in the First Pass state unless they own the planning unit.
24-10
Starting or Excluding Planning Units
1 Select the scenario and version for your planning unit.
Choose to start or exclude the entity for your planning unit.
Starting or Excluding Planning Units

After a scenario and version are selected, the members of the Entity dimension become available for processing. As the budget administrator, you can choose between tree view (hierarchical) and flat view to display entities. The Check Status and Manage Process page shows the plan cycle status, the process status, and the current owner of planning units for the selected scenario and version. The plan cycle status is visible only to budget administrators. The Start and Exclude columns contain option buttons that enable you to either begin the review process or remove an entity from the review process. Start and Exclude change the process state of the affected planning unit. Selecting Start changes the state to First Pass, whereas selecting Exclude reverts the state to Not Started.
24-11
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process Starting the Planning Cycle As the budget administrator, you begin the review process by selecting a planning unit and starting it. You can choose to start all entities or a subset of entities for a scenario and version. When the Entity list is hierarchical and you start a parent, all children of the parent entity are also started. Excluding Planning Units As the budget administrator, you can exclude a planning unit from the review process even after the planning unit is started and moved through several iterations. When you exclude a planning unit from the review process, all annotations and history associated with the planning unit are discarded. The planning unit status is returned to Not Started and the owner is set to No Owner.
24-12
Checking the Status of Planning Units
Select the Details link to view the details of a planning unit.
Checking the Status of Planning Units

The Process Status column reflects the stage of a planning unit as it moves through the budget review process. Process states are changed when a review action is taken on a planning unit.
24-13
Viewing the Details of Planning Units
Select Change Status to perform a reviewer action on a planning unit.
Viewing the Details of Planning Units

You navigate to the Details page by clicking a Details link on the Check Status and Manage Process page. From the Details page, you can complete the following tasks: Check the status of a planning unit Add or view annotations for a planning unit Change the status of a planning unit
24-14
Changing the Status of Planning Units
Select the next reviewer / owner.
1 Select a reviewer action to perform on the planning unit. 3 Enter an annotation regarding your action.
Changing the Status of Planning Units You use the Change Status dialog box to select a reviewer action and the next reviewer to move your planning unit to the next step in the process management cycle. You can also add an annotation regarding the action you are taking for the next reviewer. Actions Actions are the operations available to change the status of a planning unit and direct its movement through the budget review process. The options vary depending on the current status of the planning unit.
24-15
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process The following table summarizes the actions available based on a planning units status:
Planning Unit Status First Pass Under Review Actions Available Promote Approve Promote Sign Off Reject Approve Not Signed Off Promote Sign Off Reject Approve Signed Off Promote Reject Approve Approved Reject (budget administrators)
Next Owner Select the next reviewer in the process management cycle based on the action selected. Only individuals with Read or Write access to the planning unit are available for selection. Annotate Annotations associated with a planning unit provide guidelines to planners. You can also add annotations to explain to budget reviewers the assumptions that you made in the plan. You must have a minimum of Read access to the planning unit to view or add an annotation.
24-16
Printing Planning Unit Annotations

Administration > Reporting > Planning Unit Annotations
Printing Planning Unit Annotations

As the budget administrator, you can check the current status of planning units by creating a report on all planning unit annotations for a selected set of scenarios, versions, and entities. You set the options for creating a PDF file that reports planning unit annotations. Some points to keep in mind when creating a planning unit annotation report: The title, author, date, and annotation text of the planning unit are automatically displayed. Annotation text, not data that may be associated with the planning unit, is displayed. Planning unit annotations are displayed chronologically, with the most recent entry displayed first.
24-17
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process The report includes the following information about the planning unit: Name of the application Selected set of scenarios, versions, and entities Planning unit title and status Date of origin Author Content of the annotation When you create the report, you can select the following report options: ScenarioAll or Custom (select by name) VersionAll or Custom (select by name) EntityAll or Custom (select by name) Process Status - First Pass - Under Review - Approved - Signed Off - Not Signed Off
24-18
Copying Data Between Versions

File > Workflow > Copy Versions
Copying Data Between Versions

You use the Copy Versions task in the Workflow section of the File menu to copy data from one version of a scenario to another version within the same scenario. When you copy data for a version, you can select the entity for which you want to copy data. When you copy data to a target version, the parent-level entities are available to be copied. When you copy data to a bottom-up version, level 0 entities are available. For example, you can create a First Pass version and copy data for some or all of the entities in that version to a Second Pass version. Thus, you quickly create a starting point for the Second Pass version.
NOTE
When you copy a version, data for all years, accounts, and periods for the source version are copied to the destination version. Be sure that you do not inadvertently overwrite data for prior years.
24-19
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process When you copy versions, you have the option to copy the account annotations and supporting detail for the planning units. The Copy Versions task does not perform the following tasks: Create an entry in the planning unit history Copy or change planning unit status Copy or change planning unit ownership
NOTE
Do not stop or load another Web page until the Copy Versions process is complete. If you stop or load before the process is complete, you cannot verify that the copy process has been completed successfully. If you want to create a copy of your plan so that you can compare it to the approved version, ask the budget administrator to set up a personal bottom-up version for you. Before you promote your data, you can copy it (using Copy Versions) to your personal version. This gives you a record of the data before you promote it. You can use the copy versions option if you want to create: A copy of the data for your own records. For example, you could use the copy as a baseline to compare against future versions of data. A starting point for subsequent bottom-up versions.
24-20
Copying Data
Administration > Copy Data
Copying Data
When you copy data from one version to another for the same scenario and entities, you can select the option to include supporting detail. As a budget administrator, you can also support the planning effort by using the Copy Data command to copy all relational data and data values, including supporting detail, from one dimensional intersection to another dimensional intersection. For example, you can copy Budget, FY07, Final to Forecast, FY08, First Draft. You can also copy data from FY07 to FY08 to help planners prepare a budget, or you can copy data from one business unit to another.
24-21
Summary
In this lesson, you should have learned to: Explain the planning process Define a planning unit Manage the review cycle for a planning unit Copy data between versions Copy data
24-22
L E S S O N
2 5
25
Creating Task Lists
Objectives
At the end of this lesson, you should be able to: Define task list capabilities Navigate task lists in Basic and Advanced modes Create task lists Assign access to task lists Validate task lists Report on task lists
Module 9 Managing the Planning Process Lesson 25 Creating Task Lists
Task Lists Overview

Manage and guide users through the planning process Navigate using a step-by-step wizard in Basic mode Consist of one or more tasks
URL Task Data Form Business Rule Workflow Descriptive
Created by administrators or interactive users
Task Lists Overview

Task lists provide a powerful method of managing and guiding budget preparers through a planning process by providing lists of specific activities to complete within and outside Planning. Your organizations plan or forecast may require budget preparers to perform multiple activities, some of which may be performed infrequently. Task lists provide guidance in completing these activities. Task lists guide budget preparers by taking them through a step-by-step wizard. Not only are individual steps mapped out with instructions, but the sequence and due dates of steps are identified as well. As the budget administrator, you and interactive users can create task lists for a single user or group of users. Examples of tasks include reviewing instructions, entering data in appropriate data forms, running required business rules, using process management to submit numbers for approval, and running reports to review information.
25-2
Module 9 Managing the Planning Process Lesson 25 Creating Task Lists Depending on how you set up tasks in the task list, you can view due dates, alerts, and instructions. If you set up due dates and alerts, you provide a visual cue for the budget preparers to see their progress in completing tasks. Due dateA task can display a due date that shows when it must be completed. AlertsA task can e-mail an alert, a visual cue, about your progress in completing tasks: - GreenThe task is on schedule; the due date is not yet approaching. - YellowThe task is approaching the due date. - RedThe task is overdue; the due date has passed, but the task is not complete. InstructionsA task can include instructions. You can click the View link to view the instructions. If you set up e-mail alerts, the budget preparers receive e-mail reminders that help them keep track of their tasks. Depending on how the e-mail alerts are set up, e-mail messages remind the budget preparers of tasks that are approaching their due date or those that are past their due date. You also determine the timing and frequency of messages. After budget preparers complete the requirements for a task, they can mark the task as complete; the alert changes to a date stamp that shows the date and time of completion.
25-3
Navigating Task Lists

Basic mode: Select View > Basic Mode. Select task list from quick launch list. Focus on your predefined tasks in a task list page. Navigate between tasks using the task list wizard. Advanced mode: Select View > Advanced Mode. Access other Planning features while you work with tasks. View task lists assigned to you. View the status of the tasks and any instructions included with the task.
Navigating Task Lists

If task lists are assigned to you, you can choose to work with the task list in Basic mode or Advanced mode. Basic mode provides a wizard to guide you through the sequenced steps in the task list. Advanced mode provides the flexibility of working with all Planning functions to which you have access, along with the task lists to which you have access. The way that you view task lists depends on the mode that you are working in and how you want to work. The way that you complete a task depends on the type of task on which you are working. A data form task can require that you open a data form, add data, and then click Save. A business rule task can require that you launch a business rule. A workflow task can display a planning unit for you to promote. A descriptive task can display read-only material, such as a reminder to send a fax. After completing the requirements for a task, you can mark it as complete. If a task has dependent tasks, you must complete dependent tasks before you can complete the primary task.
25-4
Navigating Tasks Lists in Basic Mode

Select task list from View pane. View tasks listed in View pane. View tasks details or advance to next incomplete task.
View tasks listed in View pane
View task list details.
Advance to next incomplete task.
Navigating Task Lists in Basic Mode

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

View tasks in task list. View due date and status. View instructions.
Launch task list wizard / next incomplete task.
View due date and status.
View instructions.

You can choose to view the tasks in the task list while in Basic mode. This enables you to review the status and due date of tasks and to view any instructions associated with a task. After reviewing the tasks, you can click the Incomplete link to return to the wizard and proceed to the next incomplete task in the task list.
25-6

Perform task. Mark task as completed. Navigate to next task or next incomplete task.
Mark task as completed.
Proceed to next task.

After you select to proceed to the next incomplete task, that task is presented for you to perform. The sequence in the task list and the type of task defined determines what is presented to you. When you have finished working with the task list, you can access other Planning functionality by returning to Advanced mode (View > Advanced Mode).
25-7
Navigating Task Lists in Advanced Mode

View > Task Lists > Task List or Task List toolbar icon
Task list(s) to which you have access
Navigating Task Lists in Advanced Mode

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

View tasks in task list and select task to perform. View due date and status. View instructions.
Select the task to perform.
View due dates and status.
View Instructions.

On the Task List panel, you can view task instructions, launch tasks, view task status, or mark a task as completed.
25-9

View the status of a task list.

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

1. In Advanced mode, select Administration > Manage Task Lists. 2. Create task list folders. 3. Create a task list. 4. Edit the task list to add specific tasks.
Add tasks to task list. Define individual tasks further by adding instructions, due dates, and alerts. Complete task creation by setting the properties for tasks.
Assign access to task lists. Validate task lists.
Task List Creation Process

Before you create task lists, you can create folders for your task lists to organize them. Then, you create the task lists, define the tasks that comprise the task list, set task properties, assign access rights to the task lists, and, finally, test the task lists.
25-11
Working with Task List Folders
3 2
Working with Task List Folders

You can create folders to organize and keep track of task lists that are used for different purposes. Use the Task List Folders area on the left of the Task List page to set up task list folders. You can change the name of task list folders and as well as the order that the folders are displayed on the screen. To create task list folders: 1. Click Create. 2. Type the name of the folder 3. Click OK.
25-12
Module 9 Managing the Planning Process Lesson 25 Creating Task Lists To rename task list folders: 1. Select the task list folder that you want to move. 2. Click Rename. 3. Type the name of the folder and click OK. To move task list folders: 1. Select a task list folder. 2. Click Move. 3. From the Select the destination folder drop-down list, select the folder where you want to move the selected folder. 4. Click OK.
25-13
Building Task Lists
3 2
Building Task Lists

You identify tasks that users need to perform. You then determine a sequence and hierarchy to organize the tasks into a task list. To create a task list, first you decide the location and name of the task list. For example, to create a new task list in the Expense Budgeting folder, select the Expense Budgeting folder, and clicking Create. You can rename task lists by selecting the task and clicking Rename. You can move the task list to a different folder by using the Move button. Select Edit to add tasks to task lists. You can delete tasks by selecting the task and clicking Delete. You assign access to task lists so that business users can use the task list by selecting the task list and clicking Assign Access.
25-14
Module 9 Managing the Planning Process Lesson 25 Creating Task Lists To create new task lists, do one of the following: Selecting Administration > Manage Task Lists. Select File > New > Task List.
25-15
Adding Tasks to Task Lists

Use Add Child or Add Sibling to add tasks to the task list and define the hierarchy.
Adding Tasks to Task Lists

After creating a task list, you set up task titles and determine the hierarchy of the tasks. You also define task properties and add instructions to the task list or to individual tasks to help users complete the tasks.
25-16
Setting Up Tasks
Specify name of task. Specify type of task. Add instructions. Set task due date and time. Set alert due date and time. Indicate any dependency.
Setting Up Tasks
After creating task lists and adding task names, you define the individual tasks. To do so, you must navigate to the folder that contains the task list and select the task. You can specify the name of the task and the type of task and add instructions for users by using the Edit Task dialog box. You can select from the following types: URL Task Data Form Business Rule Workflow Descriptive
25-17
Module 9 Managing the Planning Process Lesson 25 Creating Task Lists Additionally, you can set the due date and time for completing the task. You can also set an alert date to alert the business user about an upcoming due date. You can also determine whether the task is dependent on another task. If you set a completion date for a task, traffic light indicators are displayed on the task to alert users when the due date is approaching or when the due date has passed. You can also set up two types of e-mail messages to be sent to users. A due-date message can be sent to notify the user that a task is overdue, or an alert message can be sent to remind the user about an approaching due date.
25-18
Setting Task Properties

Types of tasks to set properties for: Data Form Business Rule Workflow URL Task
Setting Task Properties

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

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

Assign enables users to view and use the task list. Manage enables users to modify the task list. Manage and Assign enables users to modify the task list and to see and use the task list. None prevents users from seeing the task list.
Assigning Access to Task Lists

You can assign various types of access to task lists, and you can assign access to individual users or user groups. By assigning access to task lists, you determine who can view and modify task lists. By default, administrators have Manage and Assign access to all task lists for design modifications and use. Interactive users and planners have access to certain task lists, as determined by their access rights. There are four types of access that you can assign to a task list.
25-21
Validating Task Lists

Ensure that you are in Basic mode. Select the task list from the quick launch list. Use the wizard to advance to the next task. Complete the activities for the task. Mark the task as completed.
Validating Task Lists

After defining task lists, you should test them to validate that the task properties are correct, that the tasks within the task list are sequenced properly, and that the task lists are accessible to relevant users.
25-22
Reporting on Task Lists
Reporting on Task Lists

You can create reports to review the task lists created for your application. You run task list reports from the View menu by selecting View > Task List > Report. You can produce a report as either a PDF file or an Excel worksheet. The status report contains the task lists, task list owners, due dates, completion dates, and status of the task.
NOTE
You must be in Basic mode to view task list reports.
25-23
Summary
In this lesson, you should have learned to: Define task list capabilities Navigate task lists in Basic and Advanced modes Create task lists Assign access to task lists Validate task lists Report on task lists
25-24
M O D U L E
1 0
Analyzing Planning Data with Financial Reporting
25
Overview
The aim of this module is to navigate Financial Reporting and analyze plan data. Lessons in this module include: Financial Reporting Overview Navigating Reports in Workspace
L E S S O N
2 6
26
Financial Reporting Overview
Objectives
At the end of this lesson, you should be able to: Describe Financial Reporting Review data sources Navigate Financial Reporting Studio Log on to Financial Reporting Studio Identify portions of the Financial Reporting Studio workspace Open, preview, and print reports Identify report components Change the user point of view
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
Financial Reporting Features

Financial Reporting functionality Batches and books Guided analysis Grids Asymmetric reporting PDF & HTML reports Access security Scheduling
Reusable objects Charts
Conditional formatting Printing
Report designers and viewers
Reports and books
Financial Reporting Features

With Financial Reporting, you can graphically design and present analytic data. You can design traditional financial report formats, such as cash management reports, profit and loss statements, and balance sheets. You can also design nontraditional formats for financial or analytic data that includes text and graphics. Key features of Financial Reporting: Flexible range of output options Scalable, cross-platform, server-based report generation Graphical, object-based report creation with simultaneous access to multiple Hyperion data sources Objects that are reusable across multiple reports Book creation for similar reports Dynamic scheduling that enables automated reporting 26-2 Planning: Create and Manage Applications
Workforce Planning and XBRL Functionality

Workforce Planning and Financial Reporting
Using Workforce Planning Using Financial Reporting Define a dimension with attributes that change across time periods or other dimensions Display the results of these slowly changing attributes
XBRL Functionality and Financial Reporting

Using XBRL Using Financial Reporting Prepare and publish financial statements for various groups Attach XBRL metadata to an existing report as an XBRL instance document
Workforce Planning and XBRL Functionality

Workforce Planning is an add-on module for Hyperion Planning 4.0 and Hyperion System 9 Planning. Using Workforce Planning, you can define a dimension with attribute associations that change across time periods or other dimensions. For example, you may have a Status attribute dimension associated with an Employee dimension. This allows you to change the employee status over time. In January, John Smith might have the status of full time; in March his status might change to part time. You can use Financial Reporting to report on Workforce Planning applications and display the results of these slowly changing attributes. XBRL (Extensible Business Reporting Language) is an XML-based (Extensible Markup Language) framework. It provides you with a standards-based method to prepare, publish, reliably extract, and automatically exchange financial statements. XBRL makes it easier for you to produce financial statements for various audiences, such as investors, regulators, and creditors.
26-3
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview With the XBRL functionality in Financial Reporting, you can create XBRL instance documents. You attach XBRL metadata to an existing report and then export the report as an instance document. You can create XBRL instance documents using Analytic Services, Planning, or Financial Management data sources.
26-4
Financial Reporting Architecture

Client tier Financial Reporting Studio Financial Reporting Web client Web Server Financial Reporting Web application Workspace Web application Smart View Office Add-in
Application tier
Financial Reporting services Core Services
Database tier
Analytic Services
Planning
Financial Management
SAP/ BW
Repository
Financial Reporting Architecture

Financial Reporting is based on a three-tiered architecture that contains the client, application, and database tiers. Client Tier The client tier refers to the local interfaces used to author, analyze, present, report, and distribute content. With Hyperion System 9 BI+ Financial Reporting Studio , you connect to a Report Server to design reports, snapshot reports, and report objects, and to view reports. You use the Financial Reporting Web client in the Microsoft Internet Explorer Web browser to view reports and books, design and run books and batches, and manage the repository and security. Through Smart View, you can import Financial Reporting report images into Word and PowerPoint. You can also import Financial Reporting report grids into Excel. Planning: Create and Manage Applications 26-5
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview Application Tier The application tier is a middle tier that retrieves the requested information and manages security, communication, and integration. The Web server, Financial Reporting Web application, Workspace Web application, Financial Reporting services, and Core services are on the application tier. The Financial Reporting Web application and Workspace Web application rely on the Web server to send and receive content from Web clients. Financial Reporting services support Financial Reporting functionality by processing batch requests, generating output, and distributing Financial Reporting client content. Core services provide mandatory services for storing and retrieving objects in the repository, authenticating users, managing roles, and managing sessions. Database Tier The database tier contains the relational database repository and the Analytic Services or Planning data sources. The repository stores Hyperion system data, such as security information, reports, and report objects. The following relational databases are supported: Microsoft SQL Server 2000 Service Pack 3a (Enterprise or Standard Edition) Oracle 9i - 9.2.0.1 or 10g - 10.1.3.0 IBM DB2 Release 8.2 The Analytic Services and Planning data sources contain the data for your reports. Financial Reporting supports the following data sources: Analytic Services 7.1.x or System 9 Planning 4.0.5 or 9.3 Financial Management 4.0.5 or 9.3 SAP BW 3.1 or 3.5 Microsoft SQL Server 2000 or 2005 Analysis Services
26-6
Security Overview
Common user provisioning managed by Shared Services Native and external authentication of users Authorization of actions that users can perform in Financial Reporting Access privileges for report objects
Security Overview
Hyperion System 9 BI+ uses common user provisioning for centralized user administration. Common user provisioning resolves the issue in Hyperion applications of configuring the same user multiple times for each Hyperion product and application. You manage users in Shared Services and specify to apply either native or external authentication when users log on to Hyperion products. The security environment consists of authenticating users during the logon process, authorizing users to perform certain actions, and allowing access to objects and folders in the repository. When you create users, you specify how they are authenticated when they log on to Financial Reporting and what actions they can perform. For example, you define which users can design reports and which users can only view reports. After creating objects in the repository, you assign the access rights that define which users can view or modify the objects. For example, you can specify that jsmith can view all reports in the Sales Reports folder. Planning: Create and Manage Applications 26-7
Users, Groups, and Roles

Users J. Doe Groups Roles Provisioning manager Global administrator A. Smith Development F. Jones Report designer
V. Yu Marketing P. Frank Explorer
Users, Groups, and Roles

Users, groups, and roles are part of the security system. You assign roles to users to determine the type of user they are and the actions that they can perform. A role is specific to a products application and it is defined based on product functions. For example, a user with the report designer role can access Financial Reporting Studio and create reports. A user with the scheduler role can schedule and manage batches in Financial Reporting. A group is a collection of related users with similarities such as a geographical location, a department within an organization, or a need to share the same information. A user can belong to multiple groups. You can assign roles through groups. The users in the group inherit the roles assigned to the group.
26-8
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview The following table describes the available roles for Financial Reporting:
Role Directory manager Explorer Global administrator Provisioning manager Report designer Scheduler Description Create and manage users and groups Access the Explore module to search for repository content Access all resources and all functionality Provision users and groups to applications Access Financial Reporting Studio, create report objects, and import and export Financial Reporting content Schedule batches and manage batch output
26-9
Data Sources for Financial Reporting
Budgeting Application Plan Type 3 Plan Type 2 Plan Type 1
Data Sources for Financial Reporting

To analyze your plan data using Financial Reporting, you can access information using the Planning ADM (Planning Details) or Analytic Services ADM driver. The type of information you want to report on determines which ADM should be used to access the data source. The Planning Details data source should be used only when the report needs to contain Supporting Details or Planning Unit Annotations. Consider the following points when using the Planning Details data source: Attributes are not represented as dimensions; use the Member Property function for attribute member selection. By default, member properties are in the order of the outline of the base dimension; use the OrderBy member selection function to sort the report in order of the properties. There is no ability to group or subtotal attribute values automatically. The HSP_Rates dimension is not visible.
26-10
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview Linked reporting objects (LROs) are not supported. Metadata security is first checked on the relational database, and then the request for data is made to Analytic Services accordingly.
26-11
Financial Reporting Studio
Financial Reporting Studio

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

Select Start > All Programs > Hyperion System 9 BI+ > Financial Reporting Studio.
Enter user ID Select the server Click OK

Enter password
Working with Financial Reporting Studio

Before launching Financial Reporting Studio, you must start the Analytic Services Server. You must have a valid administrator or designer user ID and password to log on to Financial Reporting. The user ID is authenticated by Financial Reporting or by an external source, such as Analytic Services or Windows NT LAN Manager.
26-13
Financial Reporting Studio Workspace

Standard Toolbar Repository Toolbar
Financial Reporting Studio Workspace

When you first log on to Financial Reporting Studio, you see a workspace area with a list of report objects. From this workspace, you can create a new report or open an existing report. Standard Toolbar The standard toolbar provides the following alternatives to menu commands:
Button Description Opens a new report workspace Opens the Open dialog box to select a report Saves a report or object in the repository
26-14
Button Description Opens the repository Opens the Print dialog box Displays the active report in the Print Preview window Displays the active report in the Web browser
Repository Toolbar The repository toolbar provides the following alternatives to menu commands that manage the repository:
Button Description Deletes the selected object Refreshes the repository display of objects
26-15
Viewing Repository Objects
Object name
Object type
Viewing Repository Objects

The Financial Reporting repository is the object management tool that functions like Windows Explorer. You save all report objects in the repository and can then use the same object in more than one report. The following table describes the object types:
Object Type Batch Book Grid Image Report Description Container that processes groups of reports and books. Container that holds a group of similar reports. Report object that contains data from external data sources. Report object that contains a graphic or an image file. Layout that dynamically identifies the content and formatting of a report. A report becomes populated with data when you run it.
26-16
Object Type Snapshot Description Generated report that contains static data from a specific point in time. Subsequent changes of the data in the data source do not affect the report content. Report object that contains text or functions.
Text
You cannot delete the highest-level folder named Root. In the Financial Reporting Web client, you can add additional folders and categorize them to suit your needs. For example, you can create specific folders for batch jobs, books, images, or reports, or separate folders for different departments. To display repositor y objects: 1. Select File > Explore. A list of repository objects is displayed. 2. Select View > Display Items of Type and select one of the following options to display only selected object types: All Items Report Snapshot Book Snapshot Book Batch Saved Report Object
26-17
Opening Reports
1. Select File > Explore to display the repository objects. 2. Expand the repository folders to find the report. 3. Double-click the report to open it.
Opening Reports
You open reports to design, preview, or print them. You can display both dynamic reports and snapshot reports. A dynamic report is opened in the report workspace. A snapshot report is opened in the Web preview window. If you want to design, view, or print dynamic reports, you must be connected to an Analytic Services or Planning database. Otherwise, you can view only snapshot reports.
26-18
Report Components
Image Grid Text Box
Chart
Report Components
Reports contain report objects such as text boxes, grids, images, and charts. When you design a report, you add report objects to the report workspace. As you select each report object, its property sheet is displayed in the workspace frame on the right. You use property sheets to customize report objects.
26-19
Changing the User Point of View Members

Dimension name Member name
User POV bar
Changing the User Point of View Members

The user point of view (POV) bar displays members that are not defined in the grid. The bar is specific to a database for a single user, but not specific to any report or grid in a report. In the user POV, you change the default values for all grids in the report simultaneously. By changing the user POV, you dynamically change the data that is displayed and calculated in the report. When you select a dimension on the user POV bar, the Select Members dialog box is displayed. You can change the selected member for each dimension and attribute dimension that is not defined in the grid. In the POV, you can select only one member for each dimension.
26-20
Previewing and Printing Reports
Print Preview
Web Preview
Previewing and Printing Reports

While designing a report, you preview it to check the result of the structure, layout, and format of the report. You can preview a report in two ways: Print Preview: Displays the report with data as it appears when printed. Web Preview: Opens a Web browser window and displays the report with data as it appears in the Financial Reporting Web client. The Print Preview window includes a toolbar for printing, navigating, zooming in, and zooming out.
26-21
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview You can print dynamic and snapshot reports. For example, you might print end-of-month reports for all regions. You can open a report and then print it, or you can print the report from the Explore window without opening it. When you print the report, you can select the printer, print range, and number of copies.
26-22
Summary
In this lesson, you should have learned to: Describe Financial Reporting Review data sources Navigate Financial Reporting Studio Log on to Financial Reporting Studio Identify portions of the Financial Reporting Studio workspace Open, preview, and print reports Identify report components Change the user Point of View (POV)
26-23
26-24
L E S S O N
2 7
27
Navigating Reports in Workspace
Objectives
At the end of this lesson, you should be able to: Identify interface elements in Workspace Set preferences Set the user point of view Limit the user POV member selections Integrate reports into Microsoft Office applications
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
Workspace Overview
Set preferences Create books
View reports
Workspace Overview
Workspace provides a single point of access to BI+ content and authoring tools. You can access the following content in Workspace: Financial Reportingfor scheduled or on-demand highly formatted financial and operational reporting Web Analysisfor interactive ad hoc analysis, presentation, and reporting of multidimensional data Interactive Reportingfor ad hoc relational query, self-service reporting, and dashboards against any ODBC data source Production Reportingfor high-volume enterprise-wide production reporting Hyperion System 9 BI+ Enterprise Metrics for management metrics and analysis presented in easy-to-use, personalized, interactive dynamic dashboards
27-2
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace Depending on your assigned roles and security access, you can use Workspace to perform the following tasks related to Financial Reporting: View and print reports and books Create and modify books Create and schedule batches Assign access to repository items Set preferences Perform administrative tasks such as managing users
27-3
Workspace User Interface

Navigate menu Menu bar Buttons Standard toolbar
Process bar
View pane
Document tab bar

Adjuster
Content area
Workspace User Interface

In Workspace, you can open and work with the following Workspace elements.:
Element Name Adjuster Buttons Content area Document tab bar Menu bar Navigate menu Process bar Description Adjusts the size of the view pane and content area Enables performance of module tasks 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 the location of the current folder, item, or step
27-4
Element Name Standard toolbar View pane Description Provides shortcut buttons for performing tasks Provides buttons that enable jumps between panels
27-5
Workspace Modules
Workspace Modules
You use Workspace modules to perform the following tasks:
Module Name Explore Applications Administer Schedule Impact Manager Open Items Description View, manage, and secure repository items Access and view applications such as Planning and Financial Management Manage users, groups, roles, and authentication methods Schedule batch jobs for automated processing Update Interactive Reporting documents when database structures change View all documents or items opened in Workspace
27-6
View Pane Buttons

Tips button Folders button
View Pane Buttons

When you select a module, context-sensitive buttons are displayed at the top of the view pane.
Button Tips Folders Description Displays shortcuts to actions (Tasks) and links to online help instructions (Tips) for tasks, tips, and file details relevant to the current item Displays the Root folder and the folders and repository items below it
27-7
Setting Preferences
Select File > Preferences.
Options: None Explore Document Favorite Application
Setting Preferences
You can set preferences for the Workspace user interface, user authentication, the Explore module, and Financial Reporting Studio. Preference changes become effective the next time that you log on.
Setting General Preferences

You can set defaults for the general appearance of your Workspace user interface. You can select the page to be displayed in the content area. The Content option determines what other options are available. For the example shown on the slide, you select Explore and then select the FR/Qtr Reports folder. You can set up prompts to save unsaved files. You can also show the document path and the Tips tab. You cannot update the e-mail address because it is registered in the users security settings.
27-8
Setting Authentication Preferences

Select File > Preferences > Authentication.
Setting Authentication Preferences

If you are a native user in Workspace, you can change your password. Native users are authenticated by Shared Services, rather than by external sources, such as Analytic Services or Windows NT LAN Manager (NTLM).
27-9
Setting Explore Preferences

Select File > Preferences > Explore.
Setting Explore Preferences

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

Select File > Preferences > Financial Reporting, and then select the Financial Reporting Studio tab.
Select Inches or Centimeters

Select Dot or Line
Setting Financial Reporting Studio Preferences

You can set the following preferences for Financial Reporting Studio: Language XBRL Editing Color, style, and distance between guide lines
27-11
Setting Financial Reporting General Preferences

Select File > Preferences > Financial Reporting.
Setting Financial Reporting General Preferences

You can define preferences and formatting options for the Financial Reporting module: Default mode for previewing reports and books User POV preview, location, and member selections Microsoft Office application to which reports are exported Behavior of prompts
27-12
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace Separators for formatting numbers in a grid The separators for formatting numbers in a grid apply only if you select the Defined by Preference option during report design.
27-13
Browsing the Repository

Sort the list by clicking a column header
Qtr Reports folder
Items in the Qtr Reports folder
Browsing the Repository

In the Explore module, you can browse the repository and perform these actions: Open reports and books Edit books and batches Export and import items Set security access When you select a repository folder in the view pane, the folder items to which you have access are displayed in the content area. By default, each item displays name, type, date modified, and description. You can sort the list of items by clicking the column headings. You can also change the column order by sliding the column headings to the right or left.
27-14
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace On the View menu, you can change the display by showing or hiding columns and setting the width of each column. You can also limit the display to a particular type of item, such as displaying only a list of books. You can also use the Viewer module to access repository items located on your desktop. You specify your default desktop folder in the Explore preferences. When you select Desktop, the repository items in the specified folder are displayed as icons in the content pane. When you open reports and books, their names are listed in the Viewer module.
27-15
Searching for Items

In the Explore module, select Tools > Search.
Search criteria
Search results
Searching for Items

In the Explore module, you can search for items based on keywords. By default, keywords are generated for repository items and include the words in the item name and description. You can narrow your search by specifying item location, date, and type. Search rules: The search is not case-sensitive. Wildcards are not supported in the Keywords box. Multiple keywords are separated by a space. The search starts in the folder specified in the Look in box and proceeds through all subfolders.
27-16
Previewing Reports
User POV
Grid POV Page selector
Previewing Reports
In the Explore module, you can preview reports in two formats: Hypertext Markup Language (HTML)Preview reports or snapshots Portable Document Format (PDF)Preview or print reports or snapshots that are displayed in the Web browser in Adobe Acrobat Reader
NOTE
Before previewing reports in PDF, ensure that a PDF writer (Adobe Acrobat Distiller, GNU Ghostscript, or AFPL Ghostscript) is installed with your print server.
27-17
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace Analytic Services Server must be started so that you can view dynamic reports. When you view a dynamic report, the user POV is displayed. When you change the user POV, the report is automatically refreshed to display current data for the new member selection. When you view a snapshot report, you see data for a specific point in time. Because the POV is fixed with static data when it is created, the user POV is not displayed when you view it. A snapshot report is disconnected from the data source and is not updated when data changes. From the Financial Reporting general preferences, you can select the default preview mode for reports. When you double-click a report name in the repository, the report is displayed in the default preview mode. The selected setting remains in effect until you change it. To preview repor ts or snapshots: 1. In the repository, right-click a report or snapshot. 2. Select Open In > HTML Preview or Open In > PDF Preview. The report is displayed in the content area.
27-18
Changing the User Point of View

Wildcard search for entity names that begin with LOC
Search results
Changing the User Point of View

When you preview a dynamic report, the user POV bar is displayed in the view pane or above the report. You change the user POV member selections to dynamically change what data is displayed and calculated in the report. When you change the POV, the report runs and displays the data for the new POV member selection. You can search for a specific member to display in the user POV. For the example shown on the slide, you search for all names that begin with LOC. You can then select the member for the user POV from the Search Result dialog box.
27-19
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace The following table describes the options in the Member Selection dialog box:
Option Show Properties Expand All Rows Collapse All Rows Rows Per Page Description Select the properties to display, such as Name, Description, Generation, and Level. Expand the dimension hierarchy. Collapse the dimension hierarchy. Specify the number of rows displayed on a page. If more members are available than the number of rows specified, Next Page and Previous Page buttons enable you to scroll through the rows. Select the option on which to base the search, such as Name, Description, Generation, and Level. Enter the characters for a search: Partial text with wildcard symbols Exact characters (Enclose the characters and the blank spaces between them in quotation marks.) Find Use Wildcards Find the items that match the search criteria. Search by text and wildcard symbols:
Find list Find box
? represents one character * represents multiple characters
27-20
Previewing the Point of View

Select On to preview the user POV. Select the POV before the data is retrieved.
Open the report in HTML or PDF mode.
Previewing the Point of View

When you view a report in Workspace, the report displays the current data. If the POV is not the one that you want, you must change it and rerun the report. A second query of the database is created. If you are working with a large database, this process is timeconsuming. Workspace enables you to preview and select the user POV before it queries the database. When you preview the user POV, you make your POV selections before the report runs.
27-21
Limiting User Point of View Selections

Select File > Preferences > Financial Reporting > Setup Members.
Go to Member Selection button
Member label options
Limiting User Point of View Selections

By default, all dimension members are available when you access the user POV. For Analytic Services or Planning databases, dimensions may contain members that you never access.You can limit dimension members by creating a choices list, so that only listed members are displayed for all reports that retrieve data from the same database connection. For the example shown on the slide, you specify that available members for the Scenario dimension are Actual, Budget, and Forecast. For all other dimensions, you may select any member.
27-22
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace When setting up members for the user POV, you can define the display of member names in the user POV bar. You can select to view dimension name, member name, alias, or both member name and alias.
Dimension name and member name are displayed.
Member alias is displayed.
To set up user POV member selections: 1. Select File > Preferences, click Financial Reporting, and click Setup Members. The Setup User POV dialog box is displayed. 2. From the Database Connection list, select a database connection. The dialog box displays the database dimensions. 3. To the right of the dimension for which you want to create a choices list, click Go to Member Selection: <dimension name>. A Members tab is displayed in the Setup User POV dialog box.
27-23
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace 4. In the Available area on the left, select the members that you want to include in the choices list, and click the add button . The members are displayed in the Selected area.
5. Click OK to save the member selections. The Setup User POV dialog box is displayed with the selected members listed in the Choices List column. 6. Repeat steps 3 through 5 for any dimension for which you want to create a choices list. 7. Optional: To the right of the dimension for which you want to change the member selection, click the ALL button to set the choices list back to All Members. 8. From the Display Member Label as drop-down list, select to display the member name, the alias, or both the member name and alias. 9. From the Dimension Labels are drop-down list, select whether dimension labels are Included or Not Included in the user POV bar. 10. From the Member Selection Displays drop-down list, select to filter members according to access privileges. Options: Only Members I Can Access: Only members to which the user has access are displayed in a flat list.
27-24
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace All Members Regardless of Access: All members, regardless of the users access privilege, are displayed in a hierarchy.
NOTE
The Member Selection Displays drop-down list is available only for Planning database connections. This option is displayed only if the DisplayFilterBySecurity flag in the hr_webapp.properties file is turned on. 11. Click OK to save your changes and return to the Preferences dialog box.
27-25
Changing Page Members
ActCurr page selection
BudCurr page selection
Changing Page Members

You can change a page member only if you assigned multiple members to the page axis during the report design. You must view the report in HTML to select different page members. After you change a page member, the report is refreshed, and the data for the selected members is displayed. When you view a report with multiple page members in PDF, the data for the page members is displayed on different pages.
27-26
Printing Reports and Snapshots

1. Open the report in either HTML or PDF preview mode. 2. Select File > Print > HTML or File > Print > PDF.
Printing Reports and Snapshots

You can print reports or snapshots in HTML or PDF mode: HTMLIf a report or snapshot has multiple page members, only the displayed page member is printed. The browser print capabilities determine how the report is printed. PDFIf a report or snapshot has multiple page members, all page members are printed. PDF printing ensures that the report or snapshot is properly formatted and paginated; PDF printing provides better quality than does HTML.
27-27
Integrating Reports into Microsoft Office Applications
Integrating Reports into Microsoft Office Applications

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

After previewing a report in HTML or PDF mode, you can export the report to a Microsoft Excel spreadsheet. When you export a report to Excel, you must choose one of the following options: Fully-Formatted Grids and TextThe current page of the report is exported to Excel in a format that is similar to its format in Financial Reporting. The report is converted to HTML with the Hyperion formatting definitions and calculated numbers. Charts in the report are exported as images. To export multiple pages, you display and export one page at a time.
NOTE
If you are using Microsoft Office 2000, only the grid and text objects of the report are exported into Excel. Charts and images are not exported.
27-29
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace Query-Ready Grids and TextThe first grid in the report is exported to Excel. The grid is converted to HTML, and Hyperion-specific formatting is removed. Images and charts in the report are not exported. After the grid is exported, you connect to an Analytic Services server and use Smart View to perform ad hoc analysis. To export a repor t to Microsoft Excel: 1. In the Explore module, open the report in either HTML Preview or PDF Preview mode. 2. Select File > Export > Excel > Fully-Formatted Grids and Text or Query-Ready Grids and Text. The File Download dialog box is displayed. 3. Perform an action: Click Open to open the report in an Excel spreadsheet and then save the spreadsheet. Click Save to save the report as an Excel worksheet that you can open at a later time.
NOTE
If you have set Excel files to open as a browser preference, the file may open automatically in the browser window, without showing the File Download dialog box.
27-30
Exporting Reports to Word and PowerPoint
Exporting Reports to Word and PowerPoint

After previewing a report in the Explore module, you can export the report as an image to Word or PowerPoint. You can export reports if you are using Microsoft Office 2002 or later. To export a repor t to Word or PowerPoint: 1. In the Explore module, open a report. The report is displayed in HTML or PDF mode. 2. Select File > Export > Word or File > Export > PowerPoint. The File Download dialog box is displayed. 3. Perform an action: Click Open to open the report in Word or PowerPoint.
27-31
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace Click Save to save the report as a Word or PowerPoint document that you can open later.
TIP
After importing the image, you can use the Microsoft Office Format Picture option to further format the object; for example, to crop and resize the image.
27-32
Importing Reports to Microsoft Office Applications
Importing Reports to Microsoft Office Applications

You can import Financial Reporting reports to Microsoft Office applications through Smart View: Word and PowerPointThe report is imported as an image. ExcelThe report is imported based on the selected method (Fully Formatted Grids and Text or Query-Ready Grids and Text). In Microsoft Office, you must connect to a Workspace repository that contains the reports that you want to import. You log on to the data source only once. For example, you can log on to a data source connection in Word and use the connection to access data in Excel or PowerPoint.
27-33
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace To import reports to Microsoft Word, PowerPoint, or Excel: 1. Launch Microsoft Word, PowerPoint, or Excel. 2. Select Hyperion > Connection Manager. The Connection Manager dialog box is displayed. 3. Select the data source, and click Connect. The Connection credentials dialog box is displayed. 4. Enter the user name and password, click Connect, and click Close. 5. Select Hyperion > BI+ Document > Import. The Import Workspace Document dialog box is displayed. 6. Expand a repository folder, select a report, and click OK. The Import Workspace Document dialog box displays the report. 7. Optional: In the POV, select an unselected dimension to change the user POV. 8. Select the All Pages check box to import all pages of the report. 9. Optional: Perform an action: Word or PowerPointIn the Import Document As list, select Image to import the report as an image. ExcelIn the Import Document As list, select Fully Formatted or Query-Ready, and select Split Pages across worksheets to place pages on separate worksheets. The report is imported into the Microsoft application. 10. Click Finish. 11. Optional: Save the report as a Microsoft Office document that you can open later.
27-34
Summary
In this lesson, you should have learned to: Identify interface elements in Workspace Set preferences Set the user point of view Limit the user POV member selections Integrate reports into Microsoft Office applications
27-35
27-36
M O D U L E
1 1
27
Appendices
Overview
This module contains appendices to provide information about additional features of Planning not covered in this course. Appendices includes: Sharing Data Using Data Synchronization Working with Classic Application Administration
A P P E N D I X
Sharing Data Using Data Synchronization
Objectives
At the end of this lesson, you should be able to: Describe data synchronization Create mapping tables and data synchronizations Set data synchronization filters View data flows Execute synchronizations
Module 11 Appendices Appendix A Sharing Data Using Data Synchronization
About Data Synchronization
HYPlan application
Finbud application
Actuals
Mapping table Budgeting plans
About Data Synchronization

You use data synchronization to transfer data automatically from a source application to a destination application. Data synchronization provides filters for selecting data needed for other applications. You can schedule data synchronization to run during off-peak business hours, and you can view data flows between applications after a data synchronization has occurred. For the example shown on the slide, HYPlan is the master (source) application that contains both balance sheet and income statement actuals. Finbud is the destination application that contains financial budgeting plans. You use data synchronization to transfer the data from the Net Income hierarchy of the HYPlan application to the Net Income hierarchy of the Finbud application.
A-2
Creating Mapping Tables

To create a mapping table, you specify source and destination dimensions.
Source application is where the data is retrieved from.
Destination application is the application that receives the data.
Creating Mapping Tables

In order for the data synchronization to transfer dimension data between two applications, the dimension member names must match. If the member names do not match, you must create a mapping table to map members in the source application to members in the destination application. For example, you could map data from the Account member in the source application to the Revenue member in the destination application. After creating a mapping table, you insert it into a data synchronization. You can use the same mapping table in many data synchronizations.
Planning: Create and Manage Applications A-3
Module 11 Appendices Appendix A Sharing Data Using Data Synchronization To create mapping tables: 1. Determine which dimension members must be mapped due to mismatched member names. 2. Select File > New > Mapping Table. The Mapping Table Designer is displayed. 3. On the Setup page, specify the source application, destination application, and the dimension for which you want to map data. 4. On the Map Data page, specify how each member is mapped: a. Select the member from the source dimension. b. Select the member in the destination dimension to which it should be mapped. 5. Repeat step 4 for each member that must be mapped. 6. Validate the mapping. 7. Save the mapping table.
A-4
Creating Data Synchronizations

You use a wizard to create a data synchronization.
Data Synchronization Toolbar Validate Synchronization
Insert Mapping Table
Execute Synchronization
Creating Data Synchronizations

You create a data synchronization by performing the following tasks in the New Synchronization wizard: 1. Specify the data source and the destination application. 2. Link source dimensions to destination dimensions. 3. Create filters for source dimensions.
Specifying Source and Destination

The Data Synchronization Wizard has three pages:
Data Synchronization Page Source Type Select Source Select Destination Description Data source type that is sending the data. Object or application that is receiving the data. Application that is receiving the data. The target application can be a Planning or Financial Management application.
Specifying Source and Destination

You use the New Synchronization wizard to specify the data source and destination for a synchronization. Data source types: Flat file Interface table Planning or Financial Management application
A-6
Linking Dimensions
Insert mapping tables in Data Synchronization to ensure correct data linking between members.
Source application is where the data is retrieved from
Linking Dimensions
After specifying the data source and destination, you specify a matching dimension in the destination application for each source dimension. For example, you map the data for the GL_Accounts dimension in the source to the GAAP_Accounts dimension in the destination application. To link dimensions: Drag a dimension from the source application to the destination application. A link is displayed as a line connecting the source dimension to the destination dimension.
Setting Filters
You select filters using the Member Selector dialog box.
Setting Filters
By default, data for all dimension members of each dimension is transferred when you execute a data synchronization. You can create filters so that only member data needed in the destination application is transferred from the source. For instance, the Finbud application must receive data from the HYPlan application. However, the Finbud application needs data only from the West entity. By applying a filter to the Entity dimension in the HYPlan application, you transfer data only from West. To create filters: 1. On the Link Dimensions page, right-click a dimension and select Create Filter. The Member Selector dialog box is displayed. 2. Select members and click the right arrow button.
A-8
Applying Filter Criteria
A filter was applied to the source entity.
Applying Filter Criteria

You can set criteria to refine a filter:
Filter Criteria Equal Like Description Filters what is equal to the dimension name in the selector field Filters to perform pattern-matching functionality on partial dimension names
NOTE
After the filter is applied to the dimension, a filter icon is inserted next to the dimension name on the Link Dimension page.
Inserting Mapping Tables
Insert Mapping Table button
Inserting Mapping Tables

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

Validate Synchronization button
Validating Data Synchronizations

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

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

Execute Synchronization button
Executing Data Synchronizations

When you execute a data synchronization, the data is retrieved from the source application, transformed according to mapping rules, and pushed to the destination application. You can specify a calculation to apply to the data being transferred. For example, if you are transferring data from Actual to Budget, you could specify that the values should be increased by 10%. To execute synchronizations: 1. Right-click the synchronization and select Execute. The Data Sync Execution Options dialog box is displayed. 2. Optional: Define a calculation to perform on the data. a. In the Operator text box, enter a standard mathematical operator. b. Optional: In the Value text box, enter a numeric value. 3. Click OK. Planning: Create and Manage Applications A-13
Summary
In this lesson, you should have learned to: Describe data synchronization Create mapping tables and data synchronizations Set data synchronization filters View data flows Execute synchronizations
A-14
A P P E N D I X
Working with Classic Application Administration
Objectives
At the end of this lesson, you should be able to: Describe classic administration List the steps for creating Planning applications Create Planning applications using classic application administration Set up dimensions and members in Planning Load metadata files
Module 11 Appendices Appendix B Working with Classic Application Administration
Classic Administration Overview
Classic Administration Overview

An application is a related set of dimensions and dimension members that you use to meet a specific set of planning needs. Each application has its own accounts, entities, scenarios, and other dimensions. For example, you could create an application for your cost centers for budgeting operating expenses and a separate application for the finance department for revenue planning. You can create applications using either BPM Architect or Classic application administration. Classic administration enables you to administer Planning on an application-by-application basis. To use Classic application administration, you must be assigned the Shared Services roles of Dimension Editor and Planning Application Creator. Different menus and options are available for each type of application. This appendix describes Classic administration tasks.
B-2
Module 11 Appendices Appendix B Working with Classic Application Administration You create applications by using the Classic Application Wizard. To set up your applications dimension, you use the Planning Dimension editor. You can add dimensions and dimension members or modify existing members characteristics by working with the Planning Dimension editor. You can load metadata by using Data Integration Manager (DIM).
Planning: Create and Manage Applications B-3
Processes in Creating Planning Applications

Create an application using Classic Application Wizard Establish the currencies and corresponding exchange rates Modify the calendar with the custom summary time periods Create scenarios and versions Create entities to reflect your organizations budget review structure Create the accounts and additional dimensions Use DIM to load metadata and data Assign access rights to users and user groups Create appropriate data-entry forms Use Business Rules to build customized calculations and allocations Identify review and approval process, its requirements, and its participants
Processes in Creating Planning Applications

Setting up an application requires many steps. First, you create an application using the Classic Application Wizard. By using the Classic Application Wizard, you set up the application calendar, default currency, and plan types. After you establish the application, you can set up your application even further. If you set up your application to support multiple currencies, you establish currencies and corresponding exchange rates. If your organization has custom summary time periods, you modify the calendar to include them. You then create the scenarios and versions that you will use in your application. You create entities to reflect your organizations budget review structure. You also create the accounts and additional dimensions that you require to gather planning data. You use Data Integration Manager to load metadata into your application.
B-4
Module 11 Appendices Appendix B Working with Classic Application Administration After you finalize your dimension structure, you are at a good point to assign access rights to users and user groups. Next, you create appropriate data entry forms to meet the needs of your users and groups. As you continue to set up your application, you create customized business rules to run calculations and allocations specific to your organization. Finally, you identify the review and approval process, its requirements, and its participants.
Hyperion System 9 Planning Application Creation Overview

Create relational database Register data source
Configure relational database
Create application Create Analytic Services databases
Hyperion System 9 Planning Application Creation Overview

Before you create a Planning application, you need to create and configure a relational database to work with Planning. You then need to establish connectivity between Planning, the relational data source, and Analytic Services. To create an application, you complete the following steps: Create a relational database. Configure the relational database using the Configuration Utility. Create application using Classic Application Wizard. Create Analytic Services databases. Register the data source name (DSN) using the Classic Application Wizard.
B-6
Planning Relational Databases

Create and define a Planning system database and a relational database for each Planning application.
CorpPlan
HPSystem
CorpPlan TaxPlan Finbud
Finbud
TaxPlan
Planning Relational Databases

Planning requires one relational database for each application as well as one defined as the Planning system database, which stores an entry for each Planning application that is created. The procedures for creating relational databases vary depending on which relational store your company uses: Microsoft SQL Server, Oracle, or IBM DB2. Once the relational database is created, connectivity between Planning, the relational database, and Analytic Services databases needs to be established by registering data source names.
NOTE
Creating relational databases is typically the responsibility of a system administrator.
Configuring Data Sources
Configuring Data Sources

You configure data sources using the Configuration Utility. Configuring the data source establishes the connection between the relational data source, the relational database and the Analytic Services database. To Configure Data Sources: 1. Select Start > All Programs > Hyperion System 9 Foundation > Configuration Utility. 2. At the Welcome message, click Next. 3. On the Select the products to configure page, select Planning and Data Source Configuration, and click Next. 4. On the Select the options for managing the Data Source page, select Create Datasource and click Next.
B-8
Module 11 Appendices Appendix B Working with Classic Application Administration 5. On the Enter Details for creating Datasource page, enter the Datasource Name and description, and click Next. 6. From the Instance Name drop-down list, select an instance, and click Next. 7. On the Select the database page, select the relational database, and click Next. 8. On the Enter the Relational Storage Configuration Details page, enter the Server name, User and Password, and click Next. 9. On the Enter Analytic Server Information page, enter the Server, User and Password, and click Next. 10. At the successful message, click Next. 11. At the Do you want to go back to the Product Selection Panel message, select No, and click Next. 12. Click Finish.
Creating Applications Using Classic Application Wizard

Use Classic Application Wizard to initialize an application
Data Source
Calendar
Currencies
Plan Types
Creating Applications Using Classic Application Wizard

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

You access the Classic Application Wizard by selecting Planning Administration from the Classic Application Administration menu. To create a new application and initiate the Classic Application Wizard, click Create Application.
Selecting the Data Source
Selecting the Data Source

On the Select tab, you specify the application name and description, and register the application with Shared Services by selecting the Shared Services project. You also select a data source and instance for the application. The application name can be up to eight characters and must not be the same as an existing Analytic Services application.
NOTE
Data sources and instances are set up when you install and configure Planning. For Classic applications, you must select the instance whenever the instance changes in the Hyperion Configuration Utility.
B-12
Setting Up the Calendar
Setting Up the Calendar

You set up the calendar to establish the applications base time periods (12 months, quarters, or custom), starting fiscal year and month, and total number of years. You select the base time periods and monthly distribution pattern based on the number of fiscal weeks in a month. Base time periods are the bottom-level periods in the application. You can select from the predefined options of either months or quarters, or set up custom base time periods such as weeks or days. You can select a distribution pattern to determine how data entered in summary time periods is distributed or spread among the base time periods. If you select 12 months for base time periods: four quarters are created per year months roll up into parent quarters quarters roll up into years
Module 11 Appendices Appendix B Working with Classic Application Administration After you create an application, the starting fiscal year for the application cannot be changed. Weekly distribution sets the monthly distribution pattern, based on the number of fiscal weeks in a month. If you select a weekly distribution pattern other than Even, Planning treats quarterly values as if they were divided into 13 weeks and distributes weeks according to the selected pattern. You can select the Total Years to be included in the application. You can add more years to the calendar after the application is created.
B-14
Setting Up Currencies
Setting Up Currencies
You use the Currencies window to specify the default currency for the entities in your application and to establish whether your application supports currency conversion. You cannot change these settings after you have created the application. Multiple-currency support is available for level 0 members, regardless of their base currency. The Classic Application Wizard creates two additional dimensions for multiplecurrency applications. The dimensions are: Currency Stores the application currency, local currency, and reporting currency members. HSP_Rates Stores the input value, input currency, and exchange rate members.
Setting Up Plan Types
Setting Up Plan Types

You can include up to three plan types in your application. Separate Analytic Services databases are created for each plan type. As you create the accounts, entities, and other dimensions and members of your application, you associate them with plan types, so that the database for each plan type contains just the dimensions, members, and data values relevant to that plan type. This allows for improved system performance. The number of plan types included in an application depends on your organizations needs. For example, the sales department might be responsible for a yearly revenue plan and the finance department for a Profit and Loss plan. You could define two plan types: Revenue and PandL.
B-16
Module 11 Appendices Appendix B Working with Classic Application Administration Data can be shared between the plan types. For example, the Revenue plan might include a number of sales detail accounts that roll up to a Total Product Sales account. You can set up the P&L plan to include the Total Product Sales account, but to omit the sales detail accounts. This enables you to bring the data value for Total Product Sales into your P&L plan, without all of the account details. This creates a smaller, more efficient database for your P&L plan.
NOTE
You cannot change the number of plan types or the plan type labels after you create the application. Plan type labels can be up to eight characters long.
Completing Application Setup
Completing Application Setup

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

Creating the application, creates a folder in Analytic Services with the application name and two files in the application directory a .app file and a .log file. In order to create an initial outline with the dimension structure, you select to create the databases from the Administration > Manage Database window.
Reregistering Applications
Reregistering Applications
Your Planning applications definition is stored in a relational database, but its data is stored in Analytic Services. To bridge the communication between the relational database and Analytic Services, you need to register a DSN for each application. If you created a new application and selected a Shared Services project, your application is registered. You can use the Classic Application Wizard to reregister an application with Shared Services.
B-20
Building Member Hierarchies
Building Member Hierarchies

You can create and update dimensions by using the Dimension Editor. You can assign access rights to members, rearrange members in the dimension hierarchy, and change characteristics of dimension members. You use the Member Property tab to set and change member characteristics. To Add Dimension Members: 1. Select Administration > Dimensions. 2. From the Dimensions drop-down list, select the dimension. 3. Click Add Child or Add Sibling. 4. Set up the member properties, and then click Save.
Module 11 Appendices Appendix B Working with Classic Application Administration The next time you create or refresh the database, the Analytic Services outline is generated with members in the order that is displayed on the Dimensions window. You can add custom dimensions such as Customer or Product by selecting Add Dimension. You can add dimension members to custom dimensions the same way that you add members to Planning required dimensions.
B-22
Working with Attributes
Working with Attributes

You can set up attributes to add another level of granularity to your data. You create attributes for a dimension to group its members according to the same criterion. You create attribute values which are assigned to dimension members. For example, you can create an attribute called Channel for the Product dimension. Channel can have values of retail outlets, catalog, and internet. You then assign the values of either retail outlets, catalog, or internet to members of the Product dimension. You can filter members by their attribute values when creating data forms and reports.
NOTE
Only sparse dimensions can contain attributes. You must assign attribute values to dimension members at the same level within a dimension. Data values for attribute values are dynamically calculated and not stored.
Module 11 Appendices Appendix B Working with Classic Application Administration To Set Up Attributes: 1. Select Administration > Dimensions. 2. From the Dimension drop-down list, select the dimension for which to create attributes. 3. Select the dimension name, such as Customer or Product. 4. Click Custom Attributes. 5. By the Attributes in dimension column, Click Create. 6. Enter the name of the attribute. 7. Optionally, press Enter if you have more attributes to enter. 8. Click Save when you are finished adding attributes. 9. When done saving new attributes click Cancel to close the Create Attributes dialog box. 10. Select the attribute for which you want to enter values, and click Create above the attribute values column. 11. Enter the value for the attribute. 12. Optionally, press Enter if you have more values to enter. 13. Click Save when you are finished adding attribute values. 14. When done saving new attribute values click Cancel to close the Create Attribute Value dialog box. 15. Click Close to close the Manage Attributes and Values window. To Assign Attribute to Members: 1. From the Dimension drop-down list, select the dimension for whose member you want to assign an attribute value. 2. Select the member to which to assign an attribute value. 3. Click Edit. 4. Select Attribute Values. 5. From the Attribute Values list, select the attribute value to assign to the member and then click Add and Save.
B-24
Creating Alias Tables
Creating Alias Tables

You can assign one or more alternate names, or aliases, to Planning Account, Currency, Entity, Scenario, Period, Version, Year, and user-defined dimension members. You can create up to ten aliases per dimension member, including the default alias. For example, members in the Account dimension may be identified by their number (100, 200, 300, and so on) or by their descriptive alias (Travel Expenses, Office Supplies, Consulting Fees). Members could also have aliases for different languages. You create alias tables from the Administration menu. You set up aliases for members on the Member Properties tab in the Dimension Editor. If you add or change aliases or alias tables, you must refresh the application. Administrators can set which alias table to display by default for the application in Application Settings. Business users can override the default selection by choosing the alias table from the Preferences option on the File menu.
Module 11 Appendices Appendix B Working with Classic Application Administration To Create Alias Tables: 1. Select Administration > Alias Tables. 2. Click Add. 3. Enter the name for the alias table, and click OK. To Set Up Aliases for Members: 1. Select Administration > Dimensions. 2. From the Dimension drop-down list, select a dimension. 3. Select the member in the hierarchy for which you want to set up an alias. 4. Click Edit. 5. On the Member Properties tab, from the Alias drop-down list, select the alias table. 6. For the alias value, enter a value. 7. Click Save.
B-26
Smart Lists Overview
Smart Lists Overview

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

1. Create the Smart List:
1. Set up Smart List properties. 2. Set up Smart List entries.
2. From the Dimension Editor, create a new member or use an existing member:
1. Set the Member Properties for the member and associate the new member with the Smart List. 2. Refresh the Planning Database.
3. Set up the Smart List to work on a data form
Smart List Creation Process

Administrators can set up smart lists. After you create the smart list, you assign the smart list to dimension members as a member property. After the smart list has been created and assigned to the dimension member, you can use smart lists on data forms, by selecting the dimension member for the data form. For example, if you have an account called ProjectCat to represent project categories and you assigned a smart list (Project_Category) to that account, you would select ProjectCat as the account member to show on the data form.
B-28
Creating Smart Lists
Creating Smart Lists

You use the Smart Lists page to create, edit, and delete Smart Lists. You create smart lists by assigning values on the Properties, and Entries tabs and can review your smart list by selecting the Preview tab. You add values on the Entries tab to define the selections in the Smart List. To create Smar t Lists: 1. Select Administration > Manage Smart Lists. 2. Click Create, enter a name, and click OK.
Module 11 Appendices Appendix B Working with Classic Application Administration To Set Up Smar t Lists: 1. Select the Smart List, and click Edit. 2. Set up the Smart List properties. 3. Select Entries. 4. Click Add. 5. If you selected to automatically generate the numeric ID then do the following: Type the Name Type the Label 6. If you did not select to automatically generate the numeric ID then do the following: Type the ID Type the Name Type the Label 7. Select the Preview tab to review your smart list. 8. To save the smart list, click Save.
B-30
Associating Smart Lists

Smart lists are associated with members from a dimension, typically the Account dimension Reserve the member to store smart list values and do not use that member to enter any regular data values Consider setting up a separate rollup within the dimension for the members for which smart lists are assigned Place the member representing the Smart List onto data forms
Associating Smart Lists

After you create and set up Smart Lists, you associate Smart Lists to members as a member property. You then modify data forms to include the member. Business users working with the data form click into cells whose members are associated with a Smart List, and select from a drop-down list instead of entering data.
Setting Up UDAs
Set up UDAs to group members Create and Assign UDAs in the Dimension Editor
Setting Up UDAs
You can use user-defined attributes (UDAs)words or phrases describing a characteristic of memberswithin calc scripts, member formulas, and reports to return lists of members associated with the specified UDA. For example, say you have a Product dimension Using Smart Lists, UDAs, and Member Formulas with various product members. You could create a UDA called New Products and base certain calculations only on new products. UDAs are specific to dimensions. For example, creating a UDA for an Account member makes it available for non-shared Account members. Deleting it removes it for all Account members. To make UDAs available for multiple dimensions, create the same UDA for multiple dimensions. For example, create a UDA named New for Account and Entity dimensions to make the UDA named New available for Account and Entity members. You create, change, and select UDAs for members from the UDA tab. B-32 Planning: Create and Manage Applications
Module 11 Appendices Appendix B Working with Classic Application Administration To Create UDAs: 1. Select Administration > Dimensions. 2. In the Dimensions drop-down list, select the dimension for whose member to create the UDA. 3. From the dimension hierarchy, select a member, and click Edit. 4. Navigate to the UDA tab. 5. On the UDA tab, click Add. 6. Enter a name and click Save. To Select UDAs for members: 1. Select the UDAs for the member and move them to the Selected UDA window. 2. Click Save.
Setting Up Member Formulas

Profit Percent = Gross Profit%Net Sales;
Setting Up Member Formulas

You use the Member Formula tab to set up formulas to combine operators, calculation functions, dimension and member names, and numeric constants to perform calculations on members. You can set up member formulas to calculate data differently than what is represented in the outline structure. For example, gross profit and net sales are calculated by accumulating data from members in the Analytic Services outline. In order to calculate profit percent, you create a member formula which uses the gross profit and net sales members.
NOTE
You must place a semicolon at the end of each member formula.
B-34
Data Integration Management

Integrate ERP and transaction processing applications with analytic applications Link relational databases, applications, and text files with BPM applications Ensure data consistency
Data Integration Management

Data Integration Management provides bi-directional data movement from ERP and CRM applications to multiple applications, such as Hyperion System 9 BI+ Analytic Services, Hyperion System 9 Planning, Hyperion System 9 Financial Management, and query and reporting applications.
Planning Adapter Overview

Source/Target
Planning
DSN
Workflow Manager
Planning Adapter
Workflow Monitor
PowerCenter Server
Designer Analytic Services Adapter
Repository Server
Repository
Planning Adapter Overview

The Planning adapter enables you to connect between the PowerCenter server and the Planning Server. It is compatible with all Planning modules including Workforce Planning and Capital Expense Planning. The Planning Adapter enables you to perform the following tasks: Load metadata into attribute and custom dimensions in Planning Create UDA (User Defined Attribute) dimension targets
NOTE
You can use the Analytic Services adapter to extract data and metadata from Planning dimensions.
B-36
Working with Planning Targets

You must configure the following objects before you can import Planning targets: Planning data source names Planning target definitions User defined attribute targets
Working with Planning Targets

You create a Planning target to specify where and how to load information into Planning. For example, you can specify a target to load metadata into the Account dimension within Planning.
Creating Planning DSNs

1
Creating Planning DSNs

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

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

You can import User Defined Attribute (UDA) targets into Planning. When you create a Planning UDA target, the default table name is Planning_UDA. UDAs are associated with members of an outline to describe a characteristic of the members. Users can specify UDAs within calculation scripts and reports so that they return lists of members that have the specified UDA associated with them. The UDA table ports are Dimension (required), UDA, and Operation. In the Dimension port, you enter the dimension name for the UDA. When you load metadata to a planning database, If the UDA already exists, its properties are modified, otherwise the record is added. The UDA port value must meet the following requirements: Alphanumeric 80 characters or less B-40 Planning: Create and Manage Applications
Module 11 Appendices Appendix B Working with Classic Application Administration Not a word reserved for Analytic Services UDA name: - No tabs, double quotation marks (), or backlash (\) characters - Cannot start with the following characters: \ < , = @ _ + - { } ( ) The Operation port defaults to the Update value, but you can use the following values as well: Update - Adds, updates, or moves the member being loaded. Delete Level 0 - Deletes the member being loaded if it does not have children. Delete Idescendants - Deletes the member being loaded and its descendants. Delete Descendants - Deletes the descendants of the member being loaded, but does not delete the member.
Loading Metadata to Planning

To load metadata to Planning, you perform the following tasks: In Designer, create a mapping In Workflow Manager:
Create a Planning connection Create a workflow and configure the session task
Loading Metadata to Planning

After you define Planning targets, you can use them to load metadata to Planning. To do this, in Designer, create a mapping that includes a Planning target. In Workflow Manager, create a Planning application connection and Planning workflow, and configure the workflow session task.
B-42
Creating Planning Connections
1 2 3
Creating Planning Connections

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

Once you have mapped a session task within a workflow, you must configure the task with the proper connections. In this example, the target connection type is Hyperion Planning Application connection. To configure session tasks: 1. In Workflow Designer, create a workflow. 2. Right-click the session task and select Edit. The Edit Tasks window is displayed. 3. Select the Mapping tab to ensure that the correct connections are specified for the target and source. 4. Click OK.
B-44
Summary
In this lesson, you should have learned to: Describe classic administration List the steps for creating Planning applications Create Planning applications using classic application administration Set up dimensions and members in Planning Load metadata files
B-46

Hyperion Planning Student Guide

Uploaded by

Document Information

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 Student Guide

Uploaded by

Copyright:

Available Formats

Hyperion Planning 9.

3: Create and Manage Applications

D50751GC10 Edition 1.0 June 2007 D50935

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

Designing Data Forms

Creating Data Forms and Folders

Module 6 Lesson 17 Creating Data Forms and Folders

Designing Data Forms

Data Forms and Folders Overview

Data Forms and Folders Overview

Planning: Create and Manage Applications

Data Form Elements

Currency = Local Customer = No Customer

Data Form Elements

Planning: Create and Manage Applications

Module 6 Lesson 17 Creating Data Forms and Folders

Designing Data Forms

Planning: Create and Manage Applications

Creating Folder Structures for Data Forms

Creating Folder Structures for Data Forms

Planning: Create and Manage Applications

Module 6 Lesson 17 Creating Data Forms and Folders

Designing Data Forms