White Paper

Using FDM-FDMEE Migration Utility

Created on: 9-Nov-2015 Last Modified on: 12-Nov-2015

Table of Contents

Overview ........................................................................................................................................... 3

Pre requisites ................................................................................................................................. 3

Steps Involved in Migration ................................................................................................................ 3

Migrating FDM to FDMEE ................................................................................................................... 4

Updating DB Schema:- .................................................................................................................... 4

Updating FDMEE Schema...................................................................................................................... 4

Update the FDM Schema ...................................................................................................................... 6

Configuring ODI.............................................................................................................................. 7

Importing the Scenarios ...................................................................................................................... 10

Executing the Migration ............................................................................................................... 12

Pre requisites before running the Extract Setup ................................................................................ 12

Extract Setup ....................................................................................................................................... 12

Verify Migrated Objects in FDMEE .................................................................................................... 16

Migrated Data Load Rule & Workbench Data .................................................................................... 19

Challenges in Migration ................................................................................................................... 20

FDMEE Target application shows wrong dimension name ............................................................. 20

What can be done if you have already ran the migration with default alias name in FDM? ............. 20

Migration Issue when using Load type SQL INSERT............................................................................ 21

Migrated Data Load Mappings in Upper case ................................................................................ 22

Drill Region for HFM ........................................................................................................................ 22

Migrating Multiple Applications ................................................................................................... 22

Overview

This document explains step by step process involved in migrating Oracle Hyperion Financial Data

Quality Management (FDM) to Oracle Hyperion Financial Data Quality Management, Enterprise Edition

(FDMEE). Also discusses about the challenges faced during the migration. It is intended to have look and

feel of using FDM Migration utility, more information available in ORACLE® HYPERION FINANCIAL DATA

QUALITY MANAGEMENT, Migration guide.

http://docs.oracle.com/cd/E57185_01/epm.1112/fdm_migration.pdf

Pre requisites

Download Patch 21379349: FDM CLASSIC TO FDMEE MIGRATION UTILITY V 1.0

Working 11.1.2.x FDM Application Database

Database details of the FDM application Schema

Working FDMEE 11.1.2.4 Environment

Downloaded FDM-FDMEE Migration Utility

Database details of FDMEE Schema

ODI studio Installed & Configured

Steps Involved in Migration

Run the Prerequisite SQL Scripts in FDMEE & FDM Database

Configure FDM Data source on ODI

Import the Scenarios to ODI Designer

Execute the Scenario from ODI

Challenges in Migration

Migrating FDM to FDMEE

Updating DB Schema:-

Updating FDMEE Schema

1) Log in to FDMEE Schema using any SQL Client (SQL Developer in this case)

2) Run the aif_fdmee_create_Oracle.sql

Note: Use aif_fdmee_create_sql_server.sql for SQL Server Database

Update the FDM Schema

1) Log in to FDM Schema

2) Run aif_fdmc_create_common.sql

Note: aif_fdmc_create_common.sql works for both Oracle & SQL Server Database.

Configuring ODI

1) Extract the downloaded patch in to a newly created directory FDM. Below are the contents

of the Patch.

2) Open ODI studio configured with the FDMEE database

3) Select Topology Manager > Physical Architecture > Oracle > Right Click & Select New Data Server

4) Name the Data server as FDMC_DATA_SERVER > Enter the DBA Admin details to access the

Database.

Enter the JDBC URL Pointing to FDM Database & Test the Connection

5) Create Physical Schema under FDMC_DATA_SERVER > Select the FDM Schema & Save the Changes

6) Choose Generic SQL > New Logical Schema > Name > FDMC_SOURCE

Choose the context for GLOBAL as FDMC_DATA_SERVER

Importing the Scenarios

1) Designer > Load Plans and Scenarios > Right Click and Select Import Scenarios

2) Copy the XML files (SCEN_FDMC_EXTRACT_SETUP_001.xml And SCEN_FDMC_EXTRACT_DATA_001.xml) from the Extracted patch to the work repository

directory

<Oracle_Middleware_Home>\EPMSystem11R1\products\FinancialDataQuality\odi\11.1.2.4.00\workrep>

3) Select the Import Type: Synonym Mode INSERT_UPDATE > Browse to the Work Repository

