About this Patch

This patch can be installed in two modes:

1. Apply this patch to use Internet Explorer release 11 in standards mode instead of in Enterprise Mode. After you apply this patch, you can no longer use Enterprise Mode. You must apply the 11.1.2.3.700 PSU for all EPM products in your deployment. For details, see the "Prerequisites" section.

Note: This patch supports Internet Explorer 11 for ADF mode only; this patch does not support Internet Explorer 11 in the Classic view.

2. Standalone: Install this patch to take bug fixes for FDMEE. Prerequisites patches listed in “Prerequisites” are not applicable in this mode.

This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.

Caution: Oracle urges you to carefully read and understand the following requirements. Failure to comply may result in applying a patch that can cause your application to malfunction, including service interruptions, loss of data, or both.

Patch Type

This is a patch set update (PSU).

Supported Paths to this Patch

You can apply this patch to Release 11.1.2.3.500 and later.

Prerequisites

Required Microsoft Patch

Microsoft has identified a security issue that could compromise Windows-based systems. Before installing this patch, verify that the Visual C++ 2005 Redistributable Package installed on the computer is current. You may search and download the latest Visual C++ 2005 Redistributable Package from:

http://www.microsoft.com/en-us/download/default.aspx

Required User Rights

The user applying the patch should be the user who was set up to install and configure EPM System products. Required user privileges or rights:

Windows:

Use the user account that has Local administrator rights and was set up for installation and configuration. This user is an administrator and is the same for all EPM System products. Assign local policies if required by the product. Such assignments typically are: “Act as part of the operating system, Bypass traverse checking, Log on as a batch job, Log on as a service.”

UNIX/Linux:

Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME. If you installed other Oracle products, the user who installed EPM System products must be in the same group as the user who installed the other Oracle products. OPatches are not intended to be applied using a root user.

Other Required Patches

1. Ensure that this product's 11.1.2.3.500 patch is applied first. All patches must be applied on any machines where Foundation Services is installed. After all patches are deployed, you must redeploy the web applications.

2. If you are using WebLogic Application Server, apply WebLogic Application Server patch 17437110 for Release 10.3.6 to use Simplified Chinese and Traditional Chinese language settings when using Internet Explorer 10 and Internet Explorer 11 on Windows 8 and Windows 8.1.

For instructions on applying the patch, see Oracle Smart Update: Applying Patches to Oracle WebLogic Server.

3. Apply ADF MLR patch 21240419.

4. Apply these required EPM System release 11.1.2.3.700 PSUs first:

· Apply Oracle Hyperion Shared Services 11.1.2.3.700 PSU - 20675028. Apply the patch to all computers in the deployment.

· Apply Oracle Hyperion Enterprise Performance Management Workspace 11.1.2.3.700 PSU - 20612400. Apply to all computers with Foundation Services deployed.

5. For the rest of the products, apply the product patch on the computer where the product is deployed. Use the table below to find EPM product 11.1.2.3.700 PSU patch numbers. If the product is not listed, then it does not have a 11.1.2.3.700 PSU, and no action is needed.

Note: For Oracle Hyperion Calculation Manager, apply the patch on all computers where Oracle Hyperion Planning, or Oracle Hyperion Financial Data Quality Management Enterprise Edition, or Oracle Essbase is deployed.

Note: If you are using IBM WebSphere Application Server, you must redeploy the EPM System web applications after applying EPM System release 11.1.2.3.700 PSUs.

Product	11.1.2.3.700 PSU Bug Number
Oracle Data Relationship Management	21107706
Oracle Hyperion Calculation Manager	21292109
Oracle Hyperion Disclosure Management	20619384
Oracle Hyperion Financial Close Management	20768349
Oracle Hyperion Financial Data Quality Management Enterprise Edition	20779592
Oracle Hyperion Financial Management	20955781
Oracle Hyperion Financial Reporting	20838970
Oracle Hyperion Performance Management Architect	20929569
Oracle Hyperion Planning	20643564
Oracle Hyperion Profitability & Cost Management	20915688
Oracle Hyperion Reporting and Analysis Framework	20768325
Oracle Hyperion Tax Provision	21219363
Oracle Hyperion Web Analysis	20880421

Supported Platforms

This release applies to all supported platforms.

Supported Languages

This patch supports all languages of the base release.

Release 11.1.2.3.000 PSU 11.1.2.3.700 New Features

See the Oracle Hyperion Financial Data Quality Management, Enterprise Edition 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.

Enhanced Exclude Zero Balance Support for E-Business Suite (EBS)

When excluding zero balances from EBS, you can now exclude accounts with no activity for the period, or exclude accounts with net zero balances for the period. Data rules with exclude options now default to the exclude with net activity option. This feature is not supported in PeopleSoft.

Defects Fixed in this Patch

