Results for “prp_proposal_tokens”

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

Overview

PRP_PROPOSAL_TOKENS is a transactional table in the PRP (Proposals) product module of Oracle E-Business Suite, resident in the PRP schema. It stores the resolved values of user-defined tokens associated with a proposal. According to the Oracle documentation, the table is deliberately scoped: it holds only "User Defined" tokens whose type is either "Text" or "List of Values." System tokens and tokens of other types are not persisted here, since their values are derived from source data at render time rather than captured as user input.

In Oracle EBS 12.1.1 and 12.2.2, the Proposals module supports the authoring of structured proposal documents and templates. Tokens act as inline placeholders within those documents; PRP_PROPOSAL_TOKENS records the concrete value a user has assigned to a given placeholder on a given proposal, forming the bridge between a reusable template definition and a specific proposal instance. Under the heuristic Data Vault classification mined from its foreign-key structure, this table is best modeled as a link: it resolves a many-to-many style association between a proposal and a token definition, carrying descriptive attributes (the value itself) on the relationship. Implementers building a dimensional or vault layer should treat PROPOSAL_ID and TOKEN_ID as the participating business keys and note that the table additionally carries a foreign key to IBC_CITEM_VERSIONS_B, which ties the token value to a specific content item version.

Key Information Stored

The physical schema documented for ETRM 12.2.2 comprises twelve columns. The most significant are:

• PROPOSAL_TOKEN_ID — the surrogate primary key, enforced by PRP_PROPOSAL_TOKENS_PK and also backed by unique index PRP_PROPOSAL_TOKENS_U1. This is the row identity used by downstream references.
• PROPOSAL_ID — foreign key to PRP_PROPOSALS, identifying the parent proposal to which the token value belongs.
• TOKEN_ID — identifies the token definition being valued. Together with PROPOSAL_ID it forms the composite business key enforced by unique index PRP_PROPOSAL_TOKENS_U2, guaranteeing that a given token is stored at most once per proposal.
• TOKEN_VALUE — the user-entered value for Text tokens, or the selected display value for List of Values tokens.
• TOKEN_VALUE_ID — the stored identifier associated with the selected value, typically populated for List of Values tokens where an internal code rather than literal text is retained.
• CITEM_VERSION_ID — foreign key to IBC_CITEM_VERSIONS_B, linking the token value to the specific version of the content item in which it was captured.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified the row, when, and through which login session.

The distinction between the surrogate key (PROPOSAL_TOKEN_ID) and the business key (PROPOSAL_ID plus TOKEN_ID) is important for integration: external interfaces should key on the composite pair, while internal joins may safely use the surrogate.

Common Use Cases and Queries

Principal uses include rendering a proposal with its captured user-defined values, auditing which values were supplied for a proposal, and reporting on token usage across a proposal library. A typical retrieval joins the table to its parent proposal:

• Retrieve all tokens for a proposal: SELECT proposal_token_id, token_id, token_value, token_value_id FROM prp.prp_proposal_tokens WHERE proposal_id = :p_proposal_id;
• Resolve a single value using the composite business key: SELECT token_value FROM prp.prp_proposal_tokens WHERE proposal_id = :p_proposal_id AND token_id = :p_token_id;
• Join to the parent proposal and to IBC_CITEM_VERSIONS_B on CITEM_VERSION_ID to correlate token values with specific content versions.
• Audit reporting: filter on LAST_UPDATED_BY and LAST_UPDATE_DATE to identify changes made to proposal values within a period.

Because the table stores only Text and List of Values user-defined tokens, reporting on system-derived tokens requires querying the underlying source tables rather than this table. Reports on List of Values tokens should generally present TOKEN_VALUE for display and TOKEN_VALUE_ID for drill-through.

Related Objects

• PRP_PROPOSALS — parent entity; joined on PRP_PROPOSAL_TOKENS.PROPOSAL_ID = PRP_PROPOSALS.PROPOSAL_ID.
• IBC_CITEM_VERSIONS_B — content item version base table; joined on PRP_PROPOSAL_TOKENS.CITEM_VERSION_ID = IBC_CITEM_VERSIONS_B.CITEM_VERSION_ID.
• PRP_PROPOSAL_TOKENS_PK / PRP_PROPOSAL_TOKENS_U1 / PRP_PROPOSAL_TOKENS_U2 — the primary key and unique indexes that enforce row identity and the per-proposal token uniqueness rule.
• Token definition objects — the token master referenced by TOKEN_ID, which supplies the token name, type (Text or List of Values), and, for LOV tokens, the permitted value set.
• PRP proposal template and content APIs — the PL/SQL and OAF-based services through which proposal documents are generated and token values are applied.