fdm & erpi with essbase - streamlining data integration and challenging dogma
Post on 13-Sep-2014
15 views
DESCRIPTION
For more than a decade Essbase has provided a number of techniques to import data. As FDM and ERPi continue to become an integral component of the EPM suite, more and more people question - do we need FDM? We will explore the key benefits that FDM offers for Essbase including dynamic calc script execution, an end user controlled data integration process, detailed audit trails and lights out automation. ERPi further enhances the value add with drill through to the transactions within the source system.TRANSCRIPT
FDM & ERPI WITH
ESSBASE -
STREAMLINING
DATA
INTEGRATION AND
CHALLENGING
DOGMA
About Me
• Oracle ACE – One of 29 in the world focused on BI
• Over 12 years of experience across the EPM suite
– More than 35 implementations
• Oracle certified for Hyperion Financial Management – System 9 & Fusion 11
• FDM Practice Manager @ Edgewater Ranzal – www.ranzal.com
• www.FDMGuru.com
Essbase Dogma
• I’ve been loading data to Essbase for years. I don’t need FDM.
• I can do everything in load rules & MAXL that I can do in FDM.
• I’ve got EIS / Studio for drill through. I don’t need ERPi.
• FDM can’t handle the data volumes that are loaded to Essbase.
• FDM can’t load to ASO or the Planning repository.
FDM Key Features
• Financial Data Quality Management
• End user friendly web interface that provides directed workflow
• Drill through capabilities for data investigation
• Organization wide process monitoring & auditing
• Extensive automation capabilities using built in batch loader
• Prepackaged target system integration
• Mature product – Limited bugs / low severity
FDM Workflow
• Import – Data is loaded from a flat file or relational source into the
FDM database
– FDM transformation (maps) tables are applied
• Validate – Checks that all source members were transformed
• Export – Clears data from Essbase
– Loads data to Essbase
– Aggregates Essbase
• Check – Retrieves aggregate/calculated values from Essbase and
compares to administrator defined thresholds to determine data quality
Why Use FDM?
• Web Based
• Robust Mapping Capabilities – Cross dimensional mapping
– Wildcards
• Centralized data repository – Drill through
– Re-processing data
• Audit – When & by whom was data processed
– What maps were applied; who modified the maps; what was the old map
• Process Monitoring
FDM Mapping Types
• Explicit: 1 to 1 Mapping
• Between: Continuous range that maps to 1 EPM Member
• In: Non-continuous range that maps to 1 EPM Member
• Like: Wildcard
• Ignore: Skip/Do not load record
FDM Drill Through
FDM Audit
FDM Process Monitoring
Even More Reasons for FDM
• Distributed model
• API execution of calc scripts
– “Business Rules”
• Leverage load rules
• Post load validation
• Open architecture product that supports
enhancements
• Automation
“Business Rules”
• Dynamic based on the data being
processed
Using Load Rules
• Allows default dimensionality to be set
Post Load Validation
• Check Report retrieves aggregate values
Pre-Load Validation
• Prevent Load/Calculation Errors
Automation
• Email status including error capturing
Essbase Dogma
• I’ve been loading data to Essbase for years. I don’t need FDM.
• I can do everything in load rules & MAXL that I can do in FDM.
• I’ve got EIS / Studio for drill through. I don’t need ERPi.
• FDM can’t handle the data volumes that are loaded to Essbase.
• FDM can’t load to ASO or the Planning repository.
ERPi In a Nutshell
• Enterprise Resource Planning Integrator
• “FDM 2.0” - 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 – no data warehouse/staging needed
• 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
ERPi Drill – EPM
ERPi Drill – Source
ERPi Supported Systems
System Version EPM Version
Oracle eBusiness Suite 11.5.10 cu2
12
12.1.3
11.1.1.3+
11.1.1.3+
11.1.2.1+
PeopleSoft Financial
Management
9.0
9.1
11.1.1.3+
11.1.2.1+
PeopleSoft Commitment
Control
9.1 11.1.2.2
JD Edwards EnterpriseOne 9.0 Requires Tools 9.1 11.1.2.2
Fusion Financials 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
Management
9.0 11.1.2.0+
Essbase Dogma
• I’ve been loading data to Essbase for years. I don’t need FDM.
• I can do everything in load rules & MAXL that I can do in FDM.
• I’ve got EIS / Studio for drill through. I don’t need ERPi.
• FDM can’t handle the data volumes that are loaded to Essbase.
• FDM can’t load to ASO or the Planning repository.
FDM Volumes
• Myth: FDM can only handle files with
<500k records
• Truth: FDM can handle millions of records
in an individual file if properly designed
– Efficient Mapping
– Parallel processing
– Creativity
Essbase Dogma
• I’ve been loading data to Essbase for years. I don’t need FDM.
• I can do everything in load rules & MAXL that I can do in FDM.
• I’ve got EIS / Studio for drill through. I don’t need ERPi.
• FDM can’t handle the data volumes that are loaded to Essbase.
• FDM can’t load to ASO or the Planning repository.
ASO & Planning Loads
• FDM does not natively load Essbase ASO
cubes or the Planning relational repository
• However, FDM can execute batch files
– Execute MAXL to load Essbase
– Execute stored procedures, SSIS packages,
etc.
FDM is as powerful as the creativity &
ability of the person implementing it
Use Cases
• Stand alone FDM
• Stand Alone ERPi
• FDM with ERPi
Stand Alone FDM
• Non Oracle GL Systems
• Acquisitions
• Relational sources
Stand Alone ERPi
• Oracle source systems
• SAP General Ledger
• ASO integration
• Very large data volumes
FDM with ERPi
• Oracle source systems
• SAP General Ledger
• Complex mapping
FDM Considerations
• Multiple adaptors can be used in a single application
• Dimension names must exactly match Essbase dimension name
• ESB_PRIV_APPDESIGN or ESB_PRIV_DBDESIGN – used to perform a load using replace
• ESB_PRIV_CALC – used to execute clear & aggregation scripts
• If not loading with replace and no need to run an aggregation, no special roles are needed but string load must be enabled on the FDM target adaptor
• Load rules should be used to manage “global” dimensions
Ready to Take the Plunge
• Oracle Support
• Oracle Technology
Network (OTN)
• Oracle documentation
• Edgewater Ranzal
• www.FDMGuru.com
Questions
Tony Scalese
www.fdmguru.com
FDM, ERPi, EPMA, DRM, EAL - Understanding the Alphabet Soup of Integration: 3:45 – 4:45