Shop_Order background jobs

It is configured in Solution Manager,  Look for Batch Queue administration.  You may create new  queue´s and move the job’s.   Please  look into the tech documentation  or send PM.

​@jorlin where is the tech documentation for the jobs?

I know how to configure the batch queues, but have never seen anything on jobs.  I would be interested in looks at it.  :-)

In the Technical Documentation library look in ….

          Solution Manager User Guide  »  Background Processing  »  Background Jobs  »  Batch Queues Configuration

Also - I was able to go into one of the internal IFS test systems (25R2) and successfully used the Delete button to remove a background job from one batch queue and then add that job to a different batch queue.  This was only true for a core product job, however.  I’ll leave it for others with more experience using batch queues to respond regarding custom background jobs.

Hi Eugene,

Appreciate the answer.  I know how to move jobs around and create batch queues.

I just need to know if I can run the two jobs in different batch queues….some must be kept in the same queue...not sure if these two can be separated.

So the issue here is whether or not the Shop_Order_Cost_Bucket_API and Shop_Order_Cost_Util_API jobs are interdependent and whether or not they ought to be run together, i.e. in sequence?  Please confirm. 

If yes I’ll find a functional analyst who can help with that point.

Yes, can they run in different queues without causing an issue.

Thanks Eugene, that is what I thought and wanted to make sure of.

I appreciate you confirming :-)

​@Eugene Wager , 

We understand that Batch_Calculate and Batch_Calculate_Details are dependent jobs and should remain in the same batch queue. Could you please clarify:

• Should that queue be configured with only one worker process, or are multiple worker processes supported?
• If multiple workers are supported, how does IFS ensure that the dependency between these jobs is maintained?
• Are there any known risks of row locking, deadlocks, sequencing issues, or data consistency problems when multiple Shop Orders are processed concurrently?
• Are there any recommended queue configurations or performance best practices for customers processing a high volume of Shop Orders?

Could you please help finding answers to above?

​@Chamila Madupalie 

It is my understanding from my IFS Partner, that conversion of a shop order from a requisition to an actual shop order is not a background job.  These two background jobs are kicked off after the fact.

They are multiple worker processes, in that they are not assigned to directly to specific workers.

However, they do run first in first out in the queue, so only one runs (depending on queue configuration) at any given time...thus preventing deadlocks.

Recommendations that were given to me. are that conversion of shop order reqs to shop order be done outside of peak times, as this can affect system performance.  Maybe running a database task to convert after overnight MRP run?

 I also found that if you absolutely MUST create shop orders during peak times, that it only be done in batches of < 100 reqs at a time.

Hope this helps, my company also creates high volume of shop orders per day…