This document describes the new features and enhancements in Oracle Hyperion Profitability and Cost Management Release 18.104.22.168.120, Release 22.214.171.124.110, 126.96.36.199.100, and 188.8.131.52.000. For detailed information on these features, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide and Oracle Hyperion Profitability and Cost Management User's Guide.
For new features in Oracle Hyperion EPM Architect, refer to the Oracle Hyperion Enterprise Performance Management Architect Readme.
A new option to include input data is added to the Templates Export/Import feature. When Include Input Data is checked in the Export Template dialog, the input data for all selected POVs is included in the export. On the Import Template dialog, if input data is present in the template file being imported, the Import Input Data checkbox is enabled and input data for all selected POVs can be imported. The database cube is always automatically deployed now, whether or not the input data is imported.
LCM Export for Profitability and Cost Management applications now enables you to export an application's dimension metadata along with the other model artifacts into a single LCM export file. An LCM export file that includes dimension metadata can be imported into a new empty application that has been created previously in the Profitability Applications Console.
The target application you create in Profitability Applications Console is created with a Native application source type. If the source application was initially created in EPM Architect and you want to keep the target application as EPM Architect source type, use EPM Architect LCMs to migrate the dimensions.
Likewise, if the source application has the Master Cube source type and you want your target application to also have a source type of Master Cube, copy the dimension master cube to the target environment and use the Essbase Master Cube approach to create the target application.
Starting with this release, Profitability and Cost Management REST API version 184.108.40.206.000 is replaced by version V1. Version 220.127.116.11.000 is disabled by default. Oracle strongly recommends that you migrate to version V1. If you need more time to migrate, contact Oracle Support for how to temporarily enable REST API version 18.104.22.168.000. The Profitability and Cost Management REST Web Services API version V1 differs from version 22.214.171.124.000 in the following ways:
The Request Payload object has been changed to JSON format.
For all GET type resources, the Request Payload object is passed as a query parameter.
For other resources, the Request Payload object is passed as separate object outside the URI (Uniform Resource Identifier).
The Response object is now exposed as a JSON object and includes more details.
Exception and error messages are streamlined according to Oracle standards.
The URI has changed for DP Reporting Views Generation, Run DP Calculation and Run SP Multi POV Calculation.
Please refer to the Oracle Profitability and Cost Management REST API Developer’s Guide V1 for more information and examples on using the new REST API version.
For Management Ledger applications, you can now use the Profitability Applications Console to export an entire Profitability and Cost Management application, including application metadata, dimension metadata, and program artifacts. Exporting takes place in a single operation and produces a single application "template" file with extension .zip. This feature is useful for backing up applications or for migrating them to another environment.
The Export Template option is available from the Actions menu after selecting a Management Ledger application.
Import Template is always available from the Actions menu. This command creates a new application.
For details, see the Hyperion Profitability and Cost Management Administrator's Guide for release 126.96.36.199.110, Appendix B.
Introduced in release 188.8.131.52.000, the REST API is available to automate processes with scripts instead of action by on-site personnel. This release contains the following enhancements to support the export and import of Management Ledger template files:
The Export Template resource is added to export Profitability and Cost Management Management Ledger applications as a single template file with extension .zip for later import. Files are exported to an import_export folder on the server.
The Import Template resource is added to import Profitability and Cost Management Management Ledger applications exported with the Export Template resource or Profitability Applications Console option on the Actions menu. Importing creates a new application that contains the same metadata and artifacts as the exported application.
For more information, see the Oracle Hyperion Profitability and Cost Management REST API Developer’s Guide Version 184.108.40.206.110.
Profitability and Cost Management tasks now can be incorporated into Oracle Hyperion Financial Close Management schedules and templates. Users of Financial Close Management can create Profitability and Cost Management workflows or include Profitability and Cost Management tasks in workflows with other Oracle Enterprise Performance Management System (EPM) and non-EPM products to create an end-to-end workflow management solution for all EPM solutions. Users of Financial Close Management can find tasks assigned to them within a Financial Close Management schedule, access appropriate Oracle Hyperion Financial Close Management screens directly from the scheduler, perform the necessary tasks, and update their scheduled tasks with a status change. For more information, see the Oracle Hyperion Financial Close Management User's Guide.
The Profitability Application Console, formerly known as the Application Manager (AAM), now supports dimension load using flat files for Management Ledger applications. The Console allows users to create shell applications, load dimensions, and validate and enable applications for use with Profitability and Cost Management.
The Profitability Application Console has a simplified user interface and Job Library.
Users can choose one or more data files to load data into a Management Ledger calculation cube after it has been deployed. This feature uses the same data file formats supported by Essbase Administration Services (EAS) Console and data load rules.
Upgrade SQL scripts for Profitability and Cost Management patches now run automatically as needed when restarting the Profitability service after applying a patch that requires a database upgrade. A manual rollback script is also included. See patch readmes for details.
This new system report for Management Ledger applications assists users in validating the data present for the key elements in a calculation rule. For the selected rule, it shows all of the dimension intersections for the source and for the driver, along with the source or driver input value that is used to calculate the rule, for each intersection.
Management Ledger application users can check a new box in the Manage Calculation screen to request that the Essbase commands issued to calculate each rule be written to files on the server, one file per rule. This provides quick access to Management Ledger calculation instructions for troubleshooting calculation issues.
The Profitability Application Console and Management Ledger Job Libraries now have a Save button in the message pop-ups so users can save the messages to a file. This is useful for multiple errors in Essbase Data Load and for Validation and Impact Analysis messages.
Introduced in release 220.127.116.11.000, the REST API is available to automate processes with scripts instead of action by on-site personnel. This release contains the following enhancements:
The Prepare Detailed Views for Reporting (DP) resource is enhanced to create all DP reporting tables and views for one application in a single call, instead of requiring a separate call for each dimension.
The Essbase Data Load resource supports the new Essbase Data Load feature in the Manage Calculation screen.
The following resources support the new flat file dimension load feature for Management Ledger applications: Create File based HPCM Application, Enable File based Application, Update File based Application using a Flat File.
Dimension flat files are now packaged with sample application BksML12 so users can create the Management Ledger sample model using the File Import method. The HPCM Sample Models Readme.docx file is updated with instructions. For the location of these files, see Chapter 2 of the Oracle Hyperion Profitability and Cost Management User's Guide.
A new application type, Management Ledger, offers management reporting and modeling with data structured similarly to Oracle General Ledger and Oracle Hyperion Financial Management implementations. You define allocations and other calculations required for management reporting outputs using a more free-form approach than is supported in Standard Profitability models. In Management Ledger models, there is no concept of stages or layers. All structure is controlled through the organization of rule sets and rules under points of view (POVs).
As in other application types, POVs represent a specific instance of the model, and can be used to view or calculate different versions of a model; for example, to view values for different months or quarters, to compare budget versus actual figures, or to play scenarios to measure the impact of various changes on the bottom line. For each POV, calculation rules are organized into groups that run against the same or similar region of the database and at the same or similar time. These groups are called rule sets. They determine the order in which calculation rules run. Calculation rules can inherit default member selections from the POV or rule set level so users can define a region of the database once and use it many times without having to specify it each time. These defaults are called “contexts”.
Task areas in the user interface support validation, rule balancing, allocation tracing, reporting, and queries.
The Profitability Applications tool, Job Library, LCM tool, and other features used for all application types now support Management Ledger applications.
System reports are now available for all application types, as follows: Dimension Statistics and Execution Statistics reports are available for Management Ledger, Standard Profitability, and Detailed Profitability models; the Genealogy Statistics report is available for Standard Profitability models; and the Program Documentation report is available for Management Ledger models.
To generate system reports, select System Reports in the Reporting task area.
You can now use SQL scripts to set up model data for Detailed Profitability sample model BksDP30 in Microsoft SQL Server. A new file called BksDP30_SQL_Scripts_SqlServer.zip has been added to the samples\BksDP30 directory. Instructions for using these scripts with SQL Server are included in the HPCM Sample Models Readme.docx file.
Representational State Transfer (REST) APIs are now available for all application types for automating processes in the production environment, such as deploying Oracle Essbase cubes or transferring data, with scripts instead of action by on-site personnel. The REST APIs can also be used for basic task processing such as running calculation rules. For details, see the REST automation documentation posted with other Oracle Hyperion Profitability and Cost Management documentation on http://www.oracle.com.
Use the Cumulative Feature Overview tool to create reports of new features added in prior releases. This tool enables you to identify your current products, your current release version, and your target implementation release version. With a single click, the tool quickly produces a customized set of high-level descriptions of the product features developed between your current and target releases. This tool is available here: