Private fares can be redistributed (also known as emulation), which allows the requester to use another Pseudo City Code (PCC). Redistribution requires a prior agreement between the requester and the other travel provider, such as Selective Access or Group Coding. The provider (1G, 1V) establishes the agreement. Many private fares have redistribution coded in Category 15 and 35 to secure the private fare to a requester and a provider.
A redistributed fare can be stored in a Universal Record at either the top level or the fare level.
Request
Universal API supports redistribution of private fares in Low Fare Shopping, Air Pricing, and Air Booking at the Universal Record level, and in the Universal Record Modify at the stored fare level.
- A redistributed fare can be stored at the Universal Record level, using the PointOfSale element at the top level (e.g., AirPricReq/PointOfSale) for Low Fare Shopping, Air Pricing, and Air Booking.
- A redistributed fare can be stored at the fare level during an Air Booking by sending the provider agency's Pseudo City Code (PCC) in PointOfSale @PseudoCityCode in AirCreateReservationReq/AirPricingSolution/AirPricingInfo/AirPricingModifiers.
- A redistributed fare can be stored in an existing Universal Record at the fare level by sending the provider agency's Pseudo City Code (PCC) in PointOfSale @PseudoCityCode in UniversalModifyReq/UniversalModifyCmd/AirAdd/AirPricingInfo/AirPricingModifiers.
Note: The PointOfSale schema change for AirPricingModifiers is propagated, but not enabled, in any other Universal API services that contain the AirPricingModifiers element.
The provider checks the selective access agreements, group coding, etc. between the requestor agency and the provider agency PCCs. If an agreement exists, the fares that are returned by the provider can be either from the requestor agency PCC, the provider agency PCC, or both agency PCCs.
The PointOfSale @PseudoCityCode can be sent either at the Universal Record level or at the stored fare level. If both are sent, the Pseudo City Code at the Universal Record level is ignored.
The PointOfSale @PseudoCityCode value of each AirPricingInfo is used to create the stored fare. Therefore, when multiple AirPricingInfo elements are sent in either UniversalRecordModifyReq or AirCreateReservationReq, separate stored fares are created in the Universal Record for each AirPricingInfo element, if each instance of AirPricingInfo has a unique AirPricingInfoGroup value.
If UniversalRecordModifyReq or AirCreateReservationReq is sent with a PointOfSale @PseudoCityCode for each AirPricingInfo, but the value of each AirPricingInfoGroup attribute is the same or does not exist, a single stored fare is created for the entire Universal Record. In this case, the PointOfSale @PseudoCityCode value of the first AirPricingInfo element is used to determine the PCC. And if the first AirPricingInfo element does not contain a PseudoCityCode value, the requestor agency’s PCC is used as the default value.
Response
There are no changes to Universal Record Modify response, except when a price difference occurs between the pricing information sent in UniversalRecordModifyReq or AirCreateReservationReq and the pricing information returned by the provider. In this case, the AirSolutionChangedInfo element is returned in UniversalRecordModifyRsp or AirCreateReservationRsp.
AirSolutionChangedInfo contains the pricing information sent in UniversalRecordModifyReq. The PointOfSale element is also returned in the AirSolutionChangeInfo element, if applicable.
If the first occurrence of AirPricingInfo/PointOfSale @PseudoCityCode is used to determine the stored fare, warning messages are returned in the following scenarios:
- If Multiple AirPricingInfo elements are sent with different PCCs (@PseudoCityCode), this warning is returned:
- If Multiple AirPricingInfo elements are sent, but no PCC is included in the first AirPricingInfo element, this warning is returned:
Different PseudoCityCode values sent in multiple AirPricingInfo without AirPricingInfoGroup or with same AirPricingInfoGroup values. PCC [Pseudo City Code] used to store fares.
Multiple AirPricingInfo without AirPricingInfoGroup or with same AirPricingInfoGroup values sent. PseudoCityCode value not sent in first AirPricingInfo. PCC [Pseudo City Code] used to store fares.
Exceptions
Worldspan
Storing redistributed fares in the Universal Record via Universal Record Modify and Air Booking is supported for Worldspan (1P). However, the Pseudo City Code is not sent in the Universal Record Modify or Air Booking request. If a Pseudo City Code is sent in either request, a warning is returned: Separate PointOfSale not supported by provider.
This warning is already returned if the Pseudo City Code is sent in Low Fare Shopping, Air Pricing, and Air Booking.
Feedback / Support
