Search Results msc_questions_tl




Overview
Explore in AI Chat

Overview

MSC_QUESTIONS_TL is a translation (TL) table within the MSC schema, owned by the Oracle Advanced Supply Chain Planning (ASCP) module. It stores the language-specific, translated text of questions presented by the "Ask Oracle" feature, which is the interactive, natural-language query interface embedded in Oracle EBS planning and business intelligence workflows. Because Oracle EBS supports multilingual deployments, user-facing textual content is separated into base tables and their corresponding _TL counterparts; MSC_QUESTIONS_TL holds one row per question per installed language, allowing the same logical question to display correctly across different locale settings.

The table is documented as VALID in ETRM 12.1.1 and 12.2.2, with a documented physical schema of 11 columns. Its primary key, MSC_QUESTIONS_TK_PK, is composed of QUESTION_ID and LANGUAGE. The heuristic Data Vault classification mined from the foreign-key structure is standalone, suggesting that in a Data Vault model this object would be treated as an independent hub-like entity keyed on QUESTION_ID and LANGUAGE, with no upstream link dependencies within the MSC schema. This classification is a modeling suggestion rather than a documented constraint.

Key Information Stored

The table records translated question content and its translation lifecycle metadata. The most significant columns are:

  • QUESTION_ID — Surrogate identifier of the question; part of the composite primary key MSC_QUESTIONS_TK_PK and of the unique index.
  • LANGUAGE — Language code for the translated row; the second component of the primary key and unique index, and the discriminator that makes this a translation table.
  • USER_QUESTION_NAME — The translated, user-facing name or label of the question as displayed in the Ask Oracle interface.
  • DESCRIPTION — The translated descriptive text associated with the question, providing fuller explanation than the short name.
  • SOURCE_LANG — The language from which the translation was derived; supports translation-source tracking.
  • TRANSLATED — Flag indicating whether the row has been translated or remains pending translation.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification.
  • LAST_UPDATED_BY — User who performed the most recent update.
  • CREATION_DATE — Timestamp when the row was created.
  • CREATED_BY — User who created the row.
  • LAST_UPDATE_LOGIN — Login session associated with the last update.

The surrogate primary key (QUESTION_ID, LANGUAGE) is functionally echoed by the unique index MSC_QUESTIONS_TL_U1 (QUESTION_ID, LANGUAGE), the documented business-key candidate. The audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN follow Oracle EBS WHO-column conventions.

Common Use Cases and Queries

Typical use cases include validating translation completeness, extracting display-ready question text for a given language, and auditing translation changes.

  • Translation completeness check: select QUESTION_ID, LANGUAGE, TRANSLATED from MSC_QUESTIONS_TL where TRANSLATED = 'N';
  • Language-specific lookup: select QUESTION_ID, USER_QUESTION_NAME, DESCRIPTION from MSC_QUESTIONS_TL where LANGUAGE = :p_lang;
  • Audit trends: group records by LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recent translation activity.

Because the table is language-keyed, joins to base or other MSC objects should always constrain LANGUAGE to avoid duplicate row expansion. Reports typically pivot on QUESTION_ID with LANGUAGE as the column dimension.

Related Objects

The documented relationship data classifies MSC_QUESTIONS_TL as standalone, meaning no foreign keys were mined pointing to or from it within the schema. The following objects are the most relevant logical companions:

  • MSC_QUESTIONS_B — The base (non-translated) table sharing QUESTION_ID; joined as B.QUESTION_ID = TL.QUESTION_ID.
  • MSC_QUESTIONS_TK_PK — The primary key constraint on (QUESTION_ID, LANGUAGE).
  • MSC_QUESTIONS_TL_U1 — Unique index on (QUESTION_ID, LANGUAGE), the business-key candidate.
  • Ask Oracle UI queries — Runtime components that read USER_QUESTION_NAME and DESCRIPTION filtered by LANGUAGE.
  • FND_LANGUAGES — Reference table for validating LANGUAGE codes.
  • FND_USER — Referenced indirectly via CREATED_BY and LAST_UPDATED_BY for audit reporting.