Finit solutions getting the most out of integration

The Finit Solutions Series
Getting the Most out of
Integration: Understanding the
various Oracle EPM Integration
ProductsProducts
January 20 2010January 20, 2010
Presented by Rob Cybulski
www.finitsolutions.com

About Finit Solutions

Th Fi it S l ti S i
Integration: Understanding the Various Oracle EPM Products
Finit Introduction The Finit Solutions Series
Finit Solutions specializes in consulting services in the Oracle Hyperion Enterprise
Performance Management Solutions suite of products:
Financial Consolidation and Reporting
– Financial Management (HFM)
– Hyperion EnterpriseHyperion Enterprise
– BI+ Reporting Tools
Integration
– Financial Data Quality Management (FDM), ERP Integrator (ERPi)
– Oracle Data Integrator (ODI)
– Data Integration Management (DIM)
– EPM Architect (EPMA)
Planning and Business Intelligence
– Planning
‐ 3 ‐
a g
– Essbase

Th Fi it S l ti S i
Finit’s Integration Expertise The Finit Solutions Series
•Finit has a long history with data integration products, having worked
with Hyperion LedgerLink and Hyperion Enterprise conversion tables
g p
yp g yp p
since the early 1990’s and then becoming UpStream Software’s first
consulting partner in 2002.  Collectively, Finit has designed and
implemented data integration solutions that have sourced data fromimplemented data integration solutions that have sourced data from
over 4,800 source systems and are used by over 5,000 end users.
• Our combined expertise in Hyperion integration products, as well as
our accounting and finance‐based backgrounds, enable us to offer
complete designs that include strong data quality and validationcomplete designs that include strong data quality and validation
checks.  This blend of IT and Finance experience lets Finit consultants
work with clients to address the requirements of both the IT and
‐ 4 ‐
Finance teams in order to deliver a complete solution.

Th Fi it S l ti S i
Finit’s Client Service The Finit Solutions Series
W t k li t i i lWe take client service very seriously.
Our methodology of efficiently developing effective
solutions and exceeding expectations on every
project has resulted in a 100% client satisfaction rate
at more than 100 clients.
‐ 5 ‐

Th Fi it S l ti S i
Some Finit Clients The Finit Solutions Series
•
‐ 6 ‐

Th Fi it S l ti S i
About the Presenter The Finit Solutions Series
Rob Cybulski
(rcybulski@finitsolutions.com)
• Co‐Founder of Finit Solutions
• More than 10 years of experience• More than 10 years of experience
with the Hyperion suite
• Frequent presenter at Hyperion
fconferences
• Serves as the Hyperion Enterprise
and HFM Domain Lead for
h O l H i S i lthe Oracle Hyperion Special
Interest Group
‐ 7 ‐

Th Fi it S l ti S i
How to Ask a Question The Finit Solutions Series
Q
‐ 8 ‐

Purpose of the Webinar

Th Fi it S l ti S i
Purpose of this Session The Finit Solutions Series
• Provide an introduction and overview to all of the products that
are included in Oracle’s EPM integration product suite.
p
g p
• By integration we mean the tools that have data (financial and
other) and metadata functionality that integrate with target
li ti (HFM Pl i E b t ) b i l diapplications (HFM, Planning, Essbase, etc) by managing or loading
data / metadata information into them.
– Integration products help you get data / metadata into a target application
• Provide functionality details for each product related to data and
metadata.
Gi id H i d t th t f i il• Give guidance on Hyperion products that perform similar
functionality.
• Go through different use case examples to discuss integration tool
‐ 10 ‐
g p g
options.

Th Fi it S l ti S i
Overview of Part I Session The Finit Solutions Series
To obtain a link to this session recording, or to
receive the presentation slides please email us at:receive the presentation slides, please email us at:
insights@finitsolutions.com
‐ 11 ‐

Efficiently Delivering Effective Solutions
Oracle EPM Integration
Products
Overview of the Oracle EPM integrationOverview of the Oracle EPM integration
suite

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
p
Management Architect
(EPMA)
Data Relationship
Management (DRM)
ERP Integrator (ERPi) ‘Classic’ Metadata Tools
‐ 13 ‐

