Search Results ams_cells_all_tl_pk




Overview

The AMS_CELLS_ALL_TL table is a core translation table within the Oracle E-Business Suite (EBS) Marketing (AMS) module. It functions as a language-specific repository for all user-facing, translatable text associated with marketing cell definitions. A marketing cell is a fundamental segmentation construct used to categorize and target customers or prospects for campaigns and activities. This table enables the support of multiple languages within a single EBS instance, allowing the descriptive attributes of a cell to be stored and retrieved in a user's preferred language. Its role is integral to the global deployment of Oracle Marketing, ensuring that marketing definitions remain consistent and accessible across diverse linguistic environments.

Key Information Stored

The table's primary purpose is to store the translated textual columns for the base entity table, AMS_CELLS_ALL_B. While the specific column list is not detailed in the provided metadata, the structure of Translation (TL) tables in Oracle EBS follows a consistent pattern. The key columns typically include a foreign key to the base table (CELL_ID), a language identifier (LANGUAGE), and the translated text fields themselves. These translated fields commonly encompass the cell's name (e.g., CELL_NAME), description (DESCRIPTION), and potentially other UI labels. The primary key, AMS_CELLS_ALL_TL_PK, is a composite key on LANGUAGE and CELL_ID, ensuring a unique record for each combination of a cell and its language translation.

Common Use Cases and Queries

The primary use case is the dynamic retrieval of cell information in a user's session language for forms, reports, and segmentation logic. A common SQL pattern involves joining this table with its base table, filtered by the session's language setting. For example, to generate a report of all active cells with their translated names and descriptions, a query would join AMS_CELLS_ALL_B and AMS_CELLS_ALL_TL on CELL_ID, with a WHERE clause on AMS_CELLS_ALL_TL.LANGUAGE = userenv('LANG'). Another critical scenario is during the implementation and maintenance of multi-language support, where data loaders or APIs populate this table with translated strings for each supported language. Reporting on translation completeness—identifying cells missing descriptions in a specific language—is also a frequent administrative task.

Related Objects

  • AMS_CELLS_ALL_B: This is the base transactional table for marketing cells, storing non-translatable information such as IDs, dates, and structural attributes. The documented foreign key relationship explicitly states that AMS_CELLS_ALL_TL.CELL_ID references AMS_CELLS_ALL_B. This is the fundamental join for any query requiring both operational and descriptive cell data.
  • The table is also intrinsically linked to the Oracle Applications' multilingual architecture, interacting with seed data tables like FND_LANGUAGES to validate the LANGUAGE column. While not explicitly listed, it is typically accessed via higher-level APIs or views provided by the AMS product team, which abstract the direct joins and language filtering logic for application developers.
  • Table: AMS_CELLS_ALL_TL 12.1.1

    owner:AMS,  object_type:TABLE,  fnd_design_data:AMS.AMS_CELLS_ALL_TL,  object_name:AMS_CELLS_ALL_TL,  status:VALID,  product: AMS - Marketingdescription: This table stores all translated columns for marketing Cells definition. ,  implementation_dba_data: AMS.AMS_CELLS_ALL_TL

  • Table: AMS_CELLS_ALL_TL 12.2.2

    owner:AMS,  object_type:TABLE,  fnd_design_data:AMS.AMS_CELLS_ALL_TL,  object_name:AMS_CELLS_ALL_TL,  status:VALID,  product: AMS - Marketingdescription: This table stores all translated columns for marketing Cells definition. ,  implementation_dba_data: AMS.AMS_CELLS_ALL_TL