Versions Compared

Version Old Version 13 New Version Current
Changes made by

rks

Kho SA

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

File format for Service import

The generic file format is described in Generic file format (Extended). This documents describes all available import fields.

Note

  • When you need a standard import, please use the template as example.

  • Please keep all columns, all 4 first rows, event if there’s no data.

  • Please keep the order of all columns and all rows. Don’t move or change them.

  • Please keep the headers/titles as they are, especially the 4th row.

  • If you want to send us *.csv file, please keep columns, rows and their order also.

  • Please use option “Comma delimited” for .csv file.

Examples

Attachments

Field code

Field type

Mandatory

Description

INSTITUTION

Text 15

Code

Yes

Institution code owning the data to be imported.

ORGANIZATION

Text 15

Code

Yes

No

Organization code owning the data to be imported.

By default

If leave it empty, the

organization code is the same as the

institution code will be used.

ORDER_NR

Number

YesOrder numberOrder date

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

No

Buying date.
If leave it empty, it will be imported date by default.

OPERATION_TYPE

Enum

Yes

Operation type.

Allowed values: SALE or RESERVATION.

CONFIRMATION_DATE

Date

No

Expiration date to confirm reservation.

REMARK

Text 2000

No

Order

Internal remark of order.

BUYING_CONTACT_NR

Number

No

Buying contact number. If it is

Contact number who buys the order.
If leave it empty, the sale

is

will be anonymous by default.

ORIGIN_COUNTRY

Text 50

No

Country of buying contact (only if

Buying

buying contact is not specified).

ORIGIN_REGION

Text 50

No

Region of buying contact (only if

Buying

buying contact is not specified).

ORIGIN_ZIPCODE

Text 50

No

Zip code of buying contact (only if

Buying contact is not specified).CULTURAL_CONTACT_NRNumberNo

Cultural contact number.

If left empty and first/last name are empty, the

buying

contact number is used.FIRST_NAMEText 50NoBeneficiary first name (only if Cultural contact number is not specified).LAST_NAMEText 50NoBeneficiary last name (only if Cultural

contact

number

is not specified).

SEASON

Code

Yes

Season code of service

product

.

SERVICE

_CODE

Code

Yes

Product code of service.

ITEM

_CODE

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

Tarif

Tariff code.

PRICE

Amount

Yes

Price of

the service

ticket * 100 (so that 25$ = 2500).

CHARGE

Amount

Yes

No

Charge of

service

ticket * 100 (so that 1$ = 100).

VAT

Percentage

Yes

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 <=

 ORDERMandatory when

ORDER_DATE <= Valid to date of vat rate.

PAYMENT_DATE

Date

Yes if SALE

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).

Default value: Order date

BENEFICIARY_LASTNAME

Text 50

No

Beneficiary last name (only if cultural contact is not specified).

TICKET_STATE

Enum

Yes if SALE

The state of ticket.

Mandatory when the operation type is SALE.
Allowed values: NOT_PRINTED, PRINTED

or

Generation date.

Mandatory if

, CONTROLLED.

GENERATION_DATE

TimestampYes if PRINTED or CONTROLLED

Date

No

If leave it empty and the ticket has been printed or controlled

.Default value: Order d

, the order date will be used by default. Means it can be imported date if the order date is not given.

BARCODE

Text 50

Yes if PRINTED or CONTROLLED

No

If leave it empty and the ticket has been printed

 or controlled.Not yet used. Default now is The tax number of the ticket. Mandatory if

or controlled, it will be generated following import rules by default 'IMP-' + ticket id.

TAX_NUMBER

Text 50

Yes if PRINTED or CONTROLLED

No

If leave it empty and the ticket has been printed

 or controlled.Not yet used. Default now is

Shipment date of the service.

Default value: Order date

or controlled, it will be generated following import rules by default 'IMP-' + ticket id.

SHIPMENT_DATE

Date

Yes

Shipment mode of the service.

Allowed values: TBD.

Mandatory if

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

Yes if 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.