Caution: Oracle urges you 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 service interruptions, loss of data, or both

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 and it is built on 11.1.2.3.700 of Planning.

Supported Paths to this Patch

You can apply this patch to below releases:

· 11.1.2.3.700 (patch 20643564).

Prerequisites

EPM System Patches

Before applying this patch, install the below mentioned patch and all other required product patches as described in the 20643564 readme’s Prerequisites section

o Oracle Hyperion Planning -Release 11.1.2.3.700 Patch Set Update (PSU): 20643564

Required Microsoft Patch

Microsoft has identified a security issue that could compromise Windows-based systems. Before installing this patch, verify that the Visual C++ 2005 Redistributable Package installed on the computer is current. You may search and download the latest Visual C++ 2005 Redistributable Package from:

http://www.microsoft.com/en-us/download/default.aspx

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:

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.3.700 (Patch 20643564).

Supported Languages

This patch can be applied to all languages supported in release 11.1.2.3.700 of Oracle Enterprise Performance Management System. For the Oracle Enterprise Performance Management System Supported Platform Matrix, go to:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Defects Fixed in this Patch

Defect Number	Defect Fixed
· 17374983, 21795202	Users may not be able to input data into certain cells if the 'Hide Dimension' property in data form is selected.
· 17441244, 20763014	Empty row formula in a data form will be imported through LCM as null values in target application. Note: This fix will only correct the issue for empty row formulas created after applying this patch
· 18466964, 18608290	When a Financial Reporting report uses Planning as a data source and contains the Parent function, the function returns the value of the member itself instead of its parent.
· 18770610	Renaming of composite forms may not work.
· 18936072, 19004465, 19903967	When limits are defined on runtime prompts, member hierarchy displays incorrectly in Smart View.
· 19473936	The Point of View (POV) is not retained when navigating between data forms using context menus in Smart View.
· 19581225, 20664332	In data forms that contain Year-To-Date (YTD) members in the page dimension, changing the selection of YTD member does not display the correct data, the data for the first YTD member always displays.
· 19661021	Email notifications for task may be sent to users at periodic intervals even when user has not enabled the option for notification.
· 20563599, 20122445	User may encounter the error 'Unable to obtain dimension information and/or perform a data load: For input string' when using the 'Export the data to File' from Planning web.
· 20692626	You cannot import the scenario dimension if you change the base time period member names.
· 20747254	Users can launch business rules from context menus even when users do not have access to the rule.
· 20805463	Users may not be able to access Planning application in workspace if application had task lists with cyclic reference to each other.
· 20888836	The hide prompt option is not honored in Smart View.
· 20948001	In Enterprise Performance Management Architect Planning application, newly added members may not appear in data form if Suppress Missing Blocks is enabled.
· 20976234	If member name has single quote in it and is used as launch value for Run Time Prompt, user may not be able to open member selector in Smart View subsequent to launching the rule using this member.
· 20985033	When importing Process Management definition through LCM, user may not be able to deselect scenario and version assignment.
· 21108168	When dynamic variables are defined with functions on a data form, an incorrect value is displayed in the data grid.
· 21147695	In Manage Approvals, Display My Planning Unit, does not show the Planning Unit owned by the user when Display Full User name is selected in Application Settings.
· 21615548	The member formula editor is escaping member names that contain a percent sign "%".
· 21674416	You may not be able to open the member formula editor in SSL enabled environments.

Public Sector Planning and Budgeting Defects:

