Hyperion® Data Integration Management Adapter for Financial Management

Release 11.1.1.1

Sample Readme

[Skip Navigation Links]

Purpose. 2

About Data Integration Management Release 11.1.1.1. 2

Data Integration Management Adapters. 3

Installing the Adapter for Financial Management Sample Files. 3

Creating the Comma Application. 4

Sample 1: Data Extract from Financial Management 4

Source. 4

Target 4

File. 4

Mapping Variables Used. 4

Instructions. 5

Troubleshooting. 5

Sample 2: Data Load to Financial Management 5

Source. 5

Target 5

File. 5

Mapping Variables Used. 5

Instructions. 5

Troubleshooting. 6

Sample 3: Data Extract from Financial Management Using a Parameter File. 6

Source. 6

Target 6

File. 6

Mapping Variables Used. 6

Instructions. 6

Troubleshooting. 7

Sample 4: Data Extract from Financial Management followed by Load to Financial Management 8

Source. 8

Target 8

File. 8

Mapping Variables Used. 8

Instructions. 8

Troubleshooting. 8

Sample 5: Enumerate List Members. 9

Source. 9

Target 9

File. 9

Mapping Variables Used. 9

Instructions. 9

Sample 6: Consolidate. 9

Source. 9

Target 9

File. 9

Mapping Variables Used. 10

Instructions. 10

Troubleshooting. 10

Sample 7: Commit 10

Source. 10

Target 10

File. 10

Mapping Variables Used. 10

Instructions. 10

Troubleshooting. 11

 

Purpose

This document describes sample files that are provided to help you learn about this release of Oracle Hyperion® Data Integration Management Adapter for Financial Management. Review this information thoroughly before attempting to use the sample files.

Top of Document

About Data Integration Management Release 11.1.1.1

Data Integration Management is integrated with Informatica PowerCenter. It provides a way of uniting disparate sources of data across an enterprise. For example, it can integrate data stored in multiple warehouses and data marts, relational database management systems (RDBMS), and on-line analytical processing (OLAP) stores.

Data Integration Management includes these components:

·         PowerCenter applications:

·         PowerCenter Client

·         PowerCenter Server

Top of Document

Data Integration Management Adapters

When you have installed and configured Data Integration Management 11.1.1.1, you can install and configure adapters that enable you to retrieve and write data for these other Hyperion products:

·         Oracle Hyperion® Data Integration Management Adapter for Hyperion Enterprise®

·         Oracle Hyperion® Data Integration Management Adapter for Essbase®

·         Oracle Hyperion® Data Integration Management Adapter for Financial Management

·         Oracle Hyperion® Data Integration Management Adapter for Planning

·         Oracle Hyperion® Data Integration Management Adapter for Performance Scorecard

·         Oracle Hyperion® Data Integration Management Adapter for Translation Manager

Top of Document

Installing the Adapter for Financial Management Sample Files

Sample files for use with Adapter for Financial Management are available in the sample directory:

|-- <Informatica Install>

     |-- sample (directory)

          |-- CommaApplication

          |-- data (directory)—Contains data and metadata files and parameter files to be used for data extract and load and metadata load.

          |-- mappings (directory)—Contains XML files for sample mappings.

          |-- rules (directory)—Contains XML files for sample mappings.

 

Note:

·         Repository code page and flat files code page (load methods) specified in sample XML as MS1252.

·         This document assumes that mappings are imported into the repository called “Hyperion”.

·         When creating a Financial Management application connection, be sure to set the correct cluster, application, user name and password.

To install a sample file, import it using Designer:

1.  Select Repository > Import Objects

2.  Double-click the file name

In the repository the mapping is displayed in the mappings subfolder of the open folder.

Top of Document

Creating the Comma Application

Before using the samples, you must create the Comma application in Financial Management.

To create the Comma application:

1.  Click Create Application.

2.  In Application Profile, enter the path to the CommaCalendar.per file.

3.  In the field below Application Profile, specify the path to the Comma application.

4.  Open the Comma application and complete these steps:

a.  Click Load Security, and specify the path to the Comma.sec file in the Security folder.

b.  Click Load Metadata, and specify the path to the comma.xml file in the Metadata folder.

c.  Click Load Member Lists, and specify the path to the Comma.lst file in the Lists folder.

D.  Click Load Data, and specify the path to the Alldata.dat file in the Data folder.

d.  Click Load Rules, and specify the path to the Comma.rle in the Rules folder.

