Type : Complex Element |
Definition |
The OpenTravel Hotel Cache Change Notification message set allows a hotel supplier to push their changed hotel rates and availability information to a trading partner that caches their hotel rates and availability information and have the trading partner send an acknowledgement message that they received the information.
Note that this message set is designed to allow the trading partner to receive the changed rates and availability information from the supplier so the trading partner can create a subsequent targeted Hotel Availability Request message that only requests the specific supplier data that has changed and needs to be updated in the trading partner cache.
Hotel Cache Change Notification Request information includes:
-Point of sale information for the requestor
-Unique identifier information that allows trading partners to uniquely identify each Hotel Cache Change Notification Request message for transaction tracing purposes
-Destination system information that specifies a receiving system for the message information
-Cache change information-which specifies what hotel supplier data has changed and should be updated in the trading partners system via a subsequent OTA_HotelAvailRQ message-including:
----Chain, brand and hotel codes
----The start and end date of information that should be updated in the cache for the associated @HotelCode and an optional "change date mask" that indicates if there are changes in all or a portion of the returned date range; including Length of stay that indicates how many days of availability from start date should be shopped; and Full Pattern Length Of Stay to indicate which days from start date should be shopped
----Other changed product details, including rate plan and promotion details (Defined in file OTA_HotelCacheChangeNotifRQ.xsd , or a file it imports) |
Elements | |||
CacheChangeInfo | Information that has changed and should be updated in the cache via an OTA_HotelAvailRQ request message.Information that has changed and should be updated in the cache. | ||
DestinationSystemCodes | Defines a system to which information is to be provided.A collection of DestinationSystemCode. | ||
POS | Information about the message initiator.Point of Sale (POS) identifies the party or connection channel making the request. | ||
UniqueID | The unique identifier element allows the trading partners to uniquely identify each HotelCacheChangeNotif message, for tracing of transactions.An identifier used to uniquely reference an object in a system (e.g. an airline reservation reference, customer profile reference, booking confirmation number, or a reference to a previous availability quote). |
Attributes | |||
Attribute Group : OTA_PayloadStdAttributes | |||
AltLangID | The alternate language for a customer or message encoded as ISO 639-3. | ||
CorrelationID | Allows end-to-end correlation of log messages with the corresponding Web service message throughout the processing of the Web service message. | ||
EchoToken | A reference for additional message identification, assigned by the requesting host system. | ||
PrimaryLangID | The primary language preference for the message encoded as ISO 639-3. | ||
RetransmissionIndicator | When true, indicates the message is being re-sent after a failure. | ||
SequenceNmbr | The sequence number of the transaction assigned by the sending system for ordered message processing or message resynchronization. | ||
Target | Test or Production target system indicator. | ||
TargetName | The name of the Test or Production system. | ||
TimeStamp | ISO 8601 encoded timestamp indicating the creation date and time of the message. | ||
TransactionIdentifier | Unique identifier to relate all messages within a transaction (e.g. this would be sent in all request and response messages that are part of an on-going transaction). | ||
TransactionStatusCode | This indicates where this message falls within a sequence of messages. | ||
Version | The OpenTravel message version indicated by a decimal value. |