Search Results prp_token_values_tl_pk

Overview

The PRP_TOKEN_VALUES_TL table is a core data object within the Oracle E-Business Suite Proposals (PRP) module. It functions as a multilingual repository for the user-defined values associated with proposal tokens configured as a "List of Values" (LOV). In the context of Oracle Proposals, tokens are dynamic placeholders used to personalize and automate content within proposal templates and documents. This table specifically stores the translatable, discrete options that can be selected for a given token, ensuring that the proposal generation process supports multiple installed languages. Its role is critical for maintaining the integrity and linguistic accuracy of user-defined token data across global deployments of EBS.

Key Information Stored

The table's structure is designed to manage token values with full multilingual support. The primary columns include TOKEN_VALUE_ID, which serves as the unique system identifier for a specific value entry. The TOKEN_ID column is a foreign key that links each value to its parent token definition in the PRP_TOKENS_B table. The LANGUAGE column stores the language code (e.g., 'US', 'FR') for the translated value, while the TOKEN_VALUE column holds the actual display text of the list entry in that specific language. The table enforces data integrity through its primary key (PRP_TOKEN_VALUES_TL_PK) on TOKEN_VALUE_ID and LANGUAGE, and a unique key (PRP_TOKEN_VALUES_TL_UK1) on the combination of TOKEN_ID, LANGUAGE, and TOKEN_VALUE to prevent duplicate value entries per language.

Common Use Cases and Queries

A primary use case is the administration and reporting of list values for user-defined tokens. System administrators may query this table to audit or manage the available selections for a token across all languages. A common reporting need is to extract all translated values for a specific token to verify translation completeness. A typical SQL pattern for this involves joining to the token definition table:

• SELECT tlv.token_value, tlv.language, tk.token_name FROM prp_token_values_tl tlv, prp_tokens_b tk WHERE tlv.token_id = tk.token_id AND tk.token_name = '&TOKEN_NAME';

Another practical scenario is within the proposal generation engine itself, where the application queries this table to populate LOV prompts for users filling out token data, filtering by the current session's language and the relevant TOKEN_ID.

Related Objects

PRP_TOKEN_VALUES_TL has a direct and essential relationship with the base token definition table. As documented in the provided metadata:

• PRP_TOKENS_B: This is the primary foreign key relationship. The TOKEN_ID column in PRP_TOKEN_VALUES_TL references the TOKEN_ID in PRP_TOKENS_B. This links each list value entry to its corresponding master token definition. Any query for token values typically requires a join on this column to retrieve the token's name or other defining attributes.

While not listed in the provided excerpt, this table is also logically related to the transactional tables in the Proposals module that store the user's selected value for a token during proposal creation, which would reference the TOKEN_VALUE_ID.