Professional Documents
Culture Documents
Edition
Release 11.1.1.3
Readme
Purpose ........................................................................................................................ 2
Oracle Database Tuning ................................................................................................ 2
Restrictions .................................................................................................................. 2
New Features ............................................................................................................... 3
ERP Integration ................................................................................................................................... 3
Multi-Language Support and FDM System Requirements .................................................................... 3
Drill Through from SmartView ............................................................................................................. 3
Drill Through from Financial Reporting ............................................................................................... 3
SAP Source Adapter ............................................................................................................................ 3
Functional Changes ............................................................................................................................. 3
Documentation Updates...............................................................................................12
FDM ................................................................................................................................................... 12
ERP Integrator .................................................................................................................................. 12
Accessing Hyperion Product Documentation ..................................................................................... 12
Top of Document
Top of Document
Restrictions
The following are restrictions for FDME customers:
All components of FDME must be installed and run from one server, with the exception of RDBMS.
FDME is limited to 100 users.
Only three features/options are available for FDME: Enterprise Adapter, Tax Adapter, and Batch
Loader:
o Base pricing includes use of the Enterprise Adapter only.
o The Tax Adapter and Batch Loader are available with the purchase of the FDM Adapter Suite.
Documentation is common to FDM and FDME. Therefore, the documentation includes some
references and examples that will not apply to FDME. Some of the information includes, but is not
limited to, the following:
o FDME is limited to only two dimensions (Account and Entity). Some examples may show
dimensions not available in Hyperion Enterprise.
o FDME does not include a load balance component. Load balance servers and backup servers
cannot be specified. All components must be installed and run from one server.
Note: The FDM Adapter Suite must be downloaded to obtain the Hyperion Enterprise adapter which is
included with the purchase of FDME.
Top of Document
2
New Features
ERP Integration
This release of FDM includes the ERP Integrator. ERP Integrator is a new component of the Hyperion
Workspace that uses Oracle Data Integrator (ODI) to source data and metadata from ERP systems and
loads it into Hyperion EPM applications. ERP Integrator also supports drill through from EPM
applications to the source systems that it supports.
You must purchase the FDM Adapter Suite in order to use the ERP Integrator. Refer to the section in
this document titled EPI Integrator, the Oracle Hyperion Financial Data Quality Management ERP
Integration Adapter for Oracle Applications Administrator’s Guide, and the FDM ERP Integration
Adapter Readme for additional information.
System requirements are no longer part of the Oracle Hyperion Enterprise Performance Management
System Installation Start Here.
FDM release 11.1.1.3 supports a regional setting of Danish and multibyte compliance. The user
interface is localized only for English, French, and German. Refer to the FDM Configuration Guide for
information regarding language settings and configuration for FDM.
Functional Changes
3
New Option for SQL Service Provider
When creating new applications or adding applications, Microsoft SQL Server 2005 Native Client is now
an option as a database provider. See “Managing FDM Applications” in the FDM Administrator’s Guide
for additional information.
A new procedure for importing standard template and standard reports is included in Chapter 8 of the
FDM Configuration Guide
The FDM Adapter Suite includes the following adapters: Data Extract (Tax), Hyperion Enterprise, ERPI,
Essbase, Pull (DataMart), and Strategic Finance. The SAP Integration adapter is available as a separate
download. Although the ERPI adapter is included in the adapter suite, it requires a separate license to
use.
Note: The adapter for Oracle E-Business Suite is no longer included in the FDM adapter suite. Use the
ERP Integration adapter to integrate FDM with Oracle E-Business Suite Financials.
Adapters for Financial Management, Essbase and Planning, Data Extract (Tax), Pull (DataMart),
Hyperion Enterprise, and Strategic Finance have been updated.
Adapter Synchronization
The adapter synchronize function no longer synchronizes the No Data Value field of the adapter
dimensions. The No Data Value field is also no longer visible anywhere in the product except in the
database.
Enhancement Requests
#6584512—A log entry is created each time the POV is locked or unlocked.
#7634718—Autocomplete is automatically disabled in Internet Explorer for forms containing user
ID and/or password-type inputs.
#7429264—User logoffs are now logged. Note: Logouts as a result of timeouts and users
inappropriately closing the window (clicking X in upper-right hand corner) cannot be logged.
Top of Document
4
Installation Updates
Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition
FDM is installed using the Oracle Hyperion Enterprise Performance Management System (EPM)
Installer, Fusion Edition. Refer to the EPM documentation for installation instructions.
Shared Services
If FDM will be used with Shared Services, you must run the Oracle EPM System Configurator to
register FDM with Shared Services. Refer to the FDM Configuration Guide for all other configuration
processes, including detailed procedures to migrate users to Shared Services
If you will be using FDM with the Financial Management Classic Administration option, install the
(8785892) available on the My Oracle
Support Website. This patch fixes a connection issue between Oracle Data Integrator and Financial
Management.
Installation Procedure
This release is a maintenance install for FDM 11.1.1, FDM 11.1.1.1, and FDM 11.1.1.2. You can install
FDM 11.1.1.3 without uninstalling older versions of FDM 11.x.x.x. If you currently have FDM 9.3.1.x or
older, you must uninstall it before installing FDM 11.1.1.3.
3. Update Adapter
Steps for updating the adapters are included in the FDM Configuration Guide.
4. Update Reports
Steps for updating the reports are included in the FDM Configuration Guide.
Top of Document
Top of Document
5
Known Issues
FDM
Scripts
FDM 11.1.1.3 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). FDM 11.1.1.3 saves all
scripts in Unicode format.
6
Mapping FDM Dimension Names to Target System Dimension Names
When using the Essbase adapter, the FDM dimension names must be mapped to the target system
dimension names for drill through functionality to work.
Note: For information about a specific issue, contact Customer Support or visit the Oracle Web site.
7
ERP Integrator
Oracle RAC is not supported for this release of ERP Integrator.
ERP Integrator supports limited platforms for this release. ERP Integrator is not compatible with the
following:
- SQL Server
- DB2
- Oracle Application Server
- HPUX RISC
- IBM Websphere
If FDM is configured in the following manner, integration to ERP Integrator to retrieve data fails:
- FDM 11.1.1.3.00 w/ Enterprise Adapter
- Enterprise drill-through Scripts in Load Balancer
If a calendar item is mistakenly assigned to an undesired member in the target application, it
cannot be deleted. To work around the problem, switch the selection to a different member, such
as [No Year].
When creating a detailed member mapping, rule patterns are not assigned as expected.
When you create a calendar mapping and then select a different target application, the Define
Calendar Mapping page does not refresh as expected. To work around this problem, click OK to
refresh the page for the selected application.
In ICP segment related metadata loads, when an ICP segment exists in the chart of accounts and a
default member, such as 00, is selected in the Entity dimension mapping to the Company segment,
this member (00) is created under the ICP dimension, which is not as expected.
Before creating metadata and data rules, you should ensure that your source system data does not
include special characters. Special characters are not supported in Financial Management target
applications.
The initialization of the source system process for a PeopleSoft application will fail if different
effective dated versions of the same tree have different descriptions. The error is:
To work around this problem, manually drop the unique index, AIF_TREES_STG_U2, and create the
AIF_TREES_STG_N2 index instead:
When you create and run a data rule for Performance Management Architect target applications
and then edit the application in Performance Management Architect, the member selector in
Performance Management Architect may show base and shared members.
8
If you create a parent for all the orphan members, ensure the member meets all the criteria to be
a parent.
For PeopleSoft source systems, it is expected that metadata should load only those members that
have set ID set to a particular business unit, however, it should load the Accounts relating to set
ID.
For this release, you cannot delete Shared Dimension Library mappings.
If the dimension name is not the same as the Alias name in a Performance Management Architect
Planning application, the drill through landing page does not return any data.
When creating a detailed member mapping for an ICP dimension (target) to natural accounts
(source), the search on target members does not return all members in the ICP dimension. The
missing members are those members that get created in the ICP dimension based on the details of
the entity dimension. Entity members flagged as ICP are created as members of the ICP dimension
during deployment, and it is these members that are not shown in ERPI. ICP members created
manually will be shown in detailed member mapping as targets.
When attempting to create a metadata rule and add dimensions to the rule, the following error is
displayed, even if no dimensions have been added to the rule:
To work around this problem, click the refresh button to refresh the page.
Average daily balance values appear drillable, even though they are not. ERP Integrator does not
support drill through on average balances, therefore the drill region is not created for average daily
balances data.
The naming convention for an auto-generated Performance Management Architect import profile is
“EPMI System Profile” and then a sequential numbering scheme. This may be confusing for
Performance Management Architect users. In future versions, it will be named based on the
metadata rule that is run.
You cannot delete a source system. However, you can modify a source system.
If two metadata rules are started simultaneously for the same data source one of them may fail
with a . To work around this problem, run the rule again.
In some instances, metadata and data rules fail with a
error. To work around this problem, run the rule again.
ERP Integrator does not support drill through for Essbase applications, even though the Create Drill
Region check box on the Target Application Registration page is available. We recommend that you
do not check this box when defining the target application information.
ERP Integrator supports Essbase only in Performance Management Architect applications.
Performance Management Architect Essbase applications allows the creation of applications that
have a single Time dimension. However, ERP Integrator requires that users map the source time
periods to a target year and period. To map to a target EPMA Essbase application, the user will
need to create a period and year dimension in the Essbase application.
On the Define Calendar Mapping page, it is possible to map a source calendar period to a period
member that is above the leaf level, though ERP Integrator will not write data to that period.
Upon success or failure of a process, process details do not display error or log details related to
Performance Management Architect import profile or data synchronization creation. To view import
profile or data synchronization jobs, use the Performance Management Architect Job Console.
If you have a Classic Financial Management or Planning application and define metadata and data
rules, and then upgrade the application to Performance Management Architect you will have to
purge the rules for the application in ERP Integrator and then recreate the rules.
Consider the following for languages when working with Financial Management target applications:
- For Performance Management Architect Financial Management applications, ERP Integrator
attempts to match the ERP Integrator language to the Performance Management Architect
9
Financial Management alias members, and performs a case-sensitive match. For example, the
ERP Integrator language selection for French is “FRENCH” in all upper case letters, and it must
match the Performance Management Architect alias member exactly. If the Performance
Management Architect alias member is of mixed capitalization, then ERP Integrator will not find
a match, and the source descriptions for FRENCH will not be populated for any members. Note:
The default alias member is not required for Financial Management. The limit for the number of
languages that can be loaded is 10, and this is the Financial Management maximum.
- For Classic Financial Management applications a single language is supported. On the Target
Application Registration page, the Default Language selected populates the first language in the
list of languages in ERP Integrator. It is possible that the default language selected in Financial
Management could be English, and the first language is French, and the English member
descriptions get pushed to the French descriptions in Financial Management.
Metadata rules created for Financial Management target applications will fail in the following
instances:
- The case is inconsistent from the source to the target.
- There are multiple members in the source system named the same but with different cases
(upper and lower) that are mapped to Financial Management.
- There is a dash (hyphen) in the member name from the source system, as this is not allowed in
Financial Management.
Metadata rules created for Planning target applications will fail in the following instances:
- Invalid characters like “(“or “)” are not allowed, but duplicate aliases may be loaded. Duplicate
aliases are caught at the time of cube refresh.
- Performance Management Architect allows invalid Planning characters such as “(“ or “)” in
aliases and they are detected during application validation. See the Oracle Hyperion Enterprise
Performance Management Architect Administrator’s Guide for information on invalid characters.
Performance Management Architect mixed mode supports integration between Performance
Management Architect version 11.1.x and source applications in versions 9.3.1.x or earlier 11.1.x
applications. This may work for Performance Management Architect applications and ERP
Integrator, but drill through is not supported for any application version that is not the same
version as ERP Integrator. Also, until this is certified by Oracle development, this is not a supported
configuration for ERP Integrator.
In ERP Integrator, you can select to extract exchange rates from a source ledger to a target
application that is multi-currency enabled. If the target application is Planning, then the exchange
rates will be loaded into the Planning exchange rate tables as part of the data load process. For
Financial Management, exchange rates are only populated into the ERP Integrator exchange rate
interface tables, and you are required to manually import exchange rates into HFM.
Translated ledgers are not a valid source selection for ERPI.
Application roles are required to load metadata and data into a Classic application. For Performance
Management Architect, you need the appropriate roles that allow for deployment and data
synchronization operations. See the Oracle Security Administration Guide for roles required for
Classic Planning, Classic Financial Management, and Performance Management Architect.
It is possible that some source systems have the same member represented multiple times, but in
a different case. Problems can occur when integrating with some target applications. It is
recommended that you modify your source systems to make sure that duplicate members do not
exist because of case issues.
If implementing ERP Integrator with Performance Management Architect, you should create a
Performance Management Architect data source that can be referenced on the source system setup
page. In the EPM System Configurator, when creating the data source, deselect the “Create
interface tables” option.
If you are using PeopleSoft GL as the source system please perform the following steps:
- Go to the directory.
10
- Back up the file titled .
- Using any text editor, open the file titled .
- Search for string “ .” (without quotes) and replace with “ ” (six spaces). There will be
two instances with this reference.
Top of Document
Solution: IIS 6 Metabase compatibility is required for the FDM Web server when installed on Windows
2008.
Solution: Set the Excel sheet that contains the UPS range as the current sheet.
11
ERP Integrator
Deleting Rules
You can delete rules prior to successfully running the rule. However, after a rule runs successfully, you
cannot delete the rule. This ensures that the drill through path is consistent. (#8654278)
Top of Document
Documentation Updates
FDM
Drill Terminology
The former term “drill back” has been replaced with “drill through.” Drill through refers to the
navigation from a value in one data source to corresponding data in another source. “Drillback” is still
used when referring to navigating from a value in FDM to another value in FDM.
ERP Integrator
When the data rule is run for a Financial Management target applications, the Exchange Rates
from the source would be populated only up to the ERP Integrator interface table:
AIF_HS_EXCHANGE_RATES and will not update the Core Exchange Rates table in Financial
Management. (#8627968)
Top of Document
Adapter Fixes
Pull G4-B
No defects reported.
Financial Management
#7347763—Fixed a bug that would sometimes allow the user to continue to Review/Submit even
though the Check report contained a Lookup error.
Essbase G4-E
#7169549—FDM now correctly processes the Check report using the ActValidate action when Essbase
member names contain spaces.
Enterprise G4-E
#6578866—Fixed a bug that caused the validation rules to bring back only periodic values.
13
#8550185—Fixed a bug that caused the Check report to display incorrect data
Top of Document
14
FDM Compatibility
The following table outlines the FDM release compatibility with target and source applications.
The following table lists Oracle Hyperion Financial Data Quality Management, Fusion Edition adapters and the compatible versions of
Oracle Enterprise Performance Management System products.
16
Financial Hyperion Oracle
Essbase/ Financial Hyperion
FDM Adapter FDM Management Strategic E-Bus. SAP ERPI
Planning Management Enterprise
Intercompany Finance Suite GL
HE6x-G4-E 9.3.1.- 11.1.1.3 6.4 – 6.5.1*
R/3 4.6c,
SAP-FIN-A 11.1.1.2 – 11.1.1.3
ECC 6.0
R/3 4.6c,
SAP-FIN-B 11.1.1.2 - 11.1.2
ECC 6.0
R/3 4.6c,
SAP-FIN-C 11.1.1.2 - 11.1.2 R/3 4.7,
ECC 6.0**
* Drill through from Enterprise to FDM is only enabled when using FDM 11.1.1.3 and Enterprise 6.5.1.
** SAP-FIN-C Adapter is available only from My Oracle Support (https://support.oracle.com/CSP/ui/flash.html)
Note: The product versions listed in this table are supported per the guidelines of the Oracle Lifetime Support policy through the end of
the Extended Support timeframe.
http://www.oracle.com/support/lifetime-support-policy.html
Top of Document
17
Copyright © 2010, Oracle and / or its affiliates. All rights reserved.
http://www.oracle.com