Oracle® Hyperion Profitability and Cost Management

Addendum

Release 11.1.2.2.350


Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

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 is software or related documentation that 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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware 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:

Smart View Integrations for Standard Profitability

Profitability and Cost Management Application Manager

Smart View Integrations for Standard Profitability

Oracle Hyperion Smart View for Office integrations are available for Standard Profitability models only to provide help with data management, run diagnostics for allocation data, and enable analysis of both allocation and genealogy data. In addition, the Smart View integration provides context-sensitive investigation tools that can be launched from Stage Balancing.

Smart View queries provide users with quick access to views of Oracle Hyperion Profitability and Cost Management data. The queries can be defined against either the Calculation or Reporting database, and after Smart View 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 Smart View POV. The queries can be saved and reused, or cloned by other Profitability and Cost Management users. The queries can also be exported and reimported using Oracle Hyperion Enterprise Performance Management System Lifecycle Management.

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) and the stage combinations in order to complete the dimension defaults that are presented on the dimension layout and member selection screen.

You can also launch some predefined Smart View integrations from the Stage Balancing screen. The launch data points are represented as hyperlinks in the Stage Balancing screen and present values that have been contributed from one stage to another. You can 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 Smart View queries that reference those dimensions become invalid. The Smart View query validation screen validates all queries, and displays an error message for any invalid queries.

Only users provisioned as Admin or Power users may create, edit, copy, or delete queries. Admin, Power and Interactive users may all launch queries from the application.

See the following sections to work with Smart View queries:

Creating Custom Smart View Queries

  To create Smart View queries:

  1. Before creating the query, ensure the following products are installed, configured and running:

    • Oracle Hyperion Provider Services

    • Oracle Hyperion Shared Services

    • Oracle Essbase

    • Microsoft Excel is installed with Smart View on the client machine

  2. From the Task Area, select Reporting, and then Manage Queries.

    The Smart View screen is displayed, showing all existing queries for all applications for which the user is provisioned as an Admin or Power user.

    The Smart View screen displays existing Smart View queries.
  3. Click the Add button  Add button to open the Smart View wizard.

    Enter the Query options for the Smart View query.
  4. On Step 1: Query Options, enter the following information for the new query:

    • Name for the query

    • Optional: Description of the query

    • Select the Application to be used for the query from the drop-down list

    • Select the Database to be used for the query from the drop-down list:

      • Calculation (BSO)

      • Reporting (ASO)

    • Optional: Enter a descriptive Search Tag to be used to sort queries in the main Smart View Query screen.

  5. Under Type, select the type of query to be created:

    • Driver Measures

    • Stage Measures

    • Contribution

    • Custom

    Depending on the Type that is selected, the additional query options change to reflect the choice. See Table 1, Query Type Options.

  6. Select the Query Options based on the selected Type:

    Table 1. Query Type Options

    Query Type SelectedTypeQuery Options
    Driver MeasuresAssignmentSelect the Source and Destination stages.
    Driver MeasuresSource

    Select the Source stage.

    Driver MeasuresDestinationSelect the Destination stage.
    Driver MeasuresGlobalN/A
    Stage Measures Select the Stage to be used for the query.
    ContributionDirect AllocationSelect the Source and Destination Stages.
    ContributionGenealogySelect the Contribution Path (for example, 1-3-5).
    Custom Select as required. No default is expected.
  7. Optional: Under Smart View Options, select Suppress #Missing to set the data suppression option for the first query in Smart View, if required.

    Note:

    If you select Suppress #Missing, the Smart View option is only set for the first query run, not all queries. To set the option for subsequent drills into the data, set the option manually in Smart View.

  8. Optional: Under Smart View Options, select Use Dimension Aliases to display any assigned aliases for all dimensions in the query.

  9. Click Next.

    Step 2 - Dimension Layout is displayed.

    Select the Dimensions to be used in the query, and the appropriate Dimension Position.
  10. Under Dimensions, for each Dimension, select the Position for the placement of the dimension under the Dimension Position column on the screen using the drop-down list:

    • Smart View POV

    • Rows

    • Columns

    By default, all dimensions in the application outline are displayed, and selections are set to defaults that are appropriate for the type of query you are creating.

    For example, if you select stage measures for a specific stage, the dimensions for that stage display in the Rows section, and the top member of the first hierarchy is pre-selected for each of the stage dimensions. The other stage dimensions are placed in the Smart View POV section, and the “NoMember” member from each stage is selected.

  11. Optional: Under Dimension Position, in the Smart View POV section, use the Up and Down arrows to change the position of a highlighted dimension in the query.

  12. Optional: Under Dimension Position, in the Rows section, use the Up and Down arrows to change the position of a highlighted dimension in the query.

  13. Optional: Under Dimension Position, in the Columns section, use the Up and Down arrows to change the position of a highlighted dimension in the query.

  14. Click Next.

    Step 3 - Member Selections is displayed. All dimensions from the Smart View POV, Rows and Columns are displayed in the order defined on the Dimension Layout screen. Use the arrows to scroll up or down through the list.

    Select dimension members that are to be used in the query.
  15. Under Dimension Member Selections, use the Add arrowAdd arrow to move the dimension members to be included in the query to the Selected Dimension Members column.

    The list displays all dimension members, including alternate hierarchies and the NoMember member. Because there are no restrictions on level, alternate hierarchy, shared or base member, any member may be selected.

    Use the Ctrl key to select multiple dimensions, or the Shift key to select the first and last members in a range.

  16. Click Finish.

    The new query is added to the Manage Queries screen.

    Note:

    Before running the query, the database must be deployed. Although the database does not need to be calculated before running the query, results will be missing if it is not.

