Maybe it is because WBS duration is a calculated value (*) and not a fixed entry is why it behaves in this way.
I can think of two workarounds.
Use global change and store original duration as a user defined field, in this way it will be frozen at the activity level as well as at the WBS level, verify on this as I am not a P6 user, I am applying what I recall from my previous use of P3e, P3 and SureTrak.
Store your initial job as a baseline and on updates display baseline original duration next to current schedule original duration.
Hope this helps.
Member for
16 years 1 month
Member for16 years1 month
Submitted by Arun Vasanth on Sun, 2011-08-14 12:40
Member for
16 years 1 monthHai Artagnan I updated
Hai Artagnan
I updated Program Manually..
Regards
Arun
Member for
17 years 1 monthArun,How did you update the
Arun,
How did you update the program? Manually or some external application such as excel or SDK?
Member for
17 years 1 monthArun,How did you update the
Arun,
How did you update the program? Manually or some external application such as excel or SDK?
Member for
21 years 8 monthsMaybe it is because WBS
Maybe it is because WBS duration is a calculated value (*) and not a fixed entry is why it behaves in this way.
I can think of two workarounds.
Use global change and store original duration as a user defined field, in this way it will be frozen at the activity level as well as at the WBS level, verify on this as I am not a P6 user, I am applying what I recall from my previous use of P3e, P3 and SureTrak.
Store your initial job as a baseline and on updates display baseline original duration next to current schedule original duration.
Hope this helps.
Member for
16 years 1 monthHai Friends Any experts to
Hai Friends
Any experts to answer my above question????
regards
Arun