D50751GC10 Edition 1.0 June 2007 D50935
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. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
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
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
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
Version Dimension . . . 5-12 Creating Versions. . . 5-14
Lesson 6: Setting Up the Entity Dimension
Entities Overview . . . 6-2 Entity Members and Plan Types . . . 6-3 Identifying the Currency Value for Entities . . . 6-5 Adding and Modifying Entities . . . 6-6 Saving Dimensions . . . 6-8 Deleting Entities . . . 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
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
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
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
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
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
Performing Ad Hoc Analysis . . . 19-22 Exporting Data to Spreadsheets . . . 19-23 Adding Annotations . . . 19-24 Adding Cell Text and Account Annotations . . . 19-25 Adding Planning Unit Annotations . . . 19-26 Adding Supporting Detail . . . 19-27 Calculating Data in Data Forms . . . 19-29 Calculate Data Form Calculation Script . . . 19-31 Calculate Currencies Calculation Script. . . 19-32 Business Rules . . . 19-33 Entering Data with Smart Lists. . . 19-34 Navigating Data Forms with Menus . . . 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 . . . 21-2 Business Rules Roles . . . 21-4 Prerequisites for Accessing Business Rules . . . 21-5 Navigating Business Rules . . . 21-6
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
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
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
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
Data Integration Management . . . B-35 Planning Adapter Overview . . . B-36 Working with Planning Targets. . . B-37 Creating Planning DSNs . . . B-38 Importing Target Definitions . . . B-39 Creating UDA Targets . . . B-40 Loading Metadata to Planning . . . B-42 Creating Planning Connections . . . B-43 Configuring Session Tasks. . . B-44
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
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 class—the 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.
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.
N O T E
A note provides related information, common mistakes, or cautions about the current topic.
T I P
A tip provides information that helps you work more efficiently.
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
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
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
Data Forms and Folders Overview
Each data form is associated with a plan type.
You assign access to data forms.
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.
Data Form Elements
Page Columns
Rows
Point of View Currency = Local
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.
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.
T I P
You can search to find a data form on the Data Form Management page.
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.
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 form’s plan type.
N O T E
You cannot change the plan type for a data form.
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.
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.
You can use member relationships to select shared members. For example, to include all members of a rollup on a data form, you can select an alternate, functional rollup. Values entered into rows or columns that display shared members are saved to the base
members in the database.
Another factor to consider in the setup of data forms is how to represent the Currency dimension. You set up the Currency dimension on a data form to determine how
currency values are displayed. If a row or column on a data form has the Local member selected for the Currency dimension, no currency conversion takes place for the row or column, and you can enter data for the entities on the row or column in their native currency.
If you set a data form’s Currency member to something other than Local, then data values are displayed as converted to the selected currency, assuming that the currency calculation script has been run. The data form is read-only.
In target versions, you can enter data in rows or columns that have Currency or Local as the selected member. For applications that use a single currency, the currency selected when you created the application is used as the currency member for all entities.
To allow users to enter data in currencies other than an entity’s base currency, when selecting data-form members, you must perform one of the following actions:
• 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.
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.
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.
• To move a dimension from one axis to another, delete it from the source axis and select it for the destination axis.
Data form designers, when considering how to set up data forms, need to consider dimension composition. For columns, data form designers should use dimensions and members that business users are most likely to need to view. For example, the Period dimension—which represents months, quarters, years, or custom time periods—is typically set up on the columns. For rows, data form designers should use dimensions and members that contain a more expansive list of members. For example, the Account, Customer, and Product dimensions typically work well on the rows.
Setting Up Segment Properties
Segments are areas of data forms with special properties, such as separator lines for columns and rows and hidden or read-only data. You can define segments for
asymmetric rows and columns. For example, you can set segment properties in an asymmetric row or column to read-only or to hide members. You can also suppress the hierarchy so row definitions are not indented and columns do not include line breaks. You can select options for segment properties as described in the following table:
Setting Column Properties
The following table shows the options for column width on a data form:
Option Description
Hide Hide the segment so it is not displayed on the data form
Suppress Hierarchy For columns, do not display line breaks For rows, do not display indentation
Read only Create a read-only segment in the data form to enable comparison of old, read-only data with new, editable data Show Separator Create a bold border before the segment to visually distinguish
parts of the data form
Apply to All Segments Apply these settings to all columns in segments
Column Width Description
Small Displays columns 50 pixels wide (approximately 7 decimal places) Medium Displays columns 75 pixels wide (approximately 10 decimal
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:
Large Displays columns 100 pixels wide (approximately 13 decimal
places)
Size-to-Fit Forces all column headings to fit in the displayed space
Custom Enables you to enter a pixel width value of up to 999 (greater than 13 decimal places)
Task Action
Resize column width Drag the column heading.
Minimize column width Click the column heading and select Minimize, or double-click the column heading.
Restore a minimized
column Right-click the minimized column heading and select Restore,or double-click the minimized column heading. Restore all minimized
columns Right-click any column heading, and select Restore All. Reset all column widths to
the data form definition default property setting
Right-click any column heading, and select Reset All to Default.
You can set row properties for data form rows. The following table describes the options that you can set on rows in data forms:
Option Description
Suppress missing blocks When suppressing a large number of rows, such as 90% or more, select this option to enhance performance of the “Suppress missing data” setting. If few or no rows are suppressed, the “Suppress missing blocks” setting can degrade performance. Hyperion recommends that you test data forms before and after using this setting to determine whether performance is improved. You should also test data forms whenever you make significant changes to your application.
With this setting, data forms may not display attributes. Also, certain suppressed blocks may ignore Dynamic Calc
members.
Suppress missing data Select this option to suppress missing data. Selecting this option hides rows without data. If at least one cell of a row has a data value, then the row is not suppressed. Clear this option to display rows that contain only cells for which data is missing; the cells display #missing. You cannot
simultaneously select “Suppress missing data” and “Allow users to dynamically add rows.”
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 form’s definition by adding rows. Members that users can access are displayed on the data form. You cannot
simultaneously select “Allow users to dynamically add rows” and “Suppress missing data.”
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 Members Included on the Data Form
Member The selected member
Descendants All members below the selected member, excluding the selected member
Descendants (Inc) The selected member and all of its descendants
Ancestors All members above the selected member, excluding the selected member
Selecting Members
Member Descendants Descendants (Inc) Ancestors Ancestors (Inc) Siblings Siblings (Inc) Parent Parent (Inc) Children Children (Inc) Level 0 DescendantsDescendants plus North America Worldwide
Worldwide plus North America
200, 205, 210, 220, 225, 230, 240, 245, 250, 255, 270, 275, 280
Europe, PacRim, Corporate
Europe, PacRim, Corporate, North America Worldwide
Worldwide and North America Central, South, East, West
Siblings All members in the level of the selected member, excluding the selected member
Siblings (Inc) The selected member and all of its siblings
Parent The member in the level above the selected member, excluding the selected member
Parent (Inc) The selected member and its parent
Children All members in the level immediately below the selected member, excluding the selected member
Children (Inc) The selected member and all of its children Level 0
Descendants All descendants of the selected member that have no children
T I P
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
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).
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.
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
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.
Setting Options on the Other Options Tab
On the Other Options tab, you can set options for the data form’s display, functionality, and printing. For example, you can select to display missing values as blank rather than as #missing.
Enable account annotations
You can enable account-level annotations. In a data form, users can add annotations to accounts. However, a user must have Write access to the individual Account, Entity, Scenario, and Version members. Account-level annotations can vary, as combinations of Scenario, Version, and Entity dimensions vary.
To enable annotations for the account dimension, you must follow these rules: • Account must be selected as a row dimension.
• 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.
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.
N O T E
When a data form that is designed to suppress missing data is reloaded, rows that contains only cells with #missing are not displayed.
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
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.
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. N O T E
When launching a business rule with a runtime prompt, Planning validates the value entered, but it does not validate the business rule.
N O T E
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.
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.
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
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.
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.
Selecting Business Rules
on Composite Data Forms
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.
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 user’s group rights.
You create and change data form designs by using the Manage Data Forms option on the Administration menu. Administrators and interactive users have access to this task. When you are designing a data form in Planning, the selection list to set properties is filtered based on access rights. For example, when you set up the data form layout for page, column, row, and point of view, you select from the list of dimension members to which you have Read or Write access.
Assigning Access Rights to Data Forms
Read: Enables users to view and use the data form for
data entry.
Write: Enables users to change the data form’s design
and to view and use the data form for data entry. None: Prevents users from viewing the data form.
To get the latest set of users and groups from the User Management Console, click Refresh User/Group lists.
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..
N O T E
Access rights are assigned to data forms, not to data form folders. You can assign access to only one data form at a time.
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
Objectives
After completing this lesson, you should be able to: • Export and import data forms
• Create menus
• Specify application default settings • Manage user variables
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.
N O T E
If you installed Planning to the default location, the Utils directory is located in the following path: x:\Hyperion\HyperionPlanning\Utils.
Copyright © 2007, Hyperion. All rights reserved.
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>
Parameter Description
import or
export Specify whether to import or export the data form definition. file name or
data form name
Use file name to specify the name of the XML file to import into the Planning application.
Use data form name to specify the Planning data form to export to XML. planning
server name Specify the name of the application server that Planning is using (for example, localhost). user name Enter the name that you use to log on to the Planning application (for
example, smith).
password Enter the password that you use to log on to the Planning application (for example, pass1).
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 Copyright © 2007, Hyperion. All rights reserved.
Menus
1. Create the menu.
2. Set up menu Item properties for the menu.
3. Associate the menu with data forms.
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).
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.
Copyright © 2007, Hyperion. All rights reserved.
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 Description
Menu Item Enter a unique name that contains only alphanumeric and underscore characters (for example: Position) and no extended characters, special characters, or spaces.
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 menu’s label to File, set it to File directly or set it to the name of a resource—such as LABEL_FILE.
Icon Optional: In context of the Planning server, enter the path to and name of a graphic (for example,
8. To set up characteristics for menu items, select the menu item, and click Edit. Menu item properties differ, depending upon the menu item’s
type. The following table describes the choices that you can apply for each item.
Type Select the menu item type. Your selection determines the available properties. For example, no properties are available for the Menu Header type. Choose from the following types:
• Data Form—Launch a selected data form. When users right-click in the source data form, the member selection context for the member, page, and POV is retained. If the target data form contains the dimension members identified by the context, the target data form’s page is set to match the context.
• URL—Navigate to the specified URL.
• Business Rule—Launch the selected business rule.
• Workflow—Move to the Manage Process page to work with a planning unit.
• Menu Header—Create a menu under which you can create child menu items. To distinguish the header from other menu items, insert a separator bar by entering one hyphen as the label for the header item. For menu headers, the Required Dimension list is not available.
Required Dimension Select the dimension for which the menu item is displayed. For example, if, for a menu item, you select Account, when users right-click Account members, the menu item is available. Selecting No Required Dimension makes the menu available wherever the user right-clicks in the data form.
Item Description
Data Form a. From Data Form Folder, select the folder that contains the destination data form.
b. From Data Form, select the data form.
URL 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.
9. Click Save.
Business Rule a. From Plan Type, select the plan type for which the business rule is available.
b. From Business Rules, select the business rule to launch. c. From View Type, select how to display runtime prompt pages: • Classic View—Use the default Planning view.
• Streamline View—Display each runtime prompt on a different line, instead of in a different section; eliminate icons; and reduce screen text.
d. Optional: In Window Title, enter a title to be displayed, instead of Runtime Prompts.
e. Optional: In OK Button Label, enter the text to be displayed for the OK button.
f. Optional: In Cancel Button Label, enter the text to be displayed for the Cancel button.
g. Optional: Select Launch in a Separate Window to launch the business rule in window other than the Planning main window. Workflow Specify the planning unit to which the user is directed by selecting
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.
Copyright © 2007, Hyperion. All rights reserved.
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. Non-administrators 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.
Copyright © 2007, Hyperion. All rights reserved.
Advanced Settings
System Settings Tab
The following table describes the options on the System Settings tab:
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.
Component Description
E-mail Server Type the name of the server that hosts e-mail services for the application users; for example, mail.hyperion.com.
Available only to the application owner. E-mail Character
Set Specify the character set used for e-mail messages:• UTF-8: Use the Unicode encoding format (the default). • Regional Setting: Use the system's regional setting. Task List Date
Format Set the date format for tasks in a task list: MM-DD-YYYY or DD-MM-YYYY.
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 Type the URL for the Shared Services server, and click Register Shared Services. Display Users’
Full Names Select Yes to show the users’ full names (for example, John Smith) in addition to their user names (for example, JSmith). Select No to suppress the display of the users’ full names.
Note: If the Display Users' Full Names check box is selected, you cannot
have two users with identical full names. If you try to add a user with the same full name as an existing user, an error message is displayed. Enable Use of the
Application for Specify whether users can access the application when it is in maintenance mode, such as during backups. Select Owner,
Administrators, or All Users to give access to the application owner, to administrators, or to all users.
Enable Offline
Planning 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.
Select User Assign an administrator to be the application owner. (By default, the person who creates the application is the application owner. However, the owner may grant ownership to another administrator.)
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 defaults—by selecting the Use Application Defaults check box on the Preferences tabs.
Copyright © 2007, Hyperion. All rights reserved.
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).
Copyright © 2007, Hyperion. All rights reserved.
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.
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.
Copyright © 2007, Hyperion. All rights reserved.
Creating User Variables
1
2
3
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 form: 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.
Copyright © 2007, Hyperion. All rights reserved.
Applying User Variables
1
2