Editing Custom Smart View Queries

  To edit Smart View queries:

  1. From the Task Area, select Reporting, and then Manage Queries.

    The Smart View screen is displayed, showing all existing queries for all applications for which the user is provisioned as an Admin, Power.

  2. Click the Edit Query button  Edit Query button to open the Smart View wizard.

    Modify query options for the selected query.
  3. On Step 1: Query Options, modify any of the following fields to modify the query:

    • Name for the query

    • Optional: Description of the query

    • Select another Database to be used for the query from the drop-down list:

      • Calculation (BSO)

      • Reporting (ASO)

    • Optional: Enter a descriptive Search Tag to be used to sort queries in the main Smart View Query screen.

      Note:

      You cannot modify the Query Type or Query Options. To change the Type, create a new query.

  4. Optional: Under Smart View Options, select Suppress #Missing to set the data suppression option for the first query in Smart View, if required.

    Note:

    If you select Suppress #Missing, the Smart View option is set only for the first query run, not all queries. To set the option for subsequent drills into the data, set the option manually in Oracle Hyperion Smart View for Office.

  5. Optional: Under Smart View Options, select Use Dimension Aliases to display any assigned aliases for all dimensions in the query, if required.

  6. Click Next.

    Step 2 - Dimension Layout screen is displayed.

    Select the Dimensions to be used in the query, and the appropriate Dimension Position.
  7. Under Dimensions, for each Dimension, select the Position for the placement of the dimension under the Dimension Position column on the screen using the drop-down list:

    • Smart View POV

    • Rows

    • Columns

    By default, all dimensions in the application outline are displayed, and selections are set to defaults that are appropriate for the type of query you are creating.

    For example, if you select stage measures for a specific stage, the dimensions for that stage display in the Rows section, and the top member of the first hierarchy is pre-selected for each of the stage dimensions. The other stage dimensions are placed in the Smart View POV section, and the “NoMember” member from each stage is selected.

  8. Optional: Under Dimension Position, in the Smart View POV section, use the Up and Down arrows to fine tune the position of a highlighted dimension in the query.

  9. Optional: Under Dimension Position, in the Rows section, use the Up and Down arrows to fine tune the position of a highlighted dimension in the query.

  10. Optional: Under Dimension Position, in the Columns section, use the Up and Down arrows to fine tune the position of a highlighted dimension in the query.

  11. Click Next.

    Step 3 - Member Selections is displayed. All dimensions from the Smart View POV, Rows and Columns are displayed in the order defined on the Dimension Layout screen. Use the arrows to scroll up or down through the list.

    Select dimension members that are to be used in the query.
  12. Under Dimension Member Selections, use the Add arrowAdd arrow to move the dimension members to be included in the query to the Selected Dimension Members column.

    The list displays all dimension members, including alternate hierarchies and the NoMember member. Because there are no restrictions on level, alternate hierarchy, shared or base member, any member may be selected.

    Use the Ctrl key to select multiple dimensions, or the Shift key to select the first and last members in a range.

  13. Click Finish.

    The modified query is saved and available on the Manage Queries screen.

