Dividing Universal Records

The Universal Record (UR) identifies a traveler's entire booking file, including traveler information as well as any booked travel segments, such as air or rail reservations.

Provider Reservation Divide functionality is currently supported in Universal API only for Galileo (1G), Apollo (1V), and Worldspan (1P). Airline Content Hub (ACH) does not support this functionality.

The ProviderReservationDivide service allows users to:

• Create a new Universal Record when a PNR is divided inside a Universal Record. This functionality is also known as a Split PNR.

The information for the booking traveler (such as Address, Phone, Email, SSR, OSI) is copied and synchronized from the old UR to the new UR. A General Remark is returned in both the original and the new UR that includes both the original and new record locator codes, as well as notification of the divide.

• Import a new PNR from the provider system if a Universal Record is retrieved in Universal API which contains a PNR that was divided on the provider system.
• Import a PNR from the provider into an existing UR.
• Import the resulting divided PNR into a new Universal Record.

Note: A Universal Record in Universal API or a PNR on the provider can be divided only if it contains air segments.

The ProviderReservationDivide service mostly functions the same in Galileo and Apollo:

• Electronic ticket records are divided into two Universal Records based on the Travelers in the respective PNR. The Parent PNR remains in the Parent UR and the Child PNR becomes part of a new UR.
• Travelers divided from the Parent PNR into the Child PNR lose the association with the Parent PNR, but the Parent Universal Record (UR) still contains the original Travelers regardless of the divided PNR.

The one difference when using the ProviderReservationDivide service in Galileo and Apollo is:

• Dividing a Provider Reservation in Galileo cancels the Stored Fares, but in Apollo the Stored Fares are retained.

Split/Divide functionality was added for Worldspan (1P) with Universal v43.0. Release 17.4

Request

A PNR can be divided by traveler inside the Universal Record using the ProviderReservationDivideReq request. For the divide request to be successful, a Provider Reservation must have at least two, and no more than nine, passengers.

The request should include: 

• Universal Record locator and its version.
• Provider Locator Code.
• Provider Code.
• BookingTravelerRef, which can repeat from 1-8, based on the number of travelers to be divided.

Response

A PNR Divide response is returned in ProviderReservationDivideRsp and includes:

• Parent Provider Reservation Info, including:
• The previous Universal Record Locator (Parent Universal Record).
• The original Provider Locator Code (Parent PNR).
• Travelers included in original Parent PNR.
• Provider Code.
• Child Provider Reservation Info, including:
• Universal Record Locator (Child UR).
• New Provider Locator Code (Child PNR)
• Travelers included in the divided Child PNR.
• Provider Code.

When a new Universal Record is created during the PNR Divide, if the split Booking Traveler(s) have SSR(s) DOCS/DOCO/DOCA with @ProfileID and @ProfileSecureFlightDocKey for the Child Universal Record, then Universal API copies the ProfileID and ProfileSecureFlightDocKey to the new UR.