Release 11.1.2.2.000
This document includes important, late-breaking information about the 11.1.2.2.000 release of Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications. Review this readme thoroughly before installing ERP Integrator.
Note: | It is recommended that customers apply ERP Integrator Patchset Update 11.1.2.2.300 to the 11.1.2.2.000 environment. ERP Integrator Patchset Update 11.1.2.2.300 addresses critical updates for the Oracle Hyperion Financial Management integration. |
See the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide. For new features relating to installation, architecture, and deployment changes in this release, see "New Features" in the Oracle Enterprise Performance Management System Installation and Configuration Readme.
ERP Integrator has been enhanced to support new source systems including packaged and custom data source integrations.
Table 1. Packaged Integrations and Supported Versions
| Integration | Supported Version |
|---|---|
| Fusion Financials* | |
| SAP ERP Financials* | ECC 6, R/3 4.7 (See also SAP Integration.) |
| JD Edwards EnterpriseOne | 9.0 Requires Tools 9.1 |
| PeopleSoft Commitment Control | 9.1 |
ERP Integrator has added the Account Reconciliation module (ARM) of Financial Close Manager as a target application. ARM is a new module within Financial Close Management that manages the process of reconciling financial account records. In each reconciliation cycle, customers use ARM to load data into reconciliation accounts. Preparers then reconcile each account, review the list of transactions and make any necessary adjustments.
In this release, ERP Integrator includes centralized data load and distributed data submission enhancements.
Centralized data load enhancements include:
Multi-Ledger load from a single location
Batch Processing
Batch Scripts
A location can now be created without an accounting entity. This feature allows users to load data from multiple accounting entities from a single location. In this case, accounting entities are associated with the data rules.
Additionally, you can group multiple Accounting Entities as Groups, and then associate the Accounting Entity Group with a data rule.
In this release, a new Batch Processing feature has been added to the Task pane. Using the ERP Integrator batch processing feature, you can:
Combine one or more load rules in a batch and execute it at one time.
Run jobs in a batch in serial or parallel mode.
Define the parameters of the batch.
Create a “master” batch that includes multiple batches with different parameters.
For example, you can have one batch for metadata rules run in serial mode, and a second batch for the data rule run in parallel mode.
Instruct the batch to submit included jobs in parallel mode and return control.
Instruct the batch to submit included jobs in parallel mode and return control only when all jobs are complete.
The new Data Load Workbench and Write-Back Workbench feature provides a user interface to perform the data load processes interactively from sources in the ERP Integrator. In addition, users can view and review the data imported from the source system, including the drill-back.
Location security (user access to locations) for ERP Integrator can now be configured and enforced by options on the Security Settings tab. You define the user groups to create for each location. When a location is created or updated, then you can create as many groups as defined in the system settings for the location. Additionally, a “Maintain User Groups” feature allows you to create user groups in mass for the location if you are upgrading from previous release or enable security after creating all the locations.
The option to display the Security Settings tab is determined by the new “Enable Security by Location” setting on the Systems Settings tab.
Data load changes in this release include mapping enhancements.
In this release, users can define member mapping based on source values of multiple dimensions. For example, the mapping for Account dimension can be based on source values of Entity, Product, and Project. This allows for the derivation of target values based on the combination of source values. In addition, Lookup dimensions are added to Target Application registration. These dimensions contain source dimension but do not exist in the target application. They provide even more flexibility in creating multi-dimension filters. It is a way to facilitate conditional data loading.
Lookup dimensions can be created and assigned with data columns for target applications. Lookup dimensions are used for mapping and reference. They can only be used in ERP Integrator, and do not impact the dimensionality of a target application. They can also be used with member mapping functionality to cross reference multiple source segments and Chartfields, and assign a target value.
An Ignore Member Mapping option been added to Data Load Rules to support conditional filtering of source data.
A new import and export functionality has been added to Data Load Mappings. This feature allows users to export and import the mappings to and from a text file. Users can also create new mappings in a text file and import them. Additionally, the new import functionality supports merge or report modes along with validate or no validate options for target members.
In this release, ERP Integrator now allows users to extract balances in another currency besides the functional or base currency, and these can be either entered or translated balances. Prior to this release, ERP Integrator only supported the extraction of functional currency balances.
A new execution mode “Full Refresh” has been added alongside the existing execution modes “Snapshot” and “Incremental”. By selecting “Full Refresh”, users can perform a clean extraction from the source system, and clear any existing data rows in the appropriate ERP Integrator staging tables for a given source ledger (or Business Unit) and source period.
Data Rules now allow you to use the Explicit period mappings defined in ERP Integrator to determine the source General Ledger periods mapped to each ERP Integrator period (or Oracle Hyperion Financial Data Quality Management period) included in a Data Rule execution. Explicit period mappings allow the ability to map source General Ledger periods that are not symmetrically aligned with EPM periods.
Other changes in this release include metadata and setup enhancements.
The Metadata page has a new look and feel to improve usability and to make it consistent with other pages in ERP Integrator. Summary and detail regions have been added to the page. The Summary region lists dimensions, and the detail tabs allow users to add and modify hierarchies and attributes.
A new Attributes tab provides a table with a list of attributes. For each attribute, the user can specify a default value, and specify to use the default or not. Previously, attributes were hard coded and you could not specify new default values.
When defining metadata rule details, users can specify a prefix or suffix. A member prefix is inserted before the source member code. A member suffix is inserted after the source member code. Although optional, it is important to prefix or suffix the source values for the corresponding Performance Management Architect or Classic Financial Management or Planning dimensions to ensure members are unique in the target application.
Setup enhancements include support for Oracle Hyperion Enterprise Performance Management System Lifecycle Management, and ODI 11g.
In this release ERP Integrator leverages the Oracle Hyperion Enterprise Performance Management System Lifecycle Management (LCM) infrastructure to export/import application setup data. Users can now export all the artifacts in the system or only artifacts for specific target applications. Export and Import are supported for the following artifacts:
Target Application
Import Format
Location
Metadata Rule
Write-Back Rule
Write-Back Mapping
Human Resources Rule
Source Accounting Entity
Source Adapter
Period Mapping
Category Mapping
In this release, ERP Integrator supports Oracle Data Integrator 11.1.1.6 as the engine that extracts data and metadata from the defined sources, and then either populates the Performance Management Architect interface tables or populates the Classic applications with the extracted artifacts. For more information, see Oracle Hyperion Financial Data Quality Management Administrator's Guide.
Late-breaking information about installation of Oracle Enterprise Performance Management System products is provided in the Oracle Enterprise Performance Management System Installation and Configuration Readme. Review this information thoroughly before installing EPM System products.
This readme also includes specific ODI setup and configuration instructions. See Installation and Configuration Instructions.
Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN):
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN):
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
You can upgrade to EPM System Release 11.1.2.2 from the following releases:
Note: For instructions to upgrade, see the Oracle Enterprise Performance Management System Installation and Configuration Guide, "Upgrading EPM System Products."
Table 2. Table
| Release Upgrade Path From | To |
|---|---|
11.1.2.x | 11.1.2.2 Note that when moving from Release 11.1.2.0.x or 11.1.2.1.x to Release 11.1.2.1, you use the "Apply Maintenance Release" option in Oracle Hyperion Enterprise Performance Management System Installer, instead of following the documented upgrade procedures. |
11.1.1.3.x | 11.1.2.2 |
11.1.1.4.x | 11.1.2.2 |
If you are coming from Release 11.1.2.0 or 11.1.2.1, use the Defects Fixed Finder tool to review the list of defects fixed between those releases and Release 11.1.2.2. This tool is available here:
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1
13414185 -- Unable to write back ENTERED_DR or ENTERED_CR missing data from the GL_Interface table.
9680220 -- Add ability to have different Microsoft Internet Explorer language settings for ERP Integrator use.
12727328 -- Unable to update shared member after upgrade from 11.1.2.
13325446 -- Alias values are not populating for accounts in EPMA and Planning applications.
13465745 -- Error occurs in setting up data write-back details.
10177695 -- Setting up plan type is not passed to EPMA.
12743072 -- Zero balances for one period and currency are not imported in ERP Integrator with data load rule.
11804874 -- Parallel batch load using the ERP Integrator source adapter returns errors.
The following are the noteworthy known issues of this release:
13853038 -- ERP Integrator fails to import adapter files.
The Open Interface Adapter and JDE Adapter details are not available in Brazilian Portuguese, and simplified and traditional Chinese. As a workaround, set the browser language to English or another language.
13831793 -- The number format should be locale sensitive for amount.
This issue occurs in the Japanese version since there is no decimal for Japanese currency.
13821445 -- “Total number of rows imported” message is incorrect after data load mapping import.
13786066 -- Metadata load fails to execute.
13785895 -- Do not start the ERP Integrator from the Weblogic administrator console when using ERP Integrator with the Account Reconciliation Manager (ARM).
When the ERP Integrator server is started from the Weblogic Administrator console, then ERP Integrator fails to communicate with ARM.
To start scripts if you are running on a non-Windows environments, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.
13785611 -- Data load mapping is empty after saving a new Import Format.
13775349 -- Oracle Essbase applications should be fully functional after upgrade.
If you are upgrading from 11.1.1.3 and use an Essbase application, go to the Target Application page and select Refresh Metadata for each Essbase application before using it.
13743427 -- The target account is not displayed for data load mappings in Edit mode.
Workaround: You can change the target member by clicking Edit next to the source, and then update the target in the Multi-Dimension window.
13623601 -- When you run a data rule after upgrading from release 11.1.1.4 to 11.1.2.2.00, an additional drill is created.
Workaround: Manually delete the duplicate drill region directly in the Essbase Administration Services console (EAS). This should only be done when duplicate drill regions are shown for a cell in a Planning application. The obsolete drill region that needs to be removed is in the form of:
"Year" : "Scenario" : "Version"
For example, you might remove: "FY10" : "Current" : "BU Version_1"
The drill region that remains should be in the form: "Year" : "Scenario"
For example, the following drill region would be kept: "FY10" : "Current"
13567704 -- Export mapping does not work when ERP Integrator and ODI run on different operating systems.
13558551 -- Unable to select Accounting Entity when ERP Integrator is deployed on the WebSphere Application Server.
Workaround: Create an accounting entity group for the source system. After creating the accounting entity group, select the accounting entity in the Entity tab.
13520277 -- ERP Integrator is not accessible after the first startup of ERP Integrator when deployed on the Websphere Application Server.
Workaround: Restart the ERP Integrator Server.
13502900 -- Unable to click and make selections from drop-downs in Multi-Dimension window.
Workaround: Use the keyboard arrow keys to select items.
13438487 -- ERP Integrator does not support UNICODE character set on the SQL Server.
Workaround: Use a native character set.
13414983 -- Unable to load metadata when a prefix or suffix is added to a source member.
This issue only affects Peoplesoft Spring Trees (that is, ChartField members are participating as parents in the hierarchy).
Workaround: Do not use a member prefix/suffix or a parent member prefix/suffix on dimensions where the user has selected a Peoplesoft Spring Tree in the Metadata mapping.
13104202 -- Write-back fails for an EPMA deployed ASO Oracle Essbase application.
Workaround: None.
13087477 -- The source system initialize fails to update the language column in the source system when run the very first time after an agent start.
Workaround: Rerun the load.
13085512 -- The data load from SAP fails when executed concurrently by multiple users.
Workaround: Contact Oracle Support for availability of patch 13085512.
This section provides the following setup and configuration procedures:
Note: | It is recommended that customers apply ERP Integrator Patchset Update 11.1.2.2.300 to the 11.1.2.2.000 environment. ERP Integrator Patchset Update 11.1.2.2.300 addresses critical updates for the Oracle Hyperion Financial Management integration. |
To setup the ODI to integrate with JD Edwards:
Download the JD Edwards EnterpriseOne Data Access Driver (DAD) driver:
To copy the DAD Drive to the ODI Agent Driver directory, unzip the archive file to a temporary directory. Extract the JAR file DADriver_EAR.jar. Then, copy the extracted contents of DADriver_EAR.jar to the ODI Agent Driver directory.
If you are running the standalone ODI Agent, then the directory in a default installation is: C:\Oracle\product\11.1.1\Oracle_DI_1\oracledi\agent\drivers
Register the JD Edwards EnterpriseOne Data Access Driver by way of the Server Manager.
The combined Server Manager Agent (installed on the Oracle Data Integrator server) and Server Manager Console are used to register the JD Edwards EnterpriseOne Data Access Driver. This process generates the jas.ini file, jdbj.ini file, and jdelog.properties file, and extracts the JD Edwards EnterpriseOne Data Access Driver jar files to a target location.
Note: | A comprehensive server manager guide: Document 705509.1 - Server Manager Guide is available at: http://docs.oracle.com/cd/E24902_01/nav/upgrade.htm |
From the Server Manager Console, select the Managed Home Location named for your Oracle Data Integrator Server.
From the panel that follows, select the EnterpriseOne Data Access Driver radio button.
Complete the form fields as follows, and click Continue.
Table 3. EnterpriseOne Data Access Driver Form Fields
| Field | Description |
|---|---|
| Server Group | Select the desired group, for example, you might select “default”. |
| Instance Name | Provide the name of the instance. |
| Install Location | Provide a valid path to which to install the JD Edwards Data Access Driver jar files, for example, the ODI Agent Driver directory. For example, you might specify: <DRIVE>\Oracle\product\11.1.1\Oracle_DI_1\oracledi\agent\drivers |
| Software Component | Select the desired tools release version, for example, you might select: “9.1.0.1”. |
Complete the form fields based upon configuration attributes of the environment; and click Continue.
Caution! | Click Continue only once and wait for the panel to change. |
Navigate to the recently created Server Manager Agent JDBC driver configuration install location.
For example, navigate to: C:\JDE_HOME\targets\JDEJDBC_DAD\config
Copy the jas.ini file, jdbj.ini file, and jdelog.properties file from the JDE Application Server to the ODI Agent Driver directory.
If you are running a standalone ODI Agent, then the directory in a default installation is: C:\Oracle\product\11.1.1\Oracle_DI_1\oracledi\agent\drivers
Ensure that the security server of the jas.ini file is set correctly.
Review and edit the jdbj.ini file as follows:
If the JD Edwards application database is Oracle, update the location to the tnsnames.ora file.
It is imperative that you encrypt the [JDBj-BOOTSTRAP SESSION] stanza, then the password value.
Modifications to the .INI file password encryption can only be accomplished through the use of Server Manager.
Set the value of following parameters under [JDBj-RUNTIME PROPERTIES] stanza to:
resultSetTimeout=-1
transactionTimeout=-1
usageExecutionThreshold=20000
usageResultSetOpenThreshold=120000
usageTracking=false
msSQLQueryTimeout=1800000
Edit the jdelog.properties file and set the log level as needed.
In a production environment, set the log level to SEVERE so that only severe errors are reported in the log file.
Ensure you can access the server specified in the jdbj.ini file from the ODI Server.
Sometimes the .INI file may contain a server host name without a domain suffix. If needed, create an entry in the host file of the ODI Server so that the JDE server can be accessed.
To setup the ODI to integrate with Financial Management:
Rename odiparams.bat located at <ODI_HOME>\oracledi\agent\bin to odiparams.bat.backup.
The default installation location is C:\app\Oracle\product\11.1.1\Oracle_ODI_1.
Unzip the contents of the Companion CD to the temp directory.
For the 32 bit operating system, copy HFMDriver32_11.1.2.2.dll as HFMDriver.DLL.
For the 64bit operating system, copy HFMDriver64_11.1.2.2.dll as HFMDriver.DLL.
If you want to disable security, for example in a test instance, complete the steps below.
To disable Web Service Security for Peoplesoft:
On the left side tree, expand Farm, then Application Deployments, then AIF (11.1.2.0) (ERP Integrator), and then select AIF(11.1.2.0) (ERP Integrator).
On the right side pane, select Application Deployment, then ADF, and then Configure ADF Connections.
In the list of Web service connections, select HYPBudgetCheck, then Advanced Connection Configuration, and then HYPBudgetCheck-GL_HYP_BUDGETCHECK_Port.
From the OWSM policies tab, select the policy and then Disable.
From the Confirmation pop-up, select Yes to disable the policy.
SAP integration is supported only when Oracle Hyperion Financial Data Quality Management and ERP Integrator use an Oracle database.
If you plan to use the SAP ERP Financials integration, you must download the ERPI-SAP Adapter from the Oracle partner Bristlecone’s website. Please register at the website http://www.bristleconelabs.com/edel/edel_login.asp to obtain login information. In addition, refer to the documentation provided by Bristlecone for details regarding the SAP Adapter configuration.
The most recent version of each EPM System product guide is available for downloading or viewing from the EPM System Documentation area of the OTN Web site (http://www.oracle.com/technology/documentation/epm.html). You can also use the EPM System Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html), which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.
Deployment-related documentation is also available from the Oracle Software Delivery Cloud Web site (http://edelivery.oracle.com/EPD/WelcomePage/get_form).
Individual product guides are available for download on the Oracle Technology Network Web site only.
When you cut and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid. Workaround:: Cut and paste from the HTML version of the document.
The following caution was inadvertently removed from the topic “Configuration Prerequisites for ERP Integrator” in the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide. The caution is still applicable.
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.
In the topic “Setting System Profiles” of the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide, Step f should read: “oracle.jdbc.OracleDriver” instead of “oracle.jdbc.driver.OracleDriver”.
In addition, a new step has been added after Step i. It reads:
Step j. In EPMA Data Source Name, enter the EPMA Data Source name for the EPMA Interface Data Source.
In the topic “Using the Workbench POV Bar” (for the Write-Back Workbench) of the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide, the documentation erroneously states that the POV shows the current “Period” and “Category”. For the Write-Back Workbench, the POV only shows the current “Location”.
In the topic “Install ODI 11.1.1.6” (in the Create a New Schema (Oracle) or Database (SQL Server section) of the Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide, the documentation erroneously states the ODI Agent and Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications have to be installed on the same server. This should read the same “operating system” instead of “server”.
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community.Familyproducts support accessibility features, which are described in the product's Accessibility Guide. The most up-to-date version of this guide can be found in the Oracle Enterprise Performance Management System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).
In addition, this Readme file is accessible in HTML format.