Sabre

Sabre is a global distribution system (GDS) providing access to flights of over 380 airlines and airports world-wide.

Note that the activation of this interface is contingent upon a commercial agreement with Sabre. Certificate validation from Sabre must also be obtained.

Setting Up the Interface

Special Notes

Setting Up the Interface

  1. Go to Setup – Website Definitions.

  2. In the Configuration name field, select the relevant configuration from the drop-down list.

  3. Go to Content - Reservation Systems - Sabre.

  4. In the Active Services section, select Flight.

  5. In the General section, enter the following information supplied to you by Sabre into the appropriate fields:

    1. Valid IP

    2. URL

    3. Agent pcc - PseudoCityCode (IPCC)

    4. User ID

    5. Customer identifier

  6. In the Agency star profile code field, enter your company's Sabre agency star code.

    Sabre maintains a STAR profile on each travel agency.

    The Agency Star Code is a code that allows you to add your company's STAR profile to Sabre PNRs.

  7. If relevant, select the following options:

    Field

    Description

    Do not import PNRs from the ENS with remarks from other systems

    If this option is selected, when a PNR is imported from the ENS, the system will search the PNR for a remark with the type itinerary that begins with: DPC.

    If the system identifies, such a remark it will not open a new travel file for the PNR. If there is already an existing travel file for that PNR, the system will ignore the remark and update the travel file.

    Add transaction fee information to PNR

    If there is transaction fee for reserving a flight, select this option to send this information as a remark to Sabre.

    Display more than 12 flights

    By default when combining a static package and flights from Sabre 12 results are displayed in the query results.

    Select this option to display more than 12 flights in the query results. In the More flt iterations num field, select the number by which to multiply the amount of flight results in the search query. This number multiplied by 12 is the amount that of query results that appear (in other words 2 is 24, 3 is 36, etc).

    Enable separate net and published queries per search

    Two separate Net and Published queries are searched for. As a result the number of results may be up to doubled. The order of results display is according to the UI definitions.

    Bring Tax

    When reserving a flight through Sabre as part of a Static package, a request is sent to Sabre for the tax information on the flights.

  8. In the Default phone field, enter the phone number which is added to the PNR in the booking process.

  9. In the Ticketing Queue field, enter the ticketing queue number provided by Sabre.

    		10.

    This is used if the customer needs to send PNRs to a queue for SABRE to automatically ticket them.

  10. In the PNR import queue field, enter the Sabre queue for automatically importing PNRs.

  11. In the Instruction code field, enter the instruction code provided by Sabre to send PNRs to a ticketing queue.

  12. In the Air Rules Message File path, enter the directory path of the HTML file displaying generic air rules for reservations when air rules are not supplied by Sabre.

  13. In the Queue ID for pax files that failed to bring tax, select a queue to which travel files are added if bring tax is enabled, and the query to Sabre fails.

  14. If you do not want travel files imported through Sabre without a DK number to be associated with a corporate client select Do not add corporate client to travel files opened for PNRs without a DK number.

  15. In the Password field, enter the password supplied to you by Sabre.

  16. In the Name field, enter Sabre

  17. For online registration of agents within existing agencies, select Agent Self Registration, and enter the Agent self registration code.

  18. The Ticketing section is currently not functional:

  19. In the Ens section, select Enable Ens, and enter the Ens URL.

  20. In the Countries for searching round trip as two one ways, select countries that when searched for as a round trip are displayed as two one way trips.

  21. Click Save.

