Understanding PSA Data: Blog 11: Role Prices

Microsoft Dynamics PSA Role Prices

The concept of a role price is to define the price of a type of resource per organizational unit (or resourcing unit.) Role prices are associated with both Cost and Sales Price Lists to define the cost or price of each role within each organisational unit. For example, a Developer with the resourcing unit ‘UK’ may be billed out to a customer for £800 a day whereas a Developer with the resourcing unit ‘US’ may be billed out to a customer £900 a day, as seen below.

Example Role Prices

Role prices can be added through the Sub Grid on the organisational unit form. Units cannot be changed as all the prices need to be expressed in terms of the units defined on the Cost Price List. Also, the currency for all the role prices will match the currency defined on the price list.

Importance of Role Prices in PSA

• Role prices define the Cost estimates and the Billed Sales actuals on a project.
• If a role price is missing for a certain role, an estimate/actual will have no data to calculate these i.e. if you added a HR Consultant to a WBS of which the project was using the ‘Contoso UK’ Contracting Unit and there was no role price for a HR Consultant associated with this organisational unit, the Estimated Cost for that task would not be calculated and nor would any amounts for Actuals.

The screen shot below is of the project tracker, notice the view can be changed to see costs and sales value, this view will not show valuable information if the Role Prices are not populated.

Technical Details

• Role prices will need importing after organisational units, as they sit within the organisational unit form.
• This entity is called ‘Role Price’ in Dynamics 365
• Schema name – msdyn_resourcecategorypricelevel