Hotel Complete Availability returns all available booking codes (room rates) for a single hotel property.
This task is used to request Complete Hotel Availability for one property using a five-character RoomMaster property ID.
Transaction Name:
HotelCompleteAvailability_10_0
Can any other transactions perform this same task?
All previous HotelCompleteAvailability transactions will all accept a request for and return a response to a specific property availability request. All of these procedures handle earlier versions of the HOC request / response with information added for each new version. Therefore, the requests and responses will be slightly different from each other.
Can this task be performed in a sessionless environment?
Sessioned and sessionless requests are both supported.
Are the request and response identical on both the Apollo and Galileo systems?
Transactions on Apollo and Galileo are identical.
Industry-specific knowledge required to understand this task:
The end user need only understand the multiple rates available within the hotel industry.
Special limits or distinct restrictions to the input data.
There are no limits or restrictions on input data.
Prerequisite tasks:
There are no prerequisite tasks required before doing a complete hotel availability request if the RoomMaster Property ID is known. If the Property ID is not known, then a hotel availability or hotel index request should be made prior to the complete hotel availability request.
Expected responses:
The response can consist of an error response, or a complete availability response, <HotelCompleteAvailability>, which can include the following types of rates, depending on the source of the rate data:
Depending on the type of response, and the parameters of the request, additional data may be included in the response, including frequent customer data, corporate discount information, and More availability responses. Note that distinct elements are used in RoomMaster and Inside Availability More requests and responses.
See the tables in Section 3 for a detailed description of elements included in each response type.
Error and warning responses:
An error or warning response consists of a <HotelType> element with a value of "E", followed by a <HotelError> message.
In addition, <HotelIDError> can be returned in an Inside Availability response if the vendor and Property ID do not match in a <HotelID> request. A <HotelFrequentGuestError> can be returned in an Inside Availability response if the frequent customer number does not pass vendor validation.
Follow-on requests:
Often additional information is desired about the particular rules associated with an individual rate returned in the complete availability response. A hotel rules request, HotelRules_9_0, can be made using the RoomMaster Property ID, chain code, room type/rate type, and date information.
A Hotel sell request can also be made using the information returned in the complete availability response using the PNRBFManagement_7_11 transaction.
|
<HotelCompleteAvailabilityMods> |
Terminal Equivalents: |
Apollo: |
Galileo: |
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
HTC1 |
1 - 1 |
<HotelInsideAvailability> |
| HTC2 | 0 - 1 | <RoomMasterMore> | |
| HTC4 | 0 - 1 | <HotelInsideAvailMore> | |
| HACD | 0 - 1 | <HotelCorporateDiscount> | |
| HTFG | 0 - 1 | <HotelFrequentGuest> | |
| HTID | 0 - 1 | <HotelID> | |
| HTSL | 0 - 1 | <HotelSlotData> |
|
<HotelCompleteAvailability> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
| HTTR |
1 - 1 |
<HotelType> |
|
| HTPH | 1 - 1 | <HotelPropHeader> | |
| HAHS | 1 - 1 | <HtlAvailHeader> | |
| HTPR | 1 - 1 | <HotelPropertyRecord> | |
| HTRT | 1 - 1 | <HotelRate> | |
| HACD | 0 - 1 | <HotelCorporateDiscount> | |
| HTFG | 0 - 1 | <HotelFrequentGuest> | |
| HTID | 0 - 1 | <HotelID> | |
| HTC2 | 0 - 1 | <RoomMasterMore> | |
| HTC3 | 0 - 3 | <RoomMasterRate> | |
| HTAR | 0 - 3 | <HotelAlternateRates> | |
| HTC7 | 0 - 3 | <RoomMaster> |
|
<HotelCompleteAvailability> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
HTTR |
1 - 1 |
<HotelType> |
| HTPH | 1 - 1 | <HotelPropHeader> | |
| HAHS | 1 - 1 | <HtlAvailHeader> | |
| HTPR | 1 - 1 | <HotelPropertyRecord> | |
| HTVM | 1 - 1 | <HotelVendorMarketing> | |
| HACD | 0 - 1 | <HotelCorporateDiscount> | |
| HTFG | 0 - 1 | <HotelFrequentGuest> | |
| HTID | 0 - 1 | <HotelID> | |
| HTRT | 1 - 1 | <HotelRate> | |
| HTAR | 0 - 3 | <HotelAlternateRates> | |
| HTC4 | 0 - 1 | <HotelInsideAvailMore> | |
| HTRD | 1 - 3 | <HotelRateDescription> | |
| HTFE | 0 - 1 | <HotelFrequentGuestError> | |
| HTIE | 0 - 1 | <HotelIDError> |
|
<HotelCompleteAvailability> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
HTTR |
1 - 1 |
<HotelType> |
| HAHS | 1 - 1 | <HtlAvailHeader> | |
| HTPH | 1 - 3 | <HotelPropHeader> | |
| HTPR | 1 - 3 | <HotelPropertyRecord> | |
| HACD | 0 - 1 | <HotelCorporateDiscount> | |
| HTFG | 0 - 1 | <HotelFrequentGuest> | |
| HTID | 0 - 1 | <HotelID> | |
| HTC8 | 1 - 1 | <HotelAlternateAvailability> | |
| HTCR | 1 - 1 | <HotelCurrency> | |
| HTSL | 0 - 1 | <HotelSlotData> | |
| HTFE | 0 - 1 | <HotelFrequentGuestError> | |
| HTIE | 0 - 1 | <HotelIDError> |
|
<HotelCompleteAvailability> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
HTTR |
1 - 1 |
<HotelType> |
| HTER | 1 - 1 | <HotelError> |
HotelCompleteAvailability_10_0_1