Search Results qp_price_request_context




Overview
Explore in AI Chat

Overview

QP_PRICE_REQUEST_CONTEXT is an Oracle E-Business Suite package body owned by APPS that manages the request context and locking semantics used by the Oracle Pricing (QP) pricing engine, particularly in support of the Java pricing engine and the pricing interface tables. Its central business function is to establish a unique request identifier for each pricing request and to serialize access to the pricing interface tables so that concurrent pricing calls do not corrupt shared staging data. In releases 12.1.1 and 12.2.2 the package is classified as OTHER within the ETRM repository and is referenced by 23 other packages, indicating it is an internal utility that underpins the broader pricing API stack rather than a user-facing API.

Key Procedures and Functions

The documented API surface comprises five procedures and functions:

  • SET_REQUEST_ID — Generates and assigns the request identifier used to tag the current pricing run. When the Java engine is not running, the value is derived by incrementing the REQUEST_ID stored in the QP_CONTEXT namespace; when the Java engine is running, the next value of the QP_REQUEST_ID_S sequence is selected, an S-mode lock is acquired on the interface tables, and the interface-table counters are reset to zero.
  • GET_REQUEST_ID — Returns the current request identifier held in the QP_PREQ_GRP package state, defaulting to FND_API.G_MISS_NUM when no value has been set.
  • SET_TRANSACTION_ID — Stores a transaction identifier in the same session context, supporting the HTML Qualifiers user interface.
  • GET_TRANSACTION_ID — Retrieves the transaction identifier attribute previously stored, again primarily for the HTML Qualifiers UI.
  • RELEASE_PRICING_LOCK — Releases the DBMS_LOCK lock previously acquired on the pricing interface tables, allowing the next waiting pricing request to proceed.

An additional internal function, REQUEST_PRICING_LOCK, is declared with PRAGMA AUTONOMOUS_TRANSACTION and performs the DBMS_LOCK.ALLOCATE_UNIQUE and DBMS_LOCK.REQUEST calls in S_MODE with MAXWAIT.

Tables Accessed

The package references a small, focused set of objects through APPS synonyms:

  • QP_REQUEST_ID_S — Sequence used to obtain the next unique request identifier when the Java engine is active.
  • DBMS_LOCK — Supplies ALLOCATE_UNIQUE, REQUEST, and RELEASE to implement a shared lock that serializes work against the pricing interface tables.
  • DBMS_SESSION — Provides SET_CONTEXT to publish the request_id attribute under the qp_context namespace, making it available to session-scoped lookups.
  • DUAL — Used as the source for selecting QP_REQUEST_ID_S.NEXTVAL.

Usage Notes

QP_PRICE_REQUEST_CONTEXT is invoked internally by the pricing engine and by the packages that reference it — typically when a pricing request is initiated from the Pricing forms, an order or quoting flow, or a concurrent program that calls the QP pricing APIs. The SET_REQUEST_ID routine is called at the start of a pricing request; RELEASE_PRICING_LOCK is called when the work completes. Because the interface-table lock is shared and waits on MAXWAIT, callers should ensure that release occurs even on error paths. Custom code should not call these procedures directly unless it is deliberately participating in the same pricing-request lifecycle, and GET_REQUEST_ID and the transaction-id accessors are primarily intended for UI and diagnostic use behind the HTML Qualifiers screens.