Sabre Interface Guide
Sabre Interface Guide
Preparation Guide
Interface Overview Download & Processing
Overview of Interface
The interface process between The Host Reservation System, or GDS, and TRAMS, is a means by which
invoice and ticketing data entered in the Passenger Name Record (PNR) is automatically transmitted to the
back office system. The interface commands used to control the interface between the GDS and TRAMS
are similar to the entries already used in your office to control the transmission of messages to your various
printers (e.g., ticket, invoice/itinerary, boarding pass and hardcopy).
Once the interface option is enabled by the GDS, an interface record or image is created every time a sales
agent drives a ticket or an invoice. Specific accounting, client, vendor and booking information from the
PNR is downloaded to TRAMS Back Office and becomes available for accounting, tracking and reporting
needs.
The interface record created by driving the invoice is stored by the Host GDS on an Interface Queue, much
like your ticketing queue. Instead of retrieving the data on queue back to your workstation to update, or to
your printer to print, the record is downloaded to TRAMS as a file for TRAMS to read.
6/2/09 1
Interface. Interface is an interactive process that requires coordination between the Host Reservation
System, the Windows Interface program and TRAMS. Let's go over some terminology that we use at
TRAMS for the different parts of the Interface procedures.
Download involves TRAMS retrieving the interface records. In TRAMS Back Office this can be directly
from the interface cable or a file. As the records are downloaded, TRAMS reformats the records and places
them in a separate file for processing.
When records are retrieved from the source directory, the files are deleted and the directory is emptied. It's
important when reading across a network that full file permissions are enabled for the client workstation
downloading the records.
Process is a procedure that merges the Interface records into the TRAMS database. Each invoice is
tracked by Client, Vendor and Sales agent. Bookings within an invoice would all have the same client, but
may have different vendors or sales agents. The process procedure matches each invoice item to the
proper client, vendor and sales agent for reporting and accounting purposes. The procedure also generates
any error messages related to the new data being received, and allows operator intervention for undefined
profiles. You do not need to create Profiles prior to interface. TRAMS allows you to create new profiles
during the Interface Process.
Capturing Interface Records involves either the images to file option configured by your GDS Vendor, or
use of the Windows Interface Utility if cabled. If interface has been configured by your host in this manner,
then be sure to ask them how to start, stop and review the utility or print server software they use to capture
the records. It's also important to know the EXACT path and directory or file name for TRAMS to download
the files.
Host Print Server, Pro Printer and Host Print Modules, are utility programs used by your GDS vendor to
enable the Host system to communicate with your Host printers, including the interface device. If configured
for cable, there are protocol setups to control a serial port. If configured to capture to file, there are formats
for the file as well as a location or path and file name to the interface records.
Network Access and File sharing is a feature of your local hardware network. This option must be enabled
in order for TRAMS to download records that are captured to a workstation on the network, versus Interface
Download and Process records captured to the local hard drive where the download is handled. For our
examples we'll assume the records are captured to the SAME workstation and hard drive where the TRAMS
download is handled.
Windows Interface Utility or TRAMS Interface Utility is the program that captures interface records via
a cable. The program is configured to match the serial port communication protocol configured at the GDS
controller. The program may launch at startup or can be controlled manually.
Images to File
If your GDS Vendor has configured interface to file, then capturing records to a file has already been set up
for you. It's still important to know the EXACT path and directory or file name for TRAMS to download the
files. Please check directly with your GDS Vendor for the location of the file, as well as the procedures for
troubleshooting. Standard settings are explained in the specific GDS section of the TRAMS Interface
Guides. Check your interface queue to verify that records are leaving the Host and available in your local
interface file. Go to a GDS workstation and start the transmission of records.
2 6/2/09
default at C:\Program Files\Trams\Tramswin\winint32.exe .
Launch the TBO Interface Utility and select Configure to setup the SAME serial port protocol used at the
GDS controller. You'll need to create a spool folder or two for the records to be captured to. The Alt
Destination Directory is used as an archive folder and acts like a mirror of the original Destination Directory.
Remember to add cleaning the Alt Destination Directory to your monthly maintenance schedule as the
records will accumulate until manually deleted.
Select OK to save. To create multiple settings, select New on the TBO Interface Utility and configure each
GDS that uses an interface cable for interface.
Start the Windows Interface Program by clicking Start. Verify that the status moves to Waiting. Your own
GDS should already be configured and shown as the GDS. The example here has been configured for
SABRE and Amadeus. Go to the GDS workstation and start the transmission of records.
6/2/09 3
Step 2: Select the correct database Alias - the default is TRAMS. The database Alias should NEVER be
blank. Refer to you specific GDS section of the Interface Guide for specifics about the screen options listed
here. Select the appropriate GDS. You can scroll through a list of reservation systems with the down arrow.
Note: Sabre and Worldspan have 2 options for GDS field. Check the folder for the file structure captured
by the GDS. If multiple records exist, one per transaction, use Sabre or Worldspan as appropriate. If a
single logair.dat or pnrdata.txt file exist, use Sabre Net or Worldspan Images to Disk as appropriate.
Note: Any agency having a conflict with the Client Remarks field of a booking being interfaced to a UDID
field, can ignore UDID formats in the Client Remarks field of a booking by entering -NU in the Option field
on the Download Screen.
Note for Worldspan Agencies: There is a -D option to the Interface Download screen to make the dash
following the 5SA , 5OA, 5FJ, 5LF, and 5FF entries in Worldspan optional. If you do not want to specifically
identify an SA or OA entry as agent-related, then enter -D in the Options Field on the screen and the dash
(-) after the SA and OA entry will not be required. There is a chance, based on the entry made if no dash
(-) is present, that the name SANDY could be read as "SA", an override of the Original Sales Agent.
Note to Apollo Agencies: To ignore email updates in Apollo interface, enter -NE (No Email).
Step 3: Click the PNR File Path button to locate the directory where the interface files reside. If you used
the default settings when installing TRAMS, the path should read:
C:\Spool
If records are captured by your GDS vendor, or to a different workstation, then the PNR File Path may look
considerably different. (Refer to the GDS section of this interface guide for more information about settings
specific to your GDS platform.)
Note: Changes to the PNR File Path on the Interface/Download screen are now only saved if the user logs
in as SYSDBA. A non-SYSDBA user can change the path when logged in, but when closing the
Interface/Download screen or logging out of TBO, those changes are not saved. All changes to the GDS
PNR File Path can only be done by the systems SYSDBA User.
Note: Do not check Process Res.txt or Lanyon Format. Wait for New Records is used by high volume
agencies to enable a 'real-time' interface. The download screen can be left open to read new messages
from the file path as soon as they are created. An alternative method for the real time interface is a manual
download which is initiated with a download command in DOS (command below). This method would best
serve large agencies that have automated backup everyday and interface from the server. Create a
shortcut in the startup folder (Start|Programs|Startup). Check with your IT specialist if you are not familiar
with adding to the Startup folder.
4 6/2/09
Enter from the C Prompt (C:\)
download -username sysdba -password ****** -alias trams -auto
You may receive the warning "Unprocessed Interface Records Exist". This means you have interface
records from a previous download session that have not been processed into TBO. If this is your first
Interface Download and Process time interfacing, these may have been test records generated by the GDS
host or support desk.
TRAMS receives all records from the Destination directory and responds with a Record count of Received
and Verified. There may be a difference between the number of records received and verified. Usually this
is attributed to invalid invoices or invoices that do not contain accountable segments.
Interface Reports
Step 4: Run Interface reports to use when reconciling invoices or investigating the download session. We
would advise this on every session until you are comfortable with the TBO interface and front office formats.
The reports are an excellent training tool for both front and back office staff.
6/2/09 5
First run the Invoice List. From the TBO main menu, select Reports|Interface|Invoice List. (A Print
Invoice List button is also located to the Interface Processing Screen so that the Invoice List can be printed
prior to processing.) The Invoice List shows the valid invoice data received by TBO during the download
process. The report shows how TBO interpreted the data entered in the PNR. Remember, how data is
entered and invoices are driven, is directly related to how TBO interprets the PNR. The invoices are not yet
available in the TBO database. This is a report of the invoices downloaded in to TRAMS during this session.
Select Print Log from the report menu bar to print this report.
6 6/2/09
reads and logs the records to the correct client, agent and vendor, as it creates a TBO invoice for accounting
and reporting.
• Delete Record allows you to delete an interface record you have selected.
• Print Pending allows you to print the unprocessed record list as shown in the display.
• Print Invoice List prints out the invoice list prior to processing without going to Reports|Inter-
face|Invoice List. (When you have a new or empty database, it's easier to work through each inter-
faced record with access to your invoice and ticket hard copies.)
• View Source enables you to view the native Interface record sent by the GDS. You are better able to
make decisions on what to do with a specific record that is generating the error prompt.
• Import from File option is used for importing data from other back office systems, website captured
data, when converting to TRAMS Back Office, or can be used to import records for a Host/IC setup.
• Print Log prints the Processing Error Log
• Automatic allows TBO to process all records without stopping for errors. Records with errors remain
unprocessed and errors are reported on the Processing Error Log.
• Print Invoice prints a TBO invoice of each processed record.
Note: TRAMS recommends that the back office operator have access to the invoice, tickets and cash
receipts for proper accountability, and to maintain the integrity of the TBO. Go to
Reports|Interface|Processing Error Log to review reported processing errors.
Client Profiles
The reservation system has a client account number format that TBO reads as interface ID. The same client
number that you print on the invoice or ticket can interface to TBO as the account number. (See the GDS
specific guide for more information.) Each Interface ID must be unique to a single billing entity. A House
Account may be created to track "walk-in" clients, but you won't be capturing valuable marketing
information. TBO recommends a separate profile for every billing entity. While profiles serve as client
ledger cards, they also serve as reporting units and your client mailing lists. Profiles don't need to be
created in TBO prior to the first interface, but spend some extra processing time as you build your
database. If you get No Match on Client Interface ID during processing of new clients, TBO builds the profile
for each new client as you work through processing the invoice.
If you've converted data from another back office system, then it's important to know the procedures
required to restore the converted data to TBO. You may need to put off your first interface session until after
the Interface Download & Process converted data has been restored to create the TBO database.
6/2/09 7
No Match On Client ID
You receive No Match On Client ID prompt when TBO does not find an identical Client Interface ID to the
alphanumeric code that appears between the brackets [xxxxxxxxxx]. This occurs for various reasons. If
there is no code within the brackets, [] TRAMS did not detect a customer number in the Interface record.
For inactive Profiles a Warning Message appears: Matching xxxxx Profile is Marked Inactive - Continue?
Select OK to process the invoice to the inactive profile, and later, update the profile to active status. If
Cancel is selected, a prompt allows the operator to Modify by selecting a different Profile or create a new
Profile.
This screen shows an ID [1234567890] in brackets next to the name. This is the Customer ID the agent
entered in the PNR. TBO did not find an exact match. Select Modify to search for the client by Name.
Select Modify
By selecting Modify, TRAMS continues processing the Interface record, prompting you for input at each step
of the procedure. The client type and name are the only fields available to modify. TBO defaults to Leisure.
If you need to modify the Client Type, click the drop-down key to see your choices. Click Corporate in the
Client Type field. By selecting Corporate without modifying the Client Name, you see how TBO interprets
the Client Name differently. This is not an optional default. If the client's name or spelling is in question,
enter a few letters of the client's last name for a broader search. Next click the Client Name and move to
the Profile query screen. From there, search for the correct profile.
8 6/2/09
No Matching Profiles Found During the Client Name Search
Click Select to choose a name from the list and save. You are returned to the Interface processing screen
to continue processing the rest of the record (s). If the correct name is not on the list, click Reset. Try the
search with just a few letters of the name. Perhaps there is a misspelling?
Note: Run a list of clients and vendors often as your mailing list grows. It is easy to create a duplicate profile
as you and your staff adjusts to the disciplines of interface. Go to Reports|Client|Lists and Labels. You
can also use the Processing Error Log to update any existing Profiles with incorrect or missing Interface
ID's. When you return to Process the Interface records, watch the invoices process without you.
6/2/09 9
Invoice Notes
-- During interface processing for a void record, we added the ability for an invoice to automatically show as
a voided invoice without user intervention if all other bookings in the invoice are already voided. You are
prompted with a Confirm Void Invoice prompt screen. For a single booking invoice containing an air ticket,
nothing more need be done and the invoice is automatically voided. For an invoice containing multiple
bookings, those booking would have had to been manually voided prior to the start of interface processing,
for the invoice to be automatically voided.
Processing of the void record must be the last non-voided booking in the invoice, for the invoice to void
automatically without having to re-query the invoice after processing and manually voiding. To implement
this feature, check that Utilities|Setup|Global Defaults/ Interface/Mailmerge Prompt Tab has Allow
Voids set to Prompt. Allow Voids = PROMPT.
-- During interface processing, single payments are now created for each booking in the PNR invoice being
processed even if the CC No. is the same. This allows for easier voiding of tickets during processing when
each ticket has its own payment attached. Also multiple tickets contained in a single invoice are listed
separately on a customer's credit card statement. So an invoice with two $500 tickets in it, $1000 total
invoice amount, is shown on the credit card statement as one item with ticket number for the first $500 ticket,
and as a second item with ticket number for the second $500 ticket.
Vendor Profiles
ARC/BSP vendors, plus car and hotel vendors, are booked directly through the reservation system have an
industry standard ID assigned through the reservation system. As you process these transactions in TBO,
allow TRAMS to create the vendor profile. You have options available to group several vendors together
through the Vendor profile, or the invoice group field. (See the Profile section in the manual for a full
description of field options.) TBO recommends tracking these vendors by property. ARC/BSP vendor
profiles build by TBO include the airline code automatically. Include both the Interface ID and the airline
code when building these vendors manually.
TRAMS maintains a table of ARC/BSP vendors, complete with address information. This table is used to
create the ARC/BSP profile the first time the vendor is sold. Non-ARC/BSP vendors are also identified in
TRAMS by Interface ID, but there is no industry standard at this time. The GDS may have restrictions on
how these codes are entered within the booking or accounting line. (See the GDS section of this guide for
more information.) It is important to coordinate with the front office staff before deciding on how these
vendors should be identified.
Unlike Client Profiles, TBO searches for the Interface ID first and then the Vendor phone number and thirdly,
the Vendor name for an exact match. Due to the flexibility allowed in the building of PNRs, it is important
to establish standards used for your office.
Note: TBO matches Vendor Profiles by phone number when the Vendor name and/or Interface ID do not
match during interface processing, because the Vendor name and/or Interface ID has changed but the
phone number hasn't. A message is added to the Error Processing Log during interface processing when
a Vendor Profile has been matched by phone number.
When the name and the Interface ID changes, it's usually because a hotel property changes chains, and
the name and ID would be changed but not the phone or address. Users need to be aware of the change
so they can decide if they want to change the name and ID of the existing profile or create a new profile for
the property.
Note: -- TRAMS matches Non-ARC/BSP airline bookings to any vendor profile with a matching interface
ID. So a ticket sold on United Airlines, but not processed through ARC/BSP can be added to a single United
Airlines vendor Profile if the Interface ID matches.
10 6/2/09
No Match On Vendor Name or ID
You receive a No Match on Vendor Name or ID prompt when TBO cannot find a profile for this vendor by
Interface ID, phone number or name.
This screen shows an automated Vendor code received by the GDS at confirmation. If nothing is entered
between the [brackets], the booking may have been entered as a passive segment without a vendor code.
If there is an id between the brackets, but no name, the agent may not have entered a vendor name, just
the code. Select Modify and continue.
Select Modify
The system now, by default, only shows matching vendors based on Name, State and Zip. You can
manually uncheck either or both to see matches just on name. The check boxes are enabled if the
corresponding address field is populated in the Vendor Profile that is being processed from the GDS PNR.
If there is no State or Zip Code in the record being processed then those options are dimmed and the match
is on Name only.
Vendor Name
button
When the database has multiple vendors with the same name such as "Southwest" and no location
identification in the name, the match can be based on the Name and a part of the address. This should
alleviate the problem of common vendor names being picked by name only and putting the booking under
the incorrect vendor profile. TBO searches for the exact spelling of the Vendor Name. If the spelling is
questionable, use only the first few letters of the name to broaden the search. Click OK to begin the search.
TBO may want to attach to an existing profile with a similar name when you click OK. To prevent that, click
the New button to go straight to a new Vendor Profile screen.
6/2/09 11
No matching Profiles Found during the Vendor Name Search
The information from the Interface record moves to the new Vendor Profile screen. TBO does a good job
at capturing address and phone details from automated Car and Hotel Vendors. Passive segments may
require editing. The TBO operator would want to modify this record and assign an interface ID unique to
this hotel. Any future passive hotels with using this same Interface ID will also interface to that profile
automatically. (Refer to the Front Office formats used to account for the vendor transaction, to
ensure proper translation by TBO.) Notice the Interface ID is entered automatically. The next time this
property is booked using the same Interface ID, TBO will not require your intervention. Using the mouse,
click OK to save the profile.
Alternate Interface ID
Some agencies interface from multiple GDS systems. You can add an alternate interface ID to a vendor
profile by selecting the Marketing Tab. By adding an alternate interface ID, TBO finds a match on either of
the Interface ID's attached to the profile.
Query Option
The Query option allows you to query Vendor profiles for a match. A query of Vendor profiles is also initiated
by changing the Vendor Name on this query screen or from the Modify screen. Click Query to begin.
Because of the spelling of the Vendor name, this sample shows [No Matching Profiles Found.] If the query
is successful, highlight the Vendor and click with the mouse. If the query is too narrow or not successful,
click Reset to begin another search.
12 6/2/09
Salesagent Profiles
TRAMS Back Office receives the original booking agent from the Interface Record and captures the agent
as the primary or inside agent on the invoice. The Agent ID as it is translated from the reservation system
must match the Agent Interface ID in TBO. This ID is often referred to as the "agent sine" and is defined in
the agencies GDS profile. You may want to review these agent sines before beginning interface. TBO
reads alphanumeric sines. Non-booking agents that are tracked on an invoice can have an Interface ID
unrelated to the automatic agent id used to designate the booking agent. (See the GDS section of the
addendum for additional tracking options.) TBO allows up to 9 agents on a single booking. These are used
to track inside and outside agents, promotions and commission splits.
No Match On Agent ID
You receive a No Match On Agent ID prompt when TBO has no record of this agent in a sales agent profile.
The Agent ID that TRAMS captured from the Interface record appears between the brackets. If you don't
see an agent ID, TRAMS did not detect an agent in the record. This sometimes occurs when records are
retrieved from another agency or when bookings were created by the Airline Reservations Center and are
taken over by the agency. Click Modify to search by a different ID or to create a new Sales Agent profile.
TRAMS Back Office has no match on the Interface ID of the Agent displayed. This is probably a new agent
with GDS agent sine of TG. When you select Modify, you are prompted to search for the agent by name.
Even though the Agent ID is displayed, you want to enter the agent name to search for the agent.
If you click the Agent ID button, you can query for agents. If you click the down arrow in the window, you
are given similar names of agents. By default, TBO assumes the agent name and agent ID are the same.
If your profiles use first names for agent names, or other criteria, you may want to add the first letter of the
agent name and click the down arrow to find an existing agent.
6/2/09 13
Search for Agent by Name
Processing Errors
TBO accepts only valid invoices through the Interface Download (with a few exceptions). Invoices without
valid segment information, Itineraries, Voids and Full Invoice refunds are rejected during the download
procedure. Valid invoices with missing or duplicate information is available for modification in the Process
procedure.
14 6/2/09
Invalid ARC Number
This error means this ARC/BSP number is not setup in the Branch Utilities. From the main menu, go to
Utilities|Setup|Branches. Click the Add/Modify ARC/BSP button, and add the missing ARC/BSP number.
TRAMS Back Office does not allow duplicate invoice numbers within the same branch. You receive a
Duplicate Invoice Number prompt for various reasons. TRAMS does not allow duplicate invoice numbers.
1. The invoice may have been manually entered.
2. The invoice number was previously used in error.
3. The invoice was previously downloaded and resubmitted.
You have several options.
1. First, select View Source and note the details of the invoice such as passenger names and travel dates.
Then select Abort and go to the Invoice|Query tab and search for the invoice number. If the record to be
processed is a true duplicate invoice, and you do not want to process the record, it can be deleted during
the next download.
2) Select Ignore to move to the next record. The Ignore and Ignore All option does not remove the record(s)
from the process log. The record remains and is reported on the Processing Log.
3) Modify proceeds with the processing of this record and allows you to enter a new Invoice number.
6/2/09 15
An Select Invoice Number prompt appears.
4) Enter the Invoice Number. By deleting the number in the Invoice No field, and clicking OK, TBO
automatically assigns the next invoice number in the system. You also have the option to keep the same
invoice number and capture the record to a different branch.
16 6/2/09
manually.
Unable to Void Ticket when the form of payment isn't a CC is another void type that needs intervention when
the Global defaults is set to Prompt.
Select Modify to edit the Sale Invoice that contains the tickets to be voided.
6/2/09 17
Unprocessed Interface Records Exist.
If records were ignored during processing, they have not been removed from the Processing Log. They
remain available until the next time you Download. They can be kept or deleted from this screen. If you
choose Append, you are adding new records to the existing records in the processing log. If you choose
Overwrite, you are replacing (deleting) existing records in the processing log with new records. You can
choose Cancel to check the Interface|Process Log to check before continuing with the new download.
18 6/2/09
Files|TRAMS|tramswin|download.exe (or where your download.exe is located).
3. Next select how often you want the download to run by selecting the following: Start Time, When task
is performed and Start Day.
4. Enter the login for your computer (use the password entered when logging into your PC or to the network
in your office, and make sure your password is correct and leave blank if there is no password). Be sure to
check in the box next to Open Advanced Properties for this task when you click Finish. A Task Tab
window opens for TRAMS Back Office.
6/2/09 19
5. Ensure the correct information is entered (see below) in both the RUN: and START IN: fields.
20 6/2/09
Additional TRAMS Interface Download command line EXAMPLES which can be entered in the
Scheduler Task screen:
"C:\Program Files\Trams\Tramswin\download.exe -username MIEKE -password mieke -alias TRAMS45
-CRS 2 -path c:\sabre2\spool -auto"
"C:\Program Files\Trams\Tramswin\download.exe -username JUDITH -password authorized -alias TRAMS
-CRS 5 -path c:\wspan\tairs –auto
** auto download from file works only with folders containing individual records (multiple files)
Start In: This area is defaulted to the .exe file you browsed to in Step 2. Make sure it is correct.
6) Select the Schedule Tab|Advanced:
6/2/09 21
Preparing for Interface
Preparing for Interface starts by contacting your SABRE representative. Interface is an option offered by
SABRE, and there may be charges incurred. Trams does not charge for interface options. SABRE enables
interface options by assigning a line number or address referred to as a LNIATA. This is similar to the
terminal and printer addresses in your main office. Any branch access and STP sites should be linked via
SABRE, and Interface options should be discussed with the SABRE customer service center. 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.
Interface Option 6
Professional SABRE agencies use SABRE option 2 which allows for invoicing and ticketing. To enable
interface, your site must be cutover to allow for SABRE option 6 features, which include the creation and
format of Interface records. (Interface options are controlled by SABRE.)
Interface options can be flagged in your Agency profile referred to as the TJR. These options include flags
to include Refunds and Exchanges, E-tickets, invoice only or invoice and itineraries for hotel updates as
well as manual fare by leg information for segments not auto-priced by SABRE.
22 6/2/09
SABRE Printing Module
In most SABRE platforms, SABRE uses the Sabre Printing Module to control HOST devices such as ticket
printers, invoice printers, hardcopy printers or interface records. A SABRE field services technician or
SABRE hardware support desk can help you configure the utility for interface files or cable options.
Images to File
SABRE Net locations require interface configured to a file, while other platforms give you an option. When
configured as a Device Type: File, Trams must have network access to the folder location named in the
Device properties. Default configuration:
C:\SABRE\APPS\INTERFACE\PNRDATA.TXT
Note: Trams for DOS users, the folder name of INTERFACE exceeds DOS file name extension of 8
characters, so the default configuration in Trams needs to read:
C:\SABRE\APPS\INTERF~1\PNRDATA.TXT
cable. The cable is terminated and tested by a SABRE field services technician. It is usually the agency’s
responsibility to purchase and install the cable between a controller serial port on the SABRE system and a
receiver serial port on the Trams PC. This should be ordered and determined during the site survey. Any
questions regarding which workstations can accommodate interface, should be discussed with the SABRE
Account Executive and the Field service Technician.
The Sabre interface cable is terminated as shown in the following diagrams. A standard 9-25 pin is
compatible with either end of the SABRE cable.
6/2/09 23
SABRE Trams SABRE Trams
25PIN [f] 25 PIN [F] 9PIN [F] 9PIN [F]
The Interface cable can also be ordered through Black Box Corporation. (Prices for cables are approximate
and subject to change without notice.) Allow 3-5 days for delivery. Shipping costs are additional.
Call Black Box Corporation to order toll free at: 877-877-2269 or directly at 724-746-5500. You can
use this number as well for customer support. Cable Prices and part numbers are quoted from the Black
Part # Description Price
2 3 2 3
3 2 3 2
4 5 4 8
5 4 5 7
6 20 6 4
20 6 20 6
7 7 7 5
24 6/2/09
Trams Back Office ships with a 32-bit utility - winint32.exe. You have the option of adding the Windows
Interface Utility to load at start-up.
The SABRE with Windows platform requires a dedicated Gateway for interface. The interface cable
must be configured and run from this dedicated controller to the Trams PC. SABRE Net uses the
image to file option ONLY.
All Platforms using an Image to file option and using SINGLE as the File Type must select SABRENET as
the CRS in the TBO (Windows) download screen. Sites using MULTIPLE as the File Type must use SABRE
as the CRS in the TBO (Windows) download screen. If you are converting from ADS on the LAN to Trams
6/2/09 25
on the LAN, be sure to have the SABRE Field Service Technician, disable the Interface Queue30, before
attempting interface. Interface records may be lost due to “dupe TA’s”. If you are converting from Travel
Base to Trams, be sure to compare the LNIATA of your existing POS QUEUE to the LNIATA configured in
the SABRE Printing Module.
The Options field in the Hardware Setup screen defaults to blank. Options entered here affect how records
are handled or interpreted. You may want to use one of the options specified below, if appropriate for your
office.
-u:0 = suppresses the AC lines - used by scriptwriters
-R:2 = null modem option - used for problem cables on Windows 3.x
26 6/2/09
status is on hold or active.
Q0 0 on hold
Q1 0 on hold
Q2 33 on hold
6/2/09 27
TMO line = Sabre detects a problem with the local lines.
Check that Trams is ready to receive records.
Check the ports and cable connections.
Check the Trams Interface Setup.
TMO no ack= Sabre is receiving no acknowledgment from your site.
Check the gateway connection. Possible re-start.
Check the asynch-mini program or controller. Possible re-start.
Check that Trams is ready to receive records.
Check the Trams Interface Setup.
28 6/2/09
2) From a SABRE workstation type:
• DX STATUS to check the status of the POS queue
• DX TRANSMIT to start the transmission of records
(SABRE allows re-transmit from the DWLIST to the POS queue)
3) Once all records have been received
• Stop the transmission from SABRE with the DX HOLD command
• Press the escape key to exit the Download screen.
6/2/09 29
Multiple general ledgers is a billable feature of Trams, but can be accommodated in a single database, with
branch designations pointing to separate ARC/BSP numbers and/or general ledgers. Consult with a Trams
sales representative for pricing and a Trams accounting support representative for optimal use of these
features. If multiple branches are being maintained in separate Trams programs or database aliases, then
branch commands at time of ticketing are needed to separate the interface records for transmission from
separate interface queues.
Also go to the Utilities|Setup|Global Default menu and be sure the field “Allow Branch Entries” is set to
“STP” or “FULL." To set up Branches in Trams Back Office go to Utilities|Set Up|Branches. To set up
Branches in Trams for DOS go to Utilities|Set Up|ARC Numbers.
30 6/2/09
Trams as Interface ID 3105191225 .
The branch and customer distinction used by SABRE/ADS is not the default setting for Trams. Trams
normally reads the branch designation from the ARC number in the Interface record, and uses the entire
DK number (filled to 10 characters), as a literal customer number or Interface ID. Trams options in
Utilities|Setup|Global Defaults, do allow for Branch overrides by DK number, similar to the Branch and
Customer breakdown of the DK number used by ADS. Trams search options eliminate the need for HOUSE
DK’s by agent. Please request the ADS conversion document through Trams FAX DOCS for additional tips
on a successful conversion.
Billing Address 5/
Customer name and address information can interface to Trams for any new clients. The address interfaces
when creating new client profiles during the interface process. Trams can accept up to 40 characters for
each address line. A change of address for existing clients is Noted in the Processing Error Log for review,
but does not update profiles automatically. Trams translates the billing address fields as the client name
and address.
To assist the back office in distinguishing new leisure clients from corporate clients, it may help to assign
alpha Interface ID’s for corporate clients.
6/2/09 31
Fax Number 5.S*FX
The customers fax phone number may be captured when creating new client profiles during the Interface
process. The FX code is added to the remark field and transmits to the phone field called Fax in the Trams
profile
[email protected] 5.S*EUPAULMCC*APPLE.COM
[email protected] 5.S*EUB//GATES*MSOFT.COM
[email protected] 5.S*EUMICKEY-MOUSE*DISNEY.COM
Trams translates the following SABRE characters accepted in the remark field.
* use for @ at symbol
// use for the _ underscore symbol
- use for the - dash symbol
Trams does not capture or track E-mail addresses at the passenger level. Other SABRE formats for E-mail
address in the PNR do NOT interface to Trams.
32 6/2/09
override the default inside sales agent Two sales agent id’s will appear on the booking.
If default commission rates are defined for the outside agent in the agent profile, the commission entry
added here overrides the default commission rate. Rates are a percentage of the agency commission.
Since Trams allows multiple agents per booking, there should be flex edits or QC procedures in place to
avoid multiple OA agents per booking.
6/2/09 33
the invoice level attach to each booking. Departments can also be defined within a clients’ profile. This entry
does not update the Client Profile, but attaches to the invoice or booking for reporting.
A corporate client has asked for travel management reports that contain
information on his employees travel patterns, by employee number and
department. Run some sample reports to test how the information should
be captured and stored. By assigning a UDID for employee number and
requiring the department for each passenger, a report can be run to your
customers specifications.
You must indicate an appropriate UDIDS number after the UD entry for Trams to sort the remarks correctly.
The space following the UDID number is mandatory to allow for alphanumeric data.
UDIDS can also be used globally to track market information for special promotions. Using UDIDs in this
manner requires that specific UDIDs are defined by the agency to ALWAYS mean a marketing code, or
reconciliation code. Often they act as invoice level flags for reporting or reconciliation programs.
Note: Any agency having a conflict with the Client Remarks field of a booking being interfaced to a UDID
field, can ignore UDID formats in the Client Remarks field of a booking by entering -NU in the Option field
34 6/2/09
on the Download Screen.
6/2/09 35
Add remark as passenger state- -SMITH/JOHN MR*LEISURE
ment information in the name
field
Client payment options are available at the booking level to enhance the payment options available through
interface. Such options include Electronic fund transfers and Credit card merchant pay methods. Client
36 6/2/09
payment options must comply with the form of payment entered at the invoice level.
ACL/012345/DIS/25.00/1.50/ONE/N1.1-OPTIONAL
6/2/09 37
Example: An ARC ticket for $385.95 is sold to the employee at a net
fare. By entering the above information for Face value, Trams captures
the correct amount to be collected from the employees 0.00
commission earned, and the real value of the ARC document from the
ticketing information. Trams interprets the transaction as follows for
accounting and the ARC report.
The invoice reflects the amount to collect from the customer in the total
fare. Base fare and Taxes can be changed manually, but neither
affects the ARC report.
TOTAL FARE:350.86|BASE FARE:324.91|TAXES
25.95|COMMISSION:0.00
The expanded fare information screen reflects the Face Value of
385.95
The ARC report shows the correct totals for reporting to ARC.
GROSS FARE:385.95|COMMISSION:35.09|RATE:10.00|NET
REMIT:350.86
Note: This is not to be used for Credit Card transactions to ARC.
Segment Information
Fare-by-Leg information is controlled by SABRE pricing and the Fare-by-leg option in the TJR. Trams reads
the segment fares based on the auto-price features in SABRE. When pricing and driving a ticket in SABRE,
the interface record includes a breakdown of the segment Fares-by-Leg. Trams reads up to 255 segment
fare lines in a single interface record. To capture segment fares on non-auto priced tickets use a manual
FARE BY LEG mask. To capture segment information on non-ARC air, use the *SG at the booking level.
A more accurate Fare-by-Leg for non-ARC/BSP air bookings, or ARC/BSP bookings that do not have the
Fare-by-Leg included, is calculated by using a mileage formula when mileage is present in the interface
record. When mileage is not present in an interface record then Fare-by-Leg is be calculated as presently
done, by dividing the base fare by the number of Origin/Destination trips.
Mileage
Trams captures segment mileage if present in the IUR. The mileage is recorded under the segment tab of
the invoice booking. This information may also be entered manually in Trams.
38 6/2/09
have a partial payment, only Cash/Check & CC Merchant payments. You must have the box "Allow Cash/Ck
Payments" in Utilities/Setup/Global Defaults/Interface-Mailmerge Prompt Tab "Checked", or this partial
payment enhancement will not be active for the Cash/Check partial payments, but, is not required for the
CC merchant partial payment to interface. The entry for your GDS needs to contain (amount), (form of
payment), (Check or CC Number/expiration date for CC Merchant). All other forms of payments are ignored,
including the form of payment in the 5.S*MS line when the 5.S*PP entry is present.
CASH 5.S*PP100.00*CASH
CHECK OR CK 5.S*PP100.00*CHECK*5432
CHEQUE 5.S*PP100.00*CHEQUE*5432
6/2/09 39
GP 10 Group affiliation included in invoice and GPTAHITI97
payments for reporting purposes
DP 20 Department DPSALES
DP00234
FP No form of payment UP
Form of payment check FPT OR FPCH
Form of payment cash FOPPISH
Form of payment credit card FPAX3782443987654
40 6/2/09
GQ 1 VALID IN BSP VERSION ONLY Note: TBO automatically zeros out
GST/QST/VAT on commission for
International Air Bookings
processed via Interface
A=No GST or QST GQA
B=GST only GQB
C=QST only GQC
D=GST and QST GQD
6/2/09 41
Descriptor Codes - Valid at Booking Level
The following descriptor codes can be added or linked to an AC line to interface additional information about
the transaction to Trams. See AC*SUP for format description and examples. Trams reads only the
following segment types when linked with an AC line. SEA, TOR, OTH, AIR, PTA, MCO, HHT, CAR, INS.
All other segment types are ignored by Trams.
Descriptor codes can be added as freeflow remarks to the end of a manual AC or ACL line.
ACOTH1/SUPPLY/DOC/P11/950.00/0/ALL/CK/1-28 CHARACTER FREE FLOW
Descriptor codes can be added in an MS line that links to the sold segment of the PNR. Display the PNR
itinerary and use the SABRE numbering to link to the sold segment. Using a segment number larger than
the segments in the PNR results in an additional segment added to the accounting record.
5.S*MS1S*FA3000.00*FC370.00*FD03JUN97*VNROYAL CARIBBEAN
Descriptor codes can also be added in an MS line that links to an AC or ACL line if the 28 character limit is
too restrictive.
5.S*MS101*FVXXX.XX*CMYYY.YY*TFZZZ.ZZ
X=Face value of the amount of ticket that appears in the face value field in Expanded Fare Info tab; Y=The
commission earned by agency; Z=Total Fare collect from the agent.
5.S*MS101S*FA3000.00*FC370.00*FD03JUN97*VNROYAL CARIBBEAN
42 6/2/09
IN 1 International Indicator INI
1 Transborder Indicator INT
1 Domestic Indicator IND
VALID IN BSP VERSION ONLY
GQ 1 ** to be decremented, as TBO (Windows) GQA
reads SABRE codes A,B,C,D used at GQB
ticketing. GQC
A=No GST or QST
GQD
B=GST only
C=QST only
D=GST and QST
6/2/09 43
OA 10 Outside Agent added to booking OA44
11 Commission% or Amount overrides% in OA70 30
16 Agent Profile OASUE 30 UA OVERRIDE
Sales Agent Remarks
space required between fields
IT 88 Itinerary ITLAXDFWLAX
RM 90 Client Remarks RMNEW ADDRESS
VR 90 Vendor Remarks display on invoice and VRNET DUE ONLY
reports
44 6/2/09
XP 4 Credit card expiration date XPMMYY
Note: may be used with the FP and CP
form of payment codes on MS line and MM=Month
free flow of the SABRE accounting line YY=Year
only
6/2/09 45
Automated Hotel Segment
Hotel segments booked through Sabre interface to Trams with the following defaults. The total fare is
determined by calculating the number of nights by the nightly rate. A commission of 10% is assumed for all
bookings, based on the default commission set in Trams Utilities|Setup|Global Defaults. The actual
commission rate can be added to the invoice to override the default by entering an MS entry that matches
the segment # assigned to the booking being overridden
For automated Hotel bookings, Trams reads the G-CC field, if present, to populate the CommTrackCCNo
with the credit card number used to guarantee the booking. For any Comm Track booking where no
CommTrackCCNo is specified, the PNR FOP (if C/C) is captured and displayed in the CommTrack CC NO
field on the Expanded Fare Tab of the booking.
Trams maintains cars and hotels on invoices only. If booking a car or hotel only, without having invoiced
the PNR yet, use one of the samples below to add a zero AC line for the hotel only invoice.
Using the Misc. OTH booking and AC line allows Trams to read the hotel information directly from the sold
segment, which includes name, address and property code.
46 6/2/09
For Sabre itineraries with a *HU command in the PNR, certain air segment information (Arrival/Depart Dates
& Times and Flight #s) updates existing Trams Invoices with this updated flight information by matching
Invoices with the Record Locator Number.
Only matching segments [based on depart city] are updated. New segments are not added and
existing cities are not changed (such as a new connecting city on the return).
If an Itinerary Update doesn't find a matching invoice, a message is added to the processing log and the
record is deleted. There is no chance to reprocess the record.
Trams maintains cars and hotels on invoices only. If booking a car or hotel only, without having invoiced
the PNR yet, use the sample below to add a zero AC line for the hotel only invoice. Subsequent updates
driven with DIT from the same PNR are automatically updated through interface.
6/2/09 47
The 2 samples above have different results in how Trams captures the hotel property details. The OTH
segment option works best for new properties as all property information from the original booking are
captured.
Note: Due to the free form structure of the manual hotel entry, the hotel ID and property code is not read
from the sell segment. For manual hotel only PNR's add the hotel ID to the free flow area of the zero
accounting line.
ACHHT1/SUPPLY/DEP/0/0.00/0/ALL /CK/1-*VCHI5555
For manual hotel bookings that are included in a PNR with other transactions, you may add the hotel ID to
an MS line override linked to the hotel segment in the SABRE PNR.
5.S*MS3*VCH55555*CM15
Trams maintains cars and hotels on invoices only. If booking a car or hotel only, without having invoiced
the PNR yet, use the sample below to add a zero AC line for the car only invoice.
Trams maintains cars and hotels on invoices only. If booking a car or hotel only, without having invoiced
the PNR yet, use the sample below to add a zero AC line for the hotel only invoice.
48 6/2/09
references. (For a full list of descriptor codes used at the booking level see the Descriptor Codes Valid at
Booking level chart.) Automated accounting lines for ARC/BSP tickets can be appended to include
additional information regarding the transaction, using coded remark lines. See overriding automated ARC
AC lines.
ACPTA1/TW/12345678904/P8/198.00/19.80/ALL/CK/1
ACMCO1/AA/12345678904/P8/198.00/19.80/ONE/CK/1
6/2/09 49
Issue the invoice with the format: DIN
Trams assumes the vendor ARC/BSP and a travel type of Domestic AIR for automated MCOs. To specify
a different travel type and/or a secondary vendor on manual MCOs, append the AC line with appropriate
descriptor codes before driving the invoice.
ACMCO1/AA/12345678904/P10/198.00/19.80/ONE/CK/1-*TT10*VCBREND
AN
AC/AA/12345678904/P10/198.00/19.80/ONE/CK/1/D
Use the base tax and commission rates for add collect. Include check digit in ticket number field. Add a valid
exchange remark to include net base and taxes. The tax ID’s are optional.
E = EVEN A= Exchange with ADD collect R= Exchange with REFUND
5.S*EXA*[BASE FARE]*[TAX ID][TAX AMT]*[TAX ID2][TAX AMT 2]
50 6/2/09
Manual ARC Travel Agency Service Fees - CC FOP
This option applies to SABRE agencies who are enrolled in TAFP directly with ARC. For format
examples see AC*AIR for other information.
Create the SABRE PNR and add a valid accounting line for the TAFP service charge.
AC/XD/12345678904/P0/22.73/2.72/ONE/CCAX372112341234123
1.1ROSEN L/1/D
5.S*MS101*SBSUP
Voids
Voided tickets interface to Trams if the SABRE option has been set in the agencies TJR. To determine if
the SABRE option for voids has been initiated enter W/VOD#* at a SABRE workstation. Refer to the SABRE
Helpdesk if further assistance is needed. (Set the interface Void option to Prompt or Always in
Utilities|Setup|Global Defaults| Interface/Mailmerge.)
Discount ACL
Discounted Cash or Check FOP transactions can be included for interface. Enter the fare charged to the
client followed by the income earned by the agency after the discount amount is subtracted from the
commission.
Note: Trams Back Office reads SABRE ACL lines as defined in Format Finder. For an online example in
SABRE see ACL*AIR, ACL*DOC or ACL*SUP for appropriate use of the ACL function. To manually add
an accounting line to a PNR to show discount information for air ticket transactions. Trams Back Office reads
descriptor codes valid at booking level if entered in the optional free-flow area of the discount line.
Trams for DOS users must use the Trams Face Value feature for interfacing discounts to Trams. By design
the ACL information prints on the SABRE invoice. For options regarding the verbiage used by SABRE see
Format Finder.
Note: AC line entries with a negative total fare and commission amount (i.e refund or discounts) must now
have an TBO FP code to indicate form of payment (FPCASH). If the FP code is absent, the payment will be
read from the invoice FOP.
6/2/09 51
Bulk Ticketing 5.S*FV
Trams does not recognize the ACB line used in SABRE to markup net or special fare transactions. Trams
reads the fare of the ticket sold, but requires a *FV entry to calculate the face value for ARC/BSP and the
net commission earned. Create the invoice as normal using the net fare for ticketing and the ACB line for
the markup to the client for proper invoicing. Add the Trams Face Value entry to interface the proper fares
and commission to Trams.
SELL the ticket like normal.... but before ENDING the RECORD, add the ACB line to
reflect the markup for the SABRE invoice.
ACB/009005/BLK/329.50/0.00/ONE/N1.1-SWISHER
Add the following 5.S* lines:
5.S*FV808.00*349.50 - This is the 5.S*FV[gross to be billed the
client]*[gross comm earned]
5.S*MS101*CP4*XP0304 - This is to process the CC in full from the client,
thru your CC merchant account, the ARC report shows this ticket as FOP
CHECK by SABRE design.
Note: There is limit to the number of codes that can be added in an MS line. You should limit your entry
to a single line screen display in SABRE. Multiple lines can be linked to a single accounting line by repeating
the SAME MS segment number.
52 6/2/09
Non-ARC/BSP Supplier Invoice
The issuance of invoices for non-ARC/BSP items are dependent on the use of a supplier segment and a
matching accounting line. See AC*SUP for additional information on SABRE formats. The SABRE AC line
can be appended with up to 28 characters that do not print on the invoice. Use the Trams booking descriptor
codes to supplement the AC line with information for Trams. Trams does not translate the FOP for
Non-ARC Suppliers unless the Interface Supplier Payments flag in Utilities|Setup|Global Defaults is set
to YES.
Trams reads valid AC/AD lines linked to the following segment types:
AIR, CAR, HHT, TOR, SEA, OTH, INS, ATX
All other segment types are ignored. If you are using customized scripts based on MS formats you may need
to disable Trams ability to read AC/AD lines. Check with your script writer.
To disable the SABRE features enter -U:0 in the hardware setup options under Interface setup. If you are
using Trams Back Office, you may enter the -U:0 in the Options field in the Interface|Download screen. To
record an additional booking using an MS line, the segment number must be larger than what exists in the
PNR.
Refer to the SABRE Format Finder screens for additional information on SABRE formats. AC*DOC and
AC*. (For a full list of descriptor codes used at the booking level see the Descriptor Codes Valid at Booking
level chart.)
A B C D E F G H I J K
G = Tax amount
I = Form of payment
J = Number of documents
K = 28 character free flow area does not print on invoice, but are included in the interface record.
6/2/09 53
Issuing Invoice for Tour Deposit
Create a valid tour segment in the PNR. Add an appropriate accounting line linked to the segment type sold.
The data entered after the dash in the accounting line can be read by Trams using valid booking level
descriptor codes. SABRE allows up to 28 characters in the free flow field of an accounting line. The booking
type determines how the sale is accounted for. Check with your Trams operator to determine the preferred
option for your office.
Trams reads the vendor code from the standard AC line, or as a coded field appending the AC line.
ACTOR1/002200/DEP/0/200.00/0/ONE/CA 1.1JONES
D/1-*TT9*CF37842
54 6/2/09
Issuing Invoice for Cruise Deposit
Create a valid cruise segment in the PNR. Add an appropriate accounting line linked to the segment type
sold. The data entered after the dash in the accounting line can be read by Trams using valid booking
descriptor codes. SABRE allows up to 28 characters in the free flow field of an accounting line. The booking
type determines how the sale is accounted for. Check with your Trams operator to determine the preferred
option for your office.
To add a separate booking use a segment number larger than what exists in the PNR. To link the MS line
to an AC line, use the same segment number.
6/2/09 55
A supplier sale for CC FOP ACOTH1/SUP-
if handled thru TAFP. PLY/VCH/9.65/10.00/0/ALL/CCVI432148076844
3072 1.1TADA J/1-*TTSERV FEE*VCTAFP
Note: Trams reads the ticket number in the void record for a Sabre E-Merchant Card - Services charged
and matched to the Confirmation Number in a TBO supplier booking, closed by CC and with a Travel
Category of Service Fee, if a match, Trams voids the booking. To utilize this feature, check that
Utilities|Setup|Global Defaults\ Interface/Mailmerge Prompt Tab has Allow Voids set to Prompt.
ACOTH1/001006/FPT/10P/380.00/33.40/ALL/CCV
I3078778740829004 1.1JACKSON L/1-*TTAIR
Comm track booking ACOTH1/001120/FPT/10P/380.00/33.40/ALL/CCV
I3078778740829004 1.1JACKSON L/1-*TTDOM.
AIR*SG*SBCOM
Add Fare Savings to Non ACOTH1/SUPPLY/DOC/6.90/64.20/6.90
ARC/BSP booking /ALL/CK/1-*TT1*VCWN*SG*FJL*FF467.00*LF103.50
The SG descriptor code can be used to capture the segment information for non-ARC/BSP transactions to
be available for reporting purposes in Trams. This *SG entry has been expanded to allow the user to specify
which segments are to be included. The format is "*SG 01 02 03 04" where each segment number is
separated by a space. You will now be able to specify the proper segments for each booking in an invoice.
Descriptor codes valid at booking level can be used to capture segment and fare savings information for
non-ARC and manual AIR segments.
Supplier Exchange Ticket
Trams reads a supplier exchange ticket even when an ARC/BSP sale is in the same invoice, when entered
at the booking level using MS line options.
For example:
MS25S*VCWEBAIR*TT1*CF1234567890*SG*EXA
MS25*BF201.00*TXXG14.07
MS25*FPVI12345678901234*XP1107
56 6/2/09
Note: Sabre Non-ARC tickets entered via AC lines (i.e. Southwest) now interface as Supplier transactions.
Previously Trams read the WN in a Sabre record as Southwest Air, but creating it in TBO as a Comm Track
booking. In the days of commission, the Comm Track booking was easy to reconcile through NPC. But in
order to get the sale on the Income Statement, the agency had to manually close out all of the zero
commission comm track bookings which was a lot of extra work. Now with the bookings interfacing as
Supplier, CC with no commission, the vendor side auto closes, eliminating having to manually close them
out.
6/2/09 57
a single transaction, you must account for the transaction with separate bookings. This records the proper
fare and commission totals for clients and vendors.
Discounts ACL
Discounted Cash or Check FOP transactions can be included for interface. Enter the fare charged to the
client followed by the income earned by the agency after the discount amount is subtracted from the
commission.
Notes: Trams reads SABRE ACL lines as defined in Format Finder. For an online example in SABRE see
ACL*SUP for appropriate use. To manually add an accounting line to a PNR to show discount information
for air ticket transactions. Trams Back Office reads descriptor codes from the optional free-flow area of the
discount line.
By design the ACL information prints on the SABRE invoice. For options regarding the verbiage used by
SABRE see Format Finder.
58 6/2/09