Duplicating Smart View Queries

  To duplicate Smart View queries:

  1. From the Task Area, select Reporting, and then Manage Queries.

    The Smart View screen is displayed, showing all existing queries for all applications for which the user is provisioned as an Admin or Power user.

  2. Click the Duplicate Query button Duplicate Query button.

    The Create Duplicate Smart View Query dialog box is displayed.

    Enter the name for the new query.
  3. Enter a name for the new query, and then click OK.

    The new query is saved and added to the list on the Manage Queries screen.

Deleting Custom Smart View Queries

  To delete Smart View queries:

  1. Ensure no other users require this query.

  2. From the Task Area, select Reporting, and then Manage Queries.

    The Smart View screen is displayed, showing all existing queries for all applications for which the user is provisioned as an Admin or Power user.

  3. From the Queries List, select the query to be deleted, and click the Delete button Delete button.

    A confirmation message is displayed to confirm that you do want to delete the selected query.

  4. Click Yes.

    The selected query is removed from the Manage Queries screen.

Running Smart View Queries from the Stage Balancing Screen

You can launch some predefined Smart View integrations from the Stage Balancing screen. The launch data points are represented as hyperlinks in the stage balancing screen. The hyperlinks in the columns represent values that have been contributed from one stage to another.

Click the hyperlinks to immediately access an analysis capability to analyze the calculations and determine whether areas may need to be repaired, and to explore details of any discrepancies or missing information.

Data displayed in the query always opens the Reporting database.

  To access queries through the Stage Balancing screen:

  1. From Oracle Hyperion Enterprise Performance Management Workspace, select Navigate, then Applications, then Profitability, and then select the application for which queries have been created.

  2. Deploy the database before running the query.

    It is not necessary to calculate the database before running the query; however, you should be aware that some results will be missing.

  3. From Task Areas, select Validate, and then Stage Balancing.

    The Stage Balancing screen is displayed.

  4. Select a POV and Layer, and then click the Launch button Run button.

    The Stage Balancing report for the selected POV is displayed, with highlighted active links. By default, the following hyperlinks are available:

    • Direct Input

    • Idle

    • Overdriven

    • Unassigned Columns

    Additional columns may also contain hyperlinks. The hyperlinks in the columns represent values that have been contributed from one stage to another. If there is no contribution from one stage to another, the intersection is empty.

    The Stage Balancing report for the selected POV is displayed, showing active links that may be clicked to access the results for the highlighted item.
  5. Click any hyperlink to view the results for that intersection in Essbase for the currently selected POV.

    The results display the total for the default hyperlink (for example, CostReceivedPriorStage) for all intersections of the selected members. Because the results are from the Reporting databases, all values are automatically aggregated.

    The results for the active link in Essbase are displayed for the currently selected POV.
  6. Optional: To modify the current POV, on the POV_Linked_View pane, click the down arrow beside any dimension listed for the current POV, and click the ellipsis (...) to open a Member Selector. Select any members that you want to change, and then click Refresh to activate the POV change.

  7. Review the results of the query.

  8. Optional: To view a specific intersection, use the Zoom commands on the Essbase tab to drill down or back up to a specific intersection.

Profitability and Cost Management Application Manager

In instances where Oracle Hyperion EPM 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. The Application Type, either Standard or Detailed, is set in the Wizard when you deploy the application. It is does not come from the Essbase Master Application.

Whether you use Essbase or Performance Management Architect to create the 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.

Users must be provisioned as an Admin or a Power user to access the Application Management Home screen.

See the following sections to work with the Application Manager:

Master Essbase Application

In order to use Profitability and Cost Management Application Manager, you must create a Master Application in Essbase to provide the source for the dimensions and dimension member information for Profitability and Cost Management. The Master Application is an ASO Application. A single application can be used as the source for multiple Profitability and Cost Management applications.

Caution!

If you rename or delete dimensions in your Essbase master application, you will no longer be able to properly update dimensions on already deployed Profitability and Cost Management applications that reference those dimensions. If you want to rename or delete dimensions, consider creating a separate Essbase Master database so that your existing Profitability and Cost Management applications can still be updated if necessary.

When deploying the Master Essbase Application, the ASO dimension members and their properties, such as ASO Storage Type, ASO Formula, Hierarchy Type, and so on, are automatically read into Essbase. No manual actions are required.

