Results for “number_of_elements”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OE_DEF_CONDITIONS is a table in the ONT (Order Management) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Per the ETRM metadata, its purpose is to store defaulting conditions for an entity — that is, it holds the criteria that the Order Management defaulting framework evaluates in order to determine whether a given defaulting rule, value, or attribute applies to a specific business entity or database object.

The table is owned by the ONT schema and is registered with a documented column count of 26. Its primary key, OE_DEF_CONDITIONS_PK, is a composite key defined over DATABASE_OBJECT_NAME and CONDITION_ID. A unique index, OE_DEF_CONDITIONS_U1, extends that business key with ZD_EDITION_NAME, reflecting the editioning support introduced for the 12.2.x online patching model. From a Data Vault perspective, this object is classified heuristically as standalone — that is, it is not a link between two hubs, and the modeling suggestion is to treat it as an independent hub-like reference entity for defaulting conditions rather than as a dependent satellite. This reflects the fact that no foreign-key relationships are documented for the table; its parentage is by convention through DATABASE_OBJECT_NAME rather than by a hard FK constraint.

Key Information Stored

The most significant columns documented in the ETRM 12.2.2 physical schema are:

• CONDITION_ID — Surrogate identifier for the defaulting condition; one of the two components of the composite primary key OE_DEF_CONDITIONS_PK.
• DATABASE_OBJECT_NAME — The entity or database object to which the condition applies; the second PK component and the primary business-key driver.
• NUMBER_OF_ELEMENTS — The number of condition elements defined for the condition, indicating how many attributes participate in the evaluation.
• SYSTEM_FLAG — Indicates whether the condition is a seeded/system-defined condition rather than user-defined.
• ZD_EDITION_NAME — Editioning column supporting the 12.2.x editions-based architecture; also part of unique index OE_DEF_CONDITIONS_U1.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, providing extensibility for customer-specific condition attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO audit columns capturing creation and last-modification provenance.

The distinction between the surrogate key and business key is important: CONDITION_ID alone is not the business key. DATABASE_OBJECT_NAME combined with CONDITION_ID identifies the condition, and OE_DEF_CONDITIONS_U1 further qualifies it by edition for the 12.2.x patching model.

Common Use Cases and Queries

Typical usage centers on interrogating which defaulting conditions are defined for a given entity, and on joining condition metadata to defaulting rules. A representative query lists conditions for a specific database object:

• SELECT condition_id, database_object_name, number_of_elements, system_flag FROM ont.oe_def_conditions WHERE database_object_name = :entity_name ORDER BY condition_id;

Reporting use cases include auditing seeded versus user-defined conditions (SYSTEM_FLAG), identifying entities with complex defaulting logic (via NUMBER_OF_ELEMENTS), and performing impact analysis before modifying Order Management defaulting setup. DBA-facing queries typically inspect the unique index and editioning behaviour:

• SELECT index_name, uniqueness, column_name FROM all_ind_columns WHERE table_name = 'OE_DEF_CONDITIONS' ORDER BY index_name, column_position;
• SELECT * FROM ont.oe_def_conditions WHERE zd_edition_name = 'SET1';

Related Objects

The metadata documents OE_DEF_CONDITIONS as standalone, with no foreign-key relationships. In practice it participates in the Order Management defaulting framework alongside:

• OE_DEF_ATTR_CONDNS — attributes associated with a condition; joined on CONDITION_ID.
• OE_DEF_ATTR_RULES and OE_DEF_ATTR_VALUES — rules and values applied when conditions are satisfied.
• OE_DEF_ATTR_CATEGORIES — category grouping of defaulting attributes.
• OE_DEFAULT_ATTRIBUTES — the defaulting attribute definitions evaluated against conditions.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — transactional entities whose defaults are resolved through this framework.
• OE_DEF_VALUES_ALL / Order Management defaulting concurrent programs and the public defaulting APIs used by Order Management and Oracle Pricing.

These relationships are semantic rather than enforced by constraint; developers should validate joins against the actual ONT schema in the target environment.