Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-13740

CLONE 2021.R2 Patchback - UOM Update: Vendor Item Import- Update Reporting Unit to Largest UOM

    Details

    • 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

      Description

      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

      {DefaultToReportingUnit} and {UpdateEntityItem} directives are added to the PurchaseUnit Field, tbEntityItem.ReportingUnitID should update to the largest UOM in addition to StockTakeUnit1ID (CFAMX-13189).

      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

        Attachments

          Issue Links

          Clones

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFAMX-13726 UOM Update: Vendor Item Import- Update Reporting Unit to Largest UOM

          • Closed
          implements

          Feature Request - CFAMX-13112 INF-12276 - (R2/3/4/5) Set UOM to Largest Available

          • Major - Major loss of function.
          • Closed
          1.
          		 Review Test Scripts QA Task Done Unassigned

          0%
          Original Estimate - 0.5h
          Time Not Required
          2.
          		 Deploy QA Task Done Unassigned

          0%
          Original Estimate - 0.5h
          Time Not Required
          3.
          		 Functional Review with QA Dev Task Done Unassigned

          100%
          Original Estimate - 0.5h
          Time Spent - 1m Time Not Required
          4.
          		 DIT Dev Task Done Unassigned

          100%
          Original Estimate - 0.5h
          Time Spent - 1m Time Not Required

            Activity

              People

              • Assignee:
                charles.wheeler Charles Wheeler
                Reporter:
                soma.dixon Soma Dixon (Inactive)
              • Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2m Time Not Required
                  2m

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.