Defect Number	Defect Fixed
· 18426238	Allows Positions or Employees to be transferred across Budget Requests
· 18559593	Enable Planning to return new transaction ID for each Post request if required.
· 20191659	Planning PSE 19791275 and PSE 20107021 are not included in Planning 11.1.2.3.700.
· 20410294	Performance issues with synchronizing Planning Unit Hierarchy.
· 20651643	Allocation fails when there are more than one allocation strings and budget cycle is 2 years or more.
· 21688663	When trying to create a budget request for a decision package, you may receive this error when creating a budget request: failed to associate budget request with the Essbase member, please associate the budget request to a member before entering data.
· 21688739, 21688868	Provide a new role in Shared Services that enables a non-administrator user to copy decision packages and budget requests. Note: 1. Please refer to “Enhancements included in this patch” section for details about this enhancement. 2. Refer to “Post Installation Steps” section for additional steps required for this enhancement.
· 21688815	Occasionally Planning might hang during Decision Package usage.
· 21688841	You may receive the following error message when creating budget requests even though there are enough request members for the given scenario and version: “There are insufficient members in Essbase defined for budget requests. Please contact your administrator to add more members before proceeding”.
· 21688894	Users, without receiving an error, could copy decision packages containing budget requests even if the budget request existed with the same name in the target scenario, version, and entity combination.
· 21688906	Navigation between forms did not work as expected when you edited budget requests by entering data in the associated forms.
· 21688934	Previously, attributes were not copied from source to target decision packages. You can now choose if you want to copy attributes.

Defects fixed in 11.1.2.3.700 Patch Set Update:

Defect Number	Defect Fixed
· 21114283	For rules that contain runtime prompts which are associated with data forms and set to Run on Save, the members are not sorted in the same order in the member selection dialog when the data form is saved in Planning web versus in Smart View.
· 21114310	The point of view is not retained when navigating between multiple forms in Smart View.
· 21114328	You can enter data for members for which you only have Read access using Smart View.
· 21114226	Task list order is not consistent between Smart View and the Planning web interface. Note: For this defect Smart View version should be 11.1.2.5.400 or higher.
· 21321522	Planning User variables values in User Preferences are not saved if more than 25 user variables exist, only the last variable in the list can be modified and saved.

Known Issues in this Patch

This patch does not contain any known issues.

Enhancements Included in this PSU – Applicable only to Public sector Planning and Budgeting applications

Requirements

Planners: Ensure that your user account must be provisioned with the Copy Decision Package role in Shared Services.

Administrators: Perform these tasks:

· Create the target scenario and version

· Assign the appropriate planners write access to the target scenario and version

· Assign the appropriate planning units to the target scenario and version combination

· Either create a baseline decision package on the target, or copy the baseline budget from the previous budget scenario and version to the target. To copy the baseline budget, perform the steps in Copying Decision Packages and Budget Requests, but select Replace or Add to ensure that justification criteria and attributes are copied

Recommendations and Important Notes

· Copy only source budget data that has been finalized and approved.

· Because exchange rates tables may differ between the source scenario and the target scenario, re-run the currency conversion calculations to translate data using the rates defined for the target scenario.

· Since not all decision packages and budget requests may be copied, run aggregation rules after copying to aggregate data to Total Entity.

· If a decision package that you copied to a target scenario and version is renamed in the source scenario and version, and the Copy Option is Add, the renamed decision package or budget request is copied to the target.

· For optimal performance, Oracle recommends that no more than 500 users are provisioned with the Copy Decision Package role.

What Copy Tasks Can Administrators Perform?

Administrators can (Planners cannot):

· Copy defaults for unspecified entities and unspecified budget requests

· Copy decision packages to unspecified target entities or entities to which they do not have write access

· Replace existing data in a decision package with copied data from another decision package

· Merge and integrate copied data to a single decision package in the target

What Copy Tasks Can Planners Perform?

Planners can only view decision packages to which they have write access to the owner or shared entity.

Depending on if data already exists in the target scenario and version combination, Planners can copy as follows:

· If the selected decision packages and budget requests to be copied do not exist on the target, Planners can copy if they have write access to the target scenario, version and entity member combination.

· If the target scenario and version already contain data: Planners can copy if:

o They have write access to the target scenario, version, and entity combination

o They are the current owner of target decision package entity

Factors and Conditions That Impact Copy Tasks

Factor or Copy Option	If	Then
Different owner entities	· Decision package owner entities are different on the source and target · If budget request owner entities are different on the source and target	· New budget requests are not added to the target decision package. Neither is decision package or budget request information like justification, attribute values etc.. are synchronized. · Budget requests data are not synchronized
Add	Initiated by a user in a decision package's shared entity	Budget requests are added to the target decision package, and the shared entity's list of decision packages reflects the budget request's owner entity
Synchronize	· Initiated by current owner of the owning entity · Initiated by user in the source decision package's shared entity · Initiated by a user who isn't the current owner of a budget requests owner entity	· Decision packages and budget requests are synchronized · The synchronization is performed if the shared entity already exists as the owner or shared entity for the target decision package. · Only the budget request detail data that the user owns in the budget request is copied.

