Hyperion® Data Integration Management Adapter for Hyperion Enterprise®
Release 11.1.1.1
Sample Readme
About Data Integration Management
Release 11.1.1.1
Data Integration Management
Adapters
Installing the Adapter for Hyperion
Enterprise Sample Files
Sample 2: Enumerate Account List
Sample 3: Enumerate Categories
Sample 5: Enumerate Entity List
Sample 6: Enumerate Organizations
Sample 10: Extract Account Groups
Sample 13: Extract Organizations
Sample 15: Extract Subentities
Sample 17: Extract Data (Single
Value Mode)
Sample 18: Extract Data (Multiple
Value Mode)
Sample 19: Extract Consolidation
Detail Data (Single Value Mode)
Sample 20: Extract Consolidation
Detail Data (Multiple Value Mode)
Sample 22: Load Data (Single Value
Mode)
Sample 23: Load Data (Multiple
Value Mode)
Sample 24: Load Data (Multiple
Value Mode Based on Fiscal Year)
This document describes sample files that are provided to help you learn about this release of Oracle’s Hyperion® Data Integration Management Adapter for Hyperion Enterprise®. Review this information thoroughly before attempting to use the sample files.
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
When you have installed and configured Data Integration Management Release 11.1.1.1, you can install and configure adapters that enable you to retrieve and write data for these other Oracle products:
· Oracle’s Hyperion Data Integration Management Adapter for Hyperion Enterprise
· Oracle’s Hyperion Data Integration Management Adapter for Essbase
· Oracle’s Hyperion Data Integration Management Adapter for Financial Management
· Oracle’s Hyperion Data Integration Management Adapter for Planning
· Oracle’s Hyperion Data Integration Management Adapter for Performance Scorecard
· Oracle’s Hyperion Data Integration Management Adapter for Translation Manager
Installing the Adapter for Hyperion
Sample files for use with Adapter for Hyperion Enterprise are available in the sample directory:
|-- <Informatica Install>
|-- sample
|-- rules (directory)
|-- data (directory)—Contains data files to be used for data extract and load samples.
|-- mappings (directory) – Contains XML files for sample mappings.
Note:
· Repository code page and flat files code page (load methods) are specified in sample XML files as MS1252.
· This document assumes that mappings are imported into the repository called Hyperion.
· This document assumes that mappings are imported into the folder called Hyperion.
· When creating a Hyperion Enterprise application connection, be sure to set the correct Hyperion Enterprise 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 Hyperion folder with name Hyperion.
This sample enumerates Hyperion Enterprise accounts of given type in selected account groups and writes the result to a flat file.
Hyperion Enterprise application (local or remote) Target
Flat file
m_EnumAccounts.XML
· Selected Account Groups
· Account Type
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change values of the mapping variables used, if the mapping’s default values do not correspond to your Hyperion Enterprise application actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the task, and run it.
Sample 2: Enumerate Account List
This sample enumerates list of Hyperion Enterprise accounts and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_EnumAccountList.XML
Account List Name
1. Ensure that Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change values of the mapping variables used, if the mapping’s default values do not correspond to your Hyperion Enterprise application actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 3: Enumerate Categories
This sample enumerates Hyperion Enterprise categories and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat file
m_EnumCategories.XML
None
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.
4. (Optional) Change the target flat file output directory name and file name as needed.
5. Create a workflow with the session task, and run it.
This sample enumerates Hyperion Enterprise entities and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_EnumEntitites.XML
· Organization
· Top Entity
· Hierarchy Operator
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 5: Enumerate Entity List
This sample enumerates a list of Hyperion Enterprise entities and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_EnumEntitityList.XML
· List Name
· Organization
· “Master Organizational Structure“ (MOS) Category
· “Master Organizational Structure” (MOS) Period
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 6: Enumerate Organizations
This sample enumerates Hyperion Enterprise organizations and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_EnumOrganizations.XML
None
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.
4. (Optional) Change the target flat file output directory name and file name as needed.
5. Create a workflow with the session task, and run it.
This sample enumerates Hyperion Enterprise periods of given Category and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_EnumPeriods.XML
Category
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample extracts Hyperion Enterprise accounts of given account groups and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractAccounts.XML
· Selected Account Groups
· Selected Subaccount Tables, extract with parent
· Selected Subaccount Tables, extract separately
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample extracts Hyperion Enterprise subaccounts of given account groups and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractSubAccounts.XML
· Selected Account Groups
· Selected Subaccount Tables, extract with parent
· Selected Subaccount Tables, extract separately
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 10: Extract Account Groups
This sample extracts Hyperion Enterprise groups and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractAccountGroups.XML
Selected Account Groups
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample extracts Hyperion Enterprise categories and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractCategories.XML
Selected Categories
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample extracts Hyperion Enterprise periods of given categories and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractPeriods.XML
Selected Categories
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 13: Extract Organizations
This sample extracts Hyperion Enterprise organizations and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractOrganizations.XML
Selected Organizations
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample extracts Hyperion Enterprise entities and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractEntities.XML
· Selected Organizations
· Selected Substructures, extract with parent
· Selected Substructures, extract separately
· “Master Organizational Structure“ (MOS) Category
· “Master Organizational Structure” (MOS) Period
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 15: Extract Subentities
This sample extracts Hyperion Enterprise subentities and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractSubEntities.XML
· Selected Organizations
· Selected Substructures, extract with parent
· Selected Substructures, extract separately
· “Master Organizational Structure“ (MOS) Category
· “Master Organizational Structure” (MOS) Period
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample extracts Hyperion Enterprise journals and writes the result to a flat file.
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractJournals.XML
Journal File Name, PowerCenter server variables (like $PMTargetFileDir) are allowed
· Periods (0=All|1=Single)
· Selected Journals. Is required, when Periods=1
· Journals (1|0)
· Standard Templates (1|0)
· Recurring Templates (1|0)
· Regular (1|0)
· Parent (1|0)
· Auto-reversing (1|0)
· Unposted (1|0)
· Posted (1|0)
· Auto-reversed (1|0)
· Reviewed (1|0)
· Reversed (1|0)
· Locked (1|0)
· Balanced (1|0)
· Unbalanced (1|0)
· Balanced By Entity (1|0)
· Delimiter (~)
· Extract Posted as Unposted (1|0)
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 17: Extract Data (Single Value Mode)
This sample extracts Hyperion Enterprise data for specified entities and accounts for a specific period or range of periods and writes the result to a flat file (Single Value mode).
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractData_Single.XML
· Selected Organizations
· Selected Substructures, extract with parent
· Selected Substructures, extract separately
· Selected Subaccount Tables, extract with parent
· Selected Subaccount Tables, extract separately
· Selected Entity Lists
· Selected Account Groups
· Start Period
· End Period
· Category
· POV Organization
· Include Calculated Accounts (1|0)
· Scale
· Data View
·
· “Master Organizational Structure” (MOS) Category
· “Master Organizational Structure” (MOS) Period
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 18: Extract Data (Multiple Value Mode)
This sample extracts Hyperion Enterprise data for specified entities and accounts for a specific period or range of periods and writes the result to a flat file (Multiple Value mode).
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractData_Multiple.XML
· Selected Organizations
· Selected Substructures, extract with parent
· Selected Substructures, extract separately
· Selected Subaccount Tables, extract with parent
· Selected Subaccount Tables, extract separately
· Selected Entity Lists
· Selected Account Groups
· Start Period
· End Period
· Category
· POV Organization
· Include Calculated Accounts (1|0)
· Scale
· Data View
·
·
·
· “Master Organizational Structure” (MOS) Category
· “Master Organizational Structure” (MOS) Period
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 19: Extract Consolidation Detail Data (Single Value Mode)
This sample extracts Hyperion Enterprise consolidation detail data for specified entities and accounts for a specific period or range of periods and writes the result to a flat file (Single Value mode).
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractDSM_Single.XML
· DSM Types
· Selected Organizations
· Selected Substructures, extract with parent
· Selected Substructures, extract separately
· Selected Subaccount tables, extract with parent
· Selected Subaccount tables, extract separately
· Selected Entity Lists
· Selected Account Groups
· Start Period
· End Period
· Category
· Include Calculated Accounts (1|0)
· Scale
· Data View
·
· “Master Organizational Structure” (MOS) Category
· “Master Organizational Structure” (MOS) Period
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Sample 20: Extract Consolidation Detail Data (Multiple Value Mode)
This sample extracts Hyperion Enterprise consolidation detail data for specified entities and accounts for a specific period or range of periods and writes the result to a flat file (Multiple Value mode).
Hyperion Enterprise application (local or remote)
Flat File
m_ExtractDSM_Multiple.XML
· DSM Types
· Selected Organizations
· Selected Substructures, extract with parent
· Selected Substructures, extract separately
· Selected Subaccount Tables, extract with parent
· Selected Subaccount Tables, extract separately
· Selected Entity Lists
· Selected Account Groups
· Start Period
· End Period
· Category
· Include Calculated Accounts (1|0)
· Scale
· Data View
·
·
·
· “Master Organizational Structure” (MOS) Category
· “Master Organizational Structure” (MOS) Period
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: 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) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample loads Hyperion Enterprise journals from a flat file into a Hyperion Enterprise application.
Flat File
Hyperion Enterprise application (local or remote)
m_LoadJournals.XML
· Journals (1|0)
· Standard Templates (1|0)
· Recurring Templates (1|0)
· Regular (1|0)
· Parent (1|0)
· Auto-reversing (1|0)
· Unposted (1|0)
· Posted (1|0)
· Auto-reversed (1|0)
· Reviewed (1|0)
· Reversed (1|0)
· Locked (1|0)
· Delimiter (~)
· Use 1.8 Format (1|0)
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: Select Mappings > Parameters and Variables in Mapping Designer.
4. (Optional) Specify the srcLoadJournals.txt file from the sample mappings data subdirectory as a source file of the LoadJournals method. If you do this, copy the 500JOUR_2Load.JAF from the sample mappings data subdirectory to the PowerCenter Server source files subdirectory.
5. Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.
6. (Optional) Change the target flat file output directory name and file name as needed.
7. Create a workflow with the session task, and run it.
Sample 22: Load Data (Single Value Mode)
This sample loads Hyperion Enterprise data from a flat file into a Hyperion Enterprise application (Single Value mode).
Flat File
Hyperion Enterprise application (local or remote)
m_LoadData_Single.XML
· Exception File Name
· Calculate Account Errors (1|0)
· Start Period
· End Period
· Buffer Size
· Scale
· Load Mode
· Data View
· Calculate Formulas (1|0)
· Zero no Data (1|0)
· Account Conversion Table
· Entity Conversion Table
·
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: Select Mappings > Parameters and Variables in Mapping Designer.
4. (Optional) Specify the srcLoadData_Single.txt file from the sample mappings data subdirectory as a source file of the LoadData method. Load Data file format:
Category,Entity,SubEntity,Account,SubAccount,SubSubAccount,Value1,Period,and ReverseSign.
5. Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.
6. (Optional) Change the target flat file output directory name and file name as needed.
7. Create a workflow with the session task, and run it.
Sample 23: Load Data (Multiple Value Mode)
This sample loads data from a flat file into a Hyperion Enterprise application (Multiple Value mode).
Flat File
Hyperion Enterprise application (local or remote)
m_LoadData_Multiple.XML
· Exception File Name
· Calculate Account Errors (1|0)
· Start Period
· End Period
· Buffer Size
· Scale
· Load Mode
· Data View
· Calculate Formulas (1|0)
· Zero no Data (1|0)
· Account Conversion Table
· Entity Conversion Table
·
·
·
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: Select Mappings > Parameters and Variables in Mapping Designer.
4. (Optional) Specify the srcLoadData_Single.txt file from the sample mappings data subdirectory as a source file of the LoadData method. Load Data file format:
Category,Entity,SubEntity,Account,SubAccount,SubSubAccount,Value1[…,ValueN],and Period,ReverseSign.
5. Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.
6. (Optional) Change the target flat file output directory name and file name as needed.
7. Create a workflow with the session task, and run it.
Sample 24: Load Data (Multiple Value Mode Based on Fiscal Year)
This sample loads data from a flat file into a Hyperion Enterprise application (Multiple Value mode Based in Fiscal Year).
Flat File
Hyperion Enterprise application (local or remote)
m_LoadData_MultipleFY.XML
· Exception File Name
· Calculate Account Errors (1|0)
· Start Period
· End Period
· Buffer Size
· Scale
· Load Mode
· Data View
· Calculate Formulas (1|0)
· Zero no Data (1|0)
· Account Conversion Table
· Entity Conversion Table
·
·
1. Ensure that a Hyperion Enterprise connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
8. Change the values of the mapping variables used if the default values for the mapping do not correspond to your Hyperion Enterprise application Actual data: Select Mappings > Parameters and Variables in Mapping Designer.
3. (Optional) Specify the srcLoadData_Multiple.txt file from the sample mappings data subdirectory as a source file of the LoadData method. Load Data file format is as follows:
Category,Entity,SubEntity,Account,SubAccount,SubSubAccount,Value1[…,ValueN], FiscalYearStart,and ReverseSign.
4. Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.
5. (Optional) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
This sample consolidates a Hyperion Enterprise application.
Note: The Consolidate method of Adapter for Hyperion Enterprise recognizes all method parameters from the source flat file.
Flat File
Hyperion Enterprise application (local or remote)
m_Consolidate.XML
None
1. Ensure that a Oracle’s Hyperion® Enterprise® connection exists: Select Connections > Application in Workflow Manager.
2. Import the mapping in Designer and save it.
3. (Optional) Specify the srcConsolidate.txt file from the sample mappings data subdirectory as a source file of the Consolidate method. Load Data file format:
ConsolType,Category,StartPeriod,EndPeriod,Organization,TopEntity,and ReverseSign.
4. Create a task of the Session type for this mapping in Workflow Manager or use Wizard to create a workflow directly.
5. (Optional) Change the target flat file output directory name and file name as needed.
6. Create a workflow with the session task, and run it.
Copyright © 2008, Oracle and / or its affiliates. All
rights reserved.
http://www.oracle.com