hfm 11.1.1 implementation boot camp presentation...

1

(Oracle)

For Oracle employees and authorized partners only. Do not distribute to third parties. © 2008 Oracle Corporation – Proprietary and Confidential

The following is intended to outline our general product direction. It is intended for information

Safe Harbor Statement

ppurposes 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

f O


products remains at the sole discretion of Oracle.

2

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

Oracle Training Materials – Usage Agreement

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 redistributed in any format without Oracle written consent.

I t Pi t H

(title slide)

<Insert Picture Here>


Title of Presentation

Presenter’s NamePresenter’s Title

Hyperion Financial Management 11.1.1 Implementation Boot CampPresenter’s NamePresenter’s Title

3

Course Agenda

• Day 1• Overview

• Metadata Building

• Day 2• Data Loading

• Rules and Member Lists

• Day 3• Security

For use by Oracle employees and authorized partners only. Do not distribute to third parties.

Security

• Administrator Tasks

• Day 4• End User Tasks

Slide ContentContributed by:

Course Note – Accounting Knowledge

• While not a hard and fast prerequisite, a level of accounting knowledge is needed for this course and g gfor 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


product or the operating system, server setup, and network requirements involved in a typical implementation


4

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


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 through reliance on just the screen shots



Ch t 1 O iChapter 1 – Overview



5

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 productp p p

• 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


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 product and in 2008 had over 1,500 customers


6

HFM Dimensions

• HFM has 12 dimensions, the combination of which point to a single data amountp g

• The basic six dimensions:• Dimension Description Example

• Scenario Type of data Actual

• Account Account Net Income

• Entity Organizational Unit Total Company

• Period Quarter, Month, Week June


, ,

• Year Year 2009

• View Frequency of data Year to Date


HFM Dimensions

• The next five provide account detail

• Intercompany Partner – specifies the partner entity forIntercompany 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


p p

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


7

HFM Dimensions

• The last, Value, shows how the data consolidates from child entity to parent entityy p y

• Journal adjustments are stored in unique Value dimension members

• Each member to the righthas a unique purpose

• Becoming familiar withthis dimension is key to


this dimension is key tosuccessfully using HFM


Overview – HFM Position in EPM Suite



8


Ch t 2 M t d tChapter 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


management method• Customers upgrading tend to continue with Classic• Partners tend to recommend Classic to customers

due to familiarity and high degree of stability


9

Dimensions – Point of View

• The point of view refers to the combination of the members specified for each of the 12 dimensionsp

• 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


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 labelsg , g g

• Calculated base level members should be alphanumeric and descriptive of the calculation

• Parent levels shouldbe alphanumericand descriptive ofthe parent


the parent

• Avoid spaces andsemicolons


10

Dimensions – Key Design Consideration

• Generally, no parent member should only have just one child – is a waste of system resources that yusually 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


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 chapterp

• If covering EPMA and not Classic in the course, refer to the Classic chapter in the manual for this information



11

Metadata Development – Classic

• There are two components to metadata development• Profile – one time setup of Year, Periods, and View p , ,

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


Windows client software


Metadata Management – Classic

• Profile is created once – once an application created with a profile those dimensions cannot be changedp g

• 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


Windows client or a text file - interchangeable

• There are integrity checks within the software when loading metadata to the application


12

Metadata Management - EPMA

• EPMA offers metadata management advantages when working with multiple Hyperion applications, g p yp pp ,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 li ti


application

• An upgrade tool is built in to convert Classic application to EPMA – a one way upgrade!



Ch t 3 D tChapter 3 – Data



13

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


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


14

Data Extract Alternatives

• HFM Extended Analytics

• Hyperion Smart View for Microsoft OfficeHyperion 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)


y ( p )

• HFM API

• Partner developed tools


Copying and Clearing Data

• Tools within HFM allow for copying and clearing data within the same applicationpp

• Can apply factor when copying, like copy Actual to Budget and apply 10% growth rate

• Do not work with journal data



15


Ch t 4 R lChapter 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 forRules 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” subroutines.

• Comments may be added by placing an apostrophe in front of the comment.

• A variable is handy for storing something once and referring to it multiple times.


