Caution: You are urged to carefully read and understand the following requirements. Failure to comply may result in applying a patch that can cause your application to malfunction, including interruption of service and/or loss of data. Before installing or applying this patch:

Verify that your system configuration (product version, patch level, and platform) exactly matches what is specified in the Readme.

Patch Type

This Patch Set Update replaces files in the existing installation and is a cumulative patch, includes patches 11.1.2.1.101, 11.1.2.1.102. The complete product EAR is shipped.

Supported Paths to this Patch

You can apply this patch to the following releases:

· 11.1.2.1.000

· 11.1.2.1.101

· 11.1.2.1.102

Prerequisites

Required Microsoft Patch

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 applies to all supported platforms.

Supported Languages

This patch is supported for English only.

Top of Document

New Features

Financial Close Management Validation Tool

Financial Close Management Validation Tool scans the system configuration settings needed for successful functioning of Financial Close Management.

It is recommended to run Financial Close Management Validation Tool once you complete the installation and configuration steps to test that the components for Financial Close Management are correctly deployed and configured.

>To use Financial Close Management Validation Tool:

From a Web browser, open the following URL:

<FCMHOST>:<FCMPORT>/fcc/faces/oracle/apps/epm/fcc/ui/page/FCCValidation.jspx

where FCMHOST is the machine where Financial Close Management is configured and FCMPORT is port 8700.

Note: You can find this information from WebLogic Administration Console. To view this information, log on to the Administration Console and navigate to Environment, and then Servers.

Log in to the Financial Close Management Validation Tool with a user from the external provider. If there are issues with the external provider configuration, log on with any seeded user (seeded both on WebLogic Server and Hyperion Shared Services native directory) and run the tool to identify issues with the external provider configuration.

3. Review the status for each of the following:

Validation Item	Results
Admin Server	Host Port Status (running/shutdown)
Foundation Services Server	Host Port Status Data Sources targeted
Financial Close Managed Server	Host Port Status Data Sources targeted
SOA Server	Host Port Status Data Sources targeted SOA-infra status
FCM Web Application	Version Status DB Type
Foreign JNDI	EDN JMS (in case of sql server) SOA JMS
Authentication Providers	EPM Identity Asserter Provider information. Lib OVD configuration status.
External Idstores	Lists the external Identity store configuration. The tool only lists the values used for the configuration. It is the responsibility of the customer to make sure that the entered values are correct.
SOA composites	List of SOA composites with their status.
OWSM Keystore	The keystore referenced in jps-config.xml and if it actually exists.

4. Look for failed tests, diagnose, and fix problems.

5. Run Oracle Hyperion Financial Close Management Validation Tool again until all tests pass.

Generating a Test Schedule

The second half of the Financial Close Management Validation Tool has a utility that generates a test Main Orchestration Process, deploys it to a SOA server, and starts a test task. A table displays the status for each task, the possible cause of any errors, and the steps to fix it.

Note: Verify that the user logged into the Financial Close Management Validation Tool is also a user in Shared Services.

Note: The Validate Test Schedule button to run this test is enabled only if all the required configuration from the above table is in place and marked with a tick mark instead of an X.

6. Review the status of the following tasks:

· SOA Composite Deployment

· Business Event

· Composite Instance

· FCM Basic Task

· Human Workflow

7. In case of any errors, the test SOA Composite and the test FCCTaskExecutionComposite instance are not deleted and you can see more details of the error from the Enterprise Manager console. If all the validation items are successful, then the test composite and instance are deleted.

Event Monitoring Integration

This patch introduces a new integration execution type called Event Monitoring. The Event Monitoring type allows Financial Close Management to passively monitor processes within other applications which utilize business event notifications. Financial Close Management can leverage the receipt of the event notifications to drive further action within the close process. Within Financial Close Management, the user would create a task which contains the specific notification details. They would enter the estimated timeframe in which they expect the notification to be received. Once the task is open, Financial Close Management will wait for the specific event notification. After the notification is received, the task will be updated with the notification details and marked complete. With the incorporation of event monitors, Financial Close Management can incorporate activities that are being initiated within other systems and leverage those activities within the larger closing process.

