Results for “cac_sr_templates_tl”

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

Overview

The table CAC_SR_TEMPLATES_TL is a translation (multi-language) child table owned by the JTF schema within the CRM Foundation module of Oracle E-Business Suite. It stores the translated text attributes of a Schedule Template — specifically the template name and description — for each installed language. The base (untranslated) definition of a Schedule Template is held in the sibling table CAC_SR_TEMPLATES_B, and this _TL table carries the language-dependent content for that same logical entity. The _TL suffix is the standard Oracle Applications convention for tables holding translated (language-specific) columns, and the pairing with a _B base table reflects the standard MLS (Multi-Lingual Support) schema pattern.

From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This is a reasonable heuristic: it captures descriptive, language-variant attributes that hang off the parent template entity, and it is keyed by the natural composite of the owning entity identifier plus language. It is not a hub in its own right, and it is not a pure link, since it carries real descriptive payload (TEMPLATE_NAME, TEMPLATE_DESC). It behaves like a satellite attached to the base template.

Key Information Stored

Ten columns are documented for this table in the ETRM 12.2.2 schema. The most important are:

• TEMPLATE_ID — the foreign key to CAC_SR_TEMPLATES_B, identifying which Schedule Template this translation row belongs to.
• LANGUAGE — the language code for the translated row (for example, US for American English).
• SOURCE_LANG — the language of the source text; standard in MLS tables to identify the originating language when a translation is seeded or copied.
• TEMPLATE_NAME — the translated display name of the Schedule Template.
• TEMPLATE_DESC — the translated description of the Schedule Template.
• CREATED_BY, CREATION_DATE — standard WHO-column audit fields recording the creator and creation timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the last modification.

The surrogate identity of the row is defined by the composite primary key CAC_SR_TEMPLATES_TL_PK, which spans (LANGUAGE, TEMPLATE_ID). A unique index, CAC_SR_TEMPLATES_TL_U1, is documented on (TEMPLATE_ID, LANGUAGE). Although the two key definitions contain the same pair of columns in different order, this represents the standard pattern in which the primary key and the unique business-key index enforce the same cardinality constraint: exactly one translation per template per language. Both columns are therefore the business-key candidates identifying a translation row.

Common Use Cases and Queries

The principal use case is retrieving the correct localized name and description of a Schedule Template for display in the CRM Foundation application layer. Application queries typically join the translation table to the base table and filter on the session language:

SELECT b.template_id, t.template_name, t.template_desc
FROM   jtf.cac_sr_templates_b b,
       jtf.cac_sr_templates_tl t
WHERE  b.template_id = t.template_id
AND    t.language = USERENV('LANG');

Reporting and administration scenarios include: auditing which languages a given template has been translated into; identifying templates that exist in the base table but lack a translation row for a required language; and comparing the SOURCE_LANG against the populated LANGUAGE to verify translation completeness. A completeness query might count translations per template:

SELECT template_id, COUNT(*) translated_languages
FROM   jtf.cac_sr_templates_tl
GROUP  BY template_id
HAVING COUNT(*) < (SELECT COUNT(*) FROM fnd_languages);

Because the table participates in the MLS framework, DML against it should be performed through the supported base/translation APIs rather than direct SQL, to keep the _B and _TL rows consistent.

Related Objects

The following objects are most significant in relation to CAC_SR_TEMPLATES_TL:

• CAC_SR_TEMPLATES_B — the base table holding language-independent template definitions; joined on CAC_SR_TEMPLATES_TL.TEMPLATE_ID = CAC_SR_TEMPLATES_B.TEMPLATE_ID. This is the documented foreign key relationship and the primary dependency.
• FND_LANGUAGES — the languages reference table, used to interpret LANGUAGE and SOURCE_LANG.
• FND_TERRITORIES and related FND_* MLS views — standard CRM Foundation utilities used for language-aware queries.
• Schedule/SR template assignment and routing tables in the JTF/CRM Foundation module that consume the template name and description through joins back to the base table.
• Application APIs and concurrent programs in the CRM Foundation module that maintain Schedule Template definitions and their translations.