19 Oracle Hyperion Financial Management

19.1.1 Integration Process

You can use Oracle Data Integrator Adapter for Hyperion Financial Management to perform these data integration tasks on a Financial Management application:

• Load metadata and data

• Extract data

• Consolidate data

• Enumerate members of member lists

Using the adapter to load or extract data involves these tasks:

• Setting up an environment: defining data servers and schemas

  See Section 19.3, "Setting up the Topology".

• Reverse-engineering a Financial Management application using the Reverse-engineering Knowledge Module (RKM)

  See Section 19.4, "Creating and Reverse-Engineering a Financial Management Model".

• Loading metadata and data using Integration Knowledge Modules (IKM)

  See Section 19.5, "Designing an Interface"

• Extracting data and members using Load Knowledge Modules (LKM)

  See Section 19.5, "Designing an Interface"

19.1.2 Knowledge Modules

Oracle Data Integrator provides the Knowledge Modules (KM) listed in Table 19-1 for handling Hyperion Financial Management data. These KMs use Hyperion Financial Management specific features. It is also possible to use the generic SQL KMs with the Financial Management database. See Chapter 4, "Generic SQL" for more information.

19.2.1 System Requirements and Certifications

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.

The list of supported platforms and versions is available on Oracle Technical Network (OTN):

http://www.oracle.com/technology/products/oracle-data-integrator/index.html.

19.2.2 Technology Specific Requirements

There are no technology-specifc requirements for using the Oracle Data Integrator Adapter for Financial Management.

19.2.3 Connectivity Requirements

There are no connectivity-specific requirements for using the Oracle Data Integrator Adapter for Financial Management.

19.3.1 Creating an Hyperion Financial Management Data Server

Create a data server for the Hyperion Financial Management technology using the standard procedure, as described in "Creating a Data Server" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator. This section details only the fields required or specific for defining a Hyperion Financial Management data server:

1. In the Definition tab:

   • Name: Enter a name for the data server definition.

   • Cluster (Data Server): Enter the Financial Management cluster name.

2. Under Connection, enter a user name and password for connecting to the Financial Management server.

   Note:

   The Test button does not work for a Hyperion Financial Management data server connection; it works only for relational technologies that have a JDBC driver.

19.3.2 Creating an Hyperion Financial Management Physical Schema

Create a Hyperion Financial Management physical schema using the standard procedure, as described in "Creating a Physical Schema" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

Under Application (Catalog), specify a FinancialManagement application.

Create for this physical schema a logical schema using the standard procedure, as described in "Creating a Logical Schema" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator and associate it in a given context.

19.4.1 Create an Financial Management Model

Create an Financial Management Model using the standard procedure, as described in "Creating a Model" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

19.4.2 Reverse-Engineer an Financial Management Model

Reverse-engineering a Financial Management application creates an Oracle Data Integrator model that includes a data store for each dimension in the application, a data store for data, an optional data store for data with multiple periods, and an EnumMemberList data store.

To perform a Customized Reverse-Engineering on Hyperion Financial Management with a RKM, use the usual procedure, as described in "Reverse-engineering a Model" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator. This section details only the fields specific to the Hyperion Financial Management technology.

1. In the Reverse tab of the Financial Management Model, select the RKM Hyperion Financial Management.

2. Set the KM options as follows:

   • CREATE_HFMDATA_MULTIPLEPERIODS: Set to Yes to create an additional data store for data with multiple periods. The number of periods for that model is specified by the MULTIPERIOD_COUNT option.

     Default is No.

   • MULTIPERIOD_COUNT: Specifies the number of periods for the HFMData_MultiplePeriod table.

The RKM connects to the application (which is determined by the logical schema and the context) and imports some or all of these data stores, according to the dimensions in the application:

• HFMData: For loading and extracting data

• HFMData_MultiplePeriods: For data with the number of periods specified by the option MULTIPERIODS_COUNT

  Note:

  This data store is imported only if the CREATE_HFMDATA_MULTIPLEPERIODS option is set to Yes in the model definition.

• Account: For loading the Account dimension.

• Entity: For loading the Entity dimension.

• Scenario: For loading the Scenario dimension.

• Currency: For loading the currency dimension.

• Custom1-4: For loading the Custom1-4 dimensions.

• EnumMembersList-For extracting a members list.

