Hello all -
So I have four custom views that I use for all ticketing reporting here - one for all "main" season tickets, one for "main" season single tickets only, one for education products and one for what we call here "alternative" programming. All the program function basically the same way: they take all seats sold (from t_sub_lineitem) and reports sales on them and with each SLI representing a seat, it's both a revenue and seating program that we use across multiple other reports here in the company.
However, the report is never 100% accurate for past dates due to exchanges and such, so it's never been fully reliable for, say, looking at sales at this point last year v this year.
So I'm attempting to build a transactional seating report - but I'm running into obstacles and I'm not sure where the obstacles are. I have a new program that pulls transactionally (actually via seat history, not transactions), but I cannot get it to reconcile against any common field: for example
I can't reconcile against customer because seats can be transferred; I can't reconcile against order because the seats move from order to order; I can't reconcile against performance number because folks go in and out of performances at different prices... the list goes on and on.
Has anyone ever writing a transaction-ish seating report that is both accurate over history and in the present? I'm happy get into more detail with anyone interested - any assistance is appreciated!
RJ
My code allows me to compare against our current sales reporting for reconciliation. For the entire season last year (I wanted to use a closed season since I knew seats wouldn’t be moving real time), I’m only 122 seats off totaling $472 – that’s off by .115% in the count of seats and .009% in revenue. Now I know I have some differences in how I account for donated seats, but I’m so close that I keep banging my head against this wall… it would be reassuring to know I should stop banging my head because of a confirmed bug in 12.5 (which we’re on) vs “the bug is gone and you may have exchanged some seats incorrectly”… but again – with no solid tie between seats and seat history, I’m having difficulty.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Chris Jensen Sent: Thursday, September 15, 2016 2:42 PM To: Richard Jackson <richardj@alleytheatre.org> Subject: RE: [Tessitura Technical Forum] Tickets and Transactions
Tom Brown: We have tried to do this. We ran into problems. There were / are some bugs in how Tessitura populates T_ORDER_SEAT_HIST. [...] When we were trying to do this on our own it turned out to be a sort of hard nut.
Tom Brown:
We have tried to do this. We ran into problems. There were / are some bugs in how Tessitura populates T_ORDER_SEAT_HIST.
[...] When we were trying to do this on our own it turned out to be a sort of hard nut.
Just chiming in to add to the chorus of those that have attempted this sort of thing, e.g. in our case we have a custom daily sales report that we archive to PDF every day because, as described in this thread, it's not really possible to reliably re-generate this data on a date in the past. Folks here would love a version of this report that could do that, and like others here I have spent significant time puzzling over T_ORDER_SEAT_HIST trying to make it work.
Back in 2008, when Ron Wilson was working with us on our conversion, I asked him about reporting from this table, and he said something like, "In theory you could use that for reporting, but no-one does." And he was right!
From: Tom Brown <bounce-tombrown3568@tessituranetwork.com> Sent: 9/12/2016 11:02:30 PM
We would really love to have a view that provides this information. I would like to work with you to see if we can crack this nut. When we were trying to do this on our own it turned out to be a sort of hard nut.
--Tom
…
718.724.8135
tbrown@BAM.org
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Richard Jackson Sent: Monday, September 12, 2016 5:08 PM To: Thomas Brown Subject: [Tessitura Technical Forum] Tickets and Transactions
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!