Search Results oe_def_condn_elems_u1

Overview

The ONT.OE_DEF_CONDN_ELEMS table is a seed data table in the Oracle Order Management (ONT) schema that stores the individual elements composing a defaulting condition. Each row represents one attribute/column test — an attribute code, an operator, and a target value — that together form a rule used by the Order Management defaulting engine to determine when a default value should be applied to an order entity such as an order header, line, or pricing attribute. Conditions are identified by CONDITION_ID and resolved through the related condition header table.

The table resides in the APPS_TS_SEED tablespace, which is reserved for seeded reference and setup data, and it participates in Oracle EBS Multi-Org and TCA-independent ordering flows. The SYSTEM_FLAG column distinguishes Oracle-seeded condition elements from customer-defined ones, allowing Oracle to ship defaulting rules that can be recognized and protected from user modification. From a Data Vault modeling perspective, the metadata classifies this object heuristically as a standalone entity; it functions as a hub-like master of condition element identities with satellite-style descriptive attributes attached directly, rather than as a link between other business keys.

Key Information Stored

The primary key is CONDITION_ELEMENT_ID, a system-generated number that uniquely identifies each condition element. The unique index OE_DEF_CONDN_ELEMS_U1 enforces uniqueness on CONDITION_ELEMENT_ID (and, in the 12.2.2 physical schema, ZD_EDITION_NAME), which is the business-key candidate for this table.

• CONDITION_ID — foreign key pointing to the parent defaulting condition; groups together elements that share the same rule.
• GROUP_NUMBER — logical grouping number; elements with the same group number are ANDed together, allowing composite conditions with multiple AND/OR blocks.
• ATTRIBUTE_CODE — the Descriptive Flexfield segment (order entity attribute) being tested.
• ATTRIBUTE_CATEGORY — the DFF context or structure that qualifies the attribute.
• VALUE_OP — the comparison operator applied to the attribute value, e.g., = or <>.
• VALUE_STRING — the literal or reference value the attribute must match for the element to evaluate TRUE.
• SYSTEM_FLAG — indicates whether the element is Oracle-seeded (Y) or user-defined.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide audit tracking.
• ATTRIBUTE1–ATTRIBUTE15 — the DFF value columns available for additional element attributes.

Common Use Cases and Queries

This table is primarily queried to diagnose or report on the defaulting rules configured and shipped for Order Management. A typical query joins the conditions to their elements to reconstruct the full rule:

• Find all elements of a condition: SELECT * FROM ONT.OE_DEF_CONDN_ELEMS WHERE condition_id = :p_id ORDER BY group_number;
• Identify Oracle-seeded elements: SELECT * FROM ONT.OE_DEF_CONDN_ELEMS WHERE system_flag = 'Y';
• Search by index N1 (CONDITION_ID, ATTRIBUTE_CODE) to retrieve attributes tested for a given condition.
• Search by index N2 (ATTRIBUTE_CODE, VALUE_STRING) to find which conditions reference a particular attribute value.

Reporting scenarios include auditing defaulting rules before upgrades, troubleshooting why a default value did not apply, and documenting rule configurations for compliance or SOX purposes.

Related Objects

The following objects are most significant in relation to this table:

• ONT.OE_DEF_CONDN_HDRS (or equivalent condition header) — parent table joined on CONDITION_ID to retrieve condition descriptions and rule context.
• ONT.OE_DEFAULTING_RULES — top-level defaulting rule definitions that ultimately reference conditions and their elements.
• ONT.OE_DEF_CONDN_ELEMS_U1 / _N1 / _N2 — indexes supporting the lookups described above.
• FND_DESCR_FLEX_COL_USAGE_VL and related DFF metadata views — join on ATTRIBUTE_CODE and ATTRIBUTE_CATEGORY to resolve descriptive flexfield segment definitions.
• ONT.OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — the transactional entities whose defaulting behavior is driven by these condition elements.

Because this is a seed table with no foreign keys extending outward, its dependency surface is concentrated on the defaulting rule configuration tables that consume its rows at runtime.