Results for “qp_limit_balances_u1”

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

Overview

The APPS.QP_LIMIT_TRANSACTIONS_PVT package body is a private (PVT) Advanced Pricing utility package in Oracle E-Business Suite 12.1.1 and 12.2.2. It manages the transactional integrity of pricing limits — the maximum monetary or quantity thresholds enforced against a pricing agreement, promotion, or modifier during order capture or pricing. When Qualifier/Limiter processing evaluates a pricing event, this package reconciles the QP_LIMIT_TRANSACTIONS table against the qualifying modifiers that actually consumed limit capacity, and adjusts the balance bookkeeping held in QP_LIMIT_BALANCES. Its central design concern is ensuring the available limit balance reflects only transactions that still have a matching modifier record, preventing phantom consumption of a limit and premature exhaustion of a customer entitlement. The package is classified as PVT, meaning it is an internal implementation unit invoked by other pricing packages rather than a public API for direct customer extension.

Key Procedures and Functions

The documented interface exposes a single procedure, DELETE. It removes a limit transaction record for a given pricing event and phase combination that no longer has a corresponding modifier in the temporary request line-detail table (qp_npreq_ldets_tmp). It is driven by a cursor that joins the limit transaction to that temporary table on pricing status and phase, so that only genuinely orphaned transactions are purged. This purge is the mechanism by which the limit consumption ledger is kept synchronized with the surviving modifier set after pricing recalculation.

Although not enumerated in the extracted metadata, the package body also contains an UPDATE_BALANCE procedure declared with PRAGMA AUTONOMOUS_TRANSACTION. It applies a delta amount to the AVAILABLE_AMOUNT column of QP_LIMIT_BALANCES for an identified balance and commits independently of the caller's transaction. This autonomous commit isolates balance maintenance from the surrounding pricing transaction so a rollback of the pricing call does not silently discard the balance movement. Callers should be aware that autonomous commits cannot be revoked by the invoking session.

Tables Accessed

QP_LIMIT_TRANSACTIONS is the primary ledger of limit consumption, one row per qualifying limit event; the DELETE procedure issues deletes against it. QP_LIMIT_BALANCES holds the running available amount per limit; UPDATE_BALANCE updates it. QP_EVENT_PHASES and QP_PRICING_PHASES supply the event-to-phase and pricing-phase definitions used to resolve which event/phase combination a transaction belongs to. OE_ORDER_LINES_ALL and ASO_SHIPMENTS provide the order-line and shipment context against which limit consumption is validated.

Usage Notes

This package is not launched from a form or concurrent program directly. It is invoked internally by pricing engine packages during Qualifier and Limiter processing — typically after modifier application and recalculation in the ordering flow — to reconcile limit transaction records and refresh balances. Because the balance update runs as an autonomous transaction, it commits its own work immediately, so customizations must not attempt to wrap it in an enclosing rollback or assume consistency with the parent transaction. Extensions should never update QP_LIMIT_TRANSACTIONS or QP_LIMIT_BALANCES directly; all maintenance must flow through this package to preserve balance integrity. The DELETE procedure tolerates a status output parameter, so callers should inspect the returned return status before assuming reconciliation succeeded.