none
Updating Calendar for a future non working day redistributes past actuals RRS feed

  • Question

  • Hello

    We are using MS Project 2007 professional SP3

    When want to change 11/12/2018 and other veteran's day's for 2019 and 2020 as non working as it has become a holiday in our company.

    The issue is that when we do this it re-distributes actuals that have occurred in the past. It keeps the total but from last week and then back through time actuals get redistributed.  Our timephased area is by weeks and we gather actuals from resources and post per week. we can see it changing when we go to csc task usage.

    We don't want those actuals changing. Is there an option setting

    Any way to keep it from doing that just because we want to change non working time that is in the future?

    Friday, September 22, 2017 4:00 PM

All replies

  • Hotmail1,

    Adding non-working days in the future to your calendar should not impact actuals, but we need a little more information. Are all tasks forward scheduled (i.e. from Project start date)? What are your task types (i.e. fixed work, fixed duration, or fixed units)? Does the change in actuals impact all tasks or just a single task?

    What are your settings for "calculation options for this project" (i.e. these settings)?

    Can you post a screen shot showing the impact?

    John

    Friday, September 22, 2017 6:07 PM
  • All tasks are forward scheduled from Project STATUS DATE

    Task types are ALL FIXED WORK

    I'll have to check the change in actuals. I think it is on open tasks but not total sure of that yet.

    We use Update Project reschedule uncompleted work to start after the Friday of each week moving any uncompleted week beyond that date which is STATUS DATE. We change STATUS DATE each week.

    This week the date is 9/22/17.

    Our Calculation options for those specific ones you showed are as you showed them with the following exception...........

    We have checked Edits to total task % complete will be spread to status date

    Friday, September 22, 2017 6:41 PM
  • Hotmail1,

    An example of the issue would be most helpful.

    Can you reproduce the issue on a small test file that you could send to me if I give you my e-mail?

    And just for reference, earlier this year (May 2017) you posted a question saying you are using Project 2013. This current posting says you are using Project 2007. It seems kind of strange that you would go back to an older, less reliable version. Care to explain?

    John


    • Edited by John - Project Sunday, September 24, 2017 3:28 PM question
    Friday, September 22, 2017 7:59 PM
  • Hello

    Sure. However, please see the following;

    Also, I unchecked everything under calculation, moved to manual, updated 11/12/2018 to non working and hours still shifted

    add holiday    %   comp                             ID                  des cription actuas7/1/2017 7/8/2017 7/15/2017 7/22/2017 7/29/2017 8/5/2017
    before 93% CSROtherY2/7743 CSR 0813 -  BOE / Design   Summary   900.9 h 0.5h 2.2h 1.3h 20.4h 8.1h 12.2h
    after 74% CSROtherY2/7743 CSR 0813 -  BOE / Design   Summary   900.9 h 0.57h 2.12h 1.12h 20.07h 8.32h 12.32h
    before 98% CSROtherY2/7748 CSR 0813 - Provider, PA, MC, TPL, EVC, Ref, HC, Recipient - Design /   Create Specs / Produce PDD  713.3 h 0.5h 0h 1h 19.2h 7.2h 11.2h
    after 81% CSROtherY2/7748 CSR 0813 - Provider, PA, MC, TPL, EVC, Ref, HC, Recipient - Design /   Create Specs / Produce PDD  713.3 h 0.52h 0.03h 1.03h 19.03h 7.28h 11.28h
    before 76% CSROtherY2/12108 CSR 1947 - DEFERRED - Use of Reactivation Indicator in FDB Attribute File 76.1 h 0h 0h 0h 0h 0h 2h
    after 30% CSROtherY2/12108 CSR 1947 - DEFERRED - Use of Reactivation Indicator in FDB Attribute File 76.1 h 0.02h 0.03h 0.03h 0.03h 0.03h 2.03h
    before 63% CSROtherY2/14895 CSR 1956 - Deferred - CSRA System Integration Support 49.5 h 0h 0h 0h 0h 0h 0h
    after 27% CSROtherY2/14895 CSR 1956 - Deferred - CSRA System Integration Support 49.5 h 0.07h 0.12h 0.12h 0.12h 0.12h 0.12h
    before 100% CSROtherY2/12475 Cancelled - CSR 1959 - Enrolled Practitioner Search - Batch Upload 9 h 0h 0h 0h 0h 0h 0h
    after 100% CSROtherY2/12475 Cancelled - CSR 1959 - Enrolled Practitioner Search - Batch Upload 9 h 0.02h 0.03h 0.03h 0.03h 0.03h 0.03h

    Sunday, September 24, 2017 3:53 PM
  • Hotmail1,

    Unfortunately the "detail" you provided isn't enough (of the right stuff) to really help determine what's going on. The right mix of information on just one task should be adequate as long as it provides a complete picture. For example, let's take the last task, "Cancelled - CSR . . .". If I read it correctly it shows as being 100% complete. But I don't quite follow the information on the hours. There are 7 values starting with 9h yet there are 6 weeks shown in the dates. What is the 9h value? If that's the total work for the task and the task is 100% complete yet showing 0h for each of the 6 weeks, what happened to the 9h?

    For a given task, what is the duration? What is the start date? What is the finish date? Are resources assigned? What is the base calendar (i.e. before the veteran's day was added)? And when you say "actuals" what field are you referring to (i.e. is it the Actual Work field)?

    This would be easier if I could actually see your file, or at least a mock-up (i.e. single task test file) that shows the problem.

    John
    Monday, September 25, 2017 3:14 PM