Results for “default_comp_style_id”

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

Overview

PRP_TEMPLATE_COMPONENTS is an Oracle E-Business Suite table in the PRP (Proposals) schema. It stores the association between proposal templates and the components that compose them, effectively defining the building blocks used when a proposal is generated from a template. Each row represents one component assignment to one template, along with control attributes such as display sequence and whether the component is mandatory. Because a single template can contain many components and a single component can be reused across many templates, this table functions as a cross-reference object.

The table resides in the PRP schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. From a Data Vault modeling perspective, the mined FK structure heuristically suggests this object behaves as a link table, resolving a many-to-many relationship between templates and components. This classification should be treated as a modeling suggestion rather than an enforced design.

Key Information Stored

The documented physical schema contains 12 columns. The most significant include:

• TEMPLATE_COMPONENT_ID — the surrogate primary key (PRP_TEMPLATE_COMPONENTS_PK) uniquely identifying each template-component association.
• TEMPLATE_ID — foreign key to PRP_TEMPLATES_B; identifies the parent template.
• COMPONENT_ID — foreign key to PRP_COMPONENTS_B; identifies the component assigned to the template.
• DEFAULT_COMP_STYLE_ID — foreign key to PRP_COMPONENT_STYLES_B; supplies the default styling applied to the component within the template.
• DISPLAY_ORDER — controls the sequence in which components appear.
• MANDATORY_FLAG — indicates whether the component must be included when the template is used.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Two unique indexes are documented: PRP_TEMPLATE_COMPONENTS_U1 on TEMPLATE_COMPONENT_ID (the surrogate key) and PRP_TEMPLATE_COMPONENTS_U2 on the composite (TEMPLATE_ID, COMPONENT_ID), which acts as the business-key candidate enforcing that a component is assigned only once per template.

Common Use Cases and Queries

Typical scenarios include reporting which components belong to a given template, determining mandatory components, and resolving the display order of template content. A common query joins the table to its parent and child business tables:

• Listing all components for a template:

  SELECT tc.TEMPLATE_COMPONENT_ID, tc.COMPONENT_ID, tc.DISPLAY_ORDER, tc.MANDATORY_FLAG
  FROM   PRP.PRP_TEMPLATE_COMPONENTS tc
  WHERE  tc.TEMPLATE_ID = :template_id
  ORDER BY tc.DISPLAY_ORDER;

• Identifying mandatory components across templates:

  SELECT TEMPLATE_ID, COMPONENT_ID
  FROM   PRP.PRP_TEMPLATE_COMPONENTS
  WHERE  MANDATORY_FLAG = 'Y';

• Resolving component definitions and default styles via joins to PRP_COMPONENTS_B and PRP_COMPONENT_STYLES_B.

These patterns support template configuration reports, migration validation, and audit checks confirming that every template has the expected set of components.

Related Objects

The FK metadata identifies three direct parent relationships, and additional dependent objects may reference this table:

• PRP_TEMPLATES_B — joined via TEMPLATE_ID; the template header definition.
• PRP_COMPONENTS_B — joined via COMPONENT_ID; the reusable component definition.
• PRP_COMPONENT_STYLES_B — joined via DEFAULT_COMP_STYLE_ID; supplies component styling defaults.
• PRP_TEMPLATE_COMPONENTS_PK / _U1 / _U2 — primary and unique constraints enforcing identity and uniqueness.

Together these objects form the core of the PRP template configuration model, with PRP_TEMPLATE_COMPONENTS serving as the linking entity between templates, components, and their presentation styles.