4) Open Work Repository > Select the FDMC_EXTRACT_DATA_001 & FDMC_EXTRACT_SETUP_001

> OK to import the Scenarios.

Report will be generated showing the imported objects.

Executing the Migration

Pre requisites before running the Extract Setup

1) Length of Artifacts should NOT exceed 20 Characters, if it exceeds the process will fail.

You can identify the artifacts causing the issue by running SQL #4 in the script

aif_fdmee_misc.sql

Refer Migration Guide for more details.

Extract Setup

1) Go to ODI Studio > Designer > Select the Scenario “FDMC_EXTRACT_SETUP_Version-001” >

Right Click & Execute.

2) Select the right Context from Execution Screen.

3) Variable Values window will open with default values

4) To Edit the Value Field the Latest Value column should be Unchecked.

Replace Application with the Actual name (Should be entered in UPPERCASE)

Enter the Application Type

DB Name used for Planning application, ignored for HFM Applications

Prefix- Optional

5) Click OK to start the execution Process

6) Monitor the status from Operator Tab.

Go to Data Management > Verify whether all the objects got migrated

7) Once the execution is successful, Select the FDMC_Extract_DATA_VERSION_001 > Right Click & Execute

8) Enter the Application Name and Start & End Date for Data migration.

9) Verify the Process in Operator

With the above status, Migration would be completed.

Verify Migrated Objects in FDMEE

1) Migrated Target Application Details

2) Source System

3) Migrated Import Format

4) Migrated Location

5) Period Mapping, Category Mapping & Logic Groups

5) Data Load Mapping

Migrated Data Load Rule & Workbench Data

Challenges in Migration

FDMEE Target application shows wrong dimension name

1) FDMEE Target application uses dimension alias name mentioned in FDM application. The alias names of

FDM Dimensions MUST be same as mentioned in HFM Application.

Open FDM Workbench, verify the Dimension Aliases & Change as necessary with reference to the HFM

application.

Below example displays the dimension alias for ACCOUNT. The same procedure applies for all the other

dimensions.

What can be done if you have already ran the migration with default alias name in FDM?

Usually REFRESH METADATA option can be used to refresh the dimension names according to the

Target Application. Due to a known issue in FDMEE 11.1.2.4, it will duplicate the dimension members

and dimension members appear twice.

How to Overcome?

1. Fix dimension aliases in FDM Adapters as mentioned in the above & run the migration

Or

2. Delete all the dimensions in Target Application and then Refresh Metadata (this case was verified

in the example migration done for this documentation)

Note: Please have regular database BACKUP points to restore it to previous stages.

Migration Issue when using Load type SQL INSERT

Some of the records in the TPOVPARTITION table have a PARTTYPE value of 1. A load type 'SQL Insert' is

stored as 1 and load type 'Bulk insert' is stored as 2. In the first version of the migration utility, due to a

known issue, load type 'SQL Insert' is not supported. This will be fixed in the future versions of the

migration utility.

Follow the below workaround:-

Create a backup table

------------------------------------

create table tpovpartition_bk

as

select * from tpovpartition

update the table

--------------------------

update tpovpartition

set parttype = 2

where parttype = 1

;

The above information is available in the Oracle Knowledge.

FDM to FDMEE Migration is not Extracting All of the Artifacts from the FDM Application (Doc ID

2069544.1)

Note: Prior to making any changes have a clean BACKUP of your DATABASE.

Migrated Data Load Mappings in Upper case

When FDM used with Oracle Database, the migrated Data load mappings will be in Uppercase, which

will cause validation errors in FDMEE. FDMEE Stores members AS IS in Target applications.

To resolve this, run the Refresh Members process from Target Application, and then run the SQL#2 in

aif_fdmee_misc.sql.

Drill Region for HFM

Need to run the SQL#1 in aif_fdmee_misc.sql for using Drill URL in FDMEE.

Note: It has to be run on HFM database.

Migrating Multiple Applications

For Migrating more than one Application

Create new Physical Schema with Database details of the other application

Create new Context

Map the newly created Physical Schema

Oracle is a registered trademark of Oracle Corporation. Various product and service names referenced

herein may be trademarks of Oracle Corporation. All other product and service names mentioned may

be trademarks of their respective owners.

Copyright © 2015 Oracle Corporation All rights reserved.