Data options with hyperion planning and essbase

www.finitsolutions.com
Data Options with
Hyperion Planning and Essbase
Including Mapping, Loading, Moving and Reporting
August 14, 2015
Cindy Eichner
ceichner@finitsolutions.com

- 2 -
Data Options with Hyperion Planning and Essbase ©2015Data Options with Hyperion Planning and Essbase ©2015
• Founded in 2002
• 75+ employees in 20+ states
– Mostly CPAs, MBAs
– We have extensive Hyperion product and financial reporting
backgrounds
• 50+ Planning / Essbase Clients
• 80+ HFM Clients
– Managed several of the largest EPM projects in the U.S.
– Including the largest roll-out of HFM in North America
• Market Leader in ARM/FCM
• World Leader in FDM implementations and custom
solutions
Finit Overview

- 3 -
EPM Services
• Finit Answers
‒ Technical Support
‒ Functional / Admin
Support
‒ Access to Hyperion
SMEs
‒ Dedicated support team
and guaranteed
response times
‒ Customer Service Focus
‒ Flexible Time and
Material support
packages
‒ ‘Pay as you Go’ option
• Hyperion Planning &
Essbase
• Oracle Financial Close
Suite
• Infrastructure
• Data Services
• Project / Program
Management
• Redesign /
Enhancements
• Product Upgrades
• Application enhancements /
redesign
• Performance optimization
Dedicated
Support
Upgrades
Full Cycle
Implementations

- 4 -
• We make and deliver personalized financial
reporting solutions and experiences.
– By listening, questioning, and analyzing
– By building relationships … not company to company,
but person to person.
– We are Makers and Doers
WHY is Finit Here?

- 5 -
We Run Finit like a Family
• Invest in our employees
• All owners actively involved in
the business
• No debt or external owners
– Prioritize the customer, not profitability
• Long term stability
– Hire employees, not subcontractors
• Compensation model based on
client satisfaction
HOW do we achieve our beliefs?

- 6 -
Our values, on which we ask you to provide
consultant feedback:
Finit Values

- 7 -
Our values, culture, and approach to
becoming a trusted advisor to customers
has led to 100% customer success for
every Finit client (225+) and for every
Oracle Hyperion project (450+)
Finit Customer Success

- 8 -
Some Finit Customers

- 9 -
Questions

- 10 -
• Cindy Eichner
• Director of Finit’s Planning and Essbase
Practice
• Delivering performance management
solutions for over 30 years while
specializing in Hyperion products for over
18 years
• Certified implementation specialist
– Essbase
– Hyperion Planning
– Hyperion Financial Management (HFM)
– Hyperion Data Relationship Management
(DRM)
• Frequent speaker at KScope
About the Presenter

- 11 -
Agenda
• Different Options with Pros and Cons
– “Native” within an application
– Other tools
• Different Options Between Products
• Demonstrations / Examples
• Case Studies / Solutions
• Questions and Answers

- 12 -
• Calc scripts / business rules
– XWRITE
– XREF
– DATAEXPORT
– DATAIMPORTBIN
• Load rules
• Partitions
– Replicated
– Transparent
• Essbase report scripts
“Native” Options Within an Application

- 13 -
• FDM / FDMEE / ODI
• EPMA’s Data synchronization
• Planning’s Map to Reporting Application
• HFM’s EA
• HFM’s EAL
Other Tools

- 14 -
• Design and development
• Complexity
• Administration
• Modifications
• Performance
• Challenges
Pros and Cons

- 15 -
Different Options

- 16 -
Native Options

- 17 -
Calc Scripts / Business Rules
• DATAEXPORT
– FIX … ENDFIX: very specific slices
of data
– Text files
– Relational database table using
ODBC
– Binary
– Many options using SET DATAEXPORTOPTIONS
• DATAIMPORTBIN
– Binary file

- 18 -
• XREF
– May also be used in member formulas
– Uses location aliases
– Best for small amounts of data
– Blocks need to be created
• XWRITE
– Creates blocks
– Uses location aliases
– Best for small amounts of data

- 19 -
• Pros:
– Maintained by Planning / Essbase administrator
– May be written efficiently by using meta data
• UDAs, member set functions
• FIX … ENDFIX
• Calc Manager rules may use form point of view in Planning
– Created files may be written to or picked up from URLs
• Cons:
– Calc scripts can be hard to follow without
documentation

- 20 -
• Flat file or SQL sources
• Delimited or fixed
• Mapping is possible
• Column and text manipulation including sign flip
• Selection and rejection of records by column
values
• Overwrite / additive of data values
• May be used with scripts and by other tools like
FDM / FDMEE
Load Rules

