Customers using Engineering Change Orders (ECO) need the ability to add a different variant/configuration of the same released product as a BOM component during ECO BOM creation/maintenance. Today, this is blocked because the system treats it as adding the product to itself, even when the intent is to reference a different variant/configuration for valid engineering scenarios.

Business impact

This limitation creates real operational impact for customers who manage product changes through ECO:

• Blocks legitimate engineering change scenarios where variant-specific BOM structures are required during controlled change processes.
• Forces teams into manual workarounds and process deviations, reducing standardization and increasing risk of errors and rework during product change cycles.
• Slows down ECO processing and time-to-release, because BOM updates that should be modeled within ECO cannot be completed as designed within the system.

Requested enhancement

Introduce an option/behavior to allow BOM lines in ECO that reference the same released product when the selected component is a different variant/configuration, while still protecting against true circular references.