The problem with setting a baseline resulting in the dates not matching when the baseline has progress is a problem. The simplest solution is to delete all the resources in P3 or P3e before you set the imported P3 baseline in P3e. P3e does not import Period Performance as it is project specific in P3 amongst other differences in calculating resource usage. The other option is to be familiar with the considerations when importing P3 into P3e. Refer to the hand book "Migrating from P3 to Primavaera V5.0", turn to page 76 and read carefully "Using Autocost Rules".
Member for
20 years 6 months
Member for20 years6 months
Submitted by Jihad Daniel on Fri, 2006-08-18 03:31
This issue was raised by one of my colleague and I already found the solution. For your information, one must be very careful when importing schedule from P3 to P5 then not missing any step in creating baseline and updating the P5 schedule.
Member for
19 years 6 monthsRE: Primavera Enterprise v.5.0 problem
The problem with setting a baseline resulting in the dates not matching when the baseline has progress is a problem. The simplest solution is to delete all the resources in P3 or P3e before you set the imported P3 baseline in P3e. P3e does not import Period Performance as it is project specific in P3 amongst other differences in calculating resource usage. The other option is to be familiar with the considerations when importing P3 into P3e. Refer to the hand book "Migrating from P3 to Primavaera V5.0", turn to page 76 and read carefully "Using Autocost Rules".
Member for
20 years 6 monthsRE: Primavera Enterprise v.5.0 problem
This issue was raised by one of my colleague and I already found the solution. For your information, one must be very careful when importing schedule from P3 to P5 then not missing any step in creating baseline and updating the P5 schedule.
Thanks anyway.
Regards,