Bpma Admin

HYPERION® SYSTEM™ 9
BPM ARCHITECT
RELEASE 9.3.0.1.0
ADMINISTRATOR'S GUIDE
Copyright 2007 Hyperion Solutions.
All rights reserved.
“Hyperion,” the Hyperion logo, and Hyperion’s product names are trademarks of Hyperion. References to other
companies and their products use trademarks owned by the respective companies and are for reference purpose only.
No portion hereof may be reproduced or transmitted in form or by means, electronic or mechanical, including
photocopying, recording, or information storage and retrieval systems, for purpose other than the recipient’s personal
use, without the express written permission of Hyperion.
The information contained herein is subject to change without notice. Hyperion shall not be liable for errors contained
herein or consequential damages in connection with the furnishing, performance, or use hereof.
Hyperion software described herein is licensed exclusively subject to the conditions set forth in the Hyperion license
agreement.
Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Hyperion license
agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988),
FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable.
Hyperion Solutions
5450 Great America Parkway
Santa Clara, California 95054
Printed in the U.S.A.
Contents
Chapter 1. Using BPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About BPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
BPM Architect Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Logging on to Workspace and Accessing BPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . 12
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Navigating BPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Administering BPM Architect Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Starting and Stopping BPM Architect Dimension Server . . . . . . . . . . . . . . . . . . . . . . 17
Starting and Stopping BPM Architect Application Server . . . . . . . . . . . . . . . . . . . . . 18
Starting and Stopping BPM Architect Data Synchronizer Server . . . . . . . . . . . . . . . . 18
Chapter 2. Managing Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Importing into the Dimension Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Creating Flat Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Using Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Creating Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Managing Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Working with Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting up Alias Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Copying Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating Dimension Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Viewing and Deleting Dimension Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Deleting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Viewing Application Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Creating Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Working with Shared Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Removing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Deleting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Contents iii
Finding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Editing Property Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Viewing Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Working with User-Defined Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Working with Smart Lists (Planning Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Creating Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Modifying Smart List Dimension Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Displaying #Missing with Smart Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Associating Smart Lists to Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Working with Member Formulas (Planning, Essbase Analytics, and Enterprise Analytics
Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Validating Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Working with Formula Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Chapter 3. Managing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

About Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Workflow for Creating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Creating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Adding Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Modifying Planning Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Modifying Consolidation Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Modifying Enterprise Analytics and Essbase Analytics Application Views . . . . . . . . . . 77
Removing Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Viewing Dimension Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Viewing Application Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Working with Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Working with the Application Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Navigating the Application Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Editing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Opening Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Closing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Deleting Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Duplicating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Migrating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Reregistering Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Comparing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Viewing the Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Validating and Deploying Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Validating Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
iv Contents
Considerations for Deploying Planning Application Views . . . . . . . . . . . . . . . . . . . 100
Deploying Planning Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Deploying Consolidation Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Deploying Enterprise Analytics and Essbase Analytics Application Views . . . . . . . . . 104
Redeploying Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Considerations for Redeploying Planning Application Views . . . . . . . . . . . . . . . . . . 107
Redeploying Planning Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Chapter 4. Synchronizing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Understanding Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Synchronizing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Using Hyperion Application Views as Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Synchronizing Multiple Currency Planning Application Views . . . . . . . . . . . . . . . . 112
Using Hyperion Data Interface Tables as Sources . . . . . . . . . . . . . . . . . . . . . . . . . . 113
External Files as Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Mapping Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Filtering Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Assigning Default Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Inserting Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Editing Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Saving Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Working with Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Creating Mapping Tables in the Dimension Mapping . . . . . . . . . . . . . . . . . . . . . . . 122
Creating Mapping Tables in the Data Synchronizer . . . . . . . . . . . . . . . . . . . . . . . . . 125
Working with the Data Synchronizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Navigating the Data Synchronizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Editing Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Editing Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Duplicating Synchronizations and Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Deleting Synchronizations and Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Validating and Executing Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Chapter 5. Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Working with the Job Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Navigating the Job Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Changing the Job Console View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Refreshing the Job Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Creating Job Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Viewing Job Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Contents v
Viewing Import Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Viewing Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Deleting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Chapter 6. Using Task Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Prerequisites for Task Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Managing Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Creating Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
BPM Architect Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Adding Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Shared Services Stage Actions and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Adding Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Viewing Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Editing Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Copying Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Deleting Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Running Taskflows Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Managing Access Permissions to Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Assigning Access Permissions to Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Editing Permissions to Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Deleting Permissions to Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Viewing Taskflow Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Stopping Active Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Viewing the Taskflow Participant Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Viewing the Taskflow Participant Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Appendix A. Working with Financial Management Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Account Type Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Defining Dynamic Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Organization by Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Consolidation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Using Consolidation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Assigning Consolidation Methods Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
vi Contents
System-Generated Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Consolidation Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Ownership Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Setting Up Intercompany Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Editing System-Generated Value Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Metadata Filtering Based on Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Metadata Referential Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Metadata Referential Integrity Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Metadata Log File Referential Integrity Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Appendix B. Working with Planning Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Account Type Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Examples of Account Calculation for Zeros and Missing Values . . . . . . . . . . . . . . . 194
Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Working with Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Considerations for Working with Planning Dimensions . . . . . . . . . . . . . . . . . . . . . . . . 202
Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Planning Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Considerations for Excluding and Deleting Planning Members . . . . . . . . . . . . . . . . . . . 204
Considerations for Deleting Planning Application Views . . . . . . . . . . . . . . . . . . . . . . . . 204
Working with Shared Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Naming Restrictions for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Naming Restrictions for Dimensions, Members, and Aliases . . . . . . . . . . . . . . . . . . . . . 206
Appendix C. Working with Analytic Services Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Application View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Dimension and Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Appendix D. Working with Statistical and System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Contents vii
viii Contents
Using BPM Architect
1
In This Chapter
About BPM Architect................................................................................................................ 9
BPM Architect Modules............................................................................................................10
Architecture.........................................................................................................................11
Process Overview...................................................................................................................12
Logging on to Workspace and Accessing BPM Architect .......................................................................12
Security .............................................................................................................................13
Navigating BPM Architect .........................................................................................................14
Administering BPM Architect Servers ............................................................................................17
About BPM Architect

Hyperion® System™ 9 BPM Architect is a feature in Hyperion® System™ 9 Financial
Management™ and Hyperion® System™ 9 Planning™. BPM Architect enables administrators
to manage, create, and deploy Hyperion Applications within one interface.
Creation and Deployment:
● Create applications by dragging and dropping
● Design financial applications graphically, using one environment for all applications
● Create subject-specific financial applications using existing artifacts
● Configure dimensions and define properties from a predefined, sample library
● Create filters to select pieces of a dimension. For example, you can use the standard Account
dimension for an application but only use the Balance Sheet accounts. This enables you to
have one dimension to maintain but not use the full dimension in all applications.
● Duplicate applications for testing or what-if analyses
● Upgrade applications from previous releases to bring existing applications into the
Dimension and Application Library. This ensures that you are ready to get started with the
functionality within BPM Architect
Management:
● Visually link and manage applications.
● Reuse dimensions and attributes across multiple applications. For example, you can create
one Account dimension and use it in multiple applications. BPM Architect leverages existing
About BPM Architect 9

applications and dimensionality to spin off other applications with previously constructed
dimensions.
● Graphically manage data flows
● Perform impact analysis—graphically view and model relationships across applications
● Handle and evaluate the impact of exceptions and changes to all models
● Eliminate manual dimensional and data reconciliation between applications
This guide describes administration features introduced in BPM Architect. For information on
Classic Application Administration features (for applications not being managed using BPM
Architect), see the Hyperion System 9 Planning Administrator's Guide or the Hyperion System 9
Financial Management Administrator's Guide.
BPM Architect Modules

BPM Architect has the following modules:
● Dimension Library—A centralized location to manage dimensions and dimension
properties. You can use the Dimension Library to:
❍ Create dimension import profiles—enabling dimension updates from flat files and
relational database interface tables
❍ Add, delete, and modify dimension members
❍ Modify dimension and member properties
● Application Library—A summary of Application Views that have been created and/or
deployed to Financial Management, Planning, Hyperion® System™ 9 BI+™ Enterprise
Analytics™, or Hyperion® System™ 9 BI+™ Essbase Analytics™. Application Views contain
dimensions and dimension attributes that are designed to meet specific requirements for
Financial Management and Planning needs. You can use the Application Library to:
❍ Create Financial Management, Planning, Enterprise Analytics, or Essbase Analytics
Application Views based on Financial Management and Planning dimension sets
❍ Manage Application Views in one centralized location
❍ View the data flow between Application Views
❍ Migrate Application Views to different servers
❍ Deploy Application Views to Financial Management, Planning, Enterprise Analytics, or
Essbase Analytics
● Data Synchronization—Enables data synchronization within Hyperion applications. You
can use the Data Synchronizer to:
❍ Create data movement synchronizations between Hyperion applications. For example,
an administrator can synchronize data between two Financial Management
applications; two Planning applications, and between one Financial Management and
a Planning application
❍ Create data mappings for reuse
10 Using BPM Architect

❍ Create flat file and interface table mappings to import data into Hyperion applications
● Application Upgrade—Enables administrators to upgrade from previous Financial
Management and Planning releases.
● Job Console—Provides a summary of Dimension Library and Application View activities,
including imports, deployments, and data synchronizations.
Architecture
BPM Architect provides an interface to various sources for metadata and data including
Enterprise Resource Planning systems, relational databases, and data warehouses. Data
(dimensional hierarchies as well as data) from these sources can be imported into the system via
flat files or Hyperion interface tables.
Note:
This is a functional diagram and does not represent the number of servers needed for a
deployment.
BPM Architect provides a direct interface to Financial Management and Planning applications
enabling the creation, maintenance, and synchronization of these applications directly from
BPM Architect.
The middle tier of BPM Architect includes the required application services for application
construction, metadata management, data synchronization, and surfacing the user interface.
End users access BPM Architect via Hyperion® System™ 9 Workspace™ where they also can
access reporting content and application content.
Architecture 11
Process Overview
At a high-level, follow this process:
● Import dimensions using the Dimension Library. See Chapter 2, “Managing Dimensions.”
● Create Application Views. See Chapter 3, “Managing Application Views.”
● Drag and drop the dimensions to include in the Application View. See “Adding Dimensions”
on page 70.
● Deploy Application Views to a Hyperion product, such as Planning or Financial
Management. The Hyperion product creates the application and the product server loads
the metadata. See “Validating and Deploying Application Views” on page 99.
● Use Hyperion® System™ 9 Shared Services™ and assign access permissions. See the Hyperion
System 9 Security Guide.
● Use your Hyperion products to load data forms into the application. See the Hyperion System
9 Planning Administrator's Guide and Hyperion System 9 Financial Management
Administrator's Guide.
● Use your Hyperion products to create data forms, reports, plans, task lists, and so on.
Logging on to Workspace and Accessing BPM Architect

Before you log on to Workspace:
1. Ensure that Hyperion® License Server™ and Shared Services and Workspace Server are
running.
2. Ensure that IIS is running.
3. Ensure that the Dimension Server is running. For information on starting and stopping the
Dimension Server, see “Starting and Stopping BPM Architect Dimension Server” on page
17.
4. Ensure that the BPM Architect Application Server is running. For information on starting
and stopping the application server, see “Starting and Stopping BPM Architect Application
Server ” on page 18.
5. Start the Data Synchronizer Server by doing one of the following:
● From the Services panel, start Hyperion S9 BPMA DataSync ATS5 (for Tomcat);
Hyperion S9 BPMA DatSync WLS<version> (for WebLogic); or HyperionS9 BPMA
DataSync WAS<version> (for WebSphere).
● Select Start > Programs > Hyperion System 9 Applications+ > BPM Architect > Start
(Stop) BPMA Data Synchronizer.
● On the computer hosting your Java application server, locate the start or stop server
command.

➤ To log in to Workspace:
1 Log in to Workspace from the Start Menu (Start > Programs > Workspace > Launch Workspace) or
http://<WebServer>:<port>/workspace/, where <WebServer> is the Web server machine
host name and <port> is the Web server listen port. For example, the port number is 19000 if using the
Apache instance bundled with BI+ (http://WebServer: 19000/workspace/).
2 Enter your system user name and password and click Log On.
For information on setting up the URL, see the Hyperion System 9 Workspace Administrator’s
Guide.
Note:
If an error message displays indicating that BPM Architect is unable to authenticate the user,
verify the following: ensure that the user is provisioned for the application (if not, use Shared
Services to provision the user), the user's token or session might have timed out (in this case,
log off, then log back on to start a new session), or there could be a problem with the Hyperion
System 9 Financial Management Web Server or Application Server (in this case, contact your
system administrator).
See the Hyperion System 9 Financial Management Installation Guide or Hyperion System 9
Planning Installation Guide.
After you log in, you can use the Dimension Library to view, create, and manage dimensions
and hierarchies.
3 To access the Dimension Library, select Navigate > Administer > Dimension Library.
Security
BPM Architect supports these roles:
Table 1 BPM Architect Roles
Roles Tasks Performed
Planning Application Creator Can create applications, but can change only dimensions to which you have access
permissions. When an Application Creator deploys an application from BPM Architect,
Financial Application Creator
you automatically become the application owner.
Enterprise Analytics Creator
Note: All application creators can create Generic Application Views.
Essbase Analytics Creator
Dimension Editor Can import, delete, create, and change dimensions and dimension members. Can
also assign access permissions (Dimension Owner and Readers/Writers) to the
dimension. Cannot create applications.
Create Integrations Can create and execute data synchronizations.
Run Integrations Can execute data synchronizations.
For additional information on these roles, see the Hyperion System 9 Security Guide.
Security 13
Scenarios:
If Bob Smith selects an Application View in the Application Library and does not have the
Application Creator role for that Application View type or are a provisioned administrator for
the Application View, a dialog box is displayed indicating that Bob Smith does not have access
to this Application View. In addition, the menu items are disabled and the summary information
is limited. Consider this example:
Bob Smith selects App2 for which he is not a provisioned administrator and he does not
have any creator roles. Upon selecting the Application View a message is displayed informing
him that he has no rights to this Application View. When Bob Smith right-clicks, all options
are disabled.
If an Application View is not deployed, then all applicable options and summary information
is available to users who are creators for that application type (Consolidation, Planning,
Enterprise Analytics, and Essbase Analytics). Consider this example:
The Application Library contains five Planning Applications Views (App_6, App7, App8,
and App9 (deployed) and App10 (undeployed) and five Consolidation Application Views
(App1, App2, App3, and App4 (deployed) and App5 (undeployed). Bob Smith is a
Consolidation Application Creator, Karen Jones is a Planning Application Creator, and Jim
Harrington is an Admin for App1. Bob Smith can perform all applicable operations on App5
(deploy, edit, compare, and so on). Karen Smith can also perform all applicable operations
on App10 (deploy, edit, compare, and so on).
Any user who is provisioned as an administrator for deployed Application Views can perform
the full set of operations (delete, redeploy, migrate, and so on). Consider this example:
Jim Harrington, the administrator for App1, has full access to App1. Any user who is not a
provisioned administrator, but is an application creator has access to all the operations that
do not require product specific roles like edit, duplicate, compare, validate, and so on.
Operations that require application specific roles will fail (delete, redeploy, and migrate).
For example, Bob Smith will be able to edit and compare App1 through App4, but will not
be able to delete, redeploy or migrate them.
Navigating BPM Architect

From Workspace access the following from the Navigate menu:
● Applications—enables you to access Consolidation (Financial Management), Planning,
Essbase Analytics, and Enterprise Analytics applications. Applications are only displayed
when a user has the rights and the applications are available.
● Administer—enables you to manage users, groups, user preferences, roles, and
authentication methods. In addition, Administer enables you to access these BPM Architect
modules:
❍ Dimension Library
❍ Application Library
❍ Data Synchronization

❍ Job Console
❍ Application Upgrade
Toolbars
Standard
The Standard toolbar is used for common Workspace features.
Table 2 Standard Toolbar Buttons
Button Menu Command Description
File > New > Document Create documents, such as books, batches, analysis documents, and
scheduled batch jobs
File > Open > Document Use repository documents
Navigate > Explore Display Explore, to display the repository as a file management system
File > Logoff End the current session
Help > Help on This Topic Displays help for the page displayed in the content area
BPM Architect
The BPM Architect toolbar displays buttons specific to it.
Table 3 BPM Architect Toolbar Buttons
Button Menu Command Description
View > Refresh Refreshes the window.
View > Download Transaction Logs Displays the Filter Transaction Log dialog box.*
*Displays in the Dimension Library only.
Menus
BPM Architect options display in addition to Workspace options. The following sections
describe BPM Architect options only.
Navigating BPM Architect 15

File Menu
Table 4 File Menu
Command Description
New > Dimension Creates a dimension*
New > Application View Creates an Application View.†
*Displays in the Dimension Library only.

†Displays in all modules, except Application Upgrade.
View Menu
You can use the View menu to display specific panes in BPM Architect. These options do not
serve as a toggle. To close a pane, use the close button.
Table 5 View Menu
Command Description
Workspace
View Pane Displays the Workspace View pane. To hide the View pane, click Hide (in the middle of
the vertical divider or click View > View Pane.)
Dimension Library
Show Master View Displays the Master View
Show App View Displays the Application View pane
Show Property Grid Displays the Property Grid.
Show Member List Displays the Member Find pane
Refresh Refreshes the display
Download Transaction Logs Displays the Filter Transaction Log dialog box
Member Display Applicable for Alias dimensions. When you select this option, you must manually
refresh. After refreshing changes display for dimensions that are associated with alias
dimensions that have a Default Member specified in the System properties.
Data Synchronization, Job Console, and Application Library
Icon Displays icons and the name of the artifact.*
Details Displays the artifact name, description, and additional details
Refresh Refreshes the display
Filter Displays the Filter dialog box, enabling you to filter what you see in the module
*Displays in Data Synchronization and Application Library only.

Administration Menu
The Administration menu is displayed when you open a BPM Architect module (Dimension
Library, Application Library, Job Console, or Data Synchronization).
Table 6 Administration Menu
Command Description
Manage Taskflows Automates tasks that you commonly perform
View Taskflow Status Displays the status of any automated tasks
Help Menu
You use the Help menu to access BPM Architect Help and information about BPM Architect.
Administering BPM Architect Servers

BPM Architect has three servers that must be running:
● Dimension Server
● BPM Architect Application Server
● Data Synchronizer Server
The following sections describe how to start and stop BPM Architect servers.
Starting and Stopping BPM Architect Dimension Server

You can start and stop the BPM Architect Dimension server from the Start menu or through
the Services panel.
➤ To start or stop the Dimension server:

Do one of the following:
● Select Start > Programs > Hyperion System 9 Applications+ > BPM Architect > Start (Stop)
Hyperion S9 Dimension Server.
● From the Services panel, start Hyperion BPM Architect Process Manager.
➤ To increase the timeout setting for startup of Dimension Server:

If you experience a problem with starting up the service for the Dimension server (Hyperion
BPM Architect Process Manager), you can change the timeout setting. The default timeout
setting for startup of the Dimension server is 180 seconds.
1. Open BPMA_Server_Config.xml. This file is located in %HYPERION_HOME%\BPMA
\AppServer\DimensionServer\ServerEngine\bin.
Administering BPM Architect Servers 17

2. Search for DimensionServerStartupTimeout under Config > ProcessManager and
change the value of the timeout (in seconds).
Starting and Stopping BPM Architect Application Server

You can start and stop the BPM Architect Application Server from the Services panel, the Start
menu or by using a command. The location of the command depends on which Java application
server you are using.
➤ To start or stop the BPM Architect application server:

● From the Services panel, start Hyperion S9 BPMA Web ATS5 (for Tomcat); Hyperion S9
BPMA Web WLS<version> (for WebLogic); or HyperionS9 BPMA Web WAS<version>
(for WebSphere).
Server BPM Architect.
command.
Table 7 Location Example for StartBPMAWebServer and StopBPMAWeb Server Commands
If you are using: Go to the following directory (for example) Execute This Command
Tomcat <drive letter>:\Hyperion\ BPMA Double-click

\AppServer\InstalledApps startBPMAWebServer.bat or
\Tomcat\5.0.28\BPMAWebServer stopBPMAWebServer.bat
WebLogic <drive letter>:\Hyperion\ BPMA Double-click startBPMAWebTier.cmd or

\AppServer\InstalledApps stopBPMAWebTier.cmd
\WebLogic\<version>
\BPMAWebServer\bin
Websphere <drive letter>:\hyperion\ BPMA Double-click

\AppServer\InstalledApps startBPMAWebServer.bat or
\Websphere\<version> stopBPMAWebServer.bat
\BPMAWebServer\bin
Starting and Stopping BPM Architect Data Synchronizer

Server
The Data Synchronizer server must be started to use data movement capabilities of BPM
Architect. However, it is not needed to log into Workspace.
You can start and stop the BPM Architect Data Synchronizer server from the Services panel, the
Start menu, or by using a command. The location of the command depends on which Java
application server you are using.

➤ To start or stop the BPM Architect Data Synchronizer server:
● From the Services panel, start Hyperion S9 BPMA DataSync ATS5 (for Tomcat); Hyperion
S9 BPMA DatSync WLS<version> (for WebLogic); or HyperionS9 BPMA DataSync
WAS<version> (for WebSphere).
BPMA Data Synchronizer .
command.
Table 8 Location Example for StartBPMAWebServer and StopBPMAWeb Server Commands
If you are using: Go to the following directory (for example) Execute This Command
Tomcat <drive letter>:\Hyperion\ BPMA Double-click

\AppServer\InstalledApps startBPMADataSynchronizer.bat
\Tomcat\5.0.28\BPMADataSync or stopBPMADataSynchronizer.bat
WebLogic <drive letter>:\Hyperion\ BPMA Double-click

\AppServer\InstalledApps startBPMADataSynchronizer.cmd
\WebLogic\<version> or stopBPMADataSynchronizer.cmd
\BPMADataSync
Websphere <drive letter>:\hyperion\ BPMA Double-click

\AppServer\InstalledApps startBPMADataSynchronizer.bat
\Websphere\<version> or stopBPMADataSynchronizer.bat
\BPMADataSync\bin
Administering BPM Architect Servers 19

Managing Dimensions
2
In This Chapter
Importing into the Dimension Library ............................................................................................23
Working with Dimensions .........................................................................................................41
Viewing Transaction Logs..........................................................................................................51
Working with User-Defined Attributes ............................................................................................57
Working with Smart Lists (Planning Only)........................................................................................58
Working with Member Formulas (Planning, Essbase Analytics, and Enterprise Analytics Only) ............................61
The Dimension Library is a central location for Financial Management and Planning
administrators to view, create, and manage dimensions and hierarchies. You can import
metadata to the Dimension Library from interface tables or flat files. After data is imported, you
can drag dimensions into Application Views and remove and delete members.
Caution!
Using the Dimension Library requires that you to have the Dimension Editor security role. This
role allows you access to all functionality in the Dimension Library, such as, creating, deleting,
and changing dimensions and dimension members, creating import profiles, and running
transaction logs. See the Hyperion System 9 Security Guide.
From the Dimension Library, you can edit these properties:

● Application Views
● Dimensions
● Members
Properties are organized into these product categories:
● Essbase Analytics—used for Hyperion® System™ 9 BI+™ Analytic Services™ reporting
cubes only
● Planning—used for Planning application types
● Enterprise Analytics—used for Analytic Services reporting cubes only
● Consolidation—used for Financial Management application types
21
● System—used to identify characteristics of a member, such as name, description, and if the
member is inactive.
● Statistical—used to provide statistical information about a member such as number of
children and number of siblings.
Dimension property categories are defined in product-specific appendices:
● Appendix A, “Working with Financial Management Dimensions”
● Appendix B, “Working with Planning Dimensions”
● Appendix C, “Working with Analytic Services Properties”
● Appendix D, “Working with Statistical and System Properties”
Table 9 Dimension Types
Type Description
Account Specifies chart of account type information, for example, Net Income and Sales, in
applications.
Alias Supplies alternate descriptions and languages for dimension members in Financial
Management applications and to create alias tables for Planning and Analytic Services
applications.
Attribute Classifies members in dimensions in Planning and Analytic Services applications.
Consolidation Method Denotes consolidation behavior for Financial Management applications.
Country Tracks business activities in multiple countries in Analytic Services applications. If you tag
dimensions as Country, you can enter the currency name in the Currency text box.
Note: This dimension type does not apply to aggregate storage outlines.
Currency Specifies currencies in multi-currency applications.
Entity Specifies entity or organizational structures in applications.
Generic Specifies custom dimensions in Financial Management and Planning applications.
ICP Specifies intercompany information, such as ICP Entities, in Financial Management

applications. When you create an ICP dimension, it is automatically populated with read-
only members. The members cannot be edited or changed. This dimension must be included
in an Application View.
Period Specifies the period structure for applications, for example month, quarter, and half year.
Scenario Specifies scenarios for applications, for example Actual and Budget.
Security Class Specifies security class information in Financial Management applications.
Smart List Specifies Smart List information in Planning applications.
Time Specifies how often you collect and update data in Analytic Services applications. You can
tag only one dimension in an Analytic Services outline as Time.
Value Specifies value information, such as Entity Currency adjustments, in Financial Management
applications. When you create a Value dimension, it is automatically populated with read-
22 Managing Dimensions
Type Description
only members. The members cannot be edited or changed. This dimension must be included
in an Application View.
Version Specifies version information, such as, Version 1 and Final Version in Planning applications.
View Specifies the views for the application, such as, year-to-date and quarter-to-date in Financial
Management applications.
Year Specifies the Years used in applications.
Before you create Application Views, you must add dimensions into the Dimension Library.
➤ To access the Dimension Library, select Navigate > Administer > Dimension Library.
Importing into the Dimension Library

There are two ways to import dimension information into the Dimension Library: 1) create and
import a flat file or 2) import from interface tables.
Creating Flat Files

You can import dimensions into the Dimension Library by creating a flat file. In the flat file, a
line starting with an exclamation point ( ! ) indicates the beginning of a new section and must
be followed by a valid section name (for example, Dimensions or DimensionAssociations). A
line starting with an apostrophe ( ' ) sets the column order for the section. True and false values
are represented as Y for true and N for false. You can use a semicolon ( ; ), comma ( , ), pipe
( | ), space, or tab as the file delimiter.
Flat files contain the following sections that can be arranged in any order.
● Dimensions
● Dimension Associations
● Members
● Hierarchies
● Property Array
Dimensions Section
This section contains the list of dimensions to be processed.
Note:
This section is required.
Syntax
Importing into the Dimension Library 23

'Name;DimensionClass;DimensionAlias;CustomDimensionID
Parameter Description
Name A dimension name, for example, Currency. This parameter is required. Valid dimension
names are:
● Account
● Alias
● Attribute
● ConsolidationMethod
● Country
● Currency
● Entity
● Generic
● ICP
● Period
● Scenario
● SecurityClass
● SmartList
● Time
● Value
● Version
● View
● Year
DimensionClass The type of dimension that corresponds to the name. Valid dimension types are the same
as the valid dimension names above.
DimensionAlias An alternate name for the dimension.
CustomDimensionID A custom dimension ID.
Example
!Section=Dimensions
'Name;DimensionClass;DimensionAlias;CustomDimensionID
Currency;Currency;Currency;
Scenario;Scenario;Scenario;
Entity;Entity;Entity;
Account;Account;Account;
Dimension Associations Section

This section contains information about the associations between dimensions, for example
associations between account dimensions and security dimensions.
Note:
If member properties refer to another dimension, this section is required for new dimensions
and for dimensions using the replace method. It is optional for dimensions that use the merge
method.
Syntax
'BaseDimension;Property;TargetDimension
BaseDimension The name of a dimension to associate with another dimension, for example Account.
Property The property (such as security class) to associate with another dimension.
TargetDimension The name of the dimension to which you want to associate the property.
Example
!Section=DimensionAssociations
'BaseDimension;Property;TargetDimension
Currency;SecurityClass;SecurityClass
Scenario;SecurityClass;SecurityClass
Entity;SecurityClass;SecurityClass
Account;SecurityClass;SecurityClass
Members Section
This section contains member names and properties.
Dimension properties are defined in product-specific appendices:
Note:
This section is required for new dimensions and existing dimensions that use the replace method.
It is optional for existing dimensions that use the merge method. If this section is used, the Name
property is required.
Syntax
'Name;Product-specific properties
Name A dimension member name, for example Euro.

Product-specific properties A delimited list of property values. See the product-specific appendixes for
property information.
Example
!Members=Currency
'Name;Scale;TranslationOperator;DisplayInICT
EURO;Whole;;y
GBR;Whole;;
USD;Whole;;
!Members=Scenario
'Name;DefaultParent;DefaultFrequency;DefaultView;ZeroViewForNonAdj;_
ZeroViewForAdjConsolidateYTD;MaximumReviewLevel;UsesLineItems;_
EnableProcessManagement;SecurityClass;EnableDataAudit;_
DefFreqForICTrans
Actual;Y;MTD;Periodic;Periodic;Periodic;N;10;Y;N;;Y;MTD
Budget;Y;MTD;Periodic;Periodic;Periodic;N;10;Y;Y;;Y;MTD
!Members=Entity
'Name;DefaultParent;Currency;AllowAdjs;AllowAdjFromChildren;_
HoldingCompany;SecurityAsPartner;IsICP;SecurityClass
Entity_[None];Y;[None];N;N;;;N;
Regional;Y;USD;Y;N;;;N;CORPORATE
UnitedStates;Y;USD;Y;Y;;;N;US
!Members=Account
'Name;DefaultParent;ConsolidationAccountType;IsCalculated;_
IsConsolidated;PlugAccount;Custom1TopMember;Custom2TopMember;_
Custom3TopMember;Custom4TopMember;NumDecimalPlaces;_
EnableCustom1Aggr;EnableCustom2Aggr;EnableCustom3Aggr;_
EnableCustom4Aggr;XBRLTags;ICPTopMember;IsICP;UsesLineItems;_
SecurityClass;EnableDataAudit;CalcAttribute
Account_[None];Y;Revenue;N;N;;;;;;0;Y;Y;Y;Y;;;N;N;;N;
ExchangeRates;Y;GroupLabel;Y;Y;;;;;;0;Y;Y;Y;Y;;;N;N;;N;
Plug;Y;Revenue;N;Y;;;;;;0;Y;Y;Y;Y;;;N;N;;N;
Hierarchies Section
This section contains the hierarchical/parent-child relationships.
Note:
This section is required for new dimensions and existing dimensions that use the replace method.
It is optional for existing dimensions that use the merge method. If this section is used, the Parent
and Child properties are required.
Example
!Hierarchies=Currency
'Parent;Child
#root;EURO
#root;GBR
#root;USD
!Hierarchies=Scenario
'Parent;Child
#root;Actual
#root;Budget
!Hierarchies=Entity
'Parent;Child
#root;Entity_[None]
#root;Regional
Regional;UnitedStates
UnitedStates;California
California;Sunnyvale
California;FosterCity
UnitedStates;Connecticut
Connecticut;Stamford
!Hierarchies=Account
'Parent;Child
#root;Account_[None]
#root;ExchangeRates
ExchangeRates;Rate1
ExchangeRates;Rate2
#root;Plug
Property Array Section

This section contains the properties for each dimension.
For information on product-specific properties, see Appendix A, “Working with Financial
Management Dimensions”, Appendix B, “Working with Planning Dimensions”, and
Appendix C, “Working with Analytic Services Properties”.
Example
!PropertyArray=Currency
'Property;Name;Key;Value
Alias;EURO;English;European Euro
Alias;EURO;French;
Alias;EURO;German;
Alias;EURO;Italian;
Alias;EURO;Japanese;
Alias;GBR;English;Great Britain Pounds
Alias;GBR;French;
Alias;GBR;German;
Alias;GBR;Italian;
Alias;GBR;Japanese;
Alias;USD;English;United Stated Dollars
Alias;USD;French;
Alias;USD;German;
Alias;USD;Italian;
Alias;USD;Japanese;
!PropertyArray=Scenario
Alias;Actual;English;Actual

Alias;Budget;English;Budget
Alias;Forecast;English;Forecast
Alias;Legal;English;Legal
Alias;Modeling;English;Modeling
Alias;Plan;English;Plan
!PropertyArray=Entity
Alias;Entity_[None];English;
Alias;Entity_[None];French;
Alias;Entity_[None];German;
Alias;Entity_[None];Italian;
Alias;Entity_[None];Japanese;
Alias;Regional;English;Regional Operations
Alias;Regional;French;Operationes Regionale
Alias;Regional;German;
Alias;Regional;Italian;
Alias;Regional;Japanese;
!PropertyArray=Account
Alias;Account_[None];English;
Alias;Account_[None];French;
Alias;Account_[None];German;
Alias;Account_[None];Italian;
Alias;Account_[None];Japanese;
Alias;ExchangeRates;English;
Alias;ExchangeRates;French;
Alias;ExchangeRates;German;
Alias;ExchangeRates;Italian;
Alias;ExchangeRates;Japanese;
Alias;Plug;English;
Alias;Plug;French;
Alias;Plug;German;
Alias;Plug;Italian;
Alias;Plug;Japanese;
Using Interface Tables

Interface tables are database tables used to import data and metadata from external systems into
BPM Architect.
There are two distinct processes for importing metadata from interface tables. The first part of
the process is done outside of BPM Architect and is denoted by a dashed line in the diagram.
The second part of the process is done within BPM Architect. Following is the general process
for importing metadata into the Dimension Library.
1. Move information from an ERP system or general ledger system into an ETL system
2. Move information from the ETL system into BPM Architect interface tables
3. Import interface tables into the Dimension Library
4. Create applications in Financial Management, Planning, and Analytic Services that use the
imported metadata.
You can create multiple BPM Architect interface databases. The BPM Architect database type
can be different than the database for the interface tables. For example, the BPM Architect
database can be SQL Server while the BPM Architect interfaces can use Oracle.
Configuring Interface Datasources

This procedure is required if you want to use interface tables in BPM Architect. Interface tables
is a database interface to import metadata and data from external systems into the Dimension
Library. Before you can import metadata and data from interface tables into the Dimension
Library, you must run the Hyperion® Configuration Utility™ and configure BPM Architect
interface tables by creating datasource links that can be used during the profile creation/data
synchronization.
See Chapter 2, “Managing Dimensions” and Chapter 4, “Synchronizing Data.”
➤ To create interface datasource links:

1 Click Start > Programs > Hyperion System 9 Foundation > Configuration Utility.
2 From the product selection panel, under Hyperion System 9 BPM Architect, select Interface Datasource
Configuration.

3 Enter the Shared Services username and password.
4 Select Create a new datasource link.
5 Select the specific database type (SQL, Oracle or DB2) and click Next.
6 Enter the details for the interface datasource:

a. Enter a name for the datasource. The default, “Datasource,” is displayed but can be
changed.
b. In Host Details, enter the name of the server hosting the database and port number
(defaults display based on database type).
c. In Database Details, enter the database name to use as an interface datasource, the database
username, and password.
d. Select Create Interface Tables.
e. Click Next.
f. Click Yes to confirm deletion of existing tables.
g. Click Next after the “Configuration tasks are complete” message is displayed.
Note:
A success notification is displayed. If the configuration is not successful, check the config
log (Hyperion Home\common\config\logs\configtool.txt), and rerun the configuration
utility to correct the problem.
h. Select No to return to the Product Selection panel.
i. Click Next.
j. Click Finish.
➤ To delete a datasource link:

1 Launch the Hyperion Configuration Utility.
2 Click Next.
3 From the product selection panel, select Hyperion System 9 BPM Architect, then select Interface
Datasource Configuration and click Next.
5 Select Delete a datasource link and click Next.
6 From the drop-down list, select a datasource link to delete.
7 Optionally: select Delete interface tables to delete the tables in the database.
8 Click Next.
9 Click Next once the “Configuration tasks are complete” message is displayed.
10 Select No to return to the Product Selection panel.
11 Click Next.
12 Click Finish when all configuration tasks have been completed.
➤ To edit a datasource link:

1 Launch the Hyperion Configuration Utility.
2 From the product selection panel, select Hyperion System 9 BPM Architect, then select Interface
Datasource Configuration and click Next.
4 Select Edit a datasource link and click Next.
5 From the drop-down list, select a datasource link to edit and click Next.
6 Make changes to the fields displayed (for example, to change a database password). Optionally, select
Create interface tables, click Next and select Yes to confirm deletion of existing tables.
7 Click Next once the “Configuration tasks are complete” message is displayed.
8 Select No to return to the Product Selection panel and click Next.
9 Click Finish.

Defining Interface Tables
Interface tables in BPM Architect are grouped into two categories: system tables and user-defined
tables.
System tables are created when the interface tables are configured. They contain information
used by the import module for profile creation and execution. You must define three system
tables.
Table 10 System Tables
Table Name Description
IM_Load_Info Contains information about a load into the interface tables. Loads are identified by a
load id and can be used later to clear the interface tables.
Columns are:
● Load_ID
● Source_System
● User_Last_Updated
● Date_Last_Updated
● Last_Update_Login
IM_Dimension Contains information about the list of dimensions to be processed, their types, and
references to other sections (tables).
Columns are:
● Load_ID
● Dimension_Name
● Dimension_Class_Name
● Member_Table_Name
● Hierarchy_Table_Name
● Property_Array_Table_Name
● Dim_Property_Table_Name
This table directly corresponds to the !Dimensions section of the flat file.
IM_Dimension_Association Contains information about the associations between dimensions, for example
associations between account dimensions and security dimensions.
Columns are:
● Load_ID
● Base_Dimension
● Property
● Target_Dimension
This table directly corresponds to the !DimensionAssociation section of the flat file.
User-defined tables are used to load dimensions, members, member properties, and member
hierarchies. Each dimension can contain the following set of tables, where Dimension can be any
dimension name such as Entity, CorporateAccounts, or Products.
Table 11 User-defined Tables
Table Name Description Mandatory Property
HS_Dimension_Member Contains member names and properties. This table is Name

required and the Name column is required.
This table directly corresponds to the !Member section
of the flat file.
HS_Dimension_Hierarchy Contains the hierarchical/parent-child relationships. Parent, Child

This table is required and the Parent and Child
columns are required.
This table directly corresponds to the !Hierarchies
section of the flat file.
HS_Dimension_PropertyArray Contains the multiple property values of a member Property, Name, Key, Value
property.
This table directly corresponds to the !PropertyArray
section of the flat file.
HS_Dimension_Property Contains the property values for the dimension. None

This table directly corresponds to the !Property section
of the flat file.
Note:
The Member and Hierarchy tables are required to load a dimension. In the Member table, Name
is required. In the Hierarchy table, Parent and Child are required.
In addition to the dimension interface tables provided in the template script, you can add
interface tables for additional dimensions. For example, the template script contains one set of
tables for the Entity dimension. You can add more Entity dimensions as needed. For each
dimension added to the interface tables, you must also include the dimension in the
IM_Dimension system table so that the dimension is available during profile creation.
Clearing Interface Tables

You have the following options for the interface tables area:
● All
● Load ID
● Older Than—you can select the number of years, months, weeks, and days.
● Date Range
➤ To clear interface tables:

1 In the Dimension Library, select File > Import > Clear Interface Area.

2 Select the data source.
3 Select one of the options for the type of data source load information to clear.
4 Click Clear.
5 Click Yes to confirm.
6 Click OK at the success message.
Creating Import Profiles

Before you can import dimensions into the Dimension Library, you must create an import
profile. Profiles include important information about the dimensions to be imported such as
new dimensions, whether to merge or replace existing dimensions, and dimension properties.
You can import, edit, view, and delete import profiles. See “Managing Import Profiles” on page
40.
➤ To create an import profile:

1 From the Dimension Library, select File > Import > Create Profile.
2 Enter a profile name.
3 From Import Type, select Flat File or Interface Tables.
4 Optional: Enter a description for the profile.
5 Do one of the following:
● If you selected Flat File in Step 3, click Upload, browse to find the file, and click Upload.
● If you selected Interface Table in Step 3, from Data Source, select the database to use for this
profile.
6 Click OK.
Note:
If importing from an interface table, skip to step 11.
7 In the File Properties section, select the column delimiter used in the file.
Note:
You can use a semicolon (;), comma (,), space, or tab as the file delimiter. Semicolon is the default
delimiter.
8 Optional: Select Strip Quotes String to remove single quotes from a string.
9 Optional: Select Trim Spaces to remove spaces in the load file.

10 Click Next.
11 In the Map Dimensions section, use the following methods to specify how to import dimensions from the
flat file or interface table.
● Automatic Mapping—If a dimension in the flat file or interface table exists in the Master
View, the dimension is automatically mapped and you can select to merge the imported
dimension into the Master View dimension or replace the Master View dimension with the
imported dimension.
● Manual Mapping—From Master View, create a new dimension or map the imported
dimension to another dimension. If you map to another dimension, you can merge the
imported dimension into the Master View dimension or replace the Master View dimension
with the imported dimension. If you create a dimension in the Master View, follow these
steps.
a. From Master View, select New Dimension.
b. Enter the dimension name and optional description, select the dimension type, and click
OK.
Note:
When you create new dimensions, the merge and replace options are not applicable.

● Create New Dimension From Source—Select Create Dimensions For the Non-mapped
Dimensions with the Source Dimension Name. For any dimension that is unmapped (that
is, any dimension that is not automatically or manually mapped), the name of the dimension
in the flat file or interface table will be the name used to create the new dimension.
In this graphic, the flat file contains all new dimensions that do not exist in the Master View.
When you select the Create dimension for the non-mapped dimensions option, the Master
View column is automatically populated.
Note:
Because you are creating new dimensions, the merge and replace options are not applicable
for the unmapped dimensions.
12 Click Next.
13 To import dimension properties from the flat file or interface table, select the properties to import in the
Master View column.
Note:
You can double-click on a cell in the Master View column for a drop-down list of available
properties.

14 Optional: Select Ignore Nulls for any property to ignore blank values in the flat file.
15 Click Finish.
16 Import the profile into the Dimension Library.
17 When the import completes, you can view the import results for warnings or errors that occurred during the
import.
Managing Import Profiles

After you create import profiles, you can import dimensions into the Dimension library, view
profile details, edit a profile, and delete profiles.
➤ To import dimensions:
1 From the Dimension Library, select File > Import > Import Dimensions.
2 Select the type of import: Flat File or Interface Tables.
3 Select an import profile to use.
4 Do one of the following
● If you selected Flat File in Step 2, click Upload, browse to find the file, and click Upload.
● If you selected Interface Tables in Step 2, select the datasource and click Upload.
5 Click Import.
➤ To edit import profiles:

1 Select File > Import > Import Dimensions.
3 Do one of the following:
● If you selected Flat File in step 2, click Upload, browse to find the file and click Upload.
● If you selected Interface Tables in step 2, go to step 4.
4 Right-click a profile and select Edit Profile.
Note:
You must upload a flat file to activate the Edit Profile option.
5 Make changes to the import profile as necessary.
Follow the steps in “Creating Import Profiles” on page 34.
➤ To view import profile details:

3 Right-click a profile and select View Details.
4 Click Close.
➤ To delete import profiles:

3 Right-click a profile and select Delete Profile.
4 Click Yes to confirm deletion of the profile.
Working with Dimensions

You can manually create dimensions and edit existing dimensions. There are several ways you
can manually create a new dimension. You can copy an existing dimension. You can create
dimensions in the Dimension Library only.
Note:
Dimension names must follow naming requirements of the product with which you are working.
For Planning dimensions, see “Naming Restrictions for Dimensions, Members, and Aliases” on
page 206, for Financial Management dimensions, see Appendix A, “Working with Financial
Working with Dimensions 41

Management Dimensions”, and for Analytic Services dimensions, see Appendix C, “Working
with Analytic Services Properties.”
Note:
You may be able to enter different characters when creating a dimension in the Dimension
Library, but when the dimension is brought into an application, the application's naming rules
are applied.
➤ To create a dimension:
1 Select File > New > Dimension.
2 Enter a name and optional description for the dimension.
3 Select the dimension type.
Note:
See Table 9, “Dimension Types,” on page 22.
4 Click OK.
The dimension is added to the Dimension Library. You can add members to the dimension by
right-clicking on the dimension and selecting to create, add, or insert members. See “Creating
Members” on page 47.
Setting up Alias Dimensions

Aliases are alternate names, descriptions, languages, or other items that help to define
dimensions. You can assign one or more aliases to Planning accounts, currencies, entities,
scenarios, periods, versions, years, and user-defined dimension members. You can assign aliases
to any Financial Management dimension.
There are three elements to an Alias dimension:
● Alias dimension
● Alias members
● Alias property
You create an Alias dimension and add members to it. Enter a description, alternate name, and
so on, in the Alias property value field for members of associated dimensions. For example, you
create an Alias dimension with members: English, French, Italian. In the Currency dimension
that is associated with this Alias dimension, are the members AUD, JPY, and USD. Double-click
the alias property value for each member and enter a description for English, French, and Italian.
For example, the English descriptions might be Australian Dollar, Japanese Yen, and United
States Dollar.
You can set up how you want members and their aliases to display in the Dimension Library.
You can display just the member name, just the alias, or both. For example, if you have a currency
member named AUD with an alias of Australian Dollar, in the Dimension Library you can display
just AUD, just Australian Dollar, or AUD-Australian Dollar.
Aliases enable you to create unique identifiers for dimensions and members. For example, Cost
Center dimension members may be identified by a number (100, 200, 210, and so on) or by a
descriptive alias (Human Resources, Engineering, Sales, and so on). Members may also have
aliases for different languages.
The name of the Alias dimension must follow naming requirements of the Hyperion product.
For Planning dimensions, see “Naming Restrictions for Dimensions, Members, and Aliases” on
page 206. For Financial Management dimensions, see Appendix A, “Working with Financial
Management Dimensions”.
Note:
You may be able to enter different characters when creating an Alias dimension in the Dimension
Library, but when the Alias dimension is brought into an application, the application's naming
rules are applied.
➤ To set up the Alias dimension:

1 In the Dimension Library, create an Alias dimension and add members to it.
Note:
For Planning, child members of the Alias dimension become Alias Tables when the application
is deployed to Planning. Therefore, you must add a member named Default.
2 Create an association for a main dimension, such as Account or Entity, with the Alias dimension. See
“Creating Dimension Associations” on page 45.
3 Drag the Alias dimension to an Application View. (You also need to drag the main dimensions that have
associations with the Alias dimension if they do not exist in the Application View.)
4 Activate the associations in the Application View. See “Viewing Dimension Associations” on page 78.

5 In the application, select a main dimension member, for example Sales, and double-click in the Alias field
of the property grid.
6 Click and enter alias names in the alias tables for the member.
Note:
An alias name is not displayed in the Alias field in the property grid because multiple aliases can
exist for a member.
Copying Dimensions
When you copy dimensions, all descendants, properties, and property values are inherited by
the new dimension. If you create a dimension with the same name as another dimension in the
library, the dimension shows “Shared”.
➤ To copy dimensions:
1 Right-click a dimension and select Copy Dimension.
2 Change the default dimension name and enter a description.
3 Click OK.
The dimension is added to the Master View.
Creating Dimension Associations

You create dimension associations to assign security classes, currency, and attributes to
dimensions and dimension members. For example, for an entity dimension, you can create
associations to the security class and currency dimensions. You create associations at the
dimension level. The association is inherited by all members under that dimension.
Any dimension that references other dimensions requires associations. Thus dimensions which
reference dimensions such as security class and currency require associations. Because Hyperion
products allow for configuration of the application (which dimensions have security applied),
dimensions that require associations depend on an application's configuration.
Note:
You can also create dimension associations in a flat file. See “Dimension Associations Section”
on page 24. Existing associations are automatically created and activated when you upgrade an
application.
➤ To create dimension associations:

1 Right-click a dimension to which you want to add an association and select Create Association.
2 From Property, select the target dimension.
3 From Dimension, select the base dimension type.
4 Optional: Enter a description for the association.
5 Click OK.
Note:
The associations that you create between dimensions in the Dimension Library must be activated
in the Application View. See “Viewing Dimension Associations” on page 78.

Viewing and Deleting Dimension Associations
➤ To view and delete dimension associations:
1 In the Dimension Library, right-click a dimension and select View Associations.
2 To delete an association, select the association row and click Delete.

4 Click OK.
Deleting Dimensions
When you delete a dimension, the dimension and all members of the dimension are deleted
from the Dimension Library. The dimension and members are also deleted from Application
Views using the dimension. Associations for the dimension are also deleted.
Caution!
Before deleting a dimension, right-click the dimension and select Application Membership, to
view what Application Views are using the dimension. If an Application View contains the
dimension, you cannot delete the dimension.
For important information on deleting Planning dimensions, see “Considerations for Excluding
and Deleting Planning Members” on page 204
➤ To delete dimensions:
1 In the Dimension Library, right-click a dimension and select Delete Dimension.
2 Select Yes to confirm.
Viewing Application Membership

Application membership provides a view of where specific members or dimensions are used in
the Application Views. This helps to determine the impact of dimension changes by showing
where the dimensions and members are currently being used.
➤ To view application membership:

1 In the Dimension Library, right-click a dimension or member and select Application Membership.
2 Click OK.
Creating Members
You can create members as siblings or children of the selected member. You can create members
only in the Dimension Library. If you want to add members to Application Views, you must
first create the members in the Master View and then add them to the Application Views.
Member names must follow product naming requirements. For Planning dimensions, see
“Naming Restrictions for Dimensions, Members, and Aliases” on page 206.
For Financial Management dimensions, see Appendix A, “Working with Financial Management
Dimensions”.
Note:
You may be able to enter different characters when creating members in the Dimension Library,
but when the member is brought into an application, the application's naming rules are applied.
➤ To create members:
1 Right-click a member and select Create Member, then select As Child or As Sibling.

Note:
If you right-click on a top member for a dimension, you do not have the option to create a
sibling.
2 Enter the member name and click OK.
Working with Shared Members

Sharing members allows alternate hierarchical structures within the Dimension Library. Base
members must exist before you can create shared members. You can create multiple shared
members for a member.
The second instance of any member is tagged as a shared member, with “Shared” in parentheses.
In the following example, the entity Washington is a member of the UnitedStates hierarchy and
a member of the Management-Gates hierarchy.
➤ To create shared members:

1 Right-click a member and select Copy.
2 Locate the position in the hierarchy where you want the new member to be, right-click a member and select
Paste > As Child or Paste as Sibling.
Removing Members
You can remove members, including shared members, from the Master View hierarchy. The
members removed become orphan members. When you remove members, the member and all
of its descendents are removed from the hierarchy and are moved to the orphan area as individual
members without a hierarchical structure. When you remove a shared member, only that
member is moved to the orphan area. The same member in other hierarchy structures is not
removed.
➤ To remove members:
1 In the Dimension Library, right-click a member and select Remove.
Note:
You can use the [Ctrl] and [Shift] keys to select multiple members.
Deleting Members
You can remove members, including shared members, from the Master View hierarchy and
reuse them later. Orphan members are created when you remove members from the hierarchy.
When you remove members, the member and all of its descendents are removed from the
hierarchy and are moved to the orphan area as individual members without a hierarchy structure.
When you remove a shared member, only that member is moved to the orphan area. The same
member in other hierarchy structures is not removed.
You can delete members, including shared members, from the Master View hierarchy. When
you delete a member, the member and all of its descendents are deleted from the hierarchy and
from all views. When you delete a shared member, only that member is deleted. The same
member in other hierarchy structures is not deleted.
➤ To delete members:
1 In the Dimension Library, right-click a member and select Delete.
Note:
You can use the [Ctrl] and [Shift] keys to select multiple members to delete.
Finding Members
➤ To find members:
1 In the Dimension Library, right-click a dimension and select Find Members.
2 Enter the member to search for, then click OK.
Note:
Enter alpha-numeric characters only. Special characters are not supported.
3 Double-click a member in the Member Find pane to locate the member in the hierarchy.

The Dimension that contains the member is automatically expanded in the Dimension Library.
4 To refresh the Member Find list, right-click in the Member Find list and select Refresh List.
5 Click to close the Member Find.
Editing Property Values

When a dimension member is created, it takes on a default set of properties and property values.
Properties are organized by category.
For example, the following properties are displayed for Test_Account when the category is set
to Planning:
The following properties are displayed for Test_Account when the category is set to Essbase
Analytics:
Properties and valid property values for the Planning, Consolidation, Analytic Services,
Statistical, and System categories are defined in the following appendices:
● Appendix D, “Working with Statistical and System Properties”
Property values are in the following forms:
● String and Memo—enter text
● Integer—enter a number
● Boolean—select the check box for True, deselect for False
●
Member select—click to select a member
● Drop-down list—select an item from the list
● String Map—used to map an Alias property with an Alias dimension
● Dimension—select a dimension for Smart Lists (Planning only). See “Creating Smart Lists”
on page 59.
➤ To edit property values:

1 Double-click in the Value column of the property to edit.
2 Modify the value for the property.
Note:
When you make a change to a value, the cell changes color.
3 Click .
The property editor displays an icon to the right of each property. The icons indicate the type
of property:
●
Default
●
User-defined
●
Derived
Viewing Transaction Logs

All operations performed in the Dimension Library are recorded in transaction logs. You can
filter the log by date, application, dimension, and property. You can also restrict the log to only
those operations performed in the current session. Each operation is recorded with a time stamp,
the user name, the type of action performed, and other relevant information.
The following actions are recorded in the transaction logs.
Viewing Transaction Logs 51

Action Description
AddApplication Adds an application to a library
AddDimension Adds a dimension to a library
AddDimensionAssociation Adds a dimension association between two dimensions
AddLibrary Adds a library to the system
AddMember Adds the specified member to the specified dimension
AddOrphanMember Adds an orphan member to a dimension
AddView Adds a view object to an application
AddViewFilter Adds a view filter to a view
AddViewTopMember Adds the top member for a specified view
AddViewFilterTopMember Adds a top member to a view filter
AutomatorRun Logged action for an Automator run
ClearApplication Clears an existing application; deletes data artifacts for the application but
does not delete the application record
ClearDimension Clears an existing dimension; deletes data artifacts for the dimension but
does not delete the dimension record
CloseLibrary Logged action for closing a library
CompareRun Logged action for a Compare job
CopyApplication Copies an existing application
CopyDimension Copies an existing dimension
CopyLibrary Copies an existing library
DeleteApplication Deletes an existing application
DeleteBranch Deletes a member and its descendants
DeleteDimension Deletes a dimension from a library
DeleteLibrary Deletes an existing library
DeleteMember Deletes the specified member from the library
DeleteView Deletes a view within an application
ExportRun Logged action for a export job
ImportRun Logged action for a import job
InsertMember Inserts the specified member into the specified dimension
Action Description
MemberPropertyDataLoss Loss action for a member property data loss
MigrateApplication Migrate application view to another server
MoveMember Moves the specified member within the dimension
OpenLibrary Logged action for opening a library
RemoveApplicationArrayPropertyValue Removes (clears) the array value of the specified property of the specified
application
RemoveApplicationPropertyValue Removes (clears) the value of the specified property of the specified
application
RemoveDescendantValues Remove property value for a member’s descendants
RemoveDimensionArrayPropertyValue Removes (clears) the array value of the specified property of the specified
dimension. The property itself is not deleted because other dimensions may
be using it.
RemoveDimensionAssociation Removes a dimension association between two dimensions
RemoveDimensionPropertyValue Removes (clears) the value of the specified property of the specified
dimension. The property itself is not deleted because other dimensions may
be using it.
RemoveDuplicates Removes (clears) duplicate properties for the specified member
RemoveLibraryPropertyValue Removes (clears) the value of the specified property of the specified library.
The property itself is not deleted because other libraries may be using it.
RemoveMember Removes the specified member from the dimension
RemoveMemberArrayPropertyValue Removes (clears) the array value of the specified property of the specified
member. The property itself is not deleted because other members may be
using it.
RemoveMemberPropertyValue Removes (clears) the value of the specified property of the specified
member. The property itself is not deleted because other members may be
using it.
RemoveViewFilter Removes a view filter from an existing application
RemoveViewFilterTopMember Remove the top member from the view filter
TransactionExportRun Logged action for a transaction query
UpdateApplicationArrayPropertyValue Updates the array value of the specified property of the specified application
UpdateApplicationPropertyValue Updates the value of the specified property of the specified application
UpdateDimensionArrayPropertyValue Updates the array value of the specified property of the specified dimension
UpdateDimensionPropertyValue Updates the value of the specified property of the specified dimension
UpdateLibraryPropertyValue Updates the value of the specified property of the specified library

Action Description
UpdateMemberArrayPropertyValue Updates the array value of the specified property of the specified member
UpdateMemberPropertyValue Updates the value of the specified property of the specified member
➤ To view a transaction log:

1 From the Dimension Library, select View > Download Transaction Logs.
2 Select an application view.
Note:
You must at least select an application by which to filter the transaction log.
3 Optional: Select a dimension.
Note:
Only dimensions for the selected application are displayed in the drop-down list and you can
only select one dimension.
4 Optional: Click to select one or more members to include in the log and click OK.
5 Optional: Click to select one or more properties to include in the log and click OK.
6 Optional: Use the date drop-down lists to select a date range.
7 Optional: Select Filter to current session.
8 Click OK.
9 After the job is submitted, click the link in the message box to go to the exported transaction log.
10 In the Attachments section of the job console, click Transaction Export.

11 Select to open or save the transaction log.
Note:
Transaction logs use the .CSV file extension and can be opened in Microsoft Excel.
The transaction log consists of multiple columns of information for the criteria that you selected.
Column Name Description
TransactionID The transaction ID associated with one or more transaction actions.
DetailID The order in which actions are processed within a transaction.
Action The operation that is logged.
ApplicationID The generated ID associated with the application artifact.
ApplicationName The name of an application.
ClassID A classification of the artifact being added
CreatedDateTime The timestamp of the action.
Column Name Description
Description Description of the action.
DimensionID The generated ID of the dimension artifact.
DimensionName The name of the dimension on which the action is performed.
FromOrigin For property updates, the origin of the property value before an update occurs.
FromValue For property updates, the value of the property before an update occurs.
Level A designation given to a transaction action: Core, Logged, Loss, Result, Admin.
MemberDescription If the action is related to a member, the name of the member is logged in this column.
MemberID The generated ID of a member.
MemberName The name of the member on which the action is performed.
NewMemberOrder The order in which the member is inserted under a parent.
NewParentID The ID of a parent under which a member is inserted.
OriginalMemberOrder The original position of a child order for a parent member.
OriginalParentID The ID of the original parent prior to a move member operation.
OriginalDetailID For actions that initiate other actions, this is the detail ID of the initiating action.
OriginatingID For actions that initiate other actions, this is the ID of the initiating action.
PropertyID The generated ID of the property definition.
PropertyName The name of the property definition.
ToOrigin The origin of the property value.
ToValue The new value for a property value.
UserName The username that performed the action
LibraryName The Library name on which the action is performed.
Working with User-Defined Attributes

You can use user-defined attributes (UDAs)—words or phrases describing a characteristic of
members—within calc scripts, member formulas, and reports so that they return lists of
members associated with the specified UDA. For example, if you have a Product dimension with
various product members, you could create a UDA called New Products and base certain
calculations only on new products. For information on creating and using UDAs, see the
Hyperion System 9 BI+ Analytic Services Database Administrator’s Guide and Online Help.
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.
Working with User-Defined Attributes 57

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 in the Dimension Library Property Grid.
➤ To select UDAs for members:

1 Select the dimension for whose members to associate the UDA.
2 Select a member in the dimension to edit.
3 In the Property Grid, double-click UDA.
4 Type the name. Use a comma to separate multiple UDAs for a member.
5 To change a UDA, double-click the UDA and retype the name.
6 To delete a UDA, double-click the UDA and delete the entry. If you delete UDAs, you must update all member
formulas, calc scripts, and reports that reference them.
Working with Smart Lists (Planning Only)

Smart Lists are custom drop-down lists that users access from data form cells in Planning
applications. When clicking into data form cells, users select items from drop-down lists instead
of entering data. Users cannot type in cells that contain Smart Lists. Smart Lists display in cells
as down arrows that expand when users click into the cells.
For example, you can create a drop-down Smart List called Justification that provides selections
for Research, Customer Feedback, and Expansion. When users click into an Account named
Reason (which is associated with the Justification Smart List), they click the down arrow, which
expands into a drop-down list with these selections: Research, Customer Feedback, and
Expansion. Users select a Smart List option as a value for the cell.
Administrators use the Dimension Library to create Smart List dimensions and members, and
assign properties. Perform these tasks to create and administer Smart Lists:
● Create a new dimension with Smart List selected as the Dimension Type.
● Create members in the dimension. (The members are the items that display in the drop-
down, data form, or grid.)
● Assign properties to the Smart List dimension and members.
● Optionally:
❍ Enable Smart Lists for data forms. See the Hyperion System 9 Planning Administrator's
Guide.
❍ Use Smart List values in member formulas and business rules.
❍ Set how #missing cells associated with Smart Lists display in data forms.
Creating Smart Lists
➤ To create Smart Lists:
1 In the Dimension Library, select File > New > Dimension.
The Add New Dimension dialog box is displayed.
2 Type the Name, Description, and select the type, SmartList.
Note:
Enter a unique name containing alphanumeric and underscore characters (for example:
Position) and no special characters or spaces. Smart List names can be referenced in formula
expressions (see “Working with Formula Expressions” on page 62).
The Smart List dimension is displayed in the Master View.

Data cells can display only one Smart List. If multiple Smart Lists intersect at cells, set which one
takes precedence by setting the data type evaluation order. See “Setting Data Type Evaluation
Order” on page 75.
Next, create the members that will display as items in the drop-down list.
3 In the Master View, right-click the Smart List dimension and select Create Member > As Child.
The New Member dialog box is displayed.
4 Type the member name and click OK.
5 Create additional members, as necessary, for the dimension.
Modifying Smart List Dimension Properties

Use the Property Grid to set Smart List properties.
➤ To set Smart List properties:

1 Select a Smart List dimension.
2 Select the category, Planning. Define the Smart List properties for the dimension:
Table 12 Smart List Dimension Properties
Property Description
Label Enter the text to display when the Smart List is selected. Spaces and special characters are allowed. Smart
List labels can reference a resource, which can be translated into different languages. See the Hyperion
System 9 Planning Administrator's Guide.
Start Value Populates the “Value” property of the first member in the Smart List. For example, if the Smart List dimension
is ‘Justification’ with “Start Value” set to 10, the first member added to this list will have a value of 10.
Working with Smart Lists (Planning Only) 59

Increment This value is appended to the value of the last member in the list to determine the value for the selected
member. For example:
Justification (Start Value=0, Increment=10)
Research (Value=0)
Customer Feedback (Value=10)
Survey (Value=20)
Display Order How Smart Lists are sorted in the drop-down list: by Name, ID, or Label
● Name—Unique alphanumeric name containing alphanumeric and underscore characters (for example:
Customer_Feedback) and no special characters or spaces
● ID—Unique number that sets the order for the displayed entry.
● Label—Displayed text for the Smart List entry on the drop-down list (for example: Customer Feedback).
#Missing Data Form Label Determines how #missing vales are represented in cells associated with Smart Lists. Options:
● DropDown—Displays the label set in #Missing Drop-Down Label.
● Data Form—Displays #missing or leaves cells blank, depending on the Display Missing Values As Blank
selection for the data form (see the Hyperion System 9 Planning Administrator's Guide).
This selection determines what is displayed in the cell when it is not the focus. When the cell is in focus,
the Smart List item that is selected from the drop-down is displayed. See “Displaying #Missing with Smart
Lists” on page 60.
● Grid—Displays #missing or leaves cells blank, depending on the Display Missing Values As Blank
selection for the grid (see the Hyperion System 9 Planning Administrator's Guide).
This selection determines what is displayed in the cell when it is not the focus. When the cell is in focus,
the Smart List item that is selected from the drop-down is displayed. See “Displaying #Missing with Smart
Lists” on page 60.
#Missing Drop Down Label Enter a label (for example, “No Justification”) to be displayed as an entry in the Smart List whose value is
#missing. Notes:
● It displays as the first selection in the Smart List drop-down, allowing #missing as a selection in the data
form.
● When the cell is not in focus, this label displays only if the drop-down is selected. Otherwise, #missing
or a blank cell is displayed, depending on the Display Missing Values As Blank selection for the data
form.
● #missing labels determine only the display of cells with #missing data; #missing remains the stored
value. See “Displaying #Missing with Smart Lists” on page 60.
Displaying #Missing with Smart Lists

Administrators set the values that are displayed in Smart Lists and data cells, including what is
displayed when there is no data in the cell. When there is no data in a cell, the cell can display
no value (that is, the cell is blank), #missing, or—for cells associated with Smart Lists— another
value that you specify.
Use these options to control the display of #missing in such cells when they are not in focus:
Blank When designing the data form, select Display Missing Values as Blank.
When setting Smart List properties, select Data Form Setting.
#missing When designing the data form, do not select Display Missing Values as
Blank.
When setting Smart List properties, select Data Form Setting.
A custom label, such as “No Change” When setting Smart List properties, enter the custom label in the #Missing
Drop-Down Label field (for example, No Change). Select Drop-Down
Setting.
Associating Smart Lists to Members

After you create Smart List dimensions and modify the properties, you can associate smart lists
with members.
Note:
You must associate the Smart List with the dimension before you can add it as a property of the
dimension member.
➤ To associate smart lists:

1 Select a member in the Master View.
2 In the Property Grid, double-click Smart List.
3 Click .
The Categories dialog box displays all available Smart List dimensions.
4 Select the Smart List and click OK.
Note:
To no longer associate a smart list with a member, double-click the Smart List property and
delete the Smart List name.
Working with Member Formulas (Planning, Essbase Analytics,

and Enterprise Analytics Only)
You can define member formulas in the Property Grid for Planning, Enterprise Analytics, and
Essbase Analytics categories. Member formulas can combine operators, calculation functions,
dimension and member names, and numeric constants to perform calculations on members.
Member formulas can also include:
Working with Member Formulas (Planning, Essbase Analytics, and Enterprise Analytics Only) 61
● Operator type, function, value, member name, UDA, and so on that are allowed in Analytic
Services formulas (see the Hyperion System 9 BI+ Analytic Services Database Administrator’s
Guide and Online Help)
● Predefined formula expressions—including Smart List values—that expand into a formula
or value upon database refresh
➤ To define member formulas:

1 Select the dimension member to add or change a formula.
Note:
The Member Formula property displays in the following categories: Planning, Enterprise
Analytics, and Essbase Analytics.
2 In the Property Grid, double-click Member Formula.
3 Click .
The Memo Editor dialog box is displayed.
See the Hyperion System 9 BI+ Analytic Services Database Administrator’s Guide for syntax, rules,
and usage on Analytic Services formulas.
4 To wrap the formula text, click Word Wrap.
5 Click OK.
Validating Formulas
You can only validate member formulas after you deploy an Application View.
➤ To validate member formulas:

1 Double-click the member formula to validate.
2 Click .
The Memo Editor dialog box is displayed.
3 Click Validate.
4 If necessary, edit the formula. When finished, click OK.
Working with Formula Expressions

Member formulas support Analytic Services native formulas and formula expressions that are
evaluated and expanded into Analytic Services code blocks when the database is refreshed. In
these expressions, you can address Smart Lists by name, which are replaced with their numerical
values in calculations.
You can include predefined formula expressions in member formulas, and test them after you
deploy an Application View using the Validate button in the Memo Editor. You can also load
them using Hyperion® Application Link™ or Shared Services.
You can update the dimension outline without updating all the business rules and calc scripts
that depend on the outline. Calculations become more independent of specifics in the outline.
Performance is not decreased when you use formula expressions because they are run only when
you refresh the database.
➤ To use a formula expression in a member formula:

1 Select the dimension member to add or change a formula.
2 Double-click Member Formula, then click .

3 In the Memo Editor dialog box, define formulas for the member.
You can include formula expressions and Analytic Services native formulas in the member
formula. See the Hyperion System 9 BI+ Analytic Services Database Administrator’s Guide for
syntax, rules, and usage on Analytic Services native formulas.
Planning provides predefined formula expressions that you can use in member formulas. You
cannot edit or create your own formula expressions. See “Formula Expressions” on page 63.
4 Click OK.
Prerequisites
Before using formula expressions in member formulas, you should understand Analytic Services
formulas and calculation and the application outline. See the Hyperion System 9 BI+ Analytic
Services Database Administrator’s Guide.
Formula Expressions
Formula expressions can include these predefined variables and functions.
Table 13 Variables in Formula Expressions
Variable Description
OpenInputValueBlock Generates an IF statement if the application is a multi-currency application, or an empty

string if it is one currency application. Used with ClosedInputValueBlock.
CloseInputValueBlock Generates an End IF statement if the application is a multi-currency application, or an

empty string if it is one currency application. Used with OpenInputValueBlock.
NumberOfPeriodsInYear Returns the number of time periods in the year
NumberOfYears Returns the number of years in the application
Table 14 Functions in Formula Expressions
Function Description
Dimension(dimTag) Returns the name of a predefined dimension. The dimtags

are:
● DIM_NAME_PERIOD
● DIM_NAME_YEAR]
● DIM_NAME_ACCOUNT
● DIM_NAME_ENTITY
● DIM_NAME_SCENARIO
● DIM_NAME_VERSION
● DIM_NAME_CURRENCY
Period(periodName) Returns the specified period. The periodName options are:

● FIRST_QTR_PERIOD
● SECOND_QTR_PERIOD
● THIRD_QTR_PERIOD
● FOURTH_QTR_PERIOD
● FIRST_PERIOD
● LAST_PERIOD
CrossRef(accountName) Generates a cross reference for the account
CrossRef(accountName, prefix) Generates a cross-reference for the account. The account

name contains a prefix that you define. The default prefix is
No, followed by a blank space and the account name, for
example, No Salary.
getCalendarTPIndex() Generates a member formula that returns an index for the time
period; the index is based on the calendar year.
getFiscalTPIndex() Generates a member formula that returns an index for the time
period; the index is based on the fiscal year.
CYTD(memberName) Generates a calendar year-to-date formula for the member
CYTD(memberName, calTpIndexName, Generates a calendar year-to-date formula for the member,

fiscalTpIndexName) and the time period index based on the calendar year and
fiscal year. Use when members are renamed. The default
member names are “Cal TP-Index” and “Fiscal TP-Index”
Syntax
Formula expressions support functions and variables. Follow these syntax rules for functions
and variables when you create formula expressions:
● Enclose variables or properties with square brackets, [ ]. If you omit square brackets, the
variable is treated as a native variable.
● Enclose member names with quotation marks (for example, “Account 200”).
● Characters in variables are case-insensitive, but cannot have extra spaces or characters such
as the underscore ( _ ).
● You can include subcalls to other functions within an expression.
● Do not enter text where a number is required.
● The order of the outline is important in a member formula. For example, do not reference
a value that has not been calculated yet.
Including Smart List Values as Variables

You can include a Smart List as a variable in a formula expression, such as the formula expression,
“Status”= [Status.Departed]
“Status” is the member name, Status is the Smart List dimension name, and Departed is a Smart
List member name. If the Smart List value for Departed is 2, Analytic Services replaces
Status.Departed with 2 in the member formula (Planning treats Smart Lists as text and Analytic
Services treats Smart Lists as numbers). If the Smart List value for Departed is 2, Analytic Services
replaces Status.Departed with 2 in the calculation and stores 2 in the database.
Write Smart Lists in this format: [SmartListDimensionName.SmartListMemberName]
Understanding Common Errors

Follow the rules of syntax carefully. If formula expression syntax contains errors, error messages
are returned when you deploy an Application View. To get information about error messages,
view your Planning Application Server log. The most common error message is “Failed to
execute.” This occurs when you use parameters in the expression incorrectly. These actions cause
“Failed to execute” error messages:
● Entering the wrong number of parameters in the formula expression
● Misspelling member names, functions, or variable names
● Not surrounding member names with quotation marks
● Including numbers where strings are required
See the Hyperion System 9 Planning Administrator's Guide.
Managing Application Views
3
In This Chapter
About Application Views...........................................................................................................67
Workflow for Creating Application Views .........................................................................................67
Prerequisites........................................................................................................................68
Creating Application Views ........................................................................................................68
Working with the Application Library .............................................................................................86
Validating and Deploying Application Views.....................................................................................99
Redeploying Application Views ................................................................................................. 105
About Application Views

The Application Library enables you to view, create, validate, and deploy BPM Architect
Application Views to Hyperion financial applications. An Application View contains dimensions
and dimension attributes that are designed to meet financial management and planning needs.
Each Application View contains accounts, entities, scenarios, and other dimension elements.
As the application creator, you can create unlimited numbers of Application Views. For example,
you can create Application Views for the following purposes:
● by cost center, to budget operating expenses
● by product line, to plan revenues
● to report on tax data
● to report on Security and Exchange Commission data
Application Views differ from deployed applications:
● Deployed applications reside on a Financial Management or Planning product server.
● Deployed applications contain business rules, reports, forms, and grids; Application Views
contain only dimensions and dimension properties.
Workflow for Creating Application Views

You define Application Views in six steps:
1. Create an Application View, and select a type:
● Consolidation
About Application Views 67

● Planning
● Enterprise Analytics
● Essbase Analytics
● Generic (Template)
2. Drag dimensions (or dimension hierarchy subsets) to the Application View.
3. Modify dimension properties (only if you want Application View properties, other than the
properties listed in the Dimension Library).
4. Activate all dimension associations.
5. Validate the Application View.
6. Deploy the Application View to the Hyperion product environment.
7. Define access permissions. (See the Hyperion System 9 Security Guide, Hyperion System 9
Financial Management Administrator's Guide, Analytic Services Database Administrator’s
Guide, or Hyperion System 9 Planning Administrator's Guide.)
Prerequisites
To create Application Views, you must have the Application Creator global role for your
Hyperion product (Financial Management, Planning, Enterprise Analytics, or Essbase
Analytics). For information on creating or assigning global roles, see the Hyperion System 9
Security Guide.
Before you create Application Views, complete the following tasks:
● Install and configure Shared Services.
● Configure the product in which you plan to deploy Application Views. (Configuration
includes creating the product instance and the data source.)
● In BPM Architect, create a profile and load dimensions in the Master View of the Dimension
Library. See Chapter 2, “Managing Dimensions.”
Creating Application Views

The Application Library displays all Application Views. You can create Application Views in the
Application Library or Dimension Library. To create Application Views, you must have the
Application Creator global role for your specific Hyperion product, such as Financial
Management.
➤ To open the Application Library, select Navigate > Administer > Application Library.
➤ To create Application Views:

1 Select File > New > Application View.
2 Enter a name and select a type.
68 Managing Application Views

For Planning, Enterprise Analytics, and Essbase Analytics Application Views, the name must
contain no more than 8 characters.
For Consolidation and Generic Application Views, the name must contain no more than 10
characters, no spaces, and cannot begin with HFM, HSV, HSX, or a number.
There are five types:
● Generic—A template that enables you to create an Application View without assigning a
product. (A generic Application View displays properties for all products.)
● Consolidation—Financial Management Application View.
● Planning
● Enterprise Analytics
● Essbase Analytics
3 Enter a description and click OK.
Descriptions cannot contain “&” (ampersands) and more than 40 characters.
The Dimension Library is displayed.
When you create Application Views, the Dimension Library has three panes:
● Master View—Displays on the left and displays all dimensions currently available in the
Dimension Library.
For information on loading dimensions into the Dimension Library, see “Importing into
the Dimension Library” on page 23.
Creating Application Views 69

● Application View—Appears in the middle and when expanded, lists the names of all
dimensions in the current Application View.
● Property Grid—Displays on the right and displays the properties of the selected dimension
or member.
For information on editing properties, see “Editing Property Values” on page 50.
At the bottom of the window, you can select the tabs to move between the Application Library
and Dimension Library.
Note:
To hide the Workspace View Pane, click the Hide button in the middle of the vertical pane
divider.
Adding Dimensions
After you create an Application View, you can add dimensions.
For information on filtering dimensions for Application Views, see “Filtering Application
➤ To add dimensions to Application Views, drag the dimensions from the Master View to the
Application View.
Tip:
In the Master View, to display members of a dimension, expand the dimension. Then, to add
only a few members, drag the members you want to the Application View.
The expanded Application View lists all dimensions and members.

You can modify Application View properties. Depending on the Application View type,
requirements and properties vary. See “Modifying Planning Application Views ” on page 71
and “Modifying Consolidation Application Views” on page 76.
Tip:
If you add a member to the Master View and include the dimension in the Application View,
you can click and the new member will display in the Application View.
Modifying Planning Application Views

When you create Planning Application Views, you set base time periods (monthly, quarterly, or
custom). You can use weekly distribution to determine how values are spread for monthly
periods.
➤ To display properties for Planning Application Views, in the Dimension Library, select the name
of the Planning Application View (highest level in the Application View pane).
The properties for all dimensions in the Application View are displayed in the Property Grid.
Properties set at the highest level apply to all listed dimensions.
For information on Planning properties, see Appendix B, “Working with Planning Dimensions.”

Defining Base Time Periods and Monthly Distribution Spread
You can select a base time period and a monthly distribution pattern, based on the number of
fiscal weeks in a month. Base time periods are the bottom-level time periods in an Application
View. Predefined options are quarters or months. You can create a custom base time period,
such as weeks or days.
You use monthly distribution patterns to determine how data entered into a summary time
period is distributed (spread) among the base time periods. During data entry, users can enter
data into summary time periods, such as years or quarters. Planning distributes the entered
values over the base time periods that constitute the summary time period.
If you select a weekly distribution pattern other than Even Distribution, Planning treats quarterly
values as if they were divided into 13 weeks and distributes weeks according to the pattern that
you selected. For example, if you select the 5-4-4 pattern, Planning treats the first month of a
quarter as if it has five weeks and the last two months of the quarter as if they have four weeks.
The options for the weekly distribution pattern are available only if you select the base time
period option “12 Months.”
➤ To define base time periods and weekly distribution patterns:

1 For the Base Time Period property, select 12 Months, Quarters, or Custom.
2 In Weeks Distribution, select a weekly distribution pattern. (Options include: Even, 445, 454, and 544.)
Defining Calendar Ranges

For Application Views, you can specify the fiscal start year and start month. When specifying
the fiscal start year, consider how much historical data your organization needs and wants in
the Application View. You can add years to the calendar, but you cannot change the fiscal start
year.
➤ To define the calendar range:

1 Double-click Start Year and enter the year.
2 Double-click Start Month and select the month.
Specifying the Default Currency

You can specify the default currency for the entities of an Application View and establish whether
the Application View supports currency conversions. Multiple currency support (also known
as currency overrides) is available for level 0 members, regardless of their base currency.
➤ To specify currencies:
1 If you support multiple currencies, select Multiple Currencies.

Note:
If you support multiple currencies, two dimensions are created in the deployed Application
View: Currency and HSP_Rates. The multiple currency setting cannot be changed later.
2 Select the Default Currency.
Configuring Plan Types

In an Application View, you must configure at least one plan type. An Analytic Services database
is created for each plan type. Use the Property Grid to include up to five plan types in the
Application View. An Analytic Services database is created for each plan type. You cannot change
the name or number of plan types after creating an Application View.
As you create accounts, entities, and other elements of the application, you associate them with
plan types, so the database for each plan type contains only application dimensions, members,
and data values relevant to the plan type. This optimizes application design, size, and
performance.
Note:
You can have up to five plan types for a Planning application—three for Planning Application
Views, and the extra two pertain to Hyperion® System™ 9 Capital Expense Planning™ and
Hyperion® System™ 9 Workforce Planning™ plan types. Capital Expense Planning and
Workforce Planning are separately licensed modules. See the Hyperion System 9 Workforce
Planning Administrator's Guide and Hyperion System 9 Capital Expense Planning Administrator’s
Guide.
The number of plan types depends on the needs of your organization. For example, if the sales
department has a yearly revenue plan, and the finance department has a P&L plan, you can define
two plan types, Revenue and P&L.
Data can be shared between plan types. For example, the Revenue plan may include several sales
detail accounts that rollup into a Total Product Sales account. You can configure the P&L plan
to include the Total Product Sales account. This configuration enables you to bring the data
value for Total Product Sales into the P&L plan, without account details. Thus, the database for
your P&L plan is smaller and more efficient.
➤ To configure plan types:

1 Double-click Plan Type 1.
2 Enter the name of the plan type.
Plan type names can have up to eight characters. You can enter more than eight bytes, including
single-byte and double-byte characters, but an error message is displayed when you create the
Analytic Services database, stating that the name is too long. If Analytic Services is installed on
a UNIX server, the plan type name cannot contain underscore characters.
3 Repeat steps 1 and 2 for additional plan types.

Optimizing Performance
Use these methods to optimize Application View performance:
● Assign dimensions as dense or sparse. See “Modifying Performance Settings” on page
74.
● Change dimension order. See “Modifying Performance Settings” on page 74.
● Allocate memory for the supporting detail cache. See the Hyperion System 9 Planning
Modifying Performance Settings

You can accelerate data retrieval and minimize memory and disk space requirements by
assigning dimensions to one of two types: dense or sparse.
If a dimension lacks data values for the majority of member combinations, define it as sparse.
If a dimension has data values for the majority of member combinations, define it as dense.
Often, dense dimensions are Period and Account. Usually, Period is highly populated with data,
whereas Account is dense due to intensive calculations.
Analytic Services requires that at least one dimension be set to dense. Custom attributes cannot
be assigned to dense dimensions. See the Hyperion System 9 Planning Administrator's Guide.
➤ To improve performance for Planning Application Views:

1 In the Dimension Library Application View, right-click the Application View and select Performance
Settings.
The Plan Type Performance Settings dialog box is displayed.
2 Select plan type.

Dimensions belonging to the plan type are displayed with the number of dimensions for the
plan type. Applications can have up to five plan types.

If applications are created with a single currency, the HSP_Rates dimension is not displayed.
3 Double-click a cell in the Density column and select:
● Sparse—Lack data values for the majority of member combinations. A sparse dimension is
a dimension with a low percentage of available data positions filled.
● Dense—A dimension with a high probability that one or more data points is occupied in
every combination of dimensions.
Caution!
Deployment of an Application View fails if you do not assign at least one dimension in a cube
to be dense.
You can speed calculation time by changing the order for calculating dimensions. The order of
dimensions is critical in the structure and performance of Analytic Services databases. Dense
dimensions calculate faster than sparse dimensions, so dimensions should be in order of most
to least dense. Aggregating dimensions aggregate children into the parent to create new data;
non-aggregating dimensions do not create new data by the hierarchies (for example, a Scenario
or Version dimension).
Separate sparse dimensions into aggregating and non-aggregating dimensions, with aggregating
dimensions before non-aggregating dimensions.
Optimize performance by ordering dimensions according to these guidelines:
● Make Period and Account dense.
● Order dense dimensions from the most to least dense. The most dense is usually Period,
followed by Account.
● Separate sparse dimensions into aggregating and non-aggregating dimensions. Place
aggregating dimensions before non-aggregating dimensions. Order sparse dimensions from
most to least dense.
4 Select a dimension:
● Click to move the dimension up in the list.
● Click to move the dimension down in the list.
Setting Data Type Evaluation Order

Data types are a property that are defined for all dimension members. Data types can have
conflicting results on the face of a data form depending upon the cell intersections defined for
the data form. For example, the intersection of a "percent" data type and a "currency" data type
need to be resolved based upon a defined order set by a Power User. The Data Type Evaluation
Order is the defined order. You will set a dimension order by plan type to determine the
precedence when multiple data types intersect. Data types associated with the first dimension
in the list take precedence over data types associated with subsequent dimensions.

➤ To modify the evaluation order:
1 In the Dimension Library Application View, right-click the Application View and select Data Type Evaluation
Order.
The Evaluation Order dialog box is displayed.
Note:
If you want to allow users to enter dates or text into data form cells having Date and Text data
types in Planning Application Views, select those members' dimensions and move them to
Selected Dimensions.
2 Select a Plan Type.
Applications can have up to five plan types.
3 Select a dimension and perform one action:
● Click to move the dimension up in the list.
● Click to move the dimension down in the list.

4 Click OK.
Modifying Consolidation Application Views

A Consolidation Application View must contain the following dimension instances:
● 1 Scenario
● 1 Year
● 1 View
● 1 Period

● 1 Entity
● 1 Value
● 1 Account
● 1 ICP
● 4 Generic (Each one has to be mapped to a different custom dimension 1 through 4)
● 1 Security Class (Optional)
● 1 Alias (Optional)
The alias dimension should contain no more than 10 members.
● 1 Currency
● 1 Consolidation Method
Note:
All the dimension associations must be created and activated in the Application View.
Modifying Enterprise Analytics and Essbase Analytics

Application Views
The following are guidelines to keep in mind when modifying Enterprise Analytics and Essbase
Analytics Application views:
● Analytic Services applications do not require a fixed set of dimensions. For example, you
can create and deploy an Analytic Services Application View containing just one generic
dimension and one member.
● When adding an alias member, you must create a dimension of “Alias” type to associate
with this member. See “Creating Dimension Associations” on page 45 for information on
creating dimension associations.
The alias dimension can contain up to 10 members. At a minimum, a member named
“Default” is required in this dimension.
● When adding an attribute member, you associate the member to a base dimension. See
“Creating Dimension Associations” on page 45 for information on creating dimension
associations.
● BPM Architect only supports the attribute type, “Text.”
● You cannot use BPM Architect to create Hybrid Analysis or Advanced Relational Access
cubes.
Properties for Analytic Services applications, dimensions and members are described in
Appendix C, “Working with Analytic Services Properties.”
Information on Analytic Services requirements for applications and databases is available in the
Analytic Services Database Administrator's Guide and the Analytic Administration Services Online
Help.

Removing Dimensions
➤ To remove a dimension from an Application View, right-click the dimension, and select Remove
Dimension.
Viewing Dimension Associations

Dimension associations enable you to assign security classes and currency to dimensions and
dimension members. For example, for an entity dimension, you can create associations to the
security classes and currency dimensions. Associations are created at the dimension level and
associations are inherited by all members under the dimension. Dimension associations are
created in the Dimension Library. See “Creating Dimension Associations” on page 45.
Dimension associations are used to denote the interrelationships between the dimensions within
the Master View and Application Views. For example, within Consolidation applications there
are Account dimension properties that reference security class, custom dimension intersections
(Custom1TopMember), and so on, which directly relate to other dimensions. Dimension
Associations enable you to define the relationships between these properties and the other
dimensions which then enables you to pick the value directly from the referenced dimension.
A dimension association is created for all properties where the property value refers to a member
of another dimension. Once you create the association, you need to activate it in the Application
View.
Note:
If you have a multi-currency Application View, the Currency dimension must be associated with
the base Entity dimension. If you activate all dimension associations, it will automatically activate
the association for you.
➤ To activate all dimension associations, right-click the Application View (at the highest level) and
select Activate all associations.
➤ To view and activate one or more dimension associations:

1 In the Application View, right-click a dimension, and select Dimension Associations.
The Edit Dimension Association dialog box is displayed.

An example of associating dimensions for Planning Application Views, is the Start Period and
End Period properties of the Scenario dimension would have a dimension association with the
Period dimension. The Start Year and End Year property of the Scenario dimension would have
a dimension association with the Year dimension.
Note:
Dimension associations are not automatic, so you must use the Edit Dimension Association
dialog box to activate associations.
2 Perform and repeat one or both actions, as needed.
● To activate a dimension, in Master Associations, select the dimension, then click .
● To deactivate a dimension, in Active Associations, select the dimension, then click .

You can click Add All or Remove All to activate or deactivate all dimensions. When you activate
all dimensions, BPM Architect automatically associates all base and associated dimensions.
3 Click OK.
Viewing Application Membership

Application membership provides a view of where specific members or dimensions are used in
the list of available Application Views. This information helps you understand the impact of
changes. For example, a division is being reorganized, and you are planning to update the Entity
dimension. You use the Application Membership feature to determine which Application Views
may be impacted and to determine the scope of the change.

➤ To view application membership:
1 In Master View, right-click a dimension or member and select Application Membership.
The Applications List dialog box lists all applications of which the dimension is a member and
a description of each application.
2 Click OK.
Working with Members

As you create new dimensions or Application Views, you can search for specific members and
filter members.
Finding Members
Some dimensions include numerous members and you may need to search for specific members
to add them to an Application View. You can use the Dimension Library to drag members that
you find into the Application View.
➤ To find members and add them to Application Views:

1 In the Master View or Application View, right-click a dimension, and select Find Members.
The Member Find dialog box is displayed.
2 Enter the member name and click OK.
Note:
Enter alpha-numeric characters only. Special characters are not supported.
The Member Find view replaces the Property Grid on the right. If matches are found, they display
in the Member Find view. If no matches are found, the Member Find view is empty.

3 Double-click a member in the Member Find pane.
The Dimension that contains the member is automatically expanded in the Master View and/
or Application View.
4 To add a member to the Application View, drag the member from the Member Find pane to the Application
View.
5 Optional: To refresh the Member Find list, right-click in the Member Find list and select Refresh List.
6 Click to close the Member Find and display the Application View.
Note:
To display the Property Grid, select View > Show Property Grid.
Filtering Application Members

You can narrow the results by using a subset of a dimension. For example, you may want to filter
by a specific member, such as a product or region. When you filter by a certain member, the
results in the Application View are narrowed to this member. This is extremely helpful if you
have dimensions containing numerous members and you only need to show data for a few
members.
➤ To filter members in a dimension:

1 In the Application View, right-click a dimension and select Filter Members.

The Member Selector dialog box is displayed.
The member selector enables you to filter members within a dimension. Expand and collapse
members within a dimension using the [+] and [-].
The Member Selector dialog box has two panes—all members in the dimension on the left and
selections in the Application View on the right. The left pane, showing all members available in
the dimension, displays the member name and a short description, if available. The right pane,
showing selections for the Application View, displays the member name and the selection type.
In new Application Views, all members display in the selections pane by default.
You can use the Menu button above each pane to change the columns in the Member Selector.
a. In the left pane, click > Show > Count.

The Count column displays in addition to Name and Description. The count column
displays the number of child members under the current dimension. This can be a helpful
indicator of how long it might take to expand down a branch of the tree.
b. To remove the Count column, click , and select Show > Count.
c. To collapse a dimension, click , and select Collapse All.
Note:
When you select Collapse All, all members under the dimension or member that you
selected are collapsed. When a dimension or member is collapsed, rest the mouse pointer
over the artifact to display a ToolTip indicating the number of descendants.

You can also search for members, see “Searching for Members in the Member Selector”
on page 84.
d. In the Selections pane, click , Show, and modify the columns.
2 In the list of available dimensions and members on the left, select a member to filter by and click .
3 To deselect a member from the list of members to filter by, click .

You can also right-click to obtain additional options for the filter. For example, you may want
to filter on all siblings of a member.
4 Right-click a member in the list of members available in the dimension. Choose an option:
● Member
● Children
● Descendents
● Siblings
● Parent
● Ancestors
● Level 0 (Base)
● Inclusive
The member is moved to the right and displays the option you selected in the Selection Type
column. For example, “Descendants” displays in the Selection Type column.

Tip:
You can right-click a member in the list of selections to change the designation. For example,
you can change “Children” to “Descendents.”
5 Continue to add members to the filter. (Members that the Application View will be filtered by appear on the
right.)
Tip:
To deselect all members from the list of selections, click .

6 In the Selections pane, you can select a member and click and to move a member up or down.
7 When finished, click OK.
Searching for Members in the Member Selector
➤ To search for members:

1 In the Member Selector, select Search.
2 Select Name or Description.
3 Enter the phrase for which to search, and click .

You can use wildcards in your phrase. For example, if you are searching a customer dimension
and type Ba** in the text box, and click Search, only customer names that start with Ba display.
You can also type ! in the text box to act as a wildcard. For example, you might not know how
to spell a customer name, such as Privado, Inc., since it could be Privado, Pravado, or Provado.
In this case, you could type Pr!v to find this customer.

4 Click to move members displaying in the search results to the Application View Selections.
Excluding Members
➤ To exclude a member, in the Application View, right-click the member to exclude and select
Exclude Member.
Note:
If you have a Planning and Financial Management product installation, and create a Planning
Application View, you may need to exclude unnecessary Financial Management system
members. You should select all the Financial Management system members, displayed with
square brackets, such as [None] and [Active], and exclude them. For example, in the Accounts
dimension, when creating a Planning Application View, you would exclude all items under
Account except Liabilities and Intangible Assets.
Showing Excluded Members
➤ To show excluded members:

1 In the Application View, right-click the dimension and select Show Excluded Members.
The Exclusions dialog box is displayed.

2 To show the excluded members in the Application View, select the member and select Show. Otherwise, click
Cancel.
The excluded member is displayed in the Application View.
Setting the Base Member

Setting the base member enables you to exclude any of the children under the parent. For
example, in the Entity rollup, Europe has the children of Italy and United Kingdom, if you make
Europe the base for this rollup, then Italy and United Kingdom are no longer visible.
Note:
The Set Base Member feature is not related to shared members.
➤ To set the base member, in the Application View, right-click the member, select Set Base
Member.
Working with the Application Library

➤ To open the Application Library, select Navigate > Administer > Application Library.
Navigating the Application Library

The Application Library shows all of your Application Views. You can select an Application View
in the top pane and view summary information in the lower pane. The lower pane displays:
● Summary—Name, type, date created, date last deployed, and the associated data
synchronizations
● Description—The information you provided in the Comments field of the Application View
dialog box

● Dimensions—The dimensions available in the Application View
● Properties—The status, default currency, and specific properties set for the Application
View
● Synchronizations—The data synchronizations for this Application View
Modifying the Application Library View
➤ To modify the Application Library view:

1 Choose View > Details.
2 Perform one or more actions:

● To sort by a column, click the column heading. For example, if you want to sort by name,
click Name.
● To move a column, drag the column heading to a new location.
● To change the view to icon view, select View > Icons.
Working with the Application Library 87

Creating Application View Filters
You can create filters that allow you to see only specific Application Views in the Application
Library.
Note:
The Application Library does not filter the Application Views based on security. All applications
are shown. For example, a user will see 20 Application Views in the Application Library even if
he only has access to one of them.
➤ To create Application View filters:

1 Select View > Filter.
2 Deselect the types that you do not want to see.

3 Under Status, deselect the status that you do not want see. For example, you might want to see Application
Views that are not deployed.
4 Click OK.
Refreshing the Application Library

To ensure the most current display of application information, you can refresh the Application
Library.
➤ To refresh the Application Library, select View > Refresh.
Editing Application Views

➤ To edit Application Views:
1 In the Application Library, double-click an Application View or right-click and select Edit.
2 Right-click the Application View and select Edit.
The Dimension Library displays the Master View, Application View, and Property Grid.

Opening Application Views
After you deploy an Application View, you can open it in the Hyperion application in which it
was deployed.
➤ To open Application Views, in the Application Library, right-click a deployed Application View
and select Open.
Tip:
You can also click Navigate > Applications, then choose the Application type, such as Planning,
and select the Application View.
The Application View displays in Financial Management or Planning.
Note:
The Open option in the right-click menu is not available if the Application View has not been
deployed.
Closing Application Views

➤ To close Application Views, in the upper right corner of the view, click .
Deleting Application Views

In the Application Library, you can delete Application Views with undeployed or deployed
status. If the status is Deployment Pending, you cannot delete the Application View.
➤ To delete Application Views in the Application Library, right-click an Application View and
select Delete.
An authorization check for the deletion is performed, then a request is passed to the Hyperion
product server for a completion status. The Application View status is updated to “Marked for
Deletion” so that no other operation can access it. After an Application View is deleted, it is
removed from the Application Library.
Duplicating Application Views

Within the Application Library, you can copy Application Views. If you modify artifacts in the
Master View the changes are automatically reflected in all Application Views.

Note:
If you select a different Application View type, such as Consolidation to Planning, only the like
dimension properties are copied. After you duplicate the Application View, you should update
the new Application View type properties.
➤ To duplicate Application Views:

1 In the Application Library, right-click an Application View and select Duplicate.
The Duplicate Application View dialog box is displayed.
2 Enter the name, description (optional), and select the type. Then click OK.
It may be necessary to refresh the Application Library to see the new Application View created
by duplicating the existing Application View.
3 Select View > Refresh or click .

4 As necessary, double-click the Application View and use the Dimension Library to modify the properties.
Migrating Application Views

You can migrate Application Views from one server to another. Consolidation Application
Views can be copied across types of databases. For example, a Consolidation Application View
created using a SQL Server database can be copied to an Oracle database. Planning Application
Views cannot be copied across types of databases. For example, a Planning Application View
created using a SQL Server database must be copied to another SQL Server database.
Follow these guidelines:
● The source and destination computers must be registered to the same Shared Services server.
● Application Views cannot be migrated from one BPM Architect server to another BPM
Architect server.
● For Planning, the destination instance and data source must exist before the migration is
attempted.
➤ To migrate Application Views:

1 Right-click an Application View, and select Migrate.

Note:
The Copy Data and Copy Audit Data options are available for Consolidation applications only.
If you are migrating a Planning application, these options are not available.
2 Enter the name of the new application.
3 Optionally enter comments.
4 Select the instance name, application server, and Shared Services project.
5 Select Copy Data and/or Copy Audit Data.
The Copy Data and Copy Audit Data options are available for Consolidation applications only.
You can select Copy Data to copy the data along with the metadata/application structure
information. Select Copy Audit Data to copy the data and task audit information that has been
generated with the application up to the point of migration.
6 Click OK.
7 For Planning Application Views Only: After you complete the migration in BPM Architect, you must restart
the Planning server of the target application.
Note:
To view the status of a migration, select Navigate > Administer > Job Console.
After you migrate an Application View, it is automatically registered in Shared Services.

For information on assigning user roles, see “Managing and Provisioning Users and Groups” in
the Hyperion System 9 Security Guide.

Reregistering Application Views
Reregistering is for Shared Services only and is used in the case where Shared Services goes down
and the applications need to be reregistered.
➤ To reregister Application Views:

1 Right-click the Application View and select Reregister.
2 Select the options for your Application View, then click Reregister.
Note:
The Reregister dialog box displays different options, depending on the type of Application View.
Comparing Application Views

Compare is an integral part of the Application View flow. The Compare report shows all excluded
members and property differences.
You can compare Application Views in these ways:
● Compare to Master Library—Compares the dimensions and members in an Application
View to the dimensions and members in the Master View in the Dimension Library.
● Compare to Deployed Application—Compares an Application View to a deployed
Application View.

● Compare to Application Snapshot—Compares an Application View to the same Application
View as of a specific date and time.
➤ To compare application views:

1 Right-click an Application View, select Compare, then perform an action:
● Compare to Master Library
● Compare to Deployed Application
● Compare to Application Snapshot
If you selected Compare to Application Snapshot, the Date/Time Selection dialog box is
displayed. Select the date and time, then click Done to display the Hyperion System 9 Workspace
— Compare dialog box.
If you selected Compare to Master Library or Deployed Application, the Compare dialog box is
displayed.
2 Click View Results.
The Dimension Compare Results is displayed.

Navigating the Compare Results
The Compare View has three panes:
● “Dimension Compare Results” on page 94
● “Compare Summary” on page 96
● “Property Compare Results” on page 97
Dimension Compare Results

Dimension Compare Results, on the left, displays dimensions and members that have been
added or deleted. Initially, the Compare Results displays the Application View collapsed, with
the total number of differences in parentheses. When you expand the Application View, each
dimension displays the number of differences in parentheses when it is collapsed, and upon
expansion, artifacts that have been removed from the Application View display with a strike
through. Artifacts with property differences display in bold.

When you select artifacts the value updates in the Compare Summary and Property Compare
Results. (Depending on your selection, the Compare Summary heading displays: Application
Compare Summary, Dimension Compare Summary, or Member Compare Summary. For
example, if you select:
● Application View—the Application Compare Summary displays the total number of
differences, additions, removes, and property differences for the entire Application View.
● Dimension—the Total Differences, Additions, Removes, and Property Differences in the
Dimension Compare Summary update to reflect the values of the selected dimension.
● Removed member (with strike through)—the Member Compare Summary Total
Differences and Removes update to reflect the values of the selected member.
● Member with property differences (in bold)—the Member Compare Summary updates and
the Property Compare Results displays the Property Name that differs in the Application
Views being compared.
➤ To change the dimension compare results view:
1 Click to display a side-by-side tree.

The Dimension Compare Results displays the compared views side by side.

Note:
If you are comparing an Application View to the Deployed Application or Snapshot, the
Dimension Compare Results displays the Application View, Status, and Application View
(Snapshot).
2 Click to display a single tree (default view).
Compare Summary
Compare Summary, in the upper right, displays a summary of all changes between the
Application View and Master View or Snapshot in the Dimension Library. The Compare
Summary updates, depending on your selection. For example, if you select a dimension in the
Dimension Compare Results, the Compare Summary heading displays Dimension Compare
Summary. The Compare Summary values are based on the selected artifact in the Dimension
Compare Results. It displays:
● Total Differences—total number of differences between the Application View and Master
View or Snapshot.
● Additions—total number of artifacts added to the Application View.
● Removes—total number of removed artifacts.

● Property Differences—total number of property differences
Each summary displays a radio button. The radio buttons are filters. You can select the Additions,
Removes, or Property Differences radio buttons to display the number in parentheses and update
the Dimension Compare Results. If you select Additions the display is updated to show only
additions and all of the summary numbers are updated as well. In addition, any members without
additions are not displayed, unless it has a child that needs to be shown.
Property Compare Results

Property Compare Results, in the lower right, displays changed member properties for the
selected member in the Dimension Compare Results. The Property Compare Results displays
three columns: Property Name, Application View name, and Master View or Snapshot.
Excluding Members in the Compare Results
➤ To exclude members:
1 Right-click a member in the Dimension Compare Results and select Add to Exclude Filter.
The number of 'Removes' is updated in the Application Compare Summary.
2 When finished, click in the upper right corner of the view.
Viewing the Data Flow

You can access the data flow from the Application Library. The Data Flow shows how data is
moved between Application Views using synchronizations created with the Data Synchronizer.
Data Flow takes data synchronizations and graphically depicts the relationships of data
movement between Application Views.
Note:
To view the data flow, you must have applications that are synchronized. See Chapter 4,
“Synchronizing Data.”
➤ To view the data flow, in the Application Library, right-click an Application View and select
Data Flow.
The data flow is displayed. The data flow map shows data flowing in and out of a focal application.
The focal application is the Application View in the center of the data flow.

When you select an Application View in the data flow, properties are displayed in the lower pane.
The Application Properties include, Name, Description, and Synchronizations.
Changing the Focal Application in the Data Flow
➤ To change the focal application, right-click the Application View, and select Center.
The focal application changes according to the Application View you selected.
Viewing Synchronizations
➤ To view a synchronization, right-click the Application View, select Synchronizations and select
the synchronization name.
You can select a synchronization to edit, validate, or execute. See “Editing Synchronizations”
on page 98 and “Validating and Executing Synchronizations” on page 99.
Editing Synchronizations
➤ To edit a synchronization:
1 Perform a task:

● In the Data Flow, double-click the synchronization in the Application Properties area. In
the Synchronization Execution dialog box, select the synchronization, select the Action,
Edit and click OK.
● Access the Data Synchronizer (Navigate > Administer > Data Synchronization), right-click
the synchronization and select Edit.
2 Modify the data mappings as necessary.
See Chapter 4, “Synchronizing Data.”
Validating and Executing Synchronizations

You can execute synchronizations from the Data Flow.
➤ To validate and execute synchronizations:

1 In the Data Flow, select an Application View.
2 In the Application Properties, double-click the synchronization to execute.
The Synchronization Execution dialog box is displayed.
3 Select the Action, Validate or Execute, and click OK.
Editing Application Views

You can edit Application Views that display in the Data Flow.
➤ To edit an Application View, in the Data Flow, right-click the Application View and select
Edit.
Validating and Deploying Application Views

In BPM Architect, you create Application Views which describe the dimensionality and other
information about an application. When you create Application Views, you can then validate
and deploy the Application Views to Hyperion products. The deployment process automatically
creates an application in the desired Hyperion product, such as Financial Management or
Planning.
The deployment process involves:
Validating and Deploying Application Views 99

● Deployment and Validation—Validate and deploy an Application View to a Hyperion
product, such as Financial Management or Planning.
If the Application View is missing dimensions or other required information, the
deployment is aborted. Also, if another deployment for the Application View is in progress,
the request is cancelled. For information on viewing deployments, see Chapter 5, “Managing
Jobs.”
● Product-Specific Properties and Registration—The deploy operation retrieves product-
specific properties from the instance registration in Shared Services (via Hyperion® System™
9 Master Data Management™). The registration information also contains a deployment
URL to call for initiating deployment to the Hyperion product.
BPM Architect retrieves the metadata XML in Common Schema format from Hyperion
MDM and sends a deploy or redeploy request to the Product Web Server with the XML.
● Product Application Creation—The status of the Application View updates to “Deployment
Pending” in the Application Library. If this is a new deployment, the Hyperion product
creates the application and the Hyperion product server attempts to load the metadata. After
deployment is complete, the status and deployment timestamp is updated in the Application
Library.
Note:
If you selected a specific product type when creating the Application View, the Application View
is deployed to that product type. If you selected “Generic” for the Application View type, you
must specify the product type when you deploy.
Validating Application Views

➤ To validate an Application View:
1 Right-click the Application View and select Validate.
If there are no validation errors, the Validation Summary dialog box is displayed, indicating that
the Application view validated successfully. If there are errors in the Application View, the dialog
box indicates the number of errors.
2 If errors exist, click Details to review the errors.
3 When finished, click OK.
Considerations for Deploying Planning Application Views

Before deploying Planning Application Views, be sure all the properties are correct and meet
your needs. If you need to update any settings, do so before deploying. If Application Views are
not set up correctly, deployment fails and error messages are displayed. To deploy correctly,
Planning Application Views must meet the qualifications specified in this chapter, Chapter 2,
“Managing Dimensions,” and Appendix B, “Working with Planning Dimensions.” For example:
● The Start Year property must be defined. The year must be four digits long, such as 2006.

● The Start Year dimension and First Year property must describe the same year, using
different formats. For example, if the Start Year is 2006, the First Year property must be
FY06.
● Year dimensions must start with FY, followed by a two-digit year, such as FY06.
● The Start Month property must be defined.
● The Default Alias Table property must be defined. For information, see “Setting up Alias
Dimensions” on page 42.
● The Default Currency property must be defined.
● The Application View must include the predefined dimensions. Single-currency Application
Views require Scenario, Version, Entity, Account, Period, and Year. Multiple-currency
Application Views require Scenario, Version, Entity, Account, Period, Year, and Currency.
● The Application View must meet the qualifications specified in Appendix B, “Working with
Planning Dimensions.”
Caution!
Each data value in Planning is identified by a set of dimension members and a plan type.
Excluding dimension members from an Application View can translate to a delete action on
deployment. If excluded members are used elsewhere (such as a selection in a data form), those
associations are removed. For information, see “Considerations for Excluding and Deleting
Planning Members” on page 204.
Before excluding members from an Application View, use the Show Usage feature within
Planning to determine where members are used in the application and the implications of
exclusion of dimension members from an application during deployment. For information
about the Show Usage feature, see the Hyperion System 9 Planning Administrator's Guide.
Some information cannot be changed after the Application View is deployed. For properties
that cannot be changed after deploying, see “Considerations for Redeploying Planning
Application Views” on page 107.
Deploying Planning Application Views

Planning requires certain dimensions, depending on how the Application View is set up. For
example, Accounts, Entity, Scenario, Version, Period, Year (and Currency and HSP_RATES for
multi-currency applications). To avoid validation errors, ensure that the Application View
includes all required dimensions. For Planning dimension requirements, see Appendix B,
“Working with Planning Dimensions.”
The deploy process creates:
● Tables and values in your relational database.
● Creates an application and outline in Analytic Services without the need to refresh the cube
from the Planning Web user interface.

● HSP_Rates, for multi-currency applications, is created upon deployment (it is not a
dimension that you create manually)
Note:
Make sure to start the Planning Application Server before you deploy any Planning Application
Views.
➤ To deploy Planning Application Views:

1 Click Navigate > Administer > Application Library.
2 Right-click the Planning Application View and click Deploy.
When you deploy an Application View, the Application View is automatically validated before
it's deployed. If there are validation errors, the Application Validation Errors dialog box is
displayed. Hyperion recommends that you fix all validation errors before you deploy the
application.
When the application is deployed, any unreferenced UDAs are removed from the application.
See “Working with User-Defined Attributes” on page 57.
The Deploy dialog box is displayed.
3 Perform these tasks:

a. Select the Instance Name.
b. Select the Application Server.

c. Select the Shared Services Project.
d. Select the Data Source that the Application View uses.
e. If you are deploying the Application for the first time, click Create Outline.
f. Optional: Create Security Filters—stores access permissions in an encrypted data file
(Essbase.sec). To generate security filters for all users in the application, select Create
Security Filters but do not select Validate Security Filter Limit.
g. Optional: Shared Members Security Filters—applies access permissions to shared members.
h. Optional: Validate Security Filter Limit—identifies security filters that exceed the Analytic
Services security filter limit of 64 KB per row. This validates filter size to ensure it does not
exceed the size limit before building Analytic Services security filters.
4 Click Deploy.
Note:
When you deploy a single currency application, the Entity member Currency property will be
set to the application default property.
The Planning Application View is automatically registered with Shared Services and deployed
to Planning. To view progress and error messages, open the Planning Application Server.
Note:
To log in to the Planning application created after deployment, use your user name and
password. The default logon information is admin/password. See the Hyperion System 9 Planning
Note:
If a deployment is interrupted or deleted, the status may show “deploy pending” and the
deployment may time out. The default time out is 8 hours. You can change the default in
awbconfig.properties. If a deployment times out you should deploy the Application View
again, even though the status may indicate that it is in sync with deployment, it may not be
because of the time out.
Deploying Consolidation Application Views

See the Hyperion System 9 Financial Management Administrator's Guide for information on
clearing data from removed dimension members.
➤ To deploy Consolidation Application Views:

2 Right-click the Consolidation Application View, select Deploy.

3 If the Application Validation Errors dialog box is displayed, click Deploy again.

a. Select the Instance Name.
b. Select the Application Server.
c. Select the Shared Services Project.
d. Optional: Check Clear All Metadata and Data—all dimension members in the application
database are deleted as well as any corresponding data, journals, and intercompany
transactions.
e. Optional: Check Referential Integrity—checks the metadata against the data to ensure
integrity. See the Hyperion System 9 Financial Management Administrator's Guide.
5 Click Deploy.
Note:
Deploying Enterprise Analytics and Essbase Analytics

Application Views
Some guidelines to consider when deploying Analytic Services applications:

● You must be provisioned in Shared Services with the user role of Analytic Services
Application Creator (in the User Management Console, Hyperion Shared Services > Global
Roles > Application Creator > Analytic Services Application Creator). Refer to the Shared
Services documentation for more information on provisioning.
● Analytic Services applications do not require a fixed set of dimensions. For example, you
can create and deploy an Analytic Services Application View containing just one generic
dimension and one member.
● You cannot use BPM Architect to create Hybrid Analysis or Advanced Relational Access
cubes.
● A common validation error is that an invalid character exists in a member name. This often
occurs when member names contain square brackets ( [ ] ). To work around this, you can:
❍ Ignore the validation messages regarding the square bracket as an invalid character.
❍ In the Application View, clear the members containing square brackets using the
Exclude Member command, described in “Excluding Members” on page 85.
Note:
There is no difference in the deployment process for Enterprise Analytics or Essbase Analytics
applications.
Properties for Analytic Services applications, dimensions and members are described in
Appendix C, “Working with Analytic Services Properties.”
Information on Analytic Services requirements for applications and databases is available in the
Analytic Services Database Administrator's Guide and the Analytic Administration Services Online
Help.
➤ To deploy an Enterprise Analytics or Essbase Analytics Application View:

2 Right-click the Enterprise Analytics or Essbase Analytics Application View, select Deploy.
3 If the Application Validation Errors dialog box is displayed, click Deploy again.
Note:
In the Application Validation Errors dialog box, you may also click View Errors to bring up the
Validation Summary dialog box. Click Details to review the errors, and then edit the Application
View to make the necessary corrections. Once you make the corrections, begin the deployment
process again.

a. Select the Instance Name of the Analytic Server instance to which you want to deploy an
application.
b. Optional: Select Clear All Data if you are redeploying (deploying over a previously-
deployed application) and want to clear the data in the existing application.
5 Click Deploy.
Note:
Redeploying Application Views

Redeploying performs a merge or a replace of the application metadata based on the types of
changes made since the last deployment. For example, if any members have been moved or
deleted in any hierarchies in the Application View, then the redeployment of the metadata is
performed using a replace mode. If only property updates were made to the Application View
since the last deployment, then the redeployment of the metadata will be performed using a
merge mode.
➤ To redeploy Application Views, right-click the Application View and select Deploy.
See “Deploying Planning Application Views” on page 101.

Considerations for Redeploying Planning Application Views
Before redeploying, be sure the properties are correct and meet your needs. If Application Views
are not set up correctly, deployment fails and error messages are displayed. After a Planning
Application View is deployed, you cannot change these properties:
● Whether the Application View uses a single currency or multiple currencies. For example,
after you deploy with Multiple Currency selected, you cannot later clear Multiple Currency
to use a single currency. Likewise, with a single-currency Application View, you cannot later
select Multiple Currency.
● The default application currency. Data values might not be correct because existing currency
values are not converted to the new currency.
● The type of calendar. For example, if you set Base Time Period to 12 Months, you cannot
later change it to Quarters.
● The fiscal start month. After you set the Start Month, you cannot change it.
● The start year. For example, if you set the Start Year to 2006, you cannot change it to 2005.
You can, however, add years after the first year.
● Any years added. After years are added, you cannot remove them. For example, if the
deployed Application View includes FY06, you cannot remove this year.
● The Weeks Distribution pattern. For example, if you set Weeks Distribution to 445, you
cannot later change it to 544 or Even.
● The existing plan type, such as Valid For Plan1. You can add plan types, but you cannot
remove existing ones. For example, if you deployed an Application View with the properties
Valid For Plan1 and Valid For Plan2, you can later add Valid For Plan3. However, you cannot
later remove Valid for Plan2.
● Dimensions added. You can add dimensions up to a total of twenty, including the predefined
dimensions. You can rename dimensions, but you cannot delete them.
● Predefined dimensions. You cannot delete the predefined dimensions. Single-currency
Application Views require these dimensions: Scenario, Version, Entity, Account, Period,
and Year. Multiple-currency Application Views require these dimensions: Scenario,
Version, Entity, Account, Period, Year, and Currency.
Caution!
deployment. For information, see “Considerations for Excluding and Deleting Planning
Before excluding members from an Application View or deploying to Planning, use the Show
Usage feature within Planning to determine where members are used in the application and the
implications of excluding dimension members from the application on deployment. For
information about the Show Usage feature, see the Hyperion System 9 Planning Administrator's
Guide.
Redeploying Application Views 107

Redeploying Planning Application Views
➤ To redeploy Planning Application Views:
1 Right-click a Planning Application View and select Deploy.
2 Select the Shared Services Project.
The Shared Services Project is only available after an Application View is registered in Shared
Services. Application Views are automatically registered upon deployment in BPM Architect,
or if you register the Application View using Shared Services.
3 Select Refresh Outline and select additional security options, as necessary. See “Deploying Planning
4 Click OK.
The Application View is deployed to Planning. To view progress and error messages, open the
Planning Application Server.
Note:
When you redeploy a single currency application, the Entity member Currency property will be
set to the application default property.

Synchronizing Data
4
In This Chapter
Understanding Data Synchronization .......................................................................................... 109
Synchronizing Data .............................................................................................................. 109
Mapping Dimensions ............................................................................................................ 117
Working with Mappings.......................................................................................................... 122
Working with the Data Synchronizer............................................................................................ 127
Understanding Data Synchronization

Data synchronization enables you to synchronize and map data between Hyperion applications,
interface tables, and external files.
Tasks enabled by the Data Synchronization module:
● Create and modify synchronizations
● Select source and destination applications or files (external sources for source only)
● Define mappings between sources and destinations
● Validate synchronizations
● Execute synchronizations
● View logs of synchronization activities
The Data Synchronization module enables you to create synchronizations between Financial
Management, Planning, Enterprise Analytics, and Essbase Analytics as destinations, and the
following sources:
● Financial Management
● Planning
● Enterprise Analytics / Essbase Analytics
● External source (flat file)
● Interface table
Synchronizing Data
BPM Architect enables you to synchronize data in three locations:
Understanding Data Synchronization 109

● Application Library (“Synchronizing Application Views in the Application Library” on page
110)
● Data Flow (“Viewing the Data Flow” on page 97)
● Data Synchronizer (“Synchronizing Application Views in the Data Synchronizer” on page
110)
Using Hyperion Application Views as Sources

You can synchronize Application Views in the Application Library or Data Synchronizer.
Synchronizing Application Views in the Application Library

You can synchronize Application Views in the Application Library if two Application Views are
selected and your user name is assigned the Create Integrations access role. See the Hyperion
System 9 Security Guide.
➤ To synchronize data in the Application Library:

1 Select the source application.
2 Press [Ctrl] and select the destination application.
3 Right-click and select Synchronize.
Note:
If you are synchronizing a Planning application, you are prompted to select the plan type.
The dimension mapping is displayed. See “Mapping Dimensions” on page 117.
Synchronizing Application Views in the Data Synchronizer
➤ To synchronize data in the Data Synchronizer:

1 Select Navigate > Administer > Data Synchronization.
2 Select File > New > Synchronization.
The New Synchronization wizard is displayed.
3 Select Hyperion Application, and click Next.
4 Select the source application, and click Next.
5 Perform an action:
● If you synchronize two Financial Management applications, click Finish and omit steps 6–
8.
● If you synchronize a Planning source or destination application, click Next.
110 Synchronizing Data

The Select Plan Types dialog box is displayed.
Data can be shared between plan types. For example, the Revenue plan may include sales
detail accounts that rollup into a Total Product Sales account. You can set up the P & L plan
to include the Total Product Sales account, and omit the sales detail accounts. Thus, you
can bring the data value for Total Product Sales into your P & L plan, without the account
detail and make the database for your P & L plan smaller and more efficient.
6 Select a plan type and click Finish.
The Dimension Mapping is displayed.
Synchronizing Data 111

7 Click .
The Save Data Synchronization dialog box is displayed.
8 Enter a Name and Description and click OK.
After you save the synchronization, you can map dimensions. See “Mapping Dimensions” on
page 117.
Synchronizing Multiple Currency Planning Application Views

You can synchronize multiple currency Planning Application Views.
For example, you may want to link a Financial Management Value (source) to HSP_Rates
(destination). For every row that Financial Management generates, two rows are returned to
Planning.
In this instance, the Financial Management row
Account,Entity,Period,Scenario,Year,Value"NetProfit","UnitedStates.Massachu
setts","January","Actual","2006","USD",10.0
is transformed into

Account,Entity,Period,Scenario,Year,Currency,
HSP_Rates"NetProfit","UnitedStates.Massachusetts","January","Actual","2006"
,”Local”,"HSP_InputValue",10.
0"NetProfit","UnitedStates.Massachusetts","January","Actual","2006",”Local”
,"HSP_InputCurrency",USD
The reverse scenario works similarly. If you synchronize from Planning to Consolidation
Application Views and you map HSP_Rates to Consolidation Value, the two rows are merged
into one row (reverse of the example). Otherwise, the rows are unchanged, and every row from
the source is sent to the destination (after metadata and data translation).
Note:
The generation of the new rows or merging of the original rows occurs immediately, before data
is sent to the destination. All metadata and data transformations occur before the auto-
generation or merging of the rows.
➤ To synchronize multi-currency Application Views, right-click the HSP_Rates dimension and

select Generate Currency Members.
If you synchronize an Application View with a multi-currency Planning Application View and
the HSP_Rates dimension is linked, the HSP_Rates dimension the right-click menu displays
“Generate Currency Members.”
Note:
Synchronizing multi-currency application views is available for one-to-one mappings and not
available if HSP_Rates is linked to multiple dimensions.
When mapping Financial Management to Planning, it is expected that the Value dimension in
Financial Management be mapped to HSP_Rates in Planning and a Default member “Local”
should be assigned to the Currency dimension.
Using Hyperion Data Interface Tables as Sources

Interface tables enable you to bring information into the Hyperion schema through database
operations (SQL loads or leveraging Hyperion data integration products). After information is
stored in interface tables, the standard mapping and load mechanisms provided within data
synchronization can be used to bring the information into the respective Hyperion product.
Interface tables are useful in situations where you do not want to pre-format text files for flat
file loads and want the power and flexibility of a relational database for staging information into
the Hyperion product suite.
Defining Interface Areas

Before you create synchronizations, by using an interface area as the source, you must create an
interface area.

➤ To create interface areas:
1 Select File > New > Data Interface Area Definition.
2 Select the interface table source, database table that contains the data to import, and the column that
contains the data values for each row, and click Next.
3 Define the dimension by selecting a column on the left and entering the dimension name on the right.
For example, Col1 is displayed on the left, and Scenario is the dimension name on the right.
Tip:
Click to remove a column.

4 Click Next.
5 Enter the interface table name and description and Finish.
Creating Synchronizations
After you create an interface area, you can create a synchronization that uses an interface table
as the source.
Note:
You must define the interface table before creating a synchronization using an interface table as
the source. See “Defining Interface Areas” on page 113.
➤ To create synchronizations:
1 From the Data Synchronizer, select File > New > Synchronization.
2 Select Hyperion Data Interface Area.

3 Click Next.
4 Select a source—interface area, database table to import, and the column that contains the data for each
row—then click Next.
5 Define the dimensions—select the column and enter the dimension name—then, click Next.
6 Enter the name of the interface area and optionally enter a description, then click Finish.
External Files as Sources

You can define external files to use as sources in data synchronizations. Data Synchronization
supports a delimited file with data in the last column, and does not support fixed length fields.
You must enter all mapping rules and filters pertaining to the flat file source.
Before you create a synchronization that uses an external file as the source, you must define the
external file.
Defining External Files
➤ To define external files:

1 Select File > New > External File Definition.
The External File Mapping Wizard is displayed.
2 Perform all actions:
● Select the Delimiter—the character that separates the fields of external files. For example, a
file may be tab-delimited or comma-delimited.
● Select the Quote character—the character that identifies text values. For example, if the
quote character is “ (double quotation marks), the parser expects all members to be enclosed

in double quotation marks. If the parser finds text values that are not enclosed in the double
quotation marks the parser returns an error.
● Enter the number of Header Lines to Skip. For example, an external file may have headings
such as Name, Address, City, State, and ZipCode to skip.
3 Click Next.
4 Perform an action to preview a file:
● Click , click Browse, select the file, and click Upload.

Select Specify a file URL to preview and enter a URL; for example, file:///c:/data/
previewfile.csv.
Because you specify the format of the external file, you are not constrained to a rigid format.
However, remember the following rules:
● Every line must contain the same number of columns.
● Every line must have a member value for each dimension (no blank values).
● The last column of every line is the value for the intersection (text or numeric value).
5 Click Preview Sample File.
When you preview a file, the options specified in the wizard are applied so you can see how the
options affect the data.
6 Click Next.
7 Enter the number of dimensions in the file, then click Update.

8 Enter the name for each dimension, then click Next.
9 Enter the external file name, optionally enter a description, then click Finish.

Mapping Dimensions
After you create a synchronization, you must map the dimensions that comprise each source
and destination so that the synchronization can recognize all relevant elements. When defining
a detailed synchronization, you can create links, leverage a predefined mapping table, or assign
default values to dimensions that are not required to be mapped.
➤ To map dimensions:
1 If you created a new synchronization, the Dimension Mapping is automatically displayed. Otherwise, to access
the Dimension Mapping, in the Data Synchronizer, right-click a synchronization and click Edit.
You can use the Dimension Mapping to create, modify, or delete links between source and
destination dimensions. Data Synchronization automatically links common dimensions
between Application Views. You can drag and drop to create or change links between source
and destination dimensions dynamically.
2 Create a link between a source and destination dimension by performing an action:
● Drag the dimensions that you want to map. For example, you can drag the Accounts
dimension of the source Application View to the Accounts dimension of the destination
Application View.
● Right-click the source dimension, and select Start New Link. Right-click the destination
dimension, and select End Link.
Mapping Dimensions 117

Note:
You can create one-to-one, one-to-many, or many-to-one relationships between source and
destination dimensions.
A link can be static or you can apply a mapping table to a link to further define the relationship
between the two dimensions. See “Creating Mapping Tables in the Dimension Mapping” on
page 122.
The line types represent relationships between the source and destination dimensions:
● Solid line—No mapping table is assigned. A solid line is valid for one-to-one mappings and
one-to-many mappings.
● Dotted line—A mapping table is associated with the relationship. See “Creating Mapping
Tables in the Dimension Mapping” on page 122.
The following figure shows a synchronization with one-to-one mappings and two mappings
with a mapping table.
The links are interactive, in that you can select a link to see a summary of the relationship defined
between the linked dimensions. The summary includes:
● Source Dimension
● Destination Dimension

● Relationship Type (member relationship—for example, one-to-one or mapping table
defined)
● Filter Summary
● Default Member Selection
3 Optional: To remove a link, right-click a link and select Remove Link.
After you define mappings you can optionally filter dimensions, define mappings, and assign
default members. Then, when finished, you must save the synchronization. See “Filtering
Dimensions” on page 119, “Creating Mapping Tables in the Dimension Mapping” on page
122, “Assigning Default Members” on page 120, and “Saving Synchronizations” on page 121.
Filtering Dimensions
When you create relationships between dimensions, you can also restrict the set of members
available from the source Application View. The filter is applied at synchronization execution
against the source destination members. Some instances require filtering. For example if you
move data from Entity_1 in the source to Entity_2 in the destination with a January to February
Period mapping, a filter on the source is required to extract only from Period—January;
otherwise, results may be unpredictable.
Filtering constraints:
● Filters are not supported for flat files.
● Function filters are not supported for interface tables; however, EQUAL and LIKE are
supported.
➤ To filter dimensions:
1 Right-click a dimension, and select Create Filter.
The Filter Criteria dialog box is displayed.
2 Select a filter, EQUAL, LIKE, or FUNCTION.
Note:
You can create multiple filter selections, by delimiting each entry with a semicolon; for example,
Actual; Budget.
● EQUAL—any valid member, such as Actual for the Scenario dimension.

● LIKE—use wildcards in the filter:

❍ * for multiple character
❍ ? for single character
For example, ?ctual would match Actual, *tual would match Actual.
● FUNCTION—use any valid member selection function, such as BottomOfHierarchy()
retrieves the base level members for the dimension.
3 Enter the member to filter by or click .

The Member Selector is displayed.
4 Select multiple members to filter by and click . Then, click OK.

See “Working with Members” on page 80.
Note:
Multiple functions are not supported.
The Filter Criteria dialog box is displayed.

5 Click OK.
When a filter is applied in the dimension mapping, a funnel is displayed next to the dimension.
Assigning Default Members

If a relationship is not defined for a dimension on the destination application, one member needs
to be identified to complete the linking process. This member is used to complete each data
point intersection at synchronization execution time.
➤ To assign default members:

1 In the Destination Application View in which you want to assign a default member, right-click a dimension.
The Member Selector is displayed.
2 Select the member to assign as the default, and click OK.
A green check mark is displayed next to the dimension of the default member.
Note:
To remove a default member, right-click the dimension that contains the default member, and
select Remove Default Member.
You can select the Search tab to search for members. See “Searching for Members in the Member
Selector” on page 84.

Inserting Mapping Tables
Mapping tables are mappings that you can reuse in data synchronizations. If you have created
mapping tables, you can insert them into a synchronization. For information on creating
mapping tables, see “Working with Mappings” on page 122.
➤ To insert mapping tables:
1 Click .
The Insert Mapping Table dialog box is displayed.
2 Select a mapping table to insert, and click OK.

When a mapping table is used in a dimension mapping, the link is a dotted line.
Editing Mappings
If you are editing an existing mapping table, the Mapping Table Designer displays the source
application, destination application, and the mapped dimensions relationship.
➤ To edit mappings:
1 Right-click a mapping (dotted line link).
2 Select Edit Mapping.
The Mapping Table Designer is displayed.
3 Edit the mapping. Click Next to move through the screens, and click Finish.
Saving Synchronizations
You must save synchronizations before you can validate and execute them.

➤ To save a synchronization:
1 In the Dimension Mapping, click .

The Save Data Synchronization dialog box is displayed.
2 Enter the name and description, and click OK.
Working with Mappings

You can use mapping tables to define relationships between dimensions. Mappings are used in
scenarios where you can define the mapping once and reuse it in multiple synchronizations.
When you create mapping tables, you can select multiple source application dimensions, but
only one destination application dimension. The relationship displayed signifies that source
dimension(s) members are used as members in the destination dimension. You can define one-
to-one, one-to-many, and many-to-one relationships. Data Synchronization leverages:
● mapping tables, to perform simple or complex transformations, and
● a transformation engine to map from external sources or from application to application.
You use the Mapping Table Designer to create mapping tables. See “Creating Mapping Tables
in the Dimension Mapping” on page 122 and “Creating Mapping Tables in the Data
Synchronizer” on page 125.
You can edit mapping tables in the Data Synchronizer, see “Editing Mapping Tables” on page
129.
Creating Mapping Tables in the Dimension Mapping

The following procedure provides step-by-step information on defining mappings while linking
dimensions in the Dimension Mapping. The source and destination Application Views are
automatically selected, so the first screen of the Mapping Table Designer is skipped.
➤ To create a mapping table while mapping dimensions:

1 In the Dimension Mapping, right-click a link, and select Define Mapping.
The Mapping Table Designer (Map Data) is displayed.

Each row represents a mapping rule between the source and destination application dimensions.
You enter values into cells by typing or by selecting members.
When entering source values, you can use symbols as wildcards and indicators.
Table 15 Source Dimension Rule Syntax
Symbol Usage
* Matches on one or more characters. For example, Acc* matches Acc100, Acc101, and so on.
? Matches on one character. For example, Acc??? matches Acc100 but not Acc1000.
~ Matches on a range of characters. For example, Acc100~Acc200 matches on Acc100, Acc101, and so on up to Acc200. If
both fields are numeric, the range is evaluated numerically. If either field is alphanumeric, the range is evaluated lexicographically.
\ Indicates that the next character is interpreted literally. For example, Acc\* matches only and precisely Acc*.
^ Indicates a space.
Required—for leading and trailing spaces.
Optional—for spaces displayed in the middle of inputs.
{NULL} Matches on an empty field.
Destination dimensions use different rule syntax. The source rule syntax defines which
intersections match the rule. When a row is passed through the translation engine, each source
rule is checked to see if the member fits within the rules defined. If a match is found, the
destination rule is applied to that member. The destination rules define the modifications to be
made to the members that match the source rules. The rule syntax in destination dimensions
accepts the following entries:
● Member names
● Source member names in combination with literal strings
● Contents of wildcards
Table 16 Destination Dimension Rule Syntax
Symbol Usage
[] Destination values which can be concatenated.
Working with Mappings 123

Symbol Usage
[field#] Transfer value of the indicated input field in its entirety. An input field is identified by its sequence number based on the
order of definition for the input field. For example, [1] indicates that the value of the first input is the output. FY[1][2] indicates
that the output value is the string FY concatenated with the value of input 1 and the value of input 2, so if input 1 is Years,
and input 2 is Months, the result is FYYearMonths.
[field#,* ] The value of * from the input field. For example, if Output1 is defined as [1,*] and Input1 is defined as 123*, if Input1 =
123456, Output1 = 456.
[field#,*#] Required format if the referenced * is not the first instance of * in the input.
# is the position of the * in the input field.
[1, *1] is equivalent to [1, *].
For example, if Input3 = *123* and Output1 = abc[3, *2], Input3 = 91234 and Output1 = abc4.
[field#,?] The value of ? from the input field. For example, if Output1 is defined as [1,?] and Input1 is defined as 123?, if Input1 =
123456, Output1 = 4.
[field#,?#] Required format if the referenced ? is not the first one in the input.
# is the position of the ? in the input field.
[2, ?1] is equivalent to [2, ?].
For example, if Input1 = 123?, Input2 = 4??, and Output1 = abcd[2, ?2] and Input1 = 1237, and Input2 = 498, Output1
= abcd8.
\ Indicator that the next character is interpreted literally. A \ is necessary when the [ or ] character is used in an output. In an
output, the use of \ within a [] definition is not allowed.
^ A space indicator.
Required—for leading and trailing spaces.
Optional—for spaces displayed in the middle of inputs.
{NULL} Value used to output an empty field.
● For the source, double-click a cell, and enter a rule. Use the syntax described in Table 15,
“Source Dimension Rule Syntax,” on page 123.
● For the destination, double-click a cell and enter a rule. Use the syntax described in Table 16,
“Destination Dimension Rule Syntax,” on page 123.
● Select a cell, click Pick Member, and in the Member Selector dialog box, select a member,
and click OK.
3 If necessary, modify the mapping:
● To insert a row at the end of the table, click Add.
● To copy a row, select a row, and click Duplicate.
Duplicate rows are inserted at the end of the table.
● To delete a row, select multiple rows, and click Remove.

● To move rows up or down in the table, select the rows, and click Move Up or Move Down.

The rules are processed in order. When a match occurs, the rule is applied to the member
and processing completes (no other rules are applied to that member). In some cases,
members may match multiple rules so you can control the order of the rules.
● To edit a cell, double-click the cell or press [F2].
Tip:
You can navigate the table using the [Tab] key.
4 Click Next to validate the mapping tables.
The Validate Mappings screen contains a table with mapping rules in each row. Only rule syntax,
not member information is validated. Each rule is marked as passed or failed.
5 Click Validate.
Tip:
You can click View All to view all rules or View Exceptions Only to view only rules that do not
pass validation.
6 If a rule did not pass validation, click Back to return to the Map Data page, fix the errors, and click Next to
re-validate.
7 Click Next.
The Mapping Properties screen is displayed, enabling you to provide a name and description
for the mapping table. It is helpful to provide a prefix, such as MAP_.
8 Enter a name and description, and click Finish.
There are no restrictions for names and descriptions.
A dotted line indicates that a mapping is defined.
The mapping also displays in the Data Synchronizer. See “Working with the Data Synchronizer”
on page 127.
Creating Mapping Tables in the Data Synchronizer

The following procedure provides step-by-step information on defining mapping tables in the
Data Synchronizer, including selecting the source and destination Application Views.
Before you create a mapping table, you must create at least one Application View.
➤ To create mapping tables in the Data Synchronizer:

1 Select File > New > Mapping Table.
2 Click to select a source application.

The Source Application dialog box is displayed.
Working with Mappings 125

3 Select a Source Application. If the application is a Planning application, select the Plan Type. Then, click
OK.
4 Click to select a destination application.

5 Select a Destination Application. If the application is a Planning application, select the Plan Type. Then,
click OK.
The dimensions change depending on the plan type.
6 Choose the Source and Destination Dimensions, and click Next.
7 Perform these actions:
a. Map the data, and click Next.
b. Validate the mappings, and click Next.
c. Enter a name and description, and click Finish.
See “Creating Mapping Tables in the Dimension Mapping” on page 122 for step-by-step
information on mapping data and validating mappings.
You can view all defined mapping tables in the Data Synchronizer. See “Working with the Data
Synchronizer” on page 127.

Working with the Data Synchronizer
➤ To access data synchronizations and mapping tables, click Navigate > Administer > Data
Synchronization.
Navigating the Data Synchronizer

The Data Synchronizer identifies all synchronizations and mapping tables. If you select a
synchronization, the lower pane displays the following information:
● Summary—Name, date created, and date last modified
● Description—The information that you provided in the Description text box of the New
Synchronization dialog box
● Properties—The status and the date last synchronized
● Applications—The source and destination applications in the synchronization
● Mapping Tables—The mapping tables used in the synchronization
If you select a mapping table, the lower pane displays the following information:
● Summary—Name, date created, and date last modified
● Description—The information that you provided in the Description text box of the New
Synchronization dialog box
● Source Dimensions—The source dimensions used in the mapping table
Working with the Data Synchronizer 127

● Destination Dimensions—The destination dimensions used in the mapping table
● Synchronizations—The synchronizations that use the mapping table
Changing the Data Synchronizer View
➤ To change the Data Synchronization view:

1 Select View > Details.
Viewing details shows the synchronization name, description, and date created.
2 To sort by a column, click the column heading. For example, if you want to sort by name, click Name.
3 To move a column, click and drag the column heading to a new location.
4 To change the view to icon view, click View > Icons.
Filtering Synchronizations
You use filters to hide synchronizations or mappings from view.
➤ To create data synchronization filters:

2 Clear the types that you do not want to view.

3 Clear the status that you do not want to view, for example, you may not want to see synchronizations that
are out of sync.
4 Click OK.
Editing Synchronizations
➤ To edit synchronizations:
1 In the Data Synchronization, right-click a synchronization, and select Edit.

Tip:
You can also double-click to edit a synchronization.
2 As necessary, modify the mappings and click .
Editing Mapping Tables

➤ To edit mapping tables:
1 Double-click a mapping or right-click a mapping and select Edit.
2 Modify the values to be mapped, then click Next.
3 Validate the mappings, then click Next.
4 Modify the mapping properties, then click Finish.
Duplicating Synchronizations and Mappings

➤ To duplicate synchronizations and mappings:
1 In the Data Synchronization module, right-click a synchronization or mapping, and select Duplicate.
If you duplicate a synchronization and are using a mapping table, the mapping table is used for
the original and duplicated synchronization.
2 In the Duplicate dialog box, enter the name and description, then click OK.
Deleting Synchronizations and Mappings

➤ To delete synchronizations and mappings:
1 In the Data Synchronization module, right-click a synchronization or mapping, and select Delete.
2 If necessary, select View > Refresh.
The synchronization or mapping is removed.
Validating and Executing Synchronizations

When you execute a synchronization, data is retrieved from the source Application View,
transformed according to mapping rules, and pushed to the destination Application View where
it is committed to the Application View. When you validate a synchronization, the same process
is followed but the data is not committed to the destination Application View. This enables the
source and destination to process the request and resulting data to generate errors that might
occur without writing the data. You can quickly identify if issues exist with the synchronization.
Working with the Data Synchronizer 129

If your destination is a Consolidation Application View, the Data Synchronizer uses the default
values for: Load Mode=Merge; Accumulate within File = False; and File Contains Ownership
Data= False.
Note:
If a shared location is used for an external file, this data file needs to be accessible by the server
validating or executing the synchronization.
➤ To validate synchronizations:
● In the Data Synchronizer, right-click a synchronization, and select Validate
Synchronization.
● In the Dimension Mapping, click .

The Data Sync Validation Options dialog box is displayed.
2 Select the Operator and type the Value.
You should select the operator and enter a value if the values from the source are on a different
scale than the destination. You can select Multiply, Divide, Add, or Subtract and then enter a
numeric value to apply with the operator. For example, if you select the operator * (Multiply)
and enter the value, 10, each data value sent to the destination will be multiplied by 10.
3 If the synchronization uses an external source file, enter the URL for the source, or click Upload to use a file
as the source.
4 Click OK.
➤ To execute synchronizations:
● In the Data Synchronizer, right-click a synchronization, and select Execute.
● In the Dimension Mapping, click .

The Data Sync Execution Options dialog box is displayed.
2 Enter the Operator and Value.
3 If the synchronization uses an external source file, enter the URL for the source, or click Upload to use a file
as the source.
4 Click OK.

Managing Jobs
5
In This Chapter
Working with the Job Console................................................................................................... 131
Navigating the Job Console ..................................................................................................... 132
Viewing Job Attachments........................................................................................................ 137
Deleting Jobs ..................................................................................................................... 139
Working with the Job Console

The Job Console is a central component that provides the infrastructure for handling jobs across
many functional areas. A job is an asynchronous process that you submit to run behind the
scenes in BPM Architect.
The Job Console enables you to view and manage jobs in one centralized location. Generally,
there are two job categories: jobs and job status that need availability across sessions and jobs
that are tied to a session.
The Job Console supports the following job types:
Job Type Job associated with...
Import importing dimensions into the Dimension Library
Consolidation Application Deploy deploying a Consolidation application
Planning Application Deploy deploying a Planning application
Analytics Application Deploy deploying an Analytic Services application
Data Synchronization executing data synchronizations
Transaction History exporting of transaction history
Compare comparison of Application Views
Property Query property queries
Application Upgrade upgrading existing Hyperion applications
Application Migration migrating existing Hyperion applications
Working with the Job Console 131

➤ To open the Job Console, click Navigate > Administer > Job Console.
Running Jobs is displayed.
Each job captures information during the life of a job, during the initial submitted time or job
processing.
Navigating the Job Console

The Job Console shows BPM Architect jobs. You can select a job in the top pane and view
summary information in the bottom pane. The bottom pane displays:
● Summary—Information about the job
❍ Started Time—Used for smaller strings
❍ Submitted Time—Used for large quantities of content
❍ Last Updated Time—Last time the job was updated
❍ User Name—User name that submitted the job
❍ Process Name—Process name in which the job is running
❍ Thread—Thread ID of the current job
❍ Server—Server name where the job is running
132 Managing Jobs

❍ Detail—Job summary, including errors and warnings
● Attachments—Each job can have multiple attachments to include additional information.
Each attachment can differ and be independent. For example, you can use input parameter
files, output log files, or output result files. There are two types of attachments:
❍ Plain Text—Used for smaller strings
❍ File—Used for large quantities of content
● Status—Displays the status and progress. Each job can have the following status:
❍ Invalid—No job is running on the server
❍ Scheduled Start—Queued but has not yet started
❍ Scheduled Stop—Cancelled, but is still running
❍ Starting—Preparing to start
❍ Running—Currently running
❍ Paused
❍ Stopping—In the process of stopping
❍ Stopped—Stopped at the user's request
❍ Aborted—Aborted due to an error
❍ Completed—Completed successfully
❍ Not Responding
Note:
You cannot change the status of a job.
Changing the Job Console View

➤ To change the Job Console view:
1 To change the number of jobs per page, click Per Page and select the number of jobs, such as 100.
2 To sort by a column, click the column heading. For example, if you want to sort by name, click Name.
3 To move a column, drag the column heading to a new location.
4 To scroll through pages of jobs, click and to scroll to the last page.
5 To scroll through previous pages, click or to go to the first page.
Tip:
As you move through pages of jobs, you may want to refresh the Job Console to view the latest
job status. See “Refreshing the Job Console” on page 134.
Navigating the Job Console 133

Refreshing the Job Console
You can refresh the Job Console to view the latest status of jobs.
➤ To refresh the number of jobs displayed, click .
Creating Job Filters

You can create filters to see specific jobs in the Job Console.
➤ To create a filter:
1 Right-click a job and select FilterBy or click View > Filter.
The Jobs Filter dialog box is displayed.
2 You can filter jobs by these options:

a. Self or Other User—Select Self to create a filter to view jobs submitted by your user name
or select Other User and enter the user name. See “Filtering Your Jobs” on page 135 and
“Filtering Jobs for Other Users” on page 136.
b. Job ID—Enter the Job ID
c. Job Type—Select the job type to filter, such as Dimension Import.
d. Job Status—Select the status to filter, such as Completed.
e. Submitted Time From and To—Select a start date and end date to filter by a date range.
3 Click OK.
134 Managing Jobs

Tip:
To reset the filter to the default options, click Reset.
If jobs are filtered, a link (Job Filter Option) to the Jobs Filter dialog box is displayed in the
Running Jobs window.
Filtering Your Jobs

You can filter the jobs you see in the Job Console to only your jobs. Filtering jobs helps in
managing jobs, including deleting outdated jobs. For information on deleting jobs, see “Deleting
Jobs” on page 139.
➤ To filter your jobs:

2 If available, enter the job ID.

3 Select the job type.
4 Select the job status and time, then click OK.
The Job Console displays only your jobs, according to the selections in the Jobs Filter dialog box.
The following figure shows jobs with the following filters: self and dimension import.
Navigating the Job Console 135

Filtering Jobs for Other Users
You can filter jobs you see in the Job Console for another user.
➤ To filter jobs for other users:

2 Enter the user name.

3 If available, enter the job ID.
4 Select the job type.
5 Select the job status and time, then click OK.
The Job Console displays jobs according to the selections in the Jobs Filter dialog box.
Security
The Job Console uses BPM Architect roles for submitting and displaying jobs.
Security for Submitting Jobs

Authenticated users can submit jobs for the job types described in the previous sections.
Security for Displaying Jobs

Users who submit jobs have full access to the jobs in the Job Console—to update and to read.
In addition, users who are part of other BPM Architect roles (Dimension Editor, Application
136 Managing Jobs

Creators, Create Integrations, Run Integrations) can also have access to jobs based on the
following table.
Table 17 Job Type Security
Job Type Who can see:
Import User, Dimension Editor
Consolidation Application Deploy User, Financial Management Application creator, Dimension Editor
Planning Application Deploy User, Planning Application creator, Dimension Editor
Analytics Application Deploy User, Essbase Application creator, Dimension Editor
Data Synchronization User, Create Integrations, Run Integrations
Transaction History User, Dimension Editor
Compare User, Dimension Editor
Property Query User, Dimension Editor
Export User, Financial Management Application creator, Planning Application creator,

Essbase Application creator
Application Upgrade User, Financial Management Application creator, Planning Application creator,
Essbase Application creator, Dimension Editor
Application Migration User, Financial Management Application creator, Planning Application creator,
Essbase Application creator
Viewing Job Attachments

Each attachment type can be associated with the viewer type on the results of the job. For
example, you can view an error log file generated from the import process using the Import
Error Log Viewer. If an attachment does not have a specific viewer implemented, by default you
can view it as a text file.
Viewing Job Attachments 137

Viewing Import Results
➤ To view import results, in the Job Console – Attachment area, click Import Results.
See “Creating Import Profiles” on page 34.
Viewing Text Files

You can view the following jobs as text file attachments:
● Data Synchronizations—session log files created for the source, destination, and data
synchronization.
● Compare—if a compare fails, a text file is attached to the job.
● Deploy—if a deployment fails, a text file is attached to the job.
➤ To view a text file attachment, in the Job Console – Attachment area, click the log file link.
The following figure shows the log files in the Attachment area for a data synchronization.
138 Managing Jobs

Deleting Jobs
It is important to delete jobs, as it can be difficult to maintain large numbers of jobs in the
database. Deleting jobs makes it easy to navigate the Job Console. Remember, you must have
the appropriate user permissions to delete jobs.
➤ To delete jobs:
1 In the Job Console, right-click a job and select Delete.
The Confirm Delete dialog box is displayed.
2 Click OK.
Deleting Jobs 139

140 Managing Jobs
Using Task Automation
6
In This Chapter
Overview .......................................................................................................................... 141
Prerequisites for Task Automation.............................................................................................. 142
Managing Taskflows ............................................................................................................. 142
Creating Taskflows .............................................................................................................. 143
Viewing Taskflows ................................................................................................................ 149
Editing Taskflows ................................................................................................................ 150
Copying Taskflows ............................................................................................................... 150
Deleting Taskflows .............................................................................................................. 150
Running Taskflows Manually .................................................................................................... 151
Managing Access Permissions to Taskflows ................................................................................... 151
Assigning Access Permissions to Taskflows ................................................................................... 152
Viewing Taskflow Status ......................................................................................................... 154
Stopping Active Taskflows ...................................................................................................... 155
Overview
Task Automation provides a method for chaining a series of tasks into a taskflow. You can use
Task Automation to automate tasks that you commonly perform using BPM Architect.
When you work with BPM Architect, you routinely perform tasks such as importing dimensions,
data synchronizations, and redeploying Application Views. You can create and maintain
taskflows to perform BPM Architect operations and schedule critical tasks to be run as required.
BPM Architect supports these taskflows:
● Data Synchronizations
● Import dimensions from flat files
● Import dimensions from interface tables
● Consolidation Redeploy
● Planning Redeploy
● Analytic Services Redeploy (for Enterprise Analytics and Essbase Analytics applications)
Overview 141
Prerequisites for Task Automation
Consider these prerequisites for Task Automation:
● You must install Shared Services. See the Hyperion System 9 Shared Services Installation
Guide.
● You must register your Application View with Shared Services. Registration automatically
occurs when you deploy an Application View in BPM Architect.
Managing Taskflows
From the Manage Taskflows option, you can create, edit, save, copy, and delete taskflows, view
a list of available taskflows, assign access to taskflows, and run taskflows manually. See these
procedures:
● “Creating Taskflows ” on page 143
● “Adding Stages ” on page 146
● “Adding Links ” on page 148
● “Editing Taskflows ” on page 150
● “Copying Taskflows ” on page 150
● “Deleting Taskflows ” on page 150
● “Running Taskflows Manually” on page 151
● “Managing Access Permissions to Taskflows” on page 151
● “Assigning Access Permissions to Taskflows” on page 152
● “Viewing Taskflow Status” on page 154
● “Stopping Active Taskflows ” on page 155
142 Using Task Automation

➤ To manage taskflows, from BPM Architect, select Administration > Manage Taskflows.
Creating Taskflows
You create a taskflow to link a series of tasks and specify the time to run them. When you create
a taskflow, you assign it a name and description. Then you specify the taskflow details, such as
task stages and links between tasks.
➤ To create taskflows:
1 From the Taskflow Listing Summary screen, click New.
2 For Name, enter a taskflow name. You may want to prefix the taskflow name with BPMA, to easily recognize
BPM Architect taskflows.
The name can contain up to 40 characters.
The Application text box displays the name of the current application.
3 For Description, enter a taskflow description.
4 Click Submit.
The taskflow editor is displayed, where you can add stages and links.
Creating Taskflows 143

BPM Architect Actions
BPM Architect supports these actions:
● “Data Synchronization” on page 144
● “Import Dimensions From Flat File” on page 144
● “Import Dimensions from Interface Table” on page 145
● “Redeployment” on page 145
Data Synchronization
➤ To create data synchronization taskflows:

1 Select Processing, and select the application. For example, BPMA- Budget.
2 Select the action, Execute Data Synchronization.
● Synchronization Type—select URL, then click Edit. Choose the synchronization and click
Submit.
● Optional: External Source File—if the synchronization uses an external source file for the
source of the synchronization, type the location of the external source file.
The location must be a Universal Naming Convention (UNC) location in which your web
server has access. For example, \\server\file.dat.
● Mode—select Scan or Load.
❍ Scan—does not commit the data for the synchronization, instead, it tests the
synchronization by running it without writing the new data.
❍ Load—fully executes the synchronization.
4 Click Save.
Import Dimensions From Flat File
➤ To create flat file import taskflows:

1 Select the application.
2 Select the action, Import Dimensions From Flat File.
● Select Profile Name—select URL, click Edit, select the profile, and click Submit.
● Optional: Import Dimensions File—if the profile uses an external flat file, select TEXTBOX,
then type the location.
The location must be a Universal Naming Convention (UNC) location in which your web
server has access. For example, \\server\file.dat.

4 Click Save.
Import Dimensions from Interface Table
➤ To create interface table import taskflows:

2 Select the action, Import Dimensions From Interface Area.
3 In Select Profile Name, select URL, click Edit, select the profile, and click Submit.
4 Click Save.
Redeployment
You can create taskflows for Consolidation, Planning, and Analytic Services redeployments.
Consolidation
➤ To create consolidation redeploy taskflows:

2 Select the action, Consolidation Redeploy.
● Consolidation App—select URL, then click Edit. Choose the Application View and click
Submit.
● Optional: Clear All Metadata and Data—select PICKLIST, then select True or False.
● Optional: Check Referential Integrity—select PICKLIST, then select True or False.
4 Click Save.
Planning
➤ To create planning redeploy taskflows:

2 Select Planning Redeploy.
● Planning App—select URL, then click Edit. Choose the Application View and click
Submit.
● Datasource—select TEXTBOX, then type the original Planning data source location. (The
database or Essbase cube that the Application View uses.)
● Optional:

❍ Create Outline—select PICKLIST, then select True or False
❍ Refresh Outline—select PICKLIST, then select True or False
❍ Create Security Filters—select PICKLIST, then select True or False
❍ Shared Members Security Filters—select PICKLIST, then select True or False
❍ Validate Security Filter Limit—select PICKLIST, then select True or False
Note:
You must assign security to members in Planning Dimension Editor on the Planning web. The
Planning security options are described in the Hyperion System 9 Planning Administrator's
Guide.
4 Click Save.
Analytic Services
➤ To create Analytic Services redeploy taskflows:

2 Select the action, Analytic Services Redeploy.
● Essbase App—select URL, then click Edit. Choose the Application View and click Submit.
● Optional: Clear All Data—select PICKLIST, then select True or False.
4 Click Save.
Adding Stages
A stage describes a step in a taskflow usually performed by one individual. Each stage has an
action. These actions can have parameters in which values are supplied at runtime.
You define a stage using these three tabs:
● General: Defines the stage name, description and user ID of the user responsible for running
the stage. The user can be an initiator, which is the owner of the first stage in the taskflow,
or another user for the other stages.
● Processing: Defines the action to be performed when the taskflow is run and any required
parameters.
● Starting Event: Defines the taskflow start time, and the scheduled times for the event to
occur, based on the application server time, not the local user’s computer. This tab is
displayed only for the first stage in the taskflow. It displays the scheduled event (taskflow
start time), or is disabled (for the manual start of a taskflow executed by the Run Now
option).

➤ To add stages:
1 From the taskflow editor, click Add Stage.
A new stage is displayed in the left panel, and stage details are displayed in the right panel. If
stages exist in the taskflow, the new stage is created at the end of the taskflow.
2 Select General and enter this information:
a. For Name, enter a stage name; for example, Data_Synchronization.
Note:
Stage names cannot contain spaces. The name can contain up to 30 characters.
b. Optional: For Description, enter a taskflow description; for example, Perform
synchronization daily.
c. From Run As, select UserName, and enter a username and password for the user who
launches the taskflow.
Note:
Stage 1 requires that you enter a username and password. When you create future stages,
you can select to run as the Initiator, which tells the system to use the user ID and password
that was defined in Stage 1.
3 Select Processing and enter this information:
a. From Application, select an application from which to run the task.
b. From Action, select an action to perform; for example, Data_Synchronization.
Note:
See “BPM Architect Actions” on page 144.
c. From Type for each parameter, select Picklist, Text Box, or URL for the Point of View,
depending on the action, and enter values for the parameter.
For example, for the Data_Synchronization action, the Mode option contains a picklist
from which you can select Merge, Accumulate, or Replace.
For the data file and log file names and paths, you must manually enter the information
in a text box. The taskflow is executed from the server, so you must make sure that the file
names and paths are valid and can be accessed from the server running the task. Therefore,
you should not enter a path such as c:\file.dat that references your own hard drive.
You must identify the computer name and share directory for the file using Universal
Naming Convention (UNC); for example, \\HFMServer\share\path\file.dat.
4 Select Starting Event and enter this information:
a. From Starting Event, select an event.
The Server Date information is displayed for informational purposes.
b. For Start Date, enter the date for the task to be run, or click the pop-up calendar and select
a date.

c. From Start Time, select a time for the task to be run.
Note:
This time is based on the application server, which is identified on the Server Date line.
d. For a recurring task, select Recurrence, and from Recurrence Pattern, select the task
frequency.
e. Select an option for the task end date and time:
● No End Date
● End After occurrences, and enter the number of occurrences
● End Date, enter an end date and select an End Time.
5 Optional: To add a stage, click Add Stage and complete the stage information for General and Processing
Note:
The Starting Event tab is available only for the first stage.
Shared Services Stage Actions and Parameters

Table 18 Stage Actions and Parameters for Shared Services
Action Parameters
Email Action that enables e-mail messages to be sent automatically to an e-mail address. Complete these
parameters for the e-mail action:
● To: Type an e-mail address for the recipient
● Subject: Type a subject for the e-mail
● Message: Select a variable (by double-clicking a variable from the variables list) to display success or
failure
● Variables: Lists the available variables for the e-mail action
Execute Action that runs external programs from a command line. Complete these parameters for the execute action:
● Command: Type a command to run an external program.
The external program can be a valid command line script (such as a “bat” script on Windows or
a “sh” script on UNIX) and any valid program execution command. Make sure that your bat file
does not resolve the path dynamically; if the files uses any variables to resolve the path, it will
not work.
The command must include the full path to the executable. For example, to launch Internet
Explorer, type: C:\Program Files\Internet Explorer\IEXPLORE.EXE.
Adding Links
A link is the point during the taskflow execution where the activity in one stage is completed
and the control passes to another stage, which starts. A link can be unconditional, where the

completion of one stage leads to the start of another, or conditional, where the sequence of
operation depends on multiple link conditions.
A link specifies the action for the system to take next. Every stage needs a link. In general, most
stages have two links: success and failure. For the success link, you can specify that if the first
stage succeeds, the system should proceed to the second stage, called the Receiving stage. For
the failure link, you specify the action to be performed if problems occur in the first stage.
For example, you can set a success link so that if the first stage of Data_Synchronization succeeds,
the system proceeds to the Redeploying_Consolidation stage. You can set a failure link so that
if failure occurs or any problems are encountered in the Data_Synchronization stage, the system
proceeds to the Redeploying_Consolidation stage of End, which ends the process and terminates
the taskflow.
The last stage in the taskflow must have a final link with “End” as the target to complete the
taskflow.
You can specify variables for an event. For example, you can add a variable for a load data task
such as Data_Synchronization_Result==Success.
➤ To add links:
1 Click Add Link.
2 Select General and for Name, enter a link name.
The name can contain up to 30 characters.
3 For Description, enter a link description.
The Sending Stage is displayed for informational purposes.
4 From Receiving Stage select a stage.
5 Select Condition tab if applicable, and from Variable, select a variable, for example,
Data_Synchronization_Result.
6 From Value, select Success or Failure.
7 Click Add.
Note:
Ensure that the last stage in the taskflow has a link with an End target.
Tip:
To delete a condition, click Delete.
Viewing Taskflows
You store and manage taskflows in Shared Services. The Taskflow Listing Summary shows the
available taskflows by application, the user who created the taskflow, and a description.
Viewing Taskflows 149

➤ To view taskflow lists, select Administration > Manage Taskflows.
Editing Taskflows
After you create a taskflow, you can edit the taskflow description, and create, edit, or delete
taskflow variables. You can also add or delete a stage or a link.
➤ To edit taskflows:
1 Select Administration > Manage Taskflows.
2 Select the taskflow to edit and click Edit.
3 In the taskflow editor, select an option:
● To add a stage, click Add Stage. See“Adding Stages ” on page 146.
● To add a link, click Add Link. See “Adding Links ” on page 148.
● To delete a stage or link, click Delete.
Note:
If you delete a stage, all links associated with it are also deleted.
● To edit the taskflow description, click Properties.
4 Edit the taskflow and perform an action:
● To save the edits, click Save.
● To cancel the edits, click Cancel. The system returns you to the Taskflow Listing Summary
without saving your changes.
Copying Taskflows
After you define a taskflow for an application, you can copy it to a different application.
➤ To copy taskflows:
2 Select the taskflow to copy and click Save As.
3 Enter a new name and description for the taskflow.
4 Click Submit.
Shared Services adds a copy of the taskflow with a new name to the Taskflow Listing Summary.
Deleting Taskflows
You can delete a taskflow that you no longer need.

➤ To delete taskflows:
2 From the list of taskflows, select the taskflow to delete, and click Delete.
Running Taskflows Manually

You can run a taskflow manually instead of waiting for it to start automatically. You might want
to test a taskflow before the time that it is scheduled to run. This enables you to make adjustments
to the taskflow before it runs.
➤ To run taskflows manually:

2 From the list of taskflows, select the taskflow to run and click Run Now.
Managing Access Permissions to Taskflows

Shared Services enables you to manage access permissions to taskflows in applications
independent from any product application. You assign permissions on a model-by-model basis
to individual users or to groups of users. You can also assign permissions at the application level.
To access specific taskflows, users must be assigned access rights individually or inherit access
rights by being part of a group that is assigned access rights. If an individual group is assigned
to a group and the access rights of the individual user conflict with those of the group, the rights
of the individual user take precedence.
To give users access to taskflows other than their own, an administrator must add the users and
assign their permissions.
Taskflow management provides these types of permissions:
Table 19 Task Flow Permissions
Permission Description
Read View a taskflow.
Write Edit a taskflow.

Write permission does not automatically include Read permission. You must assign Read permission
explicitly, in addition to Write permission, if you want a user to have both.
Manage Create new users and change permissions for users.

Manage permission does not automatically include Read and Write permissions. You must assign Read
and Write permissions explicitly, in addition to Manage permission, if you want a user to have all these
permissions.
You can apply permissions to groups and to individual users. Users are automatically granted
the permissions of the groups to which they belong. You can, however, explicitly add or deny
permissions to a user to override group permissions.
Running Taskflows Manually 151

For each type of access permission (Read, Write, and Manage), you must perform an action:
● Grant: Explicitly grant the permission to the user or group.
Granting permissions to a member of a group overrides permissions inherited from the
group. For example, if a group is denied a permission, you can explicitly grant the permission
to a member of the group.
● Deny: Explicitly deny the permission to the user or group.
Denying permissions to a member of a group overrides permissions inherited from the
group. For example, if a group is granted a permission, you can explicitly deny the permission
to a member of the group.
● None: Do not apply the permission to the user or group.
Assigning Access Permissions to Taskflows

You can assign permissions to individual users or to groups of users for individual taskflows.
You must have Manage permission for a taskflow to assign permissions to it.
Users inherit the permissions of the groups to which they belong. Permissions that you assign
to an individual user, however, override any group permissions that the user inherits.
Assigning (or denying) a permission does not implicitly assign (or deny) any other permissions;
that is, assigning Write permission does not implicitly assign Read permission, and assigning
Manage permission does not implicitly assign Read and Write permissions. Likewise, denying
Read permission does not implicitly deny Write and Manage permissions, and denying Write
permission does not implicitly deny Manage permission. You must explicitly assign all
permissions for each user.
➤ To assign permissions to taskflows:

1 Select a taskflow and click Access Control.
You can view the permissions that are assigned to users and groups for the selected taskflow in
the Access Listing window.
2 To add users or groups, click Add.
The Add Principal window is displayed. Available Users/Groups lists users who are authenticated
as Shared Services users. If a user is not on the list, contact the administrator to add authenticated
users.
3 Optional: To search for users or groups:
a. From the drop-down list, select Users or Groups.
b. Enter the user or group name.
c. From Provider, select the provider that contains the user or group.
d. Click Search.
4 For Available Users/Groups, select users or groups to assign to this taskflow (press Ctrl to select multiple
users).

5 Click Add to move the selected users and groups to Selected Users/Groups or click Add All to move all
users and groups to Selected Users/Groups.
Note:
Group names are preceded by an asterisk (*).
6 For the Read, Write, and Manage permissions, select an access type: Grant, Deny, or None.
7 Click Add to assign the permissions.
Editing Permissions to Taskflows

You can edit the permissions of individual users and groups on individual taskflows. You must
have Manage permission for a taskflow to change permissions for it.
➤ To edit permissions to taskflows:

3 Select the users or groups and click Edit.
The window shows the permissions assigned to the selected users or groups.
4 Select one of the Grant, Deny, or None options for the Read, Write, and Manage permissions.
5 Click an option:
● Update to accept the changes
● Close to cancel the changes
To view changes to taskflow access, you must log out of the product application, close the
browser, and re-log on to the product application.
Deleting Permissions to Taskflows

You can delete all permissions for users and groups to individual taskflows. You must have
Manage permission for a taskflow to delete access to it.
➤ To delete access to taskflows:

You can view the permissions that are assigned to users and groups for the selected taskflow.
3 Select the users or groups and click Delete.
Assigning Access Permissions to Taskflows 153

Viewing Taskflow Status
The Taskflow Status Summary enables you to check the status of taskflows, including those that
are active, completed, or stopped. You can view all taskflows, or you can filter the list of taskflows
by status, application, or the date or range of dates on which the taskflow was initiated.
You can drill down on individual taskflows to view details of the taskflow in the Taskflow
Participant Summary. The Taskflow Participant Summary displays the status for each stage of
the taskflow and the time it was completed. You can see the stages that were completed
successfully and those that failed. This information can be used to troubleshoot the automation
routine.
Table 20 Taskflow Status Summary Elements
Element Description
Status Filter on these taskflow types:

● Active
● Done
● Stopped
● All
Application Application participating in the taskflow
Taskflow Taskflow name
Initiated between (optional) Enter or select by clicking the date or range of dates in which the taskflow was initiated
Search Click to display in the Taskflow Listing area a list of taskflows that meet the search
criteria that you specify
Taskflow Listing Displays taskflows that meet the search criteria that you specify, such as:
● ID
● Application*
● Taskflow*
● Initiator*
● Started* (lists the latest taskflow first)
● Status*
● Description
*Indicates data that is sortable. You may sort taskflows by Application, Taskflow,
Initiator, Started, or by Status by clicking on the column header.
Stop Stop an active taskflow instance.
Delete Delete the selected taskflow instance.

Note: The taskflow must be stopped before you can delete it.
Delete All Delete all of the selected taskflow instances.
Display in the Taskflow Listing area the first page of taskflow instances that meet the
specified search criteria.

Element Description
Display in the Taskflow Listing area the previous page of taskflow instances that meet
the specified search criteria.
Page Select a page to display in the Taskflow Listing area.
Display in the Taskflow Listing area the page you selected in the Page drop-down list
box.
Display in the Taskflow Listing area the next page of taskflow instances that meet the
Display in the Taskflow Listing area the last page of taskflow instances that meet the
Refresh Refresh the taskflow instances listed in the Taskflow Listing area.
From the Taskflow Status Summary, you can also stop an active taskflow. See “Stopping Active
Taskflows ” on page 155.
➤ To view taskflow status:

1 Select Administration > View Taskflow Status.
2 Double-click a task ID to display its status.
3 To search for a taskflow, select the filter criteria, and click Search.
Stopping Active Taskflows

Active taskflows are taskflows that are in progress. You can stop taskflows that are not in progress.
For example, you can stop a taskflow that has errors and make adjustments to it.
➤ To stop active taskflows:

2 From Status, select Active.
3 Optional: To filter the list, select search criteria for the taskflow, and click Search.
4 Select the taskflow to stop and click Stop.
Viewing the Taskflow Participant Summary

The Taskflow Participant Summary lists the participants in a taskflow and provides status
information for each participant instance.
➤ To view taskflow participant status:

1 Select Administration > View TaskflowStatus.
Stopping Active Taskflows 155

2 Select the search criteria for the taskflows, and click Search.
To view all of the taskflows in the Shared Services taskflow management system, select (Status)
All and click Search.
3 In the Taskflow Listing area, find the taskflow for which to view the participant summary and click the taskflow
ID.
The Taskflow Participant Summary window is displayed.
4 Click Cancel to return to the Taskflow Status Summary window.
Table 21 Taskflow Participant Summary Window Elements
Element Description
Taskflow Summary Summary information for the selected taskflow (items appear in the order of completion):
● ID
● Application
● Taskflow
● Initiator
● Started
● Status
● Description
Participant Stage participant name. Participants are selectable. Click a participant to view details about a
taskflow participant.
Stage Name Stage name
Status Stage status:

● Active
● Done
● Stopped
● All
Success Variable Outcome of the completed stage
Completed Date and time of stage completion
Viewing the Taskflow Participant Details

The Taskflow Participant Details window displays the details for a taskflow participant.
➤ To view taskflow participant details:

2 Select the search criteria for the taskflows, and click Search.
To view all the taskflows in the Shared Services taskflow management system, select (Status) All
and click Search.

3 In Taskflow Listing, find the taskflow for which to view the participant summary and click the taskflow ID.
4 Click a participant to view taskflow participant details.
Shared Services displays the Taskflow Participant Details window and sorts the participant events
chronologically.
5 Click Cancel to return to Taskflow Participant Summary.
Stopping Active Taskflows 157

Working with Financial
A Management Dimensions
In This Appendix
Account ........................................................................................................................... 160
Custom............................................................................................................................ 166
Entity .............................................................................................................................. 168
Scenario .......................................................................................................................... 169
Application........................................................................................................................ 171
Organization by Period........................................................................................................... 175
Consolidation Method ........................................................................................................... 175
Currency .......................................................................................................................... 178
System-Generated Accounts.................................................................................................... 180
Setting Up Intercompany Partners.............................................................................................. 181
Metadata Filtering Based on Security.......................................................................................... 183
Metadata Referential Integrity .................................................................................................. 184
In Financial Management, for some dimensions, you must create associations with other
dimensions. For instructions on creating associations, see “Creating Dimension Associations”
on page 45.
Dimension names can contain a maximum of 20 characters.
Table 22 Financial Management Associations
Dimension (Source) Property Name Dimension (Target)
Account Plug Account Account
Alias Alias
Custom1–4 Top Member Custom1–4
Security Class SecurityClass
ConsolidationMethod Alias Alias
Currency Alias Alias
Custom1–4 Alias Alias
159
Dimension (Source) Property Name Dimension (Target)
Entity Alias Alias
Currency Currency
Holding Company Entity
ICP Top member ICP
Security As Partner SecurityClass
ICP Alias Alias
Period Alias Alias
Scenario Alias Alias
Default Frequency View
Default Frequency For IC Transactions View
Value Alias Alias
View Alias Alias
Year Alias Alias
Account
Table 23 Account Properties
Property Value Description
Alias Description for the account. The description can contain a

maximum of 80 characters.
To use the Alias property, you must create an Alias
dimension, define the properties, and associate the Alias
dimension with another dimension. For example, you can
create an Alias dimension with the language values English,
French, and Italian and then associate it with the Account
dimension.
To enter a value for this property, you must create an
association between the Account and Alias dimensions.
See “Creating Dimension Associations” on page 45.
Calc Attribute Description of the calculations in the rules file that are done
for this account
160 Working with Financial Management Dimensions

This information displays as part of cell info in data forms
and data grids. It can contain up to 80 characters including
spaces.
Consolidation Account Type One of these values is required:

● ASSET—Store values representing the assets of a
company
● LIABILITY—Store point-in-time balances representing
the liabilities of a company
● REVENUE—Store periodic and year-to-date values that
increase net worth if the value is positive
Note: In Financial Management releases prior to 4.1,
this account type was called Income.
● EXPENSE—Store periodic and year-to-date values that
decrease net worth if the value is positive
● FLOW—Store periodic and year-to-date values
● BALANCE— Store unsigned values that relate to a point
in time
● BALANCERECURRING—Store unsigned values that
relate to a point in time and that re-occur in future
periods
● CURRENCYRATE—Store currency rate information
● GROUPLABEL—Use the account for grouping purposes
● DYNAMIC—Indicates that the account value is
calculated dynamically from the data that you are
viewing
Custom1 Top Member, Custom2 Top Member, Custom3 Which top member in the hierarchy of a Custom dimension
Top Member, Custom4 Top Member is valid for the account
Only the specified member, including all descendants, is
valid for the account.
association between the Account and Custom dimensions.
Default Parent The default parent for the account
Enable Custom1 Aggregation, Enable Custom2 Whether aggregation is enabled for intersections of the
Aggregation, Enable Custom3 Aggregation, Enable Account and Custom dimensions
Custom4 Aggregation
This property is used for special totals, not summing.
Specify Y if the account can aggregate with Custom
dimensions or N if it cannot.
Enable Data Audit Specifies whether the scenario is audited. This property for
an account or a scenario determines what can be audited.
Specify one of the following values:
● Y to automatically audit all accounts. Even accounts
that have Enable Data Audit set to False will be audited.
● O to audit only those accounts that have Enable Data
Audit set to True.
Account 161
● N to disable auditing for all accounts.
ICP Top Member The ICP top member for the account
The specified member, including all descendants, is valid
for the account.
association between the Account and ICP dimensions.
Is Calculated Whether the account is calculated

Only base-level accounts can be calculated. If a base-level
account is calculated, you cannot manually enter values.
Specify Y if the account is to be calculated; otherwise,
specify N.
Is Consolidated Whether the account is consolidated to a parent account.

If the account is not consolidated, it is ignored during
consolidation. Specify Y if the account is to be consolidated
to a parent account and N if the account is not to be
consolidated to a parent account.
Is ICP Specifies whether the account is an intercompany account.

If the account is an intercompany account, you must also
specify a plug account. Specify one of the following values
for this property:
● Y if ICP transactions, including self-ICP transactions, are
enabled for the account
● N if ICP transactions are not enabled for the account
● R if ICP transactions are enabled for the account, but
the account cannot have ICP transactions with itself
Name Specifies the name for the account. A value for this property
is required. It can contain up to 80 characters, including
spaces, but cannot start with a space.
Do not use the following characters in an account name:
● Period ( . )
● Plus sign ( + )
● Minus sign ( - )
● Asterisk ( * )
● Slash mark ( / )
● Number sign ( # )
● Comma ( , )
● Semicolon ( ; )
● At sign ( @ )
● Double quote ( “ )
● Curly brackets ( { } )
● Ampersand ( & )

Number Of Decimal Place Specifies the number of digits to be displayed to the right
of the decimal point for account values. A value for this
property is required. Specify a value from 0 to 9 for this
property.
Plug Account Specifies the name of the account used for identifying
discrepancies in intercompany transactions. The Plug
Account property is required when the Is ICP property for
the account is selected.
association between two Account dimensions.
Security Class Specifies the name of the security class that defines the
users who can access the account data. Security class
names can contain up to 80 characters. Security access
applies only to account data.
association between the Account and Security Class
dimensions.
Submission Group Specifies the submission group. The value can be a number
0 to 99.
The default is blank. A blank value defaults to the value of
1.
If you set the submission group to zero (0), the account is
not included in the review process.
User Defined1, User Defined2, User Defined3 Stores custom information for the account. You can enter a
maximum of 80 characters. The User Defined1, User
Defined2, and User Defined3 functions retrieve the text
stored in this property.
Uses Line Items Specifies whether an account can have line items. Specify
Y if the account uses line items and N if the account does
not use line items.
Caution! If you change this property after line-item detail
is entered, the stored line-item detail may no longer be valid
for the account. The following behaviors occur:
● If the account accepted line items and now it cannot,
the line-item detail stored in the database is no longer
valid. Only the total is displayed.
● If the account did not accept line items and now it can,
there is a total amount but no corresponding line-item
detail information for the account. You can extract the
total and then load it as line-item detail data so that
the total matches the line-item detail information.
XBRL Tags Specifies XBRL tags for the account. You can enter a
maximum of 225 characters.
Account 163
Account Type Behavior
The following table describes how account types behave in the system. For example, ASSET
accounts do not total across periods, while a REVENUE account provides a year to date total.
If you debit an ASSET account, the value that you enter is added to the account. If you credit an
ASSET account, the value that you enter is subtracted from the account. All account types, except
for GROUPLABEL, contain data.
Table 24 Account Type Behavior
Type YTD Total Debit Credit Default Translation
ASSET No Add Sub DefaultRateForBalance Accounts
LIABILITY No Sub Add DefaultRateForBalance Accounts
REVENUE Yes Sub Add DefaultRateForFlow Accounts
EXPENSE Yes Add Sub DefaultRateForFlow Accounts
FLOW Yes Add Sub None
BALANCE No Add Sub None
BALANCE RECURRING No Add Sub None
CURRENCYRATE No N/A N/A N/A
GROUPLABEL N/A N/A N/A N/A
DYNAMIC N/A N/A N/A N/A
The following table indicates how an account type behaves when totaled into a specific type of
parent account. For example, when aggregated, ASSET account values are added into parent
ASSET and EXPENSE accounts and subtracted from parent LIABILITY and REVENUE
accounts.
Note:
The account types across the top of the table are identified by the first one or two letters of the
account type.
Table 25 Account Type Behaviors During Aggregation into Parent Accounts
Parent Account
Account Type A L R E F B BR C G D
ASSET Add Sub Sub Add Add Add Add No No No
LIABILITY Sub Add Add Sub Add Add Add No No No
REVENUE Sub Add Add Sub Add Add Add No No No

Parent Account
Account Type A L R E F B BR C G D
EXPENSE Add Sub Sub Add Add Add Add No No No
FLOW Add Add Add Add Add Add Add No No No
BALANCE Add Add Add Add Add Add Add No No No
BALANCE RECURRING Add Add Add Add Add Add Add No No No
CURRENCYRATE No No No No No No No No No No
GROUPLABEL No No No No No No No No No No
DYNAMIC No No No No No No No No No No
Note:
In this table, No indicates that the account type is not aggregated into the parent account.
Example
The following example illustrates how account types are aggregated into parent accounts:
In this example, Total Assets is an ASSET account and the parent of Fixed Assets (an ASSET
account) and Amortization (a LIABILITY account). When the accounts are aggregated into the
parent account, the Fixed Assets value of 100 is added, the Amortization value of 20 is subtracted,
and the resulting value for Total Assets is 80.
Defining Dynamic Accounts

Dynamic accounts are accounts with values that are dynamically calculated when the data is
requested. The values for dynamic accounts are not stored. The most common type of dynamic
calculation is ratio calculation.
➤ To define a dynamic account and calculation:

1 Set up an account that uses the Dynamic account type.
Only base accounts can be dynamic.
Note:
The following account properties are ignored for dynamic accounts: Is Calculated, Is
Consolidated, Enable Custom1 Aggregation, Enable Custom2 Aggregation, Enable Custom3
Aggregation, Enable Custom4 Aggregation, Uses Line Items.
Account 165
2 In a rules file, create a Sub Dynamic () section.
3 In the rules file, define a calculation.
Custom
Table 26 Custom Properties
Alias Description for the Custom dimension. The description can contain
a maximum of 80 characters.
To use the Alias property, you must create an Alias dimension, define
properties that can be used with it, and associate the Alias dimension
with another dimension. For example, you can create an Alias
dimension with the language values English, French, and Italian. You
could then associate the Alias dimension with the Custom
dimension.
To enter a value for this property, you must create an association
between the Custom and Alias dimensions.
Aggregation Weight Specifies the percentage of the custom member to be aggregated to

the parent, with 1 representing 100%. For example, if you set the
aggregation weight to .5, only 50 percent of the value for the member
is aggregated to the parent.
Default Parent Specifies the default parent for the Custom dimension member.
Is Calculated Specifies whether the base-level Custom account is calculated. If a

base-level Custom account is calculated, you cannot manually enter
values. Specify Y if the Custom account is to be calculated and N if
the Custom account is not to be calculated.
Name Specifies the name for the custom member. A value for this property
is required. The name can contain up to 80 characters, including
Note: The name of a Custom1 dimension member cannot duplicate
the name of a consolidation method.
Do not use the following characters in the custom member name:
● Period ( . )
● Plus sign ( + )
● Asterisk ( * )
● Comma ( , )
● Semicolon ( ; )
● At sign ( @ )

● Ampersand ( & )
Security Class Specifies the name of the security class that defines the users who
can access the Custom dimension data. Security class names can
contain up to 80 characters. Security access applies only to data.
between the Custom and Security Class dimensions.
Submission Group Specifies the submission group. The value can be a number 0 to 99.
The default is blank. A blank value defaults to the value of 1.
If you set the submission group to zero (0), the account is not
included in the review process.
Switch Sign For Flow Specifies sign change (Debit or Credit) for FLOW accounts that use
the following rules:
● ASSET to LIABILITY
● LIABILITY to ASSET
● EXPENSE to REVENUE
● REVENUE to EXPENSE
● BALANCE to FLOW
● FLOW to BALANCE
Specify Y if the sign for the account is switched and N if the sign for
the account is not switched.
Switch Type For Flow Specifies the account type change for FLOW accounts that use the
following rules:
● ASSET to EXPENSE
● EXPENSE to ASSET
● LIABILITY to REVENUE
● REVENUE to LIABILITY
● BALANCE to FLOW
● FLOW to BALANCE
Specify Y if the account type for the account is switched and N if the
account type for the account is not switched.
User Defined1, User Defined2, User Defined3 Stores custom information for the custom dimension member. You
can enter a maximum of 80 characters. The User Defined1, User
Defined2, and User Defined3 functions retrieve the text stored in this
property.
Custom 167
Entity
Table 27 Entity Properties
Alias Description for the entity. The description can contain a maximum of
80 characters.
could then associate the Alias dimension with the Entity dimension.
between the Entity and Alias dimensions.
Allow Adjustments Specifies whether journal postings are permitted for this entity.
Specify Y if journal postings are permitted for the entity and N if
journal postings are not permitted for the entity.
Allow Adjustments From Children Specifies whether journal postings from children are permitted for
the parent entity. Specify Y if journal postings from children are
permitted and N if journal postings from children are not permitted.
Currency Specifies the default currency for the entity. A value for this property
is required.
between the Entity and Currency dimensions.
Default Parent Specifies the default parent for the entity.
Holding Company Specifies the holding company for the entity. Can be the name of an
entity or <blank>.
between two Entity dimensions.
Is ICP Specifies whether the entity is an intercompany entity. Specify Y if

the entity is an intercompany entity and N if the entity is not an
intercompany entity. If the entity is an intercompany entity, it is
displayed in the POV in the ICP dimension under [ICP Entities].
Name Specifies the name for the entity. A value for this property is required.
The name can contain up to 80 characters including spaces but
cannot start with a space.
Do not use the following characters in the entity name:
● Period ( . )
● Plus sign ( + )
● Asterisk ( * )

● Comma ( , )
● Semicolon ( ; )
● At sign ( @ )
● Ampersand ( & )
Note: You cannot use ALL as the name of an entity.
Security As Partner Specifies the name of a valid security class for the ICP entity. This
property enables you to secure the entity in an ICP dimension.
between the Entity and Security Class dimensions.
Security Class Specifies the name of a valid security class of users who can access
the data of the entity. Security class names can contain up to 80
characters.
between the Entity and Security Class dimensions.
User Defined1, User Defined2, User Defined3 Stores custom information for the entity. You can enter a maximum
of 80 characters. The User Defined1, User Defined2, and User
Defined3 functions retrieve the text stored in this property.
Scenario
Table 28 Scenario Dimension Properties
Alias Description for the scenario. The description can contain a maximum
of 80 characters.
could then associate the Alias dimension with the Scenario
dimension.
between the Scenario and Alias dimensions.
Consolidate YTD Specifies the view for consolidation. A value for this property is
required. Specify Y for YTD or N for periodic.
Default Frequency Specifies the types of periods for which data input is valid for the
scenario. A value for this property is required.
Scenario 169
For example, a value of Monthly indicates that you can extract input
data only in month-based periods, not in quarter-based or year-
based periods.
between the Scenario and View dimensions.
Default Parent Specifies the default parent for the scenario.
Default View Specifies the view to use when <Scenario View> is selected in the
point-of-view bar. A value for this property is required. Specify YTD
or Periodic.
If you change the default view for a scenario and line-item detail has
been entered, you should first extract the line-item detail and save
it. Then delete the line-item detail from the scenario before changing
the view. You must change the extracted line-item detail to match
the new default view before loading it.
Default Frequency For IC Transactions Specifies the default frequency for intercompany transactions. This
property must be a valid frequency and can contain a maximum of
20 characters. The default for this property is <blank>.
between the Scenario and View dimensions.
Enable Data Audit Specifies whether the scenario is audited. This property for an
account or a scenario determines what can be audited. Specify one
of the following values:
● Y to automatically audit all accounts. Even accounts that have
Enable Data Audit set to False will be audited.
● O to audit only those accounts that have Enable Data Audit set
to True.
● N to disable auditing for all accounts.
Enable Process Management Specifies whether Process Management functionality is enabled.

● Y to enable the Process Management
● N to disable the Process Management option
● A to enable Process Management and e-mail alerting.
Maximum Review Level Specifies the maximum Process Management review level for the
scenario. Specify a review level from 1 to 10. A value for this property
is required.
Name Specifies the name for the scenario. A value for this property is
required. The name can contain up to 80 characters, including
Do not use the following characters in the scenario name:
● Period ( . )
● Plus sign ( + )
● Asterisk ( * )

● Comma ( , )
● Semicolon ( ; )
● At sign ( @ )
● Ampersand ( & )
Security Class Specifies the name of a valid security class that defines users who
can access the data for the scenario. Security class names can
contain up to 80 characters. For example, a user with None access
rights to a scenario can open journal periods for the scenario.
between the Scenario and Security Class dimensions.
User Defined1, User Defined2, User Defined3 Stores custom information for the scenario. You can enter a
maximum of 80 characters. The User Defined1, User Defined2, and
User Defined3 functions retrieve the text stored in this property.
Uses Line Items Specifies whether the scenario can have line items. Specify Y if the
scenario can accept line items and N if the scenario cannot accept
line items.
Note: If you change this property after line-item detail is entered,
the stored line item detail may no longer be valid for the scenario.
The following behaviors occur:
● If the scenario accepted line items and now it cannot, the line-
item detail stored in the database is no longer valid. Only the
total is displayed.
● If the scenario did not accept line items and now it can, there is
a total amount but no corresponding line-item detail information
for the scenario. You can extract the total and then load it as line-
item detail data so that the total matches the line-item detail
information.
Zero View For Adjustments Specifies how to interpret missing, adjusted data values for the
period. A value for this property is required. Specify YTD or Periodic.
Zero View For Non-adjustments Specifies how to interpret missing, unadjusted data values for the
period. A value for this property is required. Specify YTD or Periodic.
Application
Application properties apply to an entire Financial Management application. Application
properties determine the following information for the application:
● Is the organization dynamic, using organization by period?
● Which dimensions are secured?
Application 171
● What default translation rates are used?
● What is the ICP weight?
● Are consolidation rules applied?
● What is the default currency?
Table 29 Application Properties
Consolidation Rules Specifies if consolidation rules are supported for the

application. Specify one of the following values:
● Y to use the rules written in the Consolidate() routine in
a user-defined rule.
● R to derive the proportional value in the Value
dimension. Note that the proportional data is not stored.
● N to use the default consolidation and eliminations.
The default value is N.
Default Currency Specifies the default currency for the application.

A value for this property is required.
Default Rate For Balance Accounts Specifies the account that contains the translation rate to
use for ASSET or LIABILITY accounts.
Default Rate For Flow Accounts Specifies the account that contains the translation rate to
use for REVENUE or EXPENSE accounts.
Default Value For Active Specifies if entities in the application are active by default
or inactive by default. Inactive entities are not consolidated
to their parent
Specify 0 for inactive or 1 for active.
Enable Metadata Security Filtering Specifies if users of an application see all dimension
members or only the members to which they have access.
The system can filter the following dimensions:
● Scenario
● Entity
● Intercompany Partner (ICP)
● Account
● Custom1, Custom2, Custom3, Custom4
Specify Y to display only the dimension members to which
the user has access or N to display all dimension members
in the application.
The default value is N.

ICP Entities Aggregation Weight Specifies the percentage of intercompany partner entity [ICP
Entities] amounts that aggregate to the [ICP Top] member
of the Value dimension.
The percentage is scaled to hundreds, with 1.0 equalling
100 percent.
Specifies the maximum number of characters that can be

used for cell text.
Maximum Cell Text Size
Valid values are -1 for no limit or a positive number up to
2,147,483,647.
The default value is 1900.
Specifies the maximum number of bytes for the size of

document attachments.
Maximum Document Attachment Size
2,147,483,647.
Specifies the maximum number of document attachments

per user.
Maximum Number of Document Attachments
2,147,483,647.
Node Security Specifies the type of security access for nodes.

Valid values are Parent or Entity.
Specify Entity to check node data based on security access
for the entity and Parent to check node data based on
security access for the parent.
Org By Period Application Specifies if new consolidation structures can coexist with
past consolidation structures in the application.
● Y to allow new and old organizational structures in the
application
● N to allow only active organizational structures
Use PVA For Balance Accounts Specifies the default translation method for BALANCE
accounts.
● Y to use the periodic value (PVA) translation method
● N to use the value at exchange rate (VAL) translation
method
Use PVA For Flow Accounts Specifies the default translation method for FLOW accounts.
● Y to use the periodic value (PVA) translation method
Application 173
● N to use the value at exchange rate (VAL) translation
method
Security For Accounts Specifies if accounts in the application are protected by

security.
Specify Y for security on accounts in the application and N
for no security on accounts in the application.
Security For Custom1, Security For Custom2, Security Specifies whether custom dimensions in the application are
For Custom3, Security For Custom4 protected by security. Specify Y for security on custom
dimensions in the application and N for no security on
custom dimensions in the application.
Security For Entities Specifies whether entities in the application are protected
by security. Specify Y for security on entities in the
application and N for no security on entities in the
application.
Security For ICP Specifies whether ICP members in the application are
protected by security. Specify Y for security on ICP members
in the application and N for no security on ICP members in
the application.
Security For Scenarios Specifies whether scenarios in the application are protected
by security. Specify Y for security on scenarios in the
application and N for no security on scenarios in the
application.
Validation Account Specifies the name of the account to use for validation. The
account used for validation must be an existing account and
must have a valid intersection with [ICPTop] in the Custom
dimensions.
Use Submission Phase Specifies whether phased submissions in process

management are used in the application.
Valid values are Y or N. Default is N.
Support Submission Phase for Account Specifies whether phased submissions in process
management are supported for accounts in the application.
Support Submission Phase for Custom1, Support Specifies whether phased submissions in process
Submission Phase for Custom2, Support Submission management are supported for the Custom members in the
Phase for Custom3, Support Submission Phase for application.
Custom4
Support Submission Phase for ICP Specifies whether phased submissions in process
management are supported for ICP members in the
application.
Validation Account 2 to 9 Validation accounts are used to ensure that the value equals
zero before a process unit can be promoted to the next
review level.

For example, Validation Account3 requires a valid account
for Submission Phase4.
FDM Application Name Name of the FDM application.
Organization by Period
The organization by period functionality enables the most recent consolidation structure to
coexist with past structures in the same application.
Organizational structures can change for many reasons, including acquisitions, disposals,
mergers, and reorganizations. To support organizational changes, Financial Management uses
a system account, Active, to reflect the active or inactive consolidation status of a child into its
parent. The Active account acts as a filter of the entity hierarchy. The Active account is an
intercompany account that stores data at the parent level and uses the ICP dimension to store
information about children.
For an ICP member that corresponds to a child of a parent, the Active account indicates to the
system whether the child should be considered as an active consolidation member for the current
year, scenario, and time period. Children that correspond to ICP members for which the Active
account equals 0 are considered to be inactive children and are not consolidated. Children that
correspond to ICP members for which the Active account equals 1 are considered to be active
children and are consolidated. Active account values can be viewed or changed. Changes to active
child data affect the parent, while changes to inactive child data do not affect the parent.
The Default Value For Active property controls the status of children for which the Active
account is blank. So, every parent-child intersection does not have to be flagged as active or
inactive. By default, every child is active in relation to its parent unless otherwise specified.
Consolidation Method
Table 30 Consolidation Method Properties
Alias Description for the consolidation method. The description can contain a maximum of
80 characters.
To use the Alias property, you must create an Alias dimension, define properties that
can be used with it, and associate the Alias dimension with another dimension. For
example, you can create an Alias dimension with the language values English, French,
and Italian. You could then associate the Alias dimension with the Account dimension.
To enter a value for this property, you must create an association between the
Consolidation Method and Alias dimensions.
Alias Description for the account. The description can contain a maximum of 80 characters.
Organization by Period 175

To use the Alias property, you must create an Alias dimension, define properties that
can be used with it, and associate the Alias dimension with another dimension. For
example, you can create an Alias dimension with the language values English, French,
and Italian. You could then associate the Alias dimension with the Account dimension.
To enter a value for this property, you must create an association between the Account
and Alias dimensions.
Name Specifies the name for the consolidation method.

The name can contain up to 80 characters, including spaces.
You cannot use the following characters in the name:
● Period ( . )
● Plus sign ( + )
● Asterisk ( * )
● Comma ( , )
● Semicolon ( ; )
● At sign ( @ )
● Ampersand ( & )
Control Specifies the threshold that corresponds to the type of control to be used by the
calculation routine. Specify one of the following values for this property:
● Blank
● No
● Limited
● Full
Is Holding Method Specifies if the consolidation method is used for the holding company.
Specify Y to use the method for the holding company and N to use a different method
for the holding company.
Percent Consol Specifies the consolidation percentage applied by the ownership calculation routine.
● POWN
● POWNMIN
● PERCENTAGE
Percent Consol Specifies the consolidation percentage applied by the ownership calculation routine.

● POWN
● POWNMIN
● PERCENTAGE
Note: If you select PERCENTAGE as the value, you must enter a value for the
Percent Consol Value property.
Percent Consol Value Specifies the consolidation percentage value applied by the ownership calculation
routine.
Note: This property is used by system only if PERCENTAGE is the value for the Percent
Consol property.
Specify a value between 1 and 100.
To Percent Control Specifies the upper boundary of the range for percent control. Used for the ownership
calculation routine.
Specify a value between 0 and 100.
Note: One of the method records must have a value of 100.
To Percent Control Compare Specifies if the upper boundary of the range of percent control is included in the range.
Used for the ownership calculation routine and the To Percent Control property. This
property is optional if the Used By Calc Routine property is N.
Specify < or <= for this property.
Used By Calc Routine Specifies if the method is used for the automatic ownership calculation routine.
Specify Y to use the method for ownership calculations and N not to use the method
for ownership calculations.
Using Consolidation Methods

Consolidation methods are used during the consolidation and calculate ownership processes.
When you define consolidation methods in the metadata, the system automatically generates
the [ConsolMethod] system list for the Custom1 dimension. The system list consists of all
methods defined in the consolidation methods section of the metadata.
There are two ways to assign the consolidation method to an entity for use during consolidation.
The method can be assigned manually through data load or data entry. The method can also be
assigned by the calculate ownership routine, which is based on the ultimate percent control
assigned to the entity.
Assigning Consolidation Methods Manually

To enter consolidation method information manually, you can create a data grid with the
following information:
POV: Scenario, Year, Period, View, Entity, Value, Account, C2, C3, C4
Scenario: Applicable scenario
Consolidation Method 177

Year: Applicable year
Period: Applicable period
Entity: A parent entity
Value: [None]
Account: [Method], a system generated account called Method
C2: [None]
C3: [None]
C4: [None]
Row: ICP entities (For parents, user can use the system list [ICP Entities] or the user-defined
list of selected ICP entities.)
Column: Custom1 (The user should use the system-generated list [ConsolMethods].)
Method assignment information is stored in the account method of the data file of the parent
entity. For each child of a parent, the system stores the consolidation method assignment in the
ICP dimension. The assigned method is used when the children are consolidated to the parent.
For an intersection of the grid, use 1 to indicate the method assignment to the ICP entity. For
example, if a parent group has two children, A and B, and you assign the Global method to A
and the Equity method to B, enter 1 in the intersection for the Global method and entity A and
1 in the intersection for the Equity method and entity B.
Currency
Table 31 Currency Properties
Alias Description for the currency. The description can contain a maximum of 80 characters.
To use the Alias property, you must create an Alias dimension, define properties that can be
used with it, and associate the Alias dimension with another dimension. For example, you can
create an Alias dimension with the language values English, French, and Italian. You could
then associate the Alias dimension with the Currency dimension.
To enter a value for this property, you must create an association between the Currency and
Alias dimensions.
Display In ICT Specifies if currencies display in the drop-down list in the intercompany transactions module.
Specify Y to display currencies and N to not display currencies.
Name Specifies the name for the currency.

The name can contain up to 80 characters, including spaces.
Do not use the following characters in the currency name:

● Period ( . )
● Plus sign ( + )
● Asterisk ( * )
● Comma ( , )
● Semicolon ( ; )
● At sign ( @ )
● Ampersand ( & )
Scale Specifies the unit in which amounts are displayed and stored for the currency by identifying
where the decimal point is placed.
Determines how the exchange rate must be entered. Specify one of the following values for
this property:
● Blank = None
● 0 = Units
● 1 = Tens
● 2 = Hundreds
● 3 = Thousands
● 4 = Ten thousands
● 5 = Hundred thousands
● 6 = Millions
● 7 = Ten millions
● 8 = Hundred millions
● 9 = Billions
Translation Operator Specifies the conversion calculation for intercompany transactions.

The default is blank.
● D to calculate the local currency by dividing the transaction currency by the rate
● M to calculate the local currency by multiplying the transaction currency by the rate
● <blank> to default the value to D
The system member list [Currencies] is available for the Custom1 and Custom2 dimensions.
Currencies that you add to the application are added to the [Currencies] member list. The
[Currencies] list enables the entry of currency translation rates for pairs of currencies and
provides a way of filtering out non-currency members.
Currency 179
System-Generated Accounts
When you create an application, system accounts for consolidation and ownership are
automatically created for the application.
Note:
You can change only the description, security class, and decimal location for system accounts.
All other properties for system accounts are predefined and cannot be modified.
Consolidation Accounts
The following system accounts are required for each parent in the Entity dimension and are used
in the consolidation process.
Note:
All system accounts that are used for consolidation, except for the Active account, are BALANCE
accounts. The Active account is a BALANCERECURRING account.
Table 32 System Accounts for Consolidation
Account Value Description
Active Consolidation status of a child into its parent. Yes if the child is consolidated into its
parent. No if the child is not consolidated into its parent.
[PCON] Percent consolidation. The percentage of the value of an entity that consolidates to the
parent of the entity. Positive or negative numbers between -100 and 100, including 0.
Default value is 100.
Note: For subsequent periods, derived as 0. Therefore, you must enter the percentage
in all subsequent periods.
[POWN] Percent ownership based on the shares of the entity that are owned by other entities.
A positive number between 0 and 100. Default value is 100.
[DOWN] Percent of direct ownership. A positive number between 0 and 100. Default value is
100.
[PCTRL] Percent control based on the voting shares of the entity that are owned by other entities.
A positive number between 0 and 100. Default value is 100.
Method Consolidation method assigned to the entity. <None> or a selection from the list of
available methods.
Consol1, Consol2, Consol3 Consolidation methods. A number between 0 and 255.
Ownership Accounts
The following system accounts are used for ownership calculations.

Note:
All system accounts that are used for ownership calculations are BALANCE accounts.
Table 33 System Accounts for Ownership
Account Value Description
SharesOwned Total number of shares owned. Positive number or 0. Default is 0.

Note: Total shares owned must be less than or equal to the total shares outstanding.
VotingOwned Number of voting shares owned. Positive number or 0. Default value is 0.

Note: Total voting shares owned must be less than or equal to the total voting shares
outstanding.
SharesOutstanding Total number of shares outstanding or the percentage of shares outstanding. Positive number
or 0. Default value is 0.
Note: Enter the number of shares outstanding, or enter shares outstanding as a percentage.
Enter 100 for percentage.
VotingOutstanding Number of voting shares outstanding. A positive number or 0. Default value is 0.

Note: Enter the number of voting shares outstanding, or enter voting shares outstanding as a
percentage. Enter 100 for percentage.
Shares%Owned Calculated by system.
Voting%Owned Calculated by system.
Setting Up Intercompany Partners

Intercompany transactions are managed across the Intercompany Partner (ICP) dimension. The
ICP dimension represents a container for all intercompany balances that exist for an account.
ICP is a reserved dimension used in combination with the Account dimension and custom
dimensions to track and eliminate intercompany transaction details.
To set up an application for intercompany transactions, you must perform the following actions:
● Indicate the accounts that perform intercompany transactions and indicate a plug account
for each intercompany account (Is ICP and Plug Account properties in account metadata)
● Indicate the entities that perform intercompany transactions (Is ICP property in entity
metadata)
When you create intercompany transactions, each group must have at least one intercompany
account and one plug account. You designate an account as intercompany by selecting the Is
ICP property for the account. When an account is designated as intercompany and intercompany
transactions are entered, eliminating or reversing entries are generated in the [Elimination] value
dimension member through the consolidation process.
A plug account is an account that, when eliminations are completed, stores the difference
between two intercompany accounts. A plug account can be set up as an ICP account. For a plug
Setting Up Intercompany Partners 181

account to be detailed by ICP, set the Is ICP property to Y or R so that the system writes
eliminations to the corresponding ICP member. If you do not want a plug account to be detailed
by ICP, set the Is ICP property to N so that the system writes eliminations to [ICP None]. During
consolidation, transactions between valid intercompany entities are eliminated.
Table 34 System-Generated ICP Elements
ICP Element Value Description
[ICP Top] Specifies the top intercompany member
[ICP None] Specifies that no intercompany member is used
[ICP Entities] Specifies the entities that are designated for intercompany transactions
Table 35 ICP Properties
Alias Description for the ICP. The description can contain a maximum of 80 characters.
To use the Alias property, you must create an Alias dimension, define properties that can be
used with it, and associate the Alias dimension with another dimension. For example, you can
create an Alias dimension with the language values English, French, and Italian. You could then
associate the Alias dimension with the ICP dimension.
To enter a value for this property, you must create an association between the ICP and Alias
dimensions.
Default Parent The default parent for the ICP.
Name Specifies the name for the ICP. A value for this property is required. The name must be unique
and can contain up to 20 characters, including spaces.
Do not use the following characters in the currency name:
● Period ( . )
● Plus sign ( + )
● Asterisk ( * )
● Comma ( , )
● Semicolon ( ; )
● At sign ( @ )
● Ampersand ( & )
Security Class Specifies the name of the security class that defines the users who can access the ICP data.
Security class names can contain up to 80 characters. Security access applies only to account
data.

To enter a value for this property, you must create an association between the ICP and Security
Class dimensions.
Submission Group Specifies the submission group. The value can be a number 0 to 99.
The default is blank. A blank value defaults to the value of 1.
If you set the submission group to zero (0), the account is not included in the review process.
Editing System-Generated Value Members

When you create an application, Value members are automatically created for the application.
Note:
You can modify only the description for Value members. All other properties are predefined
and cannot be modified.
After you load metadata,Financial Management automatically creates three Value dimension
members for each currency in your application: CurrencyName, CurrencyName Adjs, and
CurrencyName Total, where CurrencyName is the currency label. For example, for a currency of
USD, Financial Management creates the following Value dimension members: USD, USD Adjs,
and USD Total.
Metadata Filtering Based on Security

When you filter metadata based on security, users see only the elements of the Scenario, Entity,
ICP, Account, and Custom1 through Custom4 dimensions to which they have access. You set
up metadata filtering at the application level by setting the EnableMetadataSecurityFiltering
property to Y. For elements a user can view in a hierarchy, assign a security class and give the
user metadata access to the security class.
Users have implied access to the parents and ancestors of members to which they have access.
With implied access, users see ancestors and parents in a hierarchical tree structure but cannot
access them. For example, in the following tree structure, the user has access to only Connecticut
even though the parents (UnitedStates and Imbler) and the ancestors (Management and
Regional) are displayed in the tree.
Metadata Filtering Based on Security 183

Metadata Referential Integrity
To prevent a referential integrity problem from occurring in the application, Financial
Management verifies that metadata changes are valid to the application in its current state before
accepting the changes.
When you load metadata, the system compares the metadata load file with the metadata elements
in the application. All changes are recorded, and some changes are checked against existing data.
Modifications that cause referential integrity problems are not allowed.
Note:
When you load metadata, make sure that the Check Integrity option is selected.
Metadata Referential Integrity Checks

The following table provides information about specific changes in metadata properties that
require the system to check existing data in regard to the metadata file that you are loading. Only
metadata properties that have an effect on referential integrity are listed in the table.
Table 36 Metadata Referential Integrity Checks
Dimension Metadata Property Change Action
Account Is Calculated (from N to Y) Checks to see if a journal or template exists for the
account, and, if found, prevents the metadata from
loading.
Is ICP (from Y to R) Checks to see if a journal or template exists for the

account and ICP=<Entity>, and, if found, prevents
the metadata from loading.
Is ICP (from Y to N or from R to N) Checks to see if a journal or template exists for the
account and ICP <> [ICP None] (because the account
is not an intercompany account and ICP members
other than [ICP None] is invalid), and, if found,
prevents the metadata from loading.
Uses Line Items (from Y to N or from N to Y) Checks to see if regular data exists for the scenario
and account, and, if found, prevents the metadata
from loading.
Note: From Y to N, the system does not allow access
to line-item detail.
Custom Is Calculated (from N to Y) Checks to see if a journal or template exists for this
custom dimension, and, if found, prevents the
metadata from loading.
Entity Currency Checks to see if a journal exists for <Entity Currency

Adjs> or <Parent Currency Adjs>, and, if found,
Allow Adjustments (from Y to N) For Allow Adjustments, checks to see if a journal with
<Entity Curr Adjs> or <Parent Currency Adjs> exists

Allow Adjustments From Children (from Y to N) for the entity, and, if found, prevents the metadata
from loading.
For Allow Adjustments From Children, checks to see
if a journal with [Parent Adjs] or [Contribution Adjs]
exists for the entity, and, if found, prevents the
metadata from loading.
Is ICP (from Y to N) Checks to see if a journal in which the entity is used

in the ICP dimension exists, and, if found, prevents
the metadata from loading.
Scenario Zero View For Adjustments Checks to see if a journal exists for the scenario, and,
if found, prevents the metadata from loading.
Uses Line Items Checks to see if regular data exists for an account
with this property turned on for the specified
scenario, and, if found, prevents the metadata from
loading.
Application Default Value For Active Checks to see if a journal or recurring template exists
for [Parent Adjs] or [Contribution Adjs], and, if found,
The system also checks for invalid points of view between the load file and the metadata in the
application. If a dimension member is not in the load file but exists in a journal in the application,
the metadata load is prevented.
Metadata Log File Referential Integrity Errors

In the metadata log file, referential integrity errors are displayed under the following section:
Metadata referential integrity check started at
Each line in the referential integrity check section refers to a metadata integrity error in the load
file. Errors found during the integrity check are displayed in the following format:
Journals::SINGLECA1 Scenario::Actual Year::1999
Value::[Contribution Adjs]
Period::January has 1 occurrences of
Changed::[SCENARIO::Actual::ZeroViewForAdj: Periodic -> YTD]
This example shows that the metadata integrity error occurs in the SINGLECA1 journal with
the following point of view: Scenario Actual, Year 1999, Value [Contribution Adjs], Period
January. The error is that the ZeroViewForAdj property for the Actual scenario was changed
from Periodic to YTD. This change is not allowed because a journal exists for the Actual scenario.
Metadata Referential Integrity 185

Working with Planning
B Dimensions
In This Appendix
Account ........................................................................................................................... 192
Currency .......................................................................................................................... 195
Entity .............................................................................................................................. 196
Period ............................................................................................................................. 197
Scenario .......................................................................................................................... 198
Version ............................................................................................................................ 200
Year................................................................................................................................ 201
Considerations for Working with Planning Dimensions ....................................................................... 202
Custom Dimensions ............................................................................................................. 203
Planning Attributes............................................................................................................... 203
Considerations for Excluding and Deleting Planning Members .............................................................. 204
Considerations for Deleting Planning Application Views ..................................................................... 204
Working with Shared Members ................................................................................................. 205
Naming Restrictions for Applications........................................................................................... 205
Naming Restrictions for Dimensions, Members, and Aliases ................................................................ 206
Following are the properties for the Planning category by dimension.

For properties that apply to an entire Planning application, see Table 37, “Application
Properties,” on page 188.
Properties that are common to several dimensions are listed in Table 38, “Common Planning
Properties,” on page 189. Properties for individual dimensions included with Planning are
described in:
● “Account” on page 192
● “Currency” on page 195
● “Entity” on page 196
● “Period” on page 197
● “Scenario” on page 198
● “Version” on page 200
● “Year” on page 201
187
Important information for working with Planning dimensions is included in “Considerations
for Working with Planning Dimensions” on page 202, “Considerations for Excluding and
Deleting Planning Members” on page 204, and “Naming Restrictions for Dimensions,
Members, and Aliases” on page 206.
Table 37 Application Properties
Plan Name Specifies the plan name. Plan type names can contain up to eight characters. Although you
can enter more than eight bytes (combination of single-byte and double-byte characters), an
error message will display indicating that the name is too long when you create the Analytic
Services database. You can have up to five plan types for Planning Application Views. Plan1,
Plan2, and Plan3 are for Planning. The Workforce and Capex plan types pertain to the separately
licensed modules, Capital Expense Planning and Workforce Planning.
Valid For Plan Specifies up to three plan types in the application. An Analytic Services database is created for
each plan type. As you create accounts, entities, and other application elements, you associate
them with plan types, so the database for each plan type contains only the application
dimensions, members, and data values relevant to that plan type. This allows for optimal
application design, size, and performance. You must set up at least one plan type. Do not
change the number of plan types or the plan type names after you create the application. (The
number of plan types depends on the needs of your organization.) For example, if the sales
department creates a yearly revenue plan and the finance department creates a P&L plan. You
could define two plan types, Revenue and P&L, and share data between the plan types. The
Revenue plan may include sales detail accounts that rollup into a Total Product Sales account.
The P&L plan can include Total Product Sales, but omit sales detail accounts. Thus, the database
for your P&L plan is smaller and more efficient.
Deselecting a plan type for dimension members after data is entered into applications may
result in loss of data when applications are refreshed. For account members, data is lost if the
deselected plan type is the source plan type.
Plan types are inherited from parents to child members. If you select a different plan type for
a parent member, all descendent members in that hierarchy are also updated. To set a different
plan type for certain members, select them individually and set a different property.
Default Currency Specifies the default currency for application entities.
Multiple Currencies Indicates that the application supports multiple currencies. Once specified, you cannot change
it. Two additional dimensions are created, Currency and HSP_Rates. (With multiple currencies,
performance settings display when you right-click the Application View in the Dimension Library.
Here, the HSP_Rates dimension is visible for managing the application performance. Otherwise,
it is not displayed within the Application View.) Multiple currency support, also known as
currency overrides, is available for level 0 members, regardless of base currency.
Base Time Period Defines the bottom-level time period in the application to set how calendars rollup:
● 12 Months: Four quarters created per year; months rollup into parent quarters and quarters
into years.
● Quarters: Quarters rollup into years.
● Custom: A custom time period, such as weeks or days.
Weeks Distribution Specifies the monthly distribution pattern, based on the number of fiscal weeks in a month
(Even, 445, 454, or 544). This sets how data entered into a summary time period is spread
among the base time periods. Users can enter data into summary time periods, such as years
188 Working with Planning Dimensions

or quarters, and the value is distributed over the base time periods within the summary time
period.
If you select a weekly distribution pattern other than Even, Planning treats quarterly values as
if they were divided into 13 weeks and distributes the weeks according to the selected pattern.
For example, if you select 5-4-4, Planning treats the first month in a quarter as if it has five
weeks, and the last two months in the quarter as if they have four weeks.
The options for the weekly distribution pattern are available only if you select the base time
period option 12 Months.
Start Year Sets the fiscal start year to define the starting fiscal year for the application. Do not change this
after creating the application. Before setting this option, consider how much historical data your
organization needs in the application.
Note: The Start Year must be entered in the FYXX format.
Start Month Specifies the month in which the fiscal year will start for the application.
Default Alias Table Planning and Analytic Services require a default alias table named Default in each application.
If you do not create other alias tables, all aliases are stored in the Default table. You cannot
delete the Default table. You can create up to nine new alias tables for storing aliases in Planning
and Analytic Services applications.
To create alias tables in BPM Architect, create a dimension of type Alias in the Master View,
and create a child member named Default. This member is the default alias table required by
Planning and Analytic Services. You can create additional alias tables by adding child members
to the Alias dimension. Use the instructions in “Creating Dimension Associations” to associate
the Alias dimension to the main or base dimension such as Account, Entity, or a user-defined
dimension. Drag the Alias dimension to the Application View. (You must also drag main
dimensions that have associations with the Alias dimension.) Right-click the base dimension,
select Dimension Associations, and activate the association with the alias dimension. You can
then set the alias for individual members of the base dimension by selecting a member and
double-clicking the Alias field in the Property Grid. You can create or modify aliases of the
specific base member in any alias table. See “Setting up Alias Dimensions” on page 42.
These properties are common to several Planning dimensions. They are described once in this
table instead of in each dimension property table. For example, UDA and Member Formula are
common to all dimensions, so detailed descriptions for these properties appear only in this table.
(Smart Lists are described previously in this guide.)
Table 38 Common Planning Properties
Valid for Plan Specifies the plan types:

● Valid For Plan1
● Valid for Plan2
● Valid For Plan3
● Valid For Workforce
● Valid For CapEx
The Workforce and Capex plan types pertain to the separately licensed modules, Capital Expense
Planning and Workforce Planning.
189
Assign plan types for entity and account members to set plan type access for members. Not
assigning a plan type to a member prevents its children from accessing that plan type. For example,
Total Sales is valid for Revenue and P&L, but Fixed Assets is valid only for Balance Sheet. For
user-defined dimensions, deselecting makes all dimension members invalid for the deselected
plan type.
When moving members, if the new parent is valid for different plan types, members remain valid
only for the plan types they have in common with the new parent. If the new parent of an account
member has another source plan type, the source plan type is set to the first new valid plan type
of that member.
Typically entity members prepare different plans. When defining entity members, specify plan
types for which they are valid. Because data forms are associated with plan types, you can control
which entity members can enter data for each plan type. For example, if Eastern US is a cost
center, it can be valid for the P&L plan type, but not for the Revenue plan type; on data forms for
the Revenue plan type, Eastern US is not selectable.
Data Storage Optimizes performance and disk usage:

● Store: Stores data values of members. Do not set a parent member to Store if its children are
set to Dynamic Calc; when users save and refresh data forms, the new total for the parent is
not calculated.
● Dynamic Calc and Store: Calculates the data values of the member, then stores the values.
In most cases, you can optimize calculations and lower disk usage by using Dynamic Calc
instead of Dynamic Calc and Store when calculating members of sparse dimensions with
complex formulas or members that users retrieve frequently.
● Dynamic Calc: Use for members of dense dimensions or for data values that are being
accessed concurrently by many users. In most cases, use for calculating members of sparse
dimensions. Do not use for base-level members for which users enter data. Data values are
not saved for Dynamic Calc members. Do not use for a parent member if data is entered for
the member in target versions. Parent members set to Dynamic Calc are read-only in target
versions. The Analytic Services limit is 100 children under a dynamic calc parent.
Changing a member's storage to Dynamic Calc may result in loss of data, depending on how
the data was derived. You may need to update outlines, calculations, or both to get the
dynamically calculated value.
● Never Share: Use for parent members that have only one child member aggregating to that
parent, to apply security to the child member.
● Label Only: Use for virtual members to aid navigation or minimize database space, not for
data. Members can display values. In multi-currency applications, you cannot apply label-
only members of these dimensions: Entity, Versions, Currencies, and user-defined custom
dimensions, which must use Never Share. Do not use for level 0 members. Data cannot be
saved in the first child member; for data forms, do not use a label-only parent following its
first child member.
● Share Data: Allow members in the same dimension to share data values, enabling alternate
rollup structures in the application. For shared members, you must set Data Storage to
ShareData. Otherwise, the shared member is not added when the Application View is deployed
to Planning. See “Working with Shared Members” on page 205.
Currency Defines the currency name, for example USD (for US dollars).
This setting does not apply to aggregate storage outlines.
UDA Defines any UDA (user-defined attribute) associated with the member. To enter multiple UDAs for
a member, you must place a semicolon (;) between the UDA members. See the Hyperion System
9 BI+ Analytic Services Database Administrator's Guide and online help.

Member Formula A member formula, which can combine operators, calculation functions, dimension and member
names, and numeric constants. See the Hyperion System 9 BI+ Analytic Services Database
Administrator's Guideand online help.
Alias Defines the alias table to store the alias name, or enter a name for the member. Follow the proper
naming rules.
Aggregation Defines Aggregation For Plan1, Plan2, Plan3, Workforce, or Capex to set member aggregation
properties. This determines how children rollup into parents during consolidation:
● + (addition)
● - (subtraction)
● * (multiplication)
● / (division)
● % (percent)
● ~ (ignore during consolidation)
● Never (do not aggregate, regardless of hierarchy)
Data Type Determines how values are stored and displayed:

● Currency
● Non-Currency
● Percentage
● Smart List
● Date
● Text
● Unspecified
For accounts, if Data Type is set to any value except Currency, you must set Exchange Rate Type
to None.
Attribute Values Defines attribute values to associate with the selected member. For Planning Application Views,
attribute values can only be assigned to a single level within a dimension. See the Hyperion
System 9 BI+ Analytic Services Database Administrator's Guide and online help.
Attributes add another level of granularity to data. You create attribute values for attributes that
are assigned to dimension members. You can filter members by their attribute values when creating
data forms and reports. For example, you can have a Product dimension with members for three
product lines that are sold in retail outlets and by catalog. When you analyze or report on data,
you can separate totals for retail and catalog sales. To gather this information, you could define
an attribute called Channel for the Product dimension, with the values Retail and Catalog. You
could then assign a value to members in the Product dimension that you need to categorize.
You can assign attributes only to sparse dimensions. You cannot assign attributes to label-only
members. If you need to add an attribute to a dense dimension, you must change that dimension
to sparse for all plan types. If you change a dimension from sparse to dense, all attributes and
attribute values for the dimension are automatically deleted.
When you delete attributes, all associated attribute values are also deleted. The values are
removed from any members to which they had been assigned, and the attribute is removed from
any dimensions to which it had been assigned.
191
Account
Account dimension members specify information needed from budget planners. Create an
account structure that lets budget preparers input data for budget items to the appropriate level
of detail. You can define calculations in the account structure. For example, Detail Operating
Expense can aggregate to Total Expenses, and Total Expenses can be subtracted from Total
Revenue. Account dimensions must have an association with Attribute and Alias dimensions to
be able to assign attribute values and aliases to members of the dimension.
Table 39 Account Properties
Valid for Plan See Table 38, “Common Planning Properties,” on page 189.
If accounts are valid for multiple plan types, specify the source plan type to determine which
database stores the account value. For example, if Revenue is the source plan type for Total
Sales, the value displayed for Total Sales on data forms for the P&L plan type is the value
entered for the Revenue plan type.
Aggregation for Plan See Table 38, “Common Planning Properties,” on page 189.
UDA See Table 38, “Common Planning Properties,” on page 189.
Member Formula See Table 38, “Common Planning Properties,” on page 189.
Alias See Table 38, “Common Planning Properties,” on page 189.
Data Storage See Table 38, “Common Planning Properties,” on page 189.
Two Pass Calc Recalculate data values of members that are based on data values of the parent member or
other members. Available for account and entity members with Dynamic Calc or Dynamic Calc
and Store properties.
Smart List See Table 38, “Common Planning Properties,” on page 189.
Time Balance Set method for calculating the value of summary time periods: None, Flow, First, Balance,
Average, Weighted Average. See Table 41, “ Time Balance Property Examples,” on page
193.
Skip Value If the time balance property is First, Balance, or Average, you can specify how database
calculations treat zeros and missing values when calculating parent values:
● None: Zeros and #missing values are considered
● Missing: Excludes #missing values
● Zeroes: Excludes zero values
● Missing and Zeroes: Excludes #missing and zero values
For examples, see Table 42, “Effect of Skip When Time Balance is Set to First,” on page
194.
Variance Reporting Set whether the account is treated as an expense when determining variances:
● Expense: The actual value is subtracted from the budgeted value
● Non-Expense: The budgeted value is subtracted from the actual value

Account Type Define account time balance (how values flow over time) and sign behavior for variance
reporting: Expense, Revenue, Asset, Liability, Equity, and Saved Assumption. See Table 40,
“Valid Combinations of Account types and Dependent Properties,” on page 193.
Exchange Rate Type Set how numeric values are stored in account members and used to calculate values. For
accounts with Currency data type, these options are valid for any time period:
● None
● Average: Average exchange rate
● Ending: Ending exchange rate
● Historical: Exchange rate in effect at some point, such as during earnings for Retained
Earnings accounts
For accounts, if Data Type is set to any value except Currency, you must set Exchange Rate
Type to None.
Data Type See Table 38, “Common Planning Properties,” on page 189.
Source Plan Type The source plan type determines which plan type database stores the account value. If you
move an account member and the new parent of that member has a different source plan
type, the source plan type of the member is set to the first new valid plan type of that member.
The valid plan types are determined by the ones the member has in common with its new
parents.
Account Type Summary

Table 40 Valid Combinations of Account types and Dependent Properties
Account Type Time Balance Variance Reporting Purpose
Revenue Flow Non-Expense Source of income
Expense Flow Expense Cost of doing business
Asset Balance Non-Expense Company resource
Liability and Equity Balance Non-Expense Residual interest or obligation to creditors
Saved Assumption User-defined User-defined Centralized planning assumptions to ensure

consistency across the application
Time balance and variance reporting settings are system-defined.
Table 41 Time Balance Property Examples
Time Balance Property Description Example
Flow An aggregate of values for a summary time Jan: 10 Feb: 15 Mar: 20 Q1: 45
period as the period total.
Account 193
Time Balance Property Description Example
First The beginning value in a summary time Jan: 10 Feb: 15 Mar: 20 Q1: 10
period as the period total.
Balance The ending value in a summary time period Jan: 10 Feb: 15 Mar: 20 Q1: 20
as the period total.
Average An average for all the child values in a Jan: 10 Feb: 15 Mar: 20 Q1: 15
summary time period as the period total.
Weighted Average - Actual_Actual A weighted daily average, based on the Jan: 10 Feb: 15 Mar: 20 Q1: 15
actual number of days in a year. Accounts
for leap year, in which February has 29 days.
In the example, the average for Q1 is
calculated: (1) Multiply each value in Q1 by
the number of days in the month, (2) Sum
these values, (3) Divide the total by the
number of days in Q1. Assuming it is a leap
year, the result is calculated: (10 * 31 + 15
* 29 + 20 * 31) / 91 = 15
Weighted Average - Actual_365 A weighted daily average, based on 365 Jan: 10 Feb: 15 Mar: 20 Q1: 15
days in a year, assuming that February has
28 days. Does not account for leap years.
In the example, the average for Q1 is
calculated: (1) Multiply each value in Q1 by
the number of days in the month, (2) Sum
these values, (3) Divide the total by the
number of days in Q1. Assuming it is not a
leap year, the result is calculated: (10 * 31
+ 15 * 28 + 20 * 31) / 90 = 15
You can use the Weighted Average - Actual_Actual and Weighted Average - Actual_365
properties only with standard monthly calendars that rolls up to four quarters. For information
on how Planning calculates and spreads data, see the Hyperion System 9 Planning User's Guide.
Examples of Account Calculation for Zeros and Missing

Values
Table 42 Effect of Skip When Time Balance is Set to First
Skip Option Example
None Jan: 0 Feb: 20 Mar: 25 Q1: 0

The value of the first child (Jan) is 0, and zeros are considered when calculating the parent value,
so Q1 = 0.
Missing Jan: #missing Feb: 20 Mar: 25 Q1: 20

The value of the first child (Jan) is #missing, and #missing values are not considered when
calculating parent values, so Q1 = second child (Feb), or 20.
Zeros Jan: 0 Feb: 20 Mar: 25 Q1: 20

Skip Option Example
The value of the first child (Jan) is 0, and zero values are not considered when calculating parent
values, so Q1 = the second child (Feb), or 20.
Missing and Zeros Jan: 0 Feb: #missing Mar: 25 Q1: 25

The value of the first child (Jan) is zero, and the value of the second child (Feb) is missing.
Because missing and zero values are not considered when calculating parent values, Q1 = the
third child (Mar), or 25.
Currency
You can plan, forecast, and analyze financial information in multiple currencies by setting:
● Which currencies are used by applications and reporting
● How currencies display in reports and data forms
● How currencies are translated into other currencies
● Whether a third (triangulation) currency is used
● When currency conversions occur
For information on managing exchange rates, currency conversion, and exchange rate tables,
see the Hyperion System 9 Planning Administrator's Guide.
Table 43 Currency Properties
Thousands Separator ● None

● Comma
● Dot
● Space
● Currency Setting
Decimal Separator ● Dot

● Comma
Negative Sign ● Prefixed Minus

● Suffixed Minus
● Parentheses
Negative Color ● Black

● Red
Currency 195
Scale ● Whole
● Tens
● Hundreds
● Thousands
● TThousands
● HThousands
● Millions
● TMillions
● HMillions
● Billions
Two Pass Calc Recalculate data values of members that are based on data values of the parent member
or other members. Available for account and entity members with Dynamic Calc or Dynamic
Calc and Store properties.
Currency Code Enter the three-letter currency code.
Symbol Enter the currency symbol.
Triangulation Currency Set the triangulation currency, the interim currency for currency conversion. If you modify a
triangulation currency, you must re-enter exchange rates for the triangulation currency
property and refresh the application to transfer and store the exchange rates. You cannot
select the default currency as a triangulation currency.
Reporting Currency Set the reporting currency used to prepare financial statements. Converted reporting currency
values are stored and read-only for all users.
Attribute Values See Table 38, “Common Planning Properties,” on page 189.
Entity
You can create entity members for groups that submit plans for approval. Define the
organizational units your company requires, such as geographical regions, departments, or
divisions. For example, regional centers might prepare plans for review at corporate
headquarters. To match this structure, create members for regions, countries and headquarters.
Specify regions as children of country members, and country members as children of
headquarters. Data forms support multiple currencies per entity, enabling data entry for multiple

currencies and reporting against one currency. You can set the currency for entered values, which
are converted to other currencies with defined exchange rates.
The Entity dimension requires an association with the Currency dimension to enter a value for
Base Currency. For multi-currency applications, the Currency dimension must be associated
with the base entity dimension. Entity dimensions require an association with Attribute and
Alias dimensions to be able to assign attribute values and aliases to members of the dimension.
You can activate associations for an Application View in the Master View, by right-clicking the
Application View name and selecting Activate all Associations.
Table 44 Entity Properties
Aggregation See Table 38, “Common Planning Properties,” on page 189.
Currency Enter the three-letter currency code.

For multi-currency Application Views, specify the base currency for each entity member. For
example, if U.S. Dollars is the default currency, you can specify Yen as the base currency for the
Japan entity and U.S. Dollars for the United States entity. For data forms with values for the Japan
entity, if the display currency is U.S. Dollars, values are converted to U.S. Dollars using rates in
the exchange rate table (if Yen is the local currency and U.S. Dollars is the reporting currency).
Period
Use the Period dimension to view and change the yearly calendar rollup structure. When creating
Application Views, specify base time periods and distribution of weeks. Use the Year dimension
to add years to the calendar.
Table 45 Period Properties
Period 197
After the calendar is created, you cannot change the base time period or reduce the number of
years. Administrators can change names, descriptions, aliases, and ranges of summary time
periods. An application can have up to 100 calendar years and 500 time periods. Actual limits
are defined by calendar years and time periods. The number of time periods and years also
depends on whether your application uses multiple currencies. Hyperion recommends these
practical limits:
● 400 time periods per year and 27 years
● 360 time periods per year and 30 years
You can add and change summary time periods or the BegBalance member, including updating
the name, description, alias, starting period, and ending period. You cannot skip or change the
order of base time periods. The range cannot extend beyond the current fiscal year.
You must work from the top of the hierarchy to the bottom when creating summary time periods.
The new summary time period displays in the hierarchy as a parent of the selected item. To
enforce a balanced hierarchy, all base members must be the same number of levels from the root.
The BegBalance member is a required member for Planning applications and must exist for
successful deployment.
The YearTotal member is a required member for Planning applications and must exist for
successful deployment. The YearTotal member is the summary time period that aggregates all
of the Quarters or Weeks (for custom time periods).
Scenario
You can create scenarios to group data. Each scenario/version combination contains data for
accounts and other dimensions of each entity. After users enter entity data for a scenario and
version, they can submit or promote the data to other users for review and approval. The
intersection of entity, scenario, and version is called a planning unit. Planning tracks the status
of planning units as they move through the review process. The Scenario dimension requires an
association with Period and Year dimensions to enter start and end time period values.

Use scenarios to:
● Apply different planning methods.
● Create forecasts and budgets.
● Enter data into scenarios.
● Assign user access permissions by scenario.
● Report on scenarios.
● Compare and analyze scenarios.
You can create multiple plans with individual review cycles. Scenarios can cover different time
spans. For example, your organization can create one-year and three-year revenue plans that are
prepared by different users and follow different review paths and scenarios.
Table 46 Scenario Properties
Evaluation Order See Table 38, “Common Planning Properties,” on page 189.
Enable for Process Management Select whether the Scenario is enabled for process management. This
allows for managing a planning unit that contains this member.
Start Year, End Year, Start Period, End Period Assign a range of years and time periods for which the scenario is
valid. When users access data forms, they can enter into that scenario
only years and periods within the range.
You can modify the time range of scenarios. You can have a scenario
named 3Year Forecast that has 2006 as the start year and 2008 as
the end year. At the beginning of the 2007 fiscal year, you could
advance the start year to 2007 and the end year to 2009. You could
then enter forecast data for 2009.
Use Beginning Balance Specify whether to use the Beginning Balance time period for a
scenario
Exchange Rate Table If an application converts currencies, assign an exchange rate table
to the scenario. By assigning different exchange rate tables to
Scenario 199
scenarios, you can model the effect of different assumptions about
currency rates.
Working with Scenarios

Scenarios are required for Planning applications, and must exist for successful deployment. You
can specify access permissions for Scenario dimension members to determine whether groups
or users can view or modify data. For information about setting access permissions for Planning,
see the Hyperion System 9 Planning Administration Guide.
When you delete scenarios, all planning units that use the scenario (including data) are deleted.
You cannot delete scenarios that are used in planning units that are started or assigned to an
axis on a data form. You must first remove references to scenarios from data forms and assign
different scenarios.
Version
Versions are required for Planning applications, and must exist for successful deployment. Use
Version dimensions to:
● Allow multiple iterations of a plan, such as Preliminary and Final
● Model possible outcomes based on assumptions such as Best Case and Worst Case
● Control plan data, such as Internal and External
● Facilitate target setting
Versions are independent of scenarios. You can change the version name and access permissions.
For example, you can give users read-only access to the Final version. At least one version must
remain in the application. For information on setting access permissions, see the Hyperion System
9 Planning Administrator's Guide.
Table 47 Version Properties
Evaluation Order See Table 38, “Common Planning Properties,” on page 189.

Enable for Process Management Select whether the Version should be enabled for process management. This
allows for managing a planning unit that contains this Version member. Not
available for target versions.
Version Type Target: Users enter data for members at any level, and use business rules to
distribute values from parent members to descendants. For example, enter the
target for Total Expenses into the Europe member and use business rules to
distribute target values to Northern and Southern Europe based on headcount.
Use target versions to set high-level targets for plans. Planners working with
bottom-up versions can reference targets when entering plan data. For example,
the Total Sales member might have Retail, Wholesale, and Distributors as children.
A budget manager can enter 10,000 into Total Sales for the California entity in a
target version to set the sales target. The budget preparer for California can then
enter a combination of values for Retail, Wholesale, and Distributor that total
10,000 into a bottom-up version to show how the target will be met.
Target versions use top-down budgeting. Workflow tasks are not allowed, and
children of target members must be blank (for example, #missing) to enable data
input at the top level. Target members must be set to Store (Dynamic Calc overrides
data input with sum of children).
Bottom Up: Users enter data into bottom-level members. Parent-level members
are display-only. Values for parent members are aggregated from bottom level
members. For example, enter data for Northern Europe and Southern Europe, and
the total for Europe is the aggregated result.
Year
Use the Year dimension for calendar years.
You must add the Start Year for the Application View to the Year dimension. The Start Year
property must use four digits, such as 2006. When you add Year dimensions, the names must
start with FY, followed by a two-digit year, such as FY06. You cannot modify the Start Year of
an application after the Application View has been deployed.
The Start Year dimension and First Year property must describe the same year, using different
formats. For example, if the Start Year is 2006, the First Year property must be FY06. If there is
a discrepancy between the years, such as FY05 and 2006, an error displays and the Application
View cannot be deployed.
You can add, change, or assign aliases to years. You cannot reduce the number of calendar years
without creating a new database.
BPM Architect adds No Year as a system member, as the first member in the Year dimension.
In BPM Architect, No Year is saved as the first member in the Year dimension, but it is saved as
the last year in the Planning repository.
Year 201
Table 48 Year Properties
Considerations for Working with Planning Dimensions

You create hierarchical relationships in dimensions by creating and organizing members, which
are components of dimensions. You can add dimension members individually or using Import
Profiles. Dimension names must use the conventions detailed in “Naming Restrictions for
Dimensions, Members, and Aliases” on page 206.
Sparse dimensions lack data values for the majority of member combinations, and have a low
percentage of available data positions filled. Dense dimensions have a high probability that one
or more data points are occupied in every combination of dimensions.
To optimize database performance, designate dimensions as sparse or dense. If a dimension is
sparse, Planning calculates only data values that are occupied in each dimension combination.
This optimizes performance by decreasing calculation time and lowering disk usage. By default,
Planning designates the Account and Period dimensions as dense and other dimensions as
sparse.
Dimension hierarchies define structural and mathematical relationships, and consolidations
between members in the database. For example, a Period dimension might contain YearTotal,
which contains Q1, Q2, Q3, and Q4. Members Q1, Q2, Q3, and Q4 contain their own members
for the corresponding months in the year. To consolidate data values in the Period dimension,
rollup monthly values to get quarterly values, and quarterly values to get yearly values.
Members of the same level that belong to the same dimension or member are called siblings. In
the example, Q1, Q2, Q3, and Q4 are siblings because they are at the same level in the hierarchy,
and are members of YearTotal. However, Jan and Apr are not siblings because Jan is a member
of Q1 and Apr is in Q2.
Members that belong to a dimension are called children of the dimension. Members that belong
to a member are called children of that member. In the example, the member YearTotal is a
child of Period, the members of Q1, Q2, Q3, and Q4 are children of YearTotal, and Jan, Feb,
and Mar are children of Q1. Q1 is the parent of Jan, Feb, and Mar, YearTotal is the parent of

Q1, Q2, Q3, and Q4, and Period is the parent of YearTotal. Data values for Jan, Feb, and Mar
are consolidated for Q1. Q1, Q2, Q3, and Q4 are consolidated for YearTotal.
For important information about Application Views, see “Considerations for Deploying
Planning Application Views” on page 100 and “Considerations for Redeploying Planning
Additional considerations include:
● New dimensions created in the Dimension Library do not have any default associations.
● If dimensions are loaded from a flat file, the association must be specified in the flat file.
● If applications are upgraded from Planning to BPM Architect, the associations may be
assigned.
● It is not necessary to associate a Smart List with a main dimension (such as Account or
Entity) but Smart Lists are associated in the Smart List property field.
● You can use the Dimension Alias in System Properties (not Planning properties) to deploy
dimensions with different names.
Custom Dimensions
Dimension names and aliases must be unique and can contain up to 80 characters, including
spaces. Descriptions can have up to 255 characters. Dimensions must follow the naming
conventions in “Naming Restrictions for Dimensions, Members, and Aliases” on page 206.
You can assign access permissions to members, rearrange the dimension member hierarchy, and
share members of the Entity, Account, and custom dimensions. For information about assigning
access permissions, see the Hyperion System 9 Planning Administration Guide.
Planning Attributes
Attribute names must be unique, and must use proper naming rules. See “Naming Restrictions
for Dimensions, Members, and Aliases” on page 206. You can assign attributes only to sparse
dimensions. For dense dimensions, you must change them to sparse for all plan types. When
changing dimensions to dense, all attributes and attribute values for the dimension are
automatically deleted. You cannot assign attributes to label-only members. Dimensions such as
Entity and Account require an association with Attribute and Alias dimensions to be able to
assign attribute values and aliases to members of the dimension.
If you change or delete attributes, you must update and validate business rules, reports, and data
forms. When you delete attributes, all associated attributes values are also deleted. When you
delete an attribute value, it is removed from custom dimension members to which it is assigned.
You can use Import Profiles to load attribute values. You must create attribute dimensions before
loading the property values.
Custom Dimensions 203

Considerations for Excluding and Deleting Planning Members
deployment. Hence, excluding dimension members can result in data loss when redeploying
Application Views. On redeployment, a Planning application is refreshed from BPM Architect
and all dimensions used in the application are refreshed with their current structure in BPM
Architect. Redeployment refreshes all dimensions and their members, even if they have no
changes in them.
If the excluded members are used elsewhere (such as a selection in a data form), those associations
are removed. Before excluding members from an Application View, use the Planning Show
Usage feature within Planning to determine where members are used in the application and the
implications of exclusion of dimension members from an application during deployment. For
information about the Show Usage feature, see the Hyperion System 9 Planning Administrator's
Guide.
When you exclude a member from a dimension in an Application View and deploy the
application to Planning, this automatically deletes the member from that dimension in Planning.
It also deletes any associated supporting detail, data, and references to the member. For example:
● Excluding a Scenario, Version, or Entity dimension member deletes a planning unit and all
of its history (data) and annotations associated.
● Excluding a member referenced by data forms changes the data form definition so it uses
the root dimension member only. This may result in loss of access permission or cause no
data to display in a data form.
● Excluding a currency dimension member referenced by an entity changes the entity
dimension so it uses the default currency for the Application View.
● Excluding a currency member referenced as a triangulation currency removes the
triangulation.
When custom dimensions and attribute dimensions are excluded from an Application View in
BPM Architect, they are not deleted from Planning during deployment. However, when
members for these dimensions are excluded from an Application View, they are deleted from
Planning during deployment.
To improve performance when deleting entities, first exclude planning units for the subtree (by
excluding the root member) for all scenarios and versions. After deleting entity members, you
must update and validate business rules, reports, and data forms.
Considerations for Deleting Planning Application Views

Before deleting an Application View, you must back up the Planning application and application
databases as described in the Hyperion System 9 Planning Installation Guide. After backing up,
use the procedure for deleting Application Views in this guide. When you finish deleting
Application Views, ensure that the application is deleted from Analytic Services, and that the
Planning relational tables are deleted from the relational database.

Working with Shared Members
Sharing members allows alternate rollup structures within Planning Application Views. A base
member must exist before you can create a shared member. You can create multiple shared
members for the base member. A base member must display before its shared members in
position from top to bottom.
Note that the BPM Architect Set Base Member feature is not related to shared members. The
BPM Architect Set Base Member feature enables you to exclude children under a parent. For
example, in the Entity rollup, Region can have children called Division1 and Division2. If you
make Region the base for the rollup, Division1 and Division2 are no longer visible.
Shared members are available for Entity, Account, and custom dimensions. For example, you
can rollup by function, line of business, or geography. Shared member values can be ignored to
avoid double-counting values.
Shared members share some property definitions with base members, such as member name,
alias name, base currency, and plan types for which members are valid. Shared members must
have unique parent members and different rollup aggregation settings. Custom properties,
custom property values, and member formulas are not allowed for shared members.
Shared members cannot be moved to another parent member. You must delete shared members
and recreate them under different parent members. Shared members must be at the lowest level
(level zero) in the hierarchy and cannot have children. (The base member need not be level zero.)
You can enter data in shared members, and values are stored with base members. With shared
members:
● The base member cannot be the parent of the shared member. The shared member can be
anywhere else in the dimension hierarchy.
● The shared member must have the same name as its base member. It can have another
description.
● You must set Data Storage for shared members to ShareData in BPM Architect. Otherwise,
the shared member is not added when the Application View is deployed to Planning.
Shared members are displayed similarly to base members in the dimension hierarchy for member
selection in Hyperion® System™ 9 Business Rules™ and Hyperion® System™ 9 Smart View for
Office™. For Business Rules, there is no labeling distinction, so you might not be able to select
shared members for actions such as Copy Data.
Naming Restrictions for Applications

This topic describes the rules for naming applications in Analytic Services. For detailed
information on creating Analytic Services applications and databases, see the Analytic Services
product documentation.
When naming applications, follow these rules:
Working with Shared Members 205

● Use no more than 8 bytes when naming non Unicode mode applications and databases; use
no more than 30 characters when naming Unicode mode applications and databases.
● Do not use spaces.
● Do not use these special characters:
asterisks plus signs
backslashes question marks
brackets double quotation marks
colons semicolons
commas single quotation marks
equal signs slashes
greater than signs tabs
less than signs vertical bars
periods
● In relational database environments, extended characters, except for the underscore, cannot
be used in Planning application names.
● For aggregate storage databases only, do not use these words as application names:
DEFAULT, LOG, METADATA, or TEMP.
Enter the name in the case in which to display the word. The application name is created exactly
as you enter it.
Naming Restrictions for Dimensions, Members, and Aliases

When naming dimensions, members, and aliases, follow these rules:
● Use no more than 80 bytes when naming non Unicode mode dimensions, members, or
aliases; use no more than 80 characters when naming Unicode mode dimensions, members,
or aliases.
● Names are not case sensitive unless case sensitivity is enabled.
● Do not use HTML tags in member names, dimension names, aliases, and descriptions.
● Do not use quotation marks, brackets, backslashes, or tabs anywhere in a name. Brackets
are supported in block storage outlines, but are not recommended because their use causes
errors when converting to an aggregate storage outline.
● At the beginning of a dimension or member name, do not use these characters:
at signs parentheses
backslashes periods

braces plus signs
commas single quotation marks
dashes, hyphens, or minus underscores
equal signs vertical bars
less than signs
● Do not place spaces at the beginning or end of a name. Analytic Services ignores spaces at
the beginning or end of a name.
● Do not use forward slashes in member names.
● Do not use spaces in prefixes to time periods in custom calendars.
● Do not use these words as dimension or member names:
❍ Calculation script commands, operators, and keywords. For a list of commands, see the
Analytic Services product documentation.
❍ Report writer commands. For a list of commands, see the Analytic Services product
documentation.
❍ Function names and function arguments. For a list of functions, see the Analytic Services
product documentation.
❍ Names of other dimensions and members (unless the member is shared), and generation
names, level names, and aliases in the database.
❍ These words:
ALL AND ASSIGN AVERAGE CALC GENRANGE GROUP GT ID OR PAREN PARENPARM PERCENT
CALCMBR COPYFORWARD IDERROR INTEGER LE PLUS RELOP SET SKIPBOTH
CROSSDIM CURMBRNAME DIM LEVELRANGE LOOPBLOCK SKIPMISSING SKIPNONE
DIMNAME DIV DYNAMIC LOOPPARMS LT MBR MBRNAME SKIPZERO TO TOLOCALRATE
EMPTYPARM EQ EQOP EXCEPT EXP MBRONLY MINUS MISSING MUL TRAILMISSING TRAILSUM UMINUS
EXPERROR FLOAT FUNCTION GE GEN MULOP NE NON NONINPUT NOT UPPER VARORXMBR XMBRONLY $
$UNIVERSE$$ #MISSING #MI
If you enable Dynamic Time Series members, do not use the associated generation names,
History, Year, Season, Period, Quarter, Month, Week, or Day.
Naming Restrictions for Dimensions, Members, and Aliases 207

Working with Analytic Services
C Properties
In This Appendix
Application View Properties ..................................................................................................... 209
Dimension and Member Properties ............................................................................................ 212
Application View Properties

Following are the properties for Enterprise Analytics and Essbase Analytics application views in
alphabetical order.
Note:
Unless otherwise noted, the properties apply to both Enterprise Analytics and Essbase Analytics
application views.
Table 49 Essbase Analytics and Enterprise Analytics Application Properties
Attribute Description
Allow Duplicates in Outline Select to allow duplicate member names in an outline.

By default, Analytic Services outlines require that member names are
unique. If you want to allow duplicate member names in an existing
unique outline, you can select this option to convert the application to
allow duplicate members. Once an application is converted, it cannot
be changed back to unique.
By default, all dimensions in a duplicate member name application
allow duplicate member names. You can clear the “Allow Duplicates in
Dimension” option for one or more dimensions in a duplicate member
name outline to require unique member names in the dimension.
Attribute Calculations Avg Name To avoid duplicating names in an outline, you may need to change the
name of the Attribute Calculations dimension or its members.
If desired, specify a new name for the Attribute Calculations dimension
or a new name for any of the members. The names specified are used
in reports and spreadsheets. The function of the member is not affected
by the member name. For example, the second member of the
dimension counts, regardless of what the name is.
Optional: Specify a new name for the Attribute Calculations Avg
member.
Application View Properties 209

Note: This option only applies to Essbase Analytics applications.
Attribute Calculations Boolean False Name Optional:Enter the name for all False members of Boolean attribute
dimensions; for example, all members with a False value might be
named No.
The default is False.
Attribute Calculations Boolean True Name Optional:Enter the name for all True members of Boolean attribute
dimensions; for example, all members with a True value might be named
Yes.
The default is True.
Attribute Calculations Date Name Select the format for names of members of date attribute dimensions:
● Month First (mm-dd-yyyy)
● Day First (dd-mm-yyyy)
Attribute Calculations Count Name Optional: Specify a new name for the Attribute Calculations Count
member.
Attribute Calculations Dimension Name Optional: Specify a new name for the Attribute Calculations dimension.
Attribute Calculations Max Name Optional: Specify a new name for the Attribute Calculations Max
member.
Attribute Calculations Min Name Optional: Specify a new name for the Attribute Calculations Min
member.
Attribute Calculations Range Name Specify whether the attribute value is the top or bottom value of a
numeric range. For example, if Tops of ranges is selected, with attributes
named 1000, 100000, and 1000000, the ranges are 0-1000,
1001-100000, and 100001-1000000.
Select one of the following options:
● Bottoms of ranges
● Tops of ranges
Attribute Calculations Sum Name Optional: Specify a new name for the Attribute Calculations dimension.
Auto Configure Indicates whether or not Analytic Services automatically determines

whether dimensions have a dense or sparse data configuration.
● true: Analytic Services automatically sets each dimension as dense
or sparse. You cannot manually change the dimension storage type.
The default value is true.
● false: The dense or sparse data configuration can be manually
changed.
Note: This setting only applies to Essbase Analytics applications.
Case Sensitive Indicates whether or not members are treated as case sensitive.
210 Working with Analytic Services Properties

● If the check box is selected:
Member names are case-sensitive; for example, Product is different
from product. Members whose names differ only by case are treated
as separate members in all member comparison and search
operations. This is the default.
● If the check box is cleared:
Member names are case-insensitive.
Comment Optional: Type a descriptive comment for this application.
Conversion Method Select the conversion method to be used during the conversion
calculation:
● Multiply: Multiplies local data values in the main database by
exchange rates in the currency database.
● Divide (the default): Divides local data values in the main database
by exchange rates in the currency database.
Currency Database Select a currency database to link to for currency conversion

calculations. If no currency database is linked to the current database,
the currency database is None.
Database Name Type the name of the multidimensional database to be created when
this application is deployed.
Prefix/Suffix Format Select prefix or suffix.

● Prefix: Attaches the specified prefix before the names of members
of Boolean, date, and numeric attribute dimensions; for example,
Population_6000000. Prefix is the default value.
● Suffix: Attaches the specified suffix after the names of members of
Boolean, date, and numeric attribute dimensions; for example,
6000000_Population.
Prefix/Suffix Separator Separator: Select one of the following separators to insert between the
prefix or suffix and the attribute member name:
● _ Underscore: For example, Population_Small_6000000.
Underscore is the default value.
● | Pipe: For example, Population|Small|6000000.
● ^ Caret: For example, Population^Small^6000000.
Prefix/Suffix Value Select the source of the value that Analytic Services attaches to the
names of members of Boolean, date, and numeric attribute dimensions:
● None: Uses the complete member name with no prefix or suffix
attached; for example, 6000000.
● Dimension: Attaches the name of the attribute dimension as prefix
or suffix to the complete member name; for example,
Population_6000000.
Application View Properties 211

● Parent: Attaches the name of the immediate parent as prefix or suffix
to the complete member name; for example, Small_6000000.
● Grandparent: Attaches the name of the grandparent as prefix or
suffix to the complete member name; for example,
Population_6000000.
● Ancestors: Attaches the name of all higher-level generations as the
prefix or suffix to the complete member name; for example,
Population_Small_6000000.
Unicode Select this check box to migrate an application to Unicode mode.

Caution! Setting an application to Unicode mode cannot be undone.
See the Analytic Services Database Administrator's Guide for
information on migrating applications to Unicode Mode.
Dimension and Member Properties

Following are the properties for Enterprise Analytics and Essbase Analytics dimensions and
members in alphabetical order.
Note:
Unless otherwise noted, the properties apply to dimensions and members in both Enterprise
Analytics and Essbase Analytics application views.
Table 50 Enterprise Analytics and Essbase Analytics Dimension and Member Properties
Alias Enter the alias in the text box.

Displays all alias tables defined for the database and all aliases defined for the
current member.
● Default: To assign or change the default alias name for the current dimension
or member, click the existing alias name and enter the new one. Follow the
proper naming rules. All databases have an alias table named Default.
● A list of alias tables: To assign or change an alias name for the current dimension
or member, click the existing alias name next to the alias table and enter the
new name. Follow the proper naming rules.
Allow Duplicates In Dimension In an outline that allows duplicate member names, select one of the following
options to specify member name uniqueness at a granular level:
● true: Duplicate member names are allowed in the dimension.
● false: Unique member names are required within the dimension. This is the
default for duplicate member name outlines.
Note: This setting does not apply to outlines that require unique member names.
Comment Enter a comment for the dimension or member. Comments can contain up to 255
characters. By default, this text box displays the current comment, if one exists.

You cannot assign a comment to an attribute dimension or member.
Consolidation Member consolidation properties determine how children rollup into their parents.
If the current member is not a dimension or an attribute, select the consolidation
operator to assign to the member:
● + (addition):
● - (subtraction)
● * (multiplication)
● / (division)
● % (percent)
● ~ (ignore during consolidation)
Addition (+) is the default setting for new members.
See also “Calculating Attribute Data” in the Administration Services Online Help.
Note: There are some restrictions with use of consolidation operators in aggregate
storage outlines.
Currency Shown if the selected item is a dimension, and if the dimension is tagged as country.
Enter the currency name, for example USD (for US dollars). When preparing a main
database outline for currency conversion, you need to assign currency names to the
country dimension and its members (for example, assigning dollars to the U.S., Euro
to Germany, and so forth).
Currency Conversion If the current member is a member of the accounts dimension and within a currency
application, complete the following options.
Currency conversion drop-down list box. Select one of the following currency
conversion options to define categories of currency exchange rates.
● None: The member has no relationship to currency conversion. This is the default
setting.
● No Conversion: The member is not converted because it is not a currency value.
It can be a value such as a quantity or percentage.
● Category: The member requires currency conversion to the Category you specify.
See “Preparing the Main Database Outline for Currency Conversion” in the
Administration Services Online Help.
Currency Category If the current member is a member of the accounts dimension and the member
requires currency conversion, enter the type of currency conversion required.
Currency category types are the names of members of the accounts dimension of
the currency database.
See also “Assigning Currency Categories to Accounts Members” in the
Data Storage Select one of the following storage options:
Dimension and Member Properties 213

● Existing definition or store: Select to use the data storage setting that is specified
in the outline. If there is no existing setting, Analytic Services sets the data
storage property to store. This is the default.
● Store data: Select to specify that the data is stored with the dimension.
● Never share: Select to specify that the data associated with this dimension
cannot shared, even if there is an implied share relationship, such as with a
parent with one child. In this case, the data is duplicated in the parent and
child.
Note: This option does not apply to stored hierarchies in aggregate storage
outlines.
● Label only: Select to specify that no data be associated with this dimension.
Note: This option has restrictions for aggregate storage outlines.
● Dynamic calc and store: Select to specify that the data associated with this
dimension is not calculated until requested by a user. Once calculated, the data
is stored.
Note: This option does not apply to aggregate storage outlines.
● Dynamic calc: Select to specify that the data associated with this dimension is
not calculated until requested by a user. The data is not stored but is discarded
after the request is completed.
Note: This option does not apply to aggregate storage outlines.
Note: You cannot use BPM Architect to create Hybrid Analysis or Advanced
Relational Access cubes.
Dimension Solve Order Select one of the following solve order options:
● Existing value or 0: Select to use the solve order setting that is specified in the
outline. If there is no existing setting, Analytic Services sets the solve order value
to 0.
● New value: Select to specify a number to represent the priority with which
Analytic Services calculates the formulas. The formula on the member that has
the highest solve order takes precedence. You can specify a solve order between
0 and 127. Values less than 0 or greater than 127 are reset to 0 and 127
respectively. No warning message is displayed. The default value is 0.
You can also specify solve order at the member level. Members that do not have a
solve order inherit the solve order of their dimension.
For complete information about solve order, see “Calculation Order” in the
Note: These settings only apply to Enterprise Analytics applications.
Fully Qualified Shared Member In outlines enabled for duplicate member names, displays the qualified name for
members with duplicate (non-unique) names. A qualified member name is
constructed by prefixing ancestor names to the member name, up to the ancestor
that makes the name unique.
For example, if the outline has two members named New York, one under State and
one under City, the qualified member names include the first ancestor name that
differentiates the members from each other:
[State].[New York]
[City].[New York]

Hierarchy Type Select one of the following hierarchy options:

● Existing definition or stored: Select to use the hierarchy setting that is specified
in the outline. If there is no existing setting, Analytic Services sets the hierarchy
type to stored.
● Multiple hierarchy enabled: Select to use both stored and dynamic hierarchies
in the dimension.
● Stored: Select to set the dimension as a stored hierarchy. This is the default.
● Dynamic: Select to set the dimension as a dynamic hierarchy.
The dimension tagged as accounts is automatically considered a dynamic hierarchy.
You cannot specify the accounts dimension as a stored hierarchy.
For important information about restrictions with using dynamic and stored
hierarchies, see “Hierarchies” in the Administration Services Online Help.
Member Formula Displays any formulas associated with the member.
Member Solve Order Specify a number to represent the priority with which Analytic Services calculates
the formulas. The formula on the member that has the highest solve order takes
precedence. You can specify a solve order between 0 and 127. Values less than 0
or greater than 127 are reset to 0 and 127 respectively. No warning message is
displayed. The default value is 0.
Members that have a solve order of 0 inherit the solve order of their dimension.
Members with the same solve order are evaluated in the order in which their
dimensions appear in the database outline. Members with no solve order are
evaluated after members with a solve order.
For complete information about solve order, see “Calculation Order” in the
Note: This setting only applies to Enterprise Analytics applications.
Primary Level Weighting Primary level weighting restricts the levels which can be selected by the view
selection engine during aggregation operations.
Select one of the following options:
● Default: The view selection engine is free to decide which levels to pick. This is
the initial value for new hierarchies.
● Consider all Levels: The view selection engine considers all levels of the hierarchy
for aggregation.
● Do Not Aggregate: The view selection engine cannot select any levels for
aggregation.
● Consider Top Level Only: The view selection engine considers only the highest
level of the dimension for aggregation.
● Never Aggregate to Intermediate Levels: The view selection engine considers
only the highest level and the lowest level of the dimension for aggregation.
Skip Value Select one of the following options to determine what Analytic Services skips, or
ignores, during a time balance calculation. You can only specify skip settings if you
set the time balance properties as first, last, or average.

● None: Select to include zeros and missing values when calculating parent
values.
Note: If Analytic Services encounters #MISSING values when calculating, the
#MISSING values are not divided by the total number of members. Instead, the
#MISSING values are divided by the number of members with actual values.
● Missing: Select to exclude #MISSING values when calculating parent values.
● Zeros: Select to exclude zeros when calculating parent values.
● Missing and zeros: Select to exclude #MISSING values and zeros when
calculating parent values.
Time Balance Select one of the following options to set time balance properties.
● Existing definition or none: Select to use the setting specified in the outline. If
there is no existing setting, Administration Services sets the time balance
property to none. This is the default.
● None: Select to use no time balance properties. Member values are calculated
in the default manner.
● First: Select as the time balance property when the parent value represents the
value at the beginning of a time period.
● Average: Select as the time balance property, when the parent value represents
the average value of a time period.
● Skip node: Select one of the following options to determine what Analytic
Services skips, or ignores, during a time balance calculation. You can only
specify skip settings if you set the time balance properties as first, last, or
average.
❍ None: Select to include zeros and missing values when calculating parent
values. Note: If Analytic Services encounters #MISSING values when
calculating, the #MISSING values are not divided by the total number of
members. Instead, the #MISSING values are divided by the number of
members with actual values.
❍ Missing: Select to exclude #MISSING values when calculating parent values.
❍ Zeros: Select to exclude zeros when calculating parent values.
❍ Missing and zeros: Select to exclude #MISSING values and zeros when
calculating parent values.
Two Pass Calc Select this check box to calculate a dimension on the second pass through the
outline.
UDA Enter the UDA name for the selected member. Multiple UDAs must be comma
separated; for example: Small Market,New Market.
Variance Reporting Select one of the following options to determine how to calculate the difference
between actual and budget data.
● Existing definition or non-expense: Select to use the setting specified in the
outline to calculate the difference between actual and budget data. If there is
no existing setting, Analytic Services stores the dimension as non-expense. This
is the default.

● Non-expense: Select to set the member as non-expense. When you budget non-
expense items, such as sales, you want the actual sales to be greater than the
budget. When the actual sales is lower than the budget, the variance is negative.
● Expense: Select to set the member as an expense. When you budget expenses
for a period, you want the actual expenses to be lower than the budget. When
actual expenses are greater than the budget, the variance is negative.
Note: These options only apply to Essbase Analytics applications.

Working with Statistical and
D System Properties
There are statistical and system properties that apply to dimension members regardless of the
category selected.
Note:
For statistical properties, properties are defined for members only.
Table 51 Statistical Properties
References Lists the parents of the member.
Child Count Number of children of the member.
Descendant Count Number of descendants of the member.
Sibling Count Number of siblings of the member
Reference Count Number of parents of the member.
Ancestor List Lists the ancestors of the member.
For system properties, properties are defined for members and for dimensions. In the following
table, the non-bold properties are member properties and the bold properties are dimension
properties.
219
Table 52 System Properties
Name Name of the member
Description Description for the member
Parent Name of the parent for the member.
Parent Description Description of the parent
Display String For future use
Member Class For future use
Auto Exclude Inserts from Member Determines if a newly-added child in the Master View is automatically excluded
from the application view.
Dimension Name Name of the dimension
Dimension Description Description of the dimension
Display Properties For future use
Default Member The default top member for the dimension.
Dimension Class The type of dimension.
Dimension Alias The alias for the dimension.
Dimension Owner Users and groups who can only view this dimension in Financial Management.
For information on setting dimension access permissions for Planning, see the
Hyperion System 9 Planning Administrator’s Guide.
Dimension Readers Users and groups who can only view this dimension in Financial Management.
Dimension Writers Users and groups who can modify this dimension in Financial Management.
220 Working with Statistical and System Properties

Glossary
! See bang character (!). active user/user group The user or user group identified as
the current user by user preferences. Determines default
#MISSING See missing data (#MISSING).
user preferences, dynamic options, access, and file
access permissions A set of operations that a user can permissions. You can set the active user to your user name
perform on a Hyperion resource. or any user group to which you belong.
accessor Input and output data specifications for data activity-level authorization Defines user access to
mining algorithms. application components and the types of activities they can
perform on the application component. Activity-level
account A dimension that represents an accounting
authorization controls whether a given user may perform a
container that identifies the location and primary nature of
certain action in an application and is independent of the
the data.
data that will be operated on by the action. Data access is
account type The definition of how an account's value controlled by data-level authorization.
flows over time, and its sign behavior. Account type options
ad hoc report An online analytical query created on-the-fly
can include expense, income, asset, liability, and equity.
by an end user.
Expense examples: payroll expenses, salaries, office supplies,
legal expenses, and rent. Revenue examples: sales, interest adaptive states Interactive Reporting level of permission.
income, and other income. Asset examples: cash, accounts There are six levels of permission: view only, view and
receivable, fixed assets, and accumulated depreciation. process. analyze, analyze and process, query and process,
Liability examples: accounts payable, accrued expenses, and and data model and analyze.
long-term debt. Equity examples: common stock, preferred
adjustment See journal entry (JE).
stock, additional paid-in-capital, and retained earnings.
Advanced Relational Access Advanced Relational Access is
accountability map A visual, hierarchical representation of
the integration of a relational database with an Analytic
the responsibility, reporting, and dependency structure of
Services multidimensional database. However, with
your organization. An Accountability map depicts how each
Advanced Relational Access, you can build entire
accountability team in your organization interacts to
dimensions, with the exception of the Account dimension,
achieve strategic goals. An accountability team is also known
so that all data remains in the relational database and is
as a critical business area. For example, team, department,
mapped to summary-level data residing in the Analytic
or office.
Services database. Advanced Relational Access uses MDX
accounts dimension A dimension type that makes extensively and only works with aggregate storage outlines.
accounting intelligence available. Only one dimension can Hybrid Analysis will continue to use SQL as the data access
be defined as Accounts. mechanism and work with aggregate storage and block
storage outlines.
active service A service whose Run Type is set to Start rather
than Hold. agent An Analytic Server process that starts and stops
applications and databases, manages connections from
active user A user who is entitled to access the system.
users, and handles user-access security. The agent is referred
to as ESSBASE.EXE.
Glossary 221
aggregate cell A cell comprising several cells. For example, Analytic Server The server component of Analytic Services.
a data cell that uses Children (Year) expands to four cells
Analytic Server log A record of actions performed by the
containing Quarter 1, Quarter 2, Quarter 3, and Quarter 4
Analytic Server (agent).
data.
Analytic Services An OLAP engine in the Hyperion
aggregate function A type of function that summarizes or
platform. An instance of Analytic Services is an Analytic
performs analysis on data. Sum, calculation of an average,
Server.
and identification of a maximum value are examples of
aggregate functions. Analyze The main Web Analysis interface for analysis,
presentation and reporting.
aggregate limit A limit placed on an aggregated request line
item or aggregated metatopic item. ancestor A branch member that has members below it. For
example, in a dimension that includes years, quarters, and
aggregate storage database The database storage model
months, the members Qtr2 and 2006 are ancestors of the
provided by Enterprise Analytics. It is designed to support
member April.
large-scale, sparsely distributed data which is categorized
into many, potentially large dimensions. Upper level appender A Log4j term for destination.
members and formulae are dynamically calculated, and
applet In Java, a program that can run in a Web browser.
selected data values are aggregated and stored, typically with
Small programs written in languages other than Java are
improvements in overall aggregation time.
sometimes referred to as applets.
aggregate view An aggregation point based on the levels of
application (1) A software program designed to run a
the members within each dimension. These are used by the
specific task or group of tasks such as a spreadsheet program
Enterprise Analytics kernel to quickly derive data values for
or database management system. (2) A related set of
queries. For example, instead of aggregating from the
dimensions and dimension members that are used to meet
bottom of an outline, Enterprise Analytics starts at the
a specific set of analytical and/or reporting requirements.
closest possible aggregate view and adds up from there.
application currency The default reporting currency for
aggregation The process of rolling up and storing values in
the application.
an aggregate storage database; the stored result of the
aggregation process. ARBORPATH An environment variable that specifies the
Analytic Services root directory.
aggregation script In aggregate storage databases only, a
file that defines a selection of aggregate views to be built into area A predefined set of members and values that makes up
an aggregation. a partition.
algorithm A method (set of instructions) that the Data arithmetic data load A data load that performs operations
Mining Framework uses to analyze data. on values in the database, such as adding 10 to each value.
alias An alternative name. For example, for a more easily artifact An individual application or repository item; for
identifiable column descriptor you can display the alias example, scripts, forms, rules files, Interactive Reporting
instead of the member name. documents, financial reports and so forth. Also referred to
as an object.
alias table A table that contains alternate names for
members. asset account An account type that stores values that
represent a company's assets.
alternate hierarchy A hierarchy of shared members. An
alternate hierarchy is based upon an existing hierarchy in a attribute Characteristics of a dimension member. For
database outline, but has alternate levels in the dimension. example, an Employee Number dimension member may
An alternate hierarchy allows the same data to be seen from have attributes of Name, Age, or Address or a product
different points of view. dimension can have several attributes, such as a size and
flavor.
222 Glossary
attribute association A relationship in a database outline axis (1) A straight line that passes through a graphic used
whereby a member in an attribute dimension describes a for measurement and categorization. (2) A report aspect
characteristic of a member of its base dimension. For used to arrange and relate multidimensional data, such as
example, if product 100-10 has a grape flavor, the product filters, pages, rows, and columns. For example, for a data
100-10 has the Flavor attribute association of grape. Thus, query in Simple Basic, an axis can define columns for values
the 100-10 member of the Product dimension is associated for Qtr1, Qtr2, Qtr3, and Qtr4. Row data would be retrieved
with the Grape member of the Flavor attribute dimension. with totals in the following hierarchy: Market, Product.
Attribute Calculations dimension A system-defined balance account An account type that stores unsigned
dimension that performs the following calculation values that relate to a point in time.
operations on groups of members: Sum, Count, Avg, Min,
balanced journal A journal in which the total debits equal
and Max. This dimension is calculated dynamically and is
the total credits.
not visible in the database outline. For example, by using
the Avg member, you can calculate the average sales value bang character (!) A character that terminates a series of
for Red products in New York in January. report commands and requests information from the
database. A report script must be terminated with a bang
attribute dimension A type of dimension that enables
character; several bang characters can be used within a
analysis based on the attributes or qualities of dimension
report script.
members.
bar chart A chart that can consist of one to 50 data sets,
attribute reporting A reporting process based on the
with any number of values assigned to each data set. Data
attributes of the base dimension members. See also base
sets are displayed as groups of corresponding bars, stacked
dimension.
bars, or individual bars in separate rows.
attribute type A text, numeric, Boolean, or date type that
base currency The currency in which daily business
enables different functions for grouping, selecting, or
transactions are performed.
calculating data. For example, because the Ounces attribute
dimension has the type numeric, the number of ounces base dimension A standard dimension that is associated
specified as the attribute of each product can be used to with one or more attribute dimensions. For example,
calculate the profit per ounce for that product. assuming products have flavors, the Product dimension is
the base dimension for the Flavors attribute dimension.
attributes In data mining, a class of values used as a factor
in analysis of a set of data. base entity An entity at the bottom of the organization
structure that does not own other entities.
authentication Verification of identity as a security
measure. Authentication is typically based on a user name batch calculation Any calculation on a database that is
and password. Passwords and digital signatures are forms done in batch; for example, a calculation script or a full
of authentication. database calculation. Dynamic calculations are not
considered to be batch calculations.
authentication service A core service that manages one
authentication system. batch file An operating system file that can call multiple
ESSCMD scripts and run multiple sessions of ESSCMD. On
automated stage A stage that does not require human
Windows-based systems, batch files have BAT file
intervention, for example, a data load.
extensions. On UNIX, batch files are written as a shell script.
auto-reversing journal A journal for entering adjustments
batch POV A collection of all dimensions on the user POV
that you want to reverse in the next period.
of every report and book in the batch. While scheduling the
batch, you can set the members selected on the batch POV.
Glossary 223
batch processing mode A method of using ESSCMD to business rules Logical expressions or formulas that are
write a batch or script file that can be used to automate created within an application to produce a desired set of
routine server maintenance and diagnostic tasks. ESSCMD resulting values.
script files can execute multiple commands and can be run
cache A buffer in memory that holds data temporarily.
from the operating system command line or from within
operating system batch files. Batch files can be used to call CALC status A consolidation status that indicates that
multiple ESSCMD scripts or run multiple instances of some values or formula calculations have changed. You
ESSCMD. must reconsolidate to get the correct values for the affected
entity.
block The primary storage unit which is a
multidimensional array representing the cells of all dense calculated member in MaxL DML A member designed for
dimensions. analytical purposes and defined in the optional WITH
section of a MaxL DML query.
block storage database The Analytics database storage
model categorizing and storing data based on the sparsity calculation The process of aggregating data, or of running
of data values defined in sparse dimensions. Data values are a calculation script on a database.
stored in blocks, which exist only for sparse dimension
calendar User-defined time periods and their relationship
members for which there are values.
to each other. Q1, Q2, Q3, and Q4 comprise a calendar or
book A container that holds a group of similar Financial fiscal year.
Reporting documents. Books may specify dimension
cascade The process of creating multiple reports for a
sections or dimension changes.
subset of member values.
book POV The dimension members for which a book is
Catalog pane A pane displaying a list of elements available
run.
to the active section. For example, if Query is the active
bookmark A link to a reporting document or a Web site, section, the Catalog pane displays a list of database tables. If
displayed on a personal page of a user. The two types of Pivot is the active section, the Catalog pane displays a list of
bookmarks are My Bookmarks and image bookmarks. results columns. If Dashboard is the active section, the
Catalog pane displays a list of embeddable sections, graphic
bounding rectangle The required perimeter that
tools, and control tools.
encapsulates the Interactive Reporting document content
when embedding Interactive Reporting document sections categories Groupings by which data is organized (for
in a personal page, specified in pixels for height and width example, month).
or row per page.
cause and effect map A map that depicts how the elements
broadcast message A simple text message sent by an that form your corporate strategy are interrelated and how
administrator to a user who is logged on to a Planning they work together to meet your organization's strategic
application. The message displays information to the user goals. A Cause and Effect map tab is automatically created
such as system availability, notification of application for each of your Strategy maps.
refresh, or application backups.
CDF See custom-defined function (CDF).
budget administrator A person responsible for setting up,
CDM See custom-defined macro (CDM).
configuring, maintaining, and controlling an application.
Has all application privileges and data access permissions. cell (1) The data value at the intersection of dimensions in
a multidimensional database; the intersection of a row and
build method A method used to modify database outlines.
a column in a worksheet. (2) A logical group of nodes
Choice of a build method is based on the format of data in
belonging to one administrative domain.
data source files.
cell note A text annotation of up to 599 bytes for a cell in
business process A set of activities that collectively
an Analytic Services database. Cell notes are a type of LRO.
accomplish a business objective.
224 Glossary
CHANGED status A consolidation status that indicates committed access An Analytic Services Kernel Isolation
data has changed for an entity. Level setting that affects how Analytic Services handles
transactions. Under committed access, concurrent
chart A graphical representation of spreadsheet data. The
transactions hold long-term write locks and yield
visual nature of charts expedites analysis, color-coding, and
predictable results.
visual cues that aid comparisons. There are many different
chart types. computed item A virtual column (as opposed to a column
that is physically stored in the database or cube) that can be
chart template A template that defines the metrics to
calculated by the database during a query, or by Interactive
display in Workspace charts.
Reporting Studio in the Results section. Computed items
child A member with a parent above it in the database are calculations of data based on functions, data items, and
outline. operators provided in the dialog box and can be included in
reports or reused to calculate other data.
choice list A list of members that a report designer can
specify for each dimension when defining the report's point configuration file The security platform relies on an XML
of view. A user who wants to change the point of view for a document to be configured by the product administrator or
dimension that uses a choice list can select only the members installer of the software. The XML document must be
specified in that defined member list or those members that modified to indicate meaningful values for properties,
meet the criteria defined in the function for the dynamic list. specifying locations and attributes pertaining to the
corporate authentication scenario.
clean block A data block that where the database is fully
calculated, if a calculation script calculates all dimensions at connection file See Interactive Reporting connection file
once, or if the SET CLEARUPDATESTATUS command is (.oce).
used in a calculation script.
console The console is displayed on the left side of the
cluster Two or more servers or databases connected Enterprise Metrics workspace. The console is context
together in such a way that they behave as a single resource sensitive, depending on the page displayed.
to share task loads and provide failover support. Clustering
consolidation The process of gathering data from
eliminates one server or database as a single point of failure
dependent entities and aggregating the data to parent
in a system.
entities. For example, if the dimension Year consists of the
clustered bar charts Charts in which categories are viewed members Qtr1, Qtr2, Qtr3, and Qtr4, its consolidation is
side-by-side within a given category; useful for side-by-side Year.
category analysis. Clustering is only done with vertical bar
consolidation rule Identifies the rule that is executed
charts.
during the consolidation of the node of the hierarchy. This
code page A mapping of bit combinations to a set of text rule can contain customer specific formulas appropriate for
characters. Different code pages support different sets of the correct consolidation of parent balances. Elimination
characters. Each computer contains a code page setting for processing can be controlled within these rules.
the character set requirements of the language of the
content Information stored in the repository for any type
computer user. In the context of this document, code pages
of file.
map characters to bit combinations for non-Unicode
encodings. See also encoding. content area The content area is displayed on the right side
of the Workspace and provides specific information for the
column A vertical display of information in a grid or table.
page that you are using.
A column can contain data from one field, derived data from
a calculation, or textual information. context variable A variable that is defined for a task flow to
identify the context of the taskflow instance.
contribution The value added to a parent from a child

entity. Each child has a contribution to its parent.
Glossary 225
conversion rate See exchange rate. custom property A property of a dimension or a dimension
member that is created by a user.
cookie A small piece of information placed on your
computer by a Web site. custom report A complex report from the Design Report
module, composed of any combination of components.
correlated subqueries Subqueries that are evaluated once
for every row in the parent query. A correlated subquery is custom-defined function (CDF) Analytic Services
created by joining a topic item in the subquery with one of calculation functions that are developed in the Java
the topic items in the parent query. programming language and added to the standard Analytic
Services calculation scripting language by means of MaxL.
critical business area (CBA) An individual or a group
See also custom-defined macro (CDM).
organized into a division, region, plant, cost center, profit
center, project team, or process; also called accountability custom-defined macro (CDM) Analytic Services macros
team or business area. that are written with Analytic Services calculator functions
and special macro functions. Custom-defined macros use
critical success factor (CSF) A capability that must be
an internal Analytic Services macro language that enables
established and sustained to achieve a strategic objective. A
the combination of calculation functions and they operate
CSF is owned by a strategic objective or a critical process
on multiple input parameters. See also custom-defined
and is a parent to one or more actions.
function (CDF).
crosstab reporting A type of reporting that categorizes and
cycle through To perform multiple passes through a
summarizes data in a table format. The cells within the table
database while calculating it.
contain summaries of the data that fit within the intersecting
categories. For example, a crosstab report of product sales Dashboard A collection of metrics and indicators that
information could show size attributes, such as Small and provide an interactive summary of your business.
Large, as column headings and color attributes, such as Blue Dashboards enable you to build and deploy analytic
and Yellow, as row headings. The cell in the table where applications.
Large and Blue intersect could contain the total sales of all
data cache A buffer in memory that holds uncompressed
Blue products that are sized Large.
data blocks.
cube A block of data that contains three or more
data cell See cell.
dimensions. An Analytic Services database is a cube.
data file cache A buffer in memory that holds compressed
currency conversion A process that converts currency
data (PAG) files.
values in a database from one currency into another
currency. For example, to convert one U. S. dollar into the data form A grid display that enables users to enter data
European euro, the exchange rate (for example, 0.923702) into the database from an interface such as a Web browser,
is multiplied with the dollar (1* 0.923702). After and to view and analyze data or related text. Certain
conversion, the European euro amount is .92. dimension member values are fixed, giving users a specific
view into the data.
currency partition A dimension type that separates local
currency members from a base currency, as defined in an data function A type of function that computes aggregate
application. A currency partition identifies currency types, values, including averages, maximums, counts, and other
such as Actual, Budget, and Forecast. statistics, that summarize groupings of data.
custom calendar Any calendar created by an administrator. data load rules A set of criteria or rules that determines how
to load data from a text-based file, a spreadsheet, or a
custom dimension A dimension created and defined by
relational data set into a database.
users. For example, channel, product, department, project,
or region could be custom dimensions. data lock A user-controlled mechanism that prevents
changes to data according to specified criteria, such as
period or scenario.
226 Glossary
data mining The process of searching through an Analytic dimension build rules Specifications, similar to data load
Services database for hidden relationships and patterns in a rules, that Analytic Services uses to modify an outline. The
large amount of data. modification is based on data in an external data source file.
data model A representation of a subset of database tables. dimension tab In the Pivot section, the tab that enables you
to pivot data between rows and columns.
data value See cell.
dimension table (1) A table that includes numerous
database connection A file that stores definitions and
attributes about a specific business process. (2) In Enterprise
properties used to connect to data sources. Database
Metrics, a table in a star schema with one part primary key.
connections enable database references to be portable and
(3) In Analytic Integration Services, a container in the OLAP
widely used.
model for one or more relational tables that define a
dense dimension In block storage databases, a dimension potential dimension in Analytic Services.
likely to contain data for every combination of dimension
dimension type A dimension property that enables the use
members. For example, a time dimension is typically a dense
of predefined functionality. Dimensions that are tagged as
dimension because it contains all combinations of all
Time have a predefined calendar functionality.
members. Contrast with sparse dimension.
dimensionality In MaxL DML, the represented
dependent entity An entity that is owned by another entity
dimensions (and the order in which they are represented)
in the organization.
in a set. For example, the following set consists of two tuples
descendant Any member below a parent in the database of the same dimensionality because they both reflect the
outline. For example, in a dimension that includes years, dimensions (Region, Year): { (West, Feb), (East, Mar) }
quarters, and months, the members Qtr2 and April are
direct rate A currency rate that you enter directly in the
descendants of the member Year.
exchange rate table. The direct rate is used for currency
Design Report An interface in Web Analysis Studio for conversion. For example, assume you want to convert
designing custom reports, from a library of components. balances from JPY to USD. In the exchange rate table, you
enter a rate for the period/scenario where the source
destination currency The currency to which the balances
currency is JPY and the destination currency is USD.
are converted. You enter exchange rates and convert from
the source currency to the destination currency. For dirty block A data block containing cells that have been
example, when you convert from EUR to USD, the changed since the last calculation. Upper level blocks are
destination currency is USD. marked as dirty if their child blocks are dirty (that is, they
have been updated).
detail chart A chart that provides the detailed information
that you see in a Summary chart. Detail charts appear in the display type One of three Web Analysis formats saved to
Investigate Section in columns below the Summary charts. the repository: spreadsheet, chart, and pinboard.
For example, if the Summary chart shows a Pie chart, then
dog-ear The flipped page corner in the upper right corner
the Detail charts below represent each piece of the pie.
of the chart header area.
dimension A data category used to organize business data
domain In data mining, a variable representing a range of
for retrieval and preservation of values. Each dimension
navigation within data.
usually contains a hierarchy of related members grouped
within it. For example, a Year dimension often includes drill-down Navigation through the query result set using
members for each time period, such as quarters and months. the organization of the dimensional hierarchy. Drilling
down moves the user perspective from general aggregated
dimension build The process of adding new dimensions
data to more detailed data. For example, drilling down can
and members (without data) to an Analytic Services outline.
reveal the hierarchical relationships between year and
quarters or between quarters and months.
Glossary 227
drill-through The navigation from a data value in one data Dynamic Time Series A process that performs period-to-
source to corresponding data in another data source. date reporting
duplicate alias name A name that occurs more than once dynamic view account An account type indicating that the
in an alias table and that can be associated with two or more account value is calculated dynamically from the data that
different members in a database outline. Duplicate alias you are viewing.
names can be used with duplicate member outlines only.
Edit Data An interface for changing data values and
duplicate member name The multiple occurrence of a sending edits back to Essbase Analytics.
member name in a database. Each occurrence of the name
elimination The process that occurs when certain
represents a different member in the database. For example,
transactions are zeroed out or “eliminated” because they
two members named “New York” exist in the same
were generated between entities within the same
database. One member represents New York state and the
organization.
other member represents New York city.
employee Users responsible for, or associated with, specific
duplicate member outline A database outline that contains
business objects. Employees do not necessarily work for an
duplicate member names.
organization, such as an analyst or consultant. An employee
Dynamic Calc and Store members A member in a block must be associated with a user account for authorization
storage outline that Analytic Server calculates only upon the purposes.
first retrieval of the value. Analytic Server then stores the
encoding A method for mapping bit combinations to text
calculated value in the database. Subsequent retrievals of a
characters for creating, storing, and displaying character
Dynamic Calc and Store member do not require calculating.
text. Each encoding has a name; for example, UTF-8. Within
Dynamic Calc members A member in a block storage a specific encoding, each character maps to a specific bit
outline that Analytic Server calculates only at retrieval time. combination; for example, in UTF-8, uppercase A maps to
Analytic Server discards calculated values after the retrieval HEX41. See also code page and locale.
request is complete.
ending period A period that enables you to adjust the date
dynamic calculation In Analytic Services, a calculation that range shown in the chart. For example, an ending period of
occurs only when you retrieve data on a member that has “month”, produces a chart that shows information through
been tagged as Dynamic Calc or Dynamic Calc and Store. the end of the current month.
The member's values are calculated at retrieval time instead
Enterprise View An Administration Services feature that
of being precalculated during batch calculation.
enables viewing and managing of the Analytic Services
dynamic hierarchy In aggregate storage database outlines environment from a graphical tree view. From Enterprise
only. A hierarchy in which the members are calculated at View, you can operate directly on Analytic Services objects.
retrieval time.
entity A dimension representing organizational units.
dynamic member list A named member set that is a system- Examples include divisions, subsidiaries, plants, regions,
created list based on predefined criteria. The dynamic products, or other financial reporting units.
member list is automatically refreshed whenever the list is
essbase.cfg The name of an optional configuration file for
referenced in the application. As dimension members are
Analytic Services. Administrators may enter parameters and
added and deleted, the dynamic member list automatically
values in this file to customize Analytic Server functionality.
reflects the changes by reapplying the user-defined criteria.
Some of the configuration settings may also be used with
dynamic reference A pointer in the rules file to header Analytic Services clients to override the Analytic Server
records in a data source. settings.
dynamic report A report containing current data. A report

becomes a dynamic report when you run it.
228 Glossary
EssCell The spreadsheet cell retrieve function into an Extract, Transform, and Load (ETL) Data source-specific
Analytic Services database. An EssCell function is entered programs that are used to extract and migrate data to an
into a cell in Essbase Spreadsheet Add-in to retrieve a single application.
database value that represents an intersection of specific
extraction command A type of Analytic Services reporting
database members.
command that handles the selection, orientation, grouping,
ESSCMD A command-line interface that is used to and ordering of raw data extracted from a database. These
perform Analytic Services operations interactively or commands begin with the less than (<) character.
through a batch script file.
extrapolation A means of showing projected figures.
ESSLANG The Analytic Services environment variable that Extrapolation from the current date to the end of the current
defines the encoding that Analytic Server uses to interpret period is displayed on Enterprise Metrics charts with a white
text characters. See also encoding. area of the bar. If a line chart shows extrapolation, the line
that is extrapolated is dotted.
essmsh See MaxL Shell.
fact table The central table in a star join schema,
exceptions Values that satisfy predefined conditions. You
characterized by a foreign key and elements drawn from a
can define formatting indicators or notify subscribing users
dimension table. This table typically contains numeric data
when an exception is generated.
that can be related to all other tables in the schema.
exchange rate A numeric value used to convert one
field A value or item in a data source file that will be loaded
currency to another. For example, to convert 1 USD into
into an Analytic Services database.
EUR, the exchange rate of 0.8936 is multiplied with the U.S.
dollar. The European euro equivalent of $1 is 0.8936. file delimiter One or more characters, such as commas or
tabs, that separate fields in a data source.
exchange rate type An identifier associated with an
exchange rate. Different rate types are used because there filter A constraint placed on data sets to restrict values to
may be multiple rates for a period and year. Users specific criteria. For example, to exclude certain tables,
traditionally define a rate at period end for the average rate metadata, data values, or to control access.
of the period and also a rate for the end of the period.
flow account An unsigned account type that stores periodic
Additional rate types are historical rates, budget rates,
and year-to-date values.
forecast rates, and so on. All these exchange rate types apply
to the same point in time. folder A file that contains other files for the purpose of
ordering and structuring a hierarchy.
expense account An account type that stores periodic and
year-to-date values that decrease net worth if the value is footer The text or images that are displayed at the bottom
positive. of each page in a report. A footer can contain a page number,
date, company logo, document title or file name, author
Extensible Markup Language (XML) A language
name, and so on. Footers can contain dynamic functions
comprised of a set of tags used to assign attributes to data
and static text.
that can be interpreted between applications based on the
schema used. format The visual characteristics of a document or a report
object.
external authentication Logging on to Hyperion
applications by means of user information stored outside formula A combination of operators and calculation
the application, typically in a corporate user directory such functions, as well as dimension names, member names, and
as MSAD or NTLM. numeric constants, used to perform specific calculations on
members of a database.
externally triggered events Non-time-based events that are
used to schedule job runs. frame An area of the desktop where information is
displayed to the user. There are two main areas on the
desktop: the navigation frame and the workspace frame.
Glossary 229
free-form grid A data object that presents manually entered highlighting Depending on your configuration, you may
data and data from different types of data sources, enabling see highlighting applied to a chart cell value or ZoomChart
you to integrate data in dynamic calculations. detail values. A value can be highlighted in red (indicating
the value is bad), yellow (indicating that the value is a
free-form reporting A method of creating reports in which
warning), or green (indicating the value is good).
you type members of dimensions or report script
commands in a worksheet. holding company An entity that is part of a legal group of
entities, and has either a direct or indirect investment in all
function A predefined routine that returns a value, a range
the other entities within the legal group.
of values, a Boolean value, or one or more database
members. host A server on which applications and services are
installed.
generation A layer in a hierarchical tree structure that
defines member relationships in a database. Generations are host properties Properties pertaining to a host, or if the
ordered incrementally from the top member of the host has multiple Install_Homes, to an Install_Home. The
dimension (generation 1) down to the child members. host properties are configured from the LSC.
generation name A unique name that describes a Hybrid Analysis The integration of a relational database
generation. with an Analytic Services multidimensional database so that
lower-level data remains in the relational database and is
generic jobs Jobs that are neither Production Reporting
mapped to summary-level data residing in the Analytic
nor Interactive Reporting jobs.
Services database. Hybrid Analysis enables Analytic Services
global report command A command that is executed when to take advantage of the mass scalability of a relational
it occurs in the report script file and that stays in effect until database while maintaining a multidimensional view of the
the end of the report file or until another global command data in a live environment.
replaces it.
hyperlink A link to a file, Web page, or an HTML page on
grid POV A means for specifying members for a dimension an intranet.
on a grid without placing the dimension on the row,
Hypertext Markup Language (HTML) A programming
column, or page intersection. A report designer can set the
language of tags that specify how Web browsers display data.
POV values at the grid level, preventing the user POV from
affecting the grid. If a dimension has only one value for the identity A unique identification of one valid user or group
entire grid, the dimension should be put into the grid POV existing on an external authentication repository.
instead of the row, column, or page.
image bookmarks Graphic links to Web personal pages or
group A container that enables the assignment of similar repository items.
access permissions to a group of users.
IMPACTED status A consolidation status indicating that
GUI Graphical user interface the data that rolls up to this parent entity has changed.
header record One or more records at the top of a data implied share A member with only one child, or a member
source. Header records describe the contents of the data with multiple children of which only one child is
source. consolidated. For this reason the parent and child share the
same value.
High Availability Server A server running the Analytic
High Availability Services software that manages requests inactive group A group that cannot access the system
between the client and Analytic Servers, in addition to because an administrator inactivated it.
providing various services, such as event handling and
inactive service A service that is on hold or excluded from
clustering.
the list of services to be started.
230 Glossary
INACTIVE status A consolidation status indicating this Interactive Reporting connection file (.oce) Files that
entity is not active for the current period. encapsulate database connection information. Interactive
Reporting connection files (.oce) specify the database API
inactive user A user who cannot access the system because
(ODBC, SQL*Net, etc.), database software, the network
an administrator inactivated the user account.
address of the database server, and your database user name.
income account An account type that stores periodic and Administrators create and publish Interactive Reporting
year-to-date values that increase net worth if the value is connection files (.oce).
positive.
interactive user Interactive users can review and approve
index (1) A method that Analytic Services uses to retrieve budgets, set up e-mail notification to other users, create
block storage data. The retrieval is based on the Web-based data forms, create worksheets using Hyperion
combinations of sparse dimensions. (2) The index file. Smart View for Office, create reports using Hyperion
Reports, create and launch integrations using Hyperion
index cache A buffer in memory that holds index pages.
Application Link, create and launch business rules using
index entry A pointer to an intersection of sparse Hyperion Business Rules and/or Analytic Services, enter
dimensions. Each index entry points to a data block on disk and view data in Web data forms and Hyperion Smart View.
and locates a cell within the block by means of an offset.
intercompany elimination See elimination.
index file A file that Analytic Services uses to store data
intercompany matching The process of comparing
retrieval information from block storage databases. The
balances for pairs of intercompany accounts within an
index file resides on disk and contains index pages.
application. Intercompany receivables are typically
index page A subdivision of an index file containing entries matched or compared to intercompany payables. The
that point to data blocks. system uses these matching accounts to eliminate any
intercompany transactions from your organization's
input block A type of data block that has at least one loaded
consolidated totals.
data value.
intercompany matching report A report that compares the
input data Any data that is loaded from a data source and
balances of a group of intercompany accounts and indicates
is not generated by calculating the database.
if the accounts are in balance or out of balance for any
Install_Home A variable name for the path and directory branch of an organization.
where Hyperion applications are installed. Refers to one
interdimensional irrelevance A situation in which a
instance of a Hyperion application when multiple
specific dimension does not intersect with other
applications are installed on the same computer.
dimensions. The data is not irrelevant, but because the data
integration Process that is run to move data between in the specific dimension cannot be accessed from the other
Hyperion applications using Shared Services. Data dimensions, those other dimensions are not relevant to the
integration definitions specify the data moving between a specific dimension.
source application and a destination application, and enable
intersection A unit of data representing the intersection of
the data movements to be grouped, ordered, and scheduled.
dimensions in a multidimensional database; also, a
intelligent calculation A calculation method that tracks worksheet cell.
which data blocks have been updated since the last
Investigation See drill-through.
calculation.
isolation level An Analytic Services Kernel setting that
determines the lock and commit behavior of database
operations. Choices are committed access and
uncommitted access.
iteration A “pass” of the budget or planning cycle in which

the same version of data is revised and promoted.
Glossary 231
Java Database Connectivity (JDBC) A client-server level 0 block A data block that is created for sparse member
communication protocol used by Java based clients and combinations when all of the members of the sparse
relational databases. The JDBC interface provides a call- combination are level 0 members.
level API for SQL-based database access.
level 0 member A member that has no children.
job output Files or reports produced from running a job.
liability account An account type that stores “point in
job parameters The compile time and runtime values time” balances that represent a company's liabilities.
necessary to run a job. Examples of liability accounts include accrued expenses,
accounts payable, and long term debt.
job parameters Reusable, named job parameters that are
accessible only to the user who created them. life cycle management The process of managing
application information from inception to retirement.
jobs A collection of documents with special properties and
that can be executed to generate output. A job can contain line chart A chart that displays one to 50 data sets, with
Interactive Reporting documents, Production Reporting automatic, uniform spacing along the X-axis. Each data set
documents, or generic documents. is rendered by a line. A line chart can optionally show each
line set stacked on the preceding ones, using either the
join A link between two relational database tables based on
absolute value or a normalized value from 0 to 100 percent.
common content in a column or record or a relational
database concept indicating a link between two topics. A line item detail The lowest level of detail in an account.
join typically occurs between identical or similar items
link (1) Fixed references to a specific object in the
within different topics. For example, a row record in the
repository. Links can reference folders, files, shortcuts, and
Customer table is joined to a related record in the Orders
other links using unique identifiers. (2) The point during
table when the Customer ID value for the record is the same
the execution of a taskflow instance where the activity in one
in each table.
stage ends and control passes to another stage, which starts.
journal entry (JE) A set of debit/credit adjustments to
link condition A logical expression that is evaluated by the
account balances for a scenario and period.
taskflow engine to decide the sequence of stage execution
JSP Java Server Pages. within a taskflow.
latest A key word that is used to extract data values based linked data model Documents that are linked to a master
on the member defined as the latest period of time. copy in a repository
layer (1) The horizontal location of members in a linked partition A form of shared partition that provides
hierarchical structure, specified by generation (top down) the ability to use a data cell to link together two different
or level (bottom up). (2) Position of objects relative to other databases. When a user clicks a linked cell in a worksheet,
objects. For example, in the Sample Basic database, Qtr1 and for example, Analytic Services opens a new sheet displaying
Qtr4 are in the same layer. Thus, Qtr1 and Qtr4 are also in the dimensions in the second database. The user can then
the same generation. However, in a different database with drill down into the available dimensions in the second
a ragged hierarchy, Qtr1 and Qtr4 might not necessarily be database.
in the same level simply because they are in the same
linked reporting object (LRO) A cell-based link to an
generation.
external file such as cell notes, URLs, or files that contain
legend box An informative box containing color-keyed text, audio, video, or pictures. Note that support of Analytic
labels to identify the data categories of a given dimension. Services LROs in Financial Reporting applies only to cell
notes at this time (by way of Cell Text functions).
level A layer of a hierarchical tree structure that defines
database member relationships. Levels are ordered local currency Input currency type. When an input
incrementally from the bottom member of the dimension currency type is not specified, the local currency matches
(level 0) up through the parent members. the entity's base currency.
232 Glossary
local report object A report object that is not linked to a Map Navigator A feature that displays your current
Financial Reporting report object in Explorer. Contrast with position on a Strategy, Accountability or Cause and Effect
linked reporting object (LRO). map. Your current position is indicated by a red outline on
the Map Navigator.
local results Results of other queries within the same data
model. These results can be dragged into the data model to master data model A data model that exists independently
be used in local joins. Local results are displayed in the and is referenced as a source by multiple queries. When you
catalog when requested. use a master data model, the text “Locked Data Model” is
displayed in the Content pane of the Query section. Thus,
locale A computer setting that identifies the local language
the data model is linked to the master data model displayed
and cultural conventions such as the formatting of currency
in the Data Model section, which may be hidden by an
and dates, sort order of the data, and the character set
administrator.
encoding to be used on the computer. Analytic Services uses
only the encoding portion of the locale. See also encoding mathematical operator A symbol that defines how data is
and ESSLANG. calculated. A mathematical operator can be any of the
standard mathematical or Boolean operators; for example,
locale header record An additional text record, at the
+, -, *, /, and %. Mathematical operators are used in
beginning of some non-Unicode-encoded text files such as
formulas and outlines.
scripts, that identifies the encoding locale.
MaxL The multidimensional database access language for
location alias A descriptor that identifies a data source. The
Analytic Services, consisting of a data definition language
location alias specifies a server, application, database, user
(MaxL DDL) and a data manipulation language (MaxL
name, and password. Location aliases are set by DBAs at the
DML). See also MaxL DDL, MaxL DML, and MaxL Shell.
database level using Administration Services Console,
ESSCMD, or the API. MaxL DDL Data definition language used by Analytic
Services for batch or interactive system-administration
locked A user-invoked process that prevents the data from
tasks.
being modified by any process, user, or other means.
MaxL DML Data manipulation language used in Analytic
locked data model Data models that cannot be modified by
Services for data query and extraction.
a user.
MaxL Perl Module A Perl module (essbase.pm) that is part
LOCKED status A consolidation status indicating that an
of the MaxL DDL component of Analytic Services. The
entity contains data that is locked for the specified period.
essbase.pm module can be added to the Perl package to
Log Analyzer An Administration Services feature that provide access to Analytic Services databases from Perl
enables filtering, searching, and analysis of Analytic Services programs.
logs.
MaxL Script Editor A script-development environment
LRO See linked reporting object (LRO). provided by Administration Services Console. The MaxL
Script Editor is an integrated alternative to using a text
LSC services The services that are configured with the Local
editor and the MaxL Shell for creating, opening, editing, and
Service Configurator. They include Global Services
running MaxL scripts for Analytic Services system
Manager (GSM), Local Services Manager (LSM), Session
administration.
Manager, Authentication Service, Authorization Service,
Publisher Service, and in some contexts, Data Access Service MaxL Shell An interface for passing MaxL statements to
(DAS) and Interactive Reporting Service. Analytic Server. The MaxL Shell executable file, located in
the bin directory for Analytic Services, is named essmsh
managed server An application server process running in
(UNIX) or essmsh.exe (Windows).
its own Java Virtual Machine (JVM).
manual stage A stage that requires human intervention to

complete the stage.
Glossary 233
MDX (multidimensional expression) The language used metadata sampling The process of retrieving a sample of
to give instructions to OLE DB for OLAP- compliant the members of a selected dimension in a drill-down
databases, as SQL is the language used for relational operation.
databases. When you build the OLAPQuery section's
metadata security Security set at the member level to
Outliner, Intelligence Clients translate your requests into
control users from accessing certain members in an outline.
MDX instructions. When you process the query, MDX is
sent to the database server. The server returns a collection metaoutline In Analytic Integration Services, a template
of records to your desktop that answer your query. See also containing the structure and rules for creating an Analytic
SQL spreadsheet. Services outline from an OLAP model.
measures Numeric values in an OLAP database cube that metric A numeric measurement computed from your
are available for analysis. Measures may be margin, cost of business data. Metrics help you assess the performance of
goods sold, unit sales, budget amount, and so on. See also your business and analyze trends in your company.
fact table.
migration The process of copying an application or users
member A discrete component within a dimension. A from one environment or computer to another.
member identifies and differentiates the organization of
MIME Type (Multipurpose Internet Mail Extension) An
similar units. For example, a time dimension might include
attribute that describes the format of data in an item, so that
such members as Jan, Feb, and Qtr1.
the system knows which application to launch to open the
member list A named group, system- or user-defined, that object. A file's mime type is determined either by the file
references members, functions, or other member lists extension or the HTTP header. Plug-ins tell browsers what
within a dimension. mime types they support and what file extensions
correspond to each mime type.
member load In Analytic Integration Services, the process
of adding new dimensions and members (without data) to mini report A mini report is a component of a report, and
an Analytic Services outline. includes layout, content, hyperlinks, and the actual query
or queries to load the report. Each report can include one
member selection report command A type of Report
or more minireports.
Writer command that selects ranges of members based on
database outline relationships, such as sibling, generation, missing data (#MISSING) A marker indicating that data in
and level. the labeled location does not exist, contains no value, or was
never entered or loaded. For example, missing data exists
member-specific report command A type of Report Writer
when an account contains data for a previous or future
formatting command that is executed as it is encountered
period but not for the current period.
in a report script. The command affects only the member
to which it is associated and executes the format command model (1) In data mining, a collection of an algorithm's
before it processes the member. findings about examined data. A model can be used
(applied) against a wider set of data to generate useful
merge A data load option that clears existing values from
information about that data. (2) A file or string of content
the accounts specified in the data load file and then replaces
containing an application-specific representation of data.
them with the values in the data load file. Unlike the Replace
Models are the basic data managed by Shared Services.
option, the Merge option clears only the values from the
Models are of two major types: dimensional and non-
accounts specified in the load file.
dimensional application objects. (3) In Business Modeling,
metadata A set of data that defines and describes the a network of boxes connected to represent and calculate the
properties and attributes of the data stored in a database or operational and financial flow through the area being
used by an application. Examples of metadata are examined.
dimension names, member names, properties, time
monetary A money-related value.
periods, and security.
234 Glossary
multidimensional database A method of organizing, OK status A consolidation status indicating that an entity
storing, and referencing data through three or more has already been consolidated, and that data has not
dimensions. An individual value is the intersection point for changed below it in the organization structure.
a set of dimensions.
OLAP Online Analytical Processing.
named set In MaxL DML, a set with its logic defined in the
OLAP Metadata Catalog In Analytic Integration Services,
optional WITH section of a MaxL DML query. The named
a relational database containing metadata describing the
set can be referenced multiple times in the query.
nature, source, location, and type of data that is pulled from
native authentication The process of authenticating a user the relational data source.
name and password from within the server or application.
OLAP model In Analytic Integration Services, a logical
nested column headings A column heading format for model (star schema) that is created from tables and columns
report columns that displays data from more than one in a relational database. The OLAP model is then used to
dimension. For example, a column heading that contains generate the structure of a multidimensional database.
Year and Scenario members is a nested column. The nested
online analytical processing (OLAP) A multidimensional,
column heading shows Q1 (from the Year dimension) in
multiuser, client-server computing environment for users
the top line of the heading, qualified by Actual and Budget
who analyze consolidated enterprise data in real time. OLAP
(from the Scenario dimension) in the bottom line of the
systems feature drill-down, data pivoting, complex
heading.
calculations, trend analysis, and modeling.
NO DATA status A consolidation status indicating that
Open Database Connectivity (ODBC) Standardized
this entity contains no data for the specified period and
application programming interface (API) technology that
account.
allows applications to access multiple third-party databases.
non-dimensional model A type of model in Shared
organization A hierarchy of entities that defines each entity
Services that includes application objects such as security
and their relationship to others in the hierarchy.
files, member lists, calculation scripts, and Web forms.
origin The intersection of two axes.
non-unique member name See duplicate member name.
outline The database structure of a multidimensional
note Additional information associated with a box,
database, including all dimensions, members, tags, types,
measure, scorecard or map element.
consolidations, and mathematical relationships. Data is
null value A value that is absent of data. Null values are not stored in the database according to the structure defined in
equal to zero. the outline.
numeric attribute range A feature used to associate a base outline synchronization For partitioned databases, the
dimension member that has a discrete numeric value with process of propagating outline changes from one database
an attribute that represents a range of values. For example, to another database.
to classify customers by age, an Age Group attribute
P&L accounts (P&L) Profit and loss accounts. Refers to a
dimension can be defined that contains members for the
typical grouping of expense and income accounts that
following age ranges: 0-20, 21-40, 41-60, and 61-80. Each
comprise a company's income statement.
member of the Customer dimension can be associated with
an Age Group range. Data can then be retrieved based on page A display of information in a grid or table often
the age ranges rather than based on individual age values. represented by the Z-axis. A page can contain data from one
field, derived data from a calculation, or text.
ODBC Open Database Connectivity. A database access
method used from any application without regard to how page file Analytic Services data file.
the database management system (DBMS) processes the
information.
Glossary 235
page heading A type of report heading that lists members pattern matching The ability to match a value with any or
that are represented on the current page of the report. All all characters of an item that is entered as a criterion. A
data values on the page have the members in the page missing character may be represented by a wild card value
heading as a common attribute. such as a question mark (?) or an asterisk (*). For example,
“Find all instances of apple” returns apple, but “Find all
page member A member that determines the page axis.
instances of apple*” returns apple, applesauce,
palette A JASC compliant file with an extension of PAL. applecranberry, and so on.
Each palette contains 16 colors that complement each other
percent consolidation The portion of a child's values that
and can be used to set the color elements of a dashboard.
is consolidated to its parent.
parallel calculation An optional calculation setting.
percent control Identifies the extent to which an entity is
Analytic Services divides a calculation into tasks and
controlled within the context of its group.
calculates some of the tasks at the same time.
percent ownership Identifies the extent to which an entity
parallel data load In Analytic Services, the concurrent
is owned by its parent.
execution of different stages of a single data load by multiple
process threads. performance indicator An image file used to represent
measure and scorecard performance based on a range you
parallel export The ability to export Analytic Services data
specify; also called a status symbol. You can use the default
to multiple files. This may be faster than exporting to a single
performance indicators or create an unlimited number of
file, and it may resolve problems caused by a single data file
your own.
becoming too large for the operating system to handle.
periodic value method (PVA) A process of currency
parent adjustments The journal entries that are posted to
conversion that applies the periodic exchange rate values
a child in relation to its parent.
over time to derive converted results.
parents The entities that contain one or more dependent
permission A level of access granted to users and groups
entities that report directly to them. Because parents are
for managing data or other users and groups.
entities and associated with at least one node, they have
entity, node, and parent information associated with them. persistence The continuance or longevity of effect for any
Analytic Services operation or setting. For example, an
partition area A subcube within a database. A partition is
Analytic Services administrator may limit the persistence of
composed of one or more areas. These areas are composed
user name and password validity.
of cells from a portion of the database. For replicated and
transparent partitions, the number of cells within an area personal pages Your personal window to information in
must be the same for the data source and the data target to the repository. You select what information to display and
ensure that the two partitions have the same shape. If the its layout and colors.
data source area contains 18 cells, the data target area must
personal recurring time events Reusable time events that
also contain 18 cells to accommodate the number of values.
are accessible only to the user who created them.
partitioning The process of defining areas of data that are
personal variable A named selection statement of complex
shared or linked between data models. Partitioning can
member selections.
affect the performance and scalability of Analytic Services
applications. perspective A category used to group measures on a
scorecard or strategic objectives within an application. A
perspective can represent a key stakeholder (such as a
customer, employee, or shareholder/financial) or a key
competency area (such as time, cost, or quality).
pie chart A chart that shows one data set segmented in a pie
formation.
236 Glossary
pinboard One of the three data object display types. preserve formulas The process of keeping user-created
Pinboards are graphics, composed of backgrounds and formulas within a worksheet while retrieving new data.
interactive icons called pins. Pinboards require traffic
primary measure A high-priority measure that is more
lighting definitions.
important to your company and business needs than many
pins Interactive icons placed on graphic reports called other measures. Primary measures are displayed in the
pinboards. Pins are dynamic. They can change images and Contents frame and have Performance reports.
traffic lighting color based on the underlying data values and
product In Shared Services, a product is an application
analysis tools criteria.
type, such as Planning or Performance Scorecard.
pivot The ability to alter the perspective of retrieved data.
Production Reporting A specialized programming
When Analytic Services first retrieves a dimension, it
language for data access, data manipulation, and creating
expands data into rows. You can then pivot or rearrange the
Production Reporting documents.
data to obtain a different viewpoint.
project An instance of Hyperion products that are grouped
planner Planners, who comprise the majority of users, can
together to comprise an implementation. For example, a
input and submit data, use reports that others create,
Planning project may consist of a Planning application, an
execute business rules, use task lists, enable e-mail
Analytic Services cube, and a Financial Reporting Server
notification for themselves, and use Smart View.
instance.
planning unit A slice of data at the intersection of a
promote The action to move a data unit to the next review
scenario, version, and entity. It is the basic unit for
level, allowing a user having the appropriate access to review
preparing, reviewing, annotating, and approving plan data.
the data. For example, an analyst may promote the data unit
plot area The area bounded by the X, Y, and Z axes; For pie to the next level for his supervisor's review.
charts, the rectangular area immediately surrounding the
promotion The process of transferring artifacts from one
pie.
environment or machine to another; for example, from a
plug account An account in which the system stores any testing environment to a production environment.
out of balance differences between intercompany account
property A characteristic of an artifact, such as size, type,
pairs during the elimination process.
or processing instructions.
POV (point of view) A feature that lets you work with
provisioning The process of granting users and groups
dimension members that are not assigned to a row, column,
specific access permissions to Hyperion resources.
or page axis. For example, you could assign the Currency
dimension to the POV and select the Euro member. By proxy server A server that acts as an intermediary between
selecting this POV in a data form, all the data in the form is a workstation user and the Internet to ensure security.
displayed in Euro values.
public job parameters Reusable, named job parameters
precalculation The process of calculating the database created by an administrator and accessible to users who have
prior to user retrieval. the requisite access privileges.
precision Number of decimal places displayed in a number. public recurring time events Reusable time events created
by an administrator and accessible through the access
predefined drill paths Paths that enable you to drill directly
control system.
to the next level of detail, as defined in the data model.
PVA See periodic value method (PVA).
presentation A playlist of Web Analysis documents,
enabling reports to be grouped, organized, ordered, qualified name A member name in a qualified format that
distributed, and reviewed. Presentations are not reports differentiates duplicate member names in a duplicate
copied into a set. A presentation is a list of pointers member outline. For example, [Market].[East].[State].
referencing reports in the repository. [New York] or [Market].[East].[City].[New York]
Glossary 237
query To request information from a data provider. For Report Extractor An Analytic Services component that
example, queries are used to access a relational data source. retrieves report data from the Analytic Services database
when a report script is run.
query governor An Analytic Integration Server parameter
or Analytic Server configuration setting that controls the report object A basic element in report designs. Report
duration and size of the queries made to the data source. objects have specific properties that define their behavior or
appearance. Report objects include text boxes, grids,
range A set of values that includes an upper and lower limit,
images, and charts.
and the values that fall between the limits. A range can
consist of numbers, amounts, or dates. report script A text file containing Analytic Services Report
Writer commands that generate one or more production
reconfigure URL URL used to reload servlet configuration
reports.
settings dynamically when a user is already logged on to the
Workspace. Report Viewer An Analytic Services component that
displays the complete report after a report script is run.
record In a database, a group of fields that make up one
complete entry. For example, a record about a customer reporting currency The currency in which an enterprise
might contain fields for name, address, telephone number, prepares its financial statements. Currency is converted
and sales data. from local currencies to one or more reporting currencies.
The converted reporting currency values are stored.
recurring template A journal template used to make
identical adjustments in every period. resources Objects or services that the system manages.
Examples of a resource include a role, user, group, file, job,
recurring time event An event that specifies a starting point
publisher service, and so on.
and the frequency for running a job.
restore An operation to reload data and structural
redundant data Duplicate data blocks that Analytic
information after a database has been damaged or
Services retains during transactions until Analytic Services
destroyed. The restore operation is typically performed after
commits the updated blocks.
you shut down and restart the database.
regular journal A feature used to enter one-time
restructure An operation to regenerate or rebuild the
adjustments for one period only. Regular journals can be
database index and, in some cases, the data files.
balanced, balanced by entity, or unbalanced.
result frequency The algorithm used to create a set of dates
relational database A type of database that stores data in
for the collection and display of results.
the form of related two-dimensional tables. Contrast with
multidimensional database. review level A Process Management review status indicator
that represents the process unit level. Review levels include
replace A data load option that clears the existing values
the following: Not Started, First Pass, Review Level 1, Review
from all accounts for the periods specified in the data load
Level 2 ... Review Level 10, Submitted, Approved, and
file, and then loads the values from the data load file. If an
Published.
account is not specified in the load file, its values for the
specified periods are cleared during the load. role The means by which access permissions are granted to
users and groups for Hyperion resources.
replicated partition A portion of a database, defined
through Partition Manager, that is used to propagate an roll-up See consolidation.
update to data that is mastered at one site to a copy of data
root member The highest member in a dimension branch.
that is stored at another site. Users are able to access the data
as though it were part of their local database. row heading A report heading that lists members down a
report page. The members are listed under their respective
replication In Analytic High Availability Services, the
row names.
copying of data from one Analytic Services application
database to another.
238 Glossary
RSC services The services that are configured with the scorecard report A report that presents the results and
Remote Service Configurator. They include Repository detailed information about scorecards attached to
Service, Service Broker, Name Service, Event Service, and employees, strategy elements, and accountability elements.
Job Service.
secondary measure A low-priority measure that is less
rules User-defined formulas. important to you than primary measures. Secondary
measures do not have Performance reports but can be used
runtime prompt A system variable that allows values to be
on scorecards and to create dimension measure templates.
entered during the execution of an allocation process.
Values can be members, strings, or numbers. Section pane Lists all sections that are available in the
current Intelligence Client document.
sampling The process of selecting a representative portion
of an entity for the purpose of determining the security agent A Web access management solutions
characteristics of that entity. See also metadata sampling. provider employed by companies to protect Web resources;
also known as Web security agent. The Netegrity SiteMinder
saved assumptions Planning assumptions, created globally
product is an example of a security agent.
or locally, that can be named, saved and referenced in
planning methods and allocations to help drive plan and security platform A framework enabling Hyperion
budget values. applications to use external authentication and single sign-
on using the security platform driver.
scale The range of values on the Y axis of a chart.
serial calculation The default calculation setting. Analytic
scaling Determines how currency values are displayed in a
Services divides a calculation pass into tasks and calculates
data form or report: in whole numbers, tens, hundreds,
one task at a time.
thousands, millions, and so on.
services Resources that provide the ability to retrieve,
scenario A dimension that specifies a data classification.
modify, add, or delete business items. Some services are
Examples include Actuals, Budget, Forecast1, and
Authorization, Authentication, Global Service Manager
Forecast2.
(GSM).
schedule Specify the job to run and the time and job
servlet A piece of compiled code executable by a Web
parameter list for running the job.
server.
scope The area of data encompassed by any Analytic
Servlet Configurator A software utility for configuring all
Services operation or setting; for example, the area of data
of the locally installed servlets.
affected by a security setting. Most commonly, scope refers
to three levels of granularity, where higher levels encompass session The time between login and logout for a user
lower levels. From highest to lowest, these levels are as connected to Analytic Server.
follows: the entire system (Analytic Server), applications on
set In MaxL DML, a required syntax convention for
Analytic Server, or databases within Analytic Server
referring to a collection of one or more tuples. For example,
applications. See also persistence.
in the following MaxL DML query, SELECT { [100-10] }
score The level at which specified targets are being ON COLUMNS FROM Sample.Basic { [100-10] } is a set.
achieved. It is usually expressed as a percentage of the target
shared application An application in Shared Services that
for a given time period.
enables two or more products to share their models. See also
scorecard Business Object used to represent the progress model.
of an employee, strategy element, or accountability element
shared member A member that shares storage space with
toward specific goals. Scorecards ascertain this progress
another member of the same name. A storage property
based on the data collected for each measure and child
designates members as shared. The use of shared members
scorecard you add to the scorecard.
prevents duplicate calculation of members that occur more
than once in an Analytic Services outline.
Glossary 239
Shared Services Application enabling users to share data stacked charts A chart where the categories are viewed on
between supported Hyperion products by publishing data top of one another for visual comparison. This type of chart
to Shared Services and running data integrations. is useful for subcategorizing within the current category.
Stacking can be used from the Y and Z axis in all chart types
sibling A child member at the same generation as another
except pie and line. When stacking charts the Z axis is used
child member and having the same immediate parent. For
as the Fact/Values axis.
example, the members Florida and New York are children
of East and siblings of each other. stage A description of a task that forms one logical step
within a taskflow, usually performed by a single individual.
single sign-on A feature that enables you to access multiple
A stage can be manual or automated.
Hyperion products after logging on just once using external
credentials. stage action For automated stages, the action that is
invoked to execute the stage.
slicer In MaxL DML, the section at the end of a query that
begins with and includes the keyword WHERE. standard dimension A dimension that is not an attribute
dimension.
smart tags Predefined properties that associate available
actions with keywords in Microsoft Office applications. standard journal template A journal function used to post
Smart tags are the mechanism by which the Hyperion menu adjustments that have common adjustment information for
is displayed and the end user can import content from each period. Instead of creating a new regular journal every
Hyperion System 9 BI+ or use functions to display month, you can create a standard template that contains the
information from Financial Management or Analytic common account IDs, entity IDs, or amounts. You can then
Services. use the template as the basis for many regular journals that
contain similar adjustment information.
SmartCut A link to an item in the repository, in the form
of a special URL. Start in Play The quickest method for creating a Web
Analysis document. The Start in Play process requires you
snapshot Read-only data from a specific point in time.
to specify a database connection, then assumes the use of a
source currency The currency from which the balances spreadsheet data object. Start in Play uses the highest
originate and are converted. You enter exchange rates and aggregate members of the time and measures dimensions to
convert from the source currency to the destination automatically populate the rows and columns axes of the
currency. For example, when you convert from EUR to spreadsheet.
USD, the source currency is EUR.
stored hierarchy In aggregate storage databases outlines
sparse dimension In block storage databases, a dimension only. A hierarchy in which the members are aggregated
unlikely to contain data for all combinations of dimension according to the outline structure. Stored hierarchy
members when compared to other dimensions. For members have certain restrictions, for example, they cannot
example, not all customers have data for all products. contain formulas.
SPF files Printer-independent files created by a Production strategic objective (SO) A long-term goal defined for an
Reporting server that contains a representation of the actual organization that is stated in concrete terms whose progress
formatted report output, including fonts, spacing, headers, is determined by measuring results. Each strategic objective
footers, and so on. is associated with one perspective in your application, has
one parent, the entity, and is a parent to critical success
Spotlighter A tool that enables color coding based on
factors or other strategic objectives. It also has measures
selected conditions.
associated with it.
SQL spreadsheet A data object that displays the result set
Strategy map A detailed representations of how your
of a SQL query.
organization translates its high-level mission and vision
statements into lower-level, constituent strategic goals and
objectives.
240 Glossary
structure view A view that displays a topic as a list of system extract A feature that allows you to transfer data
component items allowing users to see and quickly select from an application's metadata into an ASCII file.
individual data items. Structure view is the default view
target The expected result for a measure for a specified
setting.
period of time, such as a day, quarter, month and so on. You
Structured Query Language The language used to give can define multiple targets for one measure.
instructions to relational databases. When you build the
task list A listing of tasks for a user along with detailed status
Query section's Request, Limit, and Sort lines, Interactive
information for each task.
Reporting translate your requests into SQL instructions.
taskflow The automation of a business process in whole or
subscribe Register an interest in an item or folder to receive
in part, during which tasks are passed from one taskflow
automatic notification whenever the item or folder is
participant to another for actions, according to a set of
updated.
procedural rules.
Summary chart A chart that is displayed at the top of each
taskflow definition The representation of the business
chart column in the Investigate Section and plots metrics at
process in the taskflow management system, which enables
the summary level, meaning that it rolls up all of the Detail
the process to be automated. The taskflow definition
charts shown below in the same column. All colors shown
consists of a network of stages and their relationships;
in a stacked bar, pie, or lines Summary chart also appear
criteria to indicate the start and end of the taskflow; and
above each Drill button of the Detail charts and extend
information about individual stages, such as participants,
across the row, acting as the key.
associated applications, associated activities, and so on.
super service A special service used by the
taskflow instance The representation of a single instance of
startCommonServices script to start the RSC services.
a taskflow including its state and associated data.
supervisor A defined type of user who has full access to all
taskflow management system A system that defines,
applications, databases, related files, and security
creates, and manages the execution of a taskflow. It enables
mechanisms for a server.
the creation of taskflow definitions, interaction with
supporting detail Calculations and assumptions from taskflow participants (users or applications), and the
which the values of cells are derived. Supporting detail can launching of other applications during the execution of a
include text, values, and operators that define how data business process.
aggregates.
taskflow participant The resource that performs the task
suppress rows The option to exclude rows that contain associated with the taskflow stage instance. The taskflow
missing values and to underscore characters from system requires a participant for manual and automated
spreadsheet reports. stages. For a manual stage, the task is shown on the task list
for the user to execute the task. For an automated stage,
symmetric multiprocessing (SMP) A server architecture
Shared Services, along with the application, executes the
that enables multiprocessing and multithreading. Analytic
task. For automated stages, the application executes the task
Server supports multiple threads over SMP servers
on behalf of the participant.
automatically. Thus, performance is not significantly
degraded when a large number of users connect to an single TCP/IP See Transmission Control Protocol/Internet Protocol
instance of Analytic Server simultaneously. (TCP/IP).
sync The ability to synchronize models in Shared Services template A predefined format that is designed to retrieve
with models in the application. data on a regular basis and in a consistent format.
synchronized The condition that exists when the latest time dimension A dimension that defines the time period
version of a model resides in the application and in Shared that the data represents, such as fiscal of calendar periods.
Services. See also model.
time events Triggers for execution of jobs.
Glossary 241
time scale A scale that enables you to see the metrics by a transparent partition A form of shared partition that
specific period in time, such as monthly or quarterly. provides the ability to access and manipulate remote data
transparently as though it is part of a local database. The
time series reporting A process of reporting data based on
remote data is retrieved from the data source each time a
a calendar date (for example, year, quarter, month, or
request is made. Any updates made to the data are written
week).
back to the data source and become immediately accessible
token An encrypted identification of one valid user or to local data target users and transparent data source users.
group on an external authentication system.
trend How the performance of a measure or scorecard
top and side labels In the Pivot section, the column and changed since the last reporting period or a date that you
row headings on the top and sides of the pivot. These define specify.
categories by which the numeric values are organized.
triangulation A means of converting balances from one
top-level member A dimension member at the top of the currency to another via a third common currency. In
tree in a dimension outline hierarchy, or the first member Europe, this is the euro for member countries. For example,
of the dimension in sort order if there is no hierarchical to convert from French franc to Italian lira, the common
relationship among dimension members. The top-level currency is defined as European euro. Therefore, in order
member name is generally the same name as the dimension to convert balances from French franc to Italian lira,
name if a hierarchical relationship exists. balances are converted from French franc to European euro
and from European euro to Italian lira.
trace level A means of defining the level of detail captured
in the log file. triangulation currency A currency through which
exchange rates can be derived. For example, if you set up the
traffic lighting Color-coding of report cells, or pins based
Euro/Dollar exchange rate and the Euro/Yen rate, the
on a comparison of two dimension members, or on fixed
Dollar/Yen rate can be derived by using Euro as the
limits.
triangulation currency.
transformation (1) The process of transforming an artifact
triggers An Analytic Services feature that enables efficient
so that it functions properly in the destination environment
monitoring of data changes in a database. If data breaks rules
after application migration. (2) In data mining, a way to
that you specified, Analytic Services alerts the user or system
modify data (bidirectionally) flowing between the cells in
administrator.
the cube and the algorithm.
trusted password A password that enables users who have
translation See currency conversion.
been previously authenticated in another system to have
Transmission Control Protocol/Internet Protocol (TCP/ access to other applications without reentering their
IP) A standard set of communication protocols that is passwords.
adapted by many companies and institutions around the
trusted user A user authenticated by some mechanism in
world and that links computers with different operating
the environment.
systems and internal architectures. TCP/IP utilities are used
to exchange files, send mail, and store data to various tuple In MaxL DML, a required syntax convention for
computers that are connected to local and wide area referring to a member or a member combination from any
networks. number of dimensions. For example, in the Sample Basic
database, (Jan) is a tuple, and so is (Jan, Sales), and so is
transparent login A mechanism that enables users who
( [Jan], [Sales], [Cola], [Texas], [Actual] ).
have been previously authenticated by external security
criteria to log in to a Hyperion application, bypassing the two-pass calculation An Analytic Services property that is
login screen. used to recalculate members that are dependent on the
calculated values of other members. Two-pass members are
calculated during a second pass through the database
outline.
242 Glossary
UDA User-defined attribute, associated with members of user variable A variable that dynamically renders data
an outline to describe a characteristic of the members. Users forms based on a user's member selection, displaying only
can specify UDAs within calculation scripts and reports so the specified entity. For example, the user variable named
that they return lists of members that have the specified Department enables you to display only specific
UDA associated with them. UDAs can be applied to dense departments and employees.
as well as sparse dimensions.
user-defined attribute See UDA.
UI User interface
user-defined member list A named, static set of members
unary operator A group of mathematical indicators (+, -, within a dimension defined by the user. As dimension
*, /, %) that define how roll-ups take place on the database members are added to an application, member lists remain
outline. constant and will not reflect any changes made to the
application outline.
unbalanced journal A journal in which the total debits do
not equal the total credits. validation A process of checking a rules file, report script,
or partition definition against the outline to make sure that
uncommitted access An Analytic Services Kernel setting
the object being checked is valid.
that affects how Analytic Services handles transactions.
Under uncommitted access, concurrent transactions hold value dimension A dimension that is used to define the
short-term write locks and can yield unpredictable results. input value, translated value, and consolidation detail.
Unicode-mode application An Analytic Services variance The difference between two values (for example,
application wherein character text is encoded in UTF-8, between a planned and actual value).
enabling users with their computers set up for different
version A possible outcome used within the context of a
languages to share the application data. A Unicode-mode
scenario of data. For example, Budget - Best Case and
application can be created only on a Unicode-mode server.
Budget - Worst Case where Budget is the scenario and Best
Uniform Resource Locator (URL) The address of a Case and Worst Case are the versions.
resource on the Internet or an intranet.
view The representation of either a year-to-date or periodic
unique member name A non-shared member name that display of data.
exists only once in a database outline. Shared instances of
visual cue A formatted style, such as a font or a color, that
the unique member name can occur in the outline, but all
highlights specific types of data values. Data values may be
instances represent the same member in the database.
dimension members; parent, child, or shared members;
unique member outline A database outline that is not dynamic calculations; members containing a formula; read
enabled for duplicate member names. only data cells; read and write data cells; or linked objects.
upgrade The process of replacing an earlier software release Web server Software or hardware hosting intranet or
with a current release or replacing one product with Internet Web pages or Web applications.
another.
weight A value assigned to an item on a scorecard that
upper-level block A type of data block that is created for indicates the relative importance of that item in the
sparse member combinations when at least one of the sparse calculation of the overall scorecard score. The weighting of
members is a parent-level member. all items on a scorecard accumulates to 100%. For example,
to recognize the importance of developing new features for
URL See Uniform Resource Locator (URL).
a product, the measure for New Features Coded on a
user directory A centralized, corporate store of user and developer's scorecard would be assigned a higher weighting
group information. May also be referred to as a repository than a measure for Number of Minor Defect Fixes.
or provider.
Glossary 243
wild card A wild card is a character that represents any
single character (?) or any group of characters (*) in a search
string.
WITH section In MaxL DML, an optional section of the

query used for creating re-usable logic to define sets or
members. Sets or custom members can be defined once in
the WITH section, and then referenced multiple times
during a query.
workbook An entire spreadsheet file with many

worksheets.
write-back The ability for a retrieval client, such as a

spreadsheet, to update a database value.
ws.conf A configuration file for Windows platforms.
wsconf_platform A configuration file for UNIX platforms.
XML See Extensible Markup Language (XML).
Y axis scale The range of values on the Y axis of the charts

displayed in the Investigate Section. You can use a unique
Y axis scale for each chart, the same Y axis scale for all Detail
charts, or the same Y axis scale for all charts in the column.
Often, using a common Y axis improves your ability to
compare charts at a glance.
Zero Administration A software tool that identifies the

version number of the most up-to-date plug-in on the
server.
zoom A feature that sets the magnification of a report. The

report can be magnified to fit the whole page, page width or
a percentage of magnification based on 100%.
ZoomChart A feature that makes it easy to view detailed

information by enlarging a chart. Zooming in on a chart
enables you to see detailed numeric information on the
metric that is displayed in the chart.
244 Glossary
A B C D E F G H I J L M N O P R S T U V W X Y Z
Index
Symbols Aggregation for Plan1, Plan2, Plan3, Workforce, and

#missing data, 194 Capex, 191
representing with Smart Lists, 60 Aggregation Weight, 166
specifying settings for, 192 Alias, 160, 166, 168, 169, 175, 178, 182
#Missing Data Form Label option, 60 Alias dimension
#Missing Drop Down Label option, 60 setting up, 42
Alias dimension type
description, 22
Numbers alias tables
4-4-5 weekly pattern, 72
creating in Planning, 189
445 and 544 weekly patterns, considerations for
default for Planning, 189
redeploying, 107
selecting for Planning, 191
5-4-4 weekly pattern, 72
aliases
naming conventions, 206
A Planning, 191
access permissions selecting, 191
impact of deleting members, 107 using to deploy dimensions, 203
access permissions, assigning for Planning, 203 Allow Adjustments, 168
access permissions, defining for Scenarios, 200 Allow Adjustments From Children, 168
Account dimension, 192 Analytic Services application views. See Enterprise
Account dimension type Analytics application views. See Essbase Analytics
description, 22 application views
Account members application library
Account types, 193 viewing data flow, 97
plan types, 192 application members
Account properties filtering, 81
consolidation, 160 application membership
Planning, 192 viewing, 79
Account types application properties
and variance reporting, 192 consolidation, 171
described, 193 Planning, 188
summary of, 193 application views
AccountType about, 67
behavior, 164 accessing from data flow, 99
active account, 180 adding dimensions, 70
Actual_365 weighted average time balance, 194 changing the dimension order, 74
Actual_Actual weighted average time balance, 194 compare results, 94
Aggregation for Plan setting, 192 comparing, 92
Index 245
creating, 68 excluding, 204

data type evaluation order, 75 loading, 203
defining base time period, 72 Planning, 191
defining currencies, 72 average time balance property, 194
defining monthly distribution spread, 72
defining the calendar range, 72
dense and sparse dimensions, 74
B
balance account behavior, 164
deploying, 99
balance property, 194
deploying consolidation, 103
balance recurring account behavior, 164
deploying for Planning, 107
base time period, 188
excluding members, 85
defining, 72
filtering members, 81
spreading data, 72
finding members, 80
BegBalance member. See Beginning Balance time
management, 9
period
managing, 67
Beginning Balance time period
modifying consolidation, 76
and Scenarios, 199
naming rules, 205
editing, 198
optimizing performance, 74
required for deployment, 198
performance, 75
bottom-up versions, 201
plan type performance settings, 74
BPM Architect
Planning, 71
about, 9
prerequisites, 68
Planning-specific information, 187
process, 67
redeploying, 106
removing dimensions, 78 C
setting up plan types, 73 Calc Attribute, 161
validating, 99, 100 calendar range, defining, 72
viewing application membership, 79 calendars
viewing dimension associations, 78 adding years to, 201
working with members, 80 changing the current year or time period, 201
applications creating summary time periods, 198
naming rules, 205 practical limits, 198
architecture requirements for redeploying, 107
BPM Architect, 11 setting up, 197
asset account behavior, 164 Capex aggregation properties, 191
asset Account type, 193 Capex plan type, described, 188
associations Capex, aggregation for, 191
assigned when upgrading Planning, 203 characters, reserved, 205
dimension, 78 clearing interface tables, 33
loading in flat files, 203 ClosedInputValueBlock variable, 63
associations, removed when deleting Planning compare results
members, 204 excluding members, 97
attachments viewing, 94
viewing job attachments, 137 comparing
Attribute dimension type application views, 92
description, 22 Consol1...3 account, 180
attribute values Consolidate YTD, 169
246 Index
consolidation Currency Symbol, 196

application views, 76 custom dimensions
Consolidation Account Type, 161 deleting, 204
consolidation accounts excluding, 204
active account, 180 naming, 203
Consol1...3 account, 180 custom properties
DOWN account, 180 consolidation, 166
method account, 180 Planning, 203
PCON account, 180 custom time periods, Planning, 188
PCTRL account, 180 Custom Top Member, 161
POWN account, 180 CYTD(memberName) function, 64
Consolidation Method, 175 CYTD(memberName, calTpIndexName,
Consolidation Method dimension type fiscalTpIndexName) function, 64
description, 22
Consolidation Rules, 172
Control, 176
D
data
copying dimensions, 44
distribution over time, 72
Country dimension type
impact of deleting members, 107
description, 22
data flow
creating dimension associations, 45
editing synchronizations, 98
creating dimensions, 42
executing synchronizations, 99
creating import files
focal application, 98
dimension library, 23
validating synchronizations, 99
creating import profiles, 34
viewing, 97
creating members, 47
viewing synchronizations, 98
creating shared members, 48
data forms, impact of deleting members, 107
creation
Data Storage
about, 9
shared members use ShareData, 205
CrossRef(accountName) function, 64
using to optimize performance, 190
CrossRef(accountName, prefix) function, 64
data synchronization, 109
currencies
application views, 110
conversions with, 72
assigning default members, 120
defining in an application views, 72
changing the data synchronizer view, 128
multiple, 72
creating mapping tables, 122, 125
reporting, 196
creating taskflows, 144
currency, 168
creating using interface tables, 114
name, 190
data interface tables, 113
reporting, 196
defining external files, 115
requirements for redeploying, 107
defining the interface area, 113
triangulating, 196
deleting, 129
Currency Code, 196
destination dimension rule syntax, 123
Currency dimension type
duplicating, 129
description, 22
editing, 128
currency for Entity members, 197
editing from data flow, 98
currency properties
editing mapping tables, 121
consolidation, 178
executing, 129
Planning, 188
executing from data flow, 99
Index 247
external files, 115 application views, 99

filtering dimensions, 119 BegBalance required for, 198
filters, 128 checking Show Usage, 101, 107
mapping, 122 deleting members, implications of, 107
mapping dimensions, 117 Enterprise Analytics application views, 104
mapping tables, 121 Essbase Analytics application views, 77, 104
multiple currency application views, 112 excluding members, 204
navigating the data synchronizer, 127 full, not partial dimension update, 100
saving, 121 Planning considerations, 100
source dimension rule syntax, 123 required dimensions, 101
understanding, 109 Scenario required for Planning, 200
validating, 129 shared members, with ShareData, 205
validating from data flow, 99 troubleshooting, 100, 107, 201
viewing in data flow, 98 Version required for Planning, 200
working with the data synchronizer, 127 Year required for Planning, 201
Decimal Separator, 195 YearTotal required for, 198
Default Alias Table deployment
defining, 189 about, 9
requirements for deploying, 101 dimension
Default Currency, 172, 188 removing in application views, 78
requirements for redeploying, 107 Dimension Alias, in System Properties, 203
Default Frequency, 169 dimension associations
Default Frequency For IC Transactions, 170 creating, 45
default members deleting, 46
assigning for data synchronizations, 120 viewing, 46, 78
Default Parent, 161, 166, 168, 170, 182 Dimension Library
Default Rate For Balance Accounts, 172 associations, 203
Default Rate For Flow Accounts, 172 new Planning dimensions, 203
Default Value For Active, 172 dimension library
Default View, 170 viewing dimension associations, 46
defining dimension order
Consolidation Method, 175 changing, 74
deleted members dimension types
checking Show Usage in Planning, 204 Account, 22
checking usage before deploying, 101, 107 Alias, 22
deleting Attribute, 22
jobs, 139 Consolidation Method, 22
deleting dimension associations Country, 22
dimension library, 46 Currency, 22
deleting dimensions, 46 defined, 22
deleting import profiles, 41 Entity, 22
deleting members Generic, 22
dimension library, 49 ICP, 22
dense dimensions, 202 Period, 22
and performance, 74 Scenario, 22
changing to sparse, 203 Security Class , 22
deploying Smart List, 22
248 Index
Time, 22 deploying, 104

Value, 22 deployment guidelines, 104
Version, 23 modifying, 77
View, 23 Entity dimension, 197
Year, 23 Entity dimension type
Dimension(dimtag) function, 64 description, 22
dimensions Entity members
Account, 192 and plan types, 189
adding to application views, 70 currency, 197
associations, 203 Entity properties
copying, 44 consolidation, 168
creating, 42 for Planning, 197
deleting, 46, 204 equity Account type
dense, 202 summary, 193
deploying, considerations for, 100 error messages
Entity, 197 deployment, 100, 201, 205
excluding, 204 for formula expressions, 65
flat files, specifying associations, 203 redeployment, 107
hierarchies, 202 Essbase Analytics application views
managing in dimension library, 21 deploying, 104
naming conventions, 206 deployment guidelines, 104
naming conventions for Planning, 203 modifying, 77
Planning-specific information, 187 exchange rate tables, defining for Scenarios, 199
predefined, 101 exchange rates, types for Account members, 193
relationship to members, 202 excluded members
requirements for redeploying, 107 checking Show Usage in Planning, 204
sparse, 202 excluding members
user-defined, 203 in compare results, 97
Display In ICT, 178 executing
Display Order option for Smart Lists, 60 data synchronizations, 129
distribution of data over time periods, 72 data synchronizations from data flow, 99
DOWN account, 180 expense account behavior, 164
down arrows in data cells, 58 expense Account type
Dynamic Calc, 190 summary, 193
expense account type
and variance reporting, 192
E Expense setting, 192
editing
expressions. See formula expressions
mapping tables, 121
external files
editing import profiles, 41
defining, 115
Enable Custom Aggregation, 161
Enable Data Audit, 161, 170
Enable for Process Management, 199, 201 F
Enable Metadata Security Filtering, 172 FDM Application Name, 175
Enable Process Management, 170 filtering
End Period, 199 dimensions in data synchronizations, 119
End Year, 199 members, 81
Enterprise Analytics application views filters
Index 249
creating in the job console, 134 import files

other user jobs in the job console, 136 creating, 23
synchronizations, 128 Dimension Associations section, 24
your jobs in the job console, 135 Dimensions section, 23
finding Hierarchies section, 26
members, 80 Members section, 25
First time balance property, 194 Property Array section, 27
First Year import profiles
described, 201 creating, 34
format for, 101 deleting, 41
fiscal start month, requirements for redeploying, 107 editing, 41
fiscal year, setting up, 72 importing dimensions, 40
flat file import managing, 40
creating taskflows, 144 viewing, 41
flow Import Profiles, and Planning, 202
viewing data, 97 import results, 138
flow account behavior, 164 intercompany partners, setting up, 181
Flow time balance property, 193 interface area
focal application defining, 113
changing, 98 interface table import
formula expressions, 62 creating taskflows, 145
described, 63 interface tables
error messages for, 65 clearing, 33
prerequisites for using, 63 defined, 32
syntax for, 64 overview, 28
using in member formulas, 63 system tables, 32
using Smart Lists in, 65 user-defined tables, 33
functions. See formula expressions Is Calculated, 162, 166
Is Consolidated, 162
Is Holding Method, 176
G Is ICP, 162
Generic dimension type
entities, 168
description, 22
getCalendarTPIndex() function, 64
getFiscalTPIndex() function, 64 J
job
attachments, 137
H deleting, 139
Holding Company, 168
types, 131
job console
I changing the view, 133
ICP, 181 creating filters, 134
ICP dimension type deleting jobs, 139
description, 22 job types, 131
ICP Entities Aggregation Weight, 173 navigating, 132
ICP members refreshing, 134
system generated, 181 security, 136
ICP Top Member, 162 security for displaying jobs, 136
250 Index
security for submitting jobs, 136 aggregation properties, 191

viewing job attachments, 137 assigning default, 120
working with, 131 deleting, 49, 204
jobs deleting, implications of, 107
managing, 131 excluding, 204
excluding in application views, 85
finding, 80
L naming conventions, 206
Label Only option, 190
of the Entity dimension, 189
labels
Planning-specific information, 187
in Smart Lists, 59
removing, 48
leap year, accounting for, 194
searching, 84
liability account behavior, 164
working with, 80
liability Account type
working with shared members, 205
summary, 193
membership
loading dimensions, using flat files, 203
viewing application, 79
menus
M BPM Architect, 15, 16, 17
management metadata integrity, 184
application, 9 method account, 180
managing missing data in Account calculations, 194
jobs, 131 modifying
managing dimensions Enterprise Analytics application views, 77
in dimension library, 21 Essbase Analytics application views, 77
managing import profiles, 40 modules
mapping BPM Architect, 10
about, 122 monthly distribution patterns, 72
creating tables, 122 multiple currencies, 72, 107, 188
deleting, 129 multiple UDAs for a single member, 190
dimensions for synchronizations, 117
duplicating, 129
editing, 121
N
Name, 162, 166, 168, 170, 176, 178, 182
tables, 121
naming conventions, for Planning, 203
mapping tables
naming restrictions
editing, 129
applications, 205
Maximum Cell Text Size, 173
dimensions, members, and aliases, 206
Maximum Document Attachment Size, 173
navigating
Maximum Number of Document Attachments, 173
job console, 132
Maximum Review Level, 170
navigation
member formulas
BPM Architect, 14
Planning, 191
Negative Color, 195
using formula expressions in, 63
Negative Sign, 195
viewing results of validation, 62
Never Share option, 190
working with, 61
No Year member, described, 201
member selector
Node Security, 173
searching, 84
non-expense Account types, 192
members
Non-Expense setting, 192
Index 251
Number Of Decimal Place, 163 access permissions, 203

NumberOfPeriodsInYear variable, 63 Account Type, 193
NumberOfYears variable, 63 Account type combinations, 193
Accounts, 192
adding dimension members with Import Profiles,
O 202
OpenInputValueBlock variable, 63
aggregation properties, 191
optimizing performance, 74
alias tables, 191
Org By Period Application, 173
alias tables, default, 189
organization by period, 175
application properties, 188
orphan members, 48
Application Views, deploying, 107
ownership accounts
attribute values, 191, 203
SharesOutstanding account, 181
base time period, 188
SharesOwned account, 181
BegBalance member, 198
VotingOutstanding account, 181
currency, 190, 195
VotingOwned account, 181
data storage, 190
data type, 191
P default alias table, 189
PCON account, 180 deleting members, implications of, 107
PCTRL account, 180 deployment considerations, 100
Percent Consol, 176 dimensions, 187, 202, 203
Percent Consol Value, 177 distribution pattern, 188
percent consolidation, 180 dynamic calc, 190
percent control, 180 Entity properties, 197
percent direct ownership, 180 examples of Account calculation, 194
percent ownership, 180 exchange rate tables, 199
performance Exchange Rate Type, 193
changing dimension order, 74 First Year, 101
optimizing in application views, 74 member formulas, 191
plan type settings, 74 members, deleting, 204
setting data type evaluation order, 75 members, excluding, 204
Period dimension, 197 multiple currencies, 188
Period dimension type naming conventions, 203
description, 22 Period properties, 197
Period(periodName) function, 64 plan name, 188
Period, changing, 201 plan types, 188, 192
permissions, assigning for Planning, 203 predefined dimensions, 101
Plan Name, 188 process management, enabling for, 199, 201
plan types properties for, 189
Account members, 192 redeployment considerations, 107
Entity members, 189 reporting currency, 196
Planning, 188 Scenarios, 198
requirements for redeploying, 107 shared members, setting Data Storage to ShareData,
setting, 188 205
setting up in application views, 73 shared members, working with, 205
Plan1, Plan2, and Plan3 plan types, described, 188 Source Plan Type, 193
Planning, 191 sparse and dense dimension, 202
252 Index
Start Year, 100 Default Parent, 161, 166, 168, 170, 182
start year and month, 189 Default Rate For Balance Accounts, 172
target and bottom-up versions, 201 Default Rate For Flow Accounts, 172
time balance property examples, 193 Default Value For Active, 172
Two Pass Calc, 192 Default View, 170
UDAs, 190 Display In ICT, 178
Valid for Plan, 189 effect of changing dimension from sparse to dense,
Variance Reporting, 192 203
Versions, 200 Enable Custom Aggregation, 161
Year dimension, 201 Enable Data Audit, 161, 170
YearTotal member, 198 Enable Metadata Security Filtering, 172
planning units, impact of deleting members, 107 Enable Process Management, 170
Plug Account, 163 FDM Application Name, 175
POWN account, 180 Holding Company, 168
predefined dimensions ICP Entities Aggregation Weight, 173
requirements for deploying, 101 ICP Top Member, 162
requirements for redeploying, 107 Is Calculated, 162, 166
prerequisites Is Consolidated, 162
application views, 68 Is Holding Method, 176
process Is ICP, 162, 168
creating applications, 12 Maximum Cell Text Size, 173
process management, using with Planning, 199, 201 Maximum Document Attachment Size, 173
properties Maximum Number of Document Attachments,
Aggregation Weight, 166 173
Alias, 160, 166, 168, 169, 175, 178, 182 Maximum Review Level, 170
Allow Adjustments, 168 Multiple Currencies, 188
Allow Adjustments From Children, 168 Name, 162, 166, 168, 170, 178, 182
base time period, 188 name, 176
Calc Attribute, 161 Node Security, 173
Consolidate YTD, 169 Number Of Decimal Places, 163
consolidation Org By Period Application, 173
Account, 160 Percent Consol, 176
Application, 171 Percent Consol Value, 177
custom, 166 Plan Name, 188
Entity, 168 Planning, 187
Scenario, 169 Plug Account, 163
Consolidation Account Type, 161 Scale, 179
consolidation properties Security As Partner, 169
currency, 178 Security Class, 163, 167, 169, 171, 182
Consolidation Rules, 172 Security For Accounts, 174
Control, 176 Security For Custom, 174
currency, 168 Security For Entities, 174
Custom Top Member, 161 Security For ICP, 174
Default Alias Table, 189 Security For Scenarios, 174
Default Currency, 172, 188 Start Month, 189
Default Frequency, 169 Start Year, 189
Default Frequency For IC Transactions, 170 Submission Group, 163, 167, 183
Index 253
Support Submission Phase for Account, 174 summary, 193

Support Submission Phase for Custom, 174 roles
Support Submission Phase for ICP, 174 BPM Architect, 13
Switch Sign For Flow, 167 rule syntax
Switch Type For Flow, 167 destination dimension used in data
system, 203 synchronizations, 123
To Percent Control, 177 source dimension used in data synchronizations,
To Percent Control Compare, 177 123
Translation Operator, 179
Use PVA For Balance Accounts, 173
Use PVA For Flow Accounts, 173
S
saved assumptions, 193
Use Submission Phase, 174
Scale, 179, 196
Used By Calc Routine, 177
scaling, 196
User Defined 1...3, 163, 171
Scenario dimension type
User Defined1...3, 167, 169
description, 22
Uses Line Items, 163, 171
Scenario properties
Valid for Plan, 188
consolidation, 169
Validation Account, 174
Scenario properties, for Planning, 198
Weeks Distribution, 188
Scenarios
XBRL Tags, 163
access permissions, defining, 200
Zero View For Adjustments, 171
deleting, 200
Zero View For Non-adjustments, 171
deployment, required for, 200
property values, effect of changing dimension from
exchange rate tables, defining, 199
sparse to dense, 203
process management, enabling for, 199
time periods, defining, 199
R searching
range of time periods, setting, 198 for members, 84
redeploying security, 13
application views, 106 for displaying jobs, 136
checking Show Usage, 101, 107 for submitting jobs, 136
currency issues, 107 in job console, 136
Planning considerations, 107 Security As Partner, 169
Scenario considerations, 200 Security Class, 163, 167, 169, 171, 182
troubleshooting, 107, 201 Security Class dimension type
Year dimension considerations, 201 description, 22
redeployment Security For Accounts, 174
creating taskflows, 145 Security For Custom, 174
referential integrity, 184 Security For Entities, 174
refreshing Security For ICP, 174
job console, 134 Security For Scenarios, 174
removing members, 48 Set Base Member, not using in Planning, 205
reporting currencies, 196 setting up, 181
reserved characters, 205 setting up Alias dimensions, 42
results setting up ICP, 181
viewing import, 138 Share option, 190
revenue account behavior, 164 shared members
revenue Account type creating, 48
254 Index
setting Data Storage as ShareData, 205 creating mapping tables, 122, 125
working with, 205 saving, 121
Shared Services taskflows synchronizing
deleting permissions, 153 data, 109
editing permissions, 153 synchronizing data, 109
viewing participant details, 156 system accounts
viewing participant status, 155 active account, 180
ShareData Consol1...3 account, 180
deployment with, 205 DOWN account, 180
setting for shared members, 205 method account, 180
ShareData, setting for shared members, 190 PCON account, 180
SharesOutstanding account, 181 PCTRL account, 180
SharesOwned account, 181 POWN account, 180
single currency, redeploying, 107 SharesOutstanding account, 181
Skip options, 194 SharesOwned account, 181
Skip Value setting, 192 VotingOutstanding account, 181
Smart List dimension type VotingOwned account, 181
description, 22 System Properties, using Dimension Alias, 203
Smart Lists
and data entry, 58
representing #missing, 60
T
tables
setting properties, 59
mapping, 121
using in formula expressions, 65
target versions, description, 201
working with, 58
task automation
Source Plan Type, 193
prerequisites, 142
source plan type, and accounts, 192
taskflows
sparse dimensions, 202
adding links, 148
and performance, 74
copying, 150
effect of changing to dense, 203
creating, 143
spreading data, 72
creating data synchronization, 144
Start Month, 189
creating flat file imports, 144
requirements for deploying, 101
creating interface table imports, 145
creating redeployment, 145
Start Year, 189, 199
creating stages, 146
described, 201
deleting, 150
format for, 100
editing, 150
managing, 142
Submission Group, 163, 167, 183
running manually, 151
summary time periods
stopping, 155
changing the range, 198
viewing, 149
creating, 198
viewing status, 154
Support Submission Phase for Account, 174
Thousands Separator, 195
Support Submission Phase for Custom, 174
time balance calculations, 194
Support Submission Phase for ICP, 174
Time Balance property, 192
Switch Sign For Flow, 167
time balance property examples, 193
Switch Type For Flow, 167
Time dimension type
synchronizations
description, 22
Index 255
time periods variance reporting and Account type, 193

changing, 201 Version dimension type
defining for Scenarios, 199 description, 23
practical limit, 198 Version Type, 201
time periods dimension, about, 197 Versions, 200
To Percent Control, 177 process management, enabling for, 201
To Percent Control Compare, 177 properties, 200
toolbars required for Planning deployment, 200
BPM Architect, 15 setting up bottom-up versions, 201
Workspace, 15 setting up target versions, 201
Translation Operator, 179 view
triangulation, 196 filtering synchronizations, 128
triangulation currency, consequence of deleting, 107 View dimension type
troubleshooting deploying for Planning, 100, 201 description, 23
troubleshooting redeploying for Planning, 107, 201 viewing
Two Pass Calc, 192, 196 data flow, 97
types of dimensions, 22 viewing application membership
dimension library, 47
viewing dimension associations
U dimension library, 46
UDAs
viewing import profiles, 41
multiple, 190
VotingOutstanding account, 181
Planning, 190
VotingOwned account, 181
working with, 57
Use Beginning Balance, 199
Use PVA For Balance Accounts, 173 W
Use PVA For Flow Accounts, 173 weekly distribution patterns, 72
Use Submission Phase, 174 Weeks Distribution, 188
Used By Calc Routine, 177 weeks, requirements for redeploying, 107
User Defined1...3, 163, 167, 169, 171 Weighted Average time balance properties, 194
Uses Line Items, 163, 171 Workforce aggregation properties, 191
Workforce plan type, described, 188
Workforce, aggregation for, 191
V
Valid for plan setting
and Account members, 192 X
and Entity members, 189 XBRL Tags, 163
validating
application views, 99, 100
data synchronizations, 129
Y
Year
data synchronizations from data flow, 99
requirements for deploying, 101
Validation Account, 174
Year dimension type
Value dimension type
description, 23
description, 22
Year dimension, described, 201
value members
years
editing, 183
adding to calendar, 201
system generated, 181
changing current, 201
Variance Reporting, 192
maximum, 198
256 Index
No Year member, described, 201

practical limit, 198
YearTotal member
editing, 198
required for deployment, 198
Z
Zero View For Adjustments, 171
Zero View For Non-adjustments, 171
zeros in Account calculations, 194
Index 257
258 Index

Bpma Admin

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Bpma Admin

Încărcat de

Drepturi de autor:

Formate disponibile

HYPERION® SYSTEM™ 9

Chapter 1. Using BPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2. Managing Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3. Managing Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 4. Synchronizing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 5. Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Chapter 6. Using Task Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Appendix A. Working with Financial Management Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Appendix B. Working with Planning Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Appendix C. Working with Analytic Services Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Appendix D. Working with Statistical and System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

About BPM Architect

About BPM Architect 9

BPM Architect Modules

10 Using BPM Architect

Logging on to Workspace and Accessing BPM Architect

12 Using BPM Architect

Table 1 BPM Architect Roles

Roles Tasks Performed

Create Integrations Can create and execute data synchronizations.

Run Integrations Can execute data synchronizations.

Navigating BPM Architect

14 Using BPM Architect

Table 2 Standard Toolbar Buttons

Button Menu Command Description

File > Open > Document Use repository documents

File > Logoff End the current session

Table 3 BPM Architect Toolbar Buttons

Button Menu Command Description

View > Refresh Refreshes the window.

*Displays in the Dimension Library only.

Navigating BPM Architect 15

Table 4 File Menu

New > Dimension Creates a dimension*

New > Application View Creates an Application View.†

*Displays in the Dimension Library only.

Table 5 View Menu

Show Master View Displays the Master View

Show App View Displays the Application View pane

Show Property Grid Displays the Property Grid.

Show Member List Displays the Member Find pane

Refresh Refreshes the display

Data Synchronization, Job Console, and Application Library

Icon Displays icons and the name of the artifact.*

Details Displays the artifact name, description, and additional details

Refresh Refreshes the display

*Displays in Data Synchronization and Application Library only.

16 Using BPM Architect

Table 6 Administration Menu

Manage Taskflows Automates tasks that you commonly perform

View Taskflow Status Displays the status of any automated tasks

Administering BPM Architect Servers

Starting and Stopping BPM Architect Dimension Server

➤ To start or stop the Dimension server:

➤ To increase the timeout setting for startup of Dimension Server:

Administering BPM Architect Servers 17

Starting and Stopping BPM Architect Application Server

➤ To start or stop the BPM Architect application server:

Table 7 Location Example for StartBPMAWebServer and StopBPMAWeb Server Commands

Tomcat <drive letter>:\Hyperion\ BPMA Double-click

WebLogic <drive letter>:\Hyperion\ BPMA Double-click startBPMAWebTier.cmd or

Websphere <drive letter>:\hyperion\ BPMA Double-click