File format for Pass Visits
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 |
| 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 | No | Internal remark of order. |
| BUYING_CONTACT_NR | Number |
| No | 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). |
| SEASON | Code | Yes | Season code |
| of visit pass. |
| VISIT_ |
| PASS | Code | Yes |
| Product code of |
| visit |
| pass. |
| START_TIME |
| Timestamp | Yes | Start time of the visit. | |
| DURATION | Number | Yes | Duration of the visit in seconds. |
| TARIFF |
| Code | Yes |
Leave empty for individual visits
Name of the group.
Yes for group visits
Leave empty for individual visits
Theme of the visit
(only useful for guided visits)
ISO Language code of the visit (fr, en, ...)
(only useful for guided visits)
If not filled in, the purchase contact is used
For a group visit, the contact must be of type RELAY.
Operation type.
Possible values: SALE or RESERVATION
Type of visitor
Possible values: PARTICIPANT or ACCOMPANIER
Gross amount
If flat rate, full price of the visit
If individual rate, unit price per participant
| Tariff code. | |||
| CONTINGENT | Code | No | Contingent 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. |
| VISIT_PASS_NR | Number | No | Each visit pass has a unique number to know how many visit passes 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 | 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. | ||
| GROUP_NAME | Text 50 | Yes if group visits | Name of the group. Leave empty for individual visits. |
| GROUP_KIND | Code | Yes if group visits | Kind of the group. Leave empty for individual visits. |
| THEME | Code | No | Theme of the visit (only use for guided visits). |
| LANGUAGE | Code | No | ISO Language code of the visit (fr, en, ...) (only use for guided visits). |
| VISITOR_TYPE | Enum | Yes | Allowed values: PARTICIPANT or ACCOMPANIER. |
| NB_VISITORS | Number | Yes | Must be > 0. |
| PLACE | Code | No | |
| GUIDE | Code | No | Last name and first name of the guide. |
| GROUP_CRIT_ELEMENT | Code | No | Group criterion element code. |