Auto Configure Interface Parameters and Settings

The following table outlines the action types, data elements, data types and XML tag names within this OPERA Cloud Business Events module. 

Parameter Group	Parameter Name	Param Value	Description
Blocks	EXTERNAL LOCKED YN	N	->Direction: Data from external system to Opera The system creating the block can remain the owner of it, which means the block can only be modified by the originating system. Set this parameter to 'Y' if the block created by the external system shall be locked in Opera and cannot be modified by Opera users. Set to 'N' if the block created by the external system shall be fully changeable in Opera.
Blocks	HANDLE BLOCK SOLD	NONE	-> Direction: Data from external system to Opera (EXT_SYS->OPERA) Update block sold count from external system when sent to Opera. This assumes that the external system has all block reservations but Opera not. In this case we need a sold count update as part of the block messages. -> Direction: Data both ways between external system and Opera (NONE) Block sold counts will not be transmitted between the systems. Use this if both systems transmit full reservations both ways, including block reservations. In this case an additional sold count update in the block message is not necessary. -> Direction: Data from Opera to external system (OPERA->EXT_SYS) Send block sold counts from Opera to external system. This assumes that Opera has all block reservations but external system has not. In this case we need to send a sold count update as part of the block messages. -> Direction: Data both ways between external system and Opera (TRANSMIT_BOTH_WAYS) Update block sold counts from external system when sent to Opera, and also return sold counts to external system. Use this if block reservations are not transmitted between the systems at all. In this case the block messages must mutually update the sold counts.
Blocks	HANDLE MASTER BLOCKS	Y	-> Direction: Data both ways between external system and Opera Opera has the ability to convert a single block into a master block, which is used when multiple sub blocks are linked to one block as master. A common scenario for this is a tour series, in which a former single block becomes a master block from which all tour series copies are made. The master block is visibly flagged as such in Opera and has no inventory. A sub block is linked to a master block through the master block ID. If this parameter is set to 'Y', OXI will send master blocks in Opera with the respective flags so that the external system can apply the same logic. Sub blocks are sent with the master block ID and need to be linked properly to the master block in the receiving system again, where the master could have a separate ID. If the external system is not capable of handling master and sub blocks, this parameter should be set to 'N'. In this case OXI sends a block cancel in case a block converts into a master, to make sure that the external system releases the inventory from that block accordingly. All sub blocks in Opera will be sent as normal single blocks without master block ID to such an external system.
Blocks	KEEP BLOCK PACKAGES		-> Direction: Data from external system to Opera. KEEP_BLOCK_PACKAGES parameter determines how to handle the existing Opera block packages. This parameter setting will be considered only when the packages are not received as part of the blocks. If this parameter is set to Y, then do not full overlay, keep the block packages as-is. If this parameter is set to N, then full overlay the Opera block packages with received block packages. If this parameter is set to Null, based on the Allotment Packages Entity tag value, full Overlay of block packages will be decided. E.g. XML tag AllotPackages = 'Y', then block packages will be full overlayed, else existing Opera block packages will be retained.
Blocks	SPLIT INV DETAILS	Y	-> Direction: Data from Opera to external system If 'Y', OXI will split the block inventory detail message into multiple chunks of size less than 32K. If 'N', OXI will send the entire inventory detail message to the external system.
Blocks	ALLOW UPDATES TO OPERA PROTECTED BLOCKS	Y	-> Direction: Data from external system to Opera This parameter controls whether or not block updates will be applied to Opera protected blocks. An Opera protected block is defined as an Opera block that Opera is in control of. By contrast, a non-protected block is an Opera block that an external system is in control of. If 'N', block updates from the external system will be ignored unless the block is under the external system's control. If 'Y', block updates from the external system will be accepted and applied for Opera protected blocks."
Blocks	ALLOW UPDATES TO BLOCKS WITH SELL LIMITS	KEEP	-> Direction: Data from external system to Opera Note: This parameter will only be considered if the OXI_BLOCKS>ALLOW UPDATES TO OPERA PROTECTED BLOCKS parameter is set to 'Y'. This parameter controls whether or not block updates will be applied to Opera protected blocks that have sell limits and how to handle the sell limits if updates are allowed. An Opera protected block is defined as an Opera block that Opera is in control of. By contrast, a non-protected block is an Opera block that an external system is in control of. If 'N', block updates from the external system will be ignored for Opera protected blocks that have sell limits. If 'DELETE', block updates without SELLLIMIT data from the external system will be accepted and applied to Opera blocks with sell limits. Existing sell limits will be deleted from the block. If 'KEEP', block updates without SELLLIMIT data from the external system will be accepted and applied to Opera blocks with sell limits. Existing sell limits on the block will remain as are, conditional to being within the new date range of the block. Selllimits outside of the new block dates will be deleted.
Blocks	UPL CATERING BLOCKS	Y	-> Direction: Data from Opera to external system Blocks can be flagged as 'Catering' in Opera. Set this parameter to 'Y' if you wish to send catering only blocks to the external system. If set to 'N', catering only blocks will be suppressed from sending to the external system.
Blocks	UPL DED ONLY	N	-> Direction: Data from Opera to external system If the external system does not distinguish between deductible and non-deductible blocks, you may want to suppress non-deductible blocks from sending, as these would affect the other system's inventory directly and cause inventory imbalances. In such a case you would set this parameter to 'Y' and OXI will only send deductible blocks. If the external system has a similar concept of handling deductible and non-deductible blocks, you can set this parameter to 'N' and OXI will send all blocks regardless of their status. In Opera, the block status code determines whether a block is considered deductible. Please check the Opera block status configuration for further information.
Blocks	UPL OPEN ONLY	N	-> Direction: Data from Opera to external system If the external system does not have a concept of 'open for pickup' blocks, you may want to suppress non-open blocks from sending, as these would still allow pickup in the other system and cause inventory imbalances when a reservation is sent to non-open block in Opera. In such a case you would set this parameter to 'Y' and OXI will only send open for pickup blocks. If the external system has a similar concept of open for pickup blocks, you can set this parameter to 'N' and OXI will send all blocks regardless of their status. An open for pickup block is defined by its status. Please check the Opera block status configuration for further information.
Blocks	WAIT FOR BLOCK EXT REF	N	-> Direction: Data from Opera to external system If a block is created in Opera, OXI can send the block header first and expect a result message with the external system's confirmation number. Only once this confirmation is received would OXI send the block details, as it is now safe to assume that the block details would be accepted by the external system as well. This external confirmation can even be displayed on the block header, ensuring Opera users that they can pickup reservations from a block without problems, as the external system knows the block as well. Set the parameter to 'Y' if block transmissions shall be handled like this. Set the parameter to 'N' if the external system does not return a response, or if it can safely handle block header and details at the same time.
Generic	CREDIT CARD SUPPRESS	N	-> Direction both ways: Credit Card(s) information suppressed. Due to privacy laws, credit card(s) information will be suppressed based on following settings - PROFILE: OXI will not include Profile Credit Card information in the outgoing profile messages and will not store Profile Credit Card information when received through messages of any type from non-opera systems. RESERVATION: OXI will not include any reservation Credit Card information in RESERVATION messages, however Profile Credit Cards for Profiles attached to a reservation may be sent. OXI will however proccess reservation credit card information into OPERA. BOTH: OXI will not include ANY Credit card information in the outgoing Reservation and profile messages and will not process any profile credit card information when received through messages of any type from non-opera systems. OXI will however proccess reservation credit card information into OPERA. N: OXI will send and process all and any credit card information present.
Generic	GENERATE XML	Y	-> Direction: Data both ways between external system and Opera. Applicable only for custom interfaces (HOLIDEX, TRUST, FTCRS, PEGASUS, MARSHA, TLX, BWI, etc.) using non-XML message format (configured in interface setup). Generating XML messages for those interfaces may help users and support personnel to identify message contents easier, but will consume more database resources. Set to 'Y' to generate an XML message from/to the external system message, set to 'N' to avoid the XML message creation.
Generic	HANDLE PSEUDO ROOMTYPES	Y	->Direction: Data both ways between external system and Opera If 'Y' the interface will include room types that are flagged as 'pseudo' into the data transmission for reservations and rate codes. The room type conversion table will allow the selection of room types as well. If 'N', pseudo room types will be suppressed from data transmission and the room type conversion table will not display them either.
Generic	MULTI PROPERTY	Y	If 'Y', This is a global interface Id with more than 1 property. If 'N', Interface is defined only for single property.
Generic	MULTI ROOMTYPE CONV	Y	-> Direction: Data both ways between external system and Opera This parameter should always be set to 'N' in a 2-way interface bases on reasons described below. It can be used for a 1-way interface. If set to 'N', OXI will mandate a one-to-one room type conversion between external system and Opera to keep the inventory in balance. This is very important if the interface uses block or rate messages, as it is not possible to convert one-to-many room types for blocks and rates, and this would result in severe imbalances.  You should only set this to 'Y' for interfaces that transmit only reservations, as one-to-many room type conversion could then be allowed to give flexibility. Please note that a one-to-many room type conversion must be very carefully considered as it can lead to differences in room type usage between the systems. Sample: Opera has only room type KING and the external system converts both KNG and QUE into KING in the OXI room type conversion table. This is possible with the conversion defaults and in this case the Opera->external default is set to N for the record KNG<->KING and set to Y for the record QUE<->KING. If the external system sends a reservation with KNG, this will map to KING when entering Opera. If the Opera user now changes the reservation, the room type will be converted into QUE when sending to external system, as QUE is flagged as Opera->external default in this multi-to-one room type conversion table. The result is that the same reservation exists as QUE in one system and as KING in the other, which may lead to confusion and questions.
Generic	RETRY COUNT	0	-> Direction: Data from external system to Opera OXI will retry this number of times to process an incoming message if the first attempt was not successful due to e.g. a locked record. A locked record can occur when OXI tries to process a message while another user is updating this record at the same time in Opera. OXI will retry the update x number of times as defined in this parameter. This parameter is directly linked to RETRY_INTERVAL.
Generic	RETRY INTERVAL	3	->Direction: Data from external system to Opera Interval in seconds between each retry that OXI will perform to process an incoming message after the first attempt failed. This parameter is directly linked to RETRY_COUNT.
Generic	SEND COMMENT WITH CONVERSION	N	-> Direction: Data from Opera to external system. If set to 'Y', non-internal comments with conversion code exist only send to external system. If set to 'N', all the non-internal comments will be sent to the external system. Internal comments will not be sent out always.
Generic	SEND VAULTED CREDIT CARD	N	-> Direction: Data from Opera to external system. When Credit Card vault is on, this parameter determines whether to include actual plain text credit card information or the unique id received from Credit Card vault system in the outgoing messages. - Set this to Y if the receiving system is vaulted and is using the same vault and understands vaulted information in the message. - Set this to N if the receiving system is not vaulted or is using a different vault or does not understand vaulted information in the message.
Generic	WARNINGS AS TRACES	N	-> Direction: Data from external system to Opera Warnings that occur when reservations are sent to Opera can be added to these reservations as traces. Users are then prompted with the trace in due time before the guest arrives, and could update the record accordingly. A sample for a reservation warning would be if OXI uses a default instead of converted the incoming value. This warning would indicate to users that the conversion table is incomplete. Set this parameter to 'Y' and OXI will create traces for each mandatory warning that occurred on the reservation. These traces are created for the trace department selected in the OXI 'Other Defaults' for 'Trace warning'.  If set to 'N', no traces will be generated for warnings. Please note that this applies only to reservations.
Inventory	EXTERNAL PHYSICALROOMS	N	-> Direction: Data from external system to Opera The hotel may not allow ORS or Opera Sales and Catering to sell its full physical room capacity. Although the hotel has 100 rooms it may allow only 50 rooms to be sold by ORS/Opera Sales and Catering. In this case the physical rooms should be calculated from the inventory snapshot the external system sends to Opera to make sure only 50 rooms are considered. In this case the parameter would be set to 'Y'. Set it to 'N' if Opera has the entire physical room inventory from which the sold counts shall be calculated.
Inventory	INT INVENTORY SNAPSHOT	N	-> Direction: Inventory derived from RTAV message If reservations are not transmitted both ways in this interface but the external system creates reservations that affect its inventory, this parameter should be set to 'Y'. In this case inventory will be updated in the Opera based on data sent by external system. Set this parameter to 'N' if it is not necessary to update the Opera based on the data from the snapshot. This would be the case if reservations are transmitted fully both ways, or if the external system does not create any reservations on its own.
Inventory	INV ROOMCLASS	N	-> Direction: Data from Opera to external system The external system may accept the Room Class totals in the RTAV message. Set the parameter to 'YP' to include Room Class totals in the RTAV message. For Suites (Virtual Rooms), actual physical rooms comprising the Suite will be used for the Room Class totals. Set the parameter to 'YS' to include Room Class totals in the RTAV message. Each Suite (Virtual Room) will be treated as a single unit for the Room Class totals. Set the parameter to 'OO' to only send overbook counts in the RTAV message. Set it to 'N', if Room Class totals are not to be included in RTAV messages.
Inventory	INV SNAPSHOT BLOCKS	N	-> Direction: Data from external system to Opera If blocks are not transmitted both ways in this interface but the external system creates blocks that affect its inventory, this parameter should be set to 'Y'. In this case block inventory will be updated in the Opera inventory tables from the inventory snapshot sent by external system. Set this parameter to 'N' if it is not necessary to update the Opera block inventory from the snapshot. This would be the case if blocks are transmitted fully both ways, or if the external system does not create any blocks at all.
Inventory	INV SNAPSHOT RES	N	-> Direction: Data from external system to Opera If reservations are not transmitted both ways in this interface but the external system creates reservations that affect its inventory, this parameter should be set to 'Y'. In this case transient reservation inventory will be updated in the Opera inventory tables from the inventory snapshot sent by external system. Set this parameter to 'N' if it is not necessary to update the Opera reservation inventory from the snapshot. This would be the case if reservations are transmitted fully both ways, or if the external system does not create any reservations on its own.
Inventory	UPL BLOCK INFO	N	-> Direction: Data from Opera to External System Set it to 'Y' if OXI needs to send the block information (block code, ded type, blocked/sold count) to the external system. Set it to 'N' if OXI need not send the block information to the external system.
Messages	MAX SIZE BLOCKS	2048	->Direction: 512KB is the recommended value for Blocks. Messages that exceed this size limitation (in KB) will be entered in the database, but not processed and need to be reviewed for course of action.
Messages	MAX SIZE PROFILES	2048	-> Direction: Data from external system to Opera 200KB is the recommended value for Profiles. Messages that exceed this size limitation (in KB) will be entered in the database, but not processed and need to be reviewed for course of action.
Messages	MAX SIZE RATES	2048	->Direction: 512KB is the recommended value for Rates. Messages that exceed this size limitation (in KB) will be entered in the database, but not processed and need to be reviewed for course of action.
Messages	MAX SIZE RESERVATIONS	2048	-> Direction: Data from external system to Opera 200KB is the recommended value for Reservations. Messages that exceed this size limitation (in KB) will be entered in the database, but not processed and need to be reviewed for course of action.
Profiles	ACCEPT ANONYMIZATION UPDATE	Y	-> Direction: External system to Opera. This parameter determines whether to anonymize OPERA profile when update profile message is received with anonymize Flag and 'Profile Information Protection' functionality is active. - If this parameter is set to 'YR' then OPERA profile will be anonymized and a snapshot of the profile will be sent back to the calling system after it has been anonymized in OPERA. In order for the calling system to receive the profile update, the calling system must be subscribed to the UPDATE PROFILE business event. - If this parameter is set to 'Y' then OPERA profile will be anonymized. - If this parameter is set to 'N' then OPERA profile will be will NOT be anonymized.
Profiles	ACCEPT CENTRAL MERGE	ALL	-> Direction: Data from external system to Opera. This parameter determines whether to merge corresponding Opera profiles when the received PROFILE message contains MergedIDs. - If this parameter is set to 'ALL' or one or more profile types, OXI will attempt to merge while processing messages of the specified profile types and will update the merged profile with the information received in the message. - If this parameter is not set to any value, OXI will ignore MergedIDs in the message and will update one matching profile with the information received in the message.
Profiles	ACCEPT PRIVACY UPDATE	Y	-> Direction: Data from external system to Opera. This parameter determines whether to update the privacy options in Opera profile when the profile message is received. - If this parameter is set to 'Y' then privacy fields in Opera profile will be updated. - If this parameter is set to 'N' then privacy fields in Opera profile will NOT be updated.
Profiles	BROADCAST PROFILE	DISABLED	-> Direction: Data from external system to Opera Values are ENABLED or DISABLED. When ENABLED, a profile sent from a property is broadcasted to all subscribed properties including the property that has originally sent the profile to Opera. It is important to note that depending on the interface rules, the information incoming from the property might not be the same as the information that is sent back to this property when the profile is broadcasted. If e.g., the interface rule for ADDRESSES is set to 'N' and the incoming address is different from the address in Opera, the broadcasted profile will have the Opera address, thus overwriting the address that was sent by the property. When set to DISABLED, the profile will not be broadcasted to any property.
Profiles	COMPARE ADDRESS LENGTH	10	-> Direction: Data from external system to Opera Number of contiguous characters that need to match in an address: If the first address line and the city are the same between profiles, and if this number of contiguous characters match, then the existing address will be overwritten instead of inserted newly.
Profiles	CORP EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter determines whether a company profile shall be overwritten from the external system or not. This may be desirable if the external system has more accurate company data than the Opera database. Set to 'Y' and the external system profile details for company profiles will overwrite the existing Opera profile. Set to 'N' and the Opera details will remain unchanged. Even if this parameter is set to 'Y' you can manipulate how data is being overwritten with the use of profile parameters INTEREST EXT SYS OVER, NEGRATES EXT SYS OVER, PHONE/ADDR EXT SYS OVER, PREF EXT SYS OVER, PROFCOMMENTS EXT SYS OVER.
Profiles	DISCARD DUPLICATE MEMBERSHIPS	N	-> Direction: Data from external system to Opera If set to 'Y', discard received memberships if they already exist in another Opera profile and issue warning. If set to 'N', profile will be created without checking if the received memberships already exist in another Opera profile.
Profiles	DO NOT INACTIVATE SUBSCRIPTION	ENABLED	-> Direction: Data from external system to Opera Valid values are ENABLED and DISABLED. ENABLED for Company Profile types all subscriptions will be maintained as ACTIVE in ORS thus allowing multiple profiles in PMS to be linked to one profile in ORS. DISABLED means if that the each company profile type in ORS is linked by one active subscription per property, all other subscritions on the profile will be inactive.
Profiles	GLOBAL PREFERENCES	DISABLED	-> Direction: Data from external system to Opera. Valid values are ENABLED and DISABLED. ENABLED means all preferences sent by the external system, which are designated as global in Opera, will not be inserted, updated, or deleted in Opera for profiles with a primary membership attached. DISABLED means that all preferences sent by the external system will be inserted, updated and deleted for all profiles.
Profiles	GROUP EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter determines whether a group profile shall be overwritten from the external system or not. This may be desirable if the external system sends many details in the group profile while the Opera database only has the name. Set to 'Y' and the external system profile details for group profiles will overwrite the existing Opera profile. Set to 'N' and the Opera details will remain unchanged. Even if this parameter is set to 'Y' you can manipulate how data is being overwritten with the use of profile parameters INTEREST EXT SYS OVER, NEGRATES EXT SYS OVER, PHONE/ADDR EXT SYS OVER, PREF EXT SYS OVER, PROFCOMMENTS EXT SYS OVER.
Profiles	HANDLE RESORT AR NUMBERS	IGNORE	-> Direction: Data from external system to Opera This parameter determines how to handle the incoming resort AR numbers in the ResortArs collection. When set to FULLOVERLAY, all received AR Numbers for the resort will get inserted or updated, for new AR numbers OXI will copy the primary address of the profile as AR address. Existing AR numbers will only get deleted if Opera parameter 'ACCOUNTS_RECEIVABLES' is set to 'N' When set to MERGE, incoming AR numbers will Only get merged with existing Resort AR Numbers. When set to IGNORE, incoming AR numbers will be ignored.
Profiles	HANDLE RESORT PAYMENT METHOD	IGNORE	-> Direction: Data from external system to Opera This parameter determines how to handle the incoming Profile Resort Payment Method. When set to FULLOVERLAY, existing Profile Resort Payment Method will get overwritten with the incoming value. When set to UPDATE, update only if existing Profile Resort Payment Method is null. When set to IGNORE, incoming Profile Resort Payment Method will be ignored.
Profiles	IND EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter determines whether an individual profile shall be overwritten from the external system or not. This may be desirable if the external system has more accurate guest data than the Opera database. Set to 'Y' and the external system profile details for individual profiles will overwrite the existing Opera profile. Set to 'N' and the Opera details will remain unchanged. Even if this parameter is set to 'Y' you can manipulate how data is being overwritten with the use of profile parameters INTEREST EXT SYS OVER, NEGRATES EXT SYS OVER, PHONE/ADDR EXT SYS OVER, PREF EXT SYS OVER, PROFCOMMENTS EXT SYS OVER.
Profiles	INTEREST EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter will come into effect if you allow profiles to be overwritten in general. This means at least one of your parameters IND EXT SYS OVER, CORP EXT SYS OVER, TA EXT SYS OVER, SOURCE EXT SYS OVER, or GROUP EXT SYS OVER have to be set to 'Y'. The functionality of this parameter is further determined by the 'mode' of your interface. If it works with delta changes set to 'yes' (interface configuration->edit interface), the external system can send profile changes only and does not need to send the full profile every time a small change to a profile occurs. OXI will then only update the changed data and not touch the additional data that was found in the Opera profile. This also means that the external system needs to indicate intended deletions clearly with deletion indicators in the message. Sending simply blanks will not lead to data deletion if OXI works in 'delta mode'. The deletion indicators can be configured in interface configuration->edit interface. If your interface is set to delta changes 'no', OXI expects a full overlay of all profile data in every profile message, even if the external system only changes very little of the entire profile. Here is how the parameter works: If your interface is setup as 'Delta Changes = Y' and no interests are sent by external system in the profile message, this parameter is ignored and the existing Opera profile interests remain untouched. Otherwise the following parameter rules apply: If 'Y', interests sent by external system will overwrite existing Opera profile interests. If 'N', interests sent by the external system will be appended to existing Opera profile interests.
Profiles	INTERFACE DEBUG		-> Direction: irrelevant as this applies to handling within the interface. This parameter is for internal use only and will be set and used exclusively by Micros Development and Support teams. It should always be set to blank.
Profiles	MAX MATCHES ALLOWED	50	-> Direction: Data from external system to Opera This parameter works in conjunction with the parameter MATCH_CRITERIA and its setting of A (Last+City) and C (Last+Address). If this parameter is set to 50 maximum profiles to be matched, and a profile is sent to Opera that matches against a number of less than 50 existing Opera profiles, the incoming profile will be considered for those match criteria indicated above. If the profile sent to Opera matches over 50 existing Opera profiles, the incoming profile will not be considered for those match criteria specified, Instead the interface will continue to search for a profile match based on the other criteria that are classified within the MATCH_CRITERIA parameter.
Profiles	MAX PROFILE MATCHES		-> Direction: Data from external system to Opera. This setting impacts the search depth for profiles meeting matching criteria, prior to establishing weighted points:   - A lower setting (i.e. 10) will favor execution speed, while correctly matching the vast majority of profiles.   - A higher setting (i.e. 100) will favor even very distinct differentiation, while providing very good execution speed.   - A setting of 1000 can have a negative impact on performance, when reservations are received with limited profile information.   - Leave blank if you want OXI to always find and weigh all possible matches.  If the value is left blank and you have limited information in the message (i.e. John Smith in New York) and several thousand potential duplicates can be found in the database, processing these reservations may take several minutes.  During this time, the OXI Download processor will go into WAITING status and users will be prompted with a warning about the state of the interface.
Profiles	MEMBERSHIPS	ENABLED	-> Direction: Data from external system to Opera This parameter is useful if customers who do not have all memberships standardized throughout their system. Valid values are ENABLED and DISABLED. ENABLED means that membership types that cannot be converted will be disregarded from the incoming profile message into Opera. This would prevent an acceptance of membership type that are non-standard. When DISABLED, the profiles with invalid membership types  will be staged in Opera with status INVALID.  This parameter value will also be validated against stay records and memberships associated to a stay.
Profiles	MIN PHONE LENGTH	6	-> Direction: Data from external system to Opera This parameter allows you to decide what minimum phone length to allow upon sending a profile to Opera. Any phone length less than the parameter value, will be ignored and not inserted. Due to performance issues, we have limited this setting to 5, 6, or 7. A setting of 5 results in more matches, while 7 will result in less. Any setting higher or lower than this range will be defaulted to 6. We recommend setting this parameter to any value of 5, 6 or 7.
Profiles	MULTIPLES MATCHES	DISABLED	-> Direction: Data from external system to Opera When ENABLED and a match is found on property ID, the interface will look further into the database for other potential matches based upon the selected criteria. When DISABLED a match on profile ID will lead to a direct merge prompt for that profile.
Profiles	NAME CODE EQ MEMBER NO	DISABLED	->Direction: Data from external system to Opera. Valid values are ENABLED and DISABLED. If ENABLED, the name code in the ORS profile has to equal the membership number of the incoming profile for the primary membership.
Profiles	NEGRATES EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter will come into effect if you allow profiles to be overwritten in general. This means at least one of your parameters IND EXT SYS OVER, CORP EXT SYS OVER, TA EXT SYS OVER, SOURCE EXT SYS OVER, or GROUP EXT SYS OVER have to be set to 'Y'. The functionality of this parameter is further determined by the 'mode' of your interface. If it works with delta changes set to 'yes' (interface configuration->edit interface), the external system can send profile changes only and does not need to send the full profile every time a small change to a profile occurs. OXI will then only update the changed data and not touch the additional data that was found in the Opera profile. This also means that the external system needs to indicate intended deletions clearly with deletion indicators in the message. Sending simply blanks will not lead to data deletion if OXI works in 'delta mode'. The deletion indicators can be configured in interface configuration->edit interface. If your interface is set to delta changes 'no', OXI expects a full overlay of all profile data in every profile message, even if the external system only changes very little of the entire profile. Here is how the parameter works: If your interface is setup as 'Delta Changes = Y' and no negotiated rates are sent by the external system in the profile message, this parameter is ignored and the existing Opera profile negotiated rates remain untouched. Otherwise the following parameter rules apply: If 'Y', negotiated rates sent by external system will overwrite existing Opera profile negotiated rates. If 'N', negotiated rates sent by the external system will be appended to existing Opera profile negotiated rates.
Profiles	PHONE/ADDR CRS OVER	Y	-> Direction: Both ways between external system and Opera. This parameter determines how the phones/addresses received from the external system update the phones/addresses in Opera and which Opera records are included in the outbound messages. This parameter will supersede the Delta setting of the interface.   A = If received, replace Opera values with the received values. If not received, remove the values from Opera.   B = If received, replace Opera values with the received values. If not received, do not remove the values from Opera.   C = If received, merge the received values with Opera values. If not received, remove the values from Opera.   D = If received, merge the received values with Opera values. If not received, do not remove the values from Opera.   E = If received, replace only those Opera values configured in conversion with the received values. If not received, remove only those Opera values configured in conversion. In outbound messages, send only those records with converted types.   N = Ignore the phone/addresses received. Do not touch the values in Opera.
Profiles	PHONE EXTENSION SYS OVER	N	-> Direction: Data from External system to OPERA This parameter determines whether to send phone extension . - If this parameter is set to 'Y', phone extensions will be exchanged from external system. - If this parameter is set to 'N', phone extensions will not be exchanged from external system.
Profiles	PREF CRS OVER	Y	-> Direction: Data from external system to Opera This parameter is applicable only if the profiles are allowed to be updated in general. This means at least one of the parameters IND EXT SYS OVER, CORP EXT SYS OVER, TA EXT SYS OVER, SOURCE EXT SYS OVER, or GROUP EXT SYS OVER should be set to 'Y'. If this parameter is set to Y or N and the interface is configured as 'Delta Changes = Y' and no preferences are received in the profile message, existing preferences in the Opera profile will remain untouched. Otherwise, if this parameter is set to 'Y', existing preferences in Opera profile will be replaced with the preferences received in the message, if set to 'N', preferences received in the message will be added to the existing preferences in Opera profile, if set to 'C', Opera profile preferences configured in 'Guest Preference' conversion will be replaced with the preferences received in the message.
Profiles	PROCESS INBOUND DOCUMENTS	Y	-> Direction: Data from External System to OPERA only. Only Global, and not resort specific, documents will be processed based on the parameter setting. Select 'Y' to process all received Document Types. Select 'N' to ignore all received Document Types.
Profiles	PROF CREATION	Y	-> Direction: Data from external system to Opera If you do not have any reason for not creating a new profile in case a match could not be found, this parameter should always be set to either 'Y' or a comma separated combination of the alphabets 'A','B','C','D','E' AND'F'. Each alphabet stands for specific profile selection: A- Guest B- Corporate C- Group D- Travel Agent E- Source F- Contact For all interfaces that transmit reservations and blocks, this parameter has to be set to either 'Y' or the above alphabet combination and a new profile will be created in case no profile match and merge with an existing Opera profile is possible. The reason that a profile fails the match can be that the profile does not make the entry match criteria or that it fails in the weighing point match criteria. Set this parameter to 'N' if you do not transmit blocks and reservations in your interface, and no new profile will be created in case profile match fails.
Profiles	PROFCOMMENTS CRS OVER	Y	-> Direction: Data from external system to Opera This parameter is applicable only if the profiles are allowed to be updated in general. This means at least one of the parameters IND EXT SYS OVER, CORP EXT SYS OVER, TA EXT SYS OVER, SOURCE EXT SYS OVER, or GROUP EXT SYS OVER should be set to 'Y'. If this parameter is set to Y or N and the interface is configured as 'Delta Changes = Y' and no comments are received in the profile message, existing comments in the Opera profile will remain untouched. Otherwise, if this parameter is set to 'Y', existing comments in Opera profile will be replaced with the comments received in the message, if set to 'N', only those comments in Opera profile last updated by this interface will be replaced with the comments received in the message, all other comments will remain unchanged, if set to 'C', Opera profile comments configured in 'Comment Type' conversion will be replaced with the comments received in the message.
Profiles	PROFILE BROADCAST DELAY	900	-> Direction: Data from Opera to External Systems This parameter defines the delay for broadcasting profiles received from external systems.
Profiles	PROFILE PREFERENCES	ENABLED	-> Direction: Data from external system to Opera This parameter is useful if customers want to standardize preferences throughout the hotel chain. Valid values are ENABLED and DISABLED. ENABLED means that preferences that cannot be converted will be disregarded from the incoming profile message into Opera. This would prevent an acceptance of preferences that are non-standard. When DISABLED, the profiles with invalid preferences will be staged in Opera with status INVALID.
Profiles	PROFILE RATE CODE UPLOAD	ENABLED	-> Direction: Data from Opera to external system When ENABLED the negotiated rate codes in profiles will be sent from the external system to Opera. When this is set to DISABLED no negotiated rate codes will be sent by the external system as part of the profiles.
Profiles	PROFILE SECOND ADDRESS	Y	-> Direction: Data from External Systems to Opera. This parameter defines that in a multi language environment, When the incoming profile has a foreign language address that contains no special characters but English characters only and when Parameter is N, only one address will be created. When Parameter is Y, even without special characters, two addresses will be created, one for foreign language and one for English language.
Profiles	RELATIONSHIPS INCOMING	ALL	-> Direction: Data from external system to Opera. This parameter manages the transfer of relationship associations between Opera and External. None - When active, no relationship data will be sent or received from External system. All - Any update to the relationship will be updated in the receiving system regardless of local or global designation. Global - Only relationship flagged as global will be exchanged. Any local relationships will not be exchanged or updated.
Profiles	RELATIONSHIPS OUTGOING	ALL	-> Direction: Data from external system to Opera. This parameter manages the transfer of relationship associations between Opera and External. None - When active, no relationship data will be sent or received from External system. All - Any update to the relationship will be updated in the receiving system regardless of local or global designation. Global - Only relationship flagged as global will be exchanged. Any local relationships will not be exchanged or updated.
Profiles	REPLACE MEMBERSHIP CARD NUMBER	N	-> Direction: Data from external system to Opera If set to 'Y', update the card number of the existing membership with same type. If set to 'N', inactivate current membership of same type and create a new membership with the received membership number.
Profiles	SEND PROFILES PER DATABASE	Y	-> Direction: Data from Opera to External Systems. This parameter determines whether to send one profile message per external database or one profile for each resort of the external databases. - If this parameter is set to 'Y', only one profile message will be send out for each external database. - If this parameter is set to 'N', one profile message will be send out for each resort of the external databases.
Profiles	SOURCE EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter determines whether a source profile shall be overwritten from the external system or not. This may be desirable if the external system has more accurate data on the source or wholesaler than the Opera database. Set to 'Y' and the external system profile details for source profiles will overwrite the existing Opera profile. Set to 'N' and the Opera details will remain unchanged. Even if this parameter is set to 'Y' you can manipulate how data is being overwritten with the use of profile parameters INTEREST EXT SYS OVER, NEGRATES EXT SYS OVER, PHONE/ADDR EXT SYS OVER, PREF EXT SYS OVER, PROFCOMMENTS EXT SYS OVER.
Profiles	TA EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter determines whether a travel agent profile shall be overwritten from the external system or not. This may be desirable if the external system has more accurate agent data than the Opera database. Set to 'Y' and the external system profile details for agent profiles will overwrite the existing Opera profile. Set to 'N' and the Opera details will remain unchanged. Even if this parameter is set to 'Y' you can manipulate how data is being overwritten with the use of profile parameters INTEREST EXT SYS OVER, NEGRATES EXT SYS OVER, PHONE/ADDR EXT SYS OVER, PREF EXT SYS OVER, PROFCOMMENTS EXT SYS OVER.
Profiles	UPDATE PRIMARY	REPLACE	-> Direction: Data from external system to Opera This parameter allows you to decide what phone and address will be designated as primary upon sending a profile to Opera. When ENABLED, a new address/phone marked as primary sent from the external system is added to existing addresses in Opera and designated as primary. When DISABLED, the new address is inserted, however the current address will remain the primary. If the parameter setting is REPLACE, a new address will overwrite the existing address in Opera and will be set as primary
Profiles	UPDATE SALUTATION	Y	-> Direction: Data from external system to Opera - When this parameter is set to 'Y', OXI will update the salutation of a profile based on the profile's title handling, each time a PROFILE message is received. - When this parameter set to 'N', OXI will insert salutation when inserting a new profile, but will then not update this salutation, to allow users to maintain custom salutations in Opera.
Rates	HANDLE RATES POSTING RHYTHM	KEEP	-> Direction: Data from external system to Opera This parameter determines how to handle the incoming Rate Posting Rhythm (applies to non-V3 interfaces only). When set to FULLOVERLAY, existing Rate Posting Rhythm will get overwritten with the incoming value. When set to UPDATE, update Rate Posting Rhythm only if existing value is null. When set to KEEP, keep existing Rate Posting Rhythm if the received value is null. When set to IGNORE, incoming Rate Posting Rhythm will be ignored.
Rates	KEEP RATE DETAILS		-> Direction: Data from external system to Opera This parameter determines whether the Market code, Source Code, Package Elements, Yield Adjustment, Rate Amount Floor and Rate Amount Ceiling information of rate code details will be overwritten by an external system update or not. This parameter can be set to a single value or a comma separated combination of following entities : M: Market Code S: Source Code P: Package Elements Y: Yield Adjustments F: Rate Amount Floor C: Rate Amount Ceiling For example, if you don't want any modifications to any of above entities, you should set this parameter value as 'M,S,P,Y,F,C'. To allow updates to any of the above entities, don't include that entity setting in the parameter value. For parameter setting of 'M,S,P,Y,C', updates to Rate Amount Floor (parameter setting option 'F') would occur.
Rates	KEEP RATE HEADER PKG	Y	-> Direction: Data from external system to Opera This parameter determines whether package elements attached to the Opera rate code will be overwritten by an external system update or not. Set to 'Y' and only package elements attached to the rate header where the update_user = external system ID will be updated. This means that package elements created by an Opera user will not be overwritten. If this parameter is set to 'N', all package elements will be overwritten by changes from the external system, regardless where they have been created.
Rates	NO RATE HEADER UPDATE		-> Direction: Data from external system to Opera Select the letters for the rate header columns that shall not be updated by rate change messages from external systems. Values: A - Rate Description B - Rate Category C - Folio Text D - Market Code E - Source Code F - Commission Code G - Minimum Stay Through H - Maximum Stay Through I - Min Advance Booking J - Suppress Rate K - Print Rate L - Long Info M - Short Info N - Transaction Code O - Yieldable YN P - Commission % Q - Max Advance Booking R - Yield As S - Sell Sequence T - Discount U - Membership V - Daily Rates W - Day use X - Complimentary Y - House use
Rates	RATE CODE TEMPLATE	DISABLED	-> Direction: Data from external system to Opera Valid values are ENABLED,DISABLED and MANDATORY. When ENABLED the Interface will check if the rate code being sent from External System exists in the rate code Template. If the rate code is not part of the Template, Interface will add the rate code to the Template. When MANDATORY The Interface will check if the rate code being sent from External System exists in the rate code Template and if the rate code does not exist, message will be rejected and an error message generated informing the user to add the rate code to the Template. When DISABLED the rate code being sent from External System will not be subject to the rate code template check and the message will be processed.
Rates	RATE DELTA HANDLING	Y	-> Direction: Data from Opera to external system. This parameter determines if the Opera Rates will be sent as Delta or FullOverlay messages. This parameter only applies to Non-Opera interfaces. When set to 'Y', Opera Rates will be sent as Delta messages. When set to 'N', Opera Rates will be sent as FullOverlay messages.
Rates	RATE DETAIL MESSAGE HANDLING	FAIL	-> Direction: Data from external system to Opera This parameter applies only when receiving rate messages of type DETAIL, whereby OXI will not receive all rate details belonging to that rate, but is requested to update individual rate details as present in the message. This parameter determines processing principles when receiving details that offend existing rate details (i.e. existing rate DETAIL for one of the room types with dates overlapping). FAIL: When receiving an offending rate detail, OXI will FAIL the message and report RESULT FAIL in the result message returned to the sender. REMOVE: When receiving an offending rate detail, OXI will remove all existing offending rate details and rely on the external system to provide all other replacing details in subsequent messages. This is hardcoded to be the default selection for HOLIDEX interface and is recommended setting for all OPERA interfaces. REQUEST: When receiving an offending rate detail, OXI will FAIL the message and request the FULL RATE from the sending system. For this setting, the external system must support MESSAGEREQUEST V3 or higher. MAKE ROOM: Make room for the incoming rate details, during this process conflicting rate details will be appropriately adjusted to make room for incoming rate detail using split/insert/update and delete operations.
Rates	UPL TAX INCL EXCL	DISABLED	-> Direction: Data Opera to external system DISABLED means that taxes on rate codes will not be considered. ENABLED means OXI will include or exclude tax depending on Opera 'tax include' flag on property's Rate Header screen.
Reservations	ADDITIONAL REFERENCE EXCHANGE		->Direction: Data from Opera to external systems. Additional external reference types to include in the message to transfer to other systems. Include all required external reference types separated by comma(,).
Reservations	ASSIGN ROOM NO	Y	->Direction: Data from external system to Opera If 'Y', OXI will Assign the Room No. to Reservation. If 'N', OXI will Ignore  the Room No. tag in XML.
Reservations	AUTO ATTACH ELEMENTS	N	-> Direction: Data from external systems to OPERA. If this parameter is set to 'Y', OXI auto attaches the reservation elements based on the auto attach element configuration rules. If the parameter is set to 'N', OXI does not auto attach the reservation elements.
Reservations	AUTO POPULATE MEMBERSHIP YN	N	-> Direction: Data from external system to Opera. If 'Y', in addition to the selected memberships received in the reservation message, auto attachable membership(s) from other membership classes of Opera profile also will be attached to the Opera reservation. If 'N', only the selected memberships received in the reservation message will be attached to Opera reservation.
Reservations	COPY COMMENTS FROM PROFILE	GUEST	-> Direction: Data from external system to Opera. For profiles which have notes (Type: Reservation) associated with it, this parameter will determine whether to copy them on to reservation as comments. The value(s) of the parameter will also determine the type of profiles the copy is intended. Leave the value blank (null, which is default value) to avoid copying the reservation notes from profile to reservation as comments. If single value is selected then notes from that particular profile type are copied. If multiple values are selected then notes from those selected list of profile types are copied.
Reservations	EXT SYS MARKET/SOURCE CONTROL	ERBD	-> Direction: Data from external system to Opera. This parameter defines the sequence in which OXI identifies the market and source codes to apply in the reservation. R = Use the codes defined in rate definition (rate details first and then rate header), B = Use the codes defined in block definition, E = Use the codes received from the external system (after conversion, if applicable), D = Use the codes defined in OXI defaults, Y = When used alone, same as ED and N = When used alone, same as BRD. Set the value of this parameter by listing only the desired characters among R, B and E in the preferred order and optionally D as the last character without any delimiters.
Reservations	EXT SYS PRICE CONTROL		-> Direction: Data from external system to OPERA Applies to all settings: The reservation rate will be fixed if OPERA Fixed Rates is enabled and the inbound message includes an indicator (identified by a structured tag in the message) that the rate should be fixed. If the inbound message includes an indicator that the rate should not be fixed, the reservation rate will not be fixed. Y  -> External rate will be applied with the discounts present in the message. If OPERA Fixed Rates is enabled and the inbound message does not include the fixed rate indicator, the reservation rate will be fixed. YC -> External rate will be applied with the discounts present in the message. If OPERA Fixed Rates is enabled and the inbound message does not include the fixed rate indicator, then the rate comparison between the rate received in the message against the rate detail in OPERA will be done, if the rate in the inbound message does not match with the rate detail in OPERA, the rate will be fixed otherwise it will not be fixed. YD -> External rate will be applied with the discounts calculated as the difference between the rate received in the message and the OPERA rate detail amount. If OPERA Fixed Rates is enabled and the inbound message does not include the fixed rate indicator, then the rate comparison between the rate received in the message against the rate detail in OPERA will be done, if the rate in the inbound message does not match with the rate detail in OPERA, the rate will be fixed otherwise it will not be fixed. N  -> OPERA rate will be applied. Any discounts present in the message will be ignored. If OPERA Fixed Rates is enabled and the inbound message does not include the fixed rate indicator, the reservation rate will not be fixed.
Reservations	DEPOSIT RECEIVED CANCEL DELIVERY	NORMAL	-> Direction: Data from Opera to external system. NORMAL: No special handling, queues message for online delivery and offline delivery, if configured. OFFLINE_ONLY: Does not queue message for online delivery. Queues message for immediate offline delivery, if configured.
Reservations	EXT SYS PACKAGE PRICE CONTROL	N	-> Direction: Data from external system to Opera This parameter determines whether to use the package prices received in the message or the package prices configured in Opera.   Y = Use the price received from the external system in the message (if package price is not received in the message, uses Opera price).   N = Use the price defined in Opera package configuration.
Reservations	IGNORE RES FOR UPDATE OLDER THAN		-> Direction: Data from external system to Opera Enter a numeric value that will be translated into number of days. The value entered here will determine how many days in the past OXI will consider existing reservations for update when matching on external reference number. If the external reference number sent in the message matches the external reference of an existing reservation, then that reservation will be considered for update if the departure date of the existing reservation is same or later than the number of days in the past entered in this parameter.  If the departure date of the existing reservation is earlier than the number of days in the past entered in this parameter, then the existing reservation will be ignored and a new reservation will be created. If this parameter is left blank, then ALL existing reservations will be considered for update, except for HOLIDEX interface. For HOLIDEX interface, blank is treated as zero. Default setting is blank and this parameter should be left blank if the external system will always send a unique confirmation number.
Reservations	ITEM INVENTORY EXT SYS OVER	Y	-> Direction: Data from external system to Opera. This parameter determines whether to accept reservation inventory item updates from external system. Set to 'Y' and reservation inventory items will always be overwritten by external system. Set to 'N' and reservation inventory items sent by external system will be ignored.
Reservations	ITINERARY FUNCTIONALITY	N	OXI will not support Itinerary Reservations
Reservations	PACKAGE EXT SYS OVER		-> Direction: Data from external system to Opera: This parameter determines how the package elements received from the external system updates the packages in Opera.   A = If received, replace Opera values with the received values. If not received, remove the values from Opera.   B = If received, replace Opera values with the received values. If not received, do not remove the values from Opera.   C = If received, merge the received values with Opera values. If not received, remove the values from Opera.   D = If received, merge the received values with Opera values. If not received, do not remove the values from Opera.   N = Ignore the package elements received. Do not touch the values in Opera.
Reservations	PROMOTION EXT SYS OVER	N	-> Direction: Data from external system to Opera This parameter determines whether Promotion elements sent by external system shall overwrite Opera Promotion elements or not. Overwriting may be desired, as the property should decide what Promotions the guest has in this reservation.  Set to 'Y' and reservation Promotions will always be overwritten by external system Promotions. Set to 'N' and Promotion elements sent by external system will be appended to existing ones in Opera.
Reservations	REINSTATE CANCELLED RESERVATION		Direction: Data from External System to OPERA. This parameter determines how cancelled reservations will be reinstated when processing inbound reservation messages. ALWAYS:  Cancelled reservations will be reinstated when the action type in the reservation message indicates UPDATE or REINSTATE or RESYNC. REINSTATE:  Cancelled reservations will be reinstated only when the action type in the reservation message explicitly indicates REINSTATE or RESYNC.  If the action type in the reservation message is different, reservation will not be reinstated and an appropriate error will be logged.
Reservations	RESCOMMENTS EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter determines whether reservation comments sent by external system shall overwrite Opera comments or if they shall be appended to existing ones. If set to 'Y' the Opera reservation comments will always be overwritten by the external system comments. If set to 'N', only comments where the update user = external system ID in the Opera database will be updated.
Reservations	SHARER REMOVAL MODE		-> Direction: Data from external system to Opera. Applicable only when FULL OPERA SHARES=N. This parameter determines how should OXI handle share reservations those found in Opera but not coming in the message. CANCEL: Cancels any sharer present in Opera which does not appear in the incoming message. DELETE: Deletes any sharer present in Opera which does not appear in the incoming message. NEITHER: Leaves sharer(s) those present in Opera untouched, even if they don't appear in the message.
Reservations	SPECIALS EXT SYS OVER	Y	-> Direction: Data from external system to Opera This parameter determines whether special requests sent by the external system will overwrite the ones in Opera, or if they will be appended to existing ones. The functionality of this parameter is further determined by the 'mode' of your interface. If it works with delta changes set to 'yes' (interface configuration->edit interface), the external system can send reservation changes only and does not need to send the full reservation every time a small change to a reservation occurs. OXI will then only update the changed data and not touch the additional data that was found in the Opera reservation. This also means that the external system needs to indicate intended deletions clearly with deletion indicators in the message. Sending simply blanks will not lead to data deletion if OXI works in 'delta mode'. The deletion indicators can be configured in interface configuration->edit interface. If your interface is set to delta changes 'no', OXI expects a full overlay of all profile data in every profile message, even if the external system only changes very little of the entire profile. Here is how the parameter works: If set to 'Y' and the interface is setup as 'Delta Changes = 'Y', ONLY the specials originally inserted by the external system will be overwritten. If set to 'Y' and the interface is setup as 'Delta Changes = 'N', all reservation specials in Opera will be overwritten by the external system specials. If set to 'N', new specials will be appended to existing ones in Opera, regardless whether the interface works in delta mode or not.
Reservations	TRACE DEPT FOR NON REVIEWED		-> Direction: Data from external system to Opera When a non-reviewed reservation message received from the external system is processed, a trace will be logged against this trace department.
Reservations	TRACE DEPT FOR FAILURE IN EXT SYS		-> Direction: Data from external system to Opera When the external system can't process a reservation message received from Opera, if it sends a result message back to Opera indicating the error, a trace with the error message will be logged against this trace department.
Reservations	UPDATE ACCOMPANY GUEST	A	-> Direction: Data from external system to Opera This parameter determines how the accompany guest received from the external system updates the accompany guest in Opera.   A = If received, replace Opera values with the received values. If not received, remove the values from Opera.   B = If received, replace Opera values with the received values. If not received, do not remove the values from Opera.   C = If received, merge the received values with Opera values. If not received, remove the values from Opera.   D = If received, merge the received values with Opera values. If not received, do not remove the values from Opera.   N = Ignore the accompany guest received. Do not touch the values in Opera.
Reservations	UPDATE ALERTS	A	-> Direction: Data from external system to OPERA This parameter determines how the Reservation Alerts received from the external system will get processed in OPERA. A = If received, replace OPERA values with the received values. If not received, remove the values from OPERA. B = If received, replace OPERA values with the received values. If not received, do not remove the values from OPERA. C = If received, merge the received values with OPERA values. If not received, remove the values from OPERA. D = If received, merge the received values with OPERA values. If not received, do not remove the values from OPERA. N = Ignore the Reservation Alerts received. Do not touch the values in OPERA.
Reservations	UPDATE FEATURES	N	-> Direction: Data from external system to Opera. This parameter determines how the features received from the external system updates the features in Opera. A = If received, replace Opera values with the received values. If not received, remove the values from Opera. B = If received, replace Opera values with the received values. If not received, do not remove the values from Opera. C = If received, merge the received values with Opera values. If not received, remove the values from Opera. D = If received, merge the received values with Opera values. If not received, do not remove the values from Opera. N = Ignore the features received. Do not touch the values in Opera.
Reservations	UPDATE FIXED CHARGES	A	-> Direction: Data from external system to Opera This parameter determines how the fixed charges received from the external system update the fixed charges in Opera reservation.   A = If received, replace Opera values with the received values. If not received, remove the values from Opera.   B = If received, replace Opera values with the received values. If not received, do not remove the values from Opera.   C = If received, merge the received values with Opera values. If not received, remove the values from Opera.   D = If received, merge the received values with Opera values. If not received, do not remove the values from Opera.   N = Ignore the fixed charges received. Do not touch the values in Opera.
Reservations	UPDATE PAYMENT TYPES PER WINDOW	D	-> Direction: Data from external system to Opera This parameter determines how the payment types per window received from the external system updates the information in Opera.   A = If received, replace Opera values with the received values. If not received, remove the values from Opera.   B = If received, replace Opera values with the received values. If not received, do not remove the values from Opera.   C = If received, merge the received values with Opera values. If not received, remove the values from Opera.   D = If received, merge the received values with Opera values. If not received, do not remove the values from Opera.   N = Ignore the payment types per window received. Do not touch the values in Opera.
Reservations	UPDATE ROUTING TO ROOM	Y	-> Direction: Data from external system to Opera. This parameter determines how the room routing instructions received from the external system update the room routing instructions in Opera reservation.   Y = Replace all the Opera routings with the received routings. If no routings are received, remove all the Opera routings.   C = Accept all the valid routings received into Opera, remove only those Opera routings with codes configured in conversion but not received in the message.   N = Ignore the routings received. Do not modify any routings in Opera.
Reservations	UPDATE ROUTING TO WINDOW	Y	-> Direction: Data from external system to Opera. This parameter determines how the window routing instructions received from the external system update the window routing instructions in Opera reservation.   Y = Replace all the Opera routings with the received routings. If no routings are received, remove all the Opera routings.   C = Accept all the valid routings received into Opera, remove only those Opera routings with codes configured in conversion but not received in the message.   N = Ignore the routings received. Do not modify any routings in Opera.
Reservations	UPDATE SHARE RES	N	-> Direction: Data from external system to Opera This param. allows external systems to update a share reservation in Opera. If set to Y, OXI will accept changes to shared reservations in Opera based on a strict set of rules: 1) Based on the OXI param. UPDATE_INHOUSE_RES, the external system can send changes to checked-in sharers except for changes to the arrival date and room type. 2) In case the external system sends a change to the departure date, OXI will check if the room # assigned to the guest is still available for the extended stay. If not, the change will be rejected with an explicit error message. The currently assigned room number will not be removed. OXI will log all warnings in its status tables, visible to the user 3) If the OXI Param. FULL_OPERA_SHARES is set to N, changed reservation data will be updated equally for all sharers. If for example an update to market code, booker, comment, etc are sent in the reservation change message, OXI will update the same data equally in all share reservations. 4) If the OXI Param. FULL_OPERA_SHARES is set to N, all changes to the reservation will be applied to all sharers alike except for the data mentioned in the following bullet points. This means that formerly inserted changes to the share reservations in Opera are overwritten. 4a) Rate changes: OXI will apply the rate amount change to the primary sharer, which is identified by the lowest Opera confirmation #. 4b) If changes to the membership details are sent by the external system, this will only be applied to the primary sharer reservation and profile. For data from Opera to an external system, OXI will only send changes to non-inventory fields if these changes have occurred on the primary sharer, the reservation with the lowest Opera confirmation #. If this param. is set to N, OXI will reject any changes to shared reservations in Opera.
Reservations	UPDATE TRANSPORTATION COMMENTS	N	-> Direction: Data from external system to Opera. This parameter setting will determine if the transportation comments in OPERA reservation should be modified or not. If the value is set to 'Y' the transportation comments in OPERA reservation will be updated or deleted based on the existence of transportation comments in the received message. If the value is set to 'N' the transportation comments in OPERA reservation will not be modified in anyway irrespective of the transportation comments existence in the received message.
Reservations	UPL DED RES ONLY	N	-> Direction: Data from Opera to external system If set to 'Y', only deductible and non-waitlisted reservations will be sent to the external system. In a reservation this is determined by the reservation type and status, and means that only reservations with deductible reservation types and non-waitlisted status would be sent. This is desirable if the external system does not have a concept of tentative and definite reservations and would regard all bookings equally deductible regardless of their status. Set to 'N' if all reservations should be sent to the external system irrespective of the reservation type and status.
Stays	ALTERNATIVE STAY PROFILE SEARCH	ENABLED	-> Direction: Data from external system to Opera Valid values are ENABLED and DISABLED. ENABLED means that profile for the stay will be searched in ORS by its reservation confirmation number or membership number as alternative to the current subscription search before setting values in the stage table. DISABLED means it will follow the usual process and match stay profiles by their existing subscription ID.
Stays	BYPASS CONVERSION	CRMVBNS	-> Direction: Data from external system to Opera Valid values are CDRMVBNS and X. CRMVBNS means that when conversion fails for a particular field the record is not staged and the value from the external system is inserted in the stay record. Mapping for each field is C : CURRENCY CODE R : RATE CODE M : MARKET CODE V : REVENUE TYPE B : MEMBERSHIP TYPE N : CHANNEL CODE S : SOURCE CODE D : Membership Card No. will not be validated on the profile for stay records older than 30 days. For example if the parameter has values MS then if no conversion for the incoming market code (M) is found the record is not staged and external value gets inserted. if no conversion for Channel (N) is found then the record is staged until conversion is created or external value is changed to a convertible value.
Stays	BYPASS VALIDATION	ENABLED	-> Direction: Data from external system to Opera Valid values are ENABLED and DISABLED. ENABLED means that external value will be inserted in the stay record without validation. DISABLED means that the validation will be performed first and external value inserted if it passes the validation.
Stays	PRIMARY MEMBERSHIP	ENABLED	-> Direction: Data from external system to Opera Valid values are ENABLED and DISABLED. ENABLED means all memberships sent by the external system will create a membership transactation in Opera. Example for V6:   If MEMBERNR is populated in the reservation and the guest belongs to the Primary Membership then the system will automatically create the Membership Transaction for the Primary Membership. DISABLED means that memberships transactions will only be generated based upon values sent in FFPTYPE, FFPNUM, FGPTYPE and FGPNUM on the reservation by the external system.