Storing fares is required on the Galileo® CRS to guarantee the fare. Storing fares is not technically required on Apollo® CRS. However, many travel providers require stored fare quotes as part of their business process. FareQuoteCancel_6_0 cancels stored fares. This transaction does not cancel multiple Automatic Ticketing Fare Quotes (ATFQs). To cancel multiple ATFQs use the DocProdFareManipulation_# transaction.
See the Air Shop FAQ for questions regarding all air shopping transactions.
On Apollo, fare quotes for a booked itinerary are not guaranteed and can change any time prior to ticketing. Because fare quotes on Apollo can change any time prior to ticketing, the stored fare (ATFQ) is usually verified before ticketing, particularly if there is a significant gap in time between the original fare quote and ticketing. Storing and verifying fares are not mandatory. However, it is good business practice to confirm fares prior to ticketing.
In some cases, it is appropriate to cancel the stored fare. There are three (3) primary reasons why a stored fare has to be canceled:
Canceling a stored fare quote eliminates all pricing information from the PNR/BF. All stored fare fields or specific stored fields can be canceled from the PNR/BF.
This function is only valid when a fare has been stored, such as in the PNRBFManagement_# transaction. In order for any changes to take affect, this function must be followed by an End Transact, also in PNRBFManagement_#.
API Developer Notes can assist you when developing applications that use Galileo Web Services and XML Select. The following table lists the API Developer Notes that are applicable to this transaction and provides a description. Each document is a link to the PDF file:
Document | Description |
Travel Industry Airlines and Airfares | High-level overview of airline industry codes, airline routing, airline ticketing, and how fares are created. |