Results for “database_object_display_name”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_DEF_CONDITIONS_VL is a multi-language (ML) validation view owned by the APPS schema in Oracle E-Business Suite, belonging to the Order Management (ONT) product family. It presents the defaulting conditions configured within Oracle Order Management — the rule definitions that determine which defaulting source and value should be applied to order attributes during order entry. The view exposes one row per defaulting condition, translated into the session language, and joins that condition to the descriptive metadata of the database object it operates against.
The view text and column list are essentially identical between EBS 12.1.1 and 12.2.2; the documented metadata in the ETRM for 12.2.2 confirms the same underlying base objects and status (VALID). Because it is an "_VL" view, it returns language-specific display text rather than all translations, making it suitable for direct use in reports, lookups, and integration queries without an additional language predicate on display columns. The view is read-only in practical terms and is intended for reporting and diagnostic purposes rather than as a DML target.
Underlying Base Objects
The view is defined over four documented objects, combined through equality joins on the relevant keys:
- OE_DEF_CONDITIONS (synonym) — the base condition table supplying the primary key CONDITION_ID, the operational columns DATABASE_OBJECT_NAME, NUMBER_OF_ELEMENTS, SYSTEM_FLAG, the WHO audit columns, and the ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns.
- OE_DEF_CONDITIONS_TL (synonym) — the translation table holding DISPLAY_NAME and DESCRIPTION per language; the join is constrained by B.LANGUAGE = USERENV('LANG').
- AK_OBJECTS_VL (view) — the Oracle Application Object Library registration view, supplying the object's NAME as DATABASE_OBJECT_DISPLAY_NAME and its APPLICATION_NAME as APPLICATION_DISPLAY_NAME.
- OE_AK_OBJECTS_EXT (synonym) — the Order Management extension, supplying ENTITY_CODE exposed as ENTITY_NAME.
All three object references (database object, the AK registration, and the ONT extension) are joined on DATABASE_OBJECT_NAME, so the view returns only conditions whose target object is both registered in AK_OBJECTS and extended within Order Management.
Key Columns
- ROW_ID — the physical ROWID of the base OE_DEF_CONDITIONS row, supplied as A.ROWID ROW_ID.
- CONDITION_ID — the unique identifier of the defaulting condition; primary join key across all base objects.
- DATABASE_OBJECT_NAME — the internal name of the object the condition defaults, mapped into the AK and ONT extension joins.
- NUMBER_OF_ELEMENTS — the number of elements (attributes/segments) participating in the defaulting condition; this is the column commonly queried when analyzing defaulting rule complexity.
- SYSTEM_FLAG — indicates whether the condition is Oracle-seeded (system) or user-defined.
- DISPLAY_NAME / DESCRIPTION — the language-specific name and description from OE_DEF_CONDITIONS_TL.
- DATABASE_OBJECT_DISPLAY_NAME / APPLICATION_DISPLAY_NAME — the readable object name and owning application from AK_OBJECTS_VL.
- ENTITY_NAME — the Order Management entity code from OE_AK_OBJECTS_EXT.
- WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — standard audit and descriptive flexfield context columns.
Common Use Cases and Queries
Typical scenarios include auditing defaulting rule setup, investigating why a particular attribute did not default as expected, and validating the registration of defaulting objects across applications.
- List conditions for a given object:
SELECT condition_id, display_name, number_of_elements, system_flag FROM apps.oe_def_conditions_vl WHERE database_object_name = :p_object_name;
- Find conditions by element count:
SELECT condition_id, display_name, database_object_display_name, application_display_name, number_of_elements FROM apps.oe_def_conditions_vl WHERE number_of_elements > 1 ORDER BY number_of_elements DESC; - Separate seeded versus custom conditions:
SELECT system_flag, COUNT(*) FROM apps.oe_def_conditions_vl GROUP BY system_flag;
- Object/application inventory of defaulting conditions:
SELECT application_display_name, database_object_display_name, entity_name, COUNT(*) conditions FROM apps.oe_def_conditions_vl GROUP BY application_display_name, database_object_display_name, entity_name;
Because the view already enforces the session-language filter and the AK/ONT extension joins, these queries require no additional translation or registration predicates, and the ATTRIBUTE1–15 columns remain available should the client have configured a descriptive flexfield on the underlying condition table.
-
View: OE_DEF_CONDITIONS_VL 12.2.2
This view stores the defaulting conditions.
APPS.OE_DEF_CONDITIONS_VL·↳ AK_OBJECTS_VL·↳ OE_AK_OBJECTS_EXT·↳ OE_DEF_CONDITIONS·Explore ONT module →
-
View: OE_DEF_ATTR_CONDNS_V 12.2.2
This view stores the attribute level defaulting conditions.
APPS.OE_DEF_ATTR_CONDNS_V·↳ AK_OBJECT_ATTRIBUTES_VL·↳ OE_DEF_ATTR_CONDNS·↳ OE_DEF_CONDITIONS_VL·Explore ONT module →
-
View: OE_DEF_CONDITIONS_VL 12.1.1
This view stores the defaulting conditions.
APPS.OE_DEF_CONDITIONS_VL·↳ AK_OBJECTS_VL·↳ OE_AK_OBJECTS_EXT·↳ OE_DEF_CONDITIONS·Explore ONT module →
-
View: OE_DEF_ATTR_CONDNS_V 12.1.1
This view stores the attribute level defaulting conditions.
APPS.OE_DEF_ATTR_CONDNS_V·↳ AK_OBJECT_ATTRIBUTES_VL·↳ OE_DEF_ATTR_CONDNS·↳ OE_DEF_CONDITIONS_VL·Explore ONT module →
-
View: OE_DEF_AK_ATTR_EXT_V 12.2.2
APPS.OE_DEF_AK_ATTR_EXT_V·↳ AK_OBJECT_ATTRIBUTES_VL·↳ OE_AK_OBJ_ATTR_EXT·Explore ONT module →
-
View: OE_DEF_AK_ATTR_EXT_V 12.1.1
APPS.OE_DEF_AK_ATTR_EXT_V·↳ AK_OBJECT_ATTRIBUTES_VL·↳ OE_AK_OBJ_ATTR_EXT·Explore ONT module →
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.