Table of Contents:
This document includes important, late-breaking information about this release of Oracle Hyperion Financial Data Quality Management. Review this Readme thoroughly before installing FDM.
Note: In addition to the main FDM Readme, there is a readme for each individual adapter. Please consult the adapter readme for specific configuration information.
Hosted Online Help - Online Help content for EPM System products is served from a central Oracle download location, which reduces the download and installation time for EPM System. You can also install and configure online Help to run locally. For more information, see the Oracle Enterprise Performance Management System Installation and Configuration 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.
An additional logging feature has been added to store every time an administrative changes the security rights for a user by adding or deleting the available locations for a user.
A new full refresh execution mode parameter, executionMode, has been added to the web service call that clears and reloads the data to the ERPI adapter.
The Financial Management Adapter has been enhanced to support anew configurable dimensionality updates from Oracle Hyperion Financial Management.
The Intersection Validation report has changed to .HTML (it previously was .XML based).
FDM now supports the following third party applications:
Oracle DB 11.2
MS Office 14 (Office 2010) 32-bit and 64-bit versions
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.
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):
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 OTN, listed in the Oracle Business Intelligence product area:
You can upgrade to EPM System Release 184.108.40.206 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 1. Table
|Release Upgrade Path From||To|
Note that when moving from Release 220.127.116.11.x or 18.104.22.168.x to Release 22.214.171.124, you use the "Apply Maintenance Release" option in Oracle Hyperion Enterprise Performance Management System Installer, instead of following the documented upgrade procedures.
Note: If you were using Oracle Hyperion EPM Architect Release 9.3.1, you can download the Oracle Hyperion Shared Services release 9.3.3 from My Oracle Support.
A release earlier than Release 9.3.3.x
If you are upgrading from a release earlier than 9.3.3.x, you must first upgrade to a supported release and then upgrade to release 126.96.36.199. For upgrade procedures for the earlier release, see the product installation guides for the interim release that you are upgrading to.
An environment that includes multiple releases, which can include an environment with one instance of Shared Services or an environment with two instances of Shared Services
See "Upgrading from an Environment with Multiple Releases" in the "Upgrading EPM System Products" chapter in the Oracle Enterprise Performance Management System Installation and Configuration Guide.
Note: If you are starting from Release 188.8.131.52+, 9.3.0.x, 9.3.1.x (except for Oracle Essbase 184.108.40.206.1, 220.127.116.11, 18.104.22.168, and 22.214.171.124), or 11.1.1.x, Oracle recommends that you upgrade to Release 126.96.36.199 as your interim release. If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release. Security Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3, starting with Release 188.8.131.52.1. Essbase and Oracle Hyperion Shared Services Release 184.108.40.206, however, still synchronize security information. For this reason, if you are using Oracle Essbase Release 220.127.116.11.1, 18.104.22.168, 22.214.171.124, or 126.96.36.199, you must first upgrade all products to Release 9.3.3, instead of Release 188.8.131.52.
If you are coming from Release 184.108.40.206 or 220.127.116.11, use the Defects Fixed Finder tool to review the list of defects fixed between those releases and Release 18.104.22.168. This tool is available here:
12809927 -- Drilldown on multiple source values during drillback return constant information.
12936672 -- You are unable to scroll in intersection validation report.
13061539 -- When attempting to perform an import from Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications into FDM using the ERPI-Fin-C adapter, the import process fails with an error if the SQL server name contains a dash.
12883090 -- Import from FDM fails with Network Error (tcp_error).
11733083 -- The length of the source attribute dimension in the TDATASEG table is too short.
9654750 -- Logging for FDM integration with Shared Services is requested.
10397732 -- The upcheck validation does not work in multi-load.
12548925 -- When running the Account Chase - Wildcards report, the report groups items incorrectly.
12683655 -- Existing users appear as new users in User Maintenance.
12825572 -- Export to Microsoft Excel on drill-through landing page, logs off users who are not administrators.
12582216 -- A shutdown event is not triggered upon logoff or close of browser.
11678750 -- The Complex Logic function is not adding to CURVAL.
11784832 -- A session timeout error occurs during logon for basic reviewer and submitter.
10316879 -- A simple logic account does not execute a calculation correctly.
10352428 -- An error message references the Power user role instead of Administrator.
12596550 -- An Index out of Range error occurs in user maintenance when the Admin is not provisioned.
12644218 -- Non-Admin users are logged out when exporting an undefined map to Microsoft Excel.
12540570 -- Creating an application from the workbench or the web results in an error message in windows eventlog and the FDM application is not created.
7717964 -- Request to add protection of HFM cell text to the FDM Data Protection Feature.
10378515 -- The Change Partitions log does not record the user name when changing a location.
12608362 -- The Notepad Icon that appears in the workflow following the check step is not a securable item.
10302094 -- Custom General scripts are missing on Windows 2008 x 64 bit environment.
The following issues are the noteworthy known issues of this release.
9873304 -- Performance degradation occurs after loading large files.
14732412 -- An error occurs you log on to the system with a password that contains an Ä or Ö.
14399361 -- FDM does not support real time replication of the application file share, including but not limited to NAS, Client for NFS on Windows, or 3rd party replication software.
The recommended backup strategy for the FDM file share is to back up during off hours.
13850680 -- FDM and ERP Integrator integration does not work if a dash character (-) is included in the database server name.
13096401 -- In Japanese, drill through fails from Essbase if an FDM app name contains multibyte characters.
12364736 -- Alternate adapter column headers display incorrectly in the Drill page.
13721985 -- Loading data as journals fails when using text based multi load files.
12364736 -- Column headers display the default adapter column names when drilling to a location that uses an alternate adapter. Other information in the drill page is correct.
13096401 -- Drill from target systems fails when the FDM application name contains multi-byte characters.
13686851 -- When entering the LoadBalance information for the Workbench or Schema Updater only, use IP address or short server name (not fully qualified).
13721985 -- Loading data as journals using text-based multi-load file fails. Multi-Load text files loaded as journals do not work. Use Microsoft Excel files to load multi-period journal data to target systems.
13586623 -- Special requirements when importing data from ERP Integrator.
When creating a FDM application on the same database server as the ERP Integrator database, the DB Server Name (SQL only) provided must match the value entered for the HIT Config (used for JDBC Connection String). Mixing server name with alias and/or IP can cause issues. For Oracle, the DB Server Name does not exist in the FDM application creation so a TNS Names entry must be created to match the value entered in the HIT Config.
13102911 -- Pull adapter "Enable Validation Report" option descriptions are different in the adapter and Readme.
Correct description: The On/Off switch is used to enable the Check report. The default setting is On. Set to Off to disable the Check report.
13068346 -- Required role for SQL user when integrating from FDM to ERP Integrator.
When you are creating a FDM application in Oracle and you want to integrate with the ERP Integrator, use uppercase characters when specifying the Oracle user and schema names. If the application has already been created, use the Modify application to change the case.
13068341 -- Required role for SQL user when integrating from FDM to ERP Integrator.
To ensure that FDM integrates properly with ERP Integrator in the SQL environment, make sure the SQL user who is creating the FDM application has permission to link to the database server. User the following command to grant the appropriate role: Grant CONTROL SERVER to [username].
12976176 -- When attempting to import a multiload file the file checks in successfully and upon import returns: Error: File Not Found
Currently the Microsoft Excel based Multiload file contains a link to another document that FDM cannot find when attempting to process the named range in the document. The result is the "File Not Found" error message being returned when attempting to read the range and import the source data.
Solution: A) Open the Microsoft Excel Based Template in Excel. B) Remove any links from the document using "break links" and also remove any #REF entries in the file. C) Save and reload into FDM.
When using Windows 2008 server x86, create the following directory to enable Microsoft Excel importing and exporting:
Target application version needs to be same as FDM otherwise drill through will not work.
FDM 11.1.2 will only run scripts saved in Unicode format. Scripts imported to FDM (using the FDM Workbench File > Import option), from any FDM application, regardless of version, must first be saved in Unicode format prior to exporting (FDM Workbench File > Export option). FDM11.1.2 saves all scripts in Unicode format.
Only numbers entered with the direct input or single-width numbers are supported for grids containing sequencing information, dates, and so forth.
Hard-coded strings in import formats are not converted to upper case during import; they must be entered in upper case.
Note: For information about a specific issue, contact Customer Support or visit the Oracle Web site.
FDM supports 64-bit servers running in 32-bit emulation mode only. Because IIS cannot run under 32-bit and 64-bit mode simultaneously on the same server, Financial Management and FDM Web components cannot be deployed on the same 64-bit server. All other components can be deployed together.
Note: This does not apply when using IIS7 and Windows 2008.
FDM cannot be installed on a Citrix server. Citrix can publish the URL to a FDM installation that is hosted on a non-Citrix server.
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.
The following text has been added under the Wildcard Mapping topic:
“”When using Wildcard mapping, make sure that the rule name does not match the values to be mapped using the rule. For example, if the value to be mapped is ICP900, do not make the map rule name exactly the same. Change it to something like ICP900x".
The following note has been added under the Storing and Retrieving Temporary Variables topic:
"Each POV has its own set of temporary variables, therefore, the temporary variables do not carry over when using the standard workflow process (import, validate, export, check) to a different POV. For example, the temporary variables used for: Period=Nov - 2003, Category = Actual, Location = Texas would not apply to a POV of: Period = Nov - 2003, Category = Actual, Location = Ohio because the location is different. This applies to the batch workflow as well because it is separate from the standard workflow".
The following note has been added under the topic “Mapping Restrictions”:
“When using Wildcard mapping, make sure that the rule name does not match the values to be mapped using the rule. For example, if the value to be mapped is ICP900, do not make the map rule name exactly the same. For example, you might use ICP900x.”
The CAPTION column is no longer available with the Object Maintenance feature (described under the Administration security topic). The figures shown in the Object Maintenance topic are obsolete.
The description for the “Data Value” field has been changed to: “An extra dimension that is used only for integration with multi-dimension target systems. This dimension is associated with a data load location. When FDM creates the load file, the dimension value is entered for every data line that is loaded by the location. For example, the Data Value dimension is associated with the Value dimension in Financial Management. By default the data value field is not populated. For integration with Financial Management to function properly, a default value must be entered. The Data Value <ENTITY CURRENCY> is the typical default value.”
Formerly the description read: “An extra dimension that is used only for integration with multi-dimension target systems. This dimension is associated with a data load location. When FDM creates the load file, the dimension value is entered for every data line that is loaded by the location. For example, the Data Value dimension is associated with the Value dimension in Financial Management. By default, if no value is entered in this field, for integration with Financial Management, the Data Value <ENTITY CURRENCY> is the default value.”
You can drill back from Oracle Hyperion Financial Data Quality Management to Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications.
To drill back:
The following note has been replaced: “It is highly recommended to create the FDM application on the data server. When FDM imports GL data into the system, it uses a highly efficient technique that forces the SQL server process to access the GL file directly. If the FDM application path is not stored on the data server, the Windows account running the MSSQLServer Windows or Oracle service must have read access to the FDM Inbox folder.”
The note now reads: “It is recommended that the File Share be placed on a high available file server. FDM uses the Bulk Insert option to import data. The Windows account running the database service must have read/write access to the FDM file share. In addition the FDM DCOM account must have read/write access to the FDM file share.”
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle's <Product Name> supports accessibility features, which are described in Appendix <appendix letter> in the <Guide Name>. 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.