Management (FDM)g ( )
• FDM is a web based financial data tool that is used to
load, map and validate source system financial data , p y
into a target application.
• FDM has a pre‐built data load workflow that walks
through the different load steps (Import Validatethrough the different load steps (Import, Validate,
Export, Check). This workflow is the same for each
user and source system, though the data, format of
the source files and mapping may be differentthe source files and mapping may be different.
• FDM has a user‐friendly interface that allows users to
maintain their source system to target system y g y
mapping tables and load their data. The mapping
interface is pre‐built and requires no customization.
‐ 14 ‐

Management (FDM) Cont.g ( )
• FDM has pre‐built financial features such as an
‘audit‐trail’ and archive and logging capabilities.gg g p
• FDM can source financial and other data either by
directly connecting to source systems (through FDM
source adapters or via Integration scripts) or bysource adapters or via Integration scripts) or by
reading source system files.
• FDM has Hyperion target adapters for Hyperion
l / b dEnterprise, HFM, Planning / Essbase and Hyperion
Strategic Finance. It has non‐Hyperion adapters such
as the data mart and tax extract adapters. p
• FDM can be enhanced through VB script
customization.
‐ 15 ‐

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 and other 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).
• FDM is not as efficient with very large file volumes (millions of records)FDM is not as efficient with very large file volumes (millions of records).
Similarities to Other Integration Products
• ODI and DIM with their ability to load financial and other data.
• No similarities in terms of preset end user‐driven data and mappingNo similarities in terms of preset end user driven data and mapping
workflow.
Licensing / Other
• FDM does require licensing.
‐ 16 ‐
q g
• FDM was originally UpStream WebLink and acquired by Hyperion in 2006.

Oracle Data
Integrator (ODI)g ( )
• ODI is an integration tool that can load financial and
other data and application metadata into different pp
target systems.
• ODI has the flexibility to design its workflow through
a graphical workflow navigation interface As aa graphical workflow navigation interface.  As a
result, the product does not impose a workflow on
you in the beginning.
h ‘ l d d l ’ h h b l• ODI has ‘Knowledge Modules’ that have pre‐built
workflows for certain processes and systems.
• Additionally, unless the ‘Knowledge Module’ containsAdditionally, unless the Knowledge Module contains
them, logging and validations need to be built.  A
workflow needs to be set up for any item that is not
contained in a pre‐defined ‘Knowledge Module’
‐ 17 ‐
contained in a pre defined Knowledge Module .

Oracle Data
Integrator (ODI) Cont.g ( )
• ODI has strong source connection abilities as well as
the ability to launch and control jobs or calculations y j
(calling a stored procedure that moves data from one
table to another).
• ODI has adapters for Planning Essbase and HFM• ODI has adapters for Planning, Essbase and HFM.
• ODI has ‘Knowledge Modules’ for connectivity to
relational databases (SQL Server, Oracle DB, IBM
) ll ( lDB2, etc) as well as source systems (Oracle E‐
Business Suite, Siebel CRM, PeopleSoft and JDE).
• ODI does not have a robust end user‐driven mappingODI does not have a robust end user driven mapping
table. The mapping is typically stored in a relational
table and processed through the workflow steps.
‐ 18 ‐

Oracle Data Integrator
(ODI)Use Case( )
• Ability to load Hyperion metadata and financial and other data to Essbase,
l i dPlanning and HFM.
• IT driven financial data or metadata load processing.
• Situations where limited mapping or IT controlled 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).
• 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 Essbase, Planning, or HFM.
‐ 19 ‐
q , g,
• ODI was originally Sunopsis and acquired by Oracle.

Data Integration
Management (DIM)g ( )
• DIM is conceptually similar to ODI in that it is an
integration tool that can load financial and other g
data and metadata to different target systems.
• DIM differs from ODI in that it is built on Informatica
PowerCenter 8 1 Informatica PowerCenter is thePowerCenter 8.1. Informatica PowerCenter is the
engine with adapters that connect to the Hyperion
target systems.
f f h l d l h• Informatica is one of the leading ETL tools on the
market but it is not owned by Oracle. By contrast ODI
is fully owned (core engine and adapter layer).y ( g p y )
• DIM provides ‘adapters’ that can be used in
Informatica PowerCenter to connect to HFM,
Planning Essbase HE Performance Scorecard and
‐ 20 ‐
Planning, Essbase, HE, Performance Scorecard, and
Translation Manager.

Data Integration
Management (DIM) Cont.g ( )
• DIM was originally developed to allow Hyperion
clients to leverage existing investments in g g
Informatica. This allows companies who have
existing deployments of Informatica PowerCenter for
other purposes to continue to use that engine as aother purposes to continue to use that engine as a
tool for Hyperion integration without having to invest
in a new tool (ODI, FDM, etc).
• Long Term support of DIM is a little unclear• Long‐Term support of DIM is a little unclear.
Officially it is supported by Oracle, however DIM
product information cannot be easily found on
O l ’ b it d it t i l d d i thOracle’s website and it was not included in the
development of ERPi (ODI, EPMA and FDM were).
• It is recommended to speak to Oracle regarding
‐ 21 ‐
p g g
future product direction on DIM if interested.

