Results for “pattern_search_path”

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

Overview

QP_EVENT_PHASES is a configuration table in the Advanced Pricing (QP) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. The table stores the mapping between pricing events and pricing phases. In Oracle Advanced Pricing, the pricing engine processes a pricing request by executing a defined sequence of phases, such as line-level eligibility, line-level adjustments, and freight and special charges. Each phase is triggered by one or more pricing events, which represent the business transactions that invoke pricing logic — for example, order entry, order fulfillment, invoicing, or return processing. QP_EVENT_PHASES defines precisely which pricing phases are executed for a given pricing event, and therefore governs the runtime behavior of the pricing engine for that transaction type.

Mined from its foreign key structure, the table exhibits a satellite-leaning profile under Data Vault modeling heuristics. It holds descriptive attributes that depend on the combination of a pricing event and a pricing phase, rather than acting as a standalone hub of business keys or a pure link between two entities. This modeling suggestion is consistent with the table's role as a configuration qualifier of the pricing engine's execution path.

Key Information Stored

The table's primary key, QP_EVENT_PHASES_PK, is composed of PRICING_EVENT_CODE and PRICING_PHASE_ID. A unique index, QP_EVENT_PHASES_U1, extends this business key with ZD_EDITION_NAME, which supports edition-based data classification. The most important columns include:

• PRICING_EVENT_CODE — Identifies the pricing event that triggers the associated phase. This is part of the composite primary key.
• PRICING_PHASE_ID — The foreign key to QP_PRICING_PHASES, identifying the phase executed for the event. This is also part of the composite primary key.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Define the effective date range during which the event-to-phase mapping is active.
• SEARCH_FLAG and USER_SEARCH_FLAG — Flag whether the mapping participates in pricing engine search processing and user-defined searches, respectively.
• SEEDED_FLAG — Indicates whether the row was delivered as Oracle seed data or created by a user, which is critical for upgrade and patching considerations.
• PATTERN_SEARCH_PATH — Stores the search path used when matching pricing patterns during phase execution.
• ZD_EDITION_NAME — Supports Oracle's editioning and data classification framework and forms part of the unique business key.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — The standard descriptive flexfield (DFF) columns, enabling customer-specific extensions of the mapping.

Common Use Cases and Queries

Administrators and technical consultants query this table to understand which phases the pricing engine executes for a given event, particularly during troubleshooting of pricing behavior or when extending pricing logic with custom events. A typical query joins QP_EVENT_PHASES to QP_PRICING_PHASES on PRICING_PHASE_ID to retrieve phase names and sequences, filtered by PRICING_EVENT_CODE and active dates. Reporting use cases include auditing seeded versus custom mappings (via SEEDED_FLAG) and verifying the search participation flags. Because the pricing engine uses these mappings at runtime, changes should be made with care, always through supported setup paths or with full regression testing.

Related Objects

The most significant related object is QP_PRICING_PHASES, referenced through the documented foreign key QP_EVENT_PHASES.PRICING_PHASE_ID → QP_PRICING_PHASES. This join resolves the phase identifiers into readable phase definitions and sequences. The pricing event codes themselves are conceptually tied to the pricing event definitions used by the pricing engine (QP_EVENTS family of configuration), while the pricing engine and its public APIs (such as QP_PREQ_PUB and the pricing engine APIs) depend on these mappings at runtime. Modification of these rows should be coordinated with the phases and event definitions referenced across the QP schema.