This is primarily a consortium question. We have a group consisting of the Performing arts center and three resident companies. The parking garage at the center is shared by everyone. We are in the process of building the parking facility in Tessitura and plan to use allocations to each organization to prevent overselling.
This is the first time we have tried to set up an event which will be sold by multiple organizations and we are running into a roadblock due to the Business Unit settings in TR_SEASON_TYPE.
Currently we have one Season Type for each organization with the Business Unit for that organization assigned to it. I'm assuming the answer here is to create a new business unit to contain these parking sales, but I'm not at all sure how to allow users across multiple organizations access to it.
I know plenty of organizations out there have sold tickets from box offices in multiple organizations. Any help is appreciated.
Hi Levi
We just have the one BU, and all of our batches have that set – apart from anything else, I’d tend to avoid NULLs wherever possible, given their propensity to confuse people.
But the notes on tr_batch_type do say :
BU = Business Unit for this batch. If this is blank, then a batch can be mixed business units.
If this is filled in, (from TR_BU) then the entire batch can only contain transactions from
this business unit
So I guess the implication is that NULLs are ok, in this case, at least???
________________________________Ken McSwain
Systems and Technology Manager
Australian Chamber Orchestra
ken.mcswain@aco.com.au
Ph +61 2 8274 3833 :: Mob +61 418 659 360 :: Fax +61 2 9274 3801
PO Box R21, Royal Exchange NSW 1225
2 East Circular Quay, Sydney NSW 2000
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Levi SauerbreiSent: Thursday, 7 July 2011 11:31To: Ken McSwainSubject: Re: [Tessitura Ticketing Forum] Multiple organizations selling the same parking
Thank you all for the answers. And support has been very helpful as well. Follow up question as I work through some of these changes in Test tonight.
In places where a business unit is not strictly required (i.e. TR_BATCH_TYPE) is a NULL acceptable? Or would that cause problems somewhere in the process?
Thanks again all!
From: Levi Sauerbrei <bounce-levisauerbrei8271@tessituranetwork.com>Sent: 6/28/2011 8:48:43 AM
Thanks Kevin,
I've opened a ticket already. As with all major projects, it seems that the deadline for this is already upon me :)
--
Levi Sauerbrei
On Jun 28, 2011, at 8:42 AM, "Kevin Sheehan" <bounce-kevinsheehan4372@tessituranetwork.com> wrote:
Ideally, yes, you should just have one business unit. Before you start changing things around, I suggest opening a help ticket. Playing around with business units can be tricky, and support can help steer you through any potential problems. Kevin SheehanSenior Documentation & Learning Resources SpecialistTessitura Network+1 888 643 5778 x 329ksheehan@tessituranetwork.com This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
Ideally, yes, you should just have one business unit. Before you start changing things around, I suggest opening a help ticket. Playing around with business units can be tricky, and support can help steer you through any potential problems.
Kevin Sheehan
Senior 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 Ticketing Forum. You may reply to this message to post to the Ticketing 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!