Deleting a Credit Card Number

This utility report is used to remove old and inactive credit card account data from the Tessitura database.  Deletions can optionally be made to the account data (T_ACCOUNT_DATA) as well as the Credit Card Server log (T_CC_SERVER_LOG).  It exists as a front end utility so that it may be scheduled to run periodically using the Tessitura Report Server. The Purge Credit Card Account Data utility report can be found in the Data Management folder of the Reports window.

This might assist you. There is documentation on this report inside of Tessitura help system. I can email it to you also if you like.

Naomi

Thanks everyone for the replies.

Naomi, I tried manually removing them from the tables you suggested, and while I was able to remove it from the server log, I get an error message in account data that it cannot be deleted because it is being referenced somewhere else in the system. Do you know where else that may be?

I tried sifting through that report, but it either gives me a ridiculously high number (2000), or a reallly low number (3). I read through the documentation and am stumped - any suggestions on parameter settings for killing expired and inactive cc numbers? 

Hi Brian,

Double check the account in T_ACCOUNT_DATA and make sure the account in question is inactive. The report should show all a count of all accounts with an inactive status within given parameters.

I would suggest these parameters, although suggest caution as this will affect all inactive credit card accounts:

Purge payment accounts: Yes –This deletes accounts used in payments from t_account_data.

End payment date parameter will limit the credit card accounts to be deleted based on the last time the account was used. Only accounts which have not been used since the end payment date parameter will be affected. If no end payment date is entered all inactive accounts are considered.

The end payment date is the pmt_dt in the t_payment table.

Purge inactive billing accunts: Yes –This deleted accounts in t_account_data that are attached to fully paid orders, contributions, and invoice schedules.

Billing account expiration end date  will limit the accounts to be deleted based on accounts used in payment schedules which have an expiration date BEFORE the billing account expiration end date. If no date is entered, all inactive billing accounts are considered. This date is the credit card expiration date.

Purge credit card log: Yes – This deletes all log entries in the credit card server log t_cc_server_log.

Credit Card Server Log trans end date will limit the deletion on log records to rows created PRIOR to the credit card server log trans end date. If no date is enter, no entries are deleted.

No date should be entered:  Retain cards with expiration date after parameter prevents any account with an expiration date after the entered date from being deleted from t_account_data. This date is the credit card expiration date.

Counts only parameter is a review mode. The parameter should be yes until you are satisfied with the results then changed to no when you are ready to implement.

Exclusion List will give the stored procedure a list of constituents to exclude from the purge routine. –This can be optional however if you want to limit it to one customer you can get crafty and create a list that will somehow exclude only this patron.  This will ensure only their account is affected.

I highly recommend using the application to do this since it affects so many tables.

Thank you have a good day!

Naomi Williams

Hi Brian,

Double check the account in T_ACCOUNT_DATA and make sure the account in question is inactive. The report should show all a count of all accounts with an inactive status within given parameters.

I would suggest these parameters, although suggest caution as this will affect all inactive credit card accounts:

Purge payment accounts: Yes –This deletes accounts used in payments from t_account_data.

End payment date parameter will limit the credit card accounts to be deleted based on the last time the account was used. Only accounts which have not been used since the end payment date parameter will be affected. If no end payment date is entered all inactive accounts are considered.

The end payment date is the pmt_dt in the t_payment table.

Purge inactive billing accunts: Yes –This deleted accounts in t_account_data that are attached to fully paid orders, contributions, and invoice schedules.

Billing account expiration end date  will limit the accounts to be deleted based on accounts used in payment schedules which have an expiration date BEFORE the billing account expiration end date. If no date is entered, all inactive billing accounts are considered. This date is the credit card expiration date.

Purge credit card log: Yes – This deletes all log entries in the credit card server log t_cc_server_log.

Credit Card Server Log trans end date will limit the deletion on log records to rows created PRIOR to the credit card server log trans end date. If no date is enter, no entries are deleted.

No date should be entered:  Retain cards with expiration date after parameter prevents any account with an expiration date after the entered date from being deleted from t_account_data. This date is the credit card expiration date.

Counts only parameter is a review mode. The parameter should be yes until you are satisfied with the results then changed to no when you are ready to implement.

Exclusion List will give the stored procedure a list of constituents to exclude from the purge routine. –This can be optional however if you want to limit it to one customer you can get crafty and create a list that will somehow exclude only this patron.  This will ensure only their account is affected.

I highly recommend using the application to do this since it affects so many tables.

Thank you have a good day!

Naomi Williams

Hi Brian,

Just wanted to follow up with you and see if the information I gave you helped at all.

Naomi

Hi Naomi,

I have been waiting to try this out in our test server first, but have encountered a problem in our test environment and haven't been able to try the report yet (see post below for the problem I've been encountering).

http://www.tessituranetwork.com/COMMUNITY/forums/t/683.aspx