VEI.StockCountUnit2ID should NOT update the EntityItem.StockYTakeUnit2ID when the VendorItem.PurchaseUnitID < EntityItem.PurchaseUnit

Testing Environment Details

• Environment: Testing
• Store(s): 01919
• Feature: UOM - Vendor Item Import and Vendor Entity Item Import: Update "Inner"
• Related Tickets (Stories or Features): CFAMX-13934
• Other Related Links (Confluence, BRDs, Etc...): N/A
• Feature Configurations: N/A

Expected Result

When the Vendor Item Import has a greater Purchase Unit value than the Inventory Item Import Purchase Unit, we currently update the EntityItem.StocktakeUnit1ID with this value when a rule is created and applied. In this case, if the VendorItem file had a StockTakeInner value we also want to update the EntityItem.StocktakeUnit2ID with this value. When the Vendor Item Import has a lesser Purchase Unit value we do not want to perform this logic. 

Actual Result

Currently the logic updates the StockTakeUnit2ID in every scenario. It does not take into account the larger PUOM between the two (Inventory Item or Vendor Item ) it simply updates.

See attached files and the data in the DB.

Select PurchaseUnit,StocktakeUnit1, StocktakeUnit2,* from tbItem
where itemcode in ('60860','60861');

Select StocktakeUnit1ID,StocktakeUnit2ID,ReportingUnitID,* from tbEntityItem
where itemid in ('4203','4204')
and EntityID =269;

Select * from tbUnitOfMeasure
where UnitOfMeasureID in(15,58,64,89,294)

Select PurchaseUnitID,InnerUnitID,* from tbVendorItem
where itemid in ('4203','4204');

Select PurchaseUnit,StockCountUnit2ID,* from tbVendorEntityItem
where itemid in ('4203','4204');

Add screenshots here if available

AC

There are a couple real-world scenarios that we need to confirm as a part of this fix. One where there is a single vendor item that is updated and one where a new additional vendor item is introduced. In both of these scenarios, we need to confirm that the inventory item UOM data matches the appropriate active vendor item UOM data.

Scenario 1 - An existing, active vendor item is UOM is updated and the vendor item and inventory item have a 1:1 relationship.

1. All the UOM data in the inventory item matches the newly updated UOM data in from vendor item
2. The PUOM and Inner displays in the counts UI correctly.
   1. PUOM matches PUOM
   2. Inner matches Inner
3. These conditions should be true if the item is update via the Vendor Item Import or the Vendor Entity Item import.

Scenario 2 - An active vendor item exists and is assigned to an inventory item. A new vendor item is introduced and the existing vendor item is disabled preserving a 1:1 relationship between active vendor item and inventory item.

1. All the UOM data in the inventory item matches the new, active vendor item. This is true especially in the following cases
   1. The new vendor item UOM is larger than the old, disabled UOM
   2. The new vendor item UOM is smaller than the old, disabled UOM
2. These conditions should be true if the item is update via the Vendor Item Import or the Vendor Entity Item import.

Scenario 3 - An active vendor item exists and is assigned to an inventory item. A new vendor item is introduced that ALSO maps to this same inventory item. It has a different UOM and corresponding StockTakeInner. When 2 Vendor Items are linked to 1 Inventory Item, we always want to use the Highest PUOM and it's corresponding StockTakeInner. 

1. The new vendor item UOM is larger than the 1st vendor item (which will be currently reflected on the Inventory Item PUOM and StockTake2) , in this scenario use Vendor Item 2 UOM and Inner
2. The new vendor item UOM is smaller than the 1st vendor item (which will be currently reflected on the Inventory Item PUOM and StockTake2) , in this scenario continue to use Vendor Item 1 UOM and Inner.