Skip to main content
Question

Financial Plan: See the Project WBS hierarchy and roll up totals ???

  • June 12, 2026
  • 1 reply
  • 7 views

Forum|alt.badge.img

URGENT please - A basic requirement in Project Management from our project managers, effort and cost breakdown vs time? 
Using Portfolio Financial Plan, how can we see the roll-up cost at parent task levels…

A typical WBS is as follows:
Project
Work stream 1
     Cpy A
        Task A.1
        Task A.2
    Cpy B
       Task B1
       Task B2

Work stream 2
     Cpy C
        Task C1
        Task C2
    Cpy B
       Task B1
       Task B2

The leaf level is Task.
How can I see the rolled-up effort and cost per month in the financial plan for Work Stream and Cpy level?

In the Financial plan/report, we would like to see (for labour cost and effort)

                           Mth1          Mth2   ...

Workstream 1     £55            £65
    Cpy A              £30            £30
        Task A.1      £10            £5
        Task A.2      £20            £25

    Cpy B              £25           £35
       Task B1        £5             £20
       Task B2        £20           £15 


The Financial Plan only show the Effort and Cost at Leaf level… how can I include the parent tasks roll up? Please let me know how you all do this in Portfolio?

Thanks

Tony

1 reply

Forum|alt.badge.img+1
  • Silver Innovator
  • June 15, 2026

Hi ​@Happytoon 

Financial Planning in Planview typically stores and displays costs at the lowest planning entity level. Native roll-up of monthly financial values to intermediate WBS summary tasks is generally not available directly within the Financial Plan grid.

If rolled-up reporting is required, you usually consider one of the following approaches:

Use Project/Task hierarchy reports where summary task values are calculated through reporting.
Create custom reports in Analytics/Power BI that aggregate cost and effort across child tasks.
Plan financials at the level where reporting is required (for example Capability or Workstream level rather than leaf task level).