BSO-specific dimension and member properties cannot be read automatically during deployment. To manage this, you must create User-Defined Attribute Dimensions (UDAs) for BSO dimension members and properties, such as Formulas, Data Storage and Dimension Storage type, and specific Performance Management Architect dimensions and properties, such as POV dimensions. to align the BSO database with Essbase.

The Unicode property set for the Essbase Master application dictates the Unicode property for any Reporting or Calculation database applications that are created from a Profitability and Cost Management application deployed from that Master application.

See the following sections to prepare the Master Essbase Application:

Dimension Types

When creating the Master Essbase Application, every dimension must be assigned a DIMTYPE UDA.

The valid dimension types are displayed in Table 2, Dimension Types.

Table 2. Dimension Types

Property LabelProperty NameDescription
Allocation TypeDIMTYPE_ALLOCTYPE

For Standard Profitability only, create an AllocationType dimension using the following criteria:

  • Assign the Generation1 member a UDA value of “DIMTYPE_ALLOCTYPE” so the Application Manager recognizes the member. The member name may be anything, but the UDA value must be set as described.

  • Create one dummy member in this dimension to enable Essbase to save an outline where a Gen1 member has no children.

MeasuresDIMTYPE_MEASURES
  • Create a Measures dimension and assign the Generation1 member a UDA value of “DIMTYPE_MEASURES.” The member name may be anything, but the UDA value must be set as described.

  • Create one dummy member in this dimension to enable Essbase to save an outline where a Gen1 member has no children.

    Note:

    For Standard Profitability only, see Custom Measures Dimensions to use Custom Measures dimensions.

Generic (Business)DIMTYPE_GENERICAssign Business dimensions a UDA value of DIMTYPE_GENERIC.
POV
  • DIMTYPE_POV1

  • DIMTYPE_POV2

  • DIMTYPE_POV3

  • DIMTYPE_POV4

For up to four POV dimensions, assign the Generation1 Member value in numerical sequence. For example, DIMTYPE_POV1, DIMTYPE_POV2, and so on.

User-Defined Attributes

User-defined attributes (UDAs) enable analysis based on text attributes of dimension members. For example, you may add a UDA called “New Products.”

Enter the UDA name for the selected member.

You can enter up to 256 alphanumeric characters. A limit of 80 characters is applied for Unicode-enabled databases.

In any Essbase outline, ensure all dimensions have a unique name; otherwise, the creation of the outline will fail. For example, an attribute dimension member name cannot match a regular dimension name.

ASO Dimension and Member Properties

The properties for the ASO dimension and member properties displayed on Table 3, Profitability and Cost Management ASO Dimension and Member Properties are pulled automatically into Essbase during deployment. No manual actions are required to align these properties with the Master Essbase Application.

Table 3. Profitability and Cost Management ASO Dimension and Member Properties

Property LabelProperty NameDescription
AliasAliasThe alias is the dimension member name that is displayed in a deployed application. Any member aliases are displayed, except for the Root Member.
CommentCommentA comment may be entered for the dimension or member. Comments can contain up to 255 characters. By default, this text box displays the current comment, if one exists.
ConsolidationConsolidationMember consolidation properties determine how children roll up into their parents.

If the current member is not a dimension or an attribute, one of the following consolidation operators is assigned to the member:

  • + (addition) - Default

  • - (subtraction)

  • * (multiplication)

  • / (division)

  • % (percent)

  • ~ (ignore during consolidation)

  • ^ (never consolidate)

  • NotUsed

Note:

Some restrictions exist regarding the use of consolidation operators in aggregate storage outlines (ASO). See the Oracle Essbase Database Administrator's Guide.

Data Storage(ASO)
  • ASODimensionDataStorage (for dimension root member)

  • ASOMemberDataStorage (for dimension members)

The ASO storage options that are available for dimensions and members:
  • StoreData—Data is stored with the dimension.

  • ShareData—Data associated with this member can be shared. The ShareData property applies to the member only. The Dimension Root Member cannot be shared.

  • NeverShare—Data associated with this dimension cannot be shared, even if there is an implied share relationship, such as with a parent with one child. In this case, the data is duplicated in the parent and child.

    Note:

    This option does not apply to stored hierarchies in aggregate storage outlines.

  • LabelOnly—No data is associated with this dimension.

