OBIEE 11g for Hyperion Users - Are We There Yet?

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : [email protected] W: www.rittmanmead.com

Mark Rittman, Director, Rittman MeadOUG Hyperion Conference, June 2011

OBIEE 11g for Hyperion Users - Are We There Yet?

mailto:[email protected]


Agenda

•OBIEE 11g Overview•OBIEE 11g Features for Hyperion Users

‣Import Essbase Data into OBIEE Repository for Reporting‣Analyze Essbase + HFM Data in Answers‣Mapping Integration‣Extend and Integrate using Action Framework‣Strategic Analysis using Oracle Scorecard & Strategy Management

•So Can OBIEE 11g Replace Web Analysis, Planning, HFM, Excel Add-in?•Current Limitations and Issues

‣MDX Generation‣Repository Federation (Drill-through) Limitations‣Security & Deployment

•Future Developments•Conclusions



Mark Rittman

•Mark Rittman, Co-Founder of Rittman Mead•Oracle ACE Director, specialising in Oracle BI&DW•14 Years Experience with Oracle Technology•Regular columnist for Oracle Magazine•Author of forthcoming Oracle Press book on OBIEE 11g•Writer for Rittman Mead Blog :

http://www.rittmanmead.com/blog•Email : [email protected]•Twitter : @markrittman


http://www.rittmanmead.com/blog



About Rittman Mead

•Oracle BI and DW gold partner•World leading specialist partner for technical excellence, solutions delivery and

innovation in Oracle BI•Approximately 30 consultants worldwide•All expert in Oracle BI and DW•UK based•Offices in US, Europe (Belgium) and India•Skills in broad range of supporting Oracle tools:

‣OBIEE‣OBIA‣ODIEE‣Essbase, Oracle OLAP‣GoldenGate‣Exadata



Oracle Business Intelligence 11gR1

•The latest release of Oracle’s business intelligence platform•Replacement for Discoverer; full platform for analytics and dashboards•Now at version 11.1.1.5; originally derived from Siebel Analytics•11gR1 new features focused on OLAP analysis, visualizations, manageability



Web-Based Delivery of Analytics and Analysis

•Users access information and analytics through role-based dashboards•Can also publish reports to PDF, distribute, or access through MS Office



Web-Based Authoring Tools for “Power Users”

•Reports and analyses are created using web-based tools•Point-and-click creation of tables, pivot-tables, charts, maps, gauges



Integration with E-Business Suite and Other Applications

•OBIEE 11.1.1.5 is the platform for Oracle Business Intelligence applications•Pre-built reports, dashboards and analytics for EBS and other applications•Pre-built dimensional data warehouse and ETL routines•Extensible and open design



Mobile and Other Advanced Visualizations

•Mobile client for Apple iPad and iPhone•Delivery of reports and alerts via email, cell, pager etc•High-density visualizations via a thin-client web dashboard•Integration with MS Office and Open Office through SmartView



All Built Using Shared “Common Enterprise Information Model”

•All reporting tools can take their data from a shared metadata layer•Defined as dimensional model, embeds common calculations and drill paths•Subject-area and row-level security•Three-layer design to provide

abstraction from underlying complicated source systems

Simplification of the Data ModelIntegration of Disparate DataSources

Addition of Business Logic and Calculations



New in the 11g Release of Oracle Business Intelligence

•Scorecards and Key Performance Indicators•The “Action Framework”, for integration with workflows, E-Business Suite forms etc•Improve analysis capabilities•Improved manageability through Enterprise Manager•Scorecards, Mapping, new OLAP features



OBIEE 11g Features for Hyperion Users

•Essbase as a data source for Oracle BI Repository•Oracle Answers as a front-end for Essbase, HFM•Integration of Essbase and relational data into drill-through models•Oracle BI Repository as a data source for Essbase Studio•Plus access to OBIEE dashboards & reporting

‣Wide range of graphs and other visualizations‣Mapping and spatial integration‣Scorecards and KPIs‣Web Service and Application Integration‣Access to EBS, PSFT, Siebel and SAP data

through Oracle BI Applications



Supported Essbase/Hyperion Releases

