Data Integration with Hyperion and Why this is Important - An Understanding of FDMEE and Drillback

1. REMINDER
Check in on the
COLLABORATE mobile app
Data Integration with Hyperion and
Why this is Important
Prepared by:
Russ Rogers
EPM Practice
Emtec Inc.
An Understanding of FDMEE and
Drillback
Session ID#: 10169

2. Introductions
What is FDMEE
Upgrade Considerations
Process Elements
Understanding Drill Through
FDMEE Next Steps
Q & A

3. Introductions
Reid Kerr
Senior Lead – Close & Consolidations, Emtec
• 21 Years of hands on consulting experience
• 8 Years at Hyperion (IMRS, Software, Solutions, etc.)
• 12 Years Partner and Independent Firms
• Hyperion Certified (background in accounting, fx, m&a)
• 336-996-4242 office / 336-210-6934 mobile (Go TarHeels!)
• Reid.Kerr@emtecinc.com
Russ Rogers
National Practice Lead – Close & Consolidations, Emtec
• 22 Years of hands on consulting experience
• 9 Years at Hyperion (IMRS, Software, Solutions, etc.)
• 12 Years Partner and Independent Firms
• CPA, CMA, Hyperion Certified (accounting, fx, IC, m&a)
• 312-561-3398 office / 816-721-1908 mobile (Go Jayhawks!)
• Russell.Rogers@emtecinc.com

4. What is FDMEE ?
This is a subtitle or bulleted list

5. Financial Data Quality Management-Enterprise Edition
■ FDMEE is available beginning with EPM 11.1.2.3.x

6. Financial Data Quality Management-Enterprise Edition
■ FDM and ERP Integrator combined into a single product
■ Based on ODI with the FDM process wrapper. Combines the
platform strength of ODI, with time tested process and methodology
of FDM
■ Windows Based FDM still available for existing customers
▪ 11.1.2.3 is terminal release of FDM
▪ Upgrade in place for the last time
▪ Migration to FDMEE required starting with 11.1.2.4
■ New Customers may only license FDMEE
■ All new implementations are recommended to occur in FDMEE

7. Financial Data Quality Management-Enterprise Edition
Improvements in 11.1.2.3
■ Integrates security with Shared Services
■ Simplifies maintenance and development through different
workflows
■ Reduces need for custom scripting for most straight forward tasks
■ Is certified with PeopleSoft 9.2
■ New Customers may only license FDMEE going forward

8. Financial Data Quality Management-Enterprise Edition
Improvements in 11.1.2.4
■ Can now specify target application options specific to a location
■ Easily move data between the EPM applications irrespective of the
dimensionality of the application without having to create a data file from
the EPM source application.
■ Supports write-back from all EPM applications (except the Accounts
Reconciliation Manger) to Enterprise Resource Planning (ERP) applications
■ Enables you to map source fields graphically to target dimension members
■ Can view mapping errors and fix them instantly when mapping errors have
occurred in the Data Load Workbench
■ Can now launch the Data Load Workbench component of FDMEE and
manage data load activities in Financial Close Management.
■ Can concatenate an unlimited number of ERP segments and define
mappings on the concatenated code combinations

9. Upgrade Considerations

10. Financial Data Quality Management-Enterprise Edition
■ Classic FDM has some limitations that are now covered by FDMEE
▪ For example, when multi-dimensional mappings were needed, most of
the people used mapping scripts
 Difficult to maintain and understand
 Black Box
 Upgrade Considerations (Understatement of the year)
▪ In FDMEE, we have a new mapping type called Multi-Dimensional
mapping
 New mapping type will probably replace all your mapping scripts
 In addition, you can use look-up dimensions in FDMEE to support your multi-
dimensional mappings

11. Financial Data Quality Management-Enterprise Edition
■ Classic FDM required separately maintained locations to enforce
even slightly different mapping schemas or sources
▪ The more locations you have, the more you will have to maintain
▪ Data load rules allow you to simplify your location structure. Two
locations for two different file types may be replaced by one location and
two data load rules having each one import format
▪ Can share related mapping further reducing maintenance
■ Import process is almost always the bottle neck in Classic FDM
▪ Mapping process is performed during the import process and 90% of the
customers having performance issues during import follow this rule:
Wrong mapping logic design -> poor performance during import
▪ Better performance with large data sets
▪ Redesigning your artifacts will improve maintenance efforts and workflow

12. Financial Data Quality Management-Enterprise Edition
■ You will have to re-write your scripts (import, mapping, event, and
custom)
▪ Even if you keep VB for event and custom scripts, you will have to do
some changes as VB Script is replaced by VB .NET
▪ Event and custom scripts best written in Jython
• Import scripts (dump) support Jython only
• Integration scripts are not supported anymore as import scripts so they need to
be implemented in BefImport event script (Jython or VB .NET)
• VB mapping scripts are not supported anymore so you will have to re-write
them as Jython or SQL mapping scripts (or replace by multi-dimensional
mappings)
■ Great opportunity to review your code which sometimes is not as
efficient as you think
■ Commenting your code - do it now

13. Financial Data Quality Management-Enterprise Edition
Upgrade from 11.1.2.3 to 11.1.2.4
■ These items were covered in slide 8

14. Process Elements
This is a subtitle or bulleted list

15. Financial Data Quality Management-Enterprise Edition
File
Excel
XML
Other
Systems
Oracle EBS,
PeopleSoft, JDE, Fusion
APPs, SAP R/3
Data Warehouse
Data Mart
Data Strategy Management
Financial Close
Planning &
Forecasting
Profitability
Management
Financial Reports
Microsoft Office
Data & Metadata
Drill-Through & Write-Back
Web Interface
Meta-
data

