Messages To External System

Example: An OXI message status screen for MESSAGES TO EXTERNAL SYSTEM.

The upper part of the MESSAGES TO EXTERNAL SYSTEM screen contains a search section framed in yellow. Here you can filter out specific messages you would like to see on the status screen.

Search Filter Fields

Created from. Start creation date for transmitted messages.

Created to. End creation date for transmitted messages.

Msg Contains. Powerful new search tool that allows you to search for contents inside a message.

It requires a module and an interface ID in case you have multiple interfaces installed.
This tool further offers an And and Or condition where you can type in a content string into the first line, select the condition, and type the other content string into the second line.
When searching for only the Whole word and not within possible existing words activate the Whole word only check box.
The search is on the XML type of message. Will not search on external type messages. (i.e. TPI, RDR, AMF)
The search is case sensitive, which means the content entered here must have exactly the same case as it is in the message.
For a total view of a longer search string, you can double-click one of the search lines and a windows will open that allows up to 1000 character or search string.

Message ID from. Starting message ID for this display filter.

Message ID to. Ending message ID for this display filter.

Module. Module the filter should be set for. This option shows a list of all available interface modules, e.g. reservations, profiles, results, etc. A module would only be shown if a message for that module has already been processed. Please note that the module is required when using the ‘Msg contains’ search and you have multiple interfaces active.

Message Status. Status of the message that was transmitted to the external system. Options are FAIL, PROCESSED, REJECT, RESULT FAILED, RESULT SUCCESS, SUCCESS, and WARNING.

Opera Property. The Opera property ID

Interface ID. Interface ID for the filter. This is useful when you have multiple interfaces running at the same time and would like to display only the messages of one interface. Please note that the interface ID is required when using the ‘Msg contains’ search and you have multiple interfaces active.

Opera Ref. No Opera confirmation number for all processed reservation messages

Action Type. The Opera business event or other action that has triggered the creation of the upload message. Contents will show all action types for which messages exist in the OXI queue tables.

Search Filter Button Functions

Print. Works with a minimum of one sort filter to allow you to print a report of all Errors & Warnings for the interface. This report can even be narrowed down further by using the sort fields Module and Enqueue From/To.

Search. Start the search after you have selected the filters for the message display

Purge. This is the manual purge option for OXI status table entries. The purge is based on the filter criteria selected. This option can be used if an immediate clean up of the files in the status table is desired.

Note: If the purge is used without any filter, all messages will be removed from the message status tables. A warning message will appear with the default set to NO.

The middle part of the MESSAGES TO EXTERNAL SYSTEM screen is the real message status screen and shows the process status of transmitted messages. The Search Filter can be set to help find certain messages in this status screen.

Message Status Screen Fields

X. Select one or multiple records for reprocessing at the same time

Interface ID. The interface ID this message was created for. This is useful in case you have multiple interfaces running.

Create Date. Date when the message was created by OXI.

Time. Time when the message was created by OXI.

Property. Opera property this message was sent from.

Msg ID. Internal action ID from Opera for each created message.

Module. Data module of outgoing message. This identifies the kind of message sent, e.g. reservation, profile, rate, block, rate restriction, inventory, and result.

Action Type. The action type is equal to the business event that has generated the data in Opera. Some additional action types exist for cases where the messages were not initiated by business events directly.

Status. The status of a sent message from OXI. Options are:

FAILED – The message has failed in the external system during upload. The exact reasons depend on the specific system and can be reviewed in the ‘errors and warnings’ part of the screen.
NEW – Used for a membership points lookup request to OCIS to retrieve a profile's membership points. This status indicates that a STAY XML message has been built, but the membership points lookup operation has not yet been completed. The Module for this message is "STAY" and the Action Type is "POINTS REQUEST."
PROCESSED – Simply notifies that the message was processed by OXI. It has still not been delivered by the service, at which time it would turn into SUCCESS. If the messages status does not change from PROCESSED into SUCCESS, make sure that your OXI service is running and that the communication details are set correctly.
REJECT – Shown in case OXI rejects the message from upload since vital data is missing or the upload file cannot be built.
RESULT FAILED - The external system has sent a result for this message and has informed that the message was unsuccessful on external system side. The exact reasons depend on the specific system and can be reviewed in the ‘errors and warnings’ part of the screen.
RESULT SUCCESS – The external system has sent a result for this message and has informed that the message was successfully updated on external system side.
SUCCESS – Message has been delivered to the external system by the OXI service
WARNING - The message has been processed successfully but still created a mandatory warning that needs to be reviewed in the Errors and Warnings part of the screen.