About Synchronization

Synchronization updates the shared entities list for a target decision package or budget request fashion. It also adds any entities that exist on the source but not the target. Synchronization never removes entities that only exist on the target.

How Modifying Dimensions and Planning Unit Hierarchies Affects Decision Packages

· If a decision package that you copied is later renamed in the source scenario and version, and the Copy Option is Add, the renamed decision package or budget request is copied to the target.

· If changes were made to Entity members or planning unit hierarchies assigned to the scenario and version of the decision package to which you copy data, the approval hierarchies for the decision packages to which you copy data inherit the changes.

· If changes other than renaming are made to the attributes of a copied decision package or its budget requests, subsequent changes are not reflected in the target unless the Copy Option is "Add" or "Add" and "Synchronize".

· Changes made to a source scenario/version or target scenario/version may result in scenarios and versions that cannot be used together for variance analysis

Copying Decision Packages

1. Select Tools, and then Copy Decision Packages.

2. On Decision Packages, identify and select the decision package that contains the data to copy by specifying the source scenario and version.

3. Click Go.

4. In To Scenario and To Version, select the target scenario and version members to which to copy decision package data.

5. Filter the decision packages displayed by criteria such as approval status or rank or budget impact. To filter by custom attributes, perform these tasks:

o Click Advanced Search.

o From Decision Package Type, select the decision package type upon which the decision package is based.

o For each attribute in Decision Package Filters, enter or select values. For example, if you use an attribute called Implementation Date to gather the date by which decision packages and their budget requests must be complete and ready for final approval, specify that date.

6. From Copy Option, specify how to update the target with the decision package you are copying from the source:

o Replace--Overwrite existing decision packages in the target scenario and version with those that you are copying. This option is available only for Administrators.

o Add--Add the decision packages and constituent budget requests to existing decision packages in the target scenario and version. If the same decision package exists on the target scenario and version, and you want to update it with new decision package data, and changes made in the source, select Synchronize.

7. Perform a task:

o For Administrators copying the baseline budget: Select Replace and Add to copy justification criteria and attributes.

o For Planners: To choose whether or not to copy more recent attributes and justification criteria, select Add and Synchronize.

8. From Merge to one Decision Packages, select Yes to copy all budget requests in selected decision packages to a single target decision package that you specify. Select No to copy only the selected decision packages to the target scenario and version. This option is available only for Administrators.

Note: If you select Yes, ensure that the sharing defined for the owning entity in the target decision package grants the appropriate users and entities the access required to enter and modify data.

9. From Budget Type, indicate if the decision packages that you are copying contain recurring or non- recurring budgets.

10. Specify if you want to copy attributes, and supporting information, such as attachments and justification criteria.

11. Click Copy Data,.

12. Open the Job Console to review any warnings or errors that may have occurred.

13. After receiving confirmation that the copy was successful, if Human Capital Planning is implemented then, select Budget Preparation, and then select Calculate compensation budgets to process and view updated data.

Copying Decision Packages to Multiple Years

1. Select Tools, and then Copy Decision Packages.

2. On Decision Packages, select the decision package that contains the data to copy by specifying the source scenario and version and clicking Go.

3. In To Scenario and To Version, select the target scenario and version members to which to copy decision package data.

4. Select the decision packages to copy.

5. Select Period Mapping. By default, Years is populated with the years defined for the target decision package's scenario and version.

6. For each Target Year, select a corresponding Source Year. The budget amounts in the target year are replaced by those from the source year.

7. Select Enabled for each year to which to copy data.

8. From Copy Option, specify how to update the target with the decision package you are copying from the source:

o Replace--Overwrite existing decision packages in the target scenario and version with those that you are copying.

9. Perform a task:

o For Administrators copying the baseline budget: Select Replace and Add to copy justification criteria and attributes.

