Send and Receive Dependencies for the V3.X Property Interface

Certain business rules apply to the types of information that can be passed through the Interface in regards to restrictions and oversell policies. The following table depicts this list for both the FTCIS/FTCRS and the PMS. The Interface is only allowed to upload and download this information when using the lowest denominator.

ORS Restrictions Exist on the Following Levels

Restriction levels at ORS	Restriction levels at PMS	Supported by the INTERFACE
House	House (1)	(4)
Room class	Room type (2)	Room type (close and LOS only)
Room category		(4)
Rate class		(4)
Rate tier		(4)
Rate category	Rate category* (1)	(4)
Rate code	Rate code	Rate code

*Requires that the parameter rcat_avail to be activated in PMS.

Explanation of Business Rules for ORS

In the PMS you can assign restrictions on the rate category, rate code, room type and house level. At the ORS, the restriction will only be set at those corresponding levels. Any restrictions created in ORS and sent to the PMS that are not compatible will be failed in OXI_HUB interface with appropriate warnings to alert you regarding reason for failure.

PMS by default supports only the open/close room type restriction. If the parameter p_rtavail is activated it also supports LOS by room type.
ORS can handle multiple restrictions attached to a rate code. In the event of multiple restrictions the highest restriction will prevail that is sent from the PMS.
If you make restrictions at the ORS on any of these levels, the Interface sends a corresponding restriction message for any of the attached rate codes. Thus, in the PMS, that restriction is attached to all rate codes.
A user in ORS can set a date range for Opening previously Closed House, Rate code, Rate Category or by Room Type restrictions. Multiple messages by Rate Category or by Rate Code will be sent for the date range affected. PMS will be able to update the Availability grid accordingly.