...
Aim: create tables to group logical seat categories from different logical configurations (most of the time, from different venues) in categories that will be used in composed products (packages or seaon season tickets).
Description:
In the live events environment (mostly), you may have composed product / season tickets that could give access to venue with different logical configuration, and potentially different logical seat categories.
...
Set an internal name (60 characters max.) and a code (8 characters max.) to your mapping table.
Seat categories tab
Then the idea is to define "I've got a physical category 1. If i'm in an event in my logical conf A, what should it correspond to? in my logical conf B?"For each given physical seat category that is used in a logical configuration "A", you could define what is the corresponding seat category in a logical configuration "B".
Let's take an example: you want to sell a season ticket with events happening in 2 concert halls :
...
In our example, we want the following:
| Season ticket category | Seat category in Large room | SEat category in Medium room |
|---|---|---|
| Category 1 | Cat 1 | Cat 1 |
| Category 2 | Cat 2 | Cat 2 |
| Category 3 | Cat 3 | Cat 3 |
| Category 4 | Cat 4 | Cat 3 |
| Category 5 | Cat 5 | Cat 3 |
| Category 6 | Cat 6 | Cat 3 |
In order to create season ticket catory category 4, click on on 
:
And fill the following:
Seat category is the mapped category that will be used in the composed product.
...