Oracle Hyperion Planning

 

Release 11.1.2.2.000 Patch Set Update (PSU): 11.1.2.2.300

Readme

About this Patch. 2

New Features in this Release. 2

Planning. 2

Project Financial Planning. 3

Public Sector Planning and Budgeting. 5

Patch Type. 6

Supported Paths to this Patch. 6

Prerequisites. 6

Microsoft Patch. 6

EPM System, OPatch, and Oracle Application Development Framework (ADF) Patches. 6

Required User Rights. 7

Supported Platforms. 7

Supported Languages. 7

Defects Fixed in this Patch. 8

Project Financial Planning. 8

Planning. 11

Public Sector Planning and Budgeting. 14

Known Issues in this Patch. 15

Integration with PeopleSoft 15

Public Sector Planning and Budgeting. 15

Planning and Project Financial Planning. 15

Documentation Updates. 17

Oracle Hyperion Public Sector Planning and Budgeting User's Guide. 17

Oracle Hyperion Planning Administrator's Guide. 18

Oracle Hyperion User's Guide. 20

Miscellaneous. 20

Applying this Patch. 20

Post Installation Requirements. 21

Upgrading Existing Public Sector Planning and Budgeting Applications. 23

Rolling Back this Patch. 28

Troubleshooting FAQs. 29

Why do I get errors using Opatch to install a patch to an ODI 11g 64-bit configuration: 29

Why do I get a 'ELFCLASS64 (Possible cause: architecture word width mismatch)' error?. 29

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

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

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

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

About this Patch

This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.

Caution: Carefully read and understand the patch installation 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 this Readme.

New Features in this Release

This section outlines the new features provided in this patch.

Planning

Outline Load Utility Enhancements

Administrators can perform these tasks:

·         Import metadata and data from a relational data source

·         Export data export to a flat CSV file

·         Optimize command lines by storing command line arguments in a command properties file. For example, if you use a command properties file to run the same commands on multiple applications, you need only change a parameter in the command line for each import. This allows you to bundle switches for a common application. It also makes command lines shorter and easier to manage, and enhances readability and ease of use.

 

For details, see the Oracle Hyperion Planning Administrator's Guide.

Approvals Dashboard

These approval enhancements have been made:

·         The Manage Approvals page has an approvals dashboard that includes a graphical representation of approvals information. This allows users to better visualize approvals status.

·         Using a view selection option, you can switch between four different views (Process Status view, Level Status view, Group Status view, and Tree view).

·         Clicking a section of the chart displays detailed information about that chart section in the grid displayed below the chart.

 

Rolling Forecast

These rolling forecast enhancements have been made:

·         You can reuse existing substitution variables for the start year and the start period.

·         When rolling forecast periods are shifted, the values for the year and period dimensions are automatically repopulated to show the resulting year and period values after the shift.

·         Existing values are now reused when you right-click a form to start a rolling forecast.

 

Form Design

Form designers can now:

·         Easily edit forms from within the end-user view of a form.

·         Show usage for simple forms that are used in composite forms.

·         Go from a composite form to a simple form within the layout manager.

·         Easily edit a simple form from within a composite form.

 

Home Page Option

An application property can be set to specify the type of home page that all users see when they first log on to Planning: Forms, Task Lists, or Approvals.


Access Permissions

You can now edit the Currency dimension from within the dimension editor.

 

Runtime Prompts

In Calculation Manager, business rule designers can now set the Use as Override Value property at the rule or ruleset level at design-time. In Planning, the display and values of runtime prompts are affected by such aspects as:

·         If the Use as Override Value property is set at the rule or the ruleset level at design-time

·         If there are valid members on the form's Page/POV and whether the Use Members on Form and Hide Prompt options on the Business Rule Properties tab are selected.

·         If the Runtime Prompt option is set during form design or set when designing the runtime prompt (see the Oracle Hyperion Calculation Manager Designer's Guide)

·         If the Use Last Value property is set when designing the business rule

 

Project Financial Planning

This section describes the features that are provided in this patch. Note: These new features are available only for Project Financial Planning applications created after applying this patch. Applications created before applying this patch will not support the features introduced in this patch.

Language Support

This patch supports the same languages as those in Release 11.1.2.2. However, new text strings that were added for this release have not been translated.

Usability Improvements (14046145)

Project Financial Planning has implemented these usability improvements:

·         Simplified task lists¾Task lists for Contract, Capital, and Indirect projects are combined.

·         Reduced number of tasks¾There is only one task each for expense planning, revenue planning, project performance, and funding.

·         Reduced number of forms¾There is a single composite form for each project type. The bottom form displays details based on the project type.

·         Fewer menu options¾Shortcut menus on forms contain fewer menu options.

·         Improved spreading logic when calculating direct expenses¾In the Enter Direct Project Expenses form, you can choose from the following grid spread methods:

o    Fill¾Copies the value entered to each project year. For example, if a Direct Cost Input value of 1,000,000 is entered for a project with 2 years duration. The value of Year 1 will be 1,000,000 and the value for "Year 2" will be 1,000,000. This value is then evenly split into the months. The value of 1,000,000 for Year 1 will be divided by 12 and filled into the months.

o    SpreadEvenly¾Divides the value entered evenly over the duration of the project. For example, if a Direct Cost Input value of 1,000,000 is entered for a 3-year project. The Year 1 value is 333,333.33, the Year 2 value is 333,333.33, and the Year 3 value is 333,333.33.

o    Input¾You enter values directly at the Year level for Year 1, Year 2, and so on. The values for each project Year are spread evenly, or divided, over the months within that year. For example, enter 40,000 for Year 1, 50,000 for Year 2, and 60,000 for Year 3. 40,000 is divided evenly over the Year 1 months. 50,000 is divided evenly over the Year 2 months. And 60,000 is divided evenly over the Year 3 months.

o    Proportionate¾You enter a Direct Cost Input value, for example, 1,000,000, and then enter proportional values, or ratios, across project years, for example, 1:2:2. Project Financial Planning assigns the proportional values for each project year and then spreads the values evenly over the months within each year.

o    You enter the assumptions in the top form and calculated values are displayed in the bottom form. You need not enter numbers manually for each month.

·         Introduced master details forms¾Master details forms are composite forms that show detailed information in the top form and summary information in the bottom form. Master details forms were implemented for the following tasks:

o    Reviewing Existing Employees¾Existing employee details are displayed in the top form; Employee Expenses Summary and Employee Status information is displayed in the bottom form.

o    Adding New Hires¾New hire request details are displayed in the top form; the Employee Expense Summary is displayed in the bottom form.

o    Reviewing Total Employee Compensation¾Total employee compensation details are displayed in the top form; Hourly Costs are displayed in the bottom form.

o    Managing Existing Assets¾Major assets details are displayed in the top form; Asset Expenses are displayed in the bottom form.

o    Adding and Reconciling New Assets¾New asset request details are displayed in the top form; Asset Expense summary is displayed in the bottom form.

Performance Management Architect Support for Project Financial Planning Applications (14046223)

You can use Performance Management Architect to create and work with Project Financial Planning applications. To create a Performance Management Architect Project Financial Planning application, follow the instructions in the Performance Management Architect Administrator’s Guide, but use these settings:

·         For Application Information Type, select Planning.

·         For Application Type, select Project Financial Planning.

For Industry Sample, select one of the following:

·         If you are creating a basic application, select None. You will then be prompted to define the application calendar, set currency options, and set the customizable plan types, if required. See "Setting Up The Calendar" in the Oracle Hyperion Planning Administrator's Guide.

·         If you are creating an information technology (IT) industry-specific application, select Information Technology. You will not be prompted to define the application calendar, currency, and plan types. They will be set automatically with predefined settings.

When selecting dimensions, note the following:

·         The Scenario, Year, and Period dimensions must be local. They cannot be shared.

·         If any of the remaining dimensions are shared, ensure that the UDA, Currency, and Alias dimensions are also shared.

·         When deploying, for Shared Services Project, select Default Application Group (project for which you defined security and provisioning)

Note the following:

·         Performance Management Architect only supports calendar and fiscal period definitions.

·         During Performance Management Architect application creation, you can create new Project Financial Planning dimensions in addition to the required dimensions. However, Project Financial Planning forms, rules, and so on will need to be modified in order for them to work.

·         Do not rename dimensions during application creation (for example, Job or Employee). If dimensions are renamed, ensure any impacted rules, forms, and reports are updated as well. This is also true when creating Planning applications.

Form for All Overhead-based Accounts of Projects (14046136)

A shortcut menu option has been provided in the Review Project Expenses form for reviewing the details of Indirect and General and Administrative expenses. The form enables you to review the overhead.

Public Sector Planning and Budgeting

This patch provides these new features:

·         Reverse transfers that enable you to undo employee transfers made in error, or transfers that do not result in the desired compensation amount.

·         These decision package and budget request enhancements:

o    The ability to load meta data and data from supported GL and HRM source systems into decision packages and budget requests using the Outline Load Utility.

o    The ability to delete notes and attachments.

o    A predefined rollup for the provided compensation expenses decision package type. This means that planners creating decision packages using the compensation expenses decision package type need not specify a rollup for expense aggregation and display.

o    An improved user interface for justification entry that ensures planners don't overlook any questions, or information, that they must provide when defining decision packages. The number of justification questions that planners must address are therefore listed.

o    If an administrator defines them and enables the corresponding application preference, the ability to display descriptive aliases for entity members in planning units. This enables planners defining decision packages and budget requests to more easily recognize and select entity-specific planning units such as departments or bureaus when performing tasks such as creating, sharing, and submitting decision packages.

o    Decision package and budget request report templates that you can customize in Microsoft Word after installing Oracle Business Intelligence Publisher. This enables you to more closely define the layout and the formatting of PDF reports to analyze decision package and budget request data by making customizations such as adding logos, specifying the formats used, the number of columns per report, and applying shading.

o    Ability to define start and end dates for the Compensation_Budget_Start_Year and Compensation_Budget_End_Year substitution variables to calculate the compensation for a smaller number of years than those spanned by the application, and a budget administration task that accordingly updates employee and position FTE and status. For example, if an administrator defines an application with a time span of six years (FY10 - FY16), you can use the substitution variables to calculate compensation for FY12 - FY15.

·         Ability to calculate benefits and additional earnings as a percentage of salary on a monthly basis.

For information about these features, see the Oracle Hyperion Public Sector Planning and Budgeting User's Guide or online help.

Patch Type

This is a patch set update (PSU). This patch replaces files in the existing installation and does not require a full installation. This is a standalone patch; it does not include previous patches.

Supported Paths to this Patch

You can apply this patch to release 11.1.2.2.000 of Planning.

Prerequisites

Microsoft Patch

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

EPM System, OPatch, and Oracle Application Development Framework (ADF) Patches

EPM System Patches

Before applying this patch, install these patches as described in the readme for each patch:

·         Calculation Manager patch 13925741. Before applying this Planning patch, apply Calculation Manager patch first on every computer on which both Calculation Manager and Planning are installed.

·         Performance Management Architect patch 14031912

·         Smart View patch 14362638

·         Shared Services patch 14020629

·         EPM Workspace patch 13936087 

·         Financial Reporting patch 13997553

·         Reporting and Analysis patch 14200932

Note:

·         Install the Calculation Manager patch first.

·         Apply the Shared Services patch on all servers, and the EPM Workspace patch on any machine where Foundation Services is installed.

Access the patches from: http://support.oracle.com/.

ADF Patches

Install these patches in this order:

·         13952743 (select 11.1.1.6.2)

·         14339256

 

After applying the patches, perform the task for your application server:

·         Weblogic: Delete the contents of the /tmp folder, start run startWeblogic.cmd from <drive>:\Oracle\Middleware\user_projects\domains\EPMSystem\bin\, restart the AdminServer, and then redeploy. You must remove files from the AdminServer (\Oracle\Middleware\user_projects\domains\EPMSystem\servers\AdminServer\tmp), and then restart the AdminServer.

·         WebSphere: Redeploy all applications manually from the WebSphere Integrated Console as described in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

OPatch

Download the latest version of Opatch from Patch 6880880. If you encounter errors, check to see if they are described in the "Troubleshooting" section.

Required User Rights

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:

Microsoft 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 can be applied to all platforms supported in release 11.1.2.2.000 of Planning.

Supported Languages

With the exception of the translated Project Financial Planning 11.1.2.2 help, this patch is English-only.

Defects Fixed in this Patch

Project Financial Planning

Defect Number

Defect Fixed

·   13243516

Overheads should be calculated based on onsite or offsite hours. To achieve this, additional indirect cost pool and allocation basis options were added to the Enter Indirect Cost Assumptions form when entering overhead assumptions:

Indirect Cost Pool options added:

·   Onsite Labor Overhead

·   Offsite Labor Overhead

Allocation Basis options added:

·   Total Onsite Labor Costs

·   Total Offsite Labor Costs

·   Total Onsite Labor Hours

·   Total Offsite Labor Hours

Note: If the assumptions for onsite and offsite overheads are defined and the project was allocated onsite/offsite labor overhead, the “Labor Overhead” will not be allocated to the project. This avoids a duplication when calculating labor overhead.

·   13368120

For Contract projects, there should be a way to specify revenue recognition based on the percent completion.

To accomplish this, two new revenue recognition types have been added:

·   % Duration

·   % Planned Expenses

And a form has been added to define revenue recognition milestones.

The revenue will be recognized upon reaching each milestone. For example, if the revenue recognition for a project with a 24 month duration is defined as % Duration and the milestones are defined as Milestone1 - 20%, Milestone2 - 50%, and so on, the revenue will be recognized upon reaching each milestone (5th month, 12th month, and so on). Similarly, if the revenue recognition for a project with total planned expenses of $1,000,000 is defined as % Planned Expenses and the milestones are defined as Milestone1 - 20%, Milestone2 - 50%, and so on, the revenue will be recognized upon reaching each milestone (that is, in the month when the project expenses are $200,000, $500,000, and so on).

The Revenue Recognition Indicator in the Review Total Revenue form shows when the revenue will be recognized.

·   13387426

For Cost Plus projects, revenue should be calculated only as a markup on billable expenses. The following accounts have been added to enable categorization for billable and non-billable expenses. The accounts are:

·   Billable Labor Expense

·   Non-Billable Labor Expense

·   Billable Equipment Expense

·   Non-Billable Equipment Expense

·   Billable Material Expense

·   Non-Billable Material Expense

When calculating Cost Plus revenue, the calculation will include only billable expenses. Non-billable expenses will be excluded from the calculation.

For example, Billable Labor Expense×(1+Margin %) or Total Expense×(1+Margin %) (for the project duration).

·   13389954, 13518598

For Time and Materials projects, the owning entity should be able to bill customers for the labor expenses incurred by the service provider entity.

·   13407077

Users should be able to change the leased asset type (operating lease or capitalized lease) after a leased asset is added. Project Financial Planning will continue to automatically detect the lease type when it is first added based on parameters entered by the user. But then the user can change the lease type, if needed.

Note: If the user changes the parameters later, they will need to remember to change the lease type, if applicable.

·   13427235

For Contract projects, there should be different project billing rates for onsite and offsite labor hours.

·   13469563

The form header names are missing from several forms.

Header names have been added to the following forms:

·   Add And Reconcile New Assets

·   Add and Reconcile New Leased Assets

·   Review Existing Assets

·   Add New Hires

·   13490585

For Time and Materials projects, creating a project with the cash flow incidence set to "Next Month" and with the revenue recognition set to "When Billed" should be allowed.

·   13518586

When performing capital analysis, adding leased assets at the project level in the Assign Equipment to Projects form should be supported.

To request a new leased asset at the project level, navigate to the Capital Analysis task list. Launch the Raise New Equipment Request task to request a leased asset.

·   13518672

Since labor expenses are calculated based on standard rates, a rule needs to be created to recalculate all the labor expenses whenever the standard rates are changed.

If an administrator changes the standard hourly labor rates for any job while setting workforce assumptions, then it impacts the labor expenses for every project which uses the same job. There is a new shortcut menu option on the Enter Standard Hourly Labor Rates form which enables admins to perform a batch calculation that calculates the labor expenses of all projects which use the same Job dimension member.

·   13626821

Project Financial Planning should support more revenue recognition options for Time and Materials projects. Also, the full array of revenue recognition types should be supported for “Other” project types.

Billing rules have been modified to add the various revenue recognition types for Time and Materials and for Other projects. The options are similar to those supported for Cost Plus and Unit Price revenue calculations.

·   13645676

Project Financial Planning needs to add a Justification field to the Change Assignment window.

·   13582084

In Project Financial Planning, you cannot charge the costs from internal Contract projects to Capital or Indirect projects. Intercompany functionality is supported for Cost Plus Contract
projects where the Revenue Cash Flow Incidence is set to Same Month. For intercompany revenue calculations where the organization is a service provider, the Cost Plus margin must be explicitly marked as 0% for cost-based settlements and greater than 0% for cost plus-based settlements.

·   13706036

While copying the billable line items to the revenue form, there should be two options: Mark the billing level as “Unspecified” or use a default value based on some global assumptions. The default billing level for each job should be set as the global assumption.

At the global assumptions level there is a form called Set Base Billing Rate which defines the default billing level for each job. If you select the default billing level in the Add Labor form, then that billing level will be copied to the revenue form which was set at the global assumptions form (provided there is no billing level defined in the revenue form).

·   13706047

For Time and Materials projects, Project Financial Planning should provide a shortcut menu to change the billing level on the revenue form.

To change the billing level on the revenue form, right-click and select Change Billing Level. Enter or select the requested values for the job, labor requisition, spread start and end dates, and the billing level. If no dates are entered, the modified billing level will be set for the duration of the assignment.

·   13706059

When adding labor and specifying the billing level, Project Financial Planning should provide Billable and Non-Billable options.

Instead of providing Billable and Non-Billable options, a Default option will be provided. If the Default option is selected, the billing level that was defined at the global level will be copied to the revenue form. If an option other than Default is selected, then Project Financial Planning will not overwrite anything from the labor form to the revenue form.

·   13706071

Project Financial Planning will not copy the line item to the revenue form if the billing level is set to Non-Billable”, Otherwise the line item will be copied to the revenue form.

·   13725617

Project Financial Planning now supports intercompany partnerships for Contract projects (all types), Capital projects, and Indirect projects. All intercompany transactions are now billable.

When an intercompany partner is added, the administrator can change the start and end dates for the partner project. If no dates are specified, the partner project will use the owning project’s start and end dates.

For intercompany projects, the project classification and project type is always “Internal Contract” and “Cost Plus” respectively (regardless of the classification and type of the owning entity).

When adding resources for intercompany projects:

·         For labor resources, select Add Labor Assignment, and then select To Contract Projects. Hours for service providers are entered as Offsite Labor Hours.

·         For equipment resources, select Add Equipment Requisition, and then select To Contract Projects.

·         For material resources, select Add Material & Other Requirements, and then select To Contract Projects.

The revenue calculation for service providers is calculated as Cost Plus revenue.

When defining revenue assumptions for Time and Materials intercompany projects, the owning entity can define billing assumptions for resources provided by the service provider.

For Capital projects, administrators can specify whether the intercompany expense is capitalizable for the owner.

When reviewing project expenses and the impact on cash flow, there is a new account called Capitalized Intercompany Expense. This indicates whether the intercompany expenses are capitalizable for the owning entity based on the project setting selected by the administrator when the intercompany partner was added.

·   13930104

For a multiple asset Capital project, data should roll up to the parent Capital project.

To view the values for a parent project, you must first calculate the financial statements.

·   13930239

The template for importing data for leased assets and the template for importing metadata for the Job dimension were missing. These templates have been added.

PFPImportUtility, which is used to load the template data into the application, was also updated.

For the PFPImportUtility.bat or PFPImportUtility.sh files to work correctly, there are additional steps you must follow after applying oPatch. See the subsection in “Applying this Patch.”

·   14000784

You should be able to create a Project Financial Planning application if you load a report with a default currency other than USD.

·   14354086

The PFPImportUtility.sh file, which is used to import template data into the application, was not working on a Linux environment. This utility has been fixed.

For the PFPImportUtility.bat or PFPImportUtility.sh files to work correctly, there are additional steps you must follow after applying oPatch. See the Project Financial Planning subsection in “Applying this Patch.”

·   13869509

In the sample Project Financial Planning application, if you submit a plan for approval while logged in as an asset manager, an error occurs. This error does not occur in a basic Project Financial Planning application. Workaround: This error occurs because the scenario associated with the Submit Plan for Approval task is blank. Edit the Submit Plan for Approval task and select a scenario under Task Type Properties.

·   13848558

Non-owning (service provider) entities should not be allowed to reconcile a project, however, Project Financial Planning allows them to do so. The workaround is to remove the Reconcile Project rule launch access for non-owner users so that they cannot run the rule.

·   13732128

When viewing the 4.10 Review Construction in Progress (CIP) Assets form in Project Financial Planning, you must make at least one dimension visible on the row header or none of the data will display on the form.

·   13559869

When you open the Project Financial Planning help system from within
Planning, errors may display in some cases when you click index markers or search for terms. To work around this, you can access the same content in the Project Financial Planning User’s Help and Oracle Project Financial Planning User's Guide on Oracle Technical Network at: http://docs.oracle.com/cd/E17236_01/nav/portal_5.htm.

·   14275038

You can display the Project Financial Planning help in the supported languages if you perform the additional post-installation tasks.

 

Planning

Defect Number

Defect Fixed

·   14545663

Planning 11.1.2.2 does not prompt you to click Go after you select another member from a drop-down list on a form.

·   13830589

The Drill Through command on a form's Edit menu does not work. Select the drill-through icon that is displayed above and to the right of the cell instead.

·   13830429

The Apply to all selected cells option does not work correctly when attaching
documents to a range of cells in a form. You will only see the attachment in the first cell
selected.

·   13879269

Ad hoc grids are not launched in a separate Analyze tab if they are created from
forms that were opened by selecting the Launch Tasklist Wizard icon.

·   13857734

For accounts where Time Balance is set to Fill, if a child value changes, the default aggregation logic is not applying up to its parent until the child value is changed again.

·   13868374

An ad hoc grid cannot be deleted or moved if using a different Web browser
than the browser in which it was created or invoked.

·   14096170

After migrating using Lifecycle Management, the assignment of business rules, attached to a form, to the correct plan type is lost and must be manually resolved. For example, if business rules are assigned to a form associated with plan type 2, after migration the business rules are drawn from plan type 1.

·   13615823

When selecting a non-English Planning application, an error occurs if you access Planning Preferences using the File menu. The workaround is to access Planning Preferences from the left pane instead when working with a localized Planning application.

·   13062922

Planning does not provide a native utility with which to export data and decision packages and budget requests to flat files. You can now use the outline load utility to perform exports.

·   14284183,
14461495

When using the Adjust menu to add or subtract from cell values on a form, changes are not applied to the destination cell. Instead, they are applied to other cells on the form.

·   13942673

When creating a menu, certain selections cannot be saved in the required parameters field.  

·   13852525

You cannot modify cells in an ad hoc grid until the grid is refreshed by selecting Refresh.

·   14457324,
14020004,
1446835 3

Not all cell values that you select to be deleted or copied are deleted or copied. For example, the last two values in a cell may remain after you select the cell's values and press DELETE.

·   14409732,
14020004

Copy, paste, and clear may not work as expected on forms containing hidden columns. Also, you may experience issues with offsets if you use hidden columns in forms. For example, if you have two members in hidden column, and you try to paste values from five copied columns, only 3 columns are pasted.

·   14400565

Quotes do not display around dimensions whose members you select for business rules.

·   14395067,
14393132

If you launch a business rule in Planning or Workspace, no dialog box displays to indicate if the calculation is running or has finished running.

·   14393891

If you do not specify a value when creating a substitution variable, Planning becomes
unresponsive.

·   14319274,
14031323

You receive a script error in Internet Explorer and you cannot view member formulas for certain accounts in Workspace if the formulas are for members with ‘%’ in their names.

·   14268189

Although messages indicate that they were, values are not updated after you run calculation scripts upon save if you connected to Planning from the Workspace and if ADF is enabled.

·   14311779

Entry Ids that you specify for Smart Lists that you create may not be saved correctly.

·   14299784

You receive errors if you put forms of different data types, such as currency and percentage on a composite form.

·   13868533

If a Planner selects the Launch Tasklist Wizard icon before refreshing the screen, an error occurs.

·   14271828, 14234748, 12612517

Opening a runtime prompt while launching a rule takes too long.

·   14270270

Values are truncated if they exceed the width of the cell into which you are entering them.

·   14247852

SQL users receive this error when adding documents to cells in forms:
 
Query Failed: SQL_ADD_CELL_ATTACH_ITEM:[-1,
http://<server>:<port number>/raframework/browse/dyn?page=/jsp/com/hyperion/tools/workspacepages/mrulisting.jsp&cssUri=%2E%2E%2Fthemes%2Ftheme_tadpole%2Fhomepage%2Ecss&showTitle=true&theme_dir=themes%2Ftheme_tadpole%2F#, 1, null, null] java.sql.SQLIntegrityConstraintViolationException: ORA-02291: integrity constraint (TESTAPP.FK_HSP_CELNOTE_ID) violated - parent key not found

·   13867527

In Manage Approvals, clicking an action link for a planning unit node with a secondary dimension causes an error. Workaround: Use the Change Status button to modify the state of these planning units. (Note that the Change Status button is only available in Flat View.)

·   14232448

Although access has not been provided for them, users can access all task lists in ‘My Task Lists’.

·   14231926

Although you specify another column width, forms use the default column width.

·   14231820

You receive this error message, and values are converted to be in exponential notation when you adjust data on grids by percentage: 

The format is incorrect. The values you are trying to paste contain non-numeric values.

·   14216692

Although they are set to "hide"some row dimensions display unexpectedly.

·   14190917

You receive this error after double clicking a row on a form tagged as master in a master composite form, in order to apply a filter on a simple form:

java.lang.NullPointerException
ADF_FACES-60097:For more information please see the server's error log for entry beginning with: ADF_FACES-60096: Server exception during PPR #2

·   14169869

When designing forms, you cannot select and move calculation scripts as expected.

·   14152664

If using two applications simultaneously, you receive an ADF_FACES-60097 error on the Performance Setting tab when managing dimensions.

·   14141211,
14038896

The Export to Excel forms feature incorrectly renders Cyrillic characters. For example, "%" is displayed as "1023E21".

·   14123580

The Point of View does not update correctly if you navigate between forms that have custom menus using the Return to previous form function.

·   14467087

You receive the following error after transforming a Classic application with multiple years to Enterprise Performance Management Architect, adding a year in the dimension library, validating the application, and then redeploying it.


Consolidation operators for years must be set to Ignore for all plan types. Rejecting <Member>.

·   13855699

In a composite form, if you enter a data value in the top grid and then click the lower grid and click Save, the message says the save was successful but the data value is not saved.

·   14399418,
14399418, 14504639  

You may receive an error using a task list if it contains more than 25 tasks.

·   14468275, 13930137  

If the result of an adjustment on a form cell value is greater than 10,000,000, the results display incorrectly, with the decimal of the adjusted value incorrectly placed. 

·   14400248

11.1.2.2 users receive this error, and the application may become unresponsive while opening a task after clicking the Action column:

Java.lang.NullPointerException ADF_FACES-60097”

 

Public Sector Planning and Budgeting

Defect Number

Defect Fixed

·   13982781

For decision package-enabled budget requests, gross earnings and taxable compensation may calculate incompletely on Edit Employee Details. To resolve this issue, calculate compensation budgets from My Task Lists.

·   13903501

In decision package-enabled application based on the Employee configuration option, tax totals may not be properly calculated or displayed in budget requests.

·   13856610

When managing default compensation, and when multiple compensation elements per category exist, only the default compensation that is last in the list for each category is added to a new position.

·   13796448

You cannot delete decision package and budget request notes and attachments.

·   13732681

When creating a decision package type, composite forms specified on the Data Collection Forms tab are not saved.

·   13466161

You cannot perform reverse transfers to transfer employees and positions back to their original entities.

·   13407417

When working with decision packages and budget requests, you cannot display member aliases when selecting members.

·   14134505

While creating a decision package-enabled application, you must select all plan types.

·   13903813, 13903501

In decision package-enabled applications that use the employee configuration detail, tax calculations may not compute correctly.

·   13899540

In decision package-enabled, and rule-enabled Public Sector Planning applications, the annual salary spread options of Workdays and Paydays do not work as expected.

·   13866265

Annotations added during decision package approval are not saved.

·   14389710

Taxes are not included in the total compensation expense you calculate for total position cost at the employee level.

·   13472344,
9873271

In Public Sector Planning and Budgeting applications, if Value Type Input is Percent, and Payment Terms is Monthly, you have to enter 1/12 of the correct percent. For example, on the "Manage Other Compensation Components form" you should be, but are not, able to enter a percentage for a month, but instead the application adds the percentages of each month to derive an annual percent that is then multiplied by the salary.

·   12847735

You cannot calculate the compensation for only a subset of the years spanned by an application by restricting Year in the EP_SC_EmpDistElmCost_All rule.

·   13899540

For decision package- and business rule-enabled Public Sector Planning and Budgeting applications, Annual Salary Spread Workdays or Paydays is not working as expected.

·   13877081

Increment to Next Step does not increment the steps when incrementing is based on the adjustment date in a decision package-enabled application.

·   13644320

If you rename the Request dimension, when using Lifecycle Management, a second Request dimension is created if you export a decision package-enabled application and then try to import the application. Workaround: Do not rename the Request dimension.

·    13491643

When you launch a business rule by right-clicking in a form, you must select the budget request member by selecting a Dynamic User Variable. Instead, the budget request member name should display.

 

Known Issues in this Patch

This section identifies the noteworthy known issues in this patch.

Integration with PeopleSoft

OAM integration with PeopleSoft is not supported in this patch.

Public Sector Planning and Budgeting

·         14070719 - The run on save function may not work as expected for budget requests comprised of multiple forms.

·         14460520 - Internet Explorer 8 users may experience panel splitter issues or receive a JavaScript error when performing tasks on the Manage Request Positions form in decision package-enabled applications. If you modify the splitter position and reduce its size to enlarge forms, you can access position details. However, if you do not modify the splitter's position and load or specify position details, all data may not display because of reduced form size. Consequently, Oracle recommends that you use Internet Explorer 9.

·         14371168 - In decision package-enabled applications, right-click menu options for positions may be unavailable for the Manage all positions task after you add new positions using the Manage request positions task.

·         14410245- When adding other compensation elements to positions by selecting Manage compensation defaults, compensation elements are not added to a new position if the element option start date occurs after the position start date. To resolve this issue, add the element manually or perform a Mass update position and employee data to fill the positions.

·         14340834 - You must double-click a decision package type twice to open it.

·         14534927 - You may lose assigned FTE values after you change the values for the "Compensation_Budget_Start_Year' and 'Compensation_Budget_End_Year' substitution variables and perform a Reset FTE and Status calculation.

·         14543467 - Reverse transfers may not work correctly if adjustments are performed on the same day as the reverse transfers are executed.

·         14538494 - The Position Adjustment report does not display data for Unspecified Budget Request. To resolve this issue, select the system generated budget request member when defining the report.

Planning and Project Financial Planning

·         17742468 - The FormDefUtil utility cannot export Planning forms if the form name has a colon in it. Oracle recommends that you use Lifecycle Management to handle export and import of all Planning artifacts.

·         14491094 - Although they can navigate form tabs after closing the error, Internet 9 users may receive this error when opening forms in Edit mode and using the form tabs:

·         Message: Unable to get value of the property 'getClientId': object is null or
undefined Line: 686 Char: 481 Code: 0
URI:
http://hostserver:19000/HyperionPlanning/afr/partition/ie/n/default/opt/core-11.1.1.6.2-2198.js

·         14525863 - Although the owning users were deleted from a source application, you may receive this error when importing planning units previously owned by the deleted users using Lifecycle Management:

ID OF PLANNING UNIT CREATOR IS UNKNOWN

·         14312153 - The TRUNCATE function does not work as expected in FORMULA ROW on forms.  For example, if a cell (a[1]) has value of -0.27000000190734863 and a FORMULA
ROW with the function Abs(a[1],0), the returned value for the function should be 0, but it is not.                        

·         14284303 - When using the DIM Adapter for Planning, you receive error messages and data fails to load if the date format (DATE_FMT) in the HSP_SYSTEMCFG table is mm/dd/yyyy. To resolve this issue, back up the database, change the data format to MM-DD-YYYY, restart all related services, and try to load again.                                       

·         14270412 - If 25 or more members for a dimension exist, new members that you add may not display as expected. Also, the dimensional hierarchy may not immediately reflect members that you delete.           

·         14398885 - After using Lifecycle Management to import a Project Financial Planning application created in Enterprise Performance Management Architect, you
may receive a "deployment completed due to error" message caused by missing substitution variables. To resolve this issue, manually recreate these variables using the following settings, and then redeploy:

o    CurYr—The current year. For example, if the current year is 2012, set this variable to FY12.

o    LastYr—The previous year. Ensure that the previous year exists in the year dimension.

o    NextYear— The next upcoming year, such as FY13

o    Yr3—The year after NextYear, such as FY14

o    Yr4—The year after Yr3, such as FY15

o    ThisMonth—The current month

o    CurScenario—The current scenario

o    CurVersion—Working

o    ActVersion—Final

o    ForVersion—Working

o    PlanVersion—Final

o    Thisyear—The current year

 

 

·         14483057 - If you encounter defect 14398885, created the substitution variables described in the previous bullet, and received the error above after creating or refreshing the database in Planning, run Update custom defined functions option and then create or refresh the cube.

·         14059986 - In run time mode, only the first dimension displays on a row if Start Expanded is disabled. For example, if you create a form with Account and Entity on a row,
put the Account dimension first and Entity dimension second, select members for Entity using the following function, set Disable option to <Start expanded> for Entity dimension members, and then invoke the form in run time mode, only the first member (ichildren (ent1)) displays on the form:

acct1
IChildren(ent1),IChildren(ent2, IChdildren(ent3)


For information about known issues in release 11.1.2.2.000, see the Planning 11.1.2.2.000 Readme.

Documentation Updates

For Public Sector Planning and Budgeting 11.1.2.2.000, the help system accessed from within the product has been updated for the 11.1.2.2.300 release. If you open a help system from the product menu, the 11.1.2.2.300 Public Sector Planning and Budgeting  help system is displayed.  If you require a help system for the 11.1.2.2.000 release, you can download it from the documentation library: http://docs.oracle.com/cd/E17236_01/index.htm/

Oracle Hyperion Public Sector Planning and Budgeting User's Guide

Chapter 9: Working With Human Capital Compensation Budgets

Assigning Employees to Positions


To replace a To-Be-Hired employee currently assigned to a position with an existing employee, both employees must have the same:

·         Employee Type

·         Hire Date

·         Pay Type

·         FTE

Chapter 14: Using Reports and Budget Books

Customizing Reports in Oracle Business Intelligence Publisher


The file, sample report, and template names given in table in this section are incorrect. Use the following table instead. Also, HspJS.jar is in EPM_ORACLE_HOME/products/Planning/lib.

Report Type

Sample File Name

Template Name

Decision Package Listing - Summary

PlanningDPListingSample.xml

PlanningDPListingTmplt.rtf

Decision Package Listing - Detail

PlanningDPListingSample.xml

PlanningDPDetailTmplt.rtf

Decision Package Cost By Entity

PlanningDPListingSample.xml

PlanningDPBreakUPByEntityTmplt.rtf

Decision Package By Entity - Summary

PlanningDPEntityListingSample.xml

PlanningDPByEntityTmplt.rtf

Decision Package By Entity – Detail

PlanningDPEntityListingSample.xml

PlanningDPByEntityDetailTmplt.rtf

 

Oracle Hyperion Planning Administrator's Guide

Chapter 9: Managing the Budget Process

Adding Tasks to Task Lists

Alerts on Planning task lists do not display as colored circles. Disregard the content in this section describing the colored alerts.

Chapter 13: Customizing the Planning Web Client

Customizing the Style of Header Cells in Forms

Applying a bold style to all forms

1.  From HyperionPlanning.war\custom, open HspCustom.css and insert this class code:

customheaderStyle

Font-family:<font>;

Font-size:<size>;

Font-weight:bold;

For example, to use bolded garamond 14 as the style for header cells you would specify:

customheaderStyle

Font-family:garamond;

Font-size:14;

Font-weight:bold;

You can also change the font and the font size in the same portion of code.

2.    Perform the tasks in "Registering Customized Skins in Applications".

 

Applying a bold style to one form

1.    Determine the ID of the form to customize by running this query in which ‘<FORM_NAME’ is the name of the form:

Select object_id AS FORM_ID,object_name AS FORM_NAME from hsp_object 
where object_name like ‘<FORM_NAME>’

For example, to modify a form called "1.30 Per Payor – Metrics”, you would run this query:

Select object_id AS FORM_ID,object_name AS FORM_NAME from hsp_object where object_name like "1.30 Per Payor-Metrics"

2.    When the ID is returned, create a css class in HspCustom.css using the following format.  HspCustom.css is in HyperionPlanning.war\custom.

“customheaderStyle_<FORM_ID>”

 

3.    Set font-weight in .customheaderStyle as bold as shown below. You can also change the font and the font size in the same portion of code.

customheaderStyle

Font-family:<font>;

Font-size:<size>;

Font-weight:bold;

4.    To use different styles on individual forms, create a css class for each form.

5.    Perform the tasks in "Registering Customized Skins in Applications".

Customizing Skins to add Components

To customize an existing skin to add components:

1.    Create a file called trinidad-skins.xml, and insert this code:

<skins xmlns="http://myfaces.apache.org/trinidad/skin">

    <skin>

        <id>HspCustom.desktop</id>

        <family>HspCustom</family>

        <extends>blafplus-rich.desktop</extends>

        <render-kit-id>org.apache.myfaces.trinidad.desktop</render-kit-id>

        <style-sheet-name>custom/HspCustom.css</style-sheet-name>

    </skin>

</skins>

        

2.    Specify the following in the code: 

o    Family ‑ The name of the new skin

o    Style-sheet-name‑ The custom css file that contains the style selectors

o    Extends‑ The skin being modified 

3.    Override the desired style selectors.

4.    Perform the tasks in "Registering Customized Skins in Applications".

Registering Customized Skins in Applications

1.    Add the updated files to HyperionPlanning.ear.

2.    Put trinidad-skins.xml in HyperionPlanning.war\“WEB-INF\.

3.    Copy the new HspCustom.css to HyperionPlanning.war\custom to replace the existing css file.

4.    Copy the updated .ear file to: EPM_ORACLE_INSTANCE_HOME\products\Planning\AppServer\InstallableApps.

5.    Redploy to the application server.

6.    Restart the application server and clear the browser cache.

7.    In Planning, select Administration, then Application, and then Properties.

8.    Create a new application property called SKIN_FAMILY.

9.    Set the property value to reference the custom skins, such as HspCustom.

10. Log out, and then log in.

About Customizing ADF Components

Skin style selectors in ADF enable you to customize the appearance of UI components. Style sheet rules include a style selector, which identifies an element, and a set of style properties, that specify the appearance of the components.

ADF Faces components include these categories of skin style selectors:

·         Global selectors - Global selectors determine the style properties for multiple ADF Faces components

·         Component selectors - Component-specific selectors are selectors that can apply a skin to a particular ADF Faces component

For more information on style selectors, see:

·         http://docs.oracle.com/cd/E23943_01/apirefs.1111/e15862/toc.htm

·         http://www.oracle.com/technetwork/developer-tools/jdev/index-092146.html

·         http://docs.oracle.com/cd/E16764_01/web.1111/b31973/af_skin.htm

Oracle Hyperion User's Guide

Chapter 2, "Working with Task Lists"

Working With Task Lists and Tasks

Planning task lists do not display colored alerts. Disregard the content in this procedure for alerts.

Miscellaneous

Although the online help does not describe how to use formatting, you can format text you enter in Text-type cells.

Applying this Patch

The section includes important information about applying this patch for Planning.

To apply this patch:

1.    On each computer on Planning and Calculation Manager are installed, apply the Calculation Manager patch 13925741 first, before applying this Planning patch. See "Prerequisites".

2.    Ensure that you installed the required EPM System, OPatch, and the ADF patches. See "Prerequisites".

3.    Public Sector Planning and Budgeting 11.1.2.2.000 users: Create a test environment before applying this patch.

4.    Stop all of the EPM and Calculation Manager services running on the Planning server where this patch is being applied, including the Planning server, RMI services, and Financial Reports.

5.    Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

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

6.    On the Planning server machine, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

7.    Enter the appropriate command on one line:

Microsoft Windows:

opatch.bat apply <EPM_ORACLE_HOME>\OPatch\13905088 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>\jdk160_29

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/13905088 -oh /<EPM_ORACLE_HOME> -jre /<MIDDLEWARE_HOME>/jdk160_29 -invPtrLoc/<EPM_ORACLE_HOME>/oraInst.loc

The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

8.    Delete the tmp directory for the Planning server in: <MIDDLEWARE_HOME>/user_projects/domains/EPMSystem/servers/<server>
where <server> is the Planning server (for example, Planning0).

The full path for tmp is: <MIDDLEWARE_HOME>/user_projects/domains/EPMSystem/servers/<server>.

9.    Restart all the services on the Planning server that were stopped in Step 1, including the Planning server, RMI services, and Financial Reports services.

10. WebSphere users: Manually redeploy from the WebSphere Integrated Console as described in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

11. Have all users clear cached files from their browsers.

12. For each application you created before applying this patch, refresh the application database by selecting Administration, then Application, then Refresh Database, and then Update custom defined functions.

13. Perform any required post installation steps as described in the following sections.

Post Installation Requirements

Steps if Other Enterprise Performance Management Products Reside on a Server Other Than the Planning Server

 

Perform these steps on all servers that host any EPM system products other than Planning. For example, if ERPI Integrator and Performance Management Architect are installed on different a server than the Planning server, perform the following procedure on the server hosting ERPI and EPMA. 

1.    Stop all running EPM services.

2.    Make a backup copy of the files in: <EPM_ORACLE_HOME>\common\planning\11.1.2.0\lib.

3.    Extract the 11.1.2.2.300 planning patch zip file, copy all of the files in 13905088\files\common\planning\11.1.2.0\lib, and paste them in: <EPM_ORACLE_HOME>\common\planning\11.1.2.0\lib.

4.    Restart the EPM services. 

Steps if Planning and Financial Reporting are on Different Servers


If Financial Reporting (FR) is on a server other than that of Planning, perform these steps on the FR server:

1.    Stop all of the EPM services running on the FR server, and stop the FR server.

2.    Make a backup copy of all your existing files that will be replaced in the following steps. For example, rename existing HspJs.jar file as HspJs.jar.original.

3.    Extract the 11.1.2.2.300 planning patch zip file, unzip the 13905088 patch zip file, and copy HspJS.jar and HspAdm.jar in ­­\13905088\files\common\ADM\Planning\11.1.2.0\lib.

4.    Paste the copied files in these directories: 

o    <EPM_ORACLE_HOME>\common\ADM\Planning\11.1.2.0\lib

o    <EPM_ORACLE_HOME>\common\ADM-64\Planning\11.1.2.0\lib (if it exists)

5.    Copy the .dll or .so files from these directories:

o    13905088\files\common\ADM\Planning\11.1.2.0\bin\

o    \13905088\files\common\ADM-64\Planning\11.1.2.0\bin (if the FR server is 64-bit)

6.    Paste the copied files in these directories:

o    <EPM_ORACLE_HOME>\common\ADM\Planning\11.1.2.0\bin

o    <EPM_ORACLE_HOME>\common\ADM-64\Planning\11.1.2.0\bin (if it exists)

7.    Restart the Financial Reporting Server and all EPM services on the server.

8.    Restart the Planning server.

 

Steps for Project Financial Planning

1.    Perform the steps for your operating system (defect 13930239):

UNIX/Linux:

o    Copy PFPImportUtility.sh.template from <EPM_ORACLE_HOME>/products/Planning/bin, and paste it in <EPM_ORACLE_INSTANCE>/Planning/planning1.

o    Rename the copied file PFPImportUtility.sh.

o    Open the file in vi editor and change the value of EPM_PLANNING_INSTANCE to the current directory that contains the utility file. For example, EPM_PLANNING_INSTANCE= $HOME/Oracle/Middleware/user_projects/epmsystem1/Planning/planning1.

o    Save the file.

o    Grant Read, Write, and Execute permissions to the file.

Microsoft Windows:

o    Copy PFPImportUtility.bat.template from <EPM_ORACLE_HOME>/products/Planning/bin to <EPM_ORACLE_INSTANCE>/Planning/planning1.

o    Rename the copied file PFPImportUtility.bat.

o    Open the file in Notepad, and change the value of EPM_PLANNING_INSTANCE to the current directory that contains the utility file. For example, EPM_PLANNING_INSTANCE=C:/Oracle/Middleware/user_projects/epmsystem1/Planning/planning1.

o    Save the file.

o    Grant Read, Write, and Execute permissions to the file.

2.    To display the help in a supported non-English language: Perform these steps after applying the OPatch:

o    Navigate to <EPM_ORACLE_INSTANCE>\bin. For example, C:\Oracle\Middleware\user_projects\epmsystem1\bin.

o    Click epmsys_registry.bat, and in the report that displays search for the object ID for PLANNING_LWA.

o    Write down the ID for this object.

o    Open a command prompt or terminal and go to <EPM_ORACLE_INSTANCE>\bin.

o    Run this command:                                            

epmsys_registry updatefile #11d1def534ea1be0S2f16fcf513423cbfb63S7801/@WorkspaceConfig <EPM_ORACLE_HOME>\products\Planning\registry\WorkspaceConfig.xml                  

where 11d1def534ea1be0S2f16fcf513423cbfb63S7801 is the Object ID of PLANNING_LWA.               

For example, the command for Windows is:

epmsys_registry updatefile #11d1def534ea1be0S2f16fcf513423cbfb63S7801/@WorkspaceConfig C:\Oracle\Middleware\EPMSystem11R1\products\
Planning\registry\WorkspaceConfig.xml                                    

o    Restart Planning and Foundation services.                                                                             

Steps for HP UX Itanium Users (Defect 14396123)

If you use HP UX Itanium perform these steps after applying this patch:

1.    Stop the Planning server.

2.    Run the following to set the shared library .so files as executable: chmod 750 <EPM_ORACLE_HOME>/products/Planning/lib64/libHsp*.so

3.    Restart the Planning server.

 

Upgrading Existing Public Sector Planning and Budgeting Applications

Before You Begin

Before upgrading your existing 11.1.2.x (11.1.2.1 or 11.1.2.2.2) applications to 11.1.2.2.300 release, perform these tasks:

·         Read the upgrade sections to familiarize yourself with the process beforehand.

·         Create a test environment that is identical to your existing production environment.

·         Perform all the upgrade steps on a test environment first.

·         Understand that some steps may not be required based on the release of your existing application.

·         If you customized your budget applications by modifying predefined rules  , then take a backup of the changes by creating a copy so that your customizations are not lost.

·         To acquire the new decision package and PeopleSoft commitment control functionality, install Public Sector Planning and Budgeting 11.1.2.2. These new features are not supported for earlier upgrades.

Requirements

Before running the Upgrade Wizard during installation, perform these tasks:

·         Ensure that you can log on to Shared Services Console using an account enabling Lifecycle Management tasks.

·         Ensure that you can log on to Oracle EPM Workspace as a Financial Reporting administrator.

·         11.1.2.1 users: On the test environment, upgrade Planning to Release 11.1.2.2 as described in the Oracle Enterprise Performance Management System Installation and Configuration Guide and "Managing Upgrades" in the Oracle Hyperion Planning Administrator's Guide.

·         Update references to rehosted data sources (relational databases and Essbase servers). See "Managing Upgrades" in the Oracle Hyperion Planning Administrator's Guide.

·         After applying this 11.1.2.2.300 patch as described in this document, create a 11.1.2.2.300 aapplication as follows so that it is identical to the 11.1.2.1 or 11.1.2.2. test application. In subsequent steps, Application A refers to your existing 11.1.2.1 or 11.1.2.2 application before you applied this patch. Application B refers to the application created after you applied this 11.1.2.2.300 patch. When creating application B, ensure that it is identical to application A application as follows:

o    11.1.2.1 users: Do not enable the Decision Package and Commitment Control options.

o    If you are migrating from 11.1.2.2 and your existing application A is enabled for Decision Package and Commitment Control, use the same option when creating application B.

o    Use the same configuration option

o    Use the same currency options

o    Use the same calendar definition (application start year and number of years, for example)

Important Note: If your existing Application A uses Business Rules as the calculation module, must migrate all your applications from Oracle Hyperion Business Rules to Calculation Manager before proceeding with the rest of the update steps. For information about migrating, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.

·         Launch Planning 11.1.2.2.300 and open application A, and then click Upgrade. This performs the required schema upgrade. If you are upgrading an 11.1.2.2 application, then apply the following change to the planning relational data source for application A and restart planning server:

ALTER TABLE HSP_FORMOBJ_DEF_MBR DROP CONSTRAINT FK_HSP_FDEFMBR_MID;

About Migrating Data and Artifacts

The following is an overview of the tasks required to migrate data and artifacts from the application B to application A:

1.    Meet the requirements.

2.    Make changes in dimension metadata of application A using Planning or Oracle Hyperion EPM Architect as described in “Migrating Dimensional Metadata”.

3.    Migrate business rules using Calculation Manager as described in “Migrating Business Rules”.

4.    Migrate substitution & user variables, forms, smart lists, menus, reports, and task lists using Lifecycle Management in the Shared Services Console as described in the following sections.

5.    Perform post migration tasks such as refreshing the application.

6.    Verify the migrated data, and then use the same procedure to migrate the 11.1.2.1 or 11.1.2.2 production environment.

Options and Considerations

Migrate your existing Public Sector Planning and Budgeting metadata and data based on your situation. Note: Support for decision packages and PeopleSoft Financials Commitment Control introduced in 11.1.2.2 are available only for new applications; these features are not supported for existing 11.1.2.1 applications.

·         If you want to get only the updated business logic in 11.1.2.2.300 and do not want to update forms, reports, or tasks in the application, and you haven't customized your existing application, perform the tasks in these sections in this order:

o    “Migrating Dimensional Metadata”

o    “Migrating Business Rules”

o    Note: If you previously used Business Rules as your calculation engine, you cannot update only business rules, and must also migrate data forms, menus and tasks lists. In this case you must perform the steps in “Migrating Forms, Menus, Reports, and Task Lists”.

·         If you want all the new functionality in 11.1.2.2.300, and have not customized your existing application, perform the tasks in these sections in order:

o    “Migrating Dimensional Metadata”

o    “Migrating Business Rules”

o    “Migrating Forms, Menus, Reports, and Task Lists”

o    “Migrating Smart List Metadata”

·         If you want all the new functionality in 11.1.2.2.300, and you modified your existing application dimensionality and artifacts, perform the tasks in these sections in order:

o    Create a copy of the artifacts that you modified (for example, using Save As functionality). This ensures that you have a copy of all artifacts. If you saved modified artifacts using a new name, they are not overwritten.

o    “Migrating Dimensional Metadata”

o    “Migrating Business Rules”

o    “Migrating Forms, Menus, Reports, and Task Lists”

o    “Migrating Smart List Metadata”

o    Reinstate the artifacts that you copied restore your changes. Caution: To keep the changes from the predefined application for artifacts that were brought into the 11.1.2.1 test application, skip this step for those artifacts; alternately, you can merge your changes as you deem necessary.

Migrating Dimensional Metadata (Only for a 11.1.2.1 application upgrade)

The following procedure applies only to applications that use Planning application administration. If you created your applications in Performance Management Architect, you must apply similar changes in Performance Management Architect, and then redeploy the application. Note: Steps 1-6 below are only applicable for upgrading applications from 11.1.2.1 release. However, step 7 is required for both 11.1.2.1 and 11.1.2.2 application updates.

To migrate dimensional metadata:

1.    Log on EPM Workspace as an administrator, and open Application A.

2.    Select Administration, then Manage, and then Dimensions.

3.    Select the Account dimension, and then perform these tasks:

o    For the Option Value and Override Option Value members, set the Data Type to Currency and the Exchange Rate Type to Average.

o    For the Account Segment and Account Segment Description members, add a UDA called Natural_Account.

4.    If the application uses the Position and Employee configuration option:

o    In the Account dimension, select Edit for the Available FTE member, select Member Formula, and then copy the member formula from the B application.

Add a member called Replacement FTE as a child member under Total FTE with the Source Plan Type set to HCP, and Data Storage set to Store. For the HCP plan type, change the consolidation operator to Ignore.

o    Copy the member formula for the Approved FTE member from Application B, replacing that member formula for the Approved FTE member in Application A.

5.    If the application uses the Position and Employee or the Employee configuration option, perform these tasks:

o    Select the Employee dimension.

o    Select the Total Employees member, and then click Edit.

o    Change Data Storage to Never Share.

o    Select Member Formula, and then delete the member formula.

6.    If the application uses the Employee configuration option, perform these tasks, and then continue with step 7 in the next section:

o    Select the Account dimension.

o    Select the Assigned FTE member, and then change Data Storage from Dynamic Calc to Store.

o    For the HCP plan type, change the consolidation operator to Ignore.

o    Select Member Formula, and then delete the member formula.

Migrating Dimensional Metadata (for both a 11.1.2.1 and 11.1.2.2 upgrade)

7.    Copy the member formula for the Monthly Spread Factor member in Application B, and use it to replace the member formula for the Monthly Spread Factor in Application A.

8.    Perform a cube refresh.

Migrating Business Rules


To migrate business rules:

1.    Log on to EPM Workspace.

2.    Select Administer, and then Calculation Manager.

3.    Expand Planning.

4.    From the list of applications, select test Application A.

5.    Make and maintain a copy of business rules that you may have modified, such as those used in General Ledger allocations.

6.    Right-click Application A, and then select Load Predefined Rules.

7.    Right-click Application A again, and then select Deploy.

Migrating Forms, Menus, Reports, and Task Lists


To migrate forms, menus, reports, and task lists:

1.    Satisfy the requirements.

2.    Migrate composite forms, menus, task lists, forms, data load settings, and user variables from Application A to Application B as follows:

o    Log on to the Shared Services Console as an administrator.

o    Expand Application Groups, and then select Application B.

o    Expand Configuration, and then select Data Load Settings and User Variables.

o    Select Application, then Global Artifacts, then Substitution Variables

o    Expand Global Artifacts, and then select:

-      Composite forms

-      Custom menus

-      Task lists

o    Expand Plan Type, expand HCP, and then select Data Forms.

o    Select Export, and then export the artifacts to the file system by giving the appropriate folder name.

o    Import the exported application data set into Application A.

3.    Export the reports from Application B as follows:

o    Log on to EPM Workspace as a Financial Reporting administrator.

o    Click Explore.

o    Navigate to Application B.

o    Select Human Capital Planning.

o    Select File, and then Export.

o    Export all the reports into a .zip file.

4.    Import the reports to Application A as follows:

o    Log on to Oracle Hyperion Enterprise Performance Management Workspace as a Financial Reporting administrator.

o    Under the Application A folder, select Human Capital Planning.

o    To preserve reports you changed, rename the reports.

o    Select File, then Import, and then Financial Reporting Documents.

o    Import the reports you exported to a .zip file, overwriting the existing reports.

5.    After importing all reports, select Tools, then Change Database Connection, select the reports, click OK, and then select the new database connection name.

Migrating Smart List Metadata

The following procedure applies to applications that use Planning application administration. If you use Performance Management Architect to manage applications, refer to the Oracle Enterprise Performance Management System Lifecycle Management Guide to migrate Smart Lists, and then redeploy the application to Planning.

Migrate these Smart Lists, using the following procedure:

o    Employee_Status (if you use the Position and Employee configuration option)

o    Employee_Type (if you use the Position and Employee configuration option)

o    Operation_Status

o    Period List

o    Position_Status

o    Salary Basis


To migrate Smart Lists:

1.    Log on to Shared Services Console as an administrator.

2.    Expand Application Groups, and then select Application B.

3.    Select Application, then Global Artifacts, then Smart Lists, and select the Smart Lists listed above.

4.    Click Export, and then export the artifacts to the file system by giving the appropriate folder name.

5.    Import the exported Smart Lists data set to Application A.

 

Post Migration Tasks


After migrating data, perform these tasks:

1.    Log on to the Public Sector Planning and Budgeting Application A to confirm that the migrated task lists, forms, and custom menus display.

2.    Select Administration, then Application, and then Refresh Database.

3.    Select Database, select Update custom-defined functions, and then click Refresh.

4.    Select Administration, then Manage, and then Variables and then chose Substitution Variables tab. Set values as per your budget period to the substitution variables Compensation_Budget_Start_Year and Compensation_Budget_End_Year

5.    To accommodate any data changes, perform these tasks:

o    To recalculate compensation budgets, for every combination of scenario and version where you have data, recalculate compensation budgets for Total Entity.

o    For every combination of scenario and version where you have data, allocate modified compensation expenses to General Ledger accounts for Total Entity, All Positions, and Total Employees. Use the mapping reporting application functionality to push the newly allocated data to the Line Budget cube.

6.    Repeat the procedures above to migrate metadata and data from the test environment to production.

 

Rolling Back this Patch

To roll back a patch:

1.    Stop all of the EPM services running on the Planning server where this patch is being applied, including the Planning server, RMI services, and Financial Reports.

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

3.    Enter the appropriate command on one line:

Microsoft Windows:

opatch.bat rollback -id 13905088 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_29

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 13905088 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME> /jdk160_29 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

4.    Delete the tmp directory for the Planning server in: <EPM_ORACLE_HOME>/user_projects/domains/EPMSystem/servers/<server>
where <server> is the Planning server (for example, Planning0).

The full path for tmp folder is: <EPM_ORACLE_HOME>/user_projects/domains/EPMSystem/servers/<server>.

5.    Restart all the services on the Planning server that were stopped in Step 1, including the Planning server, RMI services, and Financial Reports services.

6.    Have all users clear cached files from their browsers.

7.    For each application created before you applied this patch, copy HSPCDFUT.CDF.JAR by selecting Administration, then Application, then Refresh Database, and then Update custom defined functions.

8.    If Planning and Financial Reporting are installed on different servers: Restore the files you backed up in "Post Installation Steps if Planning and Financial Reporting are on Different Servers".

9.    If other EPM products are installed on a different server than Planning: Restore the files you backed up from <EPM_ORACLE_HOME>\common\planning\11.1.2.0\lib.

 

Troubleshooting FAQs

Why do I get errors using Opatch to install a patch to an ODI 11g 64-bit configuration:

If you receive this error, perform the task described below

java.lang.UnsatisfiedLinkError:
/opt/WebLogic/1034/Oracle_ODI1/oui/lib/solaris/liboraInstaller.so: ld.so.1:
java: fatal:
/opt/WebLogic/1034/Oracle_ODI1/oui/lib/solaris/liboraInstaller.so: wrong ELF
class: ELFCLASS64 (Possible cause: architecture word width mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1703)
at java.lang.Runtime.load0(Runtime.java:770)
at java.lang.System.load(System.java:1003)

You receive this error because of a missing parameter -d64 in oraparam.ini for 64 bit platforms. To resolve this, edit $ORACLE_HOME/oui/oraparam.ini and add -d64 in JRE_MEMORY_OPTIONS. For example: JRE_MEMORY_OPTIONS=" -d64 -mx512m -XX:MaxPermSize=256m"

Why do I get a 'ELFCLASS64 (Possible cause: architecture word width mismatch)' error?

When attempting to use the opatch utility to install a one-off patch into an ODI 11g configuration running on a 64 bits platform using "Oracle Data Integrator 11g for all Platform" shiphome, the following message is signaled:

java.lang.UnsatisfiedLinkError:
/opt/WebLogic/1034/Oracle_ODI1/oui/lib/solaris/liboraInstaller.so: ld.so.1:
java: fatal:
/opt/WebLogic/1034/Oracle_ODI1/oui/lib/solaris/liboraInstaller.so: wrong ELF
class: ELFCLASS64 (Possible cause: architecture word width mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1703)
at java.lang.Runtime.load0(Runtime.java:770)
at java.lang.System.load(System.java:1003)

 

The cause is the lack of parameter -d64 in oraparam.ini for 64 bit platforms. The generic shiphome is the same for both 32 and 64 bit architectures, so it is unable to add the parameter for 64 bit platforms. To resolve this issue, edit $ORACLE_HOME/oui/oraparam.ini file and add -d64 in JRE_MEMORY_OPTIONS.

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:

Windows:

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

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29 –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