After a fare quote has been stored, modifiers can be included that apply only to the ticket issued from a stored fare and not the price. Ticketing modifiers are separate from the Pricing modifiers that are added to the pricing request, and they do not change the fare. They change the data on the ticket or the data that a ticket is handed off as a result of the ticket transaction. Examples of ticketing modifiers include commission, form of payment, and document selection.
Ticketing modifiers can be:
- Added using UniversalRecordModifyReq/UniversalModifyCmd/AirAdd/AirPricingTicketingModifiers
- Deleted using UniversalRecordModifyReq/UniversalModifyCmd/AirDelete/TicketingModifiersRef (this message removes all modifiers associated with TicketModifiersRef)
- Updated incrementally.
Each entry that contains updated ticketing modifiers acts as an overwrite for the entire list of modifiers stored with that fare. For example: If a commission override and a plating carrier have been stored with the fare, and an endorsement needs to be added, the entry must re-state the commission amount and the plating carrier along with the new endorsement. If only the endorsement data is sent in, the commission and plating carrier information are removed. The same applies if a form of payment is stored and another modifier is submitted. Modifiers are removed in the same way: by submitting all existing modifiers and omitting the modifier which is no longer needed.
If the UR synchronized with the Host booking, then AirPricingInfo can be used as the source for the modifiers.
| Air Ticketing Modifiers | Description |
|---|---|
|
The form of payment can be added, changed, or deleted using the AirPricingTicketingModifiers element in the Universal Record Modify request. |
|
|
The Net Remittance modifiers are used to adjust the fare information that is printed on the ticket and supporting documents for Net Fares. |
|
|
The Ticketing Modifiers change the data on the ticket. They include:
|
|
|
The Value Added Tax (VAT) information can be printed on the ticket. |
Universal API validates the following when the Air Ticketing Modifiers above are used:
- A stored fare (AirPricingInfo) exists in both the UR and the Host. The UR retrieve syncs the fare data between the Host and Universal API. This validation is required for the AirAdd/AirPricingTicketingModifiers message to reference valid UR AirPricingInfos.
- If AirAdd/AirPricingTicketingModifiers is used,and TicketModifers already exist for AirPricingInfo, an error is returned: "Ticketing Modifiers already exist for referenced AirPricingInfo"
- If the AirPricingInfoRef(s) referenced in the AirAdd/AirPricingTicketingModifiers are not within a single AirReservation, an error is returned: "AirPricingInfoRef must be for a single AirReservation"
To add Ticketing modifiers to multiple stored fares using a single Universal API request, use multiple UniversalModifyCmds, and specify the data separately for each stored fare. For a particular stored fare, all the AirPricingTicketingModifiers/AirPricingInfoRef must be specified or an error is returned. A stored fare is identified by the value of AirPricingInfoGroup, and all AirPricingInfos that have the same AirPricingInfoGroup belong to the same stored fare in the provider reservation.
Feedback / Support
