Story

As a system, I would like a new table for rebank transactions so that constraints can be applied to the previous table where rebank transactions were stored.

Details

This story is a result of the research performed in CFAMX-20076. Though that research, the following changes were proposed:

1. Design a new table for tbRebankTransaction that allows us to link to tbBankingTransaction (have a look at tbTransactionCashCount).
2. Update the above affected areas (see below) to look at this new source of Rebank transactions.
3. Create a data migration script to add existing rebank transactions into this new table and to delete the existing Rebank records in tbBankingTransaction.
4. Enforce a non-nullable unique constraint on the TransactionCashDepositID column in tbBankingTransaction
5. Remove the table lock from dbo.MXC_UpdateBankingTransactions.sql

   1. MERGE tbBankingTransaction with (tablockx) As [Target]
      

Affected areas:

Mx.Financial.Services

• TransactionCashCountCommandService.SaveOrUpdateChangeFundReceivedDeposits
• BankingDepositCommandService.GetSmartAndNonSmartRecords
• BankingCloseRepository.GetRebank
• BankingDepositRepository.SelectBankingTransactionsByBusinessDay
• FinalizeDayController.GetCashierSummary

SQL

• qryMMSBanking_DailySummary
• qryMMSBankingClose_SelectAndUpdate
• qryMMSBankingTransaction_GetChangeFundRebank
• qryMMSBankingTransaction_Select
• qryMMSBankingTransaction_SelectForCalendarDay

AC

The following areas of the site should continue to function as expected and with the correct data before and after the change:

• DailySummary report
• BankingClose report (Deposit Summary)
• DailySales report
• Cashier Settlement
• DailySummary on Finalize Day
• Cashier Summary report
• Daily Deposits
• Change Fund Deposit