on 08-02-2015 10:26 PM
Need your advice/help on seting up the following scenario in SAP:
We have equipment that needs to have two separate frequencies that is mutually
exclusive; one frequency for Summer and a different frequency for Winter. The
maintenance plan needs to create quarterly (every three months) PMs during
Summer and bi-monthly (every two months) during Winter. If Summer is from June
- November, how can the maintenance plan be set up to perform as expected? Is
there a way to set up a 'Hierarchy' strategy (301) with one maintenance item so
that the maintenance plan can do the above automaticallly? Can 'offset' be used
to achieve this?
Any feedback will be highly appreciated!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Shweta,
I would suggest posting a fresh question in place of using this old one. In a new question, u can tag this old question/answer.
You can put a start date like that system to create a work order in summer. Like frequency is 12 months and the start date is 01/05/2022 where scheduling parameter has "time-Key date" set to get work order always on day date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I have done is create a strategy plan and attached a task list with two operations, 26 week and 52 week packages assigned. works seamlessly. Harold
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sajeev,
You could also consider developing a solution which would allow you the have a single plan, but vary the frequencies to your own customer-specific logic.
Optimizing the Scheduling - Maintenance Planning (CS-AG/PM-PRM-MP) - SAP Library
PeteA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think Pete's suggestion is probably the best solution, but if you want to try and avoid having to maintain custom code, you could look at the Cycle Modification Factor field on the maintenance plan (on the "scheduling parameters" tab). You can use the mass change transaction MCH01 to modify this value twice a year for a group of plans, for example.
Paul
Thank you Jogeswara Rao, Tim Cheah, Sunil and Khayyam! Appreciate the quick response!
The logic definitely makes sense when using different Factory Calendars. The challenge is to get the Governance approval to create additional Factory Calendars.
Thank you again!
Regards,
Sajeev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Menoth,
If the client is ok to deactivate the status of maintenance plan for this type of specific plans or restart the plan during specific season. Below option is possible without factory calendar
You can create two plans (strategy or single), start date should be specific to the season start (June to November and December to May)
Enter the scheduling period as 6 months. This will schedule only plans for the next six months.
Regards
Terence
Hi Menoth,
Have you tried searching this topic" *seasonal Preventive*." in the same space, some months back someone has posted a nice document about this, I am not able recall exact things.
but it is similar situation.
Rgds
Sunil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Menoth,
Looks like finally we might have to settle for 2 single cycle plans plans based on 2 different Factory calendars (Summer and Winter). Wait for replies from experts in this subject for complex scheduling indicators based on strategies.
Regards
KJogeswaraRao
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.