Modifying Hotel Bookings

An existing Universal Record data can be modified to add, delete, or update booked hotel segment data or cancel hotel segments.

Request

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 hotel segment data is performed through the following child elements:

• HotelAdd, which adds a new hotel segment (PNR) to an existing Universal Record.

• HotelUpdate, which updates an existing hotel segment in a Universal Record.

• HotelDelete, which deletes hotel segment data.

If multiple modifications are made to a Universal Record, an instance of UniversalModifyCmd must be associated with each change request.

Adding Hotel Segments

The HotelAdd child of UniversalModifyCmd is used to add a hotel segment to an existing Universal Record.

 

The required ReservationLocatorCode attribute identifies the PNR to which the travel segment is added. This ReservationLocatorCode is assigned by the provider and is distinct from the identifier for the UniversalRecord that is issued by Universal API.

Note: Form of payment information for guaranteed Hotel segments is stored locally by Universal API, rather than by the host, and changes are also captured in the UR history.

Only one of each of the following is allowed per Hotel segment:

• CorporateDiscountID
• HotelSpecialRemark

If more than one of either exists for a segment, HotelAdd cannot be invoked, and a message is returned.

Updating Hotel Segments

The HotelUpdate child of UniversalModifyCmd is used to modify an existing hotel segment in a Universal Record.

As with HotelAdd, the ReservationLocatorCode attribute is required to identify the PNR to which the travel segment is added. This ReservationLocatorCode is assigned by the provider and is distinct from the identifier for the UniversalRecord that is issued by Universal API.

Note: Form of payment information for guaranteed Hotel segments is stored locally by Universal API, rather than by the host, and changes are also captured in the UR history.

Only one of each of the following is allowed per Hotel segment:

• CorporateDiscountID. If no corporate discount exists for the hotel segment, a warning message is returned and update is not possible.
• HotelSpecialRemark. If no special request exists for the hotel segment, a warning message is returned and update is not possible.

Optional information that can be modified includes:

• HotelCommission is used to add, update, or delete hotel commission for Worldspan (1P) providers.

Deleting Hotel Segment Data

The HotelDelete child of UniversalModifyCmd is used to delete existing data from a hotel segment.

Note: HotelDelete is not currently used to cancel a hotel booking from an existing Universal Record. HotelCancelReq is used to cancel booked hotel segments. Alternately, UniversalRecordCancelReq is used to cancel the entire Universal Record, including the hotel booking.

The following data is required to delete a hotel segment or segment data:

• The required ReservationLocatorCode attribute identifies the PNR with the associated hotel segments.

• The required Element attribute indicates the type of data to be deleted. Because the Element attribute is shared by several segment types, not all enumerations are used by hotel segments.

• A Key from the PNR to uniquely identify the specific item to be deleted based on the unique key assigned to that item.

Note: A validation message is returned when a request attempts to delete information, such as HotelSpecialRequest or CorporateDiscountID, that does not exist.

Exceptions