In addition to air, car, and hotel segments described earlier, Trams also reads information from air taxi (ATX), cruise (CRU), insurance (INS), tour (TOR), and other (OTH) segments. Due to the free-flow nature of these segment types, additional information for these bookings must be entered using descriptors.
Contents
- Required Information
- Sabre Scripts and PF Keys
- Accounting and MS Lines
- Deposits, Interim, and Final Payments
- Examples
Required Information
At a minimum, we recommend that all bookings include the following information:
Booking submit to (ARC/BSP, supplier, or commission tracking)
- City or itinerary
- Travel type
- Vendor name and ID
- Confirmation or ticket number
- Total fare
- Taxes
- Commission
Except for ATX and OTH segments, Trams reads the vendor ID, start date, and city for these segments. From ATX and OTH segments, Trams reads only the start date.
Depending on the type of booking, additional information may be required by your agency. Since Sabre allows up to 28 free-flow characters of text in accounting lines, you may be able to enter all the required information using only the segments and a single accounting line. But for more complex bookings, such as tours and cruises, MS lines are used for the remaining details.
This section provides example accounting and MS lines for common auxiliary reservations.
Sabre Scripts and PF Keys
Sabre scripts are helpful for entering the required Trams information for these bookings. The Sabre Marketplace offers a free set of scripts that your agency may order. Scripts obtained through the Sabre Marketplace are automatically installed in the Sabre Red Workspace. Enhanced and customized scripts are available from third party Tres Certified Consultants.
PF Keys (programmable function keys) can be used to make entering repetitive formats easier. Sample PF keys for Trams entries are provided throughout this guide. Refer to PF Key Examples on Sabre Central for more information about setting up and using them.
PF Keys (programmable function keys) can be used to make entering repetitive formats easier. Sample PF keys for Trams entries are provided throughout this guide. Refer to PF Key Examples on Sabre Central for more information about setting up and using them.
Accounting and MS Lines
Supplier accounting lines are used when entering auxiliary bookings. To interface a booking as commission tracking, include the descriptor SBCOM (submit to commission tracking).
It’s possible to enter Trams bookings without an accounting line. MS lines that are not associated with a valid segment or AC line number interface as separate bookings. These bookings do not print on Sabre invoices and itineraries.
To create a booking without an AC line, you can use an MS line number between 10 and 99. The submit to for these bookings is enter immediately after the first MS line number, before the descriptor codes. They are a single letter indicating the submit to option: A for ARC/BSP, C for commission tracking, and S for supplier. If a booking requires more than one MS line, the submit to is only included on the first line.
5.S*MS10S*VCTVLGRD*TT7*CF9001240218
5.S*MS10*TF389.00*TX9.00*FPCK*DEGOLD
5.S*MS10*SD15MAR*ED22MAR
For more information about accounting and MS lines, see Interface for the Front Office (Sabre).
Deposits, Interim, and Final Payments
A new invoice is generated for each payment. Before invoices subsequent payments, delete an accounting and MS lines relating to the previous invoice. Leaving those lines in a PNR will result in duplicate bookings in Trams.
Common Descriptor Codes for Auxiliary Bookings
Sabre segments and accounting lines include much of the mandatory booking information, including start date, city code, and the six-character vendor ID. The remaining information can be entered using descriptor codes: ED (end date), TT (travel type), and CF (confirmation or ticket number). Detailed itineraries can be included using the IT itinerary descriptor.
Refer to Descriptor Codes for a list of all descriptor codes that may be used for these bookings.
Examples
The following are examples of common auxiliary accounting and MS lines.
Non-ARC/BSP Service Fee
0OTHAAGK1LAX02FEB-AGENCY FEE
ACOTH1/SVCFEE/FEE/35.00/35.00/0.00/PER/CCVI4444333322221111/1-*XP1229*CP4
The descriptors XP (expiration date) and CP4 provide the information to process the service fee as a credit card merchant in Trams. Using the Sabre charge-age option PER means that a separate service fee will be created for each traveler on the PNR.
Cruises and Tours
When invoicing cruise and tour deposits, the payment is entered as the base fare. Commission and tax are zero as they are accounted for at the time of final payment. Most agencies use a separate travel type for deposits and final payments.
You may wish to include FA (final payment amount), FD (final payment due date), and FC (final commission) in the deposit.
Deposit with final payment amount information
ACSEA1/PRNCRU/0/250.00/0/ALL/CK/1-*TT4*CFX2Y4R9
5.S*MS101*FA1550.00*FD01MAR*FC252.00
Final payment
ACSEA1/PRNCRU/252.00/1550.00/ALL/CK/1-*TT5*CFX2Y4R9
Split Form of Payment
A single booking should include a single form of payment. Trams processes payment information at the booking level. This allows a different payment method for each booking.
When receiving a split form of payment from the customer for a single transaction, you must account for the transaction with separate bookings. This records the proper fare and commission totals for clients and vendors.