Search Results qp_event_phases




Overview
Explore in AI Chat

Overview

The QP_EVENT_PHASES table is a core configuration table within the Oracle E-Business Suite Advanced Pricing (QP) module. It serves as a critical junction table that defines the relationship between pricing events and the pricing phases that are executed in response to those events. In the Advanced Pricing architecture, a pricing event (such as entering a sales order or running a price list) triggers a sequence of pricing phases (such as price list retrieval, modifier application, and freight calculation). This table provides the essential mapping that dictates which phases are invoked for a given event, enabling the modular and sequenced execution of the pricing engine. Its configuration directly controls the pricing workflow and is fundamental to the correct application of complex pricing rules in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is focused on establishing the event-phase relationship. The primary key is a composite of two columns, ensuring a unique mapping. The key columns are:

  • PRICING_EVENT_CODE: A code identifying a specific pricing event within the system (e.g., events related to Order Management, Quoting, or other application interfaces).
  • PRICING_PHASE_ID: A numeric identifier that references a specific pricing phase defined in the related QP_PRICING_PHASES table. This dictates the order and type of calculation performed.

Together, these columns store the definitive list of which phases are executed, and in what sequence, when a particular pricing event is initiated by the application.

Common Use Cases and Queries

This table is primarily referenced for configuration analysis, troubleshooting, and impact assessment. A common use case is to audit or verify the pricing workflow for a specific module. For instance, to see all pricing phases associated with the Order Book event, a consultant might run:

  • SELECT eph.pricing_event_code, ph.phase_code, ph.name
    FROM qp_event_phases eph, qp_pricing_phases ph
    WHERE eph.pricing_phase_id = ph.pricing_phase_id
    AND eph.pricing_event_code = 'ONT_BOOK'
    ORDER BY ph.sequence_num;

Another critical scenario involves impact analysis before modifying a phase's logic or sequence. Developers would query this table to identify all events that would be affected by a change to a specific PRICING_PHASE_ID. The data is also essential for diagnosing pricing engine failures, where understanding the exact sequence of phases for an event helps isolate the point of failure.

Related Objects

The QP_EVENT_PHASES table has direct dependencies with other key Advanced Pricing setup tables. Its primary foreign key relationship is with the QP_PRICING_PHASES table, which holds the detailed definition of each phase, including its name, code, and execution sequence. The PRICING_EVENT_CODE column typically relates to lookup values and internal constants defined within the pricing engine's logic, rather than a separate key table. This mapping table is centrally referenced by the pricing engine's processing programs (often within the QP_PREQ_GRP and related PL/SQL packages) that dynamically construct the phase execution list based on the event. Consequently, changes to this table's data directly affect the runtime behavior of these core pricing APIs.