Hi @T_Lindgren
Your scenarios are very common in Preventive Maintenance in S/4HANA Public Cloud. Here are the recommended practices:
- Put a Preventive Maintenance Plan on Pause and Restart Later
In Public Cloud you cannot pause a plan directly, but you can control scheduling so no new calls are generated during the pause:
Here are suggested best Practices:
- Block or deactivate the plan temporarily
- In the Change Maintenance Plan app, set the Scheduling Indicator = Inactive or use Blocking so that the scheduler skips this plan.
- Restart later
- When ready for example after 6 months, reactivate the scheduling indicator. The system will calculate the next due package based on the scheduling cycle and last completion.
- This ensures the plan remains in the system but does not generate orders during the pause.
Change of Maintenance Plan Data
- Postpone Only One Next Call in a Strategy Plan
Sometimes you need to shift only the next cycle, without permanently changing the strategy.
These are the suggested best Practices:
- Manual Adjustment of Call Dates
- Use Display or Change Maintenance Plan Schedule app → select the due call → adjust the planned date forward by +6 months.
- Completion rescheduling
- When you complete a call/order, the next call is normally scheduled forward based on the strategy. If you want to add a one-time delay, adjust the completion date in the confirmation, which shifts the cycle.
- Use Offset or Shift Factors
- In the maintenance plan parameters, you can allow manual date shifting by entering a shift factor. This provides controlled flexibility to postpone one cycle without redesigning the whole plan.
Scheduling Parameters
I hope this provides the necessary details. I am happy to help if you have further questions.
Best regards
Chris
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.