Running and Maintaining the Interface for OXI

In the following topics we will refer to the Third Party System as ‘External System’ and to OPERA PMS as ‘OPERA’. The suggested maintenance and procedures outlined here are basic guidelines for our system users. The OPERA Xchange Interface will be referred to as 'OXI’.

The purpose of these topics is to assist Hotel Property personnel with OXI and its function at the property. Configuration setup may change from time to time in the OPERA system. These changes must be reflected in OXI. Various areas in OXI have been outfitted with Reports and Validation functions to assist with these updates. Guidance is provided in the following topics of Maintenance, Daily Procedures, Periodic Procedures, Resynchronization information and Support Case reporting tips.

Warning! Note that the interfaces names on the embedded screen-shots are samples only and may not reflect the original interface names that you will be using. If particular standards have to be observed for specific interfaces we will note this accordingly.

Maintaining the Interface

To access the majority of OXI, configuration, parameters etc., the system user will require OXI permissions. These Permissions are located in OPERA PMS’ Setup>User Configuration>User>Permission. Take note that if OXI is working in a multi-property environment, the main user maintaining OXI will need to assign themselves to the OXI permission group for all properties to manage OXI without logging in separately to each interface.

Switch Interface

To get from one OXI to the another in a multi-property setup, without logging in and out per interface type, Select Switch Interface to see all of the configured interfaces for each OPERA property. In most cases only one interface ID will be displayed for one or more properties.

For example, upon the initial login you may have logged in to the SPIRIT interface for property ABCD and now need to review SPIRIT conversion details for property XYZZ. Use the Switch Interface feature to change interface and property.

• To change between multiple interfaces go to Switch Interface and select a different interface.
• Permissions for OXI have been updated and access to other OXI's in a multi-property setup will be needed to access.

Example: Switch Interface screen with multiple installed interfaces and properties.

Fields

X. Will place an X in the column of the highlighted interface. To choose another interface, place an X in the column of the interface you wish to switch to.

Show inactive interfaces. Flag this function to display interfaces that have been deactivated

Button Functions

New. To create a new interface

Edit. To modify or view the setup details of the selected interface

Delete. To permanently remove the interface from the OXI configuration. Be aware that this will erase all details for this interface from the OXI tables.

Configuration Changes for OPERA and/or External Systems

Configuration changes can happen long after OPERA and OXI products have been installed; whether due to changing property specifics or business needs. Changes can affect the proper information handling for profiles, reservations and stay data, to name a few.

These next topics represent only a few of the Conversion and Default information areas, however they are the most vital topics in keeping OXI operating smoothly on a daily basis. It is recommended that you familiarize yourself with them.

When configuration is updated, and conversion codes and interface defaults are affected we have provided tools to assist in making the changes as simple as possible. For Conversion Codes there is a report that can be printed based on each single table or for all active conversions. Interface Defaults has a Validation button to assist in checking for OPERA based values. Please see Periodical Procedures for OXI regarding these tools.

Configuration Change for OPERA and OXI

OPERA PMS has introduced a new time-out for application users. This feature is parameter driven and it will log a user out once the screen has been left idle for X amount of time. This setting can be configures in OPERA Application Settings and is aimed to decrease issues with records being locked in OPERA where it was left open on another workstation. It will also help to eliminate the issue of records being locked on machines that are out of range of the Front Office staff during late business hours, overnight and weekends.

Go to OPERA>Setup>Application Settings>group GENERAL>function SESSION TIME OUT.

• The default timeout is going to be added to a built-in time-out of 5 minutes.
• When the screen(s) have been idle for ‘N’ minutes then the application will go to the Login prompt.
• For example, if you set the value to ‘5’ minutes, then the total time will be ‘10’ minutes before the Re-login screen will pop-up on OPERA and or OXI application screens.
• An initial setting of ‘1’ minute; which will give a total of ‘6’ minutes before the session times-out, is recommended.

Conversion Table Activation

At the time of the interfaces were installed the required conversion tables were setup and the mapping entered. Conversion Code tables can be added later as the system is upgraded and/or newer expanded functionality comes available.

For example the external system can now receive and send Titles in the Profiles, but the values are very different in each system.

• As a system user you see OXI processing Guest Profile for Mr. John Smith. But warnings displayed in OXI are showing that conversion could not be found for the title 'Mr' and the value is not inserted.
• Activate the 'Title' table and enter mapping values.
• Titles will be converted and Guest Profiles in PMS will reflect the new Title information.
• Note, if this is a Multi-property this also will require configuration update. Use the Switch Interface menu to update all properties as the same time.

Memberships

Keep in mind that as time goes on Memberships may be added, modified or deleted from the OPERA PMS. As this happens the OXI interface will also require updates. Such as when a Membership Loyalty program is phased out totally for example, then the below OXI Conversion Tables will need to be updated. Check that expired or new Loyalty programs are handled here.  This can also apply to Frequent Flyer programs.

• Membership Type

• Membership Level

• VIP Level

Example Scenario 1:  Membership Type is modified

There is mapping setup for Membership AAA (Automobile Assoc Amer.) and conversion looks like below left. Let's say that the OPERA PMS has changed the format for AAA Membership Type and the new type is (AA) below right.  Without changing the conversion below the information is not passed on. OXI will give warnings that conversion could not be found and the data will be ignored.

Existing Data:                                          Edit OPERA Value to newer (AA):

OPERA Value = External System Value        OPERA Value = External System Value

AAA = AAA                                                AA = AAA

Example Scenario 2:  Membership Type is deleted

There is a mapping setup for Membership GC (Gold Card Loyalty). Later this loyalty program is no longer used and is deleted from OPERA PMS. For our example below this loyalty program came with different levels such as 'Basic Member', 'Classic Member' and 'Gold Member'.  The tables that can be cleaned up are 'Membership Type' and 'Membership Level'.

Membership Type Conversion Codes:

Existing Data:	Edit OPERA Value:
OPERA Value = External System Value	OPERA Value = External System Value
GC = GC	(Value is deleted from Conversion)

Membership Level Conversion Codes:

Existing Data:	Edit OPERA Value:
OPERA Value = External System Value	OPERA Value = External System Value
Gold = GOLD	(Value is deleted from Conversion)
Classic  = CLSS	(Value is deleted from Conversion)
Basic  = BASE	(Value is deleted from Conversion)

Payment Methods

Payment Methods in OPERA PMS may be added too, long after OXI has been installed and running at the hotel property. Should new Payment types be added, update the conversion. (See example 1 below.) If more than one type of Payment Method was being sent by the external system, multiple mappings can be done to a single entry in OPERA PMS. (See example 2 below.)

Payment Method

• Conversion Code table
• Interface Default for Reservations field

Example Scenario 1:   Addition of Payment Method

The Payment Method Direct Billing did not exist before in the list and External System is sending value DIRECT. Because the value did not previously exist, you would have noticed that Reservations were picking up the interface default instead. Enter the new value into the Payment Method Conversion Table to correct this.

OPERA Value/External Value/ External>OPERA/ OPERA>External

DB/DIRECT/ Y/ Y

Example Scenario 2:   Addition of multiple Payment Methods (Inbound to OPERA)

Payment Method with more than one value coming from external system. Only one mapping can be used both directions in a 2-way interface. Yet you can still have differing values accepted.

OPERA Value/ External Value/ External>OPERA/ OPERA>External

AX/ AX/ Y/ Y

AX/AMEX/ Y/ Y

MC/ MC/ Y/ Y

MC/ MASTER/ Y/ N

MC/ MCARD/ Y/ N

Products/Packages

Reservations and Products/Packages:

When a reservation is sent from the External System, if the reservation carries a package it is attached to the reservation. If OPERA has any packages attached to the Rate Code, those are also attached to the reservation. Keep in mind the following for how packages are affected.

• Packages that rely on conversion will need the Product conversion table active in OXI.

• Packages are updated according to the OXI Reservation parameter PACKAGE EXT SYS OVER.

 Groups Using Products/Packages:

When a reservation is linked to a group, OXI will also look into the Allotment Header information. If a package has been attached to the group, that package will be linked to the reservation. Keep in mind the following for how packages are affected.

Go to; OXI>Interface Configuration>Interface Parameters>parameter group OXI_RESERVATIONS.

• Packages that rely on conversion will need the Product conversion table active in OXI.
• The OXI parameter PACKAGE EXT SYS OVER set to Y/N will also affect packages:
• If the parameter is Y, then the Packages will always be overwritten by CRS updates to the reservation. Example:  if the reservation has a package attached by the Hotel user but not by the CRS then the update message from the CRS will remove it and only keep the ones from the CRS, in the next update.
• If the parameter is N, then the Packages that were added from PMS side to existing CRS packages, will be kept in the next update sent from the CRS.

Profiles

Updating the OPERA system where information can affect profile handling in OXI:

• Titles
• Conversion Table – add, modify or delete values
• Interface Default for Profiles has Title default field – add, modify or delete the value
• Specials
• Conversion Table – Specials are being sent since upgrade to newer version of OPERA.  Activate the Specials table and map OPERA to External values
• Conversion Table – Specials exist but configuration has changed mapping needs attention – add, modify or delete values
• Ownership
• Interface Default Profile Tab – OPERA PMS Ownership parameter has been activated this field will need population.
• Ownership is applied to  Travel Agent and Company profiles where property representatives can be linked for handling.
• Memberships (discussed in the previous section, Memberships)
• Profile IDs are no longer restricted to simply numeric values. Now, alpha characters can also be used.
• NAME_ADDRESS.BARCODE tags have been added to PROFILE XML, to facilitate the transmission of barcode data for between system.

Rates

Updating OPERA or even the External System Rate Codes can affect Rate Code configuration and the Blocks and/or Reservations that use them.

• Rate Code in OPERA or External System
• Conversion Table – activate and add mapping values (for systems that are not using identical codes)
• Conversion Table – modify mapping if the rate code value has shrunk or lengthened
• Conversion Table – delete the mapped value when rate code is not in configuration any longer
• Rate Code Defaults
• Rate Codes are also used for Blocks and Reservations
• Interface Defaults Reservation and Block tabs has Rate Code default field this requires updates
• Rate Code no longer exists (is deleted)
• Rate Code has expired (rate details are in the past)
• Rate Codes Resync
• Should rate code details need to be updated Resync functionality is provided.
• Resync will work for systems that exchange data back and forth only.
• Rate Code resync will not be available for 1-way interfaces inbound to OPERA PMS.
• For more information on Resynchronization,refer to Resynchronization of Data - OXI.

Reservation Type

• OXI Conversion Table – Update conversion mapped values if OPERA or external system change values
• Interface Defaults
• Go to OXI>Interface Configuration>Interface Defaults
• Update Reservation Default and Block Default tabs

Room Types

• OXI Conversion Table – Update conversion mapped values if OPERA or external system has changed
• Interface Defaults - If any room type is changed in OPERA for Reservation and Blocks
• Go to OXI>Interface Configuration>Interface Defaults
• Go to the Reservation and Block tabs and update the Room Type

UDF's

• When in Delta Mode (Delta Mode = Y), if an existing UDF value needs to be removed from the database, an empty <udfValue>tag in the inbound message will delete the existing value. For example, if a profile is inserted and name.udfc35 is populated, the name will remain in the database until another message for the same profile is sent with the udfc35 value empty.

Daily Procedures for OXI

For procedures carried out more on a monthly or quarterly basis see, Periodical Procedures.

Start/Stop Processors

OXI functions with the OPERA Interface Service and Start/Stop Processors. Messages to and from OPERA will not be processed if the service or processors are off. Go to Interface Status>Start/Stop Processors to ensure that they are running.

To Check the Status:

• With a 1-Way Interface either the UPLOAD or the DOWNLOAD Process Type will be status ‘RUNNING’
• With a 2-Way Interface UPLOAD and DOWNLOAD Process Types will be status ‘RUNNING’
• Some interfaces will have additional processors for LOOKUP and or EXPORT Process Types and status will be  ‘RUNNING’

Start/Stop Processors = ‘STOPPED’

