ATO/PTO BOM Models and their Option Classes are used to automatically create model hierarchy. Models, Option Classes, and Standard Items are automatically populated into the Model. Implicit rules from an ATO/PTO model enforce the following:
Mutually Exclusive: Rules apply to parent nodes from which you can choose only one of all optional child nodes
Minimum/Maximum: At least x and at most y Options can be selected to create a valid configuration.
Default Quantity (Quantity Cascade): Calculations determine the final quantity requirements for the selected child node
Required: Rules apply to child nodes that are required with the parent node (whenever the parent is selected, the required child BOM Items are also selected)
Please note that the imported BOM Model is read-only. However, you can construct additional entities to extend the Model (for example, add customer requirements, Totals, Resources, and so on).
A Rule Sequence is a set of configuration rules ordered by their effective dates. It is useful when a model has rules that change over time.
Developing Configuration Rules
To start developing rule, click on edit of the Imported BOM in Repository Screen. This will take you to Workbench for given Model Click on Rules Link.
Logic Rules enable you to express constraints among elements of your Model in terms of logical relationships. For example, selecting one Option A may require that Options B and C be included in the configuration.
Logic rules define item to item relationships. Logic Rules can push both ways. For example, Side A can impact the logic state of Side B, and Side B can impact the logic state of Side A Either side of the rule can contain one or more Features, Options, and so on. Configuration validity at run time is ensured by Oracle Configurator.