FDM, ERPi, EPMA, DRM, EAL - Understanding the Alphabet Soup of Integration

4,482 views
4,070 views

Published on

The EPM system continues to expand and more implementations are utilizing multiple products. A myriad tools and techniques exist to manage data and metadata integration within the EPM suite. This session will explore the different options available and how they can be used independently as well as in concert with one another. The strengths and limitations of each toolset will be explored. Client examples will be used to highlight real world implementations, leading/best practices as well as lessons learned.

2 Comments
1 Like
Statistics
Notes
  • #FDM - FDMEE Hyperion Financial Data Management Enterprise Edition Oracle FDM FDMEE Hyperion Data Management Videos and Books Online Sharing $14 9GB http://www.dbmanagement.info/Tutorials/FDM.htm
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • http://www.dbmanagement.info/Tutorials/DRM.htm
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
4,482
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
272
Comments
2
Likes
1
Embeds 0
No embeds

No notes for slide

FDM, ERPi, EPMA, DRM, EAL - Understanding the Alphabet Soup of Integration

  1. 1. FDM, ERPI, EPMA, DRM, EAL - UNDERSTANDING THE ALPHABET SOUP OF INTEGRATION
  2. 2. About Me• Oracle ACE – One of 29 in the world focused on BI• Over 12 years of experience across the EPM suite• Oracle certified for Hyperion Financial Management – System 9 & Fusion 11• FDM Practice Manager @ Edgewater Ranzal – www.ranzal.com• www.FDMGuru.com
  3. 3. Terminology• Metadata – Master Data / “Data about data” – Dimensions: Accounts, Entity, etc – Hierarchies/rollups• Integration – Process of extracting, transforming & loading data and metadata from source systems to target systems – Data and metadata management/movement within the EPM suite
  4. 4. Metadata Integration
  5. 5. EPMA• Enterprise Performance Management Architect• Available since System 9 release of Hyperion• Web based - Integrated into workspace• Intended to managed EPM applications – HFM, Planning, Essbase, HPCM (required)• Free tool• “DRM lite”
  6. 6. EPMA Key Benefits• Share common dimensionality across multiple applications – reduced build and administration time• Ability to easily duplicate applications for testing• Ability to secure individual dimension maintenance• Ability to compare deployed application to EPMA shared library or app view• Ability to rename a member in HFM and not lose the data associated with the member• Metadata properties are prebuilt; application accelerators• Change audit
  7. 7. EPMA Short Comings• Intended to manage metadata for EPM applications only• Does not currently support HSF (on the roadmap)• Import options are limited and restrictive• Limited automation• Performance can be suboptimal• No workflow
  8. 8. DRM• Data Relationship Management• Former Razaa product, previously known as MDM but rebranded after Oracle acquisition of Hyperion• Enterprise level master data management hub
  9. 9. DRM Key Benefits• Programmatic business logic• Comprehensive audit trail• Versioning ability• Tool agnostic• Robust automation capabilities• Integrations with Oracle BPEL (Workflow)
  10. 10. DRM Short Comings• Cost• Not integrated in Workspace (pre 11.1.2.2)• No application administration• Lacks pre-population of EPM specific properties
  11. 11. Common Questions• Do I have to use EPMA?• Should I buy DRM?• Do I have to use EPMA when I use DRM?• Can I use DRM and EPMA together?• Are DRM and EPMA my only options?
  12. 12. Data Integration
  13. 13. FDM• Financial Data Quality Management• Formerly Upstream WebLink• Data transformation, not an ETL tool• Intended to load data to EPM applications
  14. 14. FDM Key Benefits• End user tool, very easy to use & maintain• Web based• Very robust audit & process monitoring• Strong automation capabilities• Prepackaged target system specific integration enhancements – Intersection validation – Consolidation – Data Protection – Journals• Mature product – Limited bugs / low severity
  15. 15. FDM Short Comings• Not intended to manage “big data” – Performance• Security model is not able to address more complex security schemes• Technology is old and losing support – Only capable of running on Windows & IIS• Not integrated in WorkSpace• Does not support loading data to ASO cubes• Not the strategic direction of Oracle
  16. 16. ERPi• Enterprise Resource Planning Integrator• The future of data integration in the EPM suite• Leverages Oracle Data Integrator (ODI) as its processing engine• Currently licensed as part of FDM
  17. 17. ERPi Key Benefits• The strategic direction of Oracle• Enables direct connectivity for many Oracle ERP systems & SAP (prebuilt) as well as other source systems (configuration)• Enables drill through to the source data in the source system• Enables metadata to be sourced from the source system to update EPM applications• Provides the ability to write back budget data from Planning and Essbase to the General Ledger• Integrated into WorkSpace• The use of ODI supports far larger data volumes• Utilizes JAVA web services
  18. 18. ERPi Short Comings• Does not currently include all of the functionality that are standard use in FDM• Not an overly mature product, but progressing very rapidly – Body of knowledge is limited• Learning curve for organizations & consulting partners• Potential additional licensing expense• No LCM support (prior to 11.1.2.2)
  19. 19. ODI• Oracle Data Integrator• A world class ELT solution
  20. 20. ODI Key Benefits• Many times provided at no additional cost• World class ELT tool capable of integrating nearly any source for data and metadata• Very robust processing capabilities• Prebuilt Knowledge Modules to integrate with the EPM suite
  21. 21. ODI Short Comings• Complex – True IT tool, requires strong SQL skills as well as data modeling – Not intended for end users• Thick client• Migration is sensitive• Build times can be longer
  22. 22. Kitchen Sink Key Benefits Short ComingsEPMA Data • Integrated in Workspace • Not the strategic direction ofSync • Can interact with the Oracle Planning relational repository • Mapping capabilities are limitedDIM / • World class ETL • Additional licensing expenseInformatica • Handles large volumes • Very complexEssbase Studio / • Provides drill through • Often requires a dataEIS capabilities warehouse • Can manage dimension • EIS is not the strategic builds as well as data loads direction of OracleLoad Rules • Proven • Mappings are difficult to • Fast manage • Not exposed to end users • Limited audit
  23. 23. Common Questions• We bought HFM, Planning, FDM, ERPi and Oracle gave us ODI. Which should we use?• Do I have to use FDM with ERPi?• Why should I use FDM with Essbase?• Can I get my fish back / can I change the fish in FDM?
  24. 24. Data Movement Within the EPM Suite
  25. 25. EA• Extended Analytics• Module of HFM & Hyperion Strategic Finance• Creates star schemas or flat files• Acceptable performance since System 9 release
  26. 26. EA Key Benefits• Included in HFM licensing• Extracts data from any level of any dimension• Can be scheduled using HFM Task Flows• Can be executed via the API
  27. 27. EA Short Comings• Extract profiles are specific to individual users• Flat file extracts are zipped• Only provides data extracts from HFM or HSF, not Essbase or Planning• Does not load data to “target” system
  28. 28. EAL• Essbase Analytics Link• Formerly the HyperRoll product• Provides a real time data flow from HFM to Essbase• Generates an Essbase cube on the fly
  29. 29. EAL Key Benefits• Real time results from HFM reflected in Essbase• Managed at the application tier• Prepackaged solution
  30. 30. EAL Short Comings• Additional cost• Essbase cube is dynamically created – Need to create partitions or write XREF or XWRITE calcs to populate Essbase “target”• EAL cube mirrors HFM dimensionality• Data movement is unidirectional
  31. 31. Other Approaches Key Benefits Short ComingsEPMA Data • Native functionality • Basic MappingSync • Classic apps not supported • Not real timeFDM • Able to handle complex • Additional licensing mapping • Does not include • Strong automation native/prebuilt adaptors to • Can interact with key source data from EPM apps EPM applications • Not real time • Bi-directionalERPi • Strategic direction • Additional licensing • Utilizes ODI • Limited automation • Pre-built connections • Lacks all of the FDM (future enhancement) functionality (future state) • Bi-directional • Not real time
  32. 32. Common Questions• Can FDM be used to move data between HFM & Essbase?• I don’t own EA, how much does it cost?• Are there any other options?
  33. 33. In Closing• There is not a “right” answer• Challenge the status quo• Chose the right tool for the job while thinking about your end users
  34. 34. Questions Tony Scalese ascalese@ranzal.com www.fdmguru.com

×