integrating oracle essbase and oracle business intelligence: case study
TRANSCRIPT
Integrating Oracle Essbase and Oracle Business Intelligence:
Case Studies
Prashanth Prahlad Subhajit Purkayastha
DJ Pandit
Presenta(on Overview • Client Profiles
• Business Need
• Solution Approach
• Benefits, Limitations & Next steps
• Customer View / Technical Considerations
• Demonstration
• Client Profiles • Q & A
P3 is a Premier, Oracle Specialized Partner for BI Applica(ons
P3 provides an end to end delivery model
Client Success Factors
Value
Results Industry Best Practices and Process Alignment
Change Management and Knowledge Transfer
Industry and Application Specific Accelerators
EPM/BI EBS IT Support
Operational Strategy
Founded in 2005 with alumni from Oracle, Big-5, and Industry
Case Studies
E-business Suite 11.5.10 Hyperion Planning & Budgeting, Essbase OBIEE (10G,11G)
Leading global supplier of photonics technology products and solutions.
Worldwide Operations – China, France, Germany, Italy. Korea, Japan
Synaptics is a leading worldwide developer of human interface solutions for mobile computing, communications, and entertainment devices. More than a billion devices use Synaptic Interfaces.
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
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
Hyperion Planning Repor(ng (Graph) -‐ OBIEE 11G (Standalone)
Hyperion Planning Repor(ng (Pivot table) -‐ OBIEE 11G (Standalone)
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 (7.9.6.3)
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
• Spread sheet format similar to Excel Add-‐In aUached to a dashboard
10g Report Samples
• Mul(ple Scenario Spread sheet format similar to Excel Add-‐In aUached to a dashboard
10g Report Samples -‐ Con(nued
• Pie Chart
10g Report Samples -‐ Con(nued
• Benchmark Sample
10g Report Samples -‐ Con(nued
• 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.
OBIEE 10g & 11g Differences
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.
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
Hyperion Planning Integra(on to OBIA (Financial Analy(cs)
• Demonstration
• Technical Overview
• Questions
Hyperion Planning Integra(on to Financial Analy(cs (7.9.6.3)
Demonstra(on
Hyperion Planning Repor(ng (Graph) -‐ OBIEE 11G (Standalone)
Hyperion Planning Repor(ng (Pivot table) -‐ OBIEE 11G (Standalone)
Hyperion Planning repor(ng & Dashboards in OBIEE 11G (Integrated with Financial Analy(cs)
Drill down to GL Journal transac(ons which was out of threshold
Drill down to SubLedger Transac(ons
Drill down to AP invoice details
Traverse – Lineage Tool
See wire frames ppt
Technical Overview
• Hyperion Planning was sourced from the Financial Analytics Warehouse (7.9.6.3) 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
Import the Essbase Cube
Essbase Server Details
Iden(fy the Cube to be imported
Import the cube to the Physical Layer
Create Aliases & UDAs Objects
Import the Cube within Business Model -‐ Core
Conform Fiscal Year Dimension – Add the cube to the exis(ng logical sources
Conform Fiscal Year Dimension – Secng the LTS for Fiscal Year
Create Presenta(on Subject Area
Repeat for other Dimensions & Measures
• Use slide 34, 35 &36 for other Dimension(s) & Measure (s)
Presenter(s) Informa(on Prashanth Prahlad President [email protected] Subhajit Purkayastha VP Industry Solutions [email protected] DJ Pandit Sr. Strategic Financial and Reporting Architect [email protected]
Thank You !