Dimension Formula(ASO)ASODimensionFormula (for dimension root member)The calculation formula that is applied to the dimension.
Dimension Solve OrderDimensionSolveOrderThe numeric value in the solution sequence for selected dimensions. For example, if this dimension is to be solved second, enter “2.”
Hierarchy Type

(Dimensions Only)

DimensionHierarchyType

The Hierarchy Type property applies only to Aggregate Storage (ASO) databases in Essbase.

The type of hierarchy for the dimension is set to one of the following values:

  • STORED - for any dimension members that use the following consolidation symbols:

    • +ADDITION

    • ~ IGNORE

      Note:

      The no-consolidation or IGNORE (~) operator can only be used in a STORED hierarchy if the member's parent is set to LABEL_ONLY

  • DYNAMIC - for dimension members that use any consolidation symbol, including ADDITION and IGNORE, or if the dimension member contains a formula.

  • ENABLED - to support alternate hierarchies

Hierarchy Type

(Members Only)

HierarchyTypeThe type of hierarchy available for the member:
  • Stored (For first Gen2 child)

  • Dynamic (For Second Gen2 child onwards. The Second Gen2 member can host the alternate hierarchies)

  • None (Do Not Use)

Member Formula(ASO)ASOMemberFormulaThe calculation formula that is applied to the member.
Member Solve Order

(Members Only)

MemberSolveOrderEnter the numeric value in the solution sequence for selected member. For example, if this member is to be solved second, enter “2.”

This property applies to ASO databases only.

Members that have a solve order of 0 inherit the solve order of their dimension.

Members with the same solve order are evaluated in the order in which their dimensions appear in the database outline, unless otherwise specified by the dimension sort order property.

Members with no solve order are evaluated after members with a solve order.

UnicodeUnicodeSelect Unicode to set the application to Unicode mode. Unicode-mode applications support multiple character sets.

Specifying BSO and Member Dimension Properties

The Master Essbase Application is an ASO Application, and the ASO dimensions and members are automatically read during deploymentASO Dimension and Member Properties; however, BSO-specific member properties are required for the BSO database or to handle special dimensions and members (such as the POV) that cannot be automatically read.

In order to include these BSO and Oracle Hyperion EPM Architect dimensions and members in the Essbase BSO database, a Generation1 member is required for each dimension to be deployed into Profitability and Cost Management. The order of the dimensions in the master outline is determined by the order of the dimensions in the Profitability and Cost Management generated outline.

You must create UDAs for each of the dimensions and members listed on Table 4, Dimension and Member Properties for Profitability and Cost Management. For additional information about working with Essbase, see the Oracle Essbase Database Administrator's Guide.

Caution!

Do not assign multiple UDA's of the same type to a specific member in Essbase as this results in inconsistent behavior because the Profitability and Cost Management deployment does not know which UDA type to use. For example, do not assign both DIMTYPE_POV1 and DIMTYPE_POV2 to the same member.

See Table 4, Dimension and Member Properties for Profitability and Cost Management for the properties that require special UDAs that must be assigned manually to the application:

Note:

Because the BSO properties are assigned using a UDA, if a user inadvertently assigns incompatible BSO properties in the Master Essbase database, a subsequent "Deploy to Reporting Cube" operation within Profitability and Cost Management may fail. If this situation occurs, you can identify the incompatible assignments by manually loading the data and rules files that were generated by the Reporting database deploy.

Table 4. Dimension and Member Properties for Profitability and Cost Management

Property LabelProperty NameDescription
Data Storage(BSO)
  • BSODimensionDataStorage (for dimension root member)

  • BSOMemberDataStorage (for dimension members)

For BSO Data Storage, assign one of the following UDAs to the Generation1 member of any child member:

  • BSODS_LABELONLY

  • BSODS_NEVERSHARE

  • BSODS_SHAREDATA

  • BSODS_DYNCALANDSTORE

  • BSODS_DYNCALC

  • BSODS_STOREDATA

When setting the UDA, if no value is assigned to the property BSO Data Storage, the Profitability and Cost Management deployment assumes the following default values are assigned:

  • Generation1 members are assigned “BSODS_LABELONLY”, with the following exceptions:

    • POV Generation1 Members are set to “BSODS_STOREDATA”

    • Measures Generation1 Member is set to “BSODS_DYNCALC”

  • All other members are assigned “BSODS_STOREDATA”

