FDM & ERPi with Essbase - Streamlining Data Integration and Challenging Dogma
0 likes1,628 views
The document discusses the integration of FDM and ERPI with Essbase to enhance data management and analytics for businesses. It highlights key features, advantages, and the capabilities of FDM, including data quality management, automation, and support for large data volumes. Additionally, it outlines the compatibility with various ERP systems and provides insights on mapping and data processing techniques.
FDM & ERPi with Essbase - Streamlining Data Integration and Challenging Dogma
- 1. FDM & ERPi with Essbase - Streamlining Data Integration al and Challenging Dogma a nz te rR e wa E dg March 20, 2013 y of ert P rop Anthony Scalese Edgewater Ranzal
- 2. About Edgewater Ranzal z al an r R Focus w ate Services d ge People fE 15 Years o 700+ clients rty Methodology pe 1000+ projects Pro Customers Partnership
- 3. Our Services Dashboards & Scorecards, Profitability & Cost Mgmt, Financial Analytics & Reporting, Operational Analytics, What-if Analysis, Query & Reporting, Visual Exploration Financial performance, Legal, Business z al Planning, Budgeting, Forecasting, an Segment & Mgmt Reporting, Financial Intelligence Workforce Planning, Capital Planning, rR Close Project Planning, Campaign Planning, HFM Optimization, Performance Lab ate Strategic Finance SOX Compliance Support Consolidation Planning w Installation, Upgrades, d ge Project/Program Mgmt, EPM fE Migration, System Project Road Maps, Application yo Infrastructure Management Reviews, Business Monitoring, Backup and rt Recovery, Disaster Requirements, Process pe Recovery, Load Testing, Change, Documentation ro Hardware Sizing Data Support Services Services P Data Integration, Financial Data Support Services - Project/Program Management, Data Warehousing, Master Training Mgmt, EPM Road Maps, Application Data Management, ETL Services, Reviews, Business Requirements, Performance Tuning, Automation Process Change, Documentation Dashboards/Scorecards, Profitability Cost Mgmt, Financial Analytics & Reporting, Operational Analytics, What-if Analysis, Query & Reporting, Visual Exploration
- 4. About Me • Oracle ACE – One of 29 in the world focused on BI • Over 12 years of experience acrossal nz the EPM suite Ra ter wa – More than 35 implementations ge Ed • Oracle certified for Hyperion Financial y of Management –rtSystem 9 & Fusion 11 ro pe • FDM Practice Manager @ Edgewater P Ranzal – www.ranzal.com • www.FDMGuru.com
- 5. Essbase Dogma • I’ve been loading data to Essbase for years. I don’t need FDM. al nz • I can do everything in load rulesa& MAXL that I rR ate can do in FDM. ew dg through. I don’t need fE • I’ve got EIS / Studio for drill yo ERPi. ert P rop the data volumes that are loaded • FDM can’t handle to Essbase. • FDM can’t load to ASO or the Planning repository.
- 6. FDM Key Features • Financial Data Quality Management • End user friendly web interface that provides directed workflow al • Drill through capabilities for data Ra nz ter wa investigation ge • Organization wide process monitoring & Ed auditing of rty capabilities using pe • Extensive automation roloader P built in batch • Prepackaged target system integration • Mature product – Limited bugs / low severity
- 7. FDM Workflow • Import – Data is loaded from a flat file or relational source into the FDM database – FDM transformation (maps) tables are applied l n za Ra • Validate ter – Checks that all source members were transformed wa ge • Export Ed of – Clears data from Essbase rty pe – Loads data to Essbase – Aggregateso Pr Essbase • Check – Retrieves aggregate/calculated values from Essbase and compares to administrator defined thresholds to determine data quality
- 8. Why Use FDM? • Web Based • Robust Mapping Capabilities – Cross dimensional mapping z al – Wildcards an • Centralized data repository ate rR w – Drill through d ge – Re-processing dataf E o rty • Audit ro pe – When & P whom was data processed by – What maps were applied; who modified the maps; what was the old map • Process Monitoring
- 9. FDM Mapping Types • Explicit: 1 to 1 Mapping • Between: Continuous range that maps to 1 EPM Member al nz 1 EPM Ra • In: Non-continuous range that maps to Member ter wa • Like: Wildcard ge • Ignore: Skip/Do not of Edrecord load rty ro pe P
- 10. FDM Drill Through z al an rR w ate d ge o fE rty ro pe P
- 11. FDM Audit z al an rR w ate d ge o fE rty ro pe P
- 12. FDM Process Monitoring z al an rR w ate d ge o fE rty ro pe P
- 13. Even More Reasons for FDM • Distributed model • API execution of calc scripts – “Business Rules” z al an • Leverage load rules rR ate • Post load validation ew dg that fE • Open architectureoproduct rty pe supports enhancements P • Automation ro
- 14. “Business Rules” • Dynamic based on the data being processed z al an rR w ate d ge o fE rty ro pe P
- 15. Using Load Rules • Allows default dimensionality to be set z al an rR w ate d ge o fE rty ro pe P
- 16. Post Load Validation • Check Report retrieves aggregate values z al an rR w ate d ge o fE rty ro pe P
- 17. Pre-Load Validation • Prevent Load/Calculation Errors z al an rR w ate d ge o fE rty ro pe P
- 18. Automation • Email status including error capturing z al an rR w ate d ge o fE rty ro pe P
- 19. Essbase Dogma • I’ve been loading data to Essbase for years. I don’t need FDM. • I can do everything in load rules & al MAXL that I can do in FDM. Ra nz • I’ve got EIS / Studio for wa ter drill e gERPi. through. I don’t need Ed of data volumes rty • FDM can’t handle the ro that are loadedpe to Essbase. P • FDM can’t load to ASO or the Planning repository.
- 20. ERPi In a Nutshell • Enterprise Resource Planning Integrator • “FDM 2.0” - The strategic direction of Oracle al nz (configuration) • Enables direct connectivity for many Oracle ERP systems & Ra SAP (prebuilt) as well as other source systems ter • Enables drill through to the source data in the source system – no data warehouse/staging needed wa ge Ed • Enables metadata to be sourced from the source system to update EPM applicationsf o ywrite back budget data from Planning • Provides the ability rt eto r p and Essbase toothe General Ledger P • Integrated into WorkSpace • The use of ODI supports far larger data volumes • Utilizes JAVA web services
- 21. ERPi Drill – EPM z al an rR w ate d ge o fE rty ro pe P
- 22. ERPi Drill – Source z al an rR w ate d ge o fE rty ro pe P
- 23. ERPi Supported Systems System Version EPM Version Oracle eBusiness Suite 11.5.10 cu2 al11.1.1.3+ z 11.1.1.3+ an 12 12.1.3 rR 11.1.2.1+ PeopleSoft Financial 9.0 w ate 11.1.1.3+ Management 9.1 d ge 11.1.2.1+ PeopleSoft Commitment fE 9.1 o 11.1.2.2 rty Control ro pe JD Edwards EnterpriseOne 9.0 Requires Tools 9.1 11.1.2.2 Fusion Financials P 11.1.2.1.501+ SAP R3 4.7 11.1.2.1.501+ SAP ECC 6.0 11.1.2.1.501+ PeopleSoft Human Capital 9.0 11.1.2.0+ Management
- 24. Essbase Dogma • I’ve been loading data to Essbase for years. I don’t need FDM. • I can do everything in load rules & al MAXL that I can do in FDM. Ra nz er tthrough. I wa • I’ve got EIS / Studio for drill don’t need ERPi. Ed ge ofthe data volumes • FDM can’t handle rty ro that are loadedpe to Essbase. P • FDM can’t load to ASO or the Planning repository.
- 25. FDM Volumes • Myth: FDM can only handle files with <500k records • Truth: FDM can handle millions of al nz Ra records in an individual file if properly designed a ter – Efficient Mapping d g ew fE yo – Parallel processing – Creativityop ert Pr
- 26. Essbase Dogma • I’ve been loading data to Essbase for years. I don’t need FDM. • I can do everything in load rules & al MAXL that I can do in FDM. Ra nz er tthrough. I wa • I’ve got EIS / Studio for drill don’t need ERPi. Ed ge of data volumes rty • FDM can’t handle the ro that are loadedpe to Essbase. P • FDM can’t load to ASO or the Planning repository.
- 27. ASO & Planning Loads • FDM does not natively load Essbase ASO cubes (in replace) or the Planning relational repository al nz • However, FDM can execute batch Ra files a ter g ew Ed – Execute MAXL of – Execute storedyprocedures, SSIS pert packages, etc. P ro FDM is as powerful as the creativity & ability of the person implementing it
- 28. Use Cases • Stand alone FDM • Stand Alone ERPi • FDM with ERPi z al an rR w ate d ge o fE rty ro pe P
- 29. Stand Alone FDM • Non Oracle GL Systems • Acquisitions • Relational sources z al an rR w ate d ge o fE rty ro pe P
- 30. Stand Alone ERPi • Oracle source systems • SAP General Ledger • ASO integration z al an • Very large data volumes rR w ate d ge o fE rty ro pe P
- 31. FDM with ERPi • Oracle source systems • SAP General Ledger • Complex mapping z al an rR w ate d ge o fE rty ro pe P
- 32. FDM Considerations • Multiple adaptors can be used in a single application • Dimension names must exactly match Essbase al nz Ra dimension name ter • ESB_PRIV_APPDESIGN or ESB_PRIV_DBDESIGN – used to perform a load using wa e replace dg • ESB_PRIV_CALC – used to execute clear & aggregation scripts y o fE ert ropspecial roles are needed but string • If not loading with replace and no need to run an P aggregation, no load must be enabled on the FDM target adaptor • Load rules should be used to manage “global” dimensions
- 33. Futures Discussion • Classic FDM • ERPi/FDMEE z al an rR w ate d ge o fE rty ro pe P
- 34. Ready to Take the Plunge • Oracle Support al • Oracle Technology nz Ra ter Network (OTN) • Oracle documentation ge wa • Edgewater Ranzalof Ed rty pe • www.FDMGuru.com o Pr
- 35. Questions al nz Tony Scalese Ra ter [email protected] wa www.fdmguru.com ge f Ed rt yo ro pe P