Mapping Rules set on interface level

What are mapping rules and how does it work?

The purpose of this functionality is to assist users avoid the most common mapping errors by presenting them with a number of valid choices.

Its the ability to predefine generic mapping rules to prevent “Not Applicable” combinations (room revenue to Front Office not possible) so that we avoid mapping errors being committed. You are also able to add comments to a mapping for example when a specific property wants to ignore parking revenue as its a third party revenue.

Predefined rule sets

There are a number of pre-defined rule sets. These are set to cover all normal source data and current PMI setup. The objective with the Interface editor is to assign a correct Mapping rule set to the interface. Names given to the pre-defined rule sets should be easy to recognise and understand.

Mapping rules data sources

Its possible to set several mapping rules settings in Interface Editor, in the integration site,

Each mapping rule consists of 6 settings

Entity type, see screen shot below: Refers to the first dropdown list in the mapping table. Choose what should be available in the department dropdown list. Hotel, profit centers, cockpits or combinations of these. One special choice “Profit centers with OTB activated only” is for files such as Sales & Catering OTB. Example below: Revenue can be mapped to the Hotel (room revenue) and profit centers, and labor cockpits should not be available as an option.

  1. Choose Revenue, Net from the dropdown menu, and click on Edit
  2. A pop up appears, choose Revenue, Net from the dropdown menu, and choose Hotel only in the Entity type dropdown box.
  3. Save

Level, see screen shot below. Refers to the second dropdown list in the mapping table, the “segment dropdown”. This is only visible if segments exist.

This option is used only to map to segments, that already exists. Or if it should be opened up to map to total even if the segment exists. For example: For Revenue, we have a “hybrid” where we only want to map to total if we have chosen Hotel in the first dropdown (room revenue) and only to segments if it already exists in other departments.

Net/Gross, refers to the Tax field in the mapping table. If it is set to Net, the Tax field is then hidden from the users.

Exclude from total, see screenshot below. Refers to the choice Exclude from total in the mapping table. If we import data on segment level, we can exclude the segment data to be summed up to total level. Rooms, guests and revenue, or any combinations of these, can be excluded. As per the current setup, this is only used for Rooms import on segment level where we get room revenue from another file. Then we want revenue to be excluded. We recommend this is in place so that its not an issue for the user.

Food icon visible, refers to the food icon in the mapping table. Should be ticked when a revenue account is food. Can be set to No on all other import types than revenue

Revenue adapter, refers to the possibility to set revenue types in the mapping table. Revenue type must be activated in Hierarchy settings. A revenue account can be classified as Room revenue, F&B revenue, Other revenue and so on. None of our customers have this activated as this functionality is not currently used in PMI.

External code lookup, in the mapping table the Entity type dropdown list (department list) will search for a match between imported Department ID and External code on the department or Department type. It will only display the department(s) with a match. LIKE functions is used to find a match so it does not need to the exact name.

Was this article helpful?

Related Articles