X

Oracle Customer Engineering & Advocacy Lab (CEAL) Blog covers BI Tech, EPM, BI Cloud and EPM Cloud.

HPCM 11.1.2.2.x - How to find data in an HPCM Standard Costing database

Jane Story
Senior Principal Applications Specialist - Customer Engineering & Advocacy Lab (CEAL Team)
When working with a Hyperion Profitability
and Cost Management (HPCM) Standard Costing application, there can often be a
requirement to check data or allocated results using reporting tools e.g
Smartview. To do this, you are
retrieving data directly from the Essbase databases related to your HPCM
model. For information, running reports
is covered in Chapter 9 of the HPCM User documentation. The aim of this blog is
to provide a quick guide to finding this data for reporting in the HPCM
generated Essbase database in v11.1.2.2.x of HPCM. 

In order to retrieve data from an HPCM
generated Essbase database, it is important to understand each of the following
dimensions in the Essbase database and where data is located within them:

  • Measures dimension –
    identifies Measures
  • AllocationType dimension –
    identifies Direct Allocation Data or Genealogy Allocation data
  • Point Of View (POV)
    dimensions – there must be at least one, maximum of four.
  • Business dimensions:
    • Stage
      Business dimensions – these will be identified by the Stage prefix.
    • Intra-Stage
      dimension – these will be identified by the _Intra suffix.

Essbase outlines and reporting is explained in the
documentation here:
http://docs.oracle.com/cd/E17236_01/epm.1112/hpm_user/ch09s02.html

For additional details on reporting measures, please
review this section of the documentation:
http://docs.oracle.com/cd/E17236_01/epm.1112/hpm_user/apas03.html

Reporting
requirements in HPCM quite often start with identifying non balanced items in
the Stage Balancing report. The
following documentation link provides help with identifying some of the items
within the Stage Balancing report:
http://docs.oracle.com/cd/E17236_01/epm.1112/hpm_user/generatestagebalancing.html

The following are some types of data upon
which you may want to report:

  • Stage Data:
    • Direct
      Input
    • Assigned
      Input Data
    • Assigned
      Output Data
  • Idle Cost/Revenue
  • Unassigned Cost/Revenue
  • Over Driven Cost/Revenue
  • Direct Allocation Data
  • Genealogy Allocation Data

Stage
Data

Stage Data consists of:

  • Direct Input i.e. input
    data, the starting point of your allocation e.g. in Stage 1
  • Assigned Input Data i.e. the
    cost/revenue received from a prior stage (i.e. stage 2 and higher).
  • Assigned Output Data i.e. for
    each stage, the data that will be assigned forward is assigned post stage data.

Reporting on this data is explained in the documentation
here:
http://docs.oracle.com/cd/E17236_01/epm.1112/hpm_user/ch09s03.html

Dimension

Selection

Measures

Direct
Input:

  • CostInput
  • RevenueInput

Assigned
Input (from previous stages):

  • CostReceivedPriorStage
  • RevenueReceivedPriorStage

Assigned
Output (to subsequent stages):

  • CostAssignedPostStage
  • RevenueAssignedPostStage

AllocationType

  • DirectAllocation

POV

  • One
    member from each POV dimension

Stage
Business Dimensions

  • Any members for the stage business dimensions for the
    stage you wish to see the Stage data for.

All
other Dimensions

  • NoMember

Idle/Unassigned/OverDriven

To view Idle, Unassigned or Overdriven Costs/Revenue,
first select which stage for which you want to view this data. If multiple Stages have unassigned/idle,
resolve the earliest first and re-run the calculation as differences in early
stages will create unassigned/idle in later stages.

Dimension

Selection

Measures

Idle:

  • IdleCost
  • IdleRevenue

Unassigned:

  • UnAssignedCost
  • UnAssignedRevenue

Overdriven:

  • OverDrivenCost
  • OverDrivenRevenue

AllocationType

  • DirectAllocation

POV

  • One
    member from each POV dimension

Dimensions
in the Stage with Unassigned/ Idle/OverDriven
Cost

  • All the Stage Business dimensions
    in the Stage with Unassigned/Idle/Overdriven.
  • Zoom in on each dimension
    to find the individual members to find which members have Unassigned/Idle/OverDriven
    data.

All
other Dimensions

  • NoMember

Direct
Allocation Data

Direct allocation data shows the data
received by a destination intersection from a source intersection where a
direct assignment(s) exists.

Reporting on direct allocation data is explained in the
documentation here:
http://docs.oracle.com/cd/E17236_01/epm.1112/hpm_user/ch09s04.html

You would select the following to report
direct allocation data

Dimension

Selection

Measures

  • CostReceivedPriorStage

AllocationType

  • DirectAllocation

POV

  • One
    member from each POV dimension

Stage
Business Dimensions

  • Any members for the SOURCE stage business dimensions and
    the DESTINATION stage business dimensions for the direct allocations for the stage
    you wish to report on.

All
other Dimensions

  • NoMember

Genealogy
Allocation Data

Genealogy allocation data shows the indirect
data relationships between stages. Genealogy
calculations run in the HPCM Reporting database only.

Reporting on genealogy data is explained in the
documentation here:
http://docs.oracle.com/cd/E17236_01/epm.1112/hpm_user/ch09s05.html

Dimension

Selection

Measures

  • CostReceivedPriorStage

AllocationType

  • GenealogyAllocation for releases prior to 11.1.1.3.500
  • IndirectAllocation
    for all releases 11.1.1.3.500/11.1.2.x and after

POV

  • One
    member from each POV dimension

Stage
Business Dimensions

  • Any stage business dimension
    members from the STARTING stage in Genealogy
  • Any stage business dimension
    members from the INTERMEDIATE stage(s) in Genealogy
  • Any stage business dimension
    members from the ENDING stage in Genealogy

All
other Dimensions

  • NoMember

Notes

If you still don’t see data after checking
the above, please check the following

  1. Check the calculation has
    been run. Here are couple of indicators that might help them with that.
    • Note
      the size of essbase cube before and after calculations ensure that a
      calculation was run against the database you are examing.
    • Export
      the essbase data to a text file to confirm that some data exists.
    • Examine
      the date and time on task area to see when, if any, calculations were run and
      what choices were used (e.g. Genealogy choices)
  2. If data does not exist in
    places where they are expecting, it could be that
    • No
      calculations/genealogy were run
    • No
      calculations were successfully run
    • The
      model/data at feeder location were either absent or incompatible, resulting in
      no allocation e.g no driver data.

Smartview
Invocation from HPCM

From version 11.1.2.2.350 of HPCM (this
version will be GA shortly), it is possible to directly invoke Smartview from
HPCM. There is guided navigation before the
Smartview invocation and it is then possible to see the selected value(s) in
SmartView.

Click to Download HPCM 11.1.2.2.x - How to find data in an HPCM Standard Costing database (Right click or option-click the link and choose "Save As..." to download this pdf file)

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