6.1 GDS Overview & PNR Mandatory Elements

6.1 GDS Overview & PNR Mandatory Elements

Quick Answer: A Global Distribution System (GDS) is a computerized network that enables automated transactions between travel service providers (airlines, hotels, car rental agencies) and travel agents. To create a valid reservation in any GDS, a travel agent must input five mandatory elements represented by the acronym PRINT: Phone/Contact, Received From, Itinerary, Name, and Ticketing Time Limit. The reservation is permanently stored only when the agent enters the End Transaction command (ET or E), which generates a unique 6-character alphanumeric Record Locator (PNR reference code).

---

1. Evolution & Architecture of Global Distribution Systems

In the early era of commercial aviation, airline bookings were recorded manually on physical index cards and wall-mounted availability boards. As air travel volume expanded rapidly during the 1950s and 1960s, major carriers developed individual Computer Reservation Systems (CRS) to automate internal seat inventory. Over subsequent decades, these proprietary CRS networks expanded into multi-access Global Distribution Systems (GDS)—electronic clearinghouses that connect thousands of travel suppliers with retail travel agencies, online travel agencies (OTAs), and corporate travel management systems worldwide.

Today, the global air distribution landscape is dominated by three major GDS platforms, often referred to as the "Big Three":

Core GDS Functions

1. Real-Time Inventory Querying: Displays live seat availability, cabin inventory, and schedule connections directly from airline Central Reservation Systems (CRS).
2. Fare Quote & Rules Calculation: Accesses published fares, passenger facility charges (PFCs), government taxes, and complex fare rule restrictions.
3. Reservation & PNR Creation: Holds seat space, stores passenger profiles, and records special service requirements.
4. Document Issuance: Triggers electronic ticketing (e-ticket) generation and Electronic Miscellaneous Documents (EMDs) through the IATA Billing and Settlement Plan (BSP) or ARC (Airline Reporting Corporation).

---

2. Structure of the Passenger Name Record (PNR)

A Passenger Name Record (PNR) is the fundamental database file created within a GDS or CRS that contains all travel details, personal data, and transaction histories for an individual passenger or group traveling together.

When an agent opens a blank workspace in a GDS terminal, the system creates a temporary work area known as the active buffer or short-term memory. Information typed into the terminal resides only in this volatile buffer until a formal validation command is issued to commit the file to the central database.

The 6-Character Record Locator

Upon successful completion and saving of a PNR, the GDS central system automatically assigns a unique Record Locator (also called a PNR Code, Reservation Code, or Booking Reference). The Record Locator consists of a 6-character alphanumeric string (e.g., X7K9PQ or 3M2B8R).

Exam Tip: The GDS Record Locator and the airline's internal CRS Record Locator may differ when an itinerary involves a carrier operating on a separate host database. Agents must distinguish between the GDS Record Locator (used by the agency) and the Airline Record Locator (used by airport ground staff).

---

3. The 5 Mandatory PNR Elements: The PRINT Mnemonic

To save a PNR and generate a Record Locator, the GDS requires a minimum set of information. If an agent attempts to end the transaction without supplying all required fields, the GDS will reject the entry and display an error prompt. Professional travel agents memorize these five mandatory fields using the acronym PRINT.

  P — Phone / Contact Element
  R — Received From Element
  I — Itinerary Element
  N — Name Element
  T — Ticketing Time Limit Element

Detail Breakdown of PRINT Mandatory Elements

1. P — Phone / Contact Element

Provides contact details for the booking agent, travel agency, or passenger so that airlines can communicate flight cancellations, schedule changes, or irregular operations.

• Function: Identifies agency phone, home/mobile phone, or business contact.
• Amadeus Entry: AP LON 020-7946-0123-A (Agency) or AP LON 07700-900123-M (Mobile)
• Sabre Entry: 902079460123-A
• Travelport Entry: P.LON*02079460123

2. R — Received From Element

Specifies the identity of the person who requested the booking or transaction modification. This field is essential for legal compliance, audit trails, and agency accountability.

• Function: Records who authorized the transaction (e.g., passenger, corporate travel arranger, secondary agent).
• Amadeus Entry: RF PASSENGER or RF MR SMITH
• Sabre Entry: 6PASSENGER or 6SMITH
• Travelport Entry: 6PASSENGER

3. I — Itinerary Element

Contains at least one active travel segment, such as an air flight segment, rail segment, car rental, or hotel reservation. For air segments, it defines the marketing carrier, flight number, booking class (RBD), travel date, origin/destination pair, and segment status.

• Function: Holds physical inventory space on a specific flight.
• Amadeus Entry: SS BA175 C 12MAY LHRJFK 1 (Sell Segment: British Airways flight 175, C class, 12 May, London Heathrow to New York JFK, 1 seat)
• Sabre Entry: 0BA175C12MAYLHRJFKNN1
• Travelport Entry: 0BA175C12MAYLHRJFK1

4. N — Name Element

Identifies the full legal name of each passenger traveling in the record, exactly matching the passenger's government-issued passport or national identification document.

• Function: Defines passenger count, surname, first name, and title (MR, MRS, MS, MISS, MSTR).
• Format Standard: SURNAME/FIRSTNAME TITLE
• Amadeus Entry: NM1SMITH/JOHN MR (Single passenger) or NM2SMITH/JOHN MR/MARY MRS (Two passengers with shared surname)
• Sabre Entry: -SMITH/JOHN MR
• Travelport Entry: N.SMITH/JOHN MR
• Child & Infant Rules: Children (ages 2–11) require an age indicator (e.g., NM1BROWN/DAVID (CHD/08AUG18)). Infants under age 2 not occupying a seat are attached to an adult name element (e.g., INF/BROWN/LILY/04JAN25).

5. T — Ticketing Time Limit Element

Instructs the airline's automated inventory robot when the booking must be ticketed. If the ticket is not issued by the specified deadline date and time, the airline system automatically cancels the reserved itinerary segments.

• Function: Establishes ticketing deadline or records existing ticket status.
• Amadeus Entry: TK TL15JUN/1800 (Ticket limit 15 June at 18:00) or TK OK (Already ticketed)
• Sabre Entry: 7TAW15JUN/ (Ticket Advisory Working)
• Travelport Entry: T.TAU/15JUN

---

4. Optional & Secondary PNR Elements

While the five mandatory PRINT elements permit PNR creation, a comprehensive travel booking includes secondary elements to support passenger servicing, corporate tracking, and payment processing:

---

5. The PNR Validation & End Transaction Lifecycle

The life cycle of a PNR involves moving data from volatile buffer memory to permanent GDS disk storage through specific transaction commands:

1. Active Working Buffer: The agent enters mandatory PRINT elements one by one.
2. End Transaction Command (ET or E):
   • The agent types ET (Amadeus/Travelport) or E / ER (Sabre).
   • The GDS algorithm audits the working buffer for all five mandatory PRINT elements.
   • If valid, the system claims inventory from the airline CRS, writes the record to permanent database memory, and generates the 6-character Record Locator.
3. Ignore Transaction Command (IG or I):
   • If the client decides not to proceed, the agent types IG (Amadeus/Travelport) or I (Sabre).
   • The system completely clears volatile buffer memory without reserving seats or saving data.

+-----------------------------------------------------------------------+
|                           WORKING BUFFER                              |
|  Agent enters: Name (N), Itinerary (I), Phone (P), Ticket Limit (T)   |
+-----------------------------------------------------------------------+
                                   |
                       Is Received From (R) entered?
                                   |
                +------------------+------------------+
                |                                     |
             YES (ET)                              NO (ET)
                |                                     |
   +--------------------------+          +--------------------------+
   |  System Validates PRINT  |          | System Rejects Command   | 
   |  Generates 6-Char PNR    |          | Returns Error Prompt:    | 
   |  (e.g., "X7K9PQ")        |          | "NEED RECEIVED FROM"     |
   +--------------------------+          +--------------------------+

Common Exam Trap: Entering ET without a Received From element will cause the system to freeze the transaction and issue an error message. A booking is NEVER confirmed or safe from system timeout until the End Transaction code is successfully processed and a Record Locator is displayed on screen.