Hi everyone,
I have an MBOM–EBOM scenario where I want each EBOM to have only one MBOM. In other words, there should always be a one-to-one scopelink between an EBOM revision and its corresponding MBOM revision.

My expected lifecycle is:

1. EBOM takes a revision first
2. MBOM takes its revision after EBOM
3. The new MBOM should either:
   • connect to the new EBOM revision, or
   • be created without any scopelink if linking is not possible.

However, the current behavior is incorrect. When MBOM takes a revision, both MBOM revisions end up connected to the old EBOM revision, instead of the new one.

Example of the issue:

EBOM --- .1  <--scopelink-->  MBOM --- .1
  |
  | EBOM takes revision
  v
EBOM --- A.1   <-- no scopelink -->

MBOM takes revision
EBOM --- .1  <--scopelink-->  MBOM --- .1
                    \\        
                     <--scopelink--> MBOM --- A.1

EBOM --- A.1  <-- still no scopelink -->

What I want:

• Ideally: MBOM A.1 should automatically connect to EBOM A.1
• If this is not possible: MBOM A.1 should be created without a scopelink (instead of linking to the old EBOM revision)

Is there any configuration, customization, or recommended approach to enforce this behavior?

Thanks for your helpMBOMEBOM