Dimension Formula(BSO)BSODimensionFormula (for dimension root member)For the BSO Dimension Formula, the user cannot specify the BSO Dimension formula in the Essbase Master database, because that database has to be an ASO database (and therefore the formula attribute available in the master database is the ASO formula).

After deployment, to have the BSO formula display in the Essbase Reporting database, manually enter the BSO dimension formula directly into the Reporting database. The BSO formula will have to be reentered if you redeploy.

Use the appropriate BSO CALCULATOR syntax.

Dimension Sort OrderDimensionSortOrderEnter the numeric value in the sequence to set the order of dimensions in the Essbase outline that is generated by Profitability and Cost Management.

For example, if this dimension is to be the second in the Essbase outline, enter “2.”

Dimension Sort Order must be set for every dimension in the model, except Alias and UDA dimensions.

The dimension sort order must be sequential, unique, and greater than or equal to 1.

Dimension Storage TypeDimensionStorageTypeThe Dimension Storage Type property applies only to Block Storage (BSO) databases in Essbase.

By default, the value is set to “SPARSE”.

If you require a DENSE setting, assign a UDA with the value “DIMSTORETYPE_DENSE” to the Generation1 member.

Member Formula(BSO)BSOMemberFormulaFor the BSO Member Formula, the user cannot specify the BSO member formula in the Essbase Master cube, because that database has to be an ASO database (and therefore, the formula attribute available in the master cube is the ASO formula).

After deployment, to have the BSO formula display in the Essbase Reporting database, manually enter the BSO dimension formula directly into the Reporting database. The BSO formula will have to be reentered if you redeploy.

Use the appropriate BSO CALCULATOR syntax.

Two Pass Calculation

(Dimensions Only)

BSO_TWOPASS

(for dimension root member)

For BSO databases only, specify the BSO_TWOPASS to calculate a member on the second pass through the outline.

Two Pass Calculation

(Members Only)

BSO_TWOPASS For BSO databases only, sspecify the BSO_TWOPASS to calculate a member on the second pass through the outline.

Custom Measures Dimensions

For Standard Profitability only, if you want to use custom measure members, create a member name “UserDefinedDriverMeasures” under the Driver Measures, and add custom members as children of that member. The Application Manager inserts those custom members as children of the “UserDefinedDriverMeasures” in the deployed Measures hierarchy.

The member UserDefinedDriverMeasures is where the application-specific, user-defined driver measures are stored. Set the ASOMember DataStorage and BSOMember DataStorage properties as follows:

  • Set to StoreData if the member does not have children.

  • Set to LabelOnly if members are added as children to this member, and all these children have the consolidation symbols of IGNORE.

    Note:

    All driver measures must be unique in the outline. Do not use the name of an existing driver measure in a dimension in the outline as the name of another member (including system, POV and business dimensions) ; otherwise, the Data Entry screen will not properly display the values.

Building the Master Essbase Application

Use Essbase to create dimensions and dimension members in a Master Essbase Application, which can then be imported into a Profitability and Cost Management application.

  To create the Master Essbase Application:

  1. Create the Master Essbase database for your Profitability and Cost Management application, using the following guidelines to generate the dimensions and members for the application:

    For detailed instructions on creating Applications and Databases in Essbase, see the Oracle Essbase Database Administrator's Guide.

  2. Ensure that the user who will create the Profitability and Cost Management application has been provisioned as an Admin or a Power user.

  3. Create the Profitability and Cost Management application, as outlined in Creating the Profitability and Cost Management Application.

Creating the Profitability and Cost Management Application

  To create applications from the Master Application:

  1. From EPM Workspace, select Navigate, then Applications, then Profitability, and then Profitability Applications.

    The Profitability Applications tab is displayed, showing the Applications and Job Library tabs. There is no Task Area available on this screen.

    The main screen for the Profitability and Cost Management applications is displayed.
  2. Click the Add button  Add button to open the Applications wizard.

    The first step of the New Application wizard is displayed.
  3. On the first step of the New Application Wizard, enter the following information:

    • Application Name for the query

    • Optional: Description of the application

    • Select the Instance Name from the drop-down list.

    • The address of the Web Server is displayed

    • Select the Essbase Application Server from the drop-down list.

    • Select the Shared Services Project from the drop-down list.

    • Optional: Select Detailed Profitability, if required. By default, the application type is assumed to be Standard Profitability.

  4. Click Next.

    Step 2 of the New Application Wizard is displayed.

    Step 2 of the New Application Wizard is displayed.
  5. Under Essbase Application, select the Essbase application that is to be used for the Profitability and Cost Management application.

  6. Under Available Dimensions, use the Add arrowAdd arrow to move the dimension members to be included in the Profitability and Cost Management application to the Selected Dimensions column.

    Use the Ctrl key to select multiple dimensions, or the Shift key to select the first and last members in a range.

  7. Click Finish.

    When you click Finish, the following actions are initiated:

    • A new task flow to create the new application beings. Results can be viewed on the Job Library tab. See

    • Dimensions in the source Essbase database are validated. If there are validation issues, the task flow ends. Fix any validation errors, and repeat the steps to create the new application.

    After the validation is complete, the new application is added to the Applications tab.

