|
|
|
Business Rules for Sending and Receiving Blocks Between V3 and ORS
Allotments affecting availability in CRS and PMS are transferred.
In ORS an allotment code with a block status of INITIAL will transfer to PMS as INITIAL and will only takes rooms from availability if the reservation type sent from ORS is definite. The OXI parameter UPD_DED_ONLY determines if both initial and active will be sent to PMS.
In ORS allotment code with a block status of ACTIVE will transfer to the PMS as OPEN FOR PICKUP and only take rooms from inventory if the reservation type sent from ORS is definite.
In ORS as soon as an allotment is made definite reservations can be made against it.
In PMS an allotment takes a room from availability as soon as the reservation type is definite.
In PMS you can only book against an allotment when it is (open for pickup).
ORS will send the Elastic lag set to Y only if the user selects the Elastic flag on the block header.
If the ORS sends down either Cut Off Date or Cut Off Days; the Cut Off Date/Days will be downloaded to the PMS. After the cutoff date, the PMS night audit procedure automatically releases all non-sold rooms, the Interface uploads and also releases the non-sold rooms at the ORS.
In PMS an allotment code with a block status of INITIAL will transfer to ORS as INITIAL and will only takes rooms from availability if the reservation type sent from PMS is deduct. The V3 parameter Upload Initial Phase/Tentative reservation Type determines if both initial and open for pick up will be sent to ORS.
The Interface only supports the (enhanced group/block) functionality in the PMS.
Allotments headers created at PMS can be changed at the CRS if the OXI parameter EXTERNAL_LOCKED_YN is set to Y.If this parameter is set to N the block in ORS is view only.
Allotments headers created at CRS can be changed at the PMS when the ORS sends control to the PMS.
If a PMS user is attaching profiles to a CRS created allotment header, the profiles will be uploaded when another change is made on the block header.
Any packages attached to an ORS created allotment will be attached to the block in PMS.
The CRS can pick up reservations for PMS created allotments.
The PMS can pick up reservations for CRS created allotments.
If elastic functionality is used on the PMS, the ORS allotment will also be elastic.
If the ORS group profile is required and if no profile is attached, the CRS system will have a default profile that the Interface will use with the allotment.
In the ORS if a rate code is required, PMS allotments uploaded without a rate code will be inserted with a default rate code set in the OXI defaults for block rate code
Cutoff day/dates are uploaded only if a value is inserted in the PMS.
In PMS after cutoff days/dates, the night audit automatically releases the remaining rooms (if any). In ORS the same process applies. Business Rules for Sending and Receiving Blocks
Allotments affecting availability in CRS and PMS are transferred.
In ORS an allotment code with a block status of INITIAL will transfer to PMS as INITIAL and will only takes rooms from availability if the reservation type sent from ORS is definite. The OXI parameter UPD_DED_ONLY determines if both initial and active will be sent to PMS.
In ORS allotment code with a block status of ACTIVE will transfer to the PMS as OPEN FOR PICKUP and only take rooms from inventory if the reservation type sent from ORS is definite.
In ORS as soon as an allotment is made definite reservations can be made against it.
In PMS an allotment takes a room from availability as soon as the reservation type is definite.
In PMS you can only book against an allotment when it is “open for pickup.”
ORS will send the elastic flag set to Y only if the user selects the elastic flag on the block header.
If the ORS sends down either cut off date or cut off days the cutoff date/days will be downloaded to the PMS. After the cutoff, date the PMS night audit procedure automatically releases all non-sold rooms, the Interface uploads and also releases the non-sold rooms at the ORS.
In PMS an allotment code with a block status of INITIAL will transfer to ORS as INITIAL and will only takes rooms from availability if the reservation type sent from PMS is deduct. The V3 parameter Upload Initial Phase/Tentative reservation Type determines if both initial and open for pick up will be sent to ORS.
The Interface only supports the “enhanced group/block” functionality in the PMS.
Allotments headers created at PMS can be changed at the CRS if the OXI parameter EXTERNAL_LOCKED_YN is set to Y. If this parameter is set to N the block in ORS is view only.
Allotments headers created at CRS can be changed at the PMS when the ORS sends control to the PMS.
If a PMS user is attaching profiles to a CRS created allotment header, the profiles will be uploaded when another change is made on the block header.
Any packages attached to an ORS created allotment will be attached to the block in PMS.
The CRS can pick up reservations for PMS created allotments.
The PMS can pick up reservations for CRS created allotments.
If elastic functionality is used on the PMS, the ORS allotment will also be elastic.
If the ORS group profile is required and if no profile is attached, the CRS system will have a default profile that the Interface will use with the allotment.
In the ORS if a rate code is required, PMS allotments uploaded without a rate code will be inserted with a default rate code set in the OXI defaults for block rate code
Cutoff day/dates are uploaded only if a value is inserted in the PMS.
In PMS after cutoff days/dates, the night audit automatically releases the remaining rooms (if any). In ORS the same process applies.
See Also
