Search Results oe_def_ak_obj_ext_v




Overview
Explore in AI Chat

Overview

OE_DEF_AK_OBJ_EXT_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the Order Management (ONT) product family. It is documented as a VALID database object in both EBS 12.1.1 and 12.2.2 and forms part of the Oracle Application Framework extensibility infrastructure that supports attribute defaulting for order management entities. The view presents a consolidated, query-ready projection of the metadata that describes which database objects and entities within Order Management have attribute defaulting enabled, together with the API packages and procedures EBS uses to invoke defaulting and validation logic at runtime.

Functionally, the view joins the generic Oracle Application Object Library (AK) object definition layer with an Order Management-specific extension table, filtering the result set to only those objects flagged as having defaulting enabled. This makes the view a convenient reporting and integration surface for technical consultants who need to understand or audit the configuration of descriptive flexfield and attribute defaulting behavior across order management entities such as headers, lines, and related business objects.

Underlying Base Objects

The view is defined over two documented base objects:

  • AK_OBJECTS_VL (VIEW) — the multi-language object definition view in the Application Object Library. It supplies the shared object metadata, including the object name, application identifiers, and primary key information.
  • OE_AK_OBJECTS_EXT (SYNONYM) — the Order Management extension object, which provides the entity-level detail and the defaulting-enabled indicator as well as the audit columns.

The two objects are joined on DATABASE_OBJECT_NAME, and the result is restricted by the predicate Y.DEFAULTING_ENABLED_FLAG = 'Y', ensuring that only objects with defaulting activated are exposed. The view is defined in the APPS schema and is therefore accessible to any EBS responsibility or integration user granted the appropriate APPS-level privileges.

Key Columns

The projected columns can be grouped into three categories:

The PRIMARY_KEY_NAME column identifies the key structure of the mapped entity, useful when correlating view output with the underlying business table.

Common Use Cases and Queries

Typical scenarios include auditing defaulting configurations, tracing which API performs defaulting for a given entity, and building integration extracts that mirror the attribute-defaulting setup.

  • List all entities with defaulting enabled and their associated APIs.
  • Locate the defaulting or validation package for a specific entity code.
  • Extract attribute metadata for downstream mapping documentation.

Sample query:

SELECT entity_code, database_object_name, defaulting_api_pkg, defaulting_api_proc, validation_api_pkg, validation_api_proc FROM oe_def_ak_obj_ext_v ORDER BY entity_code;

For a targeted search: SELECT * FROM oe_def_ak_obj_ext_v WHERE entity_code = 'ORDER';