Editing Applications

Only the Application Description and Shared Services Project can be modified. If you want to change any other information related to the application, you must create a new application. See Creating Custom Smart View Queries.

  To edit applications:

  1. From EPM Workspace, select Navigate, then Applications, then Profitability, and then Profitability Applications.

    The Profitability Applications tab is displayed, showing the Applications and Job Library tabs.

  2. Select the application to be modified, and then click the Modify button Modify button .

    Only the Application Description and Shared Services Project can be changed. All other options are grayed out.

    The Edit Applications window of the Application Wizard is displayed.
  3. On the Edit window of the Application Wizard, modify the following information as required:

    • Modify the Application Description, if required

    • Select a different Shared Services Project from the drop-down list.

  4. Click Next.

    Step 2 of the Application Wizard is displayed.

    The screen is populated with the selected dimensions, and cannot be modified.

  5. Click Finish.

Reregistering Applications

Registration of the new application in Oracle Hyperion Shared Services occurs automatically when you deploy an application; however, on occasion, you may need to reregister the application.

  To reregister the application:

  1. From EPM Workspace, select Navigate, then Applications, then Profitability, and then Profitability Applications.

    The Profitability Applications tab is displayed, showing the Applications and Job Library tabs.

  2. Select the application that needs to be registered or reregistered, and then click the Register button  Register button.

    A confirmation dialog is displayed, requesting whether to proceed with the registration.

  3. Click OK to register the application.

    A confirmation message advises that the application has been reregistered.

For additional information on registering applications, see the Oracle® Hyperion Enterprise Performance Management Architect Administrator's Guide.

Duplicating Applications

  To duplicate applications:

  1. From EPM Workspace, select Navigate, then Applications, then Profitability, and then Profitability Applications.

    The Profitability Applications tab is displayed, showing the Applications and Job Library tabs.

  2. On the Applications tab, select the application that you want to duplicate, and then click the Duplicate button  Duplicate button.

    The Create Duplicate Application dialog box is displayed.

    Enter the name of the new application, and then click OK.
  3. Enter the name of the new application, and then click OK.

    The duplicated application is added with the new name under Applications.

Updating Dimensions

If any changes are made to dimensions or dimension members in the Essbase database, such as adding, deleting, changing, or renaming, you must update the dimensions in the Profitability and Cost Management application.

Caution!

If you rename or delete dimensions in your Essbase master application, you will no longer be able to properly update dimensions on already deployed Profitability and Cost Management applications that reference those dimensions. If you want to rename or delete dimensions, consider creating a separate Essbase Master database so that your existing Profitability and Cost Management applications can still be updated if necessary.

Whenever the Update dialog box is used to update dimensions, a Job entry is automatically created in the Job Library to validate and update the application.

  To update Essbase dimensions in the Profitability and Cost Management application:

  1. From EPM Workspace, select Navigate, then Applications, then Profitability, and then Profitability Applications.

    The Profitability Applications tab is displayed, showing the Applications and Job Library tabs.

  2. Select the application that contains the dimensions and dimension members that need to be updated.

  3. Click the Update button  Update button.

    The Update Dimensions dialog box is displayed.

    Use the Update Dimensions dialog box to validate and update modified dimensions or dimension members.
  4. Select the Essbase Application that is being used as a staging area for dimensions.

  5. Select the Essbase Database that is being used as a staging area for dimensions.

  6. Under Dimensions, select the dimensions that need to be updated. To select all dimensions, click the Dimensions checkbox.

  7. Optional: Under Pre Update Analysis, select Validate Dimensions to verify that each of the selected changes are valid. This option does not update the dimensions. If all dimensions have been selected, this option also runs the application level dimensions validations.

    Validation errors and the results of the impact analysis are displayed in the Job Library.

  8. Optional: Under Pre Update Analysis, select Impact Analysis to perform a comparison between the model being deployed and the existing model in Profitability and Cost Management. If Impact Analysis is selected, the Validate Dimensions option is unavailable.

    The following information is displayed:

    • New Members

    • Deleted Members

    • Re-Parented Members

    • Members with Level0 change

    Validation errors and the results of the impact analysis are displayed in the Job Library.

    Caution!

    If a member is renamed or re-parented in Essbase, it is displayed as both a Deleted member and a New member in the impact analysis. In addition, any artifacts that reference a member that has been deleted during the rename or re-parent operation, such as Assignment Rule Selections, Driver Selections and Driver Exceptions, will also be removed.

  9. Optional: Check Update Dimensions to update the selected dimensions with the changes, and then click OK.

    Note:

    The modified dimensions are validated, and any exceptions are reported in the Job Library.

Deleting Applications

  To delete applications:

  1. Ensure no other users require this application.

  2. From EPM Workspace, select Navigate, then Applications, then Profitability, and then Profitability Applications.

    The Profitability Applications tab is displayed, showing the Applications and Job Library tabs.

  3. On the Applications tab, select the application that you want to duplicate, and then click the Duplicate button Duplicate button.

    The Create Duplicate Application dialog box is displayed.

    Enter the name of the new application, and then click OK.
  4. From the Queries List, select the query to be deleted, and click the Delete button Delete button.

    A confirmation message is displayed to confirm that you do want to delete the selected query.

  5. Click Yes.

    The selected query is removed from the Manage Queries screen.

Viewing Tasks in the Job Library

The Job Library provides a list of all jobs, including jobs running for existing applications. You can filter the grid to isolate jobs for a specific user or particular type.

  To view the Job Library:

  1. From EPM Workspace, select Navigate, then Applications, then Profitability, and then Profitability Applications.

    The Profitability Applications tab is displayed, showing the Applications and Job Library tabs.

  2. Select the Job Library tab.

    The Job Library screen displays the details for each currently submitted job.
  3. Under Job Listing, view the information for each job:

    • Start Date/Time displays the date and time on which the job was submitted or is scheduled to be run.

    • Application displays the name of the application for which the task is being run.

    • Job Type displays the type of task that is being performed. The following options are specific to jobs initiated during the validation or update of Oracle Essbase databases and the import into Oracle Hyperion Profitability and Cost Management applications:

      • Create Application

      • Dimension Update Analysis

      • POV Copy – POV data has been copied

      • Update Dimensions

    • Comment shows a user-entered note or details about a specific job. The Comment is entered when the task is submitted.

    • User identifies the User ID of the individual who submitted the task for processing.

    • Task Flow ID is the system-generated task ID for the specific task, displayed in the format <application name>:<task name><generated taskflow number>.

      For example, the generated taskflow number may be displayed as AppMgmt_DeployApplication_D20120824T08520_5ed, where AppMgmt is the application name, DeployApplication is the task, and D20120824T08520_5ed is the generated taskflow instance ID.

    • Status Message displays a message about the current state of the taskflow, such as Running, Success or Failure.

    • Errors displays error conditions for the submitted job.

    • Warnings displays warnings for the submitted job.

  4. Optional: Under Job Messages, review additional summary level detail about the selected job. The Job Messages may include a hyperlink that enables you to click to view more detail in a popup dialog box.

  5. Optional: Under Job Options, review the choices made during the initiation of the job.

  6. Optional: Use the Find text box at the bottom of each column to locate a job by entering text in the Find field attached to the column in which it resides.

  7. Under Job Finished, view the date and time that the highlighted task was completed.

  8. Under ODL Task ID, view the ID for the highlighted job to assist in locating error or warning messages in hpcm.log.

    In the hpcm.log file, use Find and the ODL Task ID to locate the start of the logging detail text for the selected job. After locating the start of the log entries, you can search down to find an “ERROR” in the file.

  9. Optional: If required, click Stop Job to end the highlighted task in Running state.

    Caution!

    While the task flow stops quickly after the button is pressed, activities that affect results may require additional time to ensure that the state of the data is consistent.

    For detailed instructions on using Oracle Hyperion Enterprise Performance Management Workspace taskflows, see the Oracle Enterprise Performance Management Workspace User's Guide.