Interface Preparation (Sabre)

Before beginning interface, both Trams and your GDS must be configured to share information. The Sabre support team will help with the appropriate settings for Sabre, and our GDS integration specialists at Tres will help with setting up Trams.

Interface preparation checklist

The following is a summarized checklist of the steps required for setting up interface.

For Trams Back Office:

• Review Global Defaults > Settings > Global Defaults
• Add agency ARC/BSP numbers to Global Defaults > Settings > Branches
• Set user permissions for user logins that will be performing interface download and processing.
• Set currency conversion rates in Global Defaults > Settings > Conversion Rates
• Print reference list of Trams Travel Types and Fare Justification Codes
• Review and update client, vendor, and agent profile interface IDs

For Sabre:

• Interface Option 6 enabled
• Sabre TJR options updated
• Interface user has EPR keyword MINOPR
• Install and configure Sabre Java Print Manager (SJPM) and note the interface file path

Contents

• Trams settings
  • Global Defaults > Interface Settings
  • Global Defaults > Tax Related
  • Branches and ARC/BSP numbers
  • User login permission
  • Conversion Rates
  • Travel Types and Fare Justification Codes
  • Interface IDs
• Sabre Settings
  • Sabre Interface Options: TJR Settings
  • Invoice Numbers
  • EPR Keyword MINOPR
  • Sabre Printing Module (SJPM)

Trams settings

There are several options in Trams that control how Trams processes the details from your GDS.

Global Defaults > Interface Settings

How to get here: Open Utilities > Settings > Global Defaults > Interface/Mailmerge.

• Default Area Code: Your agency’s default telephone area code. This is used when an interfaced telephone number has fewer than 10 digits.
• Country Code: Your agency’s telephone country code. For most of North America, this is 1.
• Local Currency Code: Your agency’s local currency code. Use the three-letter ISO code, such as USD, CAD, or AUD. Mailmerge Delimiter and Agency Marketing Identifier do not affect interface.

The remaining interface options control how Trams processes PNR information and are described below.

• Allow Cash/Ck Pymts: This option is disabled by default, which means that GDS bookings issued with either cash or check as form of payment will interface without any client payment information. The Trams user will need to enter the cash and check payments into Trams. When enabled, Trams will add a separate payment to each booking that is interfaced. Recommended setting: Disabled.
• Allow Supplier Pymts: When enabled, Trams will create client payments for each booking paid by the client’s credit card. This option does not affect invoices paid by non-credit card forms of payment. Recommended setting: Enabled.
• Read Multiple Taxes: When enabled, Trams will track the individual amounts for each tax code if the information is provided in the interface record. When disabled, all taxes will interface as a single lump sum. The Sabre TJR option IURMXRECORDS must be enabled for this to work. Recommended setting: Enabled.
• Read Branch ID from I/F ID: This option applies only to Sabre users. When disabled, the client’s interface ID is interfaced as entered. When enabled, the first three digits of the interface ID in the PNR will be used to assign the branch number, and the remaining characters will be used to match the specific client profile. Recommended setting: Disabled.
• Allow Comm Track Hotel/Car: When enabled, car and hotel segments will interface automatically as Comm Track bookings. When disabled, agents will need to manually enter additional information into the PNR to include those bookings. Recommended setting: Enabled.
• Allow Comm Track on Exchanges: When enabled, hotel and car bookings will be included on invoices with refunded or exchanged tickets. When disabled, any hotel and car segments will be ignored. Enabling this option may lead to duplicate hotel and car reservations. Recommended setting: Disabled.
• Allow New Client Profiles: When enabled, the Trams user will be prompted to search Trams for an existing client profile or to create a new profile when Trams cannot find an exact match with the client interface ID entered in the PNR. When disabled, the user will only be able to select an existing client profile. Recommended setting: Enabled.
• Allow New Agent Profiles: When enabled, the Trams user will be prompted to search Trams for an existing agent profile or to create a new profile when Trams cannot find an exact match with the client interface ID the PNR. When disabled, the user will only be able to select an existing agent profile. Recommended setting: Enabled.
• Read Booking Agent: When enabled, Trams will include the booking agent on the booking. When disabled, the booking agent will be ignored. The booking agent is the agent who initially created the PNR. If both this option and Read Ticketing Agent are enabled, both agents will be assigned to the booking, even if it is the same agent. Recommended setting: Enabled.
• Read Ticketing Agent: When enabled, Trams will include the booking agent on the booking. When disabled, the booking agent will be ignored. The ticketing agent is the agent who issued the ticket and invoiced the PNR. If both this option and Read Booking Agent are enabled, both agents will be assigned to the booking, even if it is the same agent. Recommended setting: Disabled.
• Allow Multiple Agents Per Booking: When enabled, Trams will track up to six inside and six outside agents per booking. When disabled, only the first agent will interface. Recommended setting: Enabled.
• Match Vendors Profiles By State/ZIP Code: When enabled and Trams does not find a match on the vendor interface ID, it will also look for vendors with matching state/ZIP code information. Recommended setting: Enabled.
• Default Refund Invoice FOP on Neg Booking: When enabled, Trams will use the same payment information to discount lines as assigned to tickets. When disabled, discount accounting lines are left open. Recommended setting: Enabled.
• Allow Voids:
  • Prompt: The Trams user is prompted to manually void the booking during interface.
  • Always: Voided ARC/BSP bookings will be automatically voided during interface. The void is included in the processing log, but no action is required by the Trams user.
  • Never: No voids are processed during interface. Only a message is included to in the processing log, but the booking must be manually voided in Trams.
    Recommended setting: Prompt or Always.
