Oracle Hyperion Financial Close Suite Tips and Tricks
6 likes1,730 views
This document outlines strategies and best practices for utilizing Oracle Hyperion Financial Close Suite, focusing on various financial management aspects such as planning, budgeting, and reporting. It provides insights into data management, intercompany eliminations, and the importance of accurate adjustments and reporting formats. Additionally, it highlights the need for proper data handling, object naming schemes, and training for effective use of the software.
Oracle Hyperion Financial Close Suite Tips and Tricks
- 1. Tips and Tricks Oracle Hyperion Financial Close Suite Chris Barbieri Vice President September 2014
- 2. Copyright © 2014 EEddggeewwaatteerr RRaannzzaall Focus Services People Methodology Customers Partnership 15 Years 700+ clients 1000+ projects
- 3. Dashboards & Scorecards, Financial Analytics & Reporting, Operational Analytics, What-if Financial performance, Legal, Analysis, Query & Reporting, Visual Exploration Segment & Mgmt Reporting, Financial Close HFM Optimization, Performance Lab SOX Compliance Support Business Intelligence Project Management Data Services Copyright © 2014 EEddggeewwaatteerr RRaannzzaall Strategic Finance, Planning, Budgeting, Forecasting, Workforce Planning, Capital Planning, Project Financial Planning Data Integration, Financial Data Management, Data Warehousing, Master Data Management &DRM, ETL Services, Automation Project/Program Mgmt, EPM Road Maps, Application Reviews, Business Requirements, Process Change, Documentation Installation, Upgrades, Migration, System Monitoring, Backup and Recovery, Disaster Recovery, Load Testing, Hardware Sizing, Exalytics Benchmarking Consolidation Enterprise Planning Infrastructure Training & Support Services Costing & Profitability Mgmt Support Services – Infrastructure & Application Support Contracts Key Teach Course Delivery: Planning, Essbase, Financial Reporting, Smart View, HPCM, HFM, FDM, DRM, OBIEE Custom Training Delivery: Process & Reporting HPCM Standard & Detailed Models, Waterfall Allocations, Activity Based Costing, Customer, Product & LOB Profitability
- 4. ► Create a “master parent” ► Flag only base entities – IsICP and AllowsAdjs – Use base entities near the parents to capture high level adjustments ► Parent intercompany entities cause two problems – Inconsistency between alternate hierarchies – Intercompany matching report can Translate, but not Consolidate ► ICPTemp – Unidentified partner still eliminates – Easy to see in validation report Copyright © 2014 EEddggeewwaatteerr RRaannzzaall
- 5. ► Retains audit trail directly back to source ledgers Bridge between GAAPs by using adjustment “buckets”. Use adjustment “buckets” to move between GAAP and Non-GAAP Add adjustment categories as you need. Track discontinued operation “projects” separately through journal entries. Allocations can be calculated in HFM. Separate each to see incremental effects. HFM performs intercompany eliminations automatically. You can see values pre- and post- elimination at all entity levels. Top side journal adjustments that don’t fit into the local GL. Post close journal adjustments that should have gone into the GL but went into HFM instead. These reverse out automatically. Forms and Smart View use this for supplemental data. FDM re-loads will preserve this (FDM Data Protection). Store only General Ledger values here. FDM re-loads will only clear this member. Copyright © 2014 EEddggeewwaatteerr RRaannzzaall
- 6. ► <Entity Currency> and <Entity Curr Adjs> are independent ► Changes in one do not “notify” the other ► Both dynamically aggregate to <Entity Curr Total> – But <EC> calculates before <ECA> Copyright © 2014 EEddggeewwaatteerr RRaannzzaall <Entity Currency> <Entity Curr Adjs> <Entity Curr Total> If sPovValue = “<Entity Currency>” Then HS.Exp “A#Ratio = A#ABC.V#<Entity Curr Total> / A#DEF.V#<Entity Curr Total>” End If
- 7. Copyright © 2014 EEddggeewwaatteerr RRaannzzaall NoData NoData NoData ABC = 10 DEF = 2 NoData ABC = 10 DEF = 2 Ratio = NoData ABC = 10 DEF = 2 NoData ABC = 10 DEF = 2 Ratio = 5 Load ABC and DEF Consolidate
- 8. ABC = 10 DEF = 2 DEF = 6 ABC = 10 DEF = 8 Ratio = 5 ABC = 10 Copyright © 2014 EEddggeewwaatteerr RRaannzzaall DEF = 2 DEF = 6 ABC = 10 DEF = 8 Ratio = 1.25 Consolidate Force it: ABC = 10 DEF = 6 DEF = 2 Consolidate All With Data ABC = 10 DEF = 8 Ratio = 5
- 9. ► Change the target POV status to impacted (yellow) Copyright © 2014 EEddggeewwaatteerr RRaannzzaall
- 10. Copyright © 2014 EEddggeewwaatteerr RRaannzzaall ► Roll-forwards – Anytime December changes, “notify” the same entity- Value for January – Don’t run for entities or Value members that had no data in December ► Copy rules – Anytime Actual changes, notify the various Forecast or Restatement scenarios ► You create a dependency/link between the years or scenarios ► Do not use this across entities or value members!
- 11. December 2014 CH CH CH January 2015 Copyright © 2014 EEddggeewwaatteerr RRaannzzaall NoData NoData NoData Load and adjust December
- 12. December 2014 January 2015 OK OK OK Copyright © 2014 EEddggeewwaatteerr RRaannzzaall Consolidate December to impact January CH CH CH If Hs.Period.IsLast = True And Hs.Entity.IsBase = True Then HS.ImpactStatus “P#First.Y#Next” End If
- 13. December 2014 January 2015 Copyright © 2014 EEddggeewwaatteerr RRaannzzaall OK OK OK OK OK OK Consolidate January and pull-forward December If Hs.Period.IsFirst = True And Hs.Entity.IsBase = True Then HS.EXP “A#OpeningBalance = A#EndingBalance.P#Last.Y#Prior” End If
- 14. ► Don’t load zeros!!! – Or calculate… or consolidate them – Leave the cell empty – Or HS.Clear it if you are about to write a zero – Or load “NODATA” ► Determines how HFM interprets the missing zero – Actuals: Year-to-date • Capture prior period adjustments – Budget, Forecast, Plan: Periodic • Expenses and revenue are planned by month ► Reports and Smart View can optionally display a zero Copyright © 2014 EEddggeewwaatteerr RRaannzzaall
- 15. Periodic = no activity this period, bring forward last period Year-To-Date = balance is Zero now, so Periodic negates prior period balance ► Applies to Profit & Loss, cash flow only – Balance sheet accounts do not get carried forward – Periodic amount factors into translation… ► Data entry and journals are independent but should be treated the same Copyright © 2014 EEddggeewwaatteerr RRaannzzaall
- 16. ► Object naming schemes Copyright © 2014 EEddggeewwaatteerr RRaannzzaall – Variables – Rule Sets ► Rule Objects – Descriptions – Captions – Comments Prefix Purpose Example s String sPOVEntity b Boolean bIsBaseEntity i Integer iPOVPeriod f Floating Point fData
- 17. Chris Barbieri cbarbieri@ranzal.com Needham, MA USA +1.617.480.6173 www.ranzal.com Copyright © 2014 EEddggeewwaatteerr RRaannzzaall