Before we update the outline, we need to set the Dimension Build Properties, meaning we need to define the attributes of each column.. Since our market data source is to be a generation
Trang 1• Create Using Join: This function is used to join two or more fields to
create a new field
In this example, we have joined the field containing the value of United
States of America and the field containing the value USA, into a new
field which looks like: United States of AmericaUSA, as shown in the
following screenshot:
• Create Using Text: Creates a new field based on the text you have entered
This is particularly helpful when you need to make Essbase-friendly data
that is repeatedly sent from the same source
As shown in the following example, a field is added between Field 6 and
Field 7 called US:
Trang 2[ 101 ]
Step 8: Associate fields with dimensions
Now that our source data file transformation is complete, we are ready to proceed
with the outline update Before we update the outline, we need to set the Dimension
Build Properties, meaning we need to define the attributes of each column In other
words, how Essbase will interpret the data in each column
Since our market data source is to be a generation build method, let us define
each column and how the outline must be updated according to the data
Open the Dimension Build Properties in EAS, with the Data Prep Editor open:
1 Click on Fields and then click on the Field Properties
2 Since this is Dimension build rule file, go to the tab Dimension
Build Properties
The following screenshot shows the Dimension build settings:
In the Dimension Build Properties screen, you need to define the dimension
name, and the corresponding field that the data will load to Some of the
available options are Generation, Alias, Property, Level, Parent, and Child.
This material is copyright and is licensed for the sole use by Paul Corcorran on 5th July 2009
8601 ave p #1, , lubbock, , 79423
Download at Boykma.Com
Trang 3You can also ignore a field by selecting the option Ignore field during dimension
build There may be times when an entire column or field is not needed for you
to load the data into Essbase For example, the file you are loading has a column
for cities in it Your database outline is only set up for countries and states Cities
are not needed so there is no need to even look at them
In our example, the Field 1 input data field is the Generation 2 member name
(Generations always start from Generation 2 as the Generation 1 level is the
dimension name itself) and the next field will be the member alias
Click on Field 1, then assign the Field Definition | Dimension as TOTAL MARKET,
in the Field | Type select Generation and in the Field | Number enter 2 and click OK The input data Field 1 is now set to load to Generation 2/Member Name If you were
finished, you could click OK now, with more fields to define, you can simply click on
Next Did you see how the cursor has automatically moved to Field 2 Select TOTAL MARKET as the dimension name and click on Alias field type When you select Alias
the Field | Number is set to Generation 2 as shown:
Trang 4[ 103 ]
Repeat the above steps by clicking on Next and choosing the Dimension name and
Field | Type until you reach the end of the file The Generation number will be
incremented by one for each new field in the data that you define as a new member Finally, all of the fields in the input data file are defined in the Essbase rules file
The rules file should look like this:
Step 9: Validate the Dimension Build rules file
Now that all of the input data fields are assigned to the appropriate outline members,
we need to validate the rules file against the database outline With the rules file
open, click on the validate button (the quick select button says Validate when you
hover over it) The validate function validates if the rules file is properly defined for
the specific database outline If the validate is successful, you will receive a validate
successful message If the rules file is not properly defined to the database outline, you will receive a message stating the validation was unsuccessful One common example
of a rules file validation failing is if you have two fields defined as building members in the same dimension When you set the dimension build to use the generation method, you must be careful that you define the fields correctly The field that is going to build
Generation 2 members must be the only field set upto do so
Upon successful rules file validation, click on File | Save and give the rule file
a name (preferably something meaningful but remember, upto 8 characters in
the name) The rules file can be saved on either the Essbase server or as a local file
Where you save it depends on your specific architecture
This material is copyright and is licensed for the sole use by Paul Corcorran on 5th July 2009
8601 ave p #1, , lubbock, , 79423
Download at Boykma.Com
Trang 5Update your outline using a rules file
Now that you have completed your first rule file, you need to update the outline
using this rules file
There are several ways you can update an outline using a data rules file and
a data file:
• Updating the outline from the EAS Outline Editor
• Executing MaxL commands
• Making your own API calls
• Running Essbase command scripts
We will discuss the first and second points now, and the third and fourth points
will be discussed with examples provided, in the next chapter
Update your outline using the EAS Outline
Editor
One of the easiest ways the outline can be updated is manually by using
the EAS Outline Editor
The steps to update the outline are:
1 In the EAS, open the Application | Database for which the outline
needs to be updated
2 Double-click on the Outline, the outline editor is opened for editing.
3 Or, you can click on the Outline in the Menu option and then click on
the Update outline The following screen will then be displayed: