• Replies 38 replies
  • Subscribers 418 subscribers
  • Views 637 views
  • Users 0 members are here
Related

Group Sales Reporting and Other Tid Bits

Kelly Thayer
$organization

Hi All !

I am looking for some help and tid bits regarding group sales. 

What are the best reports to pull to track group sales, as well as track the payments made for them (or to track payments that need to be made!) 

I am interested in any other helpful tips or tricks with Group Sales and Tessitura, as we are still fairly new to this awesome database! 

Thank you! 

Parents Reply Children
  • Former Member
    Former Member $organization in reply to Meredith Woolard (she/her)

    Here's the T_KEYWORD setup for the custom plan element, followed by the view it references.

    T_KEYWORD
    Description: Plan Production Season
    Data Type: String
    Edit Mask: Alphanumeric
    Detail Tbl: T_PLAN
    Detail Col: !.custom_2
    Ref Tbl: lvs_prod_season_list
    Ref Idcol: prod_season_no
    Ref Desccol: description
    Ref sort: sort_value
    Category: Plans
    Use For List: Plan
    Custom Id: 2

    USE [impresario]
    GO
    SET ANSI_NULLS ON
    GO
    SET QUOTED_IDENTIFIER ON
    GO
    CREATE View [dbo].[LVS_PROD_SEASON_LIST]
    AS
    /*********************************************************************************************************
    CWR 6/21/2013 #2249
    Specifically for use in List Building with new Ticket and Package History tables
    VS_PROD_SEASON_LIST edited 9/17/17 for use in Plan Production Season custom element DN
    *********************************************************************************************************/

    select prod_season_no, Coalesce(c.short_name, c.description) + ' (' + b.description + ')' as description, b.fyear, ROW_NUMBER() OVER (PARTITION BY c.type ORDER BY b.fyear desc, c.description) as sort_value
    from T_PROD_SEASON a
    JOIN VRS_SEASON b ON a.season = b.id
    JOIN T_INVENTORY c ON a.prod_season_no = c.inv_no
    GO

  • $organization in reply to Former Member

    This is just what I needed, thank you! 

    We are implanting plans to be used for our artistic team, so they can keep track of contracts and other production items! 

  • $organization in reply to Former Member

    Thank you so much for presenting this!  I have been unable to respond because my tickets and forum responses were not posting for some crazy reason.  I had to change the code so it pulled performance for us rather than production season.  After some playing around I got it to work so thank you so much for the code.  I would have been lost without it.

    I have a couple of question...I need the field to be longer on the Plans screen but it seems that it can only be one size.  Do you know if there is a way to make it wider?   l also noticed in T_Keyword  for the Detail TBL you referenced the T_PLAN table rather than the view VS_Plan .  Is there a reason I should reference the table rather than the view?

  • Former Member
    Former Member $organization in reply to Terry Stevens

    Hi Terry,

    Glad you got it to work for you!

    I don't know of anyway to make the field longer. Since it's a standard custom field I doubt there is a way, but Support may be able to help there. 

    I have a bad habit of using tables rather than views, so there's no good reason for that choice. Using the view would probably work; I'd just test it first.

    Dorothy