Oracle® Hyperion Financial Data Quality Management, Fusion Edition
Release 11.1.2.0.000 Patch Set 1 (PS1): 11.1.2.1.000
Readme
ERP Integrator Supported Source Systems
ERP Integrator Supported Target Applications
ERP Integrator Required Patches
Supported Paths to this Release
Defects Fixed in Release 11.1.2
Temporary Variables in Import Format Scripts
Using App Creation Group in Load Balance Manager
Intersection Validation Reports on Windows 2008
Drill Through with Complex Import Formats
ActiveX Error after Install (Windows 2008)
Accessing EPM System Product Documentation
Copying and Pasting Code Snippets from PDFs
This document includes important, late-breaking information about this release of Oracle Hyperion Financial Data Quality Management, Fusion Edition (FDM) release 11.1.2.1, Hyperion Enterprise Financial Data Quality Management Module (FDME) release 11.1.2.1, and Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications, Fusion Edition (ERP Integrator). Review this Readme thoroughly before installing FDM, FDME, or ERP Integrator.
Important: If you are using Oracle as the database for your FDM application, it must be tuned to ensure optimal performance. Your company’s Oracle DBA must read and follow the tuning instructions included in the FDM DBA Guide. Failure to tune the database per the FDM DBA Guide will result in poor performance.
The following sections describe the new features for FDM and ERP Integrator. For new features relating to installation, architecture, and deployment changes in this release, see “New Features” in the Oracle Hyperion Enterprise Performance Management System Installation Readme.
This release supports non-English languages. The list of supported languages for all EPM System products is included in the Oracle Hyperion Enterprise Performance Management System Certification Matrix, posted at http://www.oracle.com/technology/products/bi/hyperion-supported-platforms.html.
In Release 11.1.2.1, you can upgrade FDM from previous releases. See the FDM Configuration Guide for important post-upgrade steps.
FDM now supports the following 3rd-party applications:
· Oracle DB 11.2
· Client Java version up to 1.6
· MS Office 14 (Office 2010) 32-bit and 64-bit versions
· OSSO
· OAM
· OID
· SAP R/3 4.7 (data loading as well as drill through)
· PeopleSoft 9.1 certification for data load, write back and drill through (for ERP Integrator)
· Oracle E-Business Suite 12.1.3 (for ERP Integrator)
· SQL Server support (for ERP Integrator)
· SQL and DB2 support for PeopleSoft
In Release 11.1.2.1, you can upgrade ERP Integrator from previous releases. See the ERP Integrator Administrator’s Guide for important post-upgrade steps.
The Tasks pane (left pane) in ERP Integrator has a new look and feel to improve usability. It now displays all options, making it easier for the user to navigate without expanding and collapsing artifacts.
You can enable applications registered in FDM to be registered as target applications in ERP Integrator. For example, Oracle Hyperion Strategic Finance or Hyperion Enterprise are registered in FDM, but are not registered in Shared Services. After you enable the applications, you can define import formats, locations, and data load rules in ERP Integrator.
Typically adjustment periods are uniquely identified in the source system to record adjustment entries for the year-end or year-beginning process. In ERP Integrator 11.1.2.1, you can now map the adjustment periods to ensure that the source system adjustment periods map correctly to the ERP Integrator periods.
You now can select the YTD or Periodic amount for balance sheet accounts and income statements when defining the source filter options for a data load rule.
You now can specify the Time Balance Property (Flow or Balance) for balance sheet and income statement accounts when defining Account dimension mapping details for Planning Applications. Based on your computation requirements, this property can be assigned.
You now have three options to create HR Data Load rules:
· Copy an existing rule
· Use a template to create the rule line definitions
· Create the rule line definitions manually
There are new common search capabilities available in ERP Integrator. When you select the Search button, if the Advanced Search button is available, you can enter additional search conditions. The fields that display in the advanced search options differ depending on what artifact you select. The following operators are supported: Not equal to, Is blank, Does not contain, Ends with, Starts with, Contains, Is not blank, and Equal to.
ERP Integrator now has two new web services:
· getLocationNames
· getPeriodNames
The FDM Adapter Suite includes the following adapters: Data Extract (Tax), Hyperion Enterprise, ERP Integrator, Essbase, Pull (DataMart), and Strategic Finance. The SAP Integration adapter and Hyperion Financial Management adapter are available as separate downloads.
Note: Use the ERP Integration adapter to integrate FDM with Oracle E-Business Suite Financials, PeopleSoft Enterprise Financial Management, and PeopleSoft Human Capital Management.
ERP Integrator supports general ledger data for the following:
· PeopleSoft Enterprise Financial Management 9.0
· PeopleSoft Enterprise Financial Management 9.1
· Oracle E-Business Suite 11
· Oracle E-Business Suite 12
· Human resource data for PeopleSoft Human Capital Management 9.0
Note: ERP Integrator does not certify full support for PeopleSoft 8.9; however it supports PeopleSoft 8.9 with these exceptions:
o Users can define a PeopleSoft 8.9 source system by selecting a PeopleSoft 9.0 source system on the Source System setup page in ERP Integrator.
o Supports only dimension and data loads. Writing back data and drilling through is not supported. If users attempt to drill through and click the hyperlink on the landing page to access source system pages, an "Error 404 - Not Found" is displayed.
ERP Integrator supports the following EPM target applications (Performance Management Architect and Classic):
· Planning
· Planning enabled for Public Sector Planning and Budgeting
· Financial Management
· Essbase ASO and Essbase BSO
· Any target application supported inside FDM (must be registered via FDM)
These patches are required for ERP Integrator:
· PeopleSoft Enterprise Financial Management 9.0 Bundle #29
· Oracle Data Integrator 10.1.3.6
· Oracle E-Business Suite Compatibility and Patches
The FDM and ERP Integrator drill-through feature supports Oracle E-Business Suite versions 11.5, 12.0.6, and 12.1.1. The following patches are required for Oracle E-Business Suite version 11.5:
· 4396821 and 8307232 (replaces patch 6902648)
Pre-requisite patches for patch 4396821:
· 3262919 - Patch 11i.FWK.H
· 2032040 - WORKFLOW 2.6 FOR APPLICATIONS 11i
· 3180816 - Patch 11i.AD.I
· 2917019 - New Profile Hierarchies: Security, Server and Organization
· 3313291 - AOL JAVA ROLLUP PATCH J
The following patch is required for Oracle E-Business Suite version 12.0.6:
· 8345468:R12.GL.A
Patches are available on the Oracle Support site (https://support.oracle.com).
Late-breaking information about installation of EPM System products is provided in the Oracle Hyperion Enterprise Performance Management System Installation Readme. Review this information thoroughly before installing EPM System products.
If you use the ERP Integrator adapter and are upgrading from release 11.1.1.3 to release 11.1.2.1, do not remove the existing ERP Integrator adapter. Drill through to data loaded using the ERP Integrator adapter is only possible when using the ERP Integrator adapter originally used to load the data. If a new server is being used, be sure to update the adapter options with the new server information.
Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Hyperion 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) and listed in the Oracle Business Intelligence product area:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Hyperion 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):
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
See the FDM Configuration Guide for information regarding language settings and configuration for FDM.
You can upgrade to EPM System Release 11.1.2.1 from the following releases:
Release Upgrade Path From |
To |
11.1.2.0.x |
11.1.2.1 Note that when moving from Release 11.1.2.0.x to Release 11.1.2.1, you use the "Apply Maintenance Release" option in EPM System Installer, instead of following the documented upgrade procedures. |
11.1.1.3.x |
11.1.2.1 |
9.3.3.x* Note: If you were using Performance Management Architect Release 9.3.1, you can download the Performance Management Architect release 9.3.3 from My Oracle Support. |
11.1.2.1 |
9.2.1.x* |
11.1.2.1 |
A release earlier than Release 9.2.1.x |
If you are upgrading from a release earlier than 9.2.1.x, you must first upgrade to a supported release and then upgrade to release 11.1.2.1. For upgrade procedures for the earlier release, see the product installation guides for the interim release to which you are upgrading. |
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 Hyperion Enterprise Performance Management System Installation and Configuration Guide. |
* Does not include ERP Integrator. ERP Integrator supports upgrades 11.1.1.3 or 11.1.2.0 to 11.1.2.1.
Notes:
If you are starting from Release 9.2.x, Oracle recommends the following upgrade path: 9.2.0 to 9.2.1 to 11.1.2.1
If you are starting from Release 9.3.x, Oracle recommends the following upgrade path: 9.3.0 to 9.3.1 to 9.3.3 to 11.1.2.1
If you are starting from Release 11.1.1.x, Oracle recommends the following upgrade path: 11.1.1.0 or 11.1.1.1 or 11.1.1.2 to 11.1.1.3 to 11.1.2.1
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 9.3.1.4.1. Essbase and Shared Services Release 11.1.1.3, however, still synchronize security information. For this reason, if you are using Essbase Release 9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3, as recommended above. Upgrading to Release 11.1.1.3 is not an option for these Essbase releases.
Defect Number |
Description of Fix |
• 9454725 |
The Drillback statement was re-added to the Users error log file. |
• 9529539 |
Log file casesecurity.log is no longer written to a hard-coded path. |
• 9653969 |
USING SAP ADAPTER, TRYING TO “OPEN THE SOURCE SYSTEM” ERRORS AT IMPORT STAGE" |
• 9689849 |
Results now returned consistently when using Find function on Maps screen. |
• 9760973 |
Clicking on Dimension map in Show Conversion Rules screen now navigates to the appropriate row. Note: Patch #5206573 for OracleDB is required. |
• 9845498 |
Fixed a bug that caused an error when importing an XML metadata file that contained logic groups. |
• 9873249 |
FDM no longer throws a data access error when importing XML with large logic fields. |
• 9907165 |
Fixed a connectivity bug that prevented drill through from Financial Management when using OracleDB. |
• 9958980 |
Fixed a bug that could cause “Index was out of range” error when adding a new user. |
• 10062263 |
Clicking AMT to view record details now displays correctly in Internet Explorer 8. |
• 10109877 |
Fixed a bug that caused an error when selecting the second load balance server group when setting up a new application. |
• 10199428 |
Clicking "Select from Inbox" no longer hangs the application when selecting a location that matches the application name. |
• 10244075 |
Fixed a bug that could cause drill through from Planning to fail when amounts include non-standard characters. |
• 10247639 |
COMJNBRIDGE.EXE no longer launches when logging off. |
• 10314214 |
Setting for number of parallel processes in Workbench now correctly shows a maximum of 20. |
• 10355041 |
Fixed a bug that could cause Export to Excel at Validate step to fail for intermediate users. |
• 10379010 |
Fixed a bug that prevented HTML tags from processing correctly in the Intersection Validation report. |
Defect Number |
Adapter |
Description of Fix |
|
Data Extract (Tax) G4-C |
No defects reported. |
|
Enterprise G4-H |
No defects reported. |
• 10059397 |
ERPI FIN-C |
Fixed a bug that could cause "Error Getting Data" message when executing data load rules that take longer than 15 minutes even though file generation does eventually complete. |
• 9094888 |
Essbase G4-H |
LoadAction of adapter corrected to look for load tags "A." |
• 9561208 |
Essbase G4-H |
Essbase error messages trimmed using Essbase Load Rule file to a maximum of 1000 characters. |
• 10302719 |
Essbase G4-H |
Fixed a bug that could cause a runtime error when changing the Page Size value in the FDM Web client. Note: This option is assigned to a Long data type. |
• 10402605 |
Essbase G4-H |
Fixed a bug that could prevent drill through from Essbase to FDM. |
• 9526929, 10363412 |
Financial Management G5-E |
Fixed a bug that could prevent record sets from loading when two different currencies exist in the record set. |
|
Pull G4-D |
No defects reported. |
|
SAP FIN-C |
No defects reported. |
|
Strategic Finance G4-D |
No defects reported. |
Defect Number |
Description of Fix |
• 8371724 |
Encumbrance data is not loading into the AIF_HS_BALANCES table when the target application is Financial Management. |
• 8554158 |
PeopleSoft metadata loads should load members with SetID for a business unit. Currently, only shared SetID members are extracted |
• 8985020 |
When initializing the source system in ERP Integrator, no error messages are displayed in ERP Integrator, even though the process may fail in Oracle Data Integrator. In addition, running the initialization process a second time may produce different results. |
• 9344748 |
If you navigate to the Process Details
page by clicking on the busy icon on the |
• 9407271 |
Unable to register an application with extended ASCII characters in the application name, dimension name, or member name. |
• 9450709 |
The ERP Integrator “Create Integration” security role is not working as expected and allows the user to run processes. |
• 9451103 |
You may experience performance problems when loading exchange rates if you have large amounts of data in the source system. |
• 9467815 |
ERP Integrator HR data load rules should not allow Entity to be null in the Jobcode Property Point of View (POV) mapping details. |
• 9484792 |
Segment names do not display if you set the web browser language to a language for which segment names are not available in the source system. For example, if you set the web browser language to German and the source system languages are English and French, you will not see any segments in the Import Format drop-down list. |
• 9487483 |
When the data load is executed with an incorrect category you can run the process with incorrect category and no errors are displayed when you submit the data rule. |
• 9488223 |
When loading data to Planning, if you used an invalid category in the ERP Integrator data load and it did not exist in the Planning application, Essbase returns an error for an invalid member in the ERP Integrator log but still creates drill region. |
• 9501760 |
The Position Only (PO) model template script should map the “Max Headcount” to “Headcount”. |
• 10100647 |
Executing a metadata rule produces a unique constraint error for PeopleSoft source systems. |
• 10100740 |
Metadata rules for PeopleSoft source systems load all chartfields. |
• 10157581 |
PeopleSoft accounts are duplicated when the accounts have multiple effective dates. |
Defect Number |
Description of Fix |
• 6590727 |
Fixed a bug that could cause “Select from Inbox' feature to fail when browsing nested directories. |
• 6616948 |
Fixed a bug that could cause the Import process to perform slowly. |
• 6863904 |
Fixed a bug that caused the process to fail when exporting a large number of maps to xml. |
• 7209366 |
Fixed a bug that could cause the review level for Financial Management to not demote when the user tries to unsubmit. |
• 8246604 |
An error message is now displayed when xml import fails with a duplicate location. |
• 8556795 |
Memos can no longer be updated after the POV is locked. |
• 8572449 |
Processing of logic no longer fails when importing data with offset date period keys. |
• 8728448 |
Exporting to Excel from a drilldown page no longer throws an error when the target account name contains a pound symbol (#). |
• 8812486 and 8812486 |
Entering user names with extended ASCII characters in the User Maintenance screen no longer causes an error. |
• 8938363 |
Fixed a bug that caused the use of simple logic type "FUN" to fail. |
• 8939473 |
Fixed a bug that caused the use of complex logic type "FUN" to fail. |
• 8984108 |
All Oracle reports now run properly. |
• 9024962 |
Changing of locations in left pane of Process Explorer now works as expected. |
• 9141276 |
User names that contain an apostrophe (‘) can now be added in FDM. |
• 9152273 |
Fixed a bug that could prevent all user-defined dimensions from importing a multi-load file using Batch Loader. |
• 9227362 |
Drilling down on multiple source records now shows correct data for all records. |
Defect Number |
Adapter |
Description of Fix |
• 9363347 |
Data Extract (Tax) G4-C |
Amounts are no longer rounded in the export file. |
|
Enterprise G4-F |
No bugs reported. |
|
ERPI-FIN-B |
No bugs reported. |
• 8587637 |
Essbase G4-G |
Resolved an issue where records could be dropped when exporting files with a large set of data when using SQL as a back end data store. |
• 9327877 |
Financial Management G5-D |
Exporting intercompany transactions to Financial Management using batch processing now works as expected. |
|
Pull G4-C |
No bugs reported. |
|
SAP FIN-B |
No bugs reported. |
|
Strategic Finance G4-C |
No bugs reported. |
Defect Number |
Description of Fix |
• 8622599 |
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. ERP Integrator now supports Hyperion Essbase Classic and supports a single Time dimension. |
• 8629249 |
In some instances, metadata and data rules fail with a “java.lang.Exception: Error: No value to affect to this variable…” error. To work around this problem, run the rule again. |
• 8642982 |
Unable to delete a source system. However, you can modify a source system. |
• 8674271 |
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. |
The following issues are the noteworthy known issues of this patch.
Defect Number |
Known Issue |
13334825 |
The formatting on Microsoft Excel Reports does not output correctly. There is no resolution for this. |
10351740 |
When exporting large records from FDM into Excel 2007, the following errors may occur: “Activereports Excel Export Error. Pages collection or RDF file may be corrupt”or "Import a Memory”. |
12350827 |
<note: Where is best place in Admin Guide to move this for SP2?> In the ERPI 11.1.1.3 release, data loads executed from ERPI or FDM would filter out balance rows if the following criteria was met: - The data rule had a matching Metadata rule for the same Source System, Chart Of Accounts/BU, and Target Application. - The matching Metadata rule would have Single or Concatenated Segment/ChartField mappings where Orphan members were not handle as Root members or Children of a Parent Member. As the Metadata rule would not import all Segment/ChartField members into a Target Application, ERPI would filter out any balance rows for any invalid members. This functionality is desirable when loading from ERPI, but not when loading from FDM based on customer feedback. Therefore in ERPI 11.1.2.x release, balance row filtering has been removed for Data Loads executed from FDM. FDM users are now expected to filter or ignore invalid rows by defining data mappings directly in FDM. |
|
When using Windows 2008 server x64, create the following directory to enable Excel importing and exporting: \Windows\SysWOW64\config\systemprofile\Desktop When using Windows 2008 server x86, create the following directory to enable Excel importing and exporting: \Windows\System32\config\systemprofile\Desktop |
|
Target applications versions 11.1.2 or earlier will not drill through to FDM version 11.1.2.1. |
|
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). FDM 11.1.2 saves all scripts in Unicode format. |
|
<note: Where is best place in Admin Guide to move this for SP1?> 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. |
|
Note: The following does not apply when using IIS7 and Windows 2008. 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. |
|
If you receive an error that reads "To protect your security, Internet Explorer blocked this site from downloading files to your computer. Click here for options..." when a file is exported, Internet Explorer will require a security settings change. > To Change the IE Security Setting: 1. Open Internet Explorer 2. Select Tools > Internet Options. 3. Click the Security tab. 4. Select the Internet icon (globe). 5. Click the Custom Level button. 6. Perform an action: - To set all security settings to Medium-Low, from the Reset to: field, select Medium-Low and click Reset, then click OK. - To set only the Downloads option, in the Settings field, scroll to Downloads and under File Download, select Enable, and then click OK. <dev. note: Move to Tips & Troubleshooting of Admin Guide for sp2> |
|
FDM cannot be installed on a Citrix server. Citrix can publish the URL to an FDM installation that is hosted on a non-Citrix server. |
12775346 |
Drill through does not work for alternate adapters in FDM if the alternate adapter does not have the year dimension set. |
Defect Number |
Known Issue |
7674138 |
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. |
8569796 |
When running a metadata load into a Classic Financial Management application, the rule fails with the following error: No top-level members specified in hierarchy. To work around the problem, if you create a parent for all the orphan members, make sure the member meets all the criteria to be a parent. |
9061901 |
When registering a Classic target application, the drop-down list does not show new applications in the list. To work around the problem, change the target application type to another type, then return to the original target type. This will refresh the list. |
9101448 |
If you are using an HR source system, you define import formats, but it is not necessary to define the import format mappings. Since it is not necessary to define mappings, the details on the Import Format page should be hidden from the user to prevent confusion. |
9111998 |
When you run a metadata load in ERP
Integrator and attempt to extract an E-Business Suite Japanese Language chart
of accounts segment, the following error occurs in Oracle Data Integrator: |
9166830 |
The traversal order is not validated for concatenated mappings on the Metadata page. |
9221240 |
Members with an apostrophe (single quote) in the name are not displayed correctly in the ERP Integrator Member Selector. |
9274346 |
Currently the precision of the AIF_EBS_GL_BALANCES_STG table is not the same as the Oracle E-Business Suite table GL_BALANCES for the "amounts." This causes the following OracleDB precision error: ORA-01438: value larger than specified precision allowed for this column. |
9375192 |
Validations should occur to ensure that null values are not allowed in Position models. Specifically: For the Employee Property VOB, the Position value should not be blank. For all POV types, the values in Budget Item, Year, and Period should not be blank. If left blank, the data load to Planning fails with a “Source columns don't match result columns” error. |
9398428 |
For balance sheet accounts, you must only write-back for a single period because ERP Integrator does not accumulate the change in the account value over time, using the previous period as the starting balance. |
9392863 |
In ERP Integrator, the page may not refresh as expected when moving between the Member Mapping and Write-Back Mapping pages. |
9460283 |
On the Target Application page, if you click Refresh Metadata after deleting a dimension in the target application the dimension still displays in the list. |
9461292 |
When defining an import format, the ICP automatically-created default member mapping is not mapped when Entity is mapped. |
9589154 |
The ICP Default field should not be shown when a chart of accounts has an intercompany segment. |
9862700 |
When creating a metadata mapping, the drop-down list for Starting Parent should not show the parent value twice. |
10038358 |
Intermittent errors appear when returning from the Process Details page to the Metadata page. |
10041509 |
ERP Integrator experiences issues with case-sensitive collations in SQL Server. The following error may appear when accessing the Source Systems page: [FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid object name aif_lookup_values |
10060413 |
The date and time is currently using the server time zone and not the client's local time zone. |
10060450 |
The process log is not localized. |
10134184 |
When extracting communication load exchange rates, users may experience slow performance. We recommend that you run the Oracle Gather Schema stats process if you experience performance issues with the exchange loads. |
10142059 |
Running the Process Loaded Human Resources data task exposes positions that have Position Start Dates after the HR Data load's 'As of' date. Exposed positions do not have the Position Name, Position Number, and so on. |
10251396 |
The Category mapping search does not filter by the target category. |
10305331 |
When searching for a location on the Metadata page, you have the ability to enter the target application name or partial name. However, when you enter the first few characters of the application name, no search results are returned, even though the application exists. To work around this issue, click the Advanced Search button to enter search conditions. |
10315139 |
When navigating from Process Details to the Data Load page, the following error message intermittently displays: [FMWGEN][SQLServer JDBC Driver]Invalid parameter binding(s). |
10395854 |
ERP Integrator should not allow a user to save an import format if the source system is PeopleSoft Human Capital Management and the target application is not a Public Sector Budgeting application. |
10426860 |
On the HR Data Load page, you can copy existing rule mappings. ERP Integrator should not allow users to copy a mapping across Performance Management Architect and Classic target applications. For example, if defining mappings for a Classic application, users should only be able to copy the rule mappings from another Classic application. |
10649914 |
A drill region should not be created for average daily balance loads. |
11729389 |
The creation of the drill region fails when member names contain multi-byte characters. |
11864062 |
Adding multiple adjustment periods on the Period Mapping page causes a Null Pointer Exception error. To work around this problem, do not use the Browse button to select the period key. Instead, follow these steps: 1. On the Period Mapping page, select the Adjustment Period Mapping tab. 2. Select the source system, and then click Add. 3. Click Browse to select the Calendar and Adjustment Period. 4. Enter the GL Period Year. 5. Manually enter the Period Key. Do not use the Browse button. Note: You must enter the period key manually and make sure not to enter this value first. If you first fill in the date manually it is cleared when adding the adjustment period. |
11869798 |
Data load with Adjustment Period selected fails when source has multiple years of Adjustment periods mapped. |
|
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 caught 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. |
|
For Oracle E-Business Suite, you can drill through to the source system from actual, statistical data. If you drill through from budgets or encumbrance data, actual data is displayed. |
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 work flow as well because it is separate from the standard workflow. See the section titled "Storing and Retrieving Temporary Variables" in the FDM Administrator's Guide for additional information.
When an App Creation Group in Load Balance Manager is specified, only local users of the NT group may add or modify FDM applications from the FDM login screen. External users added to the NT group (user added under MSAD, for example), will not have the ability to add or modify applications from the FDM login screen.
Problem: Intersection Validation reports fail to generate on Windows 2008 environment.
Detail: Error message "Access denied java script error" message generated when using the option to save the report.
This is a known Microsoft issue related to cross-domain accessibility.
Solution: Install MSXML 3.0 SP7 using the following link:
http://support.microsoft.com/kb/308480
Drill through will not work if the original values in the Source column of the tDataSeg are manipulated. It is required that the data in the tDataSeg Source columns are sent back to the source system. If the data is manipulated outside of the source in the import format via scripts, concatenations, or parsing, the data will no longer match the source data and result in an error.
Problem: With IIS installed and ASP.Net enabled, the internal install completes but when the Finish button is clicked the following error is displayed:
Unable to get ActiveX Control named (IIS://localhost/W3SVC/1/Root). Make sure Internet Information Services is installed.
Solution: IIS 6 Metabase compatibility is required for the FDM Web server when installed on Windows 2008. For information on enabling IIS 6 Metabase compatibility, refer to the following Microsoft article:
http://technet.microsoft.com/en-us/library/bb397374(EXCHG.80).aspx
In the FDM Task Manager there are multiple batch scripts for multiple FDM applications that are configured to run. The Batch Scripts that are configured for "Parallel" processing are marked as "Succeeded" in the task manager within seconds while the process is running. The Batch Scripts that are configured for "Serial" processing are marked as "Running" until completion. Other scripts will not execute until the batch are completed.
When a Serial batch process is executed, it uses a single upsappsrv.exe process to run the batch until completion. The task manager is tied to the single upsappsrv.exe process and will not update the status until it receives a success or failure message from the application server process. For tasks that are "Parallel" processing, multiple upsappsrv.exe processes are spawned during the workflow and the task manager is not able to track the status of them. Therefore, it marks the process as "Succeeded" and the process runs in the background until completion.
<move to admin guide for sp2>12350827 In ERPI 11.1.1.3, the Metadata rule would not import all Segment/ChartField members into a Target Application, ERPI would filter out any balance rows for any invalid members. This functionality is desirable when loading from ERPI, but not when loading from FDM based on customer feedback. Therefore in ERPI 11.1.2.x release, balance row filtering has been removed for Data Loads executed from FDM. FDM users are now expected to filter or ignore invalid rows by defining data mappings directly in FDM.
<12409210: move to admin guide for sp2>When you use Conditional Mapping, if the Description field is used in the mapping, FDM cannot Drill Up on the mapped value. When searching for the source values, multiple rows can be returned with different descriptions. Since the exact description cannot be found, the Drill Up will not always return the correct member. This does not affect the mapping itself and FDM will map the value correctly. Oracle recommends not using the Description field in conditional mapping and instead use a custom dimension.
The location of Web application deployment has changed. All references to this location in the documentation should be updated from:
MIDDLEWARE_HOME/user_projects/epmsystem1/domains/<DomainName>
To:
MIDDLEWARE_HOME/user_projects/domains/domainName
where domainname is the name of the WebLogic domain.
The ODL logging location for Web applications has changed. All references in the documentation should be updated from:
MIDDLEWARE_HOME/user_projects/epmsystem1/diagnostics/logs/<ProductName>
To:
MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/<ServerName>/logs
where <ServerName> is the name of the WebLogic-managed server.
The FDM Workbench cannot connect to an instance of the FDM Load Balancer running a different version of FDM. It can only connect to an instance of the Load Balancer that is the same version.
<move to admin guide for sp2>Drill through refers to the navigation from a value in one data source to corresponding data in another source. Drillback refers to navigating from a value in FDM to another value in FDM.
<12425984 move to admin guide for sp2>In order to drill back from FDM to ERPI, update the correct workspace information in web.config located under:
%Hyperion_HOME%\products\FinancialDataQuality\WebServerComponents\Website
Look for following lines in the file and replace erpi.us.oracle.com:7777 with the correct workspace server and port number in both the places:
<setting
name="Hyperion_FDM_DrillService_GetURL_DrillServiceService"
serializeAs="String">
<value>http://erpi.us.oracle.com:7777/aif/services/DrillService</value>
</setting>
<setting
name="Hyperion_FDM_ERPIDrillService_DrillServiceService"
serializeAs="String">
<value>http://erpi.us.oracle.com:7777/aif/services/DrillService</value>
</setting>.
The section titled “Importing Metadata from Excel” in Chapter 18 of the FDM Administrator’s Guide includes a statement that reads “Uploaded Excel files should be MS Office 2002-2003 (.xls) format compliant.” This should read “Uploaded Excel files should be MS Office 2003 or 2007 (.xls or .xlsx) format compliant.”
Problem: When you copy and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid.
Solution: Copy from the HTML version of the document.
<12539601 move to admin guide for sp2>In the section titled "Creating FDM Applications", the note reads
Note: It is highly recommended to create the <product productid="FDM"/> application on the data server. When <product productid="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 <product productid="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 <product productid="FDM"/> Inbox folder.
This should be updated:
Note: It is recommended that the File Share be placed on a high available file server. FDM uses Bulk Insert to import data. The Windows account running the database service must have read and write access to the FDM file share. In addition, the FDM DCOM account must have read and write access to the FDM file share.
When upgrading from Release 11.1.1.3 to Release 11.1.2.1, you must create an explicit member mapping when creating a data load rule loading data from PeopleSoft to a Financial Management target application.
To create the explicit mapping:
1. In the Tasks pane, select Member Mapping.
2. Select the Location.
3. Select the Dimension and type of mapping (Like).
4. Click Add.
5. Enter source value as <BLANK>
6. Enter the Target Value: [ICP None].
When merging metadata into an existing Financial Management application (both through Financial Management and ERP Integrator), if the generated XML did not specify an Alias entry for a Custom dimension, the existing Custom dimension Alias value is dropped. This behavior did not cause issues in ERP Integrator 11.1.1.3 metadata load rules, data load rules, or drill-through for Financial Management applications, nor will it cause issues in ERP Integrator 11.1.2.1 for upgraded Financial Management applications. However, users will notice that after upgrading from ERP Integrator 11.1.1.3 to Release 11.1.2.1, when performing drill-through on an upgraded Financial Management application (or refreshing the metadata on an upgraded Financial Management application), one or more Custom dimensions may no longer show the Alias value as the dimension name (particularly if the Custom dimension was mapped in a metadata load rule).
Note: This is not an issue in ERP Integrator, as it is accurately reflecting the current Custom dimension Alias value in the upgraded Financial Management application. However, if users want to restore the original Custom dimension Alias value, they should make this change directly in Financial Management, and then refresh the metadata on the Target Application page in ERP Integrator.
The most recent version of each EPM System product guide is available for download from the Enterprise Performance Management System Documentation area of the OTN Web site (http://www.oracle.com/technology/documentation/epm.html). For faster access to the documentation, you can also use the Enterprise Performance Management 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 E-Delivery 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 table outlines the FDM release compatibility with target and source applications.
FDM |
Essbase / Planning |
Financial Management |
Hyperion Enterprise |
Hyperion Strategic Finance |
9.3 |
9.3.x – 11.1.1 |
9.3.1, 11.1.1 |
6.4.x |
|
9.3.1 |
9.3.x – 11.1.1 |
9.3.1, 11.1.1 |
6.4.x |
|
11.1.1 |
9.3.x – 11.1.1 |
9.3.1, 11.1.1 |
6.4.x |
|
11.1.1.1 |
9.3.x – 11.1.1.1 |
9.3.1, 11.1.1.1 |
6.4.x |
11.x |
11.1.1.2 |
9.3.x – 11.1.1.2 |
9.3.1, 11.1.1.1, 11.1.1.2 |
6.5 – 6.5.1 |
11.x |
11.1.1.3 |
9.3.x – 11.1.1.3 |
9.3.1, 11.1.1.1, 11.1.1.3 |
6.5 – 6.5.1 |
11.x |
11.1.2 |
11.1.2 |
11.1.2 |
6.5 – 6.5.1 |
11.1.2 |
11.1.2.1 |
11.1.2.1 |
9.3.1 - 11.1.2.1 |
6.5 - 6.5.1 |
11.1.1.2 - 11.1.2.1 |
The following table lists Oracle Hyperion Financial Data Quality Management, Fusion Edition adapters and the compatible versions of Oracle Enterprise Performance Management System and third-party products.
FDM Adapter |
FDM |
Essbase/ Planning |
Financial Management |
Financial Management Intercompany |
Hyperion Enterprise |
Hyperion Strategic Finance |
Oracle E-Bus. Suite GL |
SAP |
ERP Integrator |
PULL-AG31 |
9.3.x - 11.1.1 |
|
|
|
|
|
|
|
|
PULL-G3-H |
9.3.x - 11.1.1 |
|
|
|
|
|
|
|
|
PULL-G3-I |
9.3.1 - 11.1.1 |
|
|
|
|
|
|
|
|
PULL-G3-J |
9.3.1 - 11.1.1.1 |
|
|
|
|
|
|
|
|
PULL-G4-A |
9.3.1 – 11.1.1.2 |
|
|
|
|
|
|
|
|
PULL-G4-B |
9.3.1 – 11.1.1.3 |
|
|
|
|
|
|
|
|
PULL-G4-C |
9.3.1 - 11.1.2 |
|
|
|
|
|
|
|
|
PULL-G4-D |
9.3.1 - 11.1.2.1 |
|
|
|
|
|
|
|
|
PULL G4-G |
9.3.3 |
|
|
|
|
|
|
|
|
EXT-G3-A |
9.3.x - 11.1.1 |
|
|
|
|
|
|
|
|
EXT-G3-B |
9.3.x - 11.1.1.1 |
|
|
|
|
|
|
|
|
EXT-G4-A |
9.3.1 – 11.1.1.2 |
|
|
|
|
|
|
|
|
EXT-G4-B |
9.3.1 – 11.1.1.3 |
|
|
|
|
|
|
|
|
EXT-G4-C |
9.3.1 - 11.1.2.1 |
|
|
|
|
|
|
|
|
EXT-G4-G |
9.3.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ESS7X-GG31 |
9.3 |
9.2.x - 9.3.1 |
|
|
|
|
|
|
|
ESS7X-G3-H |
9.3 |
9.2.x - 9.3.1 |
|
|
|
|
|
|
|
ESS7X-G3-I |
9.3.x – 9.3.1 |
9.2.x – 9.3.1 |
|
|
|
|
|
|
|
EB7x-G3-J |
9.3.x – 9.3.1.1 |
9.2.x - 9.3.1 |
|
|
|
|
|
|
|
EB9x-G4-A |
9.3.1 - 11.1.1 |
9.2.x - 9.3.1 |
|
|
|
|
|
|
|
EB9x-G4-B |
9.3.1.1 – 11.1.1 |
9.2.x - 9.3.1 |
|
|
|
|
|
|
|
EB9x-G4-C |
9.3.1.1 – 11.1.1.1 |
9.2.x – 11.x |
|
|
|
|
|
|
|
EB11x-G4-D |
9.3.1.1 - 11.1.1.2 |
9.2.x – 11.x |
|
|
|
|
|
|
|
EB11x-G4-E |
11.1.1.3 |
9.2.x – 11.x |
|
|
|
|
|
|
|
ES11x-G4-G |
9.3.1 - 11.1.2 |
9.2.x - 11.1.2 |
|
|
|
|
|
|
|
ES11x-G4-H |
9.31 - 11.1.2.1 |
9.2.x - 111.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HFM4x-GG31 |
9.3 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
HFM4x-G3-H |
9.3 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
HFM4x-G3-I |
9.3 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
HFM9x-G3-K |
9.3 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
9.3 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
|
FM4x-G3-M |
9.3 |
|
9.3.1 - 11.1.1.2 |
|
|
|
|
|
|
HFM9x-G4-A |
9.3.1 – 11.1.1 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
HFM9x-G4-B |
9.3.1.1 – 11.1.1 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
FM9x-G4-G |
9.3.3 |
|
9.3.1 - 11.1.1 |
|
|
|
|
|
|
FM11x-G5-A |
11.1.1.1 -11.1.1.3 |
|
9.3.1 - 11.1.1.1 |
|
|
|
|
|
|
FM11xG5-B |
11.1.1.2 |
|
9.3.1 - 11.1.1.2 |
|
|
|
|
|
|
FM11xG5-C |
11.1.1.3 |
|
9.3.1 - 11.1.1.3 |
|
|
|
|
|
|
FM11x-G5-D |
11.1.1.3 - 11.1.2 |
|
9.3.1 - 11.1.2 |
|
|
|
|
|
|
FM11x-G5-E |
11.1.2.1 |
|
9.3.1 - 11.1.2.1 |
|
|
|
|
|
|
HFM4i-G3-I |
9.3 |
|
|
9.3.1 - 11.1.1 |
|
|
|
|
|
FM4i-G3-M |
9.3 |
|
|
9.3.1 - 11.1. |
|
|
|
|
|
HFM9i-G3-K |
9.3 |
|
|
9.3.1 - 11.1.1 |
|
|
|
|
|
HFM9i-G4-A |
9.3.1 - 11.1.1 |
|
|
9.3.1 - 11.1.1 |
|
|
|
|
|
HFM9i-G4-B |
9.3.1.1 – 11.1.1 |
|
|
9.3.1 - 11.1.1.1 |
|
|
|
|
|
FM9i-G4-G |
9.3.3 |
|
|
9.3.1 - 11.1.1 |
|
|
|
|
|
FM11i-G5-B |
11.1.1.2 |
|
|
9.3.1 - 11.1.1.2 |
|
|
|
|
|
FM11i-G5-C |
11.1.1.3 |
|
|
9.3.1 - 11.1.1.3 |
|
|
|
|
|
FM11i-G5-D |
11.1.1.3 - 11.1.2 |
|
|
9.3.1 - 11.1.2 |
|
|
|
|
|
FM11i-G5-E |
11.1.2.1 |
|
|
9.3.1 - 11.1.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HET6x-GG31 |
9.3 |
|
|
|
6.4 – 6.5 |
|
|
|
|
HE6x-G3-H |
9.3 |
|
|
|
6.4 – 6.5 |
|
|
|
|
HE6x-G3-I |
9.3 |
|
|
|
6.4 – 6.5 |
|
|
|
|
HE6x-G4-A |
9.3.1 - 11.1.1 |
|
|
|
6.4 – 6.5 |
|
|
|
|
HE6x-G4-B |
9.3.1 – 11.1.1 |
|
|
|
6.4 – 6.5 |
|
|
|
|
HE6x-G4-C |
9.3.1.1 – 11.1.1.1 |
|
|
|
6.4 – 6.5.1 |
|
|
|
|
HE6x-G4-D |
9.3.1.- 11.1.1.2 |
|
|
|
6.4 – 6.5.1* |
|
|
|
|
HE6x-G4-E |
|
|
|
6.4 – 6.5.1* |
|
|
|
|
|
HE6x-G4-F |
9.3.1 - 11.1.2 |
|
|
|
6.4 – 6.5.1* |
|
|
|
|
HE6x-G4-G |
9.3.3 |
|
|
|
6.4 - 6.5.1 |
|
|
|
|
HE6x-G4-H |
9.3.1 - 11.1.2.1 |
|
|
|
6.4 - 6.5.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SF11x-G3-A |
11.1.1.1 |
|
|
|
|
11.1.1.1 |
|
|
|
SF11x-G4-A |
11.1.1.2 |
|
|
|
|
11.1.1.2 |
|
|
|
SF11x-G4-B |
9.3.1.- 11.1.1.3 |
|
|
|
|
11.1.1.2, 11.1.1.3 |
|
|
|
SF11x-G4-C |
9.3.1 - 11.1.2 |
|
|
|
|
11.1.1.2 - 11.1.2 |
|
|
|
SF11x-G4-D |
9.3.1 - 11.1.2.1 |
|
|
|
|
11.1.1.2 -11.1.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
EBS-FIN-A |
11.1.1 |
|
|
|
|
|
11.5.10 cu2 |
|
|
EBS-FIN-B |
11.1.1 – 11.1.1.1 |
|
|
|
|
|
11.5.10 cu2 |
|
|
EBS-FIN-C |
11.1.1.2 |
|
|
|
|
|
11.5.10 cu2, 12.0.6, 12.1.1 |
|
|
|
|
|
|
|
|
|
|
|
|
SAP-FIN-A |
11.1.1.2 – 11.1.2 |
|
|
|
|
|
|
R/3 4.6c, ECC 6.0 |
|
SAP-FIN-B |
11.1.1.2 - 11.1.2 |
|
|
|
|
|
|
R/3 4.6c, ECC 6.0 |
|
SAP-FIN-C |
11.1.1.2 - 11.1.2.1 |
|
|
|
|
|
|
R/3 4.6C and 4.7, ECC 6 |
|
|
|
|
|
|
|
|
|
|
|
ERPI_FIN-A |
11.1.1.3 |
|
|
|
|
|
|
|
11.1.1.3 |
ERPI_FIN-A1 |
11.1.1.3 |
|
|
|
|
|
|
|
11.1.1.3 |
ERPI_FIN-B |
11.1.2 |
|
|
|
|
|
|
|
11.1.2 |
ERPI_FIN-C |
11.1.2 - 11.1.2.1 |
|
|
|
|
|
|
|
11.1.2.1 |
* Drill through from Enterprise to FDM is only enabled when using FDM 11.1.1.3 or higher and Enterprise 6.5.1.
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
Copyright © 2011, Oracle and / or its affiliates. All rights
reserved.
http://www.oracle.com