Search Results qp_default_limit_balances




Overview
Explore in AI Chat

Overview

The APPS.QP_DEFAULT_LIMIT_BALANCES package is a technical PL/SQL unit within the Oracle E-Business Suite Advanced Pricing module (QP). Its primary business function is to apply defaulting logic to limit balance records used by the pricing engine's limit and balance validation framework. Limit balances represent the accumulated monetary or quantity values associated with a specific pricing limit — for example, the total value of orders booked against a customer or promotion limit — and the pricing engine consults these balances when determining whether additional transactions may proceed.

The package served as a defaulting hook: when a limit balance record is being prepared for use and one or more of its attributes are not supplied by the calling process, this package is invoked to populate the missing values by applying the application's standard defaulting rules. The Header comment (QPXDLMBS.pls 120.1, dated 09-JUN-2005) indicates the file has been stable since the early 11i era and continued to be shipped through EBS 12.1.1 and 12.2.2 without functional change. In the ETRM metadata, the package is classified with an API classification of OTHER, indicating it is not a formal public API but rather an internal supporting utility invoked by other pricing components.

Key Procedures and Functions

The package exposes a single documented procedure:

  • Attributes — The defaulting procedure for limit balance records. It accepts an input limit balance record (typed using QP_Limits_PUB.Limit_Balances_Rec_Type, with a default of G_MISS_LIMIT_BALANCES_REC when no record is supplied), an iteration number that supports repeated defaulting passes, and returns the completed limit balance record through an OUT NOCOPY parameter. The procedure does not return a status value; callers determine success by inspecting the returned record. Its purpose is to ensure every required attribute of a limit balance record carries a valid value before the record is used by the pricing limits validation logic.

No public functions are declared in the specification. The absence of additional procedures reflects the narrow, single-purpose design of this utility.

Tables Accessed

The ETRM metadata records two tables referenced by the package through APPS synonyms:

  • QP_LIMIT_BALANCES_S — The sequence associated with limit balance records. The defaulting logic references this sequence when it must generate a surrogate key for a limit balance that has not yet been assigned an identifier.
  • DUAL — The standard Oracle single-row utility table, used for evaluating defaulting expressions, sequence pseudo-columns, or system values within PL/SQL.

The package does not directly perform INSERT, UPDATE, or DELETE operations on the QP_LIMIT_BALANCES base table within the documented specification; persistence of the defaulted record is the responsibility of the calling process, which receives the populated record through the OUT parameter.

Usage Notes

Because the package is internal and classified as OTHER, it is not intended to be called directly from customer extensions. It is invoked by other pricing packages — the ETRM metadata notes it is referenced by one other package — as part of the limit balance maintenance and validation flow. Typical invocation scenarios include the pricing engine and limit-checking routines that must materialize or refresh a limit balance record before evaluating whether a transaction exceeds an assigned limit.

Custom code should not call QP_Default_Limit_Balances.Attributes directly. Developers requiring limit balance defaulting behavior should instead use the supported public APIs in QP_Limits_PUB, which encapsulate this utility and provide validation, error handling, and persistence. As with all internal QP packages, Oracle may change the specification in future releases without notice.