Successfully reported this slideshow.

Integrating Oracle Essbase and Oracle Business Intelligence: Case Study


Published on

Most customers using Oracle Hyperion Public Sector Planning and Budgeting have important data locked up in Oracle Essbase cubes. More often than not, using the Excel plug-in, key users extract data and make manual adjustments before sending the information to key executives on a weekly or monthly basis. The problem with this approach is that the information is dependent on these key individuals with knowledge of Oracle Essbase and the point of view of the data in the cubes.

This session presents a client case study that takes the data out of Oracle Essbase and external sources into Oracle Business Intelligence dashboards so that appropriate users can have data from Oracle Essbase in an easy-to-understand format without understanding the complexities of Oracle Essbase.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Integrating Oracle Essbase and Oracle Business Intelligence: Case Study

  1. 1. Integrating Oracle Essbase and Oracle Business Intelligence: Case Studies Prashanth Prahlad Subhajit Purkayastha DJ Pandit
  2. 2. Presenta(on  Overview     •  Client Profiles •  Business Need •  Solution Approach •  Benefits, Limitations & Next steps •  Customer View / Technical Considerations •  Demonstration •  Client Profiles Q&A
  3. 3. P3  is  a  Premier,  Oracle  Specialized   Partner  for  BI  Applica(ons  Founded in 2005 with alumni from Oracle, Big-5, and Industry P3 provides an end to end delivery model Operational Strategy Value EPM/BI EBS IT Support Client Success Factors Results Industry Best Practices and Process Alignment Industry and Application Specific Accelerators Change Management and Knowledge Transfer
  4. 4. Case  Studies    Synaptics is a leading worldwide Leading global supplierdeveloper of human interface of photonics technologysolutions for mobile computing, products and solutions.communications, andentertainment devices. More than Worldwide Operations –a billion devices use Synaptic China, France, Germany,Interfaces. Italy. Korea, Japan E-business Suite 11.5.10 Hyperion Planning & Budgeting, Essbase OBIEE (10G,11G)
  5. 5. Business  Needs   •  Hyperion Planning and Budgeting used extensively for •  AOP’s •  Quarterly Forecasts •  Flash Forecasts •  Budget to Actual •  Real time visibility to budget and forecasts for Executive Management •  Provide Budget /Forecast to Actual reporting for Cost Center Managers •  Use a common reporting interface for the entire organization
  6. 6. Solu(on  Approach  –  Use  OBIEE  (10g,  11g)   1.  Use OBIEE as the reporting tool 2.  Integrate Hyperion Planning cube with OBIEE 3.  Implement cost center based security using Oracle Single Sign On (SSO) Reason -  OBIEE is already used for reporting in the organization -  Pre-built connectors exist from OBIEE to Essbase
  7. 7. Hyperion  Planning  Repor(ng  (Graph)  -­‐  OBIEE  11G      (Standalone)  
  8. 8. Hyperion  Planning  Repor(ng  (Pivot  table)  -­‐    OBIEE  11G      (Standalone)  
  9. 9. Benefits  ,  Limita(ons  &  Next  Steps   Benefits •  Tighter alignment of FP&A and Cost Center Managers •  Simplify reporting (reduce dependency on Excel add in/Smart View) •  Real time reporting from Hyperion Planning •  Immediate visibility to variances outside the threshold Limitations •  Ability to view Actual information ONLY at the summarized level •  Cannot drill from Actual to see GL Journal details Next Steps •  Integrating of Hyperion Planning with Financial Analytics (
  10. 10. Customer  View  -­‐  Technical  Considera(ons   Introduction Reasons for choosing OBIEE to Essbase integration Examples of dashboards created OBIEE 10G , 11G Differences for Essbase Integration Pro’s and Con’s Future considerations
  11. 11. 10g  Report  Samples  • Spread  sheet  format  similar  to  Excel  Add-­‐In  aUached  to  a  dashboard    
  12. 12. 10g  Report  Samples  -­‐  Con(nued  • Mul(ple  Scenario  Spread  sheet  format  similar  to  Excel  Add-­‐In  aUached   to  a  dashboard    
  13. 13. 10g  Report  Samples  -­‐  Con(nued  • Pie  Chart    
  14. 14. 10g  Report  Samples  -­‐  Con(nued  • Benchmark  Sample    
  15. 15. OBIEE  10g  &  11g  Differences   •  10G by default returns alias if present, if member name is required an additional column should be defined ( only works for leaf members), 11 G import process created both columns in physical layer. •  10 G by default designates Account dimension as measure dimension and create all members in account dimension as measures flattening account hierarchy. 11G creates single measure column retaining hierarchies for all dimensions. •  11 G import process provides option to create columns for UDA (user defined attributes). •  11G provides option to create columns for non-default aliases (i.e. German, French..) •  11G Provides Outline drill down like Essbase Outline in reports. •  11G Creates structure of attribute dimension. •  11G Brings alternate hierarchy automatically.  
  16. 16. Pro’s  &  Con’s   •  If Actual amounts are more than budgeted/forecasted amounts , it becomes difficult to drill into the details. •  FDM or ERPI provides drill down from Hyperion to single journal entry. Usually drill down is needed to focus on set of transactions.
  17. 17. Future  considera(ons-­‐  Integrate  OBIA  Financial  Analy(cs  with  Hyperion  Planning   •  Leverage existing OBIA Data Warehouse to feed Actual data to Planning/Essbase •  Actual data will be Consistent across all Hyperion and OBIEE reports •  Define Links to Pre-Built contents GL,AR, AP ... etc. for further analysis
  18. 18. Hyperion  Planning  Integra(on  to  OBIA  (Financial  Analy(cs)   • Demonstration • Technical Overview • Questions
  19. 19. Hyperion  Planning  Integra(on  to   Financial  Analy(cs  (   Demonstra(on  
  20. 20. Hyperion  Planning  Repor(ng  (Graph)  -­‐  OBIEE  11G      (Standalone)  
  21. 21. Hyperion  Planning  Repor(ng  (Pivot  table)  -­‐    OBIEE  11G      (Standalone)  
  22. 22. Hyperion  Planning  repor(ng  &  Dashboards  in  OBIEE  11G      (Integrated  with  Financial  Analy(cs)  
  23. 23. Drill  down  to  GL  Journal  transac(ons  which  was  out  of  threshold  
  24. 24. Drill  down  to  SubLedger  Transac(ons  
  25. 25. Drill  down  to  AP  invoice  details  
  26. 26. Traverse  –  Lineage  Tool   See wire frames ppt
  27. 27. Technical  Overview   •  Hyperion Planning was sourced from the Financial Analytics Warehouse ( rather than ERP •  Conformed the following dimensions between the 2 sources Fiscal Year Period Currency Ledger Account (includes Account Hierarchy – Group Account, Group Category) Cost Center Entity Scenario Version
  28. 28. Import  the  Essbase  Cube    
  29. 29. Essbase  Server  Details  
  30. 30. Iden(fy  the  Cube  to  be  imported  
  31. 31. Import  the  cube  to  the  Physical  Layer  
  32. 32. Create  Aliases  &  UDAs  Objects  
  33. 33. Import  the  Cube  within  Business  Model  -­‐  Core  
  34. 34. Conform  Fiscal  Year  Dimension  –  Add  the  cube  to  the  exis(ng  logical  sources  
  35. 35. Conform  Fiscal  Year  Dimension  –    Secng  the  LTS  for  Fiscal  Year  
  36. 36. Create  Presenta(on  Subject  Area  
  37. 37. Repeat  for  other  Dimensions  &  Measures     •  Use  slide  34,  35  &36  for  other  Dimension(s)  &   Measure  (s)  
  38. 38. Presenter(s)  Informa(on  Prashanth PrahladPresidentpprahlad@p3si.netSubhajit PurkayasthaVP Industry Solutionsspurkaya@p3si.netDJ PanditSr. Strategic Financial and Reporting
  39. 39.  Thank  You  !