Hey y'all,
I'm writing a report that needs to output all payments that could have affected a contribution. I've been investigating, and it seems the (only?) foolproof method would be to do a recursive query on T_TRANSACTION, kind of bouncing back and forth between ref_no and transaction_no until we've got all the transaction_nos, and then joining all of those transactions to T_PAYMENT.
Anyone do anything like this before that I can steal, or have any thoughts on the topic?
Nick,
I have a report that shows all payments by a chosen solicitor (for either contributions or orders) that I would be happy to share with you if you are interested in it, but it is pretty basic. It does not sound like it would be what you are looking for as it just references all the payments currently associated with the performance/contribution, but maybe you could tweak it to fit your needs?
Let me know.
John
Yeah, I am specifically trying to cover cases when someone uses the same transaction to adjust two different contributions, since that transaction would not have a payment associated with it, and could involve moving money between the two contributions. Are you doing anything in your report to cover that case?
My report does not, unless an on account payment method is in use; it does track on account payments.
From time to time we have an issue with some staff members using the wrong payment methods for orders, and because we sell all the tickets for the consortium, unfortunately the staff members DO need to have access to those payment methods for other purposes, so we just needed a simple way to track the payments made by a given staff member so I wrote this up for that purpose.
Best of luck.