Search Results ams_dm_models_all_tl




Overview
Explore in AI Chat

Overview

The AMS_DM_MODELS_ALL_TL table is a core data translation object within the Oracle E-Business Suite Marketing (AMS) module. It functions as a language-specific container for the translatable descriptive columns associated with Data Mining (DM) models. In a multi-language deployment of Oracle EBS, this table enables the storage of model names and descriptions in multiple languages, supporting global business operations. Its primary role is to separate language-sensitive textual data from the base transactional information stored in the AMS_DM_MODELS_ALL_B table, thereby facilitating a clean and efficient internationalization architecture. The table is valid and actively used in both the 12.1.1 and 12.2.2 versions of Oracle EBS.

Key Information Stored

The table's structure is designed to hold translated text linked to a specific data mining model and language. The primary key uniquely identifies each translation record and consists of two columns: MODEL_ID, which links to the base model record, and LANGUAGE, which specifies the language code (e.g., 'US' for American English). The most critical data stored includes translated descriptive attributes, typically the model's NAME and DESCRIPTION. Additional columns may exist for metadata such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN to track changes, as is standard for EBS translation tables. The SOURCE_LANG column is also commonly present to denote the original language of the source data.

Common Use Cases and Queries

The primary use case is retrieving model descriptions in a user's session language for display in Oracle Marketing forms and reports. A standard query involves joining this table with its base table, filtering by the desired MODEL_ID and the current session language. For example, to fetch a model's name in French, one might use:

  • SELECT tl.name FROM ams_dm_models_all_tl tl WHERE tl.model_id = :p_model_id AND tl.language = 'F';

Another common pattern is a left outer join from the base table to ensure a result is returned even if a specific translation is missing, often defaulting to the source language:

  • SELECT b.model_id, NVL(tl.name, b.name) model_name FROM ams_dm_models_all_b b, ams_dm_models_all_tl tl WHERE b.model_id = tl.model_id(+) AND tl.language(+) = USERENV('LANG');

Data maintenance tasks, such as seeding new translations or updating existing ones for a global rollout, also directly involve this table.

Related Objects

The table maintains a strict dependency relationship with its parent base table, as defined by its foreign key constraint. The documented relationships are:

  • Primary Key: AMS_DM_MODELS_ALL_TL_PK on columns (LANGUAGE, MODEL_ID).
  • Foreign Key (References): The table AMS_DM_MODELS_ALL_TL has a foreign key where its column MODEL_ID references the primary key of the table AMS_DM_MODELS_ALL_B. This enforces referential integrity, ensuring every translation record corresponds to a valid base model record.

Consequently, any API, form, or report within the Marketing module that displays a localized model name will inherently depend on a join between AMS_DM_MODELS_ALL_B and AMS_DM_MODELS_ALL_TL. The table may also be referenced by other translation views or public APIs that abstract the underlying join logic for developers.