• Select the Start All button on the Processor screen, processors status is updated to ‘RUNNING’
• If Processors do not go to ‘RUNNING’ and message prompt is “Please start NT service”
• Go to the PC that has the OXI service. It is labeled as ‘OPERA Interface for NAME’. (NAME = Spirit, ORS, TLX etc)
• Start the Service, status will be ‘STARTED’
• Go back to bullet #1.

Start/Stop Processors  = ‘WAITING’

• Try the Stop All button on the Processor screen, processors status is updated to ‘STOPPED’
• Restart using Start All button
• Status will go from ‘WAITING’ to ‘STOPPED’ to ‘IN PROGRESS’ and finally ‘RUNNING’

Start/Stop Processors  = ‘IN DOUBT’

This status can be due to a few different reasons, such as: network issues at the property that caused the communication to be interrupted, or messages are not being delivered every second and the processor is ‘sleeping’ until time to ‘wake up’. Sleep time configuration is handled in Communication Methods.

• Try the Stop All button on the Processor screen, processors status is updated to ‘STOPPED’
• Restart using Start All button
• Status will go from ‘WAITING’ to ‘STOPPED’ to ‘IN PROGRESS’ and finally ‘RUNNING’
• If the status returns to ‘IN DOUBT’ check the System Error Log for any errors
• If there are no errors in the System Error Log try restarting the service on the OXI PC labeled ‘OPERA Interface for NAME’ and redo bullet #1 and 2 to resolve.
• If the restart of the service did not help establish the status as ‘RUNNING’ one reason could be the ‘Sleep Time’ setting is too high.
• This status usually happens if the property has message delivery via File System.
• Go to Interface Configuration>Communication Methods>External to OPERA and OPERA to External deliveries will be setup.
• Update the setting from X minutes to (1) or (.50) and Save.
• Restart the OXI Start/Stop processors for new setting to take place.
• Status ‘IN DOUBT’ will update to ‘RUNNING’

Start/Stop Processors  = ‘EXITED’

This status can be cause by the OXI License for the interface being ‘inactivated’ or the External System setting is ‘inactive’.

• Check in OXI itself for active interface license.
• Go to OXI>Login>Interface Configuration>License Codes
• If the license is ‘inactive’, activate it and next check the External System in OPERA PMS
• If the license is ‘active, check the External System in OPERA PMS
• Check OPERA PMS for External System activation.
• Go to Setup>System Configuration> Setup>Business Events>External System.
• Check that the External System for ‘Interface Name’ is displayed on the screen.
• If the External System is there on the main screen, Try to Restart OXI Service to correct issue.
• If the External System is not on the main screen, select the Show Inactive check box and check for interface.
• When finding the External System ‘inactive’, activate
• Restart the OXI Service on the OXI PC, so the interface can run.
• The OXI Service on the OXI PC is called “OPERA Interface for ‘Interface Name’”. For example: ‘OPERA Interface for Pegasus’

Purge Utility

The Purge Utility is a processor that removes the records from the Message Status screen. Its functionality is based on an OXI Parameter called PURGE NO DAYS. This parameter is set at the time of installation. To configure this parameter go to Interface Configuration>Interface Parameters>group OXI_GENERIC. The Purge Utility screen will display how many days the records in Message Status will be kept. Any message older than X amount of days will be removed. We recommend that the PURGE NO DAYS parameter is set to either 3 or 7 days, but no higher than 7 days unless OPERA Support has directed it to be so.

Check to see that it is up and running.

• Go to OXI toolbar Utilities>Purge Data.
• There is a text message on the screen that is displayed “Purge is running in the background.”
• If not found running; select Start button
• If found running, exit out.
• It is important that messages in OXI are reviewed at least once a day. As the messages will be deleted eventually with this processor.

For our clients that have Export Files sent from OPERA to the External System:

