Change the default working of filtering on alternate numbers

[kcoppens]

When you have a BOM with different alternate BOM's (alternate number) then the system use the following filter sequence:

"From the list of iterations filtered previously (View + BOM Type), the system should try to match exactly the Alternate BOM entered in Configurable Structure. If none, then the system should use the lowest in the hierarchy defined in a configuration file; as the OOTB Alternate values are alphanumeric, the lowest one should be the first ordered value. If no iteration matches, then the system should try to get the one with "Null" as Alternate. If the user hasnt entered any value, then the system must match the "Null" value."

The result is: when you filter on a specific alternate number and for a WTPart/BOM, this alternate number does not exist, Windchill choose another alternate number.

Result:

See my example (ATS = alternate number 001) and BEU (alternate number 002). If you put a filter on the structure, you do not want to see another alternate bom but the default manufacturing view if the alternate number does not exist.

[GregoryPERASSO]

Hi

We just open this kind of case to PTC Technical Support

It seems that the filtering works regarding the ordered value of the Variation2RB file

But seems to have the same issue than you.  even if our value is orederd behind the one in the filter, it seems not select the "null" manufacturing View.

Still under investigation

Can you add a screen shot of your alternative list ? ATS is before BEU ?

regards

[kcoppens]

I have already a case opened and it works like defined (12030096).

Nevertheless, it seems not logical to show other alternate BOM's when you are filtering on a specific alternate BOM.

Alternate BOM's is used when companies are working with different plants. You can not build in a logic of sequences between plants (in practice).

[ptc-4342567]

Hi Gregory,

What is your case number?

Thanks

Hassen

[GregoryPERASSO]

Hi

our case number  12137247