finit webcast taking_fdm_to_the_next_level_052511_final

www.finitsolutions.com

The Finit Solutions Series:Taking FDM to the Next Level

May 25, 2011Scott [email protected]

http://www.finitsolutions.com/�

mailto:[email protected]�

www.finitsolutions.com- 2 -

The Finit Solutions SeriesThe Finit Solutions Series

Getting the Most out of FDM: Taking FDM to the Next Level

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

Finit Introduction

Financial Consolidation– Financial Management (HFM)– Hyperion Enterprise– Financial Close Management– Disclosure Management

Data Integration– Financial Data Quality Management

(FDM)– Oracle Data Integrator (ODI)– Data Integration Management (DIM)– Other (EPMA, ERPi, etc)

Planning and Business Intelligence– Planning– Essbase– Profitability & Cost Management

(HPCM)

BI+ Reporting Tools– Financial Reporting– Smartview– Web Analysis– Essbase Excel Add-in





• Finit consultants bring deep experience in external SEC reporting, tax reporting, and internal management analysis across a wide range of industries.

• Our backgrounds in accounting and reporting, combined with our product expertise, make us uniquely qualified to assist and advise clients on developing reporting packages that provide better insight and analysis for management.

• In addition to strong backgrounds in accounting and finance, the Finit consulting team has subject matter expertise related to Oracle EPM technical and infrastructure components. Our ability to know both sides adds value in areas such as environment strategy planning, product selection, deployment planning and overall infrastructure implementation activities.

• Finit is a member of the Oracle HFM, Planning, FDM and Hyperion Enterprise Customer Advisory Boards. In this role, we work directly with product development and quality engineering teams to address future product enhancements.

Finit’s EPM Expertise





We take client service very seriously and our results are unmatched in the industry:

Our client service approach has led to 100% customer satisfaction for every Finit client (136 and counting) for

every project (over 250 and counting).

Finit’s Client Service





•

Some Finit Clients


http://www.amwater.com/awpr1/default.html�

http://www.brinkscompany.com/�

http://www.csx.com/�

http://www.johnsoncontrols.com/�

http://www.spx.com/�

http://www.tyco.com/livesite/Page/Tyco/Home/?�

http://www.costco.com/Home.aspx?cm_re=1_en-_-Top_Left_Nav-_-Top_logo&lang=en-US�




About the Presenter

Scott Peters([email protected])

• Director of Data Integration Practice

• 6 years of experienceimplementing Hyperion products

• Has designed and implemented multiple FDM integrations with HFM, Enterprise, Essbase, Planning and Data Warehouses






How to Ask a Question





Purpose of this Webinar• To provide an overview of several situations where FDM

was enhanced to meet a certain business need. • These enhancements include:

– SmartMerge: replacing data from FDM without deleting the data that was loaded from data forms, Smart View, etc.

– Passing User Entered Parameters for scripts/task flows– Securing Scenarios for certain types of data loads (HFM specific)– Cross System Reconciliation– Loading non-financial data



SmartMerge

The Finit Solutions Series





Hyperion Issue• One frustration many companies have experienced is that Web

Form data gets ‘blown away’ if a user reloads the trial balance data as ‘Replace’. This can result in rework.

• Some companies have tried to get around this by creating multiple scenarios for Actuals, copying data back and forth, etc.

• FDM also has an option to protect data, but this involves creating a special custom dimension member that segregates data to protect and clear during an FDM load.

• There is a much simpler way to ‘protect’ any data that was entered into HFM via some method other than FDM (e.g. Web Forms, Smartview, etc.)

SmartMerge





FDM Submission #1Entity Account ValueFinit Solutions CASH 100Finit Solutions AR 200

Web Form Submission #1Entity Account ValueFinit Solutions STAT1 500

FDM Submission #2Entity Account ValueFinit Solutions AR 300

Finit Solutions CASH NODATAFinit Solutions AR NODATA

SmartMerge‘REPLACE’ will delete all of our Web Form

