Search Results ak_regions_vl




Overview
Explore in AI Chat

Overview

AK_REGIONS_VL is a validation view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the AK product family, designated in ETRM as "AK - Common Modules-AK," which supplies the shared region and object metadata infrastructure used by the Oracle Application Framework (OAF) and related self-service pages. The ETRM description is the terse note "10SC ONLY," indicating that this object is restricted to a specific configuration context rather than being a general-purpose, universally deployed view.

Functionally, AK_REGIONS_VL presents a denormalized, translatable read model of region definitions. A "region" in AK terminology is a reusable UI container definition — a page fragment with a style, a column count, defaulting and validation APIs, search-panel behavior, and presentation attributes. The view joins the base region definition to its translated name and description, to the application that owns the region, and to the underlying database object that materializes the region's data. Because it is a VL ("validation" or, in FND conventions, language-aware) view, it exposes only rows matching the session language of the caller, making it suitable for direct use in forms, OAF pages, and concurrent programs that must display region metadata in the user's own language.

Underlying Base Objects

The documented base objects underlying AK_REGIONS_VL are AK_REGIONS, AK_REGIONS_TL, AK_OBJECTS_TL, and FND_APPLICATION_VL, all referenced through synonyms in the APPS schema. The join logic is:

Because AK_OBJECTS_TL is joined on DATABASE_OBJECT_NAME rather than on a surrogate key, the relationship assumes a one-to-one correspondence between a region's backing database object and its registered object metadata. The view is therefore a pure projection: it holds no data of its own and inherits all DML restrictions from its base tables.

Key Columns

Identification columns include ROW_ID (the AK_REGIONS row identifier), REGION_APPLICATION_ID, APPLICATION_SHORT_NAME, APPLICATION_NAME, REGION_CODE, DATABASE_OBJECT_NAME, OBJECT_NAME, and OBJECT_DESCRIPTION. Presentation columns include REGION_STYLE, NUM_COLUMNS, NUM_ROWS_DISPLAY, STYLE_SHEET_FILENAME, IMAGE_FILE_NAME, and HELP_TARGET, along with the ISFORM_FLAG and STATEFUL_FLAG indicators. Behavioral columns include REGION_DEFAULTING_API_PKG and REGION_DEFAULTING_API_PROC, REGION_VALIDATION_API_PKG and REGION_VALIDATION_API_PROC, FUNCTION_NAME, CHILDREN_VIEW_USAGE_NAME, and APPLICATIONMODULE_USAGE_NAME. Search-related columns include SEARCH_PANEL, ADVANCED_SEARCH_PANEL, CUSTOMIZE_PANEL, DEFAULT_SEARCH_PANEL, RESULTS_BASED_SEARCH, and AUTO_CUSTOMIZATION_CRITERIA. The view also exposes the standard fifteen ATTRIBUTE columns and the who-columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. The translated name and description columns arrive from AK_REGIONS_TL.

Common Use Cases and Queries

Typical uses include auditing region definitions owned by a given application, locating regions backed by a particular database object, and reporting which regions declare a defaulting or validation API package. A representative query is:

SELECT REGION_APPLICATION_ID, APPLICATION_SHORT_NAME, REGION_CODE,
       OBJECT_NAME, REGION_STYLE, NUM_COLUMNS
  FROM APPS.AK_REGIONS_VL
 WHERE APPLICATION_SHORT_NAME = :p_app
 ORDER BY REGION_CODE;

To find regions that declare server-side defaulting logic:

SELECT REGION_CODE, OBJECT_NAME,
       REGION_DEFAULTING_API_PKG, REGION_DEFAULTING_API_PROC
  FROM APPS.AK_REGIONS_VL
 WHERE REGION_DEFAULTING_API_PKG IS NOT NULL;

Because the view filters on USERENV('LANG'), results reflect the language of the connected session; clients requiring all translations should query AK_REGIONS_TL directly. The "10SC ONLY" designation means implementations should verify availability in their specific instance before depending on the view in custom code or reports.