Using mixed Resource Types
joooles
plans fail to 'publish' into PWA. One of the causes thought is that these
plans have both cost and work type resources within the same task.
Is it good practice to separate these resource types into different tasks?
--
joooles
G�rard Ducouret
It seems it's a bad pratice. Please see the posts I noticed several month
ago:
G�rard Ducouret
------------------------------------
If we assign a Cost resource to a task (as the only one resource on that
task) and then we enter some % Complete, Project Pro 2007 calculates the
Actual Cost correctly.
If we assign a Cost resource to a task besides a Work resource, and then we
enter some % Complete, Project Pro 2007 does not calculate any Actual Cost
for the Cost resource.
Answer 1:
Because of this and because Cost Resources inappropriately affect duration,
you need to define a separate task for cost resources in order to use them
effectively.
Answer 2: Eric M. Zenz (MSFT) <ez...@microsoft.om>
% Complete functions differently when the assignment only contains a cost
resource vs. a mixture of cost and work or material. This is by design.
We can only infer that the % complete refers to the completion of
expenditure of money if the only assignment is a cost assignment. When the
assignments are mixed, we must assume or infer that the task % complete
applies to work progress and not cost progress for legacy reasons. The
workaround you describe is the suggested best practice use.
-------------------------------------
"joooles" <joo...@discussions.microsoft.com> a �crit dans le message de
news: D9B9D1E0-1B58-4BBF...@microsoft.com...
Dale Howard [MVP]
To expand on what Gerard told you in his post, Microsoft officially
recommends that you DO NOT assign Cost resources to tasks on which you also
assign enterprise resources who report progress from PWA. Microsoft
released this recommendation in the summer of 2008 after they released SP1
and the Infrastructure Update. I think you see that this recommendation
needlessly complicates the user of Cost resources, but at least your problem
confirms that Microsoft's recommendation is solid. Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
"joooles" <joo...@discussions.microsoft.com> wrote in message
news:D9B9D1E0-1B58-4BBF...@microsoft.com...
Mike Glen
Project MVP
"Gérard Ducouret" <ducouret.ger...@THATfree.fr> wrote in message news:eG6KcKJh...@TK2MSFTNGP05.phx.gbl...
Hello joooles,
It seems it's a bad pratice. Please see the posts I noticed several month
ago:
Gérard Ducouret
------------------------------------
If we assign a Cost resource to a task (as the only one resource on that
task) and then we enter some % Complete, Project Pro 2007 calculates the
Actual Cost correctly.
If we assign a Cost resource to a task besides a Work resource, and then we
enter some % Complete, Project Pro 2007 does not calculate any Actual Cost
for the Cost resource.
Answer 1:
Because of this and because Cost Resources inappropriately affect duration,
you need to define a separate task for cost resources in order to use them
effectively.
Answer 2: Eric M. Zenz (MSFT) <ez...@microsoft.om>
% Complete functions differently when the assignment only contains a cost
resource vs. a mixture of cost and work or material. This is by design.
We can only infer that the % complete refers to the completion of
expenditure of money if the only assignment is a cost assignment. When the
assignments are mixed, we must assume or infer that the task % complete
applies to work progress and not cost progress for legacy reasons. The
workaround you describe is the suggested best practice use.
-------------------------------------
"joooles" <joo...@discussions.microsoft.com> a écrit dans le message de