Search Results get_uninvoiced_commitment_bal




Overview

OE_ACCOUNTING is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its documented role is narrow and interoperability-focused: it exposes accounting-related calculation logic from Oracle Order Entry (OE) so that Oracle Receivables (AR) and other calling modules can obtain commitment balances without querying Order Entry tables directly. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the definer, an appropriate choice for a cross-module API invoked from multiple product schemas.

The package carries the API classification OTHER in the ETRM 12.2.2 repository, which reflects that it is not a full business API with a generated PL/SQL specification, but rather a targeted utility surface. The historical header comment in the source identifies it as a facility provided by Order Entry for interoperability between the older and newer Order Entry code lines, confirming that its purpose is backward compatibility within the product family rather than new functional development.

Key Procedures and Functions

Only one documented function is exposed by this package.

  • GET_UNINVOICED_COMMITMENT_BAL — Returns a numeric value representing the uninvoiced commitment balance for a given commitment. The function accepts the customer transaction identifier as its input parameter and is described as being called by Oracle Receivables. Its purpose is to calculate the total of order lines associated with a particular commitment that have not yet been interfaced to AR. The function therefore answers the question "how much of this commitment remains unbilled?" from the Order Entry perspective, supplying AR with a figure it cannot derive from its own tables because the qualifying order lines reside in OE. The source declares a WNDS and WNPS purity pragma, indicating that the function does not write database state or package state and is safe for use within SQL statements and read-consistent queries.

No other procedures or functions are documented for this package in the ETRM metadata.

Tables Accessed

The documented table reference for OE_ACCOUNTING is OE_ORDER_LINES, accessed through an APPS synonym. This access is consistent with the stated calculation: the uninvoiced commitment balance is defined as the total of order lines linked to a commitment that have not yet been interfaced to Receivables. The function reads order line records to identify the lines belonging to the commitment, evaluates whether those lines have been passed to AR, and aggregates the remaining amount. Because the purity pragma confirms no writes, OE_ORDER_LINES is read only. Related Order Entry tables such as order headers, commitment records, and AR interface staging tables may be joined internally in the implementation, but only OE_ORDER_LINES is documented in the ETRM repository.

Usage Notes

The primary documented consumer of this package is Oracle Receivables, which invokes GET_UNINVOICED_COMMITMENT_BAL to obtain commitment balances for invoicing and reconciliation processing. The package is not referenced by any other documented package in the repository, so its call surface is deliberately limited.

Typical invocation patterns include:

  • Called from AR code or AR-adjacent logic when a customer transaction or commitment requires an uninvoiced balance figure supplied by Order Entry.
  • Callable from custom PL/SQL in the APPS schema when a report or extension must reproduce the same interoperability calculation.
  • Suitable for use inside SQL because of the WNDS/WNPS purity guarantees, though callers should validate that the returned value reflects lines in an interim state between Order Entry and Receivables.

Because the function is declared AUTHID CURRENT_USER, custom callers must have the necessary privileges on the underlying APPS synonyms. Integrity impact is LOW, as the function performs no data modification. The package should be treated as a stable compatibility interface; new development in the 12.1.1 and 12.2.2 code lines is expected to use current Order Entry and Receivables APIs rather than extending this package.