The OB Fee follow-on is a request to display the possible fees and taxes that may apply to the booking based on the itinerary, passengers and form of payment, etc.
See the Air Shop FAQ for questions regarding all air shopping transactions.
Transaction Name:
FareQuoteMultiDisplay_16
Can this task be performed in a sessionless environment?
Existing data from the itinerary must be returned on the request to obtain the correct fees and taxes.
Are the request and response identical on both the Apollo and Galileo systems?
No. This only applies to the Galileo system.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
Fees returned from the follow-on entry represent the possible fees that may apply. All forms of payment fees for a carrier that may apply is listed as reference but is not finalized until all forms of payment have been entered and the itinerary has been ticketed.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Fees and taxes will only display and apply for those carriers who have elected to participate in OB Fees. The carrier must be activated within the CRS in order for the fees and taxes to apply.
Request:
The requirement for this function is a <FareDisplayMods> (1424 Data Record) containing at least a <OBFeesInfo> and <OBFeesPsgrInfo> element.
The <OBFeesInfo> contains data applicable to all passengers.
Multiple <OBFeesPsgrInfo> can exist, as one <OBFeesPsgrInfo>is required for each passenger .
The <OBFeesCCInfo> provides the option to add form of payment information on the request.
Fees and Taxes specific to the form of payments are returned in the <OBFeesResp> only if only if the <OBFeesCCInfo>accompanies the <OBFeesInfo>and <OBFeesPsgrInfo>in the request.
Prerequisite tasks:
The OB Fee request is a follow-on to a fare quote or fare shop entry. OB Fees will only be returned for carriers that participate in OB Fees.
Expected response:
The response is the <FareInfo>, which always contains one <OBFeesResp> for each passenger. Within the <OBFeesResp>, repeating sections will contain multiple fees and taxes applying to the passenger.
Error and warning responses:
If no data is OB Fee data is returned, the count of fees and taxes in the <OBFeesResp> will be set to zero.
Follow-on requests:
N/A.
|
<FareDisplayMods> |
Terminal Equivalents: Apollo: N/A Galileo: FO, *FF# FO# FSOF#. |
|
||||
|
Ordering |
KLR |
Min-Max |
XML Tag |
||
|
|
GFOF |
1-1 |
<OBFeesInfo> |
||
|
|
GFOP |
1-? |
<OBFeesPsgrInfo> |
||
|
|
GFOC |
0-1 |
<OBFeesCCInfo> |
||
|
<FareInfo> |
|
|
||||
|
Ordering |
KLR |
Min-Max |
XML Tag |
||
|
|
GFOR |
0-? |
<OBFeesResp> |
||