Upgrading HFM to Fusion 11.x

Upgrading HFM to Fusion 11.x –Introduction to New Functionality

and Upgrade Considerations

Robert Cybulski, CPAFi it S l tiFinit Solutionsrcybulski@finitsolutions.com

Upgrading HFM to Fusion 11.x

• What are the most recent releases of HFM & FDM?

• New HFM features & functionality

• New FDM features & functionalityNew FDM features & functionality

• Migration options

• Technical considerations

• Project planning• Project planning

About Finit Solutions

Finit Introduction

Finit Solutions specializes in consulting services in the Oracle Hyperion Enterprise Performance Management Solutions suite of products:

Financial Consolidation– Financial Management (HFM)

Hyperion Enterprise

Planning and Business Intelligence– Planning

Essbase– Hyperion Enterprise

Integration– Financial Data Quality

– Essbase

BI+ Reporting ToolsFinancial Reporting– Financial Data Quality

Management (FDM)– Oracle Data Integrator (ODI)– Data Integration Management

– Financial Reporting– Smartview– Web Analysis

Essbase Excel Add inData Integration Management (DIM)

– Other (EPMA, ERPi, etc)

– Essbase Excel Add-in

Focus on Client Service

We take client service very seriously.

Our client service approach has led to 100% customer satisfaction for every Finit

client (117 and counting).

Focus on Client Service

What is the Most Recent Release?

Fusion Edition, Release 11.1.1.3

• The most recent releases of HFM and FDM are:– Oracle Hyperion Financial Management, Fusion Edition, Release yp g , ,

11.1.1.3– Oracle Hyperion Financial Data Quality Management, Fusion

Edition, Release 11.1.1.3,

• All major releases are synchronized, so that the ‘supporting’ products (e.g. Smart View, Financial Reporting etc) are also on Release 11 1 1 3Reporting, etc) are also on Release 11.1.1.3.

• Any service fixes between releases will not be synchronized. For example, you could see an HFM y p , y11.1.1.3.001 service fix without a corresponding Smart View 11.1.1.3.001 service fix. Only major releases are kept in synckept in sync.

Fusion Edition, Release 11.1.1.3

• The Fusion Edition, Release 11.1 will remain on Oracle’s Premier Support until July 2013.pp y

• Premier Support for HFM and FDM 9.3 expires in January 2012.

• Premier Support for HFM and FDM 9.2 expires in June 2010.

• Premier Support for versions prior to 9 2 has alreadyPremier Support for versions prior to 9.2 has already expired.

• Oracle’s Lifetime Support Policy can be found here: http://www.oracle.com/support/library/brochure/lifetime-support-applications.pdf

New HFM Features & Functionality

EPMA

• EPMA stands for Enterprise Performance Management Architect.

• EPMA was previously known as BPMA (Business Performance Management Architect).

• EPMA is used to manage, create, and deploy Hyperion applications within one interface.

• EPMA can be used with HFM Planning and EssbaseEPMA can be used with HFM, Planning, and Essbase.• EPMA is not new to the 11.1.1.3 release; however, it has

begun gaining traction and much wider usage in 11.1.1.x.

EPMA

• EPMA is a great tool for metadata dimension hierarchy and attribute maintenance as well as metadata deployment into specific Hyperion applications.

• EPMA helps solve the issue of sharing metadata across applications. HFM classic metadata manager does not easily allow for this as separate .xml / .app files are y p ppneeded.

• EPMA can also do some basic data movements (e.g. 1-to-1 mappings.) The data movement works best when dimensions line up cleanly among applications.dimensions line up cleanly among applications.

EPMA Modules

• Dimension Library– A centralized location to manage dimensions and dimension g

properties / attributes.– This takes the place of the HFM Classic Metadata Manager.

• Application Library• Application Library– A summary of Application Views that have been created and/or

deployed. Application Views contain dimensions and dimension attributes that are designed to meet specific requirements forattributes that are designed to meet specific requirements for HFM and Planning.

– This is where metadata is deployed to applications after it is built in the Dimension Libraryin the Dimension Library.

• Data Synchronization– Enable data movement synchronizations between Hyperion

applications

EPMA Modules

• Application Upgrade– Enables upgrades from previous HFM and Planning releases pg p g

(Classic to EPMA.)

• Library Job Consoley– Provides a summary of Dimension Library and Application View

activities, including imports, deployments, and data synchronizations.y

– The job consol also shows the status of deployments.

• Calculation Manager• Calculation Manager– Create, validate, deploy, and administer sophisticated

