Jiwa

I've got a challenging tweak to develop when UOMs are used on sales orders. I've done sufficient hours fiddling in a plugin to realise that I need assistance!

Scenario:
Lets say the base SKU is called EACH.
We have a UOM called CARTON which is 12 EACHes. And a bigger UOM which is BIGCTN, which is 2 CARTONS (so 24 eaches).

We have 7 EACHes SOH.

On a sales order, they order 1 CARTON, but it goes to backorder for 5 and Qty This Del = 7. Fair enough, that's correct.
But when the warehouse staff go to pick it, they see they need to pick 0.58 of a CARTON. But the warehouse staff are, shall we say limited in their maths ability so they want to see that they need to pick 7 EACHes.
So instead of the Jiwa screen showing the UOM as CARTON, I'm trying to get it to switch to the inner UOM and have the UOM ordered qty = Ordered Qty.
In the Jiwa grid, a new line is entered as EACH. As soon as I enter 12 as the Ordered Qty, it immediately populates the UOM Qty = 1 and changes the UOM to CARTON. That is logically correct as I'm ordering a quantity which equals 1 CARTON.
But when I have backordered quantities I want the UOM to remain as EACH. This helps the warehouse staff to know to pick in EACHes, not CARTONs.

Have I explained OK? Over to the brains trust.

PS. I know that I could modify the pick slip but in this case they're using ASPluris and it uses the line UOM.

Your problem may even be a bit more complex because given you are talking about a scanning system the UOM and Unit can have different barcodes also.

DannyC wrote:As soon as I enter 12 as the Ordered Qty, it immediately populates the UOM Qty = 1 and changes the UOM to CARTON

It doesn't do that for me... I add the item to an order, the Unit Of Measure is EACH, I key in 12 in the Ordered Quantity and it does not change the UOM - it remains as EACH.


This is the inventory item UOM configuration:


I'm using 7.2.1 SR5 and the demo data. If you are using a different version to that, it may not be relevant - but it *might* - so that would be nice to know.

It doesn't do that for me

Odd. I thought that was inherent in Jiwa but I see it also happens like that in my demo database. Must be something customised with this client....back to the drawing board.