Skip to main content

Air Reservations (Sabre)

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

Air Reservations (Sabre)

  • Updated

Both ARC/BSP and Non-ARC/BSP tickets can be interfaced to Trams. Non-ARC/BSP tickets are interfaced as supplier bookings.

Contents

ARC/BSP Tickets

Sabre creates the necessary accounting lines automatically upon ticketing. Additional information can be included by entering MS lines prior to invoicing.

Manual ARC/BSP Tickets

ARC/BSP tickets issued outside of Trams can be interfaced:

  1. Create air segments using the appropriate segment status. Trams reads both active and passive segment details.
  2. Create an ARC/BSP accounting line with the ticket details. Enter the command AC*AIR for details.
  3. Enter any required MS lines.
  4. Generate invoice using the command DIN.

ARC/BSP Exchanges)

When issued using Sabre automated exchanges, the necessary accounting lines are created automatically. To issue an automated exchange:

  1. Remove any previous accounting lines and any related MS lines.
  2. Issue the exchange using the appropriate Sabre format.
  3. Add any necessary MS lines.
  4. Generate the invoicing using the command DIN.

ARC/BSP Refunds

When issued using Sabre automated refunds, the necessary accounting lines are created automatically. To issue a refund:

Do not remove any segments from the PNR until the refund is invoiced.

  1. Remove any previous accounting lines and related MS lines.
  2. Issue the refund using the appropriate Sabre format.
  3. Add any necessary MS lines.
  4. Issue the invoice using the format DIN¥R.
  5. Cancel the segments and end the PNR.

ARC/BSP Voids

A void message is transmitted to Trams when the Sabre WV command is used. Tickets voided outside of Sabre, such as in IAR, must be manually voided in Trams.

NDC (New Distribution Capability)

Sabre NDC bookings interface to Trams Back Office. Note that Sabre generates an invoice and an interface records as part of the fulfillment workflow. You must enter any invoice- or booking-level descriptor codes before fulfilling the NDC order.

See NDC Bookings in Trams Back Office for more information.

Non-ARC/BSP Tickets

Non-ARC/BSP tickets include those issued directly non-ARC/BSP airlines, such as Spirit, and tickets purchased through consolidators. Non-ARC/BSP tickets are entered as supplier bookings.

  1. Create air segments using the appropriate segment status. Trams reads both active and passive segment details.
  2. Create and OTH (other) segment.
  3. Create a supplier accounting line linked to the OTH segment. See AC*SUP for more information.
  4. Enter any required MS lines.
  5. Generate invoice using the command DIN.

Non-ARC/BSP Supplier Accounting Line

ACOTH1/SUPPLY/TKT/0.00/0.00/0.00/ONE/CK 1.1DOE J/1-(free-flow data) 
  A    B      C   D    E.   F    G   H             I
  • A. Sabre segment type and number: The three-letter Sabre segment type and number
  • B. Vendor ID or placeholder: Six-character vendor ID, or placeholder, “SUPPLY.” If the placeholder is used, include the descriptor VC and vendor ID in the free-flow data portion of the accounting line.
  • C. Sabre supply code: Three-letter code that controls what is printed on Sabre-generated invoices and itineraries. The code TKT prints “Ticket”. Refer to DU*/ACT for options.
  • D. Commission: The amount of commission. To enter a percentage, enter “P” followed by the percentage.
  • E. Base Fare: Base fare amount
  • F. Taxes: Total taxes. Sabre adds the base fare and taxes to arrive at the total amount.
  • G. Amount By: Enter ONE, PER, or ALL:
    • ONE: Accounting line applies to a single passenger. Passenger association must be included in the form of payment section and a separate accounting line must be entered for each booking.
    • PER: Accounting line amounts are multiplied by the number of passengers and a separate, identical Trams booking is created for each passenger.
    • ALL: Single accounting line with a total amount that applies to all passengers. One Trams booking is created.
  • H. Form of payment: The form of payment details, CA (cash), CK (check), or CC (credit card). CC is followed by the card type and account number. For accounting lines using the amount by option ONE, include a space, followed by the passenger number and name.
  • I. Free-flow text: Used to enter up to 28 characters of descriptors and data.

If you need to include more than 28 characters of additional information, create an MS line associated to the accounting line.

