Maintenance Plan Scheduling - IP30

[Former Member]

Hi all,

I am new to SAP PM and would like to get clarified about a few points in connection to preventive maintenance planning.

What is the significance of the 'Interval for Call Objects' field in IP30 layout vis-a-vis the scheduling period maintained in the maintenance plan? If we are running a batch job for scheduling by creating variant, we do mention the start date, time for the batch job. Does this job continue for an indefinite time, regardless of what scheduling period is maintained in maint. plan (if not manually terminated using SM37)?
In what scenarios should we use Scheduling Indicator as 'Time' and as 'Time - Key Date'?

Kindly help.

Thanks in advance.

[pardhreddyc]

Dear,

You create some maintenance plans with a maintenance strategy. The following table shows which maintenance plan types require a maintenance strategy.

Maintenance Plan Type	Maintenance Strategy
Single cycle plan, time-based	No
Single cycle plan, performance-based	No
Strategy plan, time-based	Yes
Strategy plan, performance-based	Yes
Multiple counter plan	No

Maintenance Packages

Maintenance activities that must be performed at a particular date or point in time are combined into maintenance packages. These contain, for example, the cycle duration and unit of measurement

Scheduling Parameters

The scheduling parameters (for example, call horizon, shift factor) contain the scheduling data for the respective maintenance strategy, with which you can influence the scheduling of maintenance plans. When you create a strategy plan, the system copies this data to the plan where you can change it.

Scheduling Indicators

Within a maintenance strategy, you can use different scheduling indicators to specify the type of scheduling you require or to define a cycle set:

• Time-based (for example, every 30 days)
• Time-based by key date (for example, every 30 days on the 30th day of the month)
• Time-based by factory calendar (for example, every 30 working days)
• Performance-based (for example, every 50 operating hours)

Please find the very usefull document to make you understand by our Jogeswara rao garu

Regards,

Pardhu

[Former Member]

Hi Santanu

You have two form of planning time base planning and performance base planning.

In time base planning you can schedule by time , time key date and factory calendar.

These indicator help you to set call date based on your need.

For example

If you have an equipment that regularly calibarate or do PM in exact time and date , ok you can use time key date indicator.

If your scheduling plan depends on a factory calendar you should use this indicator .

[tinaren]

Hi Santanu,

Generally, a call object is generated if the current date is later then the actual planned date.

But with this parameter "interval for call objects", you generate the call objects (notification, order) in advance and then you can get an overview on the notifications, orders that you need to do in the following days.

Please check the F1 help for more details:

It is important that the call interval in the scheduling parameters of the maintenance plan is bigger than or at least equal to the interval for the call objects that is maintained here.

Example: Interval for call objects: 14 days Report run on: 01.01.XX The system generates call objects for the calls waiting up to the 15.01.XX.

You can also check the F1 help for the Time-key date in transaction IP02. It has the detailed explanation.

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

Best regards,

Tina