Ticketing Point Mileage is a request for the flown mileages between two or more “ticketed points” on a journey and the maximum permitted mileage (MPM) from the first point specified to the last point specified. It is used for mileage based fares to determine if the customer traveling is within the maximum point mileage allowed for those city pairs.
Transaction Name:
FareQuoteMultiDisplay_8_3.
Can any other transaction perform this same task?
No
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.
The IATA mileage principles must be understood.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
Not applicable.
Request:
The requirement for this function is a <FareDisplayMods> request that contains a <QueryHeader> and a <MileageQuery> tag. Click here to view a list of Action Codes to enter in the <QueryHeader> tag.
Prerequisite tasks:
There are no prerequisite tasks for this function.
Expected response:
The response is returned in a <FareInfo> response, which always contains a <ResponseHeader> tag. The format of the response is always in the format of a <Msg> tag. The <Msg> tag contains a formatted screen display of the headers and the city pairs, the mileage between the city pairs (ticketed point mileage), the maximum permitted mileage, and any additional percentage that may be charged.
Error and warning responses:
Not available.
Follow-on requests:
None.
|
<FareDisplayMods> |
|
|
|
Ordering |
KLR |
Min-Max |
XML Tag |
|
|
GFQH |
1-1 |
<QueryHeader> |
|
|
GFMQ |
1-1 |
<MileageQuery> |
|
<FareInfo> |
|
|
|
Ordering |
KLR |
Min-Max |
XML Tag |
|
|
GFRH |
1-1 |
<RespHeader> |
|
|
GROM |
0-1 |
<OutputMsg> |