This document includes important, late-breaking information about this release of Oracle Hyperion Profitability and Cost Management, Fusion Edition. Review this Readme thoroughly before installing Oracle Hyperion Profitability and Cost Management.

Top of Document

New Features

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 Hyperion Enterprise Performance Management System Installation Readme.

Top of Document

Installation Information

Late-breaking information about installation of EPM System products is provided in the Oracle Hyperion Enterprise Performance Management System Installation Readme. Review this information thoroughly before installing EPM System products.

Enterprise Performance Management Architect Required Post-Installation Patch

If you use Profitability and Cost Management with Enterprise Performance Management Architect, after the installation and configuration of Enterprise Performance Management Architect 11.1.2.1.00, you must install Enterprise Performance Management Architect patch 11804477.

Upgrading Essbase Databases for Release 11.1.2.1.00 Applications

After upgrading Profitability and Cost Management to Release 11.1.2.1.00, before you can use your applications, you must also upgrade Essbase to Release 11.1.2.1.00.

For complete instructions on upgrading your Essbase release, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

Changes to Deployment

There have been significant changes to the deployment architecture for this release. A brief summary is provided here but for a complete list, see “New Features” and “General Installation Information” in the Oracle® Hyperion Enterprise Performance Management System Installation and Configuration Readme.

· The EPM System directory structure has changed significantly. The default directories are now Middleware Home and EPM Oracle Home.

· EPM System Installer now installs WebLogic Server (replaces Apache Tomcat as the embedded Java container) and Oracle HTTP Server (replaces Apache Web Server as the embedded Web server).

· The manual deployment process is greatly simplified, using the Fusion Middleware Configuration Wizard (deployed with WebLogic) to manually deploy Web applications.

· The Shared Services relational database is now used as Native Directory (replaces OpenLDAP as the central storage for native EPM System user accounts and provisioning information).

· The new Foundation Services Web application is deployed to one managed server and includes Shared Services and EPM Workspace Web applications.

Top of Document

Supported Platforms

Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Hyperion 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) and listed in the Oracle Business Intelligence product area:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Top of Document

Supported Languages

Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN (listed in the Oracle Business Intelligence product area):

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Top of Document

Supported Paths to this Release

You can upgrade to EPM System Release 11.1.2.1 from the following releases:

Note: For instructions to upgrade, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide, “Upgrading EPM System Products.”

Release Upgrade Path From	To
11.1.2.0	11.1.2.1 Note that when moving from Release 11.1.2.0 to Release 11.1.2.1, you use the "Apply Maintenance Release" option in EPM System Installer, instead of following the documented upgrade procedures.
11.1.1.3.x	11.1.2.1
An environment that includes multiple releases, which can include an environment with one instance of 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 Hyperion Enterprise Performance Management System Installation and Configuration Guide.

Note: If you are starting from Release 11.1.1.x, Oracle recommends the following upgrade path: 11.1.1.0 or 11.1.1.1 or 11.1.1.2 to 11.1.1.3 to 11.1.2.1

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 Shared Services was removed in Essbase Release 9.3, starting with Release 9.3.1.4.1. Essbase and Shared Services Release 11.1.1.3, however, still synchronize security information. For this reason, if you are using Essbase Release 9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3, as recommended above. Upgrading to Release 11.1.1.3 is not an option for these Essbase releases.

Top of Document

Defects Fixed in this Release

Defect Number	Defect Fixed
• 11680782, 10306270	Duplication errors are created when copying a Profitability and Cost Management using Lifecycle Management.
• 10312883	Drivers now correctly display Russian characters under Lifecycle Management.
• 10278590	The driver calc script correctly displays Russian characters.
• 9964514	In this release, Oracle Diagnostic Logging (ODL) is being used as the logging mechanism. The ODL framework provides uniform support for managing log files, including log file rotation, maximum log file size, and the maximum log directory size. For more information, see the “Using EPM System Logs” chapter of the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
• 9792619	Only primary hierarchy members are now displayed on the Trace Report.
• 9725580	Genealogy is now correctly calculated.
• 9657556	With this release, Profitability and Cost Management customers can use Web Services to create a custom script to invoke a number of operations from the command line console. See the Oracle Hyperion Profitability and Cost Management New Features for additional information.
• 9585665	You can use the Down arrow to scroll down a long list of members.
• 9477141	Previously, an incorrect error message was displayed in the log during deployment, implying that the deployment was not successful. A message has been added to the Profitability and Cost Management HPCM log so interested users can check the actual progress of the job cloning progress using Performance Management Architect's Job Console.
• 9057377	The universal driver is no longer displayed for intersections that have an assigned Exception driver.
• 9008013	It is now possible to filter and sort exception driver selections.
• 8678078	‘Not Equal’ operator is now available on the Name/Alias Assignment Rule Filter.
• 8664823	When a list is filtered in Grid View, the filter can now be changed without having to reset the filter by toggling to the Tree view, and then back to the Grid view.
• 8661878	With this release, it is now possible to easily sort and filter assignment rules.
• 8661534	With this release, the new Assignment Rule Definition screen enables users to create assignment rules without having to first select level zero member(s) from the source dimensions. See the Oracle Hyperion Profitability and Cost Management User's Guide for instructions.
• 8661088	With this release, you can sort assignments by Destination dimensions.

