Alternative Item Codes for Bolts

Alternative item codes for bolts are taken from UDAs set on DTAB elements, not on the SPCOM like other elements (see Alternative Item Codes).

Note: For additional bolting items such as washers and nuts, the UDA must be set on SPCOM because these items do not have associated DTAB elements.

Alternative item codes for bolts are set up as follows:

• The SBOLT elements must have NSTD attributes pointing to the DTAB elements.

• The names of the UDAs on the DTAB elements must be related to the UDAs set for the SPCOM. For example, if the SPCOM UDAs are named: clienta and :clientb, there could be one set of DTAB UDAs named :clienta1,:clienta2, and another set of UDAs named clientb1, clientb2,

• The item codes are stored in the DTAB UDAs as texts separated by spaces. As text UDAs have an upper limit of 120 characters, the list of item codes continues across the set of UDAs.

• For example, if each item code is 10 characters in length, then 11 item codes can be stored in each UDA of the set.

• The number of item codes stored in each set of UDAs (for example, all the UDAs for clientb) should correspond to the number of elements in the BLEN attribute of the DTAB.

  Notes:
  - Normally, the user can use the same SBOLT element for bolts with the same geometry, and the material will be defined in the Specification. When bolts of the same geometry but different materials are used, the user will need to create a DTAB for each SBOLT element and an SBOLT for each Bolt SPCOM if they want to set different item codes.
  - The user must make sure that a consistent set of UDAs are set up in the Lexicon database.

The following example shows part of a specification and part of a catalogue. Note that SPECON cannot output UDAs in tabular format, and so this example is just for illustration.

Part of Specification

Part of Catalogue