OPERA Setup For the OXI Interface

OPERA Configuration Check

A complete OPERA configuration is crucial for the proper functionality of the interface. Some elements are mandatory and others are optional. Check that the following mandatory components for the creation of a valid message entry in OPERA have been configured.

Mandatory Elements for Reservations & Blocks

Rate Codes

Room Types

Reservation Types

Payment Methods

Credit Card Types

Market Codes

Source Codes

Exchange Rates between OXI CRS currency and OPERA home currency have to be configured

Mandatory Elements for Profiles

Address Types

Phone Types

Membership Types

Membership Levels

Country Codes

Nationality Codes

Commission Codes for TA profiles

Bank Accounts – at least one account with each payment method EFT (CENT if no EFT license was purchased) and CHK has to be configured for Travel Agent profile commission processing.

If the hotel works with owners, these have to be configured to allow OXI to set an owner default for downloading profiles and blocks

Setup OXI Default Rate Code

Setup a Rate Code specific for OXI interface reservations. If any of the property rates have been subjected to Restrictions, this default rate can be used to insert the booking without failing it. This OXI specific Rate Code can be called ‘OXI Rate’, ‘OXI Default Rate’ or similar. This default rate is not to be subject to specific Rate Restrictions and Close Outs. This default is especially useful when properties and central systems do not exchange Rates or Restrictions.

Have the Rate Header and Rate Details include all room types.
See that the Rate Details include an End Sell date as far into the future allowed.
Set the rate amount to $0.00. If proper revenue/ADR is a factor set a rate amount instead.
This default rate code will be used on bookings when the actual rate is closed out or restricted.
Applicable warnings will be issued in OXI’s Message Status screen alerting system user that reservation needs attention.
This default will also alert the property of Rate Codes that are expired and need updates
If desired: To receive these types of warnings as a Trace on the reservation
Go to OXI>Interface Configuration>Interface Parameters>OXI_GENERIC> Warnings As Traces = Y.
Traces will be attached to the reservation for action by Hotel Personal
Traces Reports can be tagged for Reception or Reservation action as needed
Go to OXI>Interface Configuration>Interface Defaults>Reservation tab and populate the Rate Code in ‘External to OPERA’ column. Select a default Room Type to go with the Rate Code.
Additional points and information is provided under Reservation Defaults further in this document.

OXI Interface Permissions

Access to certain areas of OXI interface will require permissions linked to System Users. Access to these areas allows that user to Create, Edit and Delete entries and or values. Go to OPERA PMS, Login and path to Setup>System Configuration> Setup>User Configuration>Users.

OXI AUTOMATIC TRANSMISSION - This gives access to Automatic Transmission Scheduler under Interface Configuration.
OXI COMMUNICATION METHODS - This gives access to Comm Methods under Interface Configuration.
OXI CONV CODE – This gives access to Conversion Codes under Interface Configuration.
OXI CONV TABLE – This gives access to Conversion Tables under Interface Configuration.
OXI COPY CONVERSION – This gives access to Copy Conversion Utility.
OXI DATA REQUEST - This gives user access to unique data request functionality. Only for OPERA to OPERA usage.
OXI DEFAULTS – This gives access to Interface Defaults under Interface Configuration.
OXI DELETE ERROR LOG - This gives user rights to delete any reviewed entries in System Error Log under. Interface Status.
OXI DELETE INTERFACE - This gives system user right to delete active/inactive OXI's under Switch Interface.
OXI EDIT INTERFACE - This gives user ability to delete the interface setup done.
OXI IMP EXP - This gives access to Import/Export Utility.
OXI INACTIVE INTERFACES - This displays on-screen parameter for showing Inactive Interfaces under Switch Interface.
OXI LICENSE – This gives access to OXI License codes under Interface Configuration
OXI MSG STATUS – This gives access to Message Status and System Error Log screens under Interface Status.
OXI NEW INTERFACE – This gives access to New Interface under Interface Configuration.
OXI PARAMETERS – This gives access to Interface Parameters under Interface Configuration.
OXI PROFILE – This gives access to Profile Matching under Interface Configuration.
OXI PURGE DATA – This gives access to Purge Data Utility.
OXI RECEIVE TRANSMIT FILE - This gives access to use Receive/Transmit file buttons on Message Status screen for manual dropping of XML messages.
OXI REPORTS - This gives access to Reports module and reports active there.
OXI REPROCESS MESSAGE - This gives a user ability to use Reprocess button and have message processed through OXI conversion and defaults again.
OXI RESYNC – This gives access to Resync Utility.
OXI REVIEW MESSAGE - This gives a user ability to flag a message as reviewed on Message Status screen.
OXI SPECIAL CODES - This gives user access to Special Codes setup for interfaces linking codes to rooms and rates.
OXI START PROCESS – This gives access to Start/Stop Processor screen under Interface Status.
OXI SWITCH INTERFACE – This gives access to Switch Interface.
OXI SYSTEM ERROR LOG - This gives user access to the System Error Log screen under Interface Status. To be used with permission OXI DELETE ERROR LOG.
OXI UDF CONVERSION - This gives user access to UDF Conversion screen under Interface Configuration.

