Hi all,
We recently implemented a fix in our scheduled procedures to make it so that our previously-buggy and incomplete T_Ticket_History populates (we hope) correctly.
I am trying to test that this process is working, but I can't seem to find a good way to do so! I've tried comparing T_Ticket_History to T_Order and I've compared T_Ticket_History dates to canned reports such as the Daily Sales Report, and no matter what I try, the data populating in T_Ticket_History sometimes shows more ticket sales than whatever I'm comparing it to, and sometimes shows less, and I can't seem to find the perfect system.
So. How would you check to see that the number of tickets sold per performance per day was indeed being accurately recorded in T_Ticket History?
T_SUB_LINEITEM is the place to go for reliable sales data.
Something else you might consider doing would be to compare the output of your custom history-populating procedure with the output of the standard one (TP_UPDATE_TICKET_HISTORY).
Would also recommend checking totals for performances rather than daily sales.
If your totals match then you are good.
Daily is an issue only because of how dates are recorded. You have the date the order was placed, but you also have the evnts in Order Seat History showing when it was added released bought etc and then you have dates in t_Transaction for when the money came in. The standard reports can use a variety of these whereas you are more likelyto be using order date in ticket history
Mark
Thanks Nick! This was the place to go! After I sorted out all General Public Sales and returned tickets (these two things are not captured in Ticket History), t_ticket_history matched up perfectly. Hooray!
ah, this is good to know re: the different dates at play. I was wondering why my numbers were only off by a handful in some cases while matching perfectly in others. I bet this is why.