2 Import File Format
This interface is designed to read a flat or comma delimited file format only. The acceptable file type is determined by the value set in Parameter group “DataImport”,”Reservation File Type”. For example, 'D' for delimited, 'F' for fixed length or a default value if a parameter is not specified
Each flat file represents a group of entries that the program is able to import. The format of each file name is described below:
<DATA_TYPE><EXPORT_DATE>.TXT
Where:
<DATA_TYPE>
is the group of entries presented
in the file. <EXPORT_DATE>
is the date when the file
was created by an external system. Format is always YYYYMMDD..TXT
is the File extension.The sequence in which the data is read is important. The program will first process the Group details file, followed by the Guest or Crew Master File. This sequence allows you to assign guests/crew to groups, translating external system identifiers into SPMS internal numbers.
Below is the supported data transfer and file format.
Table 2-1 Reservation Data Type
NAME | FILE NAME | DESCRIPTION |
---|---|---|
MASTERYYYYMMDD.TXT |
Master data (required and imported first) used when importing guests. |
|
CRWMASTERYYYYMMDD.TXT |
Master data (required and imported first) used when importing crew members. |
|
GROUPYYYYMMDD.TXT |
Groups details. |
|
VISITORYYYYMMDD.TXT |
Visitor details. |
|
FLIGHTYYYYMMDD.TXT |
Flight details (can have many rows for one Master Data row). |
|
GIFTYYYYMMDD.TXT |
Amenity and gift orders details (can have many rows for one Master Data row). |
|
DOCUMENTSYYYYMMDD.TXT |
Document Types (can have many rows for one Master Data row). |
|
SRTYYYYMMDD.TXT |
Special request orders (can have many rows for one Master Data row). |
|
PPSYYYYMMDD.TXT |
Pre-Postings (can have many rows for one Master Data row). |
|
EXCYYYYMMDD.TXT |
Excursions pre-booked tickets (can have many rows for one Master Data row). |
|
PREPAIDESEYYYYMMDD.TXT |
Excursions pre-paid tickets (can have many rows for one Master Data row). |
|
EPWYYYYMMDD.TXT |
Excursions waitlist (can have many rows for one Master Data row). |
|
COURSEYYYYMMDD.TXT |
Courses/Certificates details (can have many rows for one Master Data row). Basically, the difference between standard courses and medical certificates is by the TAK_COUID imported by the reservation. |
|
DINING.TXT |
Restaurant dining information file (for Dining System). |
|
GHIYYYYMMDD.TXT |
Guest history information. |
|
CHIYYYYMMDD.TXT |
Crew history information. |
|
DISYYYYMMDD.TXT |
Discount details. |
|
ROTYYYYMMDD.TXT |
Routing details. |
|
UDFYYYYMMDD.TXT |
User definable field details. |
|
UDDYYYYMMDD.TXT |
User definable data details. |
|
SPIYYYYMMDD.TXT |
Spa retail items details. |
|
SPYYYYYMMDD.TXT |
Spa treatment items details. |
|
SPBYYYYMMDD.TXT |
Spa packages details. |
|
SPVYYYYMMDD.TXT |
Spa price definition details. |
|
SPAYYYYMMDD.TXT |
Spa bookings details. |
|
GC1YYYYMMDD.TXT |
Gift Card details. |
|
CC1YYYYMMDD.TXT |
Credit Card details. |
|
PREBOOKEDTKPOYYYYMMDD.TXT PREPAIDTKPOYYYYMMDD.TXT |
Pre-booked and Pre-paid Events Tickets (can have many rows for one Master Data row). For Pre-booked Events Tickets, must be all in one import file and Prepaid Event Tickets must be in a separate file. |
|
TKPWYYYYMMDD.TXT |
Events Waitlist (can have many rows for one Master Data row). |
Table 2-2 Standard Type of Setup
NAME | FILE NAME | DESCRIPTION |
---|---|---|
STDEXCURSION.TXT |
Standard Excursion import (Can import pre-setup standard excursion to be used onboard). |
|
BOKEXCURSION.TXT |
Bookable Excursions import is based on Standard Excursion setup import with a particular DATE. |
|
EXCPACKAGE.TXT |
Excursions Package Definition import should always be imported prior to Packaged Excursions Linking Setup import. |
|
EXCPACKAGELINK.TXT |
Packaged Excursions Linking Setup defines which Tours are assigned to each Package with the necessary Package specific prices. |
|
CCERTSETUP.TXT |
Courses and Certificates Code import (To be able to import the courses and certificates code and description). |
|
AMTSETUP.TXT |
Amenity Code import (To be able to import the amenity code and description). |
|
SRTSETUP.TXT |
Special Request Code import (To be able to import the special request code and description). |
|
EVENTTEMPLATES.TXT |
Event Templates import. |
|
EVENTTEMPLATESPRICING.TXT |
Since Events can have different Prices for different Price Categories and Account Types, we need to be able to import Prices for each Event Template. |
|
EVENTBOOKABLES.TXT |
Bookable Events import is based on Event Templates setup, imported with a particular DATE. |
|
EVENTBOOKABLESPRICING.TXT |
Since Events can have different Prices for different Price Categories and Account Types, we need to be able to import Prices for each Bookable Event. |