Results for “amv_d_entities_tl”

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

Overview

AMV_D_ENTITIES_TL is the translation table for AMV_D_ENTITIES_B within the AMV (Marketing Encyclopedia System) product module of Oracle E-Business Suite. It stores all columns and data required for Multi-Language Support (MLS), allowing the entity content defined in the base table to be presented in multiple installed languages. The object is owned by the AMV schema and carries VALID status in both Oracle EBS 12.1.1 and 12.2.2.

Under the heuristic Data Vault classification mined from its foreign key structure, AMV_D_ENTITIES_TL is satellite-leaning. This classification should be treated as a modeling suggestion: the table is a dependent, descriptive child rather than an independent hub or an associative link. It extends a parent business entity with language-specific descriptive attributes, and its rows are only meaningful in the context of that parent.

Key Information Stored

The documented physical schema contains twelve columns. The most functionally significant are listed below.

• ENTITY_ID — Surrogate identifier of the parent entity in AMV_D_ENTITIES_B; part of the composite primary key.
• LANGUAGE — The installed language code for the translated row; the second component of the primary key.
• ENTITY_NAME — The translated name of the entity, a principal business-key candidate.
• DESCRIPTION — The translated descriptive text associated with the entity.
• SOURCE_LANG — The language in which the record was originally authored, used by MLS processing to determine translation status.
• SECURITY_GROUP_ID — Security grouping reference used for data access partitioning.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching in 12.2.x.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing who created and last modified the row and when.

The surrogate primary key is AMV_D_ENTITIES_TL_PK, defined on (ENTITY_ID, LANGUAGE). Two unique indexes act as business-key candidates: AMV_D_ENTITIES_TL_U1 on (ENTITY_ID, LANGUAGE, ZD_EDITION_NAME) and AMV_D_ENTITIES_TL_U2 on (ENTITY_NAME, LANGUAGE, ZD_EDITION_NAME). Note that U2 enforces uniqueness of the translated entity name within a language, which is a meaningful constraint for MLS data quality.

Common Use Cases and Queries

Typical usage centers on retrieving translated entity names and descriptions for a given language while joining the base table for language-independent attributes.

• Fetching translated content for a specific language:

  SELECT b.entity_id, t.entity_name, t.description
  FROM   amv_d_entities_b b,
         amv_d_entities_tl t
  WHERE  b.entity_id = t.entity_id
  AND    t.language = USERENV('LANG');

• Auditing translation coverage by comparing the base table against the translation table to identify entities lacking a row for a target language.
• Reporting on MLS authorship and staleness using SOURCE_LANG and the audit date columns.
• Enforcing or investigating the business-key uniqueness rule on (ENTITY_NAME, LANGUAGE) when duplicate translated names are suspected.

Related Objects

• AMV_D_ENTITIES_B — The base table; joined on ENTITY_ID = ENTITY_ID. The translation table cannot exist without it.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID, governing secured access to translated data.
• AMV_D_ENTITIES_TL_PK — The primary key constraint on (ENTITY_ID, LANGUAGE).
• AMV_D_ENTITIES_TL_U1 and AMV_D_ENTITIES_TL_U2 — Unique indexes serving as business-key candidates.
• Standard MLS/FND language infrastructure objects that resolve LANGUAGE and SOURCE_LANG values.

Because AMV is a Marketing Encyclopedia System component, all access should respect MLS language filtering, and any integration reading translated content must supply a LANGUAGE predicate to avoid returning multiple rows per entity.