PowerExchange for Hyperion Essbase 8.5 User Guide Documentation/1/PWX… · from the Essbase server and create a logical definition used to write data to the Essbase server. Use the

User Guide

PowerExchange for Hyperion Essbase(Version 8.5)

Informatica PowerExchange for Hyperion Essbase User Guide Version 8.5 May 2008 Copyright (c) 2004–2008 Informatica Corporation. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software is protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775, 6,850,947; 6,895,471, 7,254,590, and other U.S. Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-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 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica Complex Data Exchange and Informatica On Demand Data Replicator are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

Part Number: PWX-HEU-85000-002

Table of Contents

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixNew Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1: Understanding PowerExchange for Hyperion Essbase . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Essbase Source Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Essbase Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Essbase Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

ROLAP for Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

PowerCenter and Hyperion Essbase Integration . . . . . . . . . . . . . . . . . . . . . . . 4

Integration Service and Hyperion Essbase Integration . . . . . . . . . . . . . . . 4

Chapter 2: Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . 5Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installing and Configuring PowerExchange for Hyperion Essbase . . . . . . . 6

Before You Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Upgrading PowerExchange for Hyperion Essbase . . . . . . . . . . . . . . . . . . . 6

Installing PowerExchange for Hyperion Essbase . . . . . . . . . . . . . . . . . . . . . . . 8

Registering the Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Setting the Library Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Setting the Library Paths on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Setting the Library Paths on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Uninstalling PowerExchange for Hyperion Essbase . . . . . . . . . . . . . . . . . . . . 13

Uninstalling from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Uninstalling from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table of Contents iii

Chapter 3: Essbase Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Creating a DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Type 1 and Type 2 Essbase Source Definitions . . . . . . . . . . . . . . . . . . . . . . . 19

Connecting to Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Creating Type 1 and Type 2 Source Definitions . . . . . . . . . . . . . . . . . . . 19

Creating Columns for Type 1 and Type 2 Source Definitions . . . . . . . . . 19

Creating Filter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Identifying Attribute Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Editing Report Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Type 3 Source Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Connecting to the Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Creating Type 3 Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Creating Columns for Type 3 Source Definition . . . . . . . . . . . . . . . . . . . 22

Example of Setting Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Steps to Create Essbase Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Steps to Create Columns for Type 1 and Type 2 Source Definitions . . . . . 28

Steps to Create Columns for Type 3 Source Definition . . . . . . . . . . . . . . 30

Steps to Identify Attribute Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Steps to Edit Report Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 4: Essbase Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Type 1 and Type 2 Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41


Creating Type 1 and Type 2 Target Definitions . . . . . . . . . . . . . . . . . . . 41

Creating Columns for Type 1 Target Definitions . . . . . . . . . . . . . . . . . . 41

Columns in Type 2 Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating Filter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Type 3 Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43


Creating Type 3 Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Creating Columns for a Type 3 Target Definition . . . . . . . . . . . . . . . . . . 43

Steps to Create Essbase Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Steps to Create Columns for Type 1 Target Definition . . . . . . . . . . . . . . 45

Steps to Create Columns for Type 3 Target Definition . . . . . . . . . . . . . . 47

iv Table of Contents

Loading Data with a Rules File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


Chapter 5: Essbase Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . 51Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Creating an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Creating a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Adding a Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Adding a Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 5: Essbase Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Creating Essbase Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 6: Essbase Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Configuring Application Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring a Session for an Essbase Source . . . . . . . . . . . . . . . . . . . . . . . . . 74

Setting the Partition Query Condition . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configuring a Session for an Essbase Target . . . . . . . . . . . . . . . . . . . . . . . . . 75

Using Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Running Calculation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76


Appendix A: Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Hyperion Essbase and Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . 80

Appendix B: Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Designer Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Integration Service Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Appendix C: Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

v Table of Contents

vi Table of Contents

List of Tables

Table 2-1. Environment Variables and Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11



Table 3-1. Default Values for Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 3-2. Default Values for TwoPassCalc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 3-3. Default Values for Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 3-4. Default Values for TimeBalance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Table 3-5. Default Values for TimeBalanceSkip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Table 3-6. Default Values for VarReporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table 3-7. Default Values for CurrCon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table 6-1. Session Properties for Essbase Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Table 6-2. Session Properties for Essbase Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Table A-1. Essbase and Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

List of Tables vii

viii List of Tables

Preface

The Informatica PowerExchange for Hyperion Essbase User Guide provides information to read data from a Hyperion Essbase source, write data to a Hyperion Essbase target, and modify the Hyperion Essbase outline. The PowerExchange for Hyperion Essbase User Guide is written for database administrators and developers that are responsible for reading data from Hyperion Essbase and writing to Hyperion Essbase.

ix

New Features and EnhancementsPowerExchange for Hyperion Essbase includes the following new features and enhancements:

♦ Connection object extension. Specify the values for the application and the database in the connection object to override the default application and database names stored in the table definition. You can use the connection parameter in the connection settings to specify these values.

♦ Outline metadata extraction. Extract the metadata associated with a member such as member name, parent name, and data storage.

♦ Ordering of mapped columns. Modify the order of the mapped columns in the Column Mapping Wizard.

♦ Outline modification. Modify the database structure of a multi-dimensional database. You can modify the dimensions, members, tags, types, consolidations, and mathematical relationships in a database. You can add members in the outline at any level and set the member properties.

♦ Selection of multiple measure dimensions member. Select more than one member measure dimension at a time.

♦ Suppress data. Suppress the missing data with zero or missing values and exclude the rows containing missing values when you read from Essbase.

♦ Clear database. Clear all the blocks in the database before loading data into Essbase.

x Preface

Informatica Resources

Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.

Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.

Informatica Global Customer SupportYou can contact a Customer Support Center through telephone or the WebSupport Service. WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Toll Free +1 877 463 2435

Standard RateBrazil: +55 11 3523 7761Mexico: +52 55 1168 9763United States: +1 650 385 5800

Toll Free 00 800 4632 4357

Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511 445

Toll Free Australia: 1 800 151 830Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738

Preface xi

http://my.informatica.com

http://www.informatica.com

http://www.informatica.com

xii Preface

C h a p t e r 1

Understanding PowerExchange for Hyperion Essbase

This chapter includes the following topics:

♦ Overview, 2

♦ PowerCenter and Hyperion Essbase Integration, 4

1

OverviewPowerExchange for Hyperion Essbase provides bidirectional connectivity between PowerCenter and the Essbase server to extract and load data.

Use PowerExchange for Hyperion Essbase to perform the following tasks:

♦ Import metadata.

♦ Create source definitions.

♦ Create target definitions.

♦ Administer outlines.

♦ Transfer data into Relational Online Analytical Processing (ROLAP) model cube.

Essbase Source DefinitionsA source definition is a logical representation of columns and dimensions used to read data from the Essbase server. When you create a source definition in PowerCenter, you import the metadata from the Essbase server and create a logical definition used to read data from the Essbase server.

Use the Designer Wizard to create Type 1, Type 2, and Type 3 source definitions:

♦ Accounts dimension member as a column (Type 1). Create Type 1 source definitions to map accounts dimension members to the source definition columns. You can map any number of accounts dimension members to columns.

♦ Accounts dimension as a column (Type 2). Create Type 2 source definitions to map accounts dimension to source definition columns. Essbase creates a data column for Type 2 source definitions. The data column receives data and loads it into the Essbase database.

♦ Extract members (Type 3). Create Type 3 source definitions to map any standard dimension or level under the dimension to source definition columns. The data is extracted for all the descendents under the dimension or level.

Essbase Target DefinitionsA target definition is a logical representation of columns and dimensions used to write data to the Essbase server. When you create a target definition in PowerCenter, you import metadata from the Essbase server and create a logical definition used to write data to the Essbase server.

Use the Designer Wizard to create Type 1, Type 2, and Type 3 target definitions:

♦ Accounts dimension member as a column (Type 1). Create Type 1 target definitions to map accounts dimension members to the target definition columns. You can map any number of account dimension members to columns.

♦ Accounts dimension as a column (Type 2). Essbase creates the definition for Type 2 target definition. The Designer Wizard creates columns for the dimensions in an Essbase outline to retrieve data from Essbase.

2 Chapter 1: Understanding PowerExchange for Hyperion Essbase

♦ Dynamic dimension building (Type 3). Create Type 3 target definitions to add members to an Essbase outline. To add members to the outline, create columns to retrieve member names and the metadata associated with the members.

Essbase AdministrationYou can connect to Hyperion Essbase from the PowerCenter Designer to perform some of the Essbase administrative tasks that you can also perform in the Hyperion Essbase Administration Console.

ROLAP for EssbaseYou can transfer data from the Essbase server into a ROLAP model cube and from a ROLAP model cube to the Essbase database. Essbase provides read and write access to the data in the Essbase server.

Overview 3

PowerCenter and Hyperion Essbase IntegrationThe Designer connects to the Essbase server to import the Essbase source and target definitions. After establishing the connection, the Designer starts an Essbase session and accesses the Essbase database to import the source or target metadata.

Integration Service and Hyperion Essbase IntegrationCreate a connection object in the Workflow Manager to connect to the Essbase server. The Integration Service uses the connection information to connect to the Essbase server through the Hyperion Essbase C SDK.

Figure 1-1 shows how PowerCenter connects to the Essbase server to read and write Essbase data:

Figure 1-1. Integration Service and Hyperion Essbase Integration

Repository

Workflow

Essbase SessionEssbase Application Connection

The Integration Service reads and writes Essbase data based on the workflow and Essbase application connection configuration.

The Integration Service uses the the Hyperion Essbase C SDK to connect to the Essbase server to read and write Essbase data.

Integration Service

Hyperion Essbase Server

4 Chapter 1: Understanding PowerExchange for Hyperion Essbase

C h a p t e r 2

Installation and Configuration


♦ Overview, 6

♦ Installing PowerExchange for Hyperion Essbase, 8

♦ Registering the Plug-in, 10

♦ Setting the Library Paths, 11

♦ Uninstalling PowerExchange for Hyperion Essbase, 13

5

OverviewThis chapter provides information about upgrading, installing, and uninstalling PowerExchange for Hyperion Essbase.

Minimum System RequirementsEnsure that the minimum system requirements are met.

PrerequisitesBefore you install or upgrade PowerExchange for Hyperion Essbase, complete the following tasks:

♦ Install or upgrade PowerCenter. For more information about the PowerCenter versions that PowerExchange for Hyperion Essbase is compatible with, see the PowerExchange for Hyperion Essbase Release Notes.

♦ Verify that you have read and write permissions on the directories where you want to install PowerExchange for Hyperion Essbase.

The installer must be able to add and overwrite files in the installation directory.

Installing and Configuring PowerExchange for Hyperion EssbaseTo install and configure PowerExchange for Hyperion Essbase, complete the following steps:

1. Install the components. Install Client, Repository, and Integration Service components to access PowerExchange for Hyperion Essbase. For more information, see “Installing PowerExchange for Hyperion Essbase” on page 8.

2. Register the plug-in. Register the plug-in with the repository. For more information, see “Registering the Plug-in” on page 10.

3. Set library paths. Set library paths on Windows and UNIX platforms. For more information, see “Setting the Library Paths” on page 11.

After you install and configure PowerExchange for Hyperion Essbase, you can create connections to access Essbase. Create connection objects in the Workflow Manager so that the Integration Service can connect to Essbase.

Before You UpgradeBefore you upgrade PowerExchange for Hyperion Essbase, uninstall the previous version. When you uninstall PowerExchange for Hyperion Essbase, you do not need to unregister the plug-in.

Upgrading PowerExchange for Hyperion EssbaseWhen you upgrade PowerExchange for Hyperion Essbase, complete the following tasks:

6 Chapter 2: Installation and Configuration

1. Install PowerExchange for Hyperion Essbase. When you install PowerExchange for Hyperion Essbase, you install the PowerCenter Client and Services components. For more information, see “Installing PowerExchange for Hyperion Essbase” on page 8.

2. Upgrade the plug-in registration. Register the PowerExchange for Hyperion Essbase plug-in, to update the existing plug-in registration. For more information, see “Registering the Plug-in” on page 10.

Overview 7

Installing PowerExchange for Hyperion Essbase

When you install PowerExchange for Hyperion Essbase, you install components that allow PowerCenter to access Hyperion Essbase. Install the following components:

♦ Client component. Allows you to import definitions, create mappings, and create connection objects using the PowerCenter Client.

♦ Repository component. Allows the Repository Service to store and access the Essbase metadata in the repository.

♦ Integration Service component. Allows the Integration Service to run Essbase sessions.

Install these components on the machines that you want to access Essbase.

To install PowerExchange for Hyperion Essbase on Windows:

1. Run setup.exe from the installation package.

2. Click Next.

3. Enter your name and organization name.

4. Click Next.

5. Select the directory where you want to install PowerExchange for Hyperion Essbase.

You can install PowerExchange for Hyperion Essbase in the same location as PowerCenter. By default, it is installed in the following location:

C:\Program Files\PWX_ESSBASE

6. Click Next to begin the installation.

7. Click Next.

8. Select to restart the machine now or later.

9. Click Finish.

If you did not restart your machine in step 8, restart now.

To install PowerExchange for Hyperion Essbase on UNIX:

1. Copy the Server.tar file to the machine.

2. Enter tar -xvf Server.tar command at the prompt to untar the file.

3. Go to the Installer directory.

4. Enter ./install at the prompt.

5. Enter the absolute path to install PowerExchange for Hyperion Essbase.

Step 1. InstallStep 1. Upgrade


You can install PowerExchange for Hyperion Essbase in the same location as PowerCenter.

Installing PowerExchange for Hyperion Essbase 9

Registering the Plug-in

After you install PowerExchange for Hyperion Essbase, register the plug-in with the repository.

A plug-in is an XML file that defines the functionality of PowerExchange for Hyperion Essbase. To register the plug-in, the repository must be running in exclusive mode. Use the Administration Console or the pmrep RegisterPlugin command to register the plug-in.

The plug-in file for PowerExchange for Hyperion Essbase is Essbase.xml. By default, the plug-in file is located in the following directory:

<PowerExchange for Hyperion Essbase Installation Directory>/PWX_ESSBASE/Bin

Copy the Essbase.xml file to the following directory:

<PowerCenter Installation Directory>/server/bin/Plugin

For more information about using the Administration Console to register a plug-in, see the PowerCenter Administrator Guide.

For more information about the pmrep RegisterPlugin command, see the PowerCenter Command Line Reference.

Note: If you do not have the correct privileges to register the plug-in, contact the user who manages the Repository Service.

Step 2. InstallStep 2. Upgrade


Setting the Library Paths

Setting the Library Paths on WindowsVerify that you set the following environment variables to the specified locations:

Step 3. Install

Table 2-1. Environment Variables and Locations

Environment Variable Machine Locations

PATH Integration Service <PowerExchange for Hyperion Essbase Installation Directory>\PWX_ESSBASE\Bin

<Essbase Installation Directory>\AnalyticServices

PowerCenter Client <PowerExchange for Hyperion Essbase Installation Directory>\PWX_ESSBASE\Bin


PWX_ESSBASE Integration Service <PowerExchange for Hyperion Essbase Installation Directory>\PWX_ESSBASE\Bin

PowerCenter Client <PowerExchange for Hyperion Essbase Installation Directory>\PWX_ESSBASE\Bin

ARBORPATH Integration Service <Essbase Installation Directory>\AnalyticServices

PowerCenter Client <Essbase Installation Directory>\AnalyticServices

Setting the Library Paths 11

Setting the Library Paths on UNIX

To set the library paths on Unix:

1. Verify that you set the following environment variables to the specified locations:

2. Add one of the following environment variables on the Integration Service machine based on the applicable operating system:


Environment Variable Machine Locations

PATH Integration Service <PowerExchange for Hyperion Essbase Installation Directory>/PWX_ESSBASE/Bin

<Essbase Installation Directory>/AnalyticServices

PWX_ESSBASE Integration Service <PowerExchange for Hyperion Essbase Installation Directory>/PWX_ESSBASE/Bin

ARBORPATH Integration Service <Essbase Installation Directory>/AnalyticServices


Environment Variable Machine Location

LD_LIBRARY_PATH Linux or Solaris <PowerExchange for Hyperion Essbase Installation Directory>/PWX_ESSBASE/Bin

SHLIB_PATH HP-UX <PowerExchange for Hyperion Essbase Installation Directory>/PWX_ESSBASE/Bin

LIBPATH AIX <PowerExchange for Hyperion Essbase Installation Directory>/PWX_ESSBASE/Bin


Uninstalling PowerExchange for Hyperion EssbaseTo uninstall PowerExchange for Hyperion Essbase, uninstall it from each machine where you installed the Client, Repository Service, or Integration Service components.

Uninstalling from WindowsTo uninstall PowerExchange for Hyperion Essbase from Windows, use the Windows Add/Remove Programs.

Uninstalling from UNIXYou can uninstall the PowerExchange for Hyperion Essbase Repository and Integration Service components from UNIX.

To uninstall the Repository and the Integration Service component from UNIX:

1. Enter ./install at the prompt.