Packages Between OPERA

For Products to be transmitted between two OPERA products then the Business Events for them have to be activated. Delivery of package messages is only when using OPERA ORS to an OPERA PMS. Packages on Reservations will now be transmitted with Quantity and Length of time the package will be available on the reservation.

Scenario Example:

If reservation for Mr. Jones is for 2 days and has ‘2’ Breakfast packages for date range of 1 day entered. The package will be sent for the total packages of ‘2’ with 1 day.
If reservation for Ms. Smith is for 3 days and has ‘1’ Breakfast package, with no entry for date the package is available over. The package will be sent for the total packages of ‘1’ with 3 days. The amount of days is defaulted based on the length of the booking if the user does not enter the amount of days the package is to be available for.

Requirements:

The Packages have to be configured the same in both OPERA products.
The Transaction codes also have to be configured the same.

Business Events and their data elements that have to be activated for package information to be passed back and forth. Business events are in Setup>System Configuration>Setup>Business Events>Configuration>select External system>select Module Rate.

NEW PRODUCT
UPDATE PRODUCT
DELETE PRODUCT

OPERA Application Settings

All interfaces:

Go to System Configuration>Setup>Application Settings>Reservations, select option button 'Parameters' and set FIXED RATE the way it should work for your property.

All interfaces:

Function – FIXED RATES

Go to System Configuration>Setup>Application Settings>Reservations, select option button ‘Function’ and set FIXED RATES the way it should work for your property.

Function – IATA COMPANY TYPE

Go to System Configuration>Setup>Application Settings>Profiles, select option button ‘Functions’ and set IATA COMPANY TYPE. Set it the way it would work for your property if required. Verify if this is required for the central system to work before activating.

This function will release the PAD CORPNO DIGITS and PAD IATA DIGITS settings in Profiles.
These settings can be used for any property that requires previous Corporate Numbers or IATA Numbers to be validated in the property database to a specific valid length. Update of IATA and or Corporate Numbers in a central reservation system may also require that these numbers be of certain length to be valid and acceptable.
Functionality Dependency: Before the use of these parameters; should the property database require an update of IATA or Corporate numbers to specific length there is a Utility that will allow simple update without manual intervention. Go to Utilities>Login to application>Utilities>Profile>Padding.

Setting – SESSION TIME OUT

Go to Setup>Application Settings>General, select option button Settings and set SESSION TIME OUT the way it will work for your property.

Session Time Out will log system users out of the application where the applications have been idle for N amount of time. Releasing possible locked records left open at that station.
The log-out will also work with open OXI applications on remote stations.
When this setting is = null then the applications will not timeout after being idle. The OPERA and OXI application windows will be open.

We recommend: initial setting of ‘5-10’ minutes before the session times-out for any OPERA access.

OPERA to OPERA:

Rate Tiers

Parameter under RATES>RATE TIER set to Y to allow for Rate Tiers activation in OPERA properties
Rate Tiers must be configured exactly the same for this feature to work. In OPERA PMS go to Setup>System Configuration>Rate Management>Rate Classifications>Rate Tiers.

Block Restrictions

In OPERA, go to Setup>Application Settings>BLOCKS

The following Function must be active for Group blocks to show Restrictions and set Restrictions. Restrictions can be sent from OPERA PMS to ORS. SET BLOCK PICKUP RESTRICTIONS = Y.

Financial Transactions

In OPERA, go to Setup>Application Settings>Reservations>Parameter

SEND DEPOSITS TO ORS = Y then the financial transaction made on the reservation will be sent to ORS. Will then be inserted on the reservation there. This for transaction such as credit/Deposit.

SEND DEPOSITS TO ORS = N then there will be no transmission of the financial transactions to ORS system.

OPERA Add-on Licenses Required

OPERA Travel Agent Commission Configuration Requirements

All hotels that receive TA profiles from external systems and that are using the OPERA Travel Agent Commission Handling.

Setup>System Configuration>Commission Processing>Bank Accounts

