Search Results lov_presence_flag

Overview

AK_REGION_ITEMS_VL is a validation view (VL) owned by the APPS schema in Oracle E-Business Suite, belonging to the AK – Common Modules product family. Its ETRM documentation carries the terse description "10SC ONLY," indicating that its intended usage is confined to the ten-schema (10SC) configuration and that it is not a general-purpose interface for external consumers. Functionally, the view flattens the metadata that defines the individual items rendered within an Oracle EBS region. Each row corresponds to one region item — a field, prompt, list of values, or display element — and the view joins that item's operational attributes to the translatable names and descriptions of the attribute and the region it belongs to.

In reporting and integration terms, AK_REGION_ITEMS_VL exposes the self-describing metadata layer that drives the Oracle Application Framework and related AK region rendering engine. It is therefore encountered primarily in diagnostics, metadata extracts, upgrade or migration audits, and custom tooling that must reconstruct how a region is composed rather than in transactional reporting.

Underlying Base Objects

The documented view text is anchored on ARA, an alias for AK_REGION_ITEMS, which supplies the bulk of the item-level attributes. Translatable and descriptive context is supplied through joins to AK_REGION_ITEMS_TL (attribute label long and short forms), AK_ATTRIBUTES and AK_ATTRIBUTES_TL (attribute name, description, and data type), AK_REGIONS_TL (the LOV region name), and FND_APPLICATION / FND_APPLICATION_TL (the application name for the attribute's owning application). The ETRM metadata also lists FND_MENUS and AK_ATTRIBUTES as referenced base objects, reflecting the region-to-menu relationships used elsewhere in the AK schema. All base objects are accessed through APPS synonyms, so the view presents a single, schema-qualified read surface regardless of the physical location of the underlying tables.

Key Columns

• REGION_APPLICATION_ID, REGION_CODE — identify the parent region to which the item belongs.
• ATTRIBUTE_APPLICATION_ID, ATTRIBUTE_CODE, ATTRIBUTE_NAME, ATTRIBUTE_DESCRIPTION — identify and describe the attribute bound to the item, with the translatable name sourced from AK_ATTRIBUTES_TL.
• DISPLAY_SEQUENCE, ORDER_SEQUENCE, ORDER_DIRECTION — control item ordering within the region.
• NODE_DISPLAY_FLAG, NODE_QUERY_FLAG, UPDATE_FLAG, REQUIRED_FLAG, SUBMIT, ENCRYPT — behavioral flags governing rendering, queryability, updatability, and submission.
• LOV_PRESENCE_FLAG, LOV_REGION_NAME, LOV_FOREIGN_KEY_NAME, LOV_ATTRIBUTE_NAME, LOV_DEFAULT_FLAG — describe list-of-values configuration; LOV_PRESENCE_FLAG is derived via DECODE on LOV_FOREIGN_KEY_NAME.
• DEFAULT_VALUE_VARCHAR2, DEFAULT_VALUE_DATE, DEFAULT_VALUE_NUMBER — datatype-specific defaults for the item.
• REGION_DEFAULTING_API_PKG/PROC, REGION_VALIDATION_API_PKG/PROC, ICX_CUSTOM_CALL — server-side hooks invoked during defaulting and validation.
• DATA_TYPE — the attribute's underlying datatype sourced from AK_ATTRIBUTES.
• ATTRIBUTE_LABEL_LONG, ATTRIBUTE_LABEL_SHORT, ATTRIBUTE_LABEL_LENGTH — prompt text and its display width.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage is metadata inspection. To list all items for a given region in display order:

SELECT region_code, attribute_code, attribute_name,
       display_sequence, required_flag, lov_presence_flag
FROM   apps.ak_region_items_vl
WHERE  region_application_id = :app_id
AND    region_code = :region_code
ORDER  BY display_sequence;

To find every region exposing an attribute with an associated LOV:

SELECT region_code, attribute_code, lov_region_name
FROM   apps.ak_region_items_vl
WHERE  lov_presence_flag = 'Y';

Because the object is documented as "10SC ONLY," queries should be restricted to the supported configuration and treated as read-only metadata access; direct DML against AK_REGION_ITEMS should be performed through supported AK APIs rather than through this view.