The following descriptors should be included in Non-ARC/BSP accounting lines:

  • SG: Indicates that flight segment details should be included with the booking. Enter SG alone will include all air segments in the PNR. You can select specific segments by including the number after the SG descriptor, for example, “SG01 03”.
  • CF: Confirmation or ticket number. Ticket numbers for non-ARC/BSP bookings are entered as 10 digits, excluding the airline validation number. For example, ticket number 006-2402181649 would be entered as 2402181649.
  • VC: If using the two-letter airline code or another code that is not six-characters.

Non-ARC/BSP Exchanges

Non-ARC/BSP exchanges are entered using supplier accounting lines and the following descriptors. Note that refund exchanges are entered using a refund supplier accounting line. Refer to ACR*SUP for details.

  • EX: Indicates the type of exchange:
    • EXE: Even exchange
    • EXA: Add-Collect
    • EXR: Exchange with Refund
  • OT: The original ticket/confirmation number

Non-ARC/BSP Exchange Accounting Line

ACOTH1/SUPPLY/TKT/0.00/0.00/0.00/ALL/CK/1-*SG*CF2402181734*EXE*OT2401241899
  A    B      C   D    E    F    G   H     I  J            K   L
  • A. Segment number
  • B. Vendor ID or placeholder, “SUPPLY”
  • C. Sabre supply code. Refer to DU*/ACT for options. TKT prints “Ticket”.
  • D. Commission amount or “P” followed by commission percentage.
  • E. Base fare
  • F. Total taxes
  • G. Sabre charge-as option
  • H. Form of payment and passenger association
  • I. SG indicates that segment information should be interfaced, optionally followed by specific segment numbers.
  • J. CF followed by the new ticket/confirmation number
  • K. EXE, EXA, or EXR for exchange type. EXR is entered using a refund accounting line.
  • L. OT followed by the original ticket or confirmation number.

Non-ARC/BSP Refund

Non-ARC/BSP refunds are interfaced using refund accounting lines. Refer to ACR*SUP for more information. Do not cancel refunded segments until the refund invoice is generated.

Non-ARC/BSP Voids

Non-ARC/BSP voids must be manually entered in Trams.

Fare Savings (FF, LF, and FJ)

Fare savings information can be entered for reporting purposes. These allow Trams to provide reports detailing fare savings and loss along with the reason for each booking.

Fare savings can be entered at the PNR or booking level. When entered at the PNR level, the high fare (FF), low fare (LF), and fare justification code (JF) is included on all bookings, including any non-air reservations in the PNR.

Fare justification codes are defined by your agency. A list of codes can be printed by opening Utilities > Setup > Fare Codes, then selecting Print.

When entered at the invoice level, fare savings information will interface to all air reservations on the invoice.

Consolidator Bookings and Marked Up/Discouned Air (ACL and FV)

Trams reads Sabre discount lines (ACL). ACLs are the easiest way to invoice discounted tickets. For more information, refer to ACL*AIR and ACL*SUP.

To markup ARC/BSP tickets, use the descriptor FV (face value) along with FF (full fare) and CM (commission). The FV descriptor is used to show the amount of the ARC/BSP document as reported to ARC or BSP. Enter TF followed by the amount charged to the client, and CMA followed by the net commission received by the agency, including the markup/discount.

5.S*MS101*FV1700.00*TF1900.00*CMA200.00
    A     B         C         D
  • A. Accounting line association
  • B. FV: Total amount of ticket as reported to ARC or BSP
  • C. TF: Total amount charged to the client
  • D. CMA: Net amount of commission included the markup or discount

Other ARC/BSP Documents

Sabre creates the required accounting lines for ARC/BSP documents issued in the GDS. Manual ARC/BSP accounting lines can be added using the appropriate Sabre formats. Refer to AC*DOC for more information.

Travel Agency Service Fees (MISF)

Sabre creates the required accounting lines for travel agency service fees (TASF) issued using the MISF format.

Electronic Miscellaneous Documents (EMD) and Miscellaneous Charge Orders (MCO)

When issued using automated formats in Sabre, the required accounting lines are created automatically.

EMDs interface to the first Trams travel type with the word “Misc.” If no travel types include Misc in their name, they interface to the first travel type with the category Other. The travel type can be overridden using the descriptor TT (travel type) in the free-flow text of the AC line or in an MS line.

EMDs associated with segments automatically include segment details. To interface without segment details, create an MS line with the descriptor SG0.

Prepaid Travel Advice (PTO)

While rare, prepaid travel advice (PTA) documents may be interfaced to Trams using the appropriate Sabre formats. Refer to AC*PTA and Sabre Central for more information.

 

Related to

Related articles