Search Results ak_custom_region_items_tl_u1

Overview

AK_CUSTOM_REGION_ITEMS_TL is the translation ("TL") table that stores language-specific values for the base table AK_CUSTOM_REGION_ITEMS in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Both tables reside in the AK (Application Object Library / Attribute Knowledge) schema, which underpins the Oracle Application Framework (OAF) and the broader personalization, customization, and attribute-management framework. The base table defines customizable properties of a region item — that is, a customizable attribute exposed on a specific region of a specific page — and the TL table holds the translatable text associated with those definitions, principally the property value when its datatype is VARCHAR2.

The object is classified as VALID and is physically stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. The ETRM record lists this object alongside its base table, and the Data Vault classification heuristic derived from the FK structure describes AK_CUSTOM_REGION_ITEMS_TL as standalone. In Data Vault modeling terms, this can be viewed as a satellite-like structure: it carries descriptive, language-dependent attributes (the translated property value and the language/source-language descriptors) attached to the business key defined in the parent items object, rather than representing an independent business entity or an association between entities. The classification is a modeling suggestion only and should not be treated as a physical design directive.

Key Information Stored

The table's primary key, AK_CUSTOM_REGION_ITEMS_TL_PK, is a composite of eight columns: CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, REGION_APPLICATION_ID, REGION_CODE, ATTRIBUTE_APPLICATION_ID, ATTRIBUTE_CODE, PROPERTY_NAME, and LANGUAGE. This composite key uniquely identifies a translated property value for a given customization, region, and attribute. Notably, there is no single surrogate key column; the primary key is entirely composed of business-key components.

• Business-key columns: CUSTOMIZATION_APPLICATION_ID (application where the customization is used) and CUSTOMIZATION_CODE (the customization identifier); REGION_APPLICATION_ID and REGION_CODE (the region where the customization applies); ATTRIBUTE_APPLICATION_ID and ATTRIBUTE_CODE (the attribute being customized); and PROPERTY_NAME (the name of the customizable property).
• LANGUAGE and SOURCE_LANG: the target translation language and the source language from which the value was translated.
• PROPERTY_VARCHAR2_VALUE: the translated value of the property when its datatype is VARCHAR2, up to 4000 characters.
• WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record audit and concurrency information for each row.

Two indexes are documented: AK_CUSTOM_REGION_ITEMS_TL_U1, a UNIQUE index in APPS_TS_TX_IDX over the composite key columns plus ZD_EDITION_NAME (the editioning column present in 12.2.x Online Patching environments), making it the primary business-key candidate; and AK_CUSTOM_REGION_ITEMS_TL_N3, a NONUNIQUE index supporting lookups by REGION_CODE, REGION_APPLICATION_ID, CUSTOMIZATION_CODE, CUSTOMIZATION_APPLICATION_ID, ATTRIBUTE_APPLICATION_ID, and ATTRIBUTE_CODE.

Common Use Cases and Queries

The table is queried most often to resolve the effective text of a customizable region property in a specific language, particularly for personalization and OAF page rendering. Typical patterns include:

• Joining AK_CUSTOM_REGION_ITEMS_TL to AK_CUSTOM_REGION_ITEMS on the seven key columns excluding LANGUAGE, with a LANGUAGE predicate such as tl.language = userenv('LANG') or an explicit language code, to retrieve the translated property value.
• Filtering by REGION_APPLICATION_ID and REGION_CODE using index AK_CUSTOM_REGION_ITEMS_TL_N3 to locate all customized attributes within a region.
• Reporting on the inventory of customizations per application, grouping by CUSTOMIZATION_CODE and PROPERTY_NAME, and auditing changes through CREATION_DATE, LAST_UPDATE_DATE, and the WHO user columns.
• Translation validation queries that compare SOURCE_LANG against LANGUAGE to identify missing or untranslated property values (NULL or empty PROPERTY_VARCHAR2_VALUE).
• Reconciliation queries against the base table to detect orphaned translation rows or missing language coverage.

A basic join pattern is: SELECT tl.property_varchar2_value FROM ak_custom_region_items_tl tl WHERE tl.customization_application_id = :cust_app AND tl.customization_code = :cust_code AND tl.region_code = :region AND tl.language = userenv('LANG');

Related Objects

• AK.AK_CUSTOM_REGION_ITEMS — the base (non-translated) table to which this TL table corresponds; join on the seven shared key columns (CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, REGION_APPLICATION_ID, REGION_CODE, ATTRIBUTE_APPLICATION_ID, ATTRIBUTE_CODE, PROPERTY_NAME).
• Index AK_CUSTOM_REGION_ITEMS_TL_U1 — the unique index enforcing the primary business key plus ZD_EDITION_NAME.
• Index AK_CUSTOM_REGION_ITEMS_TL_N3 — the nonunique index supporting region and customization lookups.
• AK_CUSTOM_REGION_ITEMS_TL_PK — the primary key constraint spanning the eight key columns.
• FND_LANGUAGES / FND_LANGUAGE — reference tables used to resolve LANGUAGE and SOURCE_LANG values to installed languages.
• FND_APPLICATION — resolves the various application ID columns (CUSTOMIZATION_APPLICATION_ID, REGION_APPLICATION_ID, ATTRIBUTE_APPLICATION_ID) to application names.
• AK_REGIONS and AK_ATTRIBUTES — the AK metadata objects defining regions and attributes referenced by REGION_CODE and ATTRIBUTE_CODE.
• AK_CUSTOM_REGION_ITEM_VL / AK_CUSTOM_REGION_ITEMS_VL — the documented VL (translated view) layer that exposes language-specific values for these entities.
• OAF personalization APIs — the OA framework customization services that read and write these tables when regions and attributes are personalized.