Data Integration Management
(DIM)Use Case( )
• Ability to load Hyperion metadata and financial and other data to Essbase,
l i dPlanning and HFM.
• IT driven data or metadata load processing. Very powerful engine that can
process large volumes of data.
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).
• 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.
‐ 22 ‐
• Informatica is an independent company not owned by Oracle.

Hyperion Application
Link (HAL)( )
• HAL was Hyperion’s tool that provided financial and other
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 but
rather 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.
• HAL is currently on Sustaining Support and is set to be
di ti d i J 2010 t hi h i t th d t ill bdiscontinued in June 2010, at which point the product will be
unsupported and Oracle tech support will not take any calls
on it.
‐ 23 ‐

Management Architect (EPMA)g ( )
• EPMA was released in Hyperion System 9.3.0. (as
BPMA, Business Performance Management , g
Architect).
• EPMA provides limited financial data functionality.
EPMA h D t S h i ti f t d• EPMA has a Data Synchronization feature geared
towards moving data between Hyperion systems.
This feature currently has limited mapping (one to
) d f lone) and set up functionality.
• EPMA allows for the ability to manage the metadata
structures / hierarchies for Hyperion target systemsstructures / hierarchies for Hyperion target systems
(HFM, Planning, Essbase, Profitability & Cost Mgmt).
It has a pre‐built graphical interface to design and
manage metadata attributes and hierarchies
‐ 24 ‐
manage metadata attributes and hierarchies.

Management Architect (EPMA) Cont.g ( )
• EPMA has a Dimension Library to manage the
metadata and hierarchies for different dimensions
and products.
• Metadata can be pushed and loaded into the
Hyperion target systemsHyperion target systems.
• EPMA can be deployed on an application by
application basis. As a result, you can install it and
d l l h d l lldeploy one application without deploying all
applications.
• Calculation Manager, a graphical calculation managerCalculation Manager, a graphical calculation manager
released in Fusion 11.x, is tied into EPMA. In release
11.1.1.3 they can be run independently, but
Calculation Manager requires EPMA to be installed
‐ 25 ‐
Calculation Manager requires EPMA to be installed.

Enterprise Performance Management
Architect (EPMA)Use Case( )
• Ability to manage Hyperion metadata for HFM, Planning, and Essbase in
i fone interface.
• Ability to load or push metadata into the different Hyperion target
systems.
• Fully integrated with Shared Services (roles and external authentication)Fully 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 limitedEPMA s 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.
Similarities to Other Integration Productsg
• DRM
Licensing / Other
• EPMA does not require a license; it is included with HFM, Planning and
‐ 26 ‐
q ; , g
Essbase licensing.

Data Relationship
Management (DRM)g ( )
• DRM is a robust metadata management tool that
allows metadata properties and the hierarchy of p p y
metadata rollups to be managed.
• DRM allows for the ability to manage the metadata
of Hyperion and non Hyperion target systemsof Hyperion and non‐Hyperion target systems.
• DRM can be used to push metadata ‘downstream’ to
source systems such as general ledger systems or
d h l b d hdata warehouses.  It can also be used to push
metadata ‘upstream’ to Hyperion target systems.
This means that DRM can be used to manage all g
metadata for multiple Hyperion products (i.e. HFM
and Planning) as well as source systems (data
warehouse, SAP, Oracle E‐Business Suite).
‐ 27 ‐
, , )

Data Relationship
Management (DRM) Cont.g ( )
• Has more advanced metadata functionality such as
custom attributes, versioning, and custom export file , g, p
functionality.  Additionally, it has ‘rollback’
functionality to roll back to a point in time.
• DRM allows for the ability to compare across• DRM allows for the ability to compare across
versions to identify what changes were applied.
• You can build more extensive validations inside of
h h lDRM than you can in EPMA or other tools.
• DRM does not perform any data processing (source
to Hyperion or Hyperion to Hyperion). It is strictly ato Hyperion or Hyperion to Hyperion).  It is strictly a
metadata management and metadata loading tool.
‐ 28 ‐

