Task: Flight-Specific Fare Quote

The FareScheduleDisplay transaction allows the agent to make both an availability and a fare display request in one entry. The request applies to flight availability, plus normal and excursion fare options within the U.S., Canada, Puerto Rico and the U.S. Virgin Islands. The response includes the available flights and the best fare options for those flights, the fare basis code, and also indicates whether the fare is roundtrip. Apollo (1V) only.

Section 1: Short Answer

Transaction Name:

FareScheduleDisplay_6

Can this task be performed in a sessionless environment?

Yes

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

Apollo (1V) only.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

No

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

This entry applies only to normal and excursion fares within the U.S., Canada, Puerto Rico, and the U. S Virgin Islands.

Section 2: Detailed Description

Request:

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

<AirAvailMods>

The required data for the request includes the departure or arrival date, the board point and arrival point. To refine the information returned, a considerable amount of data may be included in the request. See the documentation for the latest AirAvailability XML Transaction.

<FareScheduleMods>

The <FareScheduleMods> record contains one primary element, the <FSDMods>. The <FSDMods> supports several functions:

1. Request one way only.
2. Indicate a return date and validate the minimum/maximum stay.
3. Request a specific booking class.
   

Prerequisite tasks:

None. This entry submits both an availability request and a fare display request at the same time.

Expected response:

<AirAvail>

For the <AirAvail> record, depending upon the information in the request, various responses may be returned.  Some are the responses described below.

• In the <AirAvail> response, a node in the <AvailFlt> element,<AvailSource>, contains the value of the source of the availability status. It is recommended that this value is saved and used to populate the <AirSegSell> element in the 1060 <AirSegSellMods> record to help determine the cause of sell failures.

Note: If the AAFI <AvailFlt> / <GenTrafRestriction> element is returned in the 1001 <AirAvail> response, see the Flight Item General Traffic Restriction Codes page.

<FareSchedule>

The <FareSchedule> displays the following information:

1. <ResponseHeader> displays the database update date/time and currency code
2. <FSDOptionalText> may display one of the following text messages:
   • TAXES/FEES NOT INCLUDED
   • U.S.PASSENGER FACILITY CHARGE MAY APPLY

   The following text messages may also display in relation to the <FSDFltItem> tag

   • FARE UNAVAILABLE
   • UNA TO PROCESS FQ
   • DBL CXNS UNAVL
   • INTL CITIES UNAVL
   • FARE UPDT IN PROG
   • FQ TEMP UNAVL
   • WAIT LIST
     
3. <FSDFltItem> displays related fare data.

Error and warning responses:

Errors display in the <ErrText> element. The following errors may display:

RESTRICTED ENTRY

NO AVAILABILITY FOR THIS REQUEST

INVALID PENALTY MODIFIER

SYSTEM ERROR

Follow-on requests:

Follow-on requests can be both detauled and summary rules for a selected fare/flight item. For example, FareQuoteMultiDisplay.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

FareScheduleDisplay_6_s1

FareScheduleDisplay_6_s2

FareScheduleDisplay_6_s3

FareScheduleDisplay_6_s4