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

Blank ASN - Happy Path - Import an ASN with no order number and create an order from it

    Details

    • Sprint:
      CFAMX 2020R1 - SA Sprint 4, CFAMX 2020R1 - SA Sprint 5, CFAMX 2020R1 - SA Sprint 6
    • SCRUM Team:
      Globogym Purple Cobras
    • Story Points:
      5
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As an admin I want to be able to import an ASN that contains items that are assigned to my store, but doesn't contain an order number so that InFORM can create an order from the data in the file

      Notes

      • This is happy path - only items that are assigned to the vendor/store
      • Full Sample of ASN
      • ASN Trimmed down to one item and no order # included
      • Something similar was implemented in the Mx Trunk, MX-21137, but it used a tag in the file header rather than a vendor setting

      Acceptance Criteria

      1. When an ASN is processed the imported file contains a blank order node ( <cac:Shipment><cbc:ID></cbc:ID> ) AND the Vendor is configured to Create Order from ASN (CFAMX-6990):
        • For any order(s) included in the file for the specified store and vendor, the order is automatically created with the details provided.
          • This applies only to orders in the Shipping Confirmation (ASN) file where the "PurchaseOrderNumber" is BLANK.
          • The "Created By" user on the order is recorded as "System"
          • The "Ordered" Quantity is zero, due to the original order quantity being unknown in this scenario.
          • The "Shipped" Quantity is the value provided in the ASN as shipped for this item by the vendor.
          • The import log reflects a warning that the order provided did not exist and was automatically created (including the system-generated Purchase Order Number).
          • The status should be Shipped for the newly created order
      2. All orders created/updated by the Shipping Confirmation (ASN) import reflect the appropriate status in MxConnect Ordering/Receiving.
        • New 11/22 - The status of the orders should be Shipped
      3. Shipping Confirmation (ASN) functionality behaves as it did prior to this change (with the addition of auto-creation of missing orders), including:
        • Order must be for a valid store in the system.
        • Order must be for a valid vendor in the system.
        • The Vendor must be assigned to the store.
        • The Vendor Item(s) included in the order must be valid vendor items in the system.
        • The Vendor Item(s) included in the order must be assigned to the store.
        • The Purchase Units provided for the items must be valid.
        • The Quantities provided must be valid.
        • The Shipping Confirmation (ASN) file must be in the appropriate format for import or pre-processed by a custom XSLT Transform into the correct format.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 28h Original Estimate - 28h
                  28h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 51.75h
                  51.75h

                    PagerDuty

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