Table of Contents:
This document includes important, late-breaking information about this release of Oracle Hyperion Profitability and Cost Management. Review this Readme thoroughly before installing Profitability and Cost Management.
For information about the new or extended functionality in this release, see the Oracle Hyperion Profitability and Cost Management New Features.
For new features relating to installation, architecture, and deployment changes in this release, see "New Features" in the Oracle Enterprise Performance Management System Installation and Configuration Readme.
Late-breaking information about installation of Oracle Enterprise Performance Management System products is provided in the Oracle Enterprise Performance Management System Installation and Configuration Readme. Review this information thoroughly before installing EPM System products.
Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN):
Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab of the Oracle Fusion Middleware Supported System Configurations page on OTN:
You can upgrade to EPM System 126.96.36.199 from the following releases.
For instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide and “Upgrading EPM System Products”.
Table 1. Supported Paths to this Release
|Release Upgrade Path From||To|
If moving from Release 188.8.131.52.x or 184.108.40.206.x to Release 220.127.116.11, use the "Apply Maintenance Release" option in the EPM System Installer, instead of following the documented upgrade procedures.
For Financial Close Management, applying the maintenance release is supported only from Release 18.104.22.168.
An environment that includes multiple releases, which can include an environment with one instance of Oracle Hyperion Shared Services or an environment with two instances of Shared Services
See "Upgrading from an Environment with Multiple Releases" in the "Upgrading EPM System Products" chapter in the Oracle Enterprise Performance Management System Installation and Configuration Guide.
If you are starting from Release 22.214.171.124+, 9.3.0.x, 9.3.1.x (except for Oracle Essbase 126.96.36.199.1, 188.8.131.52, 184.108.40.206, and 220.127.116.11), or 11.1.1.x, upgrade to Release 18.104.22.168 as your interim release.
If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release.
Security Synchronization between Essbase and Oracle Hyperion Shared Services was removed in Essbase 9.3, starting with Release 22.214.171.124.1. Consequently, if you use Essbase Release 126.96.36.199.1, 188.8.131.52, 184.108.40.206, or 220.127.116.11, upgrade all products to Release 9.3.3, not 18.104.22.168.
If you are coming from Release 22.214.171.124 or 126.96.36.199, use the Defects Fixed Finder tool to review the list of defects fixed between those releases and Release 188.8.131.52. This tool is available here: https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1
13577161 -- When redeploying a Profitability and Cost Management application (BSO cube) to Essbase, if the Update database option is selected as well as Archive Data and Reload after deploy, Essbase fails to load data back into the BSO cube.
13532628 -- When using MS SQL, if you update staging tables to use an Object Calculation driver, the import task fails; and error messages are not displayed in hpcm log.
12981414 -- It is not possible to use Oracle Hyperion Enterprise Performance Management System Lifecycle Management export with Profitability and Cost Management when in Compact deployment mode.
12931223 -- Error messages are generated when running model validations.
12709730, 12693108 -- Errors for large IDs received on multiple applications.
12704623 -- Deployment of an application takes a long time to complete.
12623571, 12623563 -- When performing trace allocations, the CPU was at 100% usage.
12577391 -- Import of assignments is very slow.
12557684 -- Trace allocations cannot be performed for a large core application although it is working for smaller applications.
12351827-- A Copy POV operation takes a long time to be completed.
12351800-- Staging load is very slow.
12316225 -- If the "Allow Intrastage Assignments" option is disabled on all stages, a POV Copy operation will fail.
The following are the noteworthy known issues in this release:
13838989 -- In both Standard and Detailed Profitability, if a POV with a status of either “Archived” or “Published” is selected, the new POV seems to be correctly applied. If you then select a valid POV with a “Draft” status and create or edit a driver association using the double-click and <...> option, or select it from drop-down list, the driver rule cannot be created or modified, and the changes are not saved.
This defect does not apply if the Add icon is selected to create or edit the driver rule.
13832599 -- For Detailed Profitability, if a source stage table has a joined lookup table, the Stage Balancing report is not created because both the source table and its associated lookup table have the same system column, and the column is registered as a measure column on either the source table or its lookup.
13810867-- For Detailed Profitability only, if Measures contain different types of data (for example, numerical headcount versus monetary values), the Stage Balancing report may provide incorrect results because the different value types cannot be properly distinguished. The accuracy of the results are determined as outlined below:
For Vertical Source Tables, the Stage Balance view results are correct if you put all your statistical measures on a joined lookup table; however if you have statistical measures directly on your source table, the results are incorrect.
For Horizontal Source Tables, the Stage Balance view results are incorrect if you have ANY statistical measures, either on a joined lookup table or directly on the source table itself.
13803615 -- After creating and successfully deploying a Standard Profitability application to Profitability and Cost Management, if you go to the Data Entry screen and redeploy the calculation cube using the “Replace”' option, the redeployment fails and an error is generated in the hpcm.log.
To work around this issue, unload the Essbase application using any of the Essbase clients.
13800625 -- For Detailed Profitability, additional Model Validations are required to check for missing database privileges.
After installation, the following privileges should be assigned:
For Oracle database, Detailed Profitability requires that these system privileges (or roles that include them) be granted to the Product Schema:
CREATE ANY SYNONYM
DROP ANY SYNONYM
For SQL Server, Detailed Profitability requires that these system privileges (or roles that include them) be granted to the Product Schema:
ALTER or CONTROL
In Oracle, users and schemas are the same thing. In SQL Server, they are separate. For SQL Server-based installations, Detailed Profitability requires you to create a user with the same name as the Model Data Schema, and that user must have privileges on all the objects in the model data schema.
13772443 -- If you try to delete or edit an assignment that had the same dimension member set as Source One, an error is generated.
13713095 -- For Detailed Profitability, when you create a new assignment rule, if you select the Same As Source check box, only the Same As Source members are listed.
13702673 -- In the Assignment Rules dialog box, when you open a Destination Rule and the focus is on the first dimension, if you select the Same As Source check box, the browser freezes.
13700793 -- On the Stage screen, you cannot change the stage table selection to a new stage table after a calculation has been run.
13768324 -- When using Internet Explorer 10, if you change the Destination pane mode without saving data, no confirmation is displayed, and the Save icon remains enabled.
13742313 -- When using Internet Explorer 9 with Standard Profitability, if you select Tracing Allocations, no links are displayed.
13723174 -- For Detailed Profitability applications, if a source stage table has a vertical format, the Stage Balancing Report does not contain the source measures from a joined Lookup table.
13717938 -- For both Standard and Detailed Profitability, when importing using staging tables, if an extra dimension is added, the task seems to finish successfully; however, no errors are generated for driver exceptions and assignment rule selections. The “Exceptions” column shows a status of “OK_IMPORTED”; although no data is actually imported into the model.
13682525 -- When completing Model Data Registration for Detailed Profitability applications, after editing the tables or columns, if you go directly to Finish without making any selections on the Mapping Measures step, a warning message is displayed. For example, the message may read “Selected measure does not exist: 'Quantity'. Select another measure.”
To work around this issue, you must go back and reselect all measures.
13644803 -- In either Standard or Detailed Profitability applications, if you select an application (select Navigate, then Applications, then Profitability, and then the application), the first application is correctly selected. However, if you select a second application, an error message is generated.
13613585 -- If the Override Total Driver Value is used in a Ratio-Based driver, and its value is greater than the calculated Total Driver Value, the Idle_Cost column is not calculated. The Stage Balancing report displays an empty Idle_Cost column, and the corresponding idle values are shown in the Unassigned column of the report.
13591567 -- If two instances of EPM System share a database and a model schema, both applications use the same names for temporary objects. Multiple EPM System instances cannot share the same model data schema.
To work around this issue, you can create another model data schema.
13537329 -- For MS SQL Server only, if horizontal source tables in Detailed Profitability contain incompatible datatypes (for example, a precision value of numeric 10,4 and numeric 10,2), validation during creation of the Stage Balance view does not generate a warning in the hpcm.log.
13328441 -- When calculating Standard Profitability models, if you select the check box “Transfer data after calculation” on the Allocation tab of the Manage Calculation screen, both the Cost and Revenue data will be transferred after calculation. This information will be added to the documentation for the next release.
13491128 -- After successfully calculating models that have checked options for Level-0 contribution and stage balancing, when you run Clear Calculation, the Stage Balancing and Source Destination Level-0 tables, and the sum results for all tables, are not cleared.
12704464 -- If errors are generated for ID column values that display negative values because of overflow in any of the Profitability and Cost Management tables, you must run a specific script to correct the situation.
See Running the defragment_ids.sql Script in the Tips and Troubleshooting section of this document for instructions on running the SQL script.
This workaround is applicable only for an installation which has Profitability and Cost Management configured with an Oracle database.
11742793 -- In instances where the name of a new Profitability and Cost Management application contains foreign characters, which may result in longer names, you may not be able deploy the application in EPM Architect.
13324110 -- Numbers between 0 and 1 are handled incorrectly in Data and Custom Filters. For example the number '0.002' is treated as '.002', so the corresponding query does not return the necessary records.
12562262 -- For a Detailed Profitability application, if an application containing invalid artifacts is imported using Oracle Hyperion Enterprise Performance Management System Lifecycle Management, there is no validation of the artifacts. The import seems to be successful, and the invalid artifacts are imported.
12560535 -- When performing Model Data Registration for a Detailed Profitability application, if you add new tables in the wizard, and then click Back to change a selection, the original selections cannot be modified. This same behavior also occurs in the Table type combo-box and Column type combo-boxes in the Table Registration wizard and the External Table, Table type combo-boxes in the Create New Join wizard.
To work around this issue, exit the wizard and start again.
10278828 -- If you enter unexpected or restricted words or characters in the Driver Editor, the validation error message is not explicit.
To work around this issue, exit the wizard and start again.
Do not use the following Windows reserved names for Calculation/Reporting Application or Database names: CON, PRN, AUX, CLOCK$, NUL, COM0, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT0, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9
Do not use Essbase reserved words for Calculation or Reporting database names. See Oracle Essbase Database Administrator's Guide.
10008989 -- If the sum of the lengths of the prefix and the dimension name exceeds 80 characters, deployment to Essbase will fail. The concatenation of dimension and prefix names must not exceed 80 characters.
10007895 -- When upgrading from Release 184.108.40.206.x to Release 220.127.116.11, the upgrade may fail if the EPM_ORACLE_INSTANCE variable is not set.
To work around this issue, ensure that the EPM_ORACLE_INSTANCE variable is set before running the upgrade_reregister_ps1.bat (sh) script. For instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.
9562829 -- On the Driver Data tab of the Data Entry screen, when you double-click a non-0-level member that had not been previously selected, a busy indicator is displayed and the selected non-0 level member is not expanded correctly.
To work around this issue, click on the row to select it first, and then double-click to expand the selection.
9289136 -- Occasionally, the first time you create a new import configuration after an installation, when the import configuration is opened, the data source details are missing and the configuration cannot be edited or run.
To work around this issue, restart the services, and then open the import configuration.
8449860 -- If global drivers have been loaded into a model, when you select “Clear All” for all stages after running the calculation scripts, the global driver measures are not deleted. When the stages are cleared, the global data is not cleared because they do not have stage specifications.
8208784 -- For MS SQL Server, when creating the Import Staging Tables configuration, the application does not respond, and the screen is disabled during loading.
To work around this issue, ensure the credentials for both MS SQL Server and the database type are correct, and retry the operation.
7394379 -- When starting a taskflow, the following error message may be displayed: “oracle.classloader.util.AnnotatedNoClassDefFoundError”
To work around this issue, from the Task Areas, select Jobs Status, then Search Process, and stop the current job. Select Jobs Status, then Manage Task Flow to restart the task.
7228966 -- When a Profitability and Cost Management application is deployed to Essbase, the stage dimensions are created in Essbase with the dimension name prefixed with the defined stage prefix. If the resulting dimension name is the same as any existing member name or dimension name in the application, the Essbase cube deployment will fail.
To work around this issue, when creating definitions in the model, ensure that the resulting Essbasedimension names are unique in the resulting outline.
7192173 -- Filtering on Aliases in the user interface is not supported in this release.
When you filter on names in assignment rules, matching is performed on both names and aliases.
7113198 -- If you are using Firefox 2.0 as your browser, the cursor is not displayed in a number of locations on the screen, such as edit fields, name, description, and so on. This issue is fixed by using Firefox 3.0.
6979777 -- It is possible to incorrectly import negative, empty, and duplicated order driver records using the import from the HPM_STG_DRIVER.
6979576 -- The stage order is not correctly updated when using the import from the HPM_STG_STAGE table.
To assist you in creating your custom scripts, a Sample Client and Sample Client Readme are also included with the installation (%EPM_ORACLE_HOME%\products\Profitability\samples\wsclient).
The Sample Client File for Web Services displays the commands that can be used in your custom script for automating Profitability and Cost Management tasks, and identifies data within your Profitability and Cost Management model. The sample client file is intended as a guide only, to assist you in creating your custom scripts.
For information on each operation, and its input and output parameters, see the Oracle Hyperion Profitability and Cost Management Web Service API Reference - Profitability Services.
If errors are generated for ID column values that run into negative values due to overflow in any of the Profitability and Cost Management tables, you must run a specific script to correct the situation. (See Defect `1704464 or 12704452) This is a release-specific script that scans all the tables in the Profitability and Cost Management product schema to defragment any sequence number loss. The file is available at %HYPERION_HOME%\products\Profitability\database\Common\Oracle.
This workaround is applicable only for an installation which has Profitability and Cost Management configured with an Oracle database.
See the following procedures:
To run the defragment_ids.sql script:
Oracle strongly recommends that you back up the database schema in case you need to roll back to the state that existed before the ID value defragmentation.
sqlplus <user_name>/<password>@<SID> @defragment_ids.sql
Wait for the SQL script to finish running before proceeding to the next step. If any errors are logged during execution, use the procedure, Backing Out the defragment_ids.sql Scriptand contact Oracle Support for further assistance.
If any errors are discovered, back out of the changes made by the defragmentation script, as outlined in the procedure, Backing Out the defragment_ids.sql Script and contact Oracle Support for further assistance.
To back out the defragmentation script:
sqlplus <user_name>/<password>@<SID> @drop.sql
Restore the database schema using the backup version created in Step 2 of the procedure, Running the defragment_ids.sql Script.
Navigate through all screens in the Profitability and Cost Management application to validate that your original database schema has been restored. Contact Support if additional assistance is required.
For Standard Profitability only, when entering a search value in a filter, enter the entire string if the filters are UDA-based. Trailing wildcard symbols, such as asterisks (*) and question marks (?) are supported in assignment rule name and alias filters. For example, enter "B*" to filter members having names or aliases beginning with the letter "B". You cannot use "*B" as this means that the filter is beginning with a wildcard, which is not allowed.
For assignment rule filters:
Both the EQUAL and NOT EQUAL operations are currently supported to filter Names, Aliases and Attributes.
Only the EQUAL operation is currently supported for UDAs.
When "Name" is selected as the parameter, matching is performed on both names and aliases.
The ‘Hierarchy Type’ property applies only to Aggregate Storage Databases in Essbase. (The Reporting Cube is generated by Profitability and Cost Management).
If a Dimension Hierarchy Type is set to “Stored” in Oracle Hyperion EPM Architect, all its members must have the consolidation set to “+ (addition)”. The only exception is if the Dimension root member has the “Data Storage (ASO)” set to “LabelOnly,” then generation 2 children of the root member which are not the first child can have the consolidation set to “~ (ignore)”, (for example, “NoMember”). Any dimension members that use a consolidation symbol other than ADDITION and IGNORE in the Stored hierarchy type (for example, - SUBTRACT) will cause error messages while generating the reporting cube.
To be able to use other consolidation type symbols (other than ADDITION and IGNORE) the hierarchy type should be set to “DYNAMIC”.
To set the hierarchy type:
Select Stored for any dimension members that use the following consolidation symbols:
~ IGNORE (only underneath LABEL ONLY members.)
Select Dynamic for any business dimension that needs to use all supported consolidation symbols, or that has a formula.
By default, Profitability and Cost Management uses “Embedded mode” to connect to Essbase. If you are using APS, the APS mode uses many TCP ports while deploying the Essbase cubes. This situation may cause a network error which is displayed in the Profitability and Cost Management log file.
If you receive a network error when using the APS Connection Type, switch the Connection Type to embedded mode, and redeploy the cube.
To set the Connection Type to Embedded mode:
If the cube deployment fails in embedded mode, or you have to use APS mode, you can modify the Windows registry TCPIP parameters - TcpTimedWaitDelay and MaxUserPort - as recommended by the Windows Operating System documentation.
Before making any changes to the Windows Registry, consult the Microsoft Windows Operating System documentation for the correct settings and best practices to avoid any risk of corrupting the registry.
If you are experiencing difficulties using the ‘embedded’ Connection Type mode in Profitability and Cost Management to connect to Oracle Essbase (especially in distributed configurations), you must set the environment variable ESS_ES_HOME as a JVMOption for Oracle Hyperion Profitability and Cost Management to point to any local folder which contains two empty folders called “bin” and “data”.
If APS is installed on the system, set ESS_ES_HOME to the same value as the APS_HOME environment variable. (APS_HOME should have the required folder structure.)
If APS is not installed, set ESS_ES_HOME to any folder which contains empty ‘bin’ and ‘data’ folders.
No changes are required if you are using the ‘APS’ Connection Type mode.
To set the JVMOption for the Embedded Connection Type:
To improve the ability of the Windows operating system to deal with a high rate of network connections:
TcpTimedWaitDelay - Set this to a low value (for example, 30) for the sockets to be released quickly. This DWORD value ranges between 30-300.
MaxUserPort - Set this to a high value (for example, 33000) to increase the total number of sockets that can be connected to the port. This is a DWORD value.
Before modifying these parameters, refer to the Microsoft Windows operating system documentation for more details.
Oracle recommends that only a system administrator who is very familiar with the system should make this change. The system administrator should consider all the effects on the Operating System before making this change.
To improve the ability of the Linux server to deal with a high number of outgoing network connections, increase the local port range:
$ sysctl net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 32768 61000
The available parameters are listed under /proc/sys/. This option is only useful for high bandwidth, busy Linux servers or large scale grid servers.
# echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range
$ sudo sysctl -w net.ipv4.ip_local_port_range="1024 64000"
# increase system IP port limits net.ipv4.ip_local_port_range = 1024 65535
If you are using Lifecycle Management to import large models, the import may take longer to process than the time specified in the default timeout settings on the Oracle WebLogic Server. To work around this issue, you must reset the default timeout settings.
To modify the default timeout for WebLogic Server:
# Timeout: The number of seconds before receives and sends time out. Timeout 3000
The server timeout shown above is a suggested limit. Because timeout settings vary from application server to application server, refer to the timeout settings specific to your application server.
The most recent version of each EPM System product guide is available for downloading or viewing from the EPM System Documentation area of the OTN Web site (http://www.oracle.com/technology/documentation/epm.html). You can also use the EPM System Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html), which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.
Deployment-related documentation is also available from the Oracle Software Delivery Cloud Web site (http://edelivery.oracle.com/EPD/WelcomePage/get_form).
Individual product guides are available for download on the Oracle Technology Network Web site only.
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. EPM System products support accessibility features, which are described in the product's Accessibility Guide. The most up-to-date version of this guide can be found in the Oracle Enterprise Performance Management System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).
In addition, this Readme file is accessible in HTML format.