Skip to main content

Interface for the Back Office (Sabre)

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

Interface for the Back Office (Sabre)

  • Updated

This section explains how to perform manage GDS interface transmission and how to download and process Sabre records into Trams.

The interface process begins when an agent issues tickets or invoices in Sabre. Sabre then sends an interface text file (IUR) to the Sabre Print Module (SJPM), which is installed on the agency’s computer. The print module saves the IUR file to a specific folder on the agency’s computer.

Once the print module has saved the file, it is available for download and interface into Trams.

Contents

Sabre Interface Control

The SJPM must be running and active. The check the status of the SJPM, look for its tray icon in your Windows taskbar. The icon is a printer with a green, red, or yellow square behind it. If the square is green, the SJPM is online. If it is yellow or red, the print module is offline and needs to be reconnected. For more information about re-connecting the SJPM, refer to Sabre Central.

Sabre Interface Transmission

You can monitor start, stop, and monitor transmission from within Sabre. To start and stop transmission, the user’s EPR must be assigned the keyword MINOPR.

Interface transmission status (DX STATUS)

The Sabre command DX STATUS displays details of the current PCC’s POS queue. The first line displays the interface mini-TA address, and the last line, labeled “Q 2”, indicates the status and how many messages are pending transmission.

When Q2 is Active, Sabre will transmit new interface records immediately upon creation. When the status is On Hold, messages are held in Sabre for up to 10 days and are released when transmission is reactivated. Because Sabre only holds pending interface records for 10 days, it’s important to transmit records frequently.

Activate Transmission (DX TRANSMIT)

Enter the Sabre command DX TRANSMIT to begin interface transmission. A response like the DX STATUS will be shown, indicating that transmission has been activated.

Stopping Interface Transmission (DX END and DX HOLD)

It is not necessary to manually end transmission. Leaving transmission active will ensure that your interface records are transmitted from Sabre before the 10-day expiration. But you can manually stop transmission if you choose. There are two formats to stop interface transmission:

  • DX END: Places transmission on hold after any pending messages are transmitted.
  • DX HOLD: Immediately places transmission on hold, keeping pending messages on queue in Sabre.

History of Transmission Activity (DX HISTORY)

If Sabre is unable to connect to the SJPM, it will automatically put transmission on hold. You can check the transmission history by entering the command DX HISTORY. The message TMO NO ACK RCVD indicates that the SJPM is offline and needs to be restarted.

Retransmitting Interface Records (DW)

Interface records can be retransmitted to Trams for 24 hours. Records are retransmitted from the Sabre DWLIST. You can retransmit specific records from the DWLIST or all available records.

Retransmit all available records

To retransmit all available records:

  1. Enter the command SI9 to begin Sabre supervisor mode.
  2. Enter the command DWLIST to display a list of records.
  3. Enter the command DWALL.
  4. Enter the command DWYES to confirm.

Retransmit specific records

  1. Enter the command SI9 to begin Sabre supervisor mode.
  2. Enter the command DWLIST to display a list of records.
  3. Enter the command DW(record number/range):
    • To retransmit a single record, enter DW(record number).
    • To retransmit a series of records, enter DW(starting record)-(ending record).
    • To retransmit specific records, enter DW(record number)/(record number) …
  4. Enter the command DWYES to confirm.

Interface Download

Once the interface records have been transmitted from Sabre, they can be downloaded into Trams. Download is the first step for interface in Trams and places the records into the interface processing list.

How to get here: Open Interface > Download

Download Options

  1. Database Alias: Select your Trams database alias. The default alias for most agencies is “Trams”.
  2. User Name and Password: These will be prefilled with the current user’s login information and usually be left as-is.
    If making changes to any of the options in this window, using a login with "Manager" authorization will save them. Any changes made by other user logins will not be saved.
  3. Download From: Most agencies use the Sabre option, which is used for multiple interface files. If your interface is set to use a single file, select Sabre Net.
  4. Options (Not Required): Enter any desired interface options, including a dash before each option and a space between them.
    • -NG: If there is a credit card number in the automated hotel segment for guarantee purposes, a client remark will automatically get created in the booking 'Guaranteed to: AX37-XXXX-9999' which will then be printed on the invoice re-print associated to the hotel booking. To exclude these remarks, enter “-NG”.
    • -NC: If there is no guarantee credit card number in the automated car and hotel segment, the PNR FOP credit card number will get mapped to the Comm Track CC No field in the expanded fare tab. It will then print Charged to followed a masked version of the number on invoices printed in Trams. To exclude this information, enter -NC.
  5. PNR File Path: The path to the folder holding the Sabre interface (IUR) files. The folder is configured in the Sabre Print Module. Use the button to navigate to the folder. If you are using the single-file interface option, include the filename, which is usually PNRDATA.TXT.

The bottom of the interface download window displays the current version of the Download utility. When a new version is released, you will be prompted to install the upgrade. We recommend installing updates as soon as they are available.

Interface > Download

Select the Download button to begin download. The download log shows the status of each record as it’s imported. You can reprint the download log from the Trams reports menu by opening Reports > Interface > Download/Processing Log.

Unprocessed Interface Records

If there are existing interface records in the Trams pending records queue, you will be prompted to Append, Overwrite, or Cancel. It most circumstances, you will want to choose Append. The Overwrite option will delete any pending interface records and the existing records will not be available for interfacing. To cancel download so you can review the pending records, select Cancel.

Select Print from the download window to print or save a copy of the download log for the current session. You can print the download log by date by opening Reports > Interface > Download/Processing Log.

Interface > Process

Once records have been downloaded into Trams, they are ready to be processed. During processing, interfaced invoices and payments are created in Trams, and certain information in existing bookings may be updated.

