Oracle® Hyperion Profitability and Cost Management, Fusion Edition
Release 11.1.2.2 Patch Set Update (PSU): 11.1.2.2.353
Readme
Defects Fixed in Patch 11.1.2.2.352
Defects Fixed in Patch 11.1.2.2.351
Defects Fixed in Patch 11.1.2.2.350
Defects Fixed in Patch 11.1.2.2.301
Defects Fixed in Patch 11.1.2.2.300
New Features with Earlier Patch 11.1.2.2.350
Integrating Smart View Queries
Profitability and Cost Management Application Manager
Outline Builder (Cube Generator)
Patch Post-Installation Instructions
Changes to Web Services in Earlier PSUs
Model Data Prerequisites for Detailed Profitability
Database system Privileges Required by the Product Schema
Model Data Schema and Model Data User (SQL Server Only)
Model Data Schema Table Structural Requirements
Model Data Schema Table Grants to the Product Schema
Using the Detailed Application Model Calculation Statistics Script
Calculation Process Related Artifacts
Setting the Hierarchy Type Property
Solving Issues with Profitability and Cost Management Connection Type
Changing the Connection Type to Embedded Mode
Setting the JVMOption for Embedded Connection Type
Setting for High Rate of Network Connections for Windows
Increasing Local Port Range for Linux
Modifying Default WebLogic Timeout Settings for Lifecycle Management
Creating Import Staging Tables
Accessing EPM System Product Documentation
Copying and Pasting Code Snippets from PDFs
This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.
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.
This Patch Set Update (PSU) requires a full installation of Profitability and Cost Management Services for Release 11.1.2.2.00.
This patch is a cumulative patch; it includes these previous patches:
• Release 11.1.2.2.300
• Release 11.1.2.2.301
• Release 11.1.2.2.350
• Release 11.1.2.2.351
• Release 11.1.2.2.352
You can apply this patch to releases 11.1.2.2.00, 11.1.2.2.300, 11.1.2.2.301, 11.1.2.2.350, 11.1.2.2.351 and 11.1.2.2.352 only.
This Profitability and Cost Management patch requires these other EPM System patches:
• EPM Workspace patch 13936087 (Patch Set Update for 11.1.2.2.300)
• Shared Services patch 14020629 (Patch Set Update for 11.1.2.2.300)
• Shared Services patch 14521719 (Patch Set Exception for 11.1.2.2.300; requires Shared Services patch 14020629)
• Shared Services Patch 17537889 (Patch Set Exception for 11.1.2.2.303).
Both the Shared Services and EPM Workspace patch set update patches must be applied on any machines where Foundation Services is installed. This Profitability and Cost Management patch and the Shared Services patch set exception patch must be applied on any machines where Profitability and Cost Management is installed. To avoid errors, Oracle recommends you apply the patches in the order listed above, then apply this patch and redeploy all Web applications.
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.
This release supports the same platforms as the base release.
Information about supported languages for Enterprise Performance Management products is available in the Oracle Enterprise Performance Management System Release 11.1.2.x (Excel) spreadsheet, in the Translation Support tab. This spreadsheet can be found on the Oracle Enterprise Performance Management System - Supported Platforms page on OTN.
Defects Fixed in Patch 11.1.2.2.352
|
Defect Number |
Description |
|
• 16450797 |
When importing from staging tables for assignment rule selections, driver selections, or driver exceptions for either Standard or Detailed Profitability applications, with only a single POV dimension defined, the error ORA-904 "Invalid Identifier" occurred. This patch corrects the error so single-POV applications now import correctly from all staging tables. |
|
• 16403790 |
Profitability and Cost Management calculation scripts for Standard Profitability applications are now generated with the directive “SET MSG NONE;”. This reduces the output to the Essbase log and improves calculation performance. |
|
• 16398658 |
Calc script generation performance is dependent on the effectiveness of the XIE3HPM_ASSIGNMENT unique index. Performance can degrade after importing explicit assignments via staging imports or LCM, which causes updates to this index and can leave it in a non-performant state.
This patch adds automatic rebuild of the XIE3HPM_ASSIGNMENT index, to maintain proper calc script performance. This assignment index is rebuilt at the beginning of each calc script generation. |
|
• 16390694 |
Calc script execution would run very long in certain cases where the calc script was generated incorrectly due to intermittent caching issues. That problem is resolved in this patch. |
|
• 16358339 |
Genealogy calculation performance is enhanced by reducing the number of calls to Essbase during execution. |
|
• 15985494 |
When the same dimension member name was used in more than one dimension, the error “Essbase Error (1260073): Cannot uniquely identify a member” occurred after clicking a Smart View hyperlink from the Stage Balancing screen in a Standard Profitability application. That problem is resolved in this patch. |
Defects Fixed in Patch 11.1.2.2.351
|
Defect Number |
Description |
|
• 15935314 |
In release 11.1.2.2.350, for dimension member aliases containing a comma, attribute assignments did not propagate from HPCM to the Essbase outline. Attributes are now correctly created in the Essbase outlines. |
|
• 15903025 |
In release 11.1.2.2.350, when deploying a Unicode-enabled Profitability application to Essbase, multi-byte characters were improperly interpreted as ASCII characters. Unicode applications now correctly create Unicode Essbase outlines. |
|
• 15885965 |
These two problems with the staging imports for Assignment Rule Selections and Driver Associations for Standard Profitability applications are resolved in this patch: 1) If the application has two stages that have identical dimensionality, and for each of those stages, some identical dimension tuples are being loaded, a SQL error can occur during the staging import. 2) If the application has two stages with different dimensionality, but some members have the same names across the different dimensions AND some dimension tuples that are identical in their dimension member names are loaded for each of those stages, a null pointer exception error can occur during calc script generation. |
|
• 15885814 |
In release 11.1.2.2.350, the Model Validation screen under Missing Driver Assignments incorrectly showed nodes which do actually have a driver assigned to them. With this patch, those false positive entries are eliminated. |
|
• 15880583 |
In release 11.1.2.2.350, member formulae with quotes and newlines were not getting loaded correctly when deployed to Essbase. Member formulae are now correctly created in the Essbase outline. |
|
• 15851078 |
The order that repeated dimensions (where the dimension is used in more than one stage) were redeployed to Essbase from a Profitability application was inconsistent from one redeploy to the next. The dimension order in the outline for a repeated dimension is now consistent with the order of stages in which the particular dimension is used. |
|
• 15851045 |
|
|
• 14839917 |
The time taken to generate calculation scripts was considerably longer in release 11.1.2.2.350 when compared to the 11.1.2.1.603 release. The problem is resolved in this patch, bringing that time back down to what it was before. |
|
• 14838668 |
In release 11.1.2.2.350, on deploy to Essbase using the Update method, dimensions were being deleted and recreated, the same as with the Replace method. This was causing the dimension order to be reset. The Update method of deploying to Essbase now preserves the existing dimension order and settings. |
|
• 14796116 |
Multiple import configurations kicked off in parallel are now executed sequentially, to prevent the possibility of duplicate dimension member groups being created. |
|
• 14768899 |
Staging imports for Assignment Rule Selections, Driver Rules, and Driver Exceptions failed when using MSSQL Server as the staging repository, due to problems with the IDENTITY property on the ID columns in the various staging tables. |
Defects Fixed in Patch 11.1.2.2.350
|
Defect Number |
Description |
|
• 14611132 |
Dimensions order is now consistent across EPMA, HPCM, and Essbase. |
|
• 14280372 |
Previously, a security policy was tied with the Profitability and Cost Management web service and there was no other way to remove it and apply a different security policy. Now web services are disjoint from the associated security policy. This makes it easy to verify if the web service is working, and it avoids some security configuration steps if the username with SAML token policy is not used. |
|
• 14152781 |
Certain text fields and search fields are now restricted from using special characters which could pose a security risk. |
|
• 14146687 |
If you re-parent an attribute dimension member from level 0 to non-level-0 in Enterprise Performance Management Architect, then re-deploy the application to Profitability and Cost Management, the re-deployment fails with a Null Pointer Exception error. This error is fixed in this patch. |
|
• 14073976 |
There is now a confirmation to save an ad-hoc view when there are no created views in Manage Views dialog. |
|
• 14068852 |
Artifact ‘Created By’ fields are no longer changed if another user edits the artifact. |
|
• 14057774 |
Filtering, sorting, and searching by member alias no longer causes error messages to appear onscreen. These functions now work correctly when displaying member alias onscreen. |
|
• 14048604 |
Using staging import, Drivers were being imported successfully even with duplicated measures in its definition. With this patch, usage of duplicated measures is checked in Driver definitions, and those with duplicated measures are rejected. |
|
• 14036706 |
It is now possible to register a view as a Destination stage table in a Microsoft SQL Server installation. |
|
• 14036389 |
LCM import of custom pre- and post- SQL scripts now successfully completes for Detailed Models on systems using SQL Server. |
|
• 14035608 |
A calculation run in a Detailed model using a limited source set failed if the source assignment rule had a level-0 member selection. |
|
• 14026468 |
In a Detailed Profitability application, an incorrect error message no longer appears when attempting to delete an assignment rule that has been used in the bulk editor. |
|
• 14025614 |
After deleting driver exceptions or assignment rule selections using the Bulk Edit feature, any deleted entries previously shown on the screen remain until the screen is refreshed. If you selected one of those entries to edit or delete it, an "Unexpected error in business logic" error was generated. This action no longer causes an error. |
|
• 14025377 |
Assignment rule validation now checks if an Attribute or UDA association has been removed from a dimension used in an assignment rule with Attribute/UDA filtering. |
|
• 14015108 |
Correct artifact names now appear in application audit reports. |
|
• 14010798 |
Paging errors on the unused drivers validation report have been fixed. |
|
• 13981697 |
Search member function now correctly performs ‘find next’ when sorting of members is active. |
|
• 13969601 |
It is now possible to change the Same as Source dimension when an Assignment rule is opened for editing. |
|
• 13956950 |
In Detailed Profitability applications the staging table import jobs now display the error count in the job library screen. |
|
• 13882145 |
Unnecessary message “An error was encountered while closing all content. Can only remove the children” no longer appears when logging off of the Workspace while an HPCM application is open. |
|
• 13849017 |
Driver data report now generates correctly when there are more than 1 driver measures in any of the driver measures location choices. |
|
• 13845862 |
In certain circumstances changes to stage definitions were not saved. These issues are now resolved. |
|
• 13635401 |
In certain circumstances Assignment Rules using the Same as Source option could become invalid after stage definition changes. The Assignment Rule Validation report now detects these cases. |
|
• 13545212 |
LAST_UPLOAD_DATE column of all staging tables is now updated when Import Staging Tables is completed successfully. |
|
• 13512183 |
Two columns: 'Sequence Priority Number' and 'Write Result to Destination Measure' have been added to the Driver Definitions main screen. |
|
• 12808353 |
Missing Assignment Destination validation report no longer displays a red cross error icon when there are no missing assignments found. |
Defects Fixed in Patch 11.1.2.2.301
|
Defect Number |
Description |
|
• 14256127 |
The system-generated dimension hierarchy reporting views (HPMD_<app_name7>_<dim_short_name10>_HIER_V) created for Detailed Profitability applications in the Reporting Views page under Manage Database were not able to perform well enough to support general reporting functions. With this patch, these views are no longer created as views but as tables, with persisted data, to solve the reporting performance problem. The new tables and their synonyms are created using this naming convention: HPMD_<app_name7>_<dim_short_name10>_HIER (same as the views but without "_V"). Note that because the data is now persisted, you will have to re-generate these reporting tables after maintaining dimensions in Performance Management Architect and re-deploying dimension changes to Profitability and Cost Management, in order to refresh the persisted data in these tables. |
|
• 13509411 |
For Detailed Profitability models, on the assignment rule definition screen, data filter tab, the column headers now match the data displayed. |
|
• 13692025 |
A new Web Services method, clearPOVData, has been added to clear POV Data. This new operation is equivalent to the operation performed in the UI (Select Manage Model, then POV Manager, and then Delete). |
|
• 14165415, 14165185, 14164922, 13982243, 13926648, 13847420, 13742313, 13738281, 13644803, 13644743 |
Several browser compatibility display issues were fixed for Internet Explorer 9, Firefox 9 and Firefox 10. |
|
• 14057645, 13930295, 13879506, 13736687, 13736613, 13734582, 13725330, 13725283, 13584522, 13570483, 13570481, 13523061, 13520390, 13520082 |
Several screens and messages had translation errors fixed. |
Defects Fixed in Patch 11.1.2.2.300
|
Defect Number |
Description |
|
• 14055507 |
For Standard Profitability, when loading the reporting cube for BksSP81R_AllData, an error was generated stating “Member Not Found in Database.” As a result, the Stage balancing report could not be generated. |
|
• 13973953 |
For Standard Profitability, if you change a Level-0 destination member that is used in an assignment to a non-Level-0 member in the EPM Architect Dimension Library, when you redeploy the Profitability and Cost Management application, the assignment is not deleted, although it does display as a non-Level-0 member. |
|
• 13903325 |
The Comment property from EPM Architect is not sent to Essbase. |
|
• 13875455 |
For localized applications, validation of the Driver definition may fail if the Destination measure is inserted in the driver formula. |
|
• 13838989 |
If you select a POV that has a status of Published or Archived, and then select a POV that has a status of Draft, when you try to create or edit a driver association using the double-click or <…> option, or select a driver name from the drop-down list, the driver rule is not created, and the changes are not saved. |
|
• 13835585 |
When using alias in the assignment screen, the destinations are duplicated. |
|
• 13832599 |
The Stage Balancing report is not created in the following cases: - The Source stage table has a joined lookup table - Both the Source and its Lookup table have the SAME system column, and it is registered as a Measure column on the Source or Lookup tables. |
|
• 13810890 |
Import Configuration List is NOT sorted
and the entire list needs to be |
|
• 13803615 |
For Standard Profitability, after a successful cube deployment, if you go to the Data Entry or Stage Balancing screen, and then try to redeploy the Essbase cube using the Replace option, the redeployment fails. |
|
• 13792756 |
When importing driver definitions through Staging tables, some drivers are not successfully inserted and the following error is displayed: "ERROR_DRIVER_MEASURE_NOT_FOUND". |
|
• 13789389 |
When creating an assignment rule selection, if the Same As Source rule dimension member does not exist on the Destination dimension, no warning message is displayed. |
|
• 13772443 |
In Standard Profitability, if you create one assignment with the same dimension member set to Same As Source, when you try to edit or delete the created assignment in the Destination pane, an error message is displayed. |
|
• 13768324 |
If you are using Firefox 10, when you change the destination pane mode without saving data, there is no confirmation message and the Save icon remains enabled. |
|
• 13717938 |
For both Standard and Detailed Profitability, if extra dimension members are added and then imported into Profitability and Cost Management, the import seems to be successfully completed, but no errors are generated for incorrect driver exceptions and assignment rule selections. |
|
• 13703813 |
A new Web Services method, processGenealogyPathsWithOutASOCubeClear, has been added to run Genealogy execution paths without clearing the ASO cube for the selected POV. This operation is treated as a "Run Now" and executed immediately on creation. The return value is the Process Name generated (CES task ID) for this asynchronous request. You can use this task name to track the status using "getTaskflowStatusByProcessName" See “Change in Web Services in Earlier PSUs” in this document for additional Web Services operations added in this release. |
|
• 13703803 |
A new Web Services method, clearASOCube, has been added to clear the ASO cube for a selected POV and Layer combination. You can use this task name to track the status using "getTaskflowStatusByProcessName" See “Change in Web Services in Earlier PSUs” in this document for additional Web Services operations added in this release. |
|
• 13700793 |
For Detailed Profitability, after running calculations for a model, if you try to edit the Source or Destination stage, or associated stage dimensions, the changes cannot be saved. |
|
• 13613687 |
For Standard Profitability, if you change a Level-0 destination member that is used in an assignment to a non-Level-0 member in the EPM Architect Dimension Library, when you redeploy the Profitability and Cost Management application, all rules and assignments are displayed as still applied and participate in the calculation, although they are not displayed on the Assignments screen. |
|
• 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, when the Stage Balancing report is generated, the Idle column is empty, and the corresponding values are shown in the Unassigned column. |
|
• 13537329 |
For Detailed Profitability, if several measures (such as Rate) are registered on a horizontal source table along with the Input measure, the Stage Balancing report may fail. This issue does not occur on a vertical source table. |
|
• 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. |
|
• 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. |
New Features with Earlier Patch - 11.1.2.2.350
The following new features were introduced in release 11.1.2.2.350 for Profitability and Cost Management:
Integrating Smart View Queries
SmartView integrations are available only for Standard Profitability models to provide help with data management, run diagnostics for allocation data, and enable analysis of both allocation and genealogy data. In addition, the SmartView integration provides context-sensitive investigation tools that can be launched from Stage Balancing.
SmartView queries provide users with quick access to views of Profitability and Cost Management data. The queries can be defined against either the Calculation or Reporting database, and after SmartView is launched, the grid can be used for analysis. Data entry may also be performed against the Calculation database.
The Manage Queries screen enables you to select a query type, and then refine your query using a grid and a SmartView POV. The queries can be saved and reused, or cloned by other Profitability and Cost Management users. The queries can also be exported and re-imported using Lifecycle Management (requires Shared Services patch 14521719 to enable the new artifact – see the Other Required Patches section).
The default queries offer different views, depending on the query type selected. Each of the queries enable additional selections for the selected type. For example, the Driver Measures query type prompts the user to specify the driver location (Source, Assignment, Destination or Global) and the stage combinations in order to complete the dimension defaults that are presented on the dimension layout and member selection screen.
The results of the queries are viewed through the Stage Balancing report using default hyperlinks that can be selected to launch SmartView with the relevant grid. You can also drill down further on input or allocation data. For example, you could drill-down into Unassigned costs after an allocation run, or to examine input data that was used in the same run.
If any dimensions or dimension members are renamed or deleted, the SmartView queries that reference those dimensions become invalid. The Queries tab in the Model Validations screen validates all queries, and displays an error message for any invalid queries.
For instructions on creating, maintaining and viewing Smart View queries, see the Profitability and Cost Management Addendum for Patch Release 11.1.2.2.350 on the Oracle Technology Network (OTN), listed in the Oracle Hyperion Profitability and Cost Management product area.
Profitability and Cost Management Application Manager (Profitability Applications)
In instances where Performance Management Architect cannot be installed, the Profitability and Cost Management Application Manager provides an alternative to using Performance Management Architect to manage Profitability and Cost Management applications and dimensions.
For Application Manager, Essbase is used as the dimension management system, or source of dimensions for the Profitability and Cost Management application. Users create dimensions and dimension members in a Master Essbase Application, which are then imported into a Profitability and Cost Management application. The same Master Application can be used to create multiple Profitability and Cost Management applications. You select the application type, either Standard or Detailed, when you create the Profitability application.
Whether you use Essbase or Performance Management Architect to create a Profitability and Cost Management application, there is no difference in how the applications work; however, you can only modify the source by using the original dimension management system.
For instructions on creating and maintaining the Essbase Master Application and using it to create Profitability applications, see the Profitability and Cost Management Addendum for Patch Release 11.1.2.2.350 on the Oracle Technology Network (OTN), listed in the Oracle Hyperion Profitability and Cost Management product area.
Please note these changes from the Addendum that apply to this release:
1. Attribute dimensions are not supported in this release.
2. Alternate hierarchies are not supported for business dimensions or point of view dimensions in this release.
3. The Duplicate Application capability is not enabled in this release.
Outline Builder (Cube Generator)
In release 11.1.2.2.350, a new Outline Builder has been created that enables the deployment of very large models from Profitability and Cost Management to Essbase. The new feature also reduces the Essbase outline deployment time and the usage of TCP ports consumption during the deployment. Both ASO and BSO databases are supported.
No action is required by users, as the Outline Builder automatically supports the deployment operations.
The following issues are the noteworthy known issues of this release.
|
Defect Number |
Known Issues |
|
Life Cycle Management import for the new Smart View Query artifact does not support merge functionality. That is, if the query already exists in the target application, it will not be imported. To update a Smart View Query in the target environment by importing it, first delete it in the target application. |
|
|
15958955 |
For Detailed Profitability applications it’s possible to create duplicate assignment rule selections or driver exceptions using Bulk Edit after re-ordering the dimensions on the source stage. |
|
15958075 |
For Standard Profitability applications that use the “Two Pass Calculation” property on some dimension, when re-deploying the outline to Essbase using the Update option, the re-deploy fails with an error. The workaround is to re-deploy the outline using the Replace option. |
|
15952742 |
In the Manage Database - Reporting Tables and Views screen, the attribute dimension short names don’t get used for naming the attribute columns in the resulting views. Instead, the first 30 characters of the actual attribute name are used for the column name. |
|
14678739 |
In a Detailed Profitability application, if you try to delete an assignment rule from the Assignment Rule Management dialog, and the assignment rule is referenced by a Stage Object Calculation rule, the deletion attempt will fail with an error. You can delete the rule successfully from the main Assignment Rule Management screen. |
|
14668093 |
The Duplicate Application functionality of the new Application Manager feature is not enabled in this release. As a workaround, just create a new application and source it from the same dimension master cube as the original application was sourced from. If the dimension master contents have not changed since the original application was created, the new application will be identical to the original. |
|
14620404 |
In the new Application Manager feature, once dimensions have been deployed from the Essbase dimension master to the Profitability and Cost Management application, you should not delete the source dimensions from the Essbase dimension master cube. If you do, you will not be able to update that dimension any more from the master. Likewise, you should not change the dimension name or the dimension type in the Essbase dimension master cube once that dimension has been deployed to your Profitability and Cost Management application. In other words, you should not modify in any way the UDAs that define the dimension type. The existing validations in the Pre-Update Analysis option, do not currently report these cases. |
|
14593199 |
In the new Application Manager feature, if you create one application after another in close succession, you may experience deadlock in the database when using MS SQL Server. |
|
14549948 |
When a POV dimension member is moved from level 0 to non-level 0 in the Essbase dimension master cube, that member is not properly updated in HPCM by the Update Dimensions action, and no appropriate error or warning is given. |
|
14544845 |
In this release there is a new pseudo-application called "Profitability Applications" that shows in the list of Profitability Applications from the Workspace menu when you select Navigate -> Applications -> Profitability. This pseudo-application is used to invoke the new Application Manager feature. The "Profitability Applications" pseudo-application also shows up in the Shared Services Console under the Default Application Group in the Application Groups folder, and may also be present in the applications list in the File System folder. In these contexts it should be ignored, since it is not a real application, and is not actually available for import or export. |
|
14514809 |
In the Manage Queries create/edit wizard, the screen for step 2 – Dimension Layout does not function properly when you use the Back button to return to it from the screen for step 3 – Member Selections. |
|
14488136 |
For a Detailed Profitability application, when you run two Data POV's together in the same calculation, if the execution for the first POV encounters warnings, and the execution for the second POV has none, the job completes with status "Success" (instead of "Success with Warnings") and the warnings from the first Data POV are not counted in the Warnings column for that job in the Job Library. |
|
14481677 |
In Model Data Registration, when you duplicate a registration for a destination stage table and then assign that new registration to the destination stage, the primary key information does not get copied from the source registration, and the calculation will fail with this error: "Primary key for the Destination stage table is not registered." The workaround is to run Validate on the Model Data Registration tab in Model Validations. This action will find and save the missing primary key metadata for the registered destination stage table. |
|
14256127 |
With this patch, the Deploy function in the Reporting Views page under Manage Database for Detailed Profitability applications now creates tables in place of the system-generated dimension hierarchy reporting views (HPMD_<app_name7>_<dim_short_name10>_HIER_V). This is done in order to persist the data for better reporting performance. The new tables and their synonyms are created using this naming convention: HPMD_<app_name7>_<dim_short_name10>_HIER (same as the views but without "_V"). Note that because the data is now persisted, you will have to re-generate these reporting tables after maintaining dimensions in EPMA and re-deploying dimension changes to HPCM, in order to refresh the persisted data in these tables. If you have already created a Detailed Profitability application and have deployed the system-generated dimension hierarchy reporting views, this patch will not delete them or their matching synonyms in the model data schema, in order to preserve any external references to them you may have created. To take advantage of the improved performance offered by the new tables without disturbing those external references (for example, OBIEE reports), you can drop the view synonyms and recreate them with the same name but referencing the new tables instead of the views. |
|
14251027 |
Application performance in Profitability and Cost Management configurations using SQL Server can degrade over time as the database statistics become stale. If this happens, the database administrator should execute the SP_UPDATESTATS function to collect statistics for the database. This can be done from the DBO user or from any user that has the SYSADMIN role. Note: Do NOT grant the SYSADMIN role to the HPCM product schema user. Doing so will alter the default schema for that user. |
|
13954655 |
In Profitability and Cost Management configurations using MS SQL Server, calculations for rate-based drivers can be imprecise due to an amount column in a temporary table that is used in the calculation not carrying enough decimal places. |
|
13930150 |
Currently, the Oracle Hyperion Profitability and Cost Management Administrator’s Guide states that, in order to perform an Essbase deployment, the Power User must be granted the following rights: - Create and maintain elements within the model, such as stages, drivers, POVs, driver associations, assignments and application preferences. - Perform POV Copy, calculation validation, data entry and trace allocations. - Deploy to Essbase and generate calculation scripts - Import and export data.
|
|
13827118 |
For Detailed Profitability, when creating a new application in EPM Architect, do not use multibyte characters (for example, Japanese) in the application name. Use only ASCII characters to enter the application name. Note: Although multibyte characters are allowed in EPM Architect, they are not supported in Profitability and Cost Management. |
|
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. To obtain correct results and ensure the accuracy of the results on the Stage Balance view, locate the statistical measures as follows: - For Vertical and Horizontal Source Tables, put all your statistical measures on a joined lookup table. - To locate Statistical measures directly on your source table (either Vertical or Horizontal), create a new dimension called “Source Measure Types,” and assign the “input” member to all non-statistical measure members. |
|
13806255 |
A typical Detailed Profitability application may have one or more overlapping dimensions between the source and destination stages. For example, in the BksDP20 sample model, note that the Customer and the Product dimensions are used in both the Source stage and in the Destination stage. This results in a Level 0 Contribution view (for example, HPMD_BKSDP20_LEVEL_0_CONTRIB_V for the sample model) which has two columns for each of these overlapping dimensions – one for the source context and one for the destination context. In order to use this view to successfully generate a contribution report in Oracle BI EE, you must know how to properly register the system-generated dimension reporting views within the Physical Layer in OBIEE, so that each can join properly to both sets of dimension columns in the Level 0 Contribution view. Within the physical layer, you must create two Alias tables from the Level 0 view to the same dimension. For example, Level 0 view must join to the Customer dimension once for the Source (SRC) and once for the Destination (DEST). The following instructions use the hierarchy dimension view from the Customer dimension in the sample model as an example of how to do this. To generate a Level-0 Contribution Report: 1. Log in to Oracle BI EE, and navigate to your Profitability and Cost Management repository. 2. In the Physical Layer, right-click a dimension view that you want to use in your report, then select New Object, and then Alias. For example, click HPMD_BKSDP20_CUSTOMERS_HIER_V in the Sample Model as the model for the Alias table. 3. Enter a name for the new Source Alias table (such as HPMD_BKSDP20_SRCCUST_HIER_V), and then click OK. 4. In the Physical Layer, right-click your dimension view again, then select New Object, and then Alias. 5. Enter a name for the new Destination Alias table (such as HPMD_BKSDP20_DESTCUST_HIER_V), and then click OK. 6. In the Physical Layer, select the following objects, then right-click and select Physical Diagram – Selected Objects Only: HPMD_BKSDP20_SRCCUST_HIER_V HPMD_BKSDP20_DESTCUST_HIER_V HPMD_BKSDP20_LEVEL_0_CONTRIB_V 7. In the diagram, make physical joins between each of the new Alias tables and the Level 0 Contribution view. 8. Drag the Source and Destination Alias tables to the Business Model Layer. 9. In the Presentation Layer, modify the Level 0 Report to include columns from each of the new Alias tables.
|
|
13800625 |
For Detailed Profitability, additional Model Validations are required to check for missing database privileges. After installation, assign the following privileges: - For Oracle database, Detailed Profitability requires that these system privileges (or roles that include them) be granted to the Product Schema: CREATE TABLE CREATE VIEW 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: CREATE TABLE CREATE VIEW ALTER or CONTROL on the Model Data Schema to the product schema (so that the product schema has the ability to change objects in the Model Data schema) Note: Although users and schemas are regarded as the same in Oracle, in SQL Server, they are regarded as separate entities. 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. |
|
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 are transferred after calculation. This
information will be added to the Oracle Hyperion Profitability and Cost
Management User’s Guide for |
|
13322887 |
For non-Unicode Standard Profitability applications, do not use multibyte characters for the Calculation or Reporting database names. Use ASCII characters only for the database names. |
|
14011865, 14011955, 14012090, 14012139 |
For Detailed Profitability, when importing through Lifecycle Management, if the model contains incorrect files, the file may seem to be imported correctly; however, the validation may not detect the incorrect files, and the invalid artifacts may be imported with no error messages. |
|
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. |
|
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. |
|
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. |
|
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. |
|
6979576 |
The stage order is not correctly updated when using the import from the HPM_STG_STAGE table. |
The section includes important information about applying this patch for Oracle Hyperion Profitability and Cost Management.
To apply this patch:
1. Perform a full system backup, including EPM Architect and the Profitability and Cost Management databases.
2. Shut down the Profitability service (Hyperion Profitability - Web Application).
3.
Download and unzip the downloaded patch file, P17974124_11122353_<platform>.zip,
to the %EPM_ORACLE_HOME%/OPatch directory
(by default, Oracle/Middleware/EPMSystem11R1/OPatch).
Note: P17974124_11122353_<platform>.zip
is the name that My Oracle Support assigns to this patch. When you download the
file, a message indicates the file name.
4. From a command line on each machine on which Profitability and Cost Management is installed, 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\HPCM_11_1_2_2_353_17974124 -oh %EPM_ORACLE_HOME% -jre
%MIDDLEWARE_HOME%\jdk160_29
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/HPCM_11_1_2_2_353_17974124 -oh $EPM_ORACLE_HOME -jre $MIDDLEWARE_HOME/jdk160_29 -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.
If you have already applied the 11.1.2.2.300, 11.1.2.2.301, 11.1.2.2.350,
11.1.2.2.351, or 11.1.2.2.352 patches, you will get a warning of this form,
which you may ignore:
353 PSU Opatch apply request completed with the following status :
--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67620:Interim patch 17974124 is a superset of the patches [13910538, 14148563, 14400123, 14845052, 16565651] in the Oracle Home
--------------------------------------------------------------------------------
OPatch Session completed with warnings.
OPatch completed with warnings.
6. Finalize the configuration, as described in “Patch Post-Installation Instructions.”
7. Clear cached files from your browsers.
Patch Post-Installation Instructions
After installing the patch, you must finalize the post-patch configuration, as described in the following procedure.
To finalize the post-patch configuration:
1. Shut down the Profitability service (Hyperion Profitability – Web Application). It should still be down from the patch installation.
2. Start the EPM System Configurator. For instructions on using the EPM System Configurator, see the following guides:
• Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
• Oracle Hyperion Enterprise Performance Management System Installation Start Here
3. Under Profitability and Cost Management, select Deploy to Application Server only, and then click Next.
CAUTION: DO NOT select Configure Database, as this option will totally clear the database, and ALL existing applications will be lost. For additional information, refer to the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
4. Complete the remaining steps for the EPM System Configurator, as outlined in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
5. Run the appropriate database update patch script for your database type and release:
|
Release |
Database Type |
Database Patch Files |
|
From Release 11.1.2.2.00 |
MSSQL Server |
Apply the following patches using MSSQL Server Management Studio:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.300.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.301.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.350.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.00 |
Oracle |
Apply the following patches using SQL Developer:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.300.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.301.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.350.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.300 |
MSSQL Server |
Apply the following patches using MSSQL Server Management Studio:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.301.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.350.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.300 |
Oracle |
Apply the following patches using SQL Developer:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.301.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.350.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.301 |
MSSQL Server |
Apply the following patches using MSSQL Server Management Studio:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.350.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.301 |
Oracle |
Apply the following patches using SQL Developer:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.350.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.350 |
MSSQL Server |
Apply the following patches using MSSQL Server Management Studio:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.350 |
Oracle |
Apply the following patches using SQL Developer:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.351.sql • %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.351 or 11.1.2.2.352 |
MSSQL Server |
Apply the following patches using MSSQL Server Management Studio:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.2.353.sql
|
|
From Release 11.1.2.2.351 or 11.1.2.2.352 |
Oracle |
Apply the following patches using SQL Developer:
• %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.2.353.sql
|
6. If you are using Web Services with Release 11.1.2.2, see “Changes to Web Services in Earlier PSUs” for specific instructions. Also note that the application of any HPCM PSU will reset the current security policy defined for the Profitability Web Service within Oracle Web Services Manager (OWSM). If web services are used, it is important to perform the web services security policy setup steps.
7. Start the Profitability service.
8. Clear cached files from your browsers.
9. Invoke Profitability and Cost Management, open an application, and check in the System Information tab under Model Summary to verify that the Schema Version is 1.05.
10. If you have already run the create_staging.sql script in a previous release to create staging import tables, you will need to recreate the HPM_STG_ASSIGNMENT staging import table in the schema you created for staging imports.
You can do this by dropping the HPM_STG_ASSIGNMENT table and then running the statements from the create_staging.sql script that are related to the HPM_STG_ASSIGNMENT table, or you can drop all of your HPM_STG% staging tables and re-run the entire create_staging.sql script. The script is located at:
%EPM_ORACLE_HOME%/products/Profitability/database/Common/MSSQLServer
%EPM_ORACLE_HOME%/products/Profitability/database/Common/Oracle
depending on your database type.
To roll back a patch:
1. Perform a full system backup, including EPM Architect and the Profitability and Cost Management databases.
2. Shut down the Profitability service (Hyperion Profitability – Web Application).
3. From a command line, change the directory to %EPM_ORACLE_HOME%\OPatch. By default, the path is C:\Oracle\Middleware\EPMSystem11R1\OPatch.
4. To roll back the patch, enter the following command on one line:
Windows:
opatch.bat rollback -id 17974124 -oh %EPM_ORACLE_HOME% -jre %MIDDLEWARE_HOME%\jdk160_29
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 17974124
-oh $EPM_ORACLE_HOME -jre $MIDDLEWARE_HOME/jdk160_29 -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. Start the EPM System Configurator. For instructions on using the EPM System Configurator, see the following guides:
• Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
• Oracle Hyperion Enterprise Performance Management System Installation Start Here
6. Under Profitability and Cost Management, select Deploy to Application Server only, and then click Next.
CAUTION: DO NOT select Configure Database, as this option will totally clear the database, and ALL existing applications will be lost. For additional information, refer to the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
7. Complete the remaining steps for the EPM System Configurator, as outlined in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
8. Start the Profitability service.
9. Clear cached files from your browsers.
Changes to Web Services in Earlier PSUs
Changes have been made to the Profitability Web Services WSDL file, and corresponding changes were made to the sample client that is being shipped with this release.
You must use the latest sample client with Web Services. See the Web Services sample client in the %EPM_ORACLE_HOME%\products\Profitability\samples folder.
CAUTION: Any custom generated WebService port type client implementations must be modified accordingly.
To access the ProfitabilityService WSDL file and view parameters and details for the new or revised methods, go to http://<servername>:19000/profitability/ProfitabilityService?WSDL
The following change was introduced in release 11.1.2.2.350:
• Previously, a security policy was tied with the Profitability and Cost Management web service and there was no other way to remove it and apply a different security policy. Now web services are disjoint from the associated security policy. This makes it easy to verify if the web service is working, and it avoids some security configuration steps if the username with SAML token policy is not used.
This change was introduced in patch 11.1.2.2.301:
• A new Web Services method, clearPOVData, has been added to clear POV Data. This new operation is equivalent to the operation performed in the UI (Select Manage Model, then POV Manager, and then the Delete tab).
These changes were introduced in patch 11.1.2.2.300:
• A new Web Services method, processGenealogyPathsWithOutASOCubeClear, has been added to run Genealogy execution paths without clearing the ASO cube for the selected POV.
This operation is treated as a "Run Now" and executed immediately on creation. The return value is the Process Name generated (CES task ID) for this asynchronous request. You can use this task name to track the status using "getTaskflowStatusByProcessName".
• A new Web Services method, clearASOCube, to clear the ASO cube for a selected POV and Layer combination.
This operation is treated as a "Run Now" and executed immediately on creation. The return value is the Process Name generated (CES task ID) for this asynchronous request. You can use this task name to track the status using "getTaskflowStatusByProcessName".
In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are installed in an Oracle Home. For example, enter the following command on one line:
Windows:
opatch.bat lsinventory -oh %EPM_ORACLE_HOME% -jdk %MIDDLEWARE_HOME%\jdk160_29
UNIX/Linux:
./opatch lsinventory -oh /user/Oracle/Middleware/EPMSystem11R1 -jdk /user/Oracle/Middleware/jdk160_29
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.
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.
A sample application is available in the product installation which can be used for testing and self-led exploration of functional areas. The sample application includes a small data set and a fully built out model that illustrates various uses of drivers, assignments, and assignment rules.
Life Cycle Management extracts and data files are provided to support importing the model metadata, allocation artifacts, and cost and driver data. Essbase .otl files are also included as an alternative to the Life Cycle Management extracts. These files can be used to create Essbase dimension master cubes to use with the new Application Manager feature to create the sample applications. See the HPCM Sample Models Readme file for details on how to use these files.
You can find the HPCM Sample Models Readme.docx file at this location:
%EPM_ORACLE_HOME%\products\Profitability\samples
You can find the appropriate sample application files in the following locations:
• For Standard Profitability models:
%EPM_ORACLE_HOME%\products\Profitability\samples\BksSP81
• For Detailed Profitability models:
%EPM_ORACLE_HOME%\products\Profitability\samples\BksDP20
Note: The Detailed Profitability sample model is substantially larger than the Standard Profitability sample model, and it may take up to an hour to calculate.
Model Data Prerequisites for Detailed Profitability
Database System Privileges Required by the Product Schema
After installation, assign the following privileges to the Profitability and Cost Management Product Schema:
• For Oracle database, Detailed Profitability requires that these system privileges (or roles that include them) be granted to the Product Schema:
• CREATE TABLE
• CREATE VIEW
• CREATE ANY SYNONYM
• DROP ANY SYNONYM
• For Microsoft SQL Server, Detailed Profitability requires that these system privileges (or roles that include them) be granted to the user associated with the Product Schema:
• CREATE TABLE
• CREATE VIEW
• ALTER or CONTROL on the Model Data Schema to the user associated with the Product Schema (so that the Product Schema User has the ability to change objects in the Model Data Schema)
Exception: If the Product Schema User is an Administrator user such as “dbo” or “sa” it will already have the above privileges. In this case it is not necessary to perform the above grants.
Note: Do NOT grant the SYSADMIN role to the user associated with the HPCM product schema. It will change the default schema for that user, which must remain set as the HPCM product schema.
The Model Data Schema must be created in the same database/instance as the HPCM Product Schema.
Model Data Schema and Model Data User (Microsoft SQL Server Only)
In Oracle, a schema and a user are synonymous; in SQL Server they are separate entities. The implementation of the Model Data Schema in SQL Server requires you to create a Model Data User that has the same name as the Model Data Schema. The Model Data Schema should be the default schema for this user. For SQL Server, references to the Model Data Schema in the Profitability and Cost Management product and documentation refer to either the schema, or the user, or both.
Model Data Schema Table Structural Requirements
In order to register a table from the Model Data Schema for use in a Detailed Profitability application, you must meet the following requirements:
• Database object names must be in upper case characters, and may include digits 0-9, and characters “_” and “$”. Lower case and other special characters are not supported. In other words, if you have to enclose the table or column name in double quotes within the CREATE TABLE command in order for the identifier to be accepted, then it is not supported for use in Profitability and Cost Management. If you have existing database object names using lower case or special characters, you can create views to rename table, view, and column names using allowable identifiers so the views can be registered.
• For Destination Stage tables only, the table must have a numeric column named “WORKING” (in upper case characters).
• For Destination Stage tables only, the table must have a primary key constraint defined on it to enforce the uniqueness of the table.
Model Data Schema Table Grants to the Product Schema (Oracle Only)
In order to view database objects from the Model Data Schema within Model Data Registration, you must first grant privileges to the Profitability and Cost Management Product Schema. Grant the privileges for each table type as shown on the table below:
|
Table Type |
Privileges |
|
Source Stage Table, either Horizontal or Vertical |
GRANT SELECT ON <table_name or view_name> TO <hpm_product_schema> WITH GRANT OPTION |
|
Destination Stage Table |
GRANT SELECT, UPDATE ON <table_name or view_name> TO <hpm_product_schema> |
|
All types of Lookup Tables |
GRANT SELECT ON <table_name or view_name> TO <hpm_product_schema> |
Note: For Microsoft SQL Server, refer to the Database System Privileges Required by the Product Schema section above.
Note: For Oracle, the execute privilege on dbms_stats is required. By default, this privilege is granted to Public. If your organization has restricted collecting statistics, then you must grant this privilege to the product schema.
Using the Detailed Application Model Calculation Statistics Script
The script creates a table within the HPCM
Product Schema and stores statistics useful for troubleshooting model
calculated results problems, for describing the shape and
characteristics of the model, and for evaluating model calculation performance.
The dpmodelcalcstats.sql script is located within the
%EPM_ORACLE_HOME%\OPatch\HPCM_11_1_2_2_353_17974124\files\products\Profitability\database\Common\Oracle
directory after the 11.1.2.2.353 patch has been installed. It is currently only available for Oracle database installations.
The script is designed to be open and to run within SQL Developer. Please use the following procedure to generate the statistics for the requested application.
1. Open the dpmodelcalcstats.sql
script file within Oracle SQL Developer.
2. Select the connection for the HPCM Product Schema.
3. Move the cursor to the first line of the script.
4. Click on the Run Script toolbar icon or press the F5 key.
5. Enter the name of the application where model calculation statistics
are requested.
The script creates a table within the product schema using the following naming convention:
HPMD_<Application Name>_DIAGSTAT_<Unique Number>.
The table name for the BksDP20 application
would be HPMD_BksDP20_DIAGSTAT_4129 if 4129 is the next number from the Oracle
sequence for short-term tables
created by an HPCM detailed application.
Here is a short description of the columns within the
HPMD_BksDP20_DIAGSTAT_4129 table.
APPLICATION: The name of the application.
ITEM: A short description of the content within the row.
RATIO_DRV_TOT: The total number of items related to all of the Ratio-based drivers.
RATE_DRV_TOT: The total number of items related to all of the Rate-based drivers.
OBJC_DRV_TOT: The total number of items related to all of the Object Calculation drivers.
TOTAL: The total number of items related to all of the assignment.
NAME: The name of the artifact or object related to the item.
These types of diagnostic statistic items are included within the table:
Allocation Table:
The name of the allocation table with all of the assignment details for the specified application. If the count is greater than 1, then results are likely incorrect because clear calculations has not been run.
Number of Assignments:
The number of assignments identified within the model for the specified application.
No of source Nodes:
The number of source nodes (intersections) identified within the model.
Number of Assignments with Data:
The number of assignments where one or more rows within the source stage business object match a potential source node.
Number of row updates:
The total number of rows altered by the update statements performed for all of the assignments.
Number of Assignment Rules:
The number of assignment rule artifacts defined within the model with at least one assignment referencing the assignment rule.
Number of Drivers:
The number of driver artifacts defined within the model with at least one assignment referencing the driver.
Maximum Destination Row Count:
The maximum number of rows updated within the destination by an assignment.
Median Destination Row Count:
The median number of rows updated within the destination by an assignment.
Standard Deviation of Destination Row Count:
The standard deviation for rows updated within the destination by an assignment.
Driver Count:
There is one driver count item per driver referenced by at least one assignment. The item includes name of the driver artifact and the number of times referenced by an assignment.
Assignment Rule Count:
There is one assignment rule count item per assignment rule referenced by at least one assignment. The item includes name of the assignment rule artifact and the number of times referenced by an assignment.
Calculation Process Related Artifacts
Detailed Profitability applications utilize a new advanced construct called “Calculation Processes” to define how the model is calculated and to define certain other processing operations that are performed within the relational database. For information on the Driver Operation Types and Other Process Types, see “Advanced Calculation Options” in Chapter 4 of the Oracle Hyperion Profitability and Cost Management Administrator’s Guide.
The following Lifecycle Management (LCM) artifacts are related to Calculation Process definitions and administration:
• CalculationConfig
• Processes
• SQLTemplates
• Tasks
Because there is no supported customization option for these artifacts, when you export or import application artifacts using the Shared Services console, ignore these Calculation Process artifacts.
It is especially important to exclude these artifacts from your exports and imports when migrating an application across environments that may use different database platforms (such as Oracle or SQL Server) or different product versions. Uncheck these artifacts before exporting to exclude these artifacts from your export files.
Note: If you are importing application artifacts from a previous export that contains any of these artifacts, be sure to uncheck them before you import.
When entering a search value in a filter, enter the entire string if the filters are Attribute-based or UDA-based.
If you require a wildcard at the beginning of a filter, only question marks can be used, as in “?ac”.
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".
Note: You cannot use an asterisk at the beginning or within a filter for assignment rules, such as "*B" or “B*a”.
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 some dimension (except Alias, Attribute, UDA).
3. In the Property Grid, select the appropriate Hierarchy Type property:
• Select Stored for any dimension whose dimension members use the following consolidation symbols:
• + ADDITION
• ~ IGNORE (only underneath LABEL ONLY members.)
• Select Dynamic for any dimension whose dimension members needs to use all supported consolidation symbols, or have 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 Connection 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 for Windows
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 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters.
2. Add or modify the following registry entries:
• 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.
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.
Increasing Local Port Range for Linux
CAUTION: 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.
1. From a Linux shell, enter the following command to find the current range:
$ sysctl
net.ipv4.ip_local_port_range
Sample Output:
net.ipv4.ip_local_port_range = 32768 61000
2. Set the new local range using one of the following commands:
# echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range
OR
$ sudo sysctl -w net.ipv4.ip_local_port_range="1024 64000"
Note: The available
parameters are listed under /proc/sys/. This option is only useful for high
bandwidth, busy Linux servers or large scale grid servers.
3. To permanently modify /proc filesystem (the local port range), edit the /etc/sysctl.conf file to append the following to your /etc/sysctl.conf file:
# increase system IP port limits
net.ipv4.ip_local_port_range = 1024 65535
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. (Defect 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_HOME%\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf.
2. In the configuration file, locate the section LocationMatch/profitability:
<LocationMatch /profitability>
SetHandler weblogic-handler
PathTrim /
KeepAliveEnabled ON
KeepAliveSecs 20
WLIOTimeoutSecs 3000
Idempotent OFF
WeblogicCluster servername:6756
</LocationMatch>
3. Add the following lines within the LocationMatch/profitability section:
WLIOTimeoutSecs 3000
Idempotent OFF
4. Navigate to %Middleware_HOME%\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\htppd.conf.
5. 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 a relational database into Profitability and Cost Management, you must create a set of staging tables in a database schema that is separate from the Profitability and Cost Management product schema. (You may re-use the same schema used as the Model Data Schema for Detailed Profitability). You then populate these staging tables with the details of the application artifacts to be imported.
CAUTION: Do not modify the product schema.
Staging database scripts are available for MS SQL Server and Oracle Database. Use the appropriate script to create the import tables in a new database schema:
• For Standard Profitability staging tables, run create_staging.sql.
• For Detailed Profitability staging tables, run create_dp_staging.sql.
To create staging tables:
1. Create a new Oracle or MS SQL Server database schema, outside of the product schema.
2. Navigate to the location for the appropriate SQL script in the default location for your database type:
• %EPM_ORACLE_HOME%/products/Profitability/database/Common/MSSQLServer
• %EPM_ORACLE_HOME%/products/Profitability/database/Common/Oracle
3. Run the appropriate SQL script against the new database:
• For Standard Profitability staging tables, run create_staging.sql.
• For Detailed Profitability staging tables, run create_dp_staging.sql.
To import data and metadata using these staging tables, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.
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/technetwork/middleware/performance-management/documentation/index.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.
The new features in this patch are documented in the Profitability and Cost Management Addendum for Patch Release 11.1.2.2.350 on the Oracle Technology Network (OTN), listed in the Oracle Hyperion Profitability and Cost Management product area.
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.
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/technetwork/middleware/performance-management/documentation/index.html).
In addition, this Readme file is accessible in HTML format.
Copyright © 2012, Oracle and/or its
affiliates. All rights reserved.
http://www.oracle.com