supplemental data manager - what is it? what are some use cases? how do i get it?

www.finitsolutions.com

Getting the Most Out of EPM:Supplemental Data ManagerWhat is it? What are some use cases? How do I get it?

July 24th, 2015

Erich Ranz ([email protected])

http://www.finitsolutions.com/

www.finitsolutions.com- 2 -

• 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



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

• Oracle Financial Close Suite

‒ Hyperion Financial

Management

‒ Financial Close Manager

‒ Account Reconciliation

Manager

• Hyperion Planning & Essbase

• Infrastructure

• Data Services

• Project / Program

Management

• Redesign / Enhancements

• Product Upgrades

• Application enhancements /

redesign

• Performance optimization

Dedicated Support

Upgrades

Full Cycle Implementations


www.finitsolutions.com

Finit Solutions Introduction

Finit as a company:

Who we are…Why? How?



• 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?



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?



Our values, on which we ask you to provide consultant feedback:

Finit Values



Our values, culture, and approach to becoming a trusted advisor to customers

has led to 100% customer success for every Finit client (220+) and for every

Oracle Hyperion project (400+)

Finit Customer Success



Some Finit Customers



Questions



About the Presenter

Erich Ranz

([email protected])

• Eleven years Oracle EPM experience– HE admin/FP&A at Gentiva Health

Services

– Finance/Corp Compliance at Sprint Nextel

– HFM/FDM admin at Koch Industries

– HFM Team at Finit

• Based in Wichita, KS


mailto:[email protected]


• SDM Introduction & Product Overview

– Product Introduction

– Use Case Overview

– SDM Key Product Functionality

• Use Case Review and Demo

• Design Approach

• Summary

Agenda



SDM Product Introduction & Overview

SDM



• Module within Financial Close Manager (FCM)

– Joins ARM (Account Reconciliations Module) and CM (Close Manager) as modules of FCM

• All FCM modules licensed together

• SDM released in 11.1.2.4

– CM released in 11.1.2.1

– ARM released in 11.1.2.2

– SDM released in 11.1.2.4

• Part of Oracle early adopter program

SDM Introduction



• Centralized workflow and collection solution for Supplemental, Textual and Unstructured information

• Ability to combine Financial data with Commentary and Text

• Flexibility to allow for different schedules and layouts per submission needs (i.e. Debt schedule requires 12 fields but Operating Lease schedule requires 6).

Product Purpose



• Smart View

– Data Entry

– Reporting

• HFM

– Metadata pulls from

– Source data upload to

– Drill-back

• Consistent Versioning (all on 11.1.2.4)

SDM Integration with EPM



• Dashboards

– Mostly for status (Completion, open, etc.)

• Form Analysis

• Reporting via BI Publisher Add-In

– SQL Query Based (similar to FDMEE reporting)

– Very Flexible

– Some learning curve will exist

Internal Reporting and Analysis



• SEC Footnote Disclosures

• Tax Schedules

• Internal Supplemental Information

• Questionnaires

Supplemental / Unstructured Data



Sample Current Schedules



• Manual email based collection and consolidation of supplemental data

• Text & Commentary challenges with EPM Applications

• Offline Templates

• Lack of Reporting and Analysis

• No centralized workflow (Email based)

Problems SDM Solves



Use Case Overview

SDM



• Example: Roll-Forward Schedule

Case #1 – All Data



• Example: Roll-Forward Schedule

• Details: Financial data is collected on all members / fields and aggregation / consolidation and translation occurs on all members.

• Current Pain Points: Not Many

– HFM Web Forms handles this task well

– May run into dimensionality constraints in select cases.

Case #1 – All Data



• Example: Bridge Analysis

Case #2 – Mostly Data, 1 Text Field



• Example: Bridge Analysis

• Details: Financial data is collected on the majority of members / fields, but have 1 field for text collection / commentary.

• Current Pain Points: Some

– HFM cell text usually suffices with this option.

– Cell text reporting can be difficult / hard to find

Case #2 – Mostly Data, 1 Text Field



• Example: Lien Schedule

Case #3 – Mostly Text, Few Data Fields



• Example: Lien Schedule

• Details: Financial Information captured on just a few members / fields. Most of the members / fields require textual information.

• Current Pain Points: Significant

– Challenges in HFM applications to store multiple points of textual information.

