An existing Universal Record data can be modified to add a new passive segment or delete an existing segment. Because passive segment data is external, and cannot be modified through Universal API, passive segment data can only be cancelled, and not modified, through Universal API. ™
Important! Deleting a passive segment in Universal API does not cancel the segment; deleting merely removes the information from the Universal Record. The supplier or the supplier's system must be contacted directly to cancel the actual segment that is represented as a passive segment in uAPI.
Alternatively, passive segments can be deleted through the UR rather than the PNR.
Schema
See the Cancel Passive transactions:
Request
Important! Before canceling a passive segment, the Universal Record for the booking must be retrieved by the Universal API to ensure that all of the booking data is current on the system.
After the booking is retrieved, a passive segment in a PNR can be canceled by using PassiveCancelReq in the PassiveCancelService.
Response
PassiveCancelRsp is returned.
The Universal Record is returned with the cancelled passive segment or segments. The PassiveReservation child of UniversalRecord provides the locator code for the associated PNR. If segments in more than one PNR are cancelled, multiple PassiveReservation child elements may be returned.
The TravelOrder attribute in UniversalRecord/PassiveReservation/PassiveSegment is returned against the Passive Segments to indicate their position within the UniversalRecord.
ARNK (Arrival Unknown) segments are added to the host PNR automatically wherever required, particularly for continuity breaks with the provider PNR. ARNK (Arrival Unknown) segments that are present in Galileo and Apollo provider PNRs are included in the response in the ProviderARNKSegment, to allow agents to view the exact provider PNR composition.
