V2User's Guide
|
V2 User's Guide |
This function has been designed to sell a recommendation. An optional selling algorithm can be activated to overcome situations where a simple sell would normally be rejected by the airline.
This operation provides the ability to search the Amadeus fare systems for lowest fare recommendations with regards to specified trip requirements.
The parameterised fare families option is supported meaning that fare families can be defined at input time.
The Slice and Dice process is also supported meaning that Slice and Dice output is returned for the Search function. The Slice and Dice process can be disabled by the No Slice and Dice option.
The Multi office id search process is also supported, meaning the end user has the ability to specify multiple Office ids in addition to the Originator Office id.
Additional information about the recommendation, such as Fare Notes, Flight Information and so forth, which may not be available with the Powered_LowestFareSearch Interface, can be obtained using alternative Powered Interfaces.
A Fare Family is a group of Fares sharing the same characteristics.
A Parameterized Fare Family is a set of specific parameters defining a fare family from the input.
A requested Segment is an Origin/Destination/Date segment of the travel:
Examples:
In the XML structure, a Requested Segment is represented by the node itinerary. In fact, the XML node itinerary includes:
An itinerary is the combination of all the Requested Segments in the order the passenger specified them.
In the XML structure, an itinerary is represented by a repetition or a sequence of up to 3 XML itinerary nodes.
Examples:
| User Guide | XML Structure |
|---|---|
| Itinerary: CDG-JFK One requested Segment: CDG-JFK |
There is One Occurrence of the XML itinerary node : CDG-JFK PoweredLowestFare_Search/itinerary/requestedSegmentRef : 1 PoweredLowestFare_Search/itinerary/departureLocalization : CDG PoweredLowestFare_Search/itinerary/arrivalLocalization : JFK |
| User Guide | XML Structure |
|---|---|
Itinerary: CDG-JFK- CDG Two requested Segments:
|
There are two Occurrences of the Itinerary node :
PoweredLowestFare_Search/itinerary/departureLocalization : CDG PoweredLowestFare_Search/itinerary/arrivalLocalization : JFK
PoweredLowestFare_Search/itinerary/ requestedSegmentRef : 2 PoweredLowestFare_Search/itinerary/ departureLocalization : JFK PoweredLowestFare_Search/itinerary/ arrivalLocalization : CDG |
A Proposed Segment is a combination of flights that matches a Requested segment.
A Journey is a combination of Proposed Segments covering the requested Itinerary.
A Recommendation is the combination of a price and its corresponding journey that is returned as a solution to the End User.
Requested Dates and Times are relative to the reference point of each Requested Segment
Not applicable.
Message size limit: Currently, this interface may return a maximum size of 64K for any EDIFACT message. Although not all messages returned will contain such a large amount of information, the user's platform must be able to accept this maximum size (and so its XML version) to avoid potential error conditions.
Operations Listed in the XML structure but not supported by the PoweredLowestFare:
The XML structure has been conceived to be flexible in order to support:
Consequently, it is possible that a node in the XML structure (tree) has no corresponding operation in this document. In this case, the XML node has to be ignored.
However, below are listed the XML nodes that correspond to operations not supported by PoweredLowestFare:
This function has been designed to sell a recommendation. An optional selling algorithm, described below, can be activated to overcome situations where a simple sell would normally be rejected by the airline.
Each airline is polled at its highest level of access with Amadeus, i.e. Amadeus Access if it is implemented, else Direct Access if it is implemented, else Standard Access.
It is important to note that itineraryDetails in this function corresponds to the notion of Proposed Segment in the interface or ODI (Origin and Destination Information Record). This should not be confused with the notion of itinerary that refers to the whole journey.
For example a return flight would consist of two ODIs (Origin and destination information record) one for the outbound part of the journey and the other for the inbound.
This optional algorithm is available in 2 flavours, that differ in the handling of the reply when the journey cannot be sold confirmed:
Flavour M1
FOR ODI 1 to n
STEP 1: Sell ODI with bundle long sell
STEP 2: Sell all segment of the ODI point to point
STEP 3: Sell all segment of the ODI NOT ALREADY SOLD point to point
Flavour M2:
FOR ODI 1 to n
STEP 1: Sell ODI with bundle longsell
STEP 2: Sell all segment of the ODI point to point
STEP 3: Sell all segment of the ODI NOT ALREADY SOLD point to point
There is currently only one operation supported by this function.
The details of the recommendation chosen must be provided by the user.
A maximum of 9 segments can be requested in one ODI and only NN status code i s supported in the query.
Not applicable.
A basic SellFromRecommendation is composed of the following:
Mandatory Elements
The / messageActionDetails / messageFunctionDetails / messageFunction must be set to 183. The first occurrence of / messageActionDetails / messageFunctionDetails / additionalMessageFunction must be set to M1 or M2 depending on the optimization algorithm flavour wanted. The / itineraryDetails are composed of:
Optional Element
In the originatorDetails the controlNumber can be given if the request is made on an existing PNR. The record locator can be provided, to allow a better tracking of the transaction.
For each query requested, either an error message or a valid response will be returned. The reply information will vary depending on the query information provided.
Basically the reply will copy the query structure, with the following extra piece of information:
If the booking is unsuccessful:
| OK | Sold |
| UNS | Unable to sell |
| WL | Wait listed |
| X | Cancelled after a successful sell |
| RQ | Sell was not even attempted |
Note: These codes allow the user to check the application of the sell optimization algorithm, if activated. The optimization algorithm is described in the overview.
If the booking is successful
This example describes the booking request of a return trip NYC-LAX, requiring the sell using the optimization algorithm on both itineraries (ODIs). The successful reply is shown as follows:
See "Error Messages" section.
The reply structure below shows that the return (ODI) part was not successfully booked:
The first leg was refused both in the bundled sell and in the local sell; as a consequence, the full itinerary had to be cancelled, that is referred in the second leg status 'X' (successfully sold, than cancelled).
An ERC 288 is added at message level to warn the user that at least one itinerary (ODI) failed.
This example shows that the first leg of the going part was refused both in the bundled sell and in the local sell:
As a consequence, the full itinerary (ODI) had to be cancelled, this is referred to in the second leg status 'X' (successfully sold, than cancelled). Also, the rest of the message processing is stopped, as can be seen in the status codes RQ of the return itinerary.
An ERC 288 is added at message level to warn the user that at least one itinerary (ODI) failed.
The reply structure below shows that the return (ODI) part was not successfully booked: The first leg was refused both in the bundled sell and in the local sell; the itinerary is returned partially sold.
An ERC 288 is added at message level to warn the user that at least one itinerary (ODI) failed.
This example shows that the first leg of the going part was refused both in the bundled sell and in the local sell: The sell of the return part was performed anyhow, successfully.
An ERC 288 is added at message level to warn the user that at least one itinerary (ODI) failed
This function is designed to facilitate a wide range of options, ensuring that customers can narrow downor broaden the fare search, in order to precisely match their request. The flexibility of this functionprovides the potential to receive up to 200 trip recommendations, enabling web-based customers toeasily navigate through many choices.
A basic Meta Pricer search is composed of the following mandatory elements:
A list of Airline Subscriber may optionally be included in Meta Pricer search to select the airlines to target. It is recommended to use this option when the subscribers are known for the itinerary to obtain the maximum number of recommendations.
Optional elements may be included in a request in order to provide the maximum flexibility to narrowor broaden the Meta Pricer search recommendations domain returned. Optional elements may applyto the common Meta Pricer search, flight search, or fare search. The following optional elements areoutlined below identifying the specific applicable search areas affected as well as whether the option isgenerally used to broaden or narrow the recommendations of a requested search.
| Possible Options | Applicable Search Area | Broaden | Narrow |
|---|---|---|---|
| Airline Subscribers List | Flights | X | X |
| Cabin | Common | X | |
| Connecting point | Flights | X | |
| Currency Conversion | Fares | ||
| Expanded Parameter | Fares | X | |
| Flight Category | Flights | X | |
| Passenger Type | Fares | X | X |
| Price to Beat | Fares | X | |
| Selling//Ticketing Cities | Fares | ||
| Time Window | Flights | X | |
| Times: Departure/Arrival | Flights | X | |
| Unifares | Fares | X |
The ability to request segments for travel with optional filter parameters is provided and the systemwill return recommendations of proposed segments making up a journey for the requested segments ofan itinerary with applicable price information. Thus, allowing the user to navigate through the list ofrecommendations to determine the best choice for travel arrangements.
The following operations are supported with this function:
Specifying only the mandatory elements allows for the search possibilities for a specified date,city pairand airline subscribers list.
A date of travel must be specified for a Meta Pricer search query.
At least one origin and one destination must be specified for a Meta Pricersearch query.
The number of seats required for the travelling passengers must bespecified for a Meta Pricer search. This number may not always be equal to the total number ofpassengers travelling. For instance, 3 Adults and 1 Infant - as an infant does not occupy a seat- requires only 3 seats for 4 travelling passengers.
Each travelling passenger must beassociated to a passenger type code for a Meta Pricer search
The user must specify the maximum number of recommendations tobe returned.
Specifying additional optional elements in the search request will broaden or narrow the recommendationsreturned. The more optional elements included in the search request, the more precise the search recommendations will be.
The user has the ability to specify up to 10 Airlines Subscribers using 2 aphanumeric character airline code.
The user has the ability to specify a desired cabin class for the requested itinerary.
The user has the ability to include and/or exclude up to 2 connecting points for therequested Low Fare Search. The user has also the ability to include up to 2 preferred connectingpoints.
The user has the ability to specify in which currency the fare recommendationsmust be converted and returned.
The user has the ability to specify Expanded Parameters forfare quote pricing. The only valid expanded parameter options applicable for this function areNAP (No Advance Purchase), NPE (No Penalty), NR (No Restriction) and RF (No Refundable).
The User has the ability to request Non-Stop, Direct or Connecting flights; or also acombination of these categories.
The User has the ability to specify a "Price to Beat", a total amount (including taxes)for all passengers that determines the most expensive recommendation that can be returned bythe system
The User has the ability to override the Selling and/or Ticketing Cities.
The User has the ability to specify one or both of the following:
he User has the ability to specify an applicable time window range, in terms of hours,to a specified time by departure or arrival option. Thus, allowing the Meta Pricer search to includeany flight recommendations that arrive or depart within the specified number of hours on eitherside of the specified time by departure or arrival.
By default the Meta Pricer searches are applicable only to public fares. However, the Usercan specify whether the Meta Pricer search applies on Unifares only, on all Public and Unifarefares or Corporate fares.
The User should request at least as many recommendations as airline subscribers. If the user specifiesless, the request will not be rejected. However, the number returned will be the number of airlinesubscribers requested.
It is currently not possible to request more than 200 recommendations in return. If the user specifiesmore than 200 recommendations in the optional area, the request will not be rejected. However, themaximum number returned will be no greater than 200.
At the present time, this function will not process the followingfare type qualifiers if specified under the Expanded Parameter input option:
| Code | Type |
|---|---|
| RD | Dynamic Discounted Fares |
| RZ | DDF Corporate Fares |
| RA | ATPCO Nego Fares - CAT35 |
| RB | ATPCO Nego Corporate Fares - CAT35 |
| RV | ATPCO Private Fares - CAT15 |
| RX | ATPCO Private Corporate Fares - CAT15 |
The ability to specify a search request with a longitude or latitude is currentlynot processed.
The cumulative and associative discounts are currently not processed.
The option to force a location to a city from a previouslyrequested segment search result is currently not processed. e.g., 2nd requested departure cityindicated to match the 1st requested arrival city of a proposed segment.
It is currently not possible to indicate that flight combinationswith overnights are not allowed for the Meta Pricer search. Therefore, the followingSequence Number is not supported;
| Code | Type |
|---|---|
| OV | Overnight not allowed |
Not applicable.
It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilization. Insome cases it is not a full explanation of every field that can be used for the operation, but rather a guideline to its use.
When building a query it is important to understand the following concepts for the Meta Pricer search queries:
A 'Requested Segment' is an Origin/Destination segment of the travel requestedin the query: Examples:
An 'Itinerary' is the combination of all the Requested Segments in the order the passengerspecified them.
The optional parameters may apply at the Requested Segment and/or Itinerarylevel.
The following table gives the rule for each option in terms of applicablelevels:
| Options | Applies to Segment | Applies to Itinerary |
|---|---|---|
| Airline subscribers |
|
X |
| Times: Departure/Arrival | X |
|
| Time Window | X |
|
| Flight Category | X | X |
| Connecting point | X |
|
| Cabin |
|
X |
| Number of recommendations |
|
X |
| Expanded Parameter |
|
X |
| Unifares |
|
X |
| Passenger Type |
|
X |
| Selling/Ticketing Cities |
|
X |
| Currency Conversion |
|
X |
| Price to Beat |
|
X |
| Withhold All Taxes/Surcharges |
|
X |
The input validation of each option is described in the corresponding sections.
If an option applies at both Requested Segment and Itinerary levels and if the request is not rejected,as specified in the description of the corresponding option paragraph, then the option specified at theRequested Segment level takes precedence over the Itinerary option.
| Request | Process |
|---|
| Itinerary | 1st Req. Seg. | 2nd Req. Seg. | 1st Req. Seg. | 2nd Req. Seg. |
|---|---|---|---|---|
| Flight Cat.: D | Flight Cat.: D | Flight Cat.: D | ||
| Flight Cat.: D | Flight Cat.: N | Flight Cat.: N | Flight Cat.: D | |
| Flight Cat.: D | Flight Cat.: N | Flight Cat.: N | Flight Cat.: N | Flight Cat.: N |
Option Cannot be Applied at Requested Segment Level If an option is only valid at the Itinerary levelbut the User has specified it at the Requested Segment level, the entire entry is rejected with thefollowing message:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL".
Option Cannot be Applied at Itinerary Level If an option is only valid at the Requested Segment levelbut the End-User has specified it at the Itinerary level, the entire entry is rejected with the followingmessage:
"OPTION CANNOT BE APPLIED AT ITINERARY LEVEL".
For each query, either an applicable error message or a valid response will be returned. Applicableerror message information is provided under each element section within this document. The replyinformation will vary depending on the query information provided.
When building a query it is important to understand the following concepts for the Meta Pricer searchqueries:
A "Recommendation" is the combination of a fare and its correspondingjourneys that are returned as a possible solution. The journeys are divided and categorized underapplicable fares making up the number of recommendations requested in the query.
A "Journey" is a combination of Proposed Segments covering the requestedItinerary
A "Proposed Segment" is a combination of flights that matches a RequestedSegment. This may result in 3 connecting flights being considered as a single "ProposedSegment".
Examples:
| Request Segment | Proposed Segment |
|---|---|
| CDG to JFK on 26Jun | AF flight 22 on 26jun |
| LON to BKK on 26Jun | LH flight4629 LHR to FRA 26Jun LH flight744 FRA to BKK 26Jun |
| NCE to SBN on 28Jul | AF flight7701 NCE to CDG 28Jul AF flight 050 CDG to ORD 28Jul UA flight5860 ORD to SBN 28Ju |
In the API PoweredLowestFare Interface, the ElectronicTicketing indicator fieldindicates whether a flight is eligible for electronic ticketing (value 'Y' for Yes) or not (value 'N'for NO).
| addProductDetail - Data element Value | Value |
|---|---|
| /electronicTicketing | Y |
| /electronicTicketing | N |
Electronic ticketing (e-ticketing) allows to send ticketing information directly to an airline so thatpassengers can check in at the airport and board flights without requiring printed tickets. When anelectronic ticket (e-ticket) is issued via Amadeus, the system sends the flight coupons as a messageto the airline. If the airline accepts the e-ticket request, the information is stored in the airline's ownsystem as an e-ticket record and displayed in the reply structure of the API.
Notes:
Specific error conditions exist for each mandatory and optional parameter in the query. However, asthese errors may be returned in several instances and it is not always apparent to which operationalparameter they apply, this section provides the following general errors that may be returned whenbuilding a query;
If a mandatory element is missing in the query structure, including any elements that are deemedmandatory via an association to another optional parameter, the entire entry is rejected locally by theAPI application.
It should be noted here that these messages are returned in the instances when no recommendationscan be found.
Whenever the Meta Pricer does notfind any recommendation matching the requested options, the query is rejected with the followingmessage:
"NO RECOMMENDATION FOUND FOR REQUESTED ITINERARY/OPTIONS"
In the current Meta Pricer process,when no flight is available (For example, all the flights matching the requested itinerary are setto 0 or closed), the transaction is rejected with the message:
"ERC - CODE SET 9321: VALUE 977 - NO AVAILABLE FLIGHT FOUND FOR THE REQUESTEDSEGMENT nn" (Where: nn represents the first impacted requested segment number).
These messages are returned when there is an error in the query message.
A reject message will be produced by the server; indicatingthat a query is too far into the future when it goes beyond the latest possible date. The correspondingreject message:
"LATEST FUTURE DATE POSSIBLE ddmmmyy"
If more than 10 airline subcribers codes are specified the entireentry is rejected and the following message is returned:
"TOO MANY REQUESTED SUBSCRIBERS ARE DEFINED IN THE REQUEST (MORE THAN10)"
The only valid expanded parameter options applicable to aMP request are NAP, NPE, NR and RF. If an unknown Expanded Parameter is specified in theentry, the entire request is rejected and the following error message is returned:
"INVALID VALUE (CODED) - PRICINGTICKINFO"
If an unknown Unifare option is specified in the entry, theentire request is rejected and the following error message is returned:
"INVALID VALUE CODED - PRICINGTICKINFO"
Up to 2 Requested Segments 'Meta Pricer' requests are allowed.If this check fails, the entire entry is rejected with the following message:
"TOO MANY REQUESTED SEGMENTS"
If an unknown Currency is specified in the Lowest Faresearch entry, the entire request is rejected and the following error message is returned:
"INVALID VALUE (CODED) - CONVERSION RATE"
If an un-authorized value is specified in a field flagged as 'coded' at the LowestFare Search Input message level, the entire entry is rejected and, if no other specific error messageexists, the following generic reject message is returned:
"INVALID VALUE (CODED) - XXX"
where XXX is the Segment smart name (e.g. paxReference).
Note: When a field is flagged as coded, refer to the corresponding code set to check the list of valuesauthorized
| Code | Type | In or Output |
|---|---|---|
| M | Mandatory | i |
Connection points must be segment specific. They may be combined with any other option, excludingthe Non-Stop Flight Category - in which, an error message is not returned, but the connection pointspecified is ignored. Connecting Points to Include may be combined with the Connection Points toexclude, providing the same connection points are not used for both categories.
The connection points are 3 character IATA City or Airport codes. When an Include Connecting Pointoption is specified, all itineraries returned must at least go via this Connecting Point. When two IncludeConnecting Points are requested, proposed itineraries must at least go via both these ConnectingPoints in the order specified in the entry. The Change of Gauge and direct flights whose stops are inthe requested point are not selected there.
Direct flights, Change of Gauge (COG) and Connections that have at least one stop at one of theexclude connect points are excluded. When two Excluded Connecting Points are specified, any itinerarygoing through one of those Connecting Points is excluded.
If an Exclude Connecting Point is specified at the same time as a Non-Stop Flight Category option, thesystem returns Non-Stop flights recommendations and ignores the Connecting Point requested.
If an airport code is specified as an Excluded connecting point, the alternate airports associated to thesame city are candidates to the selection.
If a city code is specified as an Excluded connecting point, all Airports associated to that City areexcluded.
Examples:
| Parameter | Information |
|---|---|
| Include Connecting Point: MAD | Itineraries via, at least, MAD |
| Include Connecting Point: PAR, JFK | Itineraries via, at least, PAR and JFK in that order |
| Exclude Connecting Point: FRA | Exclude any Direct, COG and Connections via FRA |
| Include Connecting Point: NYC Exclude Connecting Point: JFK |
Itineraries via, at least, any Airport of NYC except JFK |
| Exclude Connecting Point: LON, ROM | Exclude any Direct, COG, Connections via LON or ROM |
| Include Connecting Point: LON Exclude Connecting Point: SIN |
Itineraries via, at least, LON and ExcludeDirect, Connections and COG thatgo through SIN |
| Include Connecting Point: JFK Exclude Connecting Point: NYC |
Entry rejected with the appropriate message |
| Include Connecting Point: FRA Type of Flight: Non-Stop |
Entry rejected with the appropriate message |
| Exclude Connecting Point: FRA Type of Flight: Non-Stop |
All Non-Stop from DUS to BER. Inthat case the Exclude connecting pointis meaningless |
The example below illustrates a Meta Pricer search including an optional Connection Point elementspecified with the following information.
If the city or the airport code does not exist, the following error messageis returned:
"INVALID CONNECTING POINT"
The error "SAME CITY/AIRPORTCODE CANNOT BE INCLUDED AND EXCLUDED" is returned in the following situations:
If an Include Connecting Point isspecified at the same time as a Non-Stop Flight Category option, the entire request is rejectedand the following error message is returned:
"NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION"
If no itinerary can be found then the entire itinerary isrejected with the message:
"NO ITINERARY FOUND FOR REQUESTED SEGMENT n"
where n is the number of the first Requested Segment that failed.
If a Preferred Connecting Point is specified at the same time as a Non-Stop Flight Category option,the entire request is rejected and the following error message is returned:
"NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION"
If a Preferred Connecting Point option is specified at the same time as a preferred airline option, theentire query is rejected and the following error message is returned:
"PREFERRED AND INCLUDE/EXCLUDE AIRLINE CANNOT BE MIXED"
The currency conversion option may be combined with any other option.
It is mandatory that the ticketing price type be set to "CUC" to indicate a currency conversion request.It is mandatory for any query including the currency conversion option.
It is mandatory that a currency code be specified for the conversion. All price amounts for recommendationsare converted in the requested Currency. There is no default currency for conversion, it mustbe specified.
The example below illustrates a Meta Pricer search including an optional Currency Conversion elementspecified with the following information.
If an unknown Currency is specified, the entire request is rejected andthe following error message is returned:
"INVALID CONVERSION CURRENCY"
If the ticketing price type is set to currency conversion (CUC), yet acurrency code is not specified for the conversion, the entire query is rejected with the followingerror:
"CURRENCY MUST BE SPECIFIED"
If a currency code for conversion is specified, yet the ticketing pricetype has not be set for the currency conversion (CUC), the entire query is rejected with thefollowing error message:
"INVALID VALUE - CONVERSION RATE"
The fare type - expanded parameter option may be combined with any other option. With the exceptionthat the No Restriction parameter (NR) may not be combined with any other expanded parameter.
The following fare type - Expanded Parameters are supported:
Advance purchase: NAP Search for low fares having no advance purchase.
Penalty information for cancellation: NPE Search for low fares having no penalty.
No Restriction: NR Search for low fares having no restrictions.
Refundable fares: RF Search for low fares that may be refundable.
A maximum of 3 expanded parameter may be requested.
The example below illustrates a Meta Pricer search including an optional Expanded Parameter elementspecified with the following information.
The only valid expanded parameter options applicable are NAP,NPE, NR and RF. If an unknown Expanded Parameter is specified in the entry, the entire requestis rejected and the following error message is returned:
"INVALID VALUE - PRICING/TICK INFO"
It is not possible to combine the No Restriction (NR) Expanded Parameterwith any other Expanded Parameter. If this check fails, the entire request is rejected and thefollowing error message is returned:
"CONFLICTING OPTIONS USED"
The following Flight Categories are supported:
The rules defined in Availability apply regarding the definition of the Change of Gauge (COG) flights:
This information is usually obtained from the User Office Profile settings. However, due to currentinformation limitations, the change of gauge will be always considered as a connecting flight within thisfunction.
A maximum of 3 flight categories per requested segment may be specified and may be combined withany other option, excluding an include connection point with a Non-Stop flight category.
The example below illustrates a Meta Pricer search including an optional Flight Category elementspecified with the following information.
If an unknown Flight Category is specified in the entry, the entire request isrejected and the following error message is returned:
"INVALID FLIGHT CATEGORY"
If an Include Connecting Point is specified at the same time as a Non-StopFlight Category option, the entire request is rejected and the following error message is returned:
"NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION"
This example shows a query for an adult and an infant (ins) both taking a seat.
See "Error Messages" section.
This option may be combined with any other option. The Price to Beat amount can be composed ofup to 9 digits, and the value must be higher than zero. No decimal placement is allowed in the input.The currency of the Price to Beat is the requested Currency of Conversion if specified; otherwise, it isthe default selling currency that is determined as per usual pricing rules.
If no Price to Beat is specified, all prices will be considered valid as a qualifying recommendation.The example below illustrates a Meta Pricer search including the optional Price to Beat element specifiedwith the following information:
If the Price to Beat amount is composed of more than 9 digits, thevalue is not higher than zero, or a decimal placement is included in the input, the entire requestis rejected and the following error message is returned:
"INVALID PRICE TO BEAT VALUE"
The Price to Beat is used as a reference.No recommendation that is returned to the End-User may have an higher price. If no lower pricerecommendation is found, the following error message is returned:
"NO RECOMMENDATION FOUND WITH LOWER OR EQUAL PRICE"
The airline subscriber list is used to declare the list of airlines that will be questioned by the Meta Search. Meta Pricer will return online recommendations on those airlines only.
The user can specified up to 10 subscribers designated by their 2 alphanumeric characters code.
This option may be combined with any other options. The airline subscriber list applies to the entire trip and must be specified at the itinerary level of request.
Example: The example below illustrates a Meta Pricer search including a list of subscriber with the following information:
Requested airline subscribers: DL and BA
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| Number of seats for request | 3 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Applicable passenger type code for Adult | ADT |
| Passenger reference for 1st seat | 1 |
| Passenger reference for 2nd seat | 2 |
| Applicable passenger type code for Child | CH |
| Passenger reference for 3rd seat | 3 |
| Applicable passenger type code for Infant | INF |
| Passenger reference associated to first Adult seat | 1 |
| Infant indicator | 1 |
| 1st requested segment | 1 |
| Departure city of London | LON |
| Arrival city of New York | NYC |
| Trip Date (14 Aug 2006) | 140806 |
Airline Subscribers
If more than 10 airline subcribers codes are specified the entire entry is rejected and the following message is returned:
"TOO MANY REQUESTED SUBSCRIBERS ARE DEFINED IN THE REQUEST (MORE THAN 10)"
The example below illustrates a Meta Pricer search including an optional Cabin element specified withthe following information. Query Requirements:
If the cabin code does not exist, the following error message is returned:
"INVALID CABIN CODE"
If the cabin code is not requested at theitinerary level, the following error message is returned:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL"
A Date must be specified for each Requested Segment. Note that Times and Dates are specified inlocal time, at each location.
No past Date and/or past Time are allowed.
When 2 Requested Segments are specified, Dates and Times must be in chronological order. Timesand dates are specified in local time, at each location, but the chronological order check must considerthe TU times and dates.
2 requested segments may be requested with the same Date, as long as the User specifies both:
A maximum of 2 Requested Segments is allowed. These requested segments must each include anorigin and a destination City/Airport code.
Such as,
| One segment trip | NCE-LON |
| Round trip | NCE-LON-NCE |
| Itinerary including surface sector | NCE-LON/MAN-NCE |
The origin and destination codes must comply with the standard IATA City/Airport codes. If an IATAcode is not unique to a specific airport, but identifies at the same time, a City and an Airport (e.g.HOU) the three-letter code represents the City unless it is specifically identified as an airport (A) type.Whenever the request intends to restrict the search only to the Airport, this must be specified in thecase where the IATA code is not unique to an airport.
The following table illustrates further the possible scenarios of the origin/destination search process:
| Code Entered | Specified as City/Airport | Applicable point of departure/arrival searched |
|---|---|---|
| CHI | Not Specified | Chicago city, including the following airports:
|
| CHI | City Location | Chicago city, including the following airports:
|
| CHI | AirportLocation | Chicago city, including the following airports:
|
| ORD | Not specified | O'Hare (ORD) |
| HOU | Not Specified | Houston city, including the following airports:
|
| HOU | City location | Houston city, including the following airports:
|
| HOU | Airportlocation | Houston Hobby (HOU) airport only |
That means that:
Passenger Information
The number of passenger seats must be between 1 and 9. The recommendationsreturned are applicable to all passengers in the query. All passengers must betravelling together.
As the passenger fares vary for different types of passengers, apassenger type code for any Meta Pricer search is required. Passenger type codes dictate the MetaPricer search to provide recommendations with any qualifying passenger fare discounts applicable.All passenger type codes specified must be valid type codes stored within the Amadeus system.
A maximum of 6 passenger type codes may be requested.
When more than one Passenger Type is requested, the system must search for the cheapest fareswith the possibility to return non-homogeneous recommendations: different passengers bookedin different classes in order to offer a lowest fare.
In such a case, it becomes mandatory to split the traveling parties into separate records toaccommodate the lowest fare recommendation. This can be accomplished via the PoweredPNRinterface.
When a non-homogeneous recommendation is proposed, the following warning message is returned:
SPLIT PNR - DIFFERENT BOOKING CODES REQUIRED FOR LOWEST FARE"
Exception: Infant must travel in the same class as the accompanying "adult passengers (e.g.ADT, YTH, MIL, etc.).
Note: When specifying a PTC 'inf' without a seat, they must be associated to a passenger accompanyinga seat.
The user specifies the total number of recommendations to be returned. The total number of requestedrecommendations must be a valid number between the number of airline subcribers and 200. If a numberhigher than 200 is requested, the query will not be rejected but no more than 200 recommendationswill be returned.
The example below illustrates a Meta Pricer search including the mandatory function elements ofitinerary date, origin/destination, and number of passengers with associated types specified with thefollowing information;
MANDATORY ORIGIN/DESTINATION INFORMATION FOR 1 REQUESTEDSEGMENT
|
MANDATORY ITINERARY DATE FOR 1 REQUESTED SEGMENT
|
MANDATORY PASSENGER INFORMATION
|
OPTIONAL NUMBER OF RECOMMENDATIONS
|
Itinerary Date
If no date is found in the query structure, the entire entry is rejected with thefollowing message:
""DATE IS MANDATORY"
If a past Date and/or past Time are found in the query, the entireentry is rejected with the following message:
"PAST DATE/TIME NOT ALLOWED"
When 2 Requested Segments are specified, if the Datesand Times are not in chronological order, the entire entry is rejected with the following message:
"DATE/TIME MUST BE IN CHRONOLOGICAL ORDER"
The system verifies that there is no overlapping of the requestedtime ranges. This check also applies when a time range is requested and time ranges overlap,the time ranges being interpreted according to the time or time window option definition. If thischeck fails, the entire entry is rejected with the following message:
"OVERLAPPING DATE/TIME RANGES"
When two consecutive requested air segments have a close (or equal) travel date, add a 'Timeof Arrival' option on the chronologically first segment and a 'Time of Departure' on the nextsegment. This will avoid you experiencing numerous Meta Pricer "Near requested travel dates"query failures because of missing mandatory option in the PoweredLowestFare request. Note :See Certification Guidelines for more detail.
"Near requested travel dates" queries are defined as queries for which the difference betweenarrival time and departure times of the 2 consecutive requested segments (i.e. the latest possibledeparture time of the first requested segment and the earliest possible departure time of the nextrequested segment) is inferior to 12 hours.
Origin Destination
The system verifies that there is no overlapping betweenthe origin and the destination of any requested segment. The origin and destination beingrequested as airport or city, an overlap is detected when, for a segment, at least one of thealternate origins corresponds to one of the alternate destinations. If this check fails, the entireentry is rejected with the following message:
"OVERLAPPING ORIGIN/DESTINATION SEGMENT N"
where N is the number of the first segment where an overlap is detected
If an invalid city/airport code is specified in the request, the following rejectmessage will be returned:
"UNKNOWN CITY/AIRPORT"
Passenger Information
If the specified number of passengers with seats is 0, the entire entryis rejected with the following message:
"INVALID NUMBER OF PASSENGER"
If the specified number of passengers with seats exceeds 9,the entire entry is rejected with the following message:
"NUMBER OF PASSENGERS EXCEEDS NINE"
Requested Passenger Type Codes are validated against the AmadeusSystem codes. If the Passenger Type Code does not exist, the entire request is rejected and thefollowing error message is returned:
"INVALID PASSENGER TYPE CODE"
If more than 6 Passenger Types are specified, the entirerequest is rejected and the following error message is returned:
"EXCEEDS MAXIMUM FARE DISCOUNT CODES"
The number of Passenger Typesrequiring seats (i.e. all Passenger Type Codes with the exception of IN and INF) cannot exceedthe number of seats specified in the input. If this check fails, the entire request is rejected andthe following error message is returned:
"NUMBER OF NON-INFANT PTC CANNOT EXCEED NUMBER OF SEATS"
The number of Passengers not requiringseats (IN or INF code) cannot exceed the number of seats specified (as only 1 infant is allowedper passenger having a seat). If this check fails, the entire request is rejected and the followingerror message is returned:
"NUMBER OF INFANTS CANNOT EXCEED NUMBER OF SEATS"
Number of Recommendations
As this is an optional element no system error conditions currently exist for this option.
This cabin class applies to the entire requested itinerary. It is only possible to default to other classes ofservice in the case where it has been requested to do so and at least one flight of the proposed segmentcontains the cabin class specified.
Cabin class may not be specified at individual segment levels. The following cabins may be specified:
For a marketing carrier, the cabin corresponding to each booking code is determined by the bookingcode and the first letter based on the Cabin definition stored in Amadeus System (e.g. C, CN)
When a Cabin is specified, the lowest fares are proposed using the Classes that are identified as matchingthe requested Cabin. Non-Stops, Directs, Connecting and Change of Gauges for which the cabin is notdefined or not available are not selected.
The cabin option applies to the entire trip and must be specified at the itinerary level of the request.Requested cabin options at the segment level will result in an error.
Whenever the User specifies it, and whenever the requested cabin does not exist on some flights - eithernot defined or closed - the other cabins may be considered by the system. This process is only appliedwhen in at least one of the flights of a Proposed segment on the requested cabin exists. Whenever aProposed segment may not be booked in the requested cabin on any flight, this Proposed segment iseliminated, even if the end user allowed defaulting to other cabins.
Examples:
| Request | Process |
|---|---|
| Cabin Class F for return itinerary: PARIS/NEW YORK/CHICAGO | If cabin class (F) is not available on any flight betweenParis/NewYork/Chicago, the system proposed segment will not bereturned in the recommendations. If Cabin Class (F) is only available on the system proposed segmentonly from Paris/NewYork, default cabin classes will be processed forNewYork/Chicago segments. If Cabin Class (F) is only available on the system proposed segmentonly from NewYork/Chicago, default cabin classes will be processedfor Paris/NewYork. |
The example below illustrates a Meta Pricer search including an optional Cabin element specified withthe following information. Query Requirements:
If the cabin code does not exist, the following error message is returned:
"INVALID CABIN CODE"
If the cabin code is not requested at theitinerary level, the following error message is returned:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL"
The requested Selling and/or a Ticketing Cities are used to determine applicable fares and currency forthe recommendations. The selling and ticketing cities are applied from the requestor's system office ID city settings. If the selling or ticketing city override option is used, the cities specified will be usedinstead of the requestor Office-id City.
The city code specified must be a valid city code stored in the Amadeus System. Airport codes maynot be used, unless the airport and city code are the same.
| Valid city code for Paris | PAR |
| Invalid city code to use for Paris | CDG |
A maximum of one selling and one ticketing city may be specified applicable to the entire request.These options may be combined together and/or with any other option.
The example below illustrates a Meta Pricer search including the optional selling/ticketing cities overrideelement specified with the following information.
If the requested Selling or Ticketing city are not a valid city code inthe Amadeus System, the entire request is rejected and the following message is returned:
"INVALID TICKETING/SELLING CITY"
The Time option can be:
Search for flights that depart between the requested time and 11:59PM.
Search for flights that arrive between 00:00AM and the requested time.
Examples:
| Request | Process |
|---|---|
| Date: 10SEP01 Time of Arrival: 10:00PM => Arrives by 10:00PM on the 10SEP01 |
Select flights that arrive between00:00AM and 10:00PM on the 10SEP01 |
| Date: 15OCT01 Time of Departure: 10:00PM => Depart from 10:00PM on the15OCT01 |
Select flights that arrive between10:00PM and 11:59PM on the 15OCT01 |
Refer to the paragraph for the Departure/Arrival time handling when both options are combined.
The example below illustrates a Meta Pricer search including the Times by Arrival and Departureelements specified with the following information.
The error message "INVALID TIME OPTION" is returned in the following instances:
Valid time range values range between 1 and 12.
The Time Window applies either on the Time of Departure or the Time of Arrival to restrict the searchon the flights in the range of hours around (+ and -) the requested date and time.
Time window may overlap to the previous/next day to fulfill the request.
Note: The Time of Departure/Arrival option with a specified date is mandatory when using thisoption.
Examples:
| Request | Process |
|---|---|
| Date: 20AUG01 Time of Arrival: 10:00PM Time Window: 4 hours => Arrive around 10:00 PM on the20AUG01 |
Select flights that arrive between 20AUG01 6:00PM and 21AUG0102:00AM |
The example below illustrates a Meta Pricer search including the Times by Arrival and Departureelements specified with an optional time Window element with the following information.
The time window value varies from 1 to 12 hours. If this check fails,the entire entry is rejected with the following message:
"INVALID TIME WINDOW OPTION"
If no Time of Departure/Arrivalis specified, the entire request is rejected with the following error message:
"TIME OF DEPARTURE/ARRIVAL IS MANDATORY IF TIME WINDOW REQUESTED"
If no date is specified, the entire request is rejected with the following errormessage:
"DATE IS MANDATORY"
The paper and electronic ticket surcharge concept is driven from fare data filed by the airline.
Three new pricing options are available to allow the End User to link the fare priced and the type ofFare required.
'/PT' FOR PAPER TICKET
'/ET' FOR ELETRONIC TICKET
'/EP' FOR ELECTRONIC AND PAPER TICKET
Note: that Electronic Ticketing (ET) is not yet available in all markets or all carriers, for further detailscontact your local Amadeus Help Desk for more information, to ensure that the Office Profile hasbeen modified accordingly and the market where the airlines are situated can benefit from ElectronicTicketing (ET).
Examples:
| Request | Process |
|---|---|
| If no options are entered | System will propose both Electronic and Paper Ticket travel solutions |
| Request Electronic Ticket (ET)only | Electronic Ticket sent |
| Request PaperTicket (PT)only | Paper Ticket sent |
The example below illustrates a Meta Pricer search for Electronic Ticket solutions only.
See "Error Messages" section.
If the specific types of fares are not requested, only the public fares will be searched. This option maybe combined with any other option.
The following Unifares options are supported:
These fare type searches may be combined, with the exception of Unifares (RU) or Corporate Unifares(RW) with an Amadeus Nego (RN) or Amadeus Nego Corporate (RC) in the same entry.
An associated corporate number must be specified for Corporate Unifares or Amadeus Nego Corporaterequests.
Note: The search is restricted to one corporate id (Corporate identity) Value.
The example below illustrates a Meta Pricer search including the optional Unifares element with thefollowing information.
If a valid corporate type is not specified (RW or RC) or if the corporatenumber specified is not matching the corporate type requested (RW or RC), then the entire queryis rejected with the following error message
"INVALID VALUE - CORPORATE"
If a corporate type (RC or RW) has been specified, yet noassociated corporate number is included in the query, the entire query is rejected with the followingerror:
"CORPORATE NUMBER MUST BE SPECIFIED"
Unifares and Amadeus Nego/Corporate options are not combinable. If thischeck fails, the entire request is rejected and the following message is returned:
"CONFLICTING OPTIONS USED"
This function is designed to facilitate a wide range of options, ensuring that customers can narrow down or broaden the fare search, in order to precisely match their request. The flexibility of this function provides the potential to receive up to 200 trip recommendations, enabling web-based customers to easily navigate through many choices.
A basic low fare search is composed of the following mandatory elements:
In providing maximum flexibility to narrow or broaden the lowest fare search recommendations returned, optional elements may be included in a request. Optional elements may apply to the flight search or fare search.
The ability to request segments for travel with optional filter parameters is provided and the system will return recommendations of proposed segments making up a journey for the requested segments of an itinerary with applicable price information. Thus, allowing the user to navigate through the list of recommendations to determine the best choice for travel arrangements.
The following is a high level overview of this process;
What is an "Operation"?
In this document, an "operation" describes generally a possible query scenario. More precisely; this operation corresponds very often to a use of an option. However, in some cases, it describes a scenario that points out to a hint or a feature that needs further clarification.
The following operations are supported with the search function PoweredLowestFare.
Search with Only Mandatory Elements
Specifying only the mandatory elements allows for the search possibilities for a specified date and city pair.
Itinerary Date
A date of travel must be specified for a low fare search query.
Origin / Destination
At least one origin and one destination must be specified for a low fare search query.
Passenger InformationNumber of Passenger Seats
The number of seats required for the travelling passengers must be specified for a low fare search. This number may not always be equal to the total number of passengers travelling.
e.g. 3 Adults and 1 Infant - as an infant does not occupy a seat, this request requires only 3 seats for 4 travelling passengers.
Associated Passenger Type Codes for Travelling Passengers
Each travelling passenger must be associated to a passenger type code for a low fare search.
Number of Recommendations
The user must specify the maximum number of recommendations to be returned.
Multi office id search process
The end user can specify up to 19 Office ids in addition to the Originator Office id of the ORG segment, within the same country and with the same modifier type. The system will then find the cheapest travel solutions amongst all office ids requested in input (originator office id and additional office ids) without any preference.
Flight Convenience
The following criteria are applied to measure the convenience of each
journey:
- The proportion of the Ground Time with regards to the Total Flying Time
- The ratio between the Total Flying Time and the shortest possible flying time
- The Overnight connections proportion regarding the other journeys.
If a journey fails against these criteria, it is considered as a Low Convenience Journey.
In order to ensure a good overall journey convenience of the response,
the Flight Convenience ensures that the total number of returned Low
Convenience journeys does not exceed 5% of the requested number of
recommendations.
Specifying additional optional elements in the search request will narrow the recommendations returned.The more optional elements included in the search request, the more precise the search recommendations will be.
Flight Options
Airline (Include/Exclude)
The user has the ability to include and/or exclude up to 99 Airlines in the Low Fare Search using a 2 alphanumeric character airline code.
Flight Category
The User has the ability to request Non-Stop, Direct or Connecting flights; or also a combination of these categories.
Connecting Point
The user has the ability to include and/or exclude up to 2 connecting points for the requested Low Fare Search. The user has also the ability to include up to 2 preferred connecting points.
MultiCity
The User has the ability to specify up to 20 Cities or Airports as Origin and/or Destination of each Requested Segment.
Origin/Destination Area
The user has the ability to extend the low fare search up to 300 kilometers surrounding the airport or city specified for an origin or a destination. If an origin or destination area is specified, the low fare search process may consider any city whose flying distance to the specified City or Airportis lower than the specified radius in the query.
Ignore Availability
The End-User has the ability to ignore the real availability for flight selection: all returned booking codes are considered as available.
Disable biased reference
When this option is requested, the flight search request is performed in neutral mode independently of the office settings.
No slice and dice
The End-User has the ability to disable slice and dice process with an option in the query.
Exclude Low Cost Carriers
The End-Userhas the possibility via this option to exclude from the response Message TLA Recommendations.
Online
This option forces the process to return online travel solutions only, even if cheaper recommendations mixing carriers exist.
Date/Time Options
Interline option
The End-User has the ability to request only interline solutions in Master Pricer Travel Board i.e. recommendations built with flights marketed by different carriers.
Time of Departure/Arrival
Per requested segment, the User has the ability to specify one or both of the following;
Time Window
The User has the ability to specify an applicable time window range, in terms of hours, to a specified time by departure or arrival option.Thus, allowing the low fare search to include any flight recommendationsthat arrive or depart within the specified number of hours on either side of the specified time by departure or arrival.
Range of Dates
The User has the ability to request that the low fare search to include theday before or the day after the date specified for a trip segment.
Fare Options
Currency Conversion
The user has the ability to specify in which currency the fare recommendations must be converted and returned.
Selling/Ticketing Cities Override
The End User has the ability to override the Selling and/or Ticketing Cities.
Price to Beat
The End User has the ability to specify a "Price to Beat", a total amount (including taxes) for all passengers which determines the most expensive recommendation that can be returned by the system.
Split / No Split PNR
The End-User is able to request that non-homogeneous recommendations are returned or not. Non-homogeneous recommendations requiring to book passengers on several PNRs.
Process Paper ticket / Electronic ticket
This option offers to the end user the capability to process:Paper Ticket Only or Electronic ticket only.
Unifares
By default the low fare searches are applicable only to public fares. However, the User can specify whether the low fare search applies on Unifares only, on all Public and Unifare fares or Corporate fares.
Expanded Parameters
The End-User can specify Expanded Parameters that are used to target only some fares (refundable, without penalty...). Only valid expanded parameter options applicable : NAP, NPE, NR and RF.
My Search - Fare Families
By default any applicable fare can be returned, using My Search option the end-user can specify which fares he is interested in by using criteria like Fare Basis, Prime booking Code.
Cabin Options
The user has the ability to specify a desired cabin class for the requested itinerary. There is three different flavors of process: Mandatory, Recommended and Major Cabin that are described in the corresponding operations.Fee??‚
OptionsService Fees: Pricing Scheme reference
The User has the ability to specify a Pricing Scheme Reference for the calculation of a service fee by passenger of a recommendation.
Option ancillary services
The user can requestancillary services.
In the pushed mode, all or pre-selected subset of applicable ancillary services and associated prices will be returned in each recommendation but not considered in the search of the lowest fares. The pushed mode is set as the default mode.
In the polled mode, all or pre-selected subset of ancillary services and associated prices are returned in each shopping recommendations and considered in the search of the lowest fares.
Form of Payment
The form of payment option may be combined with any other option. A maximum of 3 forms of payment may be keyed in.
Sorting with/without Fees
This optional input allows sorting recommendations considering or not fees applying to fares in the ranking. Possible values for OB fees are SORT: NOFEE or SORT: FEE.
Exempt all airline ticketing fees
Airline ticketing fees can be all exempted with this option.Add/Exempt airline ticketing fees by sub-codeAirline ticketing fees (OB fees) sub-codes can be specified in order to add or exempt particular fees.
Identify YQ,YR separately from other taxes
The purpose of this option is to return separately in the output the total amount of YQ/YR taxes per recommendation and per passenger type.
Multi Office IDs
The End User has the ability to specify up to 19 Office ids.
Price only PTC
The process returns strictly recommendations with the requested passenger type, no defaulting is done.
Distribution options
Airline Distribution: ADI
When this option is requested,the total number of Recommendations are distributed over 2 sets as following:
Airline Distribution Container: ADC
When this option is requested,the total number of Recommendations are distributed over 2 sets as following:
Output options
Empty Cells Clarification
When this option is requested, a fictitious recommendation is returned with the corresponding reason for segments and/or dates where no recommendation can be returned.
Rank in journey Server
The End User has the ability to request the display of the rank of the Flight Solution.
Multiticket option
The Multi Ticket option allows returning at the same time:
- Recommendations that require one single pricing transaction to be booked
-Recommendations that require individual pricing transactions per Proposed Segment to be booked (the search is done on the same office id for the whole itinerary).
Indian Taxes
This option details in the response message for each recommendation and for each type of passengers.
Ticketing Date
In order to avoid quoting a fare to a passenger that they are then
unable to ticket at a later date, the end-user has the option of
specifying the intended ticketing date in the input.
This option ensures that the user will only receive recommendations
that, if priced on the same day as the query is received, are valid for
ticketing on the future ticketing date specified in the input.
It is currently not possible to request more than 200 recommendations in return.If the user specifies more than 200 recommendations in the optional area,the request will not be rejected. However, the maximum number returned willbe no greater than 200. If not indicated the number of recommendation is 50.
It is currently not possible to request more than 1 day forward and/or1 day backward for the searchable date range.
It is not possible to request more than 3 requested segments.
It is not possible to request more than 9 passengers.
It is not possible to request more than 6 fare families.
It is not possible to specify more than 19 Office Ids.
Longitude/Latitude
The ability to specify a search request with a longitude or latitude is currently not processed.
Origin/Destination - Forced Location
The option to force a location to a city from a previously requested segment search result is currently not processed. e.g., 2nd requested departure city indicated to match the 1st requested arrival city of a proposed segment.
Sequence Number - Overnight Not Allowed
It is currently not possible to indicate that flight combinations with over nights are not allowed for the low fare search.
Therefore, the code OV is not supported;
Not applicable.
Depending on the flavor of the API that is used, each query will follow a given structure. The queries for the function operations are clearly explained with data element examples in a generic table view that can be adapted to the specific flavor of the API in use.
It is important to note that the examples in each chapter are only illustrations and are meant to provide the basis for a better understanding on which fields are mandatory for basic operation utilisation. In some cases it is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.
When building a query it is important to understand the following concepts for the low fare search queries:
What is a Parameterized Fare Family?
A Parameterized Fare Family is a set of specific parameters directly specified through the request. Up to 6 Parameterized Fare Families can be defined in the MP query. The parameterized Fare Family can be combined with any other option as long as the request remains functionally coherent.
What is a Requested Segment?
A 'Requested Segment' is an Origin/Destination/Date segment of the travel requested in the query:Examples:
What is an Itinerary?
An 'Itinerary' is the combination of all the Requested Segments in the order the passenger specified them.
Optional Parameters
The optional parameters may apply at the Requested Segment and/or Itinerary level.
Applicable Option Levels
The following table gives the rule for each option in terms of applicable levels:
|
|
Applies to |
|---|
| Options | Segment | Itinerary |
|---|---|---|
| Flight Options | ||
| Number of recommendations |
|
X |
| Airline | X | X |
| Cabin |
|
X |
| Time Window | X |
|
| Times: Departure/Arrival | X |
|
| Connecting point | X |
|
| Expanded Parameter |
|
X |
| Flight Category | X | X |
| Selling/Ticketing Cities |
|
X |
| Radius (origin/Destination areas) | X |
|
| Multi-city | X |
|
| No Slice and Dice | X | |
| Disabled Biased Reference | X | |
| Exclude Low Cost Carriers | ||
| Ignore Availability | X | |
| Airline Distribution: ADI | X | |
| Airline Distribution Container: ADC | X | |
| Online | X | X |
| Fare Options | ||
| Passenger Type |
|
X |
| Price to Beat |
|
X |
| Unifares |
|
X |
| Parameterized Fare Family |
|
X |
| Split/No Split PNR |
|
X |
| Currency Conversion |
|
X |
| Process Paper ticket/Electronic Ticket |
|
X |
| Ticket-ability pre-check |
|
X |
| Expanded Parameters |
|
X |
| Withhold All Taxes/Surcharges |
|
X |
| Service Fees : Pricing Scheme reference |
|
X |
| Multi-tickets |
|
X |
| Form of payment |
|
X |
| Adding/exempting specific airline ticketing fees |
|
X |
| Exempt all airline ticketing fees |
|
X |
| Sorting with/Without Fees |
|
X |
| Multi Office IDs | ||
| Identify YQ/YR tax amounts in Output | X | |
| Price only PTC | X | |
| Date Options | ||
| Range of Dates | X |
|
| Output Options | ||
| Empty Cells Clarification | X | |
| Rank in Journey Server | X | |
The input validation of each option is described in the corresponding sections.
Option requested at both requested segment level and itinerary Level?
If an option applies at both Requested Segment and Itinerary levels and if the request is not rejected, as specified in the description of the corresponding option paragraph, then the option specified at the Requested Segment level takes precedence over the Itinerary option.
Examples:
| Request | Process |
|---|
| 1st Requested Segment | 2nd Requested Segment | Itinerary | 1st Requested Segment | 2nd Requested Segment |
|---|---|---|---|---|
| Include Airlines: AA, CO |
|
Include Airlines: AA, DL | Include Airlines: AA, CO | Include Airlines: AA, DL |
| Include Airlines: FL, CO, YY |
|
Exclude Airlines: AA, DL | Include Airlines: FL, CO eventually combined with any airline but AA, DL. | Exclude Airlines: AA, DL |
Possible Option Level Errors
Option Cannot be Applied at Requested Segment Level. If an option is only valid at the Itinerary level but the User has specified it at the Requested Segment level, the entire entry is rejected with the following message:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL".
Option Cannot be Applied at Itinerary Level
If an option is only valid at the Requested Segment level but the End-User has specified it at the Itinerary level, the entire entry is rejected with the following message:
"OPTION CANNOT BE APPLIED AT ITINERARY LEVEL".
Query Structures
The query samples provided in this document are in a table format to easily identify the different levels of applicable information required in the function.
The repetitions of nodes in the samples provided are identified with brackets and numbers [n].
Each element of the function is explained with a query sample in the applicable sections of this document. In some cases, the query sample contains only the information applicable to the discussed element. The responsibility lies with the API developer to read the element sections for rules and combinability issues to build the applicable messages desired.
As a guideline for the possibility of a more complex message structure, the sample query structure below is given identifying a low fare search requesting the following information:
| Item # | Requested Information |
|---|---|
| 0 - 1 | Low Fare Search for 3 passenger |
| 2 - 3 | Requesting a maximum of 200 recommendations returned |
| 4 - 8 | Passenger Types of 2 Adults and 1 Child |
| 9 - 10 | DL airlines are to be excluded from any recommendations |
| 11 - 16 |
1st requested segment:
|
| 17 - 22 |
2nd requested segment:
|
| Item | PoweredLowestFare_SearchQuery - Data element | Value |
|---|---|---|
| 0 | /Segment/unitNumberDetail[1] / numberOfUnits | 3 |
| 1 | /Segment/unitNumberDetail[1] /typeOfUnit | PX |
| 2 | /Segment/unitNumberDetail[2] / numberOfUnits | 200 |
| 3 | /Segment/unitNumberDetail[2] /typeOfUnit | RC |
| 4 | /paxReference [1]/ ptc | ADT |
| 5 | /paxReference [1]/traveller[1] /ref | 1 |
| 6 | /paxReference [1]/traveller[2] /ref | 2 |
| 7a | /paxReference [2]/ ptc[1] | CH |
| 7b | /paxReference [2]/ ptc[2] | MIL |
| 8 | /paxReference [2]/traveller /ref | 3 |
| 9 | /travelFlightInfo/companyIdentity[2] /carrierQualifier | X |
| 10 | /travelFlightInfo/companyIdentity[2] /carrierId | DL |
| 11 | /itinerary[3]/requestedSegmentRef /segmentRef | 1 |
| 12 | /itinerary[3]/departureLocalization/departurePoint / locationId | NCE |
| 13 | /itinerary[3]/arrivalLocalization/arrivalPointDetails / locationId | HOU |
| 14 | /itinerary[3]/timeDetails/firstDateTimeDetail /timeQualifier | TA |
| 15 | /itinerary[3]/timeDetails/firstDateTimeDetail /date | 200204 |
| 16 | /itinerary[3]/timeDetails/firstDateTimeDetail /time | 1700 |
| 17 | /itinerary[4]/requestedSegmentRef /segmentRef | 2 |
| 18 | /itinerary[4]/departureLocalization/departurePoint / locationId | HOU |
| 19 | /itinerary[4]/arrivalLocalization/arrivalPointDetails / locationId | NCE |
| 20 | /itinerary[4]/timeDetails/firstDateTimeDetail /date | 300204 |
| 21 | /itinerary[4]/flightInfo/flightDetail / flightType [1] | N |
| 22 | /itinerary[4]/flightInfo/flightDetail / flightType [2] | D |
Referring to the applicable element sections of this document will provide any specific element information required.
For each query requested, either an applicable error message or a valid response will be returned. Applicable error message information is provided under each element section within this document.
In case of a valid response, two cases occur. Either the reply message is troncated if it is too big (MSG:128k appears in the STX segement), or not.
In case of troncation, the STX segment shows the maximum size of the message:
STX+FQX*USR:INV*MSG:128k
In case ancillary services are requested, and the reply message is too big and troncated, the ancillary service details part appears at the end of the message even if the recommendations dont show any ancillary services.
The reply information will vary depending on the query information provided.
When building a query it is important to understand the following concepts for the low fare search queries:
Fare Family
A Fare Family is a group of Fares sharing the same characteristics. Fare Family details can be defined as a combination of the following elements:
A combinability tag and a ranking are also provided.
? What is a Recommendation
A "Recommendation" is the combination of a fare and its corresponding journeys that are returned as a possible solution.
The journeys are divided and categorized under applicable fares making up the number of recommendations requested in the query.
What is a Journey
A "Journey" is a combination of Proposed Segments covering the requested Itinerary
What is a Proposed Segment
A "Proposed Segment" is a combination of flights that matches a Requested Segment. This may result in 3 connecting flights being considered as a single "Proposed segment".
Examples:
| Request Segment | Proposed Segment |
|---|---|
| CDG to JFK on 26Jun | AF flight 22 on 26jun |
| LON to BKK on 26Jun | LH flight4629 LHR to FRA 26Jun LH flight744 FRA to BKK 26Jun |
| NCE to SBN on 28Jul | AF flight7701 NCE to CDG 28Jul AF flight 050 CDG to ORD 28Jul UA flight5860 ORD to SBN 28Jul |
Electronic Ticketing
In the API PoweredLowestFare Interface, the ElectronicTicketing indicator field indicates whether a flight is eligible for electronic ticketing (value 'Y' for Yes) or not (value 'N' for NO).
| addProductDetail - Data element Value | Value |
|---|---|
| /electronicTicketing | Y |
| /electronicTicketing | Y |
Electronic ticketing (e-ticketing) allows to send ticketing information directly to an airline so that passengers can check in at the airport and board flights without requiring printed tickets. When an electronic ticket (e-ticket) is issued via Amadeus, the system sends the flight coupons as a message to the airline. If the airline accepts the e-ticket request, the information is stored in the airline's own system as an e-ticket record and displayed in the reply structure of the API.
Notes:
The Slice and Dice process aim is to consider all availabilities that may be used in order to optimise the price of an itinerary, and to apply the same class combination restrictions as the one applied by the carriers.
When Slice and Dice process is applied, the availability context is returned in the Master Pricer response (from VPERSP 7.1 version). This context will have to be used to book the solution returned by the engine.
Let us consider an example of 3-segment eligible connection, between the 4 cities A, B, C and D, where the 3 flights are AB, BC, and CD. Without Slice and Dice process, only O&D availability AD is checked. With the Slice and Dice process, local availabilities AB, BC, CD and Sub O&D availabilities AC and BD (respectively named Sub O&D 1 and Sub O&D 2) will also have to be checked. This means that in case an O&D context (default processing, no extra information about availability context), all flights of the connection have to be sold at the same time. In case of Sub O&D, the two corresponding flights must be sold together and in case of local context, the corresponding flight has to be sold alone.
In the segment FlightRef of the response message structure, an additional refQualifier with the value "A" (for Recommendation Availability context) is added with its refNumber
| PoweredLowestFare_SearchReply - Data element | example | Description |
|---|---|---|
| segmentFlightRef / referencingDetail / refQualifier | S | Reference of Proposed Segment |
| segmentFlightRef / referencingDetail / refNumber | 3 | Index to Proposed Segment |
| segmentFlightRef / referencingDetail / refQualifier | A | Reference to availability |
| segmentFlightRef / referencingDetail / refNumber | 1 | Index to availability context |
The corresponding description for each reference of a recommendation availability context is given in the group specificRecDetails. This group contains the following sub-groups:
Note: Possible values for the availabilityCnxType are:
| PoweredLowestFare_SearchReply - Data element | example | Description |
|---|---|---|
| specificRecDetails / specificRecItem /referenceType | A | Availability context |
| specificRecDetails/specificRecItem/refNumber | 1 | Availability context index |
| specificProductDetails/productReferences / paxFareNum | 1 | Reference to passenger |
| specificProductDetails/ fareContextDetails/ requestedSegmentInfo/ segRef | 1 | Index of Proposed Segment |
| fareContextDetails/ cnxContextDetails[1]/ fareCnxInfo/ contextDetails/ availabilityCnxType | LA | availability context "local" for first flight of Proposed Segment |
| fareContextDetails/ cnxContextDetails[2]/ fareCnxInfo/ contextDetails/ availabilityCnxType | LA | Availability context "local" for second flight of Proposed Segment |
Reply Structure
As it is not possible to cover every reply structure possible, only a sample of a possible reply structure is provided as a guideline of the typical reply message expected.
Each reply will contain the following:
My Search Reply: Parameterised Fare Families
This is only applicable for the Search Travel Board function.
Only in case the My Search option is used, the following information needs to be returned in the reply:
This table presents the XML node familyInformation structure associated to each Fare Family info that is returned in the reply:
| PoweredLowestFare_SearchReply - Data element | example | Description |
|---|---|---|
| / familyInformation /refNumber | 1 | Reference of the fare family |
| / familyInformation / fareFamilyname | FFAMILY1 | Name of the fare family |
| / familyInformation /hierarchy | 100 | 1 |
| PoweredLowestFare_SearchReply - Data element | example | Description |
|---|---|---|
| / fareDetails / groupOfFares / fareFamiliesRef /referencingDetail/ refQualifier | F | Reference of the fare family |
| / fareDetails / groupOfFares / fareFamiliesRef /referencingDetail/ refQualifier/ refNumber | 1 | Reference to the Fare Family referenced 1 in the family information node. |
| PoweredLowestFare_SearchReply - Data element | example | Description |
|---|---|---|
| /recommendation[2] /paxFareProduct[4] /fareDetails [2] /groupOfFares/ productInformation/ breakPoint | Y | The fare breakpoint : Y or N |
OB fees Output:
In the output message, information is also provided about the fact that OB fees exist for the validating carrier and the office (OID), the validating carrier used for pricing and the amount of OB fees.
| PoweredLowestFare_SearchReply - Data element | example | Description |
|---|---|---|
| priceTicketing/ priceType [1]/ | OBV | Validating carrier accepts OB fees |
| priceTicketing/ priceType [2]/ | OBA | OID accepts OB fees |
| recPriceInfo/ monetaryDetail/ amountType |
|
|
| recPriceInfo/ monetaryDetail/ amount |
|
|
| paxFareDetail/ codeShareDetails/ transportStageQualifier | V | Type of carrier: validating carrier used for pricing |
| paxFareDetail/ codeShareDetails/ company | AA | AA is validating carrier |
| paxFareDetail/ monetaryDetails/ amountType | OB | Type of Amount: OB fees |
| paxFareDetail/ monetaryDetails/ amount | 10 | Amount |
It should be noted that the number of recommendations returned are dispersed between applicable fares and will be less than or equal to the number recommendations requested in the query. E.g, One applicable Fare may contain more than one journey, resulting in a set of recommendations based on the same Fare.
Below is a typical reply structure that can be expected to the query sample provided in the "Building A Query" section of this document. The sample reply structure contains the following information for 5 recommendations to a query containing 2 requested segments (1st - Nice to Houston, 2nd - Houston to Nice):
| Item# |
|
Reply Information |
|---|---|---|
| 1 | Applicable Currency of reply in US Dollars | |
| PROPOSED SEGMENTS APPLICABLE TO 1ST REQUESTED SEGMENT | ||
| 2 | Applicable "Requested" Segment - 1st Requested segment | |
| 3 | Applicable "Proposed" Segment - 1st Proposed segment | |
| 4-5 | Total elapsed flying time for proposed segment - 13h50 | |
| 6-30 | Flight Details for 1st proposed segment | |
| 6-18 | 1st flt | Nice to Paris |
| 19-30 | 2nd flt | Paris to Houston |
| 31 | Applicable "Proposed" Segment - 2nd Proposed segment | |
| 32-33 | Total elapsed flying time for proposed segment - 13h50 | |
| 34-59 | Flight Details for 2nd proposed segment | |
| 34-46 | 1st flt | Nice to Paris |
| 47-59 | 2nd flt | Paris to Houston |
| 60 | Applicable "Proposed" Segment - 3rd Proposed segment | |
| 61 | Total elapsed flying time for proposed segment - 13h50 | |
| 62-87 | Flight Details for 2nd proposed segment | |
| 62-74 | 1st flt | Marseilles to Paris |
| 75-87 | 2nd flt | Paris to Houston |
| PROPOSED SEGMENTS APPLICABLE TO 2ND REQUESTED SEGMENT | ||
| 88 | Applicable "Requested" Segment - 2nd Requested segment | |
| 89 | Applicable "Proposed" Segment - 1st Proposed segment | |
| 90-92 | Total elapsed flying time for proposed segment - 12h15 | |
| 93-118 | Flight Details for 1st proposed segment | |
| 93-105 | 1st flt | Houston to London |
| 106-118 | 2nd flt | London to Nice |
| 119 | Applicable "Proposed" Segment - 2nd Proposed segment | |
| 120-121 | Total elapsed flying time for proposed segment - 12h20 | |
| 122-148 | Flight Details for 1st proposed segment | |
| 122-135 | 1st flt | Houston to Paris |
| 136-148 | 2nd flt | Paris to Nice |
| 149 | Applicable "Proposed" Segment - 3rd Proposed segment | |
| 150-151 | Total elapsed flying time for proposed segment - 12h20 | |
| 152-178 | Flight Details for 1st proposed segment | |
| 152-165 | 1st flt | Houston to Paris |
| 166-178 | 2nd flt | Paris to Nice |
| 179 | Applicable "Proposed" Segment - 4th Proposed segment | |
| 180-181 | Total elapsed flying time for proposed segment - 12h25 | |
| 182-208 | Flight Details for 1st proposed segment | |
| 182-195 | 1st flt | Houston to London |
| 196-208 | 2nd flt | London to Nice |
| APPLICABLE RECOMMENDATIONS FOR REQUESTED SEGMENTS | ||
| 209-258 | 1st Set of recommendations for an Applicable fare | |
| 210 | Total Price for all passengers (including taxes) | |
| 211 | Total Taxes for all passengers | |
| 212-215 | Applicable flight combination - completing recommendation #1 | |
| 216-219 | Applicable flight combination - completing recommendation #2 | |
| 220-258 | Applicable Fare Details | |
| 220-238 | Fare Details for Adult passengers | |
| 239-258 | Fare Details for Child passenger | |
| 259-300 | 2nd Set of recommendations for an Applicable fare | |
| 260 | Total Price for all passengers (including taxes) | |
| 261 | Total Taxes for all passengers | |
| 262-265 | Applicable flight combination of - completing recommendation #3 | |
| 266-269 | Applicable flight combination of - completing recommendation #4 | |
| 270-300 | Applicable Fare Details | |
| 301-330 | 3rd Set of recommendations for an Applicable fare | |
| 302 | Total Price for all passengers (including taxes) | |
| 303 | Total Taxes for all passengers | |
| 304-307 | Applicable flight combination of - completing recommendation #5 | |
| 308-330 | Applicable Fare Details | |
NOTE: The reply structure contains all proposed segments listed first followed by associated fare information for the proposed segments to complete each recommendation.
| Item | PoweredLowestFare_SearchReply - Data element | Value |
|---|---|---|
| 1 | /conversionRate/conversionRateDetail/ currency | USD |
| PROPOSED SEGMENTS FOR 1st REQUESTED SEGMENT | ||
| 2 | /flightIndex [1] /requestedSegmentRef/ segRef | 1 |
| 3 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [1] / ref | 1 |
| 4 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [2] / ref | 1350 |
| 5 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [2] / unitQualifier | EFT |
| 6 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / ref | AF |
| 7 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / unitQualifier | MCX |
| 8 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ dateOfDeparture | 200202 |
| 9 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ timeOfDeparture | 0725 |
| 10 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ dateOfArrival | 200202 |
| 11 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ timeOfArrival | 0855 |
| 12 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/location [1] / locationId | NCE |
| 13 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/location [2] / locationId | CDG |
| 14 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/location [2] / airportCityQualifier | A |
| 15 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/companyId/ marketingCarrier | AF |
| 16 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/companyId/ operatingCarrier | AF |
| 17 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/ flightNumber | 7673 |
| 18 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDetail/ equipmentType | 320 |
| 19 | /flightIndex [1] /groupOfFlights [1] / flightDetails [1] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 20 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ dateOfDeparture | 200202 |
| 21 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ timeOfDeparture | 1020 |
| 22 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ dateOfArrival | 200202 |
| 23 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ timeOfArrival | 1415 |
| 24 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/location [1] / locationId | CDG |
| 25 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/location [2] / locationId | IAH |
| 26 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/companyId/ marketingCarrier | CO |
| 27 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/companyId/ operatingCarrier | AF |
| 28 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/ flightNumber | 83 |
| 29 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDetail/ equipmentType | 343 |
| 30 | /flightIndex [1] /groupOfFlights [1] / flightDetails [2] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 31 | /flightIndex [1] /groupOfFlights [2] /propFlightGrDetail/flightProposal [1] / ref | 2 |
| 32 | /flightIndex [1] /groupOfFlights [2] /propFlightGrDetail/flightProposal [2] / ref | 1350 |
| 33 | /flightIndex [1] /groupOfFlights [2] /propFlightGrDetail/flightProposal [2] / unitQualifier | EFT |
| 34 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / ref | AF |
| 35 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / unitQualifier | MCX |
| 36 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ dateOfDeparture | 200202 |
| 37 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ timeOfDeparture | 0725 |
| 38 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ dateOfArrival | 200202 |
| 39 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ timeOfArrival | 0855 |
| 40 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/location [1] / locationId | NCE |
| 41 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/location [2] / locationId | CDG |
| 42 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/companyId/ marketingCarrier | AF |
| 43 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/companyId/ operatingCarrier | AF |
| 44 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/ flightNumber | 7673 |
| 45 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDetail/ equipmentType | 320 |
| 46 | /flightIndex [1] /groupOfFlights [2] / flightDetails [1] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 47 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ dateOfDeparture | 200202 |
| 48 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ timeOfDeparture | 1020 |
| 49 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ dateOfArrival | 200202 |
| 50 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ timeOfArrival | 1415 |
| 51 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/location [1] / locationId | CDG |
| 52 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/location [2] / locationId | IAH |
| 53 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/companyId/ marketingCarrier | AF |
| 54 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/companyId/ operatingCarrier | AF |
| 55 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/ flightNumber | 36 |
| 56 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDetail/ equipmentType | 343 |
| 57 | /flightIndex [1] /groupOfFlights [2] / flightDetails [2] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 58 | /flightIndex [1] /groupOfFlights [3] /propFlightGrDetail/flightProposal [1] / ref | 3 |
| 59 | /flightIndex [1] /groupOfFlights [3] /propFlightGrDetail/flightProposal [2] / ref | 1350 |
| 60 | /flightIndex [1] /groupOfFlights [3] /propFlightGrDetail/flightProposal [2] / unitQualifier | EFT |
| 61 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / ref | AF |
| 62 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / unitQualifier | MCX |
| 63 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ dateOfDeparture | 200202 |
| 64 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ timeOfDeparture | 0725 |
| 65 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ dateOfArrival | 200202 |
| 66 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ timeOfArrival | 0855 |
| 67 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/location [1] / locationId | MRS |
| 68 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/location [2] / locationId | CDG |
| 69 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/location [2] / airportCityQualifier | A |
| 70 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/companyId/ marketingCarrier | AF |
| 71 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/companyId/ operatingCarrier | AF |
| 72 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/ flightNumber | 7673 |
| 73 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDetail/ equipmentType | 320 |
| 74 | /flightIndex [1] /groupOfFlights [3] / flightDetails [1] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 75 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ dateOfDeparture | 200202 |
| 76 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ timeOfDeparture | 1020 |
| 77 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ dateOfArrival | 200202 |
| 78 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ timeOfArrival | 1415 |
| 79 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/location [1] / locationId | CDG |
| 80 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/location [2] / locationId | IAH |
| 81 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/companyId/ marketingCarrier | CO |
| 82 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/companyId/ operatingCarrier | AF |
| 83 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/ flightNumber | 83 |
| 84 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDetail/ equipmentType | 343 |
| 85 | /flightIndex [1] /groupOfFlights [3] / flightDetails [2] /flightInformation/addProductDetail/ electronicTicketing | Y |
| PROPOSED SEGMENTS FOR 2nd REQUESTED SEGMENT | ||
| 86 | /flightIndex [2] /requestedSegmentRef/ segRef | 2 |
| 87 | /flightIndex [2] /groupOfFlights [1] /propFlightGrDetail/flightProposal [1] / ref | 1 |
| 88 | /flightIndex [2] /groupOfFlights [1] /propFlightGrDetail/flightProposal [2] / ref | 1215 |
| 89 | /flightIndex [2] /groupOfFlights [1] /propFlightGrDetail/flightProposal [2] / unitQualifier | EFT |
| 90 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / ref | BA |
| 91 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / unitQualifier | MCX |
| 92 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ dateOfDeparture | 210302 |
| 93 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ timeOfDeparture | 1625 |
| 94 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 95 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ timeOfArrival | 0710 |
| 96 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDateTime/ dateVariation | 1 |
| 97 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/location [1] / locationId | IAH |
| 98 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/location [2] / locationId | LGW |
| 99 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/companyId/ marketingCarrier | BA |
| 100 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/companyId/ operatingCarrier | BA |
| 101 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/ flightNumber | 2024 |
| 102 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/productDetail/ equipmentType | 747 |
| 103 | /flightIndex [2] /groupOfFlights [1] / flightDetails [1] /flightInformation/addProductDetail/ electronicTicketing | N |
| 104 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ dateOfDeparture | 220302 |
| 105 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ timeOfDeparture | 0840 |
| 106 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 107 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDateTime/ timeOfArrival | 1140 |
| 108 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/location [1] / locationId | LGW |
| 109 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/location [2] / locationId | NCE |
| 110 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/companyId/ marketingCarrier | BA |
| 111 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/companyId/ operatingCarrier | BA |
| 112 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/ flightNumber | 2362 |
| 113 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/productDetail/ equipmentType | 737 |
| 114 | /flightIndex [2] /groupOfFlights [1] / flightDetails [2] /flightInformation/addProductDetail/ electronicTicketing | N |
| 115 | /flightIndex [2] /groupOfFlights [2] /propFlightGrDetail/flightProposal [1] / ref | 2 |
| 116 | /flightIndex [2] /groupOfFlights [2] /propFlightGrDetail/flightProposal [2] / ref | 1220 |
| 117 | /flightIndex [2] /groupOfFlights [2] /propFlightGrDetail/flightProposal [2] / unitQualifier | EFT |
| 118 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / ref | CO |
| 119 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / unitQualifier | MCX |
| 120 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ dateOfDeparture | 210302 |
| 121 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ timeOfDeparture | 1840 |
| 122 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 123 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ timeOfArrival | 1055 |
| 124 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDateTime/ dateVariation | 1 |
| 125 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/location [1] / locationId | IAH |
| 126 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/location [2] / locationId | CDG |
| 127 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/companyId/ marketingCarrier | CO |
| 128 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/companyId/ operatingCarrier | CO |
| 129 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/ flightNumber | 10 |
| 130 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/productDetail/ equipmentType | 777 |
| 131 | /flightIndex [2] /groupOfFlights [2] / flightDetails [1] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 132 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ dateOfDeparture | 220302 |
| 133 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ timeOfDeparture | 1235 |
| 134 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 135 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDateTime/ timeOfArrival | 1400 |
| 136 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/location [1] / locationId | CDG |
| 137 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/location [2] / locationId | NCE |
| 138 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/companyId/ marketingCarrier | AF |
| 139 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/companyId/ operatingCarrier | AF |
| 140 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/ flightNumber | 7664 |
| 141 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/productDetail/ equipmentType | 320 |
| 142 | /flightIndex [2] /groupOfFlights [2] / flightDetails [2] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 143 | /flightIndex [2] /groupOfFlights [3] /propFlightGrDetail/flightProposal [1] / ref | 3 |
| 144 | /flightIndex [2] /groupOfFlights [3] /propFlightGrDetail/flightProposal [2] / ref | 1220 |
| 145 | /flightIndex [2] /groupOfFlights [3] /propFlightGrDetail/flightProposal [2] / unitQualifier | EFT |
| 146 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / ref | CO |
| 147 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / unitQualifier | MCX |
| 148 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ dateOfDeparture | 210302 |
| 149 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ timeOfDeparture | 1840 |
| 150 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 151 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ timeOfArrival | 1055 |
| 152 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDateTime/ dateVariation | 1 |
| 153 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/location [1] / locationId | IAH |
| 154 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/location [2] / locationId | CDG |
| 155 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/companyId/ marketingCarrier | AF |
| 156 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/companyId/ operatingCarrier | CO |
| 157 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/ flightNumber | 35 |
| 158 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/productDetail/ equipmentType | 777 |
| 159 | /flightIndex [2] /groupOfFlights [3] / flightDetails [1] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 160 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ dateOfDeparture | 220302 |
| 161 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ timeOfDeparture | 1235 |
| 162 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 163 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDateTime/ timeOfArrival | 1400 |
| 164 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/location [1] / locationId | CDG |
| 165 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/location [2] / locationId | NCE |
| 166 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/companyId/ marketingCarrier | AF |
| 167 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/companyId/ operatingCarrier | AF |
| 168 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/ flightNumber | 7664 |
| 169 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/productDetail/ equipmentType | 320 |
| 170 | /flightIndex [2] /groupOfFlights [3] / flightDetails [2] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 171 | /flightIndex [2] /groupOfFlights [4] /propFlightGrDetail/flightProposal [1] / ref | 4 |
| 172 | /flightIndex [2] /groupOfFlights [4] /propFlightGrDetail/flightProposal [2] / ref | 1225 |
| 173 | /flightIndex [2] /groupOfFlights [4] /propFlightGrDetail/flightProposal [2] / unitQualifier | EFT |
| 174 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / ref | CO |
| 175 | /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal [3] / unitQualifier | MCX |
| 176 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/productDateTime/ dateOfDeparture | 210302 |
| 177 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/productDateTime/ timeOfDeparture | 1850 |
| 178 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 179 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/productDateTime/ timeOfArrival | 0955 |
| 180 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/productDateTime/ dateVariation | 1 |
| 181 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/location [1] / locationId | IAH |
| 182 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/location [2] / locationId | LGW |
| 183 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/companyId/ marketingCarrier | CO |
| 184 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/companyId/ operatingCarrier | CO |
| 185 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/ flightNumber | 4 |
| 186 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/productDetail/ equipmentType | 777 |
| 187 | /flightIndex [2] /groupOfFlights [4] / flightDetails [1] /flightInformation/addProductDetail/ electronicTicketing | Y |
| 188 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/productDateTime/ dateOfDeparture | 220302 |
| 189 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/productDateTime/ timeOfDeparture | 1115 |
| 190 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/productDateTime/ dateOfArrival | 220302 |
| 191 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/productDateTime/ timeOfArrival | 1415 |
| 192 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/location [1] / locationId | LGW |
| 193 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/location [2] / locationId | NCE |
| 194 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/companyId/ marketingCarrier | BA |
| 195 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/companyId/ operatingCarrier | BA |
| 196 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/ flightNumber | 2368 |
| 197 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/productDetail/ equipmentType | AR1 |
| 198 | /flightIndex [2] /groupOfFlights [4] / flightDetails [2] /flightInformation/addProductDetail/ electronicTicketing | N |
| RECOMMENDATIONS | ||
| 1st SET OF RECOMMENDATIONS BASED ON 1 FARE | ||
| 199 | /recommendation [1] /itemNumber/itemNumberId/ number | 1 |
| APPLICABLE FARE AMOUNT | ||
| 200 | /recommendation [1] /recPriceInfo/monetaryDetail [1] / amount | 1800.11 |
| 201 | /recommendation [1] /recPriceInfo/monetaryDetail [2] / amount | 150.00 |
| 1st APPLICABLE JOURNEY - RECOMMENDATION # 1 | ||
| 202 | /recommendation [1] /segmentFlightRef [1] /referencingDetail [1] / refQualifier | S |
| 203 | /recommendation [1] /segmentFlightRef [1] /referencingDetail [1] / refNumber | 1 |
| 204 | /recommendation [1] /segmentFlightRef [1] /referencingDetail [2] / refQualifier | S |
| 205 | /recommendation [1] /segmentFlightRef [1] /referencingDetail [2] / refNumber | 1 |
| 2nd APPLICABLE JOURNEY - RECOMMENDATION # 2 | ||
| 206 | /recommendation [1] /segmentFlightRef [2] /referencingDetail [1] / refQualifier | S |
| 207 | /recommendation [1] /segmentFlightRef [2] /referencingDetail [1] / refNumber | 2 |
| 208 | /recommendation [1] /segmentFlightRef [2] /referencingDetail [2] / refQualifier | S |
| 209 | /recommendation [1] /segmentFlightRef [2] /referencingDetail [2] / refNumber | 3 |
| APPLICABLE FARE DETAILS | ||
| 210 | /recommendation [1] /paxFareProduct [3] /paxFareDetail/ paxFareNum | 1 |
| 211 | /recommendation [1] /paxFareProduct [3] /paxFareDetail/ totalFareAmount | 1100.00 |
| 212 | /recommendation [1] /paxFareProduct [3] /paxFareDetail/ totalTaxAmount | 60.00 |
| 213 | /recommendation [1] /paxFareProduct [3] /paxReference/ ptc | ADT |
| 214 | /recommendation [1] /paxFareProduct [3] /paxReference/traveller [1] / ref | 1 |
| 215 | /recommendation [1] /paxFareProduct [3] /paxReference/traveller [2] / ref | 2 |
| 216 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /segmentRef/ segRef | 1 |
| 217 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/cabinProduct/ rbd | M |
| 218 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/cabinProduct/ cabin | M |
| 218-2 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/cabinProduct/ avlStatus | 4 |
| 219 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/fareProductDetail/ fareBasis | MLXPX |
| 220 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/fareProductDetail/ passengerType | ADT |
| 221 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/fareProductDetail/ fareType | RP |
| 222 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/ Breakpoint | N |
| 223 | /recommendation [1] /paxFareProduct [3] /fareDetails [2] /segmentRef/ segRef | 2 |
| 224 | /recommendation [1] /paxFareProduct [3] /fareDetails [2] / productInformation/avlProductDetails/ rbd | M |
| 225 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/cabinProduct/ cabin | M |
| 226 | /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/ productInformation/cabinProduct/ avlStatus | 4 |
| 227 | /recommendation [1] /paxFareProduct [3] /fareDetails [2] / productInformation/fareProductDetail/ fareBasis | MLXPX |
| 228 | /recommendation [1] /paxFareProduct [3] /fareDetails [2] / productInformation/fareProductDetail/ passengerType | ADT |
| 229 | /recommendation [1] /paxFareProduct [3] /fareDetails [2] / productInformation/fareProductDetail/ fareType | RP |
| 230 | /recommendation [1] /paxFareProduct [3] /fareDetails [2] /groupOfFares/ productInformation/ Breakpoint | Y |
| 231 | /recommendation [1] /paxFareProduct [4] /paxFareDetail/ paxFareNum | 1 |
| 232 | /recommendation [1] /paxFareProduct [4] /paxFareDetail/ totalFareAmount | 700.11 |
| 233 | /recommendation [1] /paxFareProduct [4] /paxFareDetail/ totalTaxAmount | 30.00 |
| 234 | /recommendation [1] /paxFareProduct [4] /paxReference/ ptc | CH |
| 235 | /recommendation [1] /paxFareProduct [4] /paxReference/traveller/ ref | 3 |
| 236 | /recommendation [1] /paxFareProduct [4] /fare/pricingMessage/ freeTextQualification/ messageQualifier | APM |
|
|
/recommendation [1] /paxFareProduct [4] /fare/pricingMessage/ freeTextQualification/ messageCode | 5 |
| 237 | /recommendation [1]/paxFareProduct [4] /fare/pricingMessage/ description [1] | NOT FARED AT PASSENGER TYPE REQUESTED |
| 238 | /recommendation [1] /paxFareProduct [4] /fare/pricingMessage/ description [2] | 5 |
| 239 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] /segmentRef/ segRef | 1 |
| 240 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] / productInformation/avlProductDetails/ rbd | M |
| 241 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] /groupOfFares/ productInformation/cabinProduct/ cabin | M |
| 242 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] /groupOfFares/ productInformation/cabinProduct/ avlStatus | 4 |
| 243 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] / productInformation/fareProductDetail/ fareBasis | Y4WCH |
| 244 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] / productInformation/fareProductDetail/ passengerType | CH |
| 245 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] / productInformation/fareProductDetail/ fareType | RP |
| 246 | /recommendation [1] /paxFareProduct [4] /fareDetails [1] /groupOfFares/ productInformation/ Breakpoint | N |
| 247 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] /segmentRef/ segRef | 2 |
| 248 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] / productInformation/avlProductDetails/ rbd | M |
| 249 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] /groupOfFares/ productInformation/cabinProduct/ cabin | M |
| 250 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] /groupOfFares/ productInformation/cabinProduct/ avlStatus | 4 |
| 251 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] / productInformation/fareProductDetail/ fareBasis | Y4W |
| 252 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] / productInformation/fareProductDetail/ passengerType | ADT |
| 253 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] / productInformation/fareProductDetail/ fareType | RP |
| 254 | /recommendation [1] /paxFareProduct [4] /fareDetails [2] /groupOfFares/ productInformation/ Breakpoint | Y |
| 2nd SET OF RECOMMENDATIONS BASED ON 1 FARE | ||
| 249 | /recommendation [2] /itemNumber/itemNumberId/ number | 2 |
| APPLICABLE FARE AMOUNT | ||
| 250 | /recommendation [2] /recPriceInfo/monetaryDetail [1] / amount | 1989.70 |
| 251 | /recommendation [2] /recPriceInfo/monetaryDetail [2] / amount | 200.00 |
| 1st APPLICABLE JOURNEY - RECOMMENDATION # 3 | ||
| 252 | /recommendation [2] /segmentFlightRef [1] /referencingDetail [1] / refQualifie | S |
| 253 | /recommendation [2] /segmentFlightRef [1] /referencingDetail [1] / refNumber | 1 |
| 254 | /recommendation [2] /segmentFlightRef [1] /referencingDetail [2] / refQualifier | S |
| 255 | /recommendation [2] /segmentFlightRef [1] /referencingDetail [2] / refNumber | 3 |
| 2nd APPLICABLE JOURNEY - RECOMMENDATION # 4 | ||
| 256 | /recommendation [2] /segmentFlightRef [2] /referencingDetail [1] / refQualifier | S |
| 257 | /recommendation [2] /segmentFlightRef [2] /referencingDetail [1] / refNumber | 1 |
| 258 | /recommendation [2] /segmentFlightRef [2] /referencingDetail [2] / refQualifier | S |
| 259 | /recommendation [2] /segmentFlightRef [2] /referencingDetail [2] / refNumber | 4 |
| APPLICABLE FARE DETAILS | ||
| 260 | /recommendation [2] /paxFareProduct [3] /paxFareDetail/ paxFareNum | 1 |
| 261 | /recommendation [2] /paxFareProduct [3] /paxFareDetail/ totalFareAmount | 1209.70 |
| 262 | /recommendation [2] /paxFareProduct [3] /paxFareDetail/ totalTaxAmount | 70.00 |
| 263 | /recommendation [2] /paxFareProduct [3] /paxReference/ ptc | ADT |
| 264 | /recommendation [2] /paxFareProduct [3] /paxReference/traveller [1] / ref | 1 |
| 265 | /recommendation [2] /paxFareProduct [3] /paxReference/traveller [2] / ref | 2 |
| 266 | /recommendation [2] /paxFareProduct [3] /fareDetails [1] /segmentRef/ segRef | 1 |
| 267 | /recommendation [2] /paxFareProduct [3] /fareDetails [1] / productInformation/avlProductDetails/ rbd | M |
| 268 | /recommendation [2] /paxFareProduct [3] /fareDetails [1] / productInformation/fareProductDetail/ fareBasis | TLXAPT3 |
| 269 | /recommendation [2] /paxFareProduct [3] /fareDetails [1] / productInformation/fareProductDetail/ passengerType | ADT |
| 270 | /recommendation [2] /paxFareProduct [3] /fareDetails [1] / productInformation/fareProductDetail/ fareType | RP |
| 271 | /recommendation [2] /paxFareProduct [3] /fareDetails [2] /segmentRef/ segRef | 2 |
| 272 | /recommendation [2] /paxFareProduct [3] /fareDetails [2] / productInformation/avlProductDetails/ rbd | M |
| 273 | /recommendation [2] /paxFareProduct [3] /fareDetails [2] / productInformation/fareProductDetail/ fareBasis | TLXAPT3 |
| 274 | /recommendation [2] /paxFareProduct [3] /fareDetails [2] / productInformation/fareProductDetail/ passengerType | ADT |
| 275 | /recommendation [2] /paxFareProduct [3] /fareDetails [2] / productInformation/fareProductDetail/ fareType | RP |
| 276 | /recommendation [2] /paxFareProduct [4] /paxFareDetail/ paxFareNum | 1 |
| 277 | /recommendation [2] /paxFareProduct [4] /paxFareDetail/ totalFareAmount | 780.00 |
| 278 | /recommendation [2] /paxFareProduct [4] /paxFareDetail/ totalTaxAmount | 60.00 |
| 279 | /recommendation [2] /paxFareProduct [4] /paxReference/ ptc | CH |
| 280 | /recommendation [2] /paxFareProduct [4] /paxReference/traveller/ ref | 3 |
| 281 | /recommendation [2] /paxFareProduct [4] /fareDetails [1] /segmentRef/ segRef | 1 |
| 282 | /recommendation [2] /paxFareProduct [4] /fareDetails [1] / productInformation/avlProductDetails/ rbd | M |
| 283 | /recommendation [2] /paxFareProduct [4] /fareDetails [1] / productInformation/fareProductDetail/ fareBasis | TLXAPTCH |
| 284 | /recommendation [2] /paxFareProduct [4] /fareDetails [1] / productInformation/fareProductDetail/ passengerType | CH |
| 285 | /recommendation [2] /paxFareProduct [4] /fareDetails [1] / productInformation/fareProductDetail/ fareType | RP |
| 286 | /recommendation [2] /paxFareProduct [4] /fareDetails [2] /segmentRef/ segRef | 2 |
| 287 | /recommendation [2] /paxFareProduct [4] /fareDetails [2] / productInformation/avlProductDetails/ rbd | M |
| 288 | /recommendation [2] /paxFareProduct [4] /fareDetails [2] / productInformation/fareProductDetail/ fareBasis | TLXAPTCH |
| 289 | /recommendation [2] /paxFareProduct [4] /fareDetails [2] / productInformation/fareProductDetail/ passengerType | CH |
| 290 | /recommendation [2] /paxFareProduct [4] /fareDetails [2] / productInformation/fareProductDetail/ fareType | RP |
| 3rd SET OF RECOMMENDATIONS BASED ON 1 FARE | ||
| 291 | /recommendation [3] /itemNumber/itemNumberId/ number | 3 |
| APPLICABLE FARE AMOUNT | ||
| 292 | /recommendation [3] /recPriceInfo/monetaryDetail [1] / amount | 2350.50 |
| 293 | /recommendation [3] /recPriceInfo/monetaryDetail [2] / amount | 200.00 |
| 1st ASSOCIATED JOURNEY - RECOMMENDATION # 5 | ||
| 294 | /recommendation [3] /segmentFlightRef [1] /referencingDetail [1] / refQualifier | S |
| 295 | /recommendation [3] /segmentFlightRef [1] /referencingDetail [1] / refNumber | 2 |
| 296 | /recommendation [3] /segmentFlightRef [1] /referencingDetail [2] / refQualifier | S |
| 297 | /recommendation [3] /segmentFlightRef [1] /referencingDetail [2] / refNumber | 1 |
| APPLICABLE FARE DETAILS | ||
| 298 | /recommendation [3] /paxFareProduct [7] /paxFareDetail/ paxFareNum | 1 |
| 299 | /recommendation [3] /paxFareProduct [7] /paxFareDetail/ totalFareAmount | 1350.00 |
| 300 | /recommendation [3] /paxFareProduct [7] /paxFareDetail/ totalTaxAmount | 70.00 |
| 301 | /recommendation [3] /paxFareProduct [7] /paxReference/ ptc | ADT |
| 302 | /recommendation [3] /paxFareProduct [7] /paxReference/traveller [1] / ref | 1 |
| 303 | /recommendation [3] /paxFareProduct [7] /paxReference/traveller [2] / ref | 2 |
| 304 | /recommendation [3] /paxFareProduct [7] /fareDetails [1] /segmentRef/ segRef | 1 |
| 305 | /recommendation [3] /paxFareProduct [7] /fareDetails [1] / productInformation/avlProductDetails/ rbd | C |
| 306 | /recommendation [3] /paxFareProduct [7] /fareDetails [1] / productInformation/fareProductDetail/ fareType | RP |
| 307 | /recommendation [3] /paxFareProduct [7] /fareDetails [2] /segmentRef/ segRef | 2 |
| 308 | /recommendation [3] /paxFareProduct [7] /fareDetails [2] / productInformation/avlProductDetails/ rbd | D |
| 309 | /recommendation [3] /paxFareProduct [7] /fareDetails [2] / productInformation/fareProductDetail/ fareType | RP |
| 310 | /recommendation [3] /paxFareProduct [8] /paxFareDetail/ paxFareNum | 1 |
| 311 | /recommendation [3] /paxFareProduct [8] /paxFareDetail/ totalFareAmount | 1000.50 |
| 312 | /recommendation [3] /paxFareProduct [8] /paxFareDetail/ totalTaxAmount | 60.00 |
| 313 | /recommendation [3] /paxFareProduct [8] /paxReference/ ptc | CH |
| 314 | /recommendation [3] /paxFareProduct [8] /paxReference/traveller/ ref | 3 |
| 315 | /recommendation [3] /paxFareProduct [8] /fareDetails [1] /segmentRef/ segRef | 1 |
| 316 | /recommendation [3] /paxFareProduct [8] /fareDetails [1] / productInformation/avlProductDetails/ rbd | C |
| 317 | /recommendation [3] /paxFareProduct [8] /fareDetails [1] / productInformation/fareProductDetail/ fareType | RP |
| 318 | /recommendation [3] /paxFareProduct [8] /fareDetails [2] /segmentRef/ segRef | 2 |
| 319 | /recommendation [3] /paxFareProduct [8] /fareDetails [2] / productInformation/avlProductDetails/ rbd | D |
| 320 | /recommendation [3] /paxFareProduct [8] /fareDetails [2] / productInformation/fareProductDetail/ fareType | RP |
Specific error conditions exist for each mandatory and optional parameter in the query. However, as these errors may be returned in several instances and it is not always apparent to which operational parameter they apply, this section provides the following general errors that may be returned when building a query;
If a mandatory element is missing in the query structure, including any elements that are deemed mandatory via an association to another optional parameter, the entire entry is rejected locally by the API application.
It should be noted here that these messages are returned in the instances when no recommendations can be found.
No Recommendation Found For Requested Itinerary/Options
Whenever the Powered Lowest Fare Search does not find any recommendation matching the requested options, the query is rejected with the following message:
"NO RECOMMENDATION FOUND FOR REQUESTED ITINERARY/OPTIONS"
No Available Flight Found For The Requested Segment Nn
In the current Powered Lowest Fare Search process, when no flight is available (For example, all the flights matching the requested itinerary are set to 0 or closed), the transaction is rejected with the message:
"ERC - CODE SET 9321: VALUE 977 - NO AVAILABLE FLIGHT FOUND FOR THE REQUESTED SEGMENT nn"
(Where: nn represents the first impacted requested segment number).
These messages are returned when there is an error in the PoweredLowestFare_Search input.
Latest Future Date Possible ddmmmyy
A reject message will be produced by the server; indicating that a query is too far into the future when it goes beyond the latest possible date. The corresponding reject message:
"LATEST FUTURE DATE POSSIBLE ddmmmyy"
Too Many Airline Codes
If more than 99 airline codes are specified at the 'Include Airline' option level, the entire entry is rejected and the following message is returned:
"TOO MANY AIRLINE CODES"
Invalid Value (Coded) - Pricingtickinfo
The only valid expanded parameter options applicable to a MP request are NAP, NPE, NR and RF. If an unknown Expanded Parameter is specified in the entry, the entire request is rejected and the following error message is returned:
"INVALID VALUE (CODED) - PRICINGTICKINFO"
Invalid Value Coded - Pricingtickinfo
If an unknown Unifare option is specified in the entry, the entire request is rejected and the following error message is returned:
"INVALID VALUE CODED - PRICINGTICKINFO".
Too Many Requested Segments
Up to 3 Requested Segments 'Lowest Fare search' requests are allowed, excluding surface sectors. If this check fails, the entire entry is rejected with the following message:
"TOO MANY REQUESTED SEGMENTS".
Invalid Value (Coded) - Conversion Rate
If an unknown Currency is specified in the Lowest Fare search entry, the entire request is rejected and the following error message is returned:
"INVALID VALUE (CODED) - CONVERSION RATE".
Invalid Value (Coded)
If an un-authorized value is specified in a field flagged as 'coded' at the Lowest Fare Search Input message level, the entire entry is rejected and, if no other specific error message exists, the following generic reject message is returned:
"INVALID VALUE (CODED) - XXX"
where XXX is the Segment smart name (e.g. paxReference).
Note: When a field is flagged as coded, refer to the corresponding code set to check the list of values authorized
| No. | Message |
|---|---|
| 118 | System unable to process |
| 304 | System temporarily unavailable |
| 830 | No recommendation found with lower or equal price |
| 910 | Transaction closed |
| 915 | Fare product unavailable for user |
| 916 | EDIFACT version not supported |
| 917 | EDIFACT message size Exceeded |
| 918 | Number of Requested Segments exceeds three |
| 919 | SOTI/SITO/SOTO Requests are not handled |
| 920 | Past Date/Time not allowed |
| 921 | Date/Time must be in chronological order |
| 922 | Maximum 2 Requested Segments with same date |
| 923 | Specify Times of Arrival/Departure to avoid overlapping |
| 924 | Overlapping Date/Time ranges |
| 925 | Overlapping Origin//Destination Segment |
| 926 | Invalid number of passenger |
| 927 | Number of passenger exceeds nine |
| 928 | Exceeds maximum fare discount codes |
| 929 | Option cannot be applied at Requested Segment level |
| 930 | Option cannot be applied at itinerary level |
| 931 | No itinerary found for Requested Segment n |
| 932 | RG LFS not applicable for this request |
| 934 | Invalid radius - maximum allowed 300km |
| 935 | Invalid range of date option |
| 936 | Invalid time option |
| 937 | Invalid time window option |
| 938 | Time of Departure/Arrival is mandatory if time window requested |
| 939 | Date is mandatory with time window option |
| 940 | Invalid airline code |
| 941 | Invalid exclude airline option |
| 942 | Airline cannot be at the same time included and excluded |
| 943 | Invalid - 20 airline codes maximum |
| 944 | Invalid flight category |
| 945 | Non-stop cannot be requested with connect point option |
| 946 | Invalid connecting point |
| 947 | Same city/airport code cannot be included and excluded |
| 948 | City/airport must be in same country |
| 950 | Invalid City |
| 952 | Conflicting options used |
| 953 | Invalid Unifare option |
| 954 | Service Level option must be requested |
| 955 | Invalid passenger type code |
| 956 | Exceeds maximum fare discount codes |
| 957 | Number of non-infant PTC cannot exceed number of seats |
| 958 | Number of infants cannot exceed number of seats |
| 960 | Invalid Ticketing/Selling city |
| 961 | Invalid conversion currency |
| 962 | Invalid price to beat value |
| 963 | INVALID VALUE (CODED) - originator |
| 964 | INVALID VALUE (CODED) - numberOfUnit |
| 965 | INVALID VALUE (CODED) - paxReference |
| 966 | INVALID VALUE (CODED) - pricingTickInfo |
| 967 | INVALID VALUE (CODED) - conversionRate |
| 968 | INVALID VALUE (CODED) - corporate |
| 969 | INVALID VALUE (CODED) - priceToBeat |
| 970 | INVALID VALUE (CODED) - taxInfo |
| 971 | INVALID VALUE (CODED) - travelFlightInfo |
| 972 | INVALID VALUE (CODED) - requestedSegmentRef |
| 973 | INVALID VALUE (CODED) - departureLocalization |
| 974 | INVALID VALUE (CODED) - arrivalLocalization |
| 975 | INVALID VALUE (CODED) - timeDetails |
| 976 | INVALID VALUE (CODED) - flightInfo |
| 977 | NO AVAILABLE FLIGHT FOUND FOR REQUESTED SEGMENT NN |
| 978 | TOO MANY REQUESTED SEGMENTS |
| 979 | INVALID OPTION |
| 980 | INVALID TYPE OF ITINERARY |
| 981 | NO FARE FOUND FOR REQUESTED ITINERARY |
| 982 | SPECIFY AIRLINE |
| 983 | TOO MANY AIRLINES |
| 984 | SPECIFY A COMMERCIAL FARE FAMILY |
| 985 | INVALID COMMERCIAL FARE FAMILY |
| 986 | TOO MANY COMMERCIAL FARE FAMILY REQUESTED |
| 987 | NO FARE FAMILY FOUND FOR REQUESTED COMMERCIAL FARE FAMILY |
| 988 | EXCEEDS MAXIMUM DISCOUNT CODES FOR A PASSENGER |
| 993 | INVALID TIME AT DESTINATION |
| 994 | INVALID ITINERARY POINT OF ORIGIN OPTION |
| 995 | NO FARE FOUND FOR REQUESTED FARE FAMILY |
| 997 | Fare Basis and Prime Booking Code Cannot Be Mixed |
| 998 | Invalid Type of Fare Requested |
| 999 | Invalid Fare Family Combinability Requested |
| 997 | Invalid Generic Fare Basis requested |
|
|
INVALID PRIME BOOKING CODE |
|
|
TOO MANY FARE FAMILIES |
|
|
TOO MANY MATCHING ATTRIBUTES SETS REQUESTED |
|
|
TOO MANY ATTRIBUTE OCCURENCES |
|
|
INVALID FARE FAMILY NAME REQUESTED |
|
|
INVALID CARRIER REQUESTED |
| 836 | DATE OVERRIDE OPTION NOT ALLOWED |
A Date must be specified for each Requested Segment. Note that Times and Dates are specified in local time, at each location.
No past Date and/or past Time are allowed.
When 2 or more Requested Segments are specified, Dates and Times must be in chronological order. Times and dates are specified in local time, at each location, but the chronological order check must consider the TU times and dates.
Up to 2 requested segments may be requested with the same Date, or overlapping Date ranges, as long as the User specifies both:
A maximum of 3 Requested Segments is allowed, excluding surface sectors. These requested segments must each include an origin and a destination City/Airport code.
Such as,
| One way | NCE-LON |
| Return trip | NCE-LON-NCE |
| Multiple segments | NCE-LON-MAD-NCE |
| Itinerary including surface sector | NCE-LON/MAN-NCE |
The origin and destination codes must comply with the standard IATA City/Airport codes. If an IATA code is not unique to a specific airport, but identifies at the same time, aCity (e.g. CHI) and an Airport (e.g. HOU) the three-letter code represents the City unless it is specifically identified as an airport (A) type. Whenever the request intends to restrict the search only to the Airport, this must be specified in the case where the IATA code is not unique to an airport.
The following table illustrates further the possible scenarios of the origin/destination search process:
| Code Entered | Specified as City/Airport | Applicable point of departure/arrival searched |
|---|---|---|
| CHI | Not Specified | Chicago city, including the following airports: - O'Hare (ORD) - Midway (MDW) |
| CHI | City Location | Chicago city, including the following airports: - O'Hare (ORD) - Midway (MDW) |
| CHI | Airport Location | Chicago city, including the following airports: - O'Hare (ORD) - Midway (MDW)(because CHI airport code does not exist) |
| ORD | Not specified | O'Hare (ORD) |
| HOU | Not Specified | Houston city, including the following airports: - Houston Hobby (HOU) - G.Bush Intercontinental (IAH) |
| HOU | City location | Houston city, including the following airports: - Houston Hobby(HOU) - G.Bush Intercontinental (IAH) |
| HOU | Airport location | Houston Hobby (HOU) airport only |
Only Sold in / Ticketed in (SITI) requests are handled. That means that:
Example:
| Itinerary | International/Domestic | SITI country |
|---|---|---|
| CHI-NYC | Domestic | USA |
| NCE-PAR -- LON-MAN | Domestic | France |
| CHI-LON | International | USA |
| NCE-PAR-NYC | International | France |
| NCE-PAR-NYC-MEX | International | France |
| NCE-PAR -- LON-NYC | International | UK |
Number of Passenger Seats
The number of passenger seats must be between 1 and 9.
The recommendations returned are applicable to all passengers in the query. All passengers must be travelling together.
Associated Passenger Type Codes
As the passenger fares vary for different types of passengers, a passenger type code for any low fare search is required. Passenger type codes dictate the low fare search to provide recommendations with any qualifying passenger fare discounts applicable. All passenger type codes specified must be valid type codes stored within the Amadeus system.
A maximum of 6 passenger type codes may be requested.
When more than one Passenger Type is requested, the system must search for the cheapest fares with the possibility to return non-homogeneous recommendations: different passengers booked in different classes in order to offer a lowest fare.
In such a case, it becomes mandatory to split the traveling parties into separate records to accommodate the lowest fare recommendation. This can be accomplished via the Powered PNR interface.
When a non-homogeneous recommendation is proposed, the following warning message is returned:
"SPLIT PNR - DIFFERENT BOOKING CODES REQUIRED FOR LOWEST FARE"
Exception: Infant must travel in the same class as the accompanying "adult"passengers (e.g. ADT, YTH, MIL, etc.).
Note: When specifying a PTC 'inf' without a seat, they must be associated to a passenger accompanying a seat.
The user must specify the total number of recommendations to be returned.
The total number of requested recommendations must be a valid number between 1 and 200. If a number higher than 200 is requested, the query will not be rejected but no more than 200 recommendations will be returned.
The example below illustrates a low fare search including the mandatory function elements of itinerary date, origin/destination, and number of passengers with associated types specified with the following information;
Query Requirements:
MANDATORY ORIGIN/DESTINATION INFORMATION FOR 1 REQUESTED SEGMENT
|
MANDATORY ITINERARY DATE FOR 1 REQUESTED SEGMENT
|
MANDATORY PASSENGER INFORMATION
|
MANDATORY NUMBER OF RECOMMENDATIONS
|
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 3 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Applicable passenger type code for Adult | ADT |
| Passenger reference for 1st seat | 1 |
| Passenger reference for 2nd seat | 2 |
| Applicable passenger type code for Child | CH |
| Passenger reference for 3rd seat | 3 |
| Applicable passenger type code for Infant | INF |
| Passenger reference associated to first Adult seat | 1 |
| Infant indicator | 1 |
| 1st requested segment | 1 |
| Departure city of London | LON |
| Arrival city of New York | NYC |
| Trip Date (Aug 14, 2003) | 140803 |
Date is Mandatory
If no date is found in the query structure, the entire entry is rejected with the following message:
"DATE IS MANDATORY"
Past Date/Time Not Allowed
If a past Date and/or past Time are found in the query, the entire entry is rejected with the following message:
"PAST DATE/TIME NOT ALLOWED".
Date/Time Must be in Chronological Order
When 2 or more Requested Segments are specified, if the Dates and Times are not in chronological order, the entire entry is rejected with the following message:
"DATE/TIME MUST BE IN CHRONOLOGICAL ORDER"
Maximum 2 Requested Segments with Same Date
If more than 2 Requested Segments (excluding surface segments) are found with the same Date, the entire entry is rejected with the following message:
"MAXIMUM 2 REQUESTED SEGMENTS WITH SAME DATE".
Specify Times of Arrival/Departure to Avoid Overlapping
If 2 requested segments are requested with the same date, or overlapping Date ranges, and the required parameters are not specified,
The following error message is returned:
"SPECIFY TIMES OF ARRIVAL/DEPARTURE TO AVOID OVERLAPPING".Overlapping Date/Time Ranges
The system verifies that there is no overlapping of the requested time ranges. This check also applies when a time range is requested and time ranges overlap, the time ranges being interpreted according to the time or time window option definition. If this check fails, the entire entry is rejected with the following message:
"OVERLAPPING DATE/TIME RANGES".
When two consecutive requested air segments have a close (or equal) travel date,add a 'Time of Arrival' option on the chronologically first segment and a'Time of Departure' on the next segment.This will avoid you experiencing numerous Master Pricer "Near requested travel dates"query failures because of missing mandatory option in the PoweredLowestFare request.
Note: See Certification Guidelines for more detail.
"Near requested travel dates" queries are defined as queries for which the difference between the arrival time departure times of the 2 consecutive requested segments (i.e. the latest possible departure time of the first requested segment and the earliest possible departure time of the next requested segment) is inferior to 12 hours.
Number of Requested Segments Exceeds Three
If more than 3 Requested Segments are found in the query, excluding surface sectors,the entire entry is rejected with the following message:
"NUMBER OF REQUESTED SEGMENTS EXCEEDS THREE".
Overlapping Origin/Destination Segment N
The system verifies that there is no overlapping between the origin and the destination of any requested segment. The origin and destination being requested as airport, city, area or multi-city, an overlap is detected when, for a segment, at least one of the alternate origins corresponds to one of the alternate destinations. If this check fails, the entire entry is rejected with the following message:
"OVERLAPPING ORIGIN/DESTINATION SEGMENT N"
where N is the number of the first segment where an overlap is detected
Unknown City/Airport
If an invalid city/airport code is specified in the request, the following reject message will be returned:
"UNKNOWN CITY/AIRPORT"
Invalid Number of Passenger
If the specified number of passengers with seats is 0, the entire entry is rejected with the following message:
"INVALID NUMBER OF PASSENGER".
Number of Passengers Exceeds Nine
If the specified number of passengers with seats exceeds 9, the entire entry is rejected with the following message:
"NUMBER OF PASSENGERS EXCEEDS NINE".
Invalid Passenger Type Code
Requested Passenger Type Codes are validated against the Amadeus System codes. If the Passenger Type Code does not exist, the entire request is rejected and the following error message is returned:
"INVALID PASSENGER TYPE CODE"
Exceeds Maximum Fare Discount Codes
If more than 6 Passenger Types are specified, the entire request is rejected and the following error message is returned:
"EXCEEDS MAXIMUM FARE DISCOUNT CODES".
The Number of Non-Infant PTC Cannot Exceed Number of Seats
The number of Passenger Types requiring seats (i.e. all Passenger Type Codes with the exception of IN and INF) cannot exceed the number of seats specified in the input. If this check fails, the entire request is rejected and the following error message is returned:
"NUMBER OF NON-INFANT PTC CANNOT EXCEED NUMBER OF SEATS".
The Number of Infants Cannot Exceed Number of Seats
The number of Passengers not requiring seats (IN or INF code) cannot exceed the number of seats specified (as only 1 infant is allowed per passenger having a seat). If this check fails, the entire request is rejected and the following error message is returned:
"NUMBER OF INFANTS CANNOT EXCEED NUMBER OF SEATS".
As this is a mandatory element which will fail on the local application prior to processing if not included in the query and an invalid number of recommendations (higher than 200) in the query isignored, no system error conditions currently exist for this option.
This option allows to request all ancillary services fees within one generic service sub-code "A".
See "Error Messages" section.
NOTE: this option is not yet available
This option allows the ancillary services amounts to be taken into account when determining the lowest recommendations: this is the polled mode POL option. In the Pushed mode, PUS option, the ancillary services are displayed but not taken into account in the determination of the lowest recommendations.
See "Error Messages" section.
This option allows to request a single ancillary service sub-code.
See "Error Messages" section.
This option allows to include or exclude one sub-code. Inclusion is the default mode, and can be omitted.
See "Error Messages" section.
This operation allows to specify for each service request if it should be processed in a pushed (informative mode) or polled mode (service amount taken into account in the determination of the lowest recommendations).
The default mode is the pushed mode PUS. It can be specified or not.
In the following example, the two first requests for service AAA and BBB are in polled mode.
Inclusion mode is the default mode. It can be specified or not.
Requests for CCC, DDD, EEE are all equivalent. PUS (default pushed mode) and IN (default inclusion mode) can be specified or not.
NOTE: the polled mode option is not yet available
See "Error Messages" section.
This option allows the process to match a service depending on its coverage applicability.
The service coverage option can be requested at Itinerary level (COI option). This is the default mode.
The service coverage option can be requested at Flight level (COF option).
The service coverage option can be requested at Bound level (COB option).
The service coverage option can be requested at Itinerary level or a sub-coverage of the itinerary (CIS option).
The service coverage option can be requested at Bound level or a sub-coverage of the bound (CIB option).
Each service request can be associated with a specific coverage option as shown below.
See "Error Messages" section.
This example shows how to combine coverage option and polled mode option at service level.
NOTE: the polled mode option is not yet available
See "Error Messages" section.
This example shows how to request an entire service group.
A group contains several sub-groups containing themselves several ancillary services.
See "Error Messages" section.
This example shows how to request a service sub-group.
See "Error Messages" section.
This request shows how to include UN group, exclude AS sub-group and include CCC sub-code.
See "Error Messages" section.
This option allows to request a specific service : seat characteristics in service group SA.
If not, the seat characteristic request is discarded.
See "Error Messages" section.
This example shows a complex request with all available options.
See "Error Messages" section.
The Include and Exclude options may be combined with any other option. Both the Include and Exclude options may be utilised in the same request. The Preferred option can be combined with any other option but the Preferred Connecting Point. And it cannot be specified at the same level (itinerary, same requested segment) as the Include/Exclude Airline options.
If a YY carrier code is used in the "Include" option at the same time as a specific Airline, then, this specific Airline can be proposed as Non-Stop or Direct flights and in connections with any other Airline.
If the "Exclude" option is utliised, the search process may propose any carrier except those carriers specified in the exclude parameter.
If "Include" option is combined with the "Exclude" option, the "Include" option must contain a YY carrier code for the processing of the Exclude option.
If not specified otherwise, no occurrence of an Exclude carrier as Non Stop, Direct and/or in any part of a connection is selected. In case of Joint Operation, both airline codes have to be checked. Marketing carrier and operating carrier will have to be checked.
Preferred Airline codes can be used to ensure that proposed segments considered by the system when building recommendations will include online solutions on those airlines. This option does not ensure that recommendations returned by Master Pricer will include such Proposed Segments as the objective is still to propose the lowest available recommendations.
Examples:
| Request | Process |
|---|---|
| Include: AF, BA | AF and BA as non-stop/direct flights and for connections AF and BA online and interline. |
| Include: TW, YY | TW mandatory: can be combined with any other airline. |
| Include: TW, YY Exclude: AA |
TW mandatory: can be combined with any other airline except AA. |
| Include: TW, CO, YY Exclude: AA |
TW or CO mandatory: can be combined with any other airline except AA. |
| Exclude: DL | Any carrier may be proposed, except DL airlines. |
If the same airline code appears twice within the same option the request is not rejected, rather the second occurrence of the airline code is automatically ignored.
The example below illustrates a low fare search including an optional Airline element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Mandatory carrier requested at itinerary level | M |
| AF Mandatory carrier | AF |
| Searching mandatory airline combination with all carriers | YY |
| 1st requested segment | 1 |
| Mandatory requirement on Trip Departure city of Paris | PAR |
| Mandatory requirement on Trip Arrival city of Miami | MIA |
| Trip Date (Dec 20, 2001) | 201203 |
| Recommendations for specific carrier exclusion | X |
| AA carrier to exclude | AA |
| 2nd requested segment | 2 |
| Departure city of Miami | MIA |
| Arrival city of New York | NYC |
| BA preferred carrier | BA |
| Trip Date 25th Dec, 2001 | 251203 |
The airline codes are a 2 alpha numeric character code that is defined in the Amadeus System. If the airline code specified is invalid, the entire entry will be rejected and the error "Invalid Airline Code" will be returned.
Verify the airline codes specified in the request and resend the request.
YY Airline Code Not Present in Combined Include Option
If the "Exclude" option is combined with the "Include" option and the YY code is not used as an include airline code, the entire entry is rejected with the following message:
"INVALID EXCLUDE AIRLINE OPTION"
Example:
| Request | Process |
|---|---|
| Include: TW, CO, AA Exclude: US |
Entry rejected. |
YY Airline Code in Exclude Option
If the YY code is used in the "Exclude" option, the entire entry is rejected with the following message:
"INVALID EXCLUDE AIRLINE OPTION"
If the same airline code is specified as "Include" and "Exclude", at the same request level, the entire entry is rejected with the following message:
"AIRLINE CANNOT BE AT THE SAME TIME INCLUDED AND EXCLUDED"
If an airline code is specified more than once, the entry is not rejected: the second occurrence is just ignored.
The following Flight Categories are supported:
The rules defined in Availability apply regarding the definition of the Change of Gauge (COG) flights:
This information is usually obtained from the User Office Profile settings. However, due to current information limitations, the change of gauge will be always considered as a connecting flight within this function.
Warning: High-speed trains are considered as non-stop, but when returned their stops are provided like technical stops.
A maximum of 3 flight categories per requested segment may be specified and maybe combined with any other option, excluding an include connection point with a Non-Stop flight category.
The example below illustrates a low fare search including an optional FlightCategory element specified with the following information. Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Non-Stop Flight Category request applicable for entire trip | N |
| Direct Flight Category request applicable for entire trip | D |
| Applicable on 1st segment | 1 |
| Trip departure city of Paris | PAR |
| Trip arrival city of Miami | MIA |
| Trip Date 20 Dec, 2001 | 201201 |
| Applicable on 2nd segment | 2 |
| Trip departure city of Miami | MIA |
| Trip arrival city of Paris | NYC |
| Trip Date 25January,2002 | 250102 |
| Direct Flight Category request | D |
If an unknown Flight Category is specified in the entry, the entirere quest is rejected and the following error message is returned:
"INVALID FLIGHT CATEGORY".
If an Include Connecting Point is specified at the same time as a Non-Stop FlightCategory option, the entire request is rejected and the following error message is returned:
"NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION".
Connection points must be segment specific. They may be combined with any other option, excluding the Non-Stop Flight Category - in which, an error message is not returned, but the connection point specified is ignored. Connecting Points to Include may be combined with the Connection Points to exclude, providing the same connection points are not used for both categories.
One additional specific combination restriction for preferred connection option: Preferred connecting point option can be combined with any other option except the "Non-Stop" Flight Category option and the preferred Airline option.
The connection points are 3 character IATA City or Airport codes. When an Include Connecting Point option is specified, all itineraries returned must at least go via this Connecting Point. When two Include Connecting Points are requested, proposed itineraries must at least go via both these Connecting Points in the order specified in the entry. The Change of Gauge and direct flights whose stops are in the requested point are not selected there.
Direct flights, Change of Gauge (COG) and Connections that have at least one stop at one of the exclude connect points are excluded. When two Excluded Connecting Points are specified, any itinerary going through one of those Connecting Points is excluded.
If an Exclude Connecting Point is specified at the same time as a Non-Stop Flight Category option, the system returns Non-Stop flights recommendations and ignores the Connecting Point requested.
If an airport code is specified as an Excluded connecting point, the alternate airports associated to the same city are candidates to the selection.
If a city code is specified as an Excluded connecting point, all Airports associated to that City are excluded.
When a preferred Connecting Point option is specified, the system will use it to build "Preferred" Proposed Segments. Those "Preferred" Proposed Segments will go via at least one of the Preferred Connecting Points requested. These preferred proposed segments will be considered by the system when building the recommendations (TheChange of Gauge and direct flights whose stops are in the requested point are not selected here.)
Preferred Connecting Point can be used to ensure that proposed segments considered by the system when building recommendations will include online solutions on those connecting point. This option does not ensure that recommendations returned by Master Pricer will include such Proposed Segments as the objective is still to propose the lowest available recommendations.
Examples:
| Parameter | Information |
|---|---|
| Include Connecting Point: MAD | Itineraries via, at least, MAD |
| Include Connecting Points: PAR, JFK | Itineraries via, at least, PAR and JFK in that order |
| Exclude Connecting Point: FRA | Exclude any Direct, COG and Connections via FRA |
| Include Connecting Point: NYC Exclude Connecting Point: JFK |
Itineraries via, at least, any Airport of NYC except JFK |
| Exclude Connecting Point: LON, ROM | Exclude any Direct, COG, Connections via FRA or ROM |
| Include Connecting Point: LON Exclude Connecting Point: SIN |
Itineraries via, at least, LON and Exclude Direct, Connections and COG that go through SIN |
| Include Connecting Point: JFK Exclude Connecting Point: NYC |
Entry rejected with the appropriate message |
| Include Connecting Point: FRA Type of Flight: Non-Stop |
Entry rejected with the appropriate message |
| Exclude Connecting Point: FRA Type of Flight: Non-Stop |
All Non-Stop from DUS to BER. In that case the Exclude connecting point is meaningless |
The example below illustrates a low fare search including an optional Connection Point element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| 1st requested segment | 1 |
| 1st Segment departure city PARIS | PAR |
| 1st Segment arrival city MIAMI | MIA |
| Trip Date (20 Dec, 2001) | 201201 |
| Exclusion indicator | X |
| Location for connection point exclusion | LGW |
| 2nd requested segment | 2 |
| 2nd Segment departure city PARIS | MIA |
| 2nd Segment arrival city MIAMI | PAR |
| Trip Date (20Jan, 2002) | 200102 |
| Inclusion indicator | X |
| Location for 1st connection point inclusion | NYC |
| Location for 2nd connection point exclusion | LON |
| Location for preferred connection point | JFK |
If the city or the airport code does not exist, the following error message is returned:
"INVALID CONNECTING POINT".
The error "SAME CITY/AIRPORT CODE CANNOT BE INCLUDED AND EXCLUDED" is returned in the following situations:
If an Include Connecting Point is specified at the same time as a Non-Stop Flight Category option, the entire request is rejected and the following error message is returned:
"NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION".
If no itinerary can be found then the entire itinerary is rejected with the message:
"NO ITINERARY FOUND FOR REQUESTED SEGMENT n"
where n is the number of the first Requested Segment that failed.
If a Preferred Connecting Point is specified at the same time as a Non-Stop Flight Category option, the entire request is rejected and the following error message is returned: "NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION".
If a Preferred Connecting Point option is specified at the same time as a preferred airline option, the entire query is rejected and the following error message is returned: "PREFERRED AND INCLUDE/EXCLUDE AIRLINE CANNOT BE MIXED"
This option may be combined with any other option except the Area option on the same Origin or Destination point of a Requested Segment.
Constraint: All Cities/Airports at each Origin and/or Destination must be in the same country.
When a Multi-city option is specified, search is extended to the whole list of Cities and Airports specified in the entry.
When the number of Airports is significant, preference is given at the Origin/Destination level of each Requested Segment - to the Cities/Airports according to the order specified by the End User. Cities or Airports specified too far in the list may be ignored. The number of airports to consider in such a case must be tuned to fit the quality objectives and the technical constraints.
When many airports must be considered for both end points of a requested segment,they must be all considered fairly in the search process, being equally considered in the flight research. No preference should be given to the variety of city at Origin, compared to the variety at destination, and vice versa.
Examples:
| Request | Process |
|---|---|
| Departure: WAS, BOS, NYC Arrival: LON |
Process in priority solutions: - Between WAS and LON, - Then BOS and LON, - Then NYC and LON.. |
| Departure: WAS, BOS, NYC Arrival: LON, BHX |
Process in priority solutions: - Between WAS and LON, - Then BOS and LON, - Then WAS and BHX, - Then BOS and BHX, - Then NYC and LON.. |
| 1st Requested Segment: Departure: WAS, BOS, NYCArrival: PAR, LIL 2nd Requested Segment: Departure: PAR Arrival: BOS, NYC |
Process in priority solutions: - WAS PAR/PAR BOS, - BOS PAR/PAR BOS, - WAS LIL/PAR BOS, - WAS PAR/PAR NYC, - BOS LIL/PAR BOS.. |
The example below illustrates a low fare search including an optional Multi City element specified with the following information:
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # Of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Applicable 1st segment | 1 |
| Multiple departure city 1 of Paris | PAR |
| Multiple departure city 2 of Lille | LIL |
| Multiple arrival city 1 of Miami | MIA |
| Multiple arrival city 2 of Fort Lauderdale | FLL |
| Trip Date 20Dec, 2001 | 201201 |
At each Origin/Destination level of each Requested Segments, all Cities and/or Airports must belong to the same country. If this check fails, the entire entry is rejected with the following error message:
"CITY/AIRPORTS MUST BE IN SAME COUNTRY".
A radius of search may be specified on any Origin and/or Destination point of each requested segment.
The units of measure for a radius search must be specified in kilometers. A maximum radius of 300 kilometers may be specified.
The Area of search is restricted to the Cities/Airports in the same country as the City/Airport of reference. Whenever the reference point of the area is an airport, all the airports of its city are considered in the request, as long as they are in the same country.
When an Origin/Destination Area option is specified, search is extended to all the Cities/Airports existing in the requested Area providing these Cities/Airports belong to the same country as the City/Airport of reference.
Examples:
| Type Of Request | Process With Example |
|---|---|
| FLL Fort Lauderdale (city) - No radius | Fort Lauderdale (any airport) |
| FLL Fort Lauderdale (city) - Radius: 150 km | Fort Lauderdale - Miami |
| FLL Fort Lauderdale (city) - Radius: 300 km | Fort Lauderdale - Miami - Orlando |
| LON London (city) - No radius | London (any airport) |
| LHR Heathrow (airport) - No radius | Heathrow airport |
| LHR Heathrow (airport) - Radius: 0 km | London (any airport) |
| LHR Heathrow (airport) - Radius: 5 km | Heathrow airport |
| EAP Basel Mulhouse (city) - No radius | Any airport attached to EAP in Switzerland (does not include MLH) |
| BSL Basel (airport) - No radius | Basel airport |
| EAP Basel Mulhouse (city) - Radius: 25 km | Any airport attached to EAP in Switzerland (does not include MLH) |
| BSL Basel (airport) - Radius: 0 km | Any airport attached to EAP in Switzerland (does not include MLH) |
| MLH Mulhouse (airport) - Radius: 0 km | Mulhouse in France (ignores BSL) |
Technical constraints may lead to a limited search. In such a case, preference is given to the cities of the area whose density is higher and that are closer to the city of reference.
To do so, a 2-step selection will be used, for technical reasons:
Since density and distance are repeated for each city pair, these values may be modified manually to handle specific cases where a city should not be selected, despite its high density, due to its relative inaccessibility. For example eliminate Bastia from a Nice + 300 Km request. The density of the city of reference is normally not considered, since the city of reference is normally always used. However, a manual modification of the density value should allow tuning for specific cases.
When many cities must be considered for both end points of a requested segment, both end point variety must be handled fairly in the search process: no preference should be given to the variety of cities at Origin, compared to the variety at destination, and vice versa.
Examples:
| Type Of Request | Process With Example |
|---|---|
| Departure: NCE and any Airport within a radius of 300 km (=> Considered city order: NCE, MRS, TLN, ..) Arrival: PAR |
Process in priority solutions: - between NCE and PAR, - then MRS and PAR, - then TLN and PAR,.. No Airport in Italy is considered. |
| Departure: NCE and any Airport within a radius of 300 km (=> Considered city order: NCE, MRS, TLN, ..) Arrival: TLS and any Airport within a radius of 300 km (=> Considered city order: TLS, BOD, MPL, ..) |
Process in priority solutions: - between NCE and TLS, - then MRS and TLS, - then NCE and BOD, - then NCE and MPL,.. No Airport in Italy or in Spain is considered. |
The example below illustrates a low fare search including an optional Origin/Destination Area element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Applicable 1st segment | 1 |
| Specified Search Radius of 150km | 150 |
| Specified units of measure for Kilometers | K |
| Target departure search city of Munich | MUC |
| Specified Search Radius of 100km | 100 |
| Specified units of measure for Kilometers | K |
| Target arrival search city of Newark | HOU |
| Trip Date 20Dec,2001 | 201201 |
| Identify Newark as an Airport | A |
| Applicable 2nd segment | 2 |
| Departure from New York | HOU |
| Identify NYC as a City code | C |
| Arrival in Munich | MUC |
| Trip Date 25January,2002 | 250102 |
If an Origin/Destination Area option and a Multi-city option are both specified at the same time on the same Origin or Destination point, the entire entry is rejected with the following error message:
"CONFLICTING MULTI-CITY OPTIONS".
The radius must be between 0 and 300km. If this check fails, the entire request is rejected with the following error message:
"INVALID RADIUS - MAXIMUM ALLOWED 300KM"
If the unit of measure is not specified or is specified as anything other than Kilometers (K), the entire query will be rejected and depending on whether the radius search was requested on the departure or arrival location one of the following applicable error message:
"INVALID VALUE - DEPARTURELOCALIZATION" or "INVALID VALUE - ARRIVALLOCALIZATION"
Slice and Dice process is applied by default. The End-User has the ability to disable slice and dice process with an option in the query.
When this option is requested, Slice and Dice is disabled in the availability request. As no extra availability is returned, no recommendation with Slice and Dice context will be returned.
The flight search is performed according to office settings by default. The End-User has the ability to disable biased preference display setting with an option in the query.
When this option is requested, the flight search request is performed in neutral mode independently of the office settings.
The End User has the possibility to have included in a traditional Master Pricer response message, Ticketless Access carriers recommendations or mixed of Ticketless Access Carriers and Full Service Carriers recommendations. It has the possibility via this option to exclude from the response Message TLA Recommendations.
The End-User has the ability to ignore the real availability for flight selection: all returned booking codes are considered as available.
A number of connections can be requested for Connecting flights category in such case the flights considered in the process are restricted to connecting flights with exactly the specified number of connections.
The example below illustrates a low fare search including an optional FlightCategory element specified with the following information. Query Requirements:
This option forces the process to return online travel solutions only for all requested segments, even if cheaper recommendations mixing carriers exist.
INVALID COMBINATION OF OPTION
Include option used with one or more specific airlines code: the process will only return online travel solutions of those specifics airlines).
When this option is only requested on one Requested Segment, there is no constraint on the other Requested Segments, meaning that interline solution may be returned for Requested Segments on which online option is not requested.
See "Error Messages" section.
The End-User has the ability to request only interline solutions in Master Pricer Travel Board i.e. recommendations built with flights marketed by different carriers.
See "Error Messages" section.
The end-user can define in input a Max Elapsed Flying Time to be returned. The Max EFT is a percentage (>100) of the shortest EFT returned by the journey server.
See "Error Messages" section.
The end user can request a max layover per connection (in hours and in minutes)
Each connection has a layover limited to X hours and Y minutes.
See "Error Messages" section.
The end user can request a max layover per requested segment (in hours)
If there are several connections for a requested segment, total layover can't be superior to X hours
See "Error Messages" section.
The Time option can be:
If no range of dates is requested, search for flights that depart between the requested time and 11:59PM. If a range of dates is requested, the TD applies on the first day of the range. The search for flights applies for the period between the TD on the first day of the range and 23h59 on the last day of the range like it is described in the figure below:
If no range of dates is requested, search for flights that arrive between 00:00AM and the requested time. If a range of dates is requested, search for flights that arrive on the last day of the date range before the requested time, or any time the previous day(s).
Examples:
| Request | Process |
|---|---|
| Date: 10SEP01 Time of Arrival: 10:00PM => Arrives by 10:00PM on the 10SEP01 | Select flights that arrive between 00:00AM and 10:00PM on the 10SEP01. |
| Date: 15OCT01 Time of Departure: 10:00PM => Depart from 10:00PM on the 15OCT01 | Select flights that arrive between 10:00PM and 11:59PM on the 15OCT01. |
| Range of dates: 23AUG01 and 24AUG01 Time of Departure: 06:00PM => Depart from 06:00PM on the 23AUG01 | Select flights that depart between 6:00PM and 11:59PM on the 23AUG01 or on the 24AUG01, at any time. |
| Range of dates: 23AUG01 and 24AUG01 Time of Arrival: 06:00PM => Arrive by 06:00PM on the 24AUG01 | Select flights that arrive between on 23AUG01 at any time or on 24AUG before 06:00PM. |
Refer to the paragraph for the Departure/Arrival time handling when both options are combined.
The example below illustrates a low fare search including the Times by Arrival and Departure elements specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Applicable 1st segment | 1 |
| Departure city of Paris | PAR |
| Arrival city of Miami | MIA |
| Identify search for departure by element | TD |
| Specify date for departure by 23Aug2001 | 230801 |
| Specify search time for departure by 6pm | 1800 |
The error message "INVALID TIME OPTION" is returned in the following instances:
Valid time range values range between 1 and 12.
The TimeWindow applies either on the Time of Departure or the Time of Arrivalto restrict the search on the flights in the range of hours around (+and -) the requested date and time.
When requested on a unique departure/arrival date, the time window may overlap to the previous/next day to fulfill the request.
Whenrequested on a range of dates, the time window is interpreted on eachday of the date range. Consequently, the time window may not extend therequested date range.
Note: The Time of Departure/Arrival option with a specified date is mandatory when using this option.
Examples:
| Request | Process |
|---|---|
| Date: 20AUG01 Time of Arrival: 10:00PM Time Window: 4 hours => Arrive around 10:00 PM on the 20AUG01 | Select flights that arrive between 20AUG01 6:00PM and 21AUG01 02:00AM |
| Rangeof dates: 20SEP01 and 21SEP01 Time of Departure: 10:00AM Time Window: 5hours => Depart around 10:00AM on the 20SEP01 or on the 21SEP01 | Select flights that depart between 05:00 AM and 03:00 PM on each requested day, i.e. on 20SEP01 and on 21SEP01. |
| Rangeof dates: 23AUG01 and 24AUG01 Time of Arrival: 10:00PM Time Window: 4hours => Arrive around 10:00PM on the 23AUG01 or on the 24AUG01 | Select flights that arrive on 23AUG01 or on 24AUG01: between 6:00PM 23AUG01 and 02:00 AM on the 24AUG01 or between 6:00PM and 11:59PM on the 24AUG01 NB: Flights between 00:00 AM and 02:00AM on the 23AUG01 are not considered. |
| Rangeof dates: 23AUG01 and 24AUG01 Time of Departure: 02:00AM Time Window: 4hours => Depart around 02:00AM on the 23AUG01 or on the 24AUG01 | Select flights that depart on 23AUG01 or on 24AUG01: between 00:00AM and 06:00AM on 23AUG01 or between 10:00PM on 23AUG01 and 06:00 AM on 24AUG01 NB: Flights between 10:00PM and 11:59PM on the 24AUG01 are not considered. |
Theexample below illustrates a low fare search including the Times byArrival and Departure elements specified with an optional time Windowelement with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passengerv1 | |
| Applicable 1st segment | 1 |
| Departure city of Paris | PAR |
| Arrival city of Miami | MIA |
| Identify time by arrival elementvTA | |
| Specify arrival date by 23AUG01 | 230801 |
| Specify arrival time by 10pm | 2200 |
| Specify applicable time window 4hours either side of 10pm | 4 |
| Identify date range search for Plus | P |
| Number of days in date range search | 1 |
Note: Achieving the same results, the time Window could also be specified as:
| Specify arrival date by 24AUG01 | 240801 |
| Specify arrival time by 10pm | 2200 |
| Specify applicable time window 4hours either side of 10pm | 4 |
| Identify date range search for Minus | M |
| Number of days in date range search | 1 |
The time window value varies from 1 to 12 hours. If this check fails, the entire entry is rejected with the following message:
"INVALID TIME WINDOW OPTION"
If no Time of Departure/Arrival is specified, the entire request is rejected with the following error message:
"TIME OF DEPARTURE/ARRIVAL IS MANDATORY IF TIME WINDOW REQUESTED".
If no date is specified, the entire request is rejected with the following error message:
"DATE IS MANDATORY".
When a Range of plus and/or minus one Day is specified on a Requested Segment, search of flights applies on a Range of Dates of up to three days - the current day plus and/or minus 1 day. Search is only allowed on a Range of up to three days:
In the search, no preference is given to any of the dates. The only preference factor will be the price and the carrier variety. A good distribution and variety of recommendations is expected on the different days of the range.
The example below illustrates a low fare search including the optional Range of Dates element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Applicable 1st Segment | 1 |
| Departure City Marseille | MRS |
| Arrival City Houston | HOU |
| Departure date 02Feb2002 | 200202 |
| Identify date range search as Plus range | P |
| Number of days in range | 1 |
| Applicable 2nd segment | 2 |
| Force departure city same as arrival city in 1st segment reference | 1 |
| Identify city of Houston for departure city | HOU |
| Identify arrival city of Marseille | MRS |
| Arrival date 22Mar2002 | 220302 |
| Identify date range search as Minus | M |
| Number of days in range | 1 |
Search is only allowed on a Range of two days: i.e. the requested Date plus or minus one day. If a plus or minus more than one day option is specified or if a plus and minus one day option is specified, the entire entry is rejected with the following error message:
"INVALID RANGE OF DATES OPTION".
The currency conversion option may be combined with any other option.
It is mandatory that the ticketing price type be set to "CUC" to indicate a currency conversion request. It is mandatory for any query including the currency conversion option.
It is mandatory that a currency code be specified for the conversion. All price amounts for recommendations are converted in the requested Currency. There is no default currency for conversion, it must be specified.
The example below illustrates a low fare search including an optional Currency Conversion element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Ticketing / Price type of Currency Override | CUC |
| Currency Requested for recommendations is Euros (Note: This field is mandatory when requesting a currency conversion) | EURO |
| Applicable 1st trip segment | 1 |
| Trip departure city of Paris | PAR |
| Trip arrival city of Miami | MIA |
| Trip date 20January, 2002 | 200102 |
Invalid Currency Conversion
If an unknown Currency is specified, the entire request is rejected and the following error message is returned:
"INVALID CONVERSION CURRENCY".
Currency must be specified
If the ticketing price type is set to currency conversion (CUC), yet a currency code is not specified for the conversion, the entire query is rejected with the following error:
"CURRENCY MUST BE SPECIFIED"
Invalid Value - ConversionRate
If a currency code for conversion is specified, yet the ticketing price type has not be set for the currency conversion (CUC), the entire query is rejected with the following error message:
"INVALID VALUE - CONVERSION RATE"
The requested Selling and/or a Ticketing Cities are used to determine applicable fares and currency for the recommendations. The selling and ticketing cities are applied from the requestor's system office ID city settings. If the selling or ticketing city override option is used, the cities specified will be utilized instead of the requestor Office-id City.
The city code specified must be a valid city code stored in the Amadeus System. Airport codes may not be utilized, unless the airport and city code are the same.
Examples:
| Valid city code for Paris | PAR |
| Invalid city code to use for Paris | CDG |
A maximum of one selling and one ticketing city may be specified applicable to the entire request. These options may be combined together and/or with any other option.
The example below illustrates a low fare search including the optional selling/ticketing cities override element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Selling city override location set to Paris | PAR |
| Ticketing city override location set to Munich | PAR |
| Applicable 1st segment | 1 |
| Departure city of Marseille | MRS |
| Arrival city of Miami | MIA |
| Trip Date 20Dec,2001 | 201201 |
Invalid Ticketing/Selling City
If the requested Selling or Ticketing city are not a valid city code in the Amadeus System, the entire request is rejected and the following message is returned:
"INVALID TICKETING/SELLING CITY"
This option may be combined with any other option.
The Price to Beat amount can be composed of up to 9 digits, and the value must be higher than zero. No decimal placement is allowed in the input.
The currency of the Price to Beat is the requested Currency of Conversion if specified; otherwise, it is the default selling currency that is determined as per usual pricing rules.
If no Price to Beat is specified, all prices will be considered valid as a qualifying recommendation.
The example below illustrates a low fare search including the optional Price to Beat element specified with the following information:
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Specified price to beat | 3500 |
| Applicable 1st segment | 1 |
| Departure city of Paris | PAR |
| Arrival city of Miami | MIA |
| Trip Date 20Dec,2001 | 201201 |
If the Price to Beat amount is composed of more than 9 digits, the value is not higher than zero, or a decimal placement is included in the input, the entire request is rejected and the following error message is returned:
"INVALID PRICE TO BEAT VALUE"
The Price to Beat is used as a reference. No recommendation that is returned to the End-User may have an higher price. If no lower price recommendation is found, the following error message is returned:
"NO RECOMMENDATION FOUND WITH LOWER OR EQUAL PRICE".
When a customer uses PoweredLowestFare to request fares for several passengers, these passengers may have different Passenger Type Codes (i.e. for example 1 ZZ and 1 CH). If the No Split PNR option is deactivated, the system will return the cheapest recommendations even if different booking codes have to be applied to these passengers (non homogenous solutions). This implies to create multiple PNR to finalize the booking.
The default process is the "No Split PNR mode": Fare Search returns recommendations where the same booking code is applied to all passengers (homogenous solutions).
Here is the syntax to deactivate the No Split PNR option
| Fee Type | NPS |
| FeeIdNumber | 0 |
The example below illustrates a low fare search including the de activation of the No-Split PNR option
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 2 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Adult Passenger type code | CH |
| Passenger type code applicable to 1st passenger | 2 |
| Fee Type | NPS |
| Split PNR Option activated | 0 |
| 1st requested segment | 1 |
| Trip Departure city of Paris | PAR |
| Trip Arrival city of Miami | MIA |
| Itinerary Date 02 December, 2002 | 120202 |
Not applicable.
The paper and electronic ticket surcharge concept is driven from fare data filed by the airline.
Three new pricing options are available to allow the End User to link the fare priced and the type of Fare required.
'/PT' FOR PAPER TICKET
'/ET' FOR ELETRONIC TICKET
'/EP' FOR ELECTRONIC AND PAPER TICKET
Note: that Electronic Ticketing (ET) is not yet available in all markets orall carriers, for further details contact your local Amadeus Help Deskfor more information, to ensure that the Office Profile has beenmodified accordingly and the market where the airlines are situated canbenefit from Electronic Ticketing (ET).
Examples:
| Request | Process |
|---|---|
| If no options are entered | System will propose both Electronic and Paper Ticket travel solutions |
| Request Electronic Ticket (ET)only | Electronic Ticket sent |
| Request PaperTicket (PT)only | Paper Ticket sent |
The example below illustrates a low fare search for Electronic Ticket solutions only.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Identify Published fares Price type search | ET |
| Identify Corporate Unifares type search | RU |
| Identify the corporate number as Corporate Unifares | RZ |
| Associated corporate number to Corporate Unifares | 012345 |
| Applicable 1st segment | 1 |
| Departure city of Paris | PAR |
| Arrival city of Miami | MIA |
| Trip Date 20Dec,2001 | 201201 |
The time window value varies from 1 to 12 hours. If this check fails, the entire entry is rejected with the following message:
"INVALID TIME WINDOW OPTION"
If no Time of Departure/Arrival is specified, the entire request is rejected with the following error message:
"TIME OF DEPARTURE/ARRIVAL IS MANDATORY IF TIME WINDOW REQUESTED".
If no date is specified, the entire request is rejected with the following error message:
"DATE IS MANDATORY".
If the specific types of fares are not requested, only the public fares will be searched.
This option may be combined with any other option.
The following Unifares options are supported:
Thesefare type searches may be combined, with the exception of Unifares (RU)or Corporate Unifares (RW) with an Amadeus Nego (RN) or Amadeus NegoCorporate (RC) in the same entry.
An associated corporate number must be specified for Corporate Unifares or Amadeus Nego Corporate requests.
Note: The search is restricted to one corporateid (Corporate identity) Value.
The example below illustrates a low fare search including the optional Unifares element with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum number of recommendations to be returned | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Identify Published fares Price type search | RP |
| Identify Corporate Unifares type search | RU |
| Identify the corporate number as Corporate Unifares | RZ |
| Associated corporate number to Corporate Unifares | 012345 |
| Applicable 1st segment | 1 |
| Departure city of Paris | PAR |
| Arrival city of Miami | MIA |
| Trip Date 20Dec,2001 | 201201 |
If a valid corporate type is not specified (RW or RC) or if the corporate number specified is not matching the corporate type requested (RW or RC), then the entire query isrejected with the following error message
"INVALID VALUE - CORPORATE"
If a corporate type (RC or RW) has been specified, yet no associated corporate number isincluded in the query, the entire query is rejected with the following error:
"CORPORATE NUMBER MUST BE SPECIFIED"
Unifares and Amadeus Nego/Corporate options are not combinable. If this check fails, the entire request is rejected and the following message is returned:
"CONFLICTING OPTIONS USED"
The fare type - expanded parameter option may be combined with any other option. With the exception that the No Restriction parameter (NR) may not be combined with any other expanded parameter.
The following fare type - Expanded Parameters are supported:
Search for low fares having no advance purchase.
Search for low fares having no penalty.
Search for low fares having no restrictions.
Search for low fares that may be refundable.
A maximum of 3 expanded parameter may be requested.
The example below illustrates a low fare search including an optional Expanded Parameter element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Expanded Parameter type for Refundable fares | RF |
| Applicable 1st segment | 1 |
| Trip departure city Marseille | MRS |
| Trip arrival city Miami | MIA |
| Trip Date 20January, 2002 | 200102 |
The only valid expanded parameter options applicable are NAP, NPE, NR and RF. If an unknown Expanded Parameter is specified in the entry, the entire request is rejected and the following error message is returned:
"INVALID VALUE - PRICING/TICK INFO".
It is not possible to combine the No Restriction (NR) Expanded Parameter with anyother Expanded Parameter. If this check fails, the entire request is rejected and the following error message is returned:
"CONFLICTING OPTIONS USED".
A Parameterized Fare Family is a set of specific parameters defined at input time in the search query, Up to 6 Parameterized Fare Families can be defined in the input. These parameterized fare families are inputted as options, relying on a set of criteria and attributes used to match recommendations to Fare Families.
The parameterized Fare Family can be combined with any other option. It is the responsibility of the user to ensure that combination of Fare Families parameters and other query options does not affect the functional coherence of the request.
Structure of parameterised Fare Family:
The search option offers the possibility to the end user to include up to 6 Fare families in the query.
Each fare family is defined by up to 10 sets of attributes linked logically by OR.
Within each set, attributes are logically linked by AND.
Within each attribute, values are logically linked by OR.
Each set is composed of the following attributes:
| Attributes | Format | Mandatory(M)/ Optional(O) | Occurences |
|---|---|---|---|
| Fare Family Short name (Mandatory) | 1-10 Alphanumeric | M | 1 |
| Ranking | 1-4 digits | M | 1 |
| Combinability |
|
O | 1 |
| Publishing Carrier | 2 Alphanumeric | O | 0-10 |
| Type of Fare |
|
O | 0-5 |
| Prime Booking Code | 2 alpha | O | 0-10 |
| Fare Basis | 1-9 characters (0 to 9, A to Z, -) | O | 0-10 |
| Corporate Information |
CORP / NONCORP or CORPORATE CODE CORPORATE NAME |
O O |
0-6 0-6 (Sum of CORP CODE + CORPNAME <= 6) |
| Cabin |
|
O | 0-5 |
| Expanded Parameter - Advance Purchase |
|
O | 0-2 |
| Expanded Parameter - Refundability |
|
O | 0-2 |
| Expanded Parameter - Penalty |
|
O | 0-2 |
| Expanded Parameter - Restriction |
|
O | 0-2 |
When publishing carrier criteria is used, the include airline option should also be requested in the query to target the expected flights.
There is therefore up to 10 sets of criteria for each Parameterized Fare Family and this set of criteria may not be coded negatively.
The example below illustrates a Powered Lowest Fare request including 6 parameterized fare families defined by many attributes sets, each attribute has many occurrences:
1st Parameterized fare family:
2nd Parameterized fare family:
3rd Parameterized fare family:
4th Parameterized fare family:
5th Parameterized fare family:
6th Parameterized fare family:
The following table describes the Parameterized Fare Family XML fields:
| PoweredLowestFare_Search - Data element | Description |
|---|---|
| fareFamilies/ familyInformation | Fare Family information |
| fareFamilies/ familyInformation /fareFamilyname | Fare Family Short Name |
| fareFamilies/ familyInformation /hierarchy | Fare Family Ranking |
| fareFamilies/familyCriteria/fareFamilyInfo/fareFamilyQual | Fare Family Combinability (currently "NCO" if not combinable or no field if combinable) |
| fareFamilies/familyCriteria | 1st Matching attributes Set information |
| fareFamilies/familyCriteria/carrierId | Fare Publishing carrier |
| fareFamilies/familyCriteria/rdb | Type of Fare |
| fareFamilies/familyCriteria/fareProductDetail/fareBasis | Fare Basis |
| fareFamilies/familyCriteria/fareProductDetail/fareType | Prime Booking Code |
| fareFamilies/familyCriteria/corporateInfo/corporateNumberIdentifier | CORP or NONCORP |
| fareFamilies/familyCriteria/fareProductDetail/cabinProduct/cabinDesignator | cabin |
| fareFamilies/familyCriteria/fareProductDetail/cabinProduct/otherCriteria/name | EXP |
| fareFamilies/familyCriteria/fareProductDetail/cabinProduct/otherCriteria/type | Expanded Parameter value |
| fareFamilies/otherPossibleCriteria/logicalLink /booleanExpression/codeOperator | Addition of an attribute set within the same fare family set using the OR logic operator |
| fareFamilies/otherPossibleCriteria/logicalLink /booleanExpression/codeOperator/familyCriteria | 2nd Matching attributes Set information |
| etc | etc |
In addition to the standard possible errors checks, the following ones are performed:
If more than 6 Parameterised Fare Families are specified, the entry is rejected with the following message:
"PFF - Too many fare families".
If for a parameterised far family, more than 10 matching attributes sets are specified, the entry is rejected with the following message:
"PFF - Too many matching attributes sets requested"
If for any attribute within any set defined in the query, more occurrences than the ones defined in the table below are requested, the entry is rejected with the following message:
"PFF - Too many attribute occurences requested"
If at least one of the specified Fare Families names is invalid, the whole entry is rejected with the message:
"PFF - Invalid Fare Family name requested".
If at least one of the specified publishing carriers is invalid, the whole entry is rejected with the message:
"PFF - Invalid carrier requested".
If the specified type of fare is invalid, the whole entry is rejected with the message:
"PFF - Invalid Type of Fare Requested".
If the Fare Family Combinability is different than "Not Combinable", the whole entry is rejected with the message:
"PFF - Invalid Fare Family Combinability Requested".
If the specified publishing carrier is invalid, the whole entry is rejected with the message:
"PFF - Invalid Carrier Requested".
If the requested Fare Basis contains more than one dash (-), the whole entry is rejected with the message:
"PFF - Invalid Generic Fare Basis requested".
If the requested Prime Booking code is invalid, the whole entry is rejected with the message:
"PFF - Invalid Generic Fare Basis requested".
See also the "Error Messages" section.
The End User has the ability to specify up to 19 Office ids in addition to the Originator Office id of the ORG segment, within the same country and with the same modifier type. The system will then find the cheapest travel solutions amongst all office ids requested in input (originator office id and additional office ids) without any preference.
For each additional office id, if one or several of these attributes exist:
Then, the process for the additional office id will be the same as today for a mono office id query, when these attributes are specified in the ORG segment for the originator office id.
If one of these attributes is missing for the office id requested, we don't use for this office id the attributes of the Originator office id from the ORG segment. For this requested office id, the process will be the same as today for a mono office id query, in case of this same attribute would have been missing in the ORG.
Limitations
- Multi Office Id Search can be done on a maximun number of 3 requested segments.
- A recommendation is sold for a given office id only at itinerary level. It is not possible to have one office id for outbound and another one for the inbound in a Round Trip recommendation.
- In case one of the following options is requested in addition to the Multi office id option: the Multi TPax option, the Split PNR option or the Multi Passenger Same Booking code options, then for each solution, the same Office id is used for all passengers
- In case the Multi Ticket option is requested in addition to the Multi office id option, then the search is done to find the cheapest solution that requires one single pricing transaction or individual pricing transactions per Proposed Segment to be booked, on one office id.
- Multi office id option cannot be combined with Parameterized Fare Family option (My Search) and Airline Ticketing Fees (OB fees)
- All office ids in the query (originator and additional) must fulfil all the following conditions:
- If one office id is requested several times, then the entire entry is rejected with the following message:
OFFICE IDs MUST BE REQUESTED ONLY ONCE
- if all agent set locations must be in the same country, then the entire entry is rejected with the following message:
OFFICE IDs MUST BE IN THE SAME COUNTRY
- If all office IDs have not the same modifier type, i.e. either Travel Agent (modifier 2 or 3) or Airlines (0 or 1), then the entire entry is rejected with the following message:
OFFICE IDs MUST HAVE SAME MODIFIER TYPE
- If the modifier type value of one additional office id is not 0, 1, 2 or 3, then the entire entry is rejected with the following message:
INVALID OFFICE ID:
where l is indexes of office ids with an invalid format in the list of office ids requested in input.
- If the number of office ids requested is greater than the maximum authorized, then the entire entry is rejected with the following message:
TOO MANY OFFICE IDs REQUESTED
- If one added office id format is not valid, then the entire entry is rejected with the following message:
INVALID OFFICE ID:
where l is indexes of office ids with an invalid format in the list of office ids requested in input.
- If the originator office id is not authorised to request one or several additional office ids specified in the query, the entire entry is rejected with the following message:
OID(S) NOT AUTHORISED: n
where n is indexes of office ids not authorised in the list of office ids requested in input.
- If for one additional office id, the originator type code is requested in input, then the entire entry is rejected with the following message:
ORIGINATOR TYPE CODE NOT AUTHORIZED IN INPUT FOR ADDITIONAL OFFICE IDS
- If for one additional office id, no identification information is defined, then the entire entry is rejected with the following message:
OID(S) NOT IDENTIFIED: m
where m is indexes of the requested office ids for which identification information is missing.
- If Multi Office Ids is requested with Parameterized Fare Family option (My Search), then the entire request is rejected with the following message:
"Conflicting options used".
- If Multi Office Ids is requested with a complex itinerary (more than 3 requested segments), then the entire request is rejected with the following message:
"OPTION NOT PERMITTED WITH COMPLEX ITINERARIES".
The End User has the ability to request an even distribution of the recommendations among the office ids.
The recommendations are evenly distributed among the requested office ids (including the originator office id). For each recommendation, the list of office ids for which the recommendation is applicable is returned.
The same number of recommendations is allocated to each office id on which the search is performed (originator or additional office ids). So the targeted number of recommendations to build for each office id is:
Targeted Recommendations = (Nb requested Recommendations/(Nb additional office Ids + 1))
Note: If the requested number of recommendations is not reached because of rounding, the remaining recommendations are evenly spread over the other offices ids, in the order of the request (the originator office id being the first).
The transaction returns the cheapest recommendations for each office id. If the same recommendation can be sold by several office ids, it is counted as one recommendation for each office id. As in standard mode, only the cheapest recommendation is returned for one journey.
As soon as the targeted number of recommendations for one office id is reached, this office id is no more considered for the search of the cheapest recommendations. But if a recommendation is found for another office id and is also applicable for this office, then the recommendation is marked as applicable for both offices. As a consequence, more recommendations than the number requested can be returned in output.
Limitations
- No recommendation based on a public fare (or a combination of public fares only) is returned for the additional offices ids.
- As the recommendations are distributed among the offices ids, the Majority Carrier and Time of departure diversity are not applied.
- Cannot be combined with Weighted Distribution, Airline Distribution and Airline Distribution Container options.
- If this option is requested in another product than Master Pricer Travel Board, the entire entry is rejected with the following message:
INVALID OPTION
- If this option is requested with any option it can't be combined with, then the entire request is rejected with the following message:
"CONFLICTING OPTIONS USED".
The End User has the ability to request for each office id, a fraction of the total number of recommendations by specifying a weight.
The recommendations are distributed among the requested office ids (including the originator office id) according to the weight required.
If a weight is requested for an office id, the targeted number of recommendations for this office id is:
Targeted Recommendations = (requested nb recommendations*(weigth/SUM(weigth))
If no weight is requested for an office id, no recommendations are returned for this office id.
Note: The number of recommendations calculated should be rounded down. The missing number of requested recommendations is then evenly distributed to the other office ids in the order of the request (the originator office id being the first).
The transaction returns the cheapest recommendations for each office id. If the same recommendation can be sold by several office ids, it is counted as one recommendation for each office id. As in standard mode, only the cheapest recommendation is returned for one journey.
As soon as the targeted number of recommendations for one office id is reached, this office id is no more considered for the search of the cheapest recommendations. But if a recommendation is found for another office id and is also applicable for this office, then the recommendation is marked as applicable for both offices. As a consequence, more recommendations than the number requested can be returned in output.
Limitations
- As for the even distribution option, recommendations based on a combination of public fares only are not returned for the additional office ids.
- This option cannot be combined with Even Distribution, Airline Distribution and Airline Distribution Container options.
- The Majority Carrier and Time of Departure diversity is not applied when a weight is requested for at least one office id.
- If this option is requested with any option it can't be combined with, then the entire request is rejected with the following message:
"CONFLICTING OPTIONS USED".
- If a weight is requested without the ODW keyword, the entire entry is rejected with the following message:
"INVALID OPTION"
- If all weights are either undefined or equal to zero, then the entire request is rejected with the following message:
WEIGHTS SHOULD BE REQUESTED
The purpose of this option is to return separately in the output the total amount of YQ/YR taxes per recommendation and per passenger type. This includes the fuel surcharge and whatever other surcharge/tax there might be.
There is no way to specifically identify the fuel surcharge among the YQ/YR surcharges.
As YQ/YQ are mainly filed for Fuel surcharge application purposes and as they must be displayed separately from the other taxes for legal reasons in some countries (e.g. US), this option allows to get those amounts in output. This option does not have any effect on other returned amounts.
Contrary to FlexPricer Interface, this option is not triggered by a specific option in the Query structure, but rather controlled by a dedicated parameter in the office profile.
These conditional information is then returned depending on an office setting done via FS parameter.
The process returns strictly recommendations with the requested passenger type, no defaulting is done.
The End User may specify the Distribution Ratio to be used to compute the targeted number of recommendations for each fare family processed in the request. This option is to be used in the case the default even distribution of recommendations over Fare Families is not expected.
It means that 50% of recommendations could be returned for Fare Family 1, 30% for Fare Family 2 and 20% for Fare Family 3.
The association of Distribution Ratio to each Fare Family considered by the distribution process[1] is made by considering the list of Distribution Ratio in input order and the list of Fare Families from the most restrictive to the less restrictive (i.e. in ranking decreasing order). First Distribution Ratio being associated to the most restrictive Fare Family, second Ratio to second Fare Family and so on.
In case there is less Distribution Ratio than Fare Family, 0 Ratio is associated remaining Fare Families with no corresponding Ratio, meaning that no recommendation will be returned for those Fare Families. Fares from such Fare Family may still be combined with fares from other Fare Families to provide recommendations in other Fare Families.
In case there is more Distribution Ratio than Fare Family, Ratio not linked to any Fare Family will not be considered.
As a reminder only up to 6 Fare Families can be considered in one request, the selection is made on Fare Families linked to at least one valid fare, and in case more than 6 Fare Families exist, only the 6 most restrictive ones are kept.
The example below illustrates a query including a Distribution Ratio element specified with the following information:
Query Requirements:
| RequestingDetails | Specified Data |
|---|---|
| Fare Family | FF1,FF2 |
| Distribution Ratios: 120,100,0,1,50 | 100,50 |
| 1st requested segment | 1 |
| 1st Segment departure city | LON |
| 1st Segment arrival city | NIC |
| Date | August, 14 2010 |
Invalid Ratio Format
The Distribution Ratios are a 2-digit or a 3-digit numeric. If the ratio is not a 2 or 3-digit ratio, the entire entry will be rejected. Verify the ratios sent in the request are in the correct format. More importantly, 1-digit ratios are not accepted by the system, therefore, ensure that no 1-digits ratios are included in the requests. An alternative to this issue is to add a 0 on the left side of each 1-digit ratio when they are requested. i.e. requesting 05 instead of 5.
Example:
| Ratios Format | Accepted/Rejected |
|---|---|
| DR: 150,0,20,60,5 | Rejected because 0 and 5 are 1-digit numeric. |
| DR: 150,00,20,60,05 | Accepted because all ratios are 2 or 3-digits numeric. |
Invalid - 6 Distribution Ratio Maximum
If more than 6 Distribution Ratios are listed in the DR option, the entire entry is rejected with the following message:
"TOO MANY DISTRIBUTION RATIOS REQUESTED"
With this option, the Fare Family notion is applied at requested segment level. System returns recommendations distributed over combinations of Fare Families per Requested Segment.
For each recommendation, a resulting Fare Family is determined for each Requested Segment and for any combination of Fare Family for outbound and Fare Family for inbound available recommendations are returned. A same number of recommendations for each combination of Fare Family is returned if available.
The same number of recommendations for all combinations of inbound and outbound Fare Families is targeted. In case a combination is not fully filled-in, more recommendations than targeted can be returned for the other Fare Families combinations. Targeted number of recommendations per combination of Fare Families is determined by the formula: Number of Recommendations requested divided by the number of possible combinations of Fare Families. If a Fare Family is defined as non-combinable, there is only one possible type of solution involving it: when this Fare Family is used both on outbound and on inbound.
for example, if 3 Fare Families FF1, FF2 and FF3 are defined, the following combination must be considered:
For each of those 9 fare family combinations, the process must try to return 200/9 = about 22-23 recommendations.
The example below shows a query with 2 Fare Families FF1 and FF2 and 2 requested segments.
- If the Parameterized Fare Family option is not requested, the whole entry is rejected with the message:
PARAMETERIZED FARE FAMILY OPTION MISSING
- If the number of requested segments is superior or equal to three, the whole entry is rejected with the message:
TOO many requested segments
This option is the same as the Distribution Ratio of recommendations per Fare Family one except that the ratios apply to the Fare Family combinations per Requested Segment.
In the query, the user provides a list of distribution ratio (2 or 3 digits numeric value).
The association of Distribution Ratio to each Fare Family combination considered by the distribution process is made by a list of items. Each item is composed of a Fare Family combination and its associated ratio. There are as many items as Fare Family combinations wanted to appear in the output recommendations. The order in which the Distribution Ratios are associated to Fare Family combinations has no importance.
Fare Family combinations that are not linked to a ratio will not appear in the output recommendations.
The value 0 is accepted for a ratio. It is the same as not defining the ratio at all.
If a Distribution Ratio associated to the same Fare Family combination is defined several times, only the last occurrence is considered.
Inside a Distribution Ratio item, Fare Families and Requested Segments are referred by their reference number.
For each Fare Family combination, the targeted number of recommendations is lower or equal to: ri,j * N where:
ri,j = Ri,j / (sum of Ri,j linked to Fare Family combinations considered in distribution process) where Ri,j represents the Distribution Ratio associated to Fare Family i combined with Fare Family j and N is the requested number of recommendations.
This option is not combinable with the distribution ratio of recommendations per Fare Family one.
In the example below,
Ratio of weight 10 associated with the combination First Fare Family (requested segment 1) + First Fare Family (requested segment 2)
Ratio of weight 20 associated with the combination First Fare Family (requested segment 1) + Second Fare Family (requested segment 2)
If the Parameterized Fare Family option is not requested, the whole entry is rejected with the message:
PARAMETERIZED FARE FAMILY OPTION MISSING
If at least one of the ratios requested in the input is not a two or three-digit numeric value, the entire entry is rejected and the following error message is returned:
INVALID RATIO FORMAT
If at least one ratio is associated to a non-existing Fare Family at Itinerary or Segment level, the entire entry is rejected with the message
REFERENCE TO NON-EXISTING FARE FAMILY
If in at least one reference to a Fare Family is missing, the entire entry is rejected with the message:
"REFERENCE TO FARE FAMILY MISSING"
Checks when the option is used at Requested Segment level:
If in at least one reference to a Requested Segment is missing, the entire entry is rejected with the message:
"REFERENCE TO REQUESTED SEGMENT MISSING"
If inside at least one combination, the references to the Requested Segments do not start to 1 or are not incremented at each segment, the entire entry is rejected with the message:
"REQUESTED SEGMENT DEFINITIONS NOT IN ORDER IN DISTRIBUTION RATIO"
If inside at least one combination, the number of references to Requested Segments is not equal to the number of Requested Segments, the entire entry is rejected with the message:
"INVALID NUMBER OF REF SEGMENTS"
Checks when the option is used at Itinerary level:
If inside at least one Distribution Ratio item, there is not exactly one reference to a Fare Family, the entire entry is rejected with the message:
"INVALID NUMBER OF REF SEGMENTS"
If in at least one Distribution Ratio item a reference to a Requested Segment is present, the entire entry is rejected with the message:
"REFERENCE TO REQUESTED SEGMENT IMPOSSIBLE AT ITINERARY LEVEL"
It is possible to use the distribution ratio per Fare Family at requested segment level to define a distribution ratio per Fare Family (i.e. at itinerary level). To do so, the FFS flag is not set. In that case, only one Fare Family per ITM group is defined: the resulting Fare Family at Itinerary level.
In the example below, a ratio of weight 20 associated with the First Fare Family and ratio of weight 10 associated with the Second Fare Family.
This option allows the End User to request that only those fares that are filed in the currency specified in the input should be returned. Fares filed in any other currency will not be returned in recommendations.
This option can be combined with any other option except Multi-Ticket.
If an unknown currency is specified, then the entire request is rejected and the following error message is returned:
VERIFY CURRENCY OPTION'.
When Currency of Fare Selection option is combined with Currency Conversion (currency of sale) option, the PTK segment should contains CUC (currency of sale indicator).
Also, in the CVR segment, the currency code should be set in first position (without any qualifier). This will indicate the currency of sale.
then, the currency code should be set in second position, proceeded by the qualifier (Currency of Fare Selection).
If the PTK segment contains CUC (Currency Conversion indicator) but the CVR segment only contains the qualifier CFS, followed by a currency, the entire request is rejected and the following error message is returned:
Currency required
If the PTK segment is present but does not contain CUC and if the CVR segment contains a first currency, then the qualifier CFS, followed by a second currency, then, the entire request is rejected and the following error message is returned:
Bad value (coded) - conversionRate/fareSelc
If the PTK segment is present but does not contain CUC and if the CVR segment contains 2 currencies but without the qualifier CFS, then, the entire request is rejected and the following error message is returned:
Bad value (coded) - conversionRate/fareSelc
If the PTK segment contains CUC and if the CVR segment contains 2 currencies but without the qualifier CFS, then the entire request is rejected and the following error message is returned:
Bad value (coded) - conversionRate/fareSelc
The Multi Ticket option allows returning at the same time:
This option is applicable only on round trip recommendations (2 requested segments AB, BA).
In order to target better prices, the end-user can choose two one-way flights intead of the round-trip flight if the round-trip flight is more expensive.
All solutions are displayed as following
First all ITMs OW that group the independant outbound are returned from the cheapest to the more expensive solution.
Then all ITMs OW that group the independant inbound are returned from the cheapest to the more expensive solution
And finally all ITMs RT that group RT recommendations issued with 1 ticket are returned from the cheapest to the more expensive solution.
See "Error Messages" section.
In order to avoid quoting a fare to a passenger that they are then
unable to ticket at a later date, the end-user has the option of
specifying the intended ticketing date in the input.
This option ensures that the user will only receive recommendations
that, if priced on the same day as the query is received, are valid for
ticketing on the future ticketing date specified in the input.
If a Past Date is included in THE input it will be rejected with the
following warning message:
PAST DATE PRICING NOT PERMITTED (PSP message nbr 1064)
If the Future Date specified is later than the date of departure on the
first flight segment of the itinerary, it will be rejected with the
following warning message:
FUTURE DATE TICKETING NOT PERMITTED (PSP message nbr 1065)
This cabin class applies to the entire requested itinerary. It is only possible to default to other classes of service in the case where it has been requested to do so and at least one flight of the proposed segment contains the cabin class specified.
Cabin class may not be specified at individual segment levels. The following cabins may be specified:
For a marketing carrier, the cabin corresponding to each booking code is determined by the booking code and the first letter based on the Cabin definition stored in Amadeus System (e.g. C, CN)
When a Cabin is specified, the lowest fares are proposed using the Classes that are identified as matching the requested Cabin. Non-Stops, Directs, Connecting and Change of Gauges for which the cabin is not defined or not available are not selected.
The cabin option applies to the entire trip and must be specified at the itinerary level of the request. Requested cabin options at the segment level will result in an error.
Whenever the User specifies it, and whenever the requested cabin does not exist on someflights - either not defined or closed - the other cabins may be considered by the system. This process is only applied when in at least one of the flights of a Proposed segment on the requested cabin exists. Whenever a Proposed segment may not be booked in the requested cabin on any flight, this Proposed segment is eliminated, even if the end user allowed defaulting to other cabins.
Examples:
| Request | Process |
|---|---|
| Cabin Class F for return itinerary: PARIS/NEW YORK/CHICAGO |
If cabin class (F) is not available on any flight between Paris/NewYork/Chicago,the system proposed segment will not be returned in the recommendations. If Cabin Class (F) is only available on the system proposed segment only fromParis/NewYork, default cabin classes will be processed for NewYork/Chicago segments. If Cabin Class (F) is only available on the system proposed segment only fromNewYork/Chicago, default cabin classes will be processed for Paris/NewYork. |
The example below illustrates a low fare search including an optional Cabin elementspecified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| First cabin service requested at itinerary level | F |
| 1st requested segment | 1 |
| Trip Departure city of Paris | PAR |
| Trip Arrival city of Miami | MIA |
| Itinerary Date 02 December,2002 | 120202 |
If the cabin code does not exist, the following error message is returned:
"INVALID CABIN CODE".
If the cabin code is not requested at the itinerary level, the following error message is returned:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL".
The example below illustrates a low fare search including an optional Cabin element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Requested Cabin can be defaulted | RC |
| First cabin service requested at itinerary level | F |
| 1st requested segment | 1 |
| Trip Departure city of Paris | PAR |
| Trip Arrival city of Miami | MIA |
| Itinerary Date 02 December, 2002 | 120202 |
If the cabin code does not exist, the following error message is returned:
"INVALID CABIN CODE".
If the cabin code is not requested at the itinerary level, the following error message is returned:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL".
The example below illustrates a low fare search including an optional Major Cabin element specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Requested Cabin can be defaulted | MC |
| First cabin service requested at itinerary level | F |
| 1st requested segment | 1 |
| Trip Departure city of Paris | SYD |
| Trip Arrival city of Miami | NCE |
| Itinerary Date 02 December, 2002 | 131108 |
If the cabin code does not exist, the following error message is returned:
"INVALID CABIN CODE".
If the cabin code is not requested at the itinerary level, the following error message is returned:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL".
The example below illustrates a low fare search including an optional Pricing Scheme reference number specified with the following information.
Query Requirements:
| Requesting | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Pricing Scheme Reference | 12345 |
| Mandatory carrier requested at itinerary level | M |
| AF Mandatory carrier | AF |
| Searching mandatory airline combination with all carriers | YY |
| 1st requested segment | 1 |
| Mandatory requirement on Trip Departure city of Paris | PAR |
| Mandatory requirement on Trip Arrival city of Miami | MIA |
| Trip Date (Dec 20, 2001) | 201203 |
| 2nd requested segment | 2 |
| Departure city of Miami | MIA |
| Arrival city of New York | NYC |
| Trip Date 25th Dec, 2001 | 251203 |
See "Error Messages" section.
The form of payment option may be combined with any other option. A maximum of 3 forms of payment may be keyed in.
It is optional that the traveler indicates some forms of payment.
Possible values are AGT, CC, CA, CK, GR, MS, NR, PT, SGR, UN.
If one form of payment is specified, the amount is optional
If two forms of payment are specified, one amount is mandatory and one amount is optional.
If three forms of payment are specified, two amounts must be specified.
When the form of payment is specified as CC, a 6 digit bin number is required.
The example below illustrates a low fare search including optional form of payment.
Query Requirements:
| Requesting Details | Specified Data |
|---|---|
| Request by number of seats occupied by passengers | PX |
| # of seats for request | 1 |
| Request specific maximum number of recommendations to be returned | RC |
| Maximum # of recommendations requested | 200 |
| Adult Passenger type code | ADT |
| Passenger type code applicable to 1st passenger | 1 |
| Applicable on 1st trip | 1 |
| Trip departure city of Paris | PAR |
| Trip arrival city of Nice | NCE |
| Trip date December, 21, 2007 | 211207 |
| Form of payment 1 | CC |
| Credit card bin number | 123456 |
| Amount applied on form of payment 1 | 100 |
| Form of payment 2 | CC |
| Credit card bin number | 234566 |
| Amount applied on form of payment 2 | 200 |
Two FOP must not be provided without any amounts. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
Three FOP must not be provided without any amounts. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
Three FOP must not be provided with only one amount. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
Three FOP must not be provided with three amounts. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
More than three FOP cannot be entered. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
A Form of Payment sub-code cannot be added in combination with a Form of Payment in input. If done, the whole request is rejected and the following message is returned:
"CONFLICTING OPTIONS USED"
This optional input allows sorting recommendations considering or not fees applying to fares in the ranking. Possible values for OB fees are SORT: NOFEE or SORT: FEE.
Fees cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected and the following message is returned:
"ENTRY NOT AUTHORISED"
Fees cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and the following message is returned:
"ENTRY NOT AUTHORISED"
Airline ticketing fees can all be exempted with this option.
It is optional.
Fees cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected and the following message is returned:
"ENTRY NOT AUTHORISED"
Fees cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and the following message is returned:
"ENTRY NOT AUTHORISED"
A specific fee can not be both added and exempted in input. If done, the whole request is rejected and the following message is returned:
"CONFLICTING OPTIONS USED"
Airline ticketing fees (OB fees) sub-codes can be specified in order to add or exempt particular fees.
The airline ticketing fees concept is driven from data filed by the airline.
A maximum of six sub-codes can be added or exempted. For each added FoP sub-code (neither exempted subcode nor ticketing sub-code), an amount can be optionally specified.
If one Fop sub-code is added, an amount is optional.
If two Fop sub-codes are added, the two amounts are optional.
If three Fop sub-codes are added, 0 or 2 amounts can be specified but neither 1 no 3.
Note: that airline ticketing fees are not yet available in all markets or all carriers, for further details contact your local Amadeus Help Desk.
Example:
| Requesting Details | Specified Data |
|---|---|
| Exempting airline ticketing fees for sub-code T02 | T02:EX |
| Adding airline ticketing fees applied on a credit card with a bin number starting with 4 | FC4:IN |
| Amount paid with credit card with a bin number starting with 4 is 20.00 [1] | 20.00 |
[1] Fees from FCA sub-code may apply also.
A sub-code cannot be added if OB Global Activation setting is OFF. If done, the whole request is rejected and the following message is returned:
"ENTRY NOT AUTHORISED"
It is not allowed to enter an amount with an addition of a Ticketing sub-code. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
FCA cannot be added in combination with another Form Of Payment sub-code. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
Three Form Of Payment sub-codes must not be added with only one amount. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
Three Form of Payment sub-codes must not be added with three amounts. If done, the whole request is rejected and the following message is returned:
"CHECK FORMAT"
A sub-code cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected and the following message is returned:
"ENTRY NOT AUTHORISED"
A sub-code cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and the following message is returned:
"ENTRY NOT AUTHORISED"
A Form of Payment sub-code cannot be added in combination with a Form of Payment in input. If done, the whole request is rejected and the following message is returned:
"CONFLICTING OPTIONS USED"
A specific fee can not be both added and exempted in input. If done, the whole request is rejected and the following message is returned:
"CONFLICTING OPTIONS USED"
When this option is requested, the total number of Recommendations are distributed over 2 sets as following:
This set contains the cheapest recommendation for each online carrier and the cheapest recommendation for each Mono-Main Carrier.
In case there is a recommendation online on a carrier and this carrier is also the main carrier on another recommendation, and if the main carrier recommendation is cheaper than the online one, both recommendations are returned. This means that for a carrier, in addition to the cheapest online recommendation, the cheapest recommendation on which this carrier is also the main carrier is also returned only if this recommendation is cheaper than the online one.
This set contains the cheapest recommendations matching the client's query that are not included in the Airline Diversity recommendations set.
In order to have more airline diversity within this set, the process guarantees that no more than 50% of the recommendation has the same combination of main carriers over the
itinerary.
When this option is requested, the total number of Recommendations are distributed over 2 sets as following:
Up to 25% of the Total Number of Recommendation is allocated to the airline diversity. This set of recommendations is distributed over all
the different carriers ensuring at least the cheapest recommendation for each online carrier and the cheapest recommendation for each Main
Carrier.
In case there is a recommendation online on a carrier and this carrier is also the main carrier on another recommendation, and if the main carrier recommendation is cheaper than the online one, both recommendations are returned. This means that for a carrier, in addition to the cheapest online recommendation, the cheapest recommendation on which this carrier is also the main carrier is also returned only if this recommendation is cheaper than the online one.
This set contains the cheapest recommendations matching the client's query that are not included in the Airline Diversity Container.
In order to have more airline diversity within this set, the process guarantees that no more than 50% of the cheapest recommendations set have the same combination of main carriers over the itinerary.
In order to enhance the quality of the recommendations returned by Master Pricer Travel Board, the direct distribution process has been introduced to favour the recommendations which are direct.
Direct Recommendations can be naturally returned by MPT if they are among the cheapest recommendations. For example if 250 recommendations are asked, a part or the total 250 can be direct.
In case there are not or too few direct recommendations, the process of the direct distribution will force the direct recommendations in the returned solutions up to 20% of the asked number if they exist.
See "Error Messages" section.
Direct Distribution can be deactivated using the option NDD.
See "Error Messages" section.
It is possible to deactivate the ADI distribution using the option NAD
See "Error Messages" section.
When searching cheapest solution on a given itinerary on fixed or flexible dates, the search can have locally no solution for the following reasons:
When the Empty Cells Clarification option is activated, and those cases are met during the search, the corresponding information is returned in the output message.
For dates out of the range of the request, for example when a trip duration is specified, no precision is given in the output message as it is the case for the default behaviour when this option is not activated.
The End User has the ability to request the display of the rank of the Flight Solution within the list of Flight Solutions returned by Journey Server (numbering starts to 1) per requested segment.
For Calendar product, the rank is given per requested segment and per date.
This example illustrates a 'change of gauge' flight solution.
The reply has been limited to 3 units (instead of 200) this is primarily due to the size of the output.
In Proposed segment 2, see the change of gauge (i.e. change of equipment) on flight IB6173 between MAD and SJO. Traveller stops in MIA and changes of equipment Boeing 747 => Airbus 319.
| Item | PoweredLowestFare_SearchReply - Data element | Value |
|---|---|---|
| 0 | /replyStatus/status/advisoryTypeInfo | FQX |
| 1 | /conversionRate/conversionRateDetail/currency | USD |
| 2 | /flightIndex/requestedSegmentRef/segRef | 1 |
| 3 | /flightIndex/groupOfFlights[11] /propFlightGrDetail/flightProposal[11] /ref | 1 |
| 4 | /flightIndex/groupOfFlights[11] /propFlightGrDetail/flightProposal[21] /ref | 1305 |
| 5 | /flightIndex/groupOfFlights[11] /propFlightGrDetail/flightProposal[21] / unitQualifier | EFT |
| 6 | /flightIndex/groupOfFlights[11] /propFlightGrDetail/flightProposal[31] /ref | S3 |
| 7 | /flightIndex/groupOfFlights[11] /propFlightGrDetail/flightProposal[31] / unitQualifier | MCX |
| 8 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/productDateTime/dateOfDeparture | 200703 |
| 9 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/productDateTime/timeOfDeparture | 1200 |
| 10 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/productDateTime/dateOfArrival | 200703 |
| 11 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/productDateTime/timeOfArrival | 1500 |
| 12 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/location[11] / locationId | MAD |
| 13 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/location[11] /terminal | 1 |
| 14 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/location[21] / locationId | CCS |
| 15 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/companyId/marketingCarrier | S3 |
| 16 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/companyId/operatingCarrier | S3 |
| 17 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/ flightNumber | 1333 |
| 18 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/productDetail/equipmentType | D10 |
| 19 | /flightIndex/groupOfFlights[11] / flightDetails [11] /flightInformation/addProductDetail/electronicTicketing | N |
| 20 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/productDateTime/dateOfDeparture | 200703 |
| 21 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/productDateTime/timeOfDeparture | 1615 |
| 22 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/productDateTime/dateOfArrival | 200703 |
| 23 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/productDateTime/timeOfArrival | 1705 |
| 24 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/location[11] / locationId | CCS |
| 25 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/location[21] / locationId | SJO |
| 26 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/companyId/marketingCarrier | LR |
| 27 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/companyId/operatingCarrier | LR |
| 28 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/ flightNumber | 611 |
| 29 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/productDetail/equipmentType | 320 |
| 30 | /flightIndex/groupOfFlights[11] / flightDetails [21] /flightInformation/addProductDetail/electronicTicketing | N |
| 31 | /flightIndex/groupOfFlights[21] /propFlightGrDetail/flightProposal[11] /ref | 2 |
| 32 | /flightIndex/groupOfFlights[21] /propFlightGrDetail/flightProposal[21] /ref | 1415 |
| 33 | /flightIndex/groupOfFlights[21] /propFlightGrDetail/flightProposal[21] / unitQualifier | EFT |
| 34 | /flightIndex/groupOfFlights[21] /propFlightGrDetail/flightProposal[31] /ref | IB |
| 35 | /flightIndex/groupOfFlights[21] /propFlightGrDetail/flightProposal[31] / unitQualifier | MCX |
| 36 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/productDateTime/dateOfDeparture | 200703 |
| 37 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/productDateTime/timeOfDeparture | 1215 |
| 38 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/productDateTime/dateOfArrival | 200703 |
| 39 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/productDateTime/timeOfArrival | 1830 |
| 40 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/location[11] / locationId | MAD |
| 41 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/location[11] /terminal | 1 |
| 42 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/location[21] / locationId | SJO |
| 43 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/companyId/marketingCarrier | IB |
| 44 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/companyId/operatingCarrier | IB |
| 45 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/ flightNumber | 6173 |
| 46 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/productDetail/equipmentType | 747 |
| 47 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/addProductDetail/electronicTicketing | Y |
| 48 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/productDetail/techStopNumber | 1 |
| 49 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[11] /dateQualifier | AA |
| 50 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[11] /date | 200703 |
| 51 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[11] /firstTime | 1540 |
| 52 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[11] / locationId | MIA |
| 53 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[21] /dateQualifier | AD |
| 54 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[21] /date | 200703 |
| 55 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[21] /firstTime | 1645 |
| 56 | /flightIndex/groupOfFlights[21] / flightDetails/technicalStop/stopDetails[21] /equipmentType | 319 |
| 57 | /flightIndex/groupOfFlights[21] / flightDetails/flightInformation/addProductDetail[21] //electronicTicketing | N |
| 58 | /flightIndex/groupOfFlights[31] /propFlightGrDetail/flightProposal[11] /ref | 3 |
| 59 | /flightIndex/groupOfFlights[31] /propFlightGrDetail/flightProposal[21] /ref | 2505 |
| 60 | /flightIndex/groupOfFlights[31] /propFlightGrDetail/flightProposal[21] / unitQualifier | EFT |
| 61 | /flightIndex/groupOfFlights[31] /propFlightGrDetail/flightProposal[31] /ref | AA |
| 62 | /flightIndex/groupOfFlights[31] /propFlightGrDetail/flightProposal[31] / unitQualifier | MCX |
| 63 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/productDateTime/dateOfDeparture | 200703 |
| 64 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/productDateTime/timeOfDeparture | 1655 |
| 65 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/productDateTime/dateOfArrival | 200703 |
| 66 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/productDateTime/timeOfArrival | 1815 |
| 67 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/location[11] / locationId | MAD |
| 68 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/location[11] /terminal | 1 |
| 69 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/location[21] / locationId | LHR |
| 70 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/location[21] /terminal | 2 |
| 71 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/companyId/marketingCarrier | IB |
| 72 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/companyId/operatingCarrier | IB |
| 73 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/ flightNumber | 3166 |
| 74 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/productDetail/equipmentType | 752 |
| 75 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/addProductDetail/electronicTicketing | Y |
| 76 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/productDateTime/dateOfDeparture | 200703 |
| 77 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/productDateTime/timeOfDeparture | 2005 |
| 78 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/productDateTime/dateOfArrival | 200703 |
| 79 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/productDateTime/timeOfArrival | 2250 |
| 80 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/location[11] / locationId | LHR |
| 81 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/location[11] /terminal | 3 |
| 82 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/location[21] / locationId | JFK |
| 83 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/location[21] /terminal | 8 |
| 84 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/companyId/marketingCarrier | AA |
| 85 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/companyId/operatingCarrier | AA |
| 86 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/ flightNumber | 141 |
| 87 | /flightIndex/groupOfFlights[31] / flightDetails [21] /flightInformation/productDetail/equipmentType | 777 |
| 88 | /flightIndex/groupOfFlights[31] / flightDetails [11] /flightInformation/addProductDetail/electronicTicketing | N |
| 89 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/productDateTime/dateOfDeparture | 210703 |
| 90 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/productDateTime/timeOfDeparture | 0640 |
| 91 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/productDateTime/dateOfArrival | 210703 |
| 92 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/productDateTime/timeOfArrival | 1000 |
| 93 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/location[11] / locationId | JFK |
| 94 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/location[11] /terminal | 2 |
| 95 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/location[21] / locationId | SJO |
| 96 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/companyId/marketingCarrier | LR |
| 97 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/companyId/operatingCarrier | LR |
| 98 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/ flightNumber | 663 |
| 99 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/productDetail/equipmentType | 320 |
| 100 | /flightIndex/groupOfFlights[31] / flightDetails [31] /flightInformation/addProductDetail/electronicTicketing | N |
| 101 | /recommendation[11] /itemNumber/itemNumberId/number | 1 |
| 102 | /recommendation[11] /recPriceInfo/monetaryDetail[11] /amount | 734.60 |
| 103 | /recommendation[11] /recPriceInfo/monetaryDetail[21] /amount | 9.60 |
| 104 | /recommendation[11] /segmentFlightRef/referencingDetail/ refQualifier | S |
| 105 | /recommendation[11] /segmentFlightRef/referencingDetail/ refNumber | 1 |
| 106 | /recommendation[11] /paxFareProduct/paxFareDetail/paxFareNum | 1 |
| 107 | /recommendation[11] /paxFareProduct/paxFareDetail/ totalFareAmount | 734.60 |
| 108 | /recommendation[11] /paxFareProduct/paxFareDetail/ totalTaxAmount | 9.60 |
| 109 | /recommendation[11] /paxFareProduct/paxReference/ptc | ADT |
| 110 | /recommendation[11] /paxFareProduct/paxReference/traveller/ref | 1 |
| 111 | /recommendation[11] /paxFareProduct/fare/pricingMessage/ freeTextQualification/messageQualifier | LTD |
| 112 | /recommendation[11] /paxFareProduct/fare/pricingMessage/ freeTextQualification/messageCode | 40 |
| 113 | /recommendation[11] /paxFareProduct/fare/pricingMessage/ description [11] | LAST TKT DTE |
| 114 | /recommendation[11] /paxFareProduct/fare/pricingMessage/description [21] | 20FEB03 |
| 115 | /recommendation[11] /paxFareProduct/fare/pricingMessage/description [31] | - SEE ADV PURCHASE |
| 116 | /recommendation[11] /paxFareProduct/fareDetails/segmentRef/segRef | 1 |
| 117 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [11] /avlProductDetails/rbd | M |
| 118 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [11] /avlProductDetails/avlStatus | 4 |
| 119 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [11] /fareProductDetail/ fareBasis | MHOW |
| 120 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [11] /fareProductDetail/ passengerType | ADT |
| 121 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [11] /fareProductDetail/ fareType | RP |
| 122 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [21] /avlProductDetails/rbd | Y |
| 123 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [21] /avlProductDetails/avlStatus | 7 |
| 124 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [21] /fareProductDetail/ fareBasis | MHOW |
| 125 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [21] /fareProductDetail/ passengerType | ADT |
| 126 | /recommendation[11] /paxFareProduct/fareDetails/ productInformation [21] /fareProductDetail/ fareType | RP |
| 127 | /recommendation[21] /itemNumber/itemNumberId/number | 2 |
| 128 | /recommendation[21] /recPriceInfo/monetaryDetail[11] /amount | 973.10 |
| 129 | /recommendation[21] /recPriceInfo/monetaryDetail[21] /amount | 8.10 |
| 130 | /recommendation[21] /segmentFlightRef/referencingDetail/ refQualifier | S |
| 131 | /recommendation[21] /segmentFlightRef/referencingDetail/ refNumber | 2 |
| 132 | /recommendation[21] /paxFareProduct/paxFareDetail/paxFareNum | 1 |
| 133 | /recommendation[21] /paxFareProduct/paxFareDetail/ totalFareAmount | 973.10 |
| 134 | /recommendation[21] /paxFareProduct/paxFareDetail/ totalTaxAmount | 8.10 |
| 135 | /recommendation[21] /paxFareProduct/paxReference/ptc | ADT |
| 136 | /recommendation[21] /paxFareProduct/paxReference/traveller/ref | 1 |
| 137 | /recommendation[21] /paxFareProduct/fare[11] /pricingMessage/ freeTextQualification/messageQualifier | PEN |
| 138 | /recommendation[21] /paxFareProduct/fare[11] /pricingMessage/ freeTextQualification/messageCode | 71 |
| 139 | /recommendation[21] /paxFareProduct/fare[11] /pricingMessage/description | TICKETS ARE NON-REFUNDABLE AFTER DEPARTURE |
| 140 | /recommendation[21] /paxFareProduct/fare[21] /pricingMessage/ freeTextQualification/messageQualifier | LTD |
| 141 | /recommendation[21] /paxFareProduct/fare[21] /pricingMessage/ freeTextQualification/messageCode | 40 |
| 142 | /recommendation[21] /paxFareProduct/fare[21] /pricingMessage/description [11] | LAST TKT DTE |
| 143 | /recommendation[21] /paxFareProduct/fare[21] /pricingMessage/description [21] | 06FEB03 |
| 144 | /recommendation[21] /paxFareProduct/fare[21] /pricingMessage/description [31] | - SEE ADV PURCHASE |
| 145 | /recommendation[21] /paxFareProduct/fareDetails/segmentRef/segRef | 1 |
| 146 | /recommendation[21] /paxFareProduct/fareDetails/ productInformation/avlProductDetails/rbd | B |
| 147 | /recommendation[21] /paxFareProduct/fareDetails/ productInformation/avlProductDetails/avlStatus | 9 |
| 148 | /recommendation[21] /paxFareProduct/fareDetails/ productInformation/fareProductDetail/ fareBasis | BHSXOW |
| 149 | /recommendation[21] /paxFareProduct/fareDetails/ productInformation/fareProductDetail/ passengerType | ADT |
| 150 | /recommendation[21] /paxFareProduct/fareDetails/ productInformation/fareProductDetail/ fareType | RP |
| 151 | /recommendation[31] /itemNumber/itemNumberId/number | 3 |
| 152 | /recommendation[31] /recPriceInfo/monetaryDetail[11] /amount | 1001.22 |
| 153 | /recommendation[31] /recPriceInfo/monetaryDetail[21] /amount | 26.22 |
| 154 | /recommendation[31] /segmentFlightRef/referencingDetail/ refQualifier | S |
| 155 | /recommendation[31] /segmentFlightRef/referencingDetail/ refNumber | 3 |
| 156 | /recommendation[31] /paxFareProduct/paxFareDetail/paxFareNum | 1 |
| 157 | /recommendation[31] /paxFareProduct/paxFareDetail/ totalFareAmount | 1001.22 |
| 158 | /recommendation[31] /paxFareProduct/paxFareDetail/ totalTaxAmount | 26.22 |
| 159 | /recommendation[31] /paxFareProduct/paxReference/ptc | ADT |
| 160 | /recommendation[31] /paxFareProduct/paxReference/traveller/ref | 1 |
| 161 | /recommendation[31] /paxFareProduct/fare[11] /pricingMessage/ freeTextQualification/messageQualifier | PEN |
| 162 | /recommendation[31] /paxFareProduct/fare[11] /pricingMessage/ freeTextQualification/messageCode | 71 |
| 163 | /recommendation[31] /paxFareProduct/fare[11] /pricingMessage/description | TICKETS ARE NON-REFUNDABLE AFTER DEPARTURE |
| 164 | /recommendation[31] /paxFareProduct/fare[21] /pricingMessage/ freeTextQualification/messageQualifier | LTD |
| 165 | /recommendation[31] /paxFareProduct/fare[21] /pricingMessage/ freeTextQualification/messageCode | 40 |
| 166 | /recommendation[31] /paxFareProduct/fare[21] /pricingMessage/description [11] | LAST TKT DTE |
| 167 | /recommendation[31] /paxFareProduct/fare[21] /pricingMessage/description [21] | 06FEB03 |
| 168 | /recommendation[31] /paxFareProduct/fare[21] /pricingMessage/description [31] | - SEE ADV PURCHASE |
| 169 | /recommendation[31] /paxFareProduct/fareDetails/segmentRef/segRef | 1 |
| 170 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [11] /avlProductDetails/rbd | K |
| 171 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [11] /avlProductDetails/avlStatus | 9 |
| 172 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [11] /fareProductDetail/ fareBasis | KHSXOW |
| 173 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [11] /fareProductDetail/ passengerType | ADT |
| 174 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [11] /fareProductDetail/ fareType | RP |
| 175 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [21] /avlProductDetails/rbd | K |
| 176 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [21] /avlProductDetails/avlStatus | 7 |
| 177 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [21] /fareProductDetail/ fareBasis | KHSXOW |
| 178 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [21] /fareProductDetail/ passengerType | ADT |
| 179 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [21] /fareProductDetail/ fareType | RP |
| 180 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [31] /avlProductDetails/rbd | Z |
| 181 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [31] /avlProductDetails/avlStatus | 7 |
| 182 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [31] /fareProductDetail/ fareBasis | KHSXOW |
| 183 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [31] /fareProductDetail/ passengerType | ADT |
| 184 | /recommendation[31] /paxFareProduct/fareDetails/ productInformation [31] /fareProductDetail/ fareType | RP |
See "Error Messages" section.
This example shows a reply with a 'technical stop' flight solution.
In the reply extract below note the technical stop on flight BA 772 between LHR and SYD: item 86.
| Item | PoweredLowestFare_SearchReply - Data element | Value |
|---|---|---|
| 67 | /flightIndex/groupOfFlights[3]/propFlightGrDetail/flightProposal[1]/ ref | 3 |
| 68 | /flightIndex/groupOfFlights[3]/propFlightGrDetail/flightProposal[2]/ ref | 2115 |
| 69 | /flightIndex/groupOfFlights[3]/propFlightGrDetail/flightProposal[2]/ unitQualifier | EFT |
| 70 | /flightIndex/groupOfFlights[3]/propFlightGrDetail/flightProposal[3]/ ref | BA |
| 71 | /flightIndex/groupOfFlights[3]/propFlightGrDetail/flightProposal[3]/ unitQualifier | MCX |
| 72 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/productDateTime/ dateOfDeparture | 200703 |
| 73 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/productDateTime/ timeOfDeparture | 1215 |
| 74 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/productDateTime/ dateOfArrival | 210703 |
| 75 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/productDateTime/ timeOfArrival | 1830 |
| 76 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/productDateTime/ dateVariation | 1 |
| 77 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/location[1]/ locationId | LHR |
| 78 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/location[1]/ terminal | 4 |
| 79 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/location[2]/ locationId | SYD |
| 80 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/location[2]/ terminal | I |
| 81 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/companyId/ marketingCarrier | BA |
| 82 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/companyId/ operatingCarrier | QF |
| 83 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/ flightNumber | 7372 |
| 84 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/productDetail/ equipmentType | 747 |
| 85 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/addProductDetail/ electronicTicketing | N |
| 86 | /flightIndex/groupOfFlights[3]/ flightDetails/flightInformation/productDetail/ techStopNumber | 1 |
| 87 | /flightIndex/groupOfFlights[3]/ flightDetails/technicalStop/stopDetails[1]/ dateQualifier | AA |
| 88 | /flightIndex/groupOfFlights[3]/ flightDetails/technicalStop/stopDetails[1]/ date | 210703 |
| 89 | /flightIndex/groupOfFlights[3]/ flightDetails/technicalStop/stopDetails[1]/ firstTime | 0800 |
| 90 | /flightIndex/groupOfFlights[3]/ flightDetails/technicalStop/stopDetails[1]/ locationId | SIN |
| 91 | /flightIndex/groupOfFlights[3]/ flightDetails/technicalStop/stopDetails[2]/ dateQualifier | AD |
| 92 | /flightIndex/groupOfFlights[3]/ flightDetails/technicalStop/stopDetails[2]/ date | 210703 |
| 93 | /flightIndex/groupOfFlights[3]/ flightDetails/technicalStop/stopDetails[2]/ firstTime | 0915 |
See "Error Messages" section.
Description of the Reply:
Note that many commercialAgreement may therefore refer to the same companyIdText. Note also that Code share agreements are only returned whenever the operating carrieris free form.
Example of reply with operating carrier known as free form text by the system:
See "Error Messages" section.
This example shows a query for an adult and an infant (ins) both taking a seat.
See "Error Messages" section.
The prohibited country warning indicator indicates if the flight has been flagged as a warning flight (WRN) by Prohibited country processing . Its value is 'C' in the case the flight is a warning flight.
See "Error Messages" section.