Hello,
I am doing a report on constituent with ticket exchanges. My question is by looking at some of the SQL tables such as t_order_seat_hist, t_order, t_sli_status. How can I identify that constituent having some ticket exchange transaction in that constituent?
in fact, can I look at the order_no, sli_status for exchangeable??
Thanks,
-Harry
The tables you are looking at will only tell you that the seats were returned but not if that was part of an exchange or just a return+refund.
The table that may help is t_transaction as that will show a Ticket Change transaction type if the tickets werre exchanged for other tickets in the same transaction. Again this depends how exchanges are processed.
You should be able to link that to order seat history with order numebr and perf number but will also need to use event date to match around (guessing wont be an exact match but shoudl be within seconds/minutes) the transaction date
Mark
Hello Mark,
Thanks for the hint.
I believe I see some light on table t_transaction, since every transaction is having the transaction type which recorded on trn_type in this table. I ran some tests:
1.) ticket refund vs. ticket with seat exchange. "ticket change" vs "ticket refund"
2.) Donate ticket for resale vs. ticket with seat exchange. there is no transaction type for this "donate ticket for resale"
trn_type stores a unique transaction type which refers from table tr_transaction_type. The table t_order_seat_hist will be refered to pull out constituent ID, perf_no as well
I believe by this way, it can be easily identify any constituent with seat exchanges. Do you have any idea with this thought?
Cannt help too much with seats donated for reasale as we don't do that in the UK so is not something I am familiar with.
If the Ticket Change type is the only one you are interested in then you should be able too link t_transaction to t_order to get the constituent number, which would be a faster query.
If you need to know which seats were exchanged then use order seat history using order_no, perf_no and the datetime (+/- a few minutes) of the transaction to the event datetime.