Getting the Most outof EPM Converting FDM to FDMEE – What’s it all about? March 16, 2016 Joe Mizerk

Joe Mizerk Director – Business Development CPA (Inactive) 20+ years Hyperion Experience Former Global Consolidations Manager UpStream, Hyperion, Oracle, Finit (Last 6 years) FDM, Enterprise, HFM About the Presenter

Oracle Hyperion EPM Services Full Cycle Implementations Upgrades and Redesigns Dedicated Support

Why is Finit here? Page 4 Finit takes pride in being a company of makers and Doers; people who dig in and get their hands dirty We make and deliver personalized financial reporting solutions and experiences …Not Company to Company, but Person to Person By listening, questioning, and analyzing

The Finit Family Page 5 Fully aligned with our clients, not just bottom line $ No debt or external ownership Work with Finit employees, no subcontractors Compensation based on CLIENT SATISFACTION PRIVATELY OWNED CLIENT SATISFACTIO N NO SUBCONTRACT ORS DEBT FREE

Finit Customer Success Page 6 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+)

Some Finit Customers

FDMEE Introduction FDMEE Integration versus What changed in 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 Agenda

FDM Enterprise Edition Beginning with release , 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 FDMEE Defined

Data Sources Pre-built Direct Connection File based Integration Excel based Integration Open Interface Adapter – go to DB tables Source from Target Applications - New Oracle FDMEE Integration Strategy 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

Existing FDM Customers – FDM and FDMEE are both included Choice to stay on FDM Classic Note this is the terminal release New and Existing FDM Customers – Can Only install FDMEE, there is no more FDM Upgrade considerations – Premier Support is ending FDMEE /

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 Added to FDMEE

Conversion Utility Overview

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 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 - What WILL NOT Convert

FDM version x and x are supported ERPi with FDM is only x ( and 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 ( ) Read the guide document in the patch folder FDMEE Migration Utility Prerequisites

Look at FDM to see what should convert Viewing FDM

Performing 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 Setting up for 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 Steps for Performing the 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 Post Conversion

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

Questions? Don’t ask me! Use the code “Finit” for $100 discount when you register for Kscope16