Académique Documents
Professionnel Documents
Culture Documents
Module Overview
Gates Table
Displaying a Gate Table .................................................................................................................................... 97
Creating/Deleting a Gate ................................................................................................................................... 98
Appendix A
PNR Status Code List...................................................................................................................................... 140
Item Description
Objectives By the end of the module, participants will be able to describe the purpose of each table
and use the correct entry to edit the tables, when applicable. The Tables explained in
the module are:
• The Airline Serving Airport (ASA) table
• The Passenger Terminal Information (TML) table
• The Priority Classification (PRC) table
• The Temporary Airport Restrictions and Embargoes (EMB) table.
• The Airline Directional Airport Pair Information (AAP) table.
• The Airline Seat Restrictions (ASR) table.
• The Gate Information (GATES) table.
• The Check-in Transaction History table
• The Baggage Agreement table
• The Self Tagging LNIATA table
• The IATA Message Control table
• The Irregular Operation Reason Code table working behind ESV
UAT Keywords:
Display tables: If the GDSPLY or SELECT EPR keywords are absent, the UAT
keyword FNLBDG is required in order to display the Daily Flight List, the PDC
Performance Statistics or the Oversales Statistics.
Update Tables: CONTRL or FNLBDG
Updating Gate information requires the UAT keyword CONTRL on the LNIATA (Line
Number Interchange Address Terminal Address) where the entry is being made.
Preparation For Priority Code Table users, updates should be made in TSTS only and the new
codes will be rolled into real-time as an implementation. Ten days notice is required.
The Priority Code Table is updated by Sabre Holdings.
To request updates, contact Customer Care.
Passenger Terminal x x
Restrictions/Embargoes x x
Priority Classification x x x
Gates x x
Check-In Transaction x x x
Creating
Priority Classification x x x
Updating
Restrictions/Embargoes x x
Priority Classification x x x
Gates x x x
Passenger Terminal x x x x
Unauth Bag Routing field
ESV Table x x
PNR Sync x x
Deleting
Airport Check-In x x x x
The SabreSonic® Check-in system workflow at airports rests upon processes that are determined and
stored in various database tables for each airline.
This module addresses the main database tables that serve as the foundation for your airport check-in
operations.
The tables presented in this module are:
• The Airline Serving Airport Table – or ASA table.
• The Passenger Terminal Information Table.
• The Priority Classification Table.
• The Temporary Airport Restrictions and Embargoes Table.
• The Airline Directional Airport Pair Table.
• The Airline Seat Restrictions Table.
• The Gates Table.
• The System Transaction History Table.
• The ESV Table- used for carriers who opt for the Enhanced Synchronization of VCR’s.
For each table, we will show you how to display it and we will discuss how to update it, as well as
advise whether it is you, the airline, who are responsible for the update, or whether you must request
an update via Customer Care.
The data in the tables are usually considered static, which means once the tables have been
established, the data is updated infrequently. Only your airline system administrators or employees
with specific keywords in their EPR can do the update.
All the entries to display, update and delete are in a Quick Reference at the end of the module, to help
you quickly identify the entry you need at any time.
The Airline Serving Airport table (also known as the ASA table) table is an airline maintained table.
You must create an ASA table for each station your airline flies into and out of. The ASA table
contains data related to the specific airport such as whether that airport is considered a hub or not, the
cutoff times for domestic and international flights out of that airport, the default supervisor printer
address at the airport which will receive the GENDEC message, and more.
Your airline maintains most of the fields in the ASA Table. You will find the fields maintained by
Sabre Holdings referenced in this document.
Entry Explanation
GC* Primary system display action code
Note You can add another slash separator and an optional carrier code before the airport code
(GC*ASA/U0/YVR) to view information for another airline for 3rd party ground handling.
You would create a new ASA table when your airline opens a new station. Creating an ASA table
uses the same entry as updating a table, however if you make an update entry when the airport does
not exist in the table, the system creates a new airport item using the airline code, city, qualifiers and
indicators you used in the entry. If the system finds an existing airport item for your airline in the
ASA table, it serves as a model on which to base any new airport item. Otherwise, the first airport
item found for any carrier serves as the model. Then the system duplicates the model item and
updates it with the airline code and data from your entry to form the newly created airport item.
If an airport exists, but with a different airline code, the system checks for an existing airport item
for your airline when you make an update entry.
If the airport does exist in the ASA table and the code for the airline and the city match, the system
considers the update entry as just an update to the existing city, so any qualifier or indicator data
included in your entry amends the corresponding fields in the existing airport item.
When you create or update an ASA Table, you use a “GC/ASA” entry. Every GC/ASA entry must
contain a city code, a baggage index number and any optional qualifiers.
The baggage index number is setup by Sabre Holdings. The index number serves as an internal prefix
to the bag tag number, which the system uses for baggage routing to the corresponding destination
and prevents duplication of bag tag numbers. The number will be from 3 to 9, determined by the first
letter of the city or city code (predetermined by your airline).
Index numbers corresponding to the first letter of a city can vary from airline to airline, so ensure you
use the BGI number currently in use for your airline. Please contact Customer Care for assistance in
obtaining this number. See the following for an example breakdown:
A-C = 3 D-H = 4 I=L = 5 M-O = 6 P-R = 7 S–8 T-Z – 9
Entry Explanation
The definitions of each field in the ASA table are discussed later.
Updating the ASA table means you wish to change the value of a qualifier or to re-define certain
characteristics in the table for a specific airport.
Updating the ASA table requires the following:
EPR keywords: TTSCTL and FSGAGT
Duty code: ‡ (the Cross-of-Lorraine)
Use the following example entry to update fields related to a specific station:
GC/ASA/U0/YVR/BGI9/DB60
Entry Explanation
/U0 Slash separator and the airline code (not necessary if it is your carrier)
/IB Slash separator and the International Baggage Cutoff Minutes indicator (example of an
additional update)
The response is a redisplay of the ASA table with the fields updated as requested.
The definitions of each field in the ASA table and the corresponding indicator will be explained in the
following sections. In each section, you will see example entries showing you how to update the
indicator along with a table explaining each piece of the entry. You will also see example entries on
how to remove the indicator when applicable.
The Domestic Baggage Cutoff Minutes indicator determines the number of minutes before a domestic
flight departure at which time baggage is issued as “voluntary separation”. The maximum is 999
minutes. Your airline maintains this table.
Use the following example entry to set the domestic baggage cutoff to 30 minutes:
GC/ASA/YVR/BGI9/DB30
Entry Explanation
The International Baggage Cutoff Minutes indicator determines the number of minutes before an
international flight departure at which time baggage will be issued as “voluntary separation”. The
maximum is 999 minutes.
Use the following example entry to set the international baggage cutoff to 30 minutes:
GC/ASA/YVR/BGI9/IB30
Entry Explanation
The indicator in the Checked Baggage Limit field determines the maximum number of bags a
passenger can check before excess baggage charges are applied. The maximum allowable number is
9. If the number of bags exceeds this amount during check-in, the Excess Baggage Mask (MIXB)
displays.
Use the following example entry to set the maximum number of checked bags to 2:
GC/ASA/YVR/BGI9/CL2
Entry Explanation
The Bag Tag Printer Type Code indicator is setup and maintained by Sabre Holdings to identify the
type of bag tag printer in use at the location. The ASA table only allows for one type of bag tag
printer per station. The bag tag printer type code can be overridden by LNIATA using the Airline
Printer Exception Table (PRX). For additional information on the PRX table, see FOCUS reference
(F*REM/PRX/DISPLAY).
Sabre Holdings maintains the ATB Format Message ID indicator, which determines the bag tag
printer PECTAB downloads. For additional information on PECTAB, see FOCUS reference
(F*FMH/PRINTER/DIAGNOSTIC/PECTABS). The ATB format (ATBF) and ATB print (ARBP)
message ID’s are unique to each airline carrier. Once your routine number is established, we provide
you an ATB message ID that corresponds to the entry on the ASA table.
Sabre Holdings sets up and maintains the ATB Print Message ID indicator, which determines the bag
tag printer PECTAB downloads. The ATB format (ATBF) and ATB print (ARBP) message ID’s are
unique to each airline carrier. Once your routine number is established, we will provide you an ATB
message ID that corresponds to the entry on the ASA table.
The number you enter in the Domestic Boarding Time Minutes field indicator prints on the boarding
pass, indicating the number of minutes before a domestic flight departure at which time boarding
begins. The maximum allowable time is 99 minutes. The system automaticallly updates this time if
the departure time is changed and is printed on the boarding pass.
Use the following example entry to set the domestic boarding time to 30 minutes:
GC/ASA/YVR/BGI9/DBT30
Entry Explanation
Note Boarding time on domestic or international boarding passes are scheduled departure time
minus boarding times minutes. Boarding time on domestic or international EDIFACT boarding
passes are estimated departure time minus boarding times minutes.
Example: If your flight leaves at 6:30 p.m. and you set your domestic boarding time for 30
minutes, then the time that will print on the boarding pass is 6:00 p.m.
The number you enter in the International Boarding Time Minutes field indicator prints on the
boarding pass, indicating the number of minutes before an international flight departure at which time
boarding begins. The maximum allowable time is 99 minutes. This system automatically updates this
time and prints it on the boarding pass if the departure time is changed.
Use the following example entry to set the international boarding time to 90 minutes:
GC/ASA/YVR/BGI9/IBT90
Entry Explanation
Note Boarding time on domestic or international boarding passes are scheduled departure time
minus boarding times minutes. Boarding time on domestic or international EDIFACT boarding
passes are estimated departure time minus boarding times minutes.
Example: If your flight leaves at 6:30 p.m. and you set your domestic boarding time for
90 minutes, then the time that will print on the boarding pass is 5:00 p.m.
The number you enter in the Hours Before Departure Boarding Pass Allowed field sets the number of
hours before the flight departure when you can issue boarding passes. The hours may be 0, or
anywhere from 4-48. Setting the number to 0 indicates that you can issue boarding passes anytime
within the SabreSonic Check-In flight initialization period (date plus 3 days for carriers that use the
Department of Homeland Security (DHS) Secure Flight and 2 days for DHS carriers).
The following example entry sets the cutoff for printing boarding passes to 4 hours before boarding:
GC/ASA/YVR/BGI9/PBP4
Entry Explanation
/PBP Slash separator and the Hours Before Departure BP Allowed indicator
The number you enter in the Hours Before Departure Bag Tag Allowed field sets the number of hours
before flight departure when you can issue bag tags. The hours may be 0, or anywhere from 4-48.
Setting the number to 0 indicates that you can issue bag passes anytime within the SabreSonic Check-
In flight initialization period (date plus 3 days for carriers that use the Department of Homeland
Security (DHS) Secure Flight and 2 days for DHS carriers).
The following example entry sets the cutoff for printing bag tags to 4 hours before boarding:
GC/ASA/YVR/BGI9/PBT0
Entry Explanation
/PBT Slash separator and the Hours Before Departure BT Allowed indicator
Note If Advanced Baggage Check-in field is set to Y (Yes), then the 0 setting in the Hours Before
Departure BT Allowed field will also allow you to issue bag tags for the next day’s flight.
As previously discussed, the number you enter in the Baggage Index Number field serves as an
internal prefix to the bag tag number, used for baggage routing to the corresponding destination and
prevents duplication of bag tag numbers. The number will be from 3 to 9, determined by the first
letter of the city code and is set at the creation of the ASA table.
Use the following example entry to update the baggage index number indicator:
GC/ASA/YVR/BGI9
Entry Explanation
The Supervisor Printer Address (set up by Sabre Holdings and then maintained by your airline) is the
default printer address where you can print a GENDEC (General Declarations Form) for Crew
information, Illness and Disinsecting information.
Use the following example entry to update a supervisor printer:
GC/ASA/YVR/BGI9/SPVPRT31CA3A
Entry Explanation
Hub City
The Hub City field indicates if your station is a hub for the airline. If the city is a Hub, a four-hour
window of flights displays starting with the time of display. If the city is not a hub, an eight-hour
window of flights displays. By default, this indicator is set to N (No) or “off”.
The Hub City indicator is a toggle. Entering HUB changes it to Y (Yes), and then entering HUB
again changes it back to N (No).
Use the following example entry to update a HUB city:
GC/ASA/YVR/BGI9/HUB
Entry Explanation
Reconfirmation Required
The Premium Bag Destination indicator identifies a premium passenger’s bags. This field is used
mostly by carriers who have frequent flyer programs. A “premium” passenger is a passenger in any
cabin with a full fare ticket or with a higher FQTV status. By default, this indicator is set to N (No)
or “off”.
Use the following example entry to turn on the indicator to identify a premium passenger’s bags:
GC/ASA/YVR/BGI9/PREM
Entry Explanation
Use the following example entry to turn off the indicator to identify a premium passenger’s bags:
GC/ASA/YVR/BGI9/X-PREM
You should mark the Uses Metric System Measurement indicator to Y (Yes) if the airport uses metric
units for baggage weight (metric or pounds). By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Metric System indicator:
GC/ASA/YVR/BGI9/METRIC
Entry Explanation
/METRIC Slash separator and the Uses Metric System Measurement indicator
Use the following example entry to turn off the Metric System indicator:
GC/ASA/YVR/BGI9/X-METRIC
Use the Unauthorized Bag Routing indicator for non-air Codeshare markets where your airline sells
connecting space on scheduled ground transportation such as rail or bus line.
Setting the Unauthorized Bag Routing indicator to Y (Yes) for the destination station prevents you
from issueing bag tags. If you set the Unauthorized Bag Routing indicator to Y (Yes) for the
connection city, it causes bags to be short-checked and the passenger will be required to recheck their
baggage at the next city.
Updating the Unauthorized Bag Routing field requires the following:
EPR keywords: TTSCTL, FSGAGT and ACSDBU
Duty code: ‡ (the Cross-of-Lorraine)
Use the following example entry to prevent bag tags from being issued:
GC/ASA/YVR/BGI9/BAGRTE
Entry Explanation
The Airport Check-In Active indicator determines if SabreSonic Check-in is active for your location.
By default, this indicator is set to N (No) or “off. If you do not change the Airport Check-In Active
indicator to Y (Yes), your location is considered “un-automated”.
Use the following example entry to activate airport check-in:
GC/ASA/YVR/BGI9/ACTIVE
Entry Explanation
Set the Advanced Baggage Check-In indicator to Y (Yes) to allow advanced baggage check-in up to
24 hours prior to departure. This indicator defaults to Y (Yes)
Use the following example entry to activate the advanced baggage check-in indicator:
GC/ASA/YVR/BGI9/ADBAG
Entry Explanation
Use the following example entry to deactivate the advanced baggage check-in indicator:
GC/ASA/YVR/BGI9/X-ADBAG
Your airline maintains the Standby (Stby) Boarding Pass Required field, which indicates whether the
airport requires priority list passengers to have a priority-boarding pass in order to pass through
Security. This indicator defaults to N (No).
Use the following example entry to require priority-boarding passes:
GC/ASA/YVR/BGI9/SBYBP
Entry Explanation
/SBYBP Slash separator and the STBY Boarding Pass Required indicator
Use the following example entry to remove the requirements for priority boarding passes:
GC/ASA/YVR/BGI9/X-SBYBP
Pet Restriction
Pet Restricton indicates whether your airport allows the check-in of pets or not. By default this
indicator is set toN.
Use the following example entry to activate Pet restriction:
GC/ASA/YVR/BGI9/NOPET
Entry Explanation
Use the following example entry to remove the requirements for pet restriction:
GC/ASA/YVR/BGI9/X-NOPET
Note The SSR Inventory controls the number of pets that can be checked-in per flight. The Pet
Restriction option in the ASA table addresses the airport policy whether you allow pet check-in
or not.
Use the Bag Tag with Ground Transfer option to indicate if an airport is located in a city with
multiple airports, and if ground transportation of baggage is available for connections between the
area airports. By default, this indicator is set to N (No) to indicate that the airport is not in a multi-
airport city.
Use the following example entry to activate the Bag Tags with Ground Transfer indicator:
GC/ASA/YVR/BGI9/BTGXFR
Entry Explanation
/BTGXFR Slash separator and the Bag Tags with Ground Transfer indicator
Use the following example entry to deactivate the Bag Tags with Ground Transfer indicator:
GC/ASA/YVR/BGI9/X-BTGXFR
Manual Baggage
The Manual Baggage indicator determines the acceptance of manually checked baggage. Set this
indicator to Y (Yes) to allow the airport to accept manual bag tags when there is no printer at the
location. Use this option only in locations without printers
Use the following example entry to allow manual Bag Tags:
GC/ASA/YVR/BGI9/MANBAG
Entry Explanation
Use the following example entry to deactivate the Bag Tags with Ground Transfer indicator:
GC/ASA/YVR/BGI9/X-MANBAG
The Auto Set SC Edit indicator determines whether the SC (Security Conversation) edit code is
automatically set when you issue a passenger a boarding pass or when the flight is closed. If you set
this indicator to N (No), then you must add the Security Edit to every passenger before check-in. This
indicator defaults to Y (Yes.)
Use the following example entry to activate the auto security conversation indicator:
GC/ASA/YVR/BGI9/NOSECR
Entry Explanation
Use the following example entry to deactivate the auto security conversation indicator:
GC/ASA/YVR/BGI9/X-NOSECR
The International Arrival Ticketless OK indicator means acceptance of ticketless NRSA (Non
Revenue Space Available) for international arrivals. This indicator defaults to Y (Yes.)
Use the following entry to activate the International Arr Tktl OK indicator:
Example entry:
GC/ASA/YVR/BGI9/IATKTL
Entry Explanation
The International Departure Ticketless OK indicator means acceptance of ticketless NRSA for
international departures. This indicator defaults to Y (Yes.)
Use the following entry to activate the International Dep Tktl OK indicator:
Example entry:
GC/ASA/YVR/BGI9/IDTKTL
Entry Explanation
The Domestic Arr Tktl OK indicator means acceptance of ticketless NRSA for domestic arrivals. This
indicator defaults to Y (Yes.)
Use the following entry to activate the Domestic Arr Tktl OK indicator: Example entry:
GC/ASA/YVR/BGI9/DATKTL
Entry Explanation
The Domestic Departure Ticketless OK indicator means acceptance of ticketless NRSA for domestic
departures. This indicator defaults to Y (Yes.)
Use the following entry to activate the Domestic Dep Tktl OK indicator: Example entry:
GC/ASA/YVR/BGI9/DDTKTL
Entry Explanation
Basic APPS
The Basic APPS indicator determines whether the airport uses the FAA criteria to determine
passenger profiles. This indicator applies only to U.S.-based airlines and defaults to Y for U.S. Based
carriers.
Use the following example entry to activate the basic APPS indicator:
GC/ASA/YVR/BGI9/APPS
Entry Explanation
Use the following example entry to deactivate the auto security conversation indicator:
GC/ASA/YVR/BGI9/X-APPS
The Auto Set EDIFACT Connection SC indicator determines whether the SC (Security Conversation)
edit code is set for passengers processed through EDIFACT requests. The indicator defaults to Y
(Yes).
Use the following example entry to activate the EDIFACT security conversation edit code indicator:
GC/ASA/YVR/BGI9/EDICON
Entry Explanation
/EDICON Slash separator and the Auto Set EDIFACT Connection SC indicator
Use the following example entry to deactivate the EDIFACT security conversation edit code
indicator:
GC/ASA/YVR/BGI9/X-EDICON
Inter APPS
The Allow Boarding Pass without SC field indicates whether your airline allows issuing boarding
passes from your departure station without adding the SC (Security Conversation) edit code.
Use the following example entry to allow boarding passes without adding the security conversation
edit code:
GC/ASA/YVR/BGI9/BPNOSC
Entry Explanation
/BPNOSC Slash separator and the Allow Boarding Pass W/Out SC indicator
Use the following example entry to not allow boarding passes without adding the security
conversation edit:
GC/ASA/YVR/BGI9/X-BPNOSC
Note The NOSC indicator overrides the BPNOSC and BTNOSC (explained below) settings.
The Allow Bag Tag without SC field indicates whether bag tags can be issued at your airport without
the SC (Security Conversation) edit code.
Use the following example entry to allow bag tags to be issued without adding the security
conversation edit code:
GC/ASA/YVR/BGI9/BTNOSC
Entry Explanation
/BTNOSC Slash separator and the Allow Bag Tag Without SC indicator
Use the following example entry to not allow bag tags to be issued without adding the security
conversation edit code:
GC/ASA/YVR/BGI9/X-BPNOSC
Note The NOSC indicator overrides the BPNOSC and BTNOSC settings.
PRS Active
The Pre-Reserved Active indicator determines whether pre-reserved seats are allowed.
Use the following example entry to turn on pre-reserved seating:
GC/ASA/YVR/BGI9/PRSA
Entry Explanation
Note If you set the PRSA indicator to Y (Yes), it must be set to Y (Yes) for all cities allowing pre-
reserved seating.
The lead-in line is for airports that have multiple aircraft parking positions at one gate. If you set the
Lead-In Line Gate indicator to Y (Yes) the gates lead-in line will appear on the SabreSonic Check-In
display, boarding passes, and in FLIFO. The last alphabetic character of a gate identifier will not print
on boarding passes. For example, if the gate number is 23 and the lead-in lines are 23A and 23B, only
23 will print on the boarding passes.
Use the following example entry to tell the system not to print the last character of the lead-in line
gate number on the boarding passes:
GC/ASA/YVR/BGI9/LLGT
Entry Explanation
Use the following example entry to tell the system to print the last character of the lead-in line gate
number on the boarding passes:
GC/ASA/YVR/BGI9/X-LLGT
Due to increased security regulations, this PRS Boarding Pass Allowed Inbound indicator is currently
not applicable to SabreSonic airlines.
Due to increased security regulations, this PRS Boarding Pass Allowed Outbound indicator is
currently not applicable to SabreSonic airlines.
The Ticket Edit Required indicator determines whether your airline requires a TKT edit code for
paper ticket, or whether an electronic ticket coupon is no longer associated to the flight segment. If
your airline uses E-TKT, then the default is Y (Yes).
Use the following example entry to tell the system to require a TKT edit code:
GC/ASA/YVR/BGI9/TKTREQ
Entry Explanation
Use the following example entry to tell the system not to require a TKT edit code:
GC/ASA/YVR/BGI9/X-TKTREQ
The Auto Set CLE Edit indicator is not applicable to SabreSonic airlines.
The PNR Banner Inhibit Check-In field is limited to carriers who use the Sabre ESV (Enhanced
Synchronization of VCRs) System. If you set the PNR Banner Inhibit Check-In field to Y (Yes), it
displays a message to inhibit check-in when the VCR is out-of-sync (ETO) because of name
mismatch or itinerary change.
Use the following example entry to tell the system to turn on the inhibit check-in message:
GC/ASA/YVR/BGI9/STPCHK
Entry Explanation
/STPCHK Slash separator and the PNR Banner Inhibit Check-In indicator
Use the following example entry to tell the system to turn off the inhibit check-in message:
GC/ASA/YVR/BGI9/X-STPCHK
The Bag Index by Origination Flight Destination indicator allows the baggage index number to be set
by the origin station instead of the destination to assist in baggage sortation at the origin. The
indicator defaults to N (No.)
Use the following example entry to allow the baggage index number to be set by origin station:
GC/ASA/YVR/BGI9/BGIORG
Entry Explanation
/BGIORG Slash separator and the Bag Index By Org Flt/Dest indicator
Use the following example entry to tell the system not to allow the baggage index number to be set
by origin station:
GC/ASA/YVR/BGI9/X-BGIORG
When you set the Print French Boarding Pass indicator to Y (Yes), then the boarding pass prints
bilingually in French and English. This option requires activation, so if desired, please contact
Customer Care.
Use the following example entry to turn on the bilingual boarding pass printing:
GC/ASA/YVR/BGI9/FRENCH
Entry Explanation
/FRENCH Slash separator and the Print French Boarding Pass indicator
Use the following example entry to turn off the bilingual boarding pass printing:
GC/ASA/YVR/BGI9/X-FRENCH
When you mark the Bag Weight indicator to Y (Yes), mandatory baggage weights are required at
check-in.
Use the following example entry to turn on mandatory baggage weights:
GC/ASA/YVR/BGI9/BAGWGT
Entry Explanation
Use the following example entry to turn off mandatory baggage weight:
GC/ASA/YVR/BGI9/X-BAGWGT
Bag Carryon
Set the Bag Carryon field to Y (Yes) to require passenger carry-on baggage to be weighed at check-
in.
Use the following example entry to turn on mandatory carry-on baggage weights:
GC/ASA/YVR/BGI9/BAGCBN
Entry Explanation
Use the following example entry to turn off carryon mandatory baggage weight:
GC/ASA/YVR/BGI9/X-BAGCBN
If the indicator is turned on, TBO is printed on the boarding pass at the transborder airport.
The Transborder BPass TBO indicator is presently not applicable to the SabreSonic community at
large.
A new boarding pass print routine needs to be developed if you request this option.
The option Voucher Information and Lounge Card is visible in the ASA table only if your airline has
requested its activation.
The option allows you to print meal vouchers and lounge invitations onto the boarding pass.
However, there is no sales reporting capabilities.
For meal vouchers, the default currency set in the ASA table is the local currency; but it is also
possible to set another currency if necessary.
The currency, amount, and text for either meal vouchers or lounge invitations will print on the
boarding pass stock.
Note Updates in the ASA table for this field require the EPR keywords TTSCTL or FSGAGT and
a duty code of 8.
Use the following entry to add information for the meal voucher and / or lounge card:
GC/MLV/MV/U0/YOW/CAD/15.00/AIRPORT CAFÉ ONLY
GC/LNC/LC/U0/YOW/VIP LOUNGE
Entry Explanation
/AIRPORT CAFÉ ONLY Slash separator and free text (maximum of 40 characters)
Example responses:
UPDATE SUCCESSFUL
Your airline maintains the Passenger Terminal Information (TML) table, which contains information
pertaining to the physical facilities at an airport designed for handling passengers, baggage, and
cargo. This information appears in various flight displays and prints on boarding passes.
Before you can use on-demand bag tag printing, you must set up a Passenger Terminal Information
table for each station in your network.
The Passenger Terminal Table contains information on what the terminal is called, and what kind of
baggage system the terminal is using.
The INDICATORS ON field in the TML table addresses the Baggage system your airline will use at
that terminal. You may have uncomputerized and manual baggage handling (Baggage Make Up
room), or automatic Baggage Sortation Messages (BSM). You also indicate which type of BSM
your airline selects to use (Termination, Sortation, and/or Reconciliation).
Note Sortation means the system “sorts” the bags and directs them to their final destination.
Reconciliation means the system sorts the bag and also sends information about the passenger,
such as his seat number, or his status (checked-in, boarded, offloaded, etc.).
Example:
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
If you use the BSM system, you will need to proceed and enter information about where the
messages will print or be sent to, and the type of data each message should contain.
BSM Addresses – LNIATA or TTY gives information on either printer addresses (LNIATA), or
teletype addresses instead of printers where the BSM’s will print. You can enter a maximum of two
printer addresses for each BSM type (Sortation, or Reconciliation), and up to three teletype addresses.
Note If there are printer addresses and teletype addresses in the terminal table, the teletype
addresses will take precedence and will be used. In the example below, we only have printer
addresses and no teletype addresses:
BSM ADDRESSES - LNIATA OR TTY
SORTATION PRIME - 710983 RECONCILIATION PRIME - 710983
SORTATION BACKUP – ABC345 RECONCILIATION BACKUP – ABC345
SORTATION TTY 1 - RECONCILIATION TTY 1 -
SORTATION TTY 2 - RECONCILIATION TTY 2 -
SORTATION TTY 3 - RECONCILIATION TTY 3 -
For detailed examples of BSM lessages, please refer to the IATA Passenger Services Conference
Resolutions Manual.
To create a terminal, you must include the airport code and the terminal ID.
Use the following example entry to create a new terminal in the TML table:
GC/TML/YVR/A
Entry Explanation
/TML Slash separator and the Passenger Terminal Information table qualifier
Use the following example entry to delete a terminal from the TML table:
GC/TML/YVR/X-A
Updating a Terminal
Your airline is responsible for the information in the top area of the Passenger Terminal Table
YVR PASSENGER TERMINAL
PSG TML IDENTIFIER 01
PSG TML USAGE CODE DOM
PSG TML NAME VANCOUVER
All information below the PSG TML NAME line addresses the type of Baggage system this terminal
is using. Usually, Sabre Holdings maintain the information in these fields for you. However, your
airline may decide to update the fields and maintain the data yourself, if you have the necessary
keywords and duty codes.
In the following sections, we will look at each line of information in the Terminal Table, and give you
example entries to add or delete any indicator. We will explain the entries in detail.
Note If your airline does not use BSM, skip the following pages and proceed to the next section of
the training guide on Priority Classification Table.
The Passenger Terminal Identifier indicator is an alphanumeric field used where there are multiple
terminals used in a city. You cannot change the Passenger Terminal Identifier indicator once you
create a terminal; you must delete the terminal and create a new one.
Caution If you make an update entry when the terminal does not exist in the Passenger
Terminal Information table, the system creates a new terminal item using the qualifiers you
used in the entry.
If the terminal does exist in the Passenger Terminal Information table and the code for
the airline and the city match, the system considers the update entry as just an update to
the existing terminal, so any qualifier or indicator data included in your entry amends the
corresponding fields in the existing airport item.
Use the Passenger Terminal Use Code Identifier indicator to define whether the terminal is used for
Domestic (USEDOM) or for International (USEINT) flights.
Use the following example entry to update the usage code in the TML table:
GC/TML/YVR/A/X-USEINT or GC/TML/YVR/A/USEDOM
Entry Explanation
Use the following example entry to delete the usage code in the TML table:
GC/TML/YVR/A/USEINT or GC/TML/YVR/A/X-USEDOM
You can enter a 20-character terminal name (20 characters AFTER the NAME indicator) in the
Passenger Terminal Name indicator (NAME) and it will print on the boarding pass.
Use the following example entry to update the existing terminal name in the TML table:
GC/TML/YVR/A/NAMEVANCOUVER
Entry Explanation
Note You cannot delete the terminal name, but you can update it.
Indicators ON
The INDICATORS ON field in the TML table addresses the Baggage system your airline will use at
that terminal. By default the indicators are set to N (No).
Baggage Sortation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
The Baggage Sortation indicator applies to a carrier that uses an automated baggage handling system
which reads the flight number from the bar code on the bag tag number.
Entry Explanation
The Baggage Make Up room indicator applies to a carrier that uses a manual baggage handling
system.
The Baggage Make Up Room indicator is not applicable to SabreSonic airlines.
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
The (IATA) License Plate Baggage Sortation means the system sorts the baggage by bag tag
numbers, and the bag tag numbers do not have a flight number in them.
You must turn License Plate Baggage Sort to Y if your carrier uses BSMs.
The bag tag number is always a 10-digit number. The 10-digit-number breaks down in the following
manner:
• The first digit is the Baggage Index city number as indicated in the ASA table of the
airport
• The next three digits are the airline numeric code
• The remaining six digits are the actual bag tag serial number
Example of a bag tag number: 0139050712 (0-baggage index-139 – airline numeric code – 050712 –
bag tag serial number)
Entry Explanation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
Termination BSM Data means that the system will send a teletype message to a printer, or generate a
message to the TTY or LNIATA addresses defined under BSM addresses to advise the final
destination of the bag.
Entry Explanation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
The Termination BSM Version is only active if you have selected Y to the indicator Termination
BSM and indicates the code for the version of Baggage Source Messages (BSM) the airport uses for
termination BSM.
Currently the Sabre system only supports version 1, which is the IATA standard version.
Entry Explanation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
Entry Explanation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
The Sortation BSM Version is only active if you have selected Y to the indicator Sortation BSM and
indicates the code for the version of Baggage Source Messages (BSM) the airport uses for Sortation
BSM.
If you use Sortation BSM, then you must have Sortation BSM version turned ON.
Although there are various BSM sortation versions ( such as 1, B, or C), the Sabre system supports
version 1 only.
Entry Explanation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
The Reconciliation BSM has the same information as the Sortation BSM, with additional data about
the passenger. There will be an element in the reconciliation BSM that will show the passenger’s
status, or the seat number, for example. With the additional information, the reconciliation BSM may
also generate many messages for an individual passenger, depending on how often the data about the
passenger changes.
Entry Explanation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
The Reconciliation BSM Version is only active if you have selected Y to the indicator Reconciliation
BSM and indicates the code for the version of Baggage Source Messages (BSM) the airport uses for
Reconciliation BSM. In this example, the code for the version of BSM is 1.
Entry Explanation
INDICATORS ON
BAGGAGE SORTATION Y BAGGAGE MAKE UP ROOM N
LICENSE PLATE BAGGAGE SORT N
TERMINATION BSM N
TERMINATION BSM VERSION N
SORTATION BSM N
SORTATION BSM VERSION N
RECONCILIATION BSM Y
RECONCILIATION BSM VERSION 1
RECONCILIATION BAG STATUS N
The Reconciliation Bag Status is only active if you have selected Y to the indicator Reconciliation
Bag Status and indicates whether the bag status is Inactive or Active. This indicator works together
with the Self Tagging table.
At the time a tag is generated from a Self Tagging unit, the BSM that is created will be in Inactive
status. Once the airline personnel accepts the bag, the system will change the BSM status to active.
For more details on Self Tagging, refer to the section on the Self Tagging Table.
Entry Explanation
BSM Addresses – LNIATA or TTY gives information on either printer addresses (LNIATA), or
teletype addresses instead of printers where the BSM’s will print. You can enter a maximum of two
printer addresses for each BSM type (Sortation, or Reconciliation), and up to three teletype addresses.
Sortation Prime
BSM Addresses – LNIATA or TTY gives information on either printer addresses (LNIATA), or
teletype addresses (instead of printers) where the BSM’s will print. You can enter a maximum of two
printer addresses for each BSM type (Sortation, or Reconciliation), and up to three teletype addresses.
Entry Explanation
Sortation Backup
You must establish a Sortation Prime address before you can establish a Backup address.
Use the following example entry to update a sortation backup printer address in the TML table:
Entry Explanation
Reconciliation Prime
Entry Explanation
Reconciliation Backup
You must establish a Reconciliation prime address before you can establish a Reconciliation Backup
address.
Entry Explanation
You can use teletype addresses – a maximum of three – to send the Sortation BSM’s and
Reconciliation BSM’s to. If there are LNIATA printers as well as teletype addresses in the table, the
sytem will send the messages to the teletype addresses.
Sortation TTY
The system uses the Sortation TTY fields to enter up to three teletype addresses to work in
conjunction with the TYPE B sortation field. When the Type B indicator is set to Y (Yes) and a
teletype address exists, the BSM is sent to the to the teletype address.
Always ensure that you have a teletype address if you choose to work with type B indicator.
In the example entries below, the teletype addresses are SEABCK0 and HDQBCU0.
Teletype addresses are composed of the three-letter city code (SEA or HDQ), the two-letter office
designator (BC), and the two-letter airline code(K0 or U0).
Entry Explanation
Reconciliation TTY
The system uses the Reconciliation TTY fields to enter up to three teletype addresses to work in
conjunction with the TYPE B sortation field. When the Type B indicator is set to Y (Yes) and a
teletype address exists, the BSM is sent to the to the teletype address.
Always ensure that you have a teletype address if you choose to work with type B indicator.
Entry Explanation
Every BSM message contains mandatory elements as dictated by IATA procedures. Additionally,
you may select OPTIONAL BSM ELEMENTS you wish to include in the message. By default the
optional elements are set to N (No).
For each element, the system specifies Sortation BSM or Reconciliation BSM.
A Reconciliation BSM message contains the same information as the Sortation BSM message. In
addition, it also has passenger data such as check-in status, and/or seat number.
For each optional element we will provide the entry to turn the element ON or OFF, for both BSM
types of messages – Sortation and Reconciliation.
Flight numbers and passenger data used in examples are fictitious. For more information on BSM,
please consult the IATA Passenger Services Conference Resolutions Manual.
Entry Explanation
Entry Explanation
FQTV Number
Entry Explanation
Corporate/Group Name
Entry Explanation
Entry Explanation
This field gives the information about the LNIATA of the printer used for issuing the bag tags
Entry Explanation
Entry Explanation
The Exception Date element covers data such as VIP, or baggage re-routing when alternate space
check-in takes place.. Alternate space check-in means a passenger wishes to go on an earlier or later
flight to the same destination on the same day.
The Exception Data element displays in the BSM with .E
Example: .E/VIP
Entry Explanation
Internal Data
Entry Explanation
Baggage Security
The Baggage Security element in a BSM displays with .X and indicates the passenger is a Selectee.
Example: .X/SEL
Note The Sabre system only supports the above format. IATA may have other formats available.
Type B
Type B element indicates that you are sending the BSM messages to a teletype address. If you do not
use teletype addresses, you leave Type B as N.
Type B (teletype) and Sortation Prime and Backup information are mutually exclusive.
Entry Explanation
The Transfer BSM element is mandatory if you have the Baggage Sortation indicator ON,and
displays in the BSM with .F
For a passenger with a connecting flight (or flights), the system will send a message to the transfer (or
next downline station) when he checks-in at the original departure station.
Scenario: The passenger is traveling BEY to LCA on CY 343, then connects from LCA to STN on
CY 562.
If you use BSM sortation and reconciliation, the system will send a BSM the originating city BEY
and to the connecting city LCA.
Example BSM sortation and reconciliation messages to BEY:
.V/1LBEY (V means Version /1 means Version 1, L means Local, BEY is originating city)
.F/343 (.F element for transfer / 343 is the connecting flight number)
.S/Y/C/10A (.S element means Reconciliation data / Y means Yes, authority to load / C
means passenger status Checked-in / 10A is the seat number)
Example BSM sortation and reconciliation messages to LCA, referring to the connecting flight:
.V/1TLCA (Version 1, T means Transfer, LCA is connecting city)
.S/Y/C/12B (.S element for Reconciliation data / Y means Yes authority to load / C means
passenger status is Checked-in / 12B is the seat number)
.F/562 (.F Transfer information on Flight 562 to LCA)
Entry Explanation
The Priority Classification Table (or PRC Table) determines the order of how the system lists
passengers who are added to the Priority List of each flight.
Passengers who need to be on a priority list include revenue passengers (oversales, alternate space
and others), positive space passengers (deadhead and crew, executives and others), and any other
classification of employee and non-revenue travelers.
For each type of passenger that will go to the priority list, the PRC table adds
• a priority code and a free text explanation of that code
• a priority number (see explanation later in this lesson)
• a passenger type code (see explanation later in this lesson)
• the sort sequence type (see explanation later in this lesson)
Each type of passenger needs to be further defined by turning indicators ON or OFF . Turning Off
will show in the table as N (No) and turning On will show as Y (Yes).
There are approximately 30 indicators for each classification type, including many that do not apply
to SabreSonic airlines. These non applicable indicators will always show N in the table.
Note Your airline initially creates this table, then either your airline can maintain it or you can send
update requests to Customer Care. It is important that any changes only be completed during
off-peak hours to minimize any check-in issues that may occur due to priority code placement.
Your airline should submit a request for adding, deleting or changing a priority code at least one
week in advance through Customer Care. Sabre only makes changes to this table during off-
peak hours generally on a Monday night /early Tuesday morning (Central U.S. time).
PRIORITY NUMBER 0
PASSENGER TYPE CODE F
SORT SEQUENCE TYPE C
USE FOR AUTOLIST TIER LVL
INDICATORS ON
ELIGIBLE FOR OVERSALE Y
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER N
PERSONAL TRAVEL N
BUSINESS TRAVEL N
NEED AUTHORIZATION N
EMPLOYEE NUMBER NEEDED FOR TICKETLESS N
AUTOMATIC PRIORITY LISTING WITH PRS N
ELIGIBLE FOR APPS EMPLOYEE TRAVEL N‡
APPS FREE TICKET TRAVEL N
ISSUE OUTBOUND BOARDING PASS N
RESTRICTED FOR CHECK-IN ENTRY N
TKT REQUIRED FOR NOREC N
ALLOWED FOR A-TYPE PASSENGER N
SECONDARY SORT FOR POSITIVE SPACE N
SECONDARY SORT FOR REVENUE PASSENGER N
OA EMPLOYEE ID REQUIRED N
NO REC CHECK-IN ALLOWED Y
EXPANDED OA JUMPSEAT N
SECONDARY DATE TIME STAMP N
EXPANDED CODE EXISTS N
SORT BY INV BOOKING CODE N
OA ELECTRONIC OR PAPER TICKET REQUIRED N
STANDBY ELIGIBILITY CHECK N
Each priority code has a two- or three-letter code – in this example, OS is the code for Oversale.
For each priority code, you assign a Priority Number, indicate the Passenger Type code, and the Sort
Sequence Type. Each priority code is further defined by a list of indicators, which are options that
are either Y (Yes, apply to the priority code) or N (No, do not apply to the priority code).
Note Although listed in the table, many fields in the table are not applicable to Sabre Sonic
Airlines.
PRIORITY NUMBER 1
PASSENGER TYPE CODE F PT
SORT SEQUENCE TYPE C SRT
USE FOR AUTOLIST TIER LVL AUT
INDICATORS ON
ELIGIBLE FOR OVERSALE N CHKOS
PROMOTABLE AT THRU CITIES Y THRU
COMMUTER RESTRICTED N CR
CHECK-IN BOARD CITY ONLY N BRD
TIME RESTRICTED N TM
PROMOTE E-BOOKED N E
PROMOTE MEAL-LISTED NRSA N PML
DEADHEAD CREW MEMBER N DH
PERSONAL TRAVEL N PER
BUSINESS TRAVEL N BUS
NEED AUTHORIZATION N NAUTH
EMPLOYEE NUMBER NEEDED FOR ELECTRONIC N EMPL
AUTOMATIC PRIORITY LISTING WITH PRS N APL
ELIGIBLE FOR APPS EMPLOYEE TRAVEL N EMST‡
APPS FREE TICKET TRAVEL N FTKT
ISSUE OUTBOUND BOARDING PASS N IOBP
RESTRICTED FOR CHECK-IN ENTRY N RSCK
TKT REQUIRED FOR NOREC N TKT
ALLOWED FOR A-TYPE PASSENGER N ATYP
SECONDARY SORT FOR POSITIVE SPACE N SPOS
SECONDARY SORT FOR REVENUE PASSENGER N SREV
OA EMPLOYEE ID REQUIRED N OAID
NO REC CHECK-IN ALLOWED N NOREC
EXPANDED OA JUMPSEAT N OAEXP
SECONDARY DATE TIME STAMP N SECDT
EXPANDED CODE EXISTS N EXPCD
SORT BY INV BOOKING CODE N SBC
OA ELECTRONIC OR PAPER TICKET REQUIRED N OANR
STANDBY ELIGIBILITY CHECK N SBF
In the following sections, you will see definitions of each of the fields and their corresponding
indicator. You will also see example entries showing you how to update the indicators.
Priority numbers determine the hierarchy of your priority codes, the lower the number, the higher the
priority. When you create a new priority classification code in an existing table, you use a position
indicator to tell the system where the new code should reside in the table. The following are valid
position indicators:
0 - Add as the first priority code (highest priority). When you enter the first priority code
(PRO) into the Priority code table, do not enter an existing priority code after the 0 (zero).
A - Insert the new priority code directly after (lower priority than) the specified existing
priority code.
B - Insert the new priority code directly before (higher priority than) the specified existing
priority code.
E -Add the new priority code at the same level (same priority) or equal to the specified
existing priority code
To display the details of only a specific priority code, you can add the code to the end of the entry.
For example, to display only the priority code DHD (Dead Head Crew), you would use the following
entry:
GC*PRCDHC
The response is the redisplay of the whole table beginning at the top (highest priority).
To display only the new code, use the entry GC*PRCNRSB
Caution
When you create or delete a priority classification code, the system assigns or removes a seat
assignment priority number and adjusts the other priority numbers accordingly.
Exercise extreme caution when deleting or reordering codes in the Priority Classification Table;
the recommendation is to avoid updating the codes while passengers are on a standby list. It is
important to remove a code only during off-hours; otherwise, you will affect any passenger traveling
on that code.
In the following sections, you will see definitions of each of the fields and their corresponding
indicator. You will see example entries showing you how to update the indicators.
When you update the Priority Classification table, use a “GC/PRC” entry, the priority code, and an
extra slash (/) for the title along with the indicator you are updating. If you leave off the slash for the
title, then the system assumes you are changing the title and updates it instead of the indicator.
Example entry:
GC/PRCDHD//THRU
The above entry updates priority code DHD and turns the indicator THRU to Y.
Priority Number
PRIORITY CLASSIFICATION
DHD DEADHEAD CREW
PRIORITY NUMBER 1
PASSENGER TYPE CODE P
SORT SEQUENCE TYPE S
USE FOR AUTOLIST TIER LVL
The Priority Number assigns the sequential seat assignment number to indicate the order of the
classification in the classification hierarchy. The system automatically issues the number depending
on the placement of the priority classification in the table.
Remember, the lower the number, the higher the priority.
Passenger Type
PRIORITY CLASSIFICATION
DHD DEADHEAD CREW
PRIORITY NUMBER 1
PASSENGER TYPE CODE P
SORT SEQUENCE TYPE S
USE FOR AUTOLIST TIER LVL
The Passenger Type (PT) indicator adds the passenger type to the classification. There are four valid
passenger types:
E - Employee
F - Full Fare
P - Positive Space
S - Revenue Stand-by
Entry Explanation
Slash separator for the name field (required or name field will be updated instead of
/
the PT field)
PRIORITY CLASSIFICATION
DHD DEADHEAD CREW
PRIORITY NUMBER 1
PASSENGER TYPE CODE P
SORT SEQUENCE TYPE S
USE FOR AUTOLIST TIER LVL
The Sort Sequence Type indicates whether the priority classification is sorted by Seniority date or by
Check-in time.
• Type S indicates Seniority date
• Type C indicates Check-in time
Use the following example entry to update the Sort Sequence Type indicator from S (Seniority Date)
to C (Check-In Time):
GC/PRCNRSB//SRTC
Entry Explanation
Note You must request Sabre Holdings to activate the Sort Sequence field for you to change the
sort sequence from check-in time to seniority. You must give Sabre at least three weeks
advanced notice to complete this request.
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Eligible for Oversale field indicates whether the classification is eligible for oversale
compensation. By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Eligible for Oversale indicator:
GC/PRCNRSB//CHKOS
Entry Explanation
Use the following example entry to turn off the Eligible for Oversale indicator:
GC/PRCNRSB//X-CHKOS
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Promotable at Thru Cities field indicates whether the classification receives preference at through
cities. For example, if the standby passenger were flying from DFW to ALT to CHI, when they
arrived at ATL, they would have priority boarding over a passenger boarding from ATL. By default,
this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Promotable at Thru Cities indicator:
GC/PRCNRSB//THRU
Entry Explanation
Use the following example entry to turn off the Promotable at Thru Cities indicator:
GC/PRCNRSB//X-THRU
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Commuter Restricted field indicates whether the classification is restricted to commuters only.
By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Commuter Restricted indicator:
GC/PRCNRSB//CR
Entry Explanation
Use the following example entry to turn off the Commuter Restricted indicator:
GC/PRCNRSB//X-CR
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Check-In Board City Only field indicates whether the classification is restricted to check-in only
at the board city. By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Check-In Board City indicator:
GC/PRCNRSB//BRD
Entry Explanation
Use the following example entry to turn off the Check-In Board City indicator:
GC/PRCNRSB//X-BRD
Time Restricted
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Time Restricted field indicates whether the classification is restricted from check-in until a
predefined time prior to departure. By default, this indicator is set to N (No) or “off”.
Entry Explanation
Use the following example entry to turn off the Time Restricted indicator:
GC/PRCNRSB//X-TM
Promote E-Booked
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Promote E-Booked field indicateswhether the classification receives preference if booked in E
inventory. By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Promote E-Booked indicator:
GC/PRCNRSB//E
Entry Explanation
Use the following example entry to turn off the Promote E-Booked indicator:
GC/PRCNRSB//X-E
Note It is up to to your airline to use and promote the E class of inventory for employee travel.
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Promote Meal Listed NRSA field indicates whether non-revenue passengers within this
classification receive preference if they are flight listed 12 hours prior to a domestic departure and 48
hours prior to an international departure.
Use the following example entry to turn on the Promote Meal Listed NRSA indicator:
GC/PRCNRSB//PML
Entry Explanation
Use the following example entry to turn off the Promote Meal Listed NRSA indicator:
GC/PRCNRSB//X-PML
INDICATORS ON
ELIGIBLE FOR OVERSALE N
PROMOTABLE AT THRU CITIES Y
COMMUTER RESTRICTED N
CHECK-IN BOARD CITY ONLY N
TIME RESTRICTED N
PROMOTE E-BOOKED N
PROMOTE MEAL-LISTED NRSA N
DEADHEAD CREW MEMBER Y
PERSONAL TRAVEL N
BUSINESS TRAVEL Y
The Deadhead Crew Member field indicates whether the classification qualifies as deadheading crew.
By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Deadhead Crew Member indicator:
GC/PRCNRSB//DH
Entry Explanation
Use the following example entry to turn on the Deadhead Crew Member indicator:
GC/PRCNRSB//X-DH
Personal Travel
Business Travel
Need Authorization
The Employee Number Needed for Ticketless indicator is not applicable to SabreSonic airlines.
The Automatic Priority Listing with PRS field indicates whether the classification is automatically
put on the priority list if they hold a pre-reserved seat.
By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Automatic Priority Listing with PRS indicator:
GC/PRCNRSB//APL
Entry Explanation
/APL Slash separator and Automatic Priority Listing with PRS indicator
Use the following example entry to turn off the Automatic Priority Listing with PRS indicator:
GC/PRCNRSB//X-APL
The APPS indicator applies to U.S. based airlines and U.S. domestic flights only.
An airport using APPS means it uses the FAA ( Federal Aviation Administration) criteria to
determine passenger profiles. Your ASA (Airline Serving Airport) table determines Y or N to Basic
APPS.
If the Eligible for APPS Employee Travel indicator is turned to Y, it means the airport uses APPS,
and the employee traveler under this classification could potentially appear on the airport APPS list.
Please check internally for your carrier’s specific procedures regarding APPS travel.
By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the Eligible for APPS Employee Travel indicator:
GC/PRCNRSB//EMST
Entry Explanation
/EMST Slash separator and Eligible for APPS Employee Travel indicator
Use the following example entry to turn off the Eligible for APPS Employee Travel indicator:
GC/PRCNRSB//X-EMST
The APPS Free Ticket Travel indicator is not applicable to SabreSonic airlines.
The Issue Outbound Boarding Pass field indicates whether you print boarding passes for standby
employees on connecting flights at the origination or at each up-line station. By default, this indicator
is set to N (No) or “off”.
Use the following example entry to turn on the Issue Outbound Boarding Pass indicator:
GC/PRCNRSB//IOBP
Entry Explanation
Use the following example entry to turn off the Issue Outbound Boarding Pass indicator:
GC/PRCNRSB//X-IOBP
NEED AUTHORIZATION N
EMPLOYEE NUMBER NEEDED FOR TICKETLESS N
AUTOMATIC PRIORITY LISTING WITH PRS N
ELIGIBLE FOR APPS EMPLOYEE TRAVEL N
APPS FREE TICKET TRAVEL N
ISSUE OUTBOUND BOARDING PASS N
RESTRICTED FOR CHECK-IN ENTRY N
TKT REQUIRED FOR NOREC N
Use the following example entry to turn on the Restricted for Check-in entry indicator:
GC/PRCNRSB//RSCK
Entry Explanation
Use the following example entry to turn off the Restricted for Check-in entry indicator:
GC/PRCNRSB//X-RSCK
The Ticket Required for NOREC indicator is not applicable to SabreSonic airlines.
The Allowed for A-Type Passenger indicator is not applicable to SabreSonic airlines.
The Secondary Sort for Positive Space indicator is not applicable to SabreSonic airlines.
The Secondary Sort for Revenue Passenger indicator is not applicable to SabreSonic airlines.
OA Employee ID Required
The Secondary Date Time Stamp indicator is not applicable to SabreSonic airlines.
The Sort By INV Booking Code indicator is not applicable to SabreSonic airlines.
The OA Electronic or Paper Ticket Required field indicates whether you must electronically ticket
employees from other airlines. By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the OA Electronic or Paper Ticket Required indicator:
GC/PRCNRSB//OANR
Entry Explanation
Use the following example entry to turn off the OA Electronic or Paper Ticket Required indicator:
GC/PRCNRSB//X-OANR
Your airline maintains the Temporary Airport Restrictions and Embargoes table which houses special
rules that apply, during a specified period, for INBOUND flights to a specific airport. The rules are
classified as restrictions or embargoes. For example, your airline might use this table to impose a
travel embargo for certain levels of non-revenue passengers to a new destination in order to reduce
the confusion the additional passenger load can cause.
You can also add baggage restrictions to govern how many pieces of baggage passengers can check
for a flight.
Displaying the Temporary Airport Restrictions and Embargoes table requires the following:
EPR keywords: TTSCTL and FSGAGT
Use the following example entry to displays this table:
GC*EMB/U0/PHX/NRSA
Entry Explanation
GC* Primary system display action code
/U0 Slash separator and Carrier Code (optional, defaults to the airline code in the AAA)
/NRSA Slash separator and the NRSA (Non-Revenue Space Available) indicator
(Use BAG for the Baggage Rules indicator)
The following example displays the NRSA response with the most recent end date at the top showing
the restriction start date and end date and the NRSA Priority code:
U0 PHX TEMPORARY AIRPORT RESTRICTIONS/EMBARGOES
START 15JAN END 21JAN
NRSA SA0P
You will use indicators and qualifiers to add temporary airport restrictions and embargoes into the
table. Embargo table indicators default values represent the normal case, or expected condition.
Setting the indicator to Y (Yes) or “On” overrides the normal case, causing an exception.
The following are embargo table indicators:
• BAGRST - Baggage restriction type
• BAGEMB - Baggage embargo type
• NOPET - Pet restriction
The following embargo qualifiers limit restrictions to certain criteria:
• NRSA - Non-revenue passenger with priority code (example NRSA11)
• CB - Allowable checked bag count (example CB2). You must include this option with a
count in any entry that adds either a BAGRST or BAGEMB option.
Updating the Temporary Airport Restrictions and Embargoes table requires:
EPR keywords: FSGAGT
Duty code: ‡ (the Cross-of-Lorraine)
In the following sections, you will see example entries on how to add different Temporary Airport
Restriction and Embargo along with a table explaining each piece of the entry.
The Baggage Restriction indicator uses an N (No) or Y (Yes) to allow you to check as many bags as
desired, but all bags beyond the restriction amount will be automatically marked as “voluntary
separation” on the bag tag. By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the indicator to allow as many bags as desired:
GC/EMB/U0/YVR/12JUL-15JUL/BAGRST
Entry Explanation
- Date separator
Use the following example entry to turn off the indicator to allow as many bags as desired:
GC/EMB/U0/YVR/12JUL-15JUL/X-BAGRST
The Baggage Embargo indicator uses an N (No) or Y (Yes) to restrict the number of bags allowed.
For example: if the embargo is no more than one bag, regardless of the number of bags in the check-
in entry, the system will only print one bag tag. If you add an embargo to a city, it would apply INTO
that city from any city. By default, this indicator is set to N (No) or “off”.
Use the following example entry to turn on the indicator to restrict the number of bags allowed:
GC/EMB/YVR/07AUG-10AUG/BAGEMB/CB2
Entry Explanation
The Pet Embargo Indicator uses an N (No) Y (Yes) to determine whether pets are prohibited from
travel to certain destinations, on certain flights for certain dates, or on certain equipment types. By
default, this indicator is set to N (No) or “off”. Entering a Y (Yes) in this field means your airline
does not accept pets as checked baggage, while an N (No) indicates that your airline does accept pets
as checked baggage.
Use the following example entry to turn on the indicator to not allow pets as checked baggage on
flights to this airport:
GC/EMB/U0/YVR/12JUL-25JUL/NOPET
Entry Explanation
Use the following example entry to turn off the indicator to not allow pets as checked baggage on
flights to this airport:
GC/EMB/YVR/12JUL-25JUL/X-NOPET
You must always use the CB (Allowable Checked Bag Count) entry along with the BAGRST or
BAGEMB entry to determine the number of allowable checked bags.
Use the following example entry to update the indicator to 2 to for the number of allowable checked
bags.
GC/EMB/YVR/07AUG-10AUG/CB2
Entry Explanation
/CB Slash separator and the Allowable Checked Bag Count indicator
Use the following example entry to remove the number of allowable checked bags.
GC/EMB/YVR/07AUG-10AUG/X-CB2
To change the baggage count for a station, there are three steps:
1. Turn off the baggage embargo indicator making sure you specify the same time period used
when the BAGEMB was turned on.
2. Remove the baggage count, making sure that you specify the same time period used when the
CB was first entered.
Use the following example entries to update the indicator from 2 to 3 for the number of allowable
checked bags.
GC/EMB/YVR/07AUG-10AUG/X-BAGEMB
GC/EMB/YVR/07AUG-10AUG/X-CB
GC/EMB/YVR/07AUG-10AUG/BAGEMB/CB3
Example entry:
GC/EMB/DCA/12APR-12APR/NRSASB7
Entry Explanation
The above entry would restrict non-revenue passengers with priority code SB7 from traveling on
12APR.
Use the following entry to delete all restrictions for Non Revenue traveling for the date or date range
GC/EMB/DCA/12APR-12APR/X-NRSA
Your airline creates and maintains the Airline Directional Airport Pair table (or AAP table) which the
system uses to define various functions associated with a specific city pair, such as customs list
generation, security checks and bag tag functions. You use the AAP table to designate the markets for
which your airline should transmit a passenger list to U.S. Customs at close of flight.
For example, not all flights arriving in SEA cause the system to send a passenger list to Customs, but
flights specifically flying between TYO and SEA would. If you set the Auto Send option to Y (Yes)
for the TYOSEA city pair in this table, the system automatically transmit the customer list.
The SabreSonic Check-In system will check the AAP table when a passenger checks-in for a
connecting flight. Example: if the passenger flies STL to SEA to TYO, the system will know at SEA
to check the table and to ensure that the passenger meets all requirements before a successful check-in
to the final destination.
When you display information for a city pair, the SabreSonic Check-In system shows you whether
baggage travelling between the pairs is subject to security checks, whether you can issue on-demand
bag tags, and whether the city pair is domestic travel.
Displaying the AAP Information table requires the following:
EPR keywords: TTSCTL and FSGAGT
Use the following example entry to display a listing of the AAP Information Table for your airline in
alphabetical order by boarding city:
GC*AAP
Entry Explanation
GC* Primary system display action code
The following is an example response and each of the fields in this table are discussed in detail later:
GC*AAP«
U0 AIRLINE DIRECTIONAL AIRPORT PAIR
ORIG DEST AUTO DOM BAG CURB GATE PRT PSPT PCTC PRM SHRT BRD
SEND SEC ODBT SEC I94 REQ REQ BNR API TM
AUA AUS Y N Y N N N Y Y N N
AUA JFK Y N Y N N N Y Y N N
AUS AUA Y N Y N N N Y Y N N
BDA JFK Y N Y N N N Y Y N N
CEB GTP N Y N N N N N N N N
CEB LAX Y N Y N N N Y N N N
CUN MCO Y N Y N N N Y Y N N
CUN SLC Y N Y N N N Y Y N N
DFW MAN Y N N N N N N N N N
DVO LAS N N N N N N N N N N
DVO LAX Y N Y N N N Y Y N N
FLL SDQ Y N Y N N N Y Y N N
FLL YYZ N N Y N N N Y Y N N
HDQ CRC N N Y N N N N N N N
HDQ DFW N N Y N N N N N N N
HNL YVR Y N Y N N N Y Y N N‡
Use the following example combination entry to add the city pair and all of the requirements:
GC/AAP/U0/TYOSEA/AUTO/DOM/BAGSEC/PSPTREQ/PCTCREQ
Entry Explanation
GC Primary table action code
/TYOSEA Slash separator and the board /off point of the city pair
Use the following example entry to delete the city pair and all of the requirements from the table:
GC/AAP/X-YVRDFW
You will learn about the definitions of each field in the AAP Information table and the corresponding
indicator in the following sections. In each section, you will see example entries showing you how to
update the indicator along with a table explaining each piece of the entry. You will also see example
entries on how to remove the indicator when applicable.
The ORIG and DEST fields are the three letter origination and destination city codes used to set up a
directional pair in the AAP Table. Once you create a city pair in the table, you cannot change the
cities, you have to delete the city pair and create a new entry in the table
The AUTO indicator is to determine if an automatic transmission of the customs list is sent at close
or PDC of a flight. This option requires activation. Please contact Customer Care to activate this
option for your airline.
Use the following example entry to turn on the auto transmission of the customs list:
GC/APP/YVRLAS/AUTO
Entry Explanation
/YVR Slash separator and the example origination city code for Vancouver
Use the following example entry to turn off the auto transmission of the customs list:
GC/AAP/YVRLAS/X-AUTO
Flight Type
If you set the DOM indicator to Y (Yes), the system will consider the city pair as domestic and if it is
set to N (No), the system considers it International.
Use the following example entry to designate the flight as domestic:
GC/AAP/YVRLAS/DOM
Entry Explanation
/YVR Slash separator and the example origination city code for Vancouver
If the BAGSEC indicator is set to Y (Yes), the flight is a positive bag match flight and passengers
cannot check a bag without a boarding pass. The flight will use a PULL list, which is a list of all
checked-in passengers with bags that have not yet boarded the flight. In addition, bag tags must be
reconciled if the passenger’s seat is returned. The system does not allow Curbside baggage check-in.
Use the following example entry to turn on the baggage security:
GC/AAP/YVRLAS/BAGSEC
Entry Explanation
/YVR Slash separator and the example origination city code for Vancouver
Use the following example entry to turn off the baggage security:
GC/AAP/YVRLAS/X-BAGSEC
The Curbside On-Demand Bag Tag indicator is not applicable to SabreSonic airlines.
The PSPTREQ indicator determines if a passport number is required before a passenger can check-in
or obtain a seat reassignment.
Use the following example entry to require passports before check-in:
GC/AAP/YVRLAS/PSPTREQ
Entry Explanation
Use the following example entry to not require passports before check-in:
GC/AAP/YVRLAS/X-PSPTREQ
If the PCTCREQ indicator is set to Y (Yes), then passenger contact information is required before a
passenger can check-in or obtain a seat reassignment.
Use the following example entry to require passenger contact information before check-in:
GC/AAP/YVRLAS/PCTCREQ
Entry Explanation
Use the following example entry to not require passenger contact information before check-in:
GC/AAP/YVRLAS/X-PCTCREQ
Premium Banner
This functionality refers to a shortened version of API (Advanced Passenger Information) for specific
city pairs. The default is set to N as it may not apply to your airline.
Boarding Time
This functionality refers to the boarding time for flights in specific city pairs. The default is set to N
or the clumn is left blank as it may not apply to your airline.
Sabre Holdings sets up the Airline Seat Restrictions table (or ASR table) based on your airline data
collector. You should direct any change or update requests to Customer Care.
The ASR table displays the seat assignment restrictions for your airline. These restrictions control
seat assignments of passengers, based on comparisons of passenger characteristics to seat
characteristics. For example, your airline may prohibit handicapped passengers (this is a passenger
characteristic) from being assigned an exit row seat (this is a seat characteristic). The passenger
characteristics are usually IATA SSR codes.
Displaying the Airline Seat Restrictions table requires the following:
EPR keywords: TTSCTL and FSGAGT
Use the following example entry to display seating restrictions for your airline.
GC*ASR
Entry Explanation
GC* Primary system display action code
The following is an example response showing the passenger characteristics (PSG CHAR) and the
seat characteristics (SEAT CHAR):
U0 AIRLINE SEAT RESTRICTIONS
PSG CHAR SEAT CHAR
BLND EXIT ROW
CHD EXIT ROW
DEAF EXIT ROW
INF EXIT ROW
INFANT RESTR
LANG EXIT ROW
OXYG BULKHEAD
EXIT ROW
PETC BULKHEAD
UMNR EXIT ROW
WCHR EXIT ROW
WCOB EXIT ROW
To display just a specific characteristic in the table add the characteristic to the end of the display.
For example, to only see seat restricts for wheelchairs you would enter GC*ASRWCHR.
Note If you enter less than the required amount of characters in a request, the system displays the
first code or characteristic that starts with those letters. Example: if you enter WCH, the system
displays the first passenger characteristic it finds that begins with WCH.
The Gate Table is maintained by your airline and contains a list of gates, the association of gates to
terminals and baggage claim areas at a specific airport. The gate may be exclusive to your airline or
shared by multiple carriers.
You must have a table for each gate that your airline uses, for inbound or outbound flights. Once you
have established a gate table, then you may assign that gate to a flight.
This table also lets you set temporary changes in a gate’s use for irregular circumstances (such as
construction), by entering a start and end date.
Note The Passenger Terminal Identifier in the Gates table must match the terminal identifier in the
Passenger Terminal Information table (GC*TML) to ensure that BSM works correctly. If the
Terminal ID in the two tables does not match each other, the BSM system will error out.
You can update date ranges to be applied to each item so those items can be redefined when irregular
circumstances (such as construction) force a temporary change in the gate’s use. You may only add or
update gate information for your current AAA location.
To make any updates within the Gate table, you must enter the following elements:
• GC entry
• Gate indicator
• Airport Code
• Gate Identifier
• Effective Date
• Date Separator (-)
Updating the Gates table requires the following:
EPR keyword: SELECT
Duty code: 7 or ‡ (the Cross-of-Lorraine)
UAT keyword: CONTRL on the LNIATA where the entry is made.
Use the following example entry toCreate a gate at your location:
GC/GATE/DTW/A10/21JUN11-
Entry Explanation
GC Primary table action code
To update a gate, you use the same entry used (along with variables) when creating a gate. In the
following sections, definitions of each of the fields and their corresponding indicator will be
explained. You will be provided example entries showing you how to update the indicators.
To associate a specific gate with a terminal, you add the Terminal Identifier. A terminal must first be
created in the Passenger Terminal Information table (TML). The Gate indicator TM must precede the
terminal ID in any entry.
Use the following example entry to associate a terminal with a gate:
GC/GATE/YVR/35A/25JUN10-/TM01
Entry Explanation
/TM Slash separator and the Terminal ID indicator
You cannot update the Passenger Terminal Name in the Gate table; it is automatically populated from
the TML table when you associate a gate with a terminal.
A Gate Effective Date and Gate Discontinue Date represent a temporary change in the gate’s use,
such as when irregular circumstances (such as construction) force a gate change. If there is no Gate
Discontinue Date, this signifies a permanent change.
If a discontinued date (end date) is not included in any entry, it is assumed to be infinity. If a
discontinued date is included, the date cannot be more than 330 days past the current date. Once an
end date is past for a temporary item, the Gate update is deleted by Nightly File Maintenance.
Use the following example entry to add a gate discontinue date:
GC/GATE/YVR/ST1/22JUN10-30JUN10
Entry Explanation
30JUN10 An example Discontinue Date (end date)
Use the following example entry to remove a discontinue date from a gate:
GC/GATE/YVR/ST1/22JUN10-
The Gate Status Code indicator is used to change the gate status to A (Active) or I (Inactive). The
default status for all gates is A (Active).
Use the following example entry to change a gate status to I (Inactive):
GC/GATE/YYC/33B/06MAY11-/STATI
Entry Explanation
/STAT Slash separator and the Gate Status Code indicator
I I for Inactive
The BC indicator (along with the baggage claim area number) lets you assign a baggage claim to the
specified gate information.
Use the following example entry to associate a baggage claim area to a gate:
GC/GATE/YYC/33B/06JUL11-/BC15
Entry Explanation
/BC Slash separator and the Baggage Claim Code indicator
Use the following example entry to remove a baggage claim area to a gate:
GC/GATE/YYC/33B/06JUL11-/X-BC15
An Airport Zone Code indicates an airport area. A zone may be used when the airline has multiple
terminals at a hub station. For example, a ramp zone, zone 1, zone A, etc.
Use the following example entry to add an airport zone code to a gate:
GC/GATE/YYC/33B/06JUL11-/ZONE6
Entry Explanation
/ZONE Slash separator and the Airport Zone Code indicator
Use the following example entry to remove an airport zone code to a gate:
GC/GATE/YYC/33B/06JUL11-/X-ZONE6
Use the following example entry to remove a gate phone number to a gate:
GC/GATE/YVR/35A/25JUN10-/X-GATE111-222-3333
The jet bridge phone number field requires numeric characters and is limited to a maximum of 18
characters.
Use the following example entry to add a jet bridge phone number to a gate:
GC/GATE/YVR/35A/25JUN10-/JET999-888-7777
Entry Explanation
/JET Slash separator and the Jet Bridge Phone Number indicator
Use the following example entry to remove a jet bridge phone number to a gate:
GC/GATE/YVR/35A/25JUN10-/X-JET999-888-7777
When you assign a gate, the BSMs will be sent to the terminal.. You must be AAA’d into the city
where you are assigning the gate.
Use the following example entry to assign a departure and an arrival gates:
GG¤2/10MAR-PERM/DGC10/AGC10
The following is an example response:
FLIGHT PERIOD ARR GATE BAG AREA DPTR GATE
U0 2 10MAR-PERM C10 / 11 C10 /
Entry Explanation
GG@ Primary action code and the add gate indicator
Note You can separate the entry and assign the gate separately.
GG¤2/10MAR-PERM/DGC10
GG¤1234/10MAR-PERM/AGD16
The SabreSonic Check-In System transactions and table updates for certain types of transactions that
users perform are stored for up to 30 days or 100 entries (whichever is greater) per transaction type.
For all transaction history entries, the slash and airline code after the indicator is optional; the default
is your carrier or your dedicated carrier.
Note Although the storage time of the history is determined as above, there may be situations when
the system may act differently. You may retrieve the history of an ASA table and see the last
item dated further out than the maximum time allowed. The reason is – if nothing has occurred
that would cause a more recent item to be written to history, the system will hold on to the last
item recorded until something more recent comes in to take its place.
Displaying the Check-In Table Transaction History table requires the following:
EPR keywords: TTSCTL and FSGAGT
Duty code: ‡ (the Cross-of-Lorraine)
Use the following example entry to display the Check-In Table Transaction History table:
GC*H/PC
Entry Explanation
GC* Primary check-in system display action code.
H History Indicator
The following example response displays with the most recent activity at the top and reads showing:
1. The updater’s AAA city 4. The date and time the update was made (in U.S.
Central time)
2. The updater’s duty code and sine
5. The set address where the update entry was made
3. The updater’s home station code
6. The update entry itself
Airport
The Airport entry displays the transaction history and any updates for a specific airport location.
Use the following example entry to display this history:
GC*H/AA/YVR
Entry Explanation
Aircraft
The Aircraft entry displays the transaction history and any updates for a specific aircraft by the nose
or tail number.
Use the following example entry to display this history:
GC*H/AC/T4323
Entry Explanation
The Airline Directional City Pair entry displays the transaction history and any updates for city pairs
for a specific origination.
Use the following example entry to display this history:
GC*H/AP/CLE
Entry Explanation
/AP Slash separator and Airline Directional City Pair History indicator
Configuration Aircraft
The Configuration Aircraft entry displays the transaction history and any updates for an aircraft
configuration.
Use the following example entry to display this history:
GC*H/CF/U0
Entry Explanation
/U0 Slash separator and an optional airline code (defaults to host carrier)
The Equipment Ordinal entry shows the transaction history and any updates for a specific equipment
ordinal number (sequential number assigned to an aircraft configuration).
Use the following example entry to display this history:
GC*H/EQ/018
Entry Explanation
/018 Slash separator and example equipment ordinal number assigned to an aircraft
configuration. NOTE: To obtain the list of ordinal numbers, use GMMO* entry which
displays the Configuration Ordinal Table.
Note Adding the equipment ordinal in Command Center Creates the GMMO* table.
The Master Seat Map entry displays the transaction history and any updates for a master seat map.
Use the following example entry to display this history:
GC*H/MM/73S/11/16JUL
Entry Explanation
/16JUL Slash separator and Date (must be a date within the specific Master Map’s date range)
The Physical Aircraft Type entry displays the transaction history and any updates for a physical
aircraft type code, such as 727.
Use the following example entry to display this history:
GC*H/PA/U0/320
Entry Explanation
/U0 Slash separator and an optional airline code (defaults to host carrier)
The Priority Classification Code entry displays the transaction history and any updates for priority
classification codes.
Use the following example entry to display this history:
GC*H/PC/U0
Entry Explanation
/U0 Slash separator and an optional airline code (defaults to host carrier)
The Passenger Display / Edit Code entry displays the transaction history and any updates for the
passenger edit codes.
Use the following example entry to display this history:
GC*H/PD/U0
Entry Explanation
/PD Slash separator and the Passenger Display / Edit Code indicator
/U0 Slash separator and an optional airline code (defaults to host carrier)
The Passenger Facility Type entry displays the transaction history and any updates for entries related
to passenger facilities on an aircraft.
Use the following example entry to display this history:
GC*H/PF/U0
Entry Explanation
/PF Slash separator and the Passenger Facilities (on aircraft) indicator
/U0 Slash separator and an optional airline code (defaults to host carrier)
The Physical Aircraft Type Index entry displays the transaction history and deletions to a physical
aircraft type.
Use the following example entry to display this history:
GC*H/PI/401
Entry Explanation
/PI Slash separator and the Physical Aircraft type Index indicator
/401 Slash separator and an example of a Physical Aircraft Type Index code
The Seat Map Adjustment entry displays the transaction history and any updates for master seat
maps.
Use the following example entry to display this history:
GC*H/SM/U0/M80/DEN/SDF
Entry Explanation
/U0 Slash separator and an optional airline code (defaults to host carrier)
Segment Status
The Segment Status entry displays the transaction history and any updates for all segments booked in
the Passenger Name Records (PNRs).
Use the following example entry to display this history:
GC*H/SS
Entry Explanation
/U0 Optional slash separator and an airline code (if not used, defaults to host carrier)
Today the system refers to the Encode/Decode table to determine if you can through-check a bag on
other carriers. The Baggage Agreement Table offers an alternative to handling baggage when you
ground handle other carriers. Skip this section if you do not ground handle other carriers/
You may choose between Encode/Decode table and the Baggage Agreement Table.
If your carrier is currently using the Encode/Decode table method, you must contact SabreSonic
Customer Care if you wish to activate the Baggage Agreement Table for your carrier.
Note For detailed information on the Encode/Decode Ticketing and Baggage Agreements table,
please refer to the Encode/Decode Table module. This section will only detail the Baggage
Agreements Table.
Baggage Agreement (BAGR) tables are created and maintained by your airline and are used to
determine when bags should be through checked. You will need to create a BAGR table for each
carrier for which your airline handles baggage.
You can set up “Positive” or “Negative” baggage agreement tables.
Positive tables list the carriers your airline has agreement s with, so when the system looks at
it at check-in, and if it finds the connecting airline is in the table, bags are through checked,
so bag tags are printed for all carriers.
Negative tables list the carriers our airline does not have agreements with, so when the
system looks at the table at check-in, and finds the connecting airline in it, bags are not
through checked and bag tags are only printed up to where the connecting airline handles the
baggage.
The BAGR table is accessed at the time of check-in when there is a connection to another carrier in
the itinerary.
The SabreSonic Check-In system checks the table for all connections. For example, if a passenger is
traveling on your airline to TG, then UA, then JL, then DL and you have agreement with all carriers
except DL, the bag will be checked through to the JL segment.
The following is an example response of a Positive table listing the carriers where DO agreements
exist:
GC*BAGR/U0«
BAGGAGE AGREEMENT TABLE FOR CARRIER U0
AB AE AF BE BG BL BO
CA CI CU D3 D6 ED EK
ET FJ FT FV GA GF HM
HX IY JL JO KL KM KQ
KU LG LH LO MA MD ME
The following is an example response if there are no carriers in the positive agreement table, the table
will show:
GC*BAGR/BI«
BAGGAGE AGREEMENT TABLE FOR CARRIER BI
The following is an example response of a Negative table listing the carriers where agreements DO
NOT exist:
GC*BAGR/ U0«
BAGGAGE AGREEMENT TABLE FOR CARRIER U0
AA CO CY DL JL KM MH
NH UA WN
Note If the Baggage Agreement table feature has not been activated for your carrier, the table
will display along with the message “ACTIVATION REQUIRED FOR HOST CARRIER”.
GC*BAGR/JT«
AA CO CY DL JL KM MH
Additional Information
• Your airline is responsible for building a baggage agreement table for each airline that you
ground handle.
• A baggage agreement table must exist before you can through-check any bag to the
airlines that you groundhandle.
• The baggage agreement table wil not be accessed for Inbound Edifact entries. The
system will append the bagtag with the issuing carrier code, as it does today, without
regard to any baggage agreement the airline has.
• The baggage agreement table will not be accessed if you manually enter a tag issued by
another carrier. It is assumed that the carrier issuing the tag is responsible for ensuring
baggage agreement before issuing the tag.
• The baggage agreement table will not be accessed when an inbound BTM (Baggage
Transfer Message) is received. It is assumed that the carrier issuing the tage is
responsible for checking bag agreements, not the carrier accepting the message.
• At check-in time, if the agent adds an On demand bagtag, the system will access the
baggage agreement table.
• At check-in time, if the agent adds a Manual bag tag, the system will not access the
baggage agreement table.
• Sabre does not check for the validity of the airline code you use when issuing the bag tag.
Entry Explanation
GC* Primary system display action code
Once you have created the shell for a Baggagae Agreement Table, either positive or negative, the next
step is to add airlines to the table.
There is no limit to how many airlines you can add in one entry; however there is a character limit of
300 characters including the GC entry and the slash separators.
The maximum number of airlines codes you can add to a baggage agreement table is 1000 (one
thousand).
Use the following example entry to add carriers to a BAGR table:
GC/BAGR/AB/AE/AF/BE/BG/BL/BO
BAGGAGE AGREEMENT TABLE FOR CARRIER U0
AB AE AF BE BG BL BO
Deleting An Airline
Use the following example entry to delete a carrier from the BAGR table:
GC/BAGR/X-ET/AF/BH
Entry Explanation
GC Primary system action code
/AF Slash separator and the airline code you wish to delete
/BH Slash separator and the additional airline code you wish to delete
The response will be the baggage agreement table, with the mentioned airline(s) removed.
Use the following example entry to delete all carriers from the Negative Baggage Agreement Table:
GC/BAGR/X-PG‡ALL
Entry Explanation
GC Primary system action code
The Self Tagging Table is a table that contains a list of device addresses, by airport, which will be
authorized to issue Inactive bag tags.
Using designated devices at the airport, the passenger can print and attach inactive bag tags to their
baggage.
The inactive bag tags will only become Active when they are accepted into the system through
scanning or agent entry. At this point, the PNR will also be updated with a unique 5BAG entry.
Note Your airline must work with a Baggage Sortation system which must be able to read the A
and I in the Dot S field of the Reconciliation BSM and react accordingly.
The Dot S of the BSM is the reconciliation data of a BSM. IATA / ATA has recommended the Dot S
to be the area that will identify if the BSM is Active (A) or Inactive (I).
Example of a BSM where reconciliation is active:
BSM
.V/1LLHR
.F/XX0141/25MAY/JFK/F
.N/3001277685001
.S/Y/20A/C/018/678/Y/Y/I
.P/SMITH/BASIM
.L/KXSAFR
.T/BCBAA5
.E/VIP
.R/.02LHR/GTE/HD5
ENDBSM
For a complete explanation of a BSM, please refer to the IATA Passenger Services Conference
Resolutions Manual.
.S Element identifier
You can create a Self Tagging Table that will contain all the LNIATA of the devices you allow to be
used for the issuance of Self Tagging bag tags.
Note You must use duty code Cross-of-Lorraine ‡ and have the EPR keyword FSGAGT and
HDQAGT in order to work in the Self Tagging table.
GC/STT/A/ORD/1AB76D
Entry Explanation
GC Primary system action code
/STT Slash separator and the indicator for Self Tagging Table
Additional formats:
Entry Explanation
GC/STT/D/ORD/ABC123 Delete address ABC123 from the Self Tagging Table
Example response:
GC/STT/A/SEA/111HNB
SELF-TAGGING TABLE UPDATE: DFW
LINE APT DEVICE
NBR CDE ADDRESS
--------------------------------
001 SEA 111HNB
* DEVICE ADDED
You can display the Self Tagging Table for either one airport, or for the whole system.
Example entries:
GC*STT
GC*STT/SFO
Entry Explanation
GC Primary system action code
* Display
/STT Slash separator and the indicator for Self Tagging Table
Note If you do not specify the airport, the system will display the Self Tagging
table for all airports.
Additional format:
Entry Explanation
GC*STT/SFO/H Display History of Self Tagging Table in SFO
Example response:
GC*STT/SFO/H
SELF-TAGGING TABLE HISTORY DISPLAY: SFO
AGENT CITY DATE/ INPUT
SINE CODE TIME STAMP ENTRY
-----------------------------------------------------------
XXT0 HDQ 03AUG11 14:12:00 GC/STT/A/SFO-1A9000/2A94BC/CDE789
XXT0 HDQ 12AUG11 10:31:12 GC/STT/D/SFO-1A9424/1A94BC/2B644F
Upon activation, all BSM’s will contain a status in the DOT S field. Only those bag tags issued from
the Self Tagging LNIATA’s will be created with the Inactive (I) status. All other bag tags will be
created with an Active (A) status, including manual bag tags.
The status I may be changed via either a scanning action or a manual entry for each bag tag number.
Scanning
When the barcode of a passenger’s bag tag is scanned, the system validates that the name, PNR, Bag
Tag number are a match, and then the Sabre system sends a change BSM to change the I in the Dot S
field to an A.
The PNR will automatically be updated with a 5BAG remark. Example of a 5BAG remark after a
successful scan:
5BAG-TAG DCA009054 ACCEPTED 25MAY2011 0522L/ORD/SASF
Manual Modification
You can also change the bag status from Inactive to Active – or vice versa – by manual entries.
Example entries:
GBA1235-WONG/6667658954
GBI1235-COLACHE/8877663410
Entry Explanation
GB Primary system action code for baggage
A A – Activate
I - Inactivate
At Post Departure Check-Out (PDC), the system automatically sends a number of IATA teletype
messages to the downline station(s) at programmed printer or teletype addresses.
With the IATA Message Control Table, you have a place to additionally define the outbound
messages you want to send manually at times other than PDC, such as when the flight is in Close
status. You must request activation of the table through Customer Care.
The outbound messages you can further define in the IATA Message Control Table include:
In addition to the above passenger lists, certain Load Manager types of list will be included in future
enhancements. Examples are LDM and UWS messages.
The IATA Message Control Table provides the ability to update, delete, display and send data by
station and/or carrier. A station can specify whether the data should be by flight, market or should
include all flights departing from a station. It can be accessed by the Sabre Hosted carrier, for
Codeshare parties or for Third Party Handled carriers.
In the next pages, we will show you how to display an IATA Message Control Table, and how to edit
the table. We will also give you the formats to send messages manually.
The entry to display the table must follow a specific order: The start of the entry is always
GC*IATA/
The elements that follow the slash are in the order below
1. IATA Messages Control Table keyword (Mandatory)
An entry that does not follow the prescribed order will generate an error back.
EXCEPTIONS
AS * CX FTL
AS * KE FTL
AS * CX FTL
AS * KE FTL
AS ANC PSM TPM
AS BOI PSM TPM
AS DCA TPM
AS EUG PSM PTM TPM
AS FAI TPM
AS FCA TPM
AS FLG TPM
Example response at the more specific level – marketing carrier, specific market and specific flight
number:
GC*IATA/AR*JK/GHUMAD/1234
IATA POST-DEPARTURE MESSAGE AR *JK GHU MAD 1234
EXCEPTIONS
NONE
GC*IATA/AR*JK/GHUMAD/1234
IATA POST-DEPARTURE MESSAGE AR *JK GHU MAD 1234
Field Explanation
AS Host airline
AR *JK GHU MAD 1234 Host airline * marketing airline board point off point flight
number
Field Explanation
MSG OPTIONS AND TTY ADDRESSES First example shows NONE – it means no options or
teletype addresses have been defined at the requested
display level
MINUTES PRIOR TO OR POST DEPT 0 The number of minutes prior to or post departure time that
a message should be sent – at the moment, this time field
applies only to certain messages such as ADL.
AS * CX FTL
AS * KE FTL
AS * CX FTL
AS * KE FTL
AS ANC PSM TPM
AS BOI PSM TPM
AS DCA TPM
AS EUG PSM PTM TPM
Field Explanation
At PDC time, the system sends all requested teletype messages in a batch automatically to pre-
defined printer addresses. There is no manual intervention.
The IATA Host Message table is your tool to add teletype addresses as recipients of the messages,
and the type of messages you wish to send manually, as an exception or exceptions to the batched
messages.
Once you have populated the information you wish into the table, the system works in the following
manner when it is ready to send out the messages.
2. If there is no data there, the system continues the search ach and looks one level up –flight
number, city pair, host carrier - example format: GC*IATA/AR/JFKMAD/1234
3. Again, if there is no data, the search goes to the next less specific level up – and eventually it
will find data – in this example, the level that offers data is at the departure city -
GC*IATA/AR/AEP
GC*IATA/AR/AEP«
IATA POST-DEPARTURE MESSAGE AR AEP
The fields with yellow highlight illustrate the data that is found in the table. Based on the
data, an ETL message will be sent to teletype address AEPTTTY for flights on host AR
departing out of AEP.
The entry to display the table must follow a specific order: The start of the entry is always
GC/IATA/
The elements that follow the slash are in the order below
1. IATA Messages Control Table keyword (Mandatory)
An entry that does not follow the prescribed order will generate an error back.
The answer to each Add entry is the display of a mask which corresponds to the level that you want to
work at. In the example below we want to add parameters or recipients at the departure city level:
GI IATA POST DEPARTURE MESSAGE TABLE
GF LHR PAGE 1 OF 3
TTY ADDRESSES
<HDQRMGF> <HDQRMBA> <LHRTTGF> < > < >
< > < > < > < > < >
< > < > < > < > < >
< > < > < > < > < >
The mask displays what you already have in the table. In this example, out of LHR, host carrier GF
sends an ETL at PDC time to the TTY addresses HDQRMGF, HDQRMBA and LHRTTGF.
To navigate and move through the mask, use Tab.
If you wish to add a teletype address for the TPM sent out of LHR, use the mask to add this
information to the TPM page.
U-UP D-DOWN E-EXIT < > IATA MSG PROCESSING COMPLETE-Y/N < >
Field Explanation
D-DOWN You can move DOWN a level within the mask – input
D in the <>
E-EXIT < > You can EXIT the mask – input E in the <>
IATA MSG PROCESSING COMPLETE-Y/N < > Once you have finished your edits, input Y in the <>
Once you get to the TPM page, add the recipient teletype addresses and indicate that you have
finished working in the mask with a Y.
What you need to know when editing the IATA Message Control Table
• A teletype address has a maximum of seven characters. The entered city code will be
validated.
• The system displays only active message types, in alphabetical order. Inactive messages will
remain dormant and not displayable.
• Dormant IATA types of messages require programmer intervention to be added to the
Control Table by use of indicator switch.
• Only one IATA message appears on the mask at any one time. The messages are in
alphabetical order.
• Each mask only reflects the IATA messages applicable to the level of display. For example –
PTM and TPM messages are not applicable to Codeshare flights, and they will not show for
the Codeshare mask update entry (GC*IATA/AR*JK).
• In entries with two carrier codes, the first carrier code is the host carrier and an * precedes the
second carrier code or marketing carrier - example AR*JK.
• The sender teletype address does not display or need not be updated in the mask. The system
uses HDQKMxx as the default address internally, where xx is the host or operating carrier.
• If there is no Exceptions for a requested display, the word NONE will display under the
EXCEPTION header.
• Teletype addresses listed under the EXCEPTION area override the listed market or carrier
teletype address.
• The mask history record does not record updated or deleted data.
To delete any data that you have added to a table, use the same entries as when you add it, but put an
X- in front of the operating carrier.
Example:
GC/IATA/X-AR
Examples od delete entries:
Entry Explanation
GC/IATA/X-AR Delete recipient teletype addresses and parameters for
host
Use this entry to manually send a specific teletype message. In this example, we are sending a FTL
message to a specific teletype address.
Example entry:
GFI/XX123/02JUNEZEMAD/FTL/MADODAR
Entry Explanation
GFI Primary action code
/MADODAR Slash separator and teletype recipient address (if you do not specify an address, the
system will default to the address for that message in the table
You can display teletype messages during the flight initialization period, and when the flight status is
Open, Final, Closed or PDC.
Use this entry to display a teletype message (Inbound or Outbound) before sending it.
Example entry for an Inbound message:
GMSG123/02APRSFO/I/FTL/1
Entry Explanation
GMSG Primary action code
/XX Slash separator and carrier code you are sending message to
PSM TELETYPE MESSAGE DOES NOT The PSM Outbound message you wish to display has
EXIST not been created in the system.
TELETYPE MESSAGE DOES NOT EXIST The teletype message has not been created in the
system.
Sometimes you may display a TTY message that contains no passenger data.
Example response of a PFS message with no data:
GMSG0/O/PFS/AZ«
SYS RCVD TIME-NOT AVAILABLE
QU HDQRMAZ
.HDQRMAM 131421
PFS
AZ3061/13OCT MEX PART1
MIA 00/000
ENDPFS
LDM, CPM, and UWS are messages generated by the Load Manager application.
LDM = Load Distribution Message, or Load Manager generated Messages
CPM = Container / Pallet Distribution Message (for cargo load)
UWS = Unit Weight Signal
Load Manager does not capture or store inbound TTY messages.
Tha IATA Message Control table will store and display the above messages.
The UWS message is used for Load Planning purposes and can only be displayed at a transit point of
a multi-leg flight. Using the display message functionality, you can display the message and print it.
The aircraft loading team or dispatcher can use the UWS message to load the aircraft correctly at the
transit point.
For each teletype message sent, an entry is logged in the Flight History.
Examples:
Entry logged in Flight History Action performed
FTL/AR1141/26JUNFCOEZE Change flight status to ‘PDC’ or 'PDCSUP'
The Enhanced Synchronization of VCRs (ESV) provides your airline a mechanism to identify a
Passenger Name Record (PNR) that has had changes to the itinerary or passenger name that may
require an additional collection of funds.
The ESV process requires the use of Automated Exchange and Refunds (AER). Basically, ESV
attempts to keep each flight segment and corresponding coupon associated at all times.
The sync condition of the PNR is dependent on whether or not the VCR matches the name and
itinerary in the PNR.
A PNR with out-of-sync condition shows a banner at the top right corner with one of the following
text:
PNR MODIFIED – CHECK NAME
PNR MODIFIED – CHECK ITINERARY
PNR MODIFIED – CHECK NAME AND ITINERARY
An out-of-sync PNR is placed on a queue - usually queue city XTM, and queue number 450 – 454.
Note The PNR will NOT queue if any flight segment in the PNR is for today. Airport personnel
will need to take care of such a PNR on day of departure. The passenger may be inhibited from
check-in until the ticket is reissued or the agent decides to override the check-in inhibit.
The Irregular Operations (IR) Reason Code Table provides preset specific reason codes for those
overrides most commonly used by your carrier. Your airport employees use these codes when adding
an IR edit to a passenger or to a flight to override an out-of-sync condition.
The reason code table is an airline maintained table, which controls the override reasons that:
• Display in the 5H- field of the PNR.
• Display on the SabreSonic Check-In passenger lists.
• Are reflected in the Irregular Ops Override Report.
3rd party ground handling is supported by providing a reason code table for the handled carrier. The
3rd Party carrier code must be defined in your airline file. Contact Customer Service to add a 3rd party
carrier.
Use the following entry to display the Irregular Operations Reason Code Table:
GC*IRC
Entry Explanation
GC* Primary system display action code
Reason codes are applicable to both Flight and Passenger IR edits. The carrier code, either your
carrier or a carrier defined in your airline file, is mandatory when adding or deleting reason codes.
Updating the Reason Code table requires the following:
EPR keywords: FSGAGT
Duty code: ‡ (the Cross-of-Lorraine)
Use the following entry to add an Irregular Operation Reason Code in the Table:
GC/IRC/U0/MX/MECHANICAL CANCEL
Entry Explanation
GC Primary action code
/IRC Slash separator and indicator for irregular operations reason code
Slash separator and carrier code. Carrier code can be 1-3 characters, alphanumeric,
/U0
blanks not allowed.
Slash separator and reason code. Reason code can be 1-3 characters of your
/MX
airline’s choosing, alphanumeric.
/MECHANICAL CANCEL Slash separator and explanation of code. Can be up to 50 alphanumeric characters.
The following example response includes a display of the entire table including the new reason code
added:
U0 IRREGULAR OPERATIONS REASON CODE TABLE
REASON CODE DESCRIPTION
/IRC Slash separator and indicator for irregular operations reason code
The system responds with a display of the entire table with the deleted reason code removed.
The SabreSonic Check-In Airline Serving Airport Table (ASA) controls the ESV functionality for
each AAA city. The ASA table contains a field titled “PNR BANNER INHIBIT CKI”. When you
set this field to Y, check-in is inhibited if an ETO indicator is associated to a single passenger in the
PNR.
Code Description
AF Award free ticket (no action required)
BB Book jumpseat
BK Holds confirmed (used only by automated accounts for other airline segments generates a teletype
message upon cancellation. Cannot be used to generate PTA’s).
BL Flight waitlisted directly with carrier (no message generated except for cancellation)
DK Direct access/link booking, received from other airline CRS/GDS (will OB flight if sold out).
DL Deferred from waitlist. If still desired, must be cancelled and relisted to do so, enter .CSS to HL.
DS Desires used for open segments and for connection flights preceding/following waitlisted (hl) segments.
When hl segments are confirmed, enter .CSS to NN.
FS Freesell.
GK Holds confirmed (used only by automated accounts for other airline segments. Does not generate a
message, cannot be used to generate PTA’s).
GL Holds waitlist (used only by automated accounts for other airline segments. Does not generate a
message).
GN Provides a means to control large party bookings containing host inventory. Host agents sell segments
with NN status code which automatically changes to a GN at end transactions and queue places for CRC
approval or denial. GN action status does not decrement inventory.
HK Holds confirmed (message is not generated unless OSI/SSR/5qq is added to the PNR).
HL Holds waitlist .
HS Have sold adjusts inventory (seen only in history, other airline only).
HX Have cancelled. A host cancel action will generate an HX back to the booking source.
IC Incorrect class.
IG Involuntary up/downgrade.
LL Waitlist message generated if other airline mm meal request for NRSA or pet in cabin (NOTE-may be
booked with duty code 6).
NS No show, no seat.
OB Overbook.
OS Oversold.
PN Pending need message previously sent to other airline, awaiting reply (Sabre will automatically resend the
request one time if no response within 24 hours).
PS Positive space (A 7 PS entry in the PNR permits SSCI to change segment status to PS during the post
departure process).
PU Passive segment update with ticket number (for inbound TTY only).
RR Reconfirmed passenger has reconfirmed their reservation (used primarily on international travel).
SA Space available.
SC Host schedule change, shows new segment. Change segment status to HK.
SS Sell.
TK Other airline schedule change, new times only. Change to confirmed CSS to HK.
TL Other airline schedule change, waitlisted. Advise new times and change to holds list CSS to HL.
UN Unable to confirm, flight not operating (does not generate message to booking source if segment manually
changed to UN).
VG Voluntary upgrade/downgrade.
YK Booked via vendor for agency documenting and follow-up. No message generated or itinerary action
required, space is holding confirmed (HK) in another record.
ZS Code share flight sale. Incoming message from any carrier with codeshare automation.
GC/ASA/YVR/BGI9/PBT0 Update the Hours before Departure Bag Tag Allowed indicator.
GC/ASA/YVR/BGI9/HUB Update the Hub City indicator to Y – the same entry will change it to
N.
GC/ASA/YVR/BGI9/STPCHK Updatemd
m the PNR Banner Inhibit CKI indicator to Y.
GC/EMB/DCA/12APR-12APR/X-NRSA Delete all non-revenue restrictions for specific date or date range
GC/IATA/U0/MAD Add or update all departures for HOST or 3rd party carrier.
GC/IATA/U0/MADEZE/1133 Add or update for HOST or 3rd party carrier, flight specific.
GC/IATA/X-U0/MAD Delete for HOST or 3rd party carrier, for all departures.
GC/IATA/X-U0*1S/JFK Delete for HOST or 3rd party carrier, for all departures.
GMSG123/02APRSFO/I/FTL/1 Display inbound FTL message for host flight 123 out of SFO,
Part 1
GMSG5326/2AUGIPN/O/PFS/JJ Display the targeted PFS message from host flight for JJ
GC/IRC/U0/MX/MECHANICAL CANCEL Irregular Operations Reason Code Table – Add a Reason Code.