Oracle Hyperion Financial Close Suite Tips and Tricks

Tips and Tricks Oracle Hyperion Financial Close Suite

Chris BarbieriVice President

September 2014

Copyright © 2014 Edgewater RanzalCopyright © 2014 Edgewater Ranzal

Focus

Services

People

Methodology

Customers

Partnership

15 Years

700+ clients

1000+ projects


Dashboards & Scorecards, Financial Analytics &

Reporting, Operational Analytics, What-if

Analysis, Query & Reporting, Visual ExplorationFinancial performance, Legal,

Segment & Mgmt Reporting, Financial Close

HFM Optimization, Performance Lab

SOX Compliance SupportStrategic 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

Business

Intelligence

Enterprise

Planning

Infrastructure

Training &

Support Services

Project

Management

Data

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


► 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


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.

► Retains audit trail directly back to source ledgers

Store only General Ledger values here.

FDM re-loads will only clear this member.

Forms and Smart View use this for supplemental data.

FDM re-loads will preserve this (FDM Data Protection).

HFM performs intercompany eliminations automatically. You can see values

pre- and post- elimination at all entity levels.

HFM performs intercompany eliminations automatically. You can see values

pre- and post- elimination at all entity levels.

Allocations can be calculated in HFM. Separate each to see incremental

effects.

Track discontinued operation “projects” separately through journal entries.

Add adjustment categories as you need.

Use adjustment “buckets” to move between GAAP and Non-GAAP

Bridge between GAAPs by using adjustment “buckets”.


► <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>

<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


NoData NoData

NoData

ABC = 10

DEF = 2NoData

ABC = 10

DEF = 2

Ratio = NoDataABC = 10

DEF = 2NoData

ABC = 10

DEF = 2

Ratio = 5

Load ABC and DEF

Consolidate


ABC = 10

DEF = 2DEF = 6

ABC = 10

DEF = 8

Ratio = 5 ABC = 10

DEF = 2DEF = 6

ABC = 10

DEF = 8

Ratio = 1.25

Consolidate

Force it:Consolidate All With DataABC = 10

DEF = 2DEF = 6

ABC = 10

DEF = 8

Ratio = 5


► Change the target POV status to impacted (yellow)


► 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!


CH

CH CH

December 2014

NoData

NoData NoData

January 2015

Load and adjust

December


OK

OK OK

December 2014 January 2015

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


OK

OK OK

OK

OK OK

December 2014 January 2015

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


► 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


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


► Object naming schemes

– Variables

– Rule Sets

► Rule Objects

– Descriptions

– Captions

– Comments

Prefix Purpose Example

s String sPOVEntity

b Boolean bIsBaseEntity

i Integer iPOVPeriod

f Floating Point fData


Chris [email protected]

Needham, MA

USA

+1.617.480.6173

www.ranzal.com