Fare Quote Planner is a function which allows the user to request a fare quote based on input city pairs without having to pre-book an itinerary. It returns up to 10 fare quote responses, ranging from the first class fare to the cheapest economy class fare valid for the input. These responses for different classes and fares with different levels of restriction help the user plan the booking process to obtain the best fare for a passenger. The minimal entry is at least one city pair and one carrier, although multiple city pairs may be input, each with its own carrier, date and booking code.
See the Air Shop FAQ for questions regarding all air shopping transactions.
Transaction Name:
FareQuoteMultiDisplay_27
Can this task be performed in a sessionless environment?
Yes. This is an “initial” entry, i.e. one that initiates a host session.
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.
Since the input may only contain city pair(s) and carrier, and the quotes returned are for an un-booked itinerary, there are certain rule conditions that cannot be validated. For example, flight-specific rules and booking class validation may not be possible.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Fare Quote Planner is not currently designed to return private fares.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
The requirement for this function is a <FareDisplayMods> tag containing at least a <QueryHeader> tag, <PsgrTypes> tags for each city pair on the travel itinerary, and a <GenInfo> tag. Additionally, the <PsgrType> tag is used to provide passenger information, the <TaxExempt> tag is used to provide tax exempt information, and the <PenaltyMods> tag is used to provide penalty modifiers. Click here to view a list of Action Codes to enter in the <QueryHeader> tag.
Note: When entering data in the <PICReq> tag within the <PsgrTypes> tag, a user should use the ATPCo Passenger Type Codes. The proprietary Galileo by Travelport PIC codes were discontinued in early 2005.
Prerequisite tasks:
There are no prerequisite tasks for this function.
Expected response:
The response will be returned in a <FareInfo>, which always contains a <RespHeader> tag. The user may request the format of the response to be either <Tariff> tag or <Msg> tag format. The <Tariff> tag contains fare data for a single fare; a Fare Display request that results in 30 fares will return 30 <Tariff> tags. In addition, header information will be returned in <InfoMsg> tags. The <Msg> tag contains a formatted screen display of the headers and all the fares in the response.
Error and warning responses:
Error and advice messages will be returned in an <InfoMsg>. For example, if there are no fares for the city pair and modifiers request, an <InfoMsg> tag will be returned contain the message NO FARES FOUND FOR INPUT REQUEST. In addition, the Error Message Returned indicator is set on the the <RespHeader> tag.
Follow-on requests:
Follow on requests are possible from an initial (successful) Fare Display request. These are described in the following task documents:
|
<FareDisplayMods> |
Terminal Equivalents: Apollo: $DBRDOFF… Galileo: FDBRDOFF… |
|
||||
|
Ordering |
KLR |
Min-Max |
XML Tag |
||
|
|
GFQH |
1-1 |
<QueryHeader> |
||
|
|
GFFD |
1-1 |
<TravConstraints> |
||
|
|
GFPE |
0-1 |
<PenaltyMods> |
||
|
|
GFPI |
0-1 |
<PsgrTypes> |
||
|
|
GFPW |
0-3 |
<PFMods> |
||
|
<FareInfo> |
|
|
||||
|
Ordering |
KLR |
Min-Max |
XML Tag |
||
|
|
GFRH |
1-1 |
<RespHeader> |
||
|
|
GFMM |
0-? |
<InfoMsg> |
||
|
|
GFTD |
0-? |
<Tariff> (one per fare) |
||
|
|
GFSR |
0-? |
<SegRelatedInfo> |
||
|
|
GROM |
0-1 |
<OutputMsg> |
||