ESSBASE INCREMENTAL IMPORT INTO

OBIEE RPD
BELOW ARE THE DETAILED STEPS ON HOW TO INCREMENTALLY IMPORT ESSBASE HIERARCHY
LEVELS INTO OBIEE AFTER THE INITIAL FULL IMPORT.

HIGH LEVEL STEPS:

-

Imported hierarchy to overwrite in the physical layer. Then delete unnecessary

objects.
Drag/drop new 4 physical columns in the BMM logical table
Manually add child level in hierarchy, add 4 columns to this lowest level and set
keys manually.
Manually add this new key to logical table as well
Set content tab both in DIM and FACT LTS
Drag/drop new key column in the presentation layer
Set the display column name in both the hierarchy in BMM and also in the
presentation layer.

DETAILED STEPS:
STEP 1: IMPORTING HIERARCHY IN THE PHYSICAL LAYER
-

Identify which Cube in Essbase needs to be imported. Then open the rpd either online or
offline and browse to 168.146.26.195 -> GDMEE -> GL ->Entity->Total Entity. This is where
we are going to add the new levels.
Right click on its connection pool, then select import metadata. You will be presented with
a screen showing objects in the Essbase. Navigate to the Cube GDMEE and then import.
This will overwrite the existing Cube in the physical layer with the new one, resulting in
bringing over the new levels into OBIEE.
After this step, we are done working in the physical layer. Save the rpd at this checkpoint ,
and duplicate a copy and work in that one to implement changes in the BMM layer.

The screen below shows the import process where Essbase objects are in the left pane
(Data Source view) and OBIEE objects are in the right pane(Repository View)

After the import, your new hierarchy should show the new levels in the physical layer as
shown below.

STEP 2: MOVING NEW LEVELS AND COLUMNS TO THE BMM LAYER

-

The import we performed in the physical layer brings in unnecessary objects in the BMM
layer which have to be manually deleted in The BMM layer. No need to delete those new
unnecessary objects in the physical layer.
Now we are ready to drag and drop the new 3 physical columns from the physical

layer into the BMM corresponding logical table, which is TotalEntity which has an
LTS called GL. Drag/Drop the 3 columns from the physical layer to GL LTS as
shown below.

Now Double click on TotalEntity logical table , select Key tab, and add the 3 new
keys to it by selecting them with checkboxes as shown below (using the pencil icon
for edit)

Next step is to add 3 new child levels to the TotalEntity Hierarchy object as shown
below.

Set up the levels for these new columns to the appropriate child level you just created.

Browse to the child level of the hierarchy, Double click on Gen13,TotalEntity level, and set
the keys as shown below

In the screen below, notice that you will have to manually type the Key Name, and then
select columns using dropdown.

Next step is to set the content level for both the dimension logical table TotalEntityand
the fact logical table GL to the new lowest TotalEntity level as shown below.
DIMENSION TABLES LTS NAME IS GL

FACT TABLES LTS NAME IS GL

STEP 3: BRINGING NEW COLUMNS IN THE PRESENTATION LAYER

- Next we drag and drop only the 3 key columns to the corresponding table in the
presentation layer, which is under GL Cube subject area, and under TotalEntity
Presentation Table as shown below.

Now finally, we set the display columns to the 3 key columns we brought over from
the BMM layer as shown below.

Perform the consistency check on the rpd, and save it. Deploy it to the DEV server and
restart.

This concludes our incremental import of Essbase hierarchy levels. You should now be able
to see the new levels and corresponding data in OBIEE reports and dashboards.