•Oracle Essbase 9.3.3+, 11.1.1.3.500, 11.1.2+•HFM 9.3.3, 11.1.1.3, 11.1.2.x•Planning - tbc•See Oracle Fusion Middleware Supported System Configurations doc on OTN

‣http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html


http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html


Essbase Integration with OBIEE

•OBIEE can connect to multidimensional as well as relational sources‣Microsoft Analysis Services, SAP B/W, Essbase

•Import process converts the multidimensional view into a relational view•Essbase cubes, dimensions, hierarchies converted to a logical relational star schema•Essbase data can then be combined

with data from sources•OBIEE 11g introduces new OLAP query

capabilities making Answers a first-classad-hoc query tool for Essbase cubes

•Other use case is to bring in budget, forecast data etc from Essbase and use to enhance relational data



New Essbase Cube and Metadata Features in OBIEE 11gR1

•Essbase outlines are still imported in and converted to relational stars•However outlines are now handled better

‣Accounts dimensions keep their hierarchy‣Parent-child (value-based) hierarchies are supported‣Alias tables supported‣UDAs supported

•No longer any need to recreate as outlineevolves (additional generations, members)

•Makes OBIEE a more practical reportingenvironment for financial-style Essbase cubes



Importing an Essbase Cube Step 1 : Review Essbase Outline

•Review the Essbase outline using Essbase Administration Services•Be aware of the number and type of dimensions•Check usage of alias tables, UDAs etc•Be sure to use correct Essbase versions

‣Other releases will partially work, butdrilling etc may not work



Importing an Essbase Cube Step 2 : Select Metadata Import

•Using BI Administration tool, select File > Import Metadata•Enter connection details for Essbase Server (requires Essbase Client to be

installed on server and desktop)•Select cube for import, check Import UDAs if UDAs are present in cube



Importing an Essbase Cube Step 3 : Review Import

•Review imported cube metadata‣Accounts dimension is now a hierarchy‣Single measure dimensioned by all

dimensions‣Columns still based on outline

dimension generations



Importing an Essbase Cube Step 4 : Convert To Parent-Child

•Imported level-based hierarchies can be convered to value-based‣Protects against outline evolution, new levels (generations) being added

•Right-click on dimension, select Properties > Levels, then change Hierarchy Type to Value



Importing an Essbase Cube Step 5 : Add Alias Columns

•Where aliases are present in the outline, these can be brought through to OBIEE•Right-click on dimension, select Create Columns for Alias Table•Select alias to create column for; alias then appears in physical database



Importing an Essbase Cube Step 6 : Create Remainder of Model

•Once physical model is created, drag and drop over to business model and mapping layer, and then presentation layer

•Essbase data is then ready for reporting on using Answers



New Essbase Reporting Features in OBIEE 11g

•OBIEE 11g comes with a number of improvements for reporting against Essbase•Hierarchical column provide OLAP-style

drilling against Essbase cubes•Selection steps and hierarchical prompts

provided member-based selections•UDAs can be used in filters•Value-based hierarchies remove need

to query specific levels to selectmembers for analysis



Essbase and Hierarchical Columns

•Essbase cubes now use Hierarchical Columns by default•Full drill into detail (symmetric / asymmetric drilling)•Combine with regular attribute columns•Works across both

relational and OLAP sources‣MOLAP and ROLAP

analysis combined



P&L-Style Reports

•Though Financial Reporting is the most suitable tool for P&L-style reports, Answers using hierarchical columns can reproduce a lot of their functionality



Access to OBIEE Graphing, Visualisations

•Full access to all OBIEE visuals, maps, graphs, dashboard objects, scorecards etc



Selection Steps and Essbase

•The OBIEE 11g Selection Steps feature can be used to select membersbased on a hierarchy

•Select individual members, drill into hierarchy•Select members based on

position in a hierarchy‣Select Children Of‣Select Ancestors of‣Keep/Remove members



Conditional Selection Steps

•Selection steps can be added conditionally•Select condition type, action, measure, operator and value•Allows you to add/remove/keep members based on measure values



Review Selection Steps

•Selection Steps can be reviewed using the Results tab > Selection Steps