• Export Files will be delivered according to the Start Time Delivery in Communication Method setup
• Export Files that are ready for delivery will be status of ‘READY’.
• Export Files will not be deleted if they are not successfully delivered in a timely manner and are older than the setting in the PURGE NO DAYS parameter. *
• Successful status is ‘PROCESSED’ displayed in Message Status screen.
• Export Files will be deleted along with the regular records only when they have been successfully delivered.

  Note: If the Export Files are not being successfully delivered please check the System Error Log for Export File process records and Error Text details. If there is not enough details, go to the PC where the OXI Processor Logs are and review for detailed information to resolve issue. OXI Processor Logs are located on the OXI PC and a shortcut folder exists on the desktop for easy access.

System Error Log

The System Error Log is used to view summary entries from the OXI Processor Logs. The purpose of this is to display any internal system activity and/or errors or warnings that are not displayed on the Message Status screen. It will also contain records for every Start/Stop of the interface processors. This feature is best utilized by IT Management or Reservations Management for resolution of system issues. Refer to the section, OXI Processor Logs for more details on how to access those logs and view the information that is provided there.  

For a full description and usage of the OXI Processor Logs refer to these topics:

• System Error Log
• To Delete System Error Log entries

OXI Message Status Screen

From the main menu Interface Status>Message Status. This screen is vital to running interface and must be reviewed often to identify failed messages or other transmission problems. This screen is used to view the status of transmitted messages and to review details of the original External and XML message formats. All errors and warnings that occur during message processing are visible and traceable here. A message can also be reprocessed as necessary after configuration errors have been corrected.

Helpful Usage Tips:

• Shortcut F8 key is for calling 'OPERA Login' screen. Use if need to log-out and re-login for different user.
• Since the OXI Message Status screen is the most commonly used screen in OXI, you can set this as a default login screen. Open the message status screen and then press Shortcut F7.  
• A message prompt will display telling what default screen you have set for that login name.
• The next time you log with that user/password the Message Status screen will automatically be displayed
• Use exact filters to limit your message output if you are looking for specific messages
• Once filters are set they remain active when you toggle between “Messages from external system” and “Messages to external system”. The filters will only be removed once you are hitting the Refresh button as this serves as a reset. If you wish to keep the filters active, select the Search button to refresh your screen.
• You can double-click on any record and you will see the XML or external message with ALL details, ALL warnings and errors that have occurred. This will help for troubleshooting as the entire message with its errors can be saved and sent to support.
• Note that the message status screen has grown ‘longer’ and that you can move the bar underneath the middle part of the screen to view additional information in your message.
• The message status screen can be sorted by double-clicking on a particular column within the message status
• Since OXI stores the original external system ID for incoming and outgoing messages, you can easily find out which OXI result belongs to which incoming message: compare the Msg Id from the “Messages from external system” with the Msg ID on the “Messages to external system”. You have a match, as these are the same.
• Users can select multiple messages and use the Reprocess button. Or, a mass reprocess can be done by  selecting Search Filters to narrow selection without selecting each record individually.

More:  Quick_Tips

Handling Messages – Error or Warning status

The purpose of OXI is of course to insert messages from the External System into OPERA and vice-versa. What do you do with the unsuccessful messages showing a status of Failed or Warning? Where do you start if there are many of them and course of action. Below are recommended guidelines as to the best practices to resolve these issues.

Upon finding message with Status of ‘FAILED’:

• Use the Search Filters to help find all related messages.
• Populate the Module field with message type (i.e. Reservation, Result and or Rate etc).
• Populate the Interface ID field with interface name if you have more than one OXI interface (i.e. Trust, ORS etc).
• In the case of Reservations and/or Allotments to narrow related messages, use the Ext Ref No field for external confirmation numbers and/or the Allotment’s block code.
• Select Search to find those related messages before selecting to have OXI Reprocess all of them.
• There may be messages that are delivered earlier that have not been resolved.
• There may be messages that are linked together over a couple of days that have not been resolved.
• Now that all related messages have been found;
• Note the Error and or Warning message provided.
• Check OXI’s Online Help for Troubleshooting on Errors and Warnings.
• Or check the OXI Troubleshooting Manual document for list of Errors and or Warnings provided to the hotel at the time of installation.
• Determine what caused the message to Fail in the first place;
• Was the Reservation failed due to Rate Code and Room type unavailability?
• Was the Profile failed due to missing necessary data, such as the First Name or even Last Name?
• Was any message failed due to ‘Record is locked’?
• Was any message failed due to Property Restrictions at House level being closed?
• Can you resolve the issue easily by updating the OXI Conversion Codes, Interface Defaults, checking OXI Processors are up and running?
• Can you resolve the issue by updating OPERA; such as extending Rate Details that may have expired in the future? Etc.

