...
File format for Season Tickets
| Field code | Field type | Mandatory | Description | ||
|---|---|---|---|---|---|
| INSTITUTION | Text 15Code | Yes | Institution code owning the data to be imported. | ||
| ORGANIZATION | Text 15Code | YesNo | Organization code owning the data to be imported. By defaultIf leave it empty, the organization code is the same as the institution code will be used. | ||
| ORDER_NR | Number | Yes | Order 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 | Yes | Order dateNo | Buying date. If leave it empty, it will be imported date by default. | |
| OPERATION_TYPE | Text 70Enum | Yes | Operation type. Possible Allowed values: SALE or RESERVATION | ||
| REMARK | Text | Order remark | |||
| BUYING_CONTACT_NR | Number | Yes | Buying contact number. | CULTURAL||
| CONFIRMATION_ | CONTACT_NRDATE | NumberDate | Cultural contact number. By default it is identical to the buying contact number. | ||
| FIRST_NAME | Text 50 | Beneficiary first name. | |||
| LAST_NAME | Text 50 | Beneficiary last name. | |||
| No | Expiration date to confirm reservation. | ||||
| REMARK | Text 2000 | No | Internal remark of order. | ||
| BUYING_CONTACT_NR | Number | YesSeason | ticket numberContact number who buys the order. Mandatory because a sstk needs a contact. | ||
| SEASON | Code | Yes | Season code of | theseason ticket. | |
| SEASON_ | CODETICKET | Code | Yes | Product code of season ticket. | |
| PRICE_LEVEL | Code | No | Price level code. | SEAT_NUMBER||
| TARIFF | SeatNumberCode | Seat number if the ticket holder is seated at the same place for all performances included in the season ticket | Yes | Tariff code. | |
| CONTINGENT | Code | No | Common contingentContingent code. | ||
| SEAT_ | CODECATEGORY | Code | Yes | Seat category code. | TARIFF|
| PRICE | CodeAmount | Yes | Tarif codePrice of ticket * 100 (so that 25$ = 2500). | PRICE||
| CHARGE | Amount | YesNo | PriceCharge of | season ticketticket * 100 (so that 1$ = 100). | |
| VAT | Percentage | YesNo | 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 <= | ORDERORDER_DATE <= Valid to date of vat rate. | |
| PAYMENT_DATE | Date | Payment date must be empty if price is 0 or operation type is RESERVATION | 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 | Ticket stateif SALE | Mandatory when the operation type is SALE. Allowed values: NOT_PRINTED, PRINTED | or , CONTROLLED. |
| GENERATION_DATE | TimestampDate | Generation date Mandatory when the ticket state is PRINTED or CONTROLLEDNo | 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 | Bar code of the season ticketNo | 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 | The tax number of the season ticketNo | If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default. | ||
| SHIPMENT_DATE | Date | Shipment date of the season ticket. Default value: Order dateNo | 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 | Text 50Code | Shipment mode of the season ticket. Allowed values: TBD Mandatory when the ticket state is PRINTED or CONTROLLED |
| 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
...
| Field code | Field type | Mandatory | Description | ||
|---|---|---|---|---|---|
| INSTITUTION | Text 15Code | Yes | Institution code owning the data to be imported. | ||
| ORGANIZATION | Text 15Code | YesNo | Organization code owning the data to be imported. If leave it empty, the institution code will be used. | ||
| STSEASON_TICKET_NUMBERNR | Text 20Number | Yes | Instance number of season ticket. If several season tickets in one order, they should all have different number so that SecuTix will acknowledge them as different season ticket product | SEASON_CODEEach 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 the eventsingle entry (event/competition). | ||
| EVENT_CODE | Code | Yes | The event code | STARTTIMEProduct code of single entry (event/competition). | |
| START_TIME | Timestamp | Yes | The performance start Start date time of the event | SEAT_NUMBER | SeatNumberperformance. |
| TARIFF | Code | Yes | Tariff code. | ||
| CONTINGENT | Code | No | Contingent code. | ||
| SEAT_ | CODECATEGORY | Code | Yes | Seat category code. | TARIFF|
| PRICE | CodeAmount | Yes | Tarif code | PRICEPrice of ticket * 100 (so that 25$ = 2500). | |
| CHARGE | Amount | YesNo | Price of the seatCharge of ticket * 100 (so that 1$ = 100). | ||
| VAT | Percentage | YesNo | 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 <= | ORDERORDER_DATE <= Valid to date of vat rate. | |
| PAYMENT_DATE | Date | Payment date must be empty if price is 0 or operation type is RESERVATION | 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 | CodeEnum | Yes Ticket stateif SALE | Mandatory when the operation type is SALE. Allowed values: NOT_PRINTED, PRINTED or , CONTROLLED. | ||
| GENERATION_DATE | TimestampDate | Generation date. Mandatory when the ticket state is PRINTED or CONTROLLEDNo | 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 | Bar code of the ticketNo | 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 | The tax number of the ticketNo | 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 | Text 50Code | No | If leave it empty and the ticket has been printed or controlled, it will be imported following import rules by default. |