Ensure that the relevant configuration is selected in the Configuration name field before defining any option on this page.
Click Save after updating any option on this page.
|
|
If you want to be able to automatically import a new PNR to an existing travel file with passengers and flight transactions, select Import new PNR to existing travel file.
If the PNR already exists in the system, but with different passenger names – a new travel file will be opened, as it can be assumed that the same PNR number is reused for a completely different booking. If, however, the existing PNR includes at least one passenger name from the travel file, then the travel file will be updated (and no new travel file will be opened).
If the PNR is new (does not exist in the system), but the passenger has a travel file with overlapping dates – the PNR will be updated in the existing travel file, or a new travel file will be created (according to the system logic of adding a reservation to an existing travel file or opening a separate travel file)
If the PNR is new (does not exist in the system) and the passenger does not have a travel file with overlapping dates – a new travel file will be opened.
This option does not apply to group travel files. When importing a group PNR, the system creates a group travel file. If there are individual passengers in the PNR with separate travel arrangements, the system opens a new individual travel file which is linked to the group travel file.
A match is determined as follows:
All the passengers in the PNR exist in the travel file. Passenger names, phone numbers, index numbers (if they exist in the PNR), are compared. If none of the other information matches the system will also search for travel agent/corporate client name and employee ID.
The user attached to the travel file and the user who created the PNR share the same branch.
There is up to a 48 hour overlap between the start and end dates.
If there is a match with a closed travel file, the PNR is not imported. If there is a match with a travel file that has the status Cancel, the PNR is imported and the system automatically changes the travel file status back to Open.
If the PNR contains the remark New Travel File, the PNR is imported into a new travel file, even if it was supposed to be imported into an existing travel file. However, if the the PNR already exists in the system or contains a specific travel file number, it will be imported into an existing travel file, and the remark will be ignored.
If you want the system to automatically cancel travel files and transaction fees when an XI command is performed in the GDS, select Automatically cancel travel file when PNR is cancelled in GDS.
When this option is selected, when an XI command is performed in the GDS, and the flight transaction is removed from the travel file, if there are no other transactions in the travel file:
Any tax invoices issued for transaction fees in the travel file are automatically cancelled
All transaction fees in the travel file are automatically deleted
The status of the travel file is changed to Cancel.
This option does not affect travel files containing other financial documents (for example a receipt), including cancelled financial documents.
If you want to avoid opening a new travel file for older reservations done in your previous system (before switching to Travel Booster), select Cut over date and enter a date using the dropdown menu. A PNR with a departure date earlier than the cut over date will not open a new travel file.
In the table in this section select which GDS should be used for searching and booking services (also internal contracts), which GDS should be used for importing PNRs (using the From PNR tool), which GDS should be used for the GDS to TB process, and which GDS should be used for cancelling reservations.
Before you can activate the GDS, you need to configure it in Setup - Website Definitions - Content - Reservations Systems - <GDS Name>
Click here for detailed examples.