Upon finding message with Status of ‘WARNING’:

Follow bullet points 1, 2 and 3 from the previous ‘FAILED’ message scenario above.

• Determine what caused the message to get Warnings in the first place;
  • Was the message flagged due missing conversions?
  • Was the message flagged due to interface defaults taken?
  • Can the message be Reprocessed once conversions have been updated or added?

Using the Message Status on-screen parameter ‘Optional Warnings’:

When this parameter is active, additional records will display in the Errors and Warning area. This will provide information of missing conversion data and why defaults were taken instead for the message.

•  Recommended practice to make resolution efficient.
• Activate the ‘Optional Warnings’ screen parameter.
•  Use the Search filters on the screen to target either Failed or Warning type messages.
• Run the Search screen report from Print button supplied.
• List of all records, based on the filter, will be available.
• Will list all warnings, errors or information entries per record.
• Will make fixing the interface’s conversions, defaults and some OPERA settings easier.
• Once all changes have been done. Save any new settings.
• Restart the processors; go to Interface Status>Start/Stop Processors.

  Note:  For full detailed explanation of the Message Status screen please see the OXI Configuration Manual.

See Also

• OXI Message Status - Current List of Errors
• OXI Message Status - Known Holidex Errors
• OXI Message Status - Known Pegasus Errors
• OXI Message Status - Known Marsha Errors

Reports Menu

Please see the following links to these reports for a full explanation and sample reports.

• Export Conversion Codes and Defaults
• Errors Mining

Other useful reports within OXI:

General report on all Warnings/Errors for any record processed through OXI:  Message Status General Warnings/Errors Report.

Conversion Codes report that will assist user to update mapping just for conversions:  Conversion Codes Report.

OXI Processor Logs

OXI Processor Logs record Start/Stops of the OXI Processors, errors in connectivity to the network, issues in processing messages between OXI and the External System. The logs also have Statistics on how many messages processed per hour. From the OXI Logs we populate the System Error Log with summary of processed messages. See that topic.

Where to find OXI logs:

• OXI Logs are created on the Database or Application PC. Also recognized as the PC where the OXI service resides.
• Logs are kept for 7 days.
• Older logs are removed as the date rolls forward.
• Logs are generated each day and are similar in labeling:
• Log labeling sample:  (HOLIDEX.20050725.log.xml)
• Naming convention is formatted like so: (InterfaceName.YYYYMMDD.log.xml)

Periodical Procedures for OXI

For procedures carried out on daily basis go here: Daily Procedures

The below procedures are only guidelines to keep the interface in top form long after it has been installed. As the hotel property configuration can be updated, often the interface setup is overlooked. Updating the settings will keep the interface processing messages smoothly and keep the amount of Errors and Warnings displayed in OXI to a minimum. We provide Reports and Validation functionality to assist system users in updating their interfaces. We recommend that every few months or quarterly, a check is done for the interface.

Main areas of concern after OPERA Configuration updates:

• Conversion Codes – review topics explained earlier Configuration Changes for OPERA and or External Systems.
• Interface Defaults – same as above.

Reports:

Conversion Codes

For Conversion Codes go to OXI toolbar select Interface Configuration>Conversion Codes. User will require OXI permissions to access configuration areas of OXI. The first active conversion code table is highlighted when the screen opens. The Print button is provided on the bottom right-hand side. Conversion codes can be printed just by table or for all tables.

Message Prompt:  “Do you want to print the details for ALL Conversion Codes?”

• Select No, if you only want to print the conversions for the highlighted table on display.
• Select Yes, if you want every conversion table to be printed out, even though one table is highlighted
• We recommend doing a print out for conversions so that OPERA and or External System values can be compared and updated over deleting them totally when using the Copy Conversion Utility validation function (See the following explanation of Validation on Conversion codes).