How to get here: Open Interface > Process

  1. Pending Records: The details of pending interface records are displayed, including the invoice type, invoice number, date and time received (downloaded), record locator, ARC/BSP number.
  2. ARC/BSP Number: When left blank, all pending records will be processed. If the agency has more than one ARC or BSP number, selecting a specific number will only process those records. Records associated with other ARC/BSP numbers will be ignored and left pending.
  3. Delete: Deletes the selected interface record. Multiple interface records can be selected by holding the CTRL key and clicking the desired records. User may use this to delete duplicate invoices or records that they do not wish to interface.
  4. Print Pending: Prints a summary list of the pending interface records.
  5. Print Invoice List: Prints a detailed list of pending invoices, including individual bookings.
  6. View Source: Displays the raw data associated with the interface record.
  7. Import from File: Used with the Trams IC/Host utility.
  8. Pending Records: The number of records pending.
  9. Process: Processes the records into Trams.
  10. Cancel: Closes the processing window.
  11. Print Log: Prints a log of processed records. The log can be reprinted by clicking Reports > Interface > Download/Processing Log.
  12. Other Options:
    • Automatic: Any new records downloaded while the processing window is open will be automatically processed without needing to click “Process”
    • Print Invoice: Prints a copy of each invoice as it is processed.

Process

Select Process to begin the interface process. As records are processed, details are shown in the processing log. Trams begins processing with the highlighted record and continues through the list.

Interface Exceptions

Most records will interface with any intervention. When Trams is unable to process a record automatically, Trams displays an alter and you will be given the opportunity to resolve the exception. Reasons you may encounter an interface exception include:

When this happens, you’ll be given the following options:

  • Modify: A new window will open allowing you to correct the exception.
  • Ignore: Ignore the record and continue processing the next pending record. The ignored record remains in the processing queue.
  • Ignore All: Ignores the record and continues processing the next pending record. Any subsequent exceptions are also ignored. Ignored records remain in the processing queue.
  • Abort: Ignores the current record and immediate stops processing. All pending record remain in the processing queue.
  • View Source: Opens a window with the raw interface data. This can be used to troubleshoot the exception.

Invalid Invoice Number

This indicates that the GDS did not assign an invoice number, or the assigned invoice number already exists in your Trams database.

If the GDS number is unassigned, it will be displayed as “0”. Select Modify and enter an unused invoice number or enter “0” to have Trams assign the next available invoice number for the branch. You can also select the appropriate branch number when assigning an invoice number.

Trams does not allow duplicate invoice numbers within a single branch. If an interfaced record has a duplicate invoice, we recommend clicking Abort, then querying Trams for the invoice number. If the interface record is a true duplicate, delete the pending record. If the record is not a true duplicate, you can resolve this by assigning the record a new number.

If Sabre is consistently assigning duplicate invoice numbers, you may want to change the range of invoice numbers it’s using. To change the next invoice number that Sabre will assign, the format DV(invoice number).

Invalid ARC/BSP Number

Trams reads the ARC/BSP number in the interface record and attempts to match it to the numbers configured in Utilities > Setup > Branches. If the ARC/BSP number does not exist in the branch setup, you will be selected to select the correct ARC number and branch.

No Match on Interface ID and Creating Records “On-The-Fly”

If Trams is unable to find a match to a Trams profile, the alert will display the interfaced name and interface ID if they are included in the record. The interface ID provided in the display is enclosed in square brackets (“[“ and “]”). If the exception shows “[]”, no interface ID was entered in the record.

Selecting View Source may help to find the correct information.

Select Modify to search for an existing Trams profile to match to the PNR. Depending on your Trams settings, you may also be permitted to create a new profile. When creating new profiles during interface, Trams will pre-fill the profile information with data available in the interface record.

Duplicate Ticket or Confirmation Number

Trams checks for duplicate ticket and confirmation numbers in existing invoices. If your agency has chosen prompt in Trams global defaults, you will be given the option to review the interfaced record and accept the duplicate or to ignore the record. If your agency has chosen always or never, the duplicate is noted in the interface processing log.

Refund and Void

Depending on your Trams global default, refund and voided tickets may be processed automatically, ignored, or you may be prompted to confirm the details of the refund or void. Ignored records are noted in the processing log. If prompted, you are given the option to modify the record and confirm the refund details.

Processing Log

The processing log includes details of each record as it’s processed, including any exceptions. Reviewing this log will help you spot any issues that may need further research.

Selecting Print from the processing window will allow you to print or save a copy of the log for the current session. The download log can be printed by date by opening Reports > Interface > Download/Processing Log.

Processing by ARC/BSP Number

All invoices generated in the primary Sabre PCC and linked branch PCCs are downloaded together. Records received by Trams can be processed by individual ARC/BSP number.

To process all records, regardless of ARC/BSP number, leave the ARC/BSP number dropdown empty. To process records for only a single number, select the appropriate number from the ARC/BSP dropdown. Records from other ARC/BSP numbers will be ignored.

Daily Procedures

The following is our recommended daily checklist for interface download and processing:

  1. Ensure the Sabre Print Module (SJPM) is active.
  2. Download transmitted interface records:
    • Open Interface > Download and select Download.
    • Review the interface download log for any errors or exceptions that may require further research.
    • Select Close to close the interface download window.
  3. Process pending interface records:
  4. Open Interface > Process and select Process.
  5. Review the interface processing log for any errors or exceptions that may require further research.

Scheduling Automated Interface Download and Processing

Both interface download and processing can be scheduled to run automatically. See Schedule Automatic Interface Download and Processing for more information.

Related to

Related articles