Data Relationship
Management (DRM) Cont.g ( )
• 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.
• EPMA
Licensing / OtherLicensing / Other
• DRM does require a license.
• DRM was formerly Master Data Management (MDM).
• MDM was originally developed by Raaza and purchased by Hyperion.
‐ 29 ‐
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 connectionsIt provides a framework and structure of connections
to 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/ or EPMA. It currently has adapters for Oracle E‐
Business Suite and PeopleSoft Enterprise GL.
• ERPi has its own relational ‘staging’ tables for the
/ d b d f hprocessing. Data / metadata can be moved from the
source system into ERPi and then processed into the
correct tool based on the specific use case.p
• ERPi will help simplify source system connections
among the various Oracle Hyperion integration
products
‐ 30 ‐
products.

ERP Integrator
(ERPi)Use Case( )
• Source adapter connections for Oracle E‐Business Suite and PeopleSoft
iEnterprise GL.
• Ability to manage source connections and pull metadata or 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 usage in production currentlyNew product, limited usage in production currently.
• 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. If you own FDM,
you are licensed for ERPi.
‐ 31 ‐
y

Classic Metadata Approachespp
• Many Hyperion tools allow for metadata to be built
or loaded directly into them. y
• HFM has a Metadata Manager for maintaining the
HFM metadata.
H i Pl i h Di i M t l i• Hyperion Planning has a Dimension Manager tool in
the Planning web interface for maintaining metadata.
• Essbase has a console for maintaining metadata g
through Essbase build rules.
• These tools allow for the creation and maintenance
of metadata but are on an application by applicationof metadata, but are on an application by application
basis.
• Additionally, Planning in release 11.x has a command
‐ 32 ‐
prompt for metadata load capabilities.

Classic Metadata
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.
• Most classic modes are client based (Planning is an exception).
• Similar to DRM / EPMA in the ability to manage metadata attributes andSimilar to DRM / EPMA in the ability to manage metadata attributes and
hierarchies and ability to load metadata in the application.
Licensing / Other
• All classic metadata tools are included in the base product licensing.
‐ 33 ‐
p g

Efficiently Delivering Effective Solutions
Oracle Hyperion Integration
Products
Overview of Integration Use CasesOverview of Integration Use Cases

Data
Use Case Example 1p
Example Use Case
• Company has 25 different ledger systems and is deploying HFM.  They
d l h l h d f h h i l l h fneed a tool to help the end users of each system map their local Chart of
Accounts of each source system into HFM.
Product OptionsProduct Options
• FDM, ODI, DIM for data processing capabilities.
ConsiderationsConsiderations
• 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‐built
validations, load workflow and mapping interfaces.
‐ 35 ‐

Data
Use Case Example 2p
Example Use Case
• Company has one main ledger system 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 little to no mapping is
needed.  Company wants to focus on speed of movement between
applications and large volumes are expected.
Product Options
• FDM, ODI, DIM, ERPi
Considerations
• Since little to no mapping is needed, FDM is not as clear of a fit.
• Will metadata loading be included in the integration?
• Will FDM’s pre‐built logging and validation functionality add value over
ODI / DIM? V l i b id iODI / DIM?  Volume size may be a consideration.
• Is IT using ODI or Informatica (DIM) for other solutions?
• Depending on the source system, ERPi may provide a benefit to directly
connect to the source system and to manage drill back.
‐ 36 ‐
connect to the source system and to manage drill back.

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.
• Classic methods, EPMA, DRM
Considerations
• 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 as they are used to source from a system.
• 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 needs to be installed (but not deployed if 11.1.1.3).
• If metadata updates are not too time‐consuming, classic may be easiest.
‐ 37 ‐

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.
‐ 38 ‐

Mixed
Use Case Example 1p
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
ledger #1’s chart of accounts.  Planning data will need to be migrated into
HFM.  The company does not own Informatica.
Product Options
• Data – FDM, ODI, DIM, ERPi
• Metadata – ODI, DIM, ERPi, DRM, EPMA
Considerations
• 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 hierarchy management tool (DRM / EPMA) is not needed since
it will be pulled from the source system. Since the company does not own
Informatica, ODI would be the better choice if licensing cost is an issue.
‐ 39 ‐
• ERPi may be an option if the GL is supported.