You can then use the Extract Data and Enumerate List Members samples.

Top of Document

Sample 1: Data Extract from Financial Management

This sample extracts data from the Financial Management and writes it to the flat file.

Source

Financial Management application (You can use the Comma application.)

Target

Flat file

File

m_ExtractData_HFM.XML—Data extract without descriptions

m_ExtractDataDesc_HFM.XML—Data extract with descriptions

Mapping Variables Used

$$MapScenario

$$MapYear

$$MapAccount

$$MapEntity

$$MapView

$$MapPeriod

Instructions

1.  Ensure that a Financial Management connection exists: Select Connections > Application in Workflow Manager.

2.  Import the mapping in Designer and save it.

3.  If the default values for the mapping do not correspond to your Financial Management application data, change the values of the mapping variables used: Select Mappings > Parameters and Variables in Mapping Designer.

4.  Create a task of the Session type for this mapping in Workflow Manager, or use Wizard to create a workflow directly.

5.  (Optional) Make appropriate changes to the target flat file output directory name and file name.

6.  Create a workflow with the task and run it.

Troubleshooting

When creating a connection, be sure to set the correct cluster, application, user name, and password.

Top of Document

Sample 2: Data Load to Financial Management

This sample loads Financial Management data from the flat file into the Financial Management application.

Source

Flat file

Target

Financial Management application (You can use the Comma application.)

File

m_LoadData_HFM.XML—Data load without descriptions

m_LoadDataDesc_HFM.XML—Data load with descriptions

Mapping Variables Used

None

Instructions

1.  Ensure that a Financial Management connection exists: Select Connections > Application in Workflow Manager.

2.  Import the mapping in Designer and save it.

3.  If the default values for the mapping do not correspond to your Financial Management application data, change the values of the mapping variables used: Select Mappings > Parameters and Variables in Mapping Designer.

4.  Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.

5.  Make appropriate changes to the source flat file input directory name and file name.

6.  Create a workflow with the task and run it.

Troubleshooting

·         When creating a connection, be sure to set the correct cluster, application, user name and password.

·         Ensure than an application has been deployed to Financial Management with the correct settings (rules, for example).

·         When creating a flat file, check all values for loading with the Preview Data option, to ensure that you load the correct data.

Top of Document

Sample 3: Data Extract from Financial Management Using a Parameter File

This sample extracts data from the Financial Management and writes it to the flat file according to settings in a Parameter File.

Source

Financial Management application (You can use the Comma application.)

Target

Flat file

File

m_ExtractData_HFM.XML—Data extract without descriptions

m_ExtractDataDesc_HFM.XML—Data extract with descriptions

Mapping Variables Used

$$MapScenario

$$MapYear

$$MapAccount

$$MapEntity

$$MapView

$$MapPeriod

Instructions

1.  Ensure that a Financial Management connection exists: Select Connections > Application in Workflow Manager.

2.  Import the mapping in Designer and save it.

3.  In Mapping Designer, click Mapping > Parameters and Variables and complete these steps for each variable:

a.  Enter the mapping variable names in the Name column.

b.  Specify the parameter type.

c.  (Optional) Specify initial value for the variable.

4.  Create a parameter file. For example, you can create a text file with these lines:

[session_name]

$$MapScenario=value

$$MapYear=value

$$MapAccount=value

$$MapEntity=value

$$MapView=value

$$MapPeriod=value

Note: All variables that you specified in Source (Import from Financial Management) must be described in the parameter file. You can set the values for map variables so that the records are returned with set values. For example, all records from Financial Management are returned if you create a parameter file with these lines:

[session_name]

$$MapScenario=

$$MapYear=

$$MapAccount=

$$MapEntity=

$$MapView=

$$MapPeriod=

5.  Create a task of the Session type for this mapping in Workflow Manager, or use Wizard to create a workflow directly.

6.  Set the path to the parameter file in the session properties: Select Session Properties > Parameter Filename.

7.  (Optional) Make appropriate changes to the target flat file output directory name and file name.

8.  Create a workflow with the task and run it.

Troubleshooting

·         When creating a connection, be sure to set the correct cluster, application, user name and password.

·         Set the name for mapping variables when creating the source (after selecting Mappings > Parameters and Variables), and describe all the mapping variables in the parameter file.

·         Set the correct path for the parameter file during session creation (Session Properties > Parameter Filename)

Top of Document

