1. Swimming Through the FDM to FDMEE Upgrade
Andrew Hales
3/28/18

2. AGENDA Vertical Edge Introduction Why Everyone Should Upgrade
Similarities and Differences Between FDM and FDMEE
Migration Strategies and Considerations
Oracle Migration Utility
Deeper Dive on Non-Migration Artifacts
Q&A

3. Who we are
Providing exceptional quality and value, while imparting a customer-focused approach.
Vertical Edge Consulting Group is your trusted partner for business consulting and technology solutions, ensuring reliability and scalability for your growing company.
2010
Year Founded 35
Employees 3
National Practices 2
Locations 1
Inspired Vision for Success
Our Company
Exceptional values, passion for success, and dedicated commitment drive our success.
Oracle Platinum Partner
Consultants average years of industry and Big 4 consulting experience
Technology focus on EPM, BI and Cloud solutions, integrating with leading Tier 1 and 2 ERP systems
IT Strategy & Advisory Practice with CIO and Fortune 500 leadership experience
In-depth understanding of Cloud Technology & Solutions, driving today’s strategic technology decisions
Strong dedication to customer success and uncompromising values

4. Our services Trusted Advisory Technology Technology Expertise
Enterprise Performance Management (EPM)
Oracle Hyperion Financial Management
Oracle Hyperion Planning
Oracle Hyperion Planning & Budgeting Cloud Service (PBCS)
Oracle Hyperion Essbase
Oracle Hyperion FDM/FDMEE
Oracle Hyperion DRM
Oracle Hyperion Reporting & Analysis
Oracle Hyperion SmartView
Business Intelligence (BI)
Oracle Business Intelligence Enterprise Edition (OBIEE)
Oracle Business Intelligence Foundation Suite (BIFS)
Oracle Business Intelligence Cloud Service (BICS)
Oracle Business Intelligence for Applications (OBIA)
Advisory Services
CIO Advisory
IT Strategy
Cloud Advisory
Project Management Oversight (PMO)
Enterprise Resource Planning Advisory (ERP)
Enterprise Architecture
Technology
Technology Expertise

5. Oracle epm experience Enterprise Planning & Forecasting
Oracle® Certified Platinum Partner
One of the nation’s leading Oracle EPM strategy & implementation firms
Successfully implemented Oracle EPM solutions for dozens of clients in the US, and abroad
Oracle EPM professional average 15 years of hands-on experience
Focused on Fortune 500 companies & large scale, enterprise-wide implementations
Deep expertise from process design to technology implementation
Proven functional and industry templates to leverage best practices
Hyperion Essbase, Planning and HFM certified professionals
Enterprise Planning & Forecasting
Planning, Budget & Forecasting
Workforce & Capital Expenditure Planning
Planning System Design & Implementation
Balanced Scorecard
Hyperion Planning™, Workforce Planning™, Capital Expense Planning™
Financial Consolidation
Financial Close Process Design
Consolidation System Design & Implementation
Financial Reporting & Analysis
Financial Management™, Financial Data Quality Management™
Reporting & Analytics
Management Dashboards
Profitability Analysis
Human Resource Analysis
Sales & Procurement Analytics
Essbase™ Solutions, SmartView™, and reporting tools
Business Intelligence
Data Management & Integration
Content Management
BI Enterprise Edition™, Data Relationship Management™ and integration tools

6. What is FDMEE
Successor to Financial Data Quality Management (FDM) and ERP Integrator (ERPi)
First released with version
ETL standard for EPM applications
Can integrate with virtually any source system
Replaces FDM/ERPi as of version – new customers cannot license FDM Classic
Designed to look and feel very similar to FDM to ease burden on end user training

7. Why Upgrade? Bug Fix and Enhancements support
FDMEE is built on modern technology – easier to troubleshoot
Better browser support
Direct integration into Workspace
Enhanced native integration into EPM products
Enhancements to other products that integrate with FDMEE (HFM, Planning, etc)
FDMEE continues to receive enhancements with each PSU

8. NOTABLE ENHANCEMENTS Better EPM Integration
Direct and significantly enhanced integration with EPM applications both as a source and target
HFM, Planning, Essbase, HTP, DRM, FCM, HPCM
The list is growing
Easy UI driven synchronization of EPM apps.
Multi-Dimensional Maps
Better multi-load interface and options
LCM support
Interfaces with Oracle Cloud offerings
ODI Engine
Removal of Microsoft dependencies
Automation improvements
Direct integration with common databases – Oracle, SQL, MySQL, Teradata, DB2/400

