locked
Timesheet entered hours are incorrectly recorded in the project schedule RRS feed

  • Question

  • We have Project Server 2010 and have the timesheet function set up as Single entry mode.  I have seen on a number of occasions where a timesheet is entered and the Timesheet and Status Updates are approved but when checking the schedule some time later, the actual hours in the schedule are different to the hours entered via the timesheet.

    I can confirm that the schedules have not been subsequently updated manually to enter different hours.

    In a current example, the planned hours are based on 40% units for a 40hr week which spreads the hours as 3.2 hrs per day (16 hrs per week).  The user actually works 2 full days per week (eg 8hr on two separate days - although the actual days varies from week to week).  He enters these hours in the timesheet (does not enter 0 hrs for the days he doesn't work), however once the Status Update is approved, in some weeks, one or two of the other days have the 3.2hrs recorded as actual hours.

    This does not happen every week and is not consistent regarding which days the incorrect hours appear. Has anyone ever seen this behaviour and if so, do you know how to resolve it?

    This is not an isolated incident and I am losing faith in relying on the schedule for the actual costs that are driven from this data.

    Peter

    Friday, May 15, 2015 4:07 AM

Answers

  • Hi,

    please check the patch level of Project Server. The issue you described has been fixed in the past (most of the time, there had been hours with decimals in project, even if whole hours had been entered in timesheet). Maybe your patch level is outdated. If so, I suggest to apply (SP and) current CU.

    Regards
    Barbara


    To increase the value of this forum, please mark the replies that helped to solve your issue as answer. If you find answers to questions from other forum participants to be helpful, please mark them as helpful. Your participation will help others to find an appropriate solution faster. Thanks for your support! !!!!!!!! Join the Project Virtual Conference 2015 from Oct 22-23, 2015 with a lot of support from the Microsoft Project Community - http://projectvirtualconference.com/ !!!!!!!!

    • Proposed as answer by PHanney Thursday, October 22, 2015 10:26 PM
    • Marked as answer by Barbara HenhaplMVP Wednesday, January 18, 2017 12:08 PM
    Thursday, October 22, 2015 8:38 AM

All replies

  • Hi,

      For the behavior that you have mentioned, you need to check out your project once after approvals to have the latest data fetched and to be made part of the plan. 

      Check if this is the case......

    ------------------------------

    Please mark as answer if the tip helped you resolve the prob. 

    Regards,

    Faizan.


    Regards, Syed Faizan ur Rehman, CBPM®,PRINCE2®, MCTS

    Sunday, May 17, 2015 11:06 AM
  • Hi Faizan

    Thanks for your response.  I have opened the schedule subsequent to the Status Updates being approved so the updates have been applied to the schedule.  This is not the issue.

    The issue is that the hours entered via the Timesheet are not always being reflected accurately in the schedule.

    I am still seing this type of behaviour from time to time on different schedules but can't identify any consistent behaviour that may give me a clue as to why it happens.  Unfortunately, as we track project costs in our schedules, we need the resource hours to be accurately reflected in the schedule and I am losing confidence in the information I can get from the schedules.

    Cheers

    Peter

    Thursday, October 22, 2015 6:05 AM
  • Hi,

    please check the patch level of Project Server. The issue you described has been fixed in the past (most of the time, there had been hours with decimals in project, even if whole hours had been entered in timesheet). Maybe your patch level is outdated. If so, I suggest to apply (SP and) current CU.

    Regards
    Barbara


    To increase the value of this forum, please mark the replies that helped to solve your issue as answer. If you find answers to questions from other forum participants to be helpful, please mark them as helpful. Your participation will help others to find an appropriate solution faster. Thanks for your support! !!!!!!!! Join the Project Virtual Conference 2015 from Oct 22-23, 2015 with a lot of support from the Microsoft Project Community - http://projectvirtualconference.com/ !!!!!!!!

    • Proposed as answer by PHanney Thursday, October 22, 2015 10:26 PM
    • Marked as answer by Barbara HenhaplMVP Wednesday, January 18, 2017 12:08 PM
    Thursday, October 22, 2015 8:38 AM
  • Thanks Barbara

    Your post just reminded me that we had begun the process last uyear to apply Project Server SP2 but when we did it in our TEST environment we had an issue with a custom field and started to investigate but never got to finish it. So we are only patched to SP1 in Production.

    I will re-initiate this to get SP2 installed and see if that fixes it.  I had a look at what SP2 fixes and there are issues around the correct recording of Actual work/costs that it resolves.  Hopefully appying SP2 will sort this out for me.

    I'll update this post with the result once SP2 is installed although due to the apparent randomeness of the issue, I may not be able to establish it has resolved this with any certainty for some time.

    Thanks for your input. 

    Peter

    Thursday, October 22, 2015 10:25 PM
  • Hi Barb

    Just realised I never replied to this post. We have updated to SP2 and I have not seen this behaviour appear again.  Seems that SP2 has fixed the issue.

    Thanks for your response.

    Peter

    • Proposed as answer by PHanney Wednesday, January 11, 2017 11:17 PM
    Wednesday, January 11, 2017 11:16 PM