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

Testing (S3.R2) UOM Update: Vendor Item Import - Use Largest UOM in EntityItem Table

    Details

    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      Details

      CFA has uncovered an issue where the purchase unit is not always the largest value when multiple vendor items assigned to the same vendor item exist in the system.

      The goal of this story is to make sure that CFA operators are always ordering the largest UOM when:

      1. There are multiple active vendor items with different UOMs that share an entity item.
      2. AND The user has not made any changes to the order guide by deselecting one of the multiple items.
      3. OR the user has made a change but more that one item is selected in the order guide.

      Scenario - Assuming a set of vendor items share a common inventory item.

      • Vendor Item A: Large Cup Box has existed in the system since 2018.
        • The Purchase Unit of Large Cup Box is 10 sleeves of 50.
      • Vendor Item B: Small Cup Box is imported yesterday and associated with the same inventory item as Large Cup Box.
        • The Purchase Unit of Small Cup Box is 10 sleeves of 25.
      • Each vendor item is active in the order guide

      Current Functionality: Because Small Cup Box was most recently imported, the purchase unit that the user sees in orders is updated to 10 sleeves of 25.

      Desired Functionality: CFA would like the purchase unit to be the largest of the units available instead of updating based on introduction time.

      AC

      Confirm Assuming there are multiple active items in the order guide

      1. When there are multiple active vendor items the purchase unit is populated with the largest value.
        1. This is true when new vendor items are imported.
        2. This is true when there are more that 2 vendor items that are associated with the same inventory item.
        3. This is true when the purchase unit for an existing vendor item is updated to a larger value than the one currently in use.
      2. The correct purchase unit displays in orders.

        Attachments

        1. screenshot-1.png
          screenshot-1.png
          98 kB
        2. screenshot-2.png
          screenshot-2.png
          443 kB
        3. screenshot-3.png
          screenshot-3.png
          77 kB

          Issue Links

          1.
          Review Test Scripts QA Task Ready for QA Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          2.
          Deploy QA Task Ready for QA Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          3.
          Functional Review with QA Dev Task Ready for Developer Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          4.
          DIT Dev Task Ready for Developer Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h

            Activity

              People

              • Assignee:
                jason.powell Jason Powell
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 2h
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                    PagerDuty

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