Finish Date set to an incorrect Status Date

[Garon]

We have set [Tools | Options | Calculation Tab ]
"Move end of completed parts after status back to status date" flag to
checked

However when we update a task to 100% complete with a Finish Date planned to
a date in the future, then approve the Status Update the Finish Date is being
set to a date one day prior to the status date.

The [Project | Project Information | Current Date] = "Fri 5/08/05" (Today's
Date)
The [Project | Project Information | Status Date] = "NA" (ie blank)
The [Task Information | Start] = "Fri 5/08/05"
The [Task Information | Duration] = "7 Days"
On "Fri 5/08/05" we set the Task Status to 100% complete in PWA. The
Manager then approves the Status Update on "Fri 5/08/05".

This should set the Finish Date to "Fri 5/08/05", but it is setting it to
"Thu 4/08/05".

If we set [Project | Project Information | Status Date] = "Fri 5/08/05"
and redo the test we are presented with a pompt advising the Status Date is
nt equal to the Current Date and asking which date do we want to use. The
Current Date in Project Information is definitely set to "Fri 5/08/05". The
dates shown in PWA for the Date the Status Update was sent for approval is
showing "Fri 5/08/05".

The Project Professional client workstation has a system date of "Fri
5/08/05".
The Project Server & SQL Server (SBS) has a system date of "Fri 5/08/05"

The [Task Information | Advanced Tab | Constraint Type] = "As Soon as
Possible"
The [Task Information | Advanced Tab | Task Type] = "Fixed Units"
The [Task Information | Advanced Tab | Effort Driven] = "Checked"
The [Task Information | Advanced Tab | Calendar] = "Standard"(Inchanged)
The Resource Calendar is also set to Standard

Has anyone had a similar experience. It is critical to our operations that
the "Finish Date" is set accurately to the Current Date.

 

[Gary L. Chefetz [MVP]]

Garon:

Where is the task getting its start date from?

 

[Garon]

In our test cases the "Project Start Date". The Task is set to "Start As Soon
as Possible" and has not predecessors.

We get similar results if we have a predecessor set "Start Date".

We do not use hard dates with the exception of a single unbound Project
Target Date, which we use for CPM alerts.
--
Garon Line

Garon:

Where is the task getting its start date from?

We have set [Tools | Options | Calculation Tab ]
"Move end of completed parts after status back to status date" flag to
checked

However when we update a task to 100% complete with a Finish Date planned
to
a date in the future, then approve the Status Update the Finish Date is
being
set to a date one day prior to the status date.

The [Project | Project Information | Current Date] = "Fri 5/08/05"
(Today's
Date)
The [Project | Project Information | Status Date] = "NA" (ie blank)
The [Task Information | Start] = "Fri 5/08/05"
The [Task Information | Duration] = "7 Days"
On "Fri 5/08/05" we set the Task Status to 100% complete in PWA. The
Manager then approves the Status Update on "Fri 5/08/05".

This should set the Finish Date to "Fri 5/08/05", but it is setting it to
"Thu 4/08/05".

If we set [Project | Project Information | Status Date] = "Fri 5/08/05"
and redo the test we are presented with a pompt advising the Status Date
is
nt equal to the Current Date and asking which date do we want to use. The
Current Date in Project Information is definitely set to "Fri 5/08/05".
The
dates shown in PWA for the Date the Status Update was sent for approval is
showing "Fri 5/08/05".

The Project Professional client workstation has a system date of "Fri
5/08/05".
The Project Server & SQL Server (SBS) has a system date of "Fri 5/08/05"

The [Task Information | Advanced Tab | Constraint Type] = "As Soon as
Possible"
The [Task Information | Advanced Tab | Task Type] = "Fixed Units"
The [Task Information | Advanced Tab | Effort Driven] = "Checked"
The [Task Information | Advanced Tab | Calendar] = "Standard"(Inchanged)
The Resource Calendar is also set to Standard

Has anyone had a similar experience. It is critical to our operations
that
the "Finish Date" is set accurately to the Current Date.

 

[Gary L. Chefetz [MVP]]

One possible explanation is that the system can't find 7days of availability
on the resource calendar that ends at the status date. When the scheduling
engine moves a 7-day duration, effort-driven task, it has to find 56
continuous hours of availability on corresponding resource calendar to move
the task back or forward, assuming an 8 hour work day. What's really going
on here? Did the task actually take the full seven days and the
corresponding effort of 56 hours?

Apparently you're not tracking effort, so it seems odd that you'd cast the
tasks as effort-driven to begin with. Further, when tracking by percent work
complete, you really need to capture actual start and actual finish if you
expect the system to be able record a somewhat accurate record of actual
work and actual dates.

In our test cases the "Project Start Date". The Task is set to "Start As
Soon
as Possible" and has not predecessors.

We get similar results if we have a predecessor set "Start Date".

We do not use hard dates with the exception of a single unbound Project
Target Date, which we use for CPM alerts.
--
Garon Line

Garon:

Where is the task getting its start date from?

We have set [Tools | Options | Calculation Tab ]
"Move end of completed parts after status back to status date" flag to
checked

However when we update a task to 100% complete with a Finish Date
planned
to
a date in the future, then approve the Status Update the Finish Date is
being
set to a date one day prior to the status date.

The [Project | Project Information | Current Date] = "Fri 5/08/05"
(Today's
Date)
The [Project | Project Information | Status Date] = "NA" (ie blank)
The [Task Information | Start] = "Fri 5/08/05"
The [Task Information | Duration] = "7 Days"
On "Fri 5/08/05" we set the Task Status to 100% complete in PWA. The
Manager then approves the Status Update on "Fri 5/08/05".

This should set the Finish Date to "Fri 5/08/05", but it is setting it
to
"Thu 4/08/05".

If we set [Project | Project Information | Status Date] = "Fri
5/08/05"
and redo the test we are presented with a pompt advising the Status
Date
is
nt equal to the Current Date and asking which date do we want to use.
The
Current Date in Project Information is definitely set to "Fri 5/08/05".
The
dates shown in PWA for the Date the Status Update was sent for approval
is
showing "Fri 5/08/05".

The Project Professional client workstation has a system date of "Fri
5/08/05".
The Project Server & SQL Server (SBS) has a system date of "Fri
5/08/05"

The [Task Information | Advanced Tab | Constraint Type] = "As Soon as
Possible"
The [Task Information | Advanced Tab | Task Type] = "Fixed Units"
The [Task Information | Advanced Tab | Effort Driven] = "Checked"
The [Task Information | Advanced Tab | Calendar] =
"Standard"(Inchanged)
The Resource Calendar is also set to Standard

Has anyone had a similar experience. It is critical to our operations
that
the "Finish Date" is set accurately to the Current Date.

 

[Garon]

Gary, Thanks for your support/contribution.

We do not really care about work or duration, but need to track accurate
details on when tasks are completed. AN original schedule is defined with
expected durations for each activity. All Activities are linked via
Predecessor/Successor relationships and the CPM is monitored carefully.

Staff are required to status projects to state when their activities are
completed. The company does not mind too much if the Work/Duration needs to
change.

The desired outcome for a task that finishes early is that the Work and
Duration would both be reduced to relfect the work being completed sooner
than expected. This is why we have selected Fixed Units. We have tried
setting the Effort Driven to Checked and Un-checked. Both cause the same
problem. Work/Duration try to stay constant and the task is set to have
start earlier.

Our desired outcome would be that the Start Date stays constant. The Finish
Date moves back to the Current Date (Status Date). The work/duration and if
necessary the Units can all change to relfect that the task could be competed
in a shorter time frame.

What settings must we define to achieve this result.

Regards
Garon Line

We have set [Tools | Options | Calculation Tab ]
"Move end of completed parts after status back to status date" flag to
checked

However when we update a task to 100% complete with a Finish Date planned to
a date in the future, then approve the Status Update the Finish Date is being
set to a date one day prior to the status date.

The [Project | Project Information | Current Date] = "Fri 5/08/05" (Today's
Date)
The [Project | Project Information | Status Date] = "NA" (ie blank)
The [Task Information | Start] = "Fri 5/08/05"
The [Task Information | Duration] = "7 Days"
On "Fri 5/08/05" we set the Task Status to 100% complete in PWA. The
Manager then approves the Status Update on "Fri 5/08/05".

This should set the Finish Date to "Fri 5/08/05", but it is setting it to
"Thu 4/08/05".

If we set [Project | Project Information | Status Date] = "Fri 5/08/05"
and redo the test we are presented with a pompt advising the Status Date is
nt equal to the Current Date and asking which date do we want to use. The
Current Date in Project Information is definitely set to "Fri 5/08/05". The
dates shown in PWA for the Date the Status Update was sent for approval is
showing "Fri 5/08/05".

The Project Professional client workstation has a system date of "Fri
5/08/05".
The Project Server & SQL Server (SBS) has a system date of "Fri 5/08/05"

The [Task Information | Advanced Tab | Constraint Type] = "As Soon as
Possible"
The [Task Information | Advanced Tab | Task Type] = "Fixed Units"
The [Task Information | Advanced Tab | Effort Driven] = "Checked"
The [Task Information | Advanced Tab | Calendar] = "Standard"(Inchanged)
The Resource Calendar is also set to Standard

Has anyone had a similar experience. It is critical to our operations that
the "Finish Date" is set accurately to the Current Date.

 

[Gary L. Chefetz [MVP]]

Garon:

You *have to* care about work and duration because they're part of the
formula. You may wish to track your project as if you're using Excel,
however you're using Project. Project uses Units, duration and work in its
algorithm; so must you. I think your answer is to collect actual start and
actual finish dates from your resources, like I said in my last reply. Add
these to your published fields in each project and then train your users.
Fixed units should work for you however you'll want to uncheck effort driven
on all tasks.

Gary, Thanks for your support/contribution.

We do not really care about work or duration, but need to track accurate
details on when tasks are completed. AN original schedule is defined with
expected durations for each activity. All Activities are linked via
Predecessor/Successor relationships and the CPM is monitored carefully.

Staff are required to status projects to state when their activities are
completed. The company does not mind too much if the Work/Duration needs
to
change.

The desired outcome for a task that finishes early is that the Work and
Duration would both be reduced to relfect the work being completed sooner
than expected. This is why we have selected Fixed Units. We have tried
setting the Effort Driven to Checked and Un-checked. Both cause the same
problem. Work/Duration try to stay constant and the task is set to have
start earlier.

Our desired outcome would be that the Start Date stays constant. The
Finish
Date moves back to the Current Date (Status Date). The work/duration and
if
necessary the Units can all change to relfect that the task could be
competed
in a shorter time frame.

What settings must we define to achieve this result.

Regards
Garon Line

We have set [Tools | Options | Calculation Tab ]
"Move end of completed parts after status back to status date" flag to
checked

However when we update a task to 100% complete with a Finish Date planned
to
a date in the future, then approve the Status Update the Finish Date is
being
set to a date one day prior to the status date.

The [Project | Project Information | Current Date] = "Fri 5/08/05"
(Today's
Date)
The [Project | Project Information | Status Date] = "NA" (ie blank)
The [Task Information | Start] = "Fri 5/08/05"
The [Task Information | Duration] = "7 Days"
On "Fri 5/08/05" we set the Task Status to 100% complete in PWA. The
Manager then approves the Status Update on "Fri 5/08/05".

This should set the Finish Date to "Fri 5/08/05", but it is setting it to
"Thu 4/08/05".

If we set [Project | Project Information | Status Date] = "Fri 5/08/05"
and redo the test we are presented with a pompt advising the Status Date
is
nt equal to the Current Date and asking which date do we want to use.
The
Current Date in Project Information is definitely set to "Fri 5/08/05".
The
dates shown in PWA for the Date the Status Update was sent for approval
is
showing "Fri 5/08/05".

The Project Professional client workstation has a system date of "Fri
5/08/05".
The Project Server & SQL Server (SBS) has a system date of "Fri 5/08/05"

The [Task Information | Advanced Tab | Constraint Type] = "As Soon as
Possible"
The [Task Information | Advanced Tab | Task Type] = "Fixed Units"
The [Task Information | Advanced Tab | Effort Driven] = "Checked"
The [Task Information | Advanced Tab | Calendar] = "Standard"(Inchanged)
The Resource Calendar is also set to Standard

Has anyone had a similar experience. It is critical to our operations
that
the "Finish Date" is set accurately to the Current Date.