Proactive insights, news and tips from Oracle Hyperion EPM and BI Support. Learn Oracle from Oracle.

Patch Set Update: Oracle Smart View for Office

Tanya Heise
Sr Principal Technical Support Engineer

Hyperion Product Management recently advised the release of a Patch Set Update (PSU) for Oracle Smart View for Office

Patch Set Update: Oracle Smart View for Office

Patch 26553924


This PSU download is available from the  My Oracle Support | Patches & Updates section.


Refer to the Readme files for information pertaining to the above requirements. The Readme file should also be consulted prior proceeding with the PSU implementation. This document contains important information that includes supported paths, implementing and configuration steps, list of new features and defects fixed, along with additional support information.

It is important to ensure that the requirements and support paths to this patch are met as outlined within the Readme file.

The Readme file is available from the Patches & Updates download screen.


New Features in this Release:

  • Change the Solve Order of Members in a Calculation
  • Calculation Trace
  • Audit Trail

Review the readme for the list of defects fixed in this release for the following products:

  • General
  • Essbase
  • Financial Management
  • Financial Reporting
  • Oracle BI EE
  • Oracle Enterprise Performance Reporting Cloud
  • Oracle Planning and Budgeting Cloud, Oracle Enterprise Planning and Budgeting Cloud
  • Planning


More Information:

  • Tips and troubleshooting topics are listed in the Oracle Smart View Installation and Configuration Guide. This guide is available in the Smart View library on the Oracle Help Center:
  • Available Patch Sets and Patch Set Updates for Oracle Hyperion Smart View for Office (Doc ID 2220997.1)
  • Smart View Support Matrix and Compatibility FAQ (Doc ID 1923582.1)


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.