TR_SEAT_STATUS documentation

Former Member
Former Member $organization

Hi,

Is there a document explaining specifically what happens within the ticket transaction to result in the different seat statuses?  I couldn't find it so thanks in advance for pointing me in the right direction.

Parents
  • Former Member
    Former Member $organization
    Hi Kevin,
    Thanks for the info below.  Where would I find the seat events in Seat History?


    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Sheehan
    Sent: Wednesday, February 09, 2011 7:52 PM
    To: Jeri Henderson
    Subject: RE: [Tessitura Technical Forum] TR_SEAT_STATUS documentation

    Is this what you want:

     

    A seat that is available and can be reserved.

    A seat that is being temporarily removed from inventory with a blackout hold.

    A seat that is available to be reserved after a previous ticket for that seat was donated for resale.

    A ticketed seat that has been marked as attended.

    A seat that is held and is unavailable based on the security rights of the user.

    A seat this is held and is available because the user has security rights to break the hold code holding the seat.

    A seat that is locked due to a pending transaction (reserve, release, or return) by another user. 

    A seat that is being released in the current order.

    A seat that is being reserved in the current order.

    A seat that is being returned in the current order.

    A seat that is unavailable because of an allocation code for which the order’s mode of sale and/or the constituent’s ranking do not qualify.

    A seat that is reserved by the current constituent as a part of a different order.

    A seat that is reserved by the current constituent as a part of the current order.

    A seat that is reserved and paid by another constituent.

    A seat that is reserved and unpaid by another constituent.

    A seat belonging to another constituent that has been paid and printed.

    A seat that has been paid and printed as part of the current order.

    A seat belonging to the current constituent that has been paid and printed as part of a different order.

    A paid seat for which an upgrade to another product has been requested.

    An unpaid seat for which an upgrade to another product has been requested.

    A paid seat for which an upgrade to another seat in the same product has been requested.

    An unpaid seat for which an upgrade to another seat in the same product has been requested.

     

    That is from the Ticket Order Processing document.  Or are you asking about the seat events that you see in the Seat History?

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    +1 888 643 5778 x 329

    ksheehan@tessituranetwork.com

    =




    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
    Hi Kevin,
    Thanks for the info below.  Where would I find the seat events in Seat History?


    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Sheehan
    Sent: Wednesday, February 09, 2011 7:52 PM
    To: Jeri Henderson
    Subject: RE: [Tessitura Technical Forum] TR_SEAT_STATUS documentation

    Is this what you want:

     

    A seat that is available and can be reserved.

    A seat that is being temporarily removed from inventory with a blackout hold.

    A seat that is available to be reserved after a previous ticket for that seat was donated for resale.

    A ticketed seat that has been marked as attended.

    A seat that is held and is unavailable based on the security rights of the user.

    A seat this is held and is available because the user has security rights to break the hold code holding the seat.

    A seat that is locked due to a pending transaction (reserve, release, or return) by another user. 

    A seat that is being released in the current order.

    A seat that is being reserved in the current order.

    A seat that is being returned in the current order.

    A seat that is unavailable because of an allocation code for which the order’s mode of sale and/or the constituent’s ranking do not qualify.

    A seat that is reserved by the current constituent as a part of a different order.

    A seat that is reserved by the current constituent as a part of the current order.

    A seat that is reserved and paid by another constituent.

    A seat that is reserved and unpaid by another constituent.

    A seat belonging to another constituent that has been paid and printed.

    A seat that has been paid and printed as part of the current order.

    A seat belonging to the current constituent that has been paid and printed as part of a different order.

    A paid seat for which an upgrade to another product has been requested.

    An unpaid seat for which an upgrade to another product has been requested.

    A paid seat for which an upgrade to another seat in the same product has been requested.

    An unpaid seat for which an upgrade to another seat in the same product has been requested.

     

    That is from the Ticket Order Processing document.  Or are you asking about the seat events that you see in the Seat History?

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    +1 888 643 5778 x 329

    ksheehan@tessituranetwork.com

    =




    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