[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.4.000 / 11.1.2.4.700 Patch Set Update (PSU): 11.1.2.4.709
Readme
New Features in 11.1.2.4.700 and PSU 11.1.2.4.701
Defects Fixed in this Patch 11.1.2.4.709 (27290291)
Defects Fixed in Patch 11.1.2.4.708 (26822490)
Defects Fixed in Patch 11.1.2.4.707 (26386614)
Defects Fixed in Patch 11.1.2.4.706 (25852714)
Defects Fixed in Patch 11.1.2.4.705 (25360176)
Defects Fixed in Patch 11.1.2.4.704 (24466619)
Defects Fixed in Patch 11.1.2.4.703 (24311587)
Defects Fixed in Patch 11.1.2.4.702 (23557946)
Defects Fixed in Patch 11.1.2.4.701 (23009997)
Defects Fixed in Patch 11.1.2.4.006 (22462544)
Defects Fixed in Patch 11.1.2.4.005 (22018419)
Defects Fixed in Patch 11.1.2.4.004 (21479554)
Defects Fixed in Patch 11.1.2.4.003 (20785710)
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?
This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.
Caution: You are urged 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 interruption of service and/or loss of data. Before installing or applying this patch:
Verify that your system configuration (product version, patch level, and platform) exactly matches what is specified in the Readme.
For defect number 27580097 - When using Batch Bursting in
the Batch Scheduler, and scheduling output to Snapshot reports and PDF, the
folder specified for Snapshot output, is appended to the specified PDF external
folder. This is the historical behavior, before a recent change was made to
separate the output folders between Snapshots and PDFs.
A new MBean property was added to specify if the Snapshot path is used for PDF
external ouput: "UseSnapshotSaveAsPathForExternalPDFPath =
true/false", by default this is true, which will keep the previous,
original behavior. Setting the property to "false" will utilize a
different folder path for Snapshot and PDF output.
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.4.000
11.1.2.4.003 PSU 20785710
11.1.2.4.004 PSU 21479554
11.1.2.4.005 PSU 22018419
11.1.2.4.006 PSU 22462544
11.1.2.4.700
11.1.2.4.701 PSU 23009997
11.1.2.4.702 PSU 23557946
11.1.2.4.703 PSU 24311587
11.1.2.4.704 PSU 24466619
11.1.2.4.705 PSU 25360176
11.1.2.4.706 PSU 25852714
11.1.2.4.707 PSU 26386614
11.1.2.4.708 PSU 26822490
You cannot apply this patch to the following release:
11.1.2.4.900
Upgraded Oracle Hyperion Financial Reporting Chart Rendering Engine
New Oracle Hyperion Financial Reporting Web Studio
See New_Features_in_Release_11.1.2.4.700
and Known_Issues_in_Financial_Reporting_Release_11.1.2.4.700
[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
[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, Fusion Edition, Release 11.1.2.4.700.
[NOTE TO WRITERS: State whether this patch IS being released on all platforms OR list the supported platforms.
If being released on all platforms, say Applies to all supported platforms.
If being released on one specific platform, list that platform (with no introductory text).
If being released on more than one specific platform, put the platforms in a bulleted list (with no introductory text). For example:
This way of listing supported platforms is required for consistency in the Defects Fixed Finder.]
This patch is applicable for all languages supported by Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.4.000 or 11.1.2.4.700.
[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 |
|
21756093 |
Remove User Name And Password Arguments From The Batch Command Line Scheduler. |
|
25126783 |
FR Web Studio Grid Row Column Is Not Shown While Editing A Report. |
|
25585569 |
Random Blank Pages Are Appearing In FR PDF. |
|
26180465 |
FR Web Studio After Any Change To Format Of Cell The Grid Will Refresh And Jump To Start Of The Grid. |
|
26843414 |
Expanding Grid Causes Grid Content To Appear Empty. |
|
27185044 |
FR Web Studio - Prompting Do You Want To Save The Changes You Made? In Reports When No Changes Are Made. |
|
27290325 |
Using Member Selection On A Report With A Prompt Choice Containing And Not Receives Errors. |
|
27356893 |
FR Web Studio Has A Pop Up Message, OK, When Clicked After Being Idle For 20-30 Minutes. |
|
27447600 |
Add A New Format Option Called Justify For Text Values in FR Web Studio Report. |
|
27502876 |
Select Members In FR Web Studio Is Not Working. |
|
27504974 |
FR Header - Text Object Loses Its Position When Exported To Word. |
|
27543660 |
The User POV Opens To The Second Page Of Member Selection And Only Shows That Page. |
|
27547722 |
Receiving Errors In The User POV When Custom1 Dimension Uses [NONE]. |
|
27580097 |
FR Batch Scheduler Exporting To An External Drive Is Not Posting The PDF To The Specified Path. |
|
27580360 |
Email Notification Only Contains Single PDF File. |
|
27585341 |
FR Web Studio - Clicking On The Grid Properties Buttons Resets Member Labels For Rows And Columns. |
|
27622068 |
Financial Reporting Web Studio Exit Button Is Not Easily Available. |
|
27732182 |
Financial Reporting Cannot Execute A Report, Receives An Essbase Syntax Error. |
|
27848149 |
In Reporting Schedule Batch Save The Selection Save As Snapshot In Repository. |
[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 |
|
27236797 |
Email Via Batch Scheduler Fail. |
|
27230952 |
FR Web Studio - Unable To Close Select Member Screen Page. |
|
26988585 |
Batch Scheduler Entries Deleted After Changing FRConfig Parameters. |
|
26974277 |
HTML Preview Of The FR Report With Multiple Grids Is Not Correct. |
|
26869294 |
FR Web Studio - 'Display Only The Active Entities For' Check Box Is Not Available. |
|
26840777 |
Scroll Bar Is Not Available In Text Box Where Enter A Member Name To Search. |
|
26802334 |
FR Web Studio - Unable To Remove Tick Active Entity Only. |
|
26494840 |
Scroll Bar Not Available In Preview User Point OF View Dialog. |
|
26314320 |
Batch Scheduler Window Does Not Show Correct Details. It Is Either Blank or Shows as "Loading..". |
|
26005069 |
Enter Custom Text For Member Header Is Not Saved When Click On Another Cell. |
|
25984913 |
Issue With Expand All Functionality In Page Dimension. |
|
25538927 |
MAXEMAILATTACHMENTSIZE Parameter In FRConfig Does Not Work. |
|
25192703 |
Cannot Open Sub Folders In Related Content. |
[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 |
|
26739409 |
Dimension With ~ Character Does Not Render POVs In Batch Wizard. |
|
26586077 |
Original defect 25780133 - FR Web Studio Column Headers Are Not Appearing in Report Output. |
|
26503524 |
FR Web Studio Database Connection Information Incorrect Under Summary. |
|
26494840 |
When Preview User Point Of View, No Scroll Bar Avaliable. |
|
26453008 |
The number formatting for the secondary axis, with 'Use Default' unchecked is set to one decimal place and that is not reflected in the chart output. |
|
26452971 |
Combo Chart With Line Stacked Instead Of Row Does Not Behave As Expected. |
|
26452885 |
Suffix Formatting For The Secondary Axis Is Not Being Retained. |
|
26452817 |
Combo Charts Do Not Recognize The Line Type Setting. |
|
26450233 |
Scroll Bar Is Missing In POV Selection Window. |
|
26443505 |
Edit OPatch Readme To Include WLPROXYSSL On For Web Studio Post Patch Step. |
|
26372116 |
When Exporting Financial Report to PDF or PowerPoint Using Multiple Entities, The Graph Representations Are Wrong. |
|
26353398 |
When using with HFM, FR Web Studio Member Selection Drop-Down Is Blank. |
|
26203983 |
FR Web Studio View Shifts To Left/ Top After Entering The Input And Clicking On Tick. |
|
26053064 |
FR Batches Are Completed But Status Is Still Showing As Running. |
|
26044648 |
FR Web Studio Short Name For Entities Option Is Missing. |
|
26033003 |
Cannot Retrieve Successful Schedule Batch After Batch Finished Hours later, Can Retrieve Immediately. |
|
26028668 |
FR Web Studio Default Header Size Is Less Than in FR Studio Desktop Client. |
|
25824399 |
FR POV Member Selection Windows Has A Secondary Scroll Bar. |
|
25704672 |
FR Web Studio Does Not Allow To Set Font Sizes Smaller Than 8. |
|
25697161 |
SmartView Import Fails With Custom Replace Value Function With Mixed Alpha/Numeric. |
[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 |
|
26314700 |
FR Web Studio Does Not Allow To Leave the Custom Heading Field Empty. |
|
26271250 |
FR Web Studio Does Not Allow Negative Indentation. |
|
26180046 |
Wrong Date Is Shown When FR Report Is Exported To Excel From Workspace. |
|
26166793 |
Alphanumberics(Date, Text, Smart List) Are Converted To Numeric Values. |
|
26074293 |
FR Member Selector Memberlist Selection Not Working. |
|
26044648 |
In Financial Reporting Web Studio 'Short Name For Entities' Option Is Missing. |
|
26044495 |
In Financial Reporting Web Studio Not Able To Merge Cell. |
|
26031785 |
Adjust Column Width To Fit' Option Is Not Working For Headers Of Rows OR Columns. |
|
26028994 |
Wrong Date Is Shown When FR Is Exported To Excel From Workspace. |
|
26023577 |
FR Report Descriptive And Date Fields Are Not Displaying Properly. |
|
26002445 |
Snapshot Folder Is Used By PDF External Directory. |
|
26000143 |
File -> Export option is not present for the First Report that is opened after running HTML preview of the Book. |
|
25986649 |
Issue as Preview POV window does not fully use the available space. |
|
25986612 |
Issue with Preview in Financial Reporting Web Studio cannot be enlarged. |
|
25981553 |
Emailing HTML And PDF Links Of Batch Output Does Not Work With Bursting Enabled. |
|
25969884 |
Scheduled Batch Imports Do Not Appear In Batch Scheduler. |
|
25943390 |
Cannot add Financial Reports to Workspace Page. |
|
25907182 |
In Financial Reporting Web Studio Japanese UI, resetting prompt variables cause old values lost. |
|
25879210 |
Two Planning Reports, Which Connect To The Same Planing Application Batch Fail. |
|
25851382 |
Unable To Process Request Error When Export The FR Report To The Excel. |
|
25831000 |
Alternate Hierarchy With Level-1 Member As Level-0 Does not Work. |
|
25796202 |
FR Export To Excel Creates Many Worksheets. |
|
25793614 |
In Financial Reporting Web Studio 'DISPLAY ONLY THE ACTIVE ENTITIES FOR' Check Box Is Missing. |
|
25668166 |
Financial Reporting Text Function No Longer Working LABELEDCELLTEXT. |
|
25608405 |
Merge Columns Not Working In FR Studio Web Version. |
|
25509208 |
Chart Page Break Option. |
|
21611002 |
Original defect 21568215 - HTML: Column Header Not Aligned When Using Merge And Freeze Headers. |
|
21572948 |
Original defect 21419602 - Cannot Conditionally Apply A Bold Format For Any Account That Is Not Level 0. |
[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 |
|
25563540 |
Text Function Is Not Working in FR Book. |
|
25551733 |
Reports Dooes Not Show Aliases When Executed Via Batch Scheduler. |
|
25519873 |
FR Batch Scheduler Allow To Put Incorrect Password. |
|
25249309 |
Legal Paper Setting In FR Book Renders Page On Leeter In Complete PDF Preview. |
|
25115948 |
Image Alignment Is Not Correct In HTML Output Of FR 11.1.2.4.703. |
|
24972918 |
Formatting Issues In Cell Text Function And Planning Comments. |
|
24958003 |
Difference In Footer Text Box Placement When Appying FR 11.1.2.4.703. |
|
24931168 |
Large Spacing Gap In Column Headings, When Text Is Displayed Over Multiple Lines. |
|
24834449 |
Indent Increases For Each Generation By Is Not Being Recognised In FR 11.1.2.4. |
|
24816299 |
Expand All Not Working For Customer Outline, It Results In A Blank Grid. |
|
21897617 |
Not Able To Expand The Member Selection Column When Viewed In HTML View Of Book. |
[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 |
|
20888991 |
Select Financial Reporting Preferences dialog in Polish result in error. |
|
22456928 |
'ScheduedBatchCacheTime' preference is not working properly. |
|
23634461 |
Reports with Member function cause a performance loss. |
|
23641337 |
Permissions not inherited from Snapshot Books and Reports. |
|
24336995 |
Missing first column when using sub heading. |
|
24400587 |
Ability to insert space (blank lines) before and/or after each line in TOC template file. |
|
24442067 |
Book have extra page number compare to previous Financial Reporting version. |
|
24476719 |
Removed Fonts from Client machine still shows in Financial Reporting Studio. |
|
24595348 |
Allow Financial Reporting Web Studio the ability to format rows and/or columns and not lose any prior formatting. |
|
24608482 |
Dimensions name with a colon character result in Books POV missing. |
|
24608683 |
Dimensions name with a colon character cannot be Books Export/Import in Workspace |
|
24615697 |
Member names with a colon character results in Books error. |
|
24719050 |
PDF output does not include all members from the Page Dimension when Page Dimension is set to print additional reports to the Same Page. |
|
24745886 |
Chart component displays incorrectly in HTML Preview. |
|
24749955 |
Graph is not displaying negative numbers as negative(below zero line). |
|
24792831 |
Long row may not work properly for PDF Preview. |
|
24802761 |
After updating to 703, Charts in Financial Reporting Studio show as blank boxes. |
|
24925353 |
Conditional Formatting may not working for the Essbase when using for Essbase shared members. |
|
24942882 |
The FRCONFIG value, ExportFolders, cannot be changed. |
|
25027711 |
Batch Bursting fails when using pipe symbol in member name. |
|
25078304 |
Reports with large text members failed to render in PDF format. |
|
25078500 |
Condition Suppression failed on Essbase hierarchy with level zero shared Member. |
|
25109398 |
When using Planning data source, if string is large integer, Export to Excel may output as Date type. |
|
25167114 |
Bottom border is not displaying in reports. |
|
25177305 |
Original defect 25059253: HTML view of book not loads reports. |
[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 |
|
22479808 |
Incorrect members may be returned in a grid if multiple member functions are used with an Essbase datasource. |
|
22721776 |
Financial Reporting Studio installer should support SHA-2 capability for HTTPS. |
|
22931897 |
Responding to prompts has incorrect behaviour with "Edit Member Name" enabled. |
|
23295333 |
HTML output may not center text objects properly. |
|
23300053 |
Improper report formatting is occurring in PSU 701. |
|
23338553 |
Unexpected page breaks are occurring in PDF output. |
|
23559732 |
When exporting a report to a Microsoft Excel spreadsheet the column headers may be reversed. |
|
23607902 |
An unexpected page break can appear in some reports with PDF output. |
|
23625688 |
If a Book POV has 5 or more dimensions, the last dimension is not shown in the Book POV editor. |
|
23636567 |
The FRCONFIG value, MEMBERSELECTIONROWPERPAGE, cannot be changed for Financial Reporting Studio. |
|
23705467 |
After updating to 702, cell borders are not displayed correctly when exporting to a Microsoft Excel spreadsheet or importing from Smartview. |
|
23755091 |
For 11.1.2.4, links for the Table of Contents in Books don't work. |
|
23858085 |
In Financial Reporting Web Studio, number formatting of prefixes and suffixes is not working properly. |
|
24298364 |
For 11.1.2.4 PDF output does not have the header color. |
|
24352514 |
Member names with an apostrophe cannot be selected to run a report. |
|
24354925 |
Previewing the User POV is slow on Exalytics. |
|
24370952 |
Percent sign number format is not being exported to microsoft Excel spreadsheets for positive values in 11.1.2.4. |
|
24424140 |
Internet Explorer Windings 2 font is not displaying properly in HTML output. |
|
24479959 |
'Repeat with Column Headings' is not working properly for PDF output. |
|
24484542 |
'Show Annotations' does not present the annotation icon. |
|
24490318 |
Line chart is not displaying properly after PSU 702 update. |
|
24599446 |
Top and left cell borders are not displaying in HTML output after updating to PSU 702. |
|
24674122 |
Disclosure Management defect 24658267: login is failing after PSU 702 update. |
[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 |
|
22997613 |
Carriage return and bullets now working correctly in PDF output. |
|
23196534 |
When a substitution variable name is a substring of another it is not displayed correctly in Financial Reporting Studio. |
|
23202741 |
Expand All is not working correctly for certain reports. |
|
23253685 |
Scrolling in the Prompt dialog does not display properly. |
|
23326999 |
User POV is displaying hidden dimensions since PSU 701. |
|
23580472 |
Cannot hide User POV after PSU 701. |
|
23587032 |
Incorrect data shown in some reports with an Essbase datasource using MDX. |
[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 |
|
22600061 |
Japanese characters are removed from the file name when saving a report as a PDF. |
|
22706890 |
The fix in 11.1.2.4.003 for the 'Freeze Grid Header' option causes a performance loss. |
|
22901222 |
When using the Explore window of Financial Reporting Studio the folder changes back to Root when the refresh icon is clicked. |
|
22902992 |
When viewing a report in Workspace and using the Respond to prompt dialog, wildcard searches only work the first time. |
|
22908505 |
Links for page references in the Table of Contents for a Book do not work. |
|
23056426 |
The 'Same As' option is not working in the Member Selection dialog for Financial Reporting Studio. |
[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 |
|
16308847 |
The string 'TABLE OF CONTENTS' is not localized for PDF output. |
|
20575963 |
Original defect 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. |
|
20576032 |
Original defect 20327426: Negative numbers in report header cells that use 'Freeze Grid Headers' do not use the selected color in HTML preview. |
|
21376633 |
If a grid row containing text has a large amount of text, it doesn't paginate properly but always starts the entire grid row on the next page. |
|
21498801 |
For a certain report using no data can be much larger than using data. |
|
21776090 |
In Financial Reporting Studio, the Base Members function fails for Hyperion Financial Management data sources. |
|
21982043 |
The 'wait' icon is not displayed when processing a book for PDF output. |
|
22151001 |
When a Financial Reporting report has 2 grids alignment with 'Fit To Column Width' and 'Fit To Row Height' do not work properly. |
|
22194338 |
When using the Planning Simplified interface, some Financial Reporting reports may not be displayed. |
|
22239558 |
For Microsoft Internet Explorer 11 the grid position may be incorrect for HTML output. |
|
22291040 |
Japanese characters are truncated in Workspace for Microsoft Internet Explorer 11 for some buttons in the POV selection dialog. |
|
22363047 |
In Financial Reporting Studio users can view folders and files that they should not have access to. |
|
22390227 |
The percent cell format may be incorrect for reports exported to a Microsoft Excel spreadsheet. |
|
22475144 |
In Microsoft Internet Explorer 11 with Japanese, the file name is garbled when displayed using File > Export > Excel. |
|
22564287 |
In Financial Reporting Studio, conditional formatting of cells is not working when using the Alias property. |
[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 |
|
21338848 |
HTML Preview in Financial Reporting Studio fails. |
|
21572965 |
Original defect 21419602: Conditional bold formatting not working correctly. |
|
21762863 |
The Property Sheet option on the View menu is disabled if the Report Properties window is closed. |
|
21775391 |
Original defects 20244240 and 20821414: Unwanted page breaks are being inserted into PDF output for some reports. |
|
21811585 |
Reports that return no data for a selected POV fail to return data when the POV is changed to one that has data. |
|
21866819 |
Annotations may not be displayed for some reports. |
|
21909715 |
Original defect 21875253: When running books of reports, data may be displayed only for the first POV selected. |
|
21951130 |
Using labeledCellText fails if the name of the label is 'Description'. |
|
22027261 |
Not all database connections are shown ion the dropdown list box for Books of reports having different database connections. |
[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 |
|
20835457 |
Financial Reporting Studio should not use CTRL+C. |
|
21209304 |
Some exported reports fail for PDF output. |
|
21381386 |
Scrolling is incorrect when parent members are expanded for some browsers. |
|
21384670 |
PDF preview does not display Russian fonts in bold. |
|
21393192 |
Fonts are displaying as 'helvetica' for PDF preview. |
|
21410088 |
When used with Chinese, Financial Reporting Studio fails during member selection when using check boxes for members with member functions. |
|
21439897 |
Some reports do not render properly in Microsoft Internet Explorer 10 and 11. |
|
21443091 |
The logo is too small and the report header is sized incorrectly for some reports in PDF output. |
|
21509814 |
When using the 'Display member label' preference for a database connection, the report will fail if the dimension member is on the POV. |
[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 |
|
20488164 |
Changes made in Financial Reporting Studio are not always saved when using 'Save As'. |
|
20539491 |
Borders on reports are truncated for PDF output and export to Microsoft PowerPoint. |
|
20684048 |
Running reports from Workspace that has a server URL containing non-ascii characters may fail. |
|
20684333 |
<<MEMBERALIAS('GRID1', 'SCENARIO')>> is not functioning properly. |
|
20476193 |
A complete book in PDF output includes certain reports in the Table Of Contents even if 'Do Not Display' is selected. |
|
20583198 |
If Email HTML Link or Email PDF Link is selected for a scheduled batch an invalid PDF link is also sent. |
|
20711291 |
The background image in a report imported from 11.1.2.1 does not display correctly for PDF output. |
|
20723140 |
For HTML Preview if an annotation causes a line to expand the row heading is not adjusted properly. |
|
20752041 |
Using multi-byte characters in the secondary axes title of a chart will not work without surrounding them with single quote characters. |
|
20805705 |
If a Financial Report has a border within text in a text box, it is not displayed when the report is run. |
|
20811786 |
If a Financial Report has a border within text in a text box, it is not displayed when the report is run. |
|
20811854 |
The background image in a report imported from 11.1.2.1 does not display correctly for PDF output. |
|
20872251 |
Query-Ready Export for Smart View results in the 404 error 'cannot connect to the provider...'. |
|
20881815 |
If a Scheduled Batch with multiple books has MHTML output the output for the first book is used for all books. |
|
20913455 |
Reports using a datasource with a hyphen character in the server name cannot change the POV. |
|
20918695 |
If a Report has an Arabic annotation the indentation is wrong and the characters are reversed. |
|
20964083 |
Running reports from Workspace that has a server URL containing a hyphen character may fail. |
|
20971141 |
If a Report is exported to a folder using Internet Explorer 11 Japanese file names are corrupted. |
|
21086004 |
Changes made to reports in Financial Reporting Studio are not saved until the report is closed and re-opened. |
|
21156631 |
Changes made in Financial Reporting Studio are not always saved when using 'Save As'. |
[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 |
|
21566566 |
If an entire row is merged in a Financial Reporting report it will be lost when exported to Microsoft Excel in Fully formatted mode. |
[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.4.000 or 11.1.2.4.700 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. Use the EPM System configurator to redeploy the Financial Reporting Web Application. If RA Framework, OHS, or IIS are installed on a separate host, it must be patched also.
8. In order to run the new Oracle Hyperion Financial Reporting Web Studio, you must enable proxying.
OHS Web Servers
On the machine where Oracle HTTP Server is installed, add the following to mod_wl_ohs.conf, substituting <hostname> and <port> for the actual Oracle WebLogic Server server host name and port where Financial Reporting is deployed. This file is usually located in INSTANCE_HOME//httpConfig/ohs/config/OHS/ohs_component.
Note that the number used for <port> is the same as the ^/hr port number in the same file.
<LocationMatch ^/frdesigner>
SetHandler weblogic-handler
WeblogicCluster <hostname>:<port>
WLIOTimeoutSecs 6000
Idempotent OFF
WLSocketTimeoutSecs 600
</LocationMatch>
IIS Web Servers
Complete the following steps:
a. Copy <EPM_INSTANCE_HOME>\httpConfig\VirtualHosts\hr to <EPM_INSTANCE_HOME>\httpConfig\VirtualHosts\frdesigner.
b. Change WlForwardPath=/hr to WlForwardPath=/frdesigner in <EPM_INSTANCE_HOME>\httpConfig\VirtualHosts\frdesigner\iisproxy.ini.
c. Update <EPM_INSTANCE_HOME>\httpConfig\VirtualHosts\iisproxy.ini with the new alias for /frdesigner by adding /frdesigner/*.
d. For example:
e. WlForwardPath=/calcmgr/*,/eas/*,/easconsole/*,/easdocs/*,/hfmadf/*,/oracle-epm -fm-webservices/*,/HyperionPlanning/,/workspace/*,/raframework/,/biplus_webservices/,/hr/*,/frdesigner/*,/bea_wls_internal/*,/interop/
f. Open IIS Manager, and then select Default Web Site.
g. Create a new virtual directory frdesigner, Alias: frdesigner and set the physical path to <EPM_INSTANCE_HOME>\httpConfig\VirtualHosts\frdesigner.
h. Restart IIS.
9. Restart Oracle Hyperion EPM services.
10. All users should now clear cached files from their browsers.
11. Connect to the EPM Workspace machine that was patched 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.4.000 or 11.1.2.4.700 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. Use the EPM System configurator to redeploy the Financial Reporting Web Application. If RA Framework, OHS, or IIS are installed on a separate host, this patch should be rolled back on it also.
7. Restart Oracleฎ Hyperion EPM services.
8. All users should now clear cached files from their browsers.
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 ฉ 2018, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com