TAGS

Recent Posts

Archives

Important Patch Set Exceptions (PSEs) for Hyperion Planning 11.1.2.4.005
Posted on March 15, 2017
Author: Andy Tauro, Performance Architects

For folks who are deploying Hyperion Planning (the Oracle EPM on-premise budgeting, forecasting and planning solution) 11.1.2.4.005, or for those of you who are already on that version, the Performance Architects team strongly recommends to apply Patch Set Exception (PSE) 24597360.

One very important consideration: PSEs are usually not compatible with each other. If you already have a PSE applied for 11.1.2.4.005, you may run into conflict and have to choose which one to keep. Patch Set Updates (PSU) do not usually have this problem because they are cumulative starting 11.1.2.4 (except for Shared Services) and include all fixes issued before them.

This PSE fixes two pretty important bugs with data entry web forms.

  1. Account dimension fixes

In most uses of web forms, the Account dimension is in the row. However, in cases where one or more of these members are also present in an alternate hierarchy, the row that the member is in does not show in the row labels, but the actual data row for the member does show up, especially when the setting to “Suppress missing blocks” is enabled. As a result, the data form gets skewed at best, and can get completely unusable unless this PSE is applied.

  1. Columns widths

Without the PSE, column widths do not respect width settings and instead resize to the width of the column labels. This can be very annoying for users, even if it does not make the web form unusable. For instance, if the header of a column was ‘FY17’, the column width would essentially be four characters wide. Not just would that make for a very slim column that would need to be manually resized to read a number larger than four digits, because all the column headers are most likely not the same, the form will look very ugly.

Please note that this PSE does not completely fix this problem.  On first opening the web forms, the column widths will be sized as per design settings. If any columns are set to be able to expand (such as ‘YearTotal’), the additional columns are squished as well to the size of, for example, ‘Qtr1.’ However, refreshing the web form at that point fixes the additional columns. There is a bug pending with Oracle Development for this (24838130).

If you are seeing any of these issues in your environment, hopefully this note helps you. If you feel that you will require expert assistance in applying this PSE to your environment, or with something else in on-premise Hyperion Planning or Oracle Planning and Budgeting Cloud Service (PBCS), please feel free to drop a note and we will be in touch.

 

Share
© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply

Your email address will not be published. Required fields are marked *