22 Interface Mapping

Interface Mapping is used to configure conversion values for the OPERA Codes and External System Codes.

Parent topic: Exchange

System Default Conversions

You can define the conversion values for the available conversion codes. A few conversion codes are activated and populated through the OXI installation wizard, as they contain the same values for all interfaces and are never changing. These conversion codes are Reservation Status, Reservation Action Types, Profile Types, and Guest Preference Types.

Standard Conversion Code Settings. These conversion code settings apply to all interfaces.

Conversion Code OPERA Value External Value External>OPERA OPERA>External

Action Type

CANCEL

CANCEL

Y

Y
 

CHECK IN

CHECKIN

Y

Y
 

CHECK OUT

CHECKOUT

Y

Y
 

DELETE RESERVATION

DELETE

Y

Y
 

JOIN GUEST

SHARE

Y

Y
 

NEW RESERVATION

ADD

Y

Y
 

NOSHOW

NOSHOW

Y

Y
 

REACTIVATE NO SHOW

REINSTATE

N

Y
 

REACTIVATE WAITLIST

WAITLISTTOACTIVE

Y

Y
 

REVERSE CHECK IN

CNXCHECKIN

Y

Y
 

REVERSE CHECK OUT

CNXCHECKOUT

Y

Y
 

ROLLBACK CANCEL

REINSTATE

Y

Y
 

SEPARATE GUEST FROM

ADD

N

Y
 

UPDATE RESERVATION

EDIT

Y

Y

Document Type

    

Y

Y

Guest Preference Type

NEWSPAPER

NEW

Y

Y
 

ROOM_FEATURES

FEA

Y

Y
 

SMOKING

PRS

Y

Y
 

SPECIALS

SPE

Y

Y

Profile Type

COMPANY

CORPORATE

Y

Y
 

D

GUEST

Y

Y
 

G

GROUP

Y

Y
 

S

WHOLESALER

Y

Y
 

TRAVEL_AGENT

TRAVEL

Y

Y

Reservation Status

CANCELLED

CANCELED

Y

Y
 

CHECKED IN

INHOUSE

Y

Y
 

CHECKED OUT

CHECKEDOUT

Y

Y
 

NO SHOW

NOSHOW

Y

Y
 

PROSPECT

REQUESTED

Y

Y
 

RESERVED

RESERVED

Y

Y
 

WAITLIST

WAITLISTED

Y

Y
From the Interface Mapping screen:

  • The Search panel allows you to search by Interface Type, Property and Interface code. Result panel shows all the defined mappings or conversions with OPERA code and External Code.

  • Select a Group and Create New Mappings in right pane with the New option with the OPERA Code, External Code, and Enable/Disable Data Flow options.

  • Select a Group and Edit existing conversions with the Edit option, update codes and the enable/disable Data flow options.

  • Select a Group and Specific Mapping in the right panel and delete the invalid conversions.

  1. From the OPERA Cloud Exchange menu, select Interface Mapping and then select Interface Mapping from the drop down list.
  2. On the Interface Mapping screen, select a group. Search for a Property and an Interface and click Search.
    1. From the search results, select a defined mapping or conversion.
    2. In the right panel, you have an option to create a new mapping or conversion. For example:
  3. Click Account Type group from the search results.
  4. In the Account Type panel that opens, you can see the configured mapping.
  5. Click New to create a new mapping or conversion.
    1. The Default Interface Type is displayed or you can select one from the drop-down list.
    2. The Default Property is displayed or you can search for another property by clicking the search icon.
    3. The Default Interface is displayed or you can search one by clicking the search icon.
    4. Search for OPERA Code.
    5. Enter an External Code.
  6. Click Edit to edit an existing group mapping.
    1. The fields for Interface Type, Property, and Interface are disabled. You cannot edit these fields.
    2. Select an OPERA Code and enter an External Code and then click Save.
  7. Click Delete, to delete a mapping.
  8. Select the Show Inactive check box for first time activation of the conversion table. Highlight the conversions that are used and select the Activate button. To deactivate a conversion code, uncheck the Show Inactive box, highlight a conversion code, and select Inactivate.
    When creating a new Profile Type Mapping and select:

    • External-OPERA Default: A check mark indicates what OXI uses as default in the case of multiple same entries in the external system value column. It is possible that more OPERA values than the external system values exist for a conversion code. In this case the external system values would need to be duplicated and will occur more than once in the external system value columns.

      • Only one of the duplicate external system values can be set as External->OPERA Default Y, and this is the record that OXI uses when processing data from the external system to OPERA.

      • All other duplicate codes are set to N. OXI automatically warns you if a record has already been set to Y as a default, and you are trying to flag another record with the same external system value the same way.

    • OPERA-External Default: A check mark indicates what OXI uses as default in the case of multiple same entries in the OPERA value column. It is possible that more external system values than OPERA values exist for a conversion code. In this case the OPERA values need to be duplicated and occur more than once in the OPERA value columns.

      • Only one of the duplicate OPERA values can be set as OPERA > External Default Y, and this is the record that OXI uses when processing data from OPERA to the external system.

      • All other duplicate codes are set to N. OXI automatically warns you if a record has already been set to Y as a default, and you are trying to flag another record with the same external system value the same way.

    For example: The external system has more market codes than OPERA, and the OPERA market codes have to be entered multiple times in the conversion code. If a reservation with such a market code is sent by OPERA, OXI has to know which conversion record to use. The OPERA-> External Default is the identifier for the correct conversion record.

    Table 22-1 OPERA and External Default Values

    OPERA Value External System Value External>OPERA OPERA>External

    GRP

    GROUP

    Y

    Y

    GRP

    LEIS

    Y

    N

    IND

    INDIVIDUAL

    Y

    N

    IND

    TRANSIENT

    Y

    Y