|
|
|
Messages From External System
Example: An OXI message status screen for MESSAGES FROM EXTERNAL SYSTEM. This tab is visible for all interfaces.
The upper part of the Messages Status 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 fields will work with Upper of Lower case text entries. Additionally, partial string entries will be used for best match in the existing pick-list and auto-populated, if available.
Enqueue from. Start date for transmitted messages.
Enqueue to. End date for transmitted messages.
Msg Contains. Powerful new search tool that allows you to search for contents inside a message.
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. Filter for a message status such as FAILED, SUCCESS, WARNING.
Ext System Property. The property ID provided by the external system.
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.
Error Type. Select the down arrow and choose an error type from the LOV to filter search results by a specific error type. The following values are available for selection: A - SEARCH ALL, E/O - ERROR, T - OPTIONAL WARNING, and W - WARNING.
Error Contains. Enter partial text for an error message or copy and paste a complete error message into this field to search for a specific error message that was logged.
Note: You must select an Interface Id and Module along with the error message text to search for messages with specific errors/warnings.
Ext Ref No. External system confirmation numbers for all processed reservation messages are available in this display filter.
Whole word only. Flag to allow the Msg Contains field to search for only the word you are looking for in the XML messages. When not checked the search engine will search for the value also within any context.
Include reviewed. If you have messages checked as reviewed by double-clicking on the very first column to the left within a message line, you can set this flag to include them in the view or not. Messages would be checked as reviewed if they contain errors and warnings, and have been verified or resolved. The review check would indicate to others that this errors/warning has already been taken care of and does not need further attention.
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 FROM 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.
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.
Enq Date. Date when the message was enqueued by the OXI download process.
Enq Time. Time when the message was enqueued by the OXI download process.
Property. External system property ID this message was sent from.
Msg ID. Unique ID in sequential order that the external system gives to each message when sending it to OXI.
Note: Some external systems may not send the unique number, but this will not hinder OXI being able to process the message.
Module. Data module of incoming message. This identifies the kind of message received (e.g., reservation, profile, rate, allotment, rate restriction, inventory, result).
Status. Shows the status of the message transmission.
Ext Ref. This column contains the external system confirmation number. It shows the reservation number for a reservation or the block reference number for a block message. For all other modules it remains blank.
Process. Status Shows the status of the message processing.
Retry Count. Move the status bar on the message status screen further to the right and you see a few more columns. Retry Count shows whether the processing of this message was retried and how many times. Retry counts and intervals depend on OXI parameters RETRY_COUNT and RETRY_INTERVAL under the parameter group OXI_GENERIC. A retry of a message would be attempted if the original processing attempt failed due to, for example, a locked record.
Primary Info. This column shows key information that we obtain in a message such as the guest last/first name from a reservation message or the block code from a block message. The purpose is to make the data comparison between OXI and Opera easier.
OXI ID. OXI creates a unique sequential ID for each received message, which will be used for tracking and error handling internally.
The lower part of the Message Status screen 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 part shows details of all errors and warnings that have occurred during message transmission.
Show XML. Shows the XML message details. After clicking 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.
Review All. (Available when the OXI REVIEW MESSAGE permission is assigned to user) Select to mark all messages in the grid as reviewed.
Auto-display message: (radio buttons) 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:
Optional Warnings. 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.
Error Text. The explicit description of the warning or error that occurred for the selected message (see Errors or Warnings).
Type. Type of error or warning for selected message. This will display from Highest to Lowest severity on the screen.
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. It can also be used to remove any search criteria you have formerly set on the message status screen.
Reviewed. Mark a message as reviewed after you have verified an error or warning. Click the Reviewed button and the record will be marked as reviewed and disappear from the screen with the next refresh. In order to include reviewed records into the screen output, make sure that Include reviewed search option is checked.
Receive File. Pick up a file manually from a directory to receive it into OXI. This is a helpful tool when testing an XML message download directly from within OXI. Please note that this is only recommended for interfaces that use XML message format.
Reprocess. Reprocess a specific message. This is useful in case the original transmission was unsuccessful. You can correct the error, for example, by adding the necessary code to the conversion table, and reprocess the same message 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.
Block Request. (Only available when selecting a reservation record with a qualifying block association) Select this button to request group information from the external property. This feature is best used when a reservation is flagged with a warning or when the reservation has failed. It allows a more immediate and efficient way of dealing with groups that are sent to the Central System side. Furthermore, you can request the group information from external systems without searching for failed allotment messages in the interface. This is also beneficial if the interface has already removed group messages from the Message Status screen due to the PURGE NO DAYS parameter being enabled.
See Also:
