Oracle DRM – Classic HFM Integration Process

Oracle Hyperion Financial Management is a financial consolidation and reporting application built with advanced Web technology and designed to be used and maintained by the finance team. It provides financial managers the ability to rapidly consolidate and report financial results, meet global regulatory requirements, reduce the cost of compliance and deliver confidence in the numbers.

Oracle Data Relationship Management is a Master Data Management tool where master data is maintained, analyzed, and validated before moving throughout enterprise. It is the recommended tool of choice for organizing the financial views of financial chart of accounts, cost centers and legal entities that are then used to govern on-going financial management and consolidations for an enterprises.

Some main features of DRM maintaining Master Data than creating in HFM, DRM is compatible in integrating with all the Hyperion and Non-Hyperion Systems like HFM, ESSBASE, PLANNING, Planning and budgeting cloud service (PBCS) and has a roadmap to integrate to all upcoming Oracle Cloud EPM applications. DRM Integrates with both HFM Classic and HFM EPMA.


STEP 1 : Initial Load of metadata into DRM:

When DRM is integrated with HFM for the first time, along with metadata load we also need to create Metadata objects like Property Definitions, Property Categories, Node Types, Validations etc.. These metadata objects can be loaded into DRM using epma-app-template.xml through Migration Utility. Along with this we may also need to create certain custom properties as per business requirement.

STEP 2: Importing Dimensions using Import Profile.

After loading metadata objects through migration utility into DRM ,Create import profiles to import data into DRM. After import profiles create custom properties ,property categories, validations and node types which are used to export data into HFM.


STEP 3:   Exporting Metadata from DRM.

DRM Export in the form of Hierarchy Export is done and then a book of all related export are created by combining all the dimensions containing individual exports into a single file.


STEP 4: DRM Export Automation

DRM Export Process can be automated using DRM-Batch Client

DRM Batch Client is a command line utility that allows access to various arm operations in batch mode including: Actionscript, Import, Blender, Export(Individual Export and Book Export),Opening and closing versions.


STEP 5: Importing Data into HFM Applicaiton.

Once the metadata is exported into a flat file or DB Tables from DRM next step is to import Metadata into HFM Application using Load Task.

Create an Application Profile in the Client of HFM and create an Application on the Workspace. Dimension are loaded in HFM Application using Load Metadata option in Load Task.



This Process of Loading Metadata in HFM application can be automated using Task Automator and then scheduling the task using schedulers in the Workspace.


Leave a Reply

Your email address will not be published. Required fields are marked *