FDMEE Data Integrations for

Hyperion Financial Management

Using Open Interface Adapter

Page 1
 Financial Data Quality Management, Enterprise Edition
Enabling Seamless Data and Metadata* Integration

Integration Strategy

 Develop direct “out of the box” integration

– Sources prioritized based on market demand
– Build using integration framework provided in FDM, Enterprise Edition (FDMEE)
– Table/View adapter to be available in 11.1.2.4
 Provide open interface adapter
– Available when out of the box integration not available
– Licensing modified to allow updates to ODI packages delivered with FDMEE
 Support file based integration
– Support data in any file format and majority of single and multi-byte encodings
 Complete coverage via direct, open interface adapter or file

Page 2
Supported ERP Source Systems

 EBS 11i and 12.x

 PSFT Financial Management 9.0, 9.1, 9.2
 PSFT HCM 9.0, 9.1, 9.2 to Public Sector Planning and Budgeting
 Fusion Financials GL 11.1.2 and 11.1.3
 JDE 9.0 and 9.1 with tools 9.1
 SAP 4.6c, 4.7 and ECC 6.0 enh 3+
– Prior to 11.1.2.3, certified on Oracle DB only (ERPI)
 SAP BW 7.0+
 Open Interface Adapter – Extends integration to any source!

The Open Interface Adapter is used to map data from the open interface table (AIF_OPEN_INTERFACE) to
the FDMEE staging tables. Typically, the Open Interface Adapter is used to load from a source not
supported with a pre-packaged adapter. The Open Interface Adapter eliminates the need to process and
manage data files, but the user is responsible for loading the table. Load methods include:

 Event script in FDMEE

 ODI
 SQL Loader
 anything

In the beginning, ERPi could be configured to work with FDM and as the product matured, it was
eventually combined with FDM into a single product called Financial Data Quality Management
Enterprise Edition (FDMEE - yep, the Q is still silent) FDMEE incorporates the architecture from ERPi to
integrate with various ERP systems through something called an adapter. To get access to these adapters
Oracle licenses an add-on to FDMEE called the "Adapter Suite" which includes various adapters that can
be used to integrate with specific ERP versions / vendors. If your ERP is not one of those supported "out
of the box" by FDMEE (the ERP-specific adapters included in the FDMEE adapter suite) then you may be
able to leverage another option from the adapter suite that is meant to fit the "all other" category. This
adapter is known as the "Open Interface Adapter" or sometimes shortened to "Open Adapter".

It is important to note that FDMEE uses Oracle Data Integrator (ODI) as the execution engine that
performs the extract, load and transform behind the scenes. (ELT is Oracle's take on ETL) The "Adapter
Suite" is essentially a library of prebuilt ODI projects, packages and interfaces supplied by Oracle (except
for SAP which is provided by an Oracle integration partner: Bristlecone) The Open Interface Adapter is
also a set of ODI objects, however, for this adapter specifically, the objects are meant to serve as a
starting point that should be first copied and then customized.

Page 3
Using the FDMEE Open Interface Adapter

Page 4
Open Interface Adapter – Overview

 An interface table in FDMEE that can be loaded with data from any source
(AIF_OPEN_INTERFACE)
 Typical use case is to load from a source not supported with a pre-packaged adapter
 Eliminates the need to process and manage data files
 The user is responsible for loading the table
 Load methods
– Event Script in FDMEE
– ODI
– SQL Loader
– Or Anything

Open Interface Adapter – Flow

 The Flow will show the following

– Open Interface Adapter Setup

– Usage of an event script to move data from a table in a separate database schema

– Single push button process to extract from source table, load to open interface table,
map, validate and load to a Planning application.

Open Interface Adapter – Processing Steps

1. Execute Data Load Rule

2. FDMEE Processes BefImport Script

– Data inserted in AIF_OPEN_INTERFACE from Z_OIA_SOURCE

3. Import process copies data from AIF_OPEN_INTERFACE to TDATASEG_T

Page 5
 4. Validation/Mapping processed and mapping results posted to TDATASEG

5. Remaining steps processed as needed

Loading the AIF_OPEN_INTERFACE Table

 Required Columns

– Batch Name, Currency, Amount

– The data rule uses batch name as a source table filter

 Use COL01-COL20 and ATTR1-14 as needed

 Year, Period and Period Num only required if using explicit calendar maps or multi-period loads

 For this document using default to the POV period, and will not load the time columns

Using ODI to Load the Interface Table

 ODI may be used as part of the restricted use license that comes with FDMEE

 Allowed to load the AIF_OPEN_INTERFACE table

 The content used for the event script may be re-used in ODI

 Create/Copy objects in ODI – do not update existing

 Include additional columns for drill-through URL parameters

 Columns for Desc1, Desc2, and Attributes loaded to TDATASEG

 Date columns required for multi-period or explicit data mappings

 Not required if defaulting to POV period

 The FDMEE license includes a restricted use license of ODI studio to modify the adapter as
