oracle hyperion planning case study: sourcing consolidated data from hyperion financial management
TRANSCRIPT
Oracle Hyperion Planning Case Study:Sourcing Consolidated Data from
Hyperion Financial Management (HFM)
November, 2012
RJ Linehan, Managing [email protected]
Presentation Agenda
• Introduction• Client Pain Points• Solution Objectives• Solution Architecture• Process/Data Flows• Design Elements• Pitfalls to Avoid• Q&A
Company/Presenter Profile
• Innovus Partners Oracle/Hyperion Enterprise Performance Management Oracle Gold Partner Certified Consultants with average of six years of consulting
experience Based in the New York Tri-State Area Follow us on Twitter, Facebook, and LinkedIn
• RJ Linehan Thirteen years experience consulting in the EPM/BI Space Successfully deployed over 35 EPM/BI solutions Key Industry experience: CPG, Retail, Insurance and Financial Services
Client Pain Points
• Client’s Current Budget Cycle Current Planning Tool
Oracle Hyperion Financial Management (HFM) Lack of functionality for managing planning cycle
Approval Process Planning Task Lists
No standard means for data input Planning Input forms
Lack of modeling capabilities Version Dimension Business Rules
Performance Conflicts Actual Close / Forecast and Budget Cycles
Solution Objectives
• Introduce centrally-managed planning solution for approximately 30 users
• Develop standard process that promotes ease-of-use for user and administrator
• Minimize number of custom Excel models (Phase II)• Introduce modeling capabilities and what-if analysis• Alleviate constraints on performance of HFM Server
Solution Architecture
• Oracle Hyperion Planning• Oracle Hyperion Financial Management (HFM)• Extended Analytics• SQL Server Database Services• SQL Server Integration Services
Separate Subsidiary GL’s
HFM
Subsidiary Budgets
Metadata
Planning Application
Essbase Application
Task FlowEA POV
Metadata changesare “Pushed” from
Planning to Essbase
Manual Changes
Extended Analytics
SSDBSStar Schema
SSISLoad Rule
PeoplSoft GL
Feed to HFM
Process/Data Flows: HFM to Planning
Logical Presentation
Staging Tier – SQL Server Client TierDB App Tier – HFM
HFM Task Flow
Essbase Cube
Sub BudgetHFM Application
SQL DBEPM11_HFM_EA
SSIS Package
Flat File Export
User Action
Process Flow
Data Flow
Trigger File
DB App Tier – Planning/Essbase
Batch Script
VB ScriptWindows Scheduler
Batch Script
MXL Script
Process/Data Flows: Planning to HFM
Logical Presentation
Staging Tier – SQL Server Client TierDB App Tier – HFMDB App Tier – Planning/Essbase
Process Flow
Data Flow
User Action
Trigger File
Batch Script
VB Script
Essbase Cube
SSIS Package
Flat File Export
HFM Application
HFM Load File
Windows Scheduler
Batch Script
MXL Script
Process/Data Flows: Automation
• On-demand Solution HFM Task Flows to export data from HFM Batch file to launch on-demand process File checker via Windows Scheduler VB script launches two batch scripts
Dynamic SQL to remotely execute SSIS PackageMXL script to load to Essbase
HFM Data: Intercompany Transactions and Eliminations
• What are they? Intercompany Transactions
An accounting transaction created from activity between two entities in same company
• Eliminations Offset of Intercompany Transaction via HFM Consolidation
• Pose a consolidation problem in Planning
• HFM dimensions that provide support for intercompany transactions and eliminations: Entity
Source of transaction ICP Attribute defines ICP partners Eliminations occur at first parent with common currency
ICP Target of transaction
Accounts Intercompany accounts are tagged in dimension Plug account - Attached to intercompany account to force accurate offset
Value Dimension (Currency) Entity Currency Elimination Reporting Currency
HFM Data: Intercompany Transactions and Eliminations
HFM Data: Key Shared Dimensions
• Accounts Dimension• Entity Dimension• ICP Dimension• Value Dimension (Currency)• Data Type Dimension• Version Dimension
HFM Data: Key Shared Dimensions
Accounts Dimension
HFM Data: Key Shared Dimensions
Entity Dimension
HFM Data: Key Shared Dimensions
ICP Dimension
HFM Data: Key Shared Dimensions
Value Dimension (Currency)
HFM Data: Key Shared Dimensions
Data Type Dimension
HFM Data: Key Shared Dimensions
Version Dimension
HFM/Planning: DimensionsPlanning Dimensions & Member Selection HFM Dimensions & Member Selection
Dimension Member Selection Dimension Member Selection
Account
@REALTIVE("NetProfit", 0), @RELATIVE("Assets", 0), @RELATIVE("LiabEquity, 0) Accounts
{Assets.[Base]}, {LiabEquity.[Base]}, {NetProfit.[Base]}
C3 No_Custom3 C3 [None]C4 No_Custom4 C4 [None]CF No_CF C2 TotalC2DataType DataPrePlanAdj C1 DataPostAdj PlanInput DataPrePlanAdjEntity @RELATIVE("CONSOL", 0) Entity {CONSOL.[Base]}FiscalYear FY08 FiscalYear 2008
FY09 2009 FY10 2010 FY11 2011ICP @REALTIVE("ICP_TOP", 0) ICP {[ICP TOP].[Base]}Period Jan:Dec Period Jan:DecReportCurrency Base_Entity_Local_Total Entity Currency <Entity Curr Total> Elimination (Value) <Elimination>Scenario Actual Scenario Actual NovFcst NovFcst 10_Budget 10_BudgetVersion Working N/A N/A FROM_HFM N/A N/A Final N/A N/AN/A N/A Periodic Periodic
Sourcing from HFM: Pitfalls to Avoid• POV Mapping (Planning/HFM)
Take time to properly map dimensions• Use ICP Dimension
Assists with defining Entity/ICP relationships in calc scripts• Two Distinct Data Loads to Planning
Working (Planning) Currency conversion in Planning Aggregate Entity, ICP, and Data Type Dimensions
Final (HFM) Currency conversion in HFM, Load to Planning Aggregate ICP and Data Type Dimensions
• HFM Task Flows Properly configure to execute batch script
• Using Extended Analytics Use Standard Format when extracting Report Currency (USD) Extract dynamic accounts from HFM
Oracle Hyperion Planning Integration Strategy:Sourcing Consolidated Data from
Hyperion Financial Management (HFM)
Q&A
RJ Linehan, Managing [email protected]
Oracle Hyperion Planning Case Study:Sourcing Consolidated Data from
Hyperion Financial Management (HFM)
November, 2012