•Shows steps applied sequentially to the dataset

•Can be used in conjunction with regularcriteria column filters



Filtering against UDAs

•User-Defined Attributes can be accessed via filters‣UDAs are not displayable like columns, they instead act as filters

•Add filter based on UDA = 1 (true) or false (0)



Displaying Aliases

•Aliases appear in the subject area just like other columns‣Have to be imported into the RPD, see previous steps

•Can be used just as any other column



Handling Essbase Alternate Hierarchies

•Alternate hierarchies can be imported from Essbase ASO cubes (not BSO)•Dimension must be multiple hierarchy enabled in the outline•Multiple hierarchies are then imported into the RPD and created separately, based off of

the same logical dimension table

1

2

3



Handling Attribute Dimensions

•Attribute dimensions are imported into the RPD just like regular Essbase dimensions•Can be queried in analyses alongside regular dimension members/logical columns•Typically attribute dimensions are nested within the “parent” dimension

within the presentation layer of the RPD•Can be queried separate from the “parent” dimension, or alongside it

1

2

3



Essbase Security and Filters

•Data filters and Meta Filters are respected by OBIEE•SSO integration between Workspace and OBIEE Presentation Server removed in 11g•SSO still possible but requires external solution (until 11.1.1.6+?)

‣Shared Services and OBIEE both connecting to same external LDAP server‣External SSO over both OBIEE and EPM products



Importing and Analyzing Essbase Data using OBIEE 11.1.1.5

Demonstration



New Capabilities Provided by OBIEE 11g

•Horizontal (Drill-Across) and Vertical (Drill-down) Integration with Relational Data•MapViewer Integration•Scorecards and KPIs•BI Publisher•Action Framework•Integration with EBS and other application data



Drill-Across and Drill-Through To Relational Data

•One of the most powerful features in the OBIEE it is ability to combine data sources•Multiple data sources presented as a single logical dimensional model• In terms of Essbase and HFM integration there are three main use-cases:

1.Providing drill-down from an Essbase-based model to detail-level relational data2.Displaying relational attributes and descriptive data alongside Essbase measures3.Combining Essbase and relational measures into a single business model



Setting up Vertical Federation (Drill-to-Relational Detail)

•Initially map in Essbase source (using wizard), then introduce relational data into model•Be aware of Essbase unique naming requirements (may need to prefix relational name)•Create level-based logical dimension

to indicate hierarchy levels•Set content (hierarchy) level for Essbase

and Relational sources to indicate granularity (how detailed they are)

•BI Server will then automatically switchbetween Essbase and Relational sources,depending on how detailed the report gets



Reporting at Aggregated (Essbase) Level

•Reports that then run at the aggregated level will automatically use Essbase•This is because it is mapped in to the Customer dimension at a higher (non-leaf) level

With set [Channel3] as '[Channel].Generations(3).members' set [Customers5] as '[Customers].Generations(5).members'select { [Measures].[Amount] } on columns, NON EMPTY {crossjoin ({[Channel3]},{[Customers5]})} properties ANCESTOR_NAMES, GEN_NUMBER on rowsfrom [SH.SH]



Reporting at Detailed (Relational) Level

•Reports where the user drills to transaction level then switch the relational source•This happens because the relational source is the only one that can provide

customer data at the required level

select D1.c1 as c1, D1.c2 as c2, D1.c3 as c3, D1.c4 as c4, D1.c5 as c5, D1.c6 as c6, D1.c7 as c7from (select T1915.COUNTRY_NAME as c1, T1927.CUST_CITY as c2, T1927.CUST_EMAIL as c3, T1927.CUST_CREDIT_LIMIT as c4, concat(concat(T1927.CUST_FIRST_NAME, ' - '), T1927.CUST_LAST_NAME) as c5, T203.CHANNEL_CLASS as c6, sum(T1960.AMOUNT_SOLD) as c7, T1927.CUST_ID as c8 from COUNTRIES T1915,CUSTOMERS T1927, CHANNELS T203,SALES T1960 where ( T203.CHANNEL_ID = T1960.CHANNEL_ID and T1915.COUNTRY_ID = T1927.COUNTRY_ID and T1915.COUNTRY_NAME = 'Australia' and T1927.CUST_CITY = 'Darwin' and T1927.CUST_ID = T1960.CUST_ID ) group by T203.CHANNEL_CLASS, T1915.COUNTRY_NAME, T1927.CUST_CITY, T1927.CUST_CREDIT_LIMIT, T1927.CUST_EMAIL, T1927.CUST_ID, concat(concat(T1927.CUST_FIRST_NAME, ' - '), T1927.CUST_LAST_NAME) ) D1

