2. About Edgewater Ranzal
One of the Largest
Oracle/Hyperion Practices in
the U.S.
Oracle / Hyperion Platinum
15 Years Partner - Highest Status
700+ clients
1000+ projects Vertical Expertise with High-
Profile Clients from Coast to
Coast
Sound Project Methodology
Insures Project Success
“One Stop Shop” for ALL EPM
Implementation needs
3. Our Services
Business
Consolidation Planning
Intelligence
Data Project
Infrastructure
Services Management
4. Who Is Tony Scalese
Over 10 years Experience with Data Integration and
Financial Planning & Consolidation on the Hyperion suite of
products
Established many innovative FDM design, customization
and automation concepts that have evolved into standard
Industry-wide practices.
Certified HFM Consultant - System 9 & Fusion 11
Present at Oracle conferences, Ranzal webcasts and post
on Oracle Technology Network (OTN) and blog on
www.FDMGuru.com
B.A. Economics, Allegheny College; MBA Candidate, Babson
College
5. Financial Data Quality Management is…
…the premier end user data transformation
tool to load data to Oracle EPM applications
including:
● HFM
● Essbase (Planning)
● HSF
● Hyperion Enterprise
…a centralized data management solution
…AWESOME
6. Key Benefits of FDM
End user friendly web interface that provides
directed workflow
Flexibility
Drill down & drill through capabilities for data
investigation
Organization wide process monitoring
Extensive automation capabilities using built
in batch loader
Open architecture product
7. FDM Capabilities
Load to base or upper level members
Use load rules
Execute clears & aggregations
Control dimension output order
Execute calc scripts
Execute MAXL scripts
Load multiple periods in a single execution
8. Configuring FDM Essbase Adaptor
Essbase Client (32 bit) must be installed on
the FDM application server
Essbase adaptor has a form based
configuration screen that is more elegant
than the other adaptors
Allows Machine profiles, dimensions &
integration options all to be modified from a
single interface
9. Machine Profile
Establishes the connection between the FDM
application server and the Essbase server
If a user name is specified in the machine
profile, these are the credentials used any
time FDM interacts with Essbase
The security rights of the user name in the
profile will trump the security rights if any
user is input in the integration settings or the
user logged into FDM
11. Connection Information
Enter the Essbase Application & Database
Logon Method
● Global: User ID and Password specified in the
integration settings controls all interaction with
Essbase
● Unified: The Essbase security assigned to the
FDM user controls the interaction with Essbase
unless a user name is specified in the machine
profile
13. Load Information
Enabled Drillable Region Load: used for
Drill through from Essbase to FDM
Load Rule Name: Essbase load rule FDM
will use to load the data (recommended)
Enable consolidation: Allows FDM to run
aggregation after a load.
Default Calculation Method: Dynamic; agg
calc in adaptor is used
15. Dimensions
Global – point of view dimensions; category,
period, year (if applicable)
Mappable – 23 available dimensions for
mapping; Entity, Account, ICP, Custom1-20
Attribute – 14 attributes to store additional
information about a record; can be used in
scripting
16. Dimensions
Each dimension (mapped & global) needs to
be configured & saved
Activate/Deactivate dimension as needed
Foreign name must exactly match Essbase
dimension name; select Dimension name
from the drop down
Give the dimension an alias and set
matching labels
18. Calc Order – Pros & Cons
Essbase adaptor can be configured to
control the order in which dimension are
output to the data file to be loaded
Pro: Improved data load time, less Essbase
fragmentation
Con: Cross dimensional maps could be
impacted
19. Essbase Security Roles Needed
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
20. Load Rules
Essbase load rules can be leveraged by FDM to
load the FDM produced data file
Eliminates the need to “map” global dimensions
such as version & HSP Rates as those can be
specified in the load rule
All data load errors are collected in an err file
Can be used to ignore FDM dimensions used for
mapping but that do not need to be loaded
Avoid mapping in load rules – use FDM as
intended!
21. Load Action – Data Clearing
During the Export workflow stage, when
loading in replace, FDM will execute a clear
calc script
Default calc script is coded in the Load action
and executes for each entity in the data file to
be loaded
Script can be modified for application needs
22. Consolidate Action – Aggregation
Enable consolidation option in the adaptor
2 Types of Execution
● Each base entity in the data file (Enable base
entity calc option enabled)
● For each entity in the validation entity assigned to
the location (Dynamic/File in Default calc method)
● AGG script in the Consolidate action OR
● Essbase Calc Script specified in Validation Entity
23. Tokenized Calc Scripts
Calc scripts can be created to mimic
Planning business rules that use run time
prompts (tokens)
FDM process can be created that supply the
token(s) when executing the calc script
Eliminates the need for multiple calc scripts
or custom process to update substitution
variables
24. Executing MAXL
FDM does not have an API to execute MAXL
MAXL is generally executed via a Windows
batch file
FDM can execute Windows batch files using
Windows shell
● Set wShell =
WScript.CreateObject("WScript.Shell")
● lngResult = WShell.Run(strCommand,
WindowStyle, blnWaitOnReturn)
25. Enhanced Validate
When integrating with HFM, FDM will verify that
the mapped record will successfully load to HFM
The reciprocal does NOT exist for Essbase
integrations
As an Essbase outline changes, FDM can (and
often does) have a map that translates a source
dimension member to a target member that no
longer exists in Essbase
When this happens, the user will encounter a
data load error during the Export Process
27. ERP Integrator is…
…a new module of FDM that allows data and
metadata to be sourced from Oracle ERP systems:
● Oracle eBusiness Suite (eBS)
● PeopleSoft G/L
● PeopleSoft HR
…used to drill to source level transactional data in
the ERP system directly from EPM applications
…capable of writing budget data to the ERP from an
Essbase (BSO & ASO) or Planning application
…continuing to evolve
…the future of data integration
28. ERPi Key Benefits
Direct integration to ERP & Human Resource
systems
Drill through capabilities on G/L data
Budget write back capabilities
Integration with EPM Workspace
Leverages ODI
ASO loading capabilities
Flexibility
● Integration with FDM
● Direct Usage
29. FDM with ERPi
Source adaptor controls data import process
Integration option 1 – use to specify data
rule; must be created in all CAPS in ERPi
Sign conversion happens automatically for
G/L liability, equity & revenue types
Attribute 14 – don’t use it; ERPi adaptor uses
for drill through
30. ERPi Stand Alone
Provides metadata loading capabilities
Provides write back for budget data
Automation is controlled through JAVA web
services
31. ERPi Load Methods
EPMA: loads data using data
synchronization; metadata using interface
tables and import profile
Classic: direct load to the EPM application
FDM: Data only
32. ERPi Import Formats
One to One – Single chart field/segment to 1
EPM dimension
Many to One – Up to 5 chart fields/segments
or segments to 1 EPM dimension
Chart fields/Segments can be reused
33. ERPi Mapping
Explicit
Between
Like
● *
● ?
● <segment>
● <blank>
Data synchronization routine is used to load data
when using ERPi with EPMA apps (no FDM)
Data synchronization can be further leveraged
for mapping
34. ERPi Writeback
Supports Planning, BSO & ASO for 11.1.2.x
Cannot write back to PeopleSoft Human
Capital
Supplementary process must be run in the
ledger after the ERPi process to “post” the
budget data
35. ERPi Considerations
Only functional currency is extracted using
ERPi
Currencies & Rates – Use ISO codes; only
loaded when using classic data load
Mapping – Do not use underscore (_) as the
concatenation character if using FDM
36. Integration with Essbase & Planning
“Classic” FDM, FDM with ERPi or ERPi stand
alone can all be used to load data
Single FDM application can connect to
multiple applications and/or cubes
FDM natively loads data to Essbase, not the
relational repository of Planning; however,
custom processes can be created as needed
37. Decision Point
What’s The Right Solution?
● A) FDM
● B) FDM with ERPi
● C) ERPi
Answer
● D) All of the above!
39. New Features in 11.1.2.1
FDM
● Office 2010 support
ERPi
● SQL Server support
● Data load rules refinement
● Adjustment period mapping
● HR data rules
40. Other Ranzal Presentations
Calculation Manager: The New and Improved Application to Create Hyperion
Planning Business Rules – Monday, 11:15 am, Room 102C
Security and Auditing in HFM – Tuesday, 4:30pm, 101B
Best Practices for Using DRM with EPMA – Wednesday, 8:30am, 103A
Getting Started with Calc Manager for HFM – Wednesday, 8:30am, 101B
Advanced Topics in Calc Manager for HFM – Wednesday, 9:45am, 101B
Maximizing the Value of an EPM Investment with ERPi, FDM & EPMA – Wednesday,
11:15am, 101B
Taking your FDM application to the next level with Advanced Scripting – Friday,
8:30am, 101B
IFRS reporting within Hyperion Financial Management – Thursday, 10:30am, 101B