Search Results qp_list_headers_pvt




Overview
Explore in AI Chat

Overview

QP_LIST_HEADERS_PVT is a private PL/SQL package in the Oracle E-Business Suite Advanced Pricing module (APPS schema). It provides the internal, low-level implementation logic that supports the public price list API, QP_PRICE_LIST_PUB. The package is classified as a "PVT" (private) API, meaning it is not intended to be called directly by external consumers; instead it is invoked by the public API layer and other pricing components that need to create, update, validate, and process price lists and their associated lines, qualifiers, and pricing attributes.

The central business function of this package is to process the full structure of a price list — the list header, its price list lines, qualifier rules, and pricing attributes — within a single transactional unit. This includes maintaining the relationship between the current record state and the prior (old) record state so the pricing engine can correctly apply changes, maintain related modifiers, and preserve referential integrity across the pricing schema. A named procedure, LOCK_PRICE_LIST, provides the locking primitive that serializes concurrent modifications to a given price list, which is the specific entry point users locate when searching for "lock_price_list".

Key Procedures and Functions

  • PROCESS_PRICE_LIST — The primary worker procedure. It accepts a standard API parameter signature (API version, initialization and commit flags, validation level, and a control record) together with the incoming and previous states of the price list header, lines, qualifiers, and pricing attributes, and returns the standard API return status, message count, and message data outputs. Its purpose is to carry out the core insert, update, and delete processing required to persist a price list and all of its dependent entities.
  • LOCK_PRICE_LIST — The locking procedure. It acquires the necessary lock (typically a row-level lock on the price list header) to prevent concurrent modification of the same price list, ensuring that parallel requests do not corrupt the price list or its related data during processing.
  • GET_PRICE_LIST — The retrieval procedure. It fetches price list header information so that calling code can inspect or validate the existing state of a price list before or after processing operations.

These three procedures collectively form the internal processing contract underlying the public price list API.

Tables Accessed

The package operates against the core pricing base tables accessed through APPS synonyms:

  • QP_LIST_HEADERS_B — the price list header base table, holding the primary definition and attributes of each price list.
  • QP_LIST_LINES — the individual price list lines (items, pricing values, and related attributes) belonging to a header.
  • QP_QUALIFIERS — qualifier rules that determine when a price list or line applies.
  • QP_RLTD_MODIFIERS and QP_RLTD_MODIFIERS_S — tables storing related modifiers and their translations/setup information associated with pricing entities.
  • DUAL — used for single-row operations and value checks.
  • PLITBLM — a pricing line/item temporary or interface table used during processing.

Reads and writes across these tables allow the package to persist the complete price list structure while preserving its relationships.

Usage Notes

QP_LIST_HEADERS_PVT is invoked indirectly rather than directly. It is referenced by approximately ten other packages in the pricing module, most notably the public API QP_PRICE_LIST_PUB, which delegates its processing to this private package. Pricing forms (such as the Price List setup forms) and concurrent programs that create or maintain price lists ultimately trigger this logic through the public API layer. Custom code should call QP_PRICE_LIST_PUB rather than QP_LIST_HEADERS_PVT, since private APIs are subject to change without notice and are not part of Oracle's supported public interface. The LOCK_PRICE_LIST procedure is of particular interest to integrators concerned with concurrency control, but it should be reached through the supported public API path rather than invoked directly.