Hi Nimesh,

In the current design, first thing done inside Refresh_All_Inv_Parts() method is delete all records in MOBILE_USER_INVENT_PART_TAB

Then run different cursor to repopulate the table. eg. connected warehouses, materials, returns and etc.

So it is not possible to run based in site. 

But you can try out a workaround solution like writing a custom method or event to insert records (new part/user combinations) to MOBILE_USER_INVENT_PART_TAB when you want to send a new part. Then you can keep Refresh_All_Inv_Parts job to off peak time.

Hi @Bandula,

Thank you for the response.

If the customer implements the workaround, then is it ok to run the Refresh_All_Inv_Parts job during weekends? Will that be an issue?

Because, customer doesn’t have common off-peak hours as users are accessing the system globally. 

/Nimesh

Hi @Nimesh Kasun  Yes, if the workaround implemented they don’t need to run the task daily. 

But please note current refresh task collect part/user data from different sources. eg.connected warehouses, materials, returns and few more. So if they not run the task daily, their custom method need to take care of all. 

Please have look on   Mobile_User_Invent_Part_API.Refresh_All_Inv_Parts()  method in plsq. Then you can get an idea how we populate the table. 

Hi @Bandula,

Thank you for your support. Customer has implemented the suggestion from their end.

/Nimesh