Mapping using Table Details for Hierarchical codelist - Intergraph Smart Reference Data - Version 10.1 - Customization & Programming - Hexagon

Intergraph Smart Reference Data Integration (10.1)

Language
English
Product
Intergraph Smart Reference Data
Search by Category
Customization & Programming
Smart Materials/Smart Reference Data Version
10.1

The EndPreparation sheet displayed in the picture below is used as an example of the table detail method.

Because the codelist data is fetched from the table details of one commodity attribute table, the hierarchy (level structure) must be defined using the Parent Table Details field on the Tablenames with Details screen.

The EndPreparation ShortDescription and LongDescription values are fetched from the table detail short desc/description and the corresponding codelist number from the physical attribute, which is assigned to the table detail attr_num1/char1. In our example, the table details AA, AB, AC, AD with parent table detail XA (Flanged) assigned are considered to be the lowest level 0 (zero) because the table details are not assigned as the parent table detail to other table details.

Parent table mapping

The TerminationSubClass ShortDescription and LongDescription values are fetched from the table detail short desc/description and the corresponding codelist number from the attribute Codelist_Number. The table details XA, XB with parent table detail YA (Bolted) assigned are considered to be level 1.

The TerminationClass ShortDescription and LongDescription values are fetched from the table detail short desc/description and the corresponding codelist number from the attribute Codelist_Number. This table detail does not have a parent table detail assigned, so it is considered to be the highest level 2.