Vendor Item Import - Add support to set Purchase Unit to Largest UOM

There is a job that runs at the end of the I4 Import process, which finds the largest UOM, for all Vendor Entity Items (VEI), and set the UOM to that value (For new Vendor Items).
There is a requirement to also have this logic apply to Vendor Items that are updated, in addition to new items

Notes
New Inventory Items
◾Job runs after I4 import
•If there are VEI's use the largest vendor UOM (based on derived base unit conversion)
•If there are no VEI's, use the Purchase Unit

Existing Inventory Items (updates) - New Vendor Item with larger UOM
◾Job runs after I4 import
•If there are VEI's use the largest vendor UOM (based on derived base unit conversion)
•If there are no VEI's, use the Purchase Unit

Stocktake 1 = Stocktake 'Box'

Acceptance Criteria
New Inventory Items
◾If a new inventory item is added as a part of the I4 import, and there is no VEI's associated to the Item, set Stocktake 1 to the same UOM as the Purchase Unit
◾If a new inventory item is added as a part of the I4 import, and there is one associated VEI created, set Stocktake 1 to the UOM of that VEI
◾If a new inventory item is added as a part of the I4 import, and there are multiple associated VEI's created, set Stocktake 1 to the largest UOM of the VEI's (largest being the largest when the UOM is derived from the base unit conversion)

Existing Inventory Items (updates)
◾If an existing inventory item is updated during the I4 import, and there are no associated VEI's, Stocktake 1 should be set to the Purchase Unit ◾This would only be needed if the Purchase Unit is updated

◾If an existing inventory item is updated during the I4 import, and there is one associated VEI, Stocktake 1 should be set to the UOM of that VEI
◾If an existing inventory item is updated during the I4 import, and there are multiple associated VEI's, Stocktake 1 should be set to the largest UOM of the VEI's

David Nayyar added a comment - 01/Apr/16 6:03 AM

There is a problem with the SQL query in MMS, in the UpdateAllEntityItemsUOMFromVendor(...) method of file MX.Data.Core\Inventory\Purchasing\Generated\EntityItemRepository.cs. The query does not always pick the highest unit of measure when there are multiple vendorEntityItems for the same vendor, entity, and item. Assuming this is a valid case, we will have to adjust the query.

Charles Wheeler added a comment - 01/Apr/16 7:17 AM

David, can you comment on the exact logic on how your query is determining the greatest UOM for this scenario specifically?

Also, I am seeing now that the unit of measure is correct for my store - 00442 - and it is set to 36/10 oz Bag Case, when yesterday the value for the stocktake box was 3/1Lb Bag. Did you by chance change it?

David Nayyar added a comment - 01/Apr/16 10:27 AM

The logic takes all the vendor entity items for a specific vendor, store, and item combination and sorts that by the "Conversion Rate" in descending order. The missing piece was that the order of the Conversion Rate wasn't being respected properly during the update.