Oracle® Financial Data Quality Management ERP Integration Adapter for Oracle Applications, Fusion Edition

Release ERPI-FIN-A2

Readme

Purpose. 1

Overview.. 1

Installation. 2

Configuration. 2

Using the Adapter. 3

Tips and Troubleshooting. 4

Known Issues. 4

Notes. 5

 

Purpose

This document includes important, late-breaking information about this release of the Oracle® Financial Data Quality Management (FDM) ERP Integration Adapter for Oracle Applications, Fusion Edition (ERP Integrator). Review this information thoroughly before installing the adapter.

Top of Document

Overview

The FDM ERP Integrator is a component of FDM that allows users to do the following:

·         Integrate metadata and data from an Enterprise Resource Planning (ERP) source system into an Enterprise Performance Management (EPM) target application.

·         Drill through from the EPM target application and view data in the ERP source system.

Date Created:               8/5/2011

Adapter Versions:          ERPI-FIN-A2.xml

                                  fdmERPi_FINA2.dll

Compatibility:                See the FDM 11.1.1.4 Readme for FDM compatibility information.

Top of Document


 

Installation

This section includes important information about installing this release of the ERP Integrator adapter.

Note: Oracle Data Integrator (ODI) must be installed before adding the FDM ERP Integrator adapter. ODI is downloaded from Oracle E-Delivery, and is installed separately from EPM. See the ERPI Administrator’s Guide for ODI configuration information.

> To add the adapter to an FDM application:

1.   From FDM Workbench, open an FDM application.

2.   Select the Adapters tab.

3.   Select File > Import.

      The Open Metadata Import File dialog box is displayed.

4.   Browse to find the file named ERPI-FIN-A2.xml and click Open.

5.   Click OK.

           The FDM ERP Integrator adapter is displayed in the list of imported target adapters.

6.   Select File > Register Adapter.

      The Register Adapter dialog box is displayed.

7.   Browse to find the file named fdmERPI-FIN-A2.dll and click Open.

8.   Click OK.

Top of Document

Configuration

> To configure the adapter:

1.   In FDM Workbench, from the Adapters tab, select the adapter.

2.   Right-click and select Options.

      The Adapter Options dialog box is displayed. The Options menu enables you to select any of the options and change the option settings.

3.   Set the adapter options per the guidelines in the following table:

Option Name

Information Required

ERPI Webservice

URL and port number of the server where ERP Integrator is installed. For example localhost.com:19000.

Use SSL

On/Off switch to indicate to FDM if SSL is used for the for the ERP Integrator Web service.

ERPI Data Rule Name

Name of the data rule to be executed in ERP Integrator.

ERPI Default Dimensions

Dimension names to be pulled from the source system (source systems defined ERP Integrator). Use semicolon (;) as a delimiter between dimensions (optional). Example: Version;Scenario.

ERPI Default Members

Member names to be pulled from the source system (source systems defined ERP Integrator). Use semicolon (;) as a delimiter between members (optional). Example: Working;Actual.

ERPI Plan Type (For Planning Applications Only)

Name of plan type in to integrate with in ERP Integrator.

ERPI Exchange Rate Flag

On/Off switch used to indicate to ERP Integrator to include exchange rate information in the file loaded from ERP Integrator to FDM (optional)

ERPI Exchange Begin Rate Type

Required only when ERP Integrator Exchange Rate Flag is enabled.

ERPI Exchange End Rate Type

Required only when ERP Integrator Exchange Rate Flag is enabled.

ERPI Exchange Average Rate Type

Required only when ERP Integrator Exchange Rate Flag is enabled.

Enable Drill Through

On/Off switch to enable drill through from FDM to the source system.

File Prompt

Not used. Always keep unchecked.

ERPI Execution Mode

The default value is SNAPSHOT. This option should not be changed unless the following condition occurs:

·         Due to web service time-out issues in ERPI, Data Rules get resubmitted and results in doubling of data. When this happens, the execution mode value should be changed to FULLREFRESH.A subsequent execution of the data rule with FULLREFRESH as the execution mode will clear the data and reload it.

Top of Document

Using the Adapter

Using the ERP Integrator adapter involves the following four steps:

1.    Map FDM Periods to the source system periods.

2.    Create import format group and generate the data from the source system.

3.    Set up an import format in FDM to enable FDM to import the data file generated by the adapter.

4.    Assign the Import Formats to a location.

 

>  Step 1: Map FDM Periods to the source system periods.

Note: Adapter options must be set per the guidelines outlined in the previous section of this document.

a)  In the FDM Web client, select Metadata > Control Tables.

    The Control Tables screen is displayed.

b)  From Adapter, select ERPI-FIN-A2.

c)  Map the FDM Periods to the corresponding source periods:

- Use the Target Per (M) column in the control table to map the source Period.

- Use the Year Target column in the control table to map the source Period Year.

>   Step 2: Create import format group and generate the data from source system:

a)  In FDM, create an import format group and set the type to Adapter, then select the ERP Integrator from the drop-down list.

           See the FDM Administrator’s Guide for information regarding import formats.

b)    From the Locations screen, select the location into which you want to import data.

c)    Assign the import format created in Step 2a to the location.

Note: This is required to launch the import in Step 2f.

d)    Select the WorkFlow Behaviors tab.

e)  Select Workflow > Import.

    The Import screen is displayed.

f)    Select the Upload File tab.

g)   Click Import to generate the source file from the source system (via ERP Integrator data rule).

      You will use this file to create the import format in the next procedure.

 

>   Step 3: Set up an import format in FDM to enable FDM to import the data file generated by the adapter.

>  Step 4: Assign the Import Formats to a location:

a)  Select Metadata > Locations.

b)  Select the location selected in Step 2b.

c)  Select the Integration Options tab.

e)    In the Option 1 field, enter the name of the import format defined in Step 3 and click Save.

Top of Document

Tips and Troubleshooting

The data file generated as a result of the adapter executing an ERP Integrator data rule will, by default, be placed in the FDM Application’s Inbox directory. As part of the ERP Integrator /ODI setup, ensure that the ODI Windows Service is running under a domain service account. Subsequently, the service account running the ODI service must be assigned read/write access to the FDM folder structure.

Top of Document

Known Issues

Setup Requirement to Enable Drill Through

Problem: The drill through function fails to enable after importing the adapter. This happens because no record has been created in the tPOVCategoryAdapter table.

Solution: After importing the adapter, perform the following to create a record in the tPOVCategoryAdapter table:

1.    In the Web client, open the application.

2.    Navigate to the Control Tables screen.

3.    Select the ERP Integrator.

4.    From the Control Table drop-down menu, select Category.

Top of Document

Notes

·         See the FDM 11.1.1.4 Readme and the Oracle Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator’s Guide for additional information.

Caution!

Extensive problems can occur if you switch the ERP system connection information for the Physical Schema in the Oracle Data Integrator Topology Manager after you have completed initial configuration. For example, extensive problems can occur if you start using one physical schema (ERPTEST) pointing to ERP Test Instance1 in the Oracle Data Integrator Topology Manager and then change to a connection information in this physical schema to point to ERP Test Instance2 without first creating a new context in Oracle Data Integrator. The correct procedure is to create two physical schemas (ERPTEST1 and ERPTEST2) each pointing to a different ERP instance. Then, create two contexts and associate the appropriate physical schema to the logical schema in the context.

Top of Document

 

Copyright © 2011, Oracle and / or its affiliates. All rights reserved.
http://www.oracle.com