# 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**.
## Access to Mapping Rules Page
* 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
## View Mapping Rules
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.
## Filter Mapping Rules
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.
* **Pre Attribute Values:** Click the funnel icon to select a Pre-Attribute. The system will display related values for precise filtering.
## Create or Edit a Mapping Rule
* 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.
### Prerequisite: Define Attribute Codes for Mapping
Before you begin creating mapping rules, you must configure the `PRODUCT_MAPPING_KEY_LIST` dynamic setting in Omnitron.
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 %}
## Delete a Mapping Rule
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.
## Mapping Logic for Dropdown Attributes
If the attribute type is **Dropdown**, there are two possible mapping strategies:
### 1. Full Mapping with Existing Omnitron Values
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).
#### "Send As It Is" Setting
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.
### 2. Selective Mapping with Value Manipulation
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
You can define **multiple conditions** by clicking the **plus (+)** icon under a single mapping rule to handle variations in ERP values.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.akinon.com/tutorials/omnitron/integration/erp-to-omnitron-attribute-mapping.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
