ISSUE: Resource can delete a Project Server 2007 Timesheet after Timesheet Manager approval and clos

[Frank]

Hi,

We are currently in the implementation phase of Project Server 2007 and have
some issues with the Timesheets that compromise the data integrity in the
system. We are running Project Server 2007 SP1 with no specific Add Ons.
Below you'll find our results after testing the scenario's multiple times
(also in the Microsoft EPM Solution VPC):

Scenario I:
When a resource has Saved and Submitted a Project Server 2007 Timesheet to
his/her Timesheet Manager then the resource can still recall, adjust and
delete the Timesheet even after the Timesheet Manager has approved the
Timesheet.

Scenario II:
Same situation as above but when the corresponding period has been closed as
well then the resource can still recall the Timesheet, can no longer adjust
the information in the Timesheet but can still delete the Timesheet.

To us this is a very unwanted situation, in our opinion a resource should
not be able to recall a Timesheet after this Timesheet has been approved by
the Timesheet Manager. Approving the Timesheet should fixate it's status for
the resource. Only the Timesheet Manager should be able to recall the
approved Timesheet until the corresponding period has been closed, after
closing the period nobody should be able to make adjustments in the
Timesheets for that period any longer.

Hope this explains the situation we are currently dealing with. Don't
hesitate to contact me if more information is needed.

Best regards,

Frank Jutte

 

[Mike Mahoney]

Hi,

We are currently in the implementation phase of Project Server 2007 and have
some issues with the Timesheets that compromise the data integrity in the
system. We are running Project Server 2007 SP1 with no specific Add Ons.
Below you'll find our results after testing the scenario's multiple times
(also in the Microsoft EPM Solution VPC):

Scenario I:
When a resource has Saved and Submitted a Project Server 2007 Timesheet to
his/her Timesheet Manager then the resource can still recall, adjust and
delete the Timesheet even after the Timesheet Manager has approved the
Timesheet.

Scenario II:
Same situation as above but when the corresponding period has been closed as
well then the resource can still recall the Timesheet, can no longer adjust
the information in the Timesheet but can still delete the Timesheet.

To us this is a very unwanted situation, in our opinion a resource should
not be able to recall a Timesheet after this Timesheet has been approved by
the Timesheet Manager. Approving the Timesheet should fixate it's status for
the resource. Only the Timesheet Manager should be able to recall the
approved Timesheet until the corresponding period has been closed, after
closing the period nobody should be able to make adjustments in the
Timesheets for that period any longer.

Hope this explains the situation we are currently dealing with. Don't
hesitate to contact me if more information is needed.

Best regards,

Frank Jutte

Frank

Unfortunately your analysis is correct, and I am sure everyone agrees
with your opinion.

regards

Mike

 

[Frank]

Hi,

Regarding the Timesheet issue I described I received the following reaction
from MSFT corp.:

Period close is designed to block new entries not changes which include
deletions. There is a Flag field in the PSI dataset that is called
TS_IS_PROCESSED. This can be set by a custom event or scrip when the period
is closed for timesheets within the period or as originally designed, when
the timesheet has been exported to a third party system for processing. In
2007, we are looking at the data from a position where the system of record
can modify the data and to help customers determine when Project Server is
no longer the system of record, we are leaving it up to the customer to
check that flag. After the flag is set to true then no action can be
performed on the timesheet except by duly authorized system administrators
for adjustments theoretically coming from the third party system.

I hope this gives you a good background as to the rationale behind the
design and a good idea of how to configure the system to comply with varying
company policies at customer sites.

Rgds,

Frank Jutte

Hi,

We are currently in the implementation phase of Project Server 2007 and
have
some issues with the Timesheets that compromise the data integrity in the
system. We are running Project Server 2007 SP1 with no specific Add Ons.
Below you'll find our results after testing the scenario's multiple times
(also in the Microsoft EPM Solution VPC):

Scenario I:
When a resource has Saved and Submitted a Project Server 2007 Timesheet to
his/her Timesheet Manager then the resource can still recall, adjust and
delete the Timesheet even after the Timesheet Manager has approved the
Timesheet.

Scenario II:
Same situation as above but when the corresponding period has been closed
as
well then the resource can still recall the Timesheet, can no longer
adjust
the information in the Timesheet but can still delete the Timesheet.

To us this is a very unwanted situation, in our opinion a resource should
not be able to recall a Timesheet after this Timesheet has been approved
by
the Timesheet Manager. Approving the Timesheet should fixate it's status
for
the resource. Only the Timesheet Manager should be able to recall the
approved Timesheet until the corresponding period has been closed, after
closing the period nobody should be able to make adjustments in the
Timesheets for that period any longer.

Hope this explains the situation we are currently dealing with. Don't
hesitate to contact me if more information is needed.

Best regards,

Frank Jutte

Frank

Unfortunately your analysis is correct, and I am sure everyone agrees
with your opinion.

regards

Mike

 

[Mike Mahoney]

Hi,

Regarding the Timesheet issue I described I received the following reaction
from MSFT corp.:

Period close is designed to block new entries not changes which include
deletions.  There is a Flag field in the PSI dataset that is called
TS_IS_PROCESSED.  This can be set by a custom event or scrip when the period
is closed for timesheets within the period or as originally designed, when
the timesheet has been exported to a third party system for processing.  In
2007, we are looking at the data from a position where the system of record
can modify the data and to help customers determine when Project Server is
no longer the system of record, we are leaving it up to the customer to
check that flag.  After the flag is set to true then no action can be
performed on the timesheet except by duly authorized system administrators
for adjustments theoretically coming from the third party system.

I hope this gives you a good background as to the rationale behind the
design and a good idea of how to configure the system to comply with varying
company policies at customer sites.

Rgds,

Frank Jutte











Frank

Unfortunately your analysis is correct, and I am sure everyone agrees
with your opinion.

regards

Mike- Hide quoted text -

- Show quoted text -

Frank

Frank

This is interesting but does not really explain why a user is allowed
to recall a timesheet from a closed period and cannot change it, but
can delete it. Logic suggests you should be able to do both or
neither. Prefarably the latter as the system will not allow you to
recreate the timesheet in a closed period once it has been deleted

regards

Mike