Setup Step: 25 - Defaulting Rules

Defaulting Rules are used to populate values in fields(like order type, price list etc) on forms (SO form) automatically.
Values can be populated from various sourcs like customer's record, item's record, price list, profile option or PL/SQL Code.


An Entity in this context is a group of related attributes that roughly correspond to a table or a form in Order Management. There are entities of Order Header, Order Line, Order Price Adjustment, Line Price Adjustment, and so on.

An Attribute is a field or column that belongs to that entity. Therefore, the ordered unit of measure is an attribute of the Order Line entity. When you query up the Defaulting Setup window for a particular entity, a list of all the attributes for which you can define defaulting rules display. You will not be able to define defaulting rules for descriptive flexfields, since their defaulting is controlled by AOL’s flexfield routines.


Conditions are rules set up that to control when a particular group of default sources will be looked at. Define one or more condition validation templates per entity based on common business rules to meet your business needs. Then you can use them over and over for the attributes of that entity. For example, you might set up a condition template for all return lines, or another one for all internal order lines. The ALWAYS condition is seeded for each entity. When defining a set of Conditions and using them in rules, be sure to place the ALWAYS condition last in the Precedence for Defaulting Conditions.

(In condition template we define condition of the order for which we 'll define the defaulting rule. ALWAYS condtion is the default one but we can define one condtion for return, one condition for internal orders and so on. once we have defined the conditions we set the defaulting rule of each attribute for different conditions. So the defaulting value is a combination of entity, condition template & attribute)

Notes: The Group Number is an arbitrary number used to control AND and OR conditions. Indicate that rules are to be connected by an AND rule by giving them the same group number. Rules to be connected with OR should be given
different group numbers


On the main Defaulting Setup screen, where all the attributes of the entity are listed, there is a column called Defaulting Sequence. This number determines the order in which attribute defaulting takes place. When attributes have equal sequence numbers, defaulting takes place alphabetically. All the attributes are seeded with a sequence of 50. You can change these sequences, if you need defaulting to happen in some different order. For example, you might define a sourcing rule that says default attribute A on the line from attribute B on the same line. In this case, you need to insure that the Attribute B gets its value before A is defaulted, or the rule will not work as expected.