Results for “amv_c_channels_tl”

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

Overview

AMV_C_CHANNELS_TL is the translation (TL) table for AMV_C_CHANNELS_B within the Oracle E-Business Suite Marketing Encyclopedia System (AMV) product. Its purpose is to store all language-dependent columns and data required for Multi-Language Support (MLS), so that a single base record in AMV_C_CHANNELS_B can present channel names and descriptions in the session language of each user. A channel is a marketing communication vehicle (for example, a web channel, email channel, or partner channel) and this table holds the translatable attributes that describe it.

From a Data Vault modeling perspective, the metadata classifies this table as satellite-leaning. It carries descriptive, non-key attributes tied to a parent business key rather than introducing new relationships, which is consistent with the behavior of a satellite table. It is a child of the base table rather than an independent entity.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• CHANNEL_ID — Surrogate identifier inherited from AMV_C_CHANNELS_B; the join key to the base entity.
• LANGUAGE — The NLS language code for the translated row.
• CHANNEL_NAME — The translated display name of the marketing channel; a business-key component.
• DESCRIPTION — The translated free-text description used on marketing screens.
• SOURCE_LANG — The language of the original (source) record, used by MLS to track translation lineage.
• ZD_EDITION_NAME — Editioning column supporting EBR (Edition-Based Redefinition) and Online Patching in 12.2.x; part of the documented unique indexes.
• SECURITY_GROUP_ID — Multi-Org / security grouping reference, with a foreign key to FND_SECURITY_GROUPS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns.

The surrogate primary key is AMV_C_CHANNELS_TL_PK, composed of CHANNEL_ID and LANGUAGE. Documented unique indexes that act as business-key candidates are AMV_C_CHANNELS_TL_U2 (LANGUAGE, CHANNEL_NAME, ZD_EDITION_NAME) and CH_TL_PK (CHANNEL_ID, LANGUAGE, ZD_EDITION_NAME). The distinction matters: the PK enforces uniqueness per channel per language, while the U2 index enforces uniqueness of a channel name within a language.

Common Use Cases and Queries

Typical usage joins the base table to the translation table filtered by the user's session language, for example:

• Reporting channel names in a specific locale: SELECT b.channel_id, t.channel_name FROM amv_c_channels_b b, amv_c_channels_tl t WHERE b.channel_id = t.channel_id AND t.language = 'US'.
• Finding untranslated channels: compare rows present in AMV_C_CHANNELS_B against those in AMV_C_CHANNELS_TL for a given LANGUAGE.
• Building LOVs or concurrent program outputs that must display localized names.

The MLS mechanism means applications should query the TL table using the session language, not assume a single row per channel.

Related Objects

• AMV_C_CHANNELS_B — base table; AMV_C_CHANNELS_TL.CHANNEL_ID references it.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID.
• AMV_C_CHANNELS_VL / AMV_C_CHANNELS_V — MLS views that expose translated data.