Top of Document

Defects Fixed in Release 11.1.2.0

Defect Number	Defect Fixed
• 9431733, 9431727	Previously, only 20 POVs could be displayed on the POV Manager screen, even if there were more in the application. Now, if there are more than 20 POVs, a vertical scroll bar is activated to enable you to scroll to view up to 1,000 POVs.
• 9412141, 8733055	Previously, Profitability and Cost Management data had to be migrated through Oracle Hyperion Enterprise Performance Management System Lifecycle Management as a single artifact that contained the entire model. Depending on the size of the model, out of memory errors might be encountered. With this release, you can now select one or more of the following artifacts for migration through Lifecycle Management: - Application preferences - Driver definitions - Stage definitions - POV definitions - Driver selections - Assignments - Assignment Rules - Application preferences
• 9138570	Previously, when the Calculation cube was selected to trace allocations, when the intersection was displayed, it did not expand to display destinations, and no error was posted to the log. With this release, the Trace Allocations screen now works using the Reporting cube, by default. If you decide to use the Calculation cube, the default calculation must be run.
• 9046670	It is now possible to retain Common Member Selector settings, such as the Grid View and other CMS options, for all instances of the dimension for the duration of a user session.
• 8968466	The default setting for the Essbase connection type is now set to 'Embedded.'
• 8732571	When importing stages, the order of the stages in the database is now correctly displayed in the same sequence in Profitability and Cost Management.
• 8717836	Previously, changes that resulted in the restructuring of upper level dimensions displayed Level 0 members incorrectly in the hierarchy. Although EPM Architect displayed the new structure correctly, in Profitability and Cost Management, the Level 0 members were orphaned without a parent and were displayed at the top of the hierarchy. Now, when organization changes result in restructuring of upper level dimensions, the Level 0 members are correctly displayed in the hierarchy.
• 8678088	If the POV status is changed to Published or Archived, calculation for that POV is disabled. Calculation is only available if the POV Status is set to Draft.
• 8678084	When navigating in the Driver Selection tree, it is now possible to view a list of up to 5,000 members in either Tree or Grid views.
• 8666897	Performance enhancements have been implemented to speed up the generation of the calculation cube. In addition, you must ensure that the BSO DataStorage property for the member NetCostForAssignment and all its non level 0 descendants is set to ‘Stored’ and NOT ‘DynamicCalc’.
• 8654748	The genealogy calculation time has been improved with this release.
• 8642743	If duplicate member names were erroneously created on the same hierarchy in EPM Architect, when the duplicates are deleted from EPM Architect, they are correctly removed from the Profitability and Cost Management tables.
• 8617015	The member selection is retained when you change Task Areas.
• 8576228	If you delete a UDA dimension association in the Dimension Library, when the application is redeployed into Profitability and Cost Management, the UDA association is no longer available in the common member selector filter.
• 8563493	You can no longer enter a single quote character (‘) in the name of a Calculation or Reporting Database (for example, “Smith’s”) in the Profitability and Cost Management user interface. The single quote is a restricted character in Essbase naming conventions. The use of the single quote in the database name will cause the deployment of the application to fail. For a complete list of restricted words and characters, see the Oracle Essbase Database Administrator's Guide.
• 8554298	When using the Application Creation Wizard in EPM Architect, you can now correctly create a Profitability and Cost Management application without using the Alias dimension.
• 8552951	You can now use up to 64KB in Profitability and Cost Management for both the ASOFormula and BSOFormula properties.
• 8327443	For configurations using WebLogic, Oracle and SSL, deployment to Essbase no longer fails if there are duplicate aliases with mixed cases (for example, ENGLISH and English).
• 7707307	After importing a Profitability and Cost Management model from Lifecycle Management, the preselected POV now correctly displays a status of "Draft," enabling the model for editing.

Top of Document

Known Issues

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

Defect Number	Known Issues
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. To work around this issue, create the application using a shorter version of the application name, or enter the name in English.
11737519	After completing a maintenance upgrade from an existing Release 11.1.2.0 application to Release 11.1.2.1, Essbase deployment tasks from the Manage Database task area fails. To work around this issue, you must re-register the application in Performance Management Architect: 1. From the EPM Workspace main menu, select Navigate, then Administer, and then Application Library. 2. Right-click the application, and select Reregister. 3. Select the options for your application, and then click Reregister. After the application is re-registered, deploy to Essbase.
10278828, 10274069	If you enter unexpected or restricted words or characters in the Driver Editor, the validation error message is not explicit.
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 11.1.1.3.x to Release 11.1.2.1, 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 Hyperion 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.
9482040	An error is generated if the names of prefixes, stages, dimensions or members includes an @ sign.
9309229	Attribute Dimension Member associations for the Measures dimension are not deployed to Profitability and Cost Management. This feature is not currently supported.
9289136	Occasionally, the first time after an installation when you create a new import configuration, 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 Essbase dimension 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, 7113162	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.

Top of Document

