OBIEE SmartView Part 2 – Connecting to Essbase?

Why would you use OBIEE SmartView Connection and Connect to Essbase?

Before we continue, you need to know how to use SmartView connecting to OBIEE, which was part 1 and can be found here:

So why would you use OBIEE SmartView instead of SmartView Provider Services when connecting to Essbase? For 3 simple reasons:

  1. Easy creation of Tables instead of Pivot Tables. This could be used for data export, or filtering dimensions that you don’t want to be displayed.
  2. Creating simple charts without too much Excel skills.
  3. Sharing your report through OBIEE Catalog.

I’m sure you will think of other reasons, but let’s just start with those common ones for now. You might also want to read OBIEE Integration with Essbase before you continue reading:

Continue reading “OBIEE SmartView Part 2 – Connecting to Essbase?”


ODI 12c Petition – ODI KMs for Essbase, Hyperion Planning and Hyperion Financial Management in ODI 12c

Since ODI 12c doesn’t officially support Essbase, Planning and HFM, it becomes extremely hard to perform complex ETL with multi-source data with just FDMEE option, especially if you have OBIFS. Go here and sign this petition! Tell Oracle you want it!

Tell Oracle you want them to stay committed to the Hyperion Knowledge Modules for Oracle Data Integrator.

The integration tool of choice for Hyperion has a history of poor commitment levels due do rebranding agreements.  Older users of Hyperion will remember Hyperion Application Link (HAL) which was a rebranded product from Vignette.  Then there was Data Information Management (DIM) which was Informatica rebranded.  Both have gone out of fashion and customers were left with solutions that are no longer supported.  We hope this does not happen with ODI.

When Oracle purchased Sunopsis and renamed the product to Oracle Data Integrator it positioned ODI as “a best-of-breed data integration platform focused on fast bulk data movement and handling complex data transformations.”  Unlike the previous rebranding agreements ODI is a product Oracle actually owns and has greater ability to develop and integrate with Hyperion.  The 11g version of ODI listed top new features including “Adapters for Hyperion Planning, Financial Management, and Essbase.”  What is new for 12c?  Is it the removal of Adapters for Hyperion Planning and Financial Management?  We hope not because many customers will be negatively affected by that decision.

Sign this petition and let Oracle know your interest in the Oracle Data Integrator Knowledge Modules for Hyperion.  Oracle has publicly stated they will support the Hyperion Essbase Knowledge modules for ODI, however no such acknowledgement has been made for the Hyperion Planning and Hyperion Financial Management Knowledge modules.  Rumor has it they are considering stopping support for these KMs.

An Essbase OBIEE integration walk through with tips and tricks – Finale

Continuing from the last post – viewed here

Summarizing the tips

  1. Essbase EAS – Give the hierarchies generation name
  2. Essbase  EAS or SubVar Manager – Use Essbase for Substitution Variable
  3. OBIEE RPD – Renaming Measure to Fact and Never Flatten Anything
  4. OBIEE RPD – Double Check Your Dimension & Hierarchy Types
  5. OBIEE RPD – Have a Time dimension. This is usually tagged once imported.
  6. OBIEE RPD – Have your Account or Measure dimension tagged as Measure Dimension and Value as Hierarchy Type.
  7. OBIEE RPD – Uncheck Nullable
  8. OBIEE RPD – Importing Essbase Substitution Variables
  9. OBIEE RPD – Making use of Alias Tables & Uncheck Cacheable

Since the Essbase and RPD is now done. Let’s take a look at Answers and see why these points are considered as best practices.

Continue reading “An Essbase OBIEE integration walk through with tips and tricks – Finale”

An Essbase OBIEE integration walk through with tips and tricks

Best Practices or Tips & Tricks?

It’s probably best practices for myself but tips and tricks for you.

During the past few months, I have been going through theories and logics of KPIs, Dashboards and Strategy management. There are still a lot to go through but I’ve decided to go technical again for those who are missing out on Essbase & OBIEE. I’ve been doing Essbase and OBIEE integration since 2009, accumulated more than 30 Essbase OBIEE projects and there are lots of improvements on the tools since then. Unfortunately, Hyperion experts usually don’t like OBIEE and vice versa. I know that feeling since I came from the Hyperion side and always was an Essbase fan, that was back in 2004. The integration is actually not as difficult as it seems nowadays. You just need some tips and tricks for Essbase OBIEE integration.

Continue reading “An Essbase OBIEE integration walk through with tips and tricks”

Essbase ASO Outline Grows Too Big – Solution to Fragmentation Using Compact

Compacting ASO Outline – Defragmenting

Why does it grow?

In BSO, defragmenting the cube is actually quite simple. One way is to do a full restructure and the other way is to export, clear all blocks then re-import the data. So you think ASO doesn’t need to defrag since it doesn’t contain any blocks? Too bad, you’re very wrong. ASO fragmentation happens when you add/delete/regroup members or delete/add dimensions. So to make it simple, any meta-data changes will cause fragmentation. In fact, even if you use EPMA or work direct from EAS or Essbase Studio and EVEN OBIEE AGGREGATE PERSISTENCE WIZARD, it will still cause fragmentation.

So how much would it grow?

To be honest, I do not have the algorithms on this. But if you update the cube on a daily basis, I should think it will double the size in a few months time.

What happens if I don’t do anything?

If you don’t do anything to it, and when .otl file grows to over 2gb in size, EAS won’t be able to open the outline. Would users still be able to access it? Yes they would. It’ll still work but it doesn’t really feel safe does it?

What are the solutions?

There are 3 ways to compact the outline which in the end is basically defragmenting the outline, each with pros and cons. They are explained as follows:

Continue reading “Essbase ASO Outline Grows Too Big – Solution to Fragmentation Using Compact”

OBIEE and Essbase in BI Survey

There as a recent post saying that OBIEE is poorly ranked for Enterprise Reporting. Yes, it probably might not be the best. However, if BI Foundation Suite is purchased, then it really depends on the vendor if they implement correctly. Dashboard is a dashboard which is good for interactive reporting, data analysis, drilling. It isn’t the best idea for enterprise reporting though.

Let’s take a look at BI Survey and what they have for BIFS.

Continue reading “OBIEE and Essbase in BI Survey”

Creating Text Entry in Essbase – SmartList

Essbase Text Entry – SmartList

You might all have known that Essbase does not store text. Yes, in a sense it doesn’t but it stores SmartList. In a way, smartlist are numbers that are tied with text. Payment terms maybe a good example to demonstrate this.

First, in your BSO / ASO outline, open up the Properties tab like below and ensure Typed Measures enabled is true (which is not by default). Then you will have a Text List Manager tab.


Continue reading “Creating Text Entry in Essbase – SmartList”