9. EPM Data synchronizations
Very easy, clean interface
Same familiar FDMEE map types
Can easily be automated or scheduled
Can easily run multiple periods in sequence

10. SIMILARITIES & Differences
Most functionality has corollary or similar functionality – OpenBatch etc
Basic artifacts remain largely the same – Import Formats, Locations, Mappings, Validations, etc. all behave and interact much the same.
File based integrations are virtually unchanged.
Keeps the direct integration concepts of ERPi and expands on them
DIFFERENCES
Scripting language – Jython
Reporting – BI Publisher engine. Most standard reports have a pre-built similar report in FDMEE
Workspace Integration
ODI is underlying engine doing the work
Enhancements and native integrations
Security better integrated with shared services
Data load rules
Many common custom built solutions from FDM classic are available out of the box with FDMEE

11. THINGS TO CONSIDER ON UPGRADE
This is not a “Lift and Shift” or “Wizard” upgrade
Ideal time to re-assess process, clean up applications, and take advantage of new features or integration points
All scripting should be re-written to new Jython technology. VB can be re-used in spots but best practice is to rewrite
Custom reporting will have to be re-created
Security has to be recreated.
One application per environment. Current environments with multiple FDM applications will need to be merged into a single application

12. Migration Strategies Rebuild Application(s) Manually
Only viable for very small, simple applications
Manually recreate objects using the FDMEE UI
Time consuming and slow
Manual Database Manipulation
Viable for any size application
Requires deep knowledge of both FDM and FDMEE database repositories
Practical for any size application
Enables very granular approach to migration
Oracle Migration Tool
Similar to the manual database manipulation option
Oracle provides the transformation logic between FDM and FDMEE database repositories
Some ODI knowledge is recommended as well as basic familiarity with FDM and FDMEE repositories
Not as granular as manual database manipulation

13. What is the migration utility
Two ODI scenarios – Download from My Oracle Support
One for metadata(import formats, locations, etc.)
One for data
Classic ETL approach
Extract rows from FDM Classic Database
Transform and enrich the data
Load the enhanced data into the FDMEE Database
Knowledge Requirements
Requires some ODI knowledge/familiarity to configure and troubleshoot
Knowledge of the FDM classic and FDMEE repositories is helpful in troubleshooting and executing as well

14. Migration Utility – What it does move
Import Formats and Locations
Mappings
Validation Entities/Rules*
Validation/Check Rules will require some post migration manipulation
but the existing rules are copied over and populated
Target Applications/Adapters
Category/Period mappings
Logic Groups
Historical Data
Can select how much data to bring over
Creates dummy data load rules

15. Migration Utility – What it does NOT move
Scripts
References to import scripts are maintained in import formats but scripts will need to be created
Import Integration scripts don’t exist in FDMEE. Locations with import integration scripts will be created with a new Open Interface source adapter
Security
Must be recreated manually.
Location security is granted via groups in shared services
Reports
Custom report templates will need to be recreated with BI Publisher templates
Most existing out of the box reports have a similar report in FDMEE
Inbox/Outbox Files
Not required

16. Jython is the new standard
Scripts
Jython is the new standard
Lackluster built in “editor” – recommend use of a Eclipse IDE
Download from Eclipse.org
Best Practice
Write all scripting in Jython
Import scripts are required to be written in Jython ONLY
Event and Custom script types can use either Jython or VB
There is a difference in the versions of VB utilized in classic and FDMEE
Some VB FDM API functions are no longer available
Stop and think about why each script was built in the first place. It may not be necessary anymore.

17. Jython vs VB Sample in VB Sample in Jython
Exact same functionality in 3 lines versus 6!

18. Custom reporting built using BI Publisher framework
Reports
Custom reporting built using BI Publisher framework
Most pre-packaged reports in classic have a similar report in FDMEE – more being added in patches
Create SQL Query in FDMEE
Generate XML package with source columns and sample data
Import XML package into BI Publisher Add-in
Create template and translation file from BI Publisher toolset
Bundle BI template and translation documents together
Add to FDMEE server and create report definition/registration
Add security as necessary in FDMEE and run reports

19. SECURITY
Security levels are similar to FDM classic – Intermediate 1-10, Administrator, Data Integration
Security levels can be applied at many levels to create a custom security model
Locations
Menu Items
Custom Scripts
Reports
Batch Processing
Location security is handled via FDMEE specific groups in shared services.

20. FDMEE Security Group maintenaince

21. QUESTIONS
For additional questions or additional information, please contact:
Andrew Hales
Senior Consultant at Vertical Edge Consulting Group