Skip to main content

IFS10, UPD8 O&G Extension

 

We are planning to start use the automatic ordering of spare parts based on demands on Work Tasks. To achieve this we have set the planning method to B on all inventory parts, parameters as per below. 

 

Now, we have scheduled the job Create Order Proposal for one site to run each night. 

The problem is that it runs forever:

 

The job started yesterday morning at 01:00 is still running… 

Parameters in the scheduled task are set as per below. We want to create an order proposal for all demands on all parts on work tasks, which is the reason for entering % in the parameters. 

 

Questions: 

Why is the background job never finished?

Is there a limit of how many parts the order proposal creation can handle? 

Any other limitation when it comes to demands, like planning horizon or similar?

Is anyone using this job at all? 

It would be great to hear about some examples where it works fine. 

Hi @MarieSkoldenborg ,

 

We use the create order proposal database task it runs each morning at 6:00 am.  We are currently running IFS Application 10 Update 8.  Below are screenshots of the schedule task and completed background jobs.  The background jobs usually last about 1 or 2 minutes in duration.  We are using a combination of planning method B and G on our raw materials.

 

 

 

Regards,

William Klotz

Thanks @william.klotz  for your reply. I see we have entered the parameters a bit differently, which might be a clue. 

Could you please let me know, appx how many inventory parts you have on your site with planning method B and G respectively?

Best regards,

Marie

Hi @MarieSkoldenborg ,

 

We currently have approximately 3200 to 3300 parts configured using planning method B and G but most parts are configured to use planning method G in our environment.

 

Thank you,

William Klotz

Now our job runs in a couple of minutes… The problem was that we have migrated a lot of data and not rebuilt the indexes after that. Having rebuilt the indexes on some tables and also run the background job “Gather Statistics” solved the problem. 

Hi @MarieSkoldenborg ,

 

Glad you figured it out.  I would recommend you run the database tasks “Gather Statistics” weekly and Rebuild Indexes monthly.  We run gather statistics every Sunday morning and rebuild indexes on the 1st of the month.

 

Regards,

William Klotz

Thanks for the tip @william.klotz !

Reply


Terms & ConditionsCookie settings