Search Results qp_list_header_phases_u1




Overview

QP.QP_LIST_HEADER_PHASES is a transactional table in the Oracle Advanced Pricing (QP) schema that stores all currently active phases for each pricing list header. Its stated purpose within Oracle E-Business Suite Release 12.1.1 and 12.2.2 is to support Pricing Engine performance by pre-materializing the phase information associated with a list header, rather than deriving it dynamically at runtime. Each row represents the association between a pricing list header and a pricing phase, with additional detail indicating whether the list header carries line-level qualifiers and whether the phase applies only to pricing and product attributes.

The object is fully valid in the ETRM repository and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. From a Data Vault modeling perspective, the mined relationship structure is classified heuristically as standalone. This suggests the table behaves as an independent structure rather than a classic hub, link, or satellite, because the only documented foreign key reference is the PRICING_PHASE_ID column pointing to QP.QP_PRICING_PHASES. Practically, the table functions as a performance-oriented bridge between list headers and pricing phases, and its content is typically refreshed by the pricing engine whenever list header phase configuration changes.

Key Information Stored

The table contains nine documented columns. The most significant are summarized below.

The surrogate primary key is not separately documented; instead, uniqueness is enforced through the unique index QP_LIST_HEADER_PHASES_U1 over (PRICING_PHASE_ID, LIST_HEADER_ID, PRIC_PROD_ATTR_ONLY_FLAG). This composite key is the primary business-key candidate for the table and prevents duplicate phase assignments for the same list header under the same attribute-only setting. Applications that search for "qp_list_header_phases_u1" are typically investigating this unique index, either for constraint analysis, performance tuning, or index reorganization.

Common Use Cases and Queries

Typical usage involves diagnosing Pricing Engine performance and verifying phase configuration for a specific list header. The most straightforward query retrieves all phases associated with a given list header:

  • SELECT PRICING_PHASE_ID, QUALIFIER_FLAG, PRIC_PROD_ATTR_ONLY_FLAG FROM QP.QP_LIST_HEADER_PHASES WHERE LIST_HEADER_ID = :header_id;
  • Joining to QP.QP_PRICING_PHASES to resolve phase names and sequences for audit reports.
  • Identifying list headers that have line-level qualifiers by filtering on QUALIFIER_FLAG = 'Y'.
  • Confirming attribute-only phase assignments by filtering on PRIC_PROD_ATTR_ONLY_FLAG.
  • Checking data consistency between QP_LIST_HEADERS_B and its phase rows when pricing results appear incomplete.

Because the table is a performance aid, it is also commonly examined when troubleshooting Pricing Engine latency or when validating that phase records are correctly populated after a pricing list change.

Related Objects

The following objects are the most significant dependencies and references for QP.QP_LIST_HEADER_PHASES:

  • QP.QP_LIST_HEADERS_B — referenced via LIST_HEADER_ID; the parent pricing list header definition.
  • QP.QP_PRICING_PHASES — foreign key target of PRICING_PHASE_ID; defines the available pricing phases.
  • QP.QP_LIST_HEADER_PHASES# — the underlying object referenced by this table, typically the base table or synonym target.
  • QP_LIST_HEADER_PHASES_U1 — unique index enforcing the (PRICING_PHASE_ID, LIST_HEADER_ID, PRIC_PROD_ATTR_ONLY_FLAG) business key.
  • Pricing Engine programs and concurrent processes that populate and consume these phase records during pricing execution.

No other database objects are documented as referencing this table, reinforcing its standalone classification within the mined dependency model.