Modifying Traveler Information in a Universal Record

An existing Universal Record data can be modified to add, delete, or update data for general record and traveler data. This data includes Booking Traveler information, remarks, links to other Universal Records, and agency identification and service fees.

Request

Before a UR can be modified, it must first be retrieved. After the UR is retrieved, UniversalRecordModifyReq/UniversalModifyCmd in the UniversalRecordModifyService is used to modify Universal Record data for traveler information, general UR information, and segment-related data.

Adding, deleting, or updating existing non-segment data is performed through the following child elements:

• UniversalAdd, which adds a Booking Traveler and Remark to a Universal Record, and can apply a profile.

• UniversalUpdate, which updates existing Booking Traveler data or general UR data in a Universal Record, and can update an existing applied profile.

• UniversalDelete, which deletes Booking Traveler, an applied profile, or general UR data from a Universal Record. See Canceling an Entire Journey (UR) and Canceling Travel Segments via the UR for more information on deleting Universal Records or travel segments.

Adding Universal Record Data

The UniversalAdd child of UniversalModifyCmd is used to add a traveler or generic data to a Universal Record.

• General Remark

• Accounting Remark

  Note: At this level, General and Accounting Remarks associated to the entire Universal Record. However, remarks can also be associate to a specific air, vehicle, or hotel, rail, or passive segment.

• XML Remark

• Booking Traveler information through the BookingTravelerInfo child:

  • Email

  • Phone Number

  • Address

    Note: Delivery addresses for ticketing are modified through the air segment.

  • Applied Profile

    An Applied Profile can be added to a Traveler in an existing Universal Record via BookingTravelerInfo/@AppliedProfile.

    When adding a profile, AppliedProfile @Key is optional. However, BookingTravelerInfo @Key is required. See the Durable Keys topic.

• Infant In Lap

  An Infant in Lap passenger type can be added to an existing Travelport Universal Record (UR) using UniversalRecordModifyReq/UniversalModifyCmd/UniversalAdd/BookingTravelerInfo.

  The following information is required in BookingTravelerInfo:

  • @TravelerType=INF (If @TravelerType is not INF, an error is returned.)
  • BookingTravelerName
  • DOB or NameRemark

  The Universal Record is then priced and ticketed in Universal API as currently occurs. The UR History is updated to show the addition of the INF Passenger Type Code.

• In TravelInfo, the trip name and trip purpose can be added. These traveler details are local to Universal Record and are not exported to any external system.

• Review bookings (Q-Minders) are a provider functionality that issues reminders to agents for any pending tasks that must be done by a specific date and time. The PNR and the reminders are put into the agency queue on the date and time specified in Review Booking.

 

Updating Universal Record Data

The UniversalUpdate child of UniversalModifyCmd is used to modify existing traveler data or generic data in a Universal Record.

Multiple Updates

Each addition, deletion, or update to the UR information requires a separate UniversalModifyCmd request. 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.

Deleting Universal Record Data

The UniversalDelete deletes Booking Traveler, an applied profile, or general UR data from a Universal Record. See Canceling an Entire Journey (UR) and Canceling Travel Segments via the UR for more information on deleting Universal Records or travel segments.

 

Exceptions