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.

See the Air Shop FAQ for questions regarding all air shopping transactions.

Section 1: Short Answer

Transaction Name:

FareQuoteFlightSpecific_15

Can this task be performed in a sessionless environment?

Yes.

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

No. Some functionality is CRS-specific. See the Request topic in Section 2.

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:

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

<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.
If the user wishes to define whether the most restrictive rules for the entire quote (single fare component) are returned in <RsvnRules>, <GenQuoteInfo> must be sent with the <RulesProcess> indicator set to N. If the indicator is set to Y, applicable rules are returned in <AdvRsvnTktRule>/ <MinStayRule>/ <MaxStayRule>/ <SalesRestrictionsRule>/ <PenaltiesRule> per fare component.
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 Galileo CRS includes cancel/rebook change fees (coded in Category 16 Penalties) in a fare quote. Under certain conditions, the airline may waive these fees by providing a waiver to the agency. The <WaiverMods> allows the agent to provide a waiver to bypass automated change fee collection. This waiver code can be 10-14 alpha-numeric characters long.
Fares with rule category 35 (CAT 35) data, which is net fare information, will potentially contain multiple fare levels: sell, net, ticket-audit, ticket-passenger. For users requesting the additional CAT 35 data, this information is returned in the elements identified with an asterisk (*) within the <FareInfo> response (see the Response table in Section 3).
Note: The <EnhancedPrivateFare> (GFPX KLR) is used for rules follow-ons. It is returned with rules follow-on transactions so that the correct rules text displays. Do not use or modify anything in this element.
Point-to-Point Availability: This functionality is available on the Apollo (1V) and Galileo (1G) CRS. On the Apollo CRS, If the user wishes Point to Point Availability to be considered for connecting flights, the <GenQuoteInfo> element must be included, with the indicator for Point to Point Availability set to Y. Galileo CRS users do not need to set this field. See Point to Point, Partial Thru, and O&D Faring and Shopping.
- The user’s AAT must have the field FPTP set to YES. If FPTP is set to NO, that will override a Y setting in the <GenQuoteInfo>.
- When the 1425 <FareInfo> returns Point to Point booking codes in the GFBK <NewBICSegMapping> for connecting flights, a <PtToPtAvail> node indicator is set to Y in the GFIS <ItinSeg> elements for the connecting flights, and the <AvailLinkStatus> node is set to Y' or 'J.'
- If the user wants to Sell or Rebook flights after using this XML Transaction, the <AirSegSell> or <AirSellRebookMods> elements must be used. The Availability Journey Indicator in the <AirSegSell> or <AirSellRebookMods> elements should be left blank if the connecting flights are using point to point booking codes (check results of the Point to Point indicator in the <ItinSeg> element). See Task: Air Segment Sell via Direct Sell and Task: Change Segment via Rebook in the PNRBFManagement transaction help for more information on using <AirSegSell> or <AirSellRebookMods>.
- If the user does perform "Sells" or "Rebooks" after using this XML Transaction, they should only send in the <GenQuoteInfo> indicator if they have made the supporting changes required for the <AirSegSell> or <AirSellRebookMods> elements.
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 by Travelport 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
Unable to File Fare - Conflicting Net Ticket Data Exists.
If this occurs, autoprice the fare without Force Fare Override (FIC). Use GQSS <SegSelection> KLR / <FIC> in FareQuoteClassSpecific or FareQuoteStandard. Or, autoprice the fare with the correct ticket PCC in the GQQM <GenQuoteInfo> KLR, in the <TkAgncyPCC> field.

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

<FlightSpecificBestBuyMods>

Terminal Equivalents:

Apollo: Not applicable

Galileo: Not applicable

Ordering	KLR	Min/Max	XML Tag
A	GQFS	1-1	<SegInfo>
A	GQNP or GQPA	1-4	<PsgrMods> <PassengerType>
B	GQQM	0-1	<GenQuoteInfo>
B	GQTE	0-1	<TaxExemptMods>
B	GQFP	0-1	<GenFarePrefs>
B	GQPC	0-1	<PlatingAirVMods>
B	GQSR	0-8	<SegmentMods>
B	GQSS	0-8	<SegSelection> (Private Fares only)
B	GQRC	0-1	<BookingCode>
B	GQWV	0-1	<WaiverMods>

Response (Output) Tags

Tags with asterisks (*) in the Ordering column can contain CAT 35 elements on the Galileo CRS.

<FareInfo>
	Ordering	KLR	Min/Max	XML Tag
		EROR		<ErrText>
		GF0A		<GeneralConstraints>
		GF0B		<BICConstraints>
		GF0C		<DayTmConstraints>
		GF0D		<ValidDates>
		GF0E		<FlightConstraints>
		GF0F		<InvalidDates>
		GF0G		<LastTravelConstraints>
		GFBC		<PrevBICSegMapping>
		GFBK		<NextBICSegMapping>
	*	GFC7		<CommNetGrossInfo>
		GFCI		<CityIndInfo>
		GFDR		<TkRestrictionInfo>
	*	GFEQ		<ExtendedQuoteInformation>
		GFFC		<FareConstruction>
		GFFO		<OverrideInfo>
		GFFP		<FictitiousStartPt>
		GFFS		<FilingStatus>
		GFFU		<FollowUpEntries>
		GFGQ		<GenQuoteDetails>
		GFIS		<ItinSeg>
		GFJT		<JrnyType>
		GFMM		<InfoMsg>
	*	GFN1		<SellFareConstruct>
	*	GFN2		<NetFareConstruct>
	*	GFN3		<TkAuditFareConstruct>
	*	GFN4		<TkPsgrFareConstruct>
		GFOM		<Msg>
		GFPF		<PsgrFacilityCharge>
		GFPI		<PsgrTypes>
		GFPU		<PlusUps>
	*	GFPX		<EnhancedPrivateFare>
		GFRF		<RulesDisplayBySegment>
		GFRH		<RespHeader>
		GFRI		<RulesInfo>
		GFRP		<RulesData>
		GFRR		<RvsnRules>
		GFJ5		<AdvRsvnTktRules>
		GFJ6		<MinStayRules>
		GFJ7		<MaxStayRules>
		GFJF		<SalesRestrictionRules>
		GFJG		<PenaltyRules>
	*	GFS2		<NetStructFareConstruct>
	*	GFS3		<TkAuditStructFareConstruct>
	*	GFS4		<TkPsgrStructFareConstruct>
	*	GFSF		<SellStructFareConstruct>
		GFSR		<SegRelatedInfo>
		GFSU		<Surcharge>
	*	GFT1		<TkPsgrFareConstructTaxInfo>
		GFTD		<Tariff>
		GFTS		<TaxBreakdown>
		GFXE		<BBQIntuitiveSystemsData>
		GFXG		<BBQGenQuoteInfo>
		GFXI		<FlightItemCrossRef>
		GFXJ		<BBQAvailJourneyItem>
		GFXO		<BestBuyQuoteOriginDest>
		GFXR		<BBQInfo>
		GFZ6		<SegMapping>
		GRFB		<FareBasisCodeSummary>
		GROM		<OutputMsg>

Related Samples

FareQuoteFlightSpecific_15_s1

FareQuoteFlightSpecific_15_s2

FareQuoteFlightSpecific_15_s3

FareQuoteFlightSpecific_15_s4

FareQuoteFlightSpecific_15_s5

FareQuoteFlightSpecific_15_s6

FareQuoteFlightSpecific_15_s7

FareQuoteFlightSpecific_15_s8

FareQuoteFlightSpecific_15_s9

FareQuoteFlightSpecific_15_s10

FareQuoteFlightSpecific_15_s11

FareQuoteFlightSpecific_15_s12