Search Results oe_def_attr_condns_u1

Overview

ONT.OE_DEF_ATTR_CONDNS is a seed data table within the Oracle Order Management (Order-to-Cash) schema, ONT. It serves as a configuration repository that associates defaulting conditions defined at the entity level with specific descriptive flexfield attributes. In Oracle EBS Release 12.1.1 and 12.2.2, this table underpins the attribute defaulting framework, allowing administrators to determine which defaulting rule applies to which attribute on a given database object, and in what order multiple applicable conditions are evaluated. The table resides in the APPS_TS_SEED tablespace, reflecting its role as a setup and reference table rather than a high-volume transactional store.

From a Data Vault modeling perspective, the heuristic classification for this object is hub-leaning. This suggests the table functions primarily as a durable key registry, with ATTR_DEF_CONDITION_ID acting as the stable business key that anchors relationships to dependent rule and transaction records. Modelers may treat it as a hub with attached descriptive context.

Key Information Stored

The table is keyed by the surrogate primary key column ATTR_DEF_CONDITION_ID, defined through the OE_DEF_ATTR_CONDNS_PK constraint. The unique index OE_DEF_ATTR_CONDNS_U1 (ATTR_DEF_CONDITION_ID, ZD_EDITION_NAME) represents the business-key candidate and supports editioning-aware access patterns.

• ATTR_DEF_CONDITION_ID — Surrogate primary key uniquely identifying each attribute-condition association.
• CONDITION_ID — Foreign key to OE_DEF_CONDITIONS, identifying the entity-level defaulting condition bound to the attribute.
• ATTRIBUTE_CODE — The descriptive flexfield segment or attribute to which the condition applies.
• DATABASE_OBJECT_NAME — Base view/object that owns the attribute, scoping the condition to a specific business entity.
• PRECEDENCE — Evaluation order; lower values are evaluated first when multiple conditions apply.
• ATTRIBUTE_CATEGORY — Descriptive flexfield context used to qualify the attribute.
• ENABLED_FLAG and SYSTEM_FLAG — Status controls indicating whether the association is active and whether it is seeded by Oracle.
• ZD_EDITION_NAME — Editioning column supporting EBS 12.2 online patching.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include auditing defaulting configurations, diagnosing why an attribute received an unexpected default value, and migrating setups between environments. A common query resolves the conditions applied to a given attribute:

• SELECT attribute_code, database_object_name, condition_id, precedence FROM oe_def_attr_condns WHERE attribute_code = :code ORDER BY precedence;
• SELECT * FROM oe_def_attr_condns WHERE condition_id = :cond_id;
• SELECT * FROM oe_def_attr_condns WHERE enabled_flag = 'Y' AND system_flag = 'N';

Reporting often joins this table to OE_DEF_CONDITIONS to display condition names alongside attribute associations, supporting functional documentation and setup validation.

Related Objects

• OE_DEF_ATTR_DEF_RULES — References this table via ATTR_DEF_CONDITION_ID, linking conditions to defaulting rules.
• OE_DEF_CONDITIONS — Parent of CONDITION_ID, holding entity-level defaulting condition definitions.
• OE_DEF_ATTR_CONDNS_U1 — Unique index enforcing the business key.
• OE_DEF_ATTR_CONDNS_N1 / OE_DEF_ATTR_CONDS_N2 — Non-unique indexes on ATTRIBUTE_CODE and CONDITION_ID supporting lookup queries.

Together these objects form the metadata layer that drives attribute defaulting behavior across order entities in Oracle Order Management.