hyperion integration- odi fdm hal

Efficiently Delivering Effective Solutions

Oracle Hyperion Integration Products

Introduction and OverviewIntroduction and Overview

www.finitsolutions.com

Agenda Effi i tl D li i Eff ti S l tiAgenda• Introduction


• Overview of Oracle Hyperion Integration Products

• Review of Business Cases and available tools

• Q & A

www.finitsolutions.com‐ 2 ‐



IntroductionIntroduction


Who is Finit? Effi i tl D li i Eff ti S l tiWho is Finit?Finit Solutions specializes in the Oracle Hyperion Performance Management Solutions suite of products:


g p

Financial Consolidation and Reporting

Integration

Planning and Business Intelligence

• Strong focus on customer service and value:Strong focus on customer service and value:– Over 105 clients and Finit has never had a failed project. Every client is a reference.– Value is driven from consultants with Hyperion expertise, strong Finance /

Accounting knowledge and proactive customer service.• Ranked by Inc Maga ine in 2007 and 2008 as one of the Top 100 fastest growing• Ranked by Inc. Magazine in 2007 and 2008 as one of the Top 100 fastest growing

private IT Services companies in the US.• Member of multiple Hyperion customer advisory boards and new product

validation programs.


Finit Solutions: Sample ClientsFinit Solutions: Sample Clients




Overview of Oracle’s Integration ProductsOverview of Oracle s Integration Products


Oracle Hyperion Integration ProductsOracle Hyperion Integration Products

Financial Data Quality Management (FDM)

Oracle Data Integrator (ODI)Management (FDM)

Data Integration Hyperion Application Link Management (DIM) (HAL)

Enterprise Performance Data Relationship

pManagement Architect

(EPMA)

Data Relationship Management (DRM)

ERP Integrator (ERPi) ‘Classic’ Metadata Tools


Financial Data Quality Management (FDM)g ( )

• FDM is a web based financial data tool that is used to load, map and validate source system financial data into a target.

• FDM has a pre‐built data load workflow that walks through the different load steps (Import, Validate, Export, Check).

• FDM has a user‐friendly interface that allows users to maintain their source system to target system mapping tables and load their data.

