About process configuration

A manufacturing process plan consists of three interconnected structures:

• Product

• Processes and operations

• Work area

Configuration management helps you define and apply variant rules to each of these structures independent of the other structures.

Because the process structure can have its own lifecycle and variability, lines in a process can configure out in one of the following ways:

• By occurrence effectivity If you add an operation with occurrence effectivity, it is configured out when it is not effective. Show these lines using View→Show Unconfigured Data→Show Unconfigured by Occurrence Effectivity. The default state of this button is determined by the MEShowUnconfiguredOccurrencesEffectivityDefaultState preference.

• By incremental change effectivity If you make changes with an incremental change (IC) and if it carries effectivity, the changes related to it are configured out if it is not effective. Show these changes by choosing View→Show Unconfigured Data→Show Unconfigured Changes. The default state of this button is determined by the MEShowUnconfiguredChangesDefaultState preference.

• By variants/options If a BOM line carries a variant condition making it valid for a certain set of options, it is configured out for a different option set for which it is not valid. Show these lines by choosing View→Show Unconfigured Data→Show Unconfigured Variants. Using this menu command also shows objects that were configured out using effectivity. The default state of this button is determined by the MEShowUnconfiguredVariantsDefaultState preference.

• By reference window If you have a composition-type process, a line (for example, a consumed item) may be configured out because it is configured out in the reference or parent window on which it is based. Teamcenter does not differentiate why it was configured out in the other window. Show these lines by choosing View→Show Unconfigured Data→Show Unconfigured Assigned Occurrences. In this case, the lines are gone from this process window because they are configured out of the parent structure. It is irrelevant whether they are configured out of the parent structure because of occurrence effectivity, incremental change effectivity, or variants/options. The default state of this button is determined by the MEShowUnconfiguredAssignedOccurrencesDefaultState preference.

The following preferences play a role in what processes you see when child processes are configured out:

• controllingOccsForProcessConfiguration

• typeAndRuleForProcessConfiguration