Tck Sales - Price Layer

I am needing to re-write some custom reports that break out ticket sales into price layer columns.  We have a number of custom perf sales reports that group ticket sales by price type, MOS, section, etc. with columns being price category.    

We embed a facility fee into our ticket price as a separate price layer as opposed to using fees.  On our performance sales reports (by price type, MOS, etc)  I need to break out the ticket price and fac fee portion into separate columns.  The way that I originally wrote the reports does not work with the new pricing structure (v12+)

Does anyone out there have a stored proc that does something similar?  Or if you have any advice on the best way to tackle this in the v12 structure I would greatly appreciate it.

 

 

Parents
  • Former Member
    Former Member $organization

    Not sure if you’re using SSRS or Infomaker, but you could create/update a column in the report by adding criteria to show the fee only when price_category = fee (or whatever the fee category is). Then in another column for the ticket price, you can do the same thing…show only when price category is Ticket Price. So you may be able to make these changes in the report instead of the stored procedure.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Todd Tiffany
    Sent: Thursday, July 09, 2015 10:48 AM
    To: Gloria Ormsby
    Subject: [Tessitura Technical Forum] Tck Sales - Price Layer

     

    I am needing to re-write some custom reports that break out ticket sales into price layer columns.  We have a number of custom perf sales reports that group ticket sales by price type, MOS, section, etc. with columns being price category.    

    We embed a facility fee into our ticket price as a separate price layer as opposed to using fees.  On our performance sales reports (by price type, MOS, etc)  I need to break out the ticket price and fac fee portion into separate columns.  The way that I originally wrote the reports does not work with the new pricing structure (v12+)

    Does anyone out there have a stored proc that does something similar?  Or if you have any advice on the best way to tackle this in the v12 structure I would greatly appreciate it.

     

     




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • Former Member
    Former Member $organization

    Not sure if you’re using SSRS or Infomaker, but you could create/update a column in the report by adding criteria to show the fee only when price_category = fee (or whatever the fee category is). Then in another column for the ticket price, you can do the same thing…show only when price category is Ticket Price. So you may be able to make these changes in the report instead of the stored procedure.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Todd Tiffany
    Sent: Thursday, July 09, 2015 10:48 AM
    To: Gloria Ormsby
    Subject: [Tessitura Technical Forum] Tck Sales - Price Layer

     

    I am needing to re-write some custom reports that break out ticket sales into price layer columns.  We have a number of custom perf sales reports that group ticket sales by price type, MOS, section, etc. with columns being price category.    

    We embed a facility fee into our ticket price as a separate price layer as opposed to using fees.  On our performance sales reports (by price type, MOS, etc)  I need to break out the ticket price and fac fee portion into separate columns.  The way that I originally wrote the reports does not work with the new pricing structure (v12+)

    Does anyone out there have a stored proc that does something similar?  Or if you have any advice on the best way to tackle this in the v12 structure I would greatly appreciate it.

     

     




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
No Data