File format for memberships
The generic file format is described in Generic file format (Extended). This documents describes all available import fields.
Examples
| Attachments | ||
|---|---|---|
|
Fields
| 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. | ||||||
| ORDER_NR | Number | No | Order number. Will be set by import package while importing if left empty. | 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 | SALE_DATE | Timestamp | Yes | Date of the sale. By default, sale date is importing date. | ||
| OPERATION_TYPE | Text 50Enum | Yes | Operation type. Allowed values: SALE or RESERVATION | REMARK | Text | No | Order remark. | ||
| CONTACTCONFIRMATION_NRDATE | Text 15Date | Yes | The contact number of contact that owner the membership card. | ||||||
| FIRST_NAME | Text 50 | No | Beneficiary first name. Set this info only for sold membership cards. | ||||||
| LAST_NAME | Text 50 | No | Beneficiary last name. Set this info only for sold membership cards. | ||||||
| No | Expiration date to confirm reservation. | ||||||||
| REMARK | Text 2000 | No | Internal remark of order. | ||||||
| BUYING_CONTACTMEMBER_NR | Number | YesThe | membership number of contact. This number allows another member to buy ticket on behalf of this member.Contact number who buys the order. Mandatory because a membership needs a contact. | ||||||
| SEASON | Code | Yes | Season code of the membership product. | ||||||
| MEMBERSHIP | Code | Yes | The product Product code of the membership that is to be imported. | ||||||
| TARIFFVALIDITY_BEGIN | CodeTimestamp | Yes | The tariff code linked to the season that match one of these conditions : | ||||||
| VALIDITY_BEGINEND | DateTimestamp | YesBeginning | of the membershipThe date stops to validate. | ||||||
| VALIDITY_ENDTARIFF | DateCode | Yes | End of the membershipTariff code. | ||||||
| PRICE | Amount | Yes | Price of season ticket * 100 (so that 25$ = 2500). | ||||||
| CHARGE | Amount | No | Charge of ticket * | 100Not used yet100 (so that 1$ = 100). | |||||
| VAT | PercentageYes | 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 <= ORDERORDER_DATE <= Valid to date of vat rate. | ||||||
| PAYMENT_DATE | Date | Yes if SALE | No | If leave it empty, Mandatory when 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. | |||||
| MEMBERSHIP_NR | Number | No | Each membership has a unique number to know how many memberships 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 | or , PRINTED, CONTROLLED. | |||||
| GENERATION_DATE | TimestampDate | Yes if PRINTED | 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 Generation date. Mandatory when the ticket state is PRINTED. | |||||
| BARCODE | Text | 10050 | Yes if PRINTED | The bar code of ticket. Ex: Input = 345678920 | TAX_NR | Text 30 | Yes if PRINTED | The tax number of the ticket. If not inserted, the tax number will be generated with prefix equal to "IMP-"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. |