Search Results oe_def_attr_def_rules_u1




Overview

ONT.OE_DEF_ATTR_DEF_RULES is a seed data table within the Oracle Order Management (ONT) schema that stores attribute-level defaulting rules. Each row defines how a specific attribute — identified by ATTRIBUTE_CODE and scoped to a DATABASE_OBJECT_NAME — receives its value when a matching defaulting condition is satisfied. The table is therefore the operational backbone of the Order Management attribute defaulting engine, which resolves default values for order headers, lines, and related entities during order capture and import.

Rows are grouped under a parent defaulting condition through ATTR_DEF_CONDITION_ID, which references ONT.OE_DEF_ATTR_CONDNS. A condition may produce several candidate rules; the engine evaluates them in ascending SEQUENCE_NO order and applies the first one that yields a value. Because the table is populated partly by Oracle seed data and partly by customer configuration, it resides in the APPS_TS_SEED tablespace, consistent with its mixed seeded and user-defined content.

Under a heuristic Data Vault classification, this table leans toward a satellite: it carries descriptive, condition-dependent rule attributes attached to a parent condition key rather than acting as a pure hub or link. This is a modeling suggestion only, not a formal classification in the EBS data model.

Key Information Stored

The surrogate primary key is ATTR_DEF_RULE_ID, defined by the constraint OE_DEF_ATTR_DEF_RULES_PK. In the 12.2.2 documented schema, the unique index OE_DEF_ATTR_DEF_RULES_U1 covers ATTR_DEF_RULE_ID together with ZD_EDITION_NAME, reflecting the multitenant editioning model. In 12.1.1 the unique index OE_DEF_ATTR_DEF_RULES_U1 is simply the surrogate uniqueness enforcement on ATTR_DEF_RULE_ID.

Common Use Cases and Queries

Typical inquiries center on determining which rule fires first for a given attribute, and on auditing the source definitions for API versus constant defaulting.

SELECT r.attr_def_rule_id, r.sequence_no, r.src_type,
       r.src_api_pkg, r.src_api_fn, r.src_constant_value
FROM   ont.oe_def_attr_def_rules r
WHERE  r.attr_def_condition_id = :condition_id
ORDER  BY r.sequence_no;

Because a nonunique index (N3) exists on ATTR_DEF_CONDITION_ID, this lookup is well supported. A second common pattern joins to the condition table to resolve the object and attribute scope:

SELECT c.attr_def_condition_id, r.attribute_code,
       r.database_object_name, r.sequence_no, r.src_type
FROM   ont.oe_def_attr_condns c,
       ont.oe_def_attr_def_rules r
WHERE  c.attr_def_condition_id = r.attr_def_condition_id
AND    r.database_object_name = :object_name
ORDER  BY r.sequence_no;

Reporting use cases include identifying all API-sourced rules (SRC_TYPE = 'API'), listing seeded versus custom rules via SYSTEM_FLAG, and reviewing the ATTRIBUTE1–ATTRIBUTE15 DFF columns for site-specific metadata.

Related Objects