order by c1, c2, c3, c4, c5, c6



Vertical Federation Limitations

•Only Essbase outlines that are balanced and level-based can be federated‣Unbalanced/ragged hierarchies do not consistently map to BMM columns‣Value-based (parent-child) hierarchies will not federate due to lack of “levels”

•Therefore Essbase cubes that “look like” relational cubes are the best to federate•Typically sales analysis, and cubes built to support OBIEE•There is no “refresh” facility to bring in changed outlines into OBIEE•Therefore only “stable” outlines are suitable for OBIEE•No issues over ASO, BSO etc•Versions of Essbase supported back to 7.x

‣Though you will need supported versions to be able to use hierarchical columns‣Essbase 9.3.3+, 11.1.1.3.500, 11.1.2+



Setting up Horizontal Federation (Relational alongside Essbase)

•You may have actuals data in a relational database, and forecast/budget data in Essbase

•It would be useful to report on these in a combined business model•Measures of the same dimensionality can go

in the same fact table•Measures of differing dimensionality go in

separate fact tables•Users see a single combined data source•Oracle BI Server combines the data at runtime

‣New in 11g - can use LOOKUP functionto retrieve relational descriptors etc



Displaying Essbase & Relational Data Together on Dashboards

•Relational and Essbase data can be displayed together in analyses, dashboards•Navigation can be set up between Essbase aggregated data and relational detail



Combining Essbase and Relational Data using OBIEE

Demonstration



Mapviewer Integration

•OBIEE 11g comes with Oracle MapViewer integrated and included in license cost•Display BI data using maps, layers, points of interest•Integration with NAVTEQ maps, Google Maps, Bing Maps•Perform spatial calculations using Oracle Locator (free) or Oracle Spatial Option



Key Performance Indicators

•KPIs can be defined based on actual and target measures•Can combine relational and Essbase data, plus external data from files, services ertc•Thresholds for good, bad etc performance can be set•KPIs can be dimensioned (time, customer, product etc)



KPI Watchlists

•Users can define watchlists, to monitor their KPIs•KPIs can be pinned, or user can analyze them by their allowed dimensions•Supports collaboration with KPI owner to record comments etc



KPI Scorecards

•Arrange KPIs into hierarchies, strategies etc•Define strategy trees, cause-and-effect relationships etc•Weighting of KPIs•Analyze by dimensions•Embed in dashboards



OBIEE Scorecards vs. Hyperion Performance Scorecards

•Many features in common between the products‣Kaplan & Norton views, perspectives, concepts; focus around balanced scorecards

•However OBIEE 11g Scorecards are not upgrade or like/like replacement‣Focus is more on leveraging the Oracle BI Repository + data sources‣Some HPS features not present in OBIEE Scorecards (HSS integration etc)‣OBIEE Scorecard also features integration with agents, actions and other BI elements



BI Publisher

•Used for “pixel-perfect” published reporting to PDF, email, screen etc•High-fidelity layout controls, bursting, distribution•Can access Essbase either through OBIEE semantic layer, or through Essbase MDX



Actionable Intelligence

•OBIEE concept around “closed-loop” analytics•Detect, action and then action your data•Agents provide alerts, automation•Actions provide links to external processes



Actions and Action Links

•Actions can be associated with columns through Action Links

•Drill to detail; navigate to report; invoke business process; initiate review

•Actions enable BI users to respond to insight discovered using dashboards, analyses



Using Actions for Essbase / EPM Suite Integration

