Results for “token_value”

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

Overview

PRP_TOKEN_VALUES_TL is a translation (TL) table in the Oracle EBS Proposals (PRP) module. It stores the localized display values for user-defined tokens whose type is "List of Values" (LOV). Each row represents a single allowed value for a given token, in a given installed language, allowing the same token to present a different set of selectable values depending on the session language of the user.

In the ETRM data model, tokens act as configurable placeholders that can be embedded in proposal templates and documents and later substituted with runtime content. When a token is defined as an LOV token, the admissible values are not free text; they are constrained to the set of rows maintained in this table. The translation layer is therefore what makes the proposal generation output language-aware.

From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning. The table hangs off a business hub (the token definition) via a foreign key and carries descriptive, language-qualified attributes that change over time, which is the classic profile of a satellite rather than a hub or link. This classification is a modeling suggestion only; the physical implementation remains a conventional EBS table with standard WHO audit columns.

Key Information Stored

The documented physical schema exposes eleven columns. The most significant are:

• TOKEN_VALUE_ID – Surrogate identifier for the token value record. Part of the composite primary key PRP_TOKEN_VALUES_TL_PK (TOKEN_VALUE_ID, LANGUAGE).
• TOKEN_ID – Foreign key to PRP_TOKENS_B, identifying the parent token definition. Together with LANGUAGE and TOKEN_VALUE this forms the unique business key candidate PRP_TOKEN_VALUES_TL_UK1.
• TOKEN_VALUE – The actual list-of-values entry displayed to the user. This is the translatable payload of the row.
• LANGUAGE – The installed language code for which the TOKEN_VALUE is valid. Part of both the primary key and the unique business key.
• SOURCE_LANG – The language of the source row from which a translated row was derived; used by the translation framework to distinguish original entries from localized copies.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE – Standard WHO audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns recording the most recent modification and the login that performed it.

The distinction between the surrogate key and the business key matters in practice: the primary key guarantees row uniqueness, while PRP_TOKEN_VALUES_TL_UK1 (TOKEN_ID, LANGUAGE, TOKEN_VALUE) enforces the functional rule that a token may not present the same value twice in the same language.

Common Use Cases and Queries

Typical scenarios include validating LOV token content, producing translation status reports, and diagnosing proposal generation errors caused by missing values. A representative query retrieves all values for a token in a target language:

SELECT t.TOKEN_VALUE_ID, t.TOKEN_VALUE, t.LANGUAGE, t.SOURCE_LANG
FROM PRP.PRP_TOKEN_VALUES_TL t
WHERE t.TOKEN_ID = :token_id
AND t.LANGUAGE = USERENV('LANG');

A translation completeness check compares the base-language row set with each installed language to surface untranslated values:

SELECT b.TOKEN_ID, b.TOKEN_VALUE, b.LANGUAGE base_lang, t.LANGUAGE trans_lang
FROM PRP.PRP_TOKEN_VALUES_TL b, PRP.PRP_TOKEN_VALUES_TL t
WHERE b.TOKEN_ID = t.TOKEN_ID
AND b.SOURCE_LANG = b.LANGUAGE
AND t.LANGUAGE <> b.LANGUAGE
AND b.TOKEN_VALUE = t.TOKEN_VALUE;

Reporting use cases include auditing who last changed a token value (LAST_UPDATED_BY, LAST_UPDATE_DATE), reconciling tokens whose LOV sets differ across languages, and extracting value lists into downstream document or proposal template tooling.

Related Objects

The most significant relationships are:

• PRP_TOKENS_B – Parent token definition; joined via PRP_TOKEN_VALUES_TL.TOKEN_ID = PRP_TOKENS_B.TOKEN_ID. This is the only documented foreign key.
• PRP_TOKENS_TL – Translation table for token names and descriptions; joins on TOKEN_ID and LANGUAGE to resolve localized token labels alongside localized values.
• PRP_TOKEN_VALUES_B – Base (non-translated) token value definitions, if present in the module, providing the language-independent anchor for this translation table.
• PRP_TOKEN_VALUES_TL_PK / PRP_TOKEN_VALUES_TL_U1 – The primary key and unique index objects that enforce integrity on TOKEN_VALUE_ID, LANGUAGE, and TOKEN_ID.
• Standard EBS WHO columns – CREATED_BY, LAST_UPDATED_BY and their date companions, surfaced through FND_USER joins for audit reporting.

Because this object is translation-scoped, it is typically accessed indirectly through PRP token setup forms and proposal generation APIs rather than by direct application SQL, but direct queries remain valid for diagnostic and reporting purposes.