# ERP to Omnitron Attribute Mapping

This tutorial provides comprehensive, step-by-step guidance on how to create and manage **ERP to Omnitron Mapping Rules** in Omnitron. These rules are essential for connecting ERP attributes and values to their counterparts in Omnitron.

During the setup phase, **Pre-Attributes** and **Pre-Attribute Values** are defined. These are intermediary representations that bridge ERP values to Omnitron's internal attribute system. Mapping Rules allow you to align these Pre-Attributes and their values with the corresponding **Omnitron Attributes** and **Attribute Values**.

## <mark style="color:red;">Access to Mapping Rules Page</mark> <a href="#zg9ull2dy945" id="zg9ull2dy945"></a>

* Navigate to **Integration > Mapping** in Omnitron.
* This page displays a comprehensive list of existing mapping rules. It includes tools to:
  * View mapping rules
  * Filter based on specific criteria
  * Create new rules
  * Edit existing ones
  * Delete rules

![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FwWqZtsx7G8yU6kZZxrEX%2F0.png?alt=media)

## <mark style="color:red;">View Mapping Rules</mark> <a href="#bxd1wrdblqyl" id="bxd1wrdblqyl"></a>

The Mapping Rules page lists each rule in a tabular format with the following columns:

* **ERP Features**: The ERP attribute being mapped.
* **Condition**: The logic applied to the ERP attribute. Options include:
  * Equal
  * Greater
  * Greater or Equal
  * Less Than
  * Less Than or Equal
  * Start
  * End
  * Contain
  * In
  * Is It Empty?
* **Value**: The value to evaluate according to the selected condition.
* **Attributes**: The Omnitron attribute to which the ERP attribute is mapped.
* **Value To Map**: The target Omnitron attribute value if the condition is met.
* **Default Attribute**: Choose between “Get Value from ERP Attribute” or a specific ERP attribute based on the condition.
* **Sorting**: Determines the priority of the rule. Lower values are prioritized.

![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F4mOIv3WjtDJzRVqfvXQS%2F1.png?alt=media)

## <mark style="color:red;">Filter Mapping Rules</mark> <a href="#ogvmv03ecwuj" id="ogvmv03ecwuj"></a>

Mapping Rules can be filtered using various parameters:

* **Attributes:** Filter rules by selecting a specific Omnitron Attribute.
  * **Value To Map:** After selecting an attribute, further filter by its specific value.

    <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FfIwZca9GFcKaz2C1QJat%2Fimage.png?alt=media&#x26;token=9352f259-6d35-431c-a5a4-5d52786ff036" alt=""><figcaption></figcaption></figure>
  * **Pre Attribute Values:** Click the funnel icon to select a Pre-Attribute. The system will display related values for precise filtering.

    <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FFNk4yEhVOfR15yIQYkpn%2Fimage.png?alt=media&#x26;token=e41175b4-fef3-4029-b4ac-4376cb6a5c17" alt=""><figcaption></figcaption></figure>

## <mark style="color:red;">Create or Edit a Mapping Rule</mark> <a href="#kzvgob40p40h" id="kzvgob40p40h"></a>

* To add a new rule, click the **+ New Rule Set** button.
* To edit an existing rule, simply click on the rule value from the list.
* You will be prompted to complete the necessary fields, as described above in the table column list.
* After completing the rule definitions, make sure to click the **Save Rule Set** button to save all configured mapping rules.

![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FLzbTATvq1rDotq1MoDuG%2F4.png?alt=media)

### <mark style="color:red;">Prerequisite: Define Attribute Codes for Mapping</mark>

Before you begin creating mapping rules, you must configure the `PRODUCT_MAPPING_KEY_LIST` dynamic setting in Omnitron.&#x20;

This step ensures that the system can correctly recognize which Omnitron attributes are eligible for ERP-based mapping.

To do this:

* Navigate to: **Settings > Omnitron Dynamic Settings >** `PRODUCT_MAPPING_KEY_LIST`
* Manually enter the **attribute codes** for all Omnitron attributes that will be mapped with ERP attributes.
  * For example, if the Omnitron attribute is **Color**, and its attribute code is `integration_color`, you must add `integration_color` to this list.
* You can add multiple fields using the **+ Add Field** button.
* Once all required attribute codes are entered, click **Save**.

{% hint style="warning" %}
Mapping rules will not function correctly unless the relevant attribute codes are listed in this setting.
{% endhint %}

## <mark style="color:red;">Delete a Mapping Rule</mark> <a href="#bkt7vv1kvt6e" id="bkt7vv1kvt6e"></a>

To remove a rule:

* Locate the rule in the Mapping Rule Sets list.
* Click the minus **(-)** icon next to the relevant entry.

This action will permanently delete the rule from your configuration.

![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FE6OqgDVz2qlQoDP5JpxK%2F5.png?alt=media)

## <mark style="color:red;">Mapping Logic for Dropdown Attributes</mark> <a href="#id-75yxabqejt5u" id="id-75yxabqejt5u"></a>

If the attribute type is **Dropdown**, there are two possible mapping strategies:

### <mark style="color:red;">1. Full Mapping with Existing Omnitron Values</mark> <a href="#je41qhrnd8yx" id="je41qhrnd8yx"></a>

If all attribute values already exist in Omnitron (defined under **Products and Catalogs > Product Attributes**), you can:

* Set **Condition** to: Is It Empty?
* Set **Value** to: No
* Leave **Value To Map** blank
* Set **Default Attribute** to: the related ERP Attribute

Note: For more details on defining attributes in Omnitron, [refer to here](https://docs.akinon.com/tutorials/omnitron/products-and-catalogs/how-to-create-product-attributes-and-attribute-sets-in-omnitron).

#### <mark style="color:red;">"Send As It Is" Setting</mark> <a href="#t8z1z9m8tz3u" id="t8z1z9m8tz3u"></a>

If you set:

* **Condition** = Is It Empty?
* **Value** = No

A checkbox labeled **Send As It Is** becomes available. When enabled, this option automatically creates Omnitron attribute values based on incoming ERP values — even if those values haven’t been defined yet in Omnitron.

![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F265KS7iHquqOsvaST5iD%2F6.png?alt=media)

### <mark style="color:red;">2. Selective Mapping with Value Manipulation</mark> <a href="#w6uuquib9o9l" id="w6uuquib9o9l"></a>

If only some ERP values need to be mapped or require transformation:

* Set **Condition** to: Equals
* Enter the ERP value in **Value**
* Enter the desired Omnitron value in **Value To Map**
* Set **Default Attribute** to: Get Value from ERP Attribute

![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FvoS55dBGzY0zujGJLj8r%2F7.png?alt=media)

You can define **multiple conditions** by clicking the **plus (+)** icon under a single mapping rule to handle variations in ERP values.

![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FYxOebHtX4IOv8a3QTcTo%2F8.png?alt=media)