Search Results qp_pattern_phases




Overview
Explore in AI Chat

Overview

QP_PATTERN_PHASES is a reference and configuration table within the Oracle Advanced Pricing (QP) module of Oracle E-Business Suite. It defines the relationship between a pricing pattern (a named grouping of pricing phases) and the individual pricing phases that compose it. A "pattern" in Advanced Pricing governs the sequence in which pricing engine phases — such as list price, modifier, and qualifier evaluation — are executed during the pricing calculation. QP_PATTERN_PHASES is therefore the association table that records, for each pattern, which phases are active or included.

The table resides in the QP schema and is classified as VALID in the ETRM data dictionary. The metadata provided includes no explicit primary key or unique index documentation, so the true surrogate primary key cannot be confirmed from the supplied facts. The heuristic Data Vault classification mined from the foreign key structure indicates a standalone object, meaning it does not cleanly resolve to a pure hub, link, or satellite. As a modeling suggestion, this association table behaves most like a link between two hubs — HR_PATTERNS (the pattern hub) and QP_PRICING_PHASES (the phase hub) — carrying descriptive and audit attributes that could equally be modeled as a satellite. Practitioners designing a Data Vault layer should treat PATTERN_ID and PRICING_PHASE_ID as the composite business key candidates for that link.

Key Information Stored

The documented physical schema for 12.2.2 lists 14 columns. The most significant are:

Together, PATTERN_ID and PRICING_PHASE_ID form the natural business-key candidates for the association. The audit and program columns are descriptive metadata rather than identifiers.

Common Use Cases and Queries

Typical reporting scenarios include auditing which phases are attached to a given pricing pattern, verifying active phase configurations, and tracing effective-dated changes to pattern composition. A representative query listing active phases for a pattern follows:

  • SELECT pp.PRICING_PHASE_ID, pph.PHASE_NAME, pp.START_DATE_ACTIVE, pp.END_DATE_ACTIVE FROM QP.QP_PATTERN_PHASES pp, QP.QP_PRICING_PHASES pph WHERE pp.PRICING_PHASE_ID = pph.PRICING_PHASE_ID AND pp.PATTERN_ID = :pattern_id AND pp.ACTIVE_FLAG = 'Y';

Additional use cases include reconciling pattern definitions against HR_PATTERNS, auditing changes through the concurrent program columns, and validating effective-date ranges for pricing setup certification.

Related Objects

The principal related objects, derived from the documented foreign keys, are:

  • QP_PRICING_PHASES — joined on PRICING_PHASE_ID; the parent list of pricing phases.
  • HR_PATTERNS — joined on PATTERN_ID; the parent pattern definition.
  • QP_PRICING_PHASE_ORDER — related to phase sequencing (supplemental).
  • QP_PATTERNS / pattern views in the QP schema — supplemental companions to HR_PATTERNS.
  • QP_PRICING_ENGINE APIs — consume pattern/phase configuration at runtime.

These joins support both setup administration and runtime pricing diagnostics.