Item Mappings - Intergraph Smart Reference Data - Version 10.2 - Customization & Programming - Hexagon

Intergraph Smart Reference Data Integration (10.2)

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

Use the CADWORX 10.04 Item Mappings screen to define item mappings during setup of the interface or when you add new components or new specifications in Smart Reference Data (SRD).

To map SRD data for CADWorx export, it is recommended to maintain data in the following areas:

  • On the Sheet DependentSheet Mapping tab, specify which group/part/commodity code relates to which component data sheet.

    In the picture above, the sheet for component Cap is related to all commodity codes for part CP in group D. Accordingly, you can define the relations of other groups and parts. This is important also for the auto selection feature AUTO_SELECT_SHTS_FOR_PARTS.

Other mappings might depend on where the actual data is stored. Assuming that catalog data is maintained in template sheets, this mapping is recommended:

  • On the Sheet DependentAttribute MappingSpecs tab, you can map attributes for SpecHeader sheets on the specification level:

    DEF_FLG_TYPE

    RED_SEL_TYPE

    SIZE_TABLE

    MATL_TABLE

    WTHK_TABLE

    The picture below shows an example:

The same attributes could also be mapped sheet-independent on the specification level.

  • Some attributes are used on the SpecHeader and SpecItem sheet. So it is recommended to map the values as sheet independent. A value could be mapped for each of those attributes on the spec level. If some values deviate for single spec items, those values could be mapped for those spec items.

    Candidates for this kind of mapping are:

    • BOM_TYPE (though it is not used on spec header, it could be defaulted on this level)

    • NOM_RATING,

    • TEMP_RATING,

    • PRESS_RATING,

    • LAYER,

    • COLOR

  • Other attributes might be specific to a component, so the mapping level will be group/part or commodity code. It makes sense to map them for sheet SpecItem or even better as sheet-independent. Candidates are:

    • DATA_TABLE,

    • ENDTYPE_START,

    • ENDTYPE_END,

    • ENDTYPE_BRANCH_LEFT,

    • ENDTYPE_BRANCH_RIGHT,

    • USE_ONE_ENDTYPE,

    • MATERIAL_,

      The picture below shows an example: