Task: Low Fare Shop Request

The Low Fare Shopping tool allows a user to find the best price options for a proposed journey, using origin/destination and date information, without requiring a booked itinerary. It allows a user to enter criteria to limit the shopping request, such as time period, specific carriers to include or exclude, private fare modifiers, and passenger types.

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

Section 1: Short Answer

Transaction Name:

FareQuoteSuperBB_25

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

Yes. Use FareQuoteFinder_# to fare shop if you have a booked itinerary and you want other itinerary and price options which fulfill the origin/destination and date parameters.

Can this task be performed in a sessionless environment?

Yes.

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

Yes.

Industry-specific knowledge required to understand this task in terms of the specific business process:

To receive web/private fares, the requestor must know the Pseudo City Code under which the fare was filed.
The requestor must know valid passenger types.
The requestor understand which flights (contained within the child elements of <RulesInfo>), relate to which price (contained within the child elements of <GenQuoteDetails>) and which booking codes pertain to which flight.
A special setting in the AAT (Agency Account Table) is needed for access to Galileo Optimal Shopping. See Errors and Warning responses in Section 2.

Special limits or distinct restrictions to the input data:

A maximum of 8 origin/destination pairs can be entered.
A maximum of 4 unique passenger types can be entered.
A maximum of 24 carriers in the carrier preferences can be entered. However, a maximum of 4 carriers is recommended, as this will maximize the availability scoop.

Section 2: Detailed Description

Request:

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

NOTE: In a <SuperBBMods> request, do not use the <FlexShopMods> element. This element must only be used via FareQuoteFlexShop transaction.

<AirAvailMods> / <GenAvail> (AAGA)

<AirAvailMods> must be sent with a general availability <GenAvail> child element; arrays of origin/destination pairs can be sent.

<SuperBBMods> / <PassengerType> (GQPA) and PTC Codes

The <SuperBBMods> element must also be sent with <PassengerType>.

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>. <PsgrMods> searches for a lower fare with the specified passenger type. If a lower fare does not exist, it sends back the lowest adult fare. <FqPicOnly> only searches for a lower fare for the specified passenger type. 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:

<AirAvailMods>

<AirVPrefs> (AAC1)

<AirVPrefs> provides the ability to include or exclude air vendors via the array <AirVAry>. <AirVAry> can contain up to 24 <AirVInfo> items. Including more than 24 <AirVInfo> items results in a CRS error.
<ShopModifiers> (AASM)

The following <ShopModifiers> can be added to the request:
- ROI – <RestrictOvernightItins>
- RMC – <RestrictMaxConnTime>
- RMA – <RestrictMultiAirpConn>
- NSP –<NonStopPref>

<SuperBBMods>

Point-to-Point:
All versions of FareQuoteSuperBB, both current and archived, support Point-to-Point faring. Currently, FareQuoteSuperBB does not permit a Point-to-Point availability instruction in the request. The response returns O/D and or Point-to-Point fares based on availability. See Point to Point, Partial Thru, and O&D Fares and Shopping.

<Optimize> (FLTR)
- If <Optimize> is sent on the request, then response data is organized and filtered according to data contained in <Optimize>.
- To minimize the amount of data returned, the requestor can specify only the reply elements that they to receive.
<GenQuoteInfo> (GQQM)
- 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.
- 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> (GQCB) 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).
<PFInfo> (GQOD)
- For an Airline Private Fares quote, the <PFInfo> element must be sent with the indicator for <ReqAirVPFs> set to ‘Y’ and <StartODRange> and <EndODRange> must be included. 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'.

<WaiverMods> (GQWV)
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.
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> (1425 Data Record) response (see the <FareInfo> Response table in Section 3).
Note: The <EnhancedPrivateFare> (GFPX) 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.

Availability and Classes of Service
There are three basic ways to request flights with respect to flight classes:

Class-Specific Request
Returns flights for a specific class only.
- Use the <Class> child element in <GenAvail> (AAGA)/<AirAvailMods> (Data Record 1000) to specify the class 'P' 'W' 'F’, ‘C, or ‘Y’.
  The response returns flights available only for that class. If that specific class is unavailable for one or more legs of the journey, the response is: NO AVAILABILITY FOR THIS REQUEST.
