-
Type: Testing Defect
-
Status: Done (View Workflow)
-
Priority: Critical
-
Resolution: Completed
-
Affects Version/s: CFA 2023R3
-
Fix Version/s: CFA 2023R3
-
Component/s: None
-
Labels:None
-
SCRUM Team:Brotherhood of Mutants
-
Source Code ID(s):
Scenario: When one or more sales exclusion entries have been added for the period of Dec 2022 and the store marks the EOM. IF the Sales Exclusions are removed for the store from within settings, my expectation is that EOM will continue to display the Sales Exclusions from the EOM page as historical data for that previous period.
Steps in Testing:
1) Added store 00703 to three exclusions
2) Marked End of Month for store 00703 on Dec 2022 business period
3) Went into settings and removed each Sales Exclusion from Store 00703 - one at a time.
4) Viewed EOM for 00703 for Dec 2022 after each removal in step 3 (above) and the Sales Exclusions entries remain as long as 1 was still assigned.
These are the Sales Exclusions for the store in Testing:
Select * from tbEndOfMonthStatusCheckSalesExclusions
where EndOfMonthStatusCheckId =95688
Select * from tbSalesExclusionsType
where SalesExclusionsTypeId in (121,161,181)
Defect:
When store 00703 is removed from ALL previously setup sales exclusions and EOM is viewed after this , the DEC 2022 sales exclusion section is no longer displayed and therefor it appears as if no sales exclusion entries were entered.
Expected:
We expect the previously entered Sales Exclusions to always display and be soley driven by the data entered in the tbEndOfMonthStatusCheckSalesExclusions table.
- relates to
-
CFAMX-25425 2023 R3 Testing CLONE - EOM Sales Exclusions - Automatically Move Stores In and Out of the Zone
- Closed