16. FDMEE Supported Target EPM Platforms
■ FDMEE supports the following EPM target applications
(Oracle Hyperion EPM Architect and Classic):
▪ Planning and the Planning Modules
▪ Public Sector Planning and Budgeting
▪ Financial Management
▪ Profitability and Cost Management (HPCM) and Tax Provision
▪ Essbase BSO and ASO
• If Essbase has been deployed in standalone mode, it must be registered with
Shared Services since it does not work directly with FDMEE
▪ Planning applications that rely on the standalone Essbase application
cannot work directly with FDMEE

17. Process Elements
• FDMEE is accessed directly from Workspace.
• Security managed through Shared Services

18. FDMEE is now directly linked to sources–regardless of type
■ FDMEE Is now directly linked to sources – regardless of type
■ Focuses on workflow with artifacts used to support it
• Define the Data/Metadata Source
• Define the Target Application
• Define the Source Accounting Entity
■ 11.1.2.4 Considerations
• Supports write back from all EPM applications
• Doesn’t require data files to transfer between EPM applications
• Supports the Oracle Hyperion Profitability and Cost
Management (HPCM) and Tax Provision Application

19. FDMEE is now directly linked to sources–regardless of type
• Data can be pulled from multiple types of sources.
• Adaptors no longer need to be downloaded as several are
integrated within FDMEE.
• Of course, importing from flat files and other types are available
along with other EPM applications (think Planning to HFM, for
example).
• These sources can be used for loading and drill through, allowing
destination applications to have a link back to the data details
contained within the source system.

20. FDMEE is now directly linked to sources–regardless of type
• Target application and types (HFM, Planning, Essbase) are
also easily identified along with their necessary components for
mapping purposes.
• Available fields of the application are brought in for both the
source and target systems, thus allowing ease of mapping.
• No need to configure multiple adaptors

21. Process Elements
■ After the source systems have been identified, the following items are
identified:
• The ledger or business unit (accounting entity) to use
• The Chart of Accounts
• Currency
• Calendar
• Responsibility name.

22. Process Elements
• Period Mapping still exists but now more flexible and can be
shared
• Category Mapping still exists but now reads directly from target
application

23. Process Elements
This is the last version of FDM using VB for all scripts, Jython will be
the go-forward strategy with FDMEE for most scripting needs.
Workflow menu Setup menu

24. Process Elements
Finally:
Yes, the fish still exist…..

25. Understanding Drill-back
This is a subtitle or bulleted list

26. FDMEE Supported Platforms
■ FDMEE allows drill thru data sourcing from the following ledgers
• File-based data loads that enable users to import balances from delimited or fixed-
width text files.
• Oracle E-Business Suites11i and 12
• Oracle Fusion Financials
• PeopleSoft Enterprise Financial Management 9.0, 9.1 and 9.2
• PeopleSoft Enterprise Human Capital Management (HCM) 9.1
• PeopleSoft Commitment Control
• SAP ERP Financial and BW (Business Warehouse)
• JD Edwards General Ledger system
■ FDMEE supports Human Resource Data for
• PeopleSoft HCM 9.0 and 9.1

27. FDMEE Technical Setup for Drill Thru
■ Basic technical steps for setup:
• Every setup is different, planning your upgrade is critical. Collaboration
with DBA and source system administrator is critical as well.
• Have DBA setup proper permissions to tables and views for the source
system as listed in the on the FDMEE admin guide:
https://docs.oracle.com/cd/E40248_01/epm.1112/erpi_admin_11123520.
pdf
• Once table permissions have been set, FDMEE admin needs to log into
ODI and enter the database details for the source system
• Once ODI has been updated, the FDMEE admin needs to create a
source system in FDMEE and they need to add a URL for drill-through to
work
• Once the source system has been created, it needs to be initialized

28. FDMEE Technical Setup for Drill Thru
■ Basic technical steps for setup:
• The tricky part of the setup is the initialization which is where you will find
out whether DB permissions for the source system were set properly.
Most errors during this step will be located in the ODI logs, not FDMEE
since ODI is the one performing the integration
• In most cases, synonyms in the database side will be required
• If the initialization is successful, you should see a green check mark for
the step in the FDMEE process details
• Once initialization is complete, admin can start creating import formats,
mapping tables, etc. to complete the integration

29. FDMEE Drill Back – How it Works
■ Drill Back is allowed from a base level data point to the source load and then
to the source system
• Data is only loaded at base level – you can only drill from that level
• Drill Region is enabled on the load
• Drill Back is allowed from any enabled hyperlink: FRS Reports, SmartView, Grids,
Forms
■ The First Drill Back is from the target application to the load POV in FDM
• This allows the user to see the various loaded components
• Helps allow mapping and or formatting to answer the question
■ The second drill back launches a prepopulated query to your selected URL
• e.g. PeopleSoft 9.2 launches the Oracle login to the system and prepopulates the
detailed query screen
• Allows access to journal detail
■ Table assignments can be changed using synonyms

30. Next Steps
This is a subtitle or bulleted list

31. 1.2.4 updates
■ Review scripts used in the current application
■ Review mapping tables in place and purposes
■ Review sources and destinations of data transfers
■ Discuss historical data needs for Drill Through
■ Review technical architecture

32. FDMEE – Next Steps
■ Plan your Upgrade
• Goals and timelines
• Affected Other Parties
• All products and platforms
■ Engage your services provider
• Time to review processes?
• Technical matters
• Server environments
• Workstation Environments
• Time to Re-design
■ Build Momentum for change
■ Get the Benefits

33. Questions ???????????
(and hopefully some answers)
This is a subtitle or bulleted list

34. Please complete the session
evaluation
We appreciate your feedback and insight
You may complete the session evaluation either
on paper or online via the mobile app