data. HFM would show only:Entity Account ValueFinit Solutions AR 300

‘MERGE’ will leave the CASH balance that has been reclassed. HFM would show:

Entity Account ValueFinit Solutions CASH 100Finit Solutions AR 300Finit Solutions STAT1 500

SOLUTION: SmartMerge will clear out CASH since it is not in our 2nd FDM load, but will keep STAT1 from the Web Form:Entity Account ValueFinit Solutions AR 300Finit Solutions STAT1 500





Details• SmartMerge is an FDM Event script that allows the user to load as

‘Merge’ while also clearing out the previously-loaded trial balance data for that Scenario, Year and Period.

• SmartMerge can be thought of as a ‘Replace’ in terms of how it handles trial balance data and a ‘Merge’ in terms of preserving supplemental data or data that was not loaded via FDM.

• The SmartMerge script was created by Finit and can be added to any FDM application and not just ones that integrate with HFM. It also works for Essbase and Enterprise.

• It has been implemented for nearly all of our ‘standard’ data loading clients and has been used for over 5 years.

SmartMerge



Passing User Entered Parameters to an FDM Script






Hyperion Issue• There has always been an issue in FDM where if a user needs to

run a Custom Script in FDM there is no way for users to enter parameters for that script.

• We can usually get around this situation by pulling parameters such as the POV or data that has been tagged to a location.

• However, if info needs to be entered that cannot be pulled from the POV or other areas of entry, a process can be created where FDM uses a table in the database as an entry screen and then will run a script.

Passing User Entered Parameters





Solution• Involves creating the following:

– Custom table in the FDM database to allow the user to input parameters– FDM Custom Script to display table– FDM Custom Script to run the script you wish (parameters are pulled from

Table)– Modifying the details of that table and how fields are displayed

• The process will then be seamless for the user to enter the parameters and then run the script.

Passing User Entered Parameters



Using FDM to Secure Scenario Loads to HFM






Hyperion Issue• There is a role in Shared Services that allows users to load data via

the Smart View function HSSetValue. Users are provisioned with this role if they need to enter data, such as Budget and Forecast data, via Excel.

• If those same users have ‘ALL’ access to the Actual scenario, they are also able to modify their Actual data via Smart View. This is usually not desired due to the lack of audit controls inherent in a Smart View data load.

• Several HFM security options were reviewed, including securing the Account and/or Scenario members but ultimately whatever intersections users need access to be able to load via FDM also allows them to modify that same intersection via Smart View.

Securing Scenarios for SmartView





Details in FDM• When connecting to HFM via FDM, the FDM integration adapter can be

configured for a ‘Unified’ or ‘Global’ connection.– Unified: FDM passes the individual user’s credentials so that their HFM access is

restricted according to their security configuration (i.e. if that user does not have access to an entity, FDM will prevent them from loading to it).

– Global: a “global” ID is stored in FDM and is passed to HFM when a connection is made. This ID would be configured to have access to all entities (i.e. if a user does not have access to an entity, they would still be able to load to it so long as the global ID had access).

• This integration setting applies to all connections being made by FDM. So if it is set to Unified, when FDM connects to HFM, the unified logon method is used.

• We considered using the ‘Global’ ID in FDM for all connections to HFM, but the risk existed that a user could map and load to an entity they don’t have access to because the global ID being used behind the scenes has access to all entities.






Solution:• Using a combination of Unified and Global• This involves a modification to the FDM Adapter that changes the

integration method from global to unified depending on the type of connection


Connection Reason Connection Type

Browse Maps – Account Unified

Browse Maps – Entity Unified

Browse Maps – ICP Unified

Browse Maps – Custom1 Unified



Browse Maps – Custom4 Global

Validate – Intersection Check Unified but Pass Custom4 of member that user can access

Export/Load Global

Consolidate Global





Solution:• We will use a Custom Dimension, essentially acting as a Data Type

(in our example we used Custom 4 and had TB and TBADJ for Actual loads).