Errors Mining

A new Report tool called Errors Mining can assist users in adjusting out of date conversion. Go to OXI>Reports> Errors Mining it’s use is to currently assist users in resolving messages that have not been processed or have relied heavily on defaults to get into OPERA PMS. With this report based on errors generated on messages either inbound or outbound we can see what conversion is missing or needs to be updated. Getting the optimal efficiency out of the interface being key this report can be run periodically without having to manually track down issues through each separate record.

Please see earlier description and functionality: Errors Mining Report.

Validation:

Validation is provided only against OPERA PMS values. We cannot compare against any of the existing External Values setup here.

For Conversion Codes we provide validation through the Copy Conversion Utility. Go to Utilities>Copy Conversions.

• We recommend that when the validation is done that the values are not deleted yet.
• Note the conversion table that the values reside in
• Check if the OPERA Values can be updated instead so that existing External Values are not lost
• If the values can be determined as no longer in use for both sides select the value(s) and delete.
• Deletes done here will remove the record(s) from the conversion table setup.

For Interface Defaults we provide validation directly in the Defaults screens. From OXI toolbar select Interface Configuration>Interface Defaults.

• OXI screen defaults automatically to Reservations
• The Validate button is on the bottom right-hand side of the screen.
• Validation will also check on certain OPERA PMS parameter settings

OWNER parameter in OPERA will affect whether you require the Profile Owner and Block Owner default

RATE CODE MANDATORY parameter in OPERA will affect whether you require Reservations Rate Code and Block Rate Code defaults

• The functionality will validate against ALL the default tabs. You will not need to validate on each default tab.
• Successful validations will see message “Validation OK.”
• Validations against OPERA where parameter settings have changed will prompt you to the appropriate Default Tab and field. A message prompt will let one know what requires updating.
• Any changes will require Save button to be selected so the changed value is updated.

Resynchronization of Data

Generic Resync of Data to External System at Any Time

The Resync options can be run individually and in no particular sequence at any time if you simply wish to resync specific data to the external system. The reason for this can be, for example, to send all reservations that have not received an external system number during the original transmission. Again it is recommended that reservations be only resynched once it is certain that the respective rate codes, blocks, and profiles have been built in the external system.

Recommendations:

• We do not recommend resyncs for large periods of time during peak work hours
• We suggest a resync be done in the late to early morning hours where Night Management or Night Audit can run resync with out system performance slow down
• Resyncs can be done during the day – keep in mind
• Choose short time frames
• Choose the necessary records to resync over hundreds of records at a time

Go to Utilities>Resync

Full Outline of the Resyncs go here: Resynchronization of data OXI

Membership Stay Point Lookup

This message allows the membership award points that would be available to the guest at the time of check out to be displayed on the guest folio. This feature is available to guests with membership associations as well as to guests not yet enrolled in order to show what they could have accrued if they were members.

For the membership award points projection to work, there must be a membership type in PMS designated as “primary” with points "centrally" managed. This configuration is done in ORS/OCIS on the Membership Types - Main tab by selecting the External System option under the Points Calculation Method area. In this area of the Membership Types - Main screen, the database against which the points lookup should be performed must also be selected.

OXI

The outgoing Membership Stay Point Lookup request and response message logs can be found in the OXI Message Status screen under the “Messages To External System” tab. The Module for this message is "STAY" and the action type is "POINTS REQUEST."

The XML request message contains the STAY message generated by PMS to request the membership points from ORS/OCIS. The response message generated by the ORS/OCIS contains the membership stay points. In case of request failure in the external system (ORS/OCIS), the response message will contain the error message received from the external system.

Message Statuses

The possible statuses for the Membership Stay Point Lookup message are listed below.

Status	Description
NEW	STAY XML has been built, but the point lookup operation has not yet been completed.
FAILED	Stay point lookup failed; review the error messages for details.
SUCCESS	Stay point lookup succeeded.

OXIHUB

In OXIHUB, the incoming stay point lookup request and outgoing response messages are logged in OXIHUB’s Message Status screen under the “Ext system to ORS Log” and “ORS to Ext System Log” tabs.