FDM Classic Migrating To FDMEE - US-Analytics

41
FDM Classic Migrating To FDMEE Terry M. Ledet U.S. Analytics Solutions Group LLC

Transcript of FDM Classic Migrating To FDMEE - US-Analytics

FDM Classic Migrating To FDMEETerry M. Ledet

U.S. Analytics Solutions Group LLC

The EPM Carnival! 8 - 10 PM – Room 603

sponsored by:

Featuring:

The Quest – Are you up to the challenge?

Balloon Dart EPM Trivia

Ace Director Bean Bag Toss

Great Food and Flashy Prizes

Join the EPM Community at tonight’s

This material and discussion is presented for informational and illustrative

purposes only as the views and opinions of Terry M. Ledet, Solutions

Architect of U.S. Analytics Solutions Group LLC as of the date hereof,

and do not necessarily reflect the official policy or position of U.S.

Analytics Solutions Group LLC or its affiliates. Any views or opinions

expressed constitute judgments as of the date of this material and are

subject to change at any time without notice.

Important Information and Disclosure

US-Analytics is an industry leading professional services firm focused on

helping clients successfully establish and maintain long term Analytics and

Enterprise Performance Management applications and programs.

• Program Strategy

• Analytics and Performance Management Processes/Applications

• Operational Infrastructure

• Managed Services and Hosting

For over a decade, market leading companies have trusted US-Analytics to

solve complex business problems, drive managerial excellence, and deliver

operational agility.

Learn more at:

www.us-analytics.com

About US-Analytics

Solutions Architect Approaching ten years of tenure with U.S. Analytics

Approaching sixteen years of experience with Hyperion

software

Certifications:

Planning

Essbase

Hyperion Financial Management

www.linkedin.com/in/terryledet

About Terry M. Ledet

Discuss differences from a functionality

perspective between FDM Classic / ERPi and

FDMEE

Based on client experiences provide migration

and development considerations learned during

migration

Display / code examples

Objectives

“FDMEE is offered as the full-featured

successor to Oracle® Hyperion Financial Data

Quality Management ERP Integration Adapter

for Oracle Applications (ERPIntegrator) and

Oracle Hyperion Financial Data Quality

Management (FDM). FDMEE represents the

integration of both products. It captures key

functionality from FDM, and preserves the ERP

Integrator framework that enables users to load

metadata and data, and to drill-through and

write-back.”

FDMEE

FDMEE

FDMEE

Integrated into Workspace

Functionality Changes

One Application Per Environment

Financial Controls

System Settings / Application Settings

Functionality Changes

Security is 100% Shared Services

Role Security

Location Security

● Disabled by default

● Assigned to a role

Functionality Changes

Integrated Installation

● Oracle client installed

● 32 bit

● 64 bit

Oracle Data Integrator 11.1.1.7

FDMEE 64-bit Platform

LCM for Migrations

Load of Metadata

Functionality Changes

Multiple Browser Support

Multiple Operating Support*

UI Enhancements

Consistent Scaling and Load Balancing

* If integrating with HFM only Windows is supported

Functionality Changes

Import Scripts = Jython

Mapping Scripts = Jython or SQL

● #SCRIPT

● #SQL

● #FORMAT

Event Scripts = Jython or VB.Net Script

New Mapping Type = Multi Dimension

Map Export / Import

Functionality Changes

Removed

● DCOM

● Adapter Import

● Open Batch

● Workbench

● Scripts

● Reports

● Task Manager

● Activity Log

Functionality Changes

Migration Considerations

Patch the base 11.1.2.3 install

FISH

Migration Considerations

NO WIZARDS

Migration Considerations

New / Existing Customer

FDM Classic

● Install Yes / No

Customizations

● Reports

● Actions

Migration Considerations

Number and Complexity of Scripts

● Import

● Maps

● Event

Migration Considerations

Source Data

Targets

Financial Controls

Resources / Budget

Security

Migration Considerations

Migration Considerations

Migration Considerations

Number and Complexity of Scripts

● Import

● Maps

● Event

Source System

Source Adapter

● ERP’s

● Open Interface Adapter

Target Application

Development Considerations

Visual Basic Script <> Jython

Visual Basic Script <> VB.Net

Script development

● FDMEE

● Eclipse

● Notepad++

Development Considerations

FDM VB version

If varValues(13) = "0000120512_260" Then

Result = "10796"

Elseif varValues(13) = "0000120512_A09" Then

Result = "10796"

Else

Result = "[ICP None]"

End If

FDMEE Jython version

account = fdmRow.getString("ACCOUNT")

if (account == "0000120512_260"):

