Results for “token_prompt”

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

Overview

PRP_TOKENS_TL is the translation table for proposal tokens within the Oracle EBS Proposals (PRP) module. A "token" in the Proposals application is a named substitution variable — a placeholder embedded in proposal templates and boilerplate text that is resolved at merge or generation time into customer-specific, opportunity-specific, or system-derived values. Because tokens may be presented to users in multiple languages, the Proposals module stores language-independent token attributes in a base table and language-dependent descriptive text in this companion translation table.

PRP_TOKENS_TL holds only the translatable text attributes of a token, keyed by token identifier and language. The base definition — including non-translated control attributes — resides in PRP_TOKENS_B, to which this table is joined one-to-many by language. From a Data Vault modeling perspective, the FK structure (TOKEN_ID referencing PRP_TOKENS_B, with LANGUAGE as part of the primary key) suggests classifying PRP_TOKENS_TL as satellite-leaning: it carries descriptive, language-qualified context attached to a hub-like base entity rather than representing an independent business entity or an associative relationship between two entities.

Key Information Stored

The table is defined in the PRP schema and contains twelve documented columns. The most significant are:

• TOKEN_ID — Surrogate identifier of the token. Together with LANGUAGE it forms the primary key PRP_TOKENS_TL_PK, and it is the foreign key column referencing PRP_TOKENS_B.TOKEN_ID.
• LANGUAGE — The language code for the translated row, forming the second component of the primary key and of the unique index.
• SOURCE_LANG — The source language from which the translated text was derived, supporting multilingual maintenance and translation workflow.
• TOKEN_NAME — The translated display name of the token.
• TOKEN_PROMPT — The translated prompt text presented to users when the token is selected or configured.
• TOKEN_DESC — The translated description of the token's purpose and expected content.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each translation row and when.
• ZD_EDITION_NAME — The edition name used by the EBS online patching (Editioning) framework; it participates in the unique index PRP_TOKENS_TL_U1 alongside TOKEN_ID and LANGUAGE.

The business-key candidate is the unique index PRP_TOKENS_TL_U1 (TOKEN_ID, LANGUAGE, ZD_EDITION_NAME), which distinguishes translations by token, language, and edition. Note that the primary key omits ZD_EDITION_NAME while the unique index includes it — a pattern typical of tables enabled for edition-based redefinition.

Common Use Cases and Queries

Typical usage centers on retrieving language-appropriate token metadata for the Proposals user interface and for merge-processing logic that must resolve token prompts and names. A common reporting pattern joins the translation table to the base table:

• List all translations for a given token: SELECT language, token_name, token_prompt FROM prp_tokens_tl WHERE token_id = :token_id;
• Retrieve a specific language row: SELECT token_name, token_prompt, token_desc FROM prp_tokens_tl WHERE token_id = :token_id AND language = USERENV('LANG');
• Find untranslated or missing languages by outer-joining PRP_TOKENS_B to PRP_TOKENS_TL and filtering for NULL translations.
• Audit translation currency using LAST_UPDATED_BY and LAST_UPDATE_DATE, for example to identify translations not refreshed after a base-token change.

Because the table is purely descriptive, it is read frequently by form and concurrent-program logic but written only through the Proposals setup/translation maintenance paths.

Related Objects

• PRP_TOKENS_B — The base table for token definitions; joined on TOKEN_ID (the documented foreign key). All language-independent attributes are held here.
• PRP_TOKENS_TL_PK / PRP_TOKENS_TL_U1 — The primary key and unique index supporting direct lookups by token and language.
• PRP_TOKENS_VL / _V — Any translation-enabled view following the EBS TL/VL convention, which joins PRP_TOKENS_B and PRP_TOKENS_TL to present the current-language token definition.
• PRP_* template and boilerplate tables — Objects that store proposal template text containing token placeholders and depend on token metadata at merge time.
• FND_LANGUAGES — Reference table validating the LANGUAGE and SOURCE_LANG values held in this table.

JOIN relationships should always be expressed against TOKEN_ID; there is no documented dependency on any other foreign table.