For example, Company A wants to monitor the closing of the US general ledger within their ERP system. Their ERP system has been configured to send out a business event notification when their general ledgers are closed. Within their closing schedule, the schedule owner has set up an event monitor task to wait for the event notification for the closing of the US general ledger. When the US GL is closed within the ERP, an event notification is issued. Financial Close Management identifies the notification for the US general ledger and marks the schedule task complete.

For additional details on setting up Integration types, refer to the Oracle Hyperion Financial Close Management Administrators Guide.

For additional details on integrating Financial Close Management with third-party business event notifications, refer to the Oracle Hyperion Financial Close Management Release 11.1.2.1 Integration Guide, Oracle Hyperion Financial Close Management - JMS Event Monitoring Configuration.

Event Monitoring Prerequisites

After applying Release 11.1.2.1.103, perform these steps:

1. Manually run the WebLogic Jython script FCM_JMSConfig_WLS_Script.py to set up JMS Queue and JMS Connection Factory.

2. Manually run the WebLogic deploy command to deploy FCM_DBAdapter_Plan.xml to set up DbAdapter.

For instructions, see the Oracle Hyperion Financial Close Management - JMS Event Monitoring Configuration.

Updatable Attributes

This release includes a new custom attribute type that allows the assignee or approver to update the attribute value.

Date and Time Attribute Type

Date and Time is a new attribute type that you can use to update date and time values. This attribute type provides a date and time icon on the attribute. When you click on the icon, a popup dialog opens and by default, displays the end-user’s current date and time (localized to their time zone). You can then set the attribute to any date and time. If the attribute has already been set, the dialog displays the specified value.

Updatable by User Attribute Option

When the attribute is assigned to a task or task type, a new option is presented: Updatable by User. When you select this checkbox, the system displays a list of options that determine which task roles can update the attribute value and if the attribute value is required. The attribute is inherited similarly to other attribute types. If set for a task type, the task inherits the attribute.

Updatable by User Role

When the task attribute is applied to a task or task type, the administrator can determine which user role can update the attribute value. The administrator can select the attribute to be set by the Assignee, Approver, or both. By default the Assignee option is selected. You must select at least one role, or an error occurs.

If the task does not have an approver defined on the task, the approver dialog box does not display.

If the Assignee option is not selected, the attribute will display as Read-only to the assignee within the task action dialog. If the Approver option is not selected, the attribute will display as Read-only to the approver within the task action dialog.

The task owner should see the attribute in the same state as the assignee or approver would, given the task’s current state. For example, if the task is with the approver and the attribute is updatable by only the assignee, the task owner would also see the attribute as Read-only.

If the task is restarted, the attribute values revert to the original attribute values when the task opened. If the attribute did not have any value when the task was opened, any attribute value is cleared. If the attribute value was originally set to Low and the Assignee or Approver changed it to High, upon restart, the attribute value would revert to Low.

Updates to the task action values are recorded in the Task History tab and viewable to end users. If the task owner updates the values, it is recorded in the Task History under their ID.

Attribute Required Values

The administrator may set this attribute to require a value to be set. If required and updatable by the assignee, the assignee must enter a value prior to submitting the task to the approver. If required and updatable by the approver, the attribute value must be set prior to the approver approving the task. If there are multiple approvers, the first approver must have the attribute value set. Subsequent approvers can update the attribute. The Assignee can submit the task with the attribute value blank.

Example 1 – Reporting Task Execution Details

For example, you could design all of your tasks to include two attributes: Start Time and End Time. As an administrator, for the Start Time attribute, you could configure the tasks so that only the Assignee can enter this attribute value and it is required data. For the End Time attribute, you configure the tasks so that only the Approver can enter this attribute value and it is also required data.

The closing schedule starts and Task A has been assigned to Assignee A. She opens the task and performs all required aspects of the task. She tries to submit the task, but the submit button is not enabled. She remembers that she must enter the time and date that she began to work on this task within the Start Time attribute. She clicks on the icon next to the attribute value and a popup dialog displays the current date and time. She changes it to show her task Start date and time. She can then submit the task for approval. She notes that the End Time attribute is not set and is Read-only.

