powered by CADENAS

Manual

Manual

3.2.16. Classification according to CNSORDERNO / CNSTYPECODE

PARTproject -> Edit project -> General tabbed page -> Variables -> Variable with order number and/or Variable with type code

[Note] Note
  • Classification of projects according to CNSORDERNO and/or CNSTYPECODE is mandatory [3]

    If a respective entry is missing, an error message is displayed when attempting to save.

  • Destinction between CNSORDERNO and CNSTYPECODE

    • Variable with order number (ORDERNUMBER): Can not be divided into segments. There is no direct link between single values of characteristic and parts of order number (regardless of whether numerical or alphanumerical).

      If project contains value range fields or not, it doesn't matter for the decision if ORDERNUMBER or TYPECODE. If there are value range fields, they can (but don't have to) change the order number. However, the change does not show any method.

      Example: Order number changes when changing value range value

      Example: Order number changes when changing value range value

    • Variable with type code (TYPECODE): The single parts of code are in relation to values of certain variables (e.g. type/serie, geometrical values such as length or diameter or other variable values defining the type code.

      Example: Clear relation between parts of type code and single variable values

      Example: Clear relation between parts of type code and single variable values

In PARTdataManager, you can switch between normal Full-text search and Order number/ Type code search .

The Order number/Type code search should be used, when explicitly searching for an Order number or Type code. Due to uniqueness this search will always directly lead to the desired result (if the catalog is accordingly prepared).

This method does not only lead to desired result when searching for a fixed Order number/Type code, but also then, when it is composed by values from value range variables and in fact both for simple and for complex combinations.

There are three basic cases:

  1. Simple catalog

    Catalog with only ONE article per row (which means no value ranges)

    -> For a new catalog creation just classify the variable (table column) of the order number (Variable with order number), nothing else.

    Example project without value ranges in PARTproject

    Example project without value ranges in PARTproject

    Example project without value ranges in PARTdataManager

    Example project without value ranges in PARTdataManager

    For already existing catalogs the respective mapping can be adjusted semi-automatically by the catalog manufacturer/modeler with little effort. Depending on manufacturer it may be possible that different identifiers are available. These variants have to be considered. Information on the plugin "Adjust order number and type code" can be found below.

    Also see under Section 5.9.2.3, “ Menu item Variables ”.

  2. Catalog with value ranges which simply can be resolved

    "Simple" means the number of combination possibilities.

    Default limit is less than 25.000 combination possibilities per project and 50.000 per catalog in addition to the standard rows. The setting is made by configuration file %cadenas_setup%/partsol.cfg. On this see under Section 3.2.16.2, “Limit resolving of value ranges (yellow fields) via config key ”.

    • -> Here, the classification of the order number is also required (as in 1.) (Variable with order number).

    • -> Furhermore under Search index creation -> Index order numbers dependent on value ranges, the correct entry has to be set. Thereby it is controlled, which projects have to be automatically resolved.

      To simplify the procedure you have a plugin available for this. See Section 5.8.2.1.15.15, “Resolve check ”.

    Search index creation -> Index order numbers dependent on value ranges

    Search index creation -> Index order numbers dependent on value ranges

    Example project with indexed value ranges displayed in PARTdataManager

    Example project with indexed value ranges displayed in PARTdataManager

  3. Catalogs with value ranges, which can NOT simply be resolved

    These are catalogs with very complex value ranges, where resolving would create millions and billions of combination possibilities, which exceeds the config limit.

    Example project with many value range variables, which build-up the part number interactively

    Example project with many value range variables, which build-up the part number interactively

    The effort is higher here, but is profitable for the manufacturer in any case

    • Via Order number / Typecode articles on PARTcommunity portals can safely be found and correctly be ordered.

      Deeplinks are no more required.

    • Initial article assignment of ERP numbers to PARTsolutions projects on the base of Order number / Typecode is simplified, as numbers are absolutely unique.

    • Better search results, since even values from complex value ranges are found.

    Also see Section 3.2.16.8, “Benefits of classification according to CNSORDERNO and CNSTYPECODE”.

  4. Special case at 2) and 3): Only a certain number of the actual combination possibilities resulting from value range fields has an order number and is really available or orderable.

    -> A CSV (pnomapping.csv) with mapping information on Order number and Typecode is stored in the catalog root directory.

    pnomapping.csv, column names "PARTNUMBER" and "TYPECODE", semicolon as delimiter

    pnomapping.csv, column names "PARTNUMBER" and "TYPECODE", semicolon as delimiter

    -> Search entry is order number in search mode Search for order number / type code , in fact, the search is performed with the type code in background.

    [Caution] Caution
    • Use case should not be to avoid order number in the table, but only the above mentioned.

    • The order number will not appear in the search result, as it is not present in the table.

      If the order number is needed in the table, it has to be implemented separately (which has nothing to do with the described special case).

    • The order number will not be exported to the CAD, BOM etc.

    Example: Search with order number, display of type code in the table

    Example: Search with order number, display of type code in the table



[3] The Class variables CNSORDERNO and CNSTYPECODE are mapped to the desired variable under Variable with order number and Variable with type code. Also see Section 5.9.2.3.1, “Transfer attributes via CNS classification ”.