Hello everyone,
We would like to start analysing ticket sales by individual seller and I was wondering what options are available in Tessitura to do this.
As far as the canned reports I only find the seller's name generated in two reports - Single Sale Order Listing and Package Order Listing, neither of which produce all of the information we would like - including sales by production, date range, price type.
Is it possible to input Seller as a List Manager parameter in T_KEYWORD and T_KWCODED_VALUES? We could then run the generated lists against some of the sales reports that we use in Tess. I do not have SQL (we have no internal IT department) and would not know what tables to view, so if this is possible would someone be able to assist with the info needed in each column for this parameter in T_KEYWORD?
Any other suggestions you may have or letting me know other reports that I have missed would be greatly appreciated.
As always, thank you fellow Tessiturians!
Duane
Hi there,
You could do it this way, but that would involve the agent (seller) adding such an attribute to each customer they sell to. You could then use list manager to pull a list of these customers.
The only problem is, you would have to add all your sellers to the relevant entries in t_kwcoded_values.
An example of this would be the following structure:
t_keyword - new row:
description: <your choice>
data type: string
edit mask: alphanumeric
detail tbl: tx_cust_keyword
detail col: !.key_value
ref tbl: t_kwcoded_values
ref id col: key_value
ref desccol: key_value
ref where: keyword_no = <your keyword number from column 1 in this table>
ref sort: <empty>
category: <your choice>
use for list: attributes
multiple value <tick yes>
control group: <your call>
custom id: <empty>
everything else -> <empty>
Then in tx_keyword_cust_type assign one line for each customer type for your new keyword, where relevant.
Finally, for every seller you want to include in the drop down, you have to place an entry in the t_kwcoded_values.
Et voilla!
Let me know if you need any mroe info.
all the best,
Michal
Hello Michal,
Ooo, this is sounding like considerable more work than I would want to pass along to our Box Office staff. However your comments are much appreciated.
I think I am still going to add this Attribute field as it may prove valuable down the road so thank you as well for the column data in T_KEYWORD.
Thanks,
If your local ticket history table includes solicitor, then it would be pretty easy to create a keyword that references that. (I'm assuming that the order solicitor is how you determine seller.) You could tell if your ticket history table includes solicitor by looking at the Ticket History tab. If it's in the table, it'd show on that tab.
Or you can analyze this using tstats, if you have tstats.
Hi Amanda,
Exactly, I am looking at Order Solicitor referring to ticket seller. This solicitor is showing up in the constituent Order tab, but not in our Ticket History tab.
We do have T-Stats and I have heard today that this will be a parameter in 2.0, so I think this is probably the route that we will end up going.
Thank you very much for your input, we will consider updating the local ticket history table to include this.