Canceling Travel Segments via the UR

One or more air segments or passive can be canceled from a Universal Record. Alternately, a segment can be deleted by modifying the PNR for the respective segments.

For more information about canceling an entire trip, or canceling all air segments in a PNR, see Canceling Bookings. For more information about deleting specific data within a segment without canceling the segment itself, see Modifying Bookings.

Schema

Located in Universal.xsd:

• UniversalRecordModifyReq
• UniversalRecordModifyRsp

How To

1. Important! Before canceling a segment, the Universal Record for the booking must be retrieved by Universal API to ensure that all of the booking data is current on the system.

2. Send UniversalRecordModifyReq/UniversalModifyCmd to delete one or more reservations.

3. AirDelete and PassiveDelete are used to delete air and passive segments. For each element:

   • @ReservationLocatorCode identifies the PNR with the segments that you want to delete.

   • @Element indicates the type of segment to be deleted.

   • @Key from the PNR uniquely identifies the specific item to be deleted based on the unique key assigned to that segment.

   • @BookingTravelerRef is required for air segments to identify the primary traveler for an air segment. This reference is cross-checked with the Reservation Locator Code by Universal API.

   Note: HotelDelete and VehicleDelete can be use to delete data within a booking, such as loyalty card information, but cannot be used to delete entire hotel/vehicle segments. HotelCancelReq and VehicleCancelReq, respectively, must be used to deleted booked segments.

4. To cancel and rebook a segment, use a single request to add the new segment along with the request to delete an existing segment. For example, to cancel and rebook an air segment, use a single request with an AirAdd element request and an AirDelete element.

5. Use AirDelete, HotelDelete, and VehicleDelete to delete loyalty card information if the loyalty card was added or updated in the Universal Record, even if that segment type is not included in the Universal Record.

6. A single request can contain multiple modifications. For example, if three phone numbers are added to the Universal Record, three instances of UniversalModifyCmd must be sent. Or, if a hotel segment is added and a vehicle segment is deleted, two instances of UniversalModifyCmd must be sent to accommodate each change.

7. The modified Universal Record is returned in UniversalRecordModifyRsp with the refreshed Universal Record data.

Exceptions

Galileo

• Universal API does not have a discrete equivalent to an end transact (PNRBFEnd). When a created, modified or canceled booking is submitted, Universal API internally processes the end transact as part of the request. There is also no equivalent functionality to PNRBFIgnore.

ACH

• Air segments booked through most ACH carriers cannot be canceled because these segments are ticketed and paid when they are booked. If a cancelation is requested, an error is returned for all ACH air segments.

Depending on the supplier, ACH air segments in the Universal Record may be either refunded or exchanged.

RCS

• Rails segments RCS cannot be canceled because these segments are ticketed when they are booked. If a cancelation is requested, an error is returned for all rails segments.

Depending on the supplier, RCS rails segments in the Universal Record may be either refunded or exchanged.