MSP New Driver: Start Dates are changing to Actual Thru Date for Resource even though Constraints are Set

Document ID : KB000112714
Last Modified Date : 21/09/2018
Show Technical Document Details
Issue:
When exporting a project to MSP, Task Start dates are changing to the Actual Thru date of the assignee for tasks that don't have any time posted against them and even though constraints are set on the task. The task start date will change to the first working day after the actual thru date for the resource on the project if the Actual thru date falls on a weekend. This does not happen for tasks that have actuals posted. 

Additionally:
  • For tasks with this issue, you can also see in the Time Scale Task Usage view in MSP, that 0s are entered in the Timescale starting on the Actual Through date through where ETCs first are populated)
  • Additionally, the Actual Start date is generated for these tasks even though there the % Complete is 0, and no actual hours were posted when it is expected the Actual Start date shows as 'NA'
Steps to Reproduce: 
1. Create a project in PPM (open for time with track mode PPM) 
2. Add one resource to the project team (make sure they are open for time and track mode of PPM) 
3. Create 2 tasks: 
  • Task1: 
    • Fixed Duration with start date 7/1/2018 and finish date 7/13/2018 
    • Assign resource to task (with 10 hours ETC) 
  • Task2: 
    • Fixed Duration with start date 3/25/19 and finish date 03/29/19 
    • Start No Earlier Constraint of 3/25/19 
    • Assign resource to task with 5 hours of ETCs 
4. For the user added to the team, submit 8 hours of ETC for task1 with the last hours entered on the time sheet 
  • Go to the timesheet for 7/9/18 – 7/15/18 in the new UX 
  • Ensure Assigned Tasks is selected then click Create Timesheet 
  • Enter 2 hours of work for 7/10, 7/11, 7/12, and 7/13 
  • Click Submit 
  • Click Approve 
  • Wait 5 minutes then run the Post Timesheets job 
            (Note that the actuals thru date on the Team tab is now 7/15/18)
5. Export the project from PPM to MSP 
6. Observe the start date for task 2 

Expected Results: The task start days stays as 3/25/19 
Actual Results: The task start date changes to 7/16/18, which is the first working day after the actual thru date for the resource on the project. 
Notes:
  • This does not happen for tasks that have actuals posted. 
  • For tasks with this issue, you can also see in the Time Scale Task Usage view in MSP, that 0s are entered in the Timescale starting on the Actual Through date through where ETCs first are populated) 
  • The Actual Start date is generated for these tasks even though there the % Complete is 0, and no actual hours were posted. 
Environment:
This issue applies to the MSP New Driver
Cause:
This is caused by DE44318 
Resolution:
This issue is currently under review

Workaround: Change the task type to manually scheduled but then tasks will not auto calculate based on changes to the schedule. If considering this option, see KB000047612 - What are the recommendations for Auto Scheduled versus Manually Scheduled tasks working in Microsoft Project (MSP) with PPM

Additionally, tasks must first be created originally in auto scheduled mode in MSP to ensure start/finish dates for tasks populate. To use this workaround on impacted tasks: 

1. Export the project from PPM to MSP 
2. Highlight all the tasks you want to change to Manually scheduled 
3. Go to the Task tab in MSP and click the Manually Schedule icon in the menu icon bar 
4. Correct the date of the task(s) (at this point, the Remaining work is dropped, and task then changes to a milestone) 
5. Add Remaining Work to the task 
6. Correct the duration of the task 
7. Change the Remaining work again to the correct amount 
Additional Information:
Reference KB000071385 - CA PPM and MSP integration - List of Knowledge Documents
Reference KB000015956 - CA PPM and MSP integration known defects - Support Technical Document Index