Sample 4: Data Extract from Financial Management followed by Load to Financial Management

This sample extracts data from Financial Management and writes it to Financial Management again.

Source

Financial Management application (You can use the Comma application.)

Target

Financial Management application (You can use the Comma application.)

File

m_HFM_TO_HFM.XML —Data extract without descriptions

m_HFM_to_HFM_Desc.XML —Data extract with descriptions

Mapping Variables Used

$$MapScenario

$$MapYear

$$MapAccount

$$MapEntity

$$MapView

$$MapPeriod

Instructions

1.  Ensure that a Financial Management connection exists: Select Connections > Application in Workflow Manager.

Note: If you want to extract data from one Financial Management application and load it into another, specify two different Financial Management application connections for this sample.

2.  Import the mapping in Designer and save it.

3.  If the default values for the mapping do not correspond to your Financial Management application data, change the values of the mapping variables used: Select Mappings > Parameters and Variables in Mapping Designer.

4.  Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.

5.  Create a workflow with the task and run it.

Troubleshooting

When creating a connection, be sure to set the correct cluster, application, user name and password.

Top of Document

Sample 5: Enumerate List Members

This sample gets the members of the Financial Management member list.

Source

Financial Management application (You can use the Comma application.)

Target

Flat file

File

m_EnumMembersList_HFM.XML

Mapping Variables Used

None

Instructions

1.  Ensure that a Financial Management connection exists: Select Connections > Application in Workflow Manager.

2.  Import the mapping in Designer and save it.

3.  If the default values for the mapping do not correspond to your Financial Management application data, change the values of the mapping variables used: Select Mappings > Parameters and Variables in Mapping Designer.

4.  Create a task of the Session type for this mapping in Workflow Manager, or use Wizard to create a workflow directly.

5.  (Optional) Make appropriate changes to the target flat file output directory name and file name.

6.  Create a workflow with the task and run it.

Top of Document

Sample 6: Consolidate

This sample consolidates the Hyperion Financial Management application.

Note: The Consolidate method of Adapter for Financial Management recognizes all method parameters from the source flat file. 

Source

Flat file

Target

Financial Management application (You can use the Comma application.)

File

m_Consolidate_HFM.XML

Mapping Variables Used

None

Instructions

1.  Ensure that a Financial Management connection exists: Select Connections > Application in Workflow Manager.

2.  Import the mapping in Designer and save it.

3.  You can specify the Consolidate_HFM.txt file from the sample mappings data subdirectory as a source of Consolidate method parameters. Consolidate file format: Scenario,Year,Period,Parent_Entity,Type

4.  Create a task of the Session type for this mapping in Workflow Manager, or use Wizard to create a workflow directly.

5.  (Optional) Make appropriate changes to the target flat file output directory name and file name.

6.  Create a workflow with the task and run it.

Troubleshooting

   When creating a connection, be sure to set the correct cluster, application, user name and password.

   Ensure than an application has been deployed to Financial Management with the correct settings (rules, for example).

   When creating a flat file, check all values for loading with the Preview Data option, to ensure that you load the correct data.

Top of Document

Sample 7: Commit

This sample loads Financial Management metadata from the flat files into the Financial Management application. Each dimension type (Account | Currency | Entity | Scenario | Custom1 | Custom2 | Custom3 | Custom4) is loaded from it own flat file.

Source

Flat file

Target

Financial Management application (You can use the Comma application.)

File

m_Commit_HFM.XML

Mapping Variables Used

None

Instructions

1.  Ensure that a Financial Management connection exists: Select Connections > Application in Workflow Manager.

2.  Import the mapping in Designer and save it.

3.  Delete unneeded branches from the mapping. For example, if you do not intend to import Currencies, delete the “LoadCurrencies”, “SQ_LoadCurrencies”, and “ct_ImportCurrencies” widgets from the mapping.

Note: You can also use the LoadAccounts.txt and LoadCurrencies.txt files that are supplied with the sample mappings as metadata sources.

4.  Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.

5.  (Optional) Make appropriate changes to the target flat file output directory name and file name.

6.  Create a workflow with the task and run it.

Troubleshooting

·         When creating a connection, be sure to set the correct cluster, application, user name and password.

·         Ensure than an application has been deployed to Financial Management with the correct settings (rules, for example).

·         When creating a flat file, check all values for loading with the Preview Data option, so that you can be sure to load the correct data.

Top of Document

 

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