Version

In addition to the properties described in the table, Version dimension members use most of the common properties described in Properties Applicable to All Planning Dimensions, such as:

  • Valid for Plan

  • Aggregation

  • UDA

  • Member Formula

  • Alias

  • Data Storage

  • Smart List

  • Data Type

Use the Version dimension to:

  • Provide multiple iterations of a plan, such as preliminary and final

  • Model possible outcomes based on assumptions such as best case and worst case

  • Control plan data, such as internal and external

  • Facilitate target setting

Versions are independent of Scenarios. You can change Version names and access permissions. The application must have at least one Version. For information on setting access permissions, see the Oracle Hyperion Planning Administrator's Guide.

Table 40. Version Properties

Property Label

Description

 Property Name

Enable Process Management

Select whether the Version is enabled for process management. This allows for managing a planning unit that contains this Version member. Not available for target versions.

Default Value: N/A

 EnableProcessManagement

Version Type

Target: Users enter data for members at any level, and use business rules to distribute values from parent members to descendants.

Use target versions to set high-level targets for plans. Planners working with bottom-up versions can reference targets when entering plan data.

Target versions use top-down budgeting. Workflow tasks are not allowed, and children of target members must be blank (for example, #MISSING) to enable data input at the top level. Target members must be set to Store (Dynamic Calc overrides data input with the sum of children).

Bottom Up: Users enter data into bottom-level members. Parent-level members are read-only. Values for parent members are aggregated from bottom level members.

Default Value: Bottom Up

 VersionType