Details

Currently, InFORM defaults the inventory item unit of measure on count screens for stores to the last imported unit of measure from the vendor item file system wide, regardless of the UOM of the vendor item ordered by the store. Since resolution via production defect was unsuccessful, we're hoping to implement this via a feature where the case and inner units of measure of a given Inventory Item match the case size and inner units of measure from the vendor item assigned to that store's order guide. If one store orders lettuce in 24 ct Head cases and the other in 10lb cases, we want each store to see their respective UOM, not just whichever UOM came over last in the vendor item file. In the event that a store is assigned two vendor items with different units of measure that roll up to one inventory item, the system should default to the larger of the two UOMs. We want this to apply to both the CFA provided vendor item file and the CH Robinson provided vendor item file.

Story 1

When a new vendor item is introduced, I would like (In progress)

Possible Update

Display UOM on the Order Guide

Largest UOM - Notes (Will Email)

1. When setting the purchase unit (& Reporting Unit?) of the Entity Item, the code should respect the User set Active flag in Inv & Order Setup > Maintain Order Guide
   1. Note: Maintain Order Guide, shows Vendor specific data, to resolve this issue, we need the code to look across all vendors
   2. If there is only one vendor item set to Active, use the Purchase Unit of that Vendor Entity Item
   3. If there are multiple vendor items set to Active, use the largest Purchase Unit of all the vendor items that are Active
   4. If there are No vendor items set to Active, on Maintain Order Guide, use the largest Purchase Unit of the active Vendor Entity Items associated to the Entity Item
      1. In this case active means Introduction Date is in the past and Discontinue date is Null or in the Future
      2. I believe that items only show on the Maintain Order Guide page, for the User to set the value, when the Vendor Entity Item is active, per the previous date criteria
   5. SPIKE: Can we remove the funky logic that we use to determine if a vendor item is Active or not, or is this too difficult/too far reaching? Is it even necessary to do so?
2. Store Order Guide - Inv & Order Setup > Maintain Order Guide (Clicking on Save seems to update the Purchase UOM of the item correctly, sometime...)
   1. Changes to Maintain Order Guide
      1. Add a Purchase Unit column, and display the Purchase Unit of the Vendor Entity Item
      2. When clicking on Save, all ways take the largest Purchase Unit from all vendor items that the User has marked as Active (make sure that this looks across all vendors, and not just the one that is displayed)
      3. If there are No vendor items set to Active, on Maintain Order Guide, use the largest Purchase Unit of the active Vendor Entity Items associated to the Entity Item
3. InFORM Order Guide - Administration > Assign Vendor Items
   1. After creating/updating a rule, the user clicks on Apply Rules
      1. Link the process to set the Purchase Unit of the Entity Item, to the task that applies the rules
   2. There is also a scheduled job that runs daily, to ensure that any rule changes that are not applied manually, do get applied
      1. This scheduled job should also be updated to trigger the process to update the Purchase Unit of the Entity Item
4. Vendor Item Import
   1. When the purchase unit of a vendor item changes/new vendor item introduced, the details of the vendor item (purchase unit) should not be used to update the entity item when there is not a Vendor Entity relationship AND a Vendor Entity Item record for that Vendor Item / Entity Item combination
      1. For example: when a new Vendor Item is introduced in the import, with a new larger Purchase Unit, no changes should be made to the entity items, as there will not be any Vendor Entity Items to reference, this remains the case until an Order Guide Rule is created and applied, see above.
      2. Another example: A store transitions from QCD to McLane, the Purchase Unit of the Entity Item reflects that of McLane, the store has a Vendor Entity relationship with McLane, but the previous Vendor Entity relationship with QCD is deleted when the transition occurs. When a new larger purchase unit is processed for QCD, it will not update the Entity Item at this store, as there is no QCD Vendor Entity relationship
5. New scheduled job - Discontinued Vendor Entity Items
   1. Write a new job, that can be scheduled, to look at Vendor Entity Items that were discontinued yesterday, find the remaining active Vendor Entity Items that correspond to the same Entity Item, and update the Purchase Unit of the Entity Item using the largest Purchase Unit of the current active Vendor Entity Items
   2. Note: If there are no other active Vendor Entity Items (the item has been discontinued), there is no action to take
6. New scheduled job - Introduced Vendor Entity Items
   1. Write a new job, that can be scheduled, to look for Vendor Entity Items that are Introduced today, find other active Vendor Entity Items that correspond to the same Entity Item, and update the Purchase Unit of the Entity Item using the largest Purchase Unit of the current active Vendor Entity Items
   2. Note: If there are no other active Vendor Entity Items (the item is brand new), there is no action to take

Will's research doc

https://fourthlimited-my.sharepoint.com/:x:/g/personal/will_englefield_fourth_com/EcBIKnSEzCxGq8NTMwKmw5UBwLRa7rsNNLjuE1QDAPG4dQ?e=TgMlT4

Soma Dixon per our conversation during grooming.

I have found that a good example to use is cups, as they com e in many different size cases