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.1.000 Patch Set Update (PSU): 11.1.2.1.141

Readme

About this Patch. 2

Patch Type. 2

Supported Paths to this Patch. 2

Prerequisites. 3

Required Microsoft Patch. 3

Other Required Patches. 3

Required User Rights. 4

Supported Platforms. 4

Supported Languages. 4

Defects Fixed in this Patch (20929321). 4

Defects Fixed in Patch 11.1.2.1.140 (19795722). 4

Defects Fixed in Patch 11.1.2.1.139 (18697566). 5

Defects Fixed in Patch 11.1.2.1.138 (17750920). 5

Defects Fixed in Patch 11.1.2.1.134 (16345450). 7

Defects Fixed in Patch 11.1.2.1.133 (15993965). 8

Defects Fixed in Patch 11.1.2.1.128 (14625130). 9

Defects Fixed in Patch 11.1.2.1.127 (14406630). 10

Defects Fixed in Patch 11.1.2.1.125 (14138385). 11

Defects Fixed in Patch 11.1.2.1.124 (13983154). 12

Defects Fixed in Patch 11.1.2.1.120 (13785289). 13

Defects Fixed in Patch 11.1.2.1.118 (13558484). 14

Defects Fixed in Patch 11.1.2.1.114 (13370933). 15

Defects Fixed in Patch 11.1.2.1.111 (13024785). 16

Defects Fixed in Patch 11.1.2.1.107 (12870711). 16

Defects Fixed in Patch 11.1.2.1.104 (12599877). 17

Defects Fixed in Patch 11.1.2.1.101 (11732644). 18

Known Issues in this Patch. 18

Applying this Patch. 21

Rolling Back this Patch. 23

Troubleshooting FAQs. 25

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

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

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

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

About this Patch

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.

Patch Type

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.

This patch set update will provide support for Internet Explorer 9.

[NOTE TO WRITERS:  Add a sentence stating whether the patch Requires a full installation or a partial replacement. if it’s 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 it’s 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.] 

Supported Paths to this Patch

You can apply this patch to the following releases:

•   11.1.2.1.000

•   11.1.2.1.101

•   11.1.2.1.104

•   11.1.2.1.107

•   11.1.2.1.111

•   11.1.2.1.114

•   11.1.2.1.118

•   11.1.2.1.120

•   11.1.2.1.124

•   11.1.2.1.125

•   11.1.2.1.125 PSE14494565

•   11.1.2.1.127

•   11.1.2.1.128

•   11.1.2.1.128 PSE15960874

•   11.1.2.1.128 PSE16025384

•   11.1.2.1.133

•   11.1.2.1.133 PSE16515012

•   11.1.2.1.133 PSE16997480

•   11.1.2.1.133 PSE17172008

•   11.1.2.1.133 PSE17464650

•   11.1.2.1.134

•   11.1.2.1.134 PSE17980570

•   11.1.2.1.138

•   11.1.2.1.139

•   11.1.2.1.140 PSU 19795722

 

 [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).]

Prerequisites

Required Microsoft Patch

[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

Other Required Patches

This Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.1.000 patch set exception 11.1.2.1.133 PSE 16515012 requires these other EPM System patches:

•         Shared Services patch set update 14142678

•         EPM Workspace patch set update 14119724

Both the Shared Services and EPM Workspace patches must be applied on any machine(s) where Foundation Services is installed. This Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.1.000 patch set update 11.1.2.1.138 PSU 17750920 must be applied on any machine(s) where Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.1.000 is installed. There is no required order for these patches. Apply all three patches in any order and then redeploy all Web applications.

Required Smart View Patch Set Update      

This patch set exception requires the following:

•         Install Oracle Hyperion Smart View, Fusion Edition Release 11.1.2.2.000.

[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.

Required User Rights

[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:

Windows:

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

UNIX/Linux:

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

Supported Platforms

This patch is applicable for all platforms supported by Oracleฎ Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.1.000.

[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.]

Supported Languages

This patch is applicable for all languages supported by Oracleฎ Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.1.000.

Defects Fixed in this Patch (20929321)

Defect Number

Defect Fixed

• 20181594

The MemberProperty Function throws an error even if all MemberName and MemberAlias functions are removed from the report.

• 20182764

Page breaks in hidden rows of PDF reports are ignored.

• 20218695

After applying PSU 11.1.2.1.139 row height shrinks in PDF preview.

• 20245883

In some reports if a row is expanded after a column is expanded the grid disappears.

• 20590221

If a report with a page dimension is imported to Smart View in Fully-Formatted mode and 'all Pages' and 'Split Pages Across worksheets' is selected, the report is not displayed correctly.

Defects Fixed in Patch 11.1.2.1.140 (19795722)

Defect Number

Defect Fixed

• 19196180

Reports using a member selection with a name that includes a forward slash character, '/', fail for PDF Preview.

• 19642822

Reports with multiple grids and grids across multiple pages don't display properly for PDF output.

• 19977477

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'.

Defects Fixed in Patch 11.1.2.1.139 (18697566)

Defect Number

Defect Fixed

• 13431428

Reports with embedded tab characters in text boxes are not displayed in PDF format.

• 16052894

The Page dimension's format (Font size, effect) is not saved when exporting to Excel.

• 18048560

A Financial Reporting report that is exported as 'fully formatted' will lose the number formatting when refreshed in Smart View.

• 18185622

Column headers are not displayed correctly in HTML preview when merged for certain report designs.

• 18268364

A PDF Book can have blank report pages for certain POV definitions.

• 18338649

Ghostscript image options are ignored when exporting a report image to Word or PowerPoint.

• 18364690

Grids overlap in PDF preview.

• 18384119

The paper size always defaults back to Letter in the Financial Reporting Book Editor when the book is saved.

• 18394260

Financial Reporting reports that include a period character in the report name cannot be launched from a related content link.

• 18551547 

After applying the 11.1.2.1.138 PSU, PDF display of reports is truncated.

• 18593776

After applying the 11.1.2.1.134 PSU, PDF display of reports is truncated.

• 18800295 

Reports with multiple grids are incorrect in PDF preview.

• 18916026 

Some reports display overlapping content when viewed in PDF.

Defects Fixed in Patch 11.1.2.1.138 (17750920)

Defect Number

Defect Fixed

• 16096923

The font size displayed in HTML Preview is changed in PDF Preview.

• 16179050

The second report is not using the user POV set by the first report by the same user.

• 16755821

Batch cleanup parameter does not work correctly.

• 16762194

Auto cleanup of batch jobs is not working correctly.

• 17363462

Date() function does not display Japanese characters in PDF correctly.

• 17515896

An incorrect datasource connection was created when importing a grid.

• 17590365

Some Financial Reporting reports using Financial Management as a datasource fail to display in PDF Preview.

• 17615812

The conditional formatting is not honored in Financial Reporting reports that contain supporting details and conditional formatting.

• 17719765 

The ChartPlottingIgnores MBean option setting in JConsole is not being honored.

• 17780366

Financial Reporting PDF output is different after migrating from 11.1.1.3 to 11.1.2.1.

• 17798884

The 'Hide Always' option does not work properly when inserting an empty column or row in PDF Preview.

• 17939988

When the PrintingMaxThreads MBean is set to 10, some PDF outputs generated via batch bursting are not displaying correctly.

• 17957454

If the sub folder has the same name as the parent folder, exporting the parent folder fails to produce the reports.zip file.

• 17978145

Some Financial Reporting reports with basic or advanced suppression on columns fail to display report in PDF Preview after applying 11.1.2.1.134.

• 17988096

A user assigned with 'No Access' permission can still see the related content report.

• 17995953  

Some Financial Reporting reports fail to display in PDF Preview after applying 11.1.2.1.134.

• 18037339

Batch Scheduler Jobs and repository file are not being removed correctly based on JConsole MBean option settings.

• 18111901

The Budget Book output is creating the incorrect folder path for the index.html and other files.

• 18113146

Planning user can see members in prompt member selection dialog box when running a report that the user does not have permissions to view.

• 18160663

Planning user can see members in User POV member selection dialog box in Financial Reporting Studio that they have not been granted permission to view.

• 18172365

Yellow <SCENARIO VIEW> label text shows in PDF Preview on some of the reports after applying 11.1.2.1.134 PSE 17980570.

• 18181940

If the folder name of the last folder contains the last portion of its parent folder name, importing a report to this folder will import it to a different folder.

Defects Fixed in Patch 11.1.2.1.134 (16345450)

Defect Number

Defect Fixed

• 14617341

When row and column templates are used in Financial

Reporting reports, the row formulas always take precedence over the column formulas.

• 15966512 

In a Financial Reporting Book, if the report name is more than 40 characters long, then the report name will be truncated in the table of contents in HTML or PDF preview.

• 16014874

When using Mozilla Firefox 10.x, reports are not displayed correctly if Freeze Grid Headers is set.

• 16015767 

If some cells contain non-numeric values, user will get number format error during exporting to Microsoft Excel.

• 16223424

A dead lock condition may occur when running Financial Reporting batch jobs with the bursting option enabled.

• 16312460

When scheduling a Financial Reporting Batch with a new user

that has not set up their User POV, a Null Pointer Exception error will occur.

• 16409859

When a space is selected as the thousands separator, values that require the thousands separator are exported incorrectly to Microsoft Excel with a leading quote mark.

• 16456383

In a Financial Reporting Studio, unable to change from 'Use Custom formula' to 'Use the row formula' for certain cells with rows or columns formulas.

• 16530263 

When exporting a Financial Reporting report to Microsoft Excel, negative numbers are treated as text.

• 16535866

When exporting a Financial Reporting report to Microsoft Excel, negative numbers are treated as text.

• 16545605 

Financial Reporting reports that contain multiple grids may truncate the grids when displayed in PDF Preview.

• 16683509  

A Financial Reporting report with grid positioning set to: General: 'page break before' and Vertical Positioning: 'Relative', the grid is not displayed in the designed location in PDF Preview.

• 16827348  

An additional row is added when refreshing a report exported from Workspace in Microsoft Excel.

• 16849473  

Financial Reporting reports containing native numbers formatted with () are exported as text in Microsoft Excel.

• 16903768

Some numbers are exported as text in Microsoft Excel.

• 16908835  

In a Financial Reporting report, setting SuppressRepeat on a row fails if the previous row is a formula row.

• 16915132  

After applying 11.1.2.1.133 PSU, reports with multiple grids are overlapping the grids when displayed in PDF Preview.

• 16935942  

After applying the 11.1.2.1.133 PSU, the Book's Table of Contents is not displayed in Complete Book in PDF.

• 17002013  

A Financial Reporting report containing -ve values in a grid are exported as text in Microsoft Excel.

• 17009621  

When the 'Autosize' option for text objects is selected in the report design, it resets the font size to 8 pt in PDF Preview.

• 17015940  

The Financial Reporting report does not refresh correctly when selecting View, Respond to Prompts and changing the member for the prompt.

• 17023151

Row height settings are not honored in PDF Preview.

• 17050632  

Financial Reporting report cell values containing '%' are exported as text in Microsoft Excel.

• 17157934  

When exporting a Financial Reporting report to Microsoft Excel, text values are converted to numbers if a number is included in the text.

• 17165844   

Financial Reporting reports that contain merged prompts may not refresh correctly in Smart View.

• 17246499

The grid position does not display as designed when viewing a report in PDF Preview.

• 17301233

ADM session leaks when executing certain books.

• 17322743

The Financial Reporting server may become unresponsive when executing reports using the Essbase JAPI driver and retrieving attributes for a large number of members.

• 17382604  

Financial Reporting reports display excessive white space in the report header in PDF Preview.

 

Defects Fixed in Patch 11.1.2.1.133 (15993965)

[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 can’t 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

• 14598960

When a large Financial Reporting book is opened as "Complete Book in PDF", you may encounter OutOfMemory error and no PDF output is displayed.

• 14777919

When a Financial Reporting report is exported to Microsoft Excel, a quote mark is added to the values with decimals resulting in the values being treated as text in Microsoft Excel.

• 14850426

When running a Financial Reporting report and book in "HTML Preview" or "PDF Preview", a blank screen is displayed when using Firefox 10.0.1.

• 15837623

When a Financial Reporting report is exported to Microsoft Excel, a quote mark is added to the values with decimals resulting in the values being treated as text in Microsoft Excel.

• 15839321

In a Financial Reporting report a '1' is being displayed in the top left corner of all grids in a report.

• 15843912

When a Financial Reporting report is exported to Microsoft Excel, a quote mark is added to the values with decimals resulting in the values being treated as text in Microsoft Excel.

• 15873483

The performance is slower in version 11.1.2.1 than version 9.3.3 when opening a folder in Financial Reporting Studio that contains a large number of sub-folders and report objects.

• 15930645

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.

• 15931531

In a Financial Reporting report that contains both drill through links and expansions, the data in the cells that contain drill through links may disappear after expanding a member. If you refresh the report the data in the cells containing drill through links will reappear.

• 15944740

When a large Financial Reporting book is run as a "Complete Book in PDF", the contents of the Table of Contents is not displayed correctly.

• 15953646

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.

• 15959969

Financial Reporting batch fails when an existing job is used for a different FR batch. The database connection in batch job doesn't get updated for new the FR batch.

• 15966299

In Financial Reporting report the title in the text box is truncated for reports in PDF Preview.

• 15979420

A Financial Reporting batch e-mail includes the batch details in the e-mail's message body instead of default message "See Attached Reports".

• 15991751

The Financial Reporting Studio client installer cannot be deployed successfully using Microsoft System Management Server.

 [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."]

Defects Fixed in Patch 11.1.2.1.128 (14625130)

[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 can’t 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

• 13064722

In Financial Reporting Studio, when you select Print Preview of a Financial Reporting report, the chart in a report may overlap the grid after upgrading from 9.3.0.x to 11.1.2.1.00.

• 14107335

Financial Reporting cell text overlaps into adjacent blank cell in PDF Preview.

• 14141048

In a Financial Reporting report, cell text cells overlaps into adjacent blank cell in PDF Preview after upgrading to the 11.1.2.1 release.

• 14193054

If a Financial Reporting Book contains a PDF or Microsoft Word document as the first document in the book, then the Complete Book in PDF will not display the Table of Contents.

• 14320456

A Financial Reporting Book that contains a Financial Reporting reports and external PDF documents, the order of the reports in the 'Complete Book in PDF' are not in the correct order.

• 14468242

A Financial Reporting Book displays blank grids in 'Complete Book in PDF'.

• 14500238

When running a Financial Reporting report in PDF Preview, the reports modified date in the Workspace Explore module is updated.

• 14515310

In Financial Reporting report the text displayed in text boxes are truncated when report is run in PDF Preview.

• 14533021

The Point of View is not being refreshed correctly when switching between two Financial Reporting reports.

• 14584432

When conditional suppression is applied to rows in a Financial Reporting report, will suppress data values in columns that should not be suppressed.

• 14605558

If browser language is set to Japanese, when a Financial Reporting Book does not complete successfully, the error message is not displayed correctly.

• 14605605

If browser language is set to Japanese, when a Financial Reporting Book returns no results, the message 'Book contains no results' is not displayed correctly.

• 14612890

When exporting a Financial Reporting report as a fully formatted report, all negative numbers in the report are formatted as text.

• 14617341

When a row and column template is used in a Financial Reporting report, the row formulas always take precedence over column formulas.

• 14617522

In a Financial Reporting report, the custom headings are not retained in the rows below the row and column template.

• 14680098

When exporting a Financial Reporting report to Microsoft Excel, the pages are not being sorted.

 

Defects Fixed in Patch 11.1.2.1.127 (14406630)

Defect Number

Defect Fixed

• 13724128

The reports modified date in the Workspace Explore module is updated when running a Financial Reporting report in PDF Preview.

• 13847225

When refreshing the data in a Financial Reporting report that has been exported in query ready mode, the following error message is  displayed - 'Invalid Grid. Either rows or columns have zero members. Please check suppression options and try your action again'.

• 14137184

When running a Financial Reporting report in PDF Preview, the reports modified date in the Workspace Explore module is updated.

• 14339986

The page numbers in the Financial Reporting Book are not displayed correctly for a book that is generated from a Financial Reporting Batch.

• 14368162

When exporting a Financial Reporting report containing a custom header in query ready mode, the error 'Not a valid member' is displayed.

• 14370495

In the table of contents area in the book setup pane in the Financial Reporting Book Editor, the member name or alias may not be displayed.

• 14381087

When refreshing the data in a Financial Reporting report that has been exported in query ready mode, the following error message is  displayed - 'Invalid Grid. Either rows or columns have zero members. Please check suppression options and try your action again'.

Defects Fixed in Patch 11.1.2.1.125 (14138385)

Defect Number

Defect Fixed

• 13462918

The report header font is changed after performing an upgrade.

• 13622865

MHTML output fails when a book contains a Microsoft Word document.

• 13815946

An empty set of results occurs when using a relative member function within a range function.

• 13865967

A Financial Reporting report exported to Smart View Microsoft Word does not fit inside the page in print layout.

• 13920795

Respond to prompts displays the POV rather than the prompt screen in Release 11.1.2.1.

• 13921636

The text member's value of a lower grid overlaps the upper grid's value in PDF preview.

• 14032375

A warning message is displayed even when a valid member is selected under the Financial Reporting POV.

• 14037819

Annotations for book member selection are not returned.

• 14047816

A long running bursting batch finishes successfully but disappears from the batch scheduler.

• 14088293

Advanced member selection in the web does not accept typed in members.

• 14097341

Decimal points are shifted while scheduling a Financial Reporting book as PDF.

• 14098666

Reports developed in release 11.1.2.0 using Gregorian fonts and migrated to release 11.1.2.1 are changed to Arial fonts when running the report to PDF.

• 14102947

Financial Reporting Studio web preview does not work without saving the report first.

• 14112349

A grid with multiple connections to the same data source type does not work.

• 14136770

There is a Financial Reporting performance issue with a large volume of cell text data for the Hyperion Financial Management data source.

• 14163790

Cells and rows which contain the cell text function produce extra output in release 11.1.1.4.

• 14187092

You cannot save a Financial Reporting report under a folder that has a dot in its name.

• 14213739

When a Financial Reporting book includes an unreachable report, an error message appears but the text is unintelligible.

• 14223741

Exporting a Financial Reporting report to fully formatted format does not render alphanumeric data.

• 14249861

Related contents for cell properties are sometimes copied to Conditional Format.

• 14304338

Error occurs with Financial Reporting reports when pointing to an alias table with special characters.

 

Defects Fixed in Patch 11.1.2.1.124 (13983154)

Defect Number

Defect Fixed

• 13730627

You cannot print annotation descriptions with more than 37 Chinese characters in PDF.

• 13878532

When designing a report with Column Page Break and a Dimension in Pages, the resulting PDF report displays a black box starting on the second page.

• 13887843

The page name appears as a black bar if the page contents spill over to next page.

• 13892448

You cannot run reports on non-unique outline within Essbase unique name with MDX.

• 13899572

You cannot copy member from CSV file in batch bursting if the file contain more lines.

• 13919460

Cell texts cannot show the adjusted height even if the cell is long.

• 13920184

The Preview list in the bursting option is not able to display more than 191 elements.

• 13920857

In Respond to Prompts and User POV, when selecting Cancel, the Financial Reporting report is closed.

• 13921842

Member names that contain brackets do not display correctly in Financial Reports.

• 13930874

The blank rows are updated with the data from the last data row.

• 13936307

A Financial Reporting report imports with report description instead of the report name.

• 13947957

The User POV in a report with multiple data sources does not reset properly.

• 13960514

With the User Preference set to PDF, then changing the POV by selecting View and then Preview User Point of View a Financial Reporting report changes to HTML.

• 13975143

In PDF Preview, when changing member on POV, two dialogs are displayed.

• 13981329

A HARSnapin error occurs when opening migrated Financial Reporting reports in Financial Reporting Studio.

• 13988000

Date values in Financial Reporting are off by one day.

• 14019590

You are unable to run a book that uses the AND condition.

Defects Fixed in Patch 11.1.2.1.120 (13785289)

Defect Number

Defect Fixed

• 13324843

Selecting All for common dimensions in a single User POV for a report containing grids with different data sources does not work.

• 13493567

Unable to display user defined attributes on the User Point of View in Financial Reporting Preferences for Essbase data source.

• 13623994

The Organize by Name filter shows repeat batch names at end.

• 13630441

Member Selection using functions does not save the selection the first time.

• 13657062

When creating a new version of book or batch using Save As it is owned by the admin user.

• 13686023

A Child member becomes invisible if meta read is set on parent member.

• 13704391

Smart View and function grid do not honor hidden columns.

• 13742685

Exporting a Financial Reporting report using Export in Query-Ready Mode fails.

• 13769456

The release 11.1.2.1- batch scheduler with HTML output fails with larger books.

• 13777221

Text data in a Financial Reporting report is not exported correctly to Microsoft Excel.

• 13777614

Member names containing the ampersand character (&) cannot be used in Financial Reporting reports in related content.

• 13787885

In the Function grid, merged metadata is incorrect when the merge area contains hidden fields.

• 13791383

The Financial Reporting Unknown Member error is cached for the user.

• 13799275

Deleted batches reappear in the Scheduler page in Workspace.

• 13821697

When an YTD member is selected for a report contained in a Financial Reporting book, the YTD data values are not returned when reporting against a Planning data source.

• 13878699

Batch POV changes after viewing or editing batch properties.

• 13899899

Export to Query Ready Mode fails for some reports after performing an upgrade.

• 13902979

In the Preview User Point of View dialog, the substitution variable names and values are not displayed correctly.

• 13909776

When exporting in Query Ready mode, The Essbase error (1020022) Member [ ] is out of place occurs.

Defects Fixed in Patch 11.1.2.1.118 (13558484)

Defect Number

Defect Fixed

• 12885604

The Search function does not work correctly in Financial Reporting Studio.

• 12958411

The User Point of View search on a shared member in large dimension is very slow.

• 12959666

Annotation context information differs between report and annotation manager.

• 13014129

Behavior with the Hide Annotation function is inconsistent.

• 13249166

Admin User and Password should be encrypted or removed in frsetupprintserver.properties.

• 13358254

The selected Alias table is not shown in the User POV Selection dialog.

• 13372910

The HIDE_ALWAYS option does not work correctly.

• 13413462

Setting an alias under Financial Reporting preferences does not affect all values.

• 13418959

Financial Reporting 11.1.2.1 value dimension members do not display correctly in the Book Editor.

• 13452203

An exported Financial Reporting report appends the folder name to the file name.

• 13466895

The web launch of a Financial Reporting report is uses alias names instead of member names.

• 13475507

The default preview mode option for PDF Preview does not work for books.

• 13481145

The default preview mode option for PDF Preview does not work for books.

• 13481849

Member Selection shows members in preview, but fails to show in Print Preview.

• 13501879

A failure occurs when importing Financial Reporting reports and creating new data source connection with Polish locale.

• 13518846

Related content with shaded cell and white font obscures the text.

• 13542643

Annotations are not displayed after a non-admin user deletes one annotation.

• 13562024

The Financial Reporting report does not display object in center horizontal position.

• 13563001

After exporting to Microsoft Excel, some sections are repeating.

• 13621514

Shared Member Alias does not show up in Workspace.

• 13632043

Data cells do not auto-size in PDF format when using Planning Text Data Type.

• 13635873

The correct members are not returned in the report when using the AND and NOT operands together in Advanced Member Selection.

Defects Fixed in Patch 11.1.2.1.114 (13370933)

Defect Number

Defect Fixed

• 13465881

The FR (Financial Reporting) web cluster does not direct HTML output correctly to clustered FR web boxes.

• 13408095

After applying the 11.1.2.1.107 PSU, the following exception occurs when opening a book in the Book Editor: JAVA.LANG.NUMBERFORMATEXCEPTION: NULL.

• 13405104

Header lines are missing in HTML and PDF preview of reports migrated from release 9.2.0.3.

• 13372768

In the batch destination dialog, the Print To option is greyed out.

• 13366073

The batch reports get unique constraint (epm_ra.pk_v8_access_ctrl) violated error.

• 13345628

Importing Financial Reports into Microsoft PowerPoint is very slow in compact environment.

• 13339814

Data source mapping in Financial Reporting also maps text cells.

• 13324087

The POV is not retained for attribute dimension after upgrade.

• 13256892

You cannot import Financial Reporting reports in Workspace with Polish locale.

• 13071491

You cannot pass Smart View connect in some cases.

• 13067851

Unique constraint (hyp_rep.pk_v8_access_ctrl) violated error occurs when scheduling batch.

• 13040925

ManageUserPOV does not import substitution variables in user POV.

• 13025646

The Windows security logon window appears when exporting Financial Reporting to Microsoft .ppt, .doc or .xls files.

• 12971356

A scheduled batch fails with error ora-00001: unique constraint pk_v8_access_ctrl.

• 12943994

A scheduled batch fails with error: pk_v8_access_ctrl. Cannot insert duplicate key.

• 12920316

A scheduled batch gets error: pk_v8_access_ctrl: ora-00001 unique constraint violation.

• 12697210

The Import as a Function grid loses its formatting.

Defects Fixed in Patch 11.1.2.1.111 (13024785)

Defect Number

Defect Fixed

• 13069186

Email addresses with a CSV (comma-separated values) file in bursting scheduler are not displayed in the batch recipients list.

• 12999076

The ability to hide a column header row is disabled if the report design contains two data sources in the rows.

• 12973813

The Grid POV disappears after refreshing a Financial Reporting report in Workspace.

• 12956217

Formula cells returns #ERROR rather than #MISSING. Based on this defect, a new global property named MissingValuesAreZeroInFormulas has been added.

• 12916857

The Disclosure Management mapping tool frame gets out of sync with the menu option occasionally when Preview POV preference is set to 'On'.

Defects Fixed in Patch 11.1.2.1.107 (12870711)

Defect Number

Defect Fixed

• 13071627

If a Book has page size set to Legal/Ledger/A3/A4, the complete book PDF's page numbering and Book TOC's (Table of Contents) Mapping are wrong.

• 13020685

Exporting a report by selecting “Export to Query Ready” fails when an APS URL is used.

• 13013312

The command line scheduler fails when user credentials are included on the command line. The command line scheduler requires that user credentials to be included in the batch.xml file.

• 13009319

A book containing reports using Hyperion Financial Management data source, displays dots when running Complete Book in PDF.

• 12932727

After applying PSU 11.1.2.1.104 (12599877), books retrieve User POV instead of Book POV.

• 12916552

The table of content links navigates to the wrong report in the Complete Book in PDF.

• 12916617

The page numbering in a Complete Book in PDF is incorrect.

• 12880698

While using bursting, when exporting a PDF file containing special characters in the batch bursting Output Label field, the special characters in the name change to %.

• 12829782

Page numbers are repeated in Complete Book in PDF when using Legal paper size.

• 12802465

Complete Book in PDF returns a blank page with dots in 11.1.2.1.

• 12800944

The table of contents does not display and the page numbering is incorrect in a Complete Book in PDF.

• 12780666

After an upgrade from 9.3.1 to 11.1.1.3 to 11.1.2.1, the report headers do not do not display correctly.

• 12780029

The ability to access objects through keyboard in book editor does not work.

• 12776683

Unable to set the default attribute for Preview User POV via the JConsole MBean COM.HYPERION.REPORTING.HRPREFS.PREVIEWUSERPOV.

• 12713420

When setting Row Headings Before after a text column in a report, the column preceding the text column will be empty in Print Preview and Web Preview from Financial Reporting Studio.

• 12702005

In Financial Reporting, some of the footer text that is formatted in black is displayed in red in PDF Preview after upgrading to 11.1.2.1.

Defects Fixed in Patch 11.1.2.1.104 (12599877)

Defect Number

Defect Fixed

• 12707940

Batch scheduling fails if user’s password contains '+' sign special character.

• 12688263

When exporting a query ready Financial Reporting report to Microsoft Excel which contains rows with 2 dimensions in a single row in the report, only one of the dimensions is displayed in the report in Microsoft Excel.

• 12676697

When exporting a query ready Financial Reporting report to Microsoft Excel, the custom header is displayed in the grid and results in an error "not a valid member".

• 12652176

When grid suppression is applied in a Financial Reporting report the header and footer content are being suppressed.

• 12648020

Exporting a Financial Reporting report containing a date value to Microsoft Excel as a Fully Formatted Grids and Text, changes the formatting of the date value.

• 12641816

In a Financial Reporting report with expansions defined, when opening an expanded member the report displays at the top level member position instead of maintaining the position on the expanded member.

• 12628979

Unable to create a new database connection if the database connection name contains an ampersand (&) character.

• 12617540

Error messages in Japanese are not being displayed correctly. Messages are displayed as question marks.

• 12576263

"Error executing query" error message displays when running specific Financial Reporting reports that contain a grid containing a row and column template, a prompt on the page dimension, and a text object in the report header.

• 12565954

Formulas defined in row and column template objects use relative positions.

• 12530876

A performance issue occurs with Financial Reporting reports using Essbase as the data source in 11.1.2.1 as opposed to 9.3.1.x.

• 12359345

The support of multi-byte parameters on Financial Reporting function LabeledCellText() is requested.

• 11831319

When exporting a query ready Financial Reporting report to Microsoft Excel, the dimensions in the page dimension or the User POV are displayed in the Smart View POV, and in the columns in the exported query ready report in Microsoft Excel.

Defects Fixed in Patch 11.1.2.1.101 (11732644)

Defect Number

Defect Fixed

• 11064522

Support for Financial Management enhanced cell text in Financial Reporting is requested.

• 10398261

In Financial Reporting reports, the following functions; Average, AverageA, Max, Min, Variance, VariancePercent, and Product do not evaluate suppressed missing values as zero when reporting against a Financial Management data source.

• 10387913

A Financial Reporting report design that contains merged prompts in both the rows and columns, results in a Smart View refresh error in Microsoft Office (Word, Excel and PowerPoint).

• 10382326

In Financial Reporting reports some functions do not evaluate suppressed missing values as zero when reporting against a Financial Management data source.

Known Issues in this Patch

[NOTE TO WRITERS: This section is required.  If the patch doesn’t have any known issues, INCLUDE THIS SENTENCE.] 

 [NOTE TO WRITERS: Per Legal: This sentence must be included IF THERE ARE KNOWN ISSUES.]

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

•   Patch Conflicts:

This patch contains files that are also included in the following Patch Set Updates for Oracle Hyperion Reporting and Analysis for Web Analysis 11.1.2.1.000:

PSU                             Patch Name

11.1.2.1.106                 12865010

11.1.2.1.109                 12910457

11.1.2.1.112                 13076636

11.1.2.1.117                 13535756

11.1.2.1.121                 13845220

11.1.2.1.126                 14277930

11.1.2.1.131                 14832995

To prevent a conflict situation, if any of these patches are also to be applied to the same machines, these patch set updates must be applied BEFORE the Oracle Hyperion Financial Reporting, Fusion Edition patch set update 11.1.2.1.138 PSU 17750920. If necessary, roll back Oracle Hyperion Financial Reporting, Fusion Edition patch set update 11.1.2.1.138 PSU 17750920 as described below and then re-apply this patch after applying any of the above Oracle Hyperion Reporting and Analysis for Web Analysis 11.1.2.1.000 patch set updates.

•   If you cannot get an office document in a book output in Complete Book in PDF, do the following:

1.  Run dcomcnfg.

2.  Select Microsoft Excel Application -> Right Click Properties->Open Security tab

3.  Under Security, Select Access Permissions-> Customize -> Edit.

4.  Add the user you using for the print server service & give Access.

5.  Under Security, select Launch and Activation Permissions -> Customize -> Edit.

6.  Add the user you use in for the print server service and give Access.

7.  Ensure the System User account has access too.

8.  Select the Identity tab, and then Interactive User.

9.  Do the same for Microsoft PowerPoint Application and Microsoft Word 97-2003 Document.

If you don't see Microsoft Office in the dcomcnfg, you're probably running on a 64-bit machine, which means you need to run: mmc -32 from the Start > Run dialog. Then choose File > Add/Remove Snap-in, and add Component Services. All Microsoft Office applications should appear.

10. On 64 bit OS:

Open Windows Explorer and add a folder called Desktop in C:\Windows\SysWOW64\config\systemprofile\, for example:

C:\Windows\SysWOW64\config\systemprofile\Desktop

On 32 bit OS:

Open Windows Explorer and add a folder called Desktop in C:\Windows\System32\config\systemprofile\, for example:

C:\Windows\System32\config\systemprofile\Desktop

 

Defect Number

Defect Summary

• 12325354

The text function LabeledCellText does not return error message even if the label name is not valid.

• 12373777

In a non-English Financial Reporting Studio, The default parameter of labeledcelltext() is incorrect.

 

Workaround: Delete the incorrect parameter value and replace it with appropriate values.

• 12373854

In Japanese Financial Reporting Studio, the Function default parameter separator is not a comma.

 

Workaround: Change the offending characters to a comma.

• 12376268

Function parameters are not updated after inserting saved row/column templates.

• 13061124

If the page setup has 'Fit Length to Page' selected, then when viewing a  Financial Reporting report in PDF Preview that has a grid that is one page in length and multiple pages of annotations, the annotations are truncated and not all the annotations are displayed.

• 13507398

Export to Microsoft Excel does not result in the desired output.

 

The help documentation mentions the know issue. To access the help, log on to Workspace, select Online Help, and then search for Export to Excel. The following text is displayed:

 

Note: Because of limited object positioning in HTML, exported objects will not appear in the same positions as they do in the HTML Preview of a report, and will need to be repositioned in Microsoft Excel.

• 13718047

Unable to display user defined attributes on the User Point of View in Financial Reporting Preferences for Planning data source.

• 14600458

When exporting a Financial Reporting report from Workspace to Smart View, the User Point Of View for the report is not retained. The User Point Of View defaults to the most recently used User Point Of View in Smart View.

• 14798798

A Financial Reporting report that is opened in Smart View and is saved as either an .xls or .xlsm document does not display the image correctly in the report header. The image is displayed as a red cross.

 

Workaround: After importing report into Smart View, click the refresh button.

 

[NOTE TO WRITERS: If the patch is cumulative, check with your product team about whether to include any known issues from the earlier patches.]

Applying this Patch

The section includes important information about applying this patch for Hyperion Financial Reporting.

[NOTE TO WRITERS:  Make sure that instructions for applying the PATCH indicate specifically which components are being patched and which machines in a distributed installation should be patched. for example, “on the machine hosting the shared services web application, …”]

[NOTE TO WRITERS:  For web applications, make sure you provide instructions for all supported application servers.]

To apply this patch:

On the Financial Reporting server machines:

1.    Shut down all services and servlet instances related to the Oracle Hyperion EPM Release 11.1.2.1.00 installation.

2.    Uninstall the Financial Reporting Print Server by executing the <FinancialReportingStudio_Installation_Location> \products\financialreporting\install\bin\FRRemovePrintServer.cmd.

Note: The default location of <FinancialReportingStudio_Installation_Location> is

C:\Program Files\Oracle\FinancialReportingStudio

or

C:\Program Files (x86)\Oracle\FinancialReportingStudio.

3.    Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.

4.    On the Financial Reporting server machines:

o    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.

o    From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

o    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> -jre <MIDDLEWARE_HOME>\jdk160_21

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

UNIX/Linux:

opatch.sh apply <EPM_ORACLE_HOME>/OPatch/<PATCH DIRECTORY>   -oh <EPM_ORACLE_HOME>

-jre <MIDDLEWARE_HOME>/jdk160_21 -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.    Redeploy the Financial Reporting Web Application using the EPM configuration tool.

6.    Delete the Financial Reporting precompiled jsp files located at: <ORACLE_HOME>\Middleware\user_projects\domains\EPMSystem\precompiled\hr

7.    On Financial Reporting server machine, to fully address bug 13730627, please copy ALBANY fonts (ALBANWTS.ttf, ALBANWTK.ttf, ALBANWTJ.ttf, and ALBANWTT.ttf) to the jre\lib\fonts folder(for example, <MIDDLEWARE_HOME>\jrockit_160_21\jre\lib\fonts).

8.    Restart Oracle Hyperion EPM services and servlets.

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

 

On the Financial Reporting client machines:

1.    Shut down all services and servlet instances related to the Oracle Hyperion EPM Release 11.1.2.1.00 installation.

2.    Uninstall the Financial Reporting Print Server by executing the <FinancialReportingStudio_Installation_Location> \products\financialreporting\install\bin\FRRemovePrintServer.cmd.

Note: The default location of <FinancialReportingStudio_Installation_Location> is

C:\Program Files\Oracle\FinancialReportingStudio

or

C:\Program Files (x86)\Oracle\FinancialReportingStudio.

3.    Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.

4.    On the Financial Reporting client machines:

o    Connect to the EPM Workspace machine that was patched in Step 4. 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.

 

o    After the Financial Reporting Studio installation is completed, you can configure Financial Reporting Print Server.

5.    Open the <FinancialReportingStudio_Installation_Location>\products\financialreporting\install\bin\FRSetupPrintServer.properties file with a text editor, and update the FRWebServer (server name and port number), and the AdminUser and AdminPassword for the Financial Reporting Report Server.

 

#--------------------------------------------------------

# Contains configuration settings for the Print Server

#--------------------------------------------------------

# Specify Financial Reporting Web Application Server

FRWebServer=http(s)://server:port

# Administrator Credentials for the Report Server

AdminUser=

AdminPassword=

6.    After the FRSetupPrintServer.properties file has been updated, execute <FinancialReportingStudio_Installation_Location>\products\financialreporting\install\bin\FRSetupPrintServer.cmd to setup the Financial Reporting Print Server.

Note: The default location of <FinancialReportingStudio_Installation_Location> is:

C:\Program Files\Oracle\FinancialReportingStudio

Or

C:\Program Files (x86)\Oracle\FinancialReportingStudio.

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

 [NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:

11.1.2.2: jdk160_29

11.1.2.1: jdk160_21

11.1.2.0: jdk160_11

The example here is for 11.1.2.2.

 [NOTE TO WRITERS: If your product is a web application, you need to add this step after the step where the patch is applied:

This step is not required for WebLogic.]

 [NOTE TO WRITERS: IF THIS PATCH INCLUDES CHANGES TO A JAVASCRIPT FILE, YOU NEED TO INCLUDE THE STEP ABOVE AS A FINAL STEP. IF IT DOESN’T, DELETE THIS STEP.]

Rolling Back this Patch

To roll back a patch:

1.    Shut down all services and servlet instances related to the Oracle Hyperion EPM Release 11.1.2.1.00 installation.

2.    Uninstall the Financial Reporting Print Server by executing the

<FinancialReportingStudio_Installation_Location> \products\financialreporting\install\bin\FRRemovePrintServer.cmd.

Note: The default location of <FinancialReportingStudio_Installation_Location> is

C:\Program Files\Oracle\FinancialReportingStudio

or

C:\Program Files (x86)\Oracle\FinancialReportingStudio

3.    Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.

 

On the Financial Reporting server machines:

4.    From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

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

Windows:

opatch.bat rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_21

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

UNIX/Linux:

opatch.sh rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21 -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.    Redeploy the Financial Reporting Web Application using the EPM configuration tool.

7.    Delete the Financial Reporting precompiled jsp files located at: <ORACLE_HOME>\Middleware\user_projects\domains\EPMSystem\precompiled\hr

8.    Restart Oracle Hyperion EPM services and servlets.

 

On the Financial Reporting client machines:

1.    Uninstall the Financial Reporting Print Server by executing the <FinancialReportingStudio_Installation_Location>\products\financialreporting\install\bin\FRRemovePrintSever.cmd.

Note: The default location of FinancialReportingStudio_Installation_Location is

C:\Program Files\Oracle\FinancialReportingStudio

Or

C:\Program Files (x86)\Oracle\FinancialReportingStudio.

2.    Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.

3.    Connect to the EPM Workspace machine that was rolled back in Step 4. 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.

4.    After the Financial Reporting Studio installation is completed, you will need to configure Financial Reporting Print Server.

5.    Open <FinancialReportingStudio_Installation_Location>\products\financialreporting\install\bin\FRSetupPrintServer.properties file with a text editor, and update the FRWebServer (server name and port number), and the AdminUser and AdminPassword for the Financial Reporting Report Server.

Note: The default location of FinancialReportingStudio_Installation_Location is

C:\Program Files\Oracle\FinancialReportingStudio.

 

#--------------------------------------------------------

# Contains configuration settings for the Print Server

#--------------------------------------------------------

# Specify Financial Reporting Web Application Server

FRWebServer=http(s)://server:port

# Administrator Credentials for the Report Server

AdminUser=

AdminPassword=

6.    After the FRSetupPrintServer.properties file has been updated, execute <FinancialReportingStudio_Installation_Location>\products\financialreporting\install\bin\FRSetupPrintServer.cmd to set up the Financial Reporting Print Server.

Note: The default location of FinancialReportingStudio_Installation_Location is

C:\Program Files\Oracle\FinancialReportingStudio

or

C:\Program Files (x86)\Oracle\FinancialReportingStudio.

 

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

[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:

11.1.2.2: jdk160_29

11.1.2.1: jdk160_21

11.1.2.0: jdk160_11

The example here is for 11.1.2.2.

[NOTE TO WRITERS: IF THIS PATCH INCLUDES CHANGES TO A JAVASCRIPT FILE, YOU NEED TO INCLUDE THE STEP ABOVE AS A FINAL STEP. IF IT DOESN’T, DELETE THIS STEP.]

Troubleshooting FAQs

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

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

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

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

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

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

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

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

The following warnings have occurred during OPatch execution:

1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion

-----------------------------------------------------------------------------------

OPatch Session completed with warnings.

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

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

[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:

11.1.2.2: jdk160_29

11.1.2.1: jdk160_21

11.1.2.0: jdk160_11

The example here is for 11.1.2.2.

Windows:

opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21 –invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

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

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

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

<MANAGED_SERVER_NAME/tmp/

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

<MANAGED_SERVER_NAME/cache