collab08 fdm beyond consolidations speters

8/6/2019 Collab08 FDM Beyond Consolidations SPeters

1/54

Orac le Hyper ion FDM Power fu lUses Beyond Financ ia l Consol idat ions

Scott Peters

Finit Solutions

[email protected]


2/54

Disc la imer

These views are solely of the views of FinitSolutions and do not reflect the views ofOracle.

In the referencing of future releases of OracleHyperion Financial Data Quality Management(FDM), the details are not official releasenotes.


3/54

About Fin i t So lu t ions


4/54


FINance-IT Hyperion Preferred Partner and a Member of

the Oracle Partner Network (OPN)

Recognized in the 2007 Inc 500 as the 42nd

fastest growing IT services company theonly Hyperion partner to make the list

Website:www.finitsolutions.com


5/54


Hyperion Financial Consolidations and

Reporting Experts

Specializing in Hyperion Financial DataQuality Management (FDM), Hyperion

Financial Management (HFM), and HyperionEnterprise (HE)

Strong focus on providing superior customer

service and value by providing Hyperionexpertise, strong Finance / Accounting

knowledge and a proactive approach.


6/54

Som e of our c l ient s


7/54

Purpose of t h is Session


8/54

Purpose of t h is Session

Provide an overview of Hyperion FDM. Discuss some of the traditional and emerging

uses of Hyperion FDM.

Showcase some of Hyperion FDMs new andfuture enhancements.

Discuss the business case of FDM with

consolidation and non-consolidation systems. Hyperion FDM integration and customization

examples.


9/54

Hyperion FDM Overview


10/54

What is Hyper ion FDM?

Packaged application for Financial Datamovement from any data source to any Hyperionapplication (Enterprise, HFM, Essbase, Planning,etc.)

Archives all dimensional mapping from sourcesto target

Complete transparency / audit trail for all dataand user processes

Built for business users to administer andmaintain

Unique product in industry


11/54

Hyper ion FDM Benef i t s

Reduces Risk

Transparency into data and processes

User Friendly Interface

Out of the box application approach Web Architected

More Efficient

End Users load quickly Questions answered


12/54

Hyper ion FDM Benef i t s Cont .

Flexible

Can read any file from any system

Validation rules by location to ensure

quality Capture all supplemental data

Can load HFM, Enterprise, Planning,

Essbase, HSF


13/54

Hyper ion FDM Benef i t s Cont .

Sarbox Compliant

Standardized controls

Transparency / Audit trails

Sarbanes Oxley 302 sub certification


14/54


15/54

Tradi t iona l and Em erg ing Uses of

Hyper ion FDM


16/54

Hyper ion FDM for Consol idat ions

Companies originally purchased FDM for the benefits

associated with loading to a consolidation system Controlled process

Ownership and responsibility on sites for their data

Data Quality Data has to be right and Actualdata has increased Sarbox requirements

Submission of Trial Balance and Supplementalinformation

Sarbox Requirements Hyperion FDM was designed to handle loading from

multiple sources and users


17/54


18/54

Previous Foc us


19/54

New Foc us - Cons is tenc y


20/54

FDM Produc t Enhanc em ent sCurrent Release

Additional Dimensions 23 map-able dimensions

14 attribute dimensions

Batch Loader has been improved

Hyperion FDM performs true Lights Out and Auto-Map processing

Email notifications

Can also move data between Hyperion apps,especially if mapping and a transformation needsto take place


21/54

FDM Produc t Enhanc em ent s Cont .Current Release

Tax Extract Adaptor Allows organizations to dump source and target

balances into a text file format that can then beloaded into a target Tax System

Data Mart Adaptor Allows users to map and validate data when going

to a non-Hyperion source such as a DataWarehouse

Used to map source data to common metadatamembers or formats


22/54

FDM Produc t Enhanc em ent s Cont . Fut ure Releases

Oracle Financials E-Business Suite adaptor Source adaptor to pull and drill back into

transaction level detail should be available in thenext release. PeopleSoft and JDE sourceadaptors are on the product roadmap.

Drill-back from Hyperion systems to source Customers will be able to drill back from Hyperion

systems (Planning, HFM, Essbase, HSF) to FDM

(containing ending balances) and then eventuallyto Oracle Financials, PeopleSoft and JDEtransactions.


23/54

FDM Produc t Enhanc em ent s Cont .Fut ure Releases

Hyperion Strategic Finance (HSF) Adaptor A target adaptor for Hyperion FDM to load to HSF

should be available in the next release.

Integration with Oracle SSO

Integration with Oracle SSO is planned for thenext release.


24/54

Business Case for FDM


25/54

Bus iness Case for FDM

Varying levels of data detail

Standardization of data loading to differenttarget systems (BI, Tax, Consolidations)

Centralized data repository

Audit trail detail is maintained Varying data loading methods (manual v.

automated)

Source and target analytic capabilities acrosssystems

Improved ROI consistent data approach


26/54

FDM Int egrat ion t o Essbase

Example


27/54

FDM Essbase In tegrat ion

