
But if an off shore developer from the Indian division of the company is used the cost price might be £200 per day. For example, in the UK a developer may cost £500 per day. Meaning that whenever we start an opportunity for this division CRM will know what cost prices to apply when calculating the profitability of a potential project.Ĭost price lists define the costs of resources based on their role and their organizational unit. Notice that I have added the cost prices for UK resources to this unit. This is significant as any price lists you associate with the organizational unit must also be in the same currency. The currency must be defined when you create the unit and cannot be changed. Notice that the currency is pound sterling and is readonly. As shown below.īelow you can see that I have created an Organisational unit for the UK division of my demo company. You can access the organisational units entity from the Project Service area of CRM. It has multiple purposes in PSA, one of which is to link to the cost price lists that will be used on an opportunity.

In this post, I will describe cost price list and organisational units.Īn organisational unit is a division of the company. This blog post is one of a series I have created which covers all aspects of Project Service Automation (PSA) which is part of Microsoft’s Dynamics 365.
