Handling ETIM Data in the System

This topic explains the current behavior of the STEP system during the ETIM import process, focusing on how it processes existing and new elements, applies ID patterns, and manages revisions.

Reusing existing elements

When importing ETIM data into STEP using ETIM Taxonomy API Importer, the system first checks if existing elements (attributes, units, LOVs) can be reused. The system uses comparators where the system searches for existing elements available in the system by their ETIM codes. It compares the values of these elements with the incoming data. If there is an exact match, the existing element is reused. Otherwise, a new element is created.

Note: The table below mentions instances where an attribute copy or the unit copy is created. When this occurs, the system adheres to the ID pattern described in the later section of this topic. Typically, the copied attribute's ID mirrors the original but includes either the new ETIM version or a revision number appended to it.

The table below provides a detailed explanation of how the system handles attributes, units, and LOVs when an ETIM version already exists in STEP, and a subsequent version (either higher or lower) is imported. It outlines the processes and rules applied to manage these elements effectively.

STEP Main Object	STEP Linked Object	Change description	Change to the Main Object	Change to the Linked Object	Remarks
Unit		Name of unit Translated name of the unit	Create a copy of unit.		If new ETIM data contains a unit where only the name or the translated name of the unit has changed, the system will create a copy of the unit.
Attribute		Description Translated description Order Number	Existing attributes in the system will be reused and new attributes will not be created		If ETIM data contains an attribute linked to a classification where only the description, translation of the description, or order number of the attribute has changed, the system reuses the existing attribute. No duplicate or revised version of the attribute is created. It will update the description / order number to the existing attribute in the system
Attribute	Unit	Description of unit Translated description of unit	The existing attribute in the system is reused, and no new attribute is created.	The existing unit linked to the attribute in the system is reused, and no new unit is created.	If ETIM data includes an attribute (with units) linked to a classification where only the description or translated description of the unit has changed, the system reuses the existing attribute and unit. No new or revised versions of the attribute or unit are created.
Attribute	Unit	Unit name Translation of Unit name	Create a copy of the attribute.	Create a copy of the unit with new name / translation if a similar unit does not already exist in the STEP system. If it exists, reuse the existing unit.	If ETIM data includes an attribute (with units) linked to a classification where only the unit name or the translation of the unit name has changed, the system creates a new copy of the attribute. For the unit, a copy is created with the new name or translation, provided that a similar unit does not already exist in the STEP system. If such a unit already exists, the system reuses the existing unit.
Attribute	Unit	The attribute in STEP is linked to a different unit than the one associated with the attribute from the ETIM server. The attribute in STEP does not have a linked unit, while the attribute from ETIM includes one. The attribute in STEP is linked to multiple units.	Create a copy attribute if no attribute exists in STEP with the same ETIM code and linked unit name.	The importer looks for the unit in STEP by ETIM code, compares it, and if they match, it links it to the attribute. If they donot, it creates a new unit and links it.	If ETIM data includes an attribute (with units) linked to a classification and the following conditions occur: The attribute in STEP is linked to a different unit than the one associated with the attribute from the ETIM server. The attribute in STEP does not have a linked unit, while the attribute from ETIM includes one. The attribute in STEP is linked to multiple units. In STEP, the system handles attributes by creating a copy if no existing attribute matches the ETIM code and linked unit name. For units, the importer searches STEP by ETIM code, compares the unit details, and, if a match is found, links the unit to the attribute. If no match is found, it creates a new unit with the appropriate details and links it to the attribute.
Attribute	Unit	The attribute in STEP is linked to a unit, whereas the attribute in ETIM is not.	Create a copy of the attribute if no existing attribute in STEP has the same ETIM code and lacks a linked unit.	No creation / duplication of units.	If an attribute in STEP is already linked to a unit, while the corresponding attribute in ETIM is not, the system creates a duplicate of the attribute only if there is no existing attribute in STEP with the same ETIM code and without any linked unit. For the unit, no new creation is necessary.
Attribute	LOV	An LOV valid type attribute linked to a classification in STEP has a different filter definition than compared to the ETIM data.	Try reusing an existing relevant attribute. If not create a copy of the attribute.	Values in the existing LOV is updated.	If an LOV valid-type attribute is linked to a classification in STEP and its filter definition differs from the one in the ETIM data, the importer follows this process: Identify attributes by ETIM code: The importer first narrows down all attributes in the system with the same ETIM code, including both original and copied attributes. Check existing linked attributes with matching Filter: Among the narrowed results, the importer searches for attributes that already have the required filter definition and are linked to the same classification of a different version. If such an attribute exists, it is reused. Search for unused attributes: If no linked attribute with the required filter definition exists, the importer searches for unused attributes with the same ETIM code in the narrowed results. If found, this attribute is reused. Create a new attribute: If neither of the above criteria is met, the importer creates a copy of the attribute, assigns it a new ID following the pattern described in the later section of this topic, and links it to the classification. The values in the existing LOV will be updated as needed to align with the filter definition.
Attribute	LOV	Description of LOV Translated description of LOV	The existing attribute in the system is reused, and no new attribute is created.	Values in the existing LOV is updated	If an LOV-valid type attribute is linked to a classification in STEP, and the description or translated description of the LOV is changed, the importer will reuse the existing attribute in the system. No new attribute will be created. The values in the existing LOV will be updated accordingly.
Attribute	LOV	Order Number	The existing attribute in the system is reused, and no new attribute is created.	No change to the existing LOV	If an LOV valid-type attribute is linked to a classification in STEP, and the order number of the LOV values is changed, the importer will reuse the existing attribute in the system. In this case, no new attribute is created, and the LOV values remain unchanged.

ID Patterns for ETIM Elements

The system applies the following ID patterns to ensure consistency:

For the elements that are reused across multiple ETIM versions:

IDs are generated as:

ETIM_("ETIM_Code")_("ETIM_Revision_Number").

ETIM("ETIM_Version_Number")_("ETIM_Code")_("ETIM_Revision_Number").

Note: Attributes and units created for specific ETIM versions cannot be used in dynamic ETIM versions, and vice versa. However, LOVs can be utilized in both dynamic and specific versions.