Booking a Hotel Reservation
After a hotel property and available booking code are identified, the hotel reservation can be sold. Hotel, air, and car segments are booked using the same transaction. Typically, availability and pricing are made for each of the car, air, and hotel segments in a trip. The booking requests for all segments is sent in a single transaction.
Two tasks are required to book a hotel reservation:
Selling a Hotel Segment
|
Description |
Sells (books) the hotel segment. A booking file (PNR/BF) is required to sell a hotel segment; the booking file may already exist, or may be created as part of the sell. Car and air segments for the same trip can also be sold in the same transaction as hotel segments. |
|
Request |
The required data for a hotel sell request includes the check-in and check-out dates, number of travelers, number of rooms, the affiliated hotel chain, the RoomMaster ID of the property, and the booking code for the room rate. If there is not already a PNR/BF, the sell transaction for the hotel segment must also include, at a minimum, the required data for a PNR/BF. At least one air, car, hotel, or cruise segment is required to create a PNR/BF (cruises use a separate booking transaction). |
|
Response |
The hotel sell response duplicates the request data, and also returns: a status indicator if the segment has been "Sold" or "Need", a confirmation number, rates and associated currencies, and rate change information. Text data can also be included in the response. |
|
Dependencies |
A RoomMaster Property ID for the hotel property and a booking code (room rate) must be determined and included in the request. This data is provided in a complete hotel availability response, or can be manually added in a direct sell if the user already knows the desired Property ID and booking code. Optional. A hotel rules request for the specified booking code can be made before or after the segment is sold, depending on the type of vendor participation. |
|
Recommended Use |
This task is required to sell a hotel segment. |
|
Related Topics |
Finalizing a PNR/BF
|
Description |
Commits (end transacts) the changes in the booking file (PNR/BF) to the Apollo or Galileo CRS. The hotel is not complete until the PNR/BF is end transacted. As with the booking process, any changes to a sold hotel transaction must be end transacted to the CRS to be valid. |
|
Request |
An end transact (ET) indicator specifies if the end transact is: normal, requires change of ownership for the PNR (Apollo only), queued to a pseudo city code, queued to a Galileo Preferred Agency, or should be immediately retrieved. Additional qualifier data is required, depending on the type of end transact. The individual or client application performing the end transact must also be identified. |
|
Response |
The response to a normal or queued end transact confirms a successful end transact, and returns a record locator. If the end transact specifies immediate retrieval after the end transact, the response includes all of the PNR/Booking File data. |
|
Dependencies |
The hotel segment must be sold before end transacting. |
|
Recommended Use |
This task is required to store the hotel segment data in the Apollo or Galileo CRS. Queuing is typically used for activities such as specifying ticketing dates or flagging a PNR/BF for review. Immediate retrieval is frequently used if the agent or client application wants to save the PNR/BF and then make additional changes, or to redisplay the PNR/BF data for further processing. |
|
Related Topics |
See the latest version of the PNRBFManagement transaction: In the TOC, select XML Select Service > Transactions > PNRBFManagement_#. GWS Customers Only: Booking ebL |