• FDM can source financial data either by directly connecting to ( h h dsource systems (through FDM source adapters or via

Integration scripts) or it can read source system files.• FDM has Hyperion target adapters for Hyperion Enterprise,

HFM Pl i / E b d H i St t i FiHFM, Planning / Essbase and Hyperion Strategic Finance. • FDM has a data mart adapter that can be used to map to non‐

Hyperion charts of accounts.


• FDM can be enhanced through VB script customization.

Financial Data Quality Management (FDM) Use Caseg ( )

Strengths and Use Case• Pre‐Built interface (workflow, mapping, logging)• Validations are a key component (mapping, data, target system).• Typical use case is for financial data processing that involves mapping in a

multi‐user environment.Li it tiLimitations• FDM cannot perform any Metadata functions (load metadata or manage

metadata hierarchies)Similarities to Other Integration ProductsSimilarities to Other Integration Products• ODI and DIM with their ability to load financial data. • No products in terms of preset end user driven data and mapping

workflow.Licensing / Other• FDM does require licensing.• FDM was originally UpStream WebLink and acquired by Hyperion in 2006.


g y p q y yp

Oracle Data Integrator (ODI)g ( )

• ODI is an integration tool that can load financial data and application metadata into different target systems.

• ODI has the flexibility to design its workflow through a graphical workflow navigation interface. As a result, the product does not impose a workflow on you in the beginning.

• ODI has strong source connection abilities as well as the ability to launch and control jobs or calculations (calling a stored procedure that moves data from one table to another).

h ‘ l d d l ’ h h b l kfl• ODI has ‘Knowledge Modules’ that have pre‐built workflow for certain systems.

• ODI does not have a robust end user driven mapping table. Th i i t i ll t d i l ti l t bl dThe mapping is typically stored in a relational table and processed through the workflow steps.

• Additionally, unless the ‘Knowledge Module’ contains it, l i d lid ti d t b b ilt


logging and validations need to be built.

Oracle Data Integrator (ODI)Use Case( )

Strengths and Use Case• Ability to load Hyperion metadata and financial data to Essbase, Planning

dand HFM.• IT driven financial data or metadata load processing. • Situations where limited mapping is needed.Li it tiLimitations• ODI does not have a pre‐built web based user interface to map, validate or

load data or metadata.• Validations and logging items will more than likely need to be custom builtValidations and logging items will more than likely need to be custom built

(i.e. log data load errors in a text file).Similarities to Other Integration Products• Most similar to DIM, HAL,• FDM for financial data, though typically a different use (Finance vs. IT)Licensing / Other• ODI does not require a license if used with HFM, Essbase, Planning.


q , , g• ODI was originally Sunopsis and acquired by Oracle.

Data IntegrationManagement (DIM)g ( )

• DIM is conceptually similar to ODI in that it is an integration tool that can load financial data and application metadata to diffdifferent target systems.

• DIM differs from ODI in that it is built on Informatica PowerCenter 8.1. Informatica is one of the leading ETL tools i th k t B t t ODI i lf t i din the market. By contrast ODI is self contained.

• DIM provides ‘adapters’ that can be used in Informatica PowerCenter to connect to HFM, Planning and Essbase.

ll d l d ll l• DIM was originally developed to allow Hyperion clients to leverage existing investments in Informatica.


Data Integration Management(DIM)Use Case( )

Strengths and Use Case• Ability to load Hyperion metadata and financial data to Essbase, Planning

dand HFM.• IT driven financial data or metadata load processing. Very powerful

engine that can process large volumes.LimitationsLimitations• DIM does not have a pre‐built web based user interface to map, validate

or load data or metadata.• Validations and logging items may need to be custom built (i.e. log data gg g y ( g

load errors in a text file).Similarities to Other Integration Products• Most similar to ODI, HAL• FDM for financial data, though typically a different use (Finance vs. IT)Licensing / Other• DIM does require a license if used with Hyperion products.


• Informatica is an independent company not owned by Oracle.

Hyperion ApplicationLink (HAL)( )

• HAL was Hyperion’s tool that provided financial data and metadata load capabilities (similar to ODI and DIM).

• HAL is conceptually similar to ODI and DIM in that it is workflow based and that the workflow is not pre‐built and needs to be set up.

• HAL did have a mapping tool, Translation Manager, to allow for mapping to take place between source and Hyperion targets.

d f d l d b• HAL was an OEM product for Hyperion, developed by Vignette.

• It is currently on Sustaining Support and is set to be di ti d i J 2010 Thi diff f t i idiscontinued in June 2010. This differs from sustaining support in that HAL will be unsupported after June 2010 and Oracle tech support will not take any calls on it.


Enterprise PerformanceManagement Architect (EPMA)g ( )

• EPMA was released in System 9.3.0.• EPMA provides limited financial data functionality. p y• EPMA allows for the ability to manage the metadata

structures / hierarchies for Hyperion target systems (HFM, Planning, Essbase). It has a pre‐built graphical interface to design and manage metadata attributes, and hierarchies.

• Metadata can be loaded into the Hyperion target systems.• EPMA has a Dimension Library to manage the metadata and y g

hierarchies for different dimensions and products.• EPMA has a Data Synchronization feature geared towards

moving data between Hyperion systems. This feature g yp ycurrently has limited mapping functionality (one to one).

• Calculation Manager, a graphical calculation manager released in Fusion 11.x is tied into EPMA.


• EPMA can be deployed on an application by application basis.

Enterprise Performance ManagementArchitect (EPMA)Use Case( )

Strengths and Use Case• Ability to manage Hyperion metadata for HFM, Planning, Essbase in one

i finterface.• Ability to load or push metadata into the different Hyperion target

systems.• Full integrated with Shared Services (roles and external authentication)Full integrated with Shared Services (roles and external authentication).Limitations• EPMA is geared towards Hyperion application metadata only. • EPMA’s data functionality exists but is very limitedEPMAs data functionality exists, but is very limited.• EPMA is web based, so it can be difficult to make mass changes. May have

to make them off‐line and import changes in.Similarities to Other Integration Productsg• DRMLicensing / Other• EPMA does not require a license, it is included with HFM, Planning and


q , , gEssbase licensing.

Data Relationship Management (DRM)g ( )

• DRM is a robust metadata management tool.• DRM does not perform any data processing (source to p y p g (

Hyperion or Hyperion to Hyperion).• DRM allows for the ability to manage the metadata of

Hyperion and non‐Hyperion target systems.• DRM can be used to push metadata ‘downstream’ to source

systems such as general ledger systems or data warehouses. It can also be used to push metadata ‘upstream’ to Hyperion target systems.

• Does have some more advanced metadata functionality such as custom attributes, versioning, and custom export file f ti litfunctionality.

• It allows for the ability to compare across versions, to identify what changes were applied.


Data Integration Management(DIM)Use Case( )

Strengths and Use Case• Most robust metadata management tool for Oracle Hyperion.• Ability to manage and deploy metadata to both Hyperion systems and

non‐Hyperion systems. • Use case versus EPMA is whether metadata management is to extend

beyond just the Hyperion applicationsbeyond just the Hyperion applications. Limitations• DRM does not perform any data processing.• DRM is client basedDRM is client based.Similarities to Other Integration Products• EPMALicensing / OtherLicensing / Other• DRM does require a license. • DRM was formerly MDM.• MDMwas originally developed by Raaza and purchased by Hyperion.


MDM was originally developed by Raaza and purchased by Hyperion.

ERP Integrator (ERPi)g ( )

• ERPi is a new product that was released in 11.1.1.3.• It provides a framework and structure of connections to p

source systems such as Oracle E‐Business Suite, to be used to move data / metadata into FDM, ODI and / or EPMA. It currently has adapters for Oracle E‐Business Suite and P l S ft E t i GLPeopleSoft Enterprise GL.

• ERPi has its own relational ‘staging’ tables for the processing. Data / metadata can be moved from the source system into ERPi and then processed into the correct tool based on theERPi and then processed into the correct tool based on the specific use case.

• ERPi will help simplify source system connections among the various Oracle Hyperion integration productsvarious Oracle Hyperion integration products.


ERP Integrator(ERPi)Use Case( )

Strengths and Use Case• Source adapter connections for Oracle E‐Business Suite and PeopleSoft

iEnterprise GL.• Ability to manage source connections and pull metadata / data – to then

be distributed to the appropriate Integration product.• Provides drill‐back to source systemsProvides drill back to source systems.Limitations• Currently no ability to connect to data warehouses, SAP, etc. • New product limited usageNew product, limited usageSimilarities to Other Integration Products• Unique for managing the different tools and drill‐back capability.• Similarities to FDM if data processing ODI for metadata onlySimilarities to FDM if data processing, ODI for metadata only.Licensing / Other• ERPi does require a license, it is licensed through FDM.


Classic Metadata Approachespp

• Many Hyperion tools allow for metadata to be built or loaded directly into them.

• HFM has a Metadata Manager for maintaining the HFM metadata.

• Hyperion Planning has a Dimension Manager tool in Planning web for maintaining metadata.

• Essbase has a console for maintaining metadata.• These tools allow for the creation and maintenance of

metadata, but are on an application by application basis.


Classic MetadataUse Case

Strengths and Use Case• Does not require any additional products to be installed.• Depending on system, can be more robust than other tools.Limitations• Limited to performing metadata in different tools for different Hyperion

li iapplications.• Limited to performing metadata within a tool on an application by

application basis. • Limited versioning and audit capabilitiesLimited versioning and audit capabilities.Similarities to Other Integration Products• Similar to DRM / EPMA in the ability to manage metadata attributes and

hierarchies and ability to load metadata in the application.y ppLicensing / Other• All classic metadata tools are included in the base product licensing.




Overview of Use CaseOverview of Use Case


Data Use Case Example 1p

Example Use Case• Company has 25 different ledger systems and is deploying HFM. They

d l h l h h h f ineed a tool to help them map the Chart of Accounts into HFM.

Product OptionsFDM ODI DIM f d i• FDM, ODI, DIM for data processing

Considerations• FDM is the best fit here because mapping will be needed and end users

will need a user friendly tool to load and validate their financial data into HFM.

• ODI and DIM are not as good of fits as they do not have pre‐builtODI and DIM are not as good of fits as they do not have pre built validations, load workflow and mapping interfaces.



Example Use Case• Company has one main ledger systems that will be loading data to HFM

d i l i h d i l i li iand Hyperion Planning. The HFM and Hyperion Planning applications are designed off of the GL chart of accounts, thus no mapping is needed. Company wants to focus on speed of movement between applications.

Product Options• FDM, ODI and DIM• ERPiConsiderations• Since no mapping is needed, FDM is not as clear of a fit. • Questions will center on whether FDM’s pre‐built logging and validation p gg g

functionality can add value over ODI / DIM. Volume size may be a consideration as well due to it coming from one main ledger.

• Depending on the source system, ERPi may provide a benefit to directly connect to the source system and to manage drill back.


connect to the source system and to manage drill back.


Example Use Case• Company has a Hyperion Planning application that contains Department

b d d f i f i l i li i hbudget and forecast information. It also contains an HFM application that contains legal entity members. Once the budget and forecasts are complete in Hyperion Planning, the data will need to be moved from Hyperion Planning into HFM, as HFM will remain the final book of records f lid d A l B d d F i f ifor consolidated Actual, Budget and Forecast information.

Product Options• FDM, ODI, DIM and EPMA

dConsiderations• What type of mapping or transformation needs to take place between

Hyperion Planning and HFM? – EPMA DIM and ODI are limited in their mapping If more mapping functionality isEPMA, DIM and ODI are limited in their mapping. If more mapping functionality is

needed, FDM may be a better fit.

• Will the integration tool perform any validations between Planning and HFM?

• Is FDM already licensed? If not is licensing an issue?


• Is FDM already licensed? If not, is licensing an issue?

Metadata Use Case Example 1p

Example Use Case• Company has a single HFM application. They need to make metadata

h f d i i h h i h i li ichanges for new accounts and entities each month in their application. Their HFM application is at a consolidated chart of accounts and different than other systems.

Product OptionsProduct Options• Classic methods, EPMA, DRMConsiderations• A tool is needed to manage the hierarchies and members so ODI and DIMA tool is needed to manage the hierarchies and members, so ODI and DIM

are not viable.• Since the chart of accounts is different and this company only needs to

manage one hierarchy, DRM does not appear to be a great fit.I h d i h C l l i M i h F i 11 ? If• Is there a desire to use the Calculation Manager with Fusion 11.x? If so, EPMA would be the only option.

• If metadata updates are not too consuming, classic may be easiest.


Metadata Use Case Example 2p

Example Use Case• Company has multiple HFM applications along with Hyperion Planning.

h i i b h i d l iThere is some consistency between the primary HFM and Planning applications, but Planning extends the Entity and Chart of Accounts. The company is currently using the classic methods to manage their metadata. The chart of accounts in all products differs from what is in the source systems.

Product Options• Classic methods, EPMA, DRM

dConsiderations• A tool is needed to manage the hierarchies and members, so ODI and DIM

are not viable.• Since multiple products are being used DRM and EPMA are stronger• Since multiple products are being used, DRM and EPMA are stronger

considerations. For DRM – since no source system integration will be performed, the focus would be whether its more robust functionality is worth the license cost over EPMA.


MixedUse Case Examplep

Example Use Case• A company has one HFM application where they are currently using FDM

f h l d f h i l d h i i l ifor the load of three main ledgers. The company is implementing Hyperion Planning for one of their main ledgers. Planning is based on the ledger chart of accounts. Planning data will need to be migrated into HFM following the completion. The company does not own Informatica.

Product Options• Data – FDM, ODI, DIM, ERPi• Metadata – ODI, DIM, ERPiConsiderations• Since FDM is licensed, it can be used for loading data to Planning (Actuals)

and then from Planning to HFM as validations can be used in FDM. Si h Pl i li i ill b b il ff f h l d h f• Since the Planning application will be built off of the ledger chart of accounts, a tool can be used to build the hierarchies off of the ledger. Since the company does not own Informatica, ODI would be the better choice if licensing is an issue.


• ERPi may be an option if the GL is supported.

Finit ContactsEffi i tl D li i Eff ti S l tiEfficiently Delivering Effective Solutions

Thank You!Rob Cybulski Finit Solutions

[email protected]‐880‐2025


hyperion integration- odi fdm hal

Documents