Scenario:

We are using EBOM and MBOM with the Enterprise Item Number (EIN) attribute.

In Platform Management Settings, the option “Unique EIN for Product” is enabled, meaning the system does not allow duplicate EIN values across products.

Our business scenario includes cases where the Engineering item (ENG- VPM REFERENCE) and the corresponding Manufacturing item (MFG - Provide) must share the same EIN.

Example:

• Engineering item: Washer
• EIN: 1234

When Manufacturing creates the corresponding scoped item (for example, a Manufacturing Provided Part) through the scope link mechanism, the system automatically inherits the EIN from the Engineering item.

As a result:

• ENG item EIN = 1234
• MFG item EIN = 1234

Issue:

When attempting to save the Manufacturing item, the system blocks the save operation because the EIN is duplicated, due to the “Unique EIN for Product” validation rule.

Expected Behavior:

In this scenario, since the Manufacturing object is created through a valid scope link to the Engineering object, the system should allow the duplicated EIN because both objects represent the same enterprise item in different domains (Engineering vs Manufacturing).

The duplicate EIN validation should apply only when the item is unrelated (i.e., no scope link exists), to prevent unintended duplication across independent products.

Question:

Is the current behavior expected by design, or should the uniqueness validation exclude scoped ENG/MFG object relationships?