Getting the Most out of EPM
Converting FDM to FDMEE – What’s it all
about?
March 16, 2016
Joe Mizerk ([email protected])
About the Presenter
Joe Mizerk
[email protected]
• Director – Business
Development
• CPA (Inactive)
• 20+ years Hyperion Experience
• Former Global Consolidations
Manager
• UpStream, Hyperion, Oracle,
Finit (Last 6 years)
• FDM, Enterprise, HFM
Oracle Hyperion EPM Services
Full Cycle Implementations
Upgrades and Redesigns
Dedicated Support
Why is Finit here?
Finit takes pride in being a company
of makers and Doers; people who dig
in and get their hands dirty
…Not Company to
Company, but Person to
Person
By listening, questioning,
and analyzing
We make and deliver personalized financial
reporting solutions and experiences
Page
The Finit Family
PRIVATELY
OWNED
Fully aligned with
our clients, not just
bottom line $
DEBT FREE
No debt or external
ownership
Page
NO
SUBCONTRACTORS
CLIENT
SATISFACTION
Work with Finit
employees, no
subcontractors
Compensation
based on CLIENT
SATISFACTION
Finit Customer Success
Our values, culture, and approach to
becoming a trusted advisor to our
customers has led to
100% customer success
for every Finit client (250+) and for
every Oracle Hyperion project (500+)
Page
Some Finit Customers
Agenda
• FDMEE Introduction
• FDMEE Integration
• 11.1.2.3 versus 11.1.2.4
• What changed in 11.1.2.4
• Using the conversion utility
Agenda
• What will the utility convert
• What won’t the utility convert
• Setting up for the conversion
• Steps for the conversion
• Post conversion steps
• FDMEE Nuances
FDMEE Defined
• FDM Enterprise Edition
• Beginning with release 11.1.2.3, Oracle
combined “FDM” with “ERPi” to create FDM
Enterprise Edition (FDMEE)
• This combines the direct sourcing and
drillback to the source that ERPi provides
while still providing users the core
functionality (workflow, mapping, controls,
audit, and he FISH) that they have grown to
love with FDM (UpStream)
• All scripting now handled with Jython
Oracle FDMEE Integration Strategy
• Data Sources
• Pre-built Direct
Connection
• File based
Integration
• Excel based
Integration
• Open Interface
Adapter – go to DB
tables
• Source from Target
Applications - New
• Target Applications
• HFM
• Planning
• Public Sector Planning
and Budgeting
• Essbase – ASO & BSO
• ARM
• HPCM
• Custom Application
• Create a Flat File to be
loaded to an external
system
FDMEE 11.1.2.3 / 11.1.2.4
• Existing FDM Customers – 11.1.2.3
• FDM and FDMEE are both included
• Choice to stay on FDM Classic
• Note this is the terminal release
• New and Existing FDM Customers – 11.1.2.4
• Can Only install FDMEE, there is no more FDM
• Upgrade considerations – Premier Support is
ending
Added to FDMEE 11.1.2.4
• Excel Interface
• Allows us to export data/tables to excel
• Allows us to import data to FDM tables from Excel
• These existed in FDM and now they exist in FDMEE
• POV Locking
• Enhanced Data Sync from FDMEE
• Use a Target Application as a Source System!
• Import Format Enhancements
• Can fix mapping errors on the fly now
• Get the Fix option to add a rule to a kick out at the
Validate step
Conversion Utility Overview
FDMEE - What WILL Convert
• Create / Replicate the Integration with the Target
• HFM, Planning, Essbase, etc
• Periods and Categories (Global and Application)
• It will bring in the Locations
• No Control Review Locations
•
•
•
•
•
•
Import Formats (.uss scripts will be tagged)
Validation Entities and Validation Rules
Logic Groups
Mapping
Data
Data Load Rules
FDMEE - What WILL NOT Convert
• User Security
• Mainly handled in Shared Services
• Detailed Object Security
• Not at the level of the old FDM
• Scripts
• All Import scripts will need to go to Jython
• Custom FDM Reports
• Canned reports are there
• Control Group Locations – Does not exist
• Task Flows – Can still be done in FDMEE – prompting is
now available
FDMEE Migration Utility Prerequisites
• FDM version 11.1.1.x and 11.1.2.x are supported
• ERPi with FDM is only 11.1.2.x (11.1.1.3 and 11.1.1.4 will
not migrate)
• ODI Studio must be installed
• ODI comes with FDMEE
• ODI Studio is used to access the old FDM application
• Must be able to access the FDM and FDMEE databases
via SQL Developer/SQL Management Studio
• Download the Patch (21379349)
• Read the guide document in the patch folder
Viewing FDM
• Look at FDM to see what should convert
Performing the Conversion
Setting up for the Conversion
• Make a backup of the FDM DB
• Database Activities
• Update FDMEE Schema with SQL
• Update FDM Schema with SQL
• Install ODI Components
• Create Logical Schema
• Create Physical Schema
• Import Scenarios
Steps for Performing the Conversion
• Execute the Metadata Migration
• Set Context
• Set Variables (App Name, object prefix, etc.)
• Execute
• Execute the Data Migration
• Set Context
• Set Variables (App Name, object prefix, periods of data, etc.)
• Execute
• ***Need to repeat these steps for each Adapter that you
have in FDM or each FDM application
Post Conversion
• There could be several items that need to
be done after the conversion is run
• Update Drill Regions
• Suggest Reviewing Check Rules
• Update Data Load Rules for filename
• Run SQL if Oracle database due to CAPS issue
• Run SQL to drop the FDM data models from
FDMEE database
• Update Calc Sequence for Planning/Essbase
apps
Nuances of FDMEE
• When Importing data, automatically goes to Validate
• Intersection Validation Report no longer has tooltips
• Mapping has an ‘All Mappings’ tab where you cannot
add a rule but can view all types
• When browsing for data in FDMEE Workbench and maps
it is case sensitive
• FDMEE does not log mapping changes yet
Questions? Don’t ask me!
Use the code “Finit” for $100 discount
when you register for Kscope16