a month ago - last edited a month ago
When maintaining the project budget, I manually uploaded the budget for higher-level WBS elements (parent WBS). However, the system automatically aggregated the budgets of lower-level WBS into the parent WBS, resulting in:
Aggregated Costs showing double-counted budget (Parent WBS budget = Manually uploaded value + Sum of child WBS budgets).
Non-Aggregated Costs displaying correctly (only the manually uploaded budget).
Requirement: How to prevent the parent WBS budget from being inflated by child WBS aggregation while ensuring accurate budget reporting?
Request clarification before answering.
Hello,
I think non-aggregated view is exactly for that usage.
Best Regards,
Owen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you maintain the WBS Budget only at the highest level and then allocate it to the lowest level of the WBS?
If we only maintain the WBS Budget at the lowest level, the aggregated view at the highest level will show the correct amount. However, maintaining the budget only at the lowest level can cause the error shown in my diagram.
User | Count |
---|---|
100 | |
15 | |
9 | |
9 | |
5 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.