Skip to main content
If you are a Planview customer, sign in to enable additional content.
Planview Customer Success Center

Rolling Up a Version to Summarize Costs and Benefits

Sign in to access this product help article.

You are viewing content for Planview® Enterprise One release – Portfolio and Resource Management.

Warning: Rolling up a version changes the levels at which users can enter financial-planning data.

You can roll up a versions for strategic financial-planning models, work financial-planning models, or outcome financial-planning models. Note: You cannot roll up versions for cost center or organization financial-planning models.

To summarize a financial-planning version's costs and benefits by rolling up the version from a given level to a summary level for a specific time period:

  1. Ensure you are familiar with how users can summarize data and roll up data while reviewing a financial plan.

  2. On the menu bar, click Administration > System Configuration > Financial Management.

  3. Click Financial Planning.

  4. Click Financial Planning Models.

  5. On the row relevant to the financial-planning model for which you are rolling up a version, click the action menu button and then click Configure Versions.

  6. On the appropriate row, click the action menu button, click Roll Up Version, and then click the option relevant to the type of financial plan for which you want to roll up data. Note: The options that appear depend on which check boxes are selected in the Allowed column on the Edit Financial Planning Model screen as well as the setting of that screen's Roll Up Target option.

    If the Work to Outcome to Strategy option is available, you can click it to configure the version to support automatically loading data of a work financial plan based on the relevant model into an outcome fnancial plan also based on that model and then rolling up data in both of those plans to a strategy financial plan based on the same model. If the Work to Strategy to Outcome option is available, you can click it to configure the version to support automatically loading data of a work financial plan based on the relevant model into a strategy financial plan also based on that model and then rolling up data in both of those plans to an outcome financial plan based on the same model.

  7. Specify whether you want to roll up all financial-planning data or the financial -planning data for a specific portfolio by clicking the relevant option. If you click the Roll up Specific Portfolio option, click the appropriate portfolio's name on the list relevant to that option.

  8. Make selections on the Roll Up Level To and From lists to specify the range of levels you want included in the roll up. Only levels allowing financial planning are available for selection. When making your selections, keep the following information in mind:

  • In general, you can roll up from one level that supports financial planning to another level that supports financial planning for the specified model, version, and period. Each level in between is also loaded.

  • The level you select in the Roll Up Level To list must be higher than the level you select in the From list.

  • The level you select in the Roll Up Level To list cannot be locked from loading, but you can select a locked level in the From list.

  • If a hierarchy branch does not have an entity at the level selected in the From list, the leaf level is used if it is below the level selected in the Roll Up Level To list.

  • For strategic and outcome financial-planning models, the levels you are rolling up data from must include the primary planning level (PPL) of the Work Breakdown Structure. For example, roll up all of the data at the Project level in a strategic financial-planning model to the Initiative level of the strategic financial-planning model.

  1. Click Roll Up.

Business Rules That Apply to Rolling Up a Version

The following business rules apply when you roll up a version for a financial-planning model:

  • The roll up does not include inactive accounts nor does it include any accounts an administrator marked to be excluded from roll ups.

  • Any load locks for a level or entity are respected during the roll up. If an entity is prevented from loading, its data is not overwritten. However, the roll up continues above the entity and reads from its unchanged data. The roll up also respects load locks by period. If an entity has periods prevented from loading, those periods are not changed or overwritten.

  • Financial Allocation % Rules:

    • An association with a Financial Allocation % of 0 is ignored in the roll up.

    • An association with a Financial Allocation % of 100 is included in the roll up.  This includes blank financial plans, which are considered a financial plan of zero, and will clear out the parent in order to roll up a zero financial plan.

    • An association with a Financial Allocation % greater than 0 but less than 100 will calculate the % of each line and roll up to the parent.

  • Version Roll Up Rules Relevant to the Portfolio Option:
    • Roll up All: Rolls up all data in the system for the selected parents.
    • Roll up Specific Portfolio: Only rolls up from the children included in the portfolio and ignores those outside of the selected portfolio.
  • Rules Relevant to the Roll Up Version Option:

    • Work

      • Roll up work to higher levels in the work hierarchy.

    • Strategy

      • Roll up from work or strategy to higher levels in the strategy hierarchy.

    • Outcome

      • Roll up from work or an outcome to higher levels in the outcome hierarchy.

    • Work to Strategy to Outcome

      • The recommended option.

      • Work is rolled up to lowest level in strategy.

      • The strategy is rolled up to the selected level in the outcome hierarchy.

      • Any work associated directly to an outcome is rolled up with the strategy. 

      • Example: Three projects are rolled up into a program to create an outcome plus any ongoing support work associated directly to that outcome is included for a total cost of the outcome.

    • Work to Outcome to Strategy

      • Not the recommended option.

      • Work is rolled up to the lowest level in the outcome hierarchy.

      • The outcome is rolled up to the selected level in the strategy.

      • Any work associated directly to a strategy is rolled up with the outcome.

  • You can perform multiple roll ups if you want to roll up to higher levels in multiple structures.
  • When outcomes roll up from projects, only the relevant percentage based on the defined allocation is rolled up.