We found that when parts are received into inventory in IFS (via Register PO Arrivals) instead of receiving on the mobile app, those parts don’t show in the user’s inventory in the mobile app.
Does anyone know why?
Is there a way to “correct it” so the stock does show in the mobile app for the user?
We are using IFS 9
Page 1 / 1
Hi,
I believe the entity that updates the inventory in mobile is synced using batch sync. Please check if the batch sync has successfully happened after the inventory update. Usually the “available quantities” of the parts of the user connected warehouses should be displayed in mobile under my stock.
The batch sync has run but the parts in the user’s warehouse in IFS (back office) are not all showing in his stock in the mobile app. Any suggestions as to how we should troubleshoot this?
I think what you can see in My stock in apps9 MWO is available quantities of the user connected warehouses, not the reserved quantities (in Apps10 MWO reserved quantities are also displayed). So in your flow if the part is reserved, you might not see it.
Other thing could be the permission set filter, that would limit data sync to mobile so worth checking it.
Also make sure to run the “Refresh All Inventory Parts” scheduled task if it is a new part.
In IFS 9, when creating a PO to order stock for a mobile user, does the Destination Warehouse field need to be populated and/or the Receive Case be “Receive into Inventory” in order for the parts to …
Show in the mobile app for the user to receive
Show in the user’s stock in the mobile app after receiving
It is has been sporadic that some users are able to receive their parts on the mobile app and for others the parts never show in the app to be received. And then when some receive the parts, they show in their stock in the mobile app whereas for other users, after they receive the parts, they do not show in their stock in the mobile app.
There are few conditions to be satisfied before the PO lines can be seen in mobile for the user to receive.
If it is a inventory purchase part, receive case should be “Receive into inventory”
If it is a non-inventory purchase part, receive case should be “Receive into arrival”
The status of the PO line should be released
If the PO is connected to the work order which the user is working on, no destination warehouse value is needed on the PO line. However if it is a stand-alone PO, only the users who has access to the destination warehouse on the PO line will see the it in mobile.
If they do not see the stock updates correctly in backend and mobile after following all required steps, it could be a bug and that needs to be investigated.
thank you for your help!
Thank you for your help with this. We are now able to get the parts to appear in the mobile app to be received and to show in stock in the app. But the user has to initialize each time.
Created and released inter-site PO for user parts. The user ran a sync in the mobile app. The background jobs were run in IFS. But the user was unable to see the parts in the app to receive until after he initialized.
Parts were received in the mobile app. The parts did not show in stock in the app but did show in stock in IFS. Ran the database task “Refresh All Inventory Parts” . The user ran a sync in the mobile app. The background jobs were run in IFS. But the user was unable to see the parts in stock in the app until after he initialized.
So here are my questions:
Why does the mobile user have to initialize in order to view parts in the mobile app?
Does the initialization process do something different than what the synchronization process does in the mobile app?
User shouldn't have to initialize the app to get the required data into mobile. The data will be sent to mobile as per the sync policy defined on each entity. Both the entities that handle PO receipts and Inventory updates are using Batch sync as specified in the screenshot below. After a successful batch sync which includes changes from above entities, mobile client should be updated with new data.
You can do a “Sync now” on those entities to bypass the batch process and see if it gets data correctly into the mobile.
And make sure to run the “Refresh all inventory parts” scheduled task prior to get the inventory updates.