Skip to main content

Sabre GDS Integration for Tres - Entries Affecting Interfaced Bookings

www.trestechnologies.com
© Tres Technologies. All Rights Reserved.

Sabre GDS Integration for Tres - Entries Affecting Interfaced Bookings

  • Updated

The following are required entries for interfaced bookings:

Client Interface ID

Tres matches GDS records to Trips using the client’s Interface ID. The interface ID is a unique code assigned to each client profile. This ID can be entered in Sabre using one of the following formats:

  1. Sabre DK Number
  2. Interface Remark

1. DK Number

  • Format: DK{Interface ID}
    • Examples: 
      DK5551234567
      DK010030
  • The DK number may be six, seven, or 10 characters based on a setting in the Sabre TJR, but it always interfaces to Tres as ten characters. Examples:
    • Six-character Customer Number input as 123456 will transmit as 0120003456
    • Seven-character Customer Number input as 1234567 will transmit as 0120034567
    • Ten-character Customer Number input as 1234567890 will transmit as 1234567890
  • Because of the way Sabre processes six- and seven-digit DK numbers, we recommend using 10-digit client IDs if your agency chooses to use the DK number field.
  • The Interface ID in the Tres client profile must match the padded value (0010000030).

2. Invoice Remark

  • Format: 5.S*AN{Interface ID}
    • Examples: 5.S*AN5551234567 or 5.S*AN010030
  • Sabre sends the Interface ID exactly as entered (no padding).
    • Example: 5.S*AN010030 → sent to Tres as 010030
  • The Interface ID in the Tres client profile must match this exact value (010030).

If Auto Create Client Profiles is enabled in Agency Settings:

  • An address must be included in the GDS PNR (Passenger Name Record).
  • The first line of the billing address is used as the default client profile name.
  • If a billing address is not included in the PNR, Tres will not automatically create a new client profile.
  • Customer name and address details will interface to Tres for new client creation.

Example:

5/GEORGE BENSON
5/111 MOODY ROAD
5/HAPPYVILLE, GA 44039

Additional Entries:

Skip to:

Generating Invoices

Tres imports new reservations from Sabre invoices, so an invoice must be generated for each PNR at least once.

Depending upon your agency’s TJR configuration, invoices may be automatically generated after issuing an airline ticket using the W¥ format. Invoices may also be generated using the DIN format.

ARC/BSP Tickets and Service Fees

Tickets and ARC/BSP service fees issued electronically in Sabre will have all the necessary information for importing into Tres. Agents only need to ensure that an invoice is generated.

Non-ARC/BSP Air Bookings

For non-ARC/BSP Air Reservations, agents will need to enter an OTH segment and manual accounting line. For specific instructions on how to create an OTH segment and supplier accounting line, see Format Finder on Sabre Central.

Step 1: Add passive air segments

Tres reads GK and YK segments. Passive airline segments must exist to interface flight-level details.

Step 2: Enter an OTH segment:

0OTHAAGK{number of travelers}{city code}{date}-{description}

Example:

0OTHAAGK1LAX22SEP-SOUTHWEST RESERVATION ABC123

Step 3: Enter the accounting line:

ACOTH{segment number}/SUPPLY/{Sabre {commission}/{base fare}/{total taxes}/{applies to}/{form of payment} {traveler}/1-*VC{supplier interface ID}*CF(ticket or confirmation number)*SG {optional segment numbers}

Example (include all segment details in reservation)

ACOTH4/SUPPLY/INV/0/245.00/45.35/ONE/CCVI4444333322221111 1.1SMITH JOHN/1-*VCWN*CF1234567890*SG

Example (include specific segment details in reservation)

ACOTH4/SUPPLY/INV/0/245.00/45.35/ONE/CCVI4444333322221111 1.1SMITH JOHN/1-*VCWN*CF1234567890*SG 01 03

Non-ARC/BSP Service Fees

PNRs must include an OTH segment and associated accounting line for each service fee. Refer to AC*SUP to details for adding Sabre supplier accounting lines.

Note: 

Before invoicing non-ARC/BSP service fees, create a Tres service fee supplier with interface ID SVCFEE.

Step 1: Add OTH Segment for service fee

0OTHAAGK(number of travelers)(city code)(date)-(description)

Example: 

0OTHAAGK1DTW22SEP-SERVICE FEE

Step 2: Add Accounting Line

ACOTH(OTH segment number)/SVCFEE/FEE/(commission)/(base fare)/(amount)/ALL/(form of payment)/1-*TCSERVICEFEE*PN(last) (first)

Example: 

ACOTH1/SVCFEE/FEE/50.00/50.00/0/ALL/CK/1-*TCSERVICEFEE*PNSMITH JOHN

To charge more than one service, add a separate accounting line for each fee.

Non-Air Bookings

Tres can import the following auxiliary segments:

  • Car (CAR)
  • Hotel (HHL, HHT)
  • Tour (TOR)
  • Cruise (SEA)
  • Insurance (INS)
  • Other (OTH)

Apart from automated car (CAR) and hotel (HHL/HHT) segments, a manual accounting line must be associated with the segment and include certain other interface information using descriptor codes.

Only limited information interfaces for non-GDS bookings. We highly recommend entering non-GDS reservations directly in Tres to capture expanded reservation information.

The basic format for entering a supplier accounting line is below. For detailed instructions, see Format Finder on Sabre Central or AC*HELP.

AC{segment type}{segment number}/{supplier interface ID}/{invoice descriptor}/{commission}/{base fare}/{total taxes}/{applies to}/{form of payment} {traveler}/1-{additional descriptor codes}

Example

ACOTH2/SUPPLY/FPT/P10/100.00/25.00/ALL/CK/1-TCINSURANCE*VCTVLGRD*SD01JUN*ED08JUN

Descriptor codes

The following is a list of descriptor codes that can be appended to automatically generated accounting information.

Code Purpose Format Example
TC Travel Category *TC{category} *TCCRUISE
VC Supplier Interface ID *VC{vendor interface id} *VCRCCL
CF Confirmation Number *CF{confirmation number} *CF123456ABC
SD Start Date *SD{date} *SD22SEP
ED End Date *ED{date} *ED27SEP
SG Capture Segment Details (All Air Segments) *SG *SG
SG Capture Segment Details (Specific Segments) *SG {seg number} {seg number} … *SG 01 03 05

 

The following  travel categories are valid when using the TC descriptor code:

  • Air
  • Car
  • Cruise
  • Excursion
  • Hotel
  • Insurance
  • Miscellaneous
  • Rail
  • Service Fee
  • Tour
  • Transfer

Descriptor Codes can be appended to the end of an accounting line or entered as a PNR remark.

To append to an accounting line, enter the format -*{descriptor code}{data}. Multiple descriptor codes can be linked together, separated by an asterisk. There is a limit to the number of characters that can be appended to an accounting line, so it may be necessary to enter additional information in PNR remarks. To do this, enter an MS remark line can be used. MS remarks can be linked to segments or to accounting lines.

To link an MS line to a segment, use the format 5.S*MS{segment number}*{descriptor code}{data}. For an accounting line, use the format 5.S*MS10{accounting line number}*{descriptor code}{data}.

An accounting line with descriptor codes:

ACOTH1/SUPPLY/10P/1200.00/250.00/ALL/CCVI4444333322221111/1-*VCWN*CF123456*SD22SEP*ED27SEP

An MS line referencing segment number 1:

5.S*MS1*VCRCCL*CF123456*TCCRUISE*SD22SEP*ED28SEP

An MS line reference accounting line number 1:

5.S*MS101*VCHY1234*TCTOUR

Hotel- and Car-Only PNRs

For hotel and car bookings included on invoices, Tres will automatically import automated hotel and car reservations.

To generate an invoice in Sabre, there must be at least one accounting line. To generate an invoice for a PNR with only automated car/hotel reservations, a “dummy” accounting line can be entered. Tres will ignore the details of the accounting line and import the segment details as the reservation.

Only the segment type and segment number must be entered based on the segment. If a PNR includes more than one hotel or car booking, only one accounting line needs to be added.

AC{segment type}{segment number}/SUPPLY/INV/0/0/0/ALL/CK/1

Example:

ACHHL1/SUPPLY/INV/0/0/0/ALL/CK/1

Tags

Trip and reservation tags are interfaced with the descriptor code UD.

UD entries associated with a specific traveler interface as Reservation Tags. UD entries that are not associated with a specific reservation or traveler interface as Trip Tags.

To enter tag details:

*UD(tag name) (information)

Example:

*UDMYTAGNAME TAGINFORMATION

Important:

There is a mandatory space between the tag name and information to be recorded in the tag.

Trip Tags

Trip tags are entered as PNR remarks with the format 5.S*UD(tagname) (information)

Format:

5.S*UD(tagname) (information)

Example:

5.S*UDTAGNAME INFORMATION

Reservation Tags

Reservation tags can be interfaced by associating the tag to a specific non-air segment or ticket accounting line.

Non-Air (auxiliary segments)

For non-air segments, refer to the PNR segment number:

5.S*MS(segment number)*UD(tag name) (information)

Example:

5.S*MS2*UDTAGNAME INFORMATION
Air Reservations

For airline tickets, refer to the the ticket account line:

5.S*MS10(accounting line number)*(tag name) (information)

Example:

5.S*MS101*TAGNAME INFORMATION

Itinerary Update (HU)

Information Updated Using Itinerary Updates

Changes to existing hotel and car reservations and flight schedules can be interfaced to Tres using Itinerary Update. To update a Tres trip:

  1. Enter the PNR remark: 5.S*HU
  2. Generate an itinerary using DIT

During interface, Tres looks for invoices matching the itinerary PNR record locator. When it finds a match, it updates the following:

  • Hotel and car reservations:
    • Any existing hotel and car reservations are voided.
    • Hotel and car reservations in the itinerary are added to the most recent trip with the PNR record locator.
    • Existing car and hotel reservations with a start date prior to itinerary date are ignored. This retains any past date reservations active in Tres, even if they’ve fallen out of the itinerary. Past date reservations remain in the original trip.
  • Flight schedules
    • Tres updates flight schedules on all bookings related to the PNR record locator.
    • Only matching flight segments based on departure city are updated. New segments are not added, and existing cities are not changed.
    • Updated information includes departure and arrival dates and times, and flight numbers.


 

Related articles