6.1.3. Background information
6.1.3.2. Internal treatment of variants
Prev  Next

6.1.3.2. Internal treatment of variants

The following figure shows a part with value ranges (semi-manufactured products) in the PARTdataManager. Different lengths receive their own ERP number. Aside from that, different materials were used and a "real" geometric variant for the variable "B" was set.[10], [11]

Different types of variants in the PARTdataManager

Different types of variants in the PARTdataManager

The following figure shows how the variants are displayed in the PARTlinkManager.

All rows are based on the same row ID [Line ID] and differ in the row subID [Line sub ID]. "Real" variants (change in a NON-value range field) have the entry 1 in the Variant column.

Different types of variants in the PARTlinkManager

Different types of variants in the PARTlinkManager

The table describes the differences in detail:

Line ID Line sub ID Variant Variant type (explanation)
18000 The first entry ; no change in the value range field; {L=100}
18010

Changed value in the value range field:

Differs from lines subID=0 by a different value in the value range field.

In the PARTlinkManager in the column PSOL identifier [PSOL Identifier] appears differently {L=80}

18020

Changed value in the value range field:

Differs from lines subID=0 by a different value in the value range field

In the PARTlinkManager in the column PSOL identifier [PSOL Identifier] appears differently {L=60}

18030

Changed value in ERP column:

Different from row subID=0 due to a different value in the ERP column.

In the PARTlinkManager in the MAT_NAME column, 10.9 appears differently.

18040

Changed value in the ERP column:

Different from row subID=0 due to a different value in the ERP column.

In the PARTlinkManager in the MAT_NAME column, 12.9 appears differently.

18051

Changed value of a NON value range field:

Different from row subID=0 due to a change in a NON-value range field.

The Variant column is given the value '1'.

In the PARTlinkManager in the PSOL identifier [PSOL Identifier] column, {B=11} appears differently.



[10] Whether a separate number should be used for different lengths is defined administratively under PARTadmin -> Category -> Configuration files -> $CADENAS_SETUP -> plinkcommon.cfg -> Block PARTdataManager -> key LockDimRange=0/1. In the example, LockDimRange=1 is set.

Detailed information on this can be found under Section 4.16.2, “ Pin dimension feature on/off / plinkcommon.cfg -> Block [PARTdataManager] -> Key "LockDimRange" ” in PARTsolutions Administration - Manual .

[11] An example for importing variants with PARTdataCenter can be found under Section 1.1.5, “ Dimension search - Automatic assignment based on standard information such as standard number, dimension, material, etc. ” in PARTwarehouse Manual

Prev Up Next
6.1.3.1. Link table and ERP table Home 6.2. Configure PARTsolutions