Skip to Content
author's profile photo Former Member
Former Member

Schedule Call Plan Date

Hi PM Gurus,

I'm hoping someone will know the answer to this question...

Why is there a one day deviation between Completed Date and next Plan Date? As you can see from the screen shot below, some times there is no deviation but sometimes there is. So completed date on line 2 matches plan date +1 year on line 3. This is the desired outcome. But then you'll see on line 4, SAP dropped by one day, from July 7 to July 6. Does anyone know a way to correct this?

Best regards,

Julie

PM Capture.PNG (27.5 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

8 Answers

  • Posted on Oct 21, 2014 at 01:36 PM

    Hi Julie,

    I guess, 2016 is a leap year, so 366 days.

    Regards

    Terence

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 21, 2014 at 03:32 PM

    The completion date comes from the TECO data entered in the order.

    Then you probably have 100% Shift Factor settings applied in the maintenance plan scheduling parameters.

    So, in the case of the 1st line its probably a leap year as explained above.

    In the 2nd line, you subtract 9 from 16 to get the 7th.

    PeteA


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 21, 2014 at 04:55 PM

    Thank you Pete and Sebastian for your replys. I think I understand now. It appears the Act. Variance is used in the determination for the next plan date.

    And yes, I see the subsequent date shifted by one day b/c 2016 is a leap year.

    Thank you so much all for helping me understand this.

    Best regards,

    Julie

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 21, 2014 at 06:35 PM

    Hi Sebasian,

    Below is the screen shot of the maint plan scheduling parameters. I apologize. I should have included it in the original screen shot. I guess I still don't understand how I got a 7/16/2014 plan date on line 2.


    PM2 Capture.PNG (56.8 kB)
    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Julie,

      I did a similar case in my test system, it is showing similar. Tolerance had no impact on the plan date with your scenario.

      Last call completed is on 07/07/2014

      For call 3 Next call planned is on 07/07/2015

      For call 4 Next call planned is on 07/06/2016

      To know why it took on 6th July 2016, the reason is because of Leap year.

      Why the date is different, is because you have chosen TIME in scheduling parameter, if you choose TIME- KEY DATE, system will work as per your requirement, there will not be any difference in date.

      Regards

      Terence

  • author's profile photo Former Member
    Former Member
    Posted on Oct 23, 2014 at 07:36 PM

    Hello Terence,

    I have spent the last two days reading and testing in our sandbox. This is my requirement. Regardless of the plan date, if the completion date is X then I need the next scheduled plan date to be X + one year. In other words, the next plan date is based off completion date not previous plan date.

    I set up a single cycle maint plan with time key date. When I complete the order two days early, the next plan date is based off the previous plan date and not the completed date as per our requirement. Any ideas how we can set up the system to behave in this way? I appreciate your help.

    Best regards.

    Julie


    PM4 Capture.PNG (27.1 kB)
    PM5 Capture.PNG (23.4 kB)
    PM5 Capture.PNG (23.4 kB)
    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Julie,

      Please find below link about tolerance.

      Tolerance - Maintenance Planning (CS-AG/PM-PRM-MP) - SAP Library

      Below is the best example of the scheduling indicators provided by SAP

      Example:

      You schedule a maintenance plan with a monthly cycle
      (for scheduling, one month is always 30 days long in the standard
      system).

      • Time
        Today's date: 04/10/1998
        Next planned date: 03/11/1998 -> Today's date + 30 days
      • Key date
        Today's date: 04/10/1998
        Next planned date: 04/11/1998 -> Always on the 4th of the month
      • Factory calendar
        Today's date: 04/10/1998
        • Next planned date: 16/11/1998 -> Today's date (or next work day) + 30 work days

        Based on the above you can define the scheduling indicator.

        Rather than 100% give 10%, this might be helpful for you to understand the concept behind it.

        Regards

        Terence

    • author's profile photo Former Member
      Former Member
      Posted on Oct 23, 2014 at 08:34 PM

      Hello Sebastian,

      I have tested exactly with the same settings as you in my maintenance plan 887 but I don't get the same result ! Could there be some configuration setting that is causing this issue? Maybe a SAP note that needs to be applied to our system? Thank you for your help.


      PM6 Capture.PNG (33.0 kB)
      PM7 Capture.PNG (31.7 kB)
      PM7 Capture.PNG (31.7 kB)
      Add a comment
      10|10000 characters needed characters exceeded

    • author's profile photo Former Member
      Former Member
      Posted on Oct 24, 2014 at 03:18 PM

      Sebastian and Terence,

      Thank you for your responses. I did another test Sebastian, this time with the completion requirement ticked and unfortunately it did not give me a different result.

      I am going to take your suggestion and contact SAP OSS about the issue.

      Thanks again for your help.

      Regards,

      Julie

      Add a comment
      10|10000 characters needed characters exceeded

    • author's profile photo Former Member
      Former Member
      Posted on Dec 05, 2014 at 02:22 PM

      Hi all,

      I just wanted to circle back and let you know how I resolved this issue.

      I determined that to influence the next schedule date on our PMs we had to enter the PM completion date in the Maintenance Plan field during the TECO process. This gave us the next PM date as per our business requirement.

      That plus creating single cycle maintenance plans and marking the scheduling indicator as time - key date resolved our issue of having the schedule date adjusted due to leap year.

      Thank you all for your help and support in my analysis to resolve this problem for our business partners!

      Best regards,

      Julie Norman

      Add a comment
      10|10000 characters needed characters exceeded

    Before answering

    You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
    You must be Logged in to submit an answer.

    Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.