Getting the Most out of EPM
Converting FDM to FDMEE
September 18, 2015
Scott Peters (speters@finitsolutions.com)
• Founded in 2002
• 75+ employees in 20+ states
• Mostly CPAs, MBAs
• We have extensive Hyperion product and financial reporting
backgrounds
• 50+ Planning / Essbase Clients
• 80+ HFM Clients
• Managed several of the largest EPM projects in the U.S.
• Including the largest roll-out of HFM in North America
• Market Leader in ARM/FCM
• World Leader in FDM implementations and custom
solutions
Finit Overview
EPM Services
• Finit Answers
‒ Technical Support
‒ Functional / Admin
Support
‒ Access to Hyperion
SMEs
‒ Dedicated support
team and
guaranteed
response times
‒ Customer Service
Focus
‒ Flexible Time and
Material support
packages
‒ ‘Pay as you Go’
option
• Hyperion Planning &
Essbase
• Oracle Financial Close
Suite
• Infrastructure
• Data Services
• Project / Program
Management
• Redesign /
Enhancements
• Product Upgrades
• Application enhancements /
redesign
• Performance optimization
Dedicated
Support
Upgrades
Full Cycle
Implementations
• We make and deliver personalized financial reporting
solutions and experiences.
• By listening, questioning, and analyzing
• By building relationships … not company to company, but
person to person.
• We are Makers and Doers
Why is Finit Here?
We Run Finit like a Family
• Invest in our employees
• All owners actively involved in the
business
• No debt or external owners
• Prioritize the customer, not
profitability
• Long term stability
• Hire employees, not subcontractors
• Compensation model based on
client satisfaction
How do we achieve our beliefs?
• Our values, on which we ask you to provide consultant
feedback:
Finit Values
• Our values, culture, and approach to becoming a trusted
advisor to customers has led to 100% customer success
for every Finit client (225+) and for every Oracle
Hyperion project (450+)
Finit Customer Success
Some Finit Customers
Questions
Scott Peters
speters@finitsolutions.com
• Partner and Director of
Integration Services
• 10 years Hyperion Experience
• FDM, FDMEE, ODI, ERPi,
HFM, Essbase, Enterprise
• Designed and implemented
some of the most complex
FDM integrations in the world
(HFM, HE, Essbase/Planning
and Data Warehouses)
About the Presenter
• What will the utility convert
• What won’t the utility convert
• Prerequisites of the conversion
• Performing the conversion
• Post conversion steps
• FDMEE Nuances
• Intro to Jython
Agenda
Conversion Utility Overview
• Create the Integration with the Target
• Periods and Categories (Global and Application)
• Locations
• Import Formats (.uss scripts will be tagged)
• Validation Entities and Validation Rules
• Logic Groups
• Mapping
• Data
• Data Load Rules
What WILL Convert
• User Security
• Object Security
• Scripts
• Custom Reports
• Control Group Locations
• Task Flows
What WILL NOT Convert
• 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
• Must be able to access the FDM and FDMEE databases
via SQL Developer/SQL Management Studio
• Download the Patch (21379349)
Prerequisites
• Look at FDM to see what should convert
Viewing FDM
Performing the Conversion
• Database Activities
• Update FDMEE Schema with SQL
• Update FDM Schema with SQL
• Install ODI Components
• Create Logical Schema
• Create Physical Schema
• Import Scenarios
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
Performing the Conversion
• Need to repeat these steps for each Adapter that you
have in FDM or each FDM application
Performing the Conversion
• There could be several items that need to be done after
the conversion is run
• Update Drill Regions
• Review 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
Post Conversion
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
Nuances of FDMEE
Introduction to Jython
• Indentation is important
• If statements must line up (no end if)
• Case sensitivity
• StrCheck is not the same as strCheck or strcheck
• If analyzing the length of a string or a taking the left 1,
make sure that the length is greater than 0 first
• It is different but it is not that scary!!
Introduction to Jython
• File Parsing
• String Parsing
Introduction to Jython
• If Statement
Introduction to Jython
• Additional If Statement
Introduction to Jython
• Replace and Skip
Introduction to Jython
Questions?
Email us for a copy of the slides
or link to the recording
insights@finitsolutions.com
Past webinars:
www.finitsolutions.com/
webinars
Thank you for attending!
Presenter:
Scott Peters
speters@finitsolutions.com
General Questions:
Greg Barrett
gbarrett@finitsolutions.com
Joe Mizerk
jmizerk@finitsolutions.com

"Converting" FDM to FDMEE

  • 1.
    Getting the Mostout of EPM Converting FDM to FDMEE September 18, 2015 Scott Peters (speters@finitsolutions.com)
  • 2.
    • Founded in2002 • 75+ employees in 20+ states • Mostly CPAs, MBAs • We have extensive Hyperion product and financial reporting backgrounds • 50+ Planning / Essbase Clients • 80+ HFM Clients • Managed several of the largest EPM projects in the U.S. • Including the largest roll-out of HFM in North America • Market Leader in ARM/FCM • World Leader in FDM implementations and custom solutions Finit Overview
  • 3.
    EPM Services • FinitAnswers ‒ Technical Support ‒ Functional / Admin Support ‒ Access to Hyperion SMEs ‒ Dedicated support team and guaranteed response times ‒ Customer Service Focus ‒ Flexible Time and Material support packages ‒ ‘Pay as you Go’ option • Hyperion Planning & Essbase • Oracle Financial Close Suite • Infrastructure • Data Services • Project / Program Management • Redesign / Enhancements • Product Upgrades • Application enhancements / redesign • Performance optimization Dedicated Support Upgrades Full Cycle Implementations
  • 4.
    • We makeand deliver personalized financial reporting solutions and experiences. • By listening, questioning, and analyzing • By building relationships … not company to company, but person to person. • We are Makers and Doers Why is Finit Here?
  • 5.
    We Run Finitlike a Family • Invest in our employees • All owners actively involved in the business • No debt or external owners • Prioritize the customer, not profitability • Long term stability • Hire employees, not subcontractors • Compensation model based on client satisfaction How do we achieve our beliefs?
  • 6.
    • Our values,on which we ask you to provide consultant feedback: Finit Values
  • 7.
    • Our values,culture, and approach to becoming a trusted advisor to customers has led to 100% customer success for every Finit client (225+) and for every Oracle Hyperion project (450+) Finit Customer Success
  • 8.
  • 9.
  • 10.
    Scott Peters speters@finitsolutions.com • Partnerand Director of Integration Services • 10 years Hyperion Experience • FDM, FDMEE, ODI, ERPi, HFM, Essbase, Enterprise • Designed and implemented some of the most complex FDM integrations in the world (HFM, HE, Essbase/Planning and Data Warehouses) About the Presenter
  • 11.
    • What willthe utility convert • What won’t the utility convert • Prerequisites of the conversion • Performing the conversion • Post conversion steps • FDMEE Nuances • Intro to Jython Agenda
  • 12.
  • 13.
    • Create theIntegration with the Target • Periods and Categories (Global and Application) • Locations • Import Formats (.uss scripts will be tagged) • Validation Entities and Validation Rules • Logic Groups • Mapping • Data • Data Load Rules What WILL Convert
  • 14.
    • User Security •Object Security • Scripts • Custom Reports • Control Group Locations • Task Flows What WILL NOT Convert
  • 15.
    • FDM version11.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 • Must be able to access the FDM and FDMEE databases via SQL Developer/SQL Management Studio • Download the Patch (21379349) Prerequisites
  • 16.
    • Look atFDM to see what should convert Viewing FDM
  • 17.
  • 18.
    • Database Activities •Update FDMEE Schema with SQL • Update FDM Schema with SQL • Install ODI Components • Create Logical Schema • Create Physical Schema • Import Scenarios Performing the Conversion
  • 19.
    • Execute theMetadata 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 Performing the Conversion
  • 20.
    • Need torepeat these steps for each Adapter that you have in FDM or each FDM application Performing the Conversion
  • 21.
    • There couldbe several items that need to be done after the conversion is run • Update Drill Regions • Review 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 Post Conversion
  • 22.
  • 23.
    • When Importingdata, 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 Nuances of FDMEE
  • 24.
  • 25.
    • Indentation isimportant • If statements must line up (no end if) • Case sensitivity • StrCheck is not the same as strCheck or strcheck • If analyzing the length of a string or a taking the left 1, make sure that the length is greater than 0 first • It is different but it is not that scary!! Introduction to Jython
  • 26.
    • File Parsing •String Parsing Introduction to Jython
  • 27.
  • 28.
    • Additional IfStatement Introduction to Jython
  • 29.
    • Replace andSkip Introduction to Jython
  • 30.
    Questions? Email us fora copy of the slides or link to the recording insights@finitsolutions.com Past webinars: www.finitsolutions.com/ webinars Thank you for attending! Presenter: Scott Peters speters@finitsolutions.com General Questions: Greg Barrett gbarrett@finitsolutions.com Joe Mizerk jmizerk@finitsolutions.com