Sabre GDS Integration for Tres - Setup and Interface

Skip To:

• Preparing for Interface
• Sabre Setup
• Sabre Interface Control
• Entries Affecting Interfaced bookings
• Generating Invoices

Preparing for Interface

Sabre must be set up to interface to Tres. Agencies that are already interfacing into Trams Back Office (TBO), already have these settings in place.

If your agency isn’t already interfacing to TBO, contact the Sabre support desk to ensure the following steps have been completed.

1. Your agency has been configured for Interface Option 6. Interface Option 6 allows for the creation of interface records that Tres uses to create booking information.
2. Your agency has been assigned a device identifier (LNIATA) for your interface files. Sabre uses the LNIATA to control where the interface files are sent.
3. The Sabre Java Print Manager (SJPM) is installed on your computer and has been configured to create multiple interface files. The SJPM is a program that creates the interface files.
4. Certain options have been set in your agency’s Travel Journal Record (TJR).
5. At least one Sabre user’s EPR has been assigned the keyword MINOPR. This keyword must be present to perform the various DX commands for controlling interface.

Once the Sabre configuration is completed, you will need to install and set up the GDS Upload Utility. GDS Upload Utility is an application that runs in the background on your computer and sends the interface records to the Tres server for processing. We highly recommend installing GDS Upload Utility on the same computer on which the SJPM is installed.

Sabre Setup

Preparing for Interface starts by contacting your Sabre representative. Interface is an option offered by Sabre, and there may be charges incurred. 

Sabre enables interface by activating Interface Option 6 and assigning a line number or address referred to as an LNIATA. This is like the terminal and printer addresses for invoice/itinerary and hardcopy printers. Any branch access and STP sites should be linked via Sabre, and interface options should be discussed with the Sabre support desk. You can view your agency options by typing PE*{pcc}. The {pcc} represents your pseudo city code. The following considerations should be discussed with SABRE.

• Option 6 has been assigned for interface in Sabre 
• A mini-TA has been assigned for interface
• Sabre Printing Module (SJPM) has been installed and configured.
  • SJPM must be configured to create individual interface files with .TXT as the file extension.
  • Once the Sabre Printing Module has been configured. You will need to make note of the folder (directory path) for the interface records. It will be important for configuring the Trams Back Office interface download screen. The default folder is C:\Sabre\Apps\OADP\output. 

Sabre Interface Options: TJR Settings

By default, Sabre agencies use Sabre Interface Option 2, which allows for invoicing and ticketing. To enable interface, your site must be cutover to allow for Sabre Option 6 features. Option 6 includes the of Interface records. Interface options are controlled by Sabre. There are several other TJR options that must be set up for interface:

Interface options are set in your Agency’s TJR. To interface into Tres, the following TJR options must be set:

TJR Setting	Status	Format
BRNCH (Interface Option Level)	6	Must be set by Sabre support
Interface Itinerary	On	Must be set by Sabre support
Interface Voids Allowed	On	W/VOD¥ON
Non-ARC Electronic Ticket Auto Account Line (NIET)	On	W/ETN¥ON
Refund and Discount Accounting Lines (RFD)	On	W/RFD¥ON
Refund/Exchange	On	Must be set by Sabre support
Enhanced Voids	Off	W/EVOID¥OFF
Interface IUR Overlay Credit Card	Yes	W/IURCCMASK¥ON

Assign Beginning Invoice Number

Each Sabre invoice must be assigned an invoice number. To ensure your invoice numbering is properly set up in Sabre Red 360 Workspace, follow these steps:

1. Check the Current Invoice Number
   Enter DV*PTR in the command line. This will display the next invoice number Sabre is set to assign.
   • If a number is already assigned, no further action is needed.
2. Assign a Starting Invoice Number (if needed)
   If no number is assigned, enter DV1 to set "1" as the next invoice number.
   • If you prefer to start with a different number, replace "1" with your desired starting number. For example: DV1234.

