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

Allow the Location Import to recognize/process multiple national distributors per individual location

    Details

      Description

      The locations import currently only handles a single national distributor per location. As Chick-fil-A continues to grow and expand, there is a business need for multiple national distributors to service a single Restaurant. This enhancement should allow for a one-to-many pairing of Restaurant to national distributors. The location file will simply have additional "distributor" attributes listed sequentially. Each distributor attribute should be processed appropriately and be assigned to the location and show up in the Ordering dropdown and other screens that require Distributor selection.

      See screenshot below, as well as a mocked-up file with just 01919 and a number of distributors assigned in the file:
      Locations_all_with_multiple_distributors.xml

      Note: Occasionally there will be multiple distribution centers that are part of the same distributor. In this case, since InFORM just places an order with head office of Distributor, the multiple “distributor” assignments should not cause “MBM” to show up in the dropdown twice. See screenshot below:

      HLE Notes
      • InFORM Order Guide was written specifically with only one National Vendor per location
      • For stores not using the InFORM Order Guide, this is not a problem
      • Vendor Entity relationship is maintained by the Location Import, as above
      • The Location Import creates and maintains mutually exclusive zones, for zone types
      • - Location - DistributorName
      • - - Comes from dist:Name
      • - Location - DistributionCenter
      • - - Concatenation of dist:ShortName + dist:DistributionCenter
      • Update the Location Import to compare arrays, rather than single values, when maintaining the Vendor Entity relationship
      • Support multiple vendors, not just two
      • Update the XSLT
      • Review the very last section in the XSLT , which puts a vendor into the entity table (is this needed or should we just drop it?)
      • Change Zone Types, above, to no longer be mutually exclusive
      • Make any necessary changes to the job that is a part of the I-4 that maintains Vendor Entity Relationships
      • Make any necessary changes to the job for Order Guide that runs rules and breaks/makes Vendor Entity Relationships

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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