Drm Integrations Epma -Ebs - Fdmee 11-13-2013 - Final

DRM INTEGRATIONS 11/13/2013 1

Michigan Oracle User Summit

11/13/2013

Presented to:

Date:

DRM Integrations: EPMA, EBS, and

FDMEE


COMPANY OVERVIEW

Implementation services provider specializing

in Oracle Enterprise Performance Management

(EPM) and Business Intelligence (BI)

technology

Oracle Platinum Partner

Offices in New York, Connecticut, New Jersey,

Michigan, Illinois, Indiana, and Texas

Focus on providing complete solutions

from conceptualization through post-

implementation support

CheckPoint Consulting has

been key to our successful

implementations of HFM,

Planning and Essbase.

Their knowledge of the tools,

work-ethic and management

capabilities are second

to none. I would not trust

my Oracle-Hyperion systems

to anyone else.

— Director, Global Consolidation and Reporting


MISSION

To be the premier Enterprise

Performance Management

and Business Intelligence

consulting firm, specializing

in large, complex, multi-

phase, multi-vendor

implementations.

CheckPoint created a

technical interpretation

of our business needs.

— Director of Finance


AGENDA: BUSINESS PROBLEM

Integrating your master data downstream

Discuss history of DRM, as it relates to integrations

Questions for a solution (The ‘who, what, when, where, and why?’)

You now have standard options from Oracle

Features

Functionality

Technical Solutions

EPMA � HFM, PLN, ESS

EBS

FDMEE


A tool that streamlines master data changes

among complex hierarchical structures

across enterprise systems.

Engages business users as direct

contributors to master data management.

Codifies the knowledge that resides in

experts into automated, repeatable

business rules.

Enables data governance & compliance

across the enterprise by enforcing

standards and controls.

WHAT IS DRM?


Build enterprise-wide consistency in terms and definitions

across systems and stakeholders.

Lower TCO with streamlined master data maintenance.

Create trustworthy insight based on high quality master

data.

Consistent metadata can dramatically reduce

reconciliation time.

Audit and traceability to help comply with rules and

regulations.

BENEFITS OF DRM


11.1.2.3 Release

Data Relationship Governance

• Business User focus

• Workflow models and tasks

• Change and remediation requests

• Governance Work list

• Workflow path and tags

• Alerts and notifications

• Preview inherited/derived props

• Request activity

Business Rules

• Dynamic scripting

• Hierarchy constraints for node properties

Data Integration

• Import from database tables

Security Management

• Workflow node access groups

• Object access groups

Usability

• Job management

Documentation

• Hosted help

• Localized documentation

11.1.2.3 AT A GLANCE


2005 Hyperion acquisition of Razza completed

Product theme: Tool Agnostic

Pro: Flexible

Con: Build your own

Methods

File

Table

Version 11: Oracle buys Hyperion and re-brands MDM as

DRM

Re-engineered code base (Delphi to java)

N-tier to Web

Began the integration trend (MDM product umbrella, and now

EPM, and EBS)

BENEFITS OF DRM


What do I need?

Technology: Build your own …

API Calls – Java, BPEL, BPM, ADF, other?

Other? ETL, ODS/DW? PL/SQL?

People

A TEAM of folks who can handle technologies above, or

more consultants

Or one incredible superstar … single point of failure

How long will it take?

Think months, not weeks ….

Upgrade, Phase II, re-build?

What will it cost ???

WHAT’S INVOLVED?


Today’s version 11.1.2.3 – packaged integrations

EBS

GL: General Ledger

Fusion Accounting Hub

EPM – Legacy Hyperion products

EPMA

�HFM

� PLN

� ESS

Future Enhancements

FDM

Explicit Mappings

Release in conjunction with FDM EE’s v11.1.2.4

LIST OF INTEGRATIONS


Configuration

XML Template (Download, Import)

Target Configuration (EBS)

DRM Web Service API

Complete

No external steps

No external processes, technology

Seamless

Push Button

INTEGRATION COMPONENTS


EPMA INTEGRATION


� Import and share business dimensions in the

Dimension Library

� Build, validate, and deploy applications in the

Application Library

� Design and maintain business rules in

Calculation Manager

� Load and synchronize transaction data into

and between EPM applications

FEATURES OF EPMA


� Oracle Hyperion EPMA Architect can import hierarchies, nodes and

Properties directly from Oracle Hyperion Data Relationship Management

for use by EPM applications.

� The dimensions imported into Performance Management Architect can

then be shared with and deployed to these EPM application types:

� Oracle Hyperion Financial Management

� Oracle Hyperion Planning

� Oracle Essbase

� An application template is loaded into a source Data Relationship

Management application to auto-configure it for managing and exporting

dimensions for Oracle Hyperion EPM architect.

