Results for “prp_component_styles_b”

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

Overview

PRP_COMPONENT_STYLES_B is the base (non-translated) table in the Proposals (PRP) module of Oracle E-Business Suite, storing the definition of component styles. Component styles describe the presentational and structural configuration applied to a component within a proposal template or proposal document. The table resides in the PRP schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. Functionally, it is a definitional master table: each row represents a distinct style that can be associated with a proposal component, a content node, or an external content item.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. PRP_COMPONENT_STYLES_B carries the natural business key COMPONENT_STYLE_CODE and a surrogate primary key COMPONENT_STYLE_ID, and it is referenced by four dependent tables, including its translation table PRP_COMPONENT_STYLES_TL. This positions it as a stable reference point for descriptive content in downstream relationships rather than as a transactional link itself.

Key Information Stored

The documented physical schema contains 27 columns. The most important are:

• COMPONENT_STYLE_ID — the surrogate primary key, enforced by index PRP_COMPONENT_STYLES_B_PK and listed as a unique index candidate.
• COMPONENT_STYLE_CODE — the natural business key, enforced by unique index PRP_COMPONENT_STYLES_B_UK1 (documented as PRP_COMPONENT_STYLES_B_U2).
• COMPONENT_ID — foreign key to PRP_COMPONENTS_B, tying the style to its parent component definition.
• CONTENT_ITEM_ID — foreign key to IBC_CONTENT_ITEMS, linking the style to a reusable content item.
• CONTENT_NODE_TYPE — classifies the type of content node associated with the style.
• OBJECT_VERSION_NUMBER — optimistic locking column used for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS who-columns for audit and multi-user tracking.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield (DFF) storage, enabling client-specific extension of the component style without schema modification.

The distinction between the surrogate key (COMPONENT_STYLE_ID) and the business key (COMPONENT_STYLE_CODE) matters when joining: foreign keys throughout the schema reference COMPONENT_STYLE_ID, whereas integrations and imports typically resolve rows by COMPONENT_STYLE_CODE.

Common Use Cases and Queries

Component styles are primarily consumed during proposal generation, where the appropriate presentation of each component is resolved. Typical reporting and diagnostic queries include:

• Listing all styles for a given component: join PRP_COMPONENT_STYLES_B to PRP_COMPONENTS_B on COMPONENT_ID and filter by COMPONENT_STYLE_CODE.
• Auditing recently modified style definitions using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Identifying styles linked to content items by joining on CONTENT_ITEM_ID to IBC_CONTENT_ITEMS.
• Extracting client-specific DFF values via ATTRIBUTE_CATEGORY and ATTRIBUTE1–15.
• Detecting orphaned or unused styles by left-joining to PRP_TEMPLATE_COMPONENTS on DEFAULT_COMP_STYLE_ID where the join is null.

A representative pattern is: SELECT cs.COMPONENT_STYLE_ID, cs.COMPONENT_STYLE_CODE, cs.COMPONENT_ID, cs.CONTENT_ITEM_ID FROM PRP.PRP_COMPONENT_STYLES_B cs WHERE cs.COMPONENT_ID = :component_id. Because the module is multilingual, display-facing queries should join to PRP_COMPONENT_STYLES_TL to obtain translated names and descriptions.

Related Objects

The table participates in several key relationships:

• PRP_COMPONENT_STYLES_TL — the translation table; joins on COMPONENT_STYLE_ID for language-specific text.
• PRP_COMPONENTS_B — referenced via COMPONENT_ID, supplying the parent component definition.
• IBC_CONTENT_ITEMS — referenced via CONTENT_ITEM_ID, providing the reusable content item.
• PRP_COMP_STYLE_CTNTVERS — references this table on COMPONENT_STYLE_ID, storing style content versions.
• PRP_PROP_STYLE_CTNTVERS — references this table on COMPONENT_STYLE_ID, storing proposal-level style content versions.
• PRP_TEMPLATE_COMPONENTS — references this table on DEFAULT_COMP_STYLE_ID, designating the default style for a template component.

Together these dependencies establish PRP_COMPONENT_STYLES_B as a central reference object for component styling across proposal templates, proposals, and content versioning.