Sabre Printing Module (SJPM)

Sabre uses the Sabre Java Printing Module (SJPM) to control devices such as ticket printers, invoice printers, hardcopy printers, and interface records. The Sabre support desk can help you configure the SJPM for your agency.

SJPM Device Settings

Sabre support will help you set up the SJPM. In the SJPM device window, review the following settings:

Printer Settings:

• Output Format: Text
• Print to Single or Multiple File(s): Multiple

Directory Settings:

• Directory Path: This is the folder to which the interface files will be saved. You will need to know this information when setting up GDS Upload Utility.

Multiple:

• Add Supplemental File Ext.: Selected (Checked)
• Supplemental File Extension: txt

Sabre Interface Control

Sabre assigns a terminal line address or LNIATA when interface is first established. Sabre refers to this line address as the MINI-TA DEVICE. You need to know the LNIATA for some of the formats used for interface control. The Sabre Interface Records are held on a Point of Sale (POS) queue by Sabre pending transmission to your office, for up to 10 days.

Transmitted records are only available for re-transmission from the daily work list (DWLIST) until midnight of the original invoice date. A request to the Sabre QP/FSGG queue can allow access to the DWLIST for an extended period. Just request the extension in advance of changes to your interface configuration. Sabre protects the records prior to interface by using an asynchronous protocol for transmission. If Sabre records leave the queue and are not received by the SJPM, it is likely that a file or other device has been configured incorrectly. While rare, it’s important to note that Sabre does not transmit records if a device address is not ready to receive the records. Interface options are controlled by Sabre.

Checking Status of the Interface Queue DX STATUS

This entry allows you to see the status of the Point of Sale or POS queue. Sabre responds with a status of the Interface Queue and the number of messages on the queue. Q2 displays normal interface records. The status is on hold or active.

DX TRANSMIT: Start Transmission of Pending Message

To start transmission of pending interface records, enter the Sabre host command DX TRANSMIT.

This entry requests SABRE begin the transmission of all pending Interface records from the POS queue to Tres. The status on Q2 and Q1 changes from “On hold” to “Active”. If your SJPM is not ready to receive records before initiating transmission, Sabre times out and the POS queues return to “On hold”. Restart the SJPM and try the DX TRANSMIT command again.

DX END and DX HOLD: Stop Transmission of Pending Message

If your SJPM goes offline, Sabre will automatically place the POS Queue back to “On hold” status. Generally, it is not necessary to manually stop the interface transmission.

If you choose to manually stop transmission, enter the command DX END or DX HOLD.

Both commands will stop sending new interface files to the SJPM. The difference between the two is that DX END will transmit all pending records, then place the POS queue back to “On hold” status.

DX HOLD will immediately stop the transmission, and any pending records will remain in the Sabre POS queue.

Once you’re ready to re-initialize transmission, enter the DX TRANSMIT command.

DW: Retransmit Records from the DWLIST

If records are not received by Tres, they can be re-transmitted until midnight of the original invoice date. To re-transmit missing records:

1. Enter the command DWLIST to view all records for your PCC
2. Select which records you wish to re-transmit
   3. To select a single record, enter DW{record number}. For example, to retransmit the invoice on line number three, enter DW3.
   4. To retransmit all available records, enter the command DWALL followed by DWYES to confirm.

DX HISTORY: Check History of Transmission Activity

This entry displays the history of activity to and from the queue. Used by Sabre to audit activity on the queue. If transmission of records fails, Sabre logs a reason code that can be viewed here.

The most common response is TMO NO ACK RCVD, which means Sabre cannot connect with the SJPM. To resolve this problem, ensure the SJPM is running and active on the computer.

If the JSPM is running and displayed in the System Tray (bottom right corner of screen). If the ICON does not appear, contact the Sabre support desk at 1-866-334-7551 for assistance, select Option 2 for Hardware.