- Note: Using the 'S' option in <Class> yields results for all scheduled flights, regardless of the number of passengers in the party, and actual seat availability.
Downgradeable Class Preference
Returns flights for a preferred class, with downgrade functionality.
- <ODNum> set to '00' (downgrade will only be in effect for entire itinerary)
- Use the <ClassPref> child element in <ClassPreference> (GQCB)/<SuperBBMods> (Data Record 1400) to show the class preference 'P' 'W' 'F’, ‘C’, or ‘Y’.
- Leave <Class> (described above) blank. See the following examples:
  Downgrade in effect at itinerary level:
  
  <ClassPreference>
  <ODPairAry>
  <ODPair>
     <ODNum>00</ODNum>
     <ClassPref>C</ClassPref>
  </ODPair>
  </ODPairAry>
  </ClassPreference>
  
  Downgrade not in effect at Origin/Destination level
  
  <ClassPreference>
  <ODPairAry>
  <ODPair>
     <ODNum>01</ODNum>
     <ClassPref>C</ClassPref>
  </ODPair>
  
  <ODPair>
     <ODNum>02</ODNum>
     <ClassPref>C</ClassPref>
  </ODPair>
  </ODPairAry>
  </ClassPreference>
- Note: The 'S' option is not valid for <ClassPref>.
- The response returns all flights available for that class, including flights for which a class downgrade is possible for one or more legs of the journey when the preferred class is unavailable.
Return all flights for all classes
Return flights for all classes available.

Leave both elements, <Class> and <ClassPref> (described above) blank.

Note: Using the 'S' option in <Class> yields results for all scheduled flights, regardless of the number of passengers in the party, and actual seat availability.

IMPORTANT: There is also <Class> element in both <AirVSpecificAvail> (AACS) and <SpecificAvailMods> (AASA). It is not advised to use either of these elements for FareQuoteSuperBB requests. FareQuoteSuperBB is designed to work only with <GenAvail> (AAGA).

Prerequisite tasks:

To use the transaction, a user must be signed up for the Low Fare Shopping function and have the appropriate field in the AAT table set to Y (yes). The user may also be signed up for agency and/or airline private fares to receive private fares.

Expected response:

<FareInfo> (1425 Data Record)

The response sends back <FareInfo> with:

The summary fare information in <GenQuoteDetails> and <FlightItemCrossRef>.
Related flight information (referenced in the <FareInfo> summary) in <AirAvail>.
All other fare details in the remainder of the <FareInfo> element (see the Response Tables in Section 3).

<AirAvail> (1001 Data Record)

The <AirAvail> response contains multiple elements. Listed are several potential response types:

<AirBlackList> (AABL)
The <AirBlackList> displays blacklisted carrier response information. The European Union maintains a blacklist comprised of airlines it deems unsafe and which are therefore banned from servicing points to, from and within the European Community.
<AvailFlt> (AAFI)
- For customer’s who are activated for Point to Point availability, the the <AvailFlt> response indicates whether point-to-point availability was used for a particular flight. This indicator is in the <InsideAvailOption> node. A value of 'P' or 'J' indicates that the flights used point-to-point availability. This key data is needed when doing a follow-on direct sell. See Task Air Segment Sell via Direct Sell in the PNRBFManagement transaction for sell instructions.
- Note: If the <AvailFlt> / <GenTrafRestriction> element is returned in the 1001 <AirAvail> response, see the Flight Item General Traffic Restriction Codes page.

Error and warning responses:

All errors are sent back in the <SuperBB> or <FareInfo> response <ErrText> tag.

An indicator in the AAT (Agency Account Table) must be set for the request to process. If the AAT indicator is not set, an error response is returned:

FSHP-O (function is allowed as an online user)
FSHP-F (function is allowed as an offline user)
FSHP-N (disallow the shop function)

Additionally, the following error/warning messages can display:

Invalid Sequence (origin/destination in wrong order).
Invalid dates, city codes, carriers, etc.
Error to indicate you are not signed up to use FareQuoteSuperBB_#.
Multiple Fares Exist for Same Fare Amount.
Verify Modifier - Invalid <ShopModifiers> values.

<AirVPrefs>, an optional air availability request tag, provides the ability to include or exclude air vendors via the array <AirVAry>. <AirVAry> may contain up to 24 <AirVInfo> items. Including more than 24 <AirVInfo> items results in a host error.

Additional errors may display in the <ErrorCode> tag in the Response. See the main help system topic Troubleshooting > Errors > Transaction and Translation Error Descriptions. Within the <ErrorCode> element is the <Err> field. For example:

<ErrorCode>0001</ErrorCode>
    <ErrText>
        <Err>F 000672</Err>
        <KlrInErr>CGWS</KlrInErr>
        <InsertedTextAry/>
        <Text>NO AVAILABILITY FOR THIS REQUEST</Text>
    </ErrText>

