Cost Plan 'Populate from Allocations' Uses Resource Location Instead of Project Location

Products

• Clarity PPM SaaS

Issue/Introduction

When running "Populate from Allocations" on a Cost Plan, a Named Resource picks up a rate based on their personal Financial Location rather than the Project Location. This happens even when the Financial Management WIP Settings are explicitly configured to source the "Project Location". At the same time, generic Roles correctly default to the Project Location rate.

Environment

Clarity PPM On Premise, Clarity PPM SaaS

Cause

Clarity separates the logic for Actuals (WIP) and Planning (Cost Plans). Financial Management WIP Settings only control the default values for posted transactions (Actuals).

The Cost Plan "Populate from Allocations" action bypasses WIP Settings entirely. Instead, it is governed by the Entity's Plan Defaults. If the Entity's Labor Rate and Cost Defaults are configured to use the "Resource", the system is strictly instructed at the Entity level to prioritize the Resource's personal location over the Project's location when reading the Rate Matrix.

Resolution

To force the Cost Plan to respect the Project Location and align the estimates with your WIP settings, you must update the Entity Plan Defaults.

1. Navigate to Administration > Finance > Setup > Entities.
2. Open the relevant Entity and click on the Plan Defaults tab.
3. Under the Labor Rate and Cost Defaults section, locate the dropdown for the Rate Source.
4. Change the dropdown value from Resource to Project.
5. Save the changes.
6. Return to your Project's Cost Plan and run Populate from Allocations again to update the Named Resource to the correct Project Location rate.