• Allow Duplicate Ticket Numbers: This option controls how Trams handles duplicate ARC/BSP tickets and other accountable documents. There are two reasons a duplicate ticket number may interface in Trams. The most common cause is that the GDS user generates an additional interface record from a PNR that was already invoiced. Occasionally, ARC/IATA will assign a series of ticket numbers that overlaps with a previous series.
  • Prompt: The Trams user will be prompted each time a duplicate ticket number is interfaced and given the option to accept the duplicate ticket or skip the record.
  • Always: Duplicate tickets will interface. The duplicate ticket will be shown in the interface processing log, but no action is required by the Trams user during interface. This is the best way to handle the situation when ARC/IATA assigns an overlapping series of ticket numbers.
  • Never: Duplicate tickets will be skipped during interface, but any other valid bookings will still be created. If no valid bookings exist in the interface record, the invoice is skipped entirely. The actions are shown in the interface log.
    Recommended setting: Prompt or never.
• Allow Duplicate Confirmation #’s: This option controls how Trams handles confirmation numbers for comm track and supplier bookings, except service fees.
  • Prompt: The Trams user will be prompted each time a duplicate confirmation number is interfaced and given the option to accept the duplicate ticket or skip the record.
  • Always: Supplier and comm track bookings with confirmation numbers already in Trams will interface. The duplicate confirmation number will be shown in the interface processing log, but no action is required by the Trams user during interface.
  • Never: Duplicate confirmation numbers will be skipped during interface, but any other valid bookings will still be created. If no valid bookings exist in the interface record, the invoice is skipped entirely. The actions are shown in the interface log.
    Recommended setting: Prompt.
• Allow Dupe. Fee Confirmation #’s: This option controls how Trams handles all duplicate service fee confirmation numbers.
  • Prompt: The Trams user will be prompted each time a duplicate service fee confirmation number is interfaced and given the option to accept the duplicate ticket or skip the record.
  • Always: Service fee bookings with confirmation numbers already in Trams will interface. The duplicate confirmation number will be shown in the interface processing log, but no action is required by the Trams user during interface.
  • Never: Duplicate confirmation numbers will be skipped during interface, but any other valid bookings will still be created. If no valid bookings exist in the interface record, the invoice is skipped entirely. The actions are shown in the interface log.
    Recommended setting: Prompt.
