New added maintenance item doesn't create order after IP30 auto job

[Private_Member_28603]

Hello together,

I have following problem with an existing single cycle maintennace plan (cycle: yearly / no completion requirement / call horiz. 97 % / scheduling period 365 days / sched.indicator time - key date) for which I added a 1 new maintenance item (no reference object, but all planning & location data is maintained on item). Initial start date in IP10 for the maint. plan was 01.01.2012 - and I got already first orders for 01.01.2013 for the initially included maintenance items.

For the new added maintenance item I expected to also get an order for 01.01.2013. Normally after the next IP30 auto-job, which I executed manually,(settings: interval for call objects 30 days / rescheduling incl. active / immediate start for all: active), orders are created for new maintenance items - but not in this case.

As there's no EQ or FL included and also no link to a task list, I'm sure that a validity date can't be the reason for the order which is not created.

I hope you have some hints for me how I can solve this issue or how I can understand a obviously error in my logic.

Kind regards,

Patrick

[peter_atkin · Accepted solution]

Patrick,

Have you tried going into IP10 and refreshing the schedule?

Also check the IP30 error log (described above)

PeteA

[former_member209020 · Accepted solution]

Patrick,

Again you try to run IP10 for scheduling the plan.

Then you can get the Orders generated for the added items.

[Private_Member_28603 · Accepted solution]

Hello Pete,

maybe I explain the whole process better:

We had the productive start of the plant in May'13 - I set up an maintenance plan with x items, which should give me at 01.01.xx each year a new (standing) order.

In order to get for 01.01.2013 the orders, I started the maintenance plan in IP10 with start date 01.01.2012 (+ cycle of 12 months & key date as scheduling indicator gave me the orders for 01.01.2013).

If execute now a restart (I guess you aimed at this function with your statement "refreshing the schedule") in IP10: ok, I for sure get the missing order for the lately added new maint. item, but I'd also get the double orders for the ones who already exist (+ on which we already collected costs).

No, as I told already to Rajen: there's no error log in IP30 (also no worrying message or return codes if you use call transaction mode A).

A possible workaround would be to create now the missing order manually for 2013 & hope that for 2014 the order will be created.

Kind regards & thanks for your inputs so far!

Patrick S.

[Rajen_Patel]

What are selection parameters for IP30? Are you running IP30 with sort field? If yes, have you populated 'Sort field' in your maintenance plan?

Can you run IP30 with just your maint plan and see if there any error/warning message?

Thanks-

[Private_Member_28603]

Hi Rajen,

the normal weekly IP30 auto job for Sunday has following settings:

-selection on plant specific sort field

-interval for call object = 30 day

-rescheduling incl. = acitve

-immediate start for all = active

-mode = call transaction (N)

When I started IP30 manually, I put in the maintenance plan number (no sort field) & interval for call object was blank. There were no yellow or red message after execution of IP30.

Regards,

Patrick

[Former Member]

For PM Order to be generated from Maintenance Plan, Task list is mandatory. Without that, how the system will generate order???

[Private_Member_28603]

Hello Maheswaran,

it's possible to have a maintenance plan with no allocated task list in the maintenance item. The description of the maintenance item (field: PSTXT) will be transferred in the order header description (+ in the operation text).

All maintenance items of the maintenance plan were initially created withouth reference to a task list & I got all the orders like expected - just for the item added lately I don't received any order.

Cheers,

Patrick