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

2019.R4(S5): Location Import: Vendor Switch should not add items from new vendor (Distr. Name, Distri. Ctr)

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Consultation
    • Affects Version/s: CFA 2019R4
    • Fix Version/s: CFA 2019R4
    • Component/s: OrderGuide
    • Labels:
      None
    • SCRUM Team:
      Brotherhood of Mutants
    • Sprint:
      CFAMX 2019R4 Sprint 5

      Description

      Environment: JAT
      Build: CFA - 19.4.0.2506
      Store: 03195 - Schertz FSU
      User: System Admin
      Day: Thr, Aug 28, 2019
      Page: https://m.inform.jatesting.cfahome.com/#/Administration/MaintainOrderGuide

      When switching from MBM to QCD in the "hurricane situation", the Store items, Operator team and Market name zone items...etc are getting moved per this story, but should the items/rules associated with the Distributor Name and Distribution Center also get added?

      If the point is that only the items that match the previous vendor should get assigned (From Vendor A to Vendor B) then we should not include those items associated with the Distributor Name and Distribution Center Zones when SWITCHING Vendors.

      Example: I have my items that I could order from MBM after the job is run ("Update Order Guide After VendorChange"), and I have two new items from QCD - and QCD-APO.

      Thoughts?
      Will Englefield Stacy Privalova

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                soma.dixon Soma Dixon (Inactive)
                Reporter:
                soma.dixon Soma Dixon (Inactive)
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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