• Prepend Worldspan Invoice Numbers with: Worldspan invoice numbers are limited to a maximum of five digits, which can lead to duplicate invoices in large Trams databases. If the invoice counter in Worldspan resets, Trams will automatically add the digits entered here to the beginning of the interfaced Worldspan invoice number. For example, if the number “9” is entered, Worldspan invoice number 10001 will become Trams invoice number 910001. This option does not apply to Sabre agencies.
  Recommended Setting: Blank, unless Worldspan invoice counter has been reset.
• Add Sabre CSL Aggregator Code in UDID: For Sabre agencies that participate in Sabre’s hotel aggregator program, the aggregator code can be tracked in a UDID. This makes it easier to report on aggregator bookings. Select the desired UDID to be used for tracking. Recommended Setting: Any UDID that is not being used for another purpose.

Global Defaults > Tax Related

Global Defaults > Tax Related (ARC version)

Global Defaults > Tax Related (BSP version)

How to get here: Open Utilities > Setup > Global Defaults > Tax-Related.

The options in the Tax-Related window apply to all bookings entered in Trams. By default, all taxes are grouped together into one total amount. If you wish to track certain tax codes separately, enter the taxes you would to have broken out next to each tax, for example: XF,AY.

The default commission rate is applied to bookings that do not have a commission specified in the PNR.

Airline OB fees

Certain airline fees are treated as taxes by ARC/BSP, using the tax code “OB”. These amounts interface to Trams along with all other taxes. To break out OB fees from other taxes, assign tax code “OB” to any tax code 1-4. For accurate reporting, use a tax that is not used to track any other taxes.

GST/HST

For agencies that participate in BSP, there are additional options related to GST/HST and QST. For more information about setting up taxes for Canadian agencies, please refer to Trams Back Office for Canadian Agencies.

Branches and ARC/BSP numbers

Add/Modify Branches

Add/Modify ARC (BSP) Numbers

How to get here: Open Utilities > Setup > Branches, then select Add/Modify ARC Numbers.

Every ARC/BSP number that your agency uses must be added to the ARC/BSP numbers table. The remaining fields are optional.

If an ARC/BSP number is assigned to a specific branch, all bookings interfaced with that number will be assigned to the corresponding branch. If the ARC/BSP number is assigned to more than one branch, invoices will be assigned to the lowest branch number. If the ARC/BSP number is not assigned to a specific branch, invoices will be assigned to branch zero.

User login permission

Users that will be performing interface download or processing must have permission to view and run reports with full credit card and bank account numbers.

How to get here: Open Utilities > Setup > User Profile, then select the Permissions tab.

Ensure the two options related to full credit card/bank account numbers are selected (checked):

• View full Credit Card/Bank Account Numbers
• Run Reports/Exports with full Credit Card/Bank Account Numbers and view REC LOC content

Conversion Rates

How to get here: Open Utilities > Setup > Conversion Rates.

Trams uses the default currency code assigned in the Global Defaults for interfaced bookings without a specified currency. If a segment includes both the foreign currency and the local currency equivalent, Trams enters the local currency in the General tab of the booking, and the foreign currency in the Foreign Currency tab. The segment includes only the foreign currency, Trams converts the foreign currency to the local currency using the rates entered here. If the foreign currency is not listed in the currency table, the booking total fare, base fare, and taxes will interface as zero dollars.

We recommend setting up a default conversion rate for commonly booked foreign currencies. Many agencies only update this table occasionally and use the average rate for the recent period.

Travel Types and Fare Justification Codes

Your agency’s travel types and fare justification codes are customizable. Since agents will need to enter this information into Sabre, we recommend printing a list of each set of codes for their references.

To print a list of travel types:

1. Open Utilities > Setup > Travel Types
2. Select Print

To print a list of fare justification codes:

1. Open Utilities > Setup > Fare Codes
2. Select Print

Interface IDs

Interface IDs are the primary link between Sabre records and the Trams profiles in your database. Every client, vendor, and agent profile should be assigned a unique interface ID.

Client Interface IDs (Client ID)

Client IDs can be entered in Sabre as either the Sabre customer number (DK Number) or a coded remark. When entered as a DK number, the client ID prints on Sabre-generated documents can be used for other purposes in Sabre, such as unused ticket reports and PNR finishing. Client IDs entered as PNR remark do not print on invoices are used exclusively for interface to Trams.

