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

Allocations - Add Support to Delete an allocation

    Details

    • Sprint:
      CFAMX 2019R3 Sprint 2
    • SCRUM Team:
      Brotherhood of Mutants
    • SOW (Time Tracking) Project:
      44918

      Description

      As a supply chain analyst I want the ability to delete an allocation through the UI so that I can correct any mistakes that I make when configuring an allocation

      Notes

      • The current allocation import has constraints around correcting the data via the import
      • This solution will provide the following:
        • Select an allocation
        • Select Delete Allocation
        • Prompt user to confirm deletion
        • Delete all records for the allocation, from the allocation tables and Order tables
        • Research - Sending an Auto Notification that has an attached CSV that shows the data that has been deleted

      Acceptance Criteria

      1. Confirm that there is an option on the Item Allocation page to select an allocation for an item for deletion
      2. Confirm that after selecting an allocation for deletion there is an option to initiate the delete process
        • Show delete option in Right Hand Panel
        • Expand RH Panel to see Delete Removed 4/18
        • Only show the End Allocation button if the user has selected today's date on the Allocation page.
      3. Confirm that the user is prompted to confirm which allocation they are going to delete and that the delete process will delete the allocation for a specific number of stores (not just the one selected in the Item Allocation page)
        • show the number of impacted stores
      4. Confirm that the allocation delete process deletes the appropriate records from the allocation and order tables (tbAllocation, tbAllocationDetails, tbTransactionSalesOrderDetailItemQuantity)
      5. Confirm that after deleting the allocation it is possible to import a file to recreate the allocation for the same item, starting tomorrow
      6. Confirm that Draft Orders that were associated with the allocation can be accessed without issue
      7. Confirm that Placed Orders that were associated with the allocation can be accessed without issue
      8. Confirm that Shipped Orders that were associated with the allocation can be accessed without issue
      9. Confirm that Received Orders that were associated with the allocation can be accessed without issue
      10. Confirm that there is an audit record written that details the Item on allocation and the number of stores that were deleted, and the user who performed the delete action (tbAllocation - AuditCategoryID = 8, AuditEventId = 503)

      Dev's Notes 

      1. It may be possible to maintain history for a deleted allocation - this would be preferred
      2. Maintaining history would require "stopping" or "ending" an allocation rather than deleted
      3. We don't have a real "this allocation for all stores" concept in the database or in the allocation import from CFA. When we look for "all allocations" to delete, we will match on item code, start date, and end date. 

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 58.5h
                  58.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 48h 55m Time Not Required
                  48h 55m

                    PagerDuty

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