• HS.Entity.Member, HS.Exp, and HS.Dynamic are HFM functions.

• An If/Then statement is the most common way of restricting when a calculation is run.


16

HFM Rules



Rules – Standard Subroutines

• Calculate – runs whenever calculating an entity. Most rules go here.• Translate – used to translate accounts with special rates. Runs when

the currency changes from Value dimension members <Entity Curr y g yTotal> to <Parent Currency>.

• Consolidation – used to calculate ownership and eliminations when default behavior is not adequate

• Allocation – can be used to perform allocations; can also be used for other types of rules – execution is separate from the consolidation process

• Input – enables data input into parent level entities at <Entity Currency> value member – not recommended

• NoInput – disables data input into members. Strict limits on the functions that can be used


functions that can be used.• Dynamic – used for calculations where the result will vary based on the

View dimension, like Gross Margin Percentage• Transactions – specifies the accounts to be used in the intercompany

transaction


17

Rules – Dimension Labels

• Use these dimension labels when referencing a member

A Account I Interco PartnerC1 Custom1 P PeriodC2 Custom2 S ScenarioC3 Custom3 V ValueC4 Custom4 W ViewE Entity Y Year


y

• Syntax example: A#NetIncome


Rules - Basics

• Use variables to store or calculate something and then refer to it later

• Restrict rules to run only when needed

• Restriction Techniques• If / Then (and variations)

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

• For / Next (processes a list of items, performing designated calculations on each)


• Rules with custom dimension members are self-restricting – will only run where validHS.Exp “C1#OpeningBalance=C1#EndingBalance.Y#PRIOR.P#LAST”


18

Rules – Common Calculations

• Opening Balance

• Year to Date Net Income to Retained EarningsYear to Date Net Income to Retained Earnings

• Balance the Balance Sheet

• Dollar Overrides

• Currency Translation Adjustment

• Impact Status

• WriteToFile


• Cash Flow

• NoInput

• OpenDataUnit


Rules - Functions

• Custom functions can be used to repeat code

• Idea is to pass variable(s) to the function and theIdea 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



19

Rules – Calculation Manager

• New with version 11.1.1 is Calculation Manager, a graphical interface to rulesg p

• 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 t / f ti


create/use functions

• Oracle working on a migration tool



Ch t 5 Li tChapter 5 – Lists



20

Lists – Basics

• Member lists can be used for a variety of activities• Rules, grids, forms, POV navigation/selection, g , , g

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


extension from lst to rle for most benefit)

• Load and extract similar to rules



Ch t 6 Sh dChapter 6 – Shared Services



21

Shared Services

• Shared Services is a separate module that supports the Hyperion EPM suiteyp

• 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



Security

• Areas of security:• Users and Groups – are provisioned (granted) accessp p (g )

• 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 a text file, modified there, and uploaded


22

Security Design

• An Excel file recommended for laying out security and sending through company for review/approvalg g p y pp



Lifecycle Management

• Can be used with EPMA applications to migrate artifacts from one application to anotherpp

• 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



23


Ch t 7Chapter 7 –Administrative Stuff



HFM Copy Application Utility

• Use to copy entire Classic applications (no EPMA apps) from one place to anotherpp ) p

• Can copy across environments or within one environment

• Only access to UDL files required – no prompt for ID and password

• Copies data from table to table at the relational database level


database level


24

HFM Utilities

• Used for various analysis by the administrator

• Base member compare and duplicates below parentsBase 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 applicationReview 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



25

Process Control

• Electronic signoff of data

• Various design considerations:Various design considerations:• Scenarios

• Edits

• Account groupings (phased submissions)

• Who involved and number of levels of signoff

• Data access available before or after signoff



Data Entry Forms

• Convenient for input of supplemental data

• For companies subject to Sarbanes-Oxley:For companies subject to Sarbanes Oxley:• Should not be used for balance sheet or profit and loss input

– supplemental input only

• Changes to balance sheet, profit and loss accounts should be via journals

• Users should not have ability to create/modify forms

• Use wizard to walk through creation of forms


• Forms can be formatted simply or heavily formatted


26

Yahoo! User Group

• Yahoo! groups exist for HFM and other Hyperion modules

