Results for “ak_region_items_tl”

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

Overview

AK_REGION_ITEMS_TL is a translation table in the AK schema (Common Modules-AK) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the multilingual (translated) content for the base table AK_REGION_ITEMS. In the Oracle EBS architecture, the _TL suffix denotes a Translation entity that mirrors the base (non-translated) table and holds language-dependent descriptive attributes—the same record exists once per installed language rather than once per business entity.

Because AK_REGION_ITEMS_TL carries descriptive, language-varying attributes keyed to a parent entity, the mined Data Vault classification is satellite-leaning. From a modeling perspective, it is best understood as a descriptive satellite that hangs off the AK_REGION_ITEMS hub, with LANGUAGE participating in the key to distinguish each translated context. The base business identity (region, application, attribute, and attribute application) originates in the parent and is repeated here as a foreign-key reference.

Key Information Stored

The table contains 15 documented columns. The most significant are the composite identifier and the translatable text attributes:

• REGION_CODE and REGION_APPLICATION_ID — identify the owning region; part of the foreign key to AK_REGION_ITEMS.
• ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID — identify the region item attribute; also part of the foreign key to the base table.
• LANGUAGE — the installed language code, keying each translated row.
• ATTRIBUTE_LABEL_LONG and ATTRIBUTE_LABEL_SHORT — the translated display strings that give the region item its presentation text in a given language.
• SOURCE_LANG and DESCRIPTION — the language the translation was sourced from and an optional descriptive note.
• ZD_EDITION_NAME — the editioning column used for online patching (Edition-Based Redefinition) in 12.2.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The surrogate primary key is AK_REGION_ITEMS_TL_PK over (REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, LANGUAGE). The documented unique index AK_REGION_ITEMS_TL_U1 extends this business key with ZD_EDITION_NAME, reflecting the editioning requirement of the 12.2 data model.

Common Use Cases and Queries

The primary use case is resolving translated labels for a region item in the user's session language, typically joined with the base table and the language table:

• Reporting region item labels for a specific deployment language.
• Auditing missing translations where a translation row does not exist for an installed language.
• Building multilingual reference extracts for integration or data-migration projects.

A typical retrieval pattern filters on language via the NLS session:

SELECT b.REGION_CODE, t.ATTRIBUTE_LABEL_SHORT, t.ATTRIBUTE_LABEL_LONG
FROM AK.AK_REGION_ITEMS_TL t, AK.AK_REGION_ITEMS b
WHERE t.REGION_CODE = b.REGION_CODE
AND t.REGION_APPLICATION_ID = b.REGION_APPLICATION_ID
AND t.ATTRIBUTE_CODE = b.ATTRIBUTE_CODE
AND t.ATTRIBUTE_APPLICATION_ID = b.ATTRIBUTE_APPLICATION_ID
AND t.LANGUAGE = USERENV('LANG');

Related Objects

The most significant related objects, based on the documented foreign-key and primary-key relationships, are:

• AK_REGION_ITEMS — the base table; the FK carries REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID.
• AK_REGION_ITEMS_TL_PK and AK_REGION_ITEMS_TL_U1 — the primary and unique key constraints enforcing identity and editioning.
• FND_LANGUAGES — the installed-language reference validated against LANGUAGE.
• Region definition objects such as AK_REGIONS / AK_REGIONS_TL, to which region items ultimately resolve.

These relationships make AK_REGION_ITEMS_TL a dependent translation satellite whose integrity depends on the AK_REGION_ITEMS business key and whose reporting value derives from joining translated labels back to their base region item.