Results for “cs_tp_questions_tl”

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

Overview

CS_TP_QUESTIONS_TL is the translation table for Template Driven Service Request questions within the Oracle E-Business Suite Service (CS) product family. It stores the language-specific, user-facing text associated with questions that appear on Service Request (SR) templates when the Template Driven SR feature is configured. In Oracle EBS 12.1.1 and 12.2.2 the object resides in the CS schema and is reported with VALID status in the ETRM repository.

Oracle's multilanguage ("_TL") convention separates language-independent attributes from translated attributes. CS_TP_QUESTIONS_TL holds the translatable content, while the companion table CS_TP_QUESTIONS_B holds the base, language-neutral definition. The two are linked by QUESTION_ID.

From a Data Vault modelling perspective, the mined metadata classifies this object as satellite-leaning. The heuristic reflects its structure: a foreign-key dependency on a base entity (CS_TP_QUESTIONS_B) plus descriptive, context-qualified attributes (NAME, TEXT, DESCRIPTION) keyed by a composite of a parent surrogate and LANGUAGE. Readers should treat the classification as a modelling suggestion rather than a documented Oracle architectural claim; in practice the table behaves as a language-dependent descriptive satellite attached to a question hub/link represented by the base table.

Key Information Stored

The documented physical schema for 12.2.2 defines twelve columns. The most significant are:

• QUESTION_ID — Surrogate identifier of the parent question. It is also the foreign key to CS_TP_QUESTIONS_B and part of the primary key.
• LANGUAGE — Language code of the translation row (for example, US for American English). Part of the primary key.
• SOURCE_LANG — Language code of the source row from which the translation was derived; used by the translation framework to trace lineage and the "translated from" relationship.
• NAME — Translated short name or label of the question as presented to the agent or end user.
• TEXT — Translated question text, i.e. the actual prompt displayed on the SR template.
• DESCRIPTION — Translated descriptive or help text associated with the question.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-organization/security-group data isolation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when.

The primary key is CS_TP_Q_TL_PK, defined on (LANGUAGE, QUESTION_ID). A unique index, CS_TP_QUESTIONS_TL_U1, is documented on (QUESTION_ID, LANGUAGE) — a business-key candidate enforcing one translation per question per language. Note that the PK and unique index express the same logical constraint with different column ordering; the unique index additionally serves as an efficient access path for lookups driven by QUESTION_ID.

Common Use Cases and Queries

Typical uses include verifying which languages a template question is translated into, correcting or extending translations, and reporting on translation coverage before an upgrade or a new language rollout.

• Retrieve all translations for a question:

  SELECT question_id, language, source_lang, name, text
FROM cs.cs_tp_questions_tl
WHERE question_id = :question_id;

• List questions missing a translation into a target language:

  SELECT b.question_id
FROM cs.cs_tp_questions_b b
WHERE NOT EXISTS (SELECT 1 FROM cs.cs_tp_questions_tl t
  WHERE t.question_id = b.question_id AND t.language = 'US');

• Join base and translated rows for reporting or a template definition extract:

  SELECT b.question_id, t.language, t.name, t.text
FROM cs.cs_tp_questions_b b, cs.cs_tp_questions_tl t
WHERE b.question_id = t.question_id;

• Audit recently changed translations using LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• Security-group filtered extracts via SECURITY_GROUP_ID joined to FND_SECURITY_GROUPS.

Because these rows drive what an agent literally sees on a template, data changes should follow the standard EBS translation maintenance path (translations form or the multilinguality utility) rather than direct DML, to keep SOURCE_LANG and the base/translation relationship consistent.

Related Objects

• CS_TP_QUESTIONS_B — Base (language-independent) question table; joined on QUESTION_ID and referenced by the documented foreign key. Together the two form the complete question definition.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security-group isolation.
• CS_TP_QUESTIONS_B / CS_TP_QUESTIONS_TL template assignment tables — Downstream template and section membership tables consume QUESTION_ID to place translated questions on SR templates.
• CS_TP_Q_TL_PK (index) — Primary-key constraint/index on (LANGUAGE, QUESTION_ID).
• CS_TP_QUESTIONS_TL_U1 (index) — Unique index on (QUESTION_ID, LANGUAGE), the business-key candidate.
• FND_LANGUAGES — Logical lookup providing valid values and descriptions for LANGUAGE and SOURCE_LANG.

The object is metadata rather than transactional data; it is therefore read frequently during template rendering and language maintenance but rarely the target of high-volume DML.