Copyright © 2009, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Table of Contents:
This document describes the new features and enhancements in Oracle Hyperion Profitability and Cost Management, Fusion Edition Release 188.8.131.52.
Information about system requirements for EPM System products is now available in a spreadsheet format in the Oracle Hyperion Enterprise Performance management System Certification Matrix. This matrix is posted at http://www.oracle.com/technology/products/bi/hyperion-supported-platforms.html.
System requirements are no longer part of the Oracle Hyperion Enterprise Performance Management System Installation Start Here.
In addition to the supported operating systems in Release 11.1.1, the following operating systems are now supported in Profitability and Cost Management:
HP-UX 11i with PA.RISC processor
Solaris with SPARC processors
These operating systems are supported for Browser-based clients only:
Oracle Enterprise Linux 32-bit version (4.0.x to 5.0 client)
Redhat Linux 32-bit version (AS/EL 4.0.x to AS/EL 5.0.x client)
For detailed instructions on planning and configuring your installation, see the following guides:
Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide
Oracle Hyperion Enterprise Performance Management System Installation Start Here
There are a number of changes to Profitability and Cost Management metadata, and dimensions and member properties, as outlined in this document. For additional details, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.
With this release of Profitability and Cost Management, the following changes have been applied for metadata:
The consolidation for NoMember members is now set to “~” (Ignore).
The following members are now aligned under AllAllocations:
The following new members have been added under AllocationType to accommodate the calculation of genealogy with intrastage assignments:
These new members are system variables, used internally for intrastage calculations. DO NOT modify these members.
The Dimension Sort Order property controls the order of dimensions in the Oracle Essbase outline that is generated by Profitability and Cost Management. The dimension sort order must be set on all dimensions within a model, except Alias and UDA. If the sort order for any dimension is left blank, the validation will fail.
The Dimension Sort Order property is set in Oracle Hyperion EPM Architect, Fusion Edition, and passed on to Profitability and Cost Management during deployment for use in generating the Essbase outline.
There are specific sequence requirements for the sort order, and the settings for the model are validated in Performance Management Architect. The following restrictions apply when setting the Dimension Sort Order property:
A dimension sort order must be set for every dimension in the model, except Alias and UDA.
The dimension sort order must be sequential.
Measure dimension is set to 1, by default.
AllocationType dimension is set to 2, by default.
Business and POV dimensions must be set to 3 or higher.
Attribute dimensions must always be sorted as the last dimensions. For example, if you have four attribute dimensions in a sequence of 12 dimensions, the attribute dimensions must be set as 9, 10, 11, and 12.
For Dimension Sort Order requirements, and instructions on setting the sort order, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.
For all business dimensions in the model, you must reorder the list of members to display NoMember as the last member; otherwise, validation of the model will fail. You can also reorder members to suit your particular requirements.
This step is not required for system dimensions, such as Alias, AllocationType, Measures, Periods, Scenarios or Years.
For additional information, see the Oracle Hyperion Profitability and Cost Management Administrator’s Guide.
The member "UserDefinedDriverMeasures" hosts the application specific driver measures.
Set the properties for ASOMemberDataStorage and BSOMemberDataStorage as follows:
If the member does not have any children, set its properties ASOMemberDataStorage and BSOMemberDataStorage to StoreData.
If members are added as children to the member and all these children have the consolidation symbols of IGNORE, set the properties ASOMemberDataStorage and the BSOMemberDataStorage properties to LabelOnly.
A number of Profitability and Cost Management properties were renamed for this release, as outlined in the following table:
Table 1. Modified Profitability and Cost Management Properties
|Original Property Name||Revised Property Name|
For additional information and a complete list of Profitability and Cost Management properties, including the new Dimension Sort Order property, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.
Allocation Measures in a Profitability and Cost Management model are used internally by the application, and are not modeling dimensions. Previously, they had to be set as “Excluded from Modeling” calculations in the Dimension Library Property Grid, but with this release, this setting is no longer required .
Two Performance Management Architect dimension types are available for use in Profitability and Cost Management:
The Account dimension type contains chart of account type information, such as Net Income and Sales, in applications.
The Entity dimension type provides entity or organizational structures in applications.
Only one dimension of each type may exist in a model. For additional information on dimension types, see the Oracle Hyperion Enterprise Performance Management Architect Administrator’s Guide.
Aliases are now available in Profitability and Cost Management, to provide an alternate name, description, language, or other item to define dimensions. For example, you may refer to a customer number in the system, but you can assign an alias that displays the company name to make it easier to identify that client. For Profitability and Cost Management, the alias must be set in Performance Management Architect.
You can assign one alias per member to accounts, currencies, entities, scenarios, periods, versions, years, and user-defined dimension members. The alias is stored in the ‘Default’ Alias table. You can view the alias on all screens that use the Common Member Selector, including Driver Selections, Assignments, Data Entry, Driver Exceptions and Traceability. Search and filtering on aliases is not currently available.
If you select Show Alias from the Context Menu, and no alias has been assigned, [noalias] is displayed in the list of members.
For detailed instructions on creating Alias dimensions, see the Oracle Hyperion Enterprise Performance Management Architect User’s Guide.
The Version dimension type is now available in Profitability and Cost Management. Using the Version dimension, you can create and maintain separate versions of the same application to monitor the impact of changes to the model, or track variations .
Use the Version dimension to perform the following tasks:
Create multiple iterations of a model, with slight variations, such as preliminary and final
Model possible outcomes based on assumptions, or “what-if” scenarios to determine best or worst case scenarios
Facilitate target setting
The version dimension type is selected in Performance Management Architect from the Dimension Library. For detailed instructions on creating Version dimension, see the Oracle Hyperion Enterprise Performance Management Architect Administrator’s Guide.
Time, Country and Currency dimensions are available in Performance Management Architect for use in Profitability and Cost Management applications; however, these dimensions are not validated during the Profitability and Cost Management deployment. See the Oracle Hyperion Enterprise Performance Management Architect Administrator’s Guide.
Two new driver measures have been added to the AllocationMeasures hierarchy in this release:
Unit Cost – The formula uses the amount of cost at a source intersection, divided by a user-input quantity to calculate the cost per unit.
CostPerDrvUnit – This formula uses the assigned cost, divided by the sum of all driver values to calculate the cost for each unit of driver value.
See Appendix A, Measures Dimension, in the Oracle Hyperion Profitability and Cost Management User’s Guide for more information.
Dimension staging tables can no longer be used to create and manage dimensions. All dimensions must now be created and managed in Performance Management Architect. For detailed instructions about creating and managing dimensions, see the Oracle Hyperion Enterprise Performance Management Architect Administrator’s Guide.
Model data and metadata for the import can still be imported in the following staging tables:
The new HPM_STG_ASGN_RULE_SELECTION staging table stores details about the source stage and dimension members for an assignment rule, and is used to import assignment rule selections.
For information about importing data and metadata through staging tables, and to see the staging table schemas, refer to the Oracle Hyperion Profitability and Cost Management Administrator's Guide.
An Administrator can create new database views in the system database that mirror the columns used in the staging tables, showing the model data that is stored in the system:
Driver Selections (HPM_STG_DRIVER_SELECTION)
Assignment Rules (HPM_STG_ASGN_RULE_SELECTION)
The database views are currently available using MS SQL Server and Oracle databases. You must run a separate query for each database view that you want to create.
To create database views:
Locate the Database Views in the following default location for your database type:
Hyperion Home/products/Profitability/database/Common/Oracle 2
Run a query to create a database view against your Profitability and Cost Management database.
Open the view to display all columns for the view, and associated data.
When creating a Profitability and Cost Management Application, the path to create a new application has been modified.
To create a new Profitability and Cost Management application:
On the Oracle Enterprise Performance Management Workspace, Fusion Edition main menu, select the Navigate icon , then Administer, and then Dimension Library to access Performance Management Architect and create the dimensions required for the first application.
For detailed instructions on creating dimensions, see the Oracle Hyperion Enterprise Performance Management Architect Administrator’s Guide.
Any business dimensions to be included in the application, for example, Generic, Account, Entity, or Country, must be added to the Dimension Library before creating the application; otherwise, the dimensions will not be available for the Application Wizard to select.
After the dimensions have been selected for Profitability and Cost Management, select Navigate, then Administer, and then Application Library.
From the Application Library, select File, then New, and then Application to create a new Profitability and Cost Management application.
Continue to create the application by selecting the application type, selecting dimensions, modifying the application settings, and validating and deploying the new application.
See the Oracle Hyperion Profitability and Cost Management Administrator’s Guide for detailed instructions on creating and working with applications.
There are several new model validations that have been added for this release:
There is only one dimension of type Account.
There is only one dimension of type Entity.
NoMember must be set as the last member for all business dimensions. This requirement does not apply to Alias, AllocationType, Measures, Periods, Scenarios or Years.
NoMember must be set to Ignore (~) in the Property Grid.
Dimension Sort Order has been set for the model. A sequential dimension sort order must be set for every dimension in the model, except Alias and UDA dimensions. See the Oracle Hyperion Profitability and Cost Management Administrator’s Guide for more information.
A duplicate dimension member does not exist in the same dimension. This validation does not apply to Measures, Allocation Type and POV dimensions.
For additional information, see the Oracle Hyperion Profitability and Cost Management Administrator’s Guide.
All driver measures must be unique in the outline. Do not use the existing name of any driver measure in any dimension in the outline (including system, POV and business dimensions) as the name of another member; otherwise, the Data Entry screen will not properly display the values.
A typical Profitability and Cost Management application contains a few business dimensions, a few POV dimensions, one Measures dimension and one AllocationType dimension. Profitability and Cost Management duplicates business dimensions if they are used in more than one stage. This process increases the Sparsity of the Essbase Calculation Cube outline generated by the application, and may have a performance impact when the calculation scripts are run. For more information, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.
Some optimization can be achieved simply by changing the Dimension Storage Type directly for the generated Calculation Cube outline, using Oracle Essbase Administration Services (EAS) console.
Changes to the Dimension Storage Type property should only be performed by a Database Administrator (DBA). For detailed instructions, refer to the Oracle Essbase Administration Services Developer's Guide.
When naming elements within Profitability and Cost Management, there are a number of naming restrictions that must be followed to avoid any problems within the application.
A new Appendix B, Essbase Naming Conventions, has been added to the Oracle Hyperion Profitability and Cost Management Administrator's Guide to provide an overview of naming conventions for the following items:
Generated Calculation Script Naming Conventions
Essbase Naming Restrictions for Applications and Databases
Essbase Naming Restrictions for Dimensions, Members and Aliases
This appendix is intended to provide lists of the most common restricted characters; however, Oracle strongly suggests that you review the Essbase naming conventions described in the Oracle Essbase Database Administrator's Guide for a complete list.
A Delete tab has been added to the POV Management screen to provide users with the means to easily delete assignments and driver associations for a selected POV, layer and list of stages.
For detailed instructions on deleting POVs, see the Oracle Hyperion Profitability and Cost Management User's Guide.
Several enhancements have been applied to genealogy calculations, as outlined in the following sections.
Previously, when calculating genealogy data, it was not possible to calculate the value of intrastage assignments because there were missing links in the calculation path. With this release of Profitability and Cost Management, "virtual links" are created in the model to enable the required paths for the genealogy algorithm.
The virtual links are stored in the updated Essbase outline under the AllocationType dimension, using the following new members:
SysAllocVar1 stores the value on the virtual link, which is part of the value allocated to another node on the same stage, and already available in the DirectAllocation member.
SysAllocVar2 is used to obtain a sum of the source links of DirectAllocation, GenealogyAllocation and SysAllocVar1.
These are system variables, used internally for intrastage calculations. DO NOT modify these members.
It is now possible to calculate genealogy for revenue allocations, including intrastage reciprocals.
Profitability and Cost Management performs two calculations: direct allocation and genealogy. The direct allocation data is required to complete genealogy calculations, so it must be calculated first.
To improve the processing time to obtain genealogy results, you must transfer direct allocation data to the reporting cube before starting genealogy calculations. During calculation, the calculated genealogy data is automatically loaded into the reporting cube. This method takes significantly less time than performing the calculations in the calculation cube.
For detailed instructions on calculating genealogy, see the Oracle Hyperion Profitability and Cost Management User's Guide.
Two new optimization levels are available, and are selected based on the size and complexity of your model. The full-matrix, source-based and allocated-based optimization levels are no longer available.
From the Manage Calculation screen, select the Optimization level from the drop-down list at the bottom of the Genealogy tab:
Select Classic to create allocation-based calculation scripts for most models. This calculation uses calculation scripts in the BSO cube, and data is transferred to the ASO cubes using the normal data transfer process..
Select Native to use Java-based genealogy calculations for large models. This calculation is performed on the ASO database only.
The Genealogy data for a POV is cleared each time before genealogy calculations are run:
For Classic genealogy calculations, both the Calculation (BSO) and Reporting (ASO) cubes are cleared.
For Native calculations, only the Reporting (ASO) cube is cleared.
Only genealogy data for a particular POV is erased; all other data remains unchanged.
To optimize processing of very large generated genealogy calculation scripts, Profitability and Cost Management may automatically split the calculation scripts into smaller sections for actual processing. The calculation scripts are executed on Oracle Essbase in the order in which they are created, to maintain the original sequence in which the sources are allocated. This process is important for intrastage assignments.
All the scripts contribute to the final genealogy calculation, but are displayed separately. A separate script name and number are appended to each split script, for example, g123c000.csc, g123c001.csc, g123c002.csc, and so on. The script splitting does not affect results of the final genealogy calculations.
When tracing allocations, you can now select different ways to view the information, as follows:
Tracing Allocation Detail enables you to follow allocations step-by-step from a source intersection to its ultimate destination, or from a destination intersection to its source. The intersections that contribute to, or receive value from the starting point show the stage and associated members.
Tracing Allocation Flow displays the source and destination intersections that have an indirect relationship, to the selected intersection, rather than a direct assignment. For example, you may have values from Stage 1 allocated to Stage 3, without any intermediate steps. By following the flow of each allocation, you can examine the contributions from the source at each step, to understand the impact of an allocation on its ultimate source or destination.
For instructions on tracing allocations, and the formulas that apply to each option, see the Oracle Hyperion Profitability and Cost Management User’s Guide.
Assignments specify where allocation results are directed. Frequently, models include multiple assignments that use the same parameters. To simplify the creation of multiple assignments that are similar in nature, you can create and reuse assignment rules that specify the assignment parameters.
An assignment rule is a collection of member sets and optional filter sets for a single destination stage. A filter is a collection of criteria that are applied to a dimension. The rules are created based on one or more of the following criteria:
Membership in a specific branch of the dimension hierarchy
UDAs (User-defined attributes)
For information on creating and using Assignment Rules, see the Oracle Hyperion Profitability and Cost Management User's Guide.
With this release, it is now possible to edit an existing assignment rule and save it as a new rule. Previously, only the content of a rule could be changed, but you can now change both the rule name and its contents.
With the new Save As option, you can create assignment rules, as follows:
Edit an existing rule, and save as a new rule.
Edit an existing rule, modify its contents, and rename the rule.
For detailed instructions on saving an existing assignment rule as a new rule, see the “Modifying Assignment Rules” section in the Oracle Hyperion Profitability and Cost Management User's Guide.
In certain situations where the destination target changes only slightly, and changes are related to the source’s dimensionality, unique assignment rules have to be created for each source. Instead of having to create individual assignment rules for each source, Same as Source assignment rules enable you to use a wildcard to dynamically change the assignment rule’s destination member choices as you move from source to source.
For detailed instructions on creating same as source assignment rules, see the Oracle Hyperion Profitability and Cost Management User's Guide.
A new Oracle's Hyperion® Shared Services Client-side log file provides details regarding security settings. By default, the log file is available at HYPERION_HOME/logs/hpm.
You can monitor activity and changes in your application using the Audit feature in the Oracle's Hyperion® Shared Services Console, and generate audit reports detailing the results. Auditing must be enabled before you can generate any reports. For instructions on enabling the Audit feature, see the Oracle Hyperion Profitability and Cost Management Administrator’s Guide.
There are three types of audit reports available, including Security Reports, Artifact Reports and Config Reports. These reports can be exported as .CSV files.
The audit reports contain activity details for the selected audit area, including the following information:
Artifact type and name
Task that was performed
For instructions on generating audit reports, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide.
You can create an import file from an existing Profitability and Cost Management application in Performance Management Architect. The Performance Management Architect File Generator must be installed with the EPM System Installer.
For detailed instructions on using and installing the utility, see the Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition File Generator User's Guide.
To create an import file for an existing Profitability and Cost Management application:
Select Start, then Programs, then Oracle EPM System, then Foundation Services, then Performance Management Architect, and then Start EPMA File Generator.
The Performance Management Architect File Generator utility is displayed.
Click From EPMA Application.
Enter the following information:
User name and password used for logging in to Oracle Enterprise Performance Management Workspace, Fusion Edition
Performance Management Architect Web Services URL
Oracle Hyperion Profitability and Cost Management, Fusion Edition application name
Location where the import file is to be saved
Optional: Dimension prefix
The .ads file is created, using the application as the source. A successful message is displayed under Status.
The following Performance Management Architect features are new for this release:
Database administrators can now populate the i_Load_ID column in the IM_Load_Info interface table to enable filtering on dimensions and members imported into Performance Management Architect. After the i_Load_ID column is populated, you can enter a load ID to filter artifacts from the interface tables when you create an import profile or import dimensions in Performance Management Architect.
Performance Management Architect Transaction History Purge Utility
Performance Management Architect creates transactions in the Performance Management Architect database. Since the database size can increase over time, you can use the Transaction History Purge Utility to remove transactions from the database and reduce database size.
Performance Management Architect Batch Client
The Batch Client provides a command-line interface that allows Performance Management Architect tasks to be scripted and run in a lights-out fashion. These Batch Client commands are new for this release:
The Oracle Hyperion Enterprise Performance Management Architect Batch Client User's Guide describes all Batch Client commands.
Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle
You can use ERP Integrator to push metadata and data from an Enterprise Resource Planning (ERP) source system into Oracle Hyperion EPM Architect, Fusion Edition target applications.
The Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Administrator's Guide describes all features of Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle.