5.12.7.1. Use of CNSORDERNO and CNSTYPECODE with examples

  • Classification according to CNSORDERNO or CNSTYPECODE?

    • CNSORDERNO = Order number (article number)

      Order number is sometimes used for products with value range fields (yellow fields).

      Order number is also used for products without value range fields (yellow fields).

      Common product groups are: Brackets, switches, bolts, nuts, but also more complex parts.

      The characteristic feature in both cases is that there is no close relationship between table values and components of the order number. This is the decisive difference to CNSTYPECODE. There is a strict system here. Compare Fig. „Example: Clear relation between parts of type code and single variable values“.

      Example project with order number without value ranges (yellow fields)

      Example project with order number without value ranges (yellow fields)

    • CNSTYPECODE = type code (article code / order code)

      Type codes are sometimes used for products with a particularly complex set of rules. In these cases, the project has value range fields (yellow fields), which usually results in a large number of possible combinations.

      Common product groups are: Cylinders, motors, gears, linear modules, if configurable and customizable.

      However,type codes can also be used for products without value range fields.

      Characteristic feature in both cases is that there is a strict relation between table values and parts of the type code.

      Example project with type code and value ranges (yellow fields)

      Example project with type code and value ranges (yellow fields)

      Example project with type code without value ranges (yellow fields)

      Example project with type code without value ranges (yellow fields)

    [Note]Note

    Note/special cases

    For legacy catalogs/projects, it is possible that there is no variable for article number or article code. In these cases, the LINA variable can be used for classification.

    The solution is NOT intended as a default, but actually only as a solution for legacy projects. It should also be noted that the use of LINA can also be unfavorable.

    Example:

    Primary / Secondary Key (Code / Type)

    Article number: 158473 -> CNSORDERNO classification.

    Article code: DNC-100-63-PPV-P -> CNSTYPECODE classification.

    LINA: 158473 (DNC-100-63-PPV-P) -> If LINA maps both article number and code, then it cannot be used individually as CNSORDERNO or as CNSTYPECODE.

  • Enter article number correctly in eCATALOGsolutions

    [Note]Note

    In the case of leading zeros in the article number please regard the exact use on the manufacturer side, otherwise searching and attribute mapping won't work.

    1. Manufacturer uses 4 to 6-digit numbers without leading zeros. On the PARTsolutions website, make sure that no zeros are added.

      Negative example from PARTsolutions table: Erroneously, it was filled up with zeros.

      Negative example from PARTsolutions table: Erroneously, it was filled up with zeros.

      Manufacturer Website

      Manufacturer Website

    2. Manufacturer always uses a 6-digit article number (also with leading zeros). The 0 must be included in the catalog at PARTsolutions.

  • Hidden variables can also be used for a mapping. The variable is considered when indexing and can be searched.