Loading Data to Essbase 11.1.2 Outlines Containing Duplicate Member Names

<Do not delete this text because it is a placeholder for the generated list of "main" topics when run in a browser>

Purpose

This tutorial shows you how to load data to an Essbase outline in which duplicate member names are enabled.

After enabling an Essbase outline to accept duplicate member names, there are two methods you can use for loading data using a data file and data load rule: loading data using qualified member names and loading data using ancestor references, both described here.

Scenario

The Bigcorp corporation, manufacturer of hard disk drives, has built an Essbase database outline for historical sales analysis. The Essbase database Sales has been designed to accept duplicate member names in the Customer dimension, since several individual customers are members of both the Original Equipment Manufacturer (OEM) and Retail channels within the dimension.

Data can be loaded by utilizing a data file containing qualified member names or ancestor references and a matching data load rule. Either method provides Essbase with a unique identifier for each duplicate member name and enables the data load to complete.

Software and Hardware Requirements

The following is a list of software requirements:

Oracle® Essbase 11.1.2

Prerequisites

Before starting this tutorial, you should have access to an Essbase database that contains duplicate member names and a data file for loading.

Loading Data by Qualified Member Name

To load data using a data file that contains qualified member names for the duplicate members, create a data load rule.

.	Open Data Prep Editor for a new rule.
.	Open the data file containing the qualified member names, in this example, QualName.txt.
.	The data file is displayed in Data Prep Editor.
.	In Data Source Properties, select the Header tab, then change Number of lines to skip to 1, and then click OK. The data load will ignore the header record, as intended.
.	In the menu, select View, and then Raw data to toggle off the raw data view.
.	In the menu, select to view Data load fields, then click the header of the column containing the qualified member names, in this example, Field3.
.	In the menu, select Field properties.
.	Select the Data Load Properties tab, and then Data load method Default.
.	In the Field definition, set the Field name to Customer, and then click OK.
.	The field definition indicates that data will be loaded to the unique customer name provided by the qualified member name in the "Customer" column.
.	Complete the definitions for the remaining fields.
.	Verify and save the data load rule as QualName.rul.
.	Load data to the Bigcorp Sales database.
.	For the data load, select data file QualName.txt and data load rule QualName.rul, then click OK.
.	Data is loaded based on the qualified member names in the data file.

Loading Data by Ancestor Reference

To load data using a data file that contains ancestor references for the duplicate member names, create a data load rule, as you did in the previous topic.

.	Open Data Prep Editor for a new rule.
.	Open the data file containing the qualified member names, in this example, Reference.txt.
.	The data file is displayed in Data Prep Editor.
.	In Data Source Properties, select the Header tab, then change Number of lines to skip to 1, and then click OK. The data load will ignore the header record, as intended.
.	In the menu, select View, and then Raw data to toggle off the raw data view
.	In the menu, select to view Data load fields, then click the header of the column containing the ancestor reference, in this example, Field3.
.	In the menu, select Field properties.
.	Select the Data Load Properties tab, and then Data load method Use Reference method.
.	Expand Type.
.	Double-click Generation to populate Type.
.	In Reference number, enter 3, the generation number for the ancestor (Channel) that sufficiently qualifies the customer name to guarantee uniqueness.
.	In Reference dimension, click Click here to edit.
.	Expand Dimension.
.	Double-click Customer to populate Reference dimension.
.	Click Next.
.	Repeat steps 8 through 14 for Field 4, which is Generation 4 of Customer.
.	Click OK. Together, fields 3 and 4 produce a qualified member name that is unique.
.	Complete the definitions for the remaining fields.
.	Verify and save the data load rule as Referenc.rul.
.	Load data to the Bigcorp Sales database.
.	For the data load, select data file Reference.txt and data load rule Referenc.rul, then click OK.
.	Data is loaded based on the ancestor references in the data file.

Summary

In this tutorial, you learned how to load data to an Essbase outline containing duplicate member names using a data load rule and a data file. The tutorial demonstrated two different methods for constructing the load rule based on the structure of the data file used for the load.

Resources

To learn more about duplicate member names in Essbase, refer to the Oracle Essbase Release 11.1.2 Database Administrator's Guide.

	About Oracle \|Oracle and Sun \| \| Careers \| Contact Us \| Site Maps \| Legal Notices \| Terms of Use \| Your Privacy Rights