The add-on license for commission handling OPP_COM must be active in OPERA
Travel Agents that are centrally paid have to be linked to the bank account that has the Payment Method type set to ‘EFT’ if the hotel works with the Electronic Funds Transfer license, or to ‘CENT’ if the hotel does not have this license. Those travel agents that are paid locally will be linked to the bank account that is set with Payment Method type ‘CHK’.
A different currency code has to be linked to the EFT/CENT and CHK bank accounts, as OXI is selecting the proper bank account based on the currency code that is linked to it.
In OXI, the flag sent by the external system for commission payment will be converted through the OXI ‘TA Currency Code’ conversion table and will be used to link the Travel Agent to the correct bank account. Conversion needs to be set up as 'Y' for central payment (EFT or CENT) or N for local payment (CHK), with the respective currency codes that reflect these payment types.

Example: In this example below we have linked the bank account ‘B45 SMK HCC Bank’ to the central payment method EFT, as the hotel has the Electronic Funds Transfer license active. This is also linked to currency code USD.

Example: In the example below we have linked the currency code USD to the external system value Y, which indicates the central commission payment for this interface. Holidex will always send Y and N. If you are using another interface, verify what values the external system will send, and configure the OXI TA currency code conversion table accordingly.

OPERA Export File Configuration

The OPERA PMS add-on license OPP_EXP must be active in OPERA.

OXI creates and transports the export files to the configured FTP server after a Night Audit has run. These files can also be transported to the FTP server when an OPERA user generates the export data manually. The export data is created as a part of the OPERA PMS sid_data at the time the OPERA PMS is installed at the property. Proper configuration is required for it to work with the OXI 2-Way. OXI will take the data from the OPERA tables and generate the messages for transportation. The OXI Communication Methods screen has to be setup with the proper FTP connection information.

OPERA License Codes and Business Event Setup

1. License Codes Setup

Business events for the external system are automatically enabled as soon as an OXI 2-Way license is activated. To access the license code from OPERA, go to the OPERA Configuration>Setup>License Codes>PMS>Add on License. To access the license code from OXI, go to Interface Configuration>License Codes. Below is a screenshot of the existing OXI licenses. Select your correct interface, enter the license code, and activate it.

Example: The below screen is just a sample. Select your correct interface license name.

See: OXI License Code Setup

Note: For an upgrade from a 1-Way to a 2-Way of the same interface: When upgrading an existing 1- Way to a 2-Way, select the license active for the 1-Way and deactivate it by blanking out the Active column. Then, select the license for the 2-Way, enter the valid license code, and check the Active column.

2. External System Setup

Go to OPERA>Setup>System Configuration>Setup>Business Events>External Systems.

The external system ID for your interface has automatically been created at the moment you have entered the OXI 2-way license code. This is the interface user ID that OPERA will use to recognize transactions from this external system. This has to be active for messages to leave OPERA through the OXI interface.

Note: Make sure that the external system is ONLY being activated at the moment you are ready to start using the interface. Do not activate the external system while you are still configuring OPERA and OXI, as this will create unnecessary business events that have to be deleted manually afterwards.

See: OPERA External System & Business Events Setup

3. Business Event Setup - ONLY (needed for 2- Way interfaces)

In OPERA go to Setup>Configuration>Setup>Business Events>External Systems>Configuration. Business Events are required in OPERA to send messages to an external system. What exact business events you need to configure depends entirely on the nature of the interface. If your interface transmits reservations and profiles to the external system, you need to configure reservation and profile business events. If rates and inventory have to be sent, you need to configure business events for rates and inventory, and so forth.

Example: Example of profile business event configuration.

Select your external system and the module you would like to configure business events for.

Example: Sample of data element selection within the business event NEW PROFILE.

Selection of the Data Element Name is done by selecting in the X column to the left of the data element. When a Data Element Name is selected here and an action is carried out in OPERA that involves that data element, a business event is generated. Which then becomes a message to the external system.

In the example above: The module is Profile and the business event is ‘NEW PROFILE’. Currently highlighted is the A/R NUMBER data element name. When this data element is activated with an X; a new profile with an AR Number populated will trigger a business event, and thus a message to the external system. Once a data element in the business event is activated, it will be part of the business event record that is created each time a user performs an activity in OPERA (e.g., create a new reservation). OXI will read the data from the business event outqueue table and will create a message from it, which is visible in the OXI message status table.

Another Example: The other purpose of an active data element within a business event is that a message will be created as soon as the OPERA user changes something in that particular element. Let’s assume that you are changing the number of adults in an existing reservation in OPERA, and nothing else. If ADULTS is an active data element in business element ‘UPDATE RESERVATION’, a business event record will now be created and OXI will create an upload message from it.