File format for Season Tickets
The generic file format is described in Generic file format (Extended). This documents describes all available import fields.
There are many different possible configurations for season tickets. Not all of them are available for season tickets imports.
- For fixed prices imports, the pricing information must be given in the first part (red part).
- For calculated pricing, the pricing information must be given in the second file (yellow part) and will remain empty in the first file.
The data to be imported needs Season tickets need to be described on two files
- The first file describes the season ticket itself.
- The optional second file describes each performance included in each season ticket.
...
Examples
| Attachments |
|---|
File format for Season Tickets
Season Ticket
Each row describes one season ticket
...
| Field code | Field type | Mandatory | Description |
|---|
| INSTITUTION | Code | Yes | Institution code owning the data to be imported. |
| ORGANIZATION | Code |
| No | Organization code owning the data to be imported. If leave it empty, the institution code will be used. |
| ORDER_NR |
| Number | No | If leave it empty, order number will be set while importing by default. One line is one ticket. So each line is a unique order number if leave it empty. Many tickets can be in an order if leave them the same order number. This number can be started from 1 in a new data file. Then it will be given new one while importing. This will be file number also. |
| ORDER_DATE | Date |
| No | Buying date. If leave it empty, it will be imported date by default. |
| OPERATION_TYPE |
| Enum | Yes |
| Allowed values: SALE or RESERVATION. | |||
| CONFIRMATION_DATE | Date | No | Expiration date to confirm reservation. |
| REMARK | Text 2000 |
SEASON TICKET
| No | Internal remark of order. |
| BUYING_CONTACT |
S_TICKET
| _NR |
| Number | Yes |
| Contact number who buys the order. Mandatory because a sstk needs a contact. |
| SEASON |
| Code | Yes |
| Season code of season ticket. |
| SEASON |
| _TICKET |
| Code | Yes |
| Product code of season ticket. | |||
| PRICE_LEVEL | Code | No | Price level code. |
| TARIFF | Code | Yes | Tariff code. |
| CONTINGENT | Code | No | Contingent code. |
| SEAT_CATEGORY | Code | Yes | Seat category code. |
| PRICE | Amount | Yes | Price of ticket * 100 (so that 25$ = 2500). |
| CHARGE | Amount | No | Charge of ticket * 100 (so that 1$ = 100). |
| VAT | Percentage | No | If leave it empty, it will be 0 while importing by default. Vat rate in percent * 100 (so that 1% = 100). Choose the rate that active and valid following this: Valid from date of vat rate <= ORDER_DATE <= Valid to date of vat rate. |
| PAYMENT_DATE | Date | No | If leave it empty, the operation type is SALE and the price is not 0, the order date will be used by default. Means it can be imported date if the order date is not given. |
| SEASON_TICKET_NR | Number | No | Each season ticket has a unique number to know how many season tickets have been published. In importation, it helps to define ticket to check between data excel file and database system after importing. This number can be started from 1 in a new data file. Then it will be given new one while importing. |
| SEAT_NUMBER | SeatNumber | Yes | Seat number if the ticket holder is seated at the same place for all performances included in the season ticket. |
| CULTURAL_CONTACT_NR | Number | No | Contact number who is ticket holder. If leave it empty and first/last name are empty, the buying contact number will be used by default. |
| BENEFICIARY_FIRSTNAME | Text 50 | No | Beneficiary first name (only if cultural contact is not specified). |
| BENEFICIARY_LASTNAME | Text 50 | No | Beneficiary last name (only if cultural contact is not specified). |
| TICKET_STATE | Enum | Yes if SALE | Mandatory when the operation type is SALE. Allowed values: NOT_PRINTED, PRINTED, CONTROLLED. |
| GENERATION_DATE | Date | No | If leave it empty and the ticket has been printed or controlled, the order date will be used by default. Means it can be imported date if the order date is not given. |
| BARCODE | Text 50 | No | If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default. |
| TAX_NUMBER | Text 50 | No | If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default. |
| SHIPMENT_DATE | Date |
| No | If leave it empty, the order date will be used by default. Means it can be imported date if the order date is not given. |
| SHIPMENT_MODE |
| Code |
| No | If leave it empty and the ticket has been printed or controlled, it will be imported following import rules by default. |
File format for Season Ticket Lines
...
Each row describes one performance included in a season ticket. The rows are linked to the first file using INSTITUTION and ST_NUMBER.
| Field code | Field type | Mandatory | Description |
|---|
| INSTITUTION |
| Code | Yes | Institution code owning the data to be imported. | |
| ORGANIZATION | Code | No | Organization code owning the data to be imported. If leave it empty, the institution code will be used. |
| SEASON_TICKET_NR | Number | Yes | Each season ticket has a unique number to know how many season tickets have been published. This is also used to link season ticket with season ticket lines. This number can be started from 1 in a new data file. Then it will be given new one while importing. |
| SEASON | Code | Yes | Season code of single entry (event/competition). |
| EVENT | Code | Yes | Product code of single entry (event/competition). |
| START_TIME | Timestamp | Yes | Start date time of performance. |
| TARIFF | Code | Yes | Tariff code. |
| CONTINGENT | Code | No | Contingent code. |
| SEAT_CATEGORY | Code | Yes | Seat category code. |
| PRICE | Amount | Yes | Price of ticket * 100 (so that 25$ = 2500). |
| CHARGE | Amount | No | Charge of ticket * 100 (so that 1$ = 100). |
| VAT | Percentage | No | If leave it empty, it will be 0 while importing by default. Vat rate in percent * 100 (so that 1% = 100). Choose the rate that active and valid following this: Valid from date of vat rate <= ORDER_DATE <= Valid to date of vat rate. |
| PAYMENT_DATE | Date | No | If leave it empty, the operation type is SALE and the price is not 0, the order date will be used by default. Means it can be imported date if the order date is not given. |
| SEAT_NUMBER | SeatNumber | Yes | Seat number for each performance in the season ticket. |
| BENEFICIARY_FIRSTNAME | Text 50 | No | Beneficiary first name (only if cultural contact is not specified). |
| BENEFICIARY_LASTNAME | Text 50 | No | Beneficiary last name (only if cultural contact is not specified). |
| TICKET_STATE | Enum | Yes if SALE | Mandatory when the operation type is SALE. Allowed values: NOT_PRINTED, PRINTED, CONTROLLED. |
| GENERATION_DATE | Date | No | If leave it empty and the ticket has been printed or controlled, the order date will be used by default. Means it can be imported date if the order date is not given. |
| BARCODE | Text 50 | No | If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default. |
| TAX_NUMBER | Text 50 | No | If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default. |
| SHIPMENT_DATE | Date | No | If leave it empty, the order date will be used by default. Means it can be imported date if the order date is not given. |
| SHIPMENT_MODE | Code | No | If leave it empty and the ticket has been printed or controlled, it will be imported following import rules by default. |