Task: Fare Display

The Display Booking Code task displays the booking code for a fare or multiple fares.

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

Section 1: Short Answer

Transaction Name:

FareQuoteMultiDisplay_16

Can this task be performed in a sessionless environment?

No.

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 is a follow-on request to retrieve booking class information for a fare on a previous Tariff Display (see Task Fare Display).

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

The <BICQuery> contains 2 fields for carrier. The first field is optional, but if populated, the carrier whose fare is being referenced should be in this first carrier field. Some fares allow carriers other than the fare carrier to participate in transport. For example,

Some British Airways fares between BOI and LON allow travel on Northwest Airlines from BOI to SEA.
The second carrier field in the <BICQuery> allows users to discover which booking class Northwest would require on their leg from BOI to SEA when the through British Airways fare is being used.

Section 2: Detailed Description

Request:

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

The <FareDisplayMods> request must contain at least a <QueryHeader> and a <BICQuery> tag.

In the <BICQuery> you can specify:

One line number, which will return the carrier's booking class information for the carrier/fare for that line.

You can also specify:

The carrier code of the fare.
One other carrier that returns booking class information for other carriers that may be used on a portion of an itinerary that that fare covers. For example, a BA fare DSM-PAR may allow carriage on AA from DSM-CHI and a <BICQuery> with carrier AA will show the booking class required for that portion of an itinerary (which may be DSM-AA-ORD-BA-LON-BA-CDG).

Prerequisite tasks:

You must first perform a Fare Display before displaying a booking code.

Expected response:

A successful response contains

A <FareInfo> tag, which always contains a <RespHeader> element.
An <OutputMsg> screen display tag, containing a formatted screen display of the header and the booking class information for the fare indicated in the request.

Error and warning responses:

Error and advice messages will be returned in the <InfoMsg>, or an <ErrText> tag displays if an error is encountered (e.g. no prior Fare Display was done, or the line number in the <BICQuery> does not match one of the line numbers in the previous display of fares).

In addition, the Error Message Returned indicator is set in the <RespHeader>.

Follow-on requests:

There are no follow-on requests.

Section 3: Tables

Request (Input) Tags

<FareDisplayMods>		Terminal Equivalents: Apollo: $LBn (n = line number) Galileo: FDC*n
	Ordering		KLR	Min-Max	XML Tag
			GFQH	1-1	<QueryHeader>
			GFLB	1-1	<BICQuery>

Response (Output) Tags

<FareInfo>
	Ordering	KLR	Min-Max	XML Tag
		GFRH	1-1	<RespHeader>
		GFMM	0-?	<InfoMsg>
		GROM	0-1	<OutputMsg>

Related Samples

FareQuoteMultiDisplay_16_s32