Details

    • Sprint:
      CFAMX 2020R1 Sprint 1
    • Story Points:
      2
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As a third party system receiving the PMix file I want the Refund Count to to populated for only one record relating to each item so that I don't have to parse out the results

      Notes

      • Currently the RefundCount is populated for each instance of a particular item, for example:
      • <ProductMixDetailInfo>
        <ItemEntryDate>2019-06-15</ItemEntryDate>
        <ItemID>10020</ItemID>
        <ItemSalesSource>POS</ItemSalesSource>
        <ItemDescription>Hash Browns</ItemDescription>
        <UnitPrice>1.09</UnitPrice>
        <SoldCount>39</SoldCount>
        <WasteCount>0</WasteCount>
        <PromotionalCount>1</PromotionalCount>
        <SampledCount>0</SampledCount>
        <RefundCount>1</RefundCount>  <---
        </ProductMixDetailInfo>
        <ProductMixDetailInfo>
        <ItemEntryDate>2019-06-15</ItemEntryDate>
        <ItemID>10020</ItemID>
        <ItemSalesSource>POS</ItemSalesSource>
        <ItemDescription>Hash Browns</ItemDescription>
        <UnitPrice>0</UnitPrice>
        <SoldCount>273</SoldCount>
        <WasteCount>0</WasteCount>
        <PromotionalCount>1</PromotionalCount>
        <SampledCount>0</SampledCount>
        <RefundCount>1</RefundCount>  <---
        </ProductMixDetailInfo>
        
      • In this case, it looks like a refund was performed against each instance of the item, when in fact only one refund was performed against the item
      • Make a change to associate the refund to the instance of the item first in the group that has the highest UnitPrice, resulting in:
      • <ProductMixDetailInfo>
        <ItemEntryDate>2019-06-15</ItemEntryDate>
        <ItemID>10020</ItemID>
        <ItemSalesSource>POS</ItemSalesSource>
        <ItemDescription>Hash Browns</ItemDescription>
        <UnitPrice>1.09</UnitPrice>
        <SoldCount>39</SoldCount>
        <WasteCount>0</WasteCount>
        <PromotionalCount>1</PromotionalCount>
        <SampledCount>0</SampledCount>
        <RefundCount>1</RefundCount>   <---
        </ProductMixDetailInfo>
        <ProductMixDetailInfo>
        <ItemEntryDate>2019-06-15</ItemEntryDate>
        <ItemID>10020</ItemID>
        <ItemSalesSource>POS</ItemSalesSource>
        <ItemDescription>Hash Browns</ItemDescription>
        <UnitPrice>0</UnitPrice>
        <SoldCount>273</SoldCount>
        <WasteCount>0</WasteCount>
        <PromotionalCount>1</PromotionalCount>
        <SampledCount>0</SampledCount>
        <RefundCount>0</RefundCount>  <---
        </ProductMixDetailInfo>
        
      • It is possible that the instance with the highest Unit Price is repeated, as below:
        • In this instance, use the first record with the Highest Unit Price for Refund Count & the others will be zero to determine which line to use, associate the refund count to the record that has the highest SoldCount, if these are the same, then use the record that has the highest PromotionalCount
      • Sample file, showing the duplicate condition that exists today ProductMix_01899_20190615 (3).xml

      Acceptance Criteria

      1. Confirm when a refund count is included in the PMix, and there are multiple instances of an item, the RefundCount is only shown for the record that has the highest Unit Price, the other records should show a refund count of zero
      2. Confirm when a refund count is included in the PMix, and there are multiple instances of an item with the same Unit Price, the RefundCount is shown against the first record that has the highest Unit Price, the other records should show a refund count of zero
      3. Confirm when a refund count is included in the PMix, and there are multiple instances of an item with the same Unit Price and same Sold Count, the RefundCount is only shown for the record that has the highest Unit Price and highest PromotionalCount, the other records should show a refund count of zero
      4. Confirm when an item is included in the Pmix and it does not have an associated Refund, the records should show a refund count of zero

        Attachments

        1. CFA Product Mix_20190918-18_56_14_684$D545E0F9_MEAL REFUND.xml
          3 kB
          Charles Wheeler
        2. CFA Product Mix_20190918-20_41_38_481$BB8FE1DF_E2E.xml
          7 kB
          Charles Wheeler
        3. ProductMix_01899_20190615 (3).xml
          188 kB
          Will Englefield
        4. screenshot-1.png
          22 kB
          Will Englefield
        5. screenshot-2.png
          34 kB
          Will Englefield

          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:

                  Time Tracking

                  Estimated:
                  Original Estimate - 13h 38m Original Estimate - 13h 38m
                  13h 38m
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 19h 46m
                  19h 46m

                    PagerDuty

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