Special Notes

  1. Supported/Unsupported Features:

    Feature

    Supported

    Unsupported

    All fare types (published, negotiated, and IT)

    ✔

     

    Commission and markup definitions for published and net fares

    ✔

     

    Multi-selection flight search (up to 3 destinations)

    ✔

     

    Airline codesharing

    Operating airline information provided in flight details

    ✔

     

    Open travel files in the system based on Sabre PNR

    ✔

     

    Update travel files in the system by importing an Sabre PNR

    ✔

     

    Optional ticketing interface

    (Sabre Robot required)

    ✔

     

    Flight search according to destination using IATA code

    ✔

     

    Flight search according to airline

    ✔

     

    Flight search according to direct flight

    ✔

     

    Round trip flight search

    ✔

     

    Flight Duration

    ✔

     

    One way flight search

    ✔

     

    Flight search according to class

    (Economy, Enhanced Economy, Business, and First)

    ✔

     

    Flight search according to time of day

    Morning:    07:00 +/- 5 hours

    Noon:        14:00 +/- 3 hours

    Evening:    19:00 +/- 3 hours

    Night:        01:00 +/- 4 hours

    ✔

     

    Price breakdown of fare and taxes

    ✔

     

    Pricing according to age (infant, child, adult, senior)

    Automated verification using date of birth

    ✔

     

    Online cancellation

    ✔

     

    User selection of inbound and outbound flights

    ✔

     

    Meal selection in the system (for B2E only)

    ✔

     

    Detailed flight information: aircraft type, airline carrier, meals on flight, and link to terms and conditions.

    ✔

     

    Seat selection

     

    X

    Cancellation fee policy

     

    X

    Online reservation amendment

     

    X

    EMD

    ✔

     

  2. Reservation Parameters:

    1. A reservation has a minimum of 1 passenger/maximum of 9 passengers.

    2. A reservation has a minimum of 2 days/maximum of 1 year.

  3. Limitations:

    1. The passenger's first name must contain at least 3 characters.

    2. The passenger's last name must contain at least 3 characters.

    3. The return flight must be at least two days after the departure flight.

  4. Search query results are displayed in ascending price order (lowest price first).

  5. The following flight information is available to the B2E user:

    1. Airline carrier

    2. Flight number

    3. Dates

    4. ETD

    5. ETA

    6. Airport

    7. Available seats

    8. Class

    9. Ticketing date (time limit)

    10. Fare type: P (Published), N (Negotiated)

    11. Total price for all passengers including taxes

  6. Supported Meals:

    1. BBML - Baby Food

    2. CHML - Child Meal

    3. DBML - Diabetic

    4. GFML - Gluten Free

    5. KSML - Kosher

    6. LFML - Low Cholesterol/Fat

    7. LSML - Low Sodium/No Salt

    8. MOML - Muslim Meal

    9. VGML - Vegetarian/Non-Dairy

    10. VLML - Vegetarian/Milk/Eggs

  7. After completing a booking in the system, a PNR is created in Sabre with the following details:

    1. Flights

    2. Passenger details (name, date of birth, telephone number, and e-mail address)

    3. Ticketing date (time limit)

    The PNR also contains the following optional details (if defined in the Sabre configuration):

    1. Special remarks

    2. Special key

    3. Price type

  8. Void tickets: A ticket is void if it is cancelled within 24 hours after being issued, and before it is reported to the BSP. A void ticket has not yet been reported to the BSP, and therefore it can be removed from the system and transaction so that a new ticket can replace it. If the system identifies void tickets in the Sabre PNR:

    1. If a voucher has not yet been issued for tickets that have become Void, the tickets are deleted from the transaction

    2. If a voucher has been issued, the voucher is cancelled, and the tickets are deleted.

    3. A log is added to the docket describing the action as follows: <tkt_no> voided+vch <no>

    4. If flights were added or cancelled in the PNR, the transaction is updated.

    5. If new tickets are issued they are added to the transaction, and if the option for issuing an automatic voucher is selected, a voucher is issued.

    6. This process occurs even if there is no itinerary in the PNR.

  9. Reissue: A new ticket is issued, or the same ticket is reissued with a new number because of a change in the flight, or the classes (this can also occur when it is no longer possible to void a ticket, and it costs less to do a refund. When a ticket is reissued, both tickets are active, and therefore an additional transaction needs to be added to the travel file with the new ticket. If the system identifies reissued tickets in the Sabre PNR:

    1. A new transaction is added to the travel file with the reissued ticket.

    2. The log entry is similar to what is added from files

    3. The transaction price is calculated according to the ticket price quote

    4. If the original ticket does not have legs, but does have an itinerary, the reissued ticket is associated with the legs that do exist in the PNR

  10. Conjunction Tickets: Occasionally a ticket is issued with two consecutive numbers, otherwise known as a Conjunction Ticket. When importing the PNR, the second number is planted in the second leg of the transaction, and is marked as a conjunction ticket. When reissuing a conjuction ticket, a new transaction is created, and the new ticket number replaces the number of the conjunction ticket in the second leg of the transaction.

  11. The following rules apply when changing flight details of a vouchered transaction during a PNR import:

    1. During the PNR import, no details of the transaction can be changed other than the flight times, and the flight status (from WL to OK).

    2. If there are no ticket numbers, and a PNR is imported with ticket numbers, the transaction is updated with the ticket numbers, and the amounts remain unchanged.

    3. If the flight date, or flight number changes, but the ticket number and price remain unchanged, then the transaction is updated with these changes.

  12. When importing a PNR,  the user is  added to the travel file, and then the branch the user is associated with.

  13. Sabre supports one letter and three letter phone types. The following phone types are supported: