Task: PNR/BF Retrieve by Record Locator

This task allows the user to retrieve an existing PNR/BF by the record locator of the PNR/BF.

Section 1: Short Answer

Transaction Name:

PNRBFManagement_30

Can any other transactions perform this same task?

Previous versions of PNRBFManagement, AgencyPNRBFDisplay, CarHotelPNRBFModify, and CarRulesPNRBF all have processes to retrieve an existing PNR/BF by record locator.

• PNRBFBuildModify and CarHotelPNRBFModify can be used in a sessioned or sessionless environment to retrieve an existing PNR/BF, and make modifications to PNR/BF information as well as Car and Hotel Itinerary.
• CarRulesPNRBF can be used in a sessioned or sessionless environment to retrieve car rule information from an existing PNR/BF.
• PNRBFManagement_30 is the preferred transaction for a simple retrieval of the PNR/BF.

Can this task be performed in a sessionless environment?

This task can be performed in a sessioned or sessionless environment. However, in a sessionless environment, the data is not accessible for any type of follow-on action.

Dividing in conjunction with this task requires a sessioned environment. See the documentation for PNRBFDivide.

Are the request and response identical on both the Apollo and Galileo systems?

The request and response information is identical on both the Apollo and Galileo systems. If an error occurs, the actual error text may differ, but the formats are identical.

List any industry-specific knowledge required to understand this task.

For this task, the user must already have the Record Locator. The user should also be aware of the security in place when attempting to retrieve a PNR/BF that they do not own.

Explain any special limits or distinct restrictions.

The user must have the authority to look at the requested PNR/BF. If the user is retrieving a PNR/BF they own, no security checks are required. If the PNR/BF belongs to someone else, security checks are made to ensure the user has the proper authority. All security checks are based on information in the existing AAA. 

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

For a PNR/BF retrieve by Record Locator request, a <PNRBFRetrieveMods> (2024) is required with a <PNRAddr> element.  <PNRAddr> must contain the record locator of the requested PNR/BF. If the request is for a PNR/BF outside of the client’s CRS, a <TargetCRSInfo> element must also be supplied, with the CRS where the PNR/BF resides.

There is also an option to retrieve only certain pieces of the requested PNR/BF. For this option, a <RequiredData> element that lists the types of data requested is required.

Prerequisite tasks:

No prerequisite tasks apply.

Expected response:

The response from a retrieve of the currently active PNR/BF is a <PNRBFRetrieve> (2025), with all of the PNR/BF data requested in the specified elements as listed in Section 3. If a <RequiredData> element is in the request, only the types of data requested in <RequiredData> element are returned in the <PNRBFRetrieve>.

<Control> is always the first element in a non-error response. This element contains the information about the remainder of the response, including the total number of main elements, and the Record ID and number of each type of main elements returned.

Following are any items with special characteristics.

Form of Payment

For Form of Payment, one of three elements are returned: <CreditCardFOP>, <CheckFOP>, and <OtherFOP>. Only one Form of Payment can be added to a PNR/BF, so only one of these three elements is present in the response.

Name

The <LNameInfo> and <FNameInfo> elements are for Last Name and First Name, respectively. The <PsgrsName> element is a mix of <LNameInfo> and <FNameInfo> elements along with some additional information like infant’s date of birth, adult infant association number, etc. The number of <LNameInfo>, <FNameInfo>, and <PsgrsName> elements is shown in <Control>, but may not reflect the order exactly.

• If there is more than one surname in the PNR/BF, a set of <LNameInfo>/<FNameInfo>/<PsgrsName> elements exist for each Last Name/First Name combination.

• If there is only one surname but multiple first names, only one <LNameInfo> exists, followed by a <FNameInfo> and <PsgrsName> for each first name.

Itinerary

For all types of Itinerary (Air, Car, Hotel, etc.), there are primary elements, which have the basic itinerary information, and secondary elements, which have additional information such as Change of Gauge, Operated By, and Optional Car or Hotel data.

The order for this information is Primary followed by any Secondary(s) that apply to the Primary. For example, an <AirSeg> element followed by an <AirSegOpAirV> followed by an <AirSegDetail> followed by the next <AirSeg> element.

The order of the Primary Itinerary elements is determined by their location in the PNR/BF. The maximum number of Itinerary items in a PNR/BF is 99, so the combination of all types of Primary Itinerary elements cannot exceed 99. The total number of each Primary and Secondary elements is shown in <Control>, but may not reflect the order exactly.

Seats

For seat information, there is a <SeatSeg> element for each segment. Following the <SeatSeg> is be a <SeatAssignment> element for each passenger for that segment. The total number of <SeatSeg> and <SeatAssignment> elements is shown in the <Control> element, but may not reflect the order exactly.

Special Services (SSRs) and Other Special Services (OSIs)

For Special Service Information (SSRs), there is a <NonProgramaticSSR> (Manual SSR) element or <ProgramaticSSR> element for each SSR. There is an <OSI> element for each OSI. The combination of SSRs and OSIs cannot exceed 255 in the PNR/BF.

The <NonProgramaticSSR>/<ProgramaticSSR> elements are in the order they are in the PNR/BF and, therefore, may be mixed. In addition, if there is free text for a Programmatic SSR, the <ProgramaticSSRText> element, which immediately follows the applicable <ProgramaticSSR> element. The total number of <NonProgramaticSSR>, <ProgramaticSSR>, and <ProgramaticSSRText> elements is shown in the <Control> element, but may not reflect the order exactly.

Ticketing Arrangement

For ticketing arrangement, there is a possible one of five elements that can be returned: <TkArrangement>, <TAUTkArrangement>, <TAWTkArrangement>, <TLTkArrangement>, and <TAMkArrangement>. Only one type of Ticketing Arrangement can be added to a PNR/BF, so only one of the five elements is present in a response.

Mileage Membership Number

For mileage membership number, there is a possibility of three elements that can be returned: <FreqCustInfo>, <CrossAccrual>, and <FreqCustInfoEx>.

• <FreqCustInfo> for frequent flyer information.

• <CrossAccrual> for cross accrual carriers.

• <FreqCustInfoEx> (for interactive FQTV vendors) will also be returned with <FreqCustInfo> containing additional FF data.
  Note: FQTV customers' products can be modified to not use and ignore <FreqCustInfoEx> data and continue to parse <FreqCustInfo>.

  • Products requiring <FreqCustInfoEx> data can parse associated data and ignore <FreqCustInfo>.

  • <CrossAccrual continues to be returned for cross accrual carriers associated with <FreqCustInfo>.
    

Error and warning responses:

The most common error returned is an error that the Record Locator or File Address is not valid for a PNR/BF.

Follow-on requests:

For a sessioned environment, numerous follow-on requests can be made. Additional data can be added to the PNR/BF, or current information in the PNR/BF can be changed or deleted. In a sessionless environment, no follow-on entries are available, because the data is no longer available after the transaction completes.

There are several other tasks that can be done in conjunction with the retrieval of the PNR/BF, or that can be done as a follow-on request in a sessioned environment. These tasks are:

•  Fare Redisplay

• Retrieve TravelScreen Status

• Retrieve AAA information

These tasks can be combined and the user can choose which task, if any, to include.

Section 3: Tables

1) Retrieve by Record Locator (Same CRS)

Request (Input) Tags

Response (Output) Tags

2) Retrieve by Record Locator (Different CRS)

Request (Input) Tags

Response (Output) Tags

Related Samples

PNRBFManagement_30_s10

PNRBFManagement_30_s36

PNRBFManagement_30_s103