calculations via a graphical interface and calculation flow.

EPMA Modules

EPMA: Calculation Manager

• Calculation Manager is a component of EPMA that allows you to manage your HFM Rules within a graphical interface.

• Calculation Manager and EPMA can be used independentlyindependently.

• Calculation Manager can be used with HFM, Planning, and Essbase.

• Calculation Manager is not new to the 11.1.1.3 release; however, it has begun gaining traction and much wider usage in 11 1 1 3usage in 11.1.1.3.

• Calculation Manager is still expanding its functionality.– For example, you currently cannot create custom functions in

Calc Manager.

EPMA: Other Tips

• Calculation Manager can be used independently from EPMA; in other words, it is possible to use Classic Metadata Manager with Calculation Manager enabled for HFM Rules.

• Conversely it is also possible to use EPMA for metadata• Conversely, it is also possible to use EPMA for metadata management and use a classic .rle file for HFM Rules.

• It is currently not possible to use the HFM app copy utility with an EPMA-enabled application.

• It is currently not possible to load an xml or app file into an EPMA enabled application The administrator mustan EPMA-enabled application. The administrator must choose between EPMA or Classic Metadata Manager –you cannot switch back and forth.

Lifecycle Management

• Lifecycle Management is a Shared Services utility that is used to migrate application ‘artifacts’ from one environment to another (e.g. Production to QA.)

• Lifecycle Management does not migrate data. Lifecycle Management is best used for migrating select itemsManagement is best used for migrating select items (versus recreating an application in its entirety.)

• Lifecycle Management can be used with HFM, Planning, and Essbase for major applications.

• It can also be used with Shared Services, Financial Reporting Web Analysis Interactive ReportingReporting, Web Analysis, Interactive Reporting, Production Reporting, EPMA, Calculation Manager, Performance Scorecard and Profitability & Cost Management.

A Comparison

• EPMA: Great for managing metadata, especially in cases where there are multiple applications with dimensional similarities.

HFM App Copy Utility: Great for copying an application• HFM App Copy Utility: Great for copying an application in its entirety – e.g. copying an application from Production into Test.

• Lifecycle Management: Great for migrating individual l t li ti i ti 5 belements among applications – e.g. migrating 5 web

forms from Test into Production or those items in addition to some Shared Services groups.

User Interface: Web Forms

• The context menu from Web Grids is now also available on Web Forms.

Reporting Annotations

• Annotations are commentary applied to a report by users. It allows users to share information about the report items.

Other HFM 11.x Items

• 64-bit processing support• Equity Pick-up Moduleq y p

– Utility for re-valuing investments in subsidiaries

• HFM System Reports (Intercompany, Journal) can be run into different outputs beyond HTMLrun into different outputs beyond HTML.

• PDF, Microsoft Word and Microsoft Power-Point files can be added to Financial Reporting books.p g– This will allow companies to more easily add commentary or

graphics and create reporting packages through Financial Reporting.p g

• Extended Analytics can export to a Flat File

New FDM Features & Functionality

FDM Drill-Back

• The ability to drill back from an HFM web grid or web form into FDM detail has existed for several releases (Right click, Audit Intersection.)• This will launch a new window that takes the user to the total

balance. From there, users can drill into the source members comprising the HFM balance.

Release 11 also offers the ability to drill back from Smart• Release 11 also offers the ability to drill back from Smart View and Financial Reporting into FDM.

• The user must be at a base level intersection in order for this to work properly.

FDM Security

• FDM is enabled to work with Shared Services. Starting with 11.1.1.3, you can not maintain external authentication providers in FDM (MSAD, LDAP, etc.)

Users are provisioned in Shared Services for FDM• Users are provisioned in Shared Services for FDM applications and FDM user levels.

• FDM Security still contains the location access by individual user and the assignment of specific FDM l t t l l (FDM bj t i t )elements to user levels (FDM object maintenance.)

FDM ERPi

• FDM ERP Integrator (ERPi) is new in Release 11.1.1.3. It provides 2 major functionalities:

ERPi streamlines the integration of metadata and data from select ERP– ERPi streamlines the integration of metadata and data from select ERP systems (e.g. PeopleSoft, Oracle E-Business Suite (EBS)) into target Oracle EPM systems (such as HFM and Planning.)

– ERPi provides drill-through capabilities from HFM and Planning intoERPi provides drill through capabilities from HFM and Planning into select ERP systems (e.g. PeopleSoft, Oracle EBS.)

• Although the capability to drill from HFM into FDM has existed for several releases, the capability to drill from FDM into the source , p yERP system via ERPi is new in 11.1.1.3.

• ERPi was built to provide a consistent integration from sourceERPi was built to provide a consistent integration from source systems to Hyperion tools. ERPi is similar to the functionality provided by some of the FDM, ODI, and EPMA source adaptors (e.g. the FDM Oracle EBS source adaptor.)( g p )

ERPi Drill-Back to Source System

FDM Timeline Viewer

• Ability to view user graphical layout.

FDM Migration

FDM Migration

• To upgrade from UpStream WebLink 8.x or FDM 9.3.1 through FDM 11:– Install FDM 11.x– Migrate the relational database to the new server– Migrate the App File Folders (Inbox, Outbox, etc) to the newMigrate the App File Folders (Inbox, Outbox, etc) to the new

server– Add the Application in FDM

Run the schema update– Run the schema update– Bring in new adapters / configure (same as a normal install)– If you have any custom Crystal Reports, they will need to be re-

itt A ti R twritten as Active Reports

• Migration from UpStream WebLink 7.x requires the usage of a special conversion utility.g p y

HFM Migration

HFM: Schema Update Utility

• Companies migrating to HFM 11.1.1.3 may have the option of using the schema update utility. The utility was designed for upgrading from the following versions:– 9.3.x– 9.2.19.2.1– 9.2.0.3

F i i i t 9 2 0 3 it ill b• For companies on a version prior to 9.2.0.3, it will be necessary to install and convert to 9.2.1 / 9.2.0.3 first, then to 11.1.1.3. This is because 9.2.0.3 / 9.2.1 are the only pre 9.3 versions supported with the schema update.

• This can all be done in a single environment.

HFM: Schema Update Utility

• Pros:– The utility migrates all log info, consolidation status,The utility migrates all log info, consolidation status,

and process level status. The application looks exactly the same after the utility runs – e.g. if something was not consolidated before running thesomething was not consolidated before running the utility, it will not be consolidated after running the utility.

– All journal information and process management information is preserved.If the compan is alread on 9 2 0 3 or a later release– If the company is already on 9.2.0.3 or a later release, and if the utility runs without errors, the conversion should be faster than Option 2 (manual rebuild.)

HFM: Schema Update Utility

• Cons:– If the company is on a release prior to 9.2.0.3,If the company is on a release prior to 9.2.0.3,

installing 9.2 as an interim step in the conversion process can be cumbersome and time-consuming.B i h i ili h– By running the conversion utility, the company may miss an opportunity to ‘clean up’ the application and database. For example, there may be hard zeroes or p , yother unnecessary clutter in the application that could be removed by doing a manual rebuild.

HFM: Rebuild Method

• Many companies opt to manually rebuild their applications by extracting and reloading security, lists, metadata, rules, data, journals, and application documents (web forms, web grids, etc.)

• This requires re-consolidation and re-promoting/locking for all prior years and periods.

HFM: Rebuild Method

• Pros:– No matter what release the company was previously using, there

is no need to install 9.2.1 or 9.2.0.3 as an interim step.– The manual rebuild is an opportunity to remove the ‘clutter’ from

the application. For example, you may decide not to migrate unused web forms, web grids, or even some of the older years of data. Entities and accounts that have not been used within the last 5 years are also often good candidates for clean-up.

– The manual rebuild can help you uncover some ‘surprises’ at a more opportune time than during a close. For example, it is possible that a recent metadata or rule change will impact hi t i l d t th t t lid t d t th ti thhistorical data that was not re-consolidated at the time the change was made. Discovering and resolving items such as this is better done during an upgrade than at a more inconvenient time such as a closeinconvenient time, such as a close.

HFM: Rebuild Method

• Cons:– Depending upon the volume of data and the volume of

‘surprises’ encountered when data is reloaded and reconsolidated, the manual conversion can take quite a bit longer than using the schema update utility.

– The manual rebuild does not convert log information. – Details related to journals and process management (e.g. User,

Time, etc) will be lost. Journals and process management in the new, rebuilt application will have the information from the person rebuilding the application.

– Converting the application documents (web forms, web grids, etc) as well as recreating their folder structures can also be time-consuming.

HFM: Hybrid Method

• The perfect approach – a hybrid?• This option entails using the schema update utility and p g p y

then subsequently cleaning up / reconsolidating the application.This allows you to keep your logs journal detail process• This allows you to keep your logs, journal detail, process management detail, etc while also removing the ‘clutter’ from your application and making it cleaner for moving forward.

• One element that would not be possible with the hybrid approach would be making changes to the applicationapproach would be making changes to the application profile (e.g. adding additional years for future data.)

Technical Considerations

64 Bit Computing

• HFM application servers with 64 bit processing are now supported. The HFM application server is the main processing component of HFM. Switching to 64 bit can significantly improve your performance times.• 64 bit processing allows for more memory to be utilized per64 bit processing allows for more memory to be utilized per

processor. With 32 bit processing, HFM is limited to 2GB of RAM per processor naturally (3GB if extended via changes.) 64 bit can allow for more.

• FDM does not yet have the ability to utilize 64 bit processing. FDM can be installed on a 64 bit server, but FDM will still only use 32 bit processing ThereforeFDM will still only use 32 bit processing. Therefore, using FDM on a 64 bit server will not improve FDM performance (all else being equal.)

Compatibility

• Internet Explorer 6 and Internet Explorer 7 are both supported for HFM and FDM 11.1.1.3.

• Internet Explorer 8 is not yet supported for HFM / FDM.• Microsoft Office 2007 is supported for HFM and FDM

11 1 1 311.1.1.3.• Windows Server 2008 is not yet supported for HFM and

FDM.• Microsoft SQL Server 2008 is not yet supported for HFM

/ FDM.• The TalleyRand release is expected to be the first

release that supports Windows Server 2008 and Microsoft SQL Server 2008 (Q1 2010 subject to change.)c oso t SQ Se e 008 (Q 0 0 subject to c a ge )

Project Planning

Pre-Project Decisions - Goals

• What are the key goals for the project?– For some companies, the only critical objective is toFor some companies, the only critical objective is to

get upgraded to the most recent release. This is sometimes referred to as a ‘technical upgrade.’F h h i k f i li d i i h– For others, there is key new functionality driving the upgrade.

– Sometimes cleaning up the application and evenSometimes cleaning up the application and even redesigning certain aspects is an important part of the project.

– Determining your full list of goals and prioritizing them with management will help you develop an accurate budget and timeline for your project.g y p j

Pre-Project Decisions - Technical

• Will we acquire new hardware for the new release?– If not, how will we manage during the conversion?

• It is highly recommended to use new hardware if possible. It takes time to uninstall, install and test the new release. A large risk exists if an ‘in-place’ upgrade is done as sufficient testing is needed to turn it liveit live.

– If so, how many environments will we build (Production, QA, etc?)Sho ld e change the ser er config ration in o r ne– Should we change the server configuration in our new environment(s) to improve performance?

• What exactly will we install?– Some companies choose to install items that they have not yet

decided whether to use. For example, you may still be unsure about enabling EPMA for your application but may decide to install it ‘just in case.’

Pre-Project Decisions - Goals

• How much testing will be required during the conversion?• Conversions that include manual rebuilds and application

changes tend to need more testing than straight schema updates.

• If you are acquiring new hardware, you may want to plan on you a e acqu g e a d a e, you ay a t to p a operforming connectivity testing and performance testing depending on the size of your user base and application.

• In most cases one parallel test may be sufficient• In most cases, one parallel test may be sufficient.• For a conversion that includes application changes, two

parallel tests may be necessary.• The decision point on parallel tests is how much is the end

user experience changing?

Pre-Project Decisions - Documentation

• How much documentation will be required related to the conversion itself?

• Do you need to create new disaster recovery documentation? Increasingly more companies aredocumentation? Increasingly, more companies are requiring full disaster and recovery testing being completed prior to going live. This includes all documentation and performing a complete recovery test.

D t t t d t ti th t h• Do you want to create some documentation that perhaps did not exist in the past (e.g. monthly close procedures, HFM maintenance guide, etc?)

Pre-Project Decisions - Training

• Will you need to retrain the users?• For a basic upgrade, a very brief training session (1-2 hours)

should be sufficient. The basic layout and functionality have not changed significantly from one release to the next. Web-based training seems to work well for this.

• If you are utilizing new functionality (e.g. Phased Submissions) then it may be necessary to conduct moreSubmissions) then it may be necessary to conduct more extensive training.

• The upgrade may be a good time to offer training as a ‘ f h ’ f h i k d th b i i th i iti l‘refresher’ for users who picked up the basics in the initial training but are not using the full functionality of the application.

Questions?

Thank You!

Robert Cybulski CPARobert Cybulski, CPAFinit Solutionsrcybulski@finitsolutions.com215 880 2025215-880-2025