Basic rules that are inherent in a BOM Model are imported and automatically applied in Oracle Configurator Developer. These rules include settings that indicate whether components in the BOM are optional or mutually exclusive, as well as any Quantity Cascade calculations. For example:

Required rules apply to child nodes that become required in the configuration when their parent node is selected. The name of this setting in Configurator Developer is "Required when Parent is Selected." For example, if this setting is Yes
for Option Class X, Oracle Configurator automatically selects it when the end user selects its parent BOM Model.

Mutually Exclusive rules apply to nodes that allow only one of their optional child nodes to be selected at a time. The name of this setting in Configurator Developer is "Optional Children are Mutually Exclusive." For example, if the options within a
BOM Option Class are mutually exclusive, an Oracle Configurator end user can select only one of them. This is similar to an Option Feature with a Maximum Selections of 1.

In Oracle Bills of Material, BOM Models that are children (components) of a BOM can be mutually exclusive. However, when you import such a BOM Model, Configurator Developer sets the Mutually Exclusive setting to No for each child (referenced) BOM Model. This is not an issue for most installations, and you can define rules that require a BOM Model's children to be mutually exclusive, if necessary.

In Configurator Developer, you can view how these rules are defined by viewing a BOM node's definition in the Structure area of the Workbench.

All of an optional BOM Model's required children have an initial logic state of Unknown. Any required child items under the root BOM Model have an initial logic state of true, due to the inherent BOM rules described in the preceding paragraphs.
Note that the root BOM Model cannot be optional, and any BOM item that is required has the "Required when parent is selected" setting set to Yes.