IP30 - Work Orders not getting generated

Logistics : PM and its sub-modules & SM

Moderators: Snowy, thx4allthefish, PJA

Post Reply
Posts: 183
Joined: Thu Jan 06, 2011 10:43 am

IP30 - Work Orders not getting generated

Post by BIDOR » Thu May 02, 2019 7:49 am


We have been having a problem since the beginning of the year where IP30 Deadline Monitoring is not creating orders when, according to maintenance plan and scheduling parameters, it should.

As an example, we have a maintenance plan with a one year cycle. The call horizon within the maintenance plan is set at 96%.

In IP30, the interval for Call Ojects is set to 6 Days..

Based upon these parameters if, for example we have a planned date of May 1st 2019, the call date would be April 16th 2019 (May 1st - 14,4 days).

If IP30 is run on April 14th at 05:00:00, it should generate an order for this maintenance plan.

As we understand it, the base date for calculation is the system date of execution of IP30 and then it should generate all calls on hold up to April 20th 2019 (April 14th + 6 days). Since the call date for the maintenance plan is on April 16th, it should have been generated but it's status stays "Scheduled hold". The thing is within the call algorithm, we can see the "Last call on 2019-04-14" and "Called by IP102..." but no order has been generated.

Are we missing Something on the calculation method ? (we have'nt had that problem last year)

Thanks for your input !

Posts: 2
Joined: Tue Dec 06, 2016 2:42 pm

Re: IP30 - Work Orders not getting generated

Post by omnisap1975 » Mon Jun 03, 2019 4:03 pm


Is so hard to understand your question.

If you have a yearly PM(365 days) with call horizon at 96%, you work order will be called on 350day. Now you have given 6 day interval in IP30, so your call date would be 15 days + 6 days ahead of time approximately. If your plan date is May 1, 2019 am thinking (approximately) your call date would be April 9,2019.


Posts: 183
Joined: Thu Jan 06, 2011 10:43 am

Re: IP30 - Work Orders not getting generated

Post by BIDOR » Thu Jun 06, 2019 6:34 am

Thanks for your reply Nureya.

I agree with your answer but the problem is that this is not happening. We have a bacground job running once a week for IP30 on syndays at 05h00h00.
So all orders with call date on 16th of april 2019 should have been called on Sunday april 14th 2019 (april 14th + 6 days brings us up to april 20th within which interval april 16th is included) but they have not been generated.

Here is the example from SAP:

The system date of the report run is always used as the basis for calculating the to-date (date up until which the call objects are generated). The interval is added to the system date of the report run. The system generates maintenance call objects for all the waiting tasks whose call date is in this interval.


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.

So that's the problem, things are not happening according to SAP definition.

We have'nt yet identified what the problem might be.

Thanks again for replying.

Post Reply