Professional Documents
Culture Documents
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
Table of Contents
Table of Contents
Table of Contents
vi
Table of Contents
Associating Smart Lists with Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22 Setting Data Forms to Use Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
vii
Table of Contents
Module 4: Loading Data and Calculating the Database Lesson 13: Loading and Calculating Data Overview
Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 Requirements for Data Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 Multicurrency Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6 Setting Up Data Load Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7 Staging Data Using Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9 Data Calculation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10 Calculations Within Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11 viii Planning: Create and Manage Applications
Table of Contents
ix
Table of Contents
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
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
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
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
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
xv
Table of Contents
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
xxi
Preface
xxii
M O D U L E
6
16
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
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
17-2
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
Page Columns
Rows
Point of View
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
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
You can search to find a data form on the Data Form Management page.
17-5
17-6
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
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
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
17-9
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
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.
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
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
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
User variables filter members displayed in data forms; for example MYCostCenter = Central (Descendants inclusive).
No user variable
User variable
17-16
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
17-17
17-18
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
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
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
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
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
17-24
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
17-25
17-26
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
17-27
17-28
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
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.
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
Module 6 Designing Data Forms Lesson 17 Creating Data Forms and Folders
Summary
In this lesson, you should have learned to: Manage data forms and folders Set up row and column properties Set up page and POV properties Assign business rules to data forms Set up display and precision options Manage data forms Create composite data forms Print data form definition reports Assign access rights to data forms
17-31
17-32
L E S S O N
1 8
18
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
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
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
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.
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. 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
18-12
18-13
18-14
18-15
18-17
18-18
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
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
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
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
19-2
View Pane
Content Area
Copyright 2007, Hyperion. All rights reserved.
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.
Page list
Data-entry cells
19-4
19-5
19-6
Cell with Modified Data Cell with Cell Text Locked Cell
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
Showing children
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
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
19-13
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
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
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
19-19
19-20
Add annotations
Cell text Account annotation Planning unit annotation
19-21
19-22
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
Account Annotation
Copyright 2007, Hyperion. All rights reserved.
19-25
Section
Description
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
19-26
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
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
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
19-32
Business Rules
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
19-33
Network Sales, Chip Sales, and Computer Sales use data values.
19-34
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
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
Planning
Financial Management
Analytic Services
20-2
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
20-3
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
Client Tier
Analytic Services
RDBMS
Data Tier
20-4
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
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
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
20-7
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
View instructions Adjust data Enter cell text Lock and spread values to base periods Enter supporting detail Calculate data Enter and preserve formulas
20-8
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
20-9
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
Row Headings
20-10
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
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
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
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
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
20-15
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
20-16
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
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
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
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
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
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
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
Summary
In this lesson, you should have learned to: Describe Smart View Enter, adjust, calculate, and analyze Planning data using Smart View Work with Planning data
20-23
Module 7 Entering Data in Hyperion System 9 Planning Lesson 20 Entering Data Using Smart View
20-24
M O D U L E
8
20
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
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
Choose graphical components to build rules Store rules in a central repository where you can organize them into projects
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
Roles
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
21-5
Lists all objects in the Business Rules repository including business rules, sequences, macros, and variables.
Access and work with Business Rules nodes. Create and edit graphical business rules. View the database outline.
Copyright 2007, Hyperion. All rights reserved.
21-6
Formulas
21-7
Select Members
21-8
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
2 3 5
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
Calculation Options and Methods Value type of User defined can be specified through Member Selection
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
4 All descendants of North America are included with the exception of Central and its descendants
1 3 6
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
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
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
Planning
21-21
3
Copyright 2007, Hyperion. All rights reserved.
21-22
To launch the rule from the Edit menu: 1. Select a Rule 2. Click Launch 3. Click Close 1
2
Copyright 2007, Hyperion. All rights reserved.
21-24
Source
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
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
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
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
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
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
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
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
22-8
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
22-9
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
22-10
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
Summary
In this lesson, you should have learned to: Describe runtime prompts Create runtime prompts
22-11
Module 8 Adding Business Rules Lesson 22 Building Runtime Prompts for Business Rules
22-12
L E S S O N
2 3
23
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
Specify certain criteria that must be met before the business rule calculates data.
23-2
5 2
23-3
(500/1000) * $100,000 =
(300/1000) * $100,000 =
Department 2 $30,000
(200/1000) * $100,000 =
Department 1 $20,000
23-4
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.
23-5
% 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
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
23-8
23-9
23-10
Custom Toolbar
Available Operators
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
7 1
3 4
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
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
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
Promote
Review
Sign Off
Approve
Reject
24-2
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
Approve
Approved
Under Review
24-4
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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.
Approved
24-5
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
Reviewer Actions
Start Status Not Started First Pass Under Review Under Review Under Review Under Review
End Status First Pass Under Review Under Review Signed Off
Current Owner Everyone with rights First owner New owner Same owner
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
= = =
= * * *
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.
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
24-10
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
24-13
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
24-14
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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
Module 9 Managing the Planning Process Lesson 24 Managing the Approval Process
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
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
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
25-4
25-5
View instructions.
25-6
25-7
25-8
View Instructions.
25-9
25-10
25-11
3 2
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
3 2
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
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
25-19
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
25-21
25-22
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
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
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
Application tier
Database tier
Analytic Services
Planning
Financial Management
SAP/ BW
Repository
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
26-12
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
Enter password
26-13
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
26-14
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
Object name
Object type
26-16
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
26-20
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
Print Preview
Web Preview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 26 Financial Reporting Overview
26-24
L E S S O N
2 7
27
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
Copyright 2007, Hyperion. All rights reserved.
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
Process bar
View pane
Adjuster
Content area
27-4
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
Element Name Standard toolbar View pane Description Provides shortcut buttons for performing tasks Provides buttons that enable jumps between panels
27-5
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-7
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
Setting Preferences
Select File > Preferences.
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.
27-8
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-9
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-10
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-11
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
Search criteria
Search results
27-16
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
Previewing Reports
User POV
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
Search results
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:
27-20
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-21
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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.
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-26
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-27
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
27-28
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
Module 10 Analyzing Planning Data with Financial Reporting Lesson 27 Navigating Reports in Workspace
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
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
HYPlan application
Finbud application
Actuals
A-2
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
Execute Synchronization
A-6
Linking Dimensions
Insert mapping tables in Data Synchronization to ensure correct data linking between members.
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
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
After the filter is applied to the dimension, a filter icon is inserted next to the dimension name on the Link Dimension page.
A-10
A-12
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
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
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).
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.
B-6
HPSystem
CorpPlan TaxPlan Finbud
Finbud
TaxPlan
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.
Data Source
Calendar
Currencies
Plan Types
B-10
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
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.
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.
B-18
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
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
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
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
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.
B-28
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
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.
B-34
Planning
DSN
Workflow Manager
Planning Adapter
Workflow Monitor
PowerCenter Server
Repository Server
Repository
NOTE
You can use the Analytic Services adapter to extract data and metadata from Planning dimensions.
B-36
B-38
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.
B-42
1 2 3
1 2
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