Implementation Boot Camp Presentation Slides

Course Note – Accounting Knowledge• While not a hard and fast prerequisite, a level of accounting knowledge is needed for this course and for consultants implementing Oracle Hyperion Fi

(Oracle)

The following is intended to outline our general

product direction It is intended for information

purposes only, and may not be incorporated into any contract It is not a commitment to deliver any

material, code, or functionality, and should not be

relied upon in making purchasing decisions

The development, release, and timing of any

features or functionality described for Oracle’s

products remains at the sole discretion of Oracle

Safe Harbor Statement

Use of this Site (“Site”) or Materials constitutes agreement with the following terms and conditions:

1 Oracle Corporation (“Oracle”) is pleased to allow its business partner (“Partner”) to download and copy the information, documents, and the online training courses (collectively, “Materials") found on this Site The use of the Materials is restricted to the non-commercial, internal training of the Partner’s employees only The Materials may not be used for training, promotion, or sales to customers or other partners or third parties

2 All the Materials are trademarks of Oracle and are proprietary information of Oracle Partner or other third party at no time has any right to resell, redistribute or create derivative works from the Materials

3 Oracle disclaims any warranties or representations as to the accuracy or completeness of any

Materials Materials are provided "as is" without warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement

4 Under no circumstances shall Oracle or the Oracle Authorized Delivery Partner be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site

of Materials As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partner’s use of the Materials.

5 Reference materials including but not limited to those identified in the Boot Camp manifest can not be

Oracle Training Materials – Usage

Agreement

<Insert Picture Here>

Title of Presentation

Presenter’s Name

Presenter’s Title

Hyperion Financial Management 11.1.1

Implementation Boot Camp

Presenter’s Name

(title slide)

Course Note – Accounting Knowledge

• While not a hard and fast prerequisite, a level of

accounting knowledge is needed for this course and for consultants implementing Oracle Hyperion

Financial Management

• Much of the product and its implementation focuses

on accounting more than IT issues

• This course does not address the installation of the product or the operating system, server setup, and

network requirements involved in a typical

implementation

Course Note – Course Material

• The designed flow of this course is to present the material via the

manual with highlights in this Powerpoint deck and then go to the

software for viewing, examination, and exercise

• These slides highlight key aspects of the manual but do not take the place of the manual

• The manual is not intended to be comprehensive product

documentation: refer to the various PDF documentation

• The course is also designed with the assumption that an experienced consultant is teaching the course The exercises are more free form to allow students to approach the topics as they see fit An experienced consultant will be able to support the students in the various directions they go.

• The separate teach note document provides information to the

instructor on how to proceed through the course; however, the teach notes, like the course, assume that the instructor is an experienced consultant.

• Software screen shots are included in the materials; however, the

student’s learning will progress by direct usage of the software, not

<Insert Picture Here>

Chapter 1 – Overview

Overview – What is HFM

• Oracle Hyperion Financial Management (HFM) is a financial

consolidation and reporting product

• Ideal for medium and large corporations – currency translation, intercompany eliminations, ownership calculations are all

accommodated

• IFRS, US GAAP, statutory, and other accounting requirements

worldwide can all be met

• Data comes in, accounting consolidation rules are applied, and final data for reports is available, all within a controlled, secured environment with supporting processes

• Month, quarter, and year end balance sheet, profit and loss,

cash flow, and supplemental reports are the typical outputs of an HFM implementation

Overview – History

• Over 25 years of accounting and consolidation

expertise in the development of the product

• Roots go back to Micro-Control, a DOS product

developed by IMRS in the early 1980s

• Second generation product was Hyperion, later

renamed to Enterprise when IMRS changed its name

to Hyperion In 2008 there were over 2,500 customers using Hyperion Enterprise and it is currently marketed

by Oracle mostly to small and mid size companies

• HFM was introduced in 2000 as the third generation

HFM Dimensions

• HFM has 12 dimensions, the combination of which

point to a single data amount

• The basic six dimensions:

• Scenario Type of data Actual

• Entity Organizational Unit Total Company

• Period Quarter, Month, Week June

• View Frequency of data Year to Date

HFM Dimensions

• The next five provide account detail

• Intercompany Partner – specifies the partner entity for

intercompany balances

• Custom1 to Custom4 – dimensions that can be

configured by account to store additional detail

• Customs can be shared across accounts or unique to a

single account

• A custom dimension can be reused for different purposes

• Examples: product, cost center, state, movement detail

HFM Dimensions

• The last, Value, shows how the data consolidates

from child entity to parent entity

• Journal adjustments are stored in unique Value

dimension members

• Each member to the right

has a unique purpose

• Becoming familiar with

this dimension is key to

successfully using HFM

Overview – HFM Position in EPM Suite

<Insert Picture Here>

Chapter 2 – Metadata

Metadata Management – EPMA vs Classic

• EPMA is a fairly new module (out for a couple of

versions) for metadata development and

management

• EPMA provides capabilities for sharing dimensions

and members across multiple Hyperion products

• Newer features, such as Lifecycle Management, are

being developed for EPMA

• Classic is the original metadata development and

management method

• Customers upgrading tend to continue with Classic

• Partners tend to recommend Classic to customers

Dimensions – Point of View

• The point of view refers to the combination of the

members specified for each of the 12 dimensions

• Example, a report may have accounts in the rows and

years in the columns – the remaining 10 dimensions would make up the point of view

• The point of view is typically how end users navigate

through the dimensions to select what they wish to

view, report, analyze, etc

• Term and usage is similar to other Hyperion products

Metadata Best Practices – Labeling

• If base level members are reflective of the general

ledger, then use the general ledger labels

• Calculated base level members should be

alphanumeric and descriptive of the calculation

• Parent levels should

Dimensions – Key Design Consideration

• Generally, no parent member should only have just

one child – is a waste of system resources that

usually just duplicates the data

• Most harmful with the account dimension, somewhat

with entities, and a little with customs

• Common error is to create parents now with the

expectation that additional children will be added later – best to create the parents when needed

• Acceptable exceptions exist for the entity dimension

for currency reporting and throughout for phased

implementations

More Design Considerations

• In the manual metadata design considerations are

included in the Metadata – Classic chapter

• If covering EPMA and not Classic in the course, refer

to the Classic chapter in the manual for this

information

Metadata Development – Classic

• There are two components to metadata development

• Profile – one time setup of Year, Periods, and View

dimensions – also lists languages for member descriptions

• Metadata Manager – initial development and ongoing

maintenance of Scenario, Account, Entity (and ICP via

derivation), and Custom1-4 dimensions – also lists

currencies, consolidation methods, and application settings

• Both of these components are part of the HFM

Windows client software

Metadata Management – Classic

• Profile is created once – once an application created

with a profile those dimensions cannot be changed

• If a change required, create a new profile and a new

application

• Dimensions in metadata management can be

changed over and over

• Metadata management can be done either with the Windows client or a text file - interchangeable

• There are integrity checks within the software when

loading metadata to the application

Metadata Management - EPMA

• EPMA offers metadata management advantages

when working with multiple Hyperion applications, whether HFM, Planning, etc

• EPMA is web based tool – no Windows client

• Text file can be used to format metadata and upload

• Text file cannot be extracted, use separate utility

• Updates are entered and then deployed to the

application

• An upgrade tool is built in to convert Classic

application to EPMA – a one way upgrade!

<Insert Picture Here>

Chapter 3 – Data

Data Format

• HFM has a native data load and extract capability and

format

• Data can be loaded as Merge, Replace, Replace by

Security or Accumulate – Replace by Security and

Merge are the two most common

• Journal data has a separate format and load/extract

process

• Journal data or data net of journals cannot be

extracted via the normal data extract process

Data Load Alternatives

• Hyperion Financial Data Quality Management

• Hyperion Data Integration Management

• Oracle Data Integrator

• Manual Input

• Hyperion Smart View for Microsoft Office

• EPMA Data Synchronization (see Chapter 2)

• HFM API

• Partner developed tools

Data Extract Alternatives

• HFM Extended Analytics

• Hyperion Smart View for Microsoft Office

• HFM Rule

• Hyperion Financial Data Quality Management

• Hyperion Data Integration Management

• Oracle Data Integrator

• EPMA Data Synchronization (see Chapter 2)

• HFM API

• Partner developed tools

Copying and Clearing Data

• Tools within HFM allow for copying and clearing data

within the same application

• Can apply factor when copying, like copy Actual to

Budget and apply 10% growth rate

• Do not work with journal data

<Insert Picture Here>

Chapter 4 – Rules

HFM Rules

• Rules are written in VB Script and use most of the same syntax

and techniques

• Rules are organized into parts called subroutines HFM looks for

specific subroutines for specific purposes and others can be

used to help organize the calculations.

• Sub Calculate and Sub Dynamic are two of the “expected”

• An If/Then statement is the most common way of restricting

when a calculation is run.

HFM Rules

Rules – Standard Subroutines

the currency changes from Value dimension members <Entity Curr

Total> to <Parent Currency>.

default behavior is not adequate

other types of rules – execution is separate from the consolidation

process

Currency> value member – not recommended

functions that can be used.

View dimension, like Gross Margin Percentage

Rules – Dimension Labels

• Use these dimension labels when referencing a

• If / Then (and variations)

• Select Case (similar but better handles multiple options with the

Rules – Common Calculations

• Opening Balance

• Year to Date Net Income to Retained Earnings

• Balance the Balance Sheet

Rules - Functions

• Custom functions can be used to repeat code

• Idea is to pass variable(s) to the function and the

function returns a value, a string, etc to place into the calling script

• Functions assist with maintenance – change the

function vs all places that use the same code

Rules – Calculation Manager

• New with version 11.1.1 is Calculation Manager, a

graphical interface to rules

• Use components to build rules

• Can also integrate VB script components

• Requires the application to be EPMA enabled – will

not work with Classic application

• As of this release cannot use Select Case and cannot create/use functions

• Oracle working on a migration tool

<Insert Picture Here>

Chapter 5 – Lists

Lists – Basics

• Member lists can be used for a variety of activities

• Rules, grids, forms, POV navigation/selection

• System has several lists built in for each dimension

that suffice for most needs – begin and end with

brackets [ ]

• Additional lists created in a VB script style text file –

can use Rules Editor to work with (rename file

extension from lst to rle for most benefit)

• Load and extract similar to rules

<Insert Picture Here>

Chapter 6 – Shared

Services

Shared Services

• Shared Services is a separate module that supports

the Hyperion EPM suite

• Key components are:

• Security, including connecting to a company’s network ID

setup and authenticating user IDs and passwords

• Lifecycle Management – movement of items from one HFM application to another

• Audit Reports

• Areas of security:

• Users and Groups – are provisioned (granted) access

• Roles – tasks or software features that users or groups can

do – consolidate, create journal, be an administrator, etc.

• Classes – a go-between between users or groups and

dimension members or web components

• Most security done within Shared Services

• Assigning classes to metadata and web components

done in metadata management and HFM web

• For Classic applications, security can be extracted to

Security Design

• An Excel file recommended for laying out security and

sending through company for review/approval

Lifecycle Management

• Can be used with EPMA applications to migrate

artifacts from one application to another

• Artifacts can be web forms, grids, etc.

• If migrating across environments (not just applications

but across whole separate instances of Hyperion), a intermediary file is used

<Insert Picture Here>

Chapter 7 –

Administrative Stuff

HFM Copy Application Utility

• Use to copy entire Classic applications (no EPMA

apps) from one place to another

• Can copy across environments or within one

HFM Utilities

• Used for various analysis by the administrator

• Base member compare and duplicates below parents

are the most commonly used features

• Also convenient for exporting metadata to Excel file

for review by company staff

HFM Administration Menu

• Contains several items for administrators to review

• Review system messages for rule errors, application

errors

• Task and Data Audit logs should be

exported/archived and cleared periodically

• Task Automation can be used to automate

consolidations and other tasks

Process Control

• Electronic signoff of data

• Various design considerations:

• Scenarios

• Edits

• Account groupings (phased submissions)

• Who involved and number of levels of signoff

• Data access available before or after signoff