– Work-around HFM options to create defined metadata members can limit flexibility (i.e. 10 generic members are created).

Case #3 – Mostly Text, Few Data Fields



• Example: Changes in Accounting Principles

Case #4 – All text



• Example: Changes in Accounting Principles

• Details: No Financial Data is collected and only text is stored. Text may involve many types (check box answers, free-form boxes, drop down lists, etc.)

• Current Pain Points: Significant

– Challenges in EPM applications to store all text and large volumes of commentary.

– Reporting Challenges

Case #4 – All text



Key SDM Functionality

SDM



• Connections

• Currencies

• Frequencies

• Periods

• Preferences

System Settings



• External Based (HFM) or Internal

• HFM Based

– Uses Connection from System Settings

– Pulls all HFM Metadata Members into SDM

• Internal Based

– Admin defines Members and Attributes

– Recommended if repeated across many Forms

• 1 centralized place for all Dimensions used across all forms.

Dimensions



• Data Sets is creation of fields for use in forms

– Think of it as the layout for an Excel workbook or Access table.

• Fields can reference Dimensions created or can be other Attributes

– Numeric, Date, yes / no, Text field, etc.

• Functions can exist (Sum, Average, Count)

• Calculations

– Validations, Math, Concatenation

Data Sets



• Can Have Multiple Sections

• Reference Data Sets

• Can Have Instructions and Attachments

• Have a Workflow

• Can Have Different Levels of User Access

• Show Revision History

• Allow Posting to HFM

Forms



• Similar to ARM Approach

• Forms are aligned to Periods

• Open Periods and Deploy Forms

Linking Forms to Periods



• SDM Workflow follows ARM Approach

• If loading data to HFM via SDM, process steps could be Prepare->Review->Post

– Load to HFM is in Post step

– Review step is for pre-data posting review

• SDM Workflow and HFM Process Management may be used:

– SDM – workflow for preparer and push to HFM

– HFM – process management for sign-off

SDM Workflow



Demo

SDM



SDM Design Approach and Considerations

SDM



• Detail HFM Balances Type

– Ending Balances are loaded via GL

– Form breaks out that balance into details not available in HFM

– Reporting done in HFM and SDM

– Example: Debt schedule breakout

– Key item to this type: • Check Required (SDM Form total vs HFM total)

• Recommended storage of SDM and HFM balance in separate members in HFM data type dimension

• GL Data is the Master, SDM is Detail Support

Type of Collection Design



• SDM Creates Totals to Load to HFM Type

– SDM Form collects details and creates totals that are then loaded to HFM.

– HFM totals are only loaded via SDM

– Reporting done in HFM and SDM

– Example: Total of Non-Compete Agreements

– Key item to this type:

• No Check Required b/c SDM creates the total

• SDM data is Master as no Source / GL data exists




• Data Only Resides in SDM

– SDM Form collects details and creates totals that only exist in SDM and are not uploaded to HFM.

– All reporting done in SDM only

– Example: Questionnaire

– Key item to this type:

• No Check Required b/c SDM creates the total (if applicable)

• No Upload to HFM




• Consolidation, Translation, Elimination

– Members / fields that should be consolidated across entities, or require translation and / or elimination.

• Analytical Reporting

– HFM vs SDM Reporting

• Load, Workflow and User Experience

– GL (FDMEE) and SDM loads and data protection

– SDM Workflow vs HFM Process Management

HFM vs SDM Considerations



SDM Summary

SDM



• Hard-Coded Point of View with Forms by Period, Year, Entity, Scenario = Hard to Scale

• Dimensions are Flat

• Workflow & Design similar to ARM, not HFM

• Currently No Data Pull from HFM for Validations

• Very Flexible in creating Forms

• Requires design of what should stay in SDM versus what should go into HFM applications

• SDM Excel Add-in not with Smart View

• Database is Relational and Designed to Handle Very Large Recordsets

Key Take Away Items



Next Finit Webinar-

Data Options with Hyperion Planning and EssbaseIncluding Mapping, Loading, Moving and Reporting

Friday, August 14th

Getting the Most out of EPM



Questions?

Email us for a

copy of the slides or

link to the recording.

Thank you for attending!

- > Erich Ranz

([email protected])

- > [email protected]

- > General Questions Greg Barrett

([email protected])

Joe Mizerk ([email protected])






supplemental data manager - what is it? what are some use cases? how do i get it?

Technology