Tips and Troubleshooting

Entering Filters

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.

Setting the Hierarchy Type Property

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

Note: If a dimension member has a formula, the hierarchy type must be set to ‘DYNAMIC.’

To set the Hierarchy Type:

1. From EPM Workspace, select Navigate, then Administer, and then Dimension Library.

2. Under the application, select Measures, and then UserDefinedDriverMeasures.

3. In the Property Grid, select the appropriate Hierarchy Type property:

o Select Stored for any dimension members that use the following consolidation symbols:

§ + ADDITION

§ ~ IGNORE (only underneath LABEL ONLY members.)

o Select Dynamic for any business dimension that needs to use all supported consolidation symbols, or that has a formula.

4. Redeploy the application to the Profitability and Cost Management, and then Essbase.

Solving Issues with Profitability and Cost Management Connection Type

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.

Changing the Connection Type to Embedded Mode

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:

1. In Profitability and Cost Management, from Task Areas, select Manage Model, and then Model Summary.

2. On the Model Summary screen, select the Model Level Preference tab.

3. Under Essbase Information, select “embedded” from the Connection Type drop-down list.

4. Click the Save icon.

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.

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

Setting the JVMOption for Embedded Connection Type

If you are experiencing difficulties using the ‘embedded’ Connection Type mode in Profitability and Cost Management to connect to Essbase (especially in distributed configurations), you must set the environment variable ESS_ES_HOME as a JVMOption for 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.

Note: No changes are required if you are using the ‘APS’ Connection Type mode.

To set the JVMOption for the Embedded Connection Type:

1. Stop the Profitability and Cost Management server.

2. Edit the Windows registry for HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Profitability0\HyS9HyS9PftWeb.

3. Add a JVMOptionX (where X is the next integer, based on the existing number of JVMOptions). For example, if the current JVMOptionCount is set to decimal 17, then add JVMOption18.

4. Set the string value for the new JVMOptionX to -DESS_ES_HOME=<folder-name>, where folder name is the name of the folder that contains the empty ‘bin’ and ‘data’ folders.

5. Increment the JVMOptionCount to the next integer. For example, if JVMOption18 is added, then set JVMOptionCount to decimal 18.

6. Start the Profitability and Cost Management server.

Setting for High Rate of Network Connections

To improve the ability of the Windows operating system to deal with a high rate of network connections:

1. From the Windows Registry, navigate to KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters.

2. Add or modify the following registry entries:

o TcpTimedWaitDelay - Set this to a low value (for example, 30) for the sockets to be released quickly. This DWORD value ranges between 30-300.

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

CAUTION: Before modifying these parameters, refer to the Microsoft Windows operating system documentation for more details.

3. Reboot the system for the changes to take effect.

Modifying Default WebLogic Timeout Settings for Lifecycle Management

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

To work around this issue, you must reset the default timeout settings as described in the following procedure.

To modify the default timeout for WebLogic Server:

1. Navigate to Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf.

2. In the configuration file, locate the section LocationMatch/profitability, and add the line WLIOTimeoutSecs 3000, as shown below:

<LocationMatch /profitability>
SetHandler weblogic-handler
PathTrim /
KeepAliveEnabled ON
KeepAliveSecs 20
WLIOTimeoutSecs 3000
WeblogicCluster servername:6756
</LocationMatch>

3. Navigate to Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\htppd.conf.

4. Set Timeout to 3000, as shown in the following text:

# Timeout: The number of seconds before receives and sends time out.

Timeout 3000

Note: The server timeout shown above is a suggested limit, and may be modified to suit the specific timeout settings provided in the documentation for your application server.

Creating Import Staging Tables

In order to import model data from relational databases into Profitability and Cost Management, you must create a set of staging tables in a separate database to format the information for use in the application.

CAUTION: Do not modify the product schema for the import.

Staging database scripts are available for MS SQL Server and Oracle Database. Use the create_staging.sql script to create the import tables in the new database.

To create staging tables:

1. Create a new Oracle or MS SQL Server database, outside of the product schema.

2. Navigate to the location for the appropriate SQL script in the default location for your database type:

o EPM_ORACLE_HOME/products/Profitability/database/Common/MSSQLServer

o EPM_ORACLE_HOME/products/Profitability/database/Common/Oracle

3. Run the appropriate SQL script against the new database:

o To create new staging tables, run create_staging.sql.

o To use existing staging tables, run hpm_stg_driver_upgrade.sql.

To import data and metadata using these staging tables, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.

Top of Document

Documentation Updates

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for download from the Enterprise Performance Management System Documentation area of the OTN Web site (http://www.oracle.com/technology/documentation/epm.html). For faster access to the documentation, you can also use the Enterprise Performance Management 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 E-Delivery 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.

Copying and Pasting Code Snippets from PDFs

When you cut and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid.
Workaround: Cut and paste from the HTML version of the document.

Top of Document

Accessibility Considerations

It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle’s Hyperion Profitability and Cost Management supports accessibility features, which are described in Appendix C in the Oracle Hyperion Profitability and Cost Management User's Guide. The most up-to-date version of this guide can be found in the EPM 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.

Top of Document