Quantcast
Channel: Primavera Online Interaction » Activity Duration
Viewing all articles
Browse latest Browse all 83

prim17039:Finish dates are not correct based on duration.

$
0
0
Solution ID: prim17039
Finish dates are not correct based on duration.
Status: Reviewed
Version(s): 3.5, 3.5, 3.5.1, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1



Problem: Finish dates are wrong based on duration
Problem: Finish date is later than expected
Problem: The Start and Finish dates do not correspond to the duration of the activity.
Problem: Early Finish date is not calculated as the Data date plus the Remaining duration.
Problem: Finish date does not match duration
Problem: Finish dates are incorrect
Problem: Early Finish is not correct
Fix: There are several reasons why this may occur:

1. Out of sequence progress exists in the project and Retained Logic is being used. To determine if this is the case, go to Tools, Schedule and create a schedule log. In the schedule log, see if any activities are listed in Out-of-Sequence Progress section. If any activities are listed there, go to Tools, Schedule, Options and select Progress Override and reschedule the project. If the Finish date is “corrected” then Out of Sequence progress exists in your project. For more information on Retained Logic and Progress Override, please see solution, prim31743:  prim31743:  Retained Logic, Progress Override and Actual Dates settings explained.


2. Multiple calendars are in use, and one or more of them does not correspond to the Time Periods setting under Admin, Admin Preferences. In this case, durations should be displayed and entered in hours. For more information, please see solution, prim1511:   prim1511:  Start and Finish dates of an activity do not match the duration when the duration is not entered in hours.


3. Display durations and dates in hours by going to Edit, User Preferences. Edit the duration format under the Time Units tab. Edit the dat format under the Dates tab. If Finish dates are off by 1 minute, see solution, prim15994:  prim15994: Finish date is stretching out 1 day beyond the duration.


If durations are not whole days, correct the duration. Also see solution, prim1511:  prim1511:  Start and Finish dates of an activity do not match the duration when the duration is not entered in hours. for a possible explanation of why the durations are not in whole days.


4.  Activity has an “As late as possible” constraint. The As late as possible constraint allows an activity to start or finish as late as possible without delaying its successors. This constraint sets the early dates as late as possible without affecting successor activities. Even if the activity is started, the Finish date can be pushed later in time if positive total float exists when the As late as possible constraint is applied. This will make the Finish date appear to be later than it would be based on the remaining duration.


5. The activity calendar contains nonwork time that is pushing the finish date out.


6. Make sure that Level resources during scheduling is unchecked



7. Project has Activities with Actual Dates > Data Date causing incorrect activity dates. To determine if this is the case, go to Tools, Schedule and create a schedule log. In the schedule log, see if any activities are listed in the Activities with Actual Dates > Data Date section. Fix those activities by either removing the actual dates, or moving the data date forward beyond those actual dates.


Viewing all articles
Browse latest Browse all 83

Trending Articles