•Actions can be used to enhance and extend OBIEE / Essbase Integration‣Launch HFM, FR etc passing BI credentials‣Writeback to Essbase database‣Run calc script, etc



MapViewer, Scorecards and Actionable Intelligence

Demonstration



So Can OBIEE Replace WebAnalysis, Planning, Financial Mgmt etc?

•OBIEE analyses, dashboards can replace all functional aspects of Web Analysis•FR is still preferable for non-trivial financial reports



... and What Issues Are Still Outstanding?

•A number of minor, and major, issues are still outstanding for Essbase / EPM users•Some are minor and will be addressed with bug fixes, enhancements

‣Restoration of SSO between EPM workspace and OBIEE dashboard‣Requirement for multiple WLS homes, EM environments‣Some early-release bugs around value-based hierarchies, drilling, formulas etc‣Post 11.1.1.5 Essbase-specific patch due soon to address many issues

•Some are just limitations of how things work‣Cannot federate value-based hierarchies‣Slower queries and analysis compared to Smartview + Essbase Add-in

•Some are fundamental and require re-engineering of OBIEE‣Complex and fragmented MDX when using hierarchical columns‣Excessively expensive MDX when using selection steps



The Hierarchical Columns and Pivoting Issue

•Hierarchical columns generate one logical query per grouping•For SQL queries, these are combined into a single SQL statement•For Essbase queries, each grouping generates it’s own MDX query, plus others

With set [_Products1] as '{Distinct({[Products]})}' set [_Products2] as 'Generate({[_Products1]},[Products].currentmember.children)'select { [Measures].[Gross Revenue] } on columns, NON EMPTY {{[_Products2]}} properties GEN_NUMBER, [Products].[Memnor], [Products].[Ancestor_Names], [Products].[MEMBER_UNIQUE_NAME], [Products].[LEVEL_NUMBER] on rows from [BISAMPLE.Sample]

With set [_Products1] as '{Distinct({[Products]})}' set [_Products2] as 'Generate({[_Products1]},[Products].currentmember.children)'select { [Measures].[Gross Revenue] } on columns, NON EMPTY {{[_Products2]}} properties GEN_NUMBER, [Products].[Memnor], [Products].[Ancestor_Names], [Products].[MEMBER_UNIQUE_NAME], [Products].[LEVEL_NUMBER] on rows from [BISAMPLE.Sample]

With set [_Axis1Set] as '{Distinct({[Products]})}'select {} on columns, {[_Axis1Set]} properties GEN_NUMBER, [Products].[Memnor], [Products].[MEMBER_UNIQUE_NAME] on rows from [BISAMPLE.Sample]

With set [_Axis1Set] as '{Distinct({[Products]})}'select {} on columns, {[_Axis1Set]} properties GEN_NUMBER, [Products].[Memnor], [Products].[MEMBER_UNIQUE_NAME] on rows from [BISAMPLE.Sample]

With set [_Axis1Set] as '{[Products].Generations(1).members}'select {} on columns, {[_Axis1Set]} properties GEN_NUMBER, [Products].[Memnor], [Products].[MEMBER_UNIQUE_NAME] on rows from [BISAMPLE.Sample]

With set [_Axis1Set] as '{[Products].Generations(1).members}'select {} on columns, {[_Axis1Set]} properties GEN_NUMBER, [Products].[Memnor], [Products].[MEMBER_UNIQUE_NAME] on rows from [BISAMPLE.Sample]

With set [_Axis1Set] as '{Distinct({[10002]})}'select {} on columns, {[_Axis1Set]} properties GEN_NUMBER, [Products].[Memnor], [Products].[Ancestor_Names], [Products].[MEMBER_UNIQUE_NAME] on rows from [BISAMPLE.Sample]

With set [_Axis1Set] as '{Distinct({[10002]})}'select {} on columns, {[_Axis1Set]} properties GEN_NUMBER, [Products].[Memnor], [Products].[Ancestor_Names], [Products].[MEMBER_UNIQUE_NAME] on rows from [BISAMPLE.Sample]

