Search Results qp_limit_balances_s

Overview

The APPS.QP_DEFAULT_LIMIT_BALANCES package body is a server-side PL/SQL component in the Oracle E-Business Suite Advanced Pricing module (Oracle Pricing). Its principal business function is to seed and maintain default limit balance records that govern the enforcement of customer and order limits within the pricing and order capture flow. Limit balances represent the consumption of authoring limits — such as maximum order values, quantity ceilings, or exposure thresholds defined on customers, price lists, or qualifiers — and are reconciled against those limits at transaction time.

The package operates in the APPS schema with a status of VALID, and is classified under API category OTHER in the ETRM 12.2.2 metadata. It is a helper package rather than a public-facing API in the sense of QP_LIMITS_PUB; it performs the internal work of validating inputs, applying defaults, and persisting balance rows that downstream validation logic consumes.

Its dependency footprint confirms this role. It references QP_LIMIT_BALANCES_S (the base table and its synonyms), QP_LIMIT_BALANCES_UTIL, and QP_LIMITS_PUB, and it leverages the standard EBS toolkit: FND_API for the common API error-handling and return-status conventions, FND_MESSAGE and OE_MSG_PUB for user-facing messages, QP_VALIDATE for pricing validation rules, QP_GLOBALS for session-level pricing parameters, and SYS.STANDARD for core PL/SQL constructs.

Key Procedures and Functions

The documented package interface exposes a single program unit:

• ATTRIBUTES — The sole documented procedure/function in the package. It handles the attribute-level processing of default limit balance records, resolving attribute definitions and their associated default values so that newly created or refreshed balance rows carry consistent metadata. Consistent with the package's dependency on FND_API and QP_VALIDATE, this unit applies EBS-standard validation and returns results through the conventional API message and status mechanism.

The broader package logic, supported by its dependencies on QP_LIMIT_BALANCES_UTIL and QP_LIMITS_PUB, applies defaulting rules, validates the resulting balance data, and writes the outcome to the limit balances table. No parameter lists are documented in the available metadata, and none are inferred here.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

• QP_LIMIT_BALANCES_S — The limit balances base table. The package reads and writes this table to create, default, and update balance records. Because the "_S" suffix denotes the base table in an EBS table/view pair, the package's inserts and updates flow through to the corresponding translated views used by the pricing application. The user search term "qp_limit_balances_s" aligns directly with this object.
• DUAL — Used for scalar evaluations, sequence-style lookups, and single-row assignments typical of PL/SQL defaulting and validation logic.

Note that QP_LIMIT_BALANCES_UTIL and QP_LIMITS_PUB are package dependencies rather than tables; any additional tables they touch are outside the documented scope of this package body.

Usage Notes

The package is not referenced by any database object according to ETRM, indicating it is not the target of a database trigger, view, or dependent package in the standard product. Instead it is invoked at runtime from pricing and order management flows — typically during order entry or pricing validation when limit balances must be defaulted or refreshed for a customer or transaction. It may also be called from concurrent programs that rebuild or repair limit balance data, and from custom extensions that need to apply the same defaulting and validation semantics as the standard product.

The metadata documents that this package references one other package set and, separately, that it is referenced by one other package, so at least one standard caller exists in the pricing dependency chain. Developers integrating with limits should prefer the public API layer (QP_LIMITS_PUB) where a supported entry point exists, and treat QP_DEFAULT_LIMIT_BALANCES as an internal utility. Because the dependency list is limited to the base table and a small set of PL/SQL units, the package is relatively self-contained, but any direct call should comply with FND_API return-status and message-stack handling to avoid bypassing the standard error reporting used throughout Advanced Pricing.