5.12.7.1. Use of CNSORDERNO and CNSTYPECODE with examples

5.12.7. Classification according to CNSORDERNO / CNSTYPECODE 5.12.7.1. Use of CNSORDERNO and CNSTYPECODE with examples
Prev	Next

Classification according to CNSORDERNO or CNSTYPECODE?

CNSORDERNO = Order number (article number)
Order number is partly used for products with value range fields (yellow fields).
But 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.
Characteristic feature in both cases is that there is no strict relation between table values and parts of the order number. This is the essential difference in compare with CNSTYPECODE. See Fig. „Example: Clear relation between parts of type code and single variable values“.

Example project with order number without value ranges (yellow fields)
CNSTYPECODE = Typenschlüssel (Article code / order code)
Type code is partly used for products with particularly complex set of rules. In these cases the project has value range fields (yellow fields), whereby mostly a huge number of combination possibilities results.
Common product groups are: Cylinders, motors, gears, linear modules, if configurable and customizable.
But Type code 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 without value ranges (yellow fields)

	Note
Note/special cases In old catalogs/projects it is possible that there is no variable for article number or article code. In these cases the variable LINA can be used for the classification. This solution is NOT intended as default, but in fact only as solution for old projects. Furthermore please regard that the use of LINA can be unfavorable in some cases. 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.

Note

Note/special cases

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

This solution is NOT intended as default, but in fact only as solution for old projects. Furthermore please regard that the use of LINA can be unfavorable in some cases.

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 in eCATALOGsolutions correctly

	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.

Manufacturer uses four to six-digit numbers without leading zeros. On the side of PARTsolutions please regard, not to fill up with zeros.

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

Manufacturer Website
Manufacturer always uses a six-digit article number (also with leading zeros). In this case, in PARTsolutions, the zero must be contained in the catalog.

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