The Approver receives a notification that Task A is awaiting her approval. She opens the task and reviews all of the information. She notes the Start Time entered by the Assignee. The End Time attribute is enabled and she enters the current date and time by simply clicking on the icon and then clicking OK. She submits the task for further review to Approver B.

Approver B receives a notification that Task A is awaiting her approval. She reviews the task details including the start and end times entered by the Assignee and Approver A. She approves the task.

Example 2 – Updating Attribute Values

In another example, a Close User has been assigned an analysis task within her company’s close. One of the attributes set on all the tasks is an attribute used to grade the risk rating of the task. By default, the majority of the tasks are set to a Neutral risk rating. As the assignee performs the task, she determines that this analysis task has uncovered a potentially high risk item and should be escalated to High. She resets the attribute to High from the custom list on the attribute and when complete, submits the task for approval.

The Approver reviews the submitted task details and notes in the comment section that while there is a potential risk, it is very unlikely to occur. She resets the attribute value to Neutral and approves the task.

Defects Fixed in this Patch

Defect Number	Defect Fixed
• 13603924	When you run script createPSU2changes.sql to update database schema, its errors: ORA-04068: existing state of packages has been discarded.
• 12937872	The submit option is available in the task actions for a parent task.
• 13603936	You can now use Financial Close Management Validation Tool to locate installation and configuration issues.

Top of Document

Defects Fixed in Patch 11.1.2.1.102

Defect Number	Defect Fixed
• 12765588	When you remap a close day, the results in a prior close day’s tasks are incorrectly assigned.
• 12760050	When you close a child task with a forced close process, a parent task displays a warning and there is no way to clear the status.
• 12758750	When you create a schedule from a template with multiple external references, the Predecessor Task table incorrectly displays “None Selected” in mapping results.
• 12758719	When you sort the template table by Assigned Schedule, the task dialog window displays the wrong mappings.
• 12758713	When a template references multiple templates, there are mismappings in the schedule.
• 12758707	The import process should generate an error when a task is a parent of itself.
• 12748786	A NullPointerException error occurs when SOA tries to update a task status to Open with assignee.
• 11805162	Smart View: The Financial Management and Financial Reporting Web integrations will fail with an error when launched from within Smart View.
• 11771874, 10236022, 11061158	Microsoft SQL Server Database: Under high concurrent usage where multiple users are executing the exact same action, the Microsoft SQL database may report deadlocks upon post actions. This may result in inconsistent rendering of the user interface or tasks failing to execute. These failures will result in the following issue being reported within the Financial Close log –“JBO-26041: Failed to post data to database during "Update"…”, and deadlocks reported in the MS SQL database log.
• 11769873	When you connect to Smart View from Microsoft Outlook, you receive an error message, “You are connecting to an older version of the server”.
• 11699188	Localization: When you create a task using the HFM Task Type, if the application name contains Japanese characters, the task parameters do not display correctly and there may be issues starting the task.
• 11695020	Financial Management Integration: If Financial Close Management logging is set to a Trace level or lower, selecting the parameters for Hyperion Financial Management integrations may generate this error: “com.ctc.wstx.exc.WstxIOException: Exceeding stated content length of 213”. If this occurs, raising the Financial Close Management logging level above Trace will clear the issue. [This is a duplicate bug of 11787915]
• 11668794, 11667534	Smart View: After you perform an action in Smart View, for example, submitting or approving a task, you must close the dialog box to refresh the screen.
• 11656837	Application Lifecycle Management: Financial Close Management artifact names with * ; ‘ characters fail to migrate.
• 11656451	Application Lifecycle Management: The Lifecycle Management right-click migration option does not work for Financial Close Management when you try to import a single artifact.
• 11655933	Application Lifecycle Management: Users who are not assigned the Financial Close Management administrator role can view a listing of Financial Close Management artifacts in Lifecycle Management.
• 11074517	Life Cycle Management: If you use Mozilla Firefox as the browser, you must select a browser language country code and a language code. If you do not select a language code, you cannot use Lifecycle Management.
• 10419989	Importing Files with Update Option: The task assignee can be reassigned to another user for an Open task if the update is made through a file load.
• 10419623	On the Dashboard, in the Schedule Tasks and My Worklist controls, any user-applied sorting within the columns is not persisted between user sessions. You need to reapply any column sorting in the controls manually. Also, any user-defined column sorting within the Tasklist and Gantt views is lost on the view refresh when you open, then close the task display.
• 10411306	Templates: A power user who is assigned as a Viewer on a template cannot create a schedule from the template.
• 10403568	Life Cycle Management: The Replace All load option is currently not supported for Financial Close artifacts. You can migrate artifacts using the Replace option, then manually delete any unwanted artifacts.
• 10304302	Application Lifecycle Management: If you use Lifecycle Management to import templates that have embedded templates, the embedded templates must be imported first.
• 10199259	Task Action: Task instructions may not display in Task Actions for system-automated tasks if the Run As ID was not set within the task definition in the source template.

