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
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.
Default Value: N/A
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