Search Results cs_tp_template_questions




Overview
Explore in AI Chat

Overview

CS_TP_TEMPLATE_QUESTIONS is a Service (CS) module table that functions as the linking table between question templates and the individual questions they contain. Its stated purpose is "template and question linking table." Within Oracle E-Business Suite Release 12.1.1 and 12.2.2, this object supports the Telephony/Scripting and template-driven question-answer frameworks used by service agents and self-service flows, where a named template must present an ordered set of questions to the end user. The table stores the association of a template to a question plus the display sequence of that question inside the template.

From a Data Vault modeling perspective, the mined heuristic classifies this object as standalone. Although it carries a classic composite key structure typical of a link table, the absence of documented foreign keys beyond SECURITY_GROUP_ID means it should be treated as an independent entity rather than a resolved link. The business-key candidate is the unique index CS_TP_TEMPLATE_QUESTIONS_U1 on (TEMPLATE_ID, QUESTION_ID).

Key Information Stored

The table contains 25 documented columns, of which a small subset carries the substantive business meaning:

  • TEMPLATE_ID — identifies the parent question template; part of the composite unique business key.
  • QUESTION_ID — identifies the question linked to that template; the second component of the composite business key.
  • SEQUENCE_NUMBER — governs the order in which questions are presented within the template, which is essential to conditional or scripted questionnaire flows.
  • SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, providing the multi-tenant / data-security partitioning dimension used across many CS tables.
  • Standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — which record insert and update provenance for each template-question link.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, available for customer-specific extensions without schema modification.

No single-column surrogate primary key is documented; the enforced uniqueness derives from the composite index CS_TP_TEMPLATE_QUESTIONS_U1, which prevents the same question from being attached twice to the same template.

Common Use Cases and Queries

Typical usage centers on resolving the ordered question list for a given template, reporting on question reuse across templates, and validating template completeness. A representative query returns the questions for one template in display order:

  • SELECT question_id, sequence_number FROM cs.cs_tp_template_questions WHERE template_id = :p_template_id ORDER BY sequence_number;
  • Reuse analysis — SELECT question_id, COUNT(DISTINCT template_id) FROM cs.cs_tp_template_questions GROUP BY question_id HAVING COUNT(DISTINCT template_id) > 1; identifies questions shared across multiple templates.
  • Security-scoped extracts joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID to restrict results to the operating unit or responsibility in context.
  • Gap detection — outer-joining to the template and question master tables to find templates with zero linked questions or orphaned links.

Because the table is primarily a relationship carrier, most production reporting joins outward to the template and question definitions rather than reading this table alone.

Related Objects

The documented foreign key relationship and usage patterns point to the following significant related objects:

  • FND_SECURITY_GROUPS — referenced by CS_TP_TEMPLATE_QUESTIONS.SECURITY_GROUP_ID; enforces data-security partitioning.
  • The CS question template master table (keyed by TEMPLATE_ID) — the parent defining each template.
  • The CS question definition table (keyed by QUESTION_ID) — supplies the question text, type, and answer domain.
  • Related CS template/question child tables that consume SEQUENCE_NUMBER ordering, such as answer-option and template-version tables.
  • CS Service APIs and concurrent programs that create and maintain telephony/scripting templates.

All facts above derive from the ETRM 12.2.2 metadata; the composite uniqueness on (TEMPLATE_ID, QUESTION_ID) and the FND_SECURITY_GROUPS reference are documented, while joins to template and question masters are inferred from the standard CS data model.