This task finds and displays dates on which a selected fare is applicable. It looks at rules for a specific fare and sends back fare rule information. These dates, although they adhere to the rules for the fare, may not have availability. The purpose of this transaction is to allow client applications to show customers dates on which a fare is and is not available.
See the Air Shop FAQ for questions regarding all air shopping transactions.
Transaction Name:
FareQuoteCalendarDates_13
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.
This transaction can be used on the Apollo or Galileo CRS, however, it is only specific to North American Fare Quotes.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Not applicable.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
The user must send a <FareDisplayMods> tag with the <QueryHeader> element tag and the <TariffMods> element tag (direct rules request). Click here to view a list of Action Codes to enter in the <QueryHeader> tag.
Prerequisite tasks:
Before sending the request, the user must search for fares.
Expected response:
The response is the <FareInfo> tag, with the <RespHeader> element tag (reply header), <GeneralConstraints> element tag (control section), and <BICConstraints> element tag (booking codes).
The <DayTmConstraints> element tag (day/time restriction), <ValidDates> element tag (valid date restrictions), <FlightConstraints> element tag (flight application data), <InvalidDates> element tag (invalid date restrictions), and <LastTravelConstraints> element tag (last travel date) may also be included in the return response, depending on the data sent in the request.
Error and warning responses:
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.
Follow-on requests:
Use the FareQuoteMultiDisplay_# transaction to view rules associated with the fare.
|
Step |
Input |
Transaction |
Output |
|
1 |
Route |
Tariff Display |
Price, FIC, AirV |
|
2 |
Route, Price, FIC, AirV |
Calendar Dates |
Date constraints. |
|
3 |
|
<Show Calendar> |
|
|
4 |
|
<User Picks Date> |
|
|
5 |
Route, FIC, AirV, Date |
Tariff-Driven Availability |
List of flights meeting all the rules. |
|
6 |
|
<Repeat steps 2 - 5 for return trip> |
|
|
<FareDisplayMods> |
Terminal Equivalents: |
Apollo |
Galileo |
|
Ordering |
KLR |
Min-Max |
XML Tag |
|
A |
GFQH |
1-1 |
<QueryHeader> |
|
A |
GFRL |
1-1 |
<TariffMods> |
|
B |
FLTR |
0-1 |
<Optimize> |
|
B |
GFFU |
0-1 |
<FollowUpEntries> |
|
B |
GFPI |
0-1 |
<PsgrTypes> |
|
B |
GFPW |
0-1 |
<PFMods> |
|
B |
GFPX |
0-1 |
<EnhancedPrivateFare> |
|
B |
GFPY |
0-1 |
<FareReferenceToken> |
|
B |
GFRK |
0-1 |
<RuleKeyInfo> |
|
B |
GINF |
0-1 |
<TruncResults> |
|
<FareInfo> |
|
|
Ordering |
KLR |
Min-Max |
XML Tag |
|
|
GFRH |
1-1 |
<RespHeader> |
|
|
GF0A |
1-1 |
<GeneralConstraints> |
|
|
GF0B |
1-1 |
<BICConstraints> |
|
|
GF0C |
0-1 |
<DayTmConstraints> |
|
|
GF0D |
0-1 |
<ValidDates> |
|
|
GF0E |
0-1 |
<FlightConstraints> |
|
|
GF0F |
0-1 |
<InvalidDates> |
|
|
GF0G |
0-1 |
<LastTravelConstraints> |
|
|
EROR |
0-1 |
<ErrText> |