Relationships Defaults for OXI

Go to Interface Configuration>Interface Defaults.

Default values are crucial for the interface functionality. The values configured here will be used as defaults for incoming and outgoing messages in case no matching conversion value from the conversion tables can be applied during data transmission, or if conversions are not activated.

Relationship between defaults and conversion codes – data from external system to OPERA

If the conversion table for a data element is activated:

• Check if property-specific conversions exist and convert value
• if fails and property default exists>use property default
• if fails>OXI will validate the data element against valid OPERA codes and if that validation passes, insert the original code.
• if fails>OXI will fail the message in case the data element is mandatory (e.g., room type), or ignore element in case the data element is optional. In this case the message will still be processed but this data element will be ignored.

If the conversion table for a data element is NOT activated:

• Check if property default exists>use property default
• if fails> OXI will validate the data element against valid OPERA codes and if that validation passes, insert the original code.
• if fails>OXI will fail the message in case the data element is mandatory (e.g., room type), or ignore element in case the data element is optional. In this case the message will still be processed but this data element will be ignored.

Relationship between defaults and conversion codes – data from OPERA to external system

If the conversion table for a data element is activated:

• Check if conversions exist and convert value
• if fails> OXI will validate the data element against valid OPERA codes and if that validation passes, insert the original code.
• if fails and an OXI default exists>use default
• if fails>OXI will fail the message in case the data element is mandatory (e.g., room type), or ignore element in case the data element is optional. In this case the message will still be processed but this data element will be ignored.

If the conversion table for a data element is NOT activated:

• Validate the data element against valid OPERA codes and if that validation passes, insert the original code.
• if fails, check if an OXI default exists->use default
• if fails>OXI will fail the message in case the data element is mandatory (e.g., room type), or ignore element in case the data element is optional. In this case the message will still be processed but this data element will be ignored.

Validate Default Settings

Validate defaults functionality is available for OPERA PMS dependent fields. The Validate button has been added to each default tab screen. The validation will be on Reservations, Profile, Blocks and Others default screens only. As soon as it is applied, OXI will display a message prompt. If you select YES to run the validation, the following will happen.

• Check if OPERA parameter for RESERVATIONS>MANDATORY RATE CODE for that property is set.
• If set to Y, and default is empty you will be prompted to set default value.
• Otherwise it can be set or not.
• Check if OPERA parameter for RESERVATIONS>METHOD OF PAYMENT MANDATORY for that property is set.
• IIf set to Y, and default is empty you will be prompted to set default value.
• Otherwise it can be set or not.
• Check if OPERA function for GENERAL>OWNER for that property is set.  
• If set to Y, check OXI profile and block defaults. If default is empty you will be prompted to set default value.
• Otherwise it must be blank as the field will not be supported.
• Check if OPERA setting for BLOCKS>MANDATORY_RATE_CODE_BLOCKS for that property is set.
• If yes, check OXI block defaults. A rate code default has to be set.
• Otherwise it can be set or not.
• Check if OPERA setting RESERVATIONS >RESERVATION_TRACES for that property is set.
• If yes, check OXI other defaults. Trace departments can be populated.
• Otherwise they must be blank as the field will not be supported.