Business Rules for Sending and Receiving Rates

Note: Rate Category will not be delivered for V6 properties unless Rate Category parameter and setup is done

The following general rules and restrictions apply to rates sent to and from external properties:

Business events for Rates must be set up.

To distribute rates from ORS to external properties then the ORS Rate parameter DISTRIBUTABLE RATES must be active.

If a rate is inactivated at property level the rate is kept in the ORS but the rate end sell date is put to the current business date and will not be available for booking. Existing reservations will keep the rate code but if the room type or length of stay is changed the reservation will have to rate query again and choose an active/available rate.

If a rate details are deleted at the property level the rate code will be updated in the ORS.

If the whole rate is deleted at the property level will be removed from the ORS as long as there are no active reservations attached to the rate code. If active reservations are attached the Rate Code will be left in ORS configuration but will not show in Rate Query for booking.

Rates created at the property level can be locked for local updates only if the parameter in OXI_HUB called

EXTERNAL_LOCKED_YN in OXI Parameters OXI_BLOCKS group is set to Y. If set to N, then the rate can be updated from ORS or at the external property.

Restrictions created at the ORS can be changed at the property and vice versa. ORS has more restriction capability than V6 offers for any that are not supported by V6 there will be an appropriate warning that this is not supported and the message will be FAILED accordingly.

Packages created by PMS can be changed by ORS and vice versa.

The restriction (Min. Stay Through = 1) and restriction (Max. Stay Through = 99) can be updated on the Rate Code header from either ORS or external property as long as either side does not have the OXI_HUB parameter EXTERNAL_LOCKED_YN set to Y.

The (Min.Stay Through = 1), is an OPERA default and will be inserted when any new Rate is created.

In ORS a product can be either inclusive or exclusive of the rate/stay.

In ORS a product must now be inclusive or exclusive and can no longer be both.

Packages attached to the rate code in PMS will be uploaded to the ORS.

In ORS the options (Suppress) and (Print) can be supported by OPERA, but with a V6 PMS the option of (Print) is the only option supported.

Business Rules for Sending and Receiving Rates Between External System and OPERA PMS

Rates - Handling from External System to OPERA PMS

Enhanced functionality for Rate Detail handling
Functionality based on matching internal key column in the base table.
When a match is found:
If a match is found and the inactive date is 'null' update the details records.
If the inactive date is not equal to 'null', then delete the record from the base table.
When a match is not found:
If inactive date is null; we validate the record and as long as their are no overlapping details OXI will insert the record.
If there are overlapping details, OXI will raise an 'E' error warning and fail the message.
If the inactive date is not null; OXI will raise a warning stating 'Could not find record to delete'.