Results for “cac_sr_templates_tl_u1”

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

Overview

JTF.CAC_SR_TEMPLATES_TL is a translation (TL) table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema. It stores the language-dependent, multilingual attributes of service request templates used by the Customer Care / TeleService (CAC) modules within the CRM foundation (JTF) layer. Each physical row represents one template rendered in one language; the language-independent attributes of the same template are held in the corresponding base table, JTF.CAC_SR_TEMPLATES_B. The "_TL" suffix is the standard Oracle Applications convention for such paired tables and signals that rows exist only for languages in which the template has been defined or translated.

Because the object carries translated descriptive text rather than transactional fact data or pure classification attributes, its heuristic Data Vault classification is satellite-leaning. In a Data Vault model it would most naturally be implemented as a satellite attached to the hub or link that represents the template entity itself, holding the name and description descriptive attributes keyed by template and language.

Key Information Stored

The table is owned by the JTF schema and resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10. Ten columns are documented. The most significant are:

• TEMPLATE_ID (NUMBER) — the surrogate identifier of the service request template. It is the foreign key to the base table JTF.CAC_SR_TEMPLATES_B and is the column through which translated and untranslated data are joined.
• LANGUAGE (VARCHAR2) — the language code for the translated row. Together with TEMPLATE_ID it forms the primary key CAC_SR_TEMPLATES_TL_PK.
• SOURCE_LANG (VARCHAR2) — the source language from which the translation was derived; used by the Oracle translation framework to track the origin of each translated string.
• TEMPLATE_NAME (VARCHAR2, length 2000) — the language-specific name of the template, the primary business-facing identifier presented to users.
• TEMPLATE_DESC (VARCHAR2, length 2000) — the language-specific description of the template.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle Applications audit columns recording who created and last modified each row and when.

Two unique indexes are documented: the composite CAC_SR_TEMPLATES_TL_U1 on (TEMPLATE_ID, LANGUAGE), which is the business-key candidate, and the primary key CAC_SR_TEMPLATES_TL_PK on (LANGUAGE, TEMPLATE_ID). Nonunique function-based indexes CAC_SR_TEMPLATES_TL_C1 and CAC_SR_TEMPLATES_TL_C2 on UPPER("TEMPLATE_NAME") and UPPER("TEMPLATE_DESC") respectively exist to support case-insensitive searching on the name and description.

Common Use Cases and Queries

Typical uses include multi-language template selection in the agent UI, translation completeness reporting, and joins in service request reporting. A common pattern joins the TL and B tables by TEMPLATE_ID and filters on LANGUAGE:

• SELECT t.TEMPLATE_NAME, t.TEMPLATE_DESC FROM JTF.CAC_SR_TEMPLATES_TL t WHERE t.TEMPLATE_ID = :id AND t.LANGUAGE = USERENV('LANG');
• SELECT b.TEMPLATE_ID, t.LANGUAGE, t.TEMPLATE_NAME FROM JTF.CAC_SR_TEMPLATES_B b, JTF.CAC_SR_TEMPLATES_TL t WHERE b.TEMPLATE_ID = t.TEMPLATE_ID;
• Case-insensitive lookup using the function-based index: SELECT TEMPLATE_ID FROM JTF.CAC_SR_TEMPLATES_TL WHERE UPPER(TEMPLATE_NAME) LIKE UPPER('%suit%');
• Translation gap analysis: SELECT TEMPLATE_ID, COUNT(*) FROM JTF.CAC_SR_TEMPLATES_TL GROUP BY TEMPLATE_ID;

Note the Oracle internal-use warning: the table should be accessed through supported Oracle Applications programs and APIs rather than direct DML.

Related Objects

The documented relationship data identifies the following key dependencies:

• JTF.CAC_SR_TEMPLATES_B — the base table holding language-independent template attributes; joined on TEMPLATE_ID via the foreign key from this table.
• CAC_SR_TEMPLATES_TL# — the internal dependent object that references this table within the JTF schema.
• CAC_SR_TEMPLATES_TL_PK / CAC_SR_TEMPLATES_TL_U1 — the primary key and unique business-key index used for constraint enforcement and lookups.
• CAC_SR_TEMPLATES_TL_C1 / CAC_SR_TEMPLATES_TL_C2 — function-based indexes supporting case-insensitive searches on TEMPLATE_NAME and TEMPLATE_DESC.

Service request (SR) and TeleService application logic that creates, lists, or translates templates relies on the B/TL pairing; any reporting object that surfaces template names or descriptions in a user's session language must join through these tables.