Search Results cs_tp_templates_vl




Overview
Explore in AI Chat

Overview

CS_TP_TEMPLATES_VL is a documented view in the APPS schema belonging to the Service (CS) product family in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It functions as a translation-level (VL, or "view language") reporting construct that presents service template definitions together with their language-specific descriptive text. The view exposes the operational attributes held in the base table alongside the translatable name and description columns, resolving the appropriate language row at query time through the USERENV('LANG') session context. Its status is VALID in the ETRM metadata, confirming it is a supported, active database object.

Because the view joins the transactional base table to its translation table, it serves as the standard access point for concurrent programs, Oracle Forms blocks, OAF pages, and custom reporting or integration code that need complete template information without writing the translation join manually. In integration scenarios, the view is typically queried by interfaces extracting template configuration for downstream provisioning or questionnaire systems.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

  • CS_TP_TEMPLATES_B — the base table holding non-translatable, operational attributes of each service template, including the primary key TEMPLATE_ID, activation dates, the default template flag, WHO audit columns, and the DFF ATTRIBUTE1 through ATTRIBUTE15 columns.
  • CS_TP_TEMPLATES_TL — the translation table holding the language-dependent NAME and DESCRIPTION columns, keyed by TEMPLATE_ID and LANGUAGE.

The view text joins the two on B.TEMPLATE_ID = T.TEMPLATE_ID and filters T.LANGUAGE = USERENV('LANG'), so only the translation row matching the caller's session language is returned. This is the characteristic pattern of an Oracle "VL" view, and it means the view behaves as a single-language presentation layer over a multi-language data model.

Key Columns

The view exposes the union of the base and translation columns. Notable columns include:

Common Use Cases and Queries

Typical usages include validation reports listing active templates, integration extracts feeding external questionnaire engines, and LOV queries in custom forms requiring the translated template name. Because language resolution depends on USERENV('LANG'), results vary by the session language of the connected user or concurrent program.

A representative query retrieving currently active templates is:

  • SELECT template_id, name, description, default_flag, start_date_active, end_date_active FROM cs_tp_templates_vl WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY name;

To locate the default template:

  • SELECT template_id, name FROM cs_tp_templates_vl WHERE default_flag = 'Y';

When extracting DFF data alongside the translated text, additional ATTRIBUTE columns may be selected. Note that the LANGUAGE filter is applied internally; callers requiring multiple languages simultaneously must query CS_TP_TEMPLATES_TL directly rather than relying on this view.