Vendor Item Import - Update Entity Item values of Purchase Unit and Reporting Unit - INF-11763

Hi Rehan Weber, Stacy Privalova found this gap today, something that we hadn't discussed but is in the FRD/BRD.

We have focused on the VENDOR Entity Item, but there is also a requirement to update the Purchase Unit and the Reporting Unit of the ENTITY ITEM, note, NOT the Vendor Entity Item.

The requirements are below:

Confirm that Purchase UOM and Reporting UOM at the store level is created or updated based on the value in the Vendor Item import.
The value should follow definitions below:

• Description: Default Purchasing Unit of Measure
• Data Type: TEXT
• Length/ Format: 50
• Required: O (Optional)
  Field Validation:

1. If provided, must match a value in the 'Unit Name' field on the 'Units of Measure' tab on the 'Units of Measure' page.
2. If not provided, and the vendor item exists, then that vendor purchase unit of measure is used.
3. If not provided, and the vendor item does not exist, it is an error.
4. If provided, and the unit of measure does not match the vendor item's purchase unit of measure, a warning is logged.
5. If there is no conversion from the purchase unit of measure to the inventory item's base unit of measure, it is an error.
6. If the Import file does not provide the Purchase UOM, and this item DOES exist in InFROM at the Vendor level, this item is successfully assigned to the designated store or zone, utilizing the Purchase Unit from the item at the Vendor level.
7. If the Import file does not provide the Purchase UOM, and this item DOES NOT exist in InFORM at the Vendor level, this item cannot be assigned via import and is logged as an error.
8. If the Import file does provide the Purchase UOM, and this Purchase UOM is DIFFERENT from the Purchase UOM stored at the Vendor Item level, the item is successfully assigned to the designated store or zone, using the Purchase UOM provided in the file. A warning is logged indicating that the Purchase UOM assigned to the item at this store is different from the vendor-level Purchase UOM.
9. If the Import file does provide the Purchase UOM, and this Purchase UOM is the same as the Purchase UOM stored at the Vendor Item level, the item is successfully assigned to the designated store or zone, using the UOM provided in the file. No warning is logged in this scenario.
10. If the Purchase UOM provided in the Vendor Entity Item import file does not exist in InFORM then this item cannot be assigned and is logged as an error.
11. If the Purchase UOM provided in the Vendor Entity Item import file does exist in InFORM, but there is not a valid conversion rate between the Purchase UOM and the inventory item’s base UOM, then this item cannot be assigned and is logged as an error. (2015.3)

Notes:

Purchase Unit = Stocktake 'Box'
Reporting Unit = Reporting Unit

It seems that there are two directives in the VEI Import in the Purchase Unit filed, which we missed, these are:

1. {DefaultToReportingUnit} & {UpdateEntityItem} - In this case it seems to really mean, update the entity item

PART 2

I also see the {UpdateEntityItem} directive on two more fields:
1. PerformStockCount
2. StockTakeInner
Confluence page: https://hotschedules.atlassian.net/wiki/spaces/RBCD/pages/60115206/Vendor+Entity+Item+Import+Template

Looking at the Headers of a file from Production:

Stacy Privalova
I see more directives on StockTakeInner.

• Do you know if this too updates the Entity Item (StocktakeUnit2ID)?

It looks like the CFA file does not use the a directive on PerformStockCount, can you confirm that this is your understanding as well, and also, where is this value managed?