Security Roles for Standard Profitability

Table 2-1 Standard Profitability and Cost Management Security Roles

Security Role Description
Administrator (admin);Type of role = Power
  • Create and maintain user accounts and security roles, and provision users, using Oracle Hyperion Shared Services

  • Generate Oracle Essbase databases

  • Set up and maintain application preferences

  • Create and maintain elements within the model, such as stages, drivers, POVs, driver selections, assignments, and application preferences

  • Perform POV Copy, calculation, validation, data entry, and trace allocations

  • Deploy to Essbase and generate calculation scripts

    Caution:

    The Oracle Hyperion Profitability and Cost Management Administrator must also be assigned Essbase access rights to perform Essbase ASO and BSO deployment.

  • Import and export data

  • Use the Lifecycle Management Utility to promote data from one environment, such as development or testing, to another environment, such as production

  • Back up and restore Profitability and Cost Management model components

  • Monitor changes made to business objects.

  • Create, edit, copy, delete, and launch queries.

  • Use the Profitability Applications Console to create and manage new Profitability and Cost Management applications.

Power User;Type of role = Power
  • Create and maintain elements within the model, such as stages, drivers, POVs, driver selections, assignments, and application preferences.

  • Perform POV Copy, calculation, validation, data entry and trace allocations.

  • Import and export data

  • Deploy to Essbase and generate calculation scripts.

    Caution:

    The Profitability and Cost Management Power User must also be assigned Essbase access rights such as Create Application and Application Manager to input data into Essbase and perform Essbase ASO and BSO deployment.

  • Create, edit, copy, delete, and launch queries.

Note:

The Power User does not necessarily require specific security roles to perform tasks. For example, if a Power User runs a calculation from the Calculate screen, this action creates and executes a taskflow behind the scenes. The Power User does not require the Manage Taskflow role to perform this task, unless the Power User wants to access this task directly from the Manage Taskflows task.

Interactive User;Type of role = Interactive
  • View all modelling screens

  • View and modify data in the Data Entry screen

  • View Trace Allocations

  • Launch queries.

View User;Type of role = Interactive View only access for these functions:
  • Trace Allocations

  • Application Preferences

  • Model Stages, Drivers and POVs

Manage Taskflows;Type of role = Shared Services Role Required to create and edit taskflows.

For more information, see the Oracle Enterprise Performance Management System User Security Administration Guide.

Run Taskflows;Type of role = Shared Services Role Required to enable users to only run and view taskflows. Users with this role cannot create or edit taskflows.

For more information, see the Oracle Enterprise Performance Management System User Security Administration Guide.