1.7.1.3. Background information
1.7.1.3.2. Internal treatment of variants
Prev  Next
1.7.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.[14], [15]

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 Line ID and differentiate themselves in the Line sub ID.

Different types of variants in the PARTlinkManager

Different types of variants in the PARTlinkManager

The table describes the differences in detail:

ERP_PDM_NUMBER Line sub ID Variant type (description)
3.342.1160 The first entry; no changes in value range field; {L=100}
3.342.116b 1

Changed value in the value range column:

Different from row subID=0 due to a different value in the value range field..

In the PARTlinkManager in column PSOL Identifier, {L=80} shows up variably.

3.342.116c 2

Changed value in the value range field:

Different from row subID=0 due to a different value in the value range field..

In the PARTlinkManager in column PSOL Identifier, {L=60} shows up variably.

3.342.116_109 3

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 shows up variably.

3.342.116_129 4

Changed value in the ERP column:

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

In the PARTlinkManager in column MAT_NAME, 12.9 shows up variably.

3.342.116_b11 5

Changed value of a NON-value range field:

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

Column Variant contains the value '1'.

In the PARTlinkManager in column PSOL Identifier, {B=11} shows up variably.



[14] Whether different lengths receive their own number is set administratively under PARTadmin -> Category -> Configuration files -> $CADENAS_SETUP -> plinkcommon.cfg -> Block PARTdataManager -> the key LockDimRange=0/1 needs to be set. In the example LockDimRange=1 is set.

More information can be found under Section 4.17.3, “ Pinning Dimension attribute OnOff / plinkcommon.cfg -> Block [PARTdataManager] -> Key "LockDimRange" ” in PARTsolutions - Administration Manual.

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

Prev Up Next
1.7.1.3.1. Link table and ERP table Home 1.7.2. Keep data up-to-date