Dynamics Community Forum Thread Details

Multi-Project contract, multiple OUs

Hi everyone,

i'm implementing PSA in my company's CRM instance and we have already set up almost everything (Cost/Sales Price Lists, OUs etc.).

We have a fairly complex OU suddivision, evert OU is identified as a Cost Center.

We're trying to achieve a configuration which could allow us to track:

the percentage of hours spent on a project by OU resources that are not part of the Contracting Unit;
track estimates/actuals for every OU (and do a little forecasting, but this is another story).

So far, so good.

The trouble is a particular scenario which happens fairly often: sometimes we subscribe project contracts with our top customers that may contain multiple projects of very different nature and that we should to mark with different contracting units.

An example:

Order XYZ -> generic CU
- Prj 0 -> presales CU;
- Prj 1 -> network CU;
- Prj 2 -> service CU;

I'm aware that when you "attach" a project to an order (project contract) through the order line, the project's CU is synced with the order CU, so it's basically impossible to reproduce our scenario.

Has anyone faced this problem before? Are there some strategies to apply in order achieve this?

Thanks in advance.

Hi Daniele,

As far as I know, organisational unit on project in PSA 3.x has no impact on any system behaviours (unlike on contract).

I was not aware that organisational unit on a project gets updated when you link the project to a contract. But it makes sense.

However if you do not like that behaviour, you could have a workflow or plugin that runs after any standard plugin and overwrites that.

You could then run your analysis on 'actuals'. You could build a query that looks at Billed Sales actuals. Actuals include 'Bookable Resource' (and you can check their resourcing unit) as well as 'Project' (and you can check its contracting unit).

So let's assume that the total of Billed Sales actuals is $100 and that $70 is coming from actuals where Contracting Unit and Resourcing Unit are the same ('local' resources scenario) and $30 is coming from actuals where Contracting Unit and Resourcing Unit are not the same ('borrowed' resources scenario). You could calculate it this way.

If you could design it differently, I would rather create 4 orders with 1 project each and keep the OU on both the same. With that setup you could use standard 'intercompany' actuals that get created when you lend and borrow resources between OUs. You might use a custom entity to link these contracts to a custom 'master contract' record and/or link these projects to a custom 'program' record.

I hope it helps a bit.

Kind regards

Matthew

Quick Links