Task: Flight-Specific Fare Quote

This task finds the lowest price and book information for the specific booked itinerary.

If booking codes are requested, this task finds the lowest price for requested booking codes.

Section 1: Short Answer

Transaction Name:

FareQuoteFlightSpecific_9

Can any other transaction(s) perform this same task?

No.

Can this task be performed in a sessionless environment?

Yes.

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

Yes.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

<NewBICSegMapping> returns the booking codes. For the new fare quote to be valid, the user must book.

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

The itinerary has a maximum of eight segments; requesting more than eight segments returns an error.

If the task is used for booking codes request, be aware that most of the discounted booking classes have round trip requirement, and using different booking codes as a request for each of the leg of the round trip may cause “NO VALID FARE FOR INPUT CRITERIA” in the response message.

Section 2: Detailed Description

Request:

<FlightSpecificBestBuyMods> must be sent with <SegInfo>, which contains flight information, and <PassengerType>, which contains passenger information.

Other data in the request can include:

• A <GenQuoteInfo> element to include ticket dates in the request. If no dates are sent, today’s date is assumed.
   
• For a historical fare quote, <GenQuoteInfo> must include ticket dates. For an accurate historical quote, a <SegSelection> element with <FareType> set to ‘F’, and a fare basis code <FIC> are recommended.
   
• For an Airline Private Fares quote, the <SegSelection> element must be sent with the indicator for <ReqAirVPFs> set to ‘Y’ and a <PFQual> section. Within the Private Fares section, the types of fares considered can be further restricted for the input segment/segment range. Limitations can include:
  • The types of fares (both public and private fares or only private fares).
  • The types of private fares (only airline private fares or only agency private fares).
  • The requirement for account code usage (only fares for the input account code and input contract, if any or no restriction on account code usage).

  The response formats do not vary if Airline Private Fares are returned.
   

• For public and private fares to be considered in the response, the <PublishedFaresInd> child element in <SegSelection>  must be set to 'Y'. The lowest fares, whether public or private are returned. If public fares will not be considered, <PublishedFaresInd> must be set to 'N'.
   
• The <PassengerType> element support several functions. <PassengerType> can be used to:

• Supply personal geography details in the request, which allow pricing of fares that have geographical restrictions, such as country residency or state employment. Fares that have geographical restrictions are not quoted unless matching personal geography information for the passenger is sent in the request.

Without appropriate personal geography information, a user may not receive a lower fare based on their request. If a lower fare is NOT returned, either higher fares or an error response are returned.

• Enter an amount increase (IF) or decrease (DF) of more than six characters when necessary, e.g., 'IF20000'.

• Supply Spanish residency modifiers in the request, which allows the pricing of Spanish resident fares:

  • A Spanish resident fare can only be quoted if the appropriate Spanish resident PTC and Spanish resident modifier is given in the request.
  • You must use the Spanish modifier in conjunction with the residency SSR from the booking file to provide required residency information.

• Enter a PTC and a discount in the <PassengerType> in a single request.

  Note: The use of proprietary Galileo International Passenger Information Codes (PIC) was discontinued in early 2005. PICs have been been replaced with ATPCo Passenger Type Codes (PTC).

  Previously, PIC data was sent in the <PIC> child element within <PsgrMods> or <FqPicOnly>. While these elements are still available, it is now recommended to send PTCs using the <PTC> child element in <PassengerType>.

  The <PassengerType> element also allows the <PricePTCOnly> (PIC Only) search to be requested for fares for a specific PTC only (similar to <FqPicOnly>).

• Override any fare ticket codes or designators using the <TkDesignator> and <TkCode> elements.

Prerequisite tasks:

Before sending the request, the user should check flight availability. See the AirAvailability_# transaction; task Air Availability.

Expected response:

A successful response includes the <NewBICSegMapping> element, which details the classes for which the itinerary needs to be booked to qualify for the best price. If the itinerary is already booked in the cheapest class, <NewBICSegMapping> is not returned.

Error and warning responses:

The following error messages might display:

• Invalid Sequence (origin/destination in wrong order)
• Invalid dates, city codes, carriers, etc.
• Unable to Fare Quote
• No valid fare for input criteria
• Multiple Fares Exist for Same Fare Amount

The following warning messages might display:

• Must be e-ticket or paper ticket
• Plating Carrier Restriction
• Best fare for PTC passenger
• Not valid before/after XXX date

Follow-on requests:

The follow-on requests are as follows:

• FareQuoteMultiDisplay_# – Rules Display.
• Routes Display (optional).
• PNRBFManagement_# - Air segment sell via direct sell.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

FareQuoteFlightSpecific_9_s1

FareQuoteFlightSpecific_9_s2

FareQuoteFlightSpecific_9_s3