Results for “prp_templates_tl”

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

Overview

PRP_TEMPLATES_TL is the translation (language) table for proposal templates within the Oracle EBS Proposals (PRP) module. It stores the language-dependent, user-facing descriptive attributes of a template — its name and description — so that a single template definition can be presented in multiple installed languages. The base, language-independent definition is held in the companion table PRP_TEMPLATES_B, to which this table is tied by a foreign key on TEMPLATE_ID.

In Data Vault modeling terms, the mined relationship structure classifies this object as satellite-leaning: it hangs off the PRP_TEMPLATES_B hub/link structure and carries descriptive, attribute-bearing payload rather than acting as a hub or link in its own right. This classification is a heuristic modeling suggestion derived from the foreign-key topology; it is not an Oracle-authored designation.

The table resides in the PRP schema and is documented as VALID in the ETRM metadata for 12.1.1 and 12.2.2. It comprises 10 columns in the documented physical schema.

Key Information Stored

The primary key, PRP_TEMPLATES_TL_PK, is composite and consists of TEMPLATE_ID and LANGUAGE. The unique index PRP_TEMPLATES_TL_U1 also covers (TEMPLATE_ID, LANGUAGE), confirming that TEMPLATE_ID plus LANGUAGE forms the business-key candidate governing uniqueness. TEMPLATE_ID functions as the surrogate foreign key into PRP_TEMPLATES_B, while LANGUAGE identifies the specific translation row.

• TEMPLATE_ID — Foreign key to PRP_TEMPLATES_B; identifies the template being translated.
• LANGUAGE — The language code of this translation row; part of the composite primary key.
• SOURCE_LANG — The source language from which the translation derives, supporting the standard EBS language-translation pattern.
• TEMPLATE_NAME — The translated, displayable name of the template.
• TEMPLATE_DESC — The translated description text for the template.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified each translation row and when.

Common Use Cases and Queries

Typical usage centers on resolving a template's display name and description for the session or reporting language. A common query joins the translation table back to the base table, filtering on LANGUAGE, as follows:

SELECT b.template_id,
       t.template_name,
       t.template_desc
FROM   prp.prp_templates_b  b,
       prp.prp_templates_tl t
WHERE  b.template_id = t.template_id
AND    t.language    = USERENV('LANG');

Reporting use cases include listing all templates with their translated names, auditing which templates have translations in which languages, and identifying templates that lack a translation for a required language (by LEFT JOIN from the base table). Reconciliation queries comparing SOURCE_LANG to LANGUAGE help track translation completeness and staleness.

Related Objects

The most significant related object is PRP_TEMPLATES_B, the base table holding the language-independent template definition and the parent of the foreign key PRP_TEMPLATES_TL.TEMPLATE_ID → PRP_TEMPLATES_B.TEMPLATE_ID. Reporting and lookup logic typically join these two objects on TEMPLATE_ID, filtered by LANGUAGE. Other Proposals module objects that reference templates — such as proposal and template-assignment entities within the PRP schema — commonly reach the translated name through PRP_TEMPLATES_B rather than directly, so PRP_TEMPLATES_B serves as the principal and most frequent join partner in practice.