- 21 -
• Pros:
– Data loads with rules are fast
– Maintained by Essbase / Planning administrator
– Another product is not needed
• Cons:
– Rule is a binary object which may only be
maintained in EAS
– Prefixes, suffixes, maps, row rejects, row accepts
must be viewed independently – no documentation
format
Load Rules

- 22 -
• Cons, continued
– Maps may not be loaded but must be manually
entered
– Complex mapping or column manipulation is not
easy and sometimes not possible
– Occasionally rules become corrupted and must be
recreated
– Changes to files / columns oft times require
creating a new load rule
Load Rules

- 23 -
• Transparent
– No data movement – just database pointers
• Replicated
– Copies data
• Area definitions
– May use member set functions
• Mapping
– 1 to 1 (for example: Jan = 01)
• May be scripted with MaxL
Partitions

- 24 -
• Pros:
– Maintained by Essbase / Planning administrator
– May be scripted using MaxL
– Data accessed via transparent partition is “live”
• Cons:
– May only be used for data movement between
Essbase / Planning applications
– Replicated requires manually invoked or scheduled
data movement
Partitions

- 25 -
• Pros:
– Maintained by Essbase / Planning
administrator
– May be scripted using MaxL
– May use member set functions
• Cons:
– Like coding an old “green bar”
report on mainframes
– Formatting challenged
– Poor performance with a lot of data
Essbase Report Scripts

- 26 -
Other Tools

- 27 -
• Mapping including complex mapping
• Validation of load members
• Multiple sources and import formats
• Multiple users loading data
• May be customized for data clears and calcs
• May use load rules
• Audit trail
FDM / FDM EE / ODI

- 28 -
• FDMEE and ODI may be used for
metadata
• FDM Classic can be used to generate .ADS
files for DRM or EPMA
• In 11.1.2.4 data sync is moved to FDMEE
– Hyperion applications as sources
– Map
– Load to other Hyperion applications as targets
FDM / FDM EE / ODI

- 29 -
• Pros:
– Excellent for mapping
– Drill back to the source
– Auditors “love” the audit trail
• Cons:
– Another product to build and maintain
– Potentially additional licensing
– Reduced performance with very large data sets
(>1.5-2M records) in FDM classic
FDM / FDM EE / ODI

- 30 -
• Requires both source and target applications to
be EPMA applications
• Mapping
• Filtering and overrides
• Targets may be HFM, Planning,
EPMA’s Data Synchronization
Essbase (both ASO and BSO), PBCM
• Sources may also include flat files and interface
tables
• Create/modify, define, validate, execute steps

- 31 -
• Pros:
– May be automated
– May use variables to define Year and Period
– Good for copying data within the same application
• Cons:
– Requires applications to be maintained with EPMA
– Member lists (HFM) are not allowed
– Mapping too limited in some cases
– How long will it be supported due to the move to
FDMEE?
EPMA’s Data Synchronization

- 32 -
• Dimension mapping defined in Planning
• May map Smart Lists to dimensions
– Smart Lists may be synchronized to the reporting app
• PushData.exe utility available on Planning server
– Batch jobs and scheduled pushes
• Reporting app may not have attribute dimensions
• Reporting app may not have “Duplicate Members
Allowed” option
• Runs a DATAEXPORT calc script
• Source must be BSO plan type (not ASO)
Planning’s Map to Reporting Application

- 33 -
• Pros:
– Reporting on Planning data in
a separate application
– Aggregating and reporting on
Smart Lists
Planning’s Map to Reporting Application
– May link Planning data to multiple reporting applications
– May be automated
• Cons:
– Planning automatically maps same-named dimensions
– Member names must match in both applications

- 34 -
• Several file format options
– Flat file
– Database tables
• POV templates may be saved, reused, shared
• Only extracting meta data is possible
• Specific slices of data may be extracted at any
level
• Definitions may use member lists, members,
functions
• Has now been merged into HFM Data Extract
HFM’s EA - Extended Analytics

- 35 -
• Pros:
– May be automated with task flows
– Very fast for small amounts of data
– Extracts may be used outside of EPM
• Cons:
– Set up used to be by trial and error until successful
but in recent versions is now quite easy
– No mapping available
– No native automated load to target application
– Extract format may not be modified
HFM’s EA - Extended Analytics

- 36 -
• Uses partitions to create an Essbase
database version of HFM
• Replicated partition loads data into Essbase
• Transparent partition utilizes a data
synchronization repository storing data
outside of Essbase
• Can be set up for instant or manual updates
HFM’s EAL – Essbase Analytics Link