Another important distinction is the format in which Sabre transmits this information to Trams. PNR remarks interface exactly as entered in the PNR, while DK numbers may interface slightly differently.

The DK number may be six, seven, or 10 characters based on a setting in the Sabre TJR, but it always interfaces to Trams 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.

There is a global default option to Read Branch ID from I/F ID. If enabled, Trams assigns invoices to the branch number in the first three digits of the expanded DK number, and the profile interface ID as the remaining digits.

Vendor Interface IDs (Vendor Code)

Airlines: Trams uses the two-character GDS code for the airline, for example, “AA” for American Airlines, and “DL” for Delta Air Lines. The pseudo airline code “XD” is used for ARC service fees, and “XB” is used for BSP service fees.

Car companies: Trams uses the two-character code for the rental company, for example, “ZL” for National Car Rental and “ZE” for Hertz.

Hotels: The hotel interface ID transmitted by Sabre depends on whether the hotel is booked using a “Sabre rate” or an aggregator rate. Hotels booked using a Sabre rate (HHL segments) use a combination of the hotel chain code, such as “MC” for Marriott and “HH” for Hilton, followed by the Sabre property ID. An example of an interface ID for HHL segments is MC9448.

Hotels booked using aggregator rates (HHX segments) interface with the hotel’s global property ID, a unique ninedigit number. As a fallback, Trams also reads the telephone number in the segment and will match existing profiles with matching numbers.

In the example above, the hotel chain code, global property ID, and Sabre ID for the hotel are highlighted. When booked using a Sabre rate, the interface ID is MC (the chain code) followed by 54087 (the Sabre ID): MC54087. If the same hotel were booked using an aggregator rate, the interface ID would be 100103838.

Cruise lines, tour companies, and other vendors not in Sabre: The agency can assign any arbitrary code to other vendors. While the interface ID can be up to ten characters, many Sabre agencies assign six-character codes to these auxiliary vendors. This allows agents to enter the vendor ID into Sabre accounting lines without having to use additional descriptor codes.

Agent Interface IDs

Sabre reads the two-character agent sign as the agent interface ID. The agent ID can be overridden by entering a coded remark in the PNR, in which case it can be up to ten characters long. Sabre does not differentiate between agent signs in different PCCs.

Sabre Settings

Preparing for Interface starts by contacting your Sabre representative.

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), replacing (pcc) with your agency’s Sabre 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 need to note the folder (directory path) for the interface records. You’ll need it when configuring the Trams Back Office interface download screen. The default folder is C:\sabre\apps\interface\.

Sabre Interface Options: TJR Settings

By default, Sabre agencies use 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 creation 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 Trams, 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	Never	W/IURCCMASK¥NEVER

Invoice Numbers

Sabre automatically assigns invoice numbers. Because Trams does not allow duplicate invoice numbers within a branch, assign a range of numbers that does not conflict with those being assigned by Trams, ClientBase, or any other GDS your agency uses.

One way to select an invoice number range is to add a digit to the number already being assigned. For example, if your most recent Trams invoice number is six digits long, assign a seven-digit number in Sabre.

Enter the command DV*PTR to view the current invoice number and DV(invoice number) to assign the next Sabre invoice number.

EPR Keyword MINOPR

Every Sabre user who will be performing interface control operations requires the EPR (employee profile record)

keyword MINOPR. To assign the keyword to an EPR:

1. Begin supervisor mode: SI9
2. Begin EPR setup: HB(agent sign)
3. Authorize edit: H/AUTH (your name)
4. Add keyword: H/UAT/A-MINOPR
5. Save EPR update: HE

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. Refer to Sabre Central for more information about SJPM.

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 downloading interface records.
• Multiple:
  • Add Supplemental File Ext.: Selected (Checked) o Supplemental File Extension: txt

Single File Interface

While we recommend using multiple files for interface, the SJPM allows for a single file option. When enabled, Sabre appends new interface records to single file. If single file is enabled, you must select Sabre.net as the CRS during interface download. Scheduled interface download is not available using the single file option.