• By making these changes, the individual’s user ID will be used to authenticate that they have access to all dimensions in HFM with the exception of Custom 4, which the global ID will be used for authentication.






Solution:• In addition, end users will NOT have access to two Custom4

members, TBFIN and TBFINADJ. Only the FDM admin account (Global ID) will have ALL access to these members. This will prevent any user from writing data to these intersections from outside of FDM.

• End users will, however, have access to the other members of the Custom 4 dimension, which they can use when loading their Stat or Budget and Forecast data from Smart View.




Cross System Reconciliation






Hyperion Issue• When using both HFM and Essbase/Planning, there has never been

a good way to easily move data between applications and preserving the integrity of that data.






Solution• The Cross System Reconciliation process is a custom solution that

reconciles the data between Essbase and HFM. • The process involves extracting data from each application, and

loading that data into FDM. • FDM then flips the sign on the Essbase amounts, and ‘squeezes’

together common intersections of data from each application, leaving a difference at each common intersection.

• That difference is then loaded from FDM back into Essbase. After the process is completed, the data in HFM and Essbase is in sync.






Solution• The data is extracted from both HFM and Essbase at common

intersections.• The FDM Batch Loader is used to load data to FDM from both

systems.• The data is loaded to 1 FDM location (Essbase extract first, HFM file

second).• Because there are common intersections, the data squeezes

together and any differences are loaded to Essbase.




Loading Data other than General Leger Data






Details• FDM can be used for more than just loading General Ledger data to

Hyperion Target systems.• Examples include storing HR data or Project Point of Contact

information.• FDM has 35 storable dimensions and more can be created by

storing 2 or more pieces of data in a dimension.

Non-GL Data through FDM





HR Data Details• FDM was configured to handle loading of multiple dimensions (56

Dimensions Total):


• SSN• Name• Home Address• Employee Start Date• Leave Reason• Salary

• Job Title• Leave Date• Termination Reason• Benefit Effect Date• FT/PT• Pay Frequency

• Data was loaded via FDM Excel Templates.





HR Data Details• Validations were developed to ensure data was entered correctly.

– Could either stop the load from processing or simply warn the user of certain validation errors.

• Email Alerts were generated to provide a status of the loads.• End User/Admin reporting out of the FDM Database was created.• Benefits include:

– Central data repository for all locations, giving all users one place to load their files.

– Utilize multi-dimensionality capabilities of FDM to allow for the storing of 55 unique fields of information.

– 50+ validations were performed on the submitted data.






Point of Contact Project Reporting• FDM would be the book of record for all jobs but would also load

some details with cell text to HFM.• Approximately 28 dimensions are being used to store such info as

Customer Name, Contractor, Start Date, End Date, Contract Price, Costs, etc.

• The Jobs are also ranked 1-15 and some details on those jobs are loaded to HFM.






Point of Contact Project Reporting• The data is loaded via an FDM Excel template, which has a few

calculations that are loaded to FDM as checks.• Also, several validations are built in to FDM to prevent the user

from loading incomplete data (i.e. make sure that the end date is after the start date or that the other fields are complete).

• FDM then takes the top-ranked 15 jobs and adds records to FDM that will be loaded to HFM.

• Several reports were written in FDM to help end users view a month-over-month squeeze of this data.




Contact






Upcoming Webinars (Dates to be Announced)• EPM 11.1.2.1: New Features, Fixes, and

Functionality• Troubleshooting Tips for HFM and FDM• Troubleshooting Tips for Essbase and

Planning• Introduction to Financial Close

Management• HFM for the Tax Department

To register, or to view past sessions, go to: www.finitsolutions.com/Insights_Webcast.html

Finit Contacts & Upcoming Webinars

[email protected]

-> Scott [email protected]

-> Ed [email protected]>Joe [email protected]


http://www.finitsolutions.com/Insights_Webcast.html�





finit webcast taking_fdm_to_the_next_level_052511_final

Technology

finit client

levelsome finit

levelfinit solutions

finit consulting team

level finit consultants

multiple fdm integrations

internal management

tax reporting