See Section 19.6, "Data Store Tables" for more information about these tables.

19.5.1 Loading Metadata

Oracle Data Integrator provides the IKM SQL to Hyperion Financial Management Dimension for loading metadata into a Finanacial Management application.

Metadata comprises dimension members. You must load members, or metadata, before you load data values for the members.

You can load members only to existing Financial Management dimensions. You must use a separate interface for each dimension that you load. You can chain interfaces to load metadata into several dimensions at once.

The IKM SQL to Hyperion Financial Management Dimension supports the following options for defining how the adapter loads metadata into a Financial Management application:

• REPLACE_MODE: If set to Yes, metadata is replaced in the application (Replace); if set to No, metadata is overwritten in the application (Merge). Valid values: Yes or No (default).

• CLEAR_ALL_METADATA_BEFORE_LOADING: If set to Yes, all metadata is cleared before loading. Valid values: Yes or No (default).

  Caution:

  If you set this option to Yes, you lose any active data or journals in the application.

• LOG_ENABLED: If set to Yes, logging is done during the load process to the file specified by theLOG_FILE_NAME option. Valid values: Yes or No (default).

• LOG_FILE_NAME: The name of the file where logs are saved; default: Java temp folder/dimension.log

19.5.2 Loading Data

Oracle Data Integrator provides the IKM SQL to Hyperion Financial Management Data for loading data into a Financial Management application.

You can load data into selected dimension members that are already created in Financial Management. You must set up the Financial Management application before you can load data into it.

Before loading data, ensure that the members (metadata) exist in the Financial Management relational database. A data load fails if the members do not exist.

The IKM SQL to Hyperion Financial Management Data supports the following options for defining how the adapter loads and consolidates data in a Financial Management application:

• IMPORT_MODE: Determines how data in the application cells is handled during data load. Valid values are:

  • Merge (default): For each unique point of view that exists in the load data and in the application, the load data overwrites the data in the application. For each unique point of view that is in the load data but not in the application, the load data is loaded into the application.

  • Replace: For each unique point of view in the load data, the system clearscorresponding values from the application, and then the data is loaded.

    Note:

    Unless the connected user has full access rights to all specified cells, no data is changed.

  • Replace by Security: For each unique point of view in the load data to which the user has full access rights, the system clears corresponding values from the application, and then the data is loaded. Cells to which the user lacks full access are ignored.

  • Accumulate:For each unique point of view that exists in the load data and in the application, the value from the load data is added to the value in the application.

• ACCUMULATE_WITHIN_FILE: If set to Yes, multiple values for the same cells in the load data are added before they are loaded into the application. Valid values: Yes or No (default).

• FILE_CONTAINS_SHARE_DATA: Set to Yes if the load file contains ownership data, such as shares owned. Valid values: Yes or No (default).

  Caution:

  If ownership data is included in the file and this option is set to No, an error occurs when you load the file.

• CONSOLIDATE_AFTER_LOAD: If set to Yes, data is consolidated after being loaded. Valid values: Yes or No (default).

• CONSOLIDATE_ONLY: If set to Yes, data is consolidated but not loaded. Valid values: Yes and No .

• CONSOLIDATE_PARAMETERS: Specifies the parameters for consolidation as comma-separated values in this order: Scenario (required), Year, Period, Parent.Entity, and Type; default: an empty string.

  Valid Type parameter settings:

  • "I" = Consolidate

  • "D" = Consolidate All with Data

  • "A" = Consolidate All

  • "C" = Calculate Contribution

  • "F"= Force Calculate Contribution

    Example: Actual,1999,2,EastRegion.EastSales,A

• LOG_ENABLED: If set to Yes, logging is done during the load process to the file specified by the LOG_FILE_NAME option. Valid values: Yes or No (default)

• LOG_FILE_NAME: The name of the file where logs are saved; default: Java temp folder/HFMData.logor HFMData_MultiplePeriod.log.

19.5.3 Extracting Data

You can extract data for selected dimension members that exist in Financial Management. You must set up the Financial Management application before you can extract data from it.

Before extracting data, ensure that the members (metadata) exist in the Financial Management relational database; no records are extracted for members that do not exist (including the driver member and the members specified in the point of view.)

This section includes the following topics:

• Extracting Financial Management Data

• Extracting Members from Member Lists