Results for “qp_limit_transactions_pvt”

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

Overview

QP_LIMIT_TRANSACTIONS_PVT is a private PL/SQL package in the Oracle E-Business Suite Advanced Pricing (QP) module, owned by the APPS schema and classified in ETRM as a PVT (private) API. The package supports the pricing limits feature set, which enforces threshold controls — quantity, monetary, or usage-based caps — on pricing transactions during order capture and pricing execution. Its central role is to maintain the integrity of limit accounting records by conditionally removing limit transaction entries that are no longer valid, for example when a pricing event is reprocessed, deleted, or rolled back. Because the package is marked PVT rather than PUBLIC, Oracle does not expose it as a supported integration surface; it is intended for internal use by the pricing engine and its dependent modules within the same product family.

Key Procedures and Functions

The documented interface contains a single procedure, Delete. Its purpose is to delete limit transactions conditionally, based on the input pricing event code.

• Delete — Accepts a pricing event code as input and returns a status indicator through its OUT parameter, which reports the outcome of the deletion attempt to the calling program. The conditional nature of the operation means the procedure evaluates the pricing event context before removing records from the limit transaction repository, avoiding indiscriminate purges of limit data. The OUT return status allows callers to branch on success or failure and to raise appropriate error handling. No other procedures or functions are documented for this package in the ETRM metadata.

Tables Accessed

The package interacts with six tables through APPS synonyms, spanning pricing, order management, and shipping data:

• QP_LIMIT_TRANSACTIONS — The primary target of the Delete procedure, holding individual limit consumption transaction records.
• QP_LIMIT_BALANCES — Stores running limit balances; read or adjusted as part of maintaining consistency after transactions are removed.
• QP_PRICING_PHASES and QP_EVENT_PHASES — Define the pricing event and phase configuration that determines when and how a limit transaction qualifies for deletion, providing the conditional context for the procedure.
• OE_ORDER_LINES_ALL — Order line data tied to limit-bearing pricing events, used to associate transactions with their source order lines.
• ASO_SHIPMENTS — Shipping information referenced to reconcile limit consumption against fulfilled or shipped quantities.

Usage Notes

QP_LIMIT_TRANSACTIONS_PVT is a private package and is not intended for direct invocation by customer code. In practice it is called internally by the Advanced Pricing engine, and ETRM records that it is referenced by one other package. Typical invocation scenarios include order-line cancellation, pricing event rollback, and reprocessing flows where previously recorded limit transactions must be reversed so that consumed limits are returned to the available balance. Because the Delete procedure is conditional, callers rely on the pricing event code to scope the operation correctly; passing an inappropriate or overly broad event code can affect limit records beyond the intended transaction scope. Customers requiring limit maintenance logic in extensions should prefer supported public APIs and avoid binding to this PVT package, since its signature and behavior are subject to change without notice in 12.1.1 and 12.2.2. The package name has no relationship to third-party payment or "digital transaction limit" products; in Oracle EBS nomenclature, "limit transactions" refers specifically to Advanced Pricing limit consumption records.