fdmResult = "10796"

elif (account == "0000120512_A09"):

fdmResult = "10796"

else:

fdmResult = "[ICP None]"

Development Considerations

SQL version

CASE

WHEN Account = '0000120512_260' Then

'10796'

WHEN Account = '0000120512_A09' Then

'10796'

ELSE '[ICP None]‘

END

Development Considerations

Development Considerations

Development Considerations

Development Considerations

Case Sensitivity - Invalid

Development Considerations

Case Sensitivity - Valid

Development Considerations

Formatting - Invalid

Development Considerations

Formatting - Valid

Development Considerations

BefValidate

AftProcMap

Event Script Examples

If UCase(strLoc) = "SAPEAST" Then

strSQLG="MERGE INTO " & strTableName & " D USING VW_SAPEASTU V ON (D.ENTITY =

V.COCODE AND SUBSTR(D.ACCOUNT,5,10) = V.GLACCT AND D.CATKEY = V.CATKEY AND D.PERIODKEY =

V.PERIODKEY AND D.CATKEY=" & CatKey & " AND D.PeriodKey='" & PerKey & "') WHEN MATCHED THEN

UPDATE SET D.UD5 = V.GROUPACCOUNT,D.UD6 = V.DEBITCREDIT, D.UD7 = V.AMOUNT"

Set rs=API.DataWindow.DataAccess.farsKeySet(strSQLG)

'Commit the MERGE INTO

Set rs=API.DataWindow.DataAccess.farsKeySet(strSQLCOMMIT)

if fdmContext["LOCNAME"] == "SAPEAST":

query = "MERGE INTO TDATASEG D USING VW_SAPEASTU V ON (LOADID = ? AND D.CATKEY =

V.CATKEY AND D.PERIODKEY = V.PERIODKEY AND D.ENTITY = V.COCODE AND SUBSTR(D.ACCOUNT,5,10)

= V.GLACCT) WHEN MATCHED THEN UPDATE SET D.UD5 = V.GROUPACCOUNT,D.UD6 = V.DEBITCREDIT,

D.UD7 = V.AMOUNT"

params = [ fdmContext["LOADID"] ]

print fdmAPI.executeDML(query, params, False)

fdmAPI.commitTransaction()

BefValidate

if fdmContext["LOCNAME"] == "SAPEAST":

query = "MERGE INTO TDATASEG D USING TBHVLOGICITEM H ON (LOADID = ? AND

H.CALCSTMTACCOUNTDESC = D.UD5) WHEN MATCHED THEN UPDATE SET D.UD9X = 'L', D.AMOUNTX =

D.AMOUNTX * -1, D.ACCOUNTX = H.CALCSTMTMATHVALUE WHERE D.AMOUNT <> 0 AND D.CHANGESIGN =

0 AND D.UD9X = 'S' AND SUBSTR(ACCOUNT,5,1) <> SUBSTR(ACCOUNTX,2,1)"

params = [ fdmContext["LOADID"] ]

print fdmAPI.executeDML(query, params, False)

fdmAPI.commitTransaction()

if fdmContext["LOCNAME"] == "SAPWEST":

query = "MERGE INTO TDATASEG D USING TBHVLOGICITEM H ON (LOADID = ? AND

H.CALCSTMTACCOUNTDESC = D.ACCOUNTX AND H.CALCSTMTACCOUNT = D.UD4 AND

H.CALCGROUPKEY = 'SAPWEST') WHEN MATCHED THEN UPDATE SET D.UD9X = 'W', D.AMOUNTX =

D.AMOUNTX * -1 WHERE D.AMOUNT = D.AMOUNTX AND D.UD9X IS NULL"

params = [ fdmContext["LOADID"] ]

print fdmAPI.executeDML(query, params, False)

fdmAPI.commitTransaction()

AftProcMap

Install both FDM Classic and FDMEE

Migrate FDM Classic

Agree on #SCRIPT or #SQL for map scripts

Install and configure either Eclipse or

Notepad++ for Jython script development

Determine if the FDM Classic application is the

application needed going forward

Decide on resources

Test, Test, Test

Lessons Learned

● 1644737.1 -> FDMEE Performance Benchmarks

● 1584133.1 -> FDMEE Mapping Concepts

● 1640612.1 -> Where Are the Logs for FDMEE

● 1616126.1 -> How to Export the ODI Operator Log

from the ODI Console for Hyperion Support

● 1613836.1 -> FDMEE Script Samples

Appendix

Oracle Hyperion Financial Data Quality Management Enterprise Edition (FDMEE) 11.1.2.3 Mapping concepts [Video]

Questions