Good Old EV again
Forum Sponsor
Top Posters
Nick Johnson-Pond
3 posts
sairedz25
0 posts
Ahmed Awad
2 posts
Syed Shoeb
0 posts
Vimukthi
0 posts
bal aji
2 posts
Lee Mallek
23 posts
Viet Tran
9 posts
Ola Gbotoso
0 posts
Jaturapit Multongka
1 posts
Thanks for the replies guys. But i have checked all that. We are entering data directly into P3e not using timesheets etc. I have checked the start and finish times, actual and planned and they are spot on to the minute. So is the schedule data date. Check just about everything that I can check and used everything in my knowledge base as it were.
Really running out of ideas here. It has been logged with POINT but as yet no response - we have to go via a helpdesk internally first.
Ho hum
Nige
Hi Nigel
One thing do worth checking is the time(Hrs and min) in your actual finish date
to do that you need to switch on the time element and check whether the any of the finish date is cross over the 5:00pm mark(I think) it caused the system travel over the boundary.
In addition, if you are using P5 or later version, you can use the cost profile and select the time scale in days and tick the time period option and select the time period which have actual over the Data day line and carefully check those activities
HTH
ALex
Nigel,
Are you entering actuals manually, auto-computing, or using the timesheets module to record actual performance?
Have you checked the start and end dates of the periods you have created, just to ensure that there is no overlap?