*Archived Transaction*
SegmentCancel_7_0 allows for the removal of one or more segments from the itinerary. This transaction can also be used to cancel the entire PNR/BF by canceling all segments. To use this transaction, one or more segments need to exist in the booking.
If a room reservation is no longer needed, the hotel segment can be canceled using SegmentCancel_7_0 or PNRBFReservationModify_5_0_2. The cancellation request notifies the vendor that the room can be released back into inventory. Typically, the vendor will acknowledge the transaction by sending back a cancellation number.
Canceling a hotel segment is particularly important if a credit card number was used to guarantee the room. Most hotels have strict cancellation policies, and require the room be released by a specific time, one to two days prior to the check-in date. Late cancellation can result in a "no-show" charge to the credit card used to guarantee the room.
Before the air segment is canceled, the PNR/BF containing the booking must first be retrieved using PNRBFReservationModify_5_0_2. This cancellation must be followed by an End Transact, such as in the PNRBFEnd_9_0, in order for any changes to take affect.
If a car rental is no longer needed, for whatever reason, the car segment can be cancelled using SegmentCancel_7_0 or PNRBFReservationModify_5_0_2. Before the air segment is canceled, the PNR/BF containing the booking must first be retrieved using PNRBFReservationModify_5_0_2. Only then can the cancellation request be made. The cancellation request informs the vendor that the car can be released back into inventory. The vendor may acknowledge the transaction by sending back a cancellation number.
This function must be followed by an End Transact, such as in the PNRBFEnd_9_0, for changes to take affect.
Changes to a travel itinerary are not uncommon, and in some instances (such as business travel), changes to the itinerary are common. Flights, dates, even destinations can undergo several changes between booking and ticketing.
Itinerary segments are numbered sequentially, and these same numbers are used to cancel one or more segments. When multiple itinerary segments are canceled separately, they should be referenced in ascending order. For example, the lowest numbered segment should be indicated first, followed by the second to the lowest segment, and so forth.
Before the air segment is canceled, the PNR/BF containing the booking must first be retrieved using PNRBFReservationModify_5_0_2. To implement the cancellation, the function must be followed by an End Transact, such as PNRBFEnd_9_0.
Canceling an entire PNR/BF record implies canceling segments in the itinerary and canceling the stored fare (if air segments were included in the PNR/BF). Prior to canceling the record, retrieving the fare basis code using FareQuoteRulesDisplay_8_0 can indicate any penalty associated with canceling a ticketed fare.
Explicit cancellation of the stored fare is unnecessary. When the final air segment is canceled the CRS detects that the stored fare has been orphaned and deletes it automatically during the end transact procedure.
Step |
Process |
Description |
|
1 |
Rules Display |
OPTIONAL: Use fare basis code to display penalty for cancellation. |
|
2 |
Segment Cancel (FF) |
Cancels all segments for air, car, hotel, SSRs, and seats. |
The "FF" segment number submitted in the SegmentCancel_7_0 is a command to cancel all segments in the itinerary.
The process described above will cancel the reservation; however, it does not necessarily delete the PNR/BF record on the CRS. The name, phone, and other fields will still remain after the end transact command has been executed.
The CRS however keeps historical information pertaining to the segment dates even after they are canceled. More specifically, the CRS has a "garbage collection" routine that scans the system and deletes PNR/BF records 24 hours to 48 hours after the latest segment date that has been canceled or expired. Therefore, PNR/BF records can be retrieved via the Record Locator ID for a period of time after the reservation has been canceled or before it has expired.
Note on Re-Sequenced Segments:
In certain configurations, the commit command re-sequences the segments stored on the CRS. Therefore, if two (2) air segments, one (1) car segment, and one (1) hotel segment are sold in sequential order and then end transacted, the car segment may randomly change from position #3 to position #4. As a result, the PNR/BF may need to be retrieved after it is and processed to determine the segment type and position.
Contact your customer representative to determine if re-sequencing is applicable in your instance.
Before the air segment is canceled, the PNR/BF containing the booking must first be retrieved using PNRBFReservationModify_5_0_2 or AgencyPNRBFDisplay_7_5. To implement the cancellation, the function must be followed by an End Transact, such as PNRBFEnd_9_0.
SegmentCancel_7_0 and PNRBFReservationModify_5_0_2 both support canceling an air segment. SegmentCancel is generally used for sessioned environments, while PNRBFReservationModify_5_0_2 is typically used in sessionless environments.
Note: Changes to an existing PNR/BF are not necessarily itinerary changes, but can be any sort of modification or addition to the record itself.