� The application template may be optionally customized to support the specific

business requirements of different organizations.

EPMA INTEGRATION DETAILS


Dimensions – defines the dimensions to be imported

Dimension Associations – contains information about

associations between dimensions (Alias, UDA)

Members – defines dimension members and their

properties

Hierarchies – defines dimension members,

associations and parent/child relationships

Property Array – used to define special hierarchies,

such as Alias and UDA, among others

ADS FILE: COMPONENTS


IM_LOAD_INFO

Contains information about the actual loads into the interface tables such as

when and who did the last updates.

This table does not need to be populated in order to build out dimensions in

EPMA.

IM_DIMENSION– Key table

Dimension name and class such as Accounts, Versions, or Generic.

Other columns form pointers to the user defined tables

New dimension -->add a row specifying this information.

IM_DIMENSION_ASSOCIATION

This table is identical in the columns that feed the Dimensions_Association in

flat files.

Is primarily used to associate attribute dimensions with a base dimension.

INTEGRATION TABLES


Can define any table that will represent a unique dimension.

Default script will create a set of HS tables for each type of dimension.

Significant amount of tables

Examples: HS_Generic_Member, HS_Generic_Hierarchy, etc.

Table Types:

HS_Dimension_Hierarchy – Parent, Child, data storage

HS_Dimension_Member – Member name, Alias, other attributes

HS_Dimension_Property – not required, specific property values for a

dimension

HS_Dimension_PropertyArray – not required, multiple property values for

a member property

FDMEE – new integration

USER DEFINED TABLES


HIGH-LEVEL WORKFLOW


� DRM

� Metadata structures are created in DRM

� Exports are created

� Validations are performed as needed

� Filters are applied as needed

� (Depending on Integration Options)

� API is called

� File is produced

� Table Export is produced

� Scripting & Automation

� EPMA

� Import to EPMA

� Deploy to EPM applications (PLN, ESS, HFM)

� Scripting & Automation

WORKFLOW


XML TemplatePropertiesProperty CategoriesNode TypesExports

Fundamental sectionsParent-ChildChild + Attributes

Validations available

ConfigurationInstallImport XML

Use DRM Migration utility to import

https://[server.domain.com]/drm-migration-client/

Web logic components

CONFIGURATION FOR DRM


Locating and Loading the Application Template� The Enterprise Performance Management application template

(EPMA) is installed as a part of the DRM installation. The template can be used to configure the integration between DRM and EPMA.

� To location the EPMA Template:

� On the machine where DRM is installed, navigate to: � [Install

Drive]:\Oracle\Middleware\EPMSystemR11\products\DataRelationshipManagement\Server\app-templates.

� Note: This is the default installation directory for application templates.

� Locate the template file named: epma-app-template.xml.

CONFIGURATION DETAILS


MIGRATION DETAILS


DOCUMENTATION


PERFORMING THE IMPORT


SUCCESSFUL IMPORT


NEW OBJECTS IN DRM


NEW OPTIONS FOR EPMA


New Export type available

NEW OPTIONS


� Notes

� DRM Applications which have been registered with EPM Shared Services are available for

selection.

� A new option for your import profile is available in workspace, in addition to file and table

� Select the appropriate system export profile based on the target EPMA Application

Type.

� Import Type: “Data Relationship Management”

� Enhancements

� Member instance specification – Primary / Shared

� Placement options in the hierarchy – Top / Bottom

OTHER INTERFACE NOTES


EBS INTEGRATION


Overview

� Oracle Hyperion Data Relationship Management is used to manage charts of

accounts segment values and hierarchies for independent value sets in Oracle

General Ledger.

� Ability to create new segment values, edit their properties, and maintain hierarchies

using the Data Relationship Management web client.

� Synchronized to general ledger instances using a “pull” from DRM

� This integration between Data Relationship Management and Oracle General

Ledger is available for:

� Oracle E-Business Suite Release 12.1

� Oracle Fusion Accounting Hub Release 11g

EBS INTEGRATION


Overview

XML Template

Properties & Property Categories

Exports

Configuration

Pre-requisites

Web Service components


� DRM Traditional elements: Export, Version, Hierarchy, and Target (Staging) tables

� What’s new: Web service API and EBS components:

� Management into Oracle General Ledger using a concurrent request program.

� A concurrent program is an executable file that runs simultaneously with other concurrent programs and

with online operations, fully utilizing your hardware capacity. Typically, a concurrent program is a long-

running, data-intensive task, such as posting a journal or generating a report.

� Standard Request Submission (SRS) is an Oracle E-Business Suite feature that allows you to select and

run your concurrent programs from a single, standard form (Submit Request) or window (Schedule

Request). Requests to run concurrent programs are called concurrent requests.

� The program is available as a concurrent request in Oracle E-Business Suite:

� Load Segment Values and Hierarchies - imports chart of accounts data into EBS

PUSH VS. PULL


� Versions and value sets:

� Each request can load one value set of segment values and hierarchies.

� Read “One Version per Hierarchy”

� The request will only create or update segment values and hierarchies for the chart of

accounts accessible through the user's general ledger data access setting.

� The request also requires that only one Data Relationship Management version is defined

as the master for each value set using the Value Set Master property.

� Other Information: An accompanying report for the Load Segment Values and Hierarchies

request indicates whether the load into Oracle E-Business Suite is successful and provide

summary information.

ADDITIONAL NOTES


A look at the technology involved …

� The Data Relationship Management Web Service Application Programming

Interface (API)

� Public interface for remotely interacting with the Data Relationship

Management Server.

� SOAP-based web service typically user for product integration, could be

used for custom work (i.e. SOA Suite)

� DRM Web Service is implemented in Java and is deployed to the Oracle

Web Logic Application Server as a J2EE Web Application.

� The Web Service communicates with the Data Relationship Management

Server via the API Adapter.

� The DRM Web Service depends on the Oracle Web Services Manager

(OWSM) for policy management and security of service infrastructure.

UNDERSTANDING THE TECHNOLOGY


� Install metadata services schema for Oracle Web Services Manager

� Configure Oracle Web Services Manager

� Configure Web Logic to use Oracle Internet Directory

� Configure the API Adapter Host for Data Relationship Management (Console)

� Deploy the Data Relationship Management Web Service (.ear file)

� Configure security policy for the Data Relationship Management Web Service

� Test the Data Relationship Management Web Service (Test URL)

� Import the XML template objects into DRM

� Exports, Properties, Node Types

� Software and Hardware Requirements (Minimum):

� Oracle Database 11g 11.1.0.7.0

� Oracle Identity Management 11g (11.1.1.4.0)

� Oracle Hyperion Foundation Services 11.1.2.1.0

� Oracle Hyperion Data Relationship Management, Fusion Edition 11.1.2.1.0

API CONFIGURATION


� Where you will typically run into issues …

� Security / Rights / permissions – The right user with the right access

� Providers: MSAD, LDAP, OID, HSS

� Users: NT, DRM, Web Logic, EBS

� EBS staging tables

� DRM Exports (System Objects / Admin Rights)

� Ports - Never open when you need them to be …

� DRM port (multi applications are common)

� Web service / API

� Plan ahead – an ounce of prevention …

� Hosting, third-party, etc.

� Clear communication, expectations, and understanding of deadlines

TYPICAL PAIN POINTS


� There are only 2 target tables involved.

� Essentially there are 2 exports, just like an APP or ADS file.

� GL_DRM_HIERARCHY_INTERFACE - Parent-Child

� GL_DRM_ SEGVALUES_INTERFACE - Child + Attributes

� Resources

� Infrastructure resource required

� DBA

� Web Logic Admin

� EBS resource (Security)

� Hosting?

� Note on documentation, only need these two tables

� http://www.oracle.com/webfolder/technetwork/tutorials/obe/hyp/DR

M11.1.2-WebServicesAPI/index.htm

EBS STAGING TABLES


FDMEE INTEGRATION


• Oracle EBS as the primary GL

• EBS level of detail is available

• Parent-Child relationships are available

HIGH-LEVEL MAPPING


� Leverage Existing Relationships

� Parent-Child relationship

� Attributes: Lookup other hierarchy, based on business logic

� Map Types (FDM)

� Explicit

� General ledger accounts can be converted with one-to-one mapping

� Often times due to timing, complexity, and silos, this is not possible.

� Wildcard mapping (In, Between, or Like).

A NOTE ON MAPPINGS


• Basic Elements of an FDM are going to be captured in DRM.

• Relationship of Parent and child, via the hierarchy will be established.

• We simply need the source and target members.

• Dimension

• Basically the name of the hierarchy

• DimName column in FDM map

• Child Node

• 10111101

• In FDM this is the SrcKey column (Source)

• Parent Node

• Where the child rolls up to in the hierarchy

• Note: Typically this would be the parent. However, it could be a higher

level parent, as well.

• Parent is TargKey (Target)

• Description

• The Node’s description, also know as the alias

• This is the SrcDesc in FDM

SrcKey SrcDesc TargKey

(Child)

10111101CASH OPERATING BANK 1 10111100

MAPPING: SAMPLE


Thank you for attending today’s presentation!

QUESTIONS?

Brian HealeyManaging Consultant

617.680.0091

[email protected]

checkpointllc.com

Visit www.checkpointllc.com/resources to view CheckPoint webinars, download case studies and more!

Documents

Drm Integrations Epma -Ebs - Fdmee 11-13-2013 - Final