Generic BOM Change and Revision in Variant

[VB_9139347]

We defined the following in our instance:
i. Created Generic BOM, Variant Specification and Variants
ii. Both the Generic BOM and Variants are in Released state (Production)

We need system behaviour as follows:
Once the Generic BOM is revised and made changes, and if we reconfigure the “Variant Specification”, then the Variant should get revised. Instead now the variant is getting iterated which is unacceptable for the Released Variant.

Attached the files for your reference.

[AB_9493957]

It is worse than that. If you make any change to the configurable product and then revision the variant for reconfigure (a "non match" because there was some change on structure or attributes), the system will offer an update only the last iteration of the previous revision. So for example if that was A.3 and now you revise the variant to update via reconfigure, the system creates a new iteration on A (A.4, A.5.... for ever).... and you cannot update B.0 !!!

Also, when you revision a released variant specificatioin, the delivered variant reference (if there was any) gets wiped out, that is you lose that associativity.

In fact I would suggest PTC to include a full description of their concept of variant change management in the HELP pages (variant revisioning, variant spec revisioning, Configurable Product revisioning, becuase the whole "as specified" looks very different than the way we expected... and it is not simple to find alternatives or workarounds.

[JE_8968323]

We actually have the product Manager execute the reconfigure and iterate the Variants in the Released state. The downstream users (production) have subscribed to see any changes. That works for us in the current situation (without MPM-Link deployed or M-BOM in Windchill)