Search Results ak_custom_regions_tl




Overview
Explore in AI Chat

Overview

AK_CUSTOM_REGIONS_TL is the translation (TL) table corresponding to AK_CUSTOM_REGIONS in the Oracle E-Business Suite AK (Common Modules – AK) product. It resides in the AK schema and holds language-specific, translated content for custom region definitions registered through the Oracle Application Framework and the AK customization infrastructure. Where the base table AK_CUSTOM_REGIONS stores the language-independent definition of a custom region and its associated properties, AK_CUSTOM_REGIONS_TL stores the per-language values of those properties, allowing a single customization to present localized text to users running different session languages.

The object is documented as VALID in both EBS 12.1.1 and 12.2.2, with 14 physical columns in the 12.2.2 documented schema. Its primary key, AK_CUSTOM_REGIONS_TL_PK, is composed of CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, LANGUAGE, PROPERTY_NAME, REGION_APPLICATION_ID, and REGION_CODE. A unique index, AK_CUSTOM_REGIONS_TL_U1, extends that key with ZD_EDITION_NAME. Heuristic Data Vault classification derived from the foreign-key structure identifies this object as standalone; from a modeling perspective it is best treated as a satellite attached to the AK_CUSTOM_REGIONS business key, carrying descriptive, language-dependent attribute values and standard EBS audit columns.

Key Information Stored

The most significant columns are the composite key attributes and the translatable value columns:

  • CUSTOMIZATION_APPLICATION_ID and CUSTOMIZATION_CODE — identify the owning customization, the highest-level component of the key and the link back to the customization registry.
  • REGION_APPLICATION_ID and REGION_CODE — identify the specific custom region within that customization to which the translated property belongs.
  • PROPERTY_NAME — names the region property being translated (for example a prompt, label, or instructional string).
  • LANGUAGE and SOURCE_LANG — LANGUAGE is the target language of the row; SOURCE_LANG records the language from which the translation was derived, supporting the standard EBS TL pattern.
  • PROPERTY_VARCHAR2_VALUE — the actual translated text value for the property in the row's language. This is the principal payload of the table.
  • ZD_EDITION_NAME — the editioning column that supports Online Patching in 12.2.x; it participates in the unique index AK_CUSTOM_REGIONS_TL_U1.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last changed the row and when.

The surrogate-style primary key AK_CUSTOM_REGIONS_TL_PK differs from the business-key candidate AK_CUSTOM_REGIONS_TL_U1 only by the inclusion of ZD_EDITION_NAME, which is expected in a 12.2.2 editioned TL table.

Common Use Cases and Queries

Typical usage centers on retrieving the correct translated property value for a customization and region in the user's language, with fallback to the base language when no translation exists. A representative query pattern joins the TL table to the base region definition and filters on language:

  • Reporting on which customizations and regions have translations in which languages, for localization coverage analysis.
  • Extracting prompt and label text for documentation, testing scripts, or data migration where the same region is deployed to multiple operating units or locales.
  • Diagnosing missing or duplicate translation rows by checking cardinality against AK_CUSTOM_REGIONS for each LANGUAGE.
  • Auditing change history for translated content using LAST_UPDATED_BY and LAST_UPDATE_DATE.
  • Reconciling translations against SOURCE_LANG to detect values that predate a source-string change.

Queries should always constrain on LANGUAGE and, in 12.2.x, on ZD_EDITION_NAME to avoid picking retired edition rows.

Related Objects

  • AK_CUSTOM_REGIONS — the base table this object translates; joined on CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, REGION_APPLICATION_ID, and REGION_CODE.
  • AK_CUSTOM_REGIONS_TL_PK — the primary key constraint enforcing uniqueness of the composite translation key.
  • AK_CUSTOM_REGIONS_TL_U1 — the unique index adding ZD_EDITION_NAME to the key.
  • AK_CUSTOM_REGIONS_ALL / AK_CUSTOM_REGIONS_VL — the typical view family, where VL views join the base and TL tables and expose only the current-language rows.
  • AK_REGIONS and AK_REGIONS_TL — the standard (non-custom) region definitions from which custom regions are adapted.
  • FND_LANGUAGES — joined on LANGUAGE to resolve the installed language and its translated name.
  • AK_CUSTOM_REGION_PROPERTIES — where present, provides the property definitions that PROPERTY_NAME in this table references.