Search Results oe_def_attr_def_rules




Overview
Explore in AI Chat

Overview

OE_DEF_ATTR_DEF_RULES is a configuration table in the Oracle Order Management (ONT) module of Oracle E-Business Suite, residing in the ONT schema. It stores the defaulting rules that govern how attribute values are assigned when an order or order line satisfies a specific defaulting condition. The table functions as the rule layer within the broader Order Management defaulting framework: conditions defined in OE_DEF_ATTR_CONDNS determine when a default applies, while OE_DEF_ATTR_DEF_RULES determines the source and method by which the defaulted value is derived. The object is documented as VALID in both EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. In practical terms, this means the table is best understood as a descriptive, attribute-bearing structure that attaches context to a governing parent entity — here, the defaulting condition — rather than as an independent hub of business keys or a pure link resolving many-to-many relationships. Analysts designing a warehouse layer should therefore treat OE_DEF_ATTR_DEF_RULES as dependent descriptive data keyed to its condition parent.

Key Information Stored

The table contains 40 documented columns. The most operationally significant are:

A unique index, OE_DEF_ATTR_DEF_RULES_U1, spans ATTR_DEF_RULE_ID and ZD_EDITION_NAME, reflecting the edition-aware uniqueness model introduced in 12.2.

Common Use Cases and Queries

The primary use case is diagnosing why a particular order attribute defaulted to an unexpected value. A typical query joins the rule table to its condition parent:

  • SELECT r.attr_def_rule_id, r.attribute_code, r.sequence_no, r.src_type, r.src_constant_value FROM oe_def_attr_def_rules r, oe_def_attr_condns c WHERE r.attr_def_condition_id = c.attr_def_condition_id AND r.database_object_name = :obj AND r.attribute_code = :attr ORDER BY r.sequence_no;
  • Effectiveness reporting: counting rules by SRC_TYPE to understand reliance on profile options versus constants versus APIs.
  • Audit queries filtering on SYSTEM_FLAG or PERMANENT_FLAG to separate seeded Oracle rules from customer-defined entries.
  • Migration and setup comparison between environments using attribute_code and sequence_no as natural lookup keys.

On 12.1.1 installations, ZD_EDITION_NAME is not present, so queries must be adjusted accordingly; on 12.2.2 it should generally be constrained to the current edition.

Related Objects

The FK metadata documents the following principal relationship:

  • OE_DEF_ATTR_CONDNS — parent table; join on ATTR_DEF_CONDITION_ID. This is the direct, documented foreign-key relationship.

Additional functionally dependent objects in the Order Management defaulting framework include the defaulting condition and attribute definition setup tables, plus the runtime defaulting APIs that consume these rule rows during order entry. Reporting views over ONT defaulting configuration and the concurrent programs that evaluate defaults for order import also depend on this table's contents. Because documented relationship data is limited to the single FK above, broader dependencies should be confirmed against the specific ONT setup tables and defaulting API packages present in the target instance.