Opera Ref. This column is for the Opera reservation confirmation number. This shows a reservation number or a block reference number. For all other modules it remains blank.

OXI ID. OXI creates a unique sequential ID for each outgoing message, which will be used for tracking and error handling internally.

Note: The lower part of the Messages from External System is split into a Show XML/Show Ext for the messages and a part for Errors and Warnings. The Show XML/Show Ext allows viewing of the original external system format and the XML message format. The Errors and Warnings shows details of all errors and warnings that have occurred during message transmission.

Button Functions (lower left of screen)

Show XML. Shows the XML message details. After selecting on this tab only a part of the message appears. You can double-click into the message to fully view it with your linked browser. In a thick client environment a browser can be linked through the Registry Settings under FORMS60_EDITOR. Our suggestion is to use the internet explorer here.

Show Ext. This option is available for external systems that do not directly create XML messages. In that case, the original message format before conversion into XML can be viewed here.

Extract XML. Allows the user to export the whole XML message to a local directory for Opera Support purposes.

Extract Ext. Allows the user to export the external systems message to a local directory for Opera Support purposes. The external system may have an different file format, as is the case with Holidex TPI, Pegasus AMF, etc.

Reprocess All. Allows all messages to be reprocessed or just individually selected records.

Auto-display message: Select the automatic view format that should be used when you are browsing with your cursor through records on the message status screen. Options are:

NONE does not show any message format
XML shows the XML format of the message wherever it can be applied
EXTERNAL shows the original format from the external system
ANY to let OXI decide which format should be applied. OXI will try to show the external format and if that is not applicable, show the XML format. This should be your standard setting.

Error and Warnings Fields

Optional Warning. This box can be flagged if you wish to see warnings of type ‘T’ (tentative) that have occurred during message transmission. These warnings normally indicate that conversion could not be applied or that a default has been used. These warnings are not critical and can therefore be suppressed by blanking out this flag. It is however recommended to clean up conversions and default problems in OXI to achieve absolute data accuracy.

Errcode. Error code in case the selected message has returned a warning or an error

A positive number identifies a warning, e.g. 1
A negative number identifies an error, e.g. (-) 99

Error. Text The explicit description of the warning or error that occurred for the selected message. Please refer to the appendixes at the end of this document for more details.

Type. Type of error or warning for selected message. This will display from Highest to Lowest severity on the screen.

Type E indicates the Highest Error Level. This error type will be highlighted in RED text.
Type O indicates an Oracle Error. This error type will be highlighted in RED text
Type W indicates a Low Level Warning. This error type will be highlighted in BLUE text.
Type T indicates an Optional Warning. This error type will be highlighted in BLACK text.
Type R indicates a result message from the external system, which OXI displays as a mandatory warning to notify OXI users of the same.

Button Functions (bottom of screen)

Reviewed. Mark a message as reviewed after you have verified an error or warning. Select this button and the record will be marked as reviewed and disappear from the screen. In order to include reviewed records into the screen output, make sure that the Include reviewed search option is checked.

Refresh. Refresh the display of the message status screen. When loading the status screen, the message display is automatically refreshed. Once the screen is loaded, you will use this button to refresh the display if some time has passed since the last refresh. New messages will only be displayed after the use of the Refresh button.

Transmit File. Pick up a file manually from a directory to send it from OXI to the external system.

Reprocess. Reprocess a specific file. This is useful in case the original transmission was unsuccessful. You can correct the error, e.g. by adding the necessary code to the conversion table, and reprocess the same file again from this screen. If the download problem cannot be solved through user correction at this stage, the message needs to be corrected in the external system and has to be sent again.