How to create Optional PNR fields in Sabre
A travel client’s flight booking contains both mandatory and optional PNR fields relevant to the type of travel it is being booked for. It is related to the GDS-initiated travel reservations associated with a specific trip. These optional PNR fields provide important details useful to the travel agency and their clients.
To read more on how to create mandatory fields in a PNR, you can visit here.
In this article, we shall look at the optional PNR fields when creating a reservation in the Sabre GDS for a client.
Optional PNR fields
You must have been already familiar with PNR as an acronym for Passenger Name Record. It contains all the necessary information for a client’s reservation. You also must have been familiar with the five mandatory elements (fields) in a PNR. You can complete the fields in any order and you may use the keyword PRINT to easily remember these fields. That is, P- Phone field, R- Received From field, I- Itinerary field, N- Name field, T- Ticketing Time Limit field (T).
Now, let’s get familiar with some of these optional PNR fields.
The remarks field is where all PNR remarks are stored. It is used to input customer and agency information, the form of payment, and accounting data. Different formats are used depending on the type of remarks being added to the PNR. When more than one form of payment field has been entered in the remarks field, the system uses only the first 5- field.
Passenger E-Mail Address Field
An e-mail address can be added or deleted to a PNR in the PE field. When you change or delete a passenger name from your PNR, the e-mail address associated with that name is also changed or deleted. The system permits a maximum of 999 PE‡ fields in a PNR.
A cross of Lorraine (‡) after the PE code indicates the start of the e-mail address. A second cross of Lorraine (‡) at the end of the e-mail address is required. The e-mail address must have one at-sign (@) between the crosses of Lorraine (‡).
The e-mail address field must be completed before using one of the EM commands which then sends the e-mail to the specified email addresses in the PNR.
Frequent Traveler Numbers
These formats are used to store a passenger’s frequent flyer number in a PNR. A message is transmitted to a participating carrier to give passengers mileage credit for the bookings made in the Sabre system.
A separate frequent flyer entry must be made for each name and airline. The name field in the PNR must match the carrier’s frequent flyer card name to ensure mileage credit. The system generates a message to send this information to the carrier.
OSI (Other Service Information)
Agencies use Other Supplementary Information (OSI) messages when they need to send information to the carrier that does not require action or a reply by the carrier. These are low-priority messages usually used for information purposes only. OSI messages are sent to carriers, however, Sabre cannot guarantee the carrier will process the message.
SSR (Special Service Request)
Agencies send Special Service Requests (SSR) messages to carriers that require action or a reply. These messages require specific codes that can be found in Format Finder.
The system edits each SSR code to determine if a free text is required. A slash is required when free text information is required.
Common Types of SSR Requests
|Send Special Meal Request (DU*/SPM for meal codes list)||Send Wheelchair Request (WCHS)|
|Send OTHS for CC Holder to carriers (OTHS/)||Send Group Fare Basis Code (GRPF/)|
|Send Passport Info (3PSPT/)||Send Ticket Number (TKNM/)|
|Send Pet in Cabin Information (PETC/)||Send Emergency Contact Information (PCTC/)|
|Send Unaccompanied Minor Information (UMNR/)||Send Form of Identification (FOID)|
What is a DK Number in Sabre?
Agencies use the DK number field primarily as an account reference identifier for billing purposes on the Sabre GDS. The DK number can be letters, numbers, or a combination. Only one DK number can be in a PNR. When another number is entered, it replaces the previous one. An agency can require a six, seven or 10-digit DK number.
Complete a PNR
After a subscriber inputs all the required (PRINT) and optional fields, they will end transaction on the PNR. At this time Sabre sends a message to all of the carriers they sold flights on so that the carrier will create a PNR in their system. Depending on how the air itinerary segments were sold, the PNR will update with the PNR locator from the carrier’s system.
To know more about how to create optional PNR fields in the Sabre system, you can download the free Sabre GDS system training resource here.
About Sabre Corporation
Sabre Corporation is the leading technology provider to the global travel industry. Sabre’s software, data, mobile and distribution solutions are used by hundreds of airlines and thousands of hotel properties to manage critical operations, including passenger and guest reservations, revenue management, flight, network, and crew management. Sabre also operates a leading global travel marketplace, which processes more than US$120 billion of global travel spend annually by connecting travel buyers and suppliers. Headquartered in Southlake, Texas, USA, Sabre serves customers in more than 160 countries around the world.