Oracle Hyperion Financial Reporting
[NOTE TO WRITERS: Go to the File or Document properties and change the title. The correct entry for Author and Company are provided in the template.]
Release 11.1.2.3.700 Patch Set Update (PSU): 11.1.2.3.700
Readme
Defects Fixed in this Patch (20838970)
Defects Fixed in Patch 11.1.2.3.511 (20729638)
Defects Fixed in Patch 11.1.2.3.508 (20230795)
Defects Fixed in Patch 11.1.2.3.505 (19795686)
Defects Fixed in Patch 11.1.2.3.503 (19570230)
Defects Fixed in Patch 11.1.2.3.502 (19033046)
Defects Fixed in Patch 11.1.2.3.501 (18183723)
Why do I get the following patch conflict error message when running OPatch?
Why do I get the OUI-67078 warning message when applying OPatch?
How can I find out which releases and patches of EPM System products are installed in a deployment?
Apply this patch to use Internet Explorer release 11 in Standard Mode. After you apply this patch, you can no longer use Internet Explorer Enterprise Mode. You must apply the 11.1.2.3.700 PSUs for all EPM System products in your deployment. For details, see the "Prerequisites" section.
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.
This is a patch set update (PSU).
This patch set update is a partial installation. It replaces files in the existing installation, and does not require a full installation.
This patch set update is cumulative and does include fixes from previous patches.
[NOTE TO WRITERS: Add a sentence stating whether the patch Requires a full installation or a partial replacement. if its a partial replacement, The boilerplate for this statement is: This patch replaces files in the existing installation and does not require a full installation.]
[note to writers: State whether this is a cumulative or standalone Patch. If its cumulative, list the previous Patch IDs (XXXXXXXX) that are included. To find previous patch IDs, either Ask your team or look for the patch id in uninstall section of previous Readme. If Standalone, state that this patch does not include previous patches.]
You can apply this patch to the following releases:
11.1.2.3.500 (Required previous update)
11.1.2.3.500 PSE 18467894
11.1.2.3.500 PSE 18609854
11.1.2.3.501 PSU 18183723
11.1.2.3.502 PSU 19033046
11.1.2.3.503 PSU 19570230
11.1.2.3.505 PSU 19795686
11.1.2.3.508 PSU 20230795
11.1.2.3.511 PSU 20729638
[NOTE TO WRITERS: list the base Release(s) from which you can apply this patch and Include any prerequisite patches. TO refer to service fixes or service packs using the old nomenclature, use the fully qualified service fix/service pack version number along with the patch id, for example, 11.1.2.0.07 (12345678).]
[NOTE TO WRITERS: THis required MICROSOFT PATCH INFORMATION should be included in the following product readmes (FM, EPMA, HSF, FDM, Planning, Production Reporting, EAS) unless the patch is issued only on unix or linux platforms. Other products can delete this section.]
Microsoft has identified a security issue that could allow a hacker to compromise your Windows-based system. You MUST install the Microsoft VC 2005 SP1 ATL redistributable pack before applying this patch.
The updated VC 2005 redistributable is available here for both x86 (32-bit) and x64 (64-bit):
http://www.microsoft.com/en-us/download/default.aspx
Ensure that this product's 11.1.2.3.500 patch is applied first.
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.
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.
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 Name |
11.1.2.3.700 PSU Patch Number |
|
Oracle Data Relationship Management |
21107706 |
|
Oracle Financial Reporting |
20838970 |
|
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 Performance Management Architect |
20929659 |
|
Oracle Hyperion Planning |
20643564 |
|
Oracle Hyperion Profitability and Cost Management |
20915688 |
|
Oracle Hyperion Reporting and Analysis Framework |
20768325 |
|
Oracle Hyperion Tax Provision |
21219363 |
|
Oracle Hyperion Web Analysis |
20880421 |
[NOTE TO WRITERS: Does this patch REQUIRE any other PATCHES FOR THE SAME PRODUCT Or for any other products? IF SO, LIST THEM HERE. If NOT, DELETE this section.
[NOTE TO WRITERS: Delete the windows and unix sections as appropriate based on what platforms the patch is for.]
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:
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.
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.
There are no known patch conflicts with this patch.
This patch is applicable for all platforms supported by Oracle Hyperion Financial Reporting, Release 11.1.2.3.500.
This patch can be applied to all languages supported in release 11.1.2.3.000 of Oracle Enterprise Performance Management System. For the Oracle Enterprise Performance Management System Supported Platform Matrix, go to: http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
19238023 |
When a report with a row height that's larger than others is exported to an Excel spreadsheet as fully -formatted, the taller row is split across several spreadsheet rows. |
|
19248823 |
For reports that use a Hyperion Financial Manager datasource a new HFMFilterEntityByPOV option allows the Entity dimension in the POV can use the Category, Year and Period User POV for Active Entities. When set to false (default) the current behavior of Org By Period in the Entities is set for each dimension. |
|
20538673 |
If a Financial Report has a border within text in a text box, it is not displayed when the report is run. |
|
20721401 |
When the font size is set too small or too large for the row height, the appearance is incorrect in HTML preview. |
|
20723060 |
When scrolling up on expanded members in a report viewed as HTML, the entire page is moved to the top. |
|
20730832 |
If a report grid has expansions on one row and different row ha supporting details selected, when a member is expanded the grid is gone and the report is blank. |
|
20830569 |
When a book is opened in HTML preview a user is not able to expand the member selection column. |
|
20833933 |
For Internet Explorer 11, duplicate properties when creating a scheduled batch only works for the first batch created in a Workspace session. |
|
20837146 |
Reports named in Cyrillic (Russian) are named '________.xlsx' when exported to an Excel spreadsheet. |
|
20845662 |
Cell content does not wrap and align properly in Internet Explorer for HTML preview. |
|
20855609 |
When a report with cells using shading is exported to an Excel spreadsheet, the shading is lost. |
|
20865538 |
When scrolling up on expanded members in a report viewed as HTML, the entire page is moved to the top. |
|
20881111 |
When exporting details from a Planning report to an Excel spreadsheet, numbers are exported as text. |
|
20888991 |
Incorrect Polish translation for message 7006 which causes an error in Workspace. |
|
20903806 |
Borders and color shading are lost from reports when exported to an Excel spreadsheet. |
|
20982631 |
On Unix or Linux temporary PDF files created when running books are not removed. |
|
21036929 |
When scheduling batches, all dimensions that are available in the user POV are made available in the batch POV including those already selected in a book POV. |
|
21050344 |
If batch bursting is used for scheduled batches e-mails with PDF attachments are not sent. |
|
21072989 |
Aliases are not displayed in the Member Selection prompt dialog. |
|
21083087 |
Reports with multiple objects, grids and/or images, may lose color formatting. |
|
21093730 |
Cell content does not wrap and align properly in Internet Explorer for HTML preview. |
|
21131027 |
Reports with multiple objects, grids and/or images, may lose color formatting. |
|
21143813 |
Reports with multiple objects, grids and/or images, may lose color formatting. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
20489013 |
For some PDF reports a single row member may be output to a separate page. |
|
20331705 |
The MEMBERALIAS function does not work correctly. |
|
20511310 |
The background image in a report imported from 11.1.2.1 does not display correctly for PDF output. |
|
20609971 |
Arabic names are displayed in reverse for HTML output. |
|
20719342 |
Color formatting does not work for PDF output. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
16450694 |
Annotation numbers for objects are not printed in the report body for PDF output. |
|
18991687 |
The graph disappears when using conditional formatting and replacing Error cell values with Nothing. |
|
19015503 |
The Table of Contents for a Book includes reports with Do Not Display selected when output as PDF. |
|
19262066 |
Changes made in Financial Reporting Studio are not always saved when using 'Save As'. |
|
19467713 |
Changes made in Financial Reporting Studio are not always saved when using 'Save As'. |
|
19540600 |
Changes made in Financial Reporting Studio are not always saved when using 'Save As'. |
|
19604949 |
Exporting a report to an Excel spreadsheet or Word document fails with WebSphere. |
|
19689512 |
Reports with format %) lose decimal places when exported to an Excel spreadsheet. |
|
19766750 |
Manage User POV export and import fail if there is any missing data source connection. |
|
19793263 |
In Financial Reporting Studio, Aligning Text in text boxes has a new 'Justify' option that provides both left and right alignment. |
|
19867569 |
In Workspace File Preferences... for Financial Reporting, if Query-Ready Export is set to use Smart View as the Export Mode, users can select to send output to either a New Worksheet on an existing workbook or a New Workbook. |
|
19949955 |
When rows in a report extend across multiple pages, the row height from page one is not maintained across the other pages. |
|
19958660 |
Some reports that use a User Member List and Chart will not display properly in HTML or PDF output. |
|
20026772 |
In Financial Reporting Studio, if a substitution variable is set as the default "Prompt For" member in a dimension's member selection, after the report is saved the default member cannot be changed. |
|
20032681 |
In isolated cases, a script error may occur when importing a report in Smart View. |
|
20107423 |
Some reports using 'Labelled Cell Text' will display row height that is excessively high. |
|
20114633 |
Changes made in Financial Reporting Studio are not always saved when using 'Save As'. |
|
20205781 |
When running a report some members are duplicated in the list of available members presented for selection in the 'Respond to Prompts' dialog if the count exceeds the number of 'Rows Per Page' selected. |
|
20221171 |
The 'processing clock' disappears when running a book of reports which suggests that the execution may have hung. |
|
20229423 |
Changes made in Financial Reporting Studio are not always saved when using 'Save As'. |
|
20231007 |
All datasources are not updated by a change in the POV in the Preview Point of View dialog in Workspace when the Datasource Connection selected is 'ALL', |
|
20244240 |
Unwanted page breaks are being inserted into PDF output for some reports. |
|
20244962 |
If a report with a large grid has a chart the chart may overlap the grid rather than displaying on the next page for PDF output. |
|
20269153 |
If an invalid member is typed in when running a report with prompts an internal error is displayed that is not actionable for a user. |
|
20327426 |
Negative numbers in report header cells that use 'Freeze Grid Headers' do not use the selected color in HTML preview. |
|
20331925 |
When a report exported to Excel has more than 100 pages the spreadsheet fails to open in Excel. The new property, OfficeMaxNumberOfPages (defaults to 100), is added to FRConfig but should be increased only if necessary as it can consume large amounts of memory. |
|
20353684 |
FRConfig property, UseEssbaseJAPI, is removed to prevent accidentally setting it false. |
|
20384252 |
In a Book's Table Of Contents, 3rd party objects added for a report are not indented properly under the report. |
|
20391858 |
Column headers in a Report are not centered correctly in HTML output when using 'Freeze Grid Headers'. |
|
20435730 |
When a report with multiple connections is imported to Smart View the dropdown list for connections is empty. |
|
20478019 |
If a scheduled batch contains a book with bursting applied an e-mail PDF link is included even when it is not selected. |
|
20453904 |
Scrolling is not working correctly for reports using both 'Freeze Grid Headers' and 'Row Headings Before Column X'. If X is any column greater than 'A' the horizontal scroll bar will now be disabled. |
|
20455132 |
Long dimension names should be truncated when neither 'Adjust Row Height to Fit' nor 'Adjust Column Fit to Width' are selected. |
|
20487422 |
Column headers in a report are not displayed correctly in HTML output with 'Freeze Grid Headers'. |
|
20561259 |
For PDF output, reports with rows that exceed the page length may display only a few rows on the next page and then continue on the following page with additional rows. |
|
20610152 |
Adding or modifying a chart in Financial Reporting Studio causes an error. |
|
20622077 |
In the Workspace 'Setup User POV' dialog, if 'Display Member Label as:' is set to Default, an error may result when the report is run. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
18620508 |
A '$' character is not displayed before substitution variables in a grid and validation fails. |
|
18740786 |
The row indentation can be incorrect when exporting to an Excel spreadsheet. |
|
19012799 |
When using freeze headers column headers do not freeze and scroll to the left of the row header columns. |
|
19219153 |
Annotations are not imported to an Excel spreadsheet when using SmartView. |
|
19228871 |
Command Line Scheduling fails if the password contains special characters. |
|
19262066 |
Reports cannot be modified after saving with financial Reporting Studio 'Save As...'. |
|
19359615 |
User is unable to login to Financial Reporting Studio when using a proxy server that requires authentication. |
|
19467713 |
Financial Reporting Studio 'Save As...' does not save reports changes unless it is closed and re-opened. |
|
19540600 |
Financial Reporting Studio 'Save As...' does not save the changes in the report. |
|
19608901 |
Cells with '0' become text rather than numeric when exported to an Excel spreadsheet. |
|
19638636 |
Legend items in charts of type 'line chart' are not appearing in Financial Reporting reports. |
|
19666000 |
Font type should be the same for both PDF and HTML output. |
|
19771947 |
Column width is incorrect in HTML viewer when using Microsoft Internet Explorer 10. |
|
19782312 |
For Query-Ready mode set to Excel grid the Point Of View is not updated. |
|
19831914 |
<Parent Curr Total> in a column header is displayed as blank for HTML and PDF output. |
|
19846644 |
When a report is exported to an excel spreadsheet numbers are converted to text. |
|
19894944 |
Report names should be included as the worksheet tab names when exported to Microsoft Excel. |
|
19905561 |
Page breaks are ignored on hidden rows. |
|
19906240 |
Freeze grid headers does not work when drilling down on members with expansion enabled. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
19508575 |
Financial Reporting reports for Essbase running in Batch Scheduler have redundant sessions after applying PSU 502. |
|
19545621 |
With PSU 502 when run in Batch Scheduler, Financial Reporting reports do not close Essbase sessions. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
18358848 |
Financial Reporting reports displayed in HTML have column headers shifted left. |
|
18402806 |
Sorting members functionality in Select Members does not work. The resolution provided this additional sorting functionality for Essbase Reports that use MDX: 1. This feature persists the sort state for the dimensions in the report in the FR studio, but it does not persist the sort state to the member selector UI. So, if the user closes the report and opens it again, he will see the member selection to include the sort state, but when he opens the member selector and clicks View, then Sort, he will not see the sort state selected in the UI. 2. When the user opens the report in Workspace, he can see the members sorted, but this feature is supported only for Sorting by Hierarchy and Name; it does not work for description. 3. This feature does not support case-sensitive sorting on the execution side. 4. This feature is supported only for MDX version of Essbase. It does not work for normal Essbase, HFM, and Planning. So, the 'Sort' menu item is not available for HFM and Planning. 5. The sorting on the member selector UI in the FR Studio works as before. The ordering of members having same level does not happen inside a hierarchy. It happens across hierarchies (if user selects NAME as ordering criteria). If Ascending Hierarchy is Jan, Feb, Mar, Qtr1, Descending Hierarchy will be Qtr1, Jan, Feb, Mar. Descending Hierarchy will not be Qtr1, Mar, Feb, Jan. |
|
18560079 |
In PDF preview, tabs are not positioning the Financial Reporting report header correctly. |
|
18787413 |
A script error occurs when using SmartView and the member selection icon is clicked for 'Respond to Prompts'. |
|
18799644 |
Exporting a particular Financial Reporting report to Excel can produce an empty spreadsheet. |
|
18801387 |
Scheduled batches that use a CSV file fail if the 'subfolder_name' is blank. |
|
18805757 |
Decimal values are not getting exported to Excel correctly when a suffix is included. |
|
18805879 |
Financial Reporting reports fail if using properties for members that have missing associated attributes. |
|
18819137 |
POVs get mixed if viewing multiple Financial Reporting reports in Workspace. |
|
18858197 |
Indentations are lost when exporting to Excel. |
|
18941346 |
Viewing a Financial Reporting report in PDF may fail if CurrentPOV is used with a member name having a slash and the report is in a book. |
|
18951874 |
For scheduled batches, not all email recipients will receive all PDF Financial Reporting reports. |
|
18966472 |
'Fix Rows' height is ignored if cell text wraps. |
|
19015191 |
A scheduled batch that has the 'Delete if successful' option checked is deleted if the batch fails. |
|
19028941 |
Financial Reporting reports exported to Excel should not have multiple sheets. A new MBean property, ExcelExportOneSheet is introduced. When you set it to true, Export to Excel will generate ONE sheet. The default value is false, which means the logical pages will be on different Excel sheets. Logical pages are the pages defined in the page dimension in a report definition. |
|
19061390 |
Logo disappears when exporting a Financial Reporting report to Excel. |
|
19079704 |
If a Financial Reporting report with 3 or more pages is displayed in Workspace as HTML only the first 2 pages can be selected from the 'Page:' dropdown list. |
|
19134011 |
In Financial Reporting Studio a subscript out of range error results when selecting members using the right-click, tick icon option after applying patch 11.1.2.2.315. |
|
19148928 |
In Workspace, when scrolling down in a report using HTML the background may change from black to white. |
|
19152318 |
If a Financial Reporting report is exported to an Excel spreadsheet the dash character, '-', is replaced by zero, '0'. |
|
19166319 |
'Error executing query: Error: cannot add two edges with the same edge type' received when running a report after updating to 11.1.2.3.501. |
|
19195701 |
If a cell background is black it will not appear when exported to PDF. |
|
19212827 |
Financial Reporting reports exported to Excel should not have multiple sheets. A new MBean property, ExcelExportOneSheet is introduced. When you set it to true, Export to Excel will generate ONE sheet. The default value is false, which means the logical pages will be on different Excel sheets. Logical pages are the pages defined in the page dimension in a report definition. |
|
19227808 |
'Excel found unreadable content' error received for a logo text box after applying patch 11.1.2.3.501. |
|
19247538 |
When a DTS function is in the Page Axis of a report and Expansion is selected on the row, the generations are not indented when the DTS member is selected. |
|
19367983 |
'Error executing query: Error: Failed to get member property [null...' received with a valid report after adding new attributes. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
17896780 |
Large numbers are truncated and bold formatting lost for PDF display. |
|
17910384 |
When a Financial Reporting report is
imported into Smart View, |
|
18070886 |
A user who has been granted access
permissions to a limited |
|
18077093 |
The expansion option in a report is not available for a report in Smartview. |
|
18083693 |
A Planner user that has been granted limited meta-data |
|
18129929 |
Format error when exporting to Excel from HTML or PDF preview for some reports. |
|
18146849 |
Sort function in Financial Reporting Studio columns is failing. |
|
18153560 |
A user that has been assigned permissions=No Access to a report is able to see the report via a Related Content link after clicking on the error message that is displayed. |
|
18204109 |
GROUP role does not have viewer access to folders and objects created by Batch Bursting using CSV. |
|
18264307 |
The page margins are narrower than the previous releases in PDF output. |
|
18289283 |
The scrollbars for the grid are barely visible in Financial Reporting Studio in Windows 7 if 'Visual Styles' is set. |
|
18297629 |
A Financial Reporting report that is exported as 'fully formatted' will lose the number formatting when refreshed in Smart View. |
|
18358848 |
Column headers are not displayed correctly when merged in certain report designs in HTML Preview and footer and header alignment is incorrect. |
|
18402372 |
For PDF output when a grid extends to a next page the indentation is incorrect. |
|
18416151 |
The paper size always defaults back to Letter in the Financial Reporting Book Editor when the book is saved. |
|
18459063 |
Cell Text in a Text box having borders and fonts of different size is not wrapping and the text is printed out of the box in PDF output. |
|
18459428 |
There is extra space in row for cell text in PDF output. |
|
18494092 |
Reports with many rows export to multiple Excel worksheets. |
|
18498540 |
Large numbers are truncated and bold formatting lost for PDF display. Also reported in 17896780. |
|
18509938 |
When Margins are Top:0, Bottom:0, the Header and Footer are not exported to Excel. |
|
18512370 |
Reports with carriage returns and blank lines in Planning string data cells are not output correctly for PDF or HTML. |
|
18514136 |
Manually set row height is not recognized when report is viewed in Workspace. |
|
18514655 |
When batching a budget book to PDF page numbers are not updated for Excel docx files that are included. |
|
18524858 |
Reports exported to Word only output 10 pages. |
|
18528354 |
When a Financial Reporting report is exported to Excel, the results are split across multiple worksheets. |
|
18556267 |
Images in reports are presented very large in PDF preview. |
|
18560756 |
Financial Reporting Studio freezes after opening a member selection or inserting a grid and then using Alt-tab on Win7 64 bit. |
|
18607980 |
When a Financial Reporting report is exported to Excel, the results are split across multiple worksheets. |
|
18610793 |
In a Financial Reporting report, a chart will not be displayed if the report contains an Essbase attribute with an apostrophe character in the alias name. |
|
18652479 |
Reports that use a second sorting criteria have the last two columns reversed. |
|
18677959 |
Grids that have 'Freeze Grid Headers' enabled do not work in Firefox 24 or 25. |
[NOTE TO WRITERS: State whether this patch IS being released on all languages OR list the supported languages. If ENGLISH ONLY, State "This patch supports English only."]
The following issues are the noteworthy known issues of this patch.
|
Defect Number |
Defect Summary |
|
17469492 |
When exporting a Financial Reporting report to Microsoft Excel from Workspace, grids that should be side-by-side are placed one below the other and not legible.
Although presenting the grids side-by-side is not yet resolved, the grids presented one above the other can be made legible by adding the following new property to any others in the properties element as shown <properties> <property name="xlsx-keep-values-in-same-column">true</property> </properties> in <EPM_ORACLE_INSTANCE>\FinancialReporting\lib\FOProcessor\xdo.cfg on the Financial Reporting Server machine |
|
19874180 |
Fonts that are used in designing reports that are available on the Financial Reporting Studio host machine, including the Windows system font, will not render correctly in PDF or HTML unless they also exist on the Financial Reporting server. This is very likely to occur when the Financial Reporting server is not a Windows system. |
|
19951103 |
For EPM System installations where Reporting and Analysis Framework has been scaled-out to two or more machines running Microsoft Windows the SMB2 protocol must be disabled on each cluster member machine. Financial Reports may fail to execute if this operating system change is not made. Only scaled-out deployments of the Reporting and Analysis component deployed on MS Windows are affected. Documented in metalink KB 1542367.1: https://support.oracle.com/epmos/faces/DocContentDisplay?id=1542367.1 |
|
20032681 |
When a Financial Reporting report is imported into Smartview, a script error is encountered on line 872. Clicking 'Yes' in response to 'Do you want to continue running scripts on this page?' will successfully import the report. |
[NOTE TO WRITERS: If the patch is cumulative, check with your product team about whether to include any known issues from the earlier patches.]
The section includes important information about applying this patch for Oracle Hyperion Financial Reporting, Fusion Edition.
To apply this patch:
1. Shut down all services and servlet instances related to the Oracle Hyperion EPM Release 11.1.2.3.500 installation.
2. Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.
3. On the Financial Reporting server machines, download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
NOTE: <PATCH FILE NAME>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.
4. On the Financial Reporting server machines, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.
5. To apply the patch, enter the following command on one line:
Windows:
opatch.bat apply <EPM_ORACLE_HOME>/OPatch/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME>
-jdk <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 apply <EPM_ORACLE_HOME>/OPatch/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.
6. Delete the Financial Reporting precompiled jsp files located at: <ORACLE_HOME>\Middleware\user_projects\domains\EPMSystem\precompiled\hr
7. If missing, add '<property name="xlsx-keep-values-in-same-column">true</property>' without the single quote characters to xdo.cfg which is located at <ORACLE_HOME>\Middleware\user_projects\epmsystem1\FinancialReporting\lib\FOProcessor
8. Restart Oracle Hyperion EPM services and servlets.
9. All users should now clear cached files from their browsers.
10. For WebSphere deployments, you must use EPM System Configurator to redeploy the Web application.
11. Connect to the EPM Workspace machine that was patched starting in Step 3. Download the Financial Reporting Studio installer from the EPM Workspace menu: From the Tools menu, select Install and then select Financial Reporting Studio and then launch the installer. Follow the installation guide to install the Financial Reporting Studio to the location you want.
To roll back a patch:
1. Shut down all services and servlet instances related to the Oracle Hyperion EPM Release 11.1.2.3.500 installation.
2. Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.
3. On the Financial Reporting server machines; From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
4. To roll back the patch, enter the following command on one line:
Windows:
opatch.bat rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jdk <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> -jdk <MIDDLEWARE_HOME> /jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.
5. Delete the Financial Reporting precompiled jsp files located at: <ORACLE_HOME>\Middleware\user_projects\domains\EPMSystem\precompiled\hr
6. Restart Oracleฎ Hyperion EPM services and servlets.
7. All users should now clear cached files from their browsers.
8. On the Financial Reporting client machines; Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.
9. Connect to the EPM Workspace machine that was rolled back in step 3. Download the Financial Reporting Studio installer from the EPM Workspace menu: From the Tools menu, select Install and then select Financial Reporting Studio and then launch the installer.
10. All users should now clear cached files from their browsers.
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.
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.
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> -jdk <MIDDLEWARE_HOME>/jdk160_35
UNIX/Linux:
./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
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
Copyright ฉ 2015, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com