CREDIT CARD SUPPRESS

PROFILE
RESERVATION
BOTH
N

-> Direction: Data both ways between external system and OPERA.

Credit Card(s) information suppressed.

Due to privacy laws, credit card(s) information will be suppressed based on following settings -

PROFILE: OXI will not include Profile Credit Card information in the outgoing profile messages and will not store Profile Credit Card information when received through messages of any type from non-opera systems.

RESERVATION: OXI will not include any reservation Credit Card information in RESERVATION messages, however Profile Credit Cards for Profiles attached to a reservation may be sent. OXI will however process reservation credit card information into OPERA.

BOTH: OXI will not include ANY Credit card information in the outgoing Reservation and profile messages and will not process any profile credit card information when received through messages of any type from non-opera systems. OXI will however process reservation credit card information into OPERA.

N: OXI will send and process all and any credit card information present.

Set Accordingly.

GENERATE XML

Y/N

-> Direction: Data both ways between external system and OPERA.

The generation of an XML message is required for all generic interfaces where no OXA adapter translates the OPERA data format into the external system specific format. Even custom interfaces with an OXA adapter (Holidex, Trust, FTCRS, Pegasus, Marsha, TLX) may benefit from XML generation as it allows users and support personnel to recognize message contents easier. Set to Y to generate an XML message from/to the external system message. Set to N to avoid the XML message creation

Set to Y for all interfaces using the XML message format. All custom OXA interfaces can be set either way.

The default setting is Y for OXI-V6, OXI-V7, OXI-OPERA

HANDLE PSEUDO ROOMTYPES

Y/N

-> Direction: Data both ways between external system and OPERA.

If this parameter is set to Y, the interface will accept and send room types flags as pseudo in the data transmission for reservations, blocks, and rates. The OXI room type conversion table will allow the selection of pseudo room types. Se this parameter to N if pseudo room types shall be suppressed from data transmission. This would be the case if the external system has no pseudo room types configured and message would lead to failures, or conversion could be setup falsely.

Set to Y for all interfaces that support pseudo room types.

The default setting is Y for OXI-V6, OXI-V7, OXI-OPERA

MULTI ROOMTYPE CONV

Numeric value

-> Direction: Data both ways between external system and OPERA.

This parameter should always be set to N in a 2- way interface bases on reasons described below. It can be used for a 1-way interface. If set to N, OXI_HUB will mandate a one-to- one room type conversion between external system and ORS to keep the inventory in balance. This is very important if the interface uses block or rate messages, as it is not possible to convert one-to-many room types for blocks and rates, and this would result in severe imbalances. You should only set this to Y for interfaces that transmit only reservations, as one-to-many room type conversion could then be allowed to give flexibility.

Note: that a one-to-many room type conversion must be very carefully considered as it can lead to differences in room type usage between the systems.

Example: ORS has only room type KING and the external system converts both KNG and QUE into KING in the OXI_HUB room type conversion table. This is possible with the conversion defaults and in this case the OPERA->external default is set to N for the record KNG<->KING and set to Y for the record QUE<->KING. If the external system sends a reservation with KNG, this will map to KING when entering ORS. If the ORS user now changes the reservation, the room type will be converted into QUE when sending to external system, as QUE is flagged as OPERA->external default in this multi-to-one room type conversion table. The result is that the same reservation exists as QUE in one system and as KING in the other, which may lead to confusion and questions.

Set to N for all 2-way interfaces.

The default setting is N for OXI-V6, OXI-V7, OXI-OPERA

PURGE NO DAYS

Numeric value

-> Direction: irrelevant as this applies to data within OXI.

The number of days that messages are kept in the OXI_HUB status tables before they are purged. The contents of these status tables can be seen on the OXI_HUB message status screen. Please consider that multi-property installations have the number of messages multiplied by properties.

Set this value to a number of days that you would still like to review old messages after their transmission.

The default setting is 10 for OXI-V6, OXI-V7, OXI-OPERA

RETRY COUNT

Numeric value

-> Direction: Data from external system to OPERA.

OXI_HUB will retry this number of times to process an incoming message if the first attempt was not successful due to, for example, a locked record. A locked record can occur when OXI tries to process a message while another user is updating this record at the same time in ORS. OXI_HUB will retry the update x number of times as defined in this parameter. This parameter is directly linked to RETRY INTERVAL.

Set this value to a number of retries that is appropriate for your operation. We recommend at least 3 times.

The default setting is 3 for OXI-V6, OXI-V7, OXI-OPERA

RETRY INTERVAL

Numeric value

->Direction: Data from external system to OPERA.

Interval in seconds between each retry that OXI_HUB will perform to process an incoming message after the first attempt failed. This parameter is directly linked to RETRY COUNT.

Set this value to an interval you feel is appropriate. We recommend 60 seconds.

The default setting is 60 for OXI-V6, OXI-V7, OXI-OPERA

SEND COMMENT WITH CONVERSION

Y/N

-> Direction: OPERA to external system.

If set to Y, non-internal comments with conversion code exist only send to external system.

If set to N, all the non-internal comments will be sent to the external system.

Internal comments will not be sent out always.

Set accordingly.

SEND VAULTED CREDIT CARD

Y/N

-> Direction: Opera to External system.

When CC vault is on, this parameter determines whether to include actual plain text credit card information or the unique id received from CC vault system in the outgoing messages.

- Set this to Y if the receiving system is vaulted and is using the same vault and understands vaulted information in the message.

- Set this to N if the receiving system is not vaulted or is using a different vault or does not understand vaulted information in the message.

Set accordingly.

The default setting is N for OXI-V6, OXI-V7, OXI-OPERA

This parameter should be set to Y only if both sides of the interface is using same vault installation for storing and retrieving credit cards.

WARNINGS AS TRACES

Y/N

-> Direction: Data from external system to OPERA

Warnings that occur when reservations are sent to ORS can be added to these reservations as traces. Users are then prompted with the trace in due time before the guest arrives, and could update the record accordingly. A sample for a reservation warning would be if OXI_HUB uses a default instead of converted the incoming value. This warning would indicate to users that the conversion table is incomplete. Set this parameter to Y and OXI_HUB will create traces for each mandatory warning that occurred on the reservation. These traces are created for the trace department selected in the OXI_HUB Other Defaults for Trace warning.  If set to N, no traces will be generated for warnings. (Please note that this applies only to reservations.)

Set to Y if you would like to keep track of your warnings within the reservations where they have occurred.

The default setting is N for OXI-V6, OXI-V7, OXI-OPERA