- 37 -
• Pros:
– Essbase licenses are much less expensive than HFM
licenses
– Essbase view of HFM data is updated almost instantly
compared to syncing or loading data
– Custom mapping may be built in the relational db
– Other data may be added to the Essbase cube
• Cons:
– Challenging to set up

- 38 -
• Cons, continued
– Must use local EAS Console Client for build and
administration
– Additional licensing
– Potential for two versions of FR reports needed: one
sourced from HFM and one sourced from Essbase
– Oracle only has one support person globally
– No new version since 11.1.2.2 - roadmap?

- 39 -
Different Options Between
Products

- 40 -
Different Options Between Products

- 41 -
Demonstrations / Examples

- 42 -
• Calc Script with DATAEXPORT
• Load rule with mapping and record
selection

- 43 -

- 44 -
• Create Replicated Partition
• Push data
• Retrieve data with Smart View

- 45 -

- 46 -
• Create Planning Map to Reporting
• Push data
• Retrieve data with Smart View

- 47 -

- 48 -
Case Studies / Solutions

- 49 -
• HFM is primary consolidation and external reporting
tool
• Budget and Forecasts are performed in Planning
• Same data is needed in both products
• Minimize work for user by only having to load a file
once but send data to both products
• Accommodate lower level of detail in Planning
• Many different formats, maps, and data loaders
• HFM loads occur multiple times a day
• Planning loaded once a day and when actual data is
finalized
Case #1 - Requirements

- 50 -
Case #1 - Inbound

- 51 -
Case #1 - Outbound

- 52 -
• FDM solution with MaxL, calc scripts and scheduled
jobs
• Currency translation in both HFM and Planning
• Periodic conversion in Planning
• Administrator controls when to load data to Planning
• Budget/Forecast data loaded to HFM every 2 hours
• No additional work for users
• Users control mapping
• Easy to maintain
• Audit trail
Case #1 - Summary

- 53 -
• Same actual source data goes to Planning and HFM
• Users load to both products
• Amounts in both products must match within minutes
• Accommodate lower level of detail in Planning
• Many different formats, maps, and data loaders
• Loads occur multiple times a day
• Applications are EPMA maintained with shared
hierarchies

- 54 -
Case #2

- 55 -
• Dual load by users to Planning and HFM from FDM
• Data Sync of IC Eliminations from HFM to Planning
• Currency translation in both HFM and Planning
• Periodic conversion in Planning
• Users control mapping
• Data Sync scheduled and on-demand
• Audit trail
• Data between products reconciles
Case #2 - Summary

- 56 -
• Different data to Planning, HFM, and Essbase
• Drill back to source required
• Customer level reporting data with 60K SKUs
• User input to Planning at customer level with 60K SKUs
• More detail in Planning and Essbase than HFM

- 57 -
Case #3

- 58 -
• Build is in process
• FDM heavily used
• Planning to use ASO plan types and Map to Reporting
• Replicated and transparent partitions for reporting
cubes use
Case #3 - Summary

- 59 -
• Individual Planning applications for each BU
• Identical meta data in each planning application
• Meta data updated automatically from the source data
to be loaded monthly
• Data from all BU applications to be consolidated in the
corporate application

- 60 -
Case #4

- 61 -
• ODI solution for all data movement
• Meta data is updated from the Oracle EBS data to each
BU application and the corporate application
• Oracle EBS data is loaded to all 10 applications
• Budget and Forecast data is pushed / pulled to the
corporate application
Case #4 - Summary

- 62 -
• Weigh the pros and cons of
each option
• KISS theory – minimize
complexity and points of
failure
• Consider future maintenance and who will need
to do it!
• How many resources will be needed for each
product / method used?
• Do not use it just because it is there!
Summary

- 63 -
Questions and Answers

- 64 -
“What an FDM to FDMEE Conversion Looks Like”
Friday, September 18th, Noon EDT
Next Finit Webinar

- 65 -
Past Webinars:
http://www.finitsolutions.com/webinar.html
Presenter
Cindy Eichner
General Questions
Greg Barrett
gbarrett@finitsolutions.com
Joe Mizerk
jmizerk@finitsolutions.com
Questions?
Email us for a copy of the
slides or link to the recording
insights@finitsolutions.com
Thank You for Attending!

Data options with hyperion planning and essbase

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Data options with hyperion planning and essbase

Similar to Data options with hyperion planning and essbase (20)

More from finitsolutions

More from finitsolutions (20)

Recently uploaded

Recently uploaded (20)

Data options with hyperion planning and essbase