Search Results defaulting_api_pkg

Overview

AK_OBJECTS_VL is a multilingual (VL) view owned by the APPS schema within the AK – Common Modules product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the translation-ready definition of the registered objects managed by the Oracle Application Object Library (AK) framework, joining the base registration table to its translation table and to the applications lookup so that object names and descriptions are returned in the session language. The view is documented in the ETRM with the terse note "10SC ONLY," indicating that its documented implementation scope is restricted to the 10SC configuration rather than being exposed as a general-purpose public interface. Consequently, AK_OBJECTS_VL should be treated as an internal dictionary view rather than a supported customer-facing API surface.

Its principal role is to present a consolidated, readable picture of the object-level metadata that the AK framework uses to drive object behaviour at runtime and to support the Applications Dictionary and related validation/defaulting mechanisms. Because it already resolves the language-specific name and description, it is convenient for reporting and for integration code that needs to inspect which validation or defaulting routines are attached to a given database object.

Underlying Base Objects

The view is defined over three documented referenced objects:

• AK_OBJECTS (SYNONYM) — the primary registration table, supplying the database object name, application identifier, primary key column, defaulting and validation package/procedure names, and the descriptive flexfield attributes.
• AK_OBJECTS_TL (SYNONYM) — the translation table, supplying the language-specific NAME and DESCRIPTION, joined on DATABASE_OBJECT_NAME and filtered by LANGUAGE = USERENV('LANG').
• FND_APPLICATION_VL (VIEW) — the applications view, supplying APPLICATION_NAME and APPLICATION_SHORT_NAME, joined on APPLICATION_ID.

The view text joins FAV.APPLICATION_ID = AO.APPLICATION_ID and AO.DATABASE_OBJECT_NAME = T.DATABASE_OBJECT_NAME. The ROW_ID column is derived from AO.ROWID, providing a pseudo-key for the underlying AK_OBJECTS row. No DISTINCT or aggregation is applied.

Key Columns

• ROW_ID — the ROWID of the base AK_OBJECTS row; useful as a unique identifier.
• DATABASE_OBJECT_NAME, NAME, DESCRIPTION — the registered object identifier plus its translatable name and description.
• APPLICATION_ID, APPLICATION_NAME, APPLICATION_SHORT_NAME — owning application identity and read-friendly labels.
• PRIMARY_KEY_NAME — the object's primary key column used by the AK framework.
• DEFAULTING_API_PKG / DEFAULTING_API_PROC — the package and procedure invoked to supply default values.
• VALIDATION_API_PKG / VALIDATION_API_PROC — the package and procedure invoked to validate the object; this is the column pair most relevant to a search for "validation_api_proc."
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield context and segment values.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage is diagnostic: identifying which validation or defaulting routine governs a registered object, or auditing the AK registrations for a given application.

To find the validation routine bound to an object:

• SELECT database_object_name, validation_api_pkg, validation_api_proc FROM ak_objects_vl WHERE database_object_name = :object_name;

To list all objects carrying a validation procedure for one application:

• SELECT name, database_object_name, validation_api_pkg, validation_api_proc FROM ak_objects_vl WHERE application_short_name = :app AND validation_api_proc IS NOT NULL;

Because the documented status is "10SC ONLY," direct dependencies on this view in custom code should be avoided where a supported alternative exists.