Block Defaults for OXI

The following are recommended block default settings.

Table 23-2 Block Defaults for OXI

Block Defaults	Description
Block Rate Code	Select a rate code that has all of the configured room types for the property.  Since rates can be subject to restrictions that either close the rate and or room types depending on hotel occupancy, we strongly suggest making a ‘OXI Default’ group rate code and insert this value. This rate code is to be setup with all viable room types and a single rate detail, at $0.00, that has all room types linked to it. If proper revenue/ADR is a factor set a rate amount instead. Remember to include the PM room type as groups require this before booking reservations. This rate code should not be subject to restrictions as other rates are. If CRS allotted groups are setup for rates that are flagged restricted or out of inventory on the hotel side, this default is used to get the group inserted. Warnings in OXI alerts hotel users that the allotment was inserted, the rate was not available and the default was taken instead. Thus allowing the hotel to update the group accordingly. To see any warnings where a default was substituted then OXI offers a warnings report.
Block Status	OXI shows only the deductible block status types in this list of values as all received blocks from external systems are automatically considered deductible. This is a crucial element for the creation of a block and has to be set.
Block Owner	This is no longer mandatory but depending on the OPERA function Generic > Owner. If this is flagged, a block owner must be set in order to update the block in OPERA.
Destination Code	When processing a Canceled, Lost or Turndown message the destination code can be matched to the code used as the default in the OXI Block Defaults tab. If no match is found then the OXI default, if defined, can be applied. If a Block Destination Code conversion is active, then OXI tries to convert to the received value: If a conversion record found, the converted value is used to match against OPERA values. If a conversion record not found, the value as received from the message to match against OPERA values. If the Destination Code sent in the message matches with an OPERA Destination Code, the matched value is applied. If the Destination Code sent in the message does NOT match with an OPERA Destination Code, then OXI checks for a default: If a default Destination Code is defined, the default value is applied. If a default Destination Code is not defined, the field is left blank.