Results for “template_id”

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

Overview

CS_TP_TEMPLATES_TL is the translation (TL) table for CS Template Driven Service Request templates in the Oracle E-Business Suite CS (Service) module. It stores the language-specific, user-facing text attributes of a template driven SR template — specifically the template name and description — alongside the base-table linkage that anchors each translated row to its language-independent definition in CS_TP_TEMPLATES_B. The "_TL" suffix signals that this object participates in Oracle's standard multi-language translation architecture, where one logical entity is represented by a base row (in the "_B" table) and one or more translated rows (in the "_TL" table), keyed by language.

In Oracle EBS 12.1.1 and 12.2.2, template driven service requests allow service organizations to predefine structured, reusable SR templates that drive field prompts, data collection, and workflow behavior when agents create service requests. CS_TP_TEMPLATES_TL supplies the localizable presentation metadata for those templates. It is owned by the CS schema and is documented as VALID in the ETRM repository.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This is a modeling suggestion only: CS_TP_TEMPLATES_TL behaves like a satellite attached to the business key carried by CS_TP_TEMPLATES_B, and it does not itself act as a hub or link. The classification is a design heuristic, not a physical constraint.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• TEMPLATE_ID — surrogate identifier linking the translated row to its base definition; part of the primary key and a foreign key to CS_TP_TEMPLATES_B.
• LANGUAGE — the language code for the translated text; the second component of the primary key.
• SOURCE_LANG — identifies the source language from which the translation derives, used by the translation maintenance framework.
• NAME — the language-specific template name displayed to users.
• DESCRIPTION — the language-specific descriptive text for the template.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS controlling row-level access through Oracle's security group mechanism.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified each translated row, when, and through which login.

The primary key is CS_TP_T_TL_PK on (LANGUAGE, TEMPLATE_ID). A unique index, CS_TP_TEMPLATE_TL_U1, is defined on (TEMPLATE_ID, LANGUAGE), making that pair the documented business-key candidate for the translated entity. The distinction matters for query planning: the primary key leads with LANGUAGE, whereas the unique index leads with TEMPLATE_ID, so lookups by template are better served by the unique index ordering.

Common Use Cases and Queries

Typical uses center on retrieving localized template names and descriptions, validating translation coverage, and joining translated text to base template configuration for reporting.

• Retrieve the localized name and description for a specific template and language:

  SELECT name, description
  FROM   cs.cs_tp_templates_tl
  WHERE  template_id = :template_id
  AND    language    = USERENV('LANG');

• List all translations available for a given template:

  SELECT language, source_lang, name
  FROM   cs.cs_tp_templates_tl
  WHERE  template_id = :template_id;

• Identify templates with missing translations by comparing against the base table:

  SELECT b.template_id
  FROM   cs.cs_tp_templates_b b
  WHERE  NOT EXISTS (SELECT 1 FROM cs.cs_tp_templates_tl t
                     WHERE t.template_id = b.template_id
                     AND   t.language    = 'US');

• Reporting joins to the base table to combine language-independent attributes with translated text, constrained by security group.

Because translations are maintained through Oracle's translation framework, direct DML should be avoided; changes should flow through the supported template maintenance UI or concurrent translation programs.

Related Objects

• CS_TP_TEMPLATES_B — the base table; joined on TEMPLATE_ID. Every translated row must resolve to a base template row.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID to enforce row-level security group access.
• CS_TP_TEMPLATES_TL primary key CS_TP_T_TL_PK and unique index CS_TP_TEMPLATE_TL_U1 — the constraints that govern row uniqueness and drive query access paths.
• Other CS template driven SR configuration tables in the CS schema that share TEMPLATE_ID as their key, forming the broader template definition model.
• Oracle EBS translation framework objects (the standard "_TL" maintenance infrastructure) that populate and manage rows in this table.