Hi,
has anybody faced with the incorrect lag changes in claim digger report when you compare 2 schedules. For example, even the lag is not changed in both schedules, claim digger report is shown as it is changed. And it makes it in lots of activities. There is no problem in the report other than the relationship changes? When i telked with the primavera support, they said it might be happened in oracla database system.
Do you have any solution fir this?
I am facing the same problem and would appreciate it the most if anyone provided an explanation and/or solution.
Zachry - I've seen various anomolies discussed with me, but I've never seen one "in the wild" on my own. That said, the company I work for, Acumen (http://www.projectacumen.com) has a forensics module that should properly detect all lag changes (and changes to calendars, added/removed activities, any field changes, etc...) If you'd be interested in trying our software, it may readily solve this. Otherwise, I'd be interested in any files (sanitized) that have the problem in Claim Digger so that I can check this in the Acumen software.
Tom Polen
.
Resurrecting this thread I guess. I have the same problem... Digger showing relationship lags that have been deleted in the 'Revised' schedule, but that actually never existed in the 'Baseline.' Or lags that have been added in the 'Revised' schedule, but that actually already existed in the 'Baseline.'
Using P6 version 7.0
Is there a place ORACLE publishes reported bugs so their users are aware of these potential traps that can have significant time and cost impact?
Please provide the link for our knowledge, is seems there are plenty.
yes i have faced these prblem before and i would like to have the solution