TH2106
The Passenger Name Record
Mandatory Elements of the Passenger Name Record
A Passenger Name Record (PNR) contains the details of a passenger’s reservation and other information
related to their trip. PNRs can also contain information to assist airline personnel with passenger handling.
The items of information that make up a PNR are called elements. A PNR can contain a maximum of 999
elements. These PNR elements can either be mandatory or optional.
The mandatory elements are:
Letter Definition Transaction Command
S Segment SS
M Name NM
A Contact AP
R Received From RF
T Ticketing TK
When creating a PNR, the elements can be entered in any order. Several elements can also be combined into
one entry. As the system accepts each element, it assigns a number and places it in the proper sequence.
An end transaction command is used to file the record in the Amadeus System after the five (5) mandatory
elements are entered. When a PNR is filed, it is assigned with a 6-character code called a record locator, which
is used to retrieve a previously created and filed PNR.
PNRs remain active in the Amadeus system for three (3) days after the date of the last active or inactive
segment in the itinerary. Once a PNR has been purged, the corresponding past date record can be retrieved
for another five (5) years.
Below are some unique features of the Amadeus PNR:
• All elements are numbered consecutively, making modifications easier.
• All names are displayed individually, even though two (2) passengers may have the same family name.
• All names are displayed in alphabetical order by family name, regardless of how they were entered
during the PNR creation.
The following table describes the item and character limits of the mandatory PNR elements:
Element Maximum items Maximum Characters
Name 9 60
Itinerary 99 N/A
Contact 127 90
Ticket 127 14
Received From 1 69
SEGMENT ELEMENT
A segment element can be a flight, hotel, car, or cruise element. A PNR can contain up to 99 segments. In a
PNR, the segment element follows the name and is numbered consecutively.
For example:
A flight segment can be entered using a short sell entry from an availability display.
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 1 of 9
TH2106
Short Sell Entry
When an availability display is shown, a short sell segment entry can be made from the display.
To sell one Y class seat for CX flight 912, enter:
SS1Y4
SS Segment sell transaction code
1 Number of seats
Y Class of service
4 Availability line number
System Response:
* Type RTSVC to display the flight service information from the PNR
Connecting Flights
Entry Sells a connecting flight
SS1FY2 In F on the first segment and Y on the second segment
SS1C1 In C class on the first segment and second segment
Dual City Pair
Entry Sells
One F class seat from line 2 of the first availability display and one C class seat from line
SS1F2*C12
12 of the second availability display
One C class seat from line 1 from the first availability and same seat class from line 11
SS1C1*11
from the second availability
Waitlist Segment - When a class of service in the availability display shows a status 0 / L or R, a seat for a
passenger can still be reserved but on a waitlist status.
Entry:
SS2F3/PE
SS2F3 Short sell entry
/PE Slash, followed by the priority waitlist code (airline-specific)
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 2 of 9
TH2106
Arrival Unknown Segment - An arrival unknown segment is an information segment entered in the PNR to
maintain segment continuity. ARNK is used when a passenger uses another form of transportation between
cities or airports within the itinerary.
SIARNK
SI Transaction code
ARNK Arrival Unknown indicator
Open Flight Segments
When a passenger does not know the exact time or date of travel, an open segment can be entered in the
itinerary. Open segments maintain segment continuity and can be used for pricing and ticketing. To create an
open segment, enter:
SOAFC8AUGCDGMNL
SO Segment open transaction code
AF Airline code
C Class of service code
8AUG Fictitious date, DDMMM
CDGMNL Origin and destination airport/city code
System Response:
The system automatically:
• Inserts the open segment in the proper sequence
• Renumbers the itinerary elements
Note:
• Adding fictitious date in the entry is recommended for pricing and ticketing
• If without a date: SO AF C CDGMNL
To help differentiate between the levels of participation used when making a segment sell, Amadeus displays
anyone of the following status codes upon selling:
Status Explanation
DK Sold and confirmed via Amadeus Full Access ( / )and Access sell (. )
LK Sold and confirmed from Direct Access mode
SS Sold from Standard Access, 12 hours waiting time
NN Sold but status on request
DW / LL Sold but status on waitlist
NAME ELEMENT
A passenger name consists of the family name, given name, and title. Up to nine (9) names can be entered in
a PNR. A name can contain up to 60 characters.
The acceptable titles are:
Title Explanation Additional Info
MR or MS 12 years or older
MSTR or MIST 2 up to 11 years CHD
INF 1 month to 23 months old INF
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 3 of 9
TH2106
When creating a name element for an infant, the passenger type must be included, and the infant must be
associated with an adult name. (Note: Some airlines may require specific titles. In this case, it is a must to
check with the airline.)
Single Family Name Element
To create a single family name element, enter:
NM1PEREZ / TIMOTHY MR
NM Name element transaction code
1 Number of passengers with the same family name occupying seats
PEREZ/TIMOTHY MR Passenger family name, given name separated by a slash, and title
System response:
Here are some examples of different possible name element entries:
Entry Requests
NM2REYES /HANS MR/HEIDI MS More than one passenger with the same family name
NM1BRADLEY/MICHAEL MSTR(CHD/12DEC16) Child name
Infant’s Name
Entry Requests
Pauline is the infant with the same surname as
NM1BROSNAN/SUZANNE MS (INF/PAULINE/01NOV20)
the adult; the infant does not occupy a seat
John is the infant with a different surname as the
NM1CRUZ/JANE MS (INFVICTOR/JOHN/12NOV20)
adult; the infant does not occupy a seat
The infant’s name is Diana
INS – passenger type code
NM1SUMMER/DIANA (INS) SR INFT… command to request for a seat for the
infant (Note: “SR INFT –“ and “P1” [Passenger
SR INFT –11MTHS OCCUPYING SEAT/P1 association] command must be exactly inputted
while “11MTHS OCCUPYING SEAT” is freeflow
information entered)
The system automatically:
• Numbers the name element.
• Places the names in alphabetical order by family name, regardless of how these have been entered.
• Creates an Other Service Information (OSI) element when entering the name of the child.
• Creates a Special Service Request (SSR) element after the air segment is added in the PNR.
CONTACT ELEMENT
The contact element is used to store the contact information of a travel agency and its passengers in the
PNR. Except for a transaction code, the contact element is a free-flow text. A PNR can contain up to 127
contact elements, each with a maximum of 90 characters. The travel agency contact must be the primary
number added in the PNR. It is recommended that the contact element of the travel agency be entered in
the following order:
APMNL ABC TRAVEL 8406589 JOHN-A
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 4 of 9
TH2106
AP Contact transaction code
MNL City code
ABC TRAVEL Agency Name
8406589 Telephone number
John Agent name
-A Dash, followed by the location indicator
A Agency
B Business
H Home
F Fax
Hotel Hotel
E E-mail (refer to sample)
Sample Entries:
Entry Description
AP MNL 8187867-H/P1 Home Contact
AP MNL FAIRWAYS INC 99546787-B/P1, 3 or
Business Contact for Passenger 1 and 3
APB-99546787/P1,3
APM-61 2 98766111/P2 Mobile Contact for Passenger 2
APE-TSMITH@[Link] E-mail address of the passenger
RECEIVED FROM ELEMENT
The received from element identifies the person making or modifying a reservation. A maximum of 69
characters can be entered. During PNR creation, the received from element is displayed as the second line in
the PNR. After ending the transaction, the received from element is moved to the PNR history.
A received from element is required when creating a new PNR or modifying an existing one. To create the
receive from element, enter:
RFMARY
RF Received from transaction code
MARY Reference person
TICKETING ELEMENT
The ticketing element indicates the type of ticketing arrangement made to provide tickets to a passenger.
TKTL19MAY
TK Ticketing Element transaction code
TL Ticketing arrangement indicator
19MAY Date, DDMMM
System Response:
Ticketing arrangement indicators:
Option Indicator Indicates
Time Limit TL Deadline to purchase the ticket
Ticketed OK Ticket is issued
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 5 of 9
TH2106
END TRANSACTION
When the five (5) mandatory elements (SMART) have been entered, the end transaction must be performed
to file the record in the system. Below is a sample PNR during creation.
To end transaction and redisplay the PNR in the system, enter: ER
System Response:
If the system response is as follows, enter ER again.
When a transaction is ended and a PNR is redisplayed, additional information is contained in the header line.
Component Identifies
RLR Information tag
RLR Record Locator Return
SFP This tag indicates that at least one of the air segments booked
is affected by the TSA's secure flight program prerequisites.
RP Responsible office indicator
/MNL1A0901 Office ID of the responsible office
/MNL1A0901 Queuing office identification
Last two (2) characters of the agent sign who created the PNR or who carried
AA/SU out the last update and duty code
15OCT21 Date of creation or last update
/0219Z Time of creation or last update, and the Zulu time indicator (Z)
* have to add 8 from the Zulu time given to get the military time
T4SQLO Alpha-numeric 6-character Amadeus Record Locator
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 6 of 9
TH2106
IGNORE and REDISPLAY
After ending the PNR, an RLR will be displayed at the upper left corner of the booking, indicating that the
airline participates in the record locator return tool in Amadeus.
To display the airline record locator, enter: IR
System response: (partial copy of the PNR)
To ignore current updates to an existing PNR and have the PNR redisplayed on the screen in its original form
is another useful feature of this command.
IGNORE TRANSACTION
A PNR can be ignored anytime during creation or modification. When a PNR is ignored during creation, all
elements are omitted, and any flight, hotel, or car booking will be returned to inventory.
The entry is: IG
System Response:
If the ignore transaction is used when modifying an existing PNR, the system ignores the updates and
returns the PNR to its original form.
PNR RETRIEVAL
A PNR can be retrieved using the record locator or details of a flight for current date or future date.
To retrieve a PNR by record locator, enter:
RTYQEPYT
RT Retrieval transaction code
YQEPYT Record Locator
System response:
The following table describes other PNR retrieval entries:
Entry Retrieves a
RT/GARCIA PNR by family name
RT1 PNR from a list
RT0 Multi passenger list
To return to the PNR provided it is still active enter: RT
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 7 of 9
TH2106
Ways to Modify a Passenger Name Record
It is possible to modify or cancel existing elements of a passenger name record (PNR). When a PNR is modified,
the system reflects all the changes in the PNR history at end transaction.
Canceling PNR Elements
Entry Cancels
XE4 A single element
XE3-6 A range of elements
XE5,7 Selected elements
• The system automatically cancels any special service request (SSR) elements associated with the air
segment.
• When you cancel SS requests, the system automatically changes the status code to XX.
The following are the advice codes used to indicate the status of PNR elements.
Status code Explanation
HK Holding confirmed
HL Holding waitlist
HN Holding request (neither confirmed nor waitlisted)
Advice code Explanation Action required
KK Confirming from HN Change status to HK
KL Confirming from HL Change status to HK
TK Time change from HK Change status to HK
UU Wait listing from HN Change status to HL
TL Time change from HL Change status to HL
NO No action taken Delete element number
UC Unable to confirm Delete element number
UN Unable due flight not operating Delete element number
US Unable to sell seat Delete element number
HX Segment was cancelled by the airline Delete element number
Note: All negative advice codes must be deleted on the day the airline generates them to avoid any penalty
that carriers may impose.
Modifying a Passenger Name
The Amadeus system provides the Name Update command as a facility to modify the first names of
passengers.
Name change processing procedures vary from airline to airline. It is important to check with the airline
concerned if they allow name change/corrections as this may be rejected and result in non- synchronization
of records with Amadeus.
Sample PNR:
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 8 of 9
TH2106
Here are some modification entries:
Entry Modification
NU1/GRACE MS Updates the given name for passenger 1
2/MARK
MSTR(CHD/15JUL16) Changes the name and passenger type of passenger 2
3/(INF/ANNE /17JAN21) Adds an infant name to passenger 3
4/ Deletes an infant name or passenger type code attached to passenger 4
Note: If the name cannot be modified using the entries above, another way is to recreate the PNR. This applies
only to non-ticketed PNRs. Some airlines do not allow changing passenger name directly on the system. It must
be requested to the airline company.
Rebooking Flights, Classes, and Dates
PNRs booked in Amadeus should always be synchronized with that of the airline. Mishandling in rebooking
brings about most cases of non-synchronization. One must consider if the airline involved is a system user or
a non-system user.
Steps
a. Retrieve the PNR RTXXXXXX
b. Check if the desired flight is available AN
c. Redisplay the PNR RT
d. Cancel the unwanted segment XEn
e. Input a Received From and end transaction RF;ER
f. Redisplay the Availability MPAN
g. Sell the new flight SS
h. Input a Received From and end transaction RF;ER
Another way to modify flights are:
Entry Modification
SB25AUG5 Should be the entry to change the date of segment 5
SBK Should be the entry to change the booking class to K on all flight segments
Note: Do not reuse a Dead PNR. A Dead PNR is a PNR that has been previously canceled. It is possible that the
booking will not be generated by the airline.
Reference:
Amadeus Training Materials
06 Handout 1.1 *Property of STI
[Link]@[Link] Page 9 of 9