2. Enter the absolute path to the installation directory.

3. When the installer prompts you to overwrite the existing installation or uninstall the components, choose to uninstall the components.

Uninstalling PowerExchange for Hyperion Essbase 13


C h a p t e r 3

Essbase Sources


♦ Overview, 16

♦ Creating a DSN, 17

♦ Type 1 and Type 2 Essbase Source Definitions, 19

♦ Type 3 Source Definitions, 22

♦ Steps to Create Essbase Source Definition, 27

♦ Steps to Identify Attribute Dimensions, 33

♦ Steps to Edit Report Script, 35

♦ Troubleshooting, 37

15

OverviewEssbase source definitions represent metadata in the Essbase system.

Use the Designer Wizard to import metadata from Essbase and create source definitions to read data from the Essbase server.

Use the Designer Wizard to perform the following tasks:

♦ Create and modify a DSN. Create and modify a Data Source Name (DSN) in the PowerCenter. DSN is a name given to a set of information used to connect to and read data from the Essbase server.

♦ Import metadata by creating source definitions. Use the DSN to access the Essbase server, import metadata, and create Type 1, Type 2, and Type 3 source definitions.

♦ Create columns. Create columns and map them to the standard and accounts dimensions. These columns are used to read data from the Essbase server.

♦ Set filter criteria for columns. Define a data category to filter dimensions under Type 1 and Type 2 source definitions. For Type 3 source definition, you can set the filter criteria to import metadata.

♦ Edit report script. Use report scripts to set data filters, command parameters, and the member selection commands to filter dimensions under Type 1 and Type 2 source definitions.

♦ Perform administrative tasks. Connect to Essbase from the PowerCenter Designer to perform some of the Essbase administrative tasks that you can also perform through the Hyperion Essbase Administration Console. For more information about performing administrative tasks, see “Essbase Administration Overview” on page 52.

♦ View details. View information about a DSN, a source definition, or a column.

♦ Preview data. Preview data in the Essbase source after importing a source definition. You can preview data for Type 1 and Type 2 source definitions.

16 Chapter 3: Essbase Sources

Creating a DSNA DSN is a name given to a set of information used to connect and extract data from the Essbase server. Every DSN that you create is associated with a particular Essbase server and has a unique user name and password.

You can create a DSN in the following situations:

♦ You need to connect to the Essbase server for which a DSN is not available.

♦ You need to connect to the Essbase server for which a DSN is available. However, you do not have the privileges to connect to the Essbase server through this DSN.

To create a DSN:

1. In the Source Analyzer, click Sources > Import Essbase Source.

The Designer Wizard appears.

2. Right-click Essbase, and select Create DSN.

Creating a DSN 17

The DSN Creation Wizard appears.

3. Enter the following information to create the DSN:

4. To verify that the connection is successful, click Test Connectivity.

5. Click Save.

Parameters Description

DSN Name Name for the DSN.

Description Description for the DSN.

Server Name Name of the Essbase server.

User Name Essbase user name.

Password Password for the user name.


Type 1 and Type 2 Essbase Source DefinitionsUse the Designer Wizard to perform the following tasks:

♦ Connect to the Essbase server.

♦ Create source definitions to import metadata.

♦ Create columns associated with accounts and standard dimensions.

♦ Create filter expressions.

♦ Identify attribute dimensions.

♦ Edit report scripts.

Connecting to Essbase Server Use a DSN to connect to the Essbase server. Use the Designer Wizard to enter your user name and password and connect to the Essbase server through the DSN. The Designer Wizard displays the source definitions associated with this DSN.

Creating Type 1 and Type 2 Source Definitions When you select a DSN, the Designer Wizard displays the Create Table option. Use this option to access the Table Creation Wizard and create a source definition.

For more information about creating source definitions, see “Steps to Create Essbase Source Definition” on page 27.

Creating Columns for Type 1 and Type 2 Source DefinitionsAfter you create Type 1 and Type 2 source definitions, you can create columns in the source definitions. Use the Column Creation Wizard to create columns.

For Type 1 source definitions, you can create columns for the aliases and the attributes associated with the selected dimensions. You must map at least one dimension and one accounts dimension as a column for the Type 1 source definition.

For Type 2 source definitions, you can create a data column and columns for attributes associated with the selected dimensions. You must map at least one dimension as a column for the Type 2 source definition.

For more information about creating columns for Type 1 and Type 2 source definitions, see “Steps to Create Columns for Type 1 and Type 2 Source Definitions” on page 28.

Creating Filter ExpressionsDefine a data category to filter dimensions under Type 1 and Type 2 source definitions. Use the Set Outline Filter option on the Dimension - Column Mapping dialog box to create filter expressions for dimensions.

Type 1 and Type 2 Essbase Source Definitions 19

For example, you want to import dimensions that begin with “y.” Create a filter expression as “y*.” This expression filters the standard dimensions and displays the dimensions that start with “y”.

Similarly, you want to import accounts dimension that begin with “s” and at level 1 in the accounts dimension hierarchy. Create a filter expression as “s*” and set the level as “1.” This expression filters the accounts dimension and displays the levels that start with “s”, at level 1in the accounts dimension hierarchy.

Figure 3-1 shows the filter expressions for standard and accounts dimensions:

The Designer Wizard displays the standard dimension “Year,” as it is the only dimension starting with “y”. The accounts dimension, displays no members that start with “s” at level 1, so the level 1 is truncated.

Identifying Attribute DimensionsYou can add attribute dimensions to the columns in the Type 1 and Type 2 source definitions. Add attributes dimensions to columns that have attributes associated with them.

You either add all attribute dimensions to a column or select a specific attribute dimension.

For more information about identifying attribute dimensions for Type 1 and Type 2 source definitions, see “Steps to Identify Attribute Dimensions” on page 33.

Editing Report ScriptsYou can edit the report script to filter data for Type 1 and Type 2 source definitions.

Figure 3-1. Creating filter expression


You can edit the report script for the standard dimension columns. You must create standard dimension columns before you edit the report script.

From the Designer Wizard, select a source definition, and select the Report Script option. The Edit Report Script dialog box appears. Configure the Member Selection parameters and the data filters for the selected column.

Note: If you use the Dimension - Column Mapping dialog box to add, modify, or delete columns in the table, the filter conditions in the report script are reset to the default values.

For more information about editing report scripts for Type 1 and Type 2 source definitions, see “Steps to Edit Report Script” on page 35.

Declaring Command ParametersUse the Command Parameters option in the Edit Report Script dialog box to enter the range of column values.

To parameterize the query for an Essbase source definition, you can select <PARAMETERIZED in the Member Selection Command list. The column values must be supplied through Informatica mapping parameters by using a parameter file. The declaration of the <PARAMETERIZED command parameter must start with $$.

The following example shows how to declare the value for $$VAR either in the parameter file or as a default value in an Essbase mapping:

Single Value: $$VAR = “Jan”

Multiple Value: $$VAR= “Jan”, “Feb”, “Mar”

The report script uses substitution variables as command parameters. A substitution variable must start with the ampersand (&) and be declared in Essbase. For example, &Sub_Var, where Sub_Var must be declared as a substitution variable in the Essbase. Substitution variables are used with every selection command except the following:

<PARAMETERIZED

<LINK

<WITHATTR

When the Integration Service extracts data, the substitution variable is replaced by the value defined for the substitution variable.

Type 1 and Type 2 Essbase Source Definitions 21

Type 3 Source DefinitionsUse the Designer Wizard to perform the following tasks:



♦ Create columns mapped to accounts and standard dimensions.

♦ Set filter expressions.

♦ Specify column names and attributes

Connecting to the Essbase Server Use a DSN to connect to the Essbase server. Use the Designer Wizard to enter your user name and password and connect to the Essbase server through the DSN. The Designer Wizard displays the associated source definitions that were created with this DSN.

Creating Type 3 Source DefinitionWhen you select a DSN, the Designer Wizard displays the Create Table option. You can use this option to access the Table Creation Wizard and create a source definition. In the Table Creation Wizard, select the Extract Members (Type 3) option to create Type 3 source definitions.

For more information about creating source definitions, see “Steps to Create Essbase Source Definition” on page 27.

Creating Columns for Type 3 Source DefinitionAfter you create a Type 3 source definition you can create columns in it. Use the Column Creation Wizard to create a column.

For more information about creating columns for Type 3 source definitions, see “Steps to Create Columns for Type 3 Source Definition” on page 30.

Example of Setting Filter CriteriaThe Integration Service extracts the metadata based on the filter criteria specified in the Dimensions - Column Mapping dialog box. The following example shows the filter criteria used by Type 3 source definitions to extract metadata:

