Task: Hotel Description with Chain Code

Hotel description requests obtain information for hotel chains and properties, regardless of availability for a location. Information from this entry can be tailored based upon the input of keywords. A menu switch element in the request also provide hotel description keywords for use in a description request.

Section 1: Short Answer

Transaction Name:

HotelDescription_7

Can any other transactions(s) perform this same task?

No.

Can this task be performed in a sessionless environment?

Sessioned and sessionless transactions are both supported.

Are the request and response identical on both the Apollo and Galileo systems?

The Apollo and Galileo request and response are identical.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

The end user should understand the difference between chain-level and property-level requests since both are supported by the hotel description request.

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

The chain and/or property must be defined in the RoomMaster database.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

This task document shows, in section three, the necessary elements for a Chain Code request as part of the <HotelDescMods> element.

Prerequisite tasks:

There are no prerequisite tasks.

Expected response:

All responses consist of a header, <HotelDescHeader>. If the response is not an error, one or two <HotelDescMenuItems> elements and/or a <HotelDescKeywordText> element are returned.

Type of responses:

R = Chain-level generic data. The full response consists of a header <HeaderDesc> and <RespType>, and chain-generic data, <ChainBrochure>. Optional keyword menu records are returned in <KeywordList> if the <ReqHeader> / MenuSwitch> field is set to “Y”.

Error and warning responses:

Chain code and Property ID are mutually exclusive. When both chain code and property ID are entered in single Hotel Description request, an error response is generated.

E = Error - <RespType> and <HotelError> elements are returned.

Invalid Chain Code – invalid vendor chain code entered in Chain Code field
Invalid Arrival Date – invalid arrival date entered in Arrival Date field
Invalid Menu Switch – invalid value entered for menu switch field

Additionally, view the Hotel Error Messages table to see hotel errors.

Follow-on requests:

There are no follow-on requests. A <GetMoreOpt> "more token" can be used to make an additional request if more description data is available.

Section 3: Tables

Request (Input) Tags

<HotelDescMods>

Terminal Equivalents:

Apollo:
HOD

Galileo:
HOD

Ordering	KLR	Min/Max	XML Tag
	HD01	1 - 1	<ReqHeader>

Response (Output) Tags

<HotelDescHeader>

Ordering	KLR	Min/Max	XML Tag
A	HDTR	1 - 1	<RespType> This displays in all HOD responses
	HDHD	1 - 1	<HeaderDesc>
	HDCB	0 - 1	<KeywordList> Displays if <RespType> / <RespInd> = 'R'
	HDKL	0 - 1	<KeywordList> Displays if <ReqHeader> / <MenuSwitch> = Y. Precedes <KeywordDesc>. Does not display if <HeaderDesc> / <MenuItems> = 0
	HDGM	0 - 1	<GetMoreOpt>
	HTER	1 - 1	<HotelError> Displays only if error response.

Related Samples

HotelDescription_7_s3

HotelDescription_7_s4

Additional Information

See the following topics for additional information for hotel processing.

View the Hotel FAQ for answers to the frequently asked questions regarding Hotel Availability, Hotel Complete Availability, Hotel Rules, Hotel Index, and Hotel Description.
View the Hotel Codes table to see a list of codes for hotel amenities, property types, rate categories, property location, and transportation.
View the Hotel Sell Optional Field Data table to see the list of options for hotel sell.
View the Hotel Error Messages table to see hotel errors.
In the main help system, see the Travel Processes > Hotel Processes topic to see the process flow for all tasks related to hotel processing.