none
Project Server 2010 : Data mismatch Winproj, PWA and Reporting RRS feed

  • Question

  • Hello Experts,

    I have described following two scenarios related to well-known issue of data mismatch in Project.

    Please have a look and share your option.  Workaround mentioned below acts as a band aid, looking for some additional information before opening support case with Microsoft.

    Issue:

    Timesheet data mismatch between Winproj , PWA and Reporting

    Environment: 

    Project Server 2010, Project Pro 2010

    Non migrated instance

    CU: SP1, June 2011 CU and DEC 2011 CU

    Issue is not user or project specific.

                

    Scenario 1 (task 1)

    • User submits the timesheet  with AW as 1 hr each from 06/04 to 06/08
    • Submits  timesheet, Status Manager approves the Task update, Timesheet has been approved by Timesheet Manager and PM has published the project plan without any errors

    Actual Result

    06/04    06/05    06/06    06/07    06/08

    0             0             1             0             0

    Expected Result

    06/04    06/05    06/06    06/07    06/08

    1             1             1             1             1

    Observation

    If user recalls the timesheet and re-enter missing AW, and submits the timesheet, Task update notification has not been sent to status manager, which indicates to me, updates we present somewhere in the database

    Recalling and resubmitting the timesheet can be considered as workaround but not solution

    Scenario 2 (task 2)

    • User submitted timesheet update with 1 hr each from 06/04 to 06/08
    • Task update approved.
    • User recalls the timesheet and removes  AW for 04, 05 ,07, 08 and enters AW as  2 hr on 06/06,
    • Submits  timesheet, Status Manager approves the Task update, Timesheet has been approved by Timesheet Manager and PM has published the project plan without any errors

    Actual Result

    06/04    06/05    06/06    06/07    06/08

    1             1             2             1             1

    Expected Result

    06/04    06/05    06/06    06/07    06/08

    0             0             2             0             0

    Workaround

    Recalling and re-submitting the timesheet


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Tuesday, August 7, 2012 11:46 PM
    Moderator

All replies

  • Hi Hrishi,

    Can you please share with me what tables are you using?

    is it timesheetActual? Also, have you tried Protecting user updates? by selecting the  "Only allow task updates via Tasks and Timesheets check box ".  Thanks

    Wednesday, August 8, 2012 1:28 PM
  • First I am trying to address Winproj and PWA issue,  I don’t think Only allow task updates via Tasks and Timesheets check box can help here, because problem is as per the flow of the task update everything is fine, my perception is this issue is one of the problem where transaction is lost somewhere in the backend.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Wednesday, August 8, 2012 2:16 PM
    Moderator
  • Hi Hrishi,

    I've also experienced this issue at one of my clients. They're currently at the December 2011 CU (installing the June 2012 CU next week). Unfortunately, this is one of those transient issues that is extremely hard to trace. Unless you're running a SQL trace when the transactions are applied it's very hard to discover what has taken place. This is the first time we have seen this issue.

    In my client's example the time in the timesheet was booked to the overtime row on a weekend and this did not transfer through to the plan. There is approval history of the transaction in the timesheet and status update histories respectively, no failed queue jobs and nothing obvious in the ULS logs. The client is using single entry mode, but not restricting task updates.

    I don't have any answers yet, but will try and update if we find anything.

    Lester

    Tuesday, August 21, 2012 9:31 AM