Understanding equivalence and in-context ID (IDIC)

Teamcenter has several features that depend on finding parts that are considered equivalent. This equivalency is often dependent on the in-context ID (IDIC), also known as the absolute occurrence ID. The in-context ID is a unique identifier, generally alphanumeric, that determines if two parts or processes are equivalent.

You can view the in-context ID by displaying the ID in Context Top Level column. It is usually automatically generated, and you should exercise caution in modifying its value.

The following features depend on the in-context ID:

• Reconciling and engineering bill of process (EBOM) with a manufacturing bill of process (MBOM)

• Finding products in processes that are not yet expanded

• Running an accountability check to verify line equivalence

• Assigning parts to a cloned process structure

• Comparing structures to intermediate data captures

An in-context ID is automatically generated in the following situations:

• When you assign a bill of materials (BOM) to a BOM or a bill of process (BOP) to a BOP

• When you assign a BOM to a BOP or enterprise BOP (EBOP) structure if the MECopyIdInContextToAssignedLine preference is set to true

An in-context ID is not generated when you assign from an EBOP structure to an EBOP structure.

Caution

If a line has an in-context ID and you cut it and paste the same line back into the structure, Teamcenter creates a new occurrence without an in-context ID. Therefore, any of the above comparisons based on the in-context ID no longer work.

Related Topics

• Comparing the EBOM and MBOM

• Setting up the search for components in other structures

• Understanding line equivalence

• Consuming parts in a cloned process using smart in-context IDs

• About intermediate data captures