Partner Box Office Statement

Hi Mary,

Try adding either MAX([Ticket Value]) or adding [Ticket Value] in the Rows area after Price Type.

Cheers.

Chris, Thanks! That was what I was missing.

OK - So what if i want the price to be combination of all layers? Fee and Ticket?

SO really I need the Paid amount to be all layers and I am getting them both per ticket and in Value.

Hi Mary.

This might be the issue i was getting the other day with my ATP calcs. In TR_PRICE _LAYER do you have ranks in your price layers?

"If you look at TR_PRICE_LAYER_TYPE, the Ticket Count in Analytics counts all Ticket Price price categories for this field. If multiple Ticket Price price layers exist for a performance, the Ticket Price price layer with the min start date and min price layer type rank is counted - as all of your Ticket Price Layers are the same value, they all get counted hence the inflated value." Maria Christas to me

As soon as i ranked my ticket price layers the double counting went away. 

Cheers,

Heath 

Heath Wilder Wasthis problem only found in 15.1.x or did you see this in the 15.0.x series of Tessitura?

Hi Tom,

Price Layers were introduced in Analytics in 15.1.x. If you have a look under the Price Layers in Analytics note under the 15.1 Tessitura Analytics changes at  https://www.tessituranetwork.com/Help_System_v151/Content/v15_1/Tessitura%20Analytics%20Changes.htm it does indicate that the Ticket Price later with the min start date and price layer type rank is counted, however I can confirm that the rank column does exist in 15.0.x if you wanted to update that now.

Cheers,

Maria

As Maria says - you'll have that fun in 15.1

(15.0 was aok)

Ah, yes. Thanks for asking that. Making sure this is a Value rather than a field on Rows, we can use a formula to get the max total ticket value for any given SLI within each price type + zone combination.

MAX ( [SLI ID] , [Total Ticket Value] )

Here's a shot showing Ticket Value and that formula side by side. The first bit includes Price Layers valued at $33 and $1. Price Layer is then toggled off in the second shot. The MAX Ticket Value then still just shows $33, whereas the formula above yields $34, the max total ticket value for any SLI within the groupings and filters of the pivot table.

Between Chris and Heath I am good to go!

Thanks.

I'm moving up in the world

ok something still isn't right - the math doesn't add up: $124.5 x 475 does not equal $35,722.00 andI pulled for paid/reserved too.

Ideal result -

1- base price (all price levels)

2- paid price (all price levels)

3- sold count

4- total paid amount

is the Price Per Ticket a Max Value at the Price per ticket?  What's your ATP for those rows?

I was just checking your initial table 2019-10-25(E)PG102519E Zone 1 Single Ticket has 42 tickets at $4875. 
Is there dynamic pricing in there? Are you missing a Price Layer? Are some Pricetypes editable?

price per ticket is- MAX ( [SLI ID] , [Total Ticket Paid Value] )

base is MAX( [SLI ID] , [Total Seat Home Base Value] )

dynamic pricing yes. All layers are showing. Prices are editable.

Correct me if I'm wrong but MAX ( [SLI ID] , [Total Ticket Paid Value] )  will give you the most expensive Ticket Price for that Price type over all zones (ie: Premium).  Your Zone 4 Single tickets are about $45 yeah?  So your ATP for Single Tickets on Friday would be around $74.57

I just had a crack at Chris' formula and for our subs ranging from $38.25 to $83.30 it's just returning the top price of $83.30