• Replies 2 replies
  • Subscribers 336 subscribers
  • Views 48 views
  • Users 0 members are here
Related

Keyword Setup - VS_TCK_HIST

Former Member
Former Member $organization

Happy Autumn everyone! It sure is beautiful in Vermont right now!

I set up some keywords for order/perf type information and I need these items to work together to report accurate information. These are the items I have with the detail tables:

  1. Ticket Perf Date - vs_tck_hist
  2. Ticket Price Type - lvs_sub_lineitem
  3. Ticket MOS - custom view that joins data from t_order, t_sub_lineitem, t_perf, and vrs_season
  4. Order Date - same custom view as number 3
  5. Order Number - t_order_seat_hist
  6. Season - vs_tck_hist
  7. #Seats - vs_tck_hist
  8. Total Lineitem $ - vs_tck_hist

So, this would be wonderful if the order date, order number and price type were available in vs_tck_hist and I could use just that one view for everything. Price type is included in that view but it isn't populated. Does anyone know why that is? I know I need to create a new view for order_dt and order_no but I want that to connect to vs_tck_hist so the data will coincide with the data in vs_tck_hist.

Anyone have any helpful strategy?

Gloria

Parents
  • $organization

    Hi Gloria,

     

    V_TCK_HIST is a view of T_TCK_HIST, which is populated by your performance history update procedure, which should be LP_UPDATE_TKT_HIST.  You can customize the procedure and the table to include whatever data you want.  One of the main purposes of the performance history is just what you want to do, get all the data in the same table so you can pull lists on it all working together.  I would add price type, MOS, order date, and order number all to the performance history (so update the table, procedure, and view).  You can safely make changes to T_TCK_HIST, even though it doesn’t have the LT prefix.  That table is not used by standard Tessitura processes, and since the Flynn Center converted to Tessitura we’ve moved to using a local table (LT_TKT_HIST) for performance histories.

     

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    1 888 643 5778 ext 329 Office

    ksheehan@tessituranetwork.com

     

Reply
  • $organization

    Hi Gloria,

     

    V_TCK_HIST is a view of T_TCK_HIST, which is populated by your performance history update procedure, which should be LP_UPDATE_TKT_HIST.  You can customize the procedure and the table to include whatever data you want.  One of the main purposes of the performance history is just what you want to do, get all the data in the same table so you can pull lists on it all working together.  I would add price type, MOS, order date, and order number all to the performance history (so update the table, procedure, and view).  You can safely make changes to T_TCK_HIST, even though it doesn’t have the LT prefix.  That table is not used by standard Tessitura processes, and since the Flynn Center converted to Tessitura we’ve moved to using a local table (LT_TKT_HIST) for performance histories.

     

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    1 888 643 5778 ext 329 Office

    ksheehan@tessituranetwork.com

     

Children
No Data