Pages

Monday 16 September 2013

OBIEE 10g/11g Hierarchy Drill Down or/and Drill Through or/and Drill Chaining


OBIEE 10g supports level based hierarchy, with OBIEE 11g enhancements it supports level based as well as value based hierarchies with some additional configurations. The natural drill down is supported and can be configured to support drill through also. 

What id drill chaining? Does OBIEE support drill chaining?  Drill Chaining is a ability of analyze to jump from a level of one dimension hierarchy (product level in product hierarchy) to a level in another dimension hierarchy (Region level in Market hierarchy). This blog is an attempt to demonstrate on how to configure drill chaining and how it works in OBIEE 10g.  I don’t see any specific reason why it can be done in OBIEE 11g.

Drill Chaining Scenario

A scenario where user would like to start with a simple report for product and revenue, then jump from product level in product hierarchy to Region Level in Market dimensional hierarchy , and then, drilling down the whole Market hierarchy to jump to Manager level in Employee dimension and finally drill down to customer.
The analysis steps are as follows..
Define a simple query Product and Revenue from Sales Subject area


The result show revenue broken down by product


Click on any product and see jump from Product level in product hierarchy, to “Region Level” in Market dimensional hierarchy…


Then, drilling down the whole Market hierarchy to jump to Manager level in Employee dimension




Then from employee hierarchy, jumping to Customer, then orders details


Repository Configuration 
For Detailed Level in Product hierarchy, choose the tab “Preferred Drill Path”, and set “Total level” for “Market hierarchy” as next drill.



Similarly, for Detailed level in Market Hierarchy, choose tab “Preferred Drill Path”, and set  “Total level” for “Employee hierarchy” as defined as next drill….



These simple configurations in repository can set the drill chaining and achieve the result discussed earlier.

No comments:

Post a Comment