• Recommended not only to ask questions but also for access to years of archived questions and answers

• Go to http://tech.groups.yahoo.com/group/hsfm for more information




Ch t 8 E d UChapter 8 – End User Basics



27

End User Basics

• Tasklists can be used to direct users through specific tasks, grids, forms, etc.

• Depending on security role provisioning a user can be restricted to tasklist navigation only

• Data grids offer user capabilities to view the data in any possible way

• End users are encouraged to create grids or find existing grids that meet their needsP i f i i i l d id


• Point of view usage critical to data grids• Grids can be saved with security class or marked

private to limit access


Journals

• Journals used for debit/credit style adjustments

• Are stored in one of four value dimension members –Are stored in one of four value dimension members effect on data depends on which member used

• Security controls whether users are limited to creating journals, approving journals, and/or posting journals

• Journal listings and detail can be filtered and reported

• Administrator must open the period before journals ll d


are allowed

• Periods can be closed and reopened as needed


28


Ch t 9 E d UChapter 9 – End User Next Steps



Intercompany Matching / Elimination

• Intercompany accounts use the ICP dimension to store the partner entityp y

• Intercompany balances are, by default, eliminated at the first common parent

• Intercompany accounts can be matched against others (like IC receivable vs. IC payable) or can be eliminated one-sided (IC sales eliminating to IC cost of sales [and netting against non-IC cost of sales])


of sales [and netting against non IC cost of sales])

• Intercompany entries are made in the [Elimination] value dimension member


29

Intercompany Matching / Elimination

• Intercompany setup is done in metadata:• Which entities can be partnersp

• Which accounts are designated intercompany

• Which account is the plug account for intercompany account(s)

• The plug account will hold any out of balances among the intercompany accounts• If everything matches, the plug account will be zero


• Reporting is available for all users to analyze and reconcile intercompany balances


Process Control

• Process control is subject to design and controls implemented by the administrator (see chp 7)

• Validations (edits) must be passed and the data calculated before signoff can occur

• Once a user signs off on the data, they lose the ability to change – any required change would have to be done by someone at a level above them or the data rejected back to them

• Signoff follows the entity hierarchy


• Signoff follows the entity hierarchy• Accounts and customs can be signed off in phases:

financials could be the first phase and supplemental data in the second phase


30


Ch t 10 E d UChapter 10 – End User Reporting



Reporting

• Financial Reports and Web Analysis views are run from the Hyperion Workspace, the same logged into yp p , ggto access HFM

• PDF and HTML versions of Financial Reports are available by toggling the buttons on the toolbar

• Use the point of view to control the information presented



31

Smart View for Microsoft Office

• Smart View is an addin; mostly used with Excel

• First step is to establish a connection to the dataFirst step is to establish a connection to the data source – can be HFM, Planning, or BI+ (the workspace)

• Multiple types of usage:• Functions – pull a number into a specific cell

• Ad Hoc Analysis – move dimensions around, view data

• Forms – open form input data submit


Forms open form, input data, submit

• Smart tags – use to pull data into Word

• Can also pull reports into MS Office not just HFM data



Ch t 11 Fi i lChapter 11 – Financial Reporting Studio



32

Financial Reporting Studio

• Studio is the report writer for HFM.

• Reports can have grids text boxes images andReports can have grids, text boxes, images, and charts

• Within grids HFM dimensions are placed in rows, columns, and page

• Dimensions not placed in a grid remain in the user point of view



Formatting – Simple and Complex

• Various formatting options exist, from simple bolding to complex conditional formatting/suppressionp g pp

• Some of the features are for HTML view only, such as expansions and related content


33


Ch t 12 W kChapter 12 – Workspace



Workspace

• Workspace is the place where users run reports, and it also provides several tools for developersp p

• Books allow for one or more reports to be run with multiple points of view to generate a package

• Batches allow for reports and books to be scheduled and run automatically with the output going to various destinations


34

The preceding is intended to outline our general product direction. It is intended for information ppurposes 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

f O


products remains at the sole discretion of Oracle.

For More Information

search.oracle.com

or

Hyperion Financial Management


ororacle.com

35



hfm 11.1.1 implementation boot camp presentation...

Documents