Search Results default_value_date

Overview

OE_DEF_AK_ATTR_EXT_V is an APPS-owned, VALID database view within the Oracle Order Management (ONT) product family. It exposes the extended defaulting metadata that Oracle EBS attaches to order-management attributes defined in the Application Object Library attribute framework. The view is the reporting and integration surface for the configuration that drives attribute defaulting during order entry: whether defaulting is switched on, in what sequence defaulting rules execute, which source and condition flags apply, and which PL/SQL APIs perform the dependent, security, defaulting and validation work.

Because the underlying data is metadata rather than transactional order data, the view is consulted when implementers, support personnel and integration developers need to understand or audit how a given attribute on a given object will behave. The user-searched column DEFAULTING_ENABLED_FLAG is defined directly on this view and is the primary switch that indicates whether defaulting logic is active for the attribute. Combined with the rendering, LOV, validation and default-value columns inherited from the attribute definition, the view provides a single-row-per-attribute picture of both presentation and defaulting behaviour.

Underlying Base Objects

The ETRM metadata documents two referenced base objects: AK_OBJECT_ATTRIBUTES_VL (a view) and OE_AK_OBJ_ATTR_EXT (a synonym). The view text confirms a two-way join between the alias A (AK_OBJECT_ATTRIBUTES_VL) and the alias O (OE_AK_OBJ_ATTR_EXT):

• A.DATABASE_OBJECT_NAME = O.DATABASE_OBJECT_NAME
• A.ATTRIBUTE_CODE = O.ATTRIBUTE_CODE
• A.ATTRIBUTE_APPLICATION_ID = O.ATTRIBUTE_APPLICATION_ID

AK_OBJECT_ATTRIBUTES_VL supplies the generic, translatable attribute definition — columns, data types, labels, LOV definitions, validation APIs and static default values — keyed by the object name, attribute code and attribute application. OE_AK_OBJ_ATTR_EXT supplies the Oracle Order Management–specific extension: the defaulting enablement flag, defaulting sequence, condition and source flags, and the dependent and security API package/procedure pairs. Joining the two produces a consolidated attribute record where the ONT defaulting configuration is layered onto the shared attribute repository.

Key Columns

• DEFAULTING_ENABLED_FLAG — indicates whether defaulting is enabled for the attribute; the principal filter for defaulting audits.
• DEFAULTING_SEQUENCE — execution order of defaulting rules, controlling precedence when multiple sources could supply a value.
• DEFAULTING_CONDN_REF_FLAG and DEFAULTING_SOURCE_FLAG — control whether condition references and sources participate in defaulting evaluation.
• DEPENDENT_API_PKG / DEPENDENT_API_PROC and SECURITY_API_PKG / SECURITY_API_PROC — ONT extension hooks invoked for dependent-processing and security logic.
• ATTRIBUTE_CODE, DATABASE_OBJECT_NAME, ATTRIBUTE_APPLICATION_ID — the composite key linking the two base objects.
• COLUMN_NAME, TABLE_NAME, BASE_TABLE_COLUMN_NAME, DATA_TYPE, DATA_STORAGE_TYPE — physical storage mapping of the attribute.
• REQUIRED_FLAG, DISPLAY_VALUE_LENGTH, BOLD, ITALIC, VERTICAL_ALIGNMENT, HORIZONTAL_ALIGNMENT — presentation metadata.
• LOV columns (LOV_REGION_CODE, LOV_REGION_APPLICATION_ID, LOV_FOREIGN_KEY_NAME, LOV_ATTRIBUTE_CODE, LOV_ATTRIBUTE_APPLICATION_ID) — list-of-values wiring.
• DEFAULTING_API_PKG / DEFAULTING_API_PROC, VALIDATION_API_PKG / VALIDATION_API_PROC — dynamic defaulting and validation program units.
• DEFAULT_VALUE_VARCHAR2, DEFAULT_VALUE_NUMBER, DEFAULT_VALUE_DATE — static default values by datatype.
• ATTRIBUTE_LABEL_LONG, APPLICATION_NAME, OBJECT_NAME, ATTRIBUTE_CATEGORY — descriptive context for reporting.

Common Use Cases and Queries

The view is typically queried to audit defaulting configuration, troubleshoot why an attribute is not defaulting, or document the ONT extension in an upgrade or migration assessment.

List all attributes with defaulting enabled for a given object:

• SELECT attribute_code, database_object_name, defaulting_sequence, defaulting_api_pkg, defaulting_api_proc FROM oe_def_ak_attr_ext_v WHERE defaulting_enabled_flag = 'Y' AND database_object_name = :p_object ORDER BY defaulting_sequence;

Locate the configuration behind a specific attribute:

• SELECT attribute_code, database_object_name, defaulting_enabled_flag, defaulting_source_flag, defaulting_condn_ref_flag FROM oe_def_ak_attr_ext_v WHERE attribute_code = :p_attr AND attribute_application_id = :p_app;

Identify attributes that carry programmatic defaulting or validation logic:

• SELECT attribute_code, defaulting_api_pkg, defaulting_api_proc, validation_api_pkg, validation_api_proc FROM oe_def_ak_attr_ext_v WHERE defaulting_api_pkg IS NOT NULL OR validation_api_pkg IS NOT NULL;

Because the object is a view over the shared attribute repository, queries return current configuration at read time and require no materialization or refresh. Access is granted through the APPS schema in both 12.1.1 and 12.2.2.