DocProdFareManipulation_19

*Archived Transaction*

Quick Info

The DocProdFareManipulation_19 transaction controls the manipulation and redisplay of stored fares. It also allows MCOs and tickets to be issued for a specified fare within a PNR or BF. 

Notes:

• All ticketing modifiers must be updated and stored with the fare by using DocProdFareRequote_# before this transaction can be used to ticket the fare. This function is only valid when a fare has been stored, such as in the  PNRBFManagement_# transaction. Ticketing modifiers cannot be updated at the time of ticketing.

• It is highly recommended that the PNR/BF be End Transacted (ET) and then retrieved, before ticketing. For any changes to take effect,  DocProdFareManipulation_19 must be followed by an End Transact, such as in PNRBFManagement_#. If the PNR/BF is incomplete or has other problems, the ticketing will fail.
  
  When an End Transact is attempted for a bad PNR/BF, the CRS returns error messages that are clearer and easier to understand than when ticketing is attempted without an End Transact. It is therefore easier to recover from a failed End Transact than from a failed ticketing attempt. If the End Transact is successful, the chances of a failed ticketing attempt are much lower.

• To enter a null value for many child elements, the user must send blanks that are encapsulated by a CDATA tag. For example, to send a null value for <LastTkDt> the user must send:
  <LastTkDt><![CDATA[        ]></LastTkDt> (i.e., a CDATA with eight blanks).

• When <GenQuoteDetails> is used for any task, the <LastTkDt> and <QuoteDt> child elements are required. To enter a null value for these child elements, the CDATA tag with eight blanks must be used.

• When <SegRelatedInfo> is used for any task, the <NotValidBeforeDt> and <NotValidAfterDt> child elements are required. To enter a null value for these child elements, the CDATA tag with eight blanks must be used.

Canceling a Stored Fare

In some cases, it is appropriate to cancel the stored fare. There are three primary reasons why a stored fare must be canceled:

• The itinerary itself changed before the ticket was issued. Any modification that affects the price of the ticket requires that existing fare to be canceled, the itinerary re-priced, and the new fare stored.
• The original terms of the fare change, even if the itinerary does not change. For example, a stored fare quote can be canceled (without canceling the itinerary) if the traveler decides not to use a certificate.
• The transaction needs to be ended, and there is additional information that must be added to the pricing line.

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.

Repricing a Stored Fare

On Galileo, stored fares that have been ticketed cannot be canceled. If re-ticketing is required, the fare must be re-priced. Reasons why an existing fare must be canceled and re-priced include:

• The itinerary changed before the ticket could be issued. Any modification that affects the price of the ticket requires the existing fare to be canceled, the itinerary re-priced, and the new fare stored.

• The original terms of the fare change, even if the itinerary does not change. For example, a stored fare quote can be canceled (without canceling the itinerary) if the traveler decides not to use a certificate.

Use the DocProdFareManipulation_19 transaction after a fare has already been stored with the PNRBFManagement transaction.

Related API Developer Notes

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: