Skip to main content
Solved

Scheduled Database Task question

  • April 3, 2023
  • 3 replies
  • 166 views

Forum|alt.badge.img+17

Hello,

I am currently using IFS Cloud and I have created a scheduled database task to run every 2 minutes, and check if a Consolidated Pick List is ready for creation in the “Create consolidated Pick List for Customer Order” page. 

I have the parameter set up so it only applies to customer orders with site 100, but its triggering other sites as well.

Any advise would be greatly appreciated.

Thanks,
Bryan

Best answer by bdoucette

Hi @bdoucette,

Could you please share how you have configured the Scheduled Database Task? 

Hi Charith,

I solved the issue, I was actually using the Create Consolidated Pick List for Customer Orders API call and not the Create Consolidated Pick List for Shipment(CO) API call, which we have configured for the other 300, and 400 sites, so that explains why this one was taking over.

Thanks,
Bryan

3 replies

Charith Epitawatta
Ultimate Hero (Employee)
Forum|alt.badge.img+31
  • Ultimate Hero (Employee)
  • 1094 replies
  • April 3, 2023

Hi @bdoucette,

Could you please share how you have configured the Scheduled Database Task? 


Forum|alt.badge.img+17
  • Author
  • Superhero (Customer)
  • 254 replies
  • April 4, 2023

Hi @bdoucette,

Could you please share how you have configured the Scheduled Database Task? 

Of course,

 

This one is for only site 100, we have others for sites 300 and 400, but those never execute for orders other than those sites. This one executes for all sites for some reason
 

 


Forum|alt.badge.img+17
  • Author
  • Superhero (Customer)
  • 254 replies
  • Answer
  • April 4, 2023

Hi @bdoucette,

Could you please share how you have configured the Scheduled Database Task? 

Hi Charith,

I solved the issue, I was actually using the Create Consolidated Pick List for Customer Orders API call and not the Create Consolidated Pick List for Shipment(CO) API call, which we have configured for the other 300, and 400 sites, so that explains why this one was taking over.

Thanks,
Bryan