- Measures Accounts <3> (Label Only)

- Profit(+)(Dynamic Calc)

- Margin(+)<2>(Dynamic Calc)

Sales(+)(Cur Category=dsfsf COGS(-)(Expense Reporting)

- Total Expenses(-)<3>(Dynamic Calc)(Expense Reporting)


The following table describes the filter criteria listed in the above example:

Specifying Column Names and AttributesYou can create columns in a Type 3 source definition with the following column names and attributes:

Marketing(+)(Expense Reporting) Payroll(+)(Expense Reporting) Misc(+)(Expense Reporting)

- Inventory(~)<3>(Label Only)

Opening Inventory(+)(TB First)(Expense Reporting) Additions(~)<3>(Label Only) Ending Invenotry(~)(TB First)(Expense Reporting)

- Ratios(~)<3>(Label Only)

Margin%(+)(Dynamic Calc)(TwoPass) Profit%(~)(Dynamic Calc)(TwoPass) Profit per Ounce(~)(Dynamic Calc)(TwoPass)

Filter Criteria Description Example

<Descendant Descendants are members in the branches below a parent.

Profit, Inventory, and Ratios are the descendants of Measures. The child node of Profit, Inventory, and Ratios are also descendants of Measures. If Measures is mapped to a column and the Filer Criteria set to Descendant, the Integration Service extracts the metadata for all the members under these Measures.

<IDescendant IDescendants are the same as Descendants.

If Measures is mapped to a column and the Filer Criteria set to IDescendants, the Integration Service extracts the metadata for all the members including Measures.

<Children Child is any member that has a parent above it.

Sales, Margin, and Cost of Goods Sold are child nodes of the parent name. If Measures is mapped to a column, and the Filer Criteria set to Child. The Integration Service extracts the metadata for Profit, Inventory, and Ratios.

<IChildren IChild is same as Child. If Measures is mapped to a column and the Filer Criteria set to IChild. The Integration Service extracts the metadata for Profit, Inventory, and Ratios including Measures.

<Level0 Level0 are the members that have no child nodes.

Opening Inventory, Additions, and Ending Inventory are level 0 members. If Measures is mapped to a column and the Filer Criteria set to Level0. The Integration Service extracts the metadata for all level 0 members under Measures, that are Sales and COGS.

<MemberOnly Integration Service imports metadata for the member mapped as a column.

If Measures is mapped to a column and the Filer Criteria set to MemberOnly. The Integration Service extracts the metadata for the Measures column and excludes the descendants and the child nodes.

- Measures Accounts <3> (Label Only)

Type 3 Source Definitions 23

♦ MemberName. Use the name of the member to create a column.

♦ ParentName. Use the name of the member parent to create a column.

♦ Alias. Use the alias associated with the member to create a column.

♦ DataStorage. Use the data storage setting to create a column.

Table 3-1 lists the default values for data storage:

♦ TwoPassCalc. Use the TwoPassCalc setting to create a column.

Table 3-2 lists the default values for TwoPassCalc:

♦ Consolidation. Use the Consolidation setting to create a column.

Table 3-3 lists the default values for Consolidation:

♦ UDA. Use the comma-separated list of User Defined Attributes (UDA) to create a column.

♦ Formula. Use the formula associated with a member to create a column.

Table 3-1. Default Values for Data Storage

Properties Values

Store data S

Dynamic calc and store V

Dynamic calc X

Label only O

Never share N

Shared member NULL

Table 3-2. Default Values for TwoPassCalc

Properties Values

TwoPassCalc ON T

TwoPassCalc OFF NULL

Table 3-3. Default Values for Consolidation

Properties Values

Addition +

Subtraction -

Multiplication *

Division /

Percentage %

Ignore ~


♦ Comment. Use the comment associated with a member to create a column.

♦ TimeBalance. Use the TimeBalance property set for a member to create a column.

Table 3-4 describes the default values for TimeBalance:

♦ TimeBalanceSkip. Use the TimeBalanceSkip option set for a member to create a column.

Table 3-5 describes default values for TimeBalanceSkip:

♦ VarReporting. Use the variance reporting property set for a member to create a column.

Table 3-4. Default Values for TimeBalance

Properties Values Description

None NULL Sets the time balance to NONE and includes zeros and missing values to calculate parent values.

First F Sets the time balance as First if you want the parent value to represent the first member value at the beginning of a time period.

Last L Sets the time balance as Last if you want the parent value to represent the last member value at the end of a time period.

Average A Sets the time balance as Average if you want the parent value to represent the average child node value.

Table 3-5. Default Values for TimeBalanceSkip


None NULL Select NONE to include zeros and missing values when calculating parent values.

Missing M Skips missing data when calculating the parent value.

Zeros Z Skips data that equals zero when calculating the parent value.

Both Missing and Zeros

B Skips both missing data and data that equals zero when calculating the parent value.

Type 3 Source Definitions 25

Table 3-6 describes default values for VarReporting:

♦ CurrCon. Use the currency conversion type set for a member to create a column.

Table 3-7 lists the default values for CurrCon:

♦ CurConvCategory. Use the currency conversion category set for a member to create a column.

♦ AttributeMemberValues. Use a comma-separated list of associated attribute dimension members to create a column.

Table 3-6. Default Values for VarReporting


Non Expense NULL For non-expense items such as the sales, actual expenses must be higher than the budgeted expenses. When actual expenses are less than the budget, the variance is negative. The @VAR function calculates ACTUAL - BUDGET. For example, if budgeted sales are $100 and actual sales are $110, the variance is 10. The members are set to non-expense as a default.

Expense E For expense items, actual expenses must be lower than the budgeted expenses. When actual expenses are greater than the budgeted expenses, variance is negative. The @VAR function calculates BUDGET - ACTUAL. For example, if budgeted expenses are $100 and actual expenses are $110, the variance is -10.

Table 3-7. Default Values for CurrCon

Properties Values

None 0

Category 1

No category 2


Steps to Create Essbase Source DefinitionThis section describes how to create an Essbase source definition.

To create Essbase source definition:



2. Right-click the DSN, and select Create Table.

The Table Creation Wizard appears.

Tip: The default outline type for an application appears when you select the application.

3. Enter the following information to create the table:

Parameter Description

Table Name Name of the table.

Description Description for the table.

Application Name of the application.

Database Name of the database.

Outline Name of the database outline.

Steps to Create Essbase Source Definition 27

4. Click Save.

Steps to Create Columns for Type 1 and Type 2 Source DefinitionsThis section describes how to create columns associated with standard or accounts dimensions and create filter expressions.

To create columns and create filter expressions:



2. Right-click a table, and select Create Column.

The Dimension - Column Mapping dialog box appears.

Tip: Dimension displays standard dimensions and members of the account dimension.

3. Click Set Filter to specify filter expressions.

Table Type Type of table to be created. Select one of the following types of tables:- Accounts dimension member as a column (Type1).- Accounts dimension as column (Type 2).- Extract Members (Type 3).

Note: If the accounts dimension exists in the selected Essbase outline, the accounts dimension member as a column (Type 1) option is selected by default. If the accounts dimension is not a part of the selected Essbase outline, the accounts dimension as a column (Type 2) option is selected by default.



The Dimension - Column Mapping dialog box displays the Set Outline Filter options.

4. Enter the following information to filter dimensions and members:

5. Click OK.

The Dimension - Column Mapping dialog box displays the standard dimensions and members of the account dimension.

6. Select a dimension, and click the right arrow to map the dimension to a column.

The Column Creation Wizard appears.


Dimension Defines the data category used to organize business data for retrieval and consolidation of values. Select the check box to filter dimensions.

Filter Expression for Dimensions

Expression to filter the dimensions. For more information about creating filter expressions, see “Creating Filter Expressions” on page 19.

Accounts dimension members

Defines the data category used to organize accounts dimension members. Enable to filter expression for accounts dimension.

Filter Expression For Accounts dimension

Expression to filter accounts dimension members. Filter expression is a regular expression. Use asterisk (*) as a wild card character. For more information about creating filter expressions, see “Creating Filter Expressions” on page 19.

Level Measure level used to filter dimensions.


Tip: The Dynamic Time Series Members options appear for the time dimensions that contain the Dynamic Time Series (DTS) members.

7. Enter the following information to create a column:

8. To retrieve data for Dynamic Time Series Tag, select the Dynamic Time Series name from the DTS list.

9. Select the leaf member of the time dimension from the Member Name list, and click the right arrow.

The Dynamic Time Series Tag displays the associated DTS and member names.

10. To delete a mapped column, select the dimension name, and click the right arrow.

11. Click OK.

Steps to Create Columns for Type 3 Source DefinitionUse the following steps to create columns mapped to dimensions and set filter criteria.


Column Name Name of the column. If the column name exceeds 69 characters, the column name is truncated. This does not lead to any error in data extraction or loading.

Precision Precision value for the column.

User Defined Attributes Attributes to query the database based on the User Defined Attributes (UDA). The User Defined Attributes option appears if the UDAs are defined for the leaf-level members of the dimension.


To create columns in a Type 3 source definition:





The Dimension area lists the standard dimensions, accounts dimensions, and the members of these dimensions. You can associate any dimension or level except level 0 to extract the metadata for the members.

3. Select a dimension, and click the right arrow to map the dimension to a column.

The Dimension - Column Mapping dialog box displays the Column Information options.


Tip: You cannot edit the default outline member name.

4. Enter the following column information:

5. Click Save.


Column Name Name for the column. The default precision value for this column is 80.

Use Mapping Parameter

Mapping parameters for the column.

Mapping Parameter Name of the mapping parameter mentioned in the parameter file. For more information about mapping parameters, see “Declaring Command Parameters” on page 21.

Filter Criteria Filter criteria to import metadata from a Type 3 source definition. For more information about filter criteria, see “Example of Setting Filter Criteria” on page 22.


Steps to Identify Attribute DimensionsThis section describes how to use the Designer Wizard to perform the following tasks:

♦ Add all attribute dimensions to columns.

♦ Select and add specific attribute dimension to columns.

To add all attribute dimensions to the source definition:



2. Right-click the column name, and select Add All Attributes.

The Designer Wizard adds and displays all the attributes associated with the dimension.

To add selected attribute dimensions to a source definition:



2. Right-click the column name, and select Select Attributes.

Steps to Identify Attribute Dimensions 33

The Select Attributes dialog box appears.

3. From the attribute list, select the attributes to be added.

4. Click OK.


Steps to Edit Report ScriptTo edit the report script for Type 1 and Type 2 source definitions:



2. Right-click a table, and select Report Script.

The Edit Report Script dialog box appears.

3. Select the column and dimension name.

4. Configure the following Member Selection parameters:


Get data from DTS Members Only

Extracts data for DTS members. This option is enabled if a column is mapped to a Time dimension for which DTS members are selected.

Member Sort Order Sorts the members while extracting data. You can use the following order options:- <SORTNONE- <SORTASC- <SORTDESC

Member Sort Option Sets the option to sort the extracted data. You can use the following sort options:- <SORTLEVEL- <SORTGEN- <SORTMEMBERNAME

Steps to Edit Report Script 35

5. Click Save

6. Configure the following data filters.

7. Click Save.

8. Click Show Report Script.

The Report Script dialog box appears.

9. Click Validate Report Script to verify the resulting script.

10. To restore all the Member Selection and Data Filter conditions, click Reset.

11. Click OK to save the report script.

The report script must be valid before you close the Report Script dialog box.

Member Selection Command

Retrieves the child nodes under the Member Selection Command. - To parameterize the query for the Essbase source definition, select

<PARAMETERIZED in the Member Selection Command list. - To retrieve aggregated data for the non-leaf members, edit the member selection

commands in the report script. For example, use <DIMBOTTOM command retrieves leaf-level data.

Note: Command Parameter displays the selected column name.


Data Range Command Filters the Essbase command dimensions. You can use the following command options:- <RESTRICT- <TOP- <COTTOM

Command Parameters Defines the range for column values in the Command Parameters field.For more information about command parameters, see “Declaring Command Parameters” on page 21.



TroubleshootingThe Designer Wizard fails to create the DSN with the following error: Essbase Initialization Failed.

Verify that the environment variables ARBORPATH and PATH, used by the Hyperion Essbase database, are set to the following location:


For more information, see “Setting the Library Paths” on page 11.

Troubleshooting 37


C h a p t e r 4

Essbase Targets


♦ Essbase Targets Overview, 40

♦ Type 1 and Type 2 Target Definitions, 41

♦ Type 3 Target Definitions, 43

♦ Steps to Create Essbase Target Definition, 44

♦ Loading Data with a Rules File, 49


39

OverviewEssbase target definitions represent metadata in the Essbase system.

Use the Designer Wizard to import metadata from Essbase and create target definitions to write data in the Essbase server.

Use the Designer Wizard to perform the following tasks:

♦ Create and modify a DSN. Create and modify a Data Source Name (DSN) in the PowerCenter. DSN is a name given to a set of information used to connect to and write data in the Essbase server. For more information about creating and modifying a DSN, see “Creating a DSN” on page 17.

♦ Import metadata by creating target definitions. Use a DSN to access the Essbase server, import metadata, and create Type 1, Type 2, and Type 3 target definitions.

♦ Create columns. Create columns and map them to the standard and accounts dimensions. These columns are used to write data in the Essbase server.

♦ Configure rules file to load data. Specify a rules file and a valid separator as a metadata extension in the target definition. Essbase uses this file to load data in the Essbase server. Type 1 and Type 2 target definitions use a rules file when loading data into the database.

♦ Perform administrative tasks. Perform administrative tasks within the Designer Wizard. These tasks are similar to the tasks performed in the Hyperion Essbase Console. For more information about performing administrative tasks, see “Essbase Administration Overview” on page 52.

♦ View details. Use the View Details option to view information about a DSN, a target definition, or a column.

40 Chapter 4: Essbase Targets

Type 1 and Type 2 Target DefinitionsUse the Designer Wizard to perform the following tasks:


♦ Create target definitions to import metadata.

♦ Create columns mapped to accounts dimensions.

♦ Create filter expressions.

Connecting to Essbase Server You can use a DSN to connect to the Essbase server. Use the Designer Wizard to enter your user name and password and connect to the Essbase server through the DSN. The Designer Wizard displays the target definitions associated with the DSN.

Creating Type 1 and Type 2 Target DefinitionsWhen you select a DSN, the Create Table option appears in the Designer Wizard. Use this option to access the Table Creation Wizard used to create a target definition.

For more information about creating target definitions, see “Steps to Create Essbase Target Definition” on page 44.

Creating Columns for Type 1 Target DefinitionsAfter you create a Type 1 target definition, you can create columns for the Type 1 target definition.

When you select a target definition, the Designer Wizard displays the Create Table option. You can use this option to access the Dimension - Column Mapping dialog box.

Use the Dimension - Column Mapping dialog box to select dimensions and create a column mapped to these dimensions. You must map at least one accounts dimension and one measure to a column in the table.

For more information about creating column, see “Steps to Create Columns for Type 1 Target Definition” on page 45.

Columns in Type 2 Target DefinitionsWhen you create a Type 2 target definition, the Designer Wizard performs the following tasks:

♦ Add columns for all the dimensions in the Essbase outline.

♦ Add a data column to receive the data loaded into Essbase.

Note: You cannot create columns for Type 2 target definitions.

Type 1 and Type 2 Target Definitions 41

Creating Filter ExpressionsUse the Set Outline Filter option on the Dimension - Column Mapping dialog box, to create filter expressions for standard and accounts dimensions.

For more information about creating filter options, see “Creating Filter Expressions” on page 19.


Type 3 Target DefinitionsUse the Designer Wizard to perform the following tasks:



♦ Create columns mapped to accounts and standard dimensions.

Connecting to Essbase Server You can use a DSN to connect to the Essbase server. Use the Designer Wizard to enter your user name and password and connect to the Essbase server through the DSN. The Designer Wizard displays the target definitions associated with the DSN.

Creating Type 3 Target DefinitionUse the Designer Wizard to create Type 3 target definition and write data in the Essbase server.

When you select a DSN, the Designer Wizard displays the Create Table option. You can use this option to access the Table Creation Wizard used to create a target definition. In the Table Creation Wizard, select the Dynamic dimension building (Type 3) option to create Type 3 target definition.

For more information about creating target definitions, see “Steps to Create Essbase Target Definition” on page 44.

Creating Columns for a Type 3 Target DefinitionAfter you create a Type 3 target definition, you can create columns for the Type 3 target definition.

When you select a target definition the Create Columns option is displayed on the Designer Wizard. You can use this option to access the Dynamic Dimension Building dialog box used to create columns and specify the data type and Precision for the column. For more information about creating column, see “Steps to Create Columns for Type 3 Target Definition” on page 47.

You can also specify the location of the rules files on the Dynamic Dimension Building dialog box. The rules file is used to load data into the target tables. For more information about how to load data using rules file, see “Loading Data with a Rules File” on page 49.

Type 3 Target Definitions 43

Steps to Create Essbase Target Definition To create Essbase target definition:

1. In the Target Designer, click Target > Import Essbase Target.


2. In the Designer Wizard, right-click the DSN, and select Create Table.

The Table Creation Wizard appears.


Tip: The default outline type for an application appears when you select the application.

3. Enter the following information to create the table.

4. Click Save.

Steps to Create Columns for Type 1 Target DefinitionThis section describes how to create columns mapped to dimensions.

To create columns for a Type 1 target definition:






Table Name Name of the table.

Description Description for the table.


Database Name of the database.

Outline Name of the database outline.

Table Type Type of table to be created. Select one of the following types of tables:- Accounts dimension member as a column (Type1).- Accounts dimension as column (Type 2).- Dynamic dimension building (Type 3).

Note: If the accounts dimension exists in the selected Essbase outline, the accounts dimension member as a column (Type 1) option is selected by default. If the accounts dimension is not a part of the selected Essbase outline, the accounts dimension as a column (Type 2) option is selected by default.

Steps to Create Essbase Target Definition 45

Tip: Dimensions displays standard dimensions and members of the account dimension.

3. Use the Set Filter options to filter dimensions and members.

For more information about setting the filter options, see “Creating Filter Expressions” on page 19.

4. Select the members of the accounts dimension, and click the right arrow to map the members to columns.

The Column Creation Wizard appears.

5. Enter column name.


6. Click OK.

The Dimension - Column Mapping dialog box displays the mapped dimensions.

7. To delete a mapped column, select the dimension name, and click left arrow.

8. Click Save.

Steps to Create Columns for Type 3 Target DefinitionThis section describes how to create columns in a Type 3 target definition.

To create columns in a Type 3 target definition:



The Dynamic Dimension Building dialog box appears.

3. Configure the following parameters:


Column Name Name of the column.

Column Type Select the datatype to be created from the following options:- Text- Numeric- Date- Boolean

Steps to Create Essbase Target Definition 47

4. Click the right arrow to add a column.

The created columns appear in the Imported Tables list. You must create at least one column.

5. Select a column and click the left arrow to remove the column from the Selected Columns list.

6. Click Save.

Column Precision

Precision for the columns. You can use the following precision values:- Text. Default is 80. You can edit the default precision value. - Numeric. Default is 15. You cannot edit the precision value. - Date. Default is 10. You cannot edit the precision value. - Boolean. Default is 1. You cannot edit the precision value.

Rule File Selection

Use the following options to select the Rule File:- Essbase server. Select the Server option to use the rules file for the Essbase server.- Integration Service. Select the Client option to use the rules file, local to the Integration

Service.For more information about rule files, see “Loading Data with a Rules File” on page 49.



Loading Data with a Rules FileEssbase uses the rules file to load data into Essbase. A rules file stores the logical pattern that determines how the data is loaded into the database. Type 3 target definitions use a rules file to write data into the database.

You can define a rules file as a metadata extension in the target definition. Specify the name and the separator for the rules file. Use the following valid separators in the rules file:

♦ Comma

♦ Tab

♦ Space

♦ Custom characters

Specify the absolute path for the rules file in the RulesFile metadata extension if the rules file resides on the machine hosting the Integration Service. Ensure that the separator specified in the metadata extension matches the value in the rules file.

The rules file can reside on either the Essbase server or Integration Service:

♦ Essbase server. If the rules file resides on the Essbase server, enter the rules file name in the RuleFile extension name. For example, if you use ‘LoadRule’ that resides on the Essbase server, enter ‘LoadRule’ as the value for the RuleFile extension name.

♦ Integration Service. If the rules file resides on the computer hosting Integration Service, enter the absolute path of the rules file. For example, if you use ‘LoadRule.rul’ that resides in the C:\Rulesfiles folder, enter C:\Rulesfiles\LoadRule.rul as the value for the RuleFile. extension name.

Figure 4-1 shows the Metadata Extensions tab used to select rules file and rules file separator:

Figure 4-1. Selecting Rules File and Rules Separator

Loading Data with a Rules File 49

Troubleshooting The Designer Wizard fails to create the DSN and the following error appears: Essbase Initialization Failed.

Verify that the environment variables ARBORPATH and PATH, used by the Hyperion Essbase database, are set to the following location:


For more information, see “Setting the Library Paths” on page 11.

Error occurs when using the Designer Wizard. Complete the following tasks:

1. Verify that the Essbase API libraries are installed.

2. Verify that the Essbase environment variables are set.

3. Read the Essbase error code from the PWX_ESSBASE_TraceLog.log file generated in the following directory:

<PowerExchange for Hyperion Essbase Installation Directory>/PWX_ESSBASE/Bin


C h a p t e r 5

Essbase Administration


♦ Essbase Administration Overview, 52

♦ Creating an Application, 53

♦ Creating an Application, 53

♦ Creating a Database, 56

♦ Adding a Dimension, 58

♦ Adding a Member, 62

51

OverviewYou can perform administrative tasks within the Designer Wizard. These tasks are similar to the tasks you can perform in the Hyperion Essbase Console.

Use the Administration dialog box to perform the following administrative tasks:

♦ Create an application. You can connect to an Essbase server to create or delete an application.

♦ Create a database. You can connect to an Essbase server to create or delete a database.

♦ Add dimensions. You can add dimensions to a database. Add standard or attribute dimensions and specify properties. You can modify the properties of an existing dimension.

♦ Add members. You can select a dimension and add members to it. Add consolidation, calculation, and data storage properties to a member. You can modify the properties of an existing member.

52 Chapter 5: Essbase Administration

Creating an ApplicationAn application is a structure that contains one or more Essbase databases and related files that control system variables, such as memory allocation and auto load parameters. You can use the Administration dialog box to create or delete an application.

To create an application in Essbase:


-or-

In the Target Designer, click Target > Import Essbase Target.


2. Click Administration.

The Administration dialog box appears

3. Enter the connection information, and click Connect.

The Administration dialog box displays the applications and databases.

Creating an Application 53

4. Right-click Applications, and select Create Application.

The Administration dialog box displays the Create Application option.


5. Enter the following information:

6. Click OK.

The application appears in the Applications list. You can add databases, members, rules files, or calculation scripts to this application.

To delete an application from Essbase:


-or-




The Administration dialog box appears.

3. Right-click the application name, and select Delete Application.

The application and the associated databases, rules files, and calculation scripts are deleted.

Application Parameters Description

Application Name of the application. The application name must not exceed eight characters.

Application Type Application Type to create an application. Select one of the following types:- Block Storage. Organizes data in blocks. It is used to perform consolidations, analysis,

and forecasting.- Aggregate Storage. Aggregates and stores data with improvements in aggregation time.

Creating an Application 55

Creating a DatabaseAfter you create an application, you can create a database in the application. You can use the Administration dialog box to create or delete a database. The Administration dialog box displays the applications and associated databases.

To create a database:


-or-





3. Right-click application name, and select Create Database.

The Administration dialog box displays the Create Database options.

4. Enter the following information:




5. Click OK.

The database appears in the Database list under the corresponding application. You can add dimensions and members to this database.

To delete a database:


-or-





3. Right-click the database name, and select Delete Database.

The database and the associated rules files, calculation scripts, and report scripts are deleted.

Database Name of the database. The database name must not exceed eight characters.

Database Type Type of database to be created. Select one of the following types:- Currency. Translates financial data from one currency into another currency. Enables

comparison and consolidation of financial data with different currencies.- Normal. Performs the basic functions of a database, but does not translate and

compare financial data.


Creating a Database 57

Adding a DimensionAfter you create a database, you can add dimensions to it. You can use the Modify Outline dialog box to perform the following tasks:

♦ Add standard and attribute dimensions to database outline.

♦ Add, edit, and delete members at any level in a dimension.

Use the following procedure to add dimensions to a database.

To add a dimension:


-or-






3. Select a database, and click Modify Outline.

The Modify Outline dialog box appears.

Tip: The Modify Outline option is enabled if you select the database.

4. Right-click the outline name, and select Add Dimension.

The Modify Outline dialog box displays the Dimension Properties option.

Adding a Dimension 59

5. Enter the following information to create the dimension:

Dimension Properties Description

Dimension Name

Name of the dimension.

Comments Description for the dimension.

Dimension Type

Type of dimension used to create a dimension. Select one of the following types:- None- Accounts- Country- Time- Currency Partition- Attribute

Attribute Type

Attribute type for a dimension. Select one of the following types:- Numeric- Text- Boolean- Date

Base Dimension

Base dimension for the attribute dimension. Enabled if you select the attribute Dimension Type.

TwoPass Calculator

TwoPassCalc setting for the dimension from the Two Pass Calculation list.


6. Click OK.

The created dimension appears in the outline.

7. Click Save.

Data Storage Data storage for the dimension. Data Storage is enabled if you select the Standard Dimension Type.

Dimensional Storage

Storage property of the dimension:- Sparse- DenseEnabled if you select the Standard Dimension Type.

Dimension Properties Description

Adding a Dimension 61

Adding a MemberAfter you add a dimension, you can add a member at any level to it. You can use the Modify Outline dialog box to add, modify, and delete members. After you add a dimension and members to a database, the Modify Outline dialog box displays these dimensions and members below the database in the outline.

You can add a member at any level in a dimension.

To add a member:


-or-





3. Select the database, and click Modify Outline.


4. Right-click a dimension name, and select Add Member.

The Modify Outline dialog box displays the Member Properties option.


5. Enter the following information to add a member to the outline:

6. Click OK.

The member appears in the outline under the corresponding application and database.

7. Click Save.

To modify a member:


-or-





3. Select the database, and click Modify Outline.


4. Right-click member name, and select Update Member.

5. Change the member properties.

Member Properties Description

Member Name Name of the member.

Comments Description for the member name.

Alias Alias for the member.

Consolidation Consolidation properties of the member name. Select the consolidation property from one of the following:- (+) Addition- (-) Subtraction- (*) Multiplication- (/) Division- (%) Percent- Ignore.

Two-Pass Calculation

TwoPassCalc setting for the dimension from the Two Pass Calculation list.

Data Storage Data Storage type for the Member name. Select the data storage type from the following:- Store Data- Dynamic Calc and Store- Dynamic Calc- Never Share- Label Only- Shared Member

Adding a Member 63

6. Click Save.

To delete a member:

In the Modify Outline dialog box, right-click the member name, and select Delete Member.


C h a p t e r 5

Essbase Mappings

This chapter includes the following topic:

♦ Creating Essbase Mappings, 66

65

Creating Essbase MappingsPowerCenter for Hyperion Essbase integrates Essbase Online Analytical Processing (OLAP) Server with PowerCenter. You can use the Normalize Essbase cube feature to extract OLAP data in a relational format for planning, analysis, and management.

The Essbase database stores data in a multi-dimensional format. Essbase extracts the OLAP data into a fact table in a relational format.

The dimension tables store all the members under the associated dimensions. Essbase converts the OLAP source into a relational model for normalization.

The relational model is based on a star schema model that contains a central fact table and multiple dimension tables. After the source definition is normalized, generate and execute SQL in the Target Designer to create the dimension tables.

Note: You can create a relational model for Type 1 and Type 2 source definitions.

To normalize an Essbase cube:

1. In the Mapping Designer, click Mapping > Normalize Essbase Cube.

The Normalize Essbase Cube dialog box appears.

2. Select a source from the list.

3. Enter the target name.

The names of the dimension tables correspond to the column names in the Essbase source definition. Oracle is the default target database.

4. Click Finish.

66 Chapter 5: Essbase Mappings

The mapping is generated with the source definition, normalized fact tables, and dimension tables. You can use the Target Designer to change the default target database and load the relational data to the non-Essbase system.

ExampleThe following example shows how to use Normalize Essbase Cube and create a relational model.

Consider an application with the following dimensions:

♦ Year

♦ Measures

♦ Product

♦ Market

♦ Accounts

♦ Scenario

The following table displays the Profit, Cost of Goods, Total Expenses, and Ratios for the Product 100-10 in the Actuals scenario across all the regions:

Use the following steps to Normalize Cube Feature to extract the above table in a relational format:

1. Create a Type1 source definition. Import a table with the following dimensions:

♦ Standard dimensions as Product, Market, and Scenario.

♦ Accounts dimension as Profit, COGS, and Ratios.

Scenario Regions Product Profit COGS Ratios

Actuals East 100-10 23205 7443 67.93

3068 1238 58.15

1467 596 59.1

West 100-10 14862 6059 59

8923 5216 59.2

4521 2829 36

South 100-10 10604 4667 48

5676 2909 48

22008 8972 59

Central 100-10 14862 6059 59

3068 1238 58.15

4521 2829 36

Creating Essbase Mappings 67

2. Edit the Report Script and set IDescendents. Edit the report script and identify the number of levels to be imported for the standard dimensions. Select the <IDESCENDANTS member selection command for the Market, Product, and Scenario dimensions.

3. Normalize the Essbase cube. Select source definition and enter a target fact table. When you normalize a cube, the Designer creates the following objects:

− Mapplet containing a transformation for each dimension.

− Fact table.


− Dimension target tables for each standard dimension.

4. Create mappings. You can use the mapplet to create mappings in the Designer. You can extract the data in a relational format and load data to the following targets:

Creating Essbase Mappings 69


C h a p t e r 6

Essbase Sessions


♦ Configuring Application Connections, 72

♦ Configuring a Session for an Essbase Source, 74

♦ Configuring a Session for an Essbase Target, 75

♦ Using Calculation Scripts, 76


71

Configuring Application ConnectionsConfigure an application connection before the Integration Service extracts data from the sources or loads data into targets. When you configure an Essbase application connection, specify the connection attributes that the Integration Service uses to connect to an Essbase database.

You can use the connection parameters to specify the connection settings. For more information about connection parameters, see the PowerCenter Workflow Administrator Guide.

Specify the values for application and database in the connection object to define the default application and database names stored in the table definition. Essbase uses the values specified in the connection object.

To configure an Essbase application connection:

1. In the Workflow Manager, click Connection > Application.

The Application Connection Browser dialog box appears.

2. Click New.

3. From the Select Subtype list, select EssbaseConnection.

4. Click OK.

The Connection Object Definition dialog box appears.

72 Chapter 6: Essbase Sessions

5. Enter the following connection information:

Connection Attribute Description

User Name User name to connect to Essbase.

Password Password to connect to Essbase.

ServerHost Essbase server name.

Application Application type. Default is none.

Database Name of the database. Default is none.

Configuring Application Connections 73

Configuring a Session for an Essbase SourceTable 6-1 describes the session properties for an Essbase source:

Setting the Partition Query ConditionUse the following syntax to specify the partition query condition:

♦ You can extract data based on the attribute dimension:

{ATTR <standard-dimension-name>} <attribute-dim-name> operator value.

For example:

{ATTR Market} Population > 200000

♦ You can extract data based on the Accounts dimension members:

{MSR} Measure-member-name operator value.

For example:

{MSR} Sales > 10000

♦ You can extract data based on the User Defined Attribute:

{UDA <standard-dimension-name>} UDA1 name, UDA2 name.

For example:

{UDA Market} Major_Market

When a partition query condition is based on a UDA, the UDA is applied while mapping the corresponding standard dimension in the table.

Note: You can use this functionality for Type 1 and Type 2 source definitions.

Table 6-1. Session Properties for Essbase Sources

Source Options Description

Run Calculation Script only

Executes the calculation script on the Essbase database. Disable this option to extract data from the database.

Calculation Script Name

Provides name of the calculation script to calculate the database. For more information about calculation scripts, see “Using Calculation Scripts” on page 76.

Suppress data Indicates how to suppress data:- None. No data is suppressed.- Missing. Data with missing values is suppressed.- Zeros. Data with zero values is suppressed.- Missing and Zeros. Data with missing values and zero values is suppressed.

Suppress shared members

Suppresses the shared members when data is extracted.

Partition Query Condition

Queries each partition based on attribute dimensions, Accounts dimension members, or User Defined Attributes (UDA).


Configuring a Session for an Essbase TargetTable 6-2 describes the properties that you can configure for Essbase target:

For Type 3 targets, the Integration Service logs all the errors occurred while building dimensions in the builddim.err file. The Integration Service creates the builddim.err file in PWX_ESSBASE\Bin directory if the error file is not specified. You can use this path to log the error messages in the dynamic dimension building, if the absolute path is specified in the error log file.

The error log file must be local to the Integration Service. The Integration Service creates the file in the PWX_ESSBASE\Bin directory, if the absolute path is not specified.

Table 6-2. Session Properties for Essbase Target

Target Property Description

Clear database Clears the data blocks before loading the data into Essbase:- None. Database is not cleared.- All. Clears all data blocks.- Upper Blocks. Clears all consolidated level blocks. - Non-Input Blocks. Clears data blocks that contain calculated values.For the Aggregate Storage Outline application, the Upper Blocks and Non-Input Blocks options are not applicable.

Run Calculation Script only

Executes the calculation script on the Essbase database. Disable this option to load data to the database.

Calculation Script Name

Provides name of the calculation script. For more information about calculation scripts, see “Using Calculation Scripts” on page 76.

Error log File File used to log errors when the Integration Service loads data to Essbase. Specify the path for the error log file. Each partition has its own error log file.

Note: These target options are applicable for Type 1 and Type 2 target definitions.

Configuring a Session for an Essbase Target 75

Using Calculation ScriptsA calculation script contains a series of commands, equations, and formulas that describe how to calculate a database and retrieve aggregate data. You can create scripts for all types of calculations except predefined outline calculations.

Running Calculation ScriptsConfigure the Calculation Script Name session attribute to run calculation scripts. Enter the absolute path for the calculation script if it resides on the machine hosting the PowerCenter Client.

The Integration Service runs the calculation script before reading data from Essbase or after writing data into Essbase.

If you do not provide a calculation script, the dynamic calculation members are calculated using the default formulas defined in the outline.

Note: You can run calculation scripts for Type 1 and Type 2 source and target definitions.

If you select the Run Calculation Script only option, no data is extracted or loaded, and only the Calculation Script is executed on the Essbase server.


TroubleshootingEssbase libraries could not be loaded on UNIX.Verify the library path settings. If the problem persists even after setting the correct library path, restart the Integration Service.

For more information, see “Setting the Library Paths on UNIX” on page 12.

Troubleshooting 77


A p p e n d i x A

Datatypes

This appendix includes the following topic:

♦ Hyperion Essbase and Transformation Datatypes, 80

79

Hyperion Essbase and Transformation DatatypesPowerCenter uses the following datatypes in the Essbase mappings:

♦ Hyperion Essbase native datatypes. Hyperion Essbase datatypes appear in the Essbase definitions in a mapping.

♦ Transformation datatypes. Set of datatypes that appear in the transformations. They are internal datatypes based on ANSI SQL-92 generic datatypes, which the Integration Service uses to move data across platforms. They appear in all transformations in a mapping.

When the Integration Service reads source data, it converts the native Hyperion Essbase and Transformation datatypes to the comparable transformation datatypes before transforming the data. When the Integration Service writes to a target, it converts the transformation datatypes to the comparable native datatypes. For more information about datatypes, see the PowerCenter Designer Guide.

Table A-1 lists the Hyperion Essbase datatypes that PowerCenter supports and the corresponding transformation datatypes:

Table A-1. Essbase and Transformation Datatypes

Essbase Datatype

Transformation Datatype Range

Text String 1 to 104,857,600 characters

Numeric Decimal Precision 15, scale 0

Date Date Jan 1, 1753 AD to Dec 31, 9999 AD (precision to nanosecond)

Boolean String 1 to 104,857,600 characters

80 Appendix A: Datatypes

A p p e n d i x B

Error Messages

This appendix includes the following topics:

♦ Designer Error Messages, 82

♦ Integration Service Error Messages, 83

81

Designer Error Messages Failed to add menu item Import Essbase Source.Cause: The PWX_ESSBASE environment variable is not set to the <PowerExchange

for Hyperion Essbase Installation Directory>\PWX_ESSBASE\Bin directory.

Action: Set the PWX_ESSBASE environment variable to the <PowerExchange for Hyperion Essbase Installation Directory>\PWX_ESSBASE\Bin directory.

Failed to add menu item Import Essbase Target.Cause: The PWX_ESSBASE environment variable is not set to the <PowerExchange



Failed to find the PWX_ESSBASE environment variable. Cause: The PWX_ESSBASE environment variable is not set to the <PowerExchange



Unable to find the source table in the repository.Cause: The Designer Wizard could not find the source table in the repository. The

source table name is invalid.

Action: Verify that the source table information entered is correct.

Unable to import the source table information from the repository.Cause: The Designer Wizard could not import the source table information. The

source table name is invalid.

Action: Verify that the source table information entered is correct.

82 Appendix B: Error Messages

Integration Service Error MessagesESSBASEWRT_203044 Failed to create the Error Log file.Cause: The Integration Service failed to create the error log file at session level. The

error log file is invalid.

-or-

Error log file is missing at session level.

Action: Verify the path and the file name mentioned in the Error Log Directory property.

ESSBASEWRT_203049 Unable to find the PWX_ESSBASE environment variable. Cause: The PWX_ESSBASE environment variable is not set to the <PowerExchange



ESSBASEWRT_203031 Unable to find the Rule File.Cause: The Integration Service was unable to find the rule file. The rule file name is

invalid.

Action: Verify that the rule file exists in the specified directory.

Integration Service Error Messages 83

84 Appendix B: Error Messages

A p p e n d i x C

Glossary

This appendix includes the following topic:

♦ Glossary of Terms, 86

85

Glossary of Terms

alias An alternate name for a dimension, member, or description.

application A structure containing one or more Essbase databases and related files that control system variables, such as memory allocation and auto load parameters.

ARBORPATH An environment variable that specifies the Essbase root directory.

attributeA classification of a member in a dimension. Use an attribute to select and group members associated with the attribute. You can also use an attribute to perform calculations and application-specific functions.

attribute associationA relationship in a database outline where a member in an attribute dimension describes a characteristic of a member in the attribute base dimension.

attribute dimensionA type of dimension that describes the attributes or qualities of a member and base dimension.

base dimensionA standard dimension that is associated with an attribute dimension. To classify a member of a base dimension, associate it with a member of an attribute dimension that describes the classification.

calculationThe process of aggregating data or running a calculation script.

calculation scriptA text file containing a set of instructions that defines the logic to calculate a database.

dimensionA data category used to organize business data for retrieving and consolidating. A dimension contains a hierarchy of related members grouped within the dimension.

86 Appendix C: Glossary

dimension build rulesSpecifications that Essbase uses to modify an outline. The outline is modified based on an external data source file.

Dynamic Calc MembersMembers that the Essbase server calculates only during retrieval time.

Dynamic Time SeriesA process used to perform dynamic period-to-date reporting.

Dynamic Time Series MembersPredefined members that are used to perform Dynamic Time Series reporting.

leaf memberA member that has no child nodes.

memberA unique component within a dimension.

Member Selection Report CommandA command that selects a range of members based on database outline relationships, such as sibling, generation, and level.

missing dataA (#MISSING) marker indicating that data in the labeled location does not exist, contains no meaningful value, or was not entered or loaded.

outlineThe database structure of a multi-dimensional database, including all dimensions, members, tags, types, consolidations, and mathematical relationships. Data is stored in the database according to the structure defined in the outline.

standard dimensionA dimension that is not an attribute dimension.

substitution variableA global placeholder for information changes regularly.

suppress rowsAn option to exclude rows that contain missing values.

Glossary of Terms 87

time series reportingA process of reporting data based on a calendar.

User Defined Attribute.An attribute used to describe the unique characteristic of a member.

88 Appendix C: Glossary

NOTICES

This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software Corporation (“DataDirect”) which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

I n d e x

Aapplication

adding 53delete 55

Ccalculation scripts

running 76configuring

PowerExchange for Hyperion Essbase 6session, Essbase source 74session, Essbase target 75session, relational model 75

creating an Essbase mappings 66creating a relational model 66normalizing an Essbase cube 66

Ddatabase

adding 56deleting 57

datatypesHyperion Essbase and transformation 80

dimensionadding 58

Iidentifying attribute dimensions 19, 20, 30, 33installing

PowerExchange for Hyperion Essbase 6, 8PowerExchange for Hyperion Essbase on Windows 8

Integration Service 4

Llibraries

setting library paths 11setting library paths on UNIX 12setting library paths on Windows 11

Mmember

updating 64

Ooutline

creating a member 62deleting a member 64modifying 58

vii

Pplug-ins

registering, Hyperion Essbase 10prerequisites

PowerExchange for Hyperion Essbase 6

Rrelational models

creating for Essbase 66report scripts

declaring command parameters 34

Ssession

configuring, Essbase source 74configuring, Essbase target 75configuring, relational model 75

source definitioncreating filter expressions 19creating Type 1, Type 2, and Type 3 27importing source definitions 37setting filter criteria, Type 3 source definitions 22troubleshooting 37

Ttarget definition

creating columns, Type 2 43target definitions

creating filter expressions 42troubleshooting 50

Uunderstanding

administering outlines 3Essbase source definitions 2Essbase target definitions 2

uninstallingPowerExchange for Hyperion Essbase 13uninstalling from UNIX 13uninstalling from Windows 13

upgradingPowerExchange for Hyperion Essbase pre-upgrade

tasks 6PowerExchange for Hyperion Essbase upgrade tasks 6

viii Index

Documents

PowerExchange for Hyperion Essbase 8.5 User Guide Documentation/1/PWX… · from the Essbase server and create a logical definition used to write data to the Essbase server. Use the