AUTO RESYNC ON ROLL BUSINESS DATE

B/R

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

Whether to resync Opera transactions without external system confirmation number from Opera to external system when the business date is rolled in Opera.

Note: This is implemented only for those interfaces using XML message format, also for this to work, ROLL BUSINESS DATE business event must be subscribed in Opera configuration.

This parameter allows the user to pick the modules they would like to auto resync when the Opera business date is rolled.

Available values are B and R:

• When B is selected in the parameter, active blocks without subscription records will be resynced.
• When R is selected in the parameter, active reservations without external confirmation number will be resynced.

Set accordingly.

CHANGE TO PROFILE GENERATES

Profiles/ Reservations

-> Direction: Opera to External

When a Change to a profile occurs in Opera and a Profile business event is generated, OXI can use this event different ways.

Set to Profiles if the external system has a profile concept and can apply the changes to only the profile record.

Set to Reservations, if the external system has a concept of Guest Name Record (GNR), where the guest information is stored with the reservation record. In this case, OXI will search all active reservations linked to that profile and send reservation updates for these records.

Default is Profiles.

CREDIT CARD SUPPRESS

Profile
Reservation
Both
N

-> Direction both ways: 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 proccess 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 proccess reservation credit card information into OPERA.

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

Set accordingly.

DATABASE SIZE

Small/Medium/ Large

-> Direction: Data from external system to Opera.

This parameter determines what internal profile match criteria shall be used based on the size of the database.

On Individual profiles, Name Code, Membership, Credit Card, Passport, AR Number and Last + Phone will always be considered in the profile matching processes.

When database size is set to SMALL the following will also be considered. Last + Phone, Last + Address1 + City, Last + Zip, Last + Address1, Last + City.

For Non-Individual profiles Name Code, Membership and Credit Card will always be considered in matching. When database size is set to SMALL, Company + Address1 + City, Company + Zip, Company + Address1, Company + City are also considered.

When set to MEDIUM only Company + Address1 + City are considered in addition to the criteria always applied.

Set accordingly.

DEFAULT PRINTER

Network Path

-> Direction:  no direction

The name of the physical printer device configured in Opera. Used for OXI back-end printouts.

Used for reports that are not manually selected for printing. Network path is to be set to local machine easily accessed by users.

Example of usage:  Holidex OXI Automated Inventory Balancing Report.

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 other interfaces can be set either way.

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. Set 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.

LANGUAGE HANDLING

ALL

ENGLISH ONLY

SINGLE BYTE ONLY

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

This parameter controls the way OXI handles the data in multi- language systems. See the list of values for available options and details.

ALL: Transfer all data irrespective of the Language.

ENGLISH ONLY:  Transfer data having language code E (English) or unspecified language code.

SINGLE BYTE ONLY:  Transfer data consists of single byte characters

Generic:  ALL

MULTI ROOMTYPE CONV

Y/N

-> 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 will mandate a one-to-one room type conversion between external system and Opera 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. Please 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.

Sample: Opera has only room type KING and the external system converts both KNG and QUE into KING in the OXI 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 Opera. If the Opera 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. Set accordingly.

PURGE NO DAYS

Numeric Value

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

The number of days messages are kept in the OXI status tables before they are purged. The contents of these status tables can be seen on the OXI 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.

We recommend 7 days for single properties as this helps us supporting your hotel in case issues are reported that date a number of days back.

RATE DETAILS DISTINCT

Y/N

- > Direction: Data from external system to Opera.

When receiving messages of type 'DETAIL', OXI will identify the exact rate details to be updated by searching for a match with the begin date, end date, DOW flags and room types.

If an exact match is found, OXI will then update the matched rate detail with the values received in the message.

 If no exact match exists, OXI fails the message.

RETRY COUNT

Numeric Value

-> Direction: Data from external system to Opera.

OXI 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 Opera. OXI 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.

RETRY INTERVAL

Numeric Value

- >Direction: Data from Opera to external system.

Interval in seconds between each retry that OXI 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.

SEND COMMENT WITH CONVERSION

Y/N

- >Direction: Data from Opera to external system.

When 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.

Default is N.

Set accordingly.

SEND IFC CREATED ONLY

Y/N

-> Direction: Data from Opera to external system.

If set to 'Y':

Reservations:

If set to 'Y', changes and updates made to a record will be sent to this external system only if the record originated in this external system.

Rates (Ext Sys must handle rates):

When this Parameter is set to 'Y' AND Rate Code Conversion is active: Only Rates for which a conversion has been defined will be sent to this external system. Rates that do not have a defined conversion will not be sent to this external system.

If Rate Code Conversion is inactive: All Rates will be sent to this external system.

Products/Packages (Ext Sys must handle products):

When this Parameter is set to 'Y' AND Product Conversion is active: Only Products for which a conversion has been defined will be sent to this external system. Products that do not have a defined conversion will not be sent to this external system.

If Product Conversion is inactive: All Products will be sent to this external system.

Rate Code/Rate Category Restrictions:

When this Parameter is set to 'Y', only those Rate Code/Rate Category Restrictions that have an associated Rate Code/Rate Category conversion record will be sent to the external system. Rate Code/Rate Category Restrictions that do not have an associated Rate Code/Rate Category conversion record will not be sent to the external system.

If Rate Code conversion is inactive, all Rate Code Restrictions will be sent to the external system.

If Rate Category conversion is inactive, all Rate Category Restrictions will be sent to the external system.

If set to 'N':

External System will receive all Reservations, Rates and Products, irrespective of Conversions configuration.

Set to N if external system is handling External and Opera based data regardless of origin.

Set to Y if external system will only handle specific data originated in external system. (See conditions for this to work below.)

We recommend N value.

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.

Default for this parameter is N.

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.

SPECIFIC BLOCK EXCHANGE

Y/N

-> Direction: Data between External System to Opera and Opera to External System.

This parameter determines if conditions can be applied to determine which allotments and related reservations are exchanged with the external system. This parameter is an additional condition and does not enable the exchange of reservations and allotments. It function is conditional to all other configuration items and parameters related to allotments and reservations.

If this parameter is set to Y, it will enable a button OXI on Opera Block form. This button will allow selection of any external systems where the parameter is set to Y. When an external system has been selected on the allotment form, this block and all reservations related to that block will be sent to the external system.

If this parameter is set to N, all allotments and related reservations will be exchanged with the external system.

Default for this parameter is N.

WARNINGS AS TRACES

Y/N

-> Direction: Data from external system to Opera.

Warnings that occur when reservations are sent to Opera 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 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 will create traces for each mandatory warning that occurred on the reservation. These traces are created for the trace department selected in the OXI 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.