Oracle Customer Engineering & Advocacy Lab (CEAL) Blog covers Oracle Analytics Cloud, Oracle Analytics Server and...

Highlights of HPCM New Features

Jane Story
Senior Principal Applications Specialist - Customer Engineering & Advocacy Lab (CEAL Team)

The latest release of HPCM provides several
new features as well as performance improvements.

V11.1.2.3 provides the following:

  • Standard Profitability – Smart
    View Integration
  • Detailed Profitability – new
    calculation rules
  • Detailed Profitability –
    Essbase Integration
  • Detailed Profitability – Stage
    Balancing Report

Standard Profitability – Smart View Integration

There is now Smart View integration
included within the HPCM Standard Costing user interface. This will provide a dramatically reduced
learning curve for reporting as the integration takes you to the correct
combination of dimension members within Smart View. This means that less time is required to see
meaningful data.

Within the Stage Balancing report, numbers
on the report will now show as data point hyper links. Click once and a Smart View will open showing
the relevant data point in your spreadsheet.

It is also now possible to create custom
queries in HPCM that can be launched in Smart View from the new “Manage Query”
screen in the new “Reporting” Task Area.

  • Queries are easily set up using
    a setup wizard covering query options, dimension layout and Member Selections
  • Queries can be saved and
    accessible to any user. One click takes
    you to Smart View.
  • Can be used for Profitability
    analysis, Contribution Analysis.

Detailed Profitability – Calculation Rules

New Calculation Rules have been added to
Detailed Profitability in v11.1.2.3. These rules provide far more efficient modelling which should in turn
provide simpler, faster model design as well as model maintenance. Faster calculation times may also be seen.

New Calculation Rules are visible in a new
Task Area within “Manage Calculations” and allow the definition of assignment
logic for groups of sources at once. The current single source methods are still supported for exceptions.

Calculation rules combine driver
definitions to define the function to be performed with a source assignment
rule to define the sources and destination assignment rules to define the
destination to receive the output of the allocation.

Calculation rules can provide more
processing control as rules can be single or multi source. The rule’s sequence number can control the
order of the calculation.

Detailed Profitability – Essbase Integration

This Essbase Integration will enable users
to use Smart View to analyse data in Detailed Profitability. This means far quicker access to meaningful
data and helps to provide a quicker reporting learning curve.

From v11.1.2.3, there will be Essbase
integration included for Detailed Profitability. 3 ASO databases will be generated for each
model: one for the Source Stage, one for Contribution Detail between Stage 1
and 2 and one for the Destination Stage.

Deployment of the new Essbase Integrated
databases will be similar to the Essbase Deploy screens in Standard

Detailed Profitability – Stage Balancing Report

New Stage Balancing reports for Detailed
Profitability can provide customisable balancing views to match user customisations
of the destination stage as a datamart. This will help to make the stage balancing report a much more meaningful
report for users.

From v11.1.2.3, there will now be a stage
balancing report for Detailed Profitability.

The Stage Balancing Report for Detailed
Profitability will differ from Standard Costing as target measures are part of
the driver. The user must choose all the
target measures for Stage 1 and 2 to appear on the screen.

For Further Information

For further information on HPCM new
features, please see the v11.1.2.3 New Features guide: http://docs.oracle.com/cd/E40248_01/epm.1112/hpm_new_features.pdf

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.