Search Results ak_attributes_vl




Overview
Explore in AI Chat

Overview

AK_ATTRIBUTES_VL is a view owned by the APPS schema in Oracle E-Business Suite, classified under product AK (Common Modules–AK). The ETRM metadata describes it as “10SC ONLY,” indicating that this object was defined in support of the 10SC (E-Business Suite) attribute framework rather than as a general-purpose application table. The view exposes the definition of descriptive and extensible attributes registered against the AK attribute model, combining the base attribute definition stored in AK_ATTRIBUTES with translated name, description, and label text plus the owning application’s name and short name.

From a reporting and integration perspective, AK_ATTRIBUTES_VL provides a denormalized, language-aware read interface over the AK attribute dictionary. Rather than joining the base attribute table to its translation tables and FND_APPLICATION_VL manually, a consumer can query this view and obtain application short names, translated labels, display properties, data typing, and default values in a single result set. Its “_VL” suffix follows the standard EBS convention that the view returns values in the session’s current language, as determined by USERENV('LANG').

Underlying Base Objects

According to the documented view metadata, AK_ATTRIBUTES_VL is defined over four referenced objects: AK_ATTRIBUTES, AK_ATTRIBUTES_TL, AK_REGIONS_TL, and FND_APPLICATION_VL. The first three are referenced as synonyms in the APPS schema; FND_APPLICATION_VL is itself a view.

The primary driver of the query is AK_ATTRIBUTES (aliased AA), which stores the core attribute records. It is joined to AK_ATTRIBUTES_TL (AAT) on ATTRIBUTE_APPLICATION_ID and ATTRIBUTE_CODE, with the translation row restricted to AAT.LANGUAGE = USERENV('LANG'). The owning application is resolved through FND_APPLICATION_VL (FAV) on ATTRIBUTE_APPLICATION_ID = FAV.APPLICATION_ID, supplying APPLICATION_SHORT_NAME and APPLICATION_NAME. An outer join to AK_REGIONS_TL (ART) on LOV_REGION_CODE and LOV_REGION_APPLICATION_ID, again filtered by USERENV('LANG'), populates the optional list-of-values region name. Because AK_REGIONS_TL is outer-joined, attributes without a defined LOV region are still returned. The view also surfaces AA.ROWID as ROW_ID.

Key Columns

The columns fall into several functional groups:

Common Use Cases and Queries

Typical uses include attribute-dictionary reporting, auditing attribute display configuration across modules, and integration extracts that need translated labels alongside application context.

  • List attributes for a given application: 
    SELECT attribute_code, name, data_type, attribute_label_short
FROM   apps.ak_attributes_vl
WHERE  application_short_name = 'FND'
ORDER  BY attribute_code;
  • Identify attributes using a specific LOV region: 
    SELECT attribute_application_id, attribute_code, lov_region_name
FROM   apps.ak_attributes_vl
WHERE  lov_region_code IS NOT NULL;
  • Review display formatting attributes: 
    SELECT attribute_code, bold, italic, horizontal_alignment
FROM   apps.ak_attributes_vl
WHERE  bold = 'Y' OR italic = 'Y';
  • Because translation is resolved by USERENV('LANG'), results reflect the run-time language; queries intended for multilingual extracts should ensure the correct session language is set.