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

Collected Sale - Overpayment/Credit/TBC Refunded

    Details

    • SCRUM Team:
      Brotherhood of Mutants
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As an operator I want to be able to perform TBC gymnastics so that I can correct mistakes

      Use Case

      • A TBC is tendered on the POS, for $80, with a customer selected
      • The TBC is processed by InFORM
      • When the user views the TBC page the TBC is displayed
      • A collected sale is tendered on the POS, for $100, for the same customer
      • The collected sale is processed by InFORM
      • The user applies the Collected Sale of $100 to the TBC of $80, this results in a $20 balance
      • The user creates a Credit with the remaining $20 balance
      • The original TBC is Refunded on the POS, with a customer selected
      • The TBC Refund is processed by InFORM
      • On the TBC page the Refunded TBC must be resolved in order to complete the TBC process for the day
      • The TBC is locked, and it is indicated that the TBC was refunded
      • In MMS, there is no action to resolve this, a credit to a customer cannot be reversed
      • In this scenario the Finalize Day validation should fail
      • But how does the user correct this issue?
      • WILL IS GOING TO DISCUSS WITH OTHERS TO FIGURE THIS OUT!

      Acceptance Criteria

      1. Confirm when a TBC is associated to a Collected Sale and Credit, and the TBC is later refunded that the user cannot update any of the details of the TBC (Account Name, Invoice #, Description)
      2. Confirm when a TBC is associated to a Collected Sale Credit and the TBC is later refunded that it is indicated on the TBC page that the TBC is locked and has an associated refund
      3. Confirm that once deleted, neither the Credit, the TBC nor the refund are included in the CDS export
      4. Confirm that the MMS code has NOT been blindly copied without a full understanding of the processes being demonstrated

        Attachments

          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 - 20m
          Remaining Estimate - 20m
          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 - 20m
          Remaining Estimate - 20m

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1h 40m
                  1h 40m
                  Remaining:
                  Remaining Estimate - 1h 40m
                  1h 40m
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                    PagerDuty

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