Top of Document

Defects Fixed in Patch 11.1.2.1.101

Defect Number	Defect Fixed
• 10222095	Add the ability to start an End User task early.
• 10141890	The task list freezes after it is collapsed when child tasks are added or removed.
• 9744047	The task starts even when its predecessor schedule is still pending.
• 9725713	Import and Export function does not support newlines.
• 9541416	Task execution does not account for daylight saving time.
• 8913045	Scrolling the Gantt chart with the left panel hidden results in misaligned rows.
• 10178210	Dashboard printing does not print all rows in the Schedule Task control.
• 10141160	When you reimport a CVS file, an error occurs that a duplicate task ID was found.
• 10141109	The system displays incorrect predecessor links when you deploy a template.
• 10059781	A NoRowAvailable exception error may occur when you filter in a Gantt view.
• 10038117	Users cannot add a comment to an alert without submitting or approving the alert.
• 10038108	In alert comments, the text does not word wrap in the Comments section.
• 10008963	Some dialog tabs are blank if you use Internet Explorer 8 with the Compatibility View off.
• 9829038	Predecessor task links assigned may not display correctly in a task search.
• 9816116	In MyWorklist under Responsibility, the list does not update properly.
• 9782177	When you copy and paste a task, the system does not paste the second approver.
• 9757599	The dependency field is missing in the Integration Type dialog.
• 9725645	Empty columns at the end of an import file may cause unexpected errors.
• 9715374	The system should validate the task name size on task import.
• 9703487	A NoRowAvailable exception error may occur when you remove a filter in the Gantt view.
• 9672862	When you right-click on the Gantt bar, the right-click menus do not work.
• 9581164	Allow more space to view instructions and description in Task Actions.
• 9506412	Issues may occur with rounding answers for number type questions.
• 9491081	The totals in the Schedule Tasks portlet may not display correctly.
• 9450706	Problems may occur with the right-mouse menu for the Gantt task bar.
• 9412355	The workflow maintains the original assignments when the owner submits or approves a task.
• 9342567	Performance issues may occur when you use very large templates and schedules.
• 9271136	If you expand and collapse the options in the Gantt view multiple times, they may not display correctly.
• 10219802	The secondary approver has the Reject option before the task is submitted for their approval.
• 10141160	The browser retains the characteristics from the last session unless it is closed and reopened.
• 9744104	The Needs Attention icon needs hovertext and a short description.
• 9735107	A better error message is needed when an invalid ID tries to access an application.
• 9734746	In the View mode, the text needs to be displayed more distinctly from the background.
• 9728881	The Task Actions menu needs a delete comment option.
• 9660315	The system does not retain the history for changing a task from active to inactive.
• 9537788	When you reassign an approver from the Actions menu, it is not recorded in the Task Actions history.
• 9527334	The alert email should contain the task and schedule information.
• 9476890	In Task Types lists, the icon for automated tasks should be different than the icon for an End User task.
• 10215922	When you reject a task, the system inadvertently clears the Workflow action table for all tasks.
• 10141153	When you add predecessors, the system creates a blank row in the database.
• 8767816	There should be a method to remove the worklist application line in email notifications.
• 10329831	The Dashboard may not display correctly after you maximize, minimize, restore, or drag or drop portlets or icons.

Top of Document

