File format for Service import
The generic file format is described in Generic file format (Extended). This documents describes all available import fields.
Examples
| Attachments |
|---|
| 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 default, the organization code is the same as If leave it empty, the institution code will be used. | OPERATION | Not yet use. | ||||||||
| ORDER_NR | Number | Yes | 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 alsoOrder number. | |||||||||
| ORDER_DATE | Date | No | Yes | Order date. | Buying date. If leave it empty, it will be imported date by default. | ||||||||
| OPERATIONOP_TYPE | Text 50Enum | Yes | Operation typeAllowed values: SALE or RESERVATION, SALE. | REMARK | Text | Order remark. | SEASON_CODE | Text15 | Yes | ||||
| SERVICE_CODE | Text15 | Yes | Code of service product. | ||||||||||
| CONFIRMATION_DATE | Date | No | Expiration date to confirm reservation. | ||||||||||
| REMARK | Text 2000 | No | Internal remark of order | START_TIME | Date | Don't need. | SEAT_NUMBER | Don't need. | |||||
| BUYING_CONTACT_NR | Number | No | Buying contact number. | Contact number who buys the order. If leave it empty, the sale will be anonymous by default. | |||||||||
| ORIGIN_COUNTRY | Text 50 | No | Country of buying contact (only if buying contact is not specified). | ||||||||||
| ORIGIN_REGION | Text 50 | No | Region of buying contact (only if buying contact is not specified). | ||||||||||
| ORIGIN_ZIPCODE | Text 50 | No | Zip code of buying contact (only if buying contact is not specified). | CULTURAL_CONTACT_NR | Number | Cultural contact number. | FIRST_NAME | Text 50 | First name of cultural contact. | LAST_NAME | Text 50 | Last name of cultural contact. | |
| SEASON | Code | Yes | Season code of service. | ||||||||||
| SERVICE | Code | Yes | Product code of service. | ||||||||||
| ITEM | Code | Yes | Item code of service. | ||||||||||
| VALIDITY_BEGIN | Timestamp | Yes | The date starts to validate. | ||||||||||
| VALIDITY_END | Timestamp | Yes | The date stops to validate. | ||||||||||
| TARIFF | Code | Yes | Tariff code | SEATCAT_CODE | Text 15 | Not use yet. | TARIF_CODE | Text 15 | Tarif code of order. | CONTINGENT_CODE | Text 15 | Not use yet. | |
| PRICE | Amount | Yes | Price of serviceticket * 100 (so that 25$ = 2500). | ||||||||||
| CHARGE | Amount | No | Charge of serviceticket * 100 (so that 1$ = 100). | ||||||||||
| VAT | Number | 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 rateVAT in percent. | |||||||||
| PAYMENT_DATE | Date Payment date is null when operation type = 'SALE' and price = 0 or operation type = '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. | ||||||||||
| SERVICE_NR | Number | No | Each service has a unique number to know how many services 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. | ||||||||||
| 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 | Text 50Enum | Yes if SALE | Mandatory when the operation type is SALE. Allowed values: Ticket state in (' NOT_PRINTED', ' PRINTED', ' CONTROLLED'). | ||||||||||
| GENERATION_DATE | Timestamp | 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 givenGeneration date is null when ticket state = 'NOT_PRINTED'. | |||||||||
| 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 | Default now is'IMP-' + ticket id. | |||||||||
| TAX_ | NRNUMBER | Text 50 | No | If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default | Default now is'IMP-' + ticket id. | ||||||||
| SHIPMENT_DATE | Date | Shipment date. If not input: Shipment date = 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 | Code | Text 50 | Shipment date is null when ticket state = 'NOT_PRINTED'. | PERFORMANCE_DATE | Don't need. | ITEM_CODE | Text15 | Yes | Item code of ServiceNo | If leave it empty and the ticket has been printed or controlled, it will be imported following import rules by default. |