-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2021R2
-
Component/s: Imports
-
Labels:None
-
Sprint:2021.R3 New Features Sprint 2, 2021.R3 New Features Sprint 3
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:2
-
Work Type Classification:Sustaining
Story
As a system, I want the Purchase Unit and the Reporting Unit set to the Largest Unit of Measure when a Vendor Item Import is processed, so that the store can maintain accurate inventory.
Description/Notes
Not only should Purchase Unit (aka tbEntityItem.stocktakeUnit1D) be updated to the largest UOM, but in the Vendor Item Import, there are two additional directives which require the Reporting Unit to be updated for the Store Item. When the
Example:
VendorCode|ItemCode|{InsertVendorEntityItem}VendorItemCode|VendorDescription|{UpdateVendorEntityItem} **{DefaultToReportingUnit} {UpdateFromItem} {UpdateEntityItem}PurchaseUnit**|VendorPrice|IntroductionDate|{UpdateVendorEntityItem}DiscontinueDate|AutoUpdateEntityPrice|AutoUpdateEntityUnit|PerformStockCount|{UpdateEntityItem}
StockTakeInner
184774|12382|101578|KALE, CHOPPED, 5/1 #|5/1 Lb|0|2020/03/09 00:00:00|4712/12/30 00:00:00|N|N|N|1 Lb Bag
Acceptance Criteria
- Confirm when a Vendor Item Import is processed for a store item that already exists with a larger UOM, the largest UOM persists to the Reporting Unit.
- Confirm when a Vendor Item Import is processed for a store item that already exists with a smaller UOM, the largest UOM persists to the Reporting Unit.
- Confirm when a Vendor Item import is processed to delete the item with the largest UOM, the Reporting Unit defaults to the next largest UOM.
Example: If the file deletes the 5lb bag of Kale, then revert the Largest UOM to the 4lb bag
- Clones
-
- Closed
- implements
-
CFAMX-13112 INF-12276 - (R2/3/4/5) Set UOM to Largest Available
-
- Closed
-
