We are still working through our Tessitura implementation.
Contributions are now processed in Live. The rest of Tessitura will be implemented beginning in March, with a final implementation in July.
Our Development person left several months ago, and our new person starts soon.
I’m trying to process existing contributions to lessen immediate demands when our Development person arrives.
Regular contributions can be processed without error. However, I am unable to process a pledge payment to an existing pledge.
When I start the pledge payment process, the following error appears: There are no eligible pledges to pay.
Drilling into a customer record with an outstanding pledge, and contributions for the customer, I can see the original pledge and all subsequent pledge payments.
And, I can see the pledge still has an outstanding balance. However, I am unable to apply a payment toward the pledge.
We have several organizations with outstanding pledge balances, and I can’t apply a pledge payment to any of their contributions.
I’ve looked within the many tables used for the contribution process, trying to find differences between these contributions.
I did notice the BU in T_CONTRIBUTION does not match the BU in T_FUND. Could this cause the problem? If so – how to fix ?
Does anyone have some suggestions or thoughts?
BTW
In the original contribution software, it appears our previous Development person did some “creative” entries.
We’ll probably have to cancel / re-enter many contributions – including many of the pledges mentioned earlier.
Thanks
Wendell Baskin
Bass Hall – Fort Worth, Texas
Wendell,
BU (Business Unit) mismatch could certainly be a problem. I would submit a request to Tessitura Support to be certain. We ran into a similar problem when we began implementing a shared box office in the KC consortium.
Business Unit was intended to help organizations segment data among departments within an organization. However, this functionality has essentially been taken over by user groups and control groups.
I would recommend using the same BU value everywhere in the system that it appears.
- Levi