Known Issues in this Patch

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

Defect Number	Known Issues
• 12758702	Executing multiple schedules at the same time causes some tasks not to start.

Alerts

Defect Number	Known Issues
• 10350810	Reassigning an Alert assignee to the same user as the approver prevents the Alert from progressing within the workflow. Delete the alert and create a new Alert.

Application Access

Defect Number	Known Issues
• 10422907, 10079796	Under certain conditions, logging into the application with one User ID, then logging out and logging back in under another User ID within the same browser session may result in the prior user ID’s session being displayed.
• 9736096	You must have the WebLogic Admin server running at all times when you use Financial Close Management.

Application Lifecycle Management

Defect Number	Known Issues
• 10428514	Lifecycle Management displays square boxes for some double-byte international characters.
• 11071949	Financial Close Management artifacts cannot be migrated using the Lifecycle Management (command-line) Utility.
• 10414864, 10414923	If you use a double-byte or high-ASCII language such as Japanese, Korean, Chinese (Traditional and Taiwan), Russian, or Turkish, LifeCycle Management does not work properly.

Dashboard

Defect Number	Known Issues
• 10363865	Upcoming or Closed Alerts do not display in the My Worklist control.
• 9761181	An error message may be displayed if you attempt to drill into the Alerts bar in the Status Chart control after printing the control.
• 10419307	The Status Overview control displays an error if you no longer have any task assignments in any Open or Closed schedules.

Finance Calendar Views

Defect Number	Known Issues
• 10367702 10367486	Within the Gantt Chart and Calendar views, viewing a schedule/template with a very large number of tasks may cause the view to cycle a very long time. It is recommended to filter the view down to a smaller number of tasks when reviewing the schedule/template in these views.
• 10374397	If you have a large amount of tasks to be displayed in a Gantt view, you may experience performance issues. If a filter is applied, or tasks are hidden as children of parents, the performance may be improved.

Internet Explorer 7/8

Defect Number	Known Issues
• 9356443	Under certain heavy load conditions, a user's session may freeze when using Internet Explorer. Users can clear this issue by logging out and back into the application.

Schedules

Defect Number	Known Issues
• 10359859	Removing all children of an open parent task prevents the parent task from completing.

Smart View

Defect Number	Known Issues
• 11056384	When using Financial Close Management with Smart View, it is recommended that most users have their accounts configured to use shared connections, as only advanced users and technical support personnel should use private connections.
• 10383364	When using Financial Close Management with Smart View, you should not use Outlook view customization.
• 11687672	Financial Close Management tasks open in the browser language instead of the language set in Smart View.
• 11739147	When using Financial Close Management with Smart View, you can only authorize tasks with your own ID. If you try to enter different user credentials, errors will occur. If this occurs, log on to the application through the Web and enter the credentials there.

Task Action

Defect Number	Known Issues
• 9744611	If you have Financial Close Management and Task Actions from email open in the same browser session, when you close one of them, the other session will be closed.

Top of Document

Applying this Patch

The section includes important information about applying this patch for EPM System Installer.

CAUTION: Because of the extensive database changes that result from applying this patch, rolling back the patch is not supported. Before you apply the patch, be sure to perform an entire system backup.

NOTE: For Distributed environment, apply the patch in all machines by following below steps 3 to 5.

>To apply this patch:

1. Confirm the environment is running properly.

Windows:
Go to Start, then Programs, then EPM System, then Foundation Services, then Epmsystem1, and then Epm system diagnostic.

Linux:
Run this command:
<MIDDLEWARE_HOME>/user_projects/epmsystem1/bin/validate.sh).

2. Stop FinancialClose Managed Server, then stop the SOA Managed Server, and the HSS Server.

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

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

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

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

Windows:
opatch.bat apply <EPM_ORACLE_HOME>\OPatch\13603945 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>\jdk160_21

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

UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/13603945 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

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

Note: If you are already in Patch Set Update (PSU) 11.1.2.1.102, you do not need to perform step 6 (Database changes).

Do the following post-installation steps:

Oracle: DB Changes and Load Template files:

a. Login as SYSDBA to Oracle Database.

b. Grant Create Directory to Financial Close Management Schema User using the below command

