beyond oracle epm metadata synchronization
TRANSCRIPT
Beyond Oracle EPM Metadata Synchronization
Conrad ChuangOrchestra Networks
Andrew HelwigUnited Technologies Corporation
Overview: Challenges and options for managing Oracle EPM Metadata
Case Study: How we are using EPM metadata to support our entire shared services Organization
Q&A
Today’s presentation
2
What are we doing at an ODTUG meeting?
3
Customers use our solution to manage their enterprise performance management and corporate finance master/reference data.
Pre-built data models for Oracle® Hyperion EPM
Export dimensions and update to files, staging tables or services
Import dimensions from files, staging tables or
services
End users & EPM administrators maintain
metadata/hierarchies using a browser-based user interface
with built-in workflowImport master data from any system of record
EBX5 for Oracle® Hyperion EPM
Metadata our customers manage
5
Identifiers
Attributes
Hierarchies & Alt Hierarchies
Identifiers, attributes and dimensions for account, entities…
Standard and Alternate Hierarchies
Problems our customers are addressing…
6
Managing a single instance and sync
between other instances
Maintaining past, present, future and what-
if versions?
What-if?
Sharing between different applications
(EPM and non-EPM)?
Manager for Financial Systems in the UTC Center of Excellence.
Principally accountable for the Hyperion Center of Excellence.
Hyperion COE manages all HFM applications in use across UTC globally.
15+ years of experience in Oracle EPM suite
Experience: United Technologies Corporation, Hyperion Solutions (now Oracle).
About Andrew Helwig
How we are using EPM metadata to support our entire shared services Organization
Andrew Helwig,
United Technologies
8
About the United Technologies Corporation
(As of Dec 2014)211,500 Employees
$65.1B Net Sales
9
UTC Corporate Center of Excellence
10
Today we manage 26 production instances of Hyperion Financial Management
Production●(7) Hyperion Financial Management App Servers●(6) WebLogic Servers (SS, SV, WS)●(2) SQL Servers●(26) Production Applications●(1) EBX5 MDM●(4,000) Users
11
Metadata Mgmt
Metadata Mgmt
Hyperion ImplementationsHyperion Implementations
EBX5 manages metadata update process
SikorskySikorsky
Climate, Controls, SecurityClimate, Controls, Security
UTC Aerospace SystemsUTC Aerospace Systems
OtisOtis
Pratt & WhitneyPratt & Whitney
UTC CorporateUTC Corporate
Business Units (BU)
Cha
nges
& U
pdat
es
12
Current new entities business process for HFM
Field request for new
entity(ies)
Field request for new
entity(ies)
New Legal Entity?
New Legal Entity?
BU Controllers provide:•GEMS ID & Inherit Country
BU Controllers provide:•GEMS ID & Inherit Country
BU Tax Review & Approval
BU Tax Review & Approval
NO
Tag to existing LE parent in
LE Hierarchy (or NEW if unknown)
Tag to existing LE parent in
LE Hierarchy (or NEW if unknown)
YES
WHQ Approve
New Entity
WHQ Approve
New Entity
YES
Include new Rainbow fileInclude new Rainbow file
Rainbow FileRainbow File
New entities
added to EBX5
HFM and Tax
Instances
New entities
added to EBX5
HFM and Tax
Instances
Upload to HFM
Upload to HFM
New version required
?
New version required
?
Snapshot old and create new
version (dataspace)
Snapshot old and create new
version (dataspace)
13
CoE Issue: How does the CoE manage metadata across our applications?
Financial Reporting Tax Technology Business Controls
• Consolidation (Hyperion Financial Management)
• Budgeting/Planning (Hyperion Planning)
• Analysis (Oracle Essbase)
• Year End Reporting for leases – eCollect
• Data Integration = FDM (GL to Consolidation)
… and more!
• Tax Filing (CorpTax)
• Tax Provision (LongView)
• Legal Entity Hierarchy (GEMS)
… and more!
• Account Reconciliation (ARMS)
• Sarbanes Oxley Compliance (eSOX)
• Export Controls (CCRS)
… and more!
14
“Tech” Issue: Multiple overlapping instances of Entity across the applications/functions
1,400+ ARMS Entities
1,500+ Tax
Entities700+ SOX
Entities
1,300+Legal
Entities
10,000+ HFM
Entities
3,00+CCRSEntities
4,000+Longview
Tax Entities
Need alignment between entities•Get everyone on the same page
•Build data extracts from HFM to support other applications
•Cut down on inter-application reconciliation
15
Complication (Illustrative): Each application’s entities don’t really represent the same “entity”
HFM
eSOX
CorpTax
Entity is shared with HFM, but has additional attributes
Entity is exclusive to application... but associated with existing HFM Entities:•“Children,” or•“Rollups”
1:1 correspondence between HFM entities
16
Conceptual Example: HFM vs. Business controls
HFM Entity
Netherlands(Consolidated financials)
HFM Entity
Netherlands(Consolidated financials)
eSox – Entity 1
Factory #1
eSox – Entity 1
Factory #1
eSox – Entity 2
Factory #2
eSox – Entity 2
Factory #2
eSox – Entity 3
Factory #3
eSox – Entity 3
Factory #3
For financial reporting purposes the financials for all three factories in the Netherlands are consolidated.
For controls reporting we need to maintain three entities per factory.
But, we want to avoid creating dummy entities in HFM.
17
Business controls needs to maintain consistency with (or synchronize) with HFM hierarchies and members
Allow business controls specific over-rides of dimension attributes and hierarchy changes
Allow business controls specific extensions to HFM
Solution requirements for business controls
18
We used EBX functionality to create “inherited hierarchies” By default all updates to HFM are always accepted in
eSox … … Except when controls create child-only overrides:
● Create/Update/Delete members● Create/Update/Delete hierarchy relationships
How did we address the challenge?
HFM Parent (Dimensions, Hierarchies)
Child – eSox Dimensions + Hierarchies
19
• Control at HFM-level• Maintains synchronization
with controls (other apps)• Filter
New Process File Compare
20
(Right) are extracts from both the Oracle EPM HFM-only and Business Controls (SOX view).
The highlighted rows show SOX-only entities that are supported by the EBX process
HFM-Only Business Controls
Controls attributes are managed via associated extensions in EBX5
21
Managing the SOX extensions separately allows Controls group to manage the SOX only attributes using their own time cycles. We also don’t end up inadvertently sending these attributes to HFM.
Associations with HFM
Controls specific attributes
21
Result: Child Business Controls hierarchies that inherit (and sync) with HFM hierarchies
HFMHFM ControlsControls
22
Child/Inherited hierarchies helps us adjust to different cycle times
23
HFM Team
Controls Team
The HFM team releases a new version every month. The controls team releases a new version every quarter. Inherited hierarchies allows the HFM team and the controls team to maintain independence from one another but keep in sync.
Future state: Management of all entities and entity extensions in EBX
GEMS
CorpTax
Longview
eSOX
ARMS
CCRS
HFM Request
HFM
ESS
BAR
Essbase/Planning
24
Re-using dimensions and attributes eliminates synchronization and (a lot) of reconciliation issues
However enterprise-reuse requires adopting inheritance, alternate hierarchy management techniques and workflow
Version management and workflow is important when coordinating between groups that do not have the same cycle time.
Concluding thoughts & lessons learned
25
Questions and Thank You
Conrad ChuangOrchestra Networks
Andrew HelwigUnited Technologies Corporation
26