Skip to main content

I wanted to create a Purchase Requisition against the assignment in mWO (Cloud), it does not show any purchase parts when I try to create the requisition. Do we need any additional setup?

 

I have scheduled to run Refresh All Inventory Parts and Refresh All Purch Parts and also executed them before initializing the mobile still no parts are showing when trying to create the requisition (system has Supplier for purchase parts in the same site)

Hi

First you need to have the purchase parts linked to the user through a part assortment and then run the Refresh All Purch Parts job. Please see the “Mobile Part Basic Data” pages to see the user connected part assortments and parts. 

If the purchase part is already included in one of the user assigned work tasks, you might not want to run the above job but in both cases as the final step you must sync the PurchPart entity (or initialize the app) to get them into mobile.

More detailed document that explains the Inventory part and Purchase part synchronization is under way and will be released in 24R2. 

Thanks

Sampath   

 

Hi

First you need to have the purchase parts linked to the user through a part assortment and then run the Refresh All Purch Parts job. Please see the “Mobile Part Basic Data” pages to see the user connected part assortments and parts. 

If the purchase part is already included in one of the user assigned work tasks, you might not want to run the above job but in both cases as the final step you must sync the PurchPart entity (or initialize the app) to get them into mobile.

More detailed document that explains the Inventory part and Purchase part synchronization is under way and will be released in 24R2. 

Thanks

Sampath   

Hi Sampath,

 

This resolved the issue but can I know why we need Assortments to be setup in order to show the purchase parts? Why can’t we have all the purchase parts synchronized to the application?

With regards,

Jeyani

 

Hi

First you need to have the purchase parts linked to the user through a part assortment and then run the Refresh All Purch Parts job. Please see the “Mobile Part Basic Data” pages to see the user connected part assortments and parts. 

If the purchase part is already included in one of the user assigned work tasks, you might not want to run the above job but in both cases as the final step you must sync the PurchPart entity (or initialize the app) to get them into mobile.

More detailed document that explains the Inventory part and Purchase part synchronization is under way and will be released in 24R2. 

Thanks

Sampath   

Hi Sampath,

 

This resolved the issue but can I know why we need Assortments to be setup in order to show the purchase parts? Why can’t we have all the purchase parts synchronized to the application?

With regards,

Jeyani

Hi,

Part basic data set up is there to limit data ensuring mobile user only gets the relevant data synced into the mobile application. In most cases, mobile user might not work with all the purchase/Inventory parts registered in the system and it could also be differ from user to user. As an offline application, MWO is very concerned about the amount of data as it has a direct impact on the app performance. 

Thanks

Sampath

Reply


Terms & ConditionsCookie settings