Oracle Essbase 9 Implementation Guide- P22 potx

In the example above, we discussed updating the outline from the input data source file.. Delimiter: Data delimiters are used to separate individual fields in the data source.. The types

In our example, we choose a Microsoft Excel file as our data source

1 Click on the Open data file option

2 Select the file system and browse to the file (for example: c:\data\market

.xls) and the data in the excel file is as shown in the following screenshot:

3 Select the above excel file and click on OK You will see the Data Prep

Editor as shown in the following screenshot:

In this screenshot, the upper screen frame shows the data source file in its original

form The lower screen frame shows how Essbase will interpret the data before

it gets loaded into your Essbase database

In the example above, we discussed updating the outline from the input data

source file In the next chapter, we will talk about how to import data using

the second method which is directly loaded from the RDBMS SQL Data Source

Step 4: Set the Data Source Properties

While plenty of your data will be entered manually from user interaction, a good

deal of it will likely come from external systems Before Essbase can process any

data file, we need to define the data to Essbase in the rules file

Is the data in a comma separated file or tab delimited file? For some feeds, we need

to ignore the header records which are usually the first row in the input file These

settings can be set in the Data Source Properties.

Delimiter: Data delimiters are used to separate individual fields in the data source

The types of delimiters available in Essbase are given as follows:

• Comma: This is for a comma separated data source file.

• Tab: This is for a tab delimited data source file.

• All spaces: The fields will be delimited by empty white spaces.

• Custom: The common delimiter which is agreed with the source systems

For example, colon (:) or any other single character

• Column width: The data columns have specific widths For example,

the rules file will separate the data into columns based on all columns

being ten characters in width

To open an input data source file in EAS, with the Data Prep Editor open:

1 Click on Options, and then click on the Data Source Properties.

2 The first tab is the Delimiter tab as shown in the following screenshot:

3 Select or create the appropriate data delimiter The appropriate delimiter

is the character or set of characters that are used to separate the columns of

your data Essbase offers you a few of the most common delimiters and gives you the option of setting your own delimiters based on what is being used in your data file

Step 5: Set the View to Dimension build fields

In this step, we need to define if this rule is used for Dimension build fields view

or Data load fields view By default, Data load field view is selected

• Dimension build field: You will select this option when you are using the

rules file with your data file to add new members to the outline or to update existing members in the outline

• Data load field: This option is for loading data with a data load rules file

and will be discussed in more detail later

To set the Dimension build fields view in EAS, with the Data Prep Editor open:

• Click on View and then select the checkbox Dimension build fields as

we are currently doing a dimension build We will talk in-depth about

the Data load fields view in the next chapter.

Step 6: Select Dimension build method

Build dimensions methods are basically used for adding, removing, or updating

a member, an alias, or a property of an Essbase outline member These are defined

in the build rule files

There are three ways you can build an Essbase outline:

• Generation reference

• Level reference

• Parent-child reference

Let us talk about how each method can be used to update the Essbase outline

Generation reference

With the generation reference set, the data source should be arranged or organized

from top to bottom as it pertains to the database outline structure We consider the

dimension name itself as Generation 1 Each record in the rules file contains the

parent name as Generation 1, the child names are Generation 2, children of the

child name are Generation 3, children of that child name are Generation 4, and

Level reference

With the level reference set, the data source should be arranged or organized from the leaf node or bottom level to the top level or the dimension name We consider the leaf node to be Level 0, the next record is called Level 1, the next record is Level 2, and

so on, until we reach the top dimension level For example: Month | Quarter | Year.

Parent-child reference

In the parent-child reference, the parent is followed by the child Each record will

have a parent and then its child For example, the YEAR member is the parent and

the QUARTER member is the child The QUARTER level is also a parent since its

child members are the months

For this example, we have used the generation reference

GEOGRAPHIC

NorthAmerica

NorthAmerica

NorthAmerica

NorthAmerica

NorthAmerica

NorthAmerica

NorthAmerica

NorthAmerica

NA

NA NA

NA NA

NA NA

NA

Central

Central Central

Central Central

Central Central

Central

Chicago Chicago Chicago Chicago

Detroit Detroit Detroit Detroit

Motor City EssCar Motown EssCar Phord City EssCar East Side EssCar Midwest EssCar Soldier Field EssCar Capone EssCar

St Valentines EssCar

12045 12046 12047 12084 17801 17802 17803 17804

DTW

DTW DTW DTW

ORD ORD ORD ORD

As shown in the figure above, we can see two things:

• First, we see that the first record in the data file is a header record, which

usually describes something about the data file itself such as the column

names This can be skipped by setting 1 in the Number of lines to skip in

the Header section of the Data Source Properties as shown in the screenshot Then click on OK.