needed to load the AIF_OPEN_INTERFACE table

Overview of Configure Open Interface Adapter using HFM

Page 6
Enter or load data in to the AIF_OPEN_INTERFACE table under FDMEE Schema

Before loading the data into Hyperion financial Management application (SIMCLASSIC)

Source System: Create a new source system

Page 7
The ODI context code refers to the context defined in Oracle Data Integrator. A context
groups the source and target connection information. For the Source system Type, select “Others,” and
for the ODI Context Code, enter the default “GLOBAL.” If the ODI has been set up differently from the
defaults, enter the appropriate ODI Context Code if it is not “GLOBAL.”

Register the Target Application (Financial Management Application)

From Source Adapter, Create new source adapter.

a. Provide a new adapter key. The adapter key is ten characters long. Once the adapter key has been
created, it cannot be modified.
b. Change the “Adapter Name” so that it is different from the copied adapter name. The adapter name is
used in pick lists, and needs to be changed so that the copied adapter can be distinguished from the
original adapter.

Page 8
Add Import format and Map the columns according to the AIF_OPEN_INTERFACE

On the Import Format screen, define a new import format.

a. Select the source system created in Source System and the adapter from Source Adapter.
b. Map the source columns to the appropriate target dimensions.

Page 9
When the import format mappings are complete, select Regenerate ODI Scenario. This step generates
the ODI Scenario based on the import format mappings.

Add Location referring the created import format

Page 10
Define period mapping which you are going to pull the data

Page 11
Define the Scenario view

On the Data Rule screen, define the new data rule

Page 12
On the Data Rule screen, define the new data rule.
a. Select the appropriate period mapping type. Provide a value for the batch name. The batch name is
used by the system as a filter on the open interface table. This enables multiple users to load data into a
single interface table but then segregate the data by the batch name.
b. Enter Y or N for the Delete Data After Import option.

Note: Defining Source Filter Options for the Open Interface Adapter .Before executing a Data Rule using
open interface adapter, you are required to have generated the Import Format’s ODI Scenario. Once the
ODI Scenario exists in the Execution Repository,you can execute the Data Rule any number of times.
 To define the source filter options for an open interface adapter:
1 In Batch Name, enter the name of the batch used to identify the data in the interface table.
2 In Record Type, specify whether to delete data after importing the data by selecting Y (for yes) or N.
To delete the data, select Y. To retain the data, select N.

Defining the Data Load Mappings and Rules Data load rule Data load mapping

Page 13
Note: Same way has to define data mapping for other dimensions.

Execute the Data Rule for Open Interface table to EPM Applications.

Page 14
Under Process Detail Tab:

After Data Load Rule successfully completed verify the Data and Drill through in Hyperion financial
Management Side

Page 15
Page 16
Note: Customizing the FDMEE Open Interface Adapter requires access to - and knowledge of -Oracle
Data Integrator Studio (ODI Studio. FDMEE by itself does not necessarily require a deep knowledge of
ODI but when you are implementing the Open Interface Adapter a good working knowledge of ODI is
recommended.

1. In the FDMEE repository, export the Open Interface Adapter Model and ERPI Target
Model folders.
2. In the FDMEE repository, export the Open Interface Adapter Project.

3. Create a new work repository with a new ID.

Use a repository ID of 900 or higher to avoid conflicts with Oracle shipped components. This is
your development repository when performing customization. It is referred to as the “custom
repository” in the following steps.

4. In the custom repository, import the model folders named: Open Interface Adapter
Model and ERPI Target Model.

5. In the custom repository, import the Open Interface Adapter Project.

6. Perform any customizations in the custom repository.

When customizing objects, do not modify FDMEE seeded objects imported from the FDMEE
repository. Instead, copy needed objects, use the“ Custom” suffix in names to identify them, and
then modify them.
For example, copy the “Open Interface Balances” package as “Open Interface Balances Custom,”
and make any edits to it.

7. Export customized objects (for example, Project, Packages, Interfaces) from the custom
repository and import them into the FDMEE repository.

8. Using the FDMEE Source Adapter user interface, copy the Open Interface Adapter to a new
adapter and complete the following:

 For the new adapter, provide a new adapter key. The adapter key can be ten characters
long. Once it has been created, it cannot be modified.

Page 17
  Make any necessary modifications to the Display Names. Display Name are shown in the
Import Format and Data Load Workbench.

 Specify the ODI Package Name and ODI Project Code as specified in the custom project.

Additional Resources

 FDM Enterprise Edition Documentation

http://www.oracle.com/technetwork/middleware/epm/documentation/index.html

 FDM Enterprise Edition Training

Link to Oracle University FDMEE Course

 Oracle Support

http://support.oracle.com

Page 18