Defect Number	Defect Fixed
• 21138792	Support global user mode for member validation in data load mapping.
• 20910994	The import of a SAP BW adapter fails when a cube already exists in the target application.
• 20897343	Export to Essbase does not work.
• 20890916	Unable to import navigable attribute from SAP.
• 20882153	The Data Load Workbench shows an error when the currency is not ISO.
• 20855082	A file import error occurs, and FDMEE shows the message “No module named AIF.”
• 20835979	COLUMN_ORDER was incorrect in the Hyperion Financial Management data export file if there were more 10 or more custom dimensions.
• 20778841	When an Essbase calculation script failure occurs, the script does not halt the process or adjust the fish color status.
• 20766903	A PS General Ledger data load fails when FDMEE release 11.1.2.3.530 is applied on the SQL server.
• 20744117	Support the global user setting for the target application during the check process.
• 20744105	Calculation script errors are not flagged as errors in the Check reports.
• 20744078	When calling a calculation script from the Check Entity rule, parameters are not passed and the script does not evaluate passed parameters.
• 20733001	JD Edwards integration fails at the date conversion.
• 20682783	Change Check Rule example in Oracle Hyperion Financial Data Quality Management, Enterprise Edition Administrator's Guide.
• 20677404	After a POV is locked, you can delete the data from the staging table using the Delete button on the Data Load Workbench page.
• 20631845	FDMEE should be accessible and functional in release 11.1.2.3.700 with Internet Explorer 11, and Enterprise Mode should be disabled.
• 20614454	Mappings in the import format are duplicated when Lifecycle Management is rerun.

Known Issues

The following issues are the noteworthy known issues of this patch.

21123706 – In Import Formats, if you filter on a name only and the filter includes a non-file, then the error “ATTRIBUTE SOURCESYSTEMTYPE IS REQUIRED” is returned.

Workaround: When you filter on a source system type or source system and then filter on the name, the error does not occur.

20244709 -- EBS and FUSION SOURCE imports require a full refresh of data load rules after upgrading from an 11.1.2.2 release.

18665000 -- Export to Excel works for small data sets, but not for a large data set.

Workaround: Apply ADF patch 20392011.

18225596 -- In Lifecycle Management (LCM), the import of a custom script definition fails the first time, but imports correctly the second time.

18084833 -- The Simplified/Traditional Chinese language setting is not maintained on the login page or language selection list using Internet Explorer 10.

18014889 -- A script error occurs when adding criteria values on the Complex Logic Criteria Window.

Workaround: First in Internet Explorer, disable the "Display a notification about every script error" setting in Tools, then Internet Options, and then Advanced. By default this setting is disabled. Next, always type values in the Criteria value field on the Complex Logic Criteria Account popup.

17424353 -- When exporting a dimension to Excel, maps which have #SCRIPT do not have the associated script exported.

17013677 -- In Lifecycle Management (LCM), the export of artifacts from release 11.1.2.2.00 to 11.1.2.3.00 in an upgraded environment gives an invalid application name message. To correct update the component name in the registry, complete the steps below:

> To update the component name:

1. Generate an EPM Registry report.

2. In the EPM Registry report, search for 1.AIF.

The name should be FDM Enterprise Edition and not ERP Integrator.

3. Search for the component AIF_PRODUCT.

The name should be FDM Enterprise Edition and not ERP Integrator.

4. Get the object ID for the AIF_Product component.

5. From a SQL Client, connect to the HSS database, and run the following queries:

update hss_component set COMPONENT_NAME = 'FDM Enterprise Edition' where COMPONENT_ID = '1.AIF';

UPDATE HSS_COMPONENT_PROPERTY_VALUES SET PROPERTY_VALUE = 'FDM Enterprise Edition' WHERE PROPERTY_NAME = 'appDisplayName' AND COMPONENT_ID = <Object ID from Registry report>;

Commit;

6. Run the EPM Registry report again, and search for any references to ERP Integrator.

There should be no reference to ERP Integrator.

16870509 -- An error message occurs when importing .XLSX file type journals and map loader file. The journal load and mapping table load fail. Files in .XLSX format are not supported.

Applying this Patch

The section includes important information about applying this patch for Oracle Hyperion Financial Data Quality Management Enterprise Edition.

To apply the ODI Pre-Requisite Patch 17178347:

1. Stop the FDMEE service and log off any ODI components (for example, ODI Studio and the standalone agent).

2. Download ODI Patch 17178347 from the My Oracle Support site.

3. Copy the file p17178347_111170_Generic.zip to:

MW_HOME\odi\OPatch (replace the value for MW_HOME for your environment. Default location C:\Oracle\Middleware)

4. Change the directory to: MW_HOME\odi\OPatch

5. Unzip the p17178347_111170_Generic.zip.

6. Run the opatch as follows:

opatch.bat apply MW_HOME\odi\OPatch\17178347\oui -oh MW_HOME\odi -jre MW_HOME\jdk160_35

To apply the FDMEE release:

1. Stop the FDMEE service.

2. Change the directory to: %EPM_ORACLE_HOME%\OPatch

(Replace the values for EPM_ORACLE_HOME for your environment). For example, specify:

c:\oracle\middleware\epmsystem11R1\opatch

3. Run the opatch as follows (replace the values for EPM_ORACLE_HOME, MW_HOME and EPM_ORACLE_INSTANCE for your environment):

opatch apply 20779592 -oh %EPM_ORACLE_HOME% -jre %MW_HOME%\jdk160_35

For example, for Windows enter:

opatch.bat apply C:\Oracle\Middleware\EPMSystem11R1\OPatch\20779592 -oh C:\Oracle\Middleware\EPMSystem11R1 -jre C:\Oracle\Middleware\jdk160_35

For Linux, enter:

opatch apply /u01/Oracle/Middleware/EPMSystem11R1/OPatch/20779592 -oh /u01/Oracle/Middleware/EPMSystem11R1 –jre /u01/Oracle/Middleware/jdk160_35

All database schema changes and ODI Scenario changes are updated during the FDMEE Server startup. Review the FDMEE server log (for example, ErpIntegrator0.log) after a successful startup. Errors due to objects (tables, indexes) already existing can be ignored. This happens when you apply the patch more than once.

4.    Add the following rule to the OHS configuration file:

%EPM_ORACLE_INSTANCE%\httpConfig\ohs\config\OHS\ohs_component\epm_rewrite_rules.conf

(for example, specify:

C:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\epm_rewrite_rules.conf)

RewriteRule ^/aif/static/(.*) /epmstatic/aif/$1 [PT]

This step is not required if you have already performed it as part of the 11.1.2.3.XXX patchset update application.

5. Register the Hyperion Financial Management (HFM) Adapter.

If you have applied 11.1.2.3.XXX, first unregister the HFM adapter by running UnRegisterHFM.vbs from:

C:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\lib\Windows

To Register the HFM Adapter, run the EPM System Configuration tool, and then select FDMEE > Register HFM Adapter.

6. If you are running JDE or SAP BW Adapter import the following Adapter Projects:

· PROJ_JDE_Adapter_Project.xml

· PROJ_SAP_BW_Adapter_Project.xml

· To import using ODI Studio:

a. Log in to the Work Repository FDMEE.

b. Go to Designer->Project.

c. Select Import Project, then IMPORT_UPDATE for mode, and then Project File from the directory:

C:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\11.1.2.3.00\workrep

7. Update the EPM Instance with the new report batch scripts:

Copy:

%EPM_ORACLE_HOME%/products/FinancialDataQuality/bin/runreport.bat.template

to:

%EPM_ORACLE_INSTANCE%/FinancialDataQuality/runreport.bat

For UNIX, copy the following files:

o runreport.sh.template

o runbatch.sh.template

o encryptpassword.sh.template

This step is not required if you have already performed it as part of the 11.1.2.3.XXX patchset update application.

8. Start the FDMEE service.

9. Restart the HTTP Server.

Rolling Back this Patch

To roll back a patch:

1. Stop FDMEE service.

2. From a command line, change the directory to:

<EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

3. To roll back the patch, enter the following command on one line:

Windows:

opatch.bat rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_35

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1.

The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:

./opatch rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME> /jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME> is
v
$HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

4. Import the ODI Scenario from:

C:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\11.1.2.3.00\workrep

5. All users should now clear cached files from their browsers.

Troubleshooting FAQs

Why do I get the following patch conflict error message when running OPatch?

If the patch that you apply conflicts with a previously applied patch, you may receive the following error message when running OPatch:

Patch(es) <PreviousPatch#> conflict with the patch currently being installed (<NewPatch#>).

If you continue, patch(es) <PreviousPatch#> will be rolled back and the new patch (<NewPatch#>) will be installed.

If a merge of the new patch (<NewPatch#>) and the conflicting patch(es) (<PreviousPatch#>) is required, contact Oracle Support Services and request a Merged patch.

This error is returned when one patch attempts to update a previously patched file. When this conflict happens, you can either (1) roll back the previous patch and apply the new patch (this action might be appropriate if the previous patch was not critical) or (2) request a “merged patch” consisting of the new patch and the patch that it conflicts with. To request a merged patch, contact your Oracle Support representative.

Why do I get the OUI-67078 warning message when applying OPatch?

This warning means that the patch being applied is a superset of a patch already on the deployment and the existing patch will be rolled back. The following snippet shows the context of this warning.

The following warnings have occurred during OPatch execution:
1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion
-----------------------------------------------------------------------------------
OPatch Session completed with warnings.

How can I find out which releases and patches of EPM System products are installed in a deployment?

In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are installed in an Oracle Home. For example, enter the following command on one line:

Windows:

opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_35

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_35 –invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?

When patching an .EAR file for an application, you may need to delete the cached files in the following folders in order to see the changes provided with the patch:

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/tmp/

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/cache