Task: Fare Quote (Best Buy) Dollar Saver

The Fare Quote (Best Buy) Dollar Saver finds the best price for the booked itinerary, taking into account all classes that are currently available on the flights that make up the itinerary and includes the rebooking details in the response.

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

Section 1: Short Answer

Transaction Name:

FareQuoteDollarSaver_24

Can this task be performed in a sessionless environment?

No. In a sessionless environment, the equivalent transaction is FareQuoteFlightSpecific_# (Flight Specific Best Buy).

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.

The <NewBICSegMapping> tag sends back the rebooking codes. In order for the new fare quote to be valid, the user must rebook.

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. More segments returns an error.

Section 2: Detailed Description

Request:

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

<PassengerType> (GQPA) and PTC Codes

To make a Dollar Saver request, <DollarSaverMods> must be sent with the <PassengerType> element, which contains passenger information.

The <PassengerType> element supports 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.

Other data in the request can include:

<GenQuoteInfo> (GQQM)

A <GenQuoteInfo> elementto include ticket dates is 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.
The <NetFaresOnly> field with a value of ‘A’ can be used to request that unmarked-up Net Fares be considered in the shop request, along with other requested fare types.
Note: The <ClassPreference> can be used to also request multiple cabins for the same Origin/Destination.
The <GenQuoteInfo> / <UseCurntTax> displays current or historical tax on a historical fare quote request (Galileo [1G] CRS only).

<SegSelection> (GQSS)

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.

<CtrlAirVMods> (GQCC)

The <CtrlAirVMods> provides the ability to override fare selection logic and specify carriers in cases where carriers have filed fares with interline partners and they are not the significant carrier on a fare component (they are not the owning or significant carrier on an itinerary so the fares do not quote).

Category 35 Fares

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.

<TaxExemptMods> (GQTE)

The <TaxExemptMods> can be used to provide either a specific tax code or ISO country code to exempt when processing doller saver requests.

Prerequisite tasks:

Before the fare quote (best buy) dollar saver request can be sent, a booked itinerary must exist.

Expected response:

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

The <BaggDispInfo> and subsequent <BaggDispFQandFQBB> display free baggage allowance and baggage charges at fare quote (specific itinerary pricing) and are added to e-ticket confirmations.

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
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).
AirChangeSegmentStatus_# – Change Segment via Rebook (optional).

Section 3: Tables

Request (Input) Tags

<DollarSaverMods>

Terminal Equivalents:

Apollo: $BB

Galileo: FQBB

Ordering	KLR	Min/Max	XML Tag
	GQFP	0-1	<GenFarePrefs>
	GQSS	0-8	<SegSelection> - (Private Fares only)
	GQNP or GQPO or GQPA	1-4	<PsgrMods> or <FqPicOnly> or <PassengerType>
	GQPC	0-1	<PlatingAirVMods>
	GQCC	0-1	<CtrlAirVMods>
	GQQM	0-1	<GenQuoteInfo>
	GQTE	0-1	<TaxExemptMods>
	GQSR	0-8	<SegMods>
	GQPO	0-4	<FqPicOnly>
	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		<NewBICSegMapping>
	GFBD		<BaggDispInfo>
	GFBF		<BaggDispFQandFQBB>
*	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		<RsvnRules>
	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

FareQuoteDollarSaver_24 _s1

FareQuoteDollarSaver_24 _s2

FareQuoteDollarSaver_24 _s3

FareQuoteDollarSaver_24 _s4

FareQuoteDollarSaver_24 _s5

FareQuoteDollarSaver_24 _s6

FareQuoteDollarSaver_24 _s7

FareQuoteDollarSaver_24 _s8

FareQuoteDollarSaver_24 _s9

FareQuoteDollarSaver_24 _s10

FareQuoteDollarSaver_24 _s11

FareQuoteDollarSaver_24 _s12