Search Results fnd_conc_pp_templates_tl




Overview
Explore in AI Chat

Overview

FND_CONC_PP_TEMPLATES_TL is the translation table for FND_CONC_PP_TEMPLATES, the base table that stores concurrent program parameter templates in Oracle E-Business Suite. Parameter templates allow users to define and save named combinations of concurrent program parameters so they can be reused across submissions without re-entering values. Because templates carry user-facing text such as the template name and description, Oracle stores that text in a separate translation (TL) table to support multiple installed languages. The base table holds language-independent attributes, while FND_CONC_PP_TEMPLATES_TL holds the language-specific strings keyed by TEMPLATE_ID and LANGUAGE.

The table resides in the APPLSYS schema and belongs to the FND - Application Object Library product. It is present and valid in both EBS 12.1.1 and 12.2.2. ETRM documents 10 columns and the primary key FND_CONC_PP_TEMPLATES_TL_PK on TEMPLATE_ID. The table is classified heuristically as a link under Data Vault modeling: it sits between the template entity and the language, carrying descriptive, language-dependent attributes and audit foreign keys. This is a modeling suggestion rather than a physical design constraint.

Key Information Stored

The table stores the translated descriptive attributes of a concurrent program parameter template, one row per template per installed language.

  • TEMPLATE_ID — Surrogate primary key referencing the language-independent template in FND_CONC_PP_TEMPLATES. It is the first component of the primary key and the join key to the base table.
  • LANGUAGE — The language code of the translated text. Together with TEMPLATE_ID this forms the natural uniqueness of a translated row.
  • SOURCE_LANG — The language in which the text was originally authored; used by the translation framework to track the origin language.
  • USER_TEMPLATE_NAME — The translated, user-visible name of the template shown when users select or maintain templates.
  • DESCRIPTION — The translated descriptive text explaining the template's purpose and parameter contents.
  • LAST_UPDATE_DATE, CREATION_DATE — Standard audit timestamps recording creation and last modification.
  • CREATED_BY, LAST_UPDATED_BY — Foreign keys to FND_USER identifying the user who created or last updated the row.
  • LAST_UPDATE_LOGIN — Foreign key to FND_LOGINS capturing the login session associated with the last update.

The primary key is FND_CONC_PP_TEMPLATES_TL_PK on TEMPLATE_ID. Because translation rows are further qualified by LANGUAGE, the practical business key is the combination of TEMPLATE_ID and LANGUAGE rather than TEMPLATE_ID alone.

Common Use Cases and Queries

The most frequent use is retrieving the display name and description of a template for a specific language, typically joined to the base table:

  • Listing all templates with translated names for the current session language.
  • Reporting on templates that are missing translations in a particular language.
  • Locating templates by name when the template name is language-dependent.

A representative query joins the translation table to the base table on TEMPLATE_ID and filters by LANGUAGE:

SELECT b.TEMPLATE_ID, t.USER_TEMPLATE_NAME, t.DESCRIPTION
FROM FND_CONC_PP_TEMPLATES b, FND_CONC_PP_TEMPLATES_TL t
WHERE b.TEMPLATE_ID = t.TEMPLATE_ID
AND t.LANGUAGE = USERENV('LANG');

Reconciliation queries compare the base table against the translation table to identify templates lacking a row for a given language, and audit queries join CREATED_BY or LAST_UPDATED_BY to FND_USER to attribute template changes.

Related Objects

The principal related objects and their join columns are:

  • FND_CONC_PP_TEMPLATES — The base table; join on TEMPLATE_ID.
  • FND_LANGUAGES — Referenced twice via LANGUAGE and SOURCE_LANG for language validation.
  • FND_USER — Referenced via CREATED_BY and LAST_UPDATED_BY for user attribution.
  • FND_LOGINS — Referenced via LAST_UPDATE_LOGIN for session tracking.
  • FND_CONC_PP_TEMPLATE_VL — The translated view typically overlaying base and translation tables.

These relationships make FND_CONC_PP_TEMPLATES_TL central to any query that surfaces user-facing template text in a multilingual EBS environment.