© 2012 Saturn Infotech. All Rights Reserved. Oracle Hyperion Data Relationship Management Presented by: Prasad Bhavsar Saturn Infotech, Inc.

© 2012 Saturn Infotech. All Rights Reserved. What is Master Data? Why it is important to maintain Master Data? What is Hyperion DRM? What does DRM store with respect to Master Data? How to import data into DRM How to export data out of DRM to different target systems DRM VS EPMA Overview & Agenda

© 2012 Saturn Infotech. All Rights Reserved. What are Shared Nodes and when to use them? Transaction Audit Governance using BPEL or BPM Business Rules What can be extracted directly from the DRM database Challenges and Solutions Interesting Implementation Example (DRM and HFM – FDM) Overview & Agenda (Continued)

© 2012 Saturn Infotech. All Rights Reserved. “Master Data is the consistent and uniform set of objects, identifiers, attributes and rules that describe the core (and relatively stable) entities of the enterprise and is used across multiple business processes” Different from Transactional Data and Reference Data Financial and Analytical Master Data Examples: Business Unit, Operating Unit, Product, Customer, Supplier, Employee Master Data

© 2012 Saturn Infotech. All Rights Reserved. Many companies are acquired for its Master Data itself Regulatory compliance, Sarbanes –Oxley Act (SOX), Mergers and Acquisitions make Master Data Management imperative Efficient business relies on quality data - so having the right tool to maintain them is critical Master Data – An Asset

© 2012 Saturn Infotech. All Rights Reserved. Combination of applications and technologies that consolidates, cleans and augments corporate master data and synchronizes it across applications Efficient operations and Consistent Reporting Fast decision making as all reporting applications speak the same language Ensures one version of truth for the master data Master Data Management

© 2012 Saturn Infotech. All Rights Reserved. Manages business entities, hierarchies, attributes, and mappings across multiple systems Validates data relationships and calculates attribute values using business rules Enforces referential integrity across all subscribing systems and hierarchies Enables users to create and manage alternate views Merges independent data sets from different sources and combines them into a master set Oracle Hyperion DRM

© 2012 Saturn Infotech. All Rights Reserved. Maintains historical versions for comparative reporting and analysis Tracks all hierarchy and attribute changes with a full- featured audit log Can serve as the main point-of-entry to update subscribing systems or be used after-the fact for reconciliation and analysis Task Driven web interface in release Oracle Hyperion DRM – Continued…

© 2012 Saturn Infotech. All Rights Reserved. Different methods to import data into Hyperion DRM Automator (Action Script), Imports, API’s, Manual Automator – Generally used for one time loads to single or multiple versions Imports – Generally used for periodic load of same set of data into DRM Import Data into DRM

© 2012 Saturn Infotech. All Rights Reserved. Bulk set of incremental changes Flat files Each row is treated as separate transaction Generally 5 columns for each action in a standard format Ease of use for technical and business users Detailed error debugging Validations and Automator’s performance Automator (Action Script)

© 2012 Saturn Infotech. All Rights Reserved. General Actions - Sample

© 2012 Saturn Infotech. All Rights Reserved. Action Script Interface

© 2012 Saturn Infotech. All Rights Reserved. External System to Script to DRM-Automation /cfgfile=“"C:\Oracle\Data Relationship Management\ActionScriptConfig.txt“ Config File Automator – Batch Script

© 2012 Saturn Infotech. All Rights Reserved. Bulk data generally extracted from other systems into DRM Flat files File divided into mainly five sections –Version –Hierarchy –Node –Relationship –Hierarchy Node Hierarchy and Relationship Imports

© 2012 Saturn Infotech. All Rights Reserved. Flexible Selection of Columns for each section No limit on Number of Columns or data rows Allows leaf node creation, Sorting and Shared node handling Always into a new Version Import – Continued…

© 2012 Saturn Infotech. All Rights Reserved. Sample File

© 2012 Saturn Infotech. All Rights Reserved. Import Interface

© 2012 Saturn Infotech. All Rights Reserved. Import Interface

© 2012 Saturn Infotech. All Rights Reserved. Import Interface

© 2012 Saturn Infotech. All Rights Reserved. Import Interface

© 2012 Saturn Infotech. All Rights Reserved. Import Interface

© 2012 Saturn Infotech. All Rights Reserved. Import – Blend – Delete Import Data into a new version Blend the new version to the master with the hierarchies and properties defined Delete the Imported version Automates the process of periodically importing data in DRM PeopleSoft to DRM using Flat Files

© 2012 Saturn Infotech. All Rights Reserved. Configuration file Automate Import – Blend - Delete

© 2012 Saturn Infotech. All Rights Reserved. Mainly two alternatives –Flat files (Can be placed on network or ftp location) –RDBMS Tables Consistent Master Data can be sent to multiple target systems and applications Information sent as per target system requirements Export Data Out of DRM

© 2012 Saturn Infotech. All Rights Reserved. Hierarchy Exports –Hierarchy, Hierarchy XML, Generational Comparison Exports –Compare and Difference Version Export Property Exports –Property List and Property Lookup Log Exports Export Types and Uses

© 2012 Saturn Infotech. All Rights Reserved. Classic Application - App file sent periodically to HFM, to refresh its metadata HFM Dimensions stored, governed and maintained in DRM DRM book to combine different dimension extracts to one file (App settings, Currency, Scenario, Account, Entity, Custom etc.) DRM to HFM

© 2012 Saturn Infotech. All Rights Reserved. Sample App File Generated of DRM

© 2012 Saturn Infotech. All Rights Reserved. Configuration File Automate Exports

© 2012 Saturn Infotech. All Rights Reserved. DRMEPMA Dimension Library Maintains enterprise master dataEPM application dimensions (Essbase, Planning, HFM) Target IndependentTarget specific Complex and customizable business rules and data validations Static controls Transaction log for every change to master data Application specific deployment logs Granular Node level securityApplication level security VersioningNot Available DRM  EPMA Dimension Library  EPMA Applications DRM vs. EPMA

© 2012 Saturn Infotech. All Rights Reserved. The confusion - Shared Nodes vs. Linked nodes When to use shared nodes in DRM Setting shared node attributes using Action Script Explicit Shared Node vs. Implicit Shared Node Shared limb nodes Using prefix to node vs. using Shared Nodes Alternate Hierarchies and Linked nodes Global vs. Local properties Shared, Linked Nodes & Best Practices

© 2012 Saturn Infotech. All Rights Reserved. DRM Change Approval process Limitations of DRM Change Approval process BPEL (Business Process Execution Language) and BPM (Business Process Management) to manage data governance and workflow Rich interface and functionality DRM – Data Governance

© 2012 Saturn Infotech. All Rights Reserved. Core requirement of Master Data – Business Rules Flow to create a Rule or Validation in DRM –Derived Property –Query –Property Query Validation –Add to Node Type –Assign to Hierarchy Real Time vs. Batch Data validated at input and verified before exporting to target systems Business Rules and Data Validations

© 2012 Saturn Infotech. All Rights Reserved. Never Insert or update any of the tables directly Query the Transaction_History table to get details of specific transactions (User, Action, Time, Hierarchy) How it stores property values? Get list of DRM objects with custom filters Understanding DRM Database Schema

© 2012 Saturn Infotech. All Rights Reserved. Wild Card characters in formula Comparing time in formula Limited functions One Function formulas Data governance/Change Workflow Export formats Maintaining shared nodes Metadata repository for individual systems Generating Delta exports for target systems Limitations and Challenges

© 2012 Saturn Infotech. All Rights Reserved. Use prefix to classify the nodes Use linked nodes in alternate hierarchies Use list values for properties Use Formula whenever possible over defined properties Create validations (real time) as opposed to batch wherever possible Rename backups not the master version Maintain enterprise master data and not applications metadata Best Practices

© 2012 Saturn Infotech. All Rights Reserved. DRM and HFM – FDM Maintain HFM Dimensions and corresponding attributes in DRM Add source Ledger accounts and other keys as child to the corresponding target members Create Hierarchy export for combination of each location and dimension to add data directly to FDM RDBMS (TDATAMAP) table Ensures valid source to target mappings for each HFM dimension and each source location BPEL interface for users to add source to target mappings One point maintenance for HFM metadata and FDM mappings Example

© 2012 Saturn Infotech. All Rights Reserved. FDM – TDATAMAP Table

© 2012 Saturn Infotech. All Rights Reserved. Essential to maintaining enterprise master data Increases business value Implements standard across BI applications and enterprise Makes System and Business talk the same language Follows compliance and regulation Conclusion