GRANT CREATE ANY DIRECTORY TO <Financial Close Management Schema User>;

c. Create an EventMonitoring directory in temp location on the hard disk of the database server. (Windows: C:\temp\EventMonitoring; Linux: /tmp/EventMonitoring).

d. Navigate to the following folders on the EPM instance and copy all individual files in these folders to the newly created EventMonitoring folder on the database server:

<EPM_ORACLE_HOME>\products\FinancialClose\database\templates\EventMonitoring
<EPM_ORACLE_HOME>\products\FinancialClose\database\templates\EventMonitoring\xsd
<EPM_ORACLE_HOME>\products\FinancialClose\database\templates\EventMonitoring\xsl
<EPM_ORACLE_HOME>\products\FinancialClose\database\templates\EventMonitoring\SCA-INF
<EPM_ORACLE_HOME>\products\FinancialClose\database\templates\EventMonitoring\testsuites

e. Open SQL Developer and connect to the Financial Close Management database.

f. Copy the script <EPM_ORACLE_HOME>\products\FinancialClose\database\Oracle\createPSU3changes.sql to SQL WorkSheet and run the script.

g. When the script prompts for the TemplateFilesPath value, enter the path of the Event Monitoring directory that you just created. This will perform the database changes and load all the required Template files for Event Monitoring into the Financial Close Management database.

MS SQL Server: DB Changes and Load Template files:

a. Create a C:\temp\EventMonitoring directory on the database server.

b. Copy the entire folder contents from the EPM instance: <EPM_ORACLE_HOME>\products\FinancialClose\database\templates\EventMonitoring
to the newly created EventMonitoring folder on the database server.

c. Open SQL Server Management Studio and connect to the Financial Close Management database.

d. Copy the script <EPM_ORACLE_HOME>\products\FinancialClose\database\Oracle\createPSU3changes.sql
to SQL WorkSheet and run the script.

e. The script performs the database changes and loads the required Template files for Event Monitoring into the Financial Close Management database.

7. Restart all servers in the proper order (for example, Admin Server, Foundation Server, Financial Close Managed Server, and SOA Server). See the Oracle EPM System Installation and Configuration Guide for more information on the startup order.

8. Run the EPM Configurator (Select Start, then Programs, then Oracle EPM System, Foundation Services, then epmsystem1,and then EPM System Configurator), and perform only Deploy to SOA.

9. To configure Event Monitoring, refer to the Event Monitoring Prerequisites section in the New Features section of this Readme, and also see the Oracle Hyperion Financial Close Management - JMS Event Monitoring Configuration.

10. After you apply the patch, verify that the environment is running properly:

Windows:

Go to Start, then Programs, then EPM System, then Foundation Services, then Epmsystem1, and then EPM system diagnostic.

Linux:

Run this command: <MIDDLEWARE_HOME>/user_projects/epmsystem1/bin/validate.sh

11. All tests should display PASSED.

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

Top of Document

Troubleshooting

New Features Not Displaying in Financial Close Management after Applying this Patch

In some cases, the user interface may not reflect the new code applied by this patch. To confirm this is not an issue, the patch should have created a new radio button with the name Event Monitoring in the Create New or Edit Integration Type dialog in Financial Close Management. Also, if you have not previously applied the Financial Close Management Release11.1.2.1.101 or 11.1.2.102, this patch should have created an Updatable by column on the Attributes tab of the New Task dialog.

If the new features do not display, follow these steps to force the user interface to display the new code by forcing WebLogic to check for JSP pages.

1. Open the WebLogic Administration Console (http://<SERVER>:<PORT>/console).

2. Go to Home > Deployments.

3. Expand Financial Close under deployments, select fcc, go to the Configuration tab.

4. Update JSP Page Check (in seconds) to a non-negative number (for example, 1).

5. Save to update the deployment plan.

6. After saving, set the JSP Page Check (in seconds) to the original value (for example, -1).

Note: If you do not reset the value to -1, you may experience WebLogic performance issues.

7. Save again.

Top of Document

Troubleshooting FAQs

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_21

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

UNIX/Linux:

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

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

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.

Top of Document