Passenger Name Record (PNR)

Introduction

Claim PNR

Client Account
Number (5-CA)

Client Billing
Address (5-CB)

Client Delivery
Address (5-CD)

Commission
(5-CM)

Create
Passenger
Name Record
Index

Customized
Name Data

Display PNR

Display Portions of a PNR

Divide PNR
- Divide PNR   Entries

End and Copy/
Clone a PNR (Air/Car/Hotel)

End Transaction
- Simultaneous   Changes

Endorsement
Restriction
(5-ER)

Form of Payment (FOP)

Frequent Flyer

General Remarks (5)

Ignore PNR

Infant PNR

Invoice Remarks (5IR-)

Itinerary Remarks
(5RM-)

Mandatory Fields

Manual Credit Card Approval Code

Modify/Delete SSR

Name Field
- Airline Name   Change   Restrictions
- Name Field   Entries

Other Service Information

Passenger Type Codes

Past Date PNRs
- Function   Identifiers
- Reading a   Past Date
- Requesting a   Past Date

Phone Field
- Identifier Codes
- Phone Field   Entries (9)
- Phone Field   Order
- Phone Field   and World   Files
- Phone Field via   OSI

PNR Purge
Date

Received from
Field

Reduce Number in Party ($)

Request SSR's-Segment/Name
Select

Special Service Request

Ticketing Field
- Fare Type   Codes
- Function
  Identifiers
- Horizontal   Ticketing   (7TRH)
- Non-Burst   Ticketing   (7TAS)
- Prepaid Ticket   Advice (7PTA)
- Tax Ticketing   (7TAX)
- Ticket at Will   (7TAW)
- Ticket Date
- Ticketed (7/)
- Ticketing Field   Queuing
- Ticketing   Queue (7TRL)
- Ticketing Time   Limit (8TL)

Unique Remarks (5.)

Wheelchair
Assistance

Click here to display a complete list of available online e-Learning courses.

Introduction

The Passenger Name Record (PNR) contains travel and client information regarding a trip. It has four mandatory fields, plus numerous optional fields. Fields may be single item (one allowed per record) or multi-item (more than one allowed).

top of page

Create Passenger Name Record Index

A PNR is an automated file of a customer's travel related information. A PNR remains in Worldspan® for 30 days after the last ticketed flight segment.

top of page

Display PNR

top of page

Mandatory Fields

Example - PNR Display

Explanation of Example - PNR Display

top of page

Name Field

The Name Field is a mandatory PNR data field for the storage of the passenger(s) name in relation to the itineary reserved.

• Each name item must contain at least two, but not more than 69 characters number in party.

• Each PNR may contain up to 255 names, however for ten or more passengers group procedures must be followed.

• Accuracy in spelling when entering surnames must be stressed. If the first letter of the surname is entered incorrectly the PNR is unable to be retrieved. For example: Cahn is entered as Kahn. The PNR is unable to be retrieved until the first correct letter is entered.
  
  

• The PNR name fields are utilized during production of tickets,itinerary/inovices, advanced seat assignment, and boarding pass issuance therefore extreme care must be used to assure accuracy.

• Each name item is automatically numbered in the PNR.

• The number in party is determined based on the number of slashes (/) separating first names/initials and/or titles. The exception is on corporate PNRs and divide PNR entries where the number in party must be included in the name field entry.

• Once the original PNR is created and an end transaction has been performed, a name change or deletion is allowed, but no additional names can be added to the PNR. A separate PNR must be created for the additional party.

• The name field may contain a maximum of 126 characters.

• If there are ten or more names in the PNR, they are alphabetized upon re-retrieval.

top of page

Name Field Entries

NOTES:

1. The end item (#) is used to separate individual surnames in the name field entry.

2. The name field entry may be combined with all PNR fields except the itinerary field by the use of the end item #, including end transaction and queueing functions.

3. First names or initials with/without titles are mandatory. The first two characters of the surname must be two alphas.

4. The name field item number is optional when changing the name in a single name field PNR.

5. Changes to first names must be done in numerical order within the same item.

6. When OAL SSR seat items exist, 4RXO must be entered prior to the name change function.

7. When changing multiple items and some of the associated PTCs in a name field, use a slash (/) for the PTCs that are not being changed. Current PTC is assumed if it
   is not changed.

8. Some airlines do not allow name changes. Please check with each OAL for their name change policy.

9. Do *not* delete the name and re-enter it. Use the one step process for changing a name.

10. When a name is deleted and re-entered it disassociates itself from the ETR. Once the name is changed reissue a new ticket.

11. For information regarding infant name fields, refer to the Infant PNR section.

12. When creating a name field do not use the abbreviation chd - for child. the abbrevation of chd should not be used in the name field but added as an osi. For example:
    -MASON/LARRY/RACHEL/AMY*2ADT/C06
    3OSIYY 1CHD 1MASON/AMY

13. When creating name fields on reservations for United Airlines (UA) if the name field exceeds 55 characters, no positive acknowledgement record locator is returned from the carrier.

14. Deletion of name items is allowed only when one of the following conditions exist:
        a. When creating a PNR and more names are entered than the actual number of seats         requested.
        b. When an itinerary is being cancelled for one or more passsengers, but not all         passengers on a confirmed itinerary in the same PNR. To reduce number of seats
            being held in a confirmed PNR. Refer to the Reduce Number in Party ($) section.

15. When deleting more than one name field, delete in reverse numerical order.

16. When deleting more than one name item in a name field, delete in numerical order.
    
    

17. The surnames are renumbered in the PNR after the delete function is performed.

18. Name field entries must contain a Passenger Type Code (PTC) for each first name or initial in each surname. Each PTC is either system placed or entered by the user in the name field entry. PTCs are used to ensure the correct fare application to each passenger in the name field.

19. PTCs must be entered in the same sequence as the initials or titles.

20. A maximum of four different PTCs are allowed in each surname entry.

21. PTCs may be grouped to simplify the entry. The number of PTCs must equal the number in the name entry and the PTC placement must apply to the appropriate initial/title.
    

top of page

Airline Name Change Restrictions

**Does Not Apply** to World Group and Group (C/) PNRs, or car/hotel PNRs if no air segments are present.

Error Responses

NOTES:

1. A KRN table is created for participating airlines only.

2. With multiple airlines the most restrictive parameter applies to the PNR.

3. An itinerary with multiple participating airlines, may have multiple error responses. When this occurs, the error responses are returned in the same order that the airlines appear in the itinerary.

4. Tour or cruise line source PNRs are exempt when the tour or cruise line source segment(s) are the only segments in the PNR.

5. Prior to initial ET, the KRN*I entry can be made to verify if any name change restrictions apply.

6. If any segment in an itinerary is a code share flight, the marketing airline code is used to determine if any restrictions apply.
   
   For example:    /NW 4896Y 24AUG LASSFO SS1 1227A 153A/O$HP2878Y/
   
   In the above example, Northwest Airlines name change restrictions apply. HP name restrictions *do not* apply.

top of page

Customized Name Data

Customized Name Data (CND) consists of two parts:

1. CND, which prints on documents (maximum of 29 alpha/numeric characters).
2. Customized Name Comments, which transmits accounting information (maximum of 114
    alpha/numeric characters).

Explanation	Entry
Name with CND	-SMYTH/GMR@PSPT6678654@
Name with Customized Name Comments	-CLINTOCK/BOBMR@@EMP123@
Name with CND and comments	-QUINN/KATHYMS@DOB14.06.59@8879SB@
Name with CND, comments, and PTC	-SAMS/CMR@5@TVL DEPT@*MIL
Name with CND and comments using the echo function	-SEYMOUR/LIZ$@TECHNICAL DEPT@
Multiple names with CND and comments	-COX/TMR@65@IBM23@/BMRS@61@BT2@
Change CND for N1.2	-1@.2/@1234@
Change comments for N1.2	-1@.2/@@COMMENTS@
Change CND and comments for N1.2	-1@.2/@1234@COMMENTS@
CND and PTC	-BROWN/HMS@DOB100196@*INF
Change CND - all names	-A@23@
Change customized name comments - all names	-A@@CC 132@
Change echo function - all names	-A$@IT DEPT@
Delete CND	-1.3@/@
Delete customized comments	-3@/@@
Delete all CND and customized comments	-2@/@ALL
Delete CND - multiple names	-1-3@/@
Delete customized comments - multiple names	-1.1/1.2@/@@
Delete CND - all names	-A@/@
Delete customized comments - all names	-A@/@@
Delete CND and customized comments - all names	-A@/@ALL
Display PNR with CND	*-HART*CN or *6ZJI4Y*CNT or *1*CNT
Display CND - all names	*NA or *AD
Display CND - name associated	*CN
Display CND - name select	*CN#N2.3
Display CND - name number associated	*CNT

NOTES:

1. A change symbol is required before and after customized name data and comments.

2. Two change symbols are required before a customized comment when customized name data does not precede it.

3. All special characters except the change symbol may be used as customized name data.

4. Customized name data is suppressed from the name field as well as suppressed from PNR retrieval with these entries - *A,*R,*AS,*C,*N,*P.*PD,*PTA a change symbol appears next to each name indicating customized name data exists. For example: 1.2MCCARTHY/MAUREEN.MS@/ROSS@*ADT/C06

5. Customized name data appears in history after it has been changed or deleted.

6. If a surname and/or first name is changed and customize name data exists for that surname and/or first name the following warning tag will be displayed: CUSTOMIZED NAME DATA EXISTS - VERIFY DATA

7. You cannot change a name and delete customized name data in the same entry.

8. End and copy entries are applicable.

9. Customized comment is supported by all interface levels.
   

top of page

Phone Field

The Phone Field is a mandatory PNR data field for the storage of phone numbers relating to the passenger and the customer making the reservation. This field allows for automatic queueing and enables PNR retrieval by name.

top of page

Identifier Codes

Each phone number should have an identifier code following the number.

top of page

Phone Field Order

Entries in the phone field are inputted in the following order:

1. Unique Subscriber Identifier (SID) and customer phone number.
2. Unique SID and passenger's business number(s).
3. Unique SID and passenger's home number(s).
4. Unique SID and nearest downline host city identifier and passenger's enroute phone
   number for downline host airline stations if available.

NOTE: The passenger's business phone is always entered before the home or downline
              numbers.

top of page

Phone Field via OSI

NOTES:

1. The first airline in the itinerary receives the first two phone fields in the PNR via Other Service Information (OSI). The only airline to receive all phone fields is NW.
   
   
2. If a new airline is added as the first segment, a new OSI phone field message is transmitted to that airline.

top of page

Phone Field Entries (9)

The entry code for the phone field is the number 9. Each customer is assigned a unique phone field city identifier. In all cases the first phone field item in each PNR must contain this unique SID in order for the security of the record to be maintained by the customer's office. The phone field can contain up to 99 phone items.

NOTES:

1. In a PNR the phone field is indentified with the letter P- preceding the first phone item.
   
   
2. Each phone item is automatically numbered in the PNR.
   
   
3. Multiple phone field items may be entered by separating each item with an end item (#).
   
   
4. Using a display character (*) in a phone field of a Commercial World PNR must be in specific format.
   
   
5. The following SID codes are not allowed as the first (primary) phone field: CRC - FFB - FQT - GRP - MKC - WAV.
   
   NOTE: WAV may not be used in any phone field and is restricted to host airlines only.
   
   
6. Each phone field must contain at least four, but no more than 69 characters.
   
   
7. The phone field entry may be combined with all PNR field entries except the itinerary field by the use of end item (#) key. It may also be combined with end transaction and queue functions.
   
   
8. World Dial Link 2.1, Commercial World, and Travelshopper PNRs have a seven digit industry number in addition to their unique SID and phone number.
   
   
9. From the unique SID or industry number in the first phone field PNRs are queued for confirmation, schedule changes, ticketing, and enables customers to retrieve the PNR by name only.
   
   
10. A maximum of ten consecutive items can be deleted in one entry.
    
    
11. Changes to a phone field are not automatically generated to an airline unless a change is made to the itinerary.
    
    
12. In order for a PNR transfer to take place, the involved agencies must have a bridge/branch agreements.
    
    
13. Deleting phone filed items or multiple item delete entries may be combined in one entry with the change phone field entry by using the end item (#) function between items.

top of page

Phone Field and World Files

When working with World Files, the following criteria must be met:

     a. The phone number desired as the first phone field is the level one World File
     b.  It must be entered in this format: 9SID 123 555-1234T/AGENCY NAME/$#
     c. The phone field must be an Always or Optional copy item
     d. The phone field must be the first item on its line
     e. If multiple phones are in level one - the first one is the one copied into the PNR
      
top of page

Ticketing Field

The Ticketing Field is a mandatory single item data field. The date entered in the ticketing field must be less than or equal to the time limit date when one is present. An entry indicating specific ticketing arrangments is made in the ticketing field (7) when the passenger had a ticket or definite ticketing arrangement. On a retrieved PNR or redisplayed PNR the ticketing field is identified by t-

top of page

Function Identifiers

There are eight ticket arrangements that can be entered into the Ticketing Field.

• Ticket at Will (7TAW)
• Horizontal Ticketing (7TRH)
• Non-burst Ticketing (7TAS)
• Pre-paid Ticket Advice (7PTA)
• Tax Ticketing (7TAX)
• Ticketed (7/)
• Ticketing Time Limit (8TL)
• Ticketing Queue (7TRL)

top of page

Fare Type Codes

A Fare Type Code may be included in the ticketing field entries. Fare type codes ensure the correct fare application for the itinerary. The fare type codes are entered immediately following the date in the ticketing entry and is separated by an astersik (*). If a fare type code is omitted from the ticketing field entry, Worldspan assumes excusion fare (EX) is the fare type to be used.

top of page

Ticketing Field Queuing

The entry of ticketing identifier codes TAT, TAW, TAS, TRL, TRH, or TAX automatically places the PNR on the queue of the prime phone field city on date specified in the entry. It is the responsibility of each customer to monitor and service these queues daily.

• The participating airline route for rate entry used as an option to queue the PNR to the participating carriers rate desk is entered immediately following the fare type
  code. Fare type codes and the participating carrier route for rate entry are separated by a dash (-).

• The servicing carrier entry used as an option is entered immediately following the fare type code and/or the participating carrier route for rate desk pricing option.  Fare type codes and the servicing carrier codes are separated by a dash (-).

• The servicing airline option enables the automatic printing of the issuing airlines name and airline number in the issued by area of the ticket.

top of page

Ticket Date

The date specified in a ticketing field cannot be prior to todays date, nor after the date of the first flight in the face of the PNR. The ticketing field entry may be combined with all PNR field entries except the itinerary field by the use of the end item (#) key. It may also be combined with end transaction functions.

top of page

Ticket at Will (7TAW)

Ticket at Will places the PNR on the will call ticketing queue for a specific date.

NOTES:

1. Worldspan automatically places the PNR on Q9 of the SID in the first phone field on the date specified in the TAW entry.

2. For World Dial Link 2.1 and Commercial World PNRs are placed on Q0*C13.

3. The PNR is automatically queued to the category number, used in the ticketing field entry (e.g.. 7TAW/04/15JUN would go to category 04 of queue 9).

4. The fare type code appears in the ticketing facts (tkgfax) line immediately following the redisplayed ticketing field.

5. Free form information may be included up to a maximum of 50 characters.

6. The 7TAW field edits for your local date.

7. The ticketing field accepts system stored ticket designators only (e.g., 7TAW/00/15JAN/AD75). If system stored designator is stored in the TAW field and the PNR is priced with 4P, the ticket designator is appended to the fare basis code/ticket designator box on the ticket. For a list of system stored ticket designators refer to 4F/2
   

top of page

Horizontal Ticketing (7TRH)

Horizontal Ticketing allows burst interface ticketing for horizontal ladder ticket stock.

NOTE:  Interface not applicable to World Dial Link 2.1 and Commercial World.

NOTES:

1. The two letter airline code of the validating carrier is mandatory for interface ticketing and if not included in the ticketing field, may be entered in the EZ ticketing entry.

2. Tthe PNRs is automatically be placed on queue 13 of the unique SID in the first phone field on the date specified in the trl/trh entry. PNRs are not placed by Worldspan on queue when the first flt has departed.

3. Tthe PNR is automatically sent to the category number input in the ticketing field entry (e.g., 03) of the ticketing queue 13. Category 4 should not be used in a trh or trl entry. PNRs that fail burst are automatically placed on queue 13 category 4.

4. The fare type code appears in the ticketing facts /tkg fax/ immediately following the redisplayed ticketing field.
   

top of page

Non-Burst Ticketing (7TAS)

Non-burst ticketing inhibits PNR from automatically ticketing with a burst entry used with 20.15 or 11.05 transitional ticket stock.

NOTES:

1. Ticketing not available to Commercial World.

2. PNRs is automatically placed on queue 9 category 20 of the unique SID in the phone field on the date specified in the TAS entry.

3. The fare type code appears in the ticketing facts (tkg fax) immediately following the redisplayed ticketing field.
   

top of page

Prepaid Ticket Advice (7PTA)

The PTA number may be entered in the PNR through the Ticketing Field.

Basic entry: 7PTA01240101234561/NW/US 738.00
                           |                                |             |
                           |                                |           Currency Code    
                           |                               Host Airline        
                         PTA Number

NOTES:

1. Prepaid number must include the check digit.

2. All PTA numbers must begin with number (006) DL or (012) NW. The remainder of the PTA number is 11 digits - the 10 digit number and the check digit from the auditor*s coupon. If the PNR contains all OAL space, refer to the GRS pages for DL/NW to see if they accept OAL validation G/AIR/XX0 (/xx = airline)

3. The NW or DL represents the two-letter code of the airline upon whom the PTA is issued.

4. The total amount of the PTA includes any applicable taxes and must not include the PTA service charge.

5. Tthis field must be entered prior to the 7p/ *purchaser* field.

6. Use the currency code of the country where the prepaid amount is collected. Currency must be a valid ISO code.
   

top of page

Tax Ticketing (7TAX)

Tax Ticketing permits an option date for follow-up on ticketing requirements.

NOTES:

1. Robotics or other PNR interaction may remove PNRs from queue.

2. PNRs containing live or open air segments are automatically placed in the designated category of queue 8 on the date specified in the tax entry according to the SID in the first phone field.

3. If Q8 is not activated for an agency, PNRs are sent to the default queue - Q0.

top of page

Ticketed (7/)

A Ticketed Field indicates in the PNR that a passenger(s) has been completely ticketed.

NOTES:

1. As long as a PNR contains a T/ ticketing field changes made to the itinerary are not passed on to the ticketing record. This means that tickets generated while the ticketing field is T/ could incorrectly reflect the actual itinerary as shown in the PNR. To insure that the
   ticket record properly reflects the itinerary either force the PNR through repricing or create a new active ticketing field prior to generating the ticket.

2. Data after the oblique / is free form. since spaces are not recognized in this field items/words should be separated by a period or dash to maintain clarity. Maximum number of characters is 66.

3. Free form text area is optional.
   

top of page

Ticketing Time Limit (8TL)

Ticketing Time Limit allows for a mandatory ticketing field entry in Prepaid PNRs or when an airline will be ticketing the passenger.

NOTE:

1. OAL ticketing is not recommended for use with system PrePaids.
2. To change a time limit field to a ticketing field (7) use 7.

top of page

Ticketing Queue (7TRL)

Ticketing Queue allows burst interface ticketing (vertical ladder). For interface using vertical ladder ticket stock.

top of page

Received from Field

The Received from Field stores information in the PNR history indicating who made the reservation or any changes to the PNR.

NOTES:

1. The received from field is a single item field.

2. The received from field is stored in the history of the PNR when the name, itinerary, phone, and ticketing fields are changed. It is identified by R-.

3. The received from field can be changed once prior to end transaction.

4. The received from field has a minimum of two and a maximum of 69 characters permitted.
   

top of page

Form of Payment (FOP)

If two people are in a PNR with separate forms of payment, use the Document Instruction (DI) entry to indicate the different forms of payment. Name 1.1 4-DI#N1.1#$CK Name 2.0 4-DI#N2.0#$CCAX543198763026800P0705

The FOP is not a mandatory field, however, a FOP must be stored in the PNR or included in the ticketing entry in order to produce a ticket. The FOP field can contain three types of data such as: cash, check, or credit card. In the credit card example listed below, the P means physically present and the N means not physically present.

Review the airline GRS page (e.g., G/AIR/XX0) to verify each airline credit card acceptance policy. The XX = airline code.

top of page

Manual Credit Card Approval Code

NOTE:  Refer to the Credit Card ID Verification topic for the Card ID/Card Security Code (CID)
              policies.

top of page

Commission (5-CM)

The function of the Commission Remark records the commission made from the sale of a ticket. The function identifier is 5-CM

Commission may be recorded as:

• A dollar amount
  
• A percentage amount
  
• A combination of both dollar and percent

The Passenger Type Code (PTC) must match the PTC used in the name field of that PNR. The
5-CM field may contain a maximum of four PTCs. Each PTC - commission item must be separated by the change symbol (@).

top of page

Client Account Number (5-CA)

The Client Account Number Remark creates a client account number that prints on the document. The function identifier is 5-CA

NOTE: A maximum of 14 characters print in the client account area of the itinerary/invoice.

top of page

Client Billing Address (5-CB)

The function of the Client Billing Address Remark creates a billing address that prints on the document. The function identifier is 5-CB

NOTE: Up to six 5-CB lines per PNR (maximum 35 characters per line). Six lines print only
             when using blank itinerary/invoice options - BV, BVD, HV, HVD otherwise, five lines
             print. Prints on the upper right side of the itinerary/invoice if used in conjunction with
             the 5-CD otherwise, it prints on the upper left side of the itinerary/invoice.

top of page

Client Delivery Address (5-CD)

The function of the Client Delivery Address Remark creates a delivery address that prints on a document. The function identifier is 5-CD

NOTE: Up to six 5-CD lines per PNR (maximum 32 characters per line). Prints on the              upper left side of the itinerary/invoice.

NOTE: Default print position is 5-CD on left side of page and 5-CB on right. The #R in
             EZ options reverses these positions and prints 5-CD on right and 5-CB on left.

top of page

Endorsement Restriction (5-ER)

The function of the Endorsement Restriction Remark storages ticket endorsement remarks in a PNR.

Function Identifier:

• 5-ER text or code - 1 Line
  
• 5-ER text * text     - 2 lines
  
• 5-ER code * code - 2 lines
  
• 5-ER code @ text - 1 code with insert
  
  

top of page

Invoice Remarks (5IR-)

Invoice remarks (maximum 66 characters) print on combined itinerary/invoice documents.

NOTE: Segment associated remarks are not automatically canceled or renumbered when              the itinerary is changed.

top of page

Itinerary Remarks (5RM-)

Itinerary remarks (maximum 66 characters) print on a combined itinerary/invoice with EZL or an itinerary with EZN.

top of page

General Remarks (5)

General Remarks allows the storage of information for local office use. The function identifier is 5 and free form information.

NOTE: Stored information in the remarks field has unlimited number of lines.

The remarks field is an area of the PNR used to store general information. These remarks do not print on any document or transmit in the booking message.

top of page

Unique Remarks (5.)

The Unique Remarks store information in a client's PNR for local office use. The function identifier is 5. (followed by a single alpha character and free form information).

Unique remarks are used to categorize information in a PNR. There are unique remarks for each letter of the alphabet. For instance, all car information might be entered using a 5.C remark. The 5.Z remark is the only unique remark that appears in history.

Unique remarks do not print on any document or ship in the booking message. Unique remarks are suppressed from view in the PNR.

top of page

Special Service Request

A Special Service Request (SSR) is used to request a service and/or a reply from an airline. Each request must include a four letter SSR code. For a index of codes, see HELP SSRC. Special Service Requests are used to request such things as meals, wheelchairs, special assistance, and notification of frequent flyer numbers. Worldspan assumes the request is for all passengers in the PNR if name select is not used in the entry.

top of page

Request SSR's - Segment/Name Select

Special Service Request (SSR) or Other Service Information (OSI) requests are stored in the General Fax (GFAX) area of the PNR.

If a meal is requested for a NW flight with no meal service offered, the response is NO MEAL SERVICE and gives the segment numbers to which it applies. OALs accept the request, but after ET a UN is returned by the airline indicating no meal service is offered on the flight.

top of page

Wheelchair Assistance

Wheelchair assistance information does not print on the itinerary and invoices.

top of page  

Modify/Delete SSR

Modify/Delete Special Service Request (SSR) Entries

top of page  

Frequent Flyer

Frequent Flyer Entries

NOTE: Because you cannot modify and name select in one entry to change a FQTV item,              you must delete the old item and re-enter the new.

top of page  

Other Service Information

Other Service Information (OSI) is used to ship information to another airline for notification only. No response is required from the airline. An OSI is stored in the General Fax field (GFAX) area of a PNR.

top of page

Display Portions of a PNR

A PNR can be displayed by air, car, hotel, name, open segment, waitlist, record locator, and travel segment. A specific PNR can be retrieved from storage that has previously undergone a successful End Transaction (ET). The function identifier is *

top of page

Divide PNR

A PNR should be divided when one or more passengers in a PNR wish to change their reservations so that the itinerary is no longer the same as the remaining members in the party. A PNR should also be divided when one or more passengers in a multi-party PNR wishes to change or rebook their itinerary or to avoid cancellation and rebook of current seat assignments.

• The original record must be divided into two or more PNRs, the itinerary canceled, and the new itinerary added into the remaining.

• If a divide is made without changes to the itinerary , the larger airlines will process the divide. Many smaller airlines will ignore the divide request. Check with each airline before initiating a divide.

• It is not necessary to cancel seats before the divide function.
  

• All passenger data items except for non-applicable Special Service Request (SSR) name select items appear in the divided PNR. Those items (e.g., phone fields) that do not pertain to the divided record must be changed or deleted.
  

• Non-airline (auxiliary) segments do not appear in the divided PNR, they remain on the original record.

• In a divide PNR function, name changes are not allowed
  

• A remarks entry indicating that a PNR has been divided and the file address will be automatically appended to the divided and original (Parent) PNRs.
  
  
• A new file address will be assigned to the divided PNR(s) after End Transaction (ET) while the Parent PNR retains the original file address.
  
  
• A Prepaid (PTA) PNR may not be divided. If a divide is necessary, then contact the validating carriers PTA desk.
  
  
• A non-air PNR may not be divided.
  
  
• When a PNR contains a stored fare quote and a divide has been done the original date agent sine and SID remains in both the divided PNR and the new PNR.
  
  
• When a PNR is divided, any SSRs associated with the divided out name will automatically follow that name into the divided-out (filed) PNR. The Parent PNR retains the SSR's associated to the name(s) remaining in the Parent PNR name field.

• Divide/reduce to an ETKT PNR does not result in changes to the ETR.
  

• When a PNR containing document instructions is divided, the document instructions copy to the divided PNR and remain in the parent PNR.

• When a PNR containing ticketing records is divided, the ticketing records remain in the parent PNR and do not copy to the divided PNR.

• If two or more segments are married and the PNR is divided, the marriages are retained. If a cancel/rebook is initiated during the divide transaction, married segment logic applies.

* Divide is used when some of the passengers want to travel on    different dates from the others. * Reduce is used when one or more, but not all passengers, want to    cancel their trip.    NOTE: Do not divide a PNR if there are no changes to the itinerary.               Some airlines reject divide messages when no changes are               made.

top of page

Divide PNR Entries

NOTES:

1. To return the modified PNR to storage, the divided record must be filed by entering the alpha F. Make all necessary changes to the divide PNR before filing. This ensures the most current information is sent to the airline involved.
   
   
2. At any time prior to End Transaction (ET) the PNR may be returned to it's original condition by ignoring the PNR.
   
   
3. An asterisk (*) is used as an item separator when dividing more than one surname item (e.g., d3*4.2).
   
   
4. When dividing multiple name items within the same name field, a period must be used (e.g., d3.2).
   
   
5. The divided out PNR shows SPLIT PTY information. The parent PNR shows a SPLIT RMK item.
   
   
6. When dividing multiple name items in the same transaction, they must be divided in low to high order (e.g., d1*3 or d1.3.5*4).
   
   
7. After filing the divided PNR, additional divide entries may be made prior to ET.
   
   
8. ER and IR are not allowed during a divide function.
   
   
9. Commerical World users cannot ET, therefore the entry QEP must be used after the divide.
   
   
10. When the divide or reduce number of party entries are made on a PNR containing automated MCO data, thefollowing message is displayed to advise that MCO data
    exists and may have impact on the data in the MCO template: VERFIY AUTOMATED MCO DATA

top of page

Reduce Number in Party ($)

A PNR should be reduced when one or more passengers in a PNR wish to completely cancel their reservations and the remaining passengers do not wish to change their reservations:

• The reduce function reduces the number of seats being held on all flight segments to the desired number.
  
  
• The reduce function can also reduce the number in party for manual car, hotel and auxiliary segments, this includes Travel Segments.
  
  NOTE: Automated car and hotel segments booked through the system cannot be              reduced. The exception is OTS and PTS segments.
  
  
• The reduce function does not take action on passenger data fields. Thus, the applicable name(s) and any other passenger data that no longer applies to the PNR must be deleted or changed to the applicable number in party.
  
  
• Existing flight segments may not be changed during a reduce function. However new flights may be added to the PNR. If changes and cancellations are required, complete the reduce function, ET, and re-retrieve the PNR then make the necessary changes.
  
  
• A Prepaid (PTA) PNR may not be reduced.
  
  
• Only the reduced name change transactions will appear in history.
  
  
• A maximum of 99 AUX segments.
  
  
• The entry to reduce only AUX segments does not apply to segments with more than nine seats such as group bookings or corporate PNRs.
  
  
• If an ETKT PNR is reduced the ETA for the name(s) being eliminated is removed from suppressed items and added to PNR history.
  
  
• Divide/reduce to an ETKT PNR does not result in changes to the ETR. When a PNR is reduced, the associated ticket must be refunded/exchanged or voided.

Reduce number in party entries. The function identifier for reduce is $

NOTES:

1. Reduced AUX segments do not go to PNR history. Only the name appears in history.
   
   
2. The applicable SSR seat items are removed from the PNR for the name field(s) reduced upon ET.
   
   
3. If SSR seat items exist, 4RX0AL or 4R@ALL must be entered prior to the reduce function.
   
   
4. Reduce for AUX segments does not generate a cancelation message to the AUX provider.
   
   
5. If two or more segments are married and the PNR is reduced, the marriages are retained. If a cancel/rebook is initiated during the reduce transaction, married segment logic applies.
   

top of page

End and Copy/Clone a PNR (Air/Car/Hotel)

End and Copy (EC) entries End Transaction (ET) on the current PNR and use the items selected to create a new PNR. EC can be used on any newly created or retrieved PNR. Any part of a PNR may be copied with the exception of the following:

• Ticketing Field
• Flown or departed segments
• GFAX items
• Seat assignments
• Segments with status code of UN, UC, WK, or DS
• Remarks fields created by Worldspan (e.g., QR remarks, ACKNs, and ET edit items)
  

When EC is entered, the response is a newly created PNR. If some flights are not available or do not operate, the message *COPY COMPLETE CHECK SEGMENT STATUS* will be received. The agent would need to display the itinerary and update any unconfirmed flights by selling alternate flights.

Direct Sell flights are requested via the link. If the Direct Sell line is not available, Worldspan will attempt to request the flights using Direct Access. If Direct Sell/Direct Access are unavailable, the flights will be sold through Worldspan availability.

The EC function cannot be performed while in the insert mode, in queue, during a divide function or on an Amtrak PNR. Examples of EC entries with options are shown below.

top of page

Ignore PNR

The Ignore function is sometimes necessary when misinformation is added to a PNR. This function can be used either prior or after ET has been performed.

NOTES:

1. IGN or I ignores completely ignores a newly created PNR prior to ET.
   
   
2. *IR ignores any changes made and redisplays the PNR in the original form
   
   
3. IS ignores any changes made except any SSR transactions such as seats, frequent flyer information, and passport information.
   
   
4. Using the ignore function is permitted while in a queue.
   
   
5. IS is valid only when a simultaneous change situation occurs unless the change results from a change to the PNR name field, itinerary, or seat assignments during the other transaction.
   
   
6. ET must be performed in order to make the seat/boarding pass changes permanent in the PNR.

top of page

End Transaction

End Transaction (ET) must be performed when the PNR is completed. End Transaction stores the PNR and generates a booking message to every airline in the record.

At ET a check is made to ensure that the PNR contains each mandatory field and that the itinerary has correct date and city continuity. Worldspan then assigns a Record Locator to each PNR.

When used in combination with PNR data or World File Copy and end items (#), ER
must be the last item in the entry.

top of page

Simultaneous Changes

Simultaneous changes to PNR may occur on a subsequent ET or ER under the following conditions:

• Receiving acknowledement from a Direct Access airline or Amtrak.
• Schedule changes
• Confirmation of pending space
• Receiving car or hotel confirmation numbers

When this occurs, type IR (ignore and redisplay).All transactions made to the PNR are ignored.

ER is not allowed when dividing PNRs. The error response is RESTRICTED. E ends the transaction when dividing the PNR.

The entry to work a PNR when schedule changes come from an airline is: EW - To end the PNR and work the schedule change EWR - To end, work the schedule change, and redisplay the PNR

top of page

Infant PNR

A single PNR can be created with both the adult and infant passenger(s) or infant passenger(s) alone for the pricing of domestic PNRs and pricing/ticketing of international PNRs.

NOTES:

1. The number of INF PTC codes must be equal to or less than the number of non-infant when they are in the same PNR.

2. Whether the infant name is entered with or without other passengers, the infant name/PTC is automatically separated from the other names.  For example -
            Entry        -PERSON/KRISTIN/MARK/MARY*2ADT/INF
            Response - 1.2PERSON/KRISTIN/MARK*2ADT 2.1PERSON/MARY*INF

3. Changes cannot be made to the INF PTC after the initial ET.  Infant name must be deleted and re-entered.

4. Passive space MK must be booked for an infant in a stand alone infant PNR.

5. Seat assignments are not reserved for PTC code INF

6. At the time of ET, an OSI automatically goes to the applicable airlines to notify them of the infant.

7. To ensure autopricing of a PNR that contains both infant and adult passengers, the name field must include the INF PTC.

8. Adding or removing an INF PTC from an existing PNR affects the previously stored fare.

9. An autopriced infant ticket is inhibited for travel solely within the 50 United States. However, if the PNR is manually priced a ticket will issue for the infant even though the fare displays $0.00.

10. The following items print on the international infant ticket in the designated areas:
    Endorsement - No-Seat/Infant PNR and Status Box - NS.

11. Infant tickets are exempted from PFC charges and some taxes.

12. The infant passenger cannot be divided out of a PNR that contains adult passengers. To remove the infant from this PNR, cancel the infant name field.  An infant passenger can be divided from a PNR that only contains infant passengers.

13. Customized name data may be used with the INF PTC.

14. A SSR can only be associated to the INF PTC for NW.

15. If the infant appears in the PNRs alone, any cars/ hotels or air segments must be entered in as MK.
    
    
16. Prepaid tickets are not permitted with stand-alone infant PNRs.

top of page

Claim PNR

The format to claim a PNR varies from one airline to another. To display a list of airlines requiring you to claim PNRs in Worldspan, see HELP CLAIM (from this HELP page, Tab into the airlines own formats.)

top of page

Past Date PNRs

A Past Date is a PNR with at least one segment of the itinerary that has passed the day of travel. Each PNR containing a segment with today's date is copied to a file and added in the past date PNR database in an overnight process for that day.

Example: A PNR with a segment dated on 25JUL would have all the information in that PNR downloaded in a file for 25JUL. If the itinerary included a segment with a return date of 01AUG and changes were made to the itinerary on 28JUL the file for 25JUL would not reflect those changes. The past date should be requested for the 01AUG segment date to obtain a complete pastd ate with changes.

Once an itinerary segment becomes past date, the PNR can no longer be retrieved by that past date segment. The segment can still be viewed in history with *H until the entire PNR is purged from Worldspan 30 days after the last segment date.

Example: A PNR with a segment date 06JUN cannot be retrieved by that segment date after 08JUN, but the PNR can still be retrieved by record locator, SID-LASTNAME or any active segment in the PNR. When all segments in a PNR are past date, the only way to retrieve the PNR is by record locator or by SID-LASTNAME.

Once a PNR is purged the only access you have to the PNR is via a pastdate request.

top of page

Requesting a Past Date

There are three methods worldspan provides when requesting a Past Date.

For agencies not receiving microfiche individual past date requests may be submitted to the worldspan help desk 30 days after any purged segment in the PNR. Agencies following the EU regulations may request a past date three days after any purged segment and may only request a pastdate for billing disputes. To request, use the template under help pastdate a copy of the pastdate is returned to your agency via e-mail or fax. Required information is indicated with an (*) in the template and must be provided to complete the request. A past date can be requested by any segment that was present in the PNR, traveled or canceled. The Worldspan automation support department processes these requests from daily CD's.

For agencies having microfiche viewing equipment Worldspan provides a product to give those agencies weekly microfiche. This product is not recommended for new agencies. Microfiche is not applicable to countries following European Union regulations.

As a last resort, you may request past date records through your Account Executive. The request may not exceed a six month travel period of the prior 12 months additional fees may apply, contact your Account Executive for information.

Past dates may be requested using any segment residing in the PNR. For the most complete documentation request a past date using the most recent pastdate segment.

top of page

Reading a Past Date

Past Date records contain all information present in the PNR at the time the record is purged from Worldspan. Exceptions are: Electronic Ticket Acknowledgement/Authorization (ETA) and additional fee remarks.

A past date reading order is the same as an active PNR. The most recent segments are on top and reading proceeds downward. History follows and the name field and RLOC are located in the top left hand column. The PNR creation date is always on the first line prior to the purge (purg) date.

Information contained in the face of the PNR at the time of the purge is on top to the right of the name field. History begins after the purge date. A five digit space separates the live PNR information from the history. If the space is blank this indicates all space was canceled before the PNR was purge and shows in the history area below.

Each line of history indented from the left margin represents one transaction. A line starting with a SID indicates the change has been made. A line starting with a city code or headquarters indicates an associate (e.g., airline/car/hotel) sent the information. The received from is found at the end of each transaction line.

Within each transaction individual entries or modifications are numbered in parentheses (01) (02). This is followed by the action code for that entry. The action/advice codes recorded for the itinerary are followed by the number in part. For example, HK/NN/02/0 indicates the segment was requested with an NN action code for two people.

Past date records contain all information present in the PNR at the time the record is purged from Worldspan. Exception: ETA additional fee remarks.

If a remark is removed from the PNR before the PNR is purged, the remark does not reflect on the past date. With the exception of the 5.z remark, they are the only remarks stored in the history of the PNR when added/modified or deleted.

If the PNR is divided, request the parent (original) PNR, which contains history prior to the divide.

top of page

Function Identifiers

*Not* applicable to Worldspan Commercial World® or Worldspan World Dial Link®.

top of page

PNR Purge Date

After the initial End Transaction (ET), a purge date is computed for a PNR. The purge date is determined by the first phone field in the PNR. With the exceptions of EU countries and prepaids, all PNRs are purged 30 days after the most future segment. An EU country PNR is purged two days after the most future segment and the purge date is the same as the most future segment. The purge date is placed on the second line of history.

To entry to view the purge dates in PNR history is *H

Passenger Type Codes

Certain Passenger Type Codes (PTC) alter the standard data and have certain sales restrictions such as age, form of payment, possession of a valid frequent flyer identification card, or sales location. This can only be enforced by the ticket issuer at the time of ticketing. The ticket issuer is responsible for ensuring that the passenger meets all applicable qualifications.

NOTES:

1. The passenger type select option is used when there is a need to override the existing PTCs in the PNR.

2. If no name field yet exists, one or multiple PTCs may be specified. However, the number of PTCs cannot exceed the number of seats booked.

3. Multiple PTCs are separated with an slash (/).

4. The numeric number 02-11 can be added in place of the NN on the CNN PTC. For example: *C05.

5. The following PTCs print various information on the ticket.
   
   -SMITH/MARY/JANE*ADT/INF *INF
   -SMITH/MARY/JANE*ADT/CNN *CHD
   -SMITH/LISA*C06 *C06
   

6. To ensure appropriate cabin counts, update infant PNRs with appropriate PTC. OSI messages are sent to an airline automatically with a INF PTC. Manual OSI messages are sent with a INS PTC.

top of page

© 2002 Worldspan L.P.  All Rights Reserved.

Last Updated: January 19, 2005  ALN