Search Results qp_list_header_phases




Overview
Explore in AI Chat

Overview

QP_LIST_HEADER_PHASES is a table in the QP schema belonging to the Oracle Advanced Pricing module. It stores the set of pricing phases currently associated with a given price list header, together with flags that govern how the Pricing Engine applies each phase during list qualification and price calculation. The object exists primarily for Pricing Engine performance: rather than resolving the applicable phases dynamically at runtime through more expensive joins, the engine reads the pre-computed phase membership for a list header directly from this table.

Functionally, the table acts as an intersection between a list header and the pricing phases defined in QP_PRICING_PHASES, augmented by qualifier and product-attribute indicators and standard audit columns. Under a heuristic Data Vault classification mined from its foreign key structure, the table is standalone. Because it carries only one outbound foreign key and no inbound references from other documented tables, it is best modeled as an independent or low-coupling entity rather than a true link table, though its grain — one row per list header, pricing phase, and product-attribute-only flag combination — is link-like in character.

Key Information Stored

The documented physical schema for 12.2.2 contains nine columns. The most significant are:

  • LIST_HEADER_ID — Identifies the price list header (QP_LIST_HEADERS_B) to which the phase applies. Together with PRICING_PHASE_ID and PRIC_PROD_ATTR_ONLY_FLAG, this forms the business-key candidate defined by unique index QP_LIST_HEADER_PHASES_U1.
  • PRICING_PHASE_ID — The specific pricing phase from QP_PRICING_PHASES that is active for the list header. This column also carries the table's sole foreign key, QP_LIST_HEADER_PHASES.PRICING_PHASE_ID → QP_PRICING_PHASES.
  • PRIC_PROD_ATTR_ONLY_FLAG — Indicates whether the phase applies only to pricing product attributes. It participates in the unique business key, so the same phase may appear more than once for a header when this flag differs.
  • QUALIFIER_FLAG — Marks whether the phase entry is to be treated as a qualifier, influencing how the Pricing Engine evaluates eligibility before pricing.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN record the standard Oracle EBS who/when audit trail for each row.

The metadata does not document a dedicated surrogate primary key column beyond the unique business index QP_LIST_HEADER_PHASES_U1, which should be treated as the authoritative uniqueness constraint.

Common Use Cases and Queries

The principal use case is diagnosing and tuning Pricing Engine behavior — determining which phases a given price list header will execute and whether any entry is restricted to product attributes. A typical query joining phases to their definitions is:

  • SELECT lh.list_header_id, ph.pricing_phase_id, ph.name, lhp.qualifier_flag, lhp.pric_prod_attr_only_flag FROM qp_list_header_phases lhp, qp_pricing_phases ph, qp_list_headers_b lh WHERE lhp.pricing_phase_id = ph.pricing_phase_id AND lhp.list_header_id = lh.list_header_id;
  • Filtering WHERE pric_prod_attr_only_flag = 'Y' isolates phases scoped to pricing product attributes.
  • Counting distinct PRICING_PHASE_ID values per LIST_HEADER_ID supports performance-impact assessment of phase configuration.
  • Comparing LAST_UPDATE_DATE across rows helps trace when phase configuration changed, useful in troubleshooting pricing results that altered after a setup update.

Reporting scenarios include auditing which lists use qualifier phases versus price phases and validating that phase setup aligns with documented pricing strategies.

Related Objects

The most significant related objects are:

  • QP_PRICING_PHASES — Referenced through PRICING_PHASE_ID; defines phase names and behavior.
  • QP_LIST_HEADERS_B / QP_LIST_HEADERS_TL — The price list headers to which LIST_HEADER_ID points.
  • QP_LIST_LINES — List lines whose qualification depends on the phases configured here.
  • QP_QUALIFIERS / QP_PRICE_FORMULAS — Consumed by the Pricing Engine during the phases identified.
  • QP_PRICING_ATTRIBUTES — Relevant when PRIC_PROD_ATTR_ONLY_FLAG is set.

These relationships center on LIST_HEADER_ID and PRICING_PHASE_ID and collectively govern Pricing Engine execution paths.