Search Results prp_tokens_b_uk1

Overview

The PRP_TOKENS_B table is a core data object within the Oracle E-Business Suite Proposals (PRP) module. It serves as the master repository for defining tokens, which are dynamic placeholders used within the Proposals application. These tokens enable the creation of flexible, template-driven documents by allowing users to insert codes that are later replaced with context-specific values during document generation. The table stores the fundamental, non-translatable attributes of each token, establishing a unique definition that is referenced throughout the proposal lifecycle. Its role is foundational to the personalization and automation features of the Proposals module in both EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to maintain a unique registry of token definitions. The most critical columns, as indicated by the documented constraints, are the primary and unique keys. The TOKEN_ID column serves as the system-generated, numeric primary key (PRP_TOKENS_B_PK) for uniquely identifying each token record. The TOKEN_CODE column holds the actual alphanumeric code or name used to reference the token within proposal templates and logic; its uniqueness is enforced by the PRP_TOKENS_B_UK1 constraint. While the provided metadata does not list all columns, typical supporting columns in such a base table would include creation date, created by, last update date, last updated by, and other control attributes to manage the token's lifecycle and usage.

Common Use Cases and Queries

The primary use case revolves around the administration and reporting of available tokens. System administrators or functional implementers query this table to audit defined tokens, troubleshoot missing token values, or validate token codes before embedding them in templates. A common query pattern involves joining with the corresponding translation table (PRP_TOKENS_TL) to retrieve token descriptions in a specific language. For example, a search for a specific token code, as indicated by the user's search term, would use a query like:

• SELECT b.TOKEN_CODE, tl.DESCRIPTION FROM PRP.PRP_TOKENS_B b, PRP.PRP_TOKENS_TL tl WHERE b.TOKEN_ID = tl.TOKEN_ID AND tl.LANGUAGE = USERENV('LANG') AND b.TOKEN_CODE LIKE '%&TOKEN_CODE_SEARCH_STRING%';

Reporting use cases include generating a master list of all tokens for documentation or verifying that all tokens referenced in active templates have a valid entry in this base table.

Related Objects

As per the documented foreign keys, PRP_TOKENS_B has direct relationships with two key translation tables. The PRP_TOKENS_TL table depends on it, storing the language-specific descriptions and names for each token defined in the base table, linked via the TOKEN_ID column. Similarly, the PRP_TOKEN_VALUES_TL table, which likely holds the actual substitutable values for tokens in different contexts, also references PRP_TOKENS_B.TOKEN_ID as a foreign key. This structure confirms that PRP_TOKENS_B is the central, non-translatable master, while related tables handle multilingual descriptions and instance-specific values.