Results for “customization_code”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AK_CUSTOMIZATIONS_TL is the translation (TL) table corresponding to AK_CUSTOMIZATIONS within the AK - Common Modules application in Oracle E-Business Suite. The AK product family underpins the Oracle Application Framework (OAF) and related extensibility infrastructure used across EBS 12.1.1 and 12.2.2. User-defined customizations captured in the base table carry translated, language-specific attributes—principally the customization NAME and DESCRIPTION—in this companion table, one row per installed language. This design follows the standard EBS multilingual pattern in which the base (_B) table stores language-independent columns and the _TL table stores language-dependent columns keyed by LANGUAGE.

In the documented physical schema (ETRM 12.2.2), the object resides in the AK schema and contains 14 columns. Based on the mined foreign-key structure, the table is classified heuristically as standalone in Data Vault terms. In practice this suggests it behaves as a descriptive satellite attached to a customization business key, with LANGUAGE introducing effective-dating-like granularity rather than serving as a hub or link.

Key Information Stored

The table’s identity is anchored by the primary key AK_CUSTOMIZATIONS_TL_PK over CUSTOMIZATION_APPLICATION_ID, REGION_CODE, CUSTOMIZATION_CODE, LANGUAGE, and REGION_APPLICATION_ID. A unique index, AK_CUSTOMIZATIONS_TL_U1, extends the same business key with ZD_EDITION_NAME, confirming the Editioning column as part of the effective uniqueness constraint. The principal columns include:

  • CUSTOMIZATION_APPLICATION_ID – application owning the customization; part of the composite key.
  • REGION_APPLICATION_ID and REGION_CODE – identify the UI region to which the customization applies; both are key components.
  • CUSTOMIZATION_CODE – the customization identifier; part of the key.
  • LANGUAGE and SOURCE_LANG – the translated language and the source language from which it was derived.
  • NAME and DESCRIPTION – the translated (language-dependent) attributes.
  • ZD_EDITION_NAME – Editioning column supporting EBS 12.2 online patching.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS WHO audit columns.

Common Use Cases and Queries

Typical usage is reporting and troubleshooting customization registrations for a given session language, or verifying that a translation row exists for each active customization. A representative query filtering by language:

  • SELECT t.CUSTOMIZATION_CODE, t.NAME, t.DESCRIPTION FROM AK.AK_CUSTOMIZATIONS_TL t WHERE t.LANGUAGE = USERENV('LANG') AND t.CUSTOMIZATION_APPLICATION_ID = :app_id;
  • Join to the base table to detect missing translations: SELECT b.CUSTOMIZATION_CODE FROM AK.AK_CUSTOMIZATIONS b LEFT JOIN AK.AK_CUSTOMIZATIONS_TL t ON t.CUSTOMIZATION_APPLICATION_ID = b.CUSTOMIZATION_APPLICATION_ID AND t.CUSTOMIZATION_CODE = b.CUSTOMIZATION_CODE AND t.REGION_CODE = b.REGION_CODE AND t.REGION_APPLICATION_ID = b.REGION_APPLICATION_ID AND t.LANGUAGE = USERENV('LANG') WHERE t.CUSTOMIZATION_CODE IS NULL;
  • Audit reporting on LAST_UPDATE_DATE to identify recently modified translated metadata.

Related Objects

  • AK_CUSTOMIZATIONS – the base table; joined on the composite key columns listed above.
  • AK_CUSTOMIZATIONS_TL_PK / AK_CUSTOMIZATIONS_TL_U1 – primary and unique indexes enforcing the business key.
  • AK_REGIONS – region metadata referenced by REGION_CODE and REGION_APPLICATION_ID.
  • AK_APPLICATIONS / FND_APPLICATION – application dictionaries resolving the *_APPLICATION_ID columns.
  • FND_LANGUAGES – reference for LANGUAGE and SOURCE_LANG values.
  • AK_CUSTOMIZATIONS_VL – where defined, the localized view exposing translated columns.