With set [_Products2] as '{Distinct({[10002]})}' set [_Products3] as 'Generate({[_Products2]},[Products].currentmember.children)'select { [Measures].[Gross Revenue] } on columns, NON EMPTY {{[_Products3]}} properties GEN_NUMBER, [Products].[Memnor], [Products].[Ancestor_Names], [Products].[MEMBER_UNIQUE_NAME], [Products].[LEVEL_NUMBER] on rows from [BISAMPLE.Sample]

With set [_Products2] as '{Distinct({[10002]})}' set [_Products3] as 'Generate({[_Products2]},[Products].currentmember.children)'select { [Measures].[Gross Revenue] } on columns, NON EMPTY {{[_Products3]}} properties GEN_NUMBER, [Products].[Memnor], [Products].[Ancestor_Names], [Products].[MEMBER_UNIQUE_NAME], [Products].[LEVEL_NUMBER] on rows from [BISAMPLE.Sample]

1

2

3

4

5



Issue Compounded by > Hierarchical Column

•Issue becomes worse when >1 hierarchical column & pivoting is included in analysis & •Many more sub-groupings are created leading to excessivly expensive SQL•Workaround #1 : Size your system to expect greater numbers of small MDX queries•Workaround #2 : Try to limit analyses to a single hierarchical column on row-edge•Workaround #3 : Enable caching - 11g subquery caching can significantly improve perf.

=58 separate MDX queries



The Selection Steps Issue

•Selection steps (member steps) are used extensively in 11g for Essbase data•Provides an Essbase-like environment for filtering, selecting and calculating data

1

2

3



Selection Steps Multiply the Number of Physical MDX Generated

•Issue is that selection steps will multiple the number of physical MDXs sent to Essbase‣Issues also affects relational sources, but SQLs are usually combined into one

•# logical SQLs = (# steps in Dim1 x # steps Dim 2 x # steps Dimn) + Grand Total SQL•# MDX queries = 1 or 2 per logical SQL•Coupled with hierarchical columns & pivoting, can cause excessive MDX query load

With set [_Market2] as '{Distinct({[East], [West]})}' set [_Year2] as '{Distinct({[Qtr1], [Qtr2]})}'select { [Measures].[Sales] } on columns, NON EMPTY {crossjoin({[_Market2]},{[_Year2]})} properties GEN_NUMBER, [Market].[LEVEL_NUMBER], [Year].[MEMBER_UNIQUE_NAME], [Year].[Memnor], [Market].[MEMBER_UNIQUE_NAME], [Market].[Memnor], [Year].[LEVEL_NUMBER] on rows from [Sample.Basic]

With set [_Market2] as '{Distinct({[East], [West]})}' set [_Year2] as '{Distinct({[Qtr1], [Qtr2]})}'select { [Measures].[Sales] } on columns, NON EMPTY {crossjoin({[_Market2]},{[_Year2]})} properties GEN_NUMBER, [Market].[LEVEL_NUMBER], [Year].[MEMBER_UNIQUE_NAME], [Year].[Memnor], [Market].[MEMBER_UNIQUE_NAME], [Market].[Memnor], [Year].[LEVEL_NUMBER] on rows from [Sample.Basic]

With set [_Market2] as '[Market].Generations(2).members' set [_Year2] as '{Distinct({[Qtr1], [Qtr2]})}'select { [Measures].[Sales] } on columns, NON EMPTY {crossjoin({[_Market2]},{[_Year2]})} properties GEN_NUMBER, [Year].[MEMBER_UNIQUE_NAME], [Year].[Memnor], [Market].[MEMBER_UNIQUE_NAME], [Year].[LEVEL_NUMBER] on rows from [Sample.Basic]




With set [_Market2] as '[Market].Generations(2).members' set [_Year2] as '[Year].Generations(2).members'select { [Measures].[Sales] } on columns, NON EMPTY {crossjoin({[_Market2]},{[_Year2]})} properties GEN_NUMBER, [Year].[MEMBER_UNIQUE_NAME], [Market].[MEMBER_UNIQUE_NAME] on rows from [Sample.Basic]

