GenHTNG - Inventory Count
- Stephen Day
- Amanda Milam
- John West
Overview
The Inventory Count Notification message notifies a booking source of the amount of inventory available at a specific hotel property. It allows the Property Management System and CRS to synchronize the number of inventory items available for sale between them.
When a new hotel is opened for the first time, the Inventory Notification message would be used to supply the reservation systems with descriptions of rooms in the hotel. The Inventory Count Notification is used to send base inventory levels by inventory code, (e.g., room type code) to establish the physical inventory count. An Inventory Notification should always precede an Inventory Count Notification to establish the existence of inventory codes in the reservation system.
The physical inventory is the basis by which availability is determined. However, additional calculations figure into assigning the inventory counts for availability. Availability is a commitment to sell a room at a specific rate or plan. Since the same rooms may be sold under different rate plans, a system may carry a discrete inventory or an inventory count in association with different rates. The superset of inventory may be greater than the physical count, with the actual number of rooms counted down when they are sold.
The Inventory Count Notification message can be used to communicate how many rooms are available to sell during a specific period to revenue management systems. A reservation system may choose not to synchronize with actual inventory numbers but rather with a threshold. Properties and booking sources need to agree on common thresholds, whether they are derived from virtual or real inventory, in addition to a way to accommodate overbooking.
Supported Operations
The PMS uses this message to update the CRS for property level inventory changes. (Sample 1)
The message has room type data.
The message has no rate plan data.
Business Rules
This message is only sent from the PMS to the CRS.
The InvTypeCode needs to exist in the CRS.
OTA_HotelInvCountNotifRQ Elements & Attributes
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 |
|
@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 |
|
@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 6 Out of order 16 Group authorized 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. |
|
OTA_HotelInvCountNotifRQ Sample Inventory Update Message
<OTA_HotelInvCountNotifRQ xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05/OTA_HotelInvCountNotifRQ.xs d" Version="2.000" TimeStamp="2021-12-20T21:02:59+08:00" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Inventories HotelCode="SAMPLE">
<Inventory>
<StatusApplicationControl Start="2021-12-24" End="2021-12-25" InvTypeCode="ChainRoom2"/>
<UniqueID Type="16" ID="1"/>
<InvCounts>
<InvCount CountType="1" Count="20" />
<InvCount CountType="99" Count="10" />
</InvCounts>
</Inventory>
</Inventories>
</OTA_HotelInvCountNotifRQ>OTA_HotelInvCountNotifRS Elements & Attributes
Element | @Attribute | Num | Description/Contents | Origin | Value |
OTA_HotelInvCountNotifRQ | 1 | Root element of the message. |
|
@EchoToken | 0..1 | Optional |
|
@TimeStamp | 1 | Time of the transaction. |
|
@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_HotelInvCountNotifRS / Success | 1 | This is the annotation that the availability request was received successfully. It could be combined with warning messages if some of the messages in the |
|
OTA_HotelInvCountNotifRS / Warnings | 1..n |
|
|
@ Type | 1 | Refers to OTA EWT list (error warning type). |
|
@ Code | 0..1 | Optional. Refers to OTA list ERR. Should be used wherever possible |
|
@ RecordID | 0..1 | If the receiving system can identify within a batch of availability status messages which specific message failed, the UniqueID of the message should be |
|
OTA_HotelInvCountNotifRS / Errors | 1 | Errors are returned if the request was unable to be processed. |
|
@ Type | 1 | Mandatory in OTA. Refers to OTA EWT list (error warning type). |
|
@ Code | 0..1 | Optional. Refers to OTA list ERR. Should be used wherever possible |
|
@ RecordID | 0..1 | If the receiving system can identify within a batch of availability status messages which specific message failed, the UniqueID of the message should be reported here. |
|
OTA_HotelInvCountNotifRS Sample Inventory Response Message
<OTA_HotelInvCountNotifRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.opentravel.org/OTA/2003/05" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_HotelInvCountNotifRS.xsd" TimeStamp="2004-05-01T06:39:09" Target="Production" Version="1.002">
<Success/>
</OTA_HotelInvCountNotifRS>