Maintain Plan date

[gaurav_solanki2]

Hi SAP Experts,

In maintenance plan I used scheduling indicator Time-Key Date with call horizon 95% and ticked Completion requirement. Start of cycle was 08.03.2016 and it is maintained with 2 month package.System gave correct scheduling.Now what happened system generate first call date on 05.05.2016 and plan date is 08.05.2016. user also have done preventive maintenance on date.But in system due to some reason user close the call on 27.05.2016.Because of scheduling indicator Time-Key date ,system will change the next plan accordingly call close date.

Now user want that plan date should not be changed , due to some reason they could not close in system but did preventive on time.The query is that,how we can control this type of case.

PlanDate    CallDate     Completion     Pack

08.05.2016		27.05.2016	2M
27.07.2016	24.07.2016		2M
27.09.2016	24.09.2016		2M 6M
27.11.2016	24.11.2016		2M
27.01.2017	24.01.2017		2M
27.03.2017	24.03.2017		2M 6M 1Y

Thanks

Regards

Gaurav Solanki

[gaurav_solanki2 · Accepted solution]

Hi

Thanks to all,your support is highly appreciated.Now if I maintain Shift Factor late completion as '0' then it will give same date as I want , but it is applied only for if only one call has been completed and to be complete.

Now where user has completed two call , its not working. for example see the screenshot.

Is it possible that I can set plan date again on 3rd of every month.3rd plan date should be 03.06.2016.

Thanks

Regards

Gaurav Solanki

[psr2412 · Accepted solution]

Hi Gaurav,

Thanks for your response, If possible can you share settings of maintenance plan scheduling parameters.

Regards,

PS R

[gaurav_solanki2 · Accepted solution]

Hi PSR

Kindly find the attached screenshot.

[psr2412 · Accepted solution]

Thank you Gaurav,I will come back.

[Former Member · Accepted solution]

HI Gaurav,

I don't think Completion date will change by changing the scheduling parameters.

If you want all calls in future as 3 June, 3 July, 3 Aug, then restart the plan with start date as 3 May ( as maintenance for may is already completed)

Remember you have strategy in place, so its better to restart it from the beginning & skip initial 2 calls which will be in SAVE TO CALL status once you restart.

Regards,

Amol

[psr2412 · Accepted solution]

Hi Gaurav,

Having completed on 15.04.2016 against 03.04.2016 next plan date should be 03.05.2016 as per the settings, but it is 15.05.2016. Can you share some more details on start in cycle or can you retest again and share the same.

Regards,

PS R

[Former Member]

Hi Gaurav,

The third plan date onward is still onhold, then you always can restart remaining schedule to match your initial requirement (i.e plan date every 3rd etc)

thanks

salam hangat,

danniel

[psr2412]

Hi Gaurav,

Try with the solution given in my earlier reply, probably this will work out.

Plz. update on this.

Regards,

PS R

[former_member230030]

Hi Gaurav,

Maintain Shift Factor late completion as '0'.

Regards,

RP.

[Former Member]

Hoi Gaurav,

To anticipate those cases, you should use shift factor.

Use 'Early completion' and 'late completion' to suit your requirement.

Thanks

salam hangat,

Danniel

[psr2412]

Hi Gaurav,

Your query is quite interesting, completion requirement check box is only to generate subsequent orders once the previous order has been completed, so maintain as it is.Next. Coming to Shift factor early completion & shift factor late completion, the purpose is to control what percentage of the late/early completion date is to be transferred to the next planned date.

Plz. check in your case what percentage you have set in these fields.If shift factor of 100% for late completion it results in what you have shown.Hence, change shift factor late completion to 0 % and check.

Regards,

PS R

[gaurav_solanki2]

Hi,

your immediate action is highly appreciated,.But I want also that Only Create New Call Object After Completing Predecessor.

Thanks

Regards

Gaurav Solanki

[Former Member]

Hi Gaurav,

Then you need to try & test with Shift factors for late completion & tolerance.

Regards,

Amol

[former_member220863]

Hi Gaurav,

In such case, you can maintain Shift Factor Early Completion 0% and Tolerance as 100%.

Regards,

Sunil

[MTerence]

Hi Gaurav,

Well, we understood your point. Thats why i gave the two options infront. Maintain the shift factor as 0, then it will not impact your next call.

The fact here is why the order was TECO'ed lately, the process should be followed to get the data perfect. In your case, i will say that's a human error. I feel this cannot be compromised.

In another case, Considering the Industry standards, i do a maintenance 2Monthly, but due to some reason like waiting for external labour or material, my work was delayed by 20 days, so completed lately. Now i have two options to be considered

1. Next maintenance i need to do 20 early (40days)

2. Next maintenance i need to do after 2Months

Based on these scenarios you need to define in SAP.

Regards

Terence

[Former Member]

Hi Gaurav,

As suggested by maria, I think completion requirement check box should be blank in this case. So that system will not refer the closing date of previous call.

Regards,

Amol

[MTerence]

Hi Gaurav,

Two things can be done i guess

1. You need to use Tolorence and test the scenario

2. Remove Completion Requirement check box

Regards

Terence