With set [_Market2] as '[Market].Generations(2).members' set [_Year2] as '[Year].Generations(2).members'select { [Measures].[Sales] } on columns, NON EMPTY {crossjoin({[_Market2]},{[_Year2]})} properties GEN_NUMBER, [Year].[MEMBER_UNIQUE_NAME], [Market].[MEMBER_UNIQUE_NAME] on rows from [Sample.Basic]



Hierarchical Columns, Pivoting and Selection Steps Issues

Demonstration



The Value-Based Hierarchy Issue (or “Gotcha”)

•Value-based (Parent-Child) hierarchy support are a useful addition in OBIEE 11g•Removes need to re-import Essbase database if new generations added to dimension

‣All members are in the same logical column; no need to create new ones for new Essbase generation

•Allows member searches to work against single logical column•More “natural” way of holding member data for Essbase users



Value-Based Hierarchies and Vertical Federation

•Given the benefits of value-based hierarchies for changing outlines, customersoften enable them for all dimensions in OBIEE 11g ...

•... and then want to set up drill-to-detail analyses using vertical federation•... which require defined levels to join logical table sources together•... which value-based hierarchies do not have•Workaround : Analyze Essbase and Relational separately, link by actions that

pass hierarchical column selection values through hidden attribute columns



New Ways of Doing Things

•Most Essbase users access data through the Excel Add-in•Uses Query-by-Example approach to retrieve data•Combined with Excel flexibility, gives lots of options to access data•To produce similar reports, different approaches are required with OBIEE

‣Use of FILTER and time-series functions‣Adaptation for structured cross-tab style interface vs. free-form Excel



Combining OBIEE Functions and Essbase Data

•Time-offsets can be generated using OBIEE Time-Series functions‣AGO, TODATE, PERIODROLLING

•Intersections of dimension members (Accounts, Scenarios) using FILTER function•Combine OBIEE analytic functions with Essbase member references•Requires learning OBIEE function syntax and combining with Essbase skills



OBIEE Analytic Function Examples

•FILTER(measure USING expr)‣Allows you to filter generic

measure by dimension member,i.e. measure by Profit account,and Budget scenario

•AGO, TODATE, PERIODROLLING‣Generate year-to-date,

period ago, rolling total‣Pushes down to equivalent MDX

•EVALUATE, EVALUTE_AGGR‣Leverage native MDX functions



Excel Add-in/SmartView and OBIEE are Complementary Tools

•OBIEE does not remove need for Excel add-in or SmartView•Common mistake is to think it’s “all-or-nothing”•Still a role for Excel add-in for finance/analyst use•OBIEE is great for mass-distribution of financial data, combining it with other data•Accessing Essbase data requires combined Essbase / OBIEE skills



Analytics and Dimension/Measure Access using OBIEE

Demonstration



Summary

•OBIEE 11g introduces a number of new features Essbase customers were waiting for‣Proper OLAP analysis with hierarchical member selection‣Support for value-based hierarchies, so that outline changes don’t need re-import‣Support for multiple aliases, UDAs, multiple hierarchies, filters etc

•OBIEE also provides many additional features that will benefit Essbase customers‣Mapping, scorecards, better visualizations‣Action Framework, integration with Fusion Middleware

•But the 11g release also brings its own new issues‣Excessive number of MDX statements for pivoting OLAP-style queries‣Selection steps can exacerbate this issue by exponentially adding more MDX queries‣Value-based hierarchies have their own “gotchas”

•Don’t try to 100%-replace Excel Add-in With OBIEE‣Tools are complementary, have their own strengths‣Be prepared to learn OBIEE dev techniques as well as Essbase ones



More Information

•Thank you for attending this presentation•More information can be found at http://www.rittmanmead.com•Contact us at [email protected] or [email protected]•Look out for our book, “Oracle Business Intelligence Developers Guide” due Q1 2012•Follow-us on Twitter (@rittmanmead) or Facebook (facebook.com/rittmanmead)


http://www.rittmanmead.com/




Mark Rittman, Director, Rittman MeadOUG Hyperion Conference, June 2011

OBIEE 11g for Hyperion Users - Are We There Yet?

OBIEE 11g for Hyperion Users - Are We There Yet?

Technology

Transcript of OBIEE 11g for Hyperion Users - Are We There Yet?