Search Results attribute_description




Overview
Explore in AI Chat

Overview

AK_CUSTOM_REGION_ITEMS_VL is a view owned by the APPS schema in Oracle E-Business Suite, belonging to the AK (Common Modules – Application Kit) product. It presents customized properties applied to region items within the Oracle EBS personalization and extensibility framework. The view is documented as VALID and is described as storing "region item properties customizations," meaning it exposes the configuration values that administrators and personalization layers have applied to individual attributes rendered on a region. Because region items and their attributes drive dynamic user interface behavior across multiple EBS modules, this view serves as a reporting and integration surface for auditing personalizations, reviewing attribute-level customizations, and extracting descriptive metadata such as attribute descriptions.

Underlying Base Objects

The view is defined across six documented base objects, all referenced through synonyms except FND_APPLICATION_VL, which is itself a view:

  • AK_CUSTOM_REGION_ITEMS – the primary customization entity holding property values per region item.
  • AK_CUSTOM_REGION_ITEMS_TL – the translation table supplying language-specific property values where the registry marks a property translatable.
  • AK_CUSTOM_REGISTRY – the registry of property definitions, joined (outer-joined) with custom level restricted to 'REGION_ITEM'.
  • AK_REGION_ITEMS – the region item definitions, providing ITEM_NAME.
  • AK_ATTRIBUTES_TL – translated attribute metadata, supplying NAME and DESCRIPTION.
  • FND_APPLICATION_VL – the application view supplying application short name and name for the attribute's owning application.

Joins are constructed on matching customization, region, attribute, and property keys, with language filters applied via USERENV('LANG') to both translation tables. A DECODE on ACREG.TRANSLATABLE determines whether the translated or base VARCHAR2 property value is returned.

Key Columns

The view exposes both identifying keys and descriptive values. Notable columns include:

Common Use Cases and Queries

Typical use cases include personalization audits, identifying which region items carry custom property values, and resolving attribute descriptions for reporting. A representative query filtering on attribute_description is:

  • SELECT attribute_name, attribute_description, item_name, property_name, property_varchar2_value FROM apps.ak_custom_region_items_vl WHERE attribute_description LIKE '%Display%';

    • To report all customizations for a given region:

  • SELECT region_code, item_name, attribute_name, property_name, property_varchar2_value FROM apps.ak_custom_region_items_vl WHERE region_code = :region_code ORDER BY item_name, attribute_name, property_name;

    • Because the view resolves attribute descriptions and application names, it is well suited for integration extracts that feed external documentation, migration tooling, or configuration comparators without requiring callers to manually join the AK attribute and translation tables.