Task: Class-Specific Quote

This task provides fare quote information for flight specific itineraries without consideration of availability.

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

Section 1: Short Answer

Transaction Name:

FareQuoteClassSpecific_10

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.

The FareQuoteClassSpecific_10 transaction is similar to FareQuoteFlightSpecific_# (Best Buy fare quote). The user must know the specific flight information that is being requested for the fare quote. Optional modifiers include the private fare pseudo cities and account codes, the date the quote was ticketed (historical), fare basis overrides, and the currency desired for the quote.

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

There is currently a limit of 90 days on past date fare quotes.

Section 2: Detailed Description

Request:

To make a class-specific request, <ClassSpecificMods> must be sent with the <SegInfo> element, which contains flight information, and the <PassengerType> element, 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 Refund and Exchange re-pricing, the <SplitDtPricingSeg> can be in the request to perform split date pricing. Exchanged segments are priced at current fares and un-exchanged segments are re-priced at the original fare using a supplied fare basis code.
  • The original supplied fare basis code should be provided in the <SplitDtPricingSeg> and not in the <SegSelection> as a FIC fare basis code.
  • The original ticket number must be supplied.
  • The original ticket date and reservation date must be supplied for the un-exchanged segments.
    
• 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 a Fare Quote Alternate (FQA) response in the itinerary, enter Y in the <FQAMods> (International fares - Galileo CRS only). An FQA response returns up to four alternate fare quotes for the itinerary, but limited to options in the same class of service in which the BF is booked. For example, if the booking is in the Y class, the response displays up to 4 alternate Y class quotes.
  • For Agency  or Airline Private Fares, to request FQA, the <SegSelection> as described above, must have Y in the request
  • The <EnhancedPrivateFare> response indicates whether the FQA fares are agency or airline private fares.
  • The FFN, as a follow-on to FQA, is a terminal entry (not available in XML).
    
• 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 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:

This task requires the user to have a valid flight itinerary, e.g., from availability, a booked itinerary, or past date ticket information.

The response includes <RespHeader>, which contains header details. The response also includes the itinerary summary <ItinSeg>, fare component information <RulesInfo>, general quote information <GenQuoteDetails>, segment specific information <SegRelatedInfo>, fare construction <FareConstruction>, passenger information <PsgrTypes>, and booking code information <PrevBICSegMapping>.

The following error messages can display:

• Invalid Sequence (flight sequence order)

• Invalid dates, city codes, carriers, etc.

• No valid fare for input criteria (unable to fare quote)

• Multiple Fares Exist for Same Fare Amount

The following warning messages can display:

• Plating Carrier Restriction

• Best fare for passenger type

• Not valid before/after dates

The follow-on requests are:

• FareQuoteMultiDisplay_# – Rules Display

• FareQuoteMultiDisplay_# – Routes Display

• PNRBFManagement_# – Air segment sell via direct sell – Only if the fare quote is not historical.

Related Samples

FareQuoteClassSpecific_10_s1.xml

FareQuoteClassSpecific_10_s2.xml

FareQuoteClassSpecific_10_s3.xml

FareQuoteClassSpecific_10_s4.xml

FareQuoteClassSpecific_10_s5.xml

FareQuoteClassSpecific_10_s6.xml

FareQuoteClassSpecific_10_s7.xml

FareQuoteClassSpecific_10_s8.xml