Automate DRM/HFM Metadata

Integration Using the New

HFM Java SDK

Session ID: 10455

Prepared by:

Steve Bowden
VP – Integrated Planning Practice Lead
Peloton
These slides represent the work and
opinions of the presenter.

The following material does not

represent the official positions of
Oracle or any other organization.
Overview
Peloton is a recognized leader in Enterprise Performance
Management, Business Analytics and Cloud Solutions…
Long-term client relationships where we consistently deliver
success through:
- Our Business and Technology professionals with proven
track records from the top firms in our industry
- A unique combination of process improvement consulting
and hands-on technical implementation expertise
- Innovative and collaborative implementation methodologies
that drive end-user adoption
About Us
• World-Class Business and Technology Expertise:
 Integrated Planning
 Financial Close & Reporting
 Data and Business Analytics
 Enterprise Infrastructure & Managed Services
 Program & Business Process Management
• Leadership Team of Proven Industry Professionals
• Offices: Boston (HQ), Chicago, NYC, Atlanta, LA
Client Success
• Fortune 1000 and Mid-Market Base of Clients
• 275 + Successful Client Project Implementations
• 98% Client Referrals
• Complete Life Cycle Services

Partnership Approach
• 100% Focused on Oracle

Fast-Growing Private Company

2nd Consecutive Year

3
Agenda

• Why Are We Here?

• Solution Architecture

• Implementation Steps and Code Samples

• Questions?

4
Why Are We Here?
Objectives:
• In order to support a large, multi-pillar Oracle EPM
solutions containing Planning, Essbase, and HFM a
foundational hierarchy management capability has been
established in Data Relationship Manager (DRM)
• Planning and Essbase integration with DRM is simple -
using relational exports, the Outline Load Utility, and
Essbase loadrules
• HFM to DRM integration is not so simple – the traditional
EPMA approach is not a viable solution component for this
environment for several reasons including the need for
latest PFP functionality and the use of ASO plan types

Challenge:
– How do we integrate DRM with HFM, avoid EPMA, and
maintain full automation of metadata updates – and make
it work on both Windows and Exalytics?
Wait, Why Are We Avoiding EPMA?
• Everyone loves EPMA (like DRM’s free little brother)
• It is fine to continue to use EPMA, especially if your focus
is primarily the Oracle Financial Close Suite where EPMA
continues to be a strategic tool with full support
• There are indications EPMA is not strategic for Planning in
the long term (sample from Planning 11.1.2.4 Readme)

• I’m not an Oracle employee, EPMA could become a hot

strategic tool for Planning/Essbase at any time – still better
than many alternatives even with limitations
ANSWER: The New HFM Java SDK

http://docs.oracle.com/cd/E57185_01/epm.1112/hfm_customdev/hfm_customdev.html#_Toc409013153
http://docs.oracle.com/cd/E57185_01/epm.1112/hfm_javadoc/overview-summary.html
HFM Java SDK Implementation Approach

8
DRM/HFM Integration Architecture
Sample of DRM Output Pushed Into HFM

DRM creates a custom export in the format needed for an HFM upload
DRM Integration Process Steps
1. Define columns for DRM export
DRM Integration Process Steps
2. Configure DRM to export flat files in HFM app file format using
customized file headers

3. Develop Java process to login to HFM with encrypted credentials,

read the exported DRM hierarchy file, and push the content to
HFM
Java SDK Approach
• Approach is an derived from the techniques provided
in the sample application from Oracle, located in:
EPM_ORACLE_HOME\products\FinancialManagement\CustomizationSample
Getting Started with the HFM Java SDK

14
Java SDK Solution Process Steps
1. Create a DRM Export that matches the format for a HFM
native export
2. Download Oracle JDeveloper version 11.1.1.7.1
3. Download the Oracle HFM Java Samples from the
Oracle HFM Developer and Customization Site
4. Setup JDeveloper and the sample application as defined
in the guide
5. Create Java routines to load the files as outlined in the
following slides
6. Deploy the Java application to a Jar file for deployment
and execution from any HFM environment.
7. Create a batch file to execute the Jar file and pass the
export file name
 Java Code – Connecting to HFM
• HFM user and encrypted password are passed to the Java Application

• Java application connects to the HFM server and creates a session

Java Code – Uploading Metadata
• The Java application then sets appropriate parameters for the
upload and passes the name of the DRM export file to the API
which is uploaded by HFM.
Script Sample – Calling the Application
• The Java Classes are put into a Jar file and can be ported to any
environment with the HFM components available
• We have used the same Jar file on both Windows and Exalytics
HFM instances
 Questions?

Session ID: 10455

Steve Bowden Thank you!

Vice President
Integrated Planning Practice Lead
sbowden@pelotongroup.com