The following example will demonstrate anintegration to Essbase that uses FDM to loaddata

This example will also add members to theoutline that are in the data file but are not yetin the Essbase outline


28/54

FDM Essbase In tegrat ion

When Integrating to Essbase/Planning, mostof the FDM functionality is the same as HFMor HE, but there are some key differences inthe way that FDM is set-up

We will take a look at the following

Adaptor Modifications

Integration Options

Additional Adaptor Modifications (Actions)


29/54

FDM Essbase Int egrat ion Adapt or Modif i c a t ions

Unlike HFM and Enterprise where theDimensions are always the same, Essbaseand Planning can have different dimensions

FDM needs to be set-up to match an FDMdimension with an Essbase/Planningdimension


30/54



31/54

FDM Essbase Int egrat ion In t egra t i on Opt i ons

One Integration Setting that is unique toEssbase/Planning is the Load Rule Name

This allows us to load the data to Essbaseusing an Essbase Load Rule that is stored onthe Essbase Server


32/54


Why might we use a Load Rule to load toEssbase through FDM?

There are 2 main reasons

Improve Performance

Manipulate the data as it is loading to Essbase


33/54


Using a Load Rule to Improve Performance

Performance of an Essbase load can be improvedby manipulating the .dat file that is being loaded toload the sparse dimensions first followed by the

dense dimensions If this option is chosen, the .dat file will need

to be modified (More to follow in the Export

Action Modifications)


34/54


Using a Load Rule to Manipulate data as it isbeing loaded

This is probably more rare, but you may need toflip the sign of data or multiply the data by a factor.

The Load Rule would give you a way to controlthis outside of FDM if you prefer


35/54


In addition to the earlier modifications that

needed to be done in the Adaptor, there areseveral more complex modifications.

These include modifying the code for the

following FDM Actions

Export

Load

Consolidate


36/54


What is the Export Action

This is where the .dat file is produced that will getloaded to Essbase/Planning

Why this might need to be changed?

If a Load Rule was specified in the IntegrationSetting, the order of the dimensions may need tobe changed


37/54

FDM Essbase In t egrat ion Adapt or Modif i c a t ions

How to change Export Action


38/54


What is the Load Action

This is where the .dat file gets loaded toEssbase/Planning


Essbase does not have an inherent Clearcommand, it needs to be done in a Calc Script

Here you can determine what slice of the

database gets cleared before data is loaded


39/54


Below is a sample Clear Calc Script that can

be coded in the Load Action

Here we are fixing on variables that are in thePOV in FDM, so that we dont clear data thatis not in that POV


40/54


What is the Consolidate Action

This is where the calculations of the database areperformed


Essbase also does not have an inherentConsolidate or Calc like HFM, it needs to be donein a Calc Script

Here you can determine what section of thedatabase gets calculated


41/54


Below is a sample Calc Script that can be

coded in the Consolidate Action

Again, like the Clear script, we are fixing onvariables that are in the POV in FDM, andCalculating that piece of data


42/54


We can also have different Calc Scripts run

for different locations, categories, or anythingelse in the POV

This could come in handy if you are loading

different types of data and need to rundifferent calc scripts


43/54

FDM Essbase In t egrat ion In t ersec t ion Chec k Report

When Integrating with HFM, there is a built-in

Check report that looks to HFM to make surethe data that is going to be loaded is valid

When Integrating with Essbase/Planning,

there is no built in check report.


44/54


This is an important piece to have in place,

otherwise when data is loaded to Essbase ifthere are invalid members you will get a whiteExport fish

Built a script that once all source membersare mapped, FDM looks to the outline tomake sure that all members that are being

loaded exists in the outline


45/54



46/54

FDM Essbase In t egrat ion Cont .

Here is the sample outline


47/54


Here is a sample data load file that we will

load through FDM It contains the Product as well as its attributes

If we look at the outline, these two lines arenot in it. (100-40 and 600-10)


48/54


We now import the file to FDM using our

predefined Import Format


49/54


We can then Validate the Imported data

against our mapping table in FDM After all of the data transformation occurs,

FDM looks at the data and compares it to the

Outline in Essbase If members exist in the data load file that do

not exist in Essbase, they will be written to a

text file and loaded to the outline in Essbaseusing an esscmd to call a script in which a

load rule and file is referenced.


50/54


After the metadata gets loaded to Essbase, a

message box will be displayed in FDMnotifying the user that new members havebeen added to the outline


51/54


We can now look back at the outline to see

the new members that were added


52/54


The user will now click Export in FDM and

load that data to Essbase At that time, Calc scripts can automatically be

run to clear data and calculate data

These Calc scripts can be dynamic and canuse any variables in the FDM POV or load fileto Fix on


53/54

FDM as m ore o f an ETL Tool?

A little background on a project that did this

Data extracted from SAP and loaded to a StagingTable via FDM Script

Data is cleansed using SQL via FDM Script

Data is Extracted from the Staging table, written to.dat files and Loaded to HFM using the FDM BatchLoader


54/54

Quest ions

collab08 fdm beyond consolidations speters

Documents