The codes and associated errors in the <Err> field are:

Error Code	Error Description
641	INVALID DEPARTURE TIME
642	INVALID ARRIVAL TIME
643	INVALID DAY DIFFERENTIAL
644	INVALID CLASS PREFERENCE
645	INVALID SEGMENT RELATED SECTION
646	INVALID STOPOVER/CONNECTION INDICATOR
647	INVALID BREAK INDICATOR
648	CONFLICTING BREAK INDICATOR USAGE
649	INVALID CRS CODE
650	INVALID PUBLISHED FARES USE INDICATOR
651	INVALID VALIDATED CONTRACT USE INDICATOR
652	MISSING OR INVALID ITINERARY
653	AGENT NOT VALID IN PRIVATE FARES SECURITY
654	ERROR LOCATING GFI SECTION
655	ERROR READING KLR RECORDS
656	INVALID SEGMENT SELECT RANGE
657	INVALID TIC
658	TIC NOT VALID FOR THIS CARRIER
659	DUTY CODE NOT AUTHORIZED TO USE THIS TIC
660	TIC NOT AUTHORIZED FOR TRAVEL DATE
661	FIC REQUIRED FOR THIS TIC
662	INVALID ITINERARY DATE SEQUENCE
663	TODAYS DATE OUTSIDE TIC TICKETING DATES
664	INVALID PIC DISCOUNT AMOUNT OR PERCENT
665	PIC CANNOT BE COMBINED WITH A TIC
666	PIC IS NOW A TIC, USE TIC
668	TOO MANY PICS ENTERED'
669	COMPANION PIC CANNOT BE USED ALONE
670	NEW FARES LOADING
671	DUPLICATE NAME/SEGMENT COMBINATION
672	NO AVAILABILITY FOR THIS REQUEST
673	INVALID WITH MULTI-PRICING
674	MAX ATFQS/PRICING RECORDS EXIST
675	NO AGREEMENT EXISTS FOR PSEUDO CITY
676	$BBQ CURRENTLY UNAVAILABLE
677	INVALID FORMAT/DATA - NEED FIC
678	MODIFIER COMBINATION NOT ALLOWED
679	PICS NOT COMBINABLE
680	UNCONFIRMED MARRIAGE - USE SEGMENT SELECT
681	FLIGHT NOT FOUND - CHECK AVAILABILITY
682	PRIVATE FARES/PIC/TIC NOT COMBINABLE
683	CHECK ITIN/PSGR DATA - TIC NOT VALID ON MULTI-CARRIER ITIN
684	PFARE $D NOT AVAILABLE
685	PFARE $B NOT AVAILABLE
686	PFARE $BB NOT AVAILABLE
687	PFARE $BBQ NOT AVAILABLE
688	PFARE TICKETING NOT AVAILABLE
689	INVALID SEGMENT SPECIFICATION
690	NEED PSEUDO CITY
691	NEED PSEUDO CITY - USE
692	$BBQ W/PFARES TEMP UNAVL-REMOVE PRIVATE INDICATOR TO RE-REQUEST
693	PRIVATE FARES NOT APPLICABLE TO THIS PCC
694	PRIVATE FARES TEMPORARILY UNAVAILABLE - REMOVE PRIVATE FARE INDICATOR TO RE-REQUEST
695	NON PARTICIPANT CARRIER EXISTS- NO DISPLAYABLE FLIGHTS
696	FLIGHT AVAILABILITY CANNOT BE SEARCHED FOR THE REQUESTED TRAVEL DATE. PLEASE ENTER ANOTHER TRAVEL DATE WITHIN 331 DAYS OF TODAY
697	OUTPUT LENGTH HAS EXCEEDED SIZE LIMIT(GFSJ-HEAP SIZE EXCEEDED)'
698	CLASS OF SERVICE NOT AVAILABLE
699	CLASS OF SERVICE NOT OFFERED
700	MARKET NOT OPERATED BY REQUESTED CARRIER
701	BF MAY NEED DIVIDING-TRY SINGLE PASSENGER DESCRIPTION
702	UNABLE TO FARE QUOTE
703	NO VALIDATING AIRLINE FOUND
720	MARKET OPERATED - NO FLIGHTS ON REQUESTED DATE
2001	NON-PARTICIPANT CARRIER EXISTS
2002	DATE OUTSIDE SYSTEM RANGE - ENTER DATE WITH YEAR
2003	NO AVAILABILTY FOR THIS REQUEST

Follow-on requests:

The follow-on requests for this transaction are:

FareQuoteMultiDisplay_# – Rules Display, OB Fees Follow-On
PNRBFManagement_# – Air Segment Sell via Reference Sell.

For an OB Fees follow-on request with FareQuoteMultiDisplay, see the Task document "OB Fees Follow-on." The following table provides a mapping of the fields:

FareQuoteSuperBB	FareQuoteMultiDisplay
EquivCurrency	EquivCrncyCD
EquivAmt	EquivFareAmt
EquivAmt	EquivFareDecPos
TotCurrency	TotCrncyCD
TotAmt	TotFareAmt
TotDecPos	TotFareDecPos

Populate the <SegItemAry> in <OBFeesPsgrInfo> element in FareQuoteMultiDisplay with the segment data returned by FareQuoteSuperBB in the <ItinSeg>. This includes information like Start Airport, End Airport, Start Time, End Time, Air Vendor etc.

Use the FIC information returned in <SegRelatedInfo> element in the FareQuoteSuperBB transaction to set the <FBC> tag in <SegItemAry> in the FareQuoteMultiDisplay transaction

<OBFeesInfo> (GFOF KLR)

The information required in the element is independent of the FareQuoteSuperBB response. <ServiceCode> specified should be “OB”. Other information required includes AcctCode, PlatingAirV, PCC, CRS etc.

<OBFeesCCInfo> GFOC KLR)

The information in this element can be used to provide the option to add form of payment information on the request. It is not mandatory to provide this element to receive OBFeesResp.

Section 3: Tables

Request (Input) Tags

<AirAvailMods>

Terminal Equivalents:

Apollo: Not Applicable

Galileo: Not Applicable

Ordering	KLR	Min/Max	XML Tag
A	AAGA	1-1	<GenAvail>
B	AACP	0-4	<AirVPrefInd>
C	AAC1	0-4	<AirVPrefs>
D	AAMP	0-1	<ConxPrefInd>
E	AAM1	0-1	<ConxPref>
F	AABP	0-1	<BICPrefs>
G	AABF	0-1	<BICFilter>
H	AASM	0-1	<ShopModifiers>

<SuperBBMods>

Terminal Equivalents:

Apollo: Not Applicable

Galileo: Not Applicable

Ordering	KLR	Min/Max	XML Tag
A	GQNP or GQPO or GQPA	1-?	<PsgrMods> or <FqPicOnly> or <PassengerType>
A	GQOD	0-?	<PFInfo>
A	GQMF	0-?	<MaxFare>
A	GQQM	0-?	<GenQuoteInfo>
A	GQTE	0-?	<TaxExemptMods>
A	GQWV	0-1	<WaiverMods>
A	FLTR	0-?	<Optimize>
A	GQFX	0-1	<FlexShopMods>

Response (Output) Tags

<AirAvail>

Ordering	KLR	Min/Max	XML Tag
	AABL	0-1	<AirBlackList>
	AAT1	0-?	<AvailText>
	AAFT	0-?	<FltText>
	AAFH	0-1	<AvailSummary>
	AAFI	0-48	<AvailFlt>
	AABC	0-48	<FltAvailStatus>
	AAB1	0-48	<BICAvail>
	AATC	0-1	<TSAirVPrefs>
	AATS	0-1	<TSPrefs>
	AAMT	0-1	<MoreToken>

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>
	GFBC		<PrevBICSegMapping>
	GFBK		<NewBICSegMapping>
*	GFC7		<CommNetGrossInfo>
	GFCI		<CityIndInfo>
	GFDR		<TkRestrictionInfo>
*	GFEQ		<ExtendedQuoteInformation>
	GFFC		<FareConstruction>
	GFFO		<OverrideInfo>
	GFFS		<FilingStatus>
	GFGQ		<GenQuoteDetails>
	GFIS		<ItinSeg>
	GFJT		<JrnyType>
	GFMM		<InfoMsg>
*	GFN1		<SellFareConstruct>
*	GFN2		<NetFareConstruct>
*	GFN3		<TkAuditFareConstruct>
*	GFN4		<TkPsgrFareConstruct>
	GFPF		<PsgrFacilityCharge>
	GFPI		<PsgrTypes>
	GFPU		<PlusUps>
	GFPV		<PrivateFareInfo>
	GFPX		<EnhancedPrivateFare>
	GFRH		<RespHeader>
	GFRI		<RulesInfo>
	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>
	GFTS		<TaxBreakdown>
	GFXI		<FlightItemCrossRef>
	GFXR		<BBQInfo>
	GFZ6		<SegMapping>
	GRFB		<FareBasisCodeSummary>