Introduction to Configuration Rules
One of the most fundamental things to do in developing a configuration mannequin is to graph and assemble the regulations that govern what the stop person can pick to make a legitimate configuration. You want to outline regulations that specific members of the family and compatibilities amongst the Components, Features, Options, BOM Option Classes, and BOM Standard Items in your Model. Configuration policies are vital in making sure that a configured product can be ordered and manufactured successfully.
In a configuration model, policies pick out Model factors that are:
•Used as well-known defaults
•Automatically chosen when an cease consumer selects any other option
•Permitted when an cease consumer selects some other option
•Excluded when an cease consumer selects every other option
Types of Configuration Rules
Configuration Rule Types summarizes every kind of rule.
•Logic: Defines a logical relationship between most kinds of Features, Options, and any kind of BOM nodes.
•Numeric: Express constraints between Model objects in phrases of numeric relationships.
•Comparison: Performs an evaluation between the values or Properties of two nodes, or a consistent value.
•Property-based Compatibility: Specifies suits between the picks of one or extra Features or BOM Option Classes that have a frequent Property.
•Explicit Compatibility: Specifies fits between the alternatives of one or extra Features or BOM Option Classes in specific tabular form.
•Design Chart: Specifies compatibility suits amongst the selections of Features or BOM Option Classes in specific tabular form.
•Statement: Allows greater complicated expressions and constraint definitions the usage of the Constraint Definition Language (CDL).
•Rule Sequences: Specifies an ordered set of regulations whose effectivity dates are set so that a rule in the sequence will become wonderful at the equal time its predecessor ceases to be effective.
•Configurator Extensions: Use Java code that you write to operate features that go past the performance and policies that Oracle Configurator Developer provides.
•Creating Rules: You create all kinds of guidelines (except Java code for a Configurator Extension Rule) in the Rules region of the Workbench. The steps to create a rule fluctuate relying on the rule’s type.
•Rule Folders: In the Rules location of the Workbench, every Model carries a default Configuration Rules Folder. Within this Folder, you can create as many sub-Folders as you want to prepare a Model’s rules.
•Rule Folders that you create can comprise any kind of rule. You can reproduce regulations and pass them from one Folder to another. However, the identical rule can’t stay in greater than one Folder. Copying a rule to a one-of-a-kind Folder creates a new, separate rule that can be modified independently of the original.
•Rule Sequences: A Rule Sequence is a set of guidelines that are lively in accordance to their order in the sequence, which is decided by way of every rule’s effectivity dates.
•Enabling and Disabling Rules: Enabling and disabling guidelines can be a beneficial device when unit checking out and debugging a configuration model. Rules that are disabled are omitted when you generate good judgment and when you unit take a look at a Model in a runtime Oracle Configurator or the Model Debugger. You can allow or disable any kind of rule.
The Disabled column in the Rules place of the Workbench indicates whether or not a rule is presently active. When you allow or disable a rule, Configurator Developer updates this column solely after you regenerate logic.
Imported BOM Rules:
Basic policies that are inherent in a BOM Model are imported and routinely utilized in Oracle Configurator Developer. These guidelines consist of settings that point out whether or not aspects in the BOM are optionally available or collectively exclusive, as properly as any Quantity Cascade calculations.
For example: Required guidelines observe infant nodes that end up required in the configuration when their guardian node is selected. The identity of this putting in Configurator Developer is “Required when Parent is Selected.” For example, if this placing is Yes for Option Class X, Oracle Configurator robotically selects it when the cease person selects its mum or dad BOM Model.
•Mutual Exclusive regulations practice to nodes that permit solely one of their non-obligatory infant nodes to be chosen at a time. The identity of this placing in Configurator Developer is “Optional Children are Mutually Exclusive.” For example, if the choices inside a BOM Option Class are together exclusive, an Oracle Configurator stop consumer can pick out solely one of them. This is comparable to an Option Feature with a Maximum Selections of 1.
•In Oracle Bills of Material, BOM Models that are teenagers (components) of a BOM can be together exclusive. However, when you import such a BOM Model, Configurator Developer units the Mutually Exclusive placing to No for every infant (referenced) BOM Model. This is no longer a problem for most installations, and you can outline policies that require a BOM Model’s young people to be jointly exclusive, if necessary.
•Quantity Cascade calculations are defined in Quantity Cascade Calculations.
•In Configurator Developer, you can view how these regulations are described by way of viewing a BOM node’s definition in the Structure region of the Workbench.
•All of an optionally available BOM Model’s required youth have a preliminary good judgment kingdom of Unknown. Any required baby gadgets below the root BOM Model have a preliminary good judgment country of true, due to the inherent BOM guidelines described in the previous paragraphs. Note that the root BOM Model can’t be optional, and any BOM object that is required has the “Required when mother or father is selected” placing set to Yes.
Quantity Cascade Calculations
•Quantity Cascade calculations decide the ultimate extent necessities for a chosen BOM item’s children.
•When you import a BOM Model, all of the parent-to-child relationships that exist amongst the elements in the BOM are maintained. A dad or mum element (such as a BOM Option Class) might also have a couple of children; some required, some optional, and some jointly exclusive. When a father or mother is chosen in a runtime Oracle Configurator, all of its required youth are additionally selected. Similarly, when any baby is selected, its dad or mum is additionally selected.
•Each factor in a BOM is imported with a Minimum Quantity, Maximum Quantity, and Default Quantity. The Minimum Quantity is the smallest variety of the chosen node allowed per parent. The Maximum Quantity is the biggest wide variety of the chosen node allowed per parent. The Default Quantity is how many of the chosen nodes will be ordered (per parent) if this fee is no longer modified in the choice process.
•Whenever the range of a chosen choice is increased than zero, a Quantity Cascade calculation is carried out which outcomes in the authentic volume (or count) for that BOM item. The Quantity Cascade calculation is:
•child node real extent = (parent node authentic quantity) X (child node default quantity)
•This calculation is genuine when the stop person selects the dad or mum object (for example, a BOM Option Class) and one of its youngsters (a BOM Standard Item), however it no longer alternates the quantity of the baby item. Therefore, the memory of the baby is derived from the equation proven above.
•However, if the stop person enters a distinct quantity for the toddler (BOM Standard Item) and then modifications the quantity of the mum or dad (BOM Option Class), the Quantity Cascade calculation is:
•( new baby node quantity / cutting-edge toddler node quantity ) X (old guardian node amount) = new guardian node quantity
•For example, Option Class A (the mother or father node) incorporates Option1 (the baby node). Option1 has an preliminary remember of two The give up consumer units Option1 to four and then adjustments Option Class A to three The Quantity Cascade calculation determines a new quantity for Option1 as follows:
•( four / two ) X three = 6
•Note that the calculation ensures that the new quantity of the infant node (6) is a couple of of its default extent (2).
•These Quantity Cascade relationships mirror the relationships between factors that are constructed into the BOM to make sure that it is whole and legitimate earlier than ordering.
Quantity Cascade Calculation:
A BOM Model for a vehicle specifies 4 wheels and 5 lug nuts for every wheel. If you pick out the car, that skill you should have 4 wheels and 20 lug nuts. Similarly, if you pick one wheel, that forces determination of the car, which forces the Quantity Cascade calculation; therefore, 4 wheels and a complete 20 lug nuts are ordered. The Numeric Rules you outline in Configurator Developer admire these Quantity Cascade relationships.
All portions for BOM Standard Items are calculated this way and are propagated from the root node down via the complete BOM Model.
Conclusion:
Oracle Configurator direction through Gologica teaches you to use Oracle Inventory and Bills of Material to set up objects for configuration, Work in the quite a number areas of the Repository and Workbenches in Oracle Configurator Developer, Define configuration rules, Enhance Model structure, Test and post configuration models, Book a configured income order from a host application.
Author Bio:
She is an expert writer at GoLogica and contributes in-depth articles on various Technologies. She has 2.5+ years of experience in content writing and She is passionate about writing technical content. Contact her Linkedin
