Search Results lov_attribute_name




Overview
Explore in AI Chat

Overview

AK_OBJECT_ATTRIBUTES_VL is a validation and translation view owned by the APPS schema within the AK (Common Modules-AK) product family. It exposes attribute-level metadata for objects registered in the Oracle Application Object Library's extensibility framework. In Oracle EBS 12.1.1 and 12.2.2, the view serves as the reporting and integration surface over the AK_OBJECT_ATTRIBUTES table and its associated translation tables. The "_VL" suffix indicates that the view joins the base entity table with its "_TL" (translation) counterpart and filters the translation rows to the session language, using the USERENV('LANG') function. This makes the view language-aware: queries return the attribute labels, object names, region names, and attribute names appropriate to the connected user's language setting regardless of how many translations exist in the underlying tables.

The ETRM documentation marks this object as "10SC ONLY" and status VALID. It is a read-only view and therefore carries no DML triggers or constraints. Its principal role is to support both internal AK maintenance screens and external reporting against object attribute definitions, including the TRANSLATION_FLAG column that prompted the user's search.

Underlying Base Objects

The view is defined over seven referenced base objects. Five are synonyms onto AK tables, one is the FND_APPLICATION_VL view, and one is the AK_OBJECT_ATTRIBUTES table itself:

The joins are inner joins keyed on attribute code and application ID, with language filters applied to each translation table.

Key Columns

Several columns are central to interpreting the view. DATABASE_OBJECT_NAME identifies the underlying database object; OBJECT_NAME and OBJECT_DESCRIPTION provide its translated identity. ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, and the translated NAME identify the specific attribute. DATA_TYPE defines the attribute's data type (for example, VARCHAR2, NUMBER, or DATE), while COLUMN_NAME maps to the physical column when the attribute is table-backed.

Presentation and behavior columns include BOLD, ITALIC, HORIZONTAL_ALIGNMENT, VERTICAL_ALIGNMENT, DISPLAY_VALUE_LENGTH, and ATTRIBUTE_LABEL_LENGTH. Validation and defaulting metadata is carried by REQUIRED_FLAG, DEFAULTING_API_PKG, DEFAULTING_API_PROC, VALIDATION_API_PKG, VALIDATION_API_PROC, and the DEFAULT_VALUE_VARCHAR2, DEFAULT_VALUE_NUMBER, and DEFAULT_VALUE_DATE columns. LOV behavior is controlled by LOV_REGION_NAME, LOV_ATTRIBUTE_NAME, LOV_REGION_CODE, and LOV_FOREIGN_KEY_NAME.

The TRANSLATION_FLAG column, which is the term the user searched for, indicates whether the attribute participates in the AK translation model. Attribute1 through Attribute15 and ATTRIBUTE_CATEGORY provide the standard EBS descriptive flexfield columns. Audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. The ROW_ID column exposes the underlying ROWID for the AK_OBJECT_ATTRIBUTES row.

Common Use Cases and Queries

Typical uses include auditing attribute definitions for a given object, identifying attributes flagged for translation, and driving generated UI or integration metadata. A common query lists all translatable attributes for a specific object:

  • SELECT object_name, attribute_code, name, data_type, translation_flag
  • FROM apps.ak_object_attributes_vl
  • WHERE database_object_name = 'MY_OBJECT'
  • AND translation_flag = 'Y';

Another frequent scenario examines required attributes and their validation routines for a region or object, joining DESCRIPTION for documentation. Reports often select APPLICATION_SHORT_NAME, OBJECT_NAME, ATTRIBUTE_LABEL_LONG, REQUIRED_FLAG, and DATA_TYPE to produce a functional specification of an object's attribute set. Because the view filters translations by USERENV('LANG'), the same query returns localized labels for each user, making it suitable for multilingual reporting without additional translation joins. Since the object is a view, it should be queried rather than modified, and users should confirm that the connected responsibility's language is set appropriately to obtain the desired translation.