Results for “comp_style_ctntver_id”

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

Overview

PRP_STYLE_CTNTVER_TOKENS is a transactional detail table in the Oracle E-Business Suite Proposals (PRP) module. It records the individual tokens referenced by a component style document. In the Oracle EBS proposal-generation framework, component styles act as reusable templates containing placeholders — tokens — that are substituted with proposal, customer, or opportunity data at runtime. When a component document file is uploaded to the repository, the application parses the file and inserts one row into this table for each token it discovers, binding that token to the specific component style content version from which it was extracted.

The table therefore serves as the bridge between a parsed document version and the token definitions that the document consumes. Its population is driven by the upload and parse process rather than by direct user data entry, which means the row set for a given version is a faithful representation of what the document actually contained at parse time. Because each parse produces a fresh association set, the table supports verification that a template's token inventory matches the definitions expected by the rendering engine.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is best modelled as a link. It resolves a many-to-many relationship between component style content versions and tokens, carrying no descriptive attributes of its own beyond ordering and audit metadata. This classification is a modelling suggestion rather than a documented EBS construct; the physical table remains a conventional relational child object within the PRP schema.

Key Information Stored

The table contains ten documented columns. The most significant are:

• STYLE_CTNTVER_TOKEN_ID — the surrogate primary key, enforced by PRP_STYLE_CTNTVER_TOKENS_PK. It uniquely identifies each token-reference row and is the column used by downstream child objects.
• COMP_STYLE_CTNTVER_ID — foreign key to PRP_COMP_STYLE_CTNTVERS, identifying the component style content version whose document was parsed. This is the driving column for most queries.
• TOKEN_ID — the token referenced by the document. The FK metadata indicates a self-referencing relationship back into this same table's TOKEN_ID, reflecting the token registry structure within the PRP schema.
• DISPLAY_ORDER — the sequence in which the token appears within the parsed document, preserving document position for ordered rendering and review.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS 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 uploaded or parsed the document and when the row was last touched.

Two unique indexes are documented. PRP_STYLE_CTNTVER_TOKENS_U1 covers STYLE_CTNTVER_TOKEN_ID and mirrors the primary key. PRP_STYLE_CTNTVER_TOKENS_U2 covers the pair (COMP_STYLE_CTNTVER_ID, TOKEN_ID) and is the true business-key candidate: a given token may appear only once per component style content version. Any diagnostic or reconciliation query should treat this pair as the natural identifier.

Common Use Cases and Queries

The primary use case is verifying that an uploaded component style document was parsed correctly. The following query lists all tokens associated with a content version in document order:

• SELECT t.TOKEN_ID, t.DISPLAY_ORDER FROM PRP.PRP_STYLE_CTNTVER_TOKENS t WHERE t.COMP_STYLE_CTNTVER_ID = :ver_id ORDER BY t.DISPLAY_ORDER;

A second common pattern is detecting duplicate or orphaned token bindings, which manifest as rendering failures or unresolved placeholders in generated proposals. Joining to PRP_COMP_STYLE_CTNTVERS establishes the owning style and its document metadata, while aggregating counts per version supports impact analysis before a token definition is changed:

• SELECT COMP_STYLE_CTNTVER_ID, COUNT(*) FROM PRP.PRP_STYLE_CTNTVER_TOKENS GROUP BY COMP_STYLE_CTNTVER_ID HAVING COUNT(*) > :threshold;

Reporting scenarios include token-usage inventories across all component styles, comparison of token sets between successive content versions to identify template drift, and audit reports reconstructing who uploaded which document and when, driven by CREATED_BY and CREATION_DATE.

Related Objects

• PRP_COMP_STYLE_CTNTVERS — parent table referenced through COMP_STYLE_CTNTVER_ID; the principal join for any query that needs style, version, or document context.
• PRP_STYLE_CTNTVER_TOKENS (TOKEN_ID) — documented self-referencing foreign key linking each row to the token definition it represents.
• PRP_STYLE_CTNTVER_TOKENS_PK / _U1 / _U2 — the primary key and unique indexes that enforce row identity and the per-version token uniqueness rule.
• PRP_COMP_STYLES — the style header that owns the content versions, reached indirectly through PRP_COMP_STYLE_CTNTVERS.
• Proposals token definition objects — the token registry consulted during document parsing and proposal generation, surfaced through TOKEN_ID.
• Concurrent program: component document upload and parse — the process that populates this table and is the origin of all rows.