Mixed
Use Case Example 2p
Example Use Case
• A company has one predominant ledger and a handful of small ledgers. They currently have
multiple HFM applications and the smaller ledgers use FDM to load their data. They also use
Essbase for management reporting. They need to implement a new way to load the main
ledger data to HFM and Essbase as HAL is used. The majority of the metadata for HFM and
Essbase is sourced from the main ledger but not completely. The main ledger is not currently
d bsupported by ERPi.
Product Options
• Data – FDM, ODI, DIM
• Metadata ODI DIM DRM EPMA• Metadata – ODI, DIM, DRM, EPMA
Considerations
• FDM is currently licensed for the small ledgers, so it can be used for loading data to both
HFM and Essbase for the main ledger data. The volume of data needs to be considered
though as DIM and ODI were designed to handle larger volumes.
• The complexity of mapping with the main ledger will help dictate FDM vs. ODI / DIM.
• The HFM and Essbase applications will be built off of the main ledger chart of accounts as a
starting point and have the additional data added Therefore a hierarchy management tool
‐ 40 ‐
starting point and have the additional data added. Therefore a hierarchy management tool
(DRM / EPMA) is needed.

Mixed
Use Case Example 3p
Example Use Case
• Company has HFM with about 30 locations using FDM to map and load their GL
data. They also have Essbase and use it for Operating Expense detail with the data
being loaded via excel spreadsheets. The CoA’s in both applications are unique and
they are maintaining the metadata for both applications using classic methods.
• Classic methods, EPMA, DRM, FDM
Considerations
• A tool is needed to manage the hierarchies and members so ODI and DIM are not• 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. For DRM –
since no source system integration will be performed, the focus is whether itssince no source system integration will be performed, the focus is whether its
additional functionality is worth the license cost over EPMA.
• FDM could be considered for the loading of Essbase as well as HFM. In many cases
it is the same source data that is loaded to both applications so it would make
‐ 41 ‐
sense to extend FDM’s role in the data loading process.

Mixed
Use Case Example 4p
Example Use Case
• A company has HFM, Planning and FDM. They use FDM to feed data from their
source GL which is wholly EBS (Oracle E‐Business Suite) for the entire
company. Metadata is managed separately in both HFM and Planning via the
Classic methods. The company is re‐organizing to match HFM and Planning’s
metadata to the source systems and they want to streamline the maintenancemetadata to the source systems and they want to streamline the maintenance.
Product Options
• Classic methods, DRM, ERPi
C id iConsiderations
• DRM will be a good fit for metadata management to maintain members and
hierarchy and push them to both EBS and Hyperion.  With this option, FDM would
continue to be used to load data into the applicationscontinue to be used to load data into the applications.
• ERPi could be a fit with or without DRM.  With DRM, ERPi would add the source
adapter support for EBS.  This would facilitate drill‐back to EBS from FDM.
• Without DRM, ERPi can grab metadata properties from EBS and source it through
‐ 42 ‐
Without DRM, ERPi can grab metadata properties from EBS and source it through
ODI or EPMA into the Hyperion applications.

Contact and Future Webinars

Th Fi it S l ti S i
Upcoming Webinars The Finit Solutions Series
Getting the Most out of Oracle Hyperion Planning:
Understanding the Basics
p g
On February 17, you will learn the basics of Planning as we review the features
and benefits of this solution, discuss implementation strategies, and show a
brief demo of the software. This webinar will include discussions of how
Hyperion Planning provides better control over and insight into the budget andHyperion Planning provides better control over and insight into the budget and
forecast process and how it differs from other EPM tools such as HFM and HSF.
Getting the Most out of HFM and FDM:
Upgrading to the Fusion EditionUpgrading to the Fusion Edition
Oracle’s latest major release of the Enterprise Performance Management (EPM)
suite of applications is the Fusion Edition, and it contains a number of important
new features and tools. On March 17, you will learn about the new HFM andnew features and tools. On March 17, you will learn about the new HFM and
FDM features in Fusion Edition, the migration options for upgrading, hardware
and environment considerations for Fusion Edition, and implementation
strategies for the conversion.
‐ 44 ‐
To register, go to www.finitsolutions.com/Insights_Webcast.html

Th Fi it S l ti S i
Finit Contacts The Finit Solutions Series
Q ti ?Questions? Rob Cybulski
rcybulski@finitsolutions.com
215‐880‐2025
Email us for a
215 880 2025
Ed DeLise (VP of Sales)
d li @fi i l i
copy of the slides or
l k h d
edelise@finitsolutions.com
678‐296‐3611
link to the recording. insights@finitsolutions.com
‐ 45 ‐

Finit solutions getting the most out of integration

Recommended

Recommended

More Related Content

Similar to Finit solutions getting the most out of integration

Similar to Finit solutions getting the most out of integration (20)

More from finitsolutions

More from finitsolutions (20)

Recently uploaded

Recently uploaded (20)

Finit solutions getting the most out of integration