Modifying Optional Hotel Data

Optional data includes: special requests, membership program numbers, and rate information. This type of data often changes between the original booking and the actual date of travel. This task allows existing data to be modified, or new data to be added without rebooking.

Itineraries will often change between original booking and actual travel. Hotel segments can have existing data modified or new optional data added. Although all this data is optional, it does provide supplementary details to the hotel booking that can help both the traveler and the vendor.

Request

The PNR/BF that was used to book the original hotel segment must be retrieved be for optional data to be changed. PNRBFManagement_# can be used to retrieve the PNR/BF. GWS customers can also use Itinerary eBL to retrieve a PNR/BF.

The request requires the segment number, based on the order of all segments in the PNR/BF, and the new or modified optional data in the <HtlModifyOptionalDataMods> element in PNRBFManagement_#. An end transact is also required to commit the changes to the CRS.

Response

The response includes the standard booking response with the confirmation number.

Recommended Use

When a traveler wants to add or modify optional data to a booked hotel segment.

Technical Overview

Associated Transactions

For more information about the functionality of this task, see the latest version of the PNRBFManagement transaction: In the TOC, select XML Select Service > Transactions > PNRBFManagement_#. This transaction is also used to create PNRs/BFs, and to sell hotel segments.