Hello Tessitura Gurus,
I have an event that has rescheduled 3 times. Most original orders came through in Jan - Feb 2020. The cancellation utility is not working on this event. All 3 of these orders have active credit cards on their Tessitura record. This is a small order sampling. I believe that this utility is still operational and that it's only related to this performance. Our organization has been using this utility successfully since April. Not sure what's up.Thoughts and ideas are welcome!
If the Credit Card Tokenization and Deletion Utility is run with the "Purge credit card server log" paraemter set to Yes, it will remove rows from the T_PAYMENT_GATEWAY_ACTIVITY table. The Event Cancellation Utility refers to this table to verify the reference_number to use for the refund, and this message is returned if a reference_number does not exist for the original payment_no.
If necessary, it is possible to alter AP_PAYMENTS_AVAILABLE_FOR_REFUND to look at the T_PAYMENT.ccref_no column instead of the T_PAYMENT_GATEWAY_ACTIVITY table. There are several scenarios in the procedure (original payments for orders, contributions in controlled and uncontrolled batches). In each SELECT statement, there is a line that looks like this:Where p.pmt_amt > 0 AND l.reference_number IS NOT NULL AND (@include_emv_payments = 'Y' OR l.entry_method <> 'EMV')
Change this to read:Where p.pmt_amt > 0 AND p.ccref_no IS NOT NULL AND (@include_emv_payments = 'Y' OR l.entry_method <> 'EMV')
Re-run the utility and check the results to confirm that the refund is properly staged in the controlled batch.
This is all a side-effect of truncating the payment history from the T_PAYMENT_GATEWAY_ACTIVITY table. As always, its a good idea to give this a try in TEST first.