One Small Step – Transitioning to Financial Data Management – Enterprise Edition

November 18th, 2016

Matt Spencer

Why is Finit Here?

Finit takes pride in being a company of makers and doers; people who dig

in and get their hands dirty

To deliver personalized financial reporting solutions and experiences

…Not Company to Company, but Person to

Person

By listening, questioning, and analyzing

Finit Culture

No debt or external ownership means complete alignment & focus on our client’s needs and vision

We bring a quality of craftsmanship to our designs and execution that lead to solutionsthat are functional, usable and efficient

We actively seek feedback and invest in training and professional growth in our consultants

We use employees, not contractors. Compensationbased on CLIENT SATISFACTION

A CULTURE OF INTEGRITY

ADVOCATES OF YOUR INTERESTS

DRIVEN TO DELIVER

TAILORS OF OUR CRAFT

Our Partnership with Clients

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 EPM / CPM project (500+)

Some Finit Customers

Questions

About the Presenter

Matt Spencer(mspencer@finit.com)

Experience

8 years with Hyperion suite7 years in financial reporting for public and privately held companies

Certification/Education

BS – Accounting, Finance, University of Kansas (Rock Chalk!)Certified Public AccountantCertified Treasury ProfessionalHFM Certified

Client TestimonialFinit has a remarkable reputation and no matter who you meet from the company, you can understand where the comments come from. Each of them is knowledgeable in so many aspects and takes the time to make sure the client fully understands the topic. They exceed the bar of professionalism while maintaining an enjoyable atmosphere.

One Small Step – and One Giant Leap to Oracle FDMEE

• Topic Overview:• What is FDMEE?

• Reasons for Transitioning

• Pre-work

• Oracle Migration Process – Overview

• First Steps After Conversion

• New Features

• Functionality Differences

• Process Step Image

Introduction – Transitioning to FDMEE

• Financial Data Quality Management – Enterprise Edition

• Data integration tool used in the Hyperion suite of products

• Next generation of Financial Data Quality Management, the legacy Hyperion data integration tool

• How is it different?• Integrated into workspace, no longer a peripheral program

• Enhanced features and functionalities (we’ll get there later)

What is FDMEE?

1. Upgrading to HFM 11.1.2.4 or later (FDMEE is required)

2. Upgrading to HFM 11.1.2.3 and want to go ahead and convert

3. Web integration – reduction of peripheral programs

4. Because it’s AWESOME!

Transitioning to FDMEE – Why?

But Before Conversion…

• Before running the migration process, there are a few things you should do in order to make sure the conversion go a little smoother:• Make sure you have installed FDMEE 11.1.2.4.x

• Make sure you have installed ODI and SQL Mgmt Studio

• Import formats – everybody needs one!

• Update Cross-application parent locations

• Access to all of the sources and destinations

• Backup of the current FDM database

Pre-Work

10 9 8 7 6 5 4 …

• The conversion process only brings over locations that have a defined import format. This is important to remember if you have locations that are only used as parent locations for maps. If you want those locations brought over, give them some type of generic import format before migrating.

• Parent locations can no longer apply to locations across multiple applications. If you’re sharing a parent location, you will need to create new parent locations so one exists in each application.

Import Formats & Cross-App Parents

• VB-based scripting is not supported in FDMEE. Prior to migration, any import format or other custom scripts will need to be converted to the Jython language (some may not

need to be converted because of multi-dimensional mapping…stay tuned).

• There are a multitude of Jython resources available:

• The Jython Project – www.jython.org

• Jython Developer’s Guide – www.jython.org/devguide

• Various printed resources

• Finit has some pretty great resources too…

Script Conversion

Slide 16

Pre-Migration – Access Requirements

Write access to the new FDMEE database

Write Access to the Classic FDM database

ODI SQL Mgmt Studio

Oracle Migration Process –Get there in One Piece!

Oracle Migration Process - Overview

• What does it do?

• Gathers the metadata and data from your existing FDM application

• Converts it to a format that is compatible with FDMEE

• Loads the metadata and data to the new FDMEE application

• Oracle Database Integrator (ODI) and a SQL query tool are used to accomplish these activities

• Only FDM releases 11.1.1.x and 11.1.2.x to 11.1.2.4.000+

• Where can you get it?

• ODI is installed with 11.1.2.4 FDMEE

• Link to migration document:docs.oracle.com/cd/E57185_01/FDMMG/FDMMG.pdf

• Keep in mind there are really two parts to the migration

• Setup data process – locations, import formats, etc.

• Historical data process

• What comes over: • Target Applications

• Global and Application Categories

• Global and Application Periods

• Logic, Check Entity, and Check Rule Groups

• Import Formats

• Locations

• Data Mappings

• Data, workflow status and it’s mappings

• What doesn’t: • Custom Scripts

• Custom Reports

• Source adapter details

Migration Process – What Comes Over

• Activities the tool automatically performs:

• Moves all of your metadata type items, of course

• Member case in mappings and other maintenance items

• Automates the transfer of as much, or as little data as you desire

Migration Process – Make Your Life Easier

1. Download the patch from Oracle

2. Technical Prep

Update the FDM and FDMEE Schemas

Configure ODI

3. Migrate Artifacts

4. Migrate Data

5. Additional Tasks

Migration Process – High-Level Steps

• There is a patch that can be downloaded from Oracle’s site that essentially contains the queries and tasks that will be performed by ODI and the SQL tool of your choice during the conversion.

• The link to the patch can be found in the migration guide. After downloading, unzip the patch in a newly created directory that will house FDMEE items and data.

Migration Process – Get the Patch

• Updating FDM and FDMEE Schemas: The schemas are essentially the database objects. In this step, SQL commands will be run through SQL Management Studio, SQL Developer, or some other SQL tool of your choice to create some temporary FDM and FDMEE SQL objects that will be used by ODI during the migration.

• Configuring ODI involves configuring the Oracle Data Integrator tool to actually perform the migration.

• There are many, many great screenshots of all of the detailed steps above in the migration guide. That could be a webinar on its own.

Migration Process – Technical Prep

• The first portion is the migration of the metadata type artifacts. This step will bring over your locations, import formats, check groups, etc.

• The second portion of the migration relates to the movement of the data from the FDM Classic application to the new FDMEE application. During this process, you can choose a range of years/period for the migration utility to bring over. It is beneficial to have discussions before the migration of exactly how much data is required.

• Will your legacy FDM application be retained somewhere?

• Is the FDM application the source of record for any financial reporting?

• Does your audit process typically involve reviews of the data in FDMEE?

Migration Process – Migrate!

Now That You’re Up And Running…

• Security – don’t underestimate this!

• Clean up field on the data load rule

• Journal template date format

• Import format delimiters

• Rebuilding custom reports

Now That You’re Up And Running…

• Security in FDMEE is handled through shared services

• This is nice to have all of your security now in one place, but it also means you have to build this out from scratch

• Set up location groups

• Set up role groups

• Assign users accordingly

Security – Clean Sheet Design

• A good practice is to create location groups to then assign users to in shared services. You can also group these into other groups as well.

• Creating this prefix and suffix will create a shared services group for each location once you click on the “Maintain User Group” button

Security – Location Groups

• You will also need to set up roles. These are similar to the roles that were used in FDM Classic, with some changes to the level of granularity available, which we will discuss later

• Once you have defined your roles, create a group in shared services, provision a role to the group, and assign users accordingly

Security – Role Groups

• As part of the migration, the utility populates a dummy file name into the location data load rules. You will need to clear this out for your locations after the migration completes.

Data Load Rule Field

Clear this out

v

v

• The FDMEE journal feature is somewhat more picky than FDM Classic when it comes to date naming conventions.

• In FDM Classic, various formats for March of 2016 would have been accepted, such as :

• Mar – 2016

• 03/31/2016

• In FDMEE, the first option is no longer valid, and the journal template must contain the numeric date 03/31/2016.

• This is something helpful to communicate to users as they can update their journal uploads in advance of the conversion and avoid unnecessary kickouts.

Journal Template Date Format

• As opposed to the wider variety of delimiter options in FDM Classic, FDMEE only supports the following six delimiters:

• Comma “,”

• Pipe “|”

• Exclamation “!”

• Colon “:”

• Semi-colon “;”

• Tab “ “

• During the migration, any other delimiters in your import formats are changed to a comma as a default, so make sure to update your files if necessary.

Import Format Delimiters

• Custom reports do not get brought over as part of the migration, so they will need to be rebuilt for FDMEE.

• This is accomplished through a tool called Oracle BI Publisher, which is an add-in to Microsoft word. The high level steps of this process are:

1. Download and install the most recent version of Oracle BI Publisher from Oracle’s site

2. Write an SQL query in FDMEE in the Setup – Query Definition screen to retrieve the data you wish to present in your report

3. Export an XML file of that query on the same screen

4. Open Word, enable the add-in, and import the XML. This is essentially the metadata for creating your report.

5. In Word, you can define the layout and format of your report.

6. Load the updated Word report template file back on to the server to be used as a template.

7. Define your report on the Setup - Report Definition screen, specifying the use of your

SQL query and report template that you’ve created.

Custom Reports – Use of Report Tool

New Features

• Scenario specific data load rules

• Multi-dimensional mapping

• Other new features

Some New Features

• FDMEE has the capability of using scenario specific data load rules

• You can create multiple data load rules for the same location

• This can be beneficial if you want to use the same set of data to load actual results at a detailed level, but then have a separate set of maps that load forecast to more summarized accounts.

Data Load Rules by Scenario

Data Load Rule Setup - Actual

Data Load Rule Setup - Budget

Data Load Rule Map Assignment

• Multi-dimensional mapping is a new feature for FDMEE that allows you to create maps that are dependent on the members in other dimensions

• In FDM Classic, this type of activity was a pretty common reason to create import format scripts

Multi-Dimensional Mapping

Multi-Dimensional Mapping - Setup

• Some other cool new things…

• Data Sync – a new feature that allows you to move data between different EPM applications without creating an intermediary file

• The ability to see mapping errors and fix directly from the data load workbench

• The ability to use FDMEE to load application metadata

New Feature Supporting Cast

Functionality Differences

• Import File Formats

• Security…

• Check Images

Functionality Differences

• FDMEE does not support the same number of data file encodings as FDM Classic

• Because of this, some files that had previously imported into FDM without any issues may now fail at the import step in FDMEE, with little resolution guidance in the process detail log

• How to get around it, 3 different ways1. Have the users change their source file encoding

2. Have the users change their default character set (works if all files they load are the same encoding)

3. Script to work some black magic

Functionality Differences – File Formats

• This option works well, but is a little bit of a hassle for users to open the file and mess with the encoding every time they want to import.

File Format Option 1 – Text Editor

• This option also works well, but what about users who load files to multiple locations, from different source systems that have different encodings?

File Format Option 2 – User Settings

• Another option is to write a script that will temporarily change the users default character set

• Before import, the script references the Integration Option field 1 to determine if the location has been identified as one needing a character set change

• If the field contains the flag, the users default character set is changed to an option that will allow non-Unicode encoded files to import

• After the import has finished, the users default character set is updated back to it’s original setting

File Format Option 3 – Custom Script

• Along with the whole process of security now being contained within Workspace and Shared Services, role security works slightly different as well.

• In FDM Classic, there was a high level of granularity around which functions and features users had access to on each of the navigation screens. For example, users could be set up to view maps, but not have access to change those maps.

• This is slightly different in FDMEE…

Functionality Differences – Security

• On the Role Security tab, an admin can assign security to a specific role. Any user that has that role, can perform the tasks associated with that role.

Functionality Differences – Security

• Note that the choices in the role security screen align with the options in the left pane. If a role is assigned this security setting, any user with that role will have access to perform any of the activities on that screen.

• This differs from FDM Classic in that there were sub-options under many of the choices, to limit what functionality the users had access to on each of the screens.

Functionality Differences – Security

• Users with access to mapping will have access to perform any of the activities on this screen for the locations they have access to

Functionality Differences – Security

• In FDM Classic, changing your process step icons between fish and a notebooks with a checkmark was a built-in option

• In FDMEE, the functionality still exists, but you need some more access, and a maybe a sense of humor

• The check images in FDMEE are stored in the following location:

• When a process passes or fails, FDMEE calls one of these images, with either the ProcessSucceeded or ProcessFailed name

Functionality Differences – Check Images

• To change your images, simply drop in a pass and fail image of your choice, and rename the pass image “ProcessSucceeded” and the fail image “ProcessFailed”

• Now, during the import, validate, export and check steps, the icons will display as what you’ve dropped in as “ProcessSucceeded”

Functionality Differences – Check Images

Wrap-up

• Overview

• Reasons to upgrade

• Use the Oracle migration process!

• Prep items

• Immediate steps• Plan for Security

• Differences and new features to keep in mind

• Resources• Oracle Docs:

• FDMEE Admin Guide

• FDMEE Migration Guide

Summary

Thank You for Attending!

Page 58

Today’s Presenter:

Matt Spencer

mspencer@finit.com

General Questions:

Greg Barrett

gbarrett@finit.com

Joe Mizerk

jmizerk@finit.com

Copy of the slides or Recording:

Email us for a copy of the slides or a link to the recording

insights@finit.com

Past webinars:

www.finit.com/webinars

Follow us on Twitter for updates:

@Finit_Solutions

KSCOPE 2017 – Never Too Early!

Thank You!