-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:2021.R6 CloudLink Sprint 6
-
SCRUM Team:Globogym Purple Cobras
-
Story Points:3
-
Work Type Classification:Sustaining
We need to go through the Cashier Close process (see POSProcessing.vb in Mx.Binaries, method DayShiftProcessing_Radiant).
Looks like there are two Service Methods:
CreateCashierShiftDepositWithCashCountRadiant (CashierClose)
CreateCashierShiftDepositWithCashCountRadiant2 (FinalPickup)
The service method CreateCashierShiftDepositWithCashCountRadiant eventually calls the TransactionCashDepositFinancialService method CreateCashierShiftDepositRadiant which then calls the method UpdateByCashierFinancialRadiant.
The stored procedure is then called to calculate all the Control Info records used. See:
qryMMSTransactionCashDeposit_UpdateByCashierFinancialRadiant
At first glance, it seems to sum up all the ControlInfo records that have the ControlInfoSystemCode = 'Operator Shift'
- implements
-
CFAMX-14120 CloudLink - MVP
-
- Open
-
1.
|
Review Test Scripts |
|
Done | Unassigned |
|
||||||
2.
|
Deploy |
|
Done | Unassigned |
|
||||||
3.
|
DIT |
|
Done | Unassigned |
|
||||||
4.
|
Design Review |
|
Done | Unassigned |
|
||||||
5.
|
Investigate the methods in Mx.Binaries highlighted in the above description to find out what is needed out of the LiteSum file for CashierClose |
|
Done | Sree Surapaneni |
|
