One can, out of the box, update task baselines in CA PPM, OWB, MSP - baselines aren't necessarily static forever, allowing one to take into account significant changes due to major events outside the project team's control, such as a customer significantly altering due dates and/or requirements. Updating Task baselines allows one to keep the baselines unchanged for completed work, changing only those dates for incomplete work.
However, these Task baseline updates do not impact the Project Baseline Start or Baseline Finish dates, as Pilar appears to have discovered.
Sue, good idea - I'd expand on this by having the process kick off whenever a Task Baseline Finish date changes. It could then check to see if the latest task/milestone is <> project Baseline Finish, and then update project Baseline Finish accordingly.
No need for a special milestone that people must remember to put into their project and then remember to include when they perform task baseline updates.
Another thought, rather than alter the behavior of the out of the box Project Baseline Finish Date field, create a new date attribute on the Project Object, call it "Project Baseline Finish Date Revised" (or something better) and make it 'read-only.' Copy the new date to this new attribute, leaving the out of the box attribute unchanged:
- Keeps the out of the box capabilities unaltered, avoiding any problems that one might have with Gantt, MSP and/or OWB
- Provides a means to detect, report on projects where PBLFD <> PBLFDR
- Maintains record of what the original finish date was supposed to be
- Avoids CA issues that Abhisek is referring to
What do you think?