Search Results msd_cs_clmn_identifiers_tl




Overview
Explore in AI Chat

Overview

MSD_CS_CLMN_IDENTIFIERS_TL is a translatable (TL) table owned by the MSD schema, which supports the Demand Planning module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold the language-dependent, translatable attributes for the base table MSD_CS_CLMN_IDENTIFIERS. In the standard EBS multilingual architecture, each base ("_B" or base) table stores language-independent data, while its companion "_TL" table stores descriptive text that varies by installed language. This pattern enables seeded and user-defined column identifiers to display localized descriptions and prompts across a multi-language deployment.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is assessed as standalone. In Data Vault modeling terms, that suggests it is best modeled as an independent satellite-like structure keyed by its own business keys rather than as a hub or link, consistent with the fact that no outward foreign-key dependencies were documented. This classification is a modeling suggestion only, derived from the FK metadata, and reflects the object's self-contained key structure.

Key Information Stored

The table's physical schema in 12.2.2 contains 15 columns. The primary key, MSD_CS_CLMN_IDENTIFIERS_TL_PK, is defined on the composite of COLUMN_IDENTIFIER and LANGUAGE, which together constitute the language-aware surrogate/identifying key for each translated row.

  • COLUMN_IDENTIFIER — The business identifier of the column definition; combined with LANGUAGE forms the primary key.
  • LANGUAGE — The installed language code for the translation; part of the primary key.
  • DESCRIPTION — The localized, translatable descriptive text for the column identifier.
  • USER_PROMPT — The localized user-facing prompt string presented to planners in Demand Planning.
  • SOURCE_LANG — The language from which the current translated row was derived or seeded.
  • ZD_EDITION_NAME — Editioning column; part of the unique business-key candidate MSD_CS_CLMN_IDENTIFIERS_TL_U1 (COLUMN_IDENTIFIER, LANGUAGE, ZD_EDITION_NAME), supporting Edition-Based Redefinition.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording row creation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the request and program that last populated the row.

The distinction between the primary key (COLUMN_IDENTIFIER, LANGUAGE) and the unique index (COLUMN_IDENTIFIER, LANGUAGE, ZD_EDITION_NAME) reflects the 12.2 editioning model layered over the classic 12.1 multilingual key structure.

Common Use Cases and Queries

Typical use is joining the translation table to the base table to retrieve display text for a specific language, or to audit missing translations. A representative pattern resolves the base identifier and its English prompt:

  • Reporting: SELECT t.COLUMN_IDENTIFIER, t.DESCRIPTION, t.USER_PROMPT FROM MSD.MSD_CS_CLMN_IDENTIFIERS_TL t WHERE t.LANGUAGE = 'US';
  • Translation completeness: compare row counts between MSD_CS_CLMN_IDENTIFIERS and this table grouped by LANGUAGE to find identifiers lacking translated descriptions.
  • Business-key lookup: filter on COLUMN_IDENTIFIER and LANGUAGE to isolate an edition-specific row using ZD_EDITION_NAME.
  • Audit and lineage: select REQUEST_ID, PROGRAM_ID, and the audit columns to trace which concurrent program loaded or updated a translation.

These queries support localization reviews, data-quality checks, and Demand Planning configuration validation.

Related Objects

The most significant dependencies derive from the base/translation pairing and the shared key structure.

  • MSD_CS_CLMN_IDENTIFIERS — The base table whose translatable attributes are stored here; joins on COLUMN_IDENTIFIER.
  • FND_LANGUAGES — Provides valid LANGUAGE codes used as the translation key.
  • FND_APPLICATION / FND_CONCURRENT_PROGRAMS — Reference PROGRAM_APPLICATION_ID and PROGRAM_ID for load lineage.
  • FND_CONCURRENT_REQUESTS — Resolves REQUEST_ID to the concurrent request that populated rows.
  • MSD_CS_CLMN_IDENTIFIERS_TL_PK / _U1 — The primary-key and unique indexes enforcing identity.

Collectively these objects define how column identifier translations are stored, keyed, and consumed within Demand Planning.