o For Planners: To choose whether or not to copy more recent attributes and justification criteria, select Add and Synchronize.

10. From Merge to one Decision Packages, select Yes to copy all budget requests in selected decision packages to a single target decision package that you specify. Select No to copy only the selected decision packages to the target scenario and version.

Note: If you select Yes, ensure that the sharing defined for the owning entity in the target decision package grants the appropriate users and entities the access required to enter and modify data.

11. From Budget Type, indicate if the decision packages that you are copying contain recurring or non- recurring budgets.

12. Specify if you want to copy attributes, and supporting information, such as attachments and justification criteria.

13. Click Copy Data, and then open the Job Console to review any warnings or errors.

14. For HCP budgeting: Select Budget Preparation, and then Calculate compensation budgets to process and view updated data.

Applying this Patch

To apply this patch:

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

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

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

NOTE: <PATCH FILE NAME>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

4. To apply the patch, enter the following command on one line:

Windows:

opatch.bat apply <EPM_ORACLE_HOME>/OPatch/21512189 -oh <EPM_ORACLE_HOME>

-jdk <MIDDLEWARE_HOME>/jdk160_35

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

UNIX/Linux:

./opatch apply <EPM_ORACLE_HOME>/OPatch/21512189 -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

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

5. Delete the 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>/tmp.

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

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

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

Post Installation Steps

Instructions for upgrading the Public sector Planning and Budgeting enabled applications created in 11.1.2.3.500 before applying this patch:

Review the enhancements made in release 11.1.2.3.501 (patch 19142919) and follow the Post Installation Steps Instructions for upgrading the Public sector Planning and Budgeting enabled applications created before applying this patch.

These steps are not required for applications created after applying release 11.1.2.3.501 (patch 19142919), or release 11.1.2.3.502 (patch 20358563) or if existing applications were already upgraded to 11.1.2.3.501 (patch 19142919) or 11.1.2.3.502 (patch 20358563) following steps mentioned in patch 19142919 readme, or patch 20358563 readme.

Steps if Planning and Financial Reporting are on Different Servers

1. If you have Financial Reporting (FR) installed on a different server from the one where Hyperion Planning is installed, perform these steps on that server:

- Stop all of the EPM services running on the server.

- Back up HspJS.jar from

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

2. Unzip the 21512189 patch zip file and copy HspJS.jar from 21512189\files\common\ADM\Planning\11.1.2.0\lib to:

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

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

3. Restart all the EPM services on the server that were previously stopped.

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 of HspJSClient.jar and HspEpmaAds.jar file from <EPM_ORACLE_HOME>\common\planning\11.1.2.0\lib.

3. Unzip the 21512189 patch zip file and copy HspJSClient.jar and HspEpmaAds.jar from 21512189\files\common\planning\11.1.2.0\lib, and paste it in: <EPM_ORACLE_HOME>\common\planning\11.1.2.0\lib.

4. Restart all the EPM services on that server that were previously stopped.

Additional Steps for defect 21688739 and 21688868

1. On the server running Foundation services, stop all EPM services.

2. Take a backup of your Foundation services database.

3. Run the queries in file named CSSSeededRoles_db2.sql or CSSSeededRoles_mssql.sql or CSSSeededRoles_oracle.sql for db2, mssql and oracle respectively, located under <EPM_ORACLE_HOME>\products\Planning\config\sql against Foundation services database and commit the changes.

4. Restart all services stopped in step1.

5. Also restart EPM services on other servers. For example: Planning, Essbase etc.

6. Login into Shared services and check that a new role "Copy Decision Package" got created. Assign this role to appropriate Users/Groups to test the new role.

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. To roll back the patch, enter the following command on one line:

Windows:

opatch.bat rollback -id 21512189 -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35

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

UNIX/Linux:

./opatch rollback -id 21512189 -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME> /jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

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

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

5. Revert the jar files which were backed up as part of sections “Steps if Planning and Financial Reporting are on Different Servers" and "Steps if Other Enterprise Performance Management Products Reside on a Server Other than the Planning Server".

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

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

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:

Windows:

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

UNIX/Linux:

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

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