Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Element | @Attribute

Num

Description/Contents

Origin | Value

OTA_HotelInvCountNotifRQ

 1  

Root element of the message.  

   

@EchoToken  

 0..1  

   

Unique number for every transaction. Must be returned as part of the response to this message

@TimeStamp  

 1  

Time of the transaction.

Time the message was assembled

@Version  

 1  

Version is a mandatory attribute in OTA; therefore, it must remain Mandatory in HTNG to be able to use the same message.

1.000  

OTA_HotelInvCountNotifRQ / POS / Source  

 1  

Optional. This holds details regarding the requestor. It may be repeated to also accommodate the delivery systems.

Not mapped

OTA_HotelInvCountNotifRQ / POS / Source / RequestorID

 1  

The system sending the request message. An identifier of the entity making the request (e.g. ATA/IATA/ID number, Electronic Reservation Service
Provider (ERSP), Association of British Travel Agents (ABTA)).

   

@Type  

 1  

Type attribute uses the OTA code list UIT. For example, type 22 – ERSP (Electronic reservation service provider).

   

@ID  

 1  

ID is used for the name or ID of the requestor. For example, SynXis.

   

OTA_HotelInvCountNotifRQ / Inventories

 1  

A collection of Inventory. Hotel identification information are the attributes of this element.

   

@ChainCode  

 0..1  

Optional. The chain code for which the availability request is for.

   

@BrandCode  

 0..1  

Optional. The Brand Code for which the availability request is for.

Not mapped  

@HotelCode  

 1  

This is the code of the property whose availability is being requested.

Property Code of transaction 

OTA_HotelInvCountNotifRQ / Inventories / Inventory  

 1..n  

This is the inventory information for a given rate plan, room type, date, etc

   

OTA_HotelInvCountNotifRQ / Inventories / Inventory / StatusApplicationControl

 0..n  

Information on what the InvCountNotif Message applies to (i.e. the combination of inventory and/or rate codes) and the period of application.

   

@Start, @End  

 1  

The first and last dates for which the availability update is being sent

   

@Mon,@Tue,@Weds, @Thur,@Fri,@Sat,@Sun

 0..1  

The day of the week indicators are used to communicate which days of the week the update pertains to. If one is sent they must all be sent.

   

 @AllInvCode  

 0..1  

When true indicates that the data transmitted is for total inventory in the hotel. This field is required if @InvTypeCode is not set.

   SHR does not support AllInvCode

 @InvTypeCode  

 0..1  

This is the room type code for which the update is being sent. This field is required if @AllInvCode= ”false” or missing. This field should not be sent if
@AllInvCode= ”true”

   

 @InvBlockCode  

 0..1  

Code that identifies an inventory block  

   

 @RatePlanCode  

 0..1  

Code that identifies the rate plan associated with an inventory block.

   

OTA_HotelInvCountNotifRQ  / Inventories / Inventory / InvCounts  

 0..1  

A collection of inventory counts.  

   

OTA_HotelInvCountNotifRQ / Inventories / Inventory / InvCounts / InvCount

 1..n  

Individual inventory count (e.g. Physical, Available, Sold, OOO, NAFS).

   

@CountType

 1  

This identifies the type of inventory count being reported. Refer to OpenTravel Code List Inventory Count Type (INV).

1 Physical
2 Definitive availability
3 Tentative availability
4 Definite sold

6 Out of order
8 Out of inventory

16 Group authorized
17 Group sold
18 Group available

99 Oversell count

AT this time, count type ‘1’ and ‘99’ are the only type supported by the CRS. Wave RMS however can also support CountType “8”

CountType 1 should represent number of remaining rooms hotel has available to sell for each room type.

If sending “99” for oversell, the amount of oversell should not also be included in the totals provided for count type”1”.

Example: Hotel has 50 physical rooms available but would like to allow an oversell of 5.

CountType=”1” Count=”50”

CountType=”99” Count=”5”

If the PMS adds available oversell to physical rooms, then only CountType=1 should be sent (CountType=”1” Count=”55”)

It is prefered to send both CountType 1 and 99 however.

@Count  

 1  

 Number of rooms of this type  

   

OTA_HotelInvCountNotifRQ / Inventories / Inventory / UniqueID  

 0  

Used in response message in the case of an error to indicate which node failed.

   

@Type  

 0  

Type refers to OTA code list UIT – nr 16 =  Reference. This is used to identify each single availability status message for error reporting purposes.

   

@ID  

 0  

ID is a unique incremental number for each availability message that identifies that specific message.

   

...