Save actuals automatically sent to PM's update

T

TP

Hello

Description: Resource R1 enters 7H on Task T1 for Monday April 24 and hits
on Update all. The 7H is sent then for project manager Update. The 7H is
pending for Update. R1 enters then 8H on T1, for Tuesday 25 April and hits on
SAVE.

Expected result: 7H for Project Manager update.

Actual result: 15H for Project Manager update: the 8H that has just been
saved and not sent by R1. However it has automatically been sent for update.

Please let me know if you have observed the same behaviour from EPM SP2a.
Thanks
 
G

Gary L. Chefetz [MVP]

TP:

Unfortunately, Project Server is not as granularly transactional as you
expect. Think of it this way, each of your resources has a timesheet bucket.
Each time a resource sends an update, they're essentially sending a message
to the PM, "please empty my bucket" and sets a status "ready to empty" on
the data set. If bucket emptying agent, the PM, doesn't empty the bucket,
the resource doesn't get a new bucket.

To ensure that you get "expected" results, or "apparently consistent"
results from the system, you should follow a structured update process so
that updates are entered, sent, and accepted in a prescriptive structure
that meets your business requirements. Some business needs demand that this
cycle happen on a daily basis while the most typical update cycle is weekly.
Whatever cycle you set, your challenge is to make sure that participation is
consistent.
 
Top