Search Results invoice_interface_status_code




Overview
Explore in AI Chat

Overview

APPS.OE_ACCOUNTING is a PL/SQL package body in the Oracle Order Management (ONT) module of Oracle E-Business Suite, positioned as an interoperability and accounting utility that bridges Order Entry and Oracle Receivables (AR). Its header signature ($Header: OEXACCTB.pls 115.2 1999/11/15) identifies it as an original seed Oracle-delivered object carried unchanged from the earlier OE code line into Release 12.1.1 and 12.2.2. The package belongs to the API classification OTHER in ETRM, meaning it is not a public, supported open interface but a supporting library invoked internally by Oracle application code. The central business problem it solves is determining how much of a customer commitment remains un-invoiced, that is, the value of order lines tied to a commitment that have not yet been transferred to Receivables. This value is required by AutoInvoice and related AR processing so that commitment balances and multi-period invoicing arrangements remain consistent between the two modules.

Key Procedures and Functions

ETRM documents a single function, GET_UNINVOICED_COMMITMENT_BAL. Its purpose is to return the total uninvoiced commitment balance for a given commitment, keyed by the customer transaction identifier passed by the calling Receivables program. The function is deliberately dual-mode: it first calls OE_INSTALL.Get_Active_Product to detect whether the active Order Management product is the newer ONT code line or the legacy OE code line, then branches accordingly.

  • New OE (ONT) path — sums ordered quantity multiplied by unit selling price from order lines associated with the commitment, excluding return lines and excluding lines whose invoice interface status indicates they have already been interfaced to AR.
  • Old OE path — sums the residual quantity (ordered minus cancelled minus invoiced) multiplied by selling price, restricted to regular and detail line types.

The function returns a NUMBER and initializes its accumulator to zero, so a commitment with no qualifying lines yields 0 rather than NULL. No parameter list is documented beyond the single customer transaction identifier; the ETRM record does not enumerate it further and it should not be assumed.

Tables Accessed

The only documented table reference is OE_ORDER_LINES, accessed through APPS synonyms in the ONT branch of the function. The table is read, never written: the package is a pure calculation utility. The query filters on the commitment identifier, excludes return lines via line category, and—critically in the context of the search term invoice_interface_status_code—excludes any line whose invoice interface status equals 'YES', meaning the line has already been interfaced to Receivables. The legacy branch reads the obsolete SO_LINES table, which exists only in pre-11i installations.

Usage Notes

OE_ACCOUNTING is not invoked directly from a form or concurrent program. It is called by Oracle Receivables during commitment-based invoicing and revenue processing, in the same manner as other OE-provided interoperability functions. ETRM records zero dependent packages, indicating that it is a leaf-level utility with no downstream callers inside PL/SQL, which is consistent with its role as a provider rather than a consumer. The presence of the OE_INSTALL version switch means the same code can execute against installations that have not yet migrated to the ONT schema, and developers writing custom extensions against commitments should mirror that check rather than assuming OE_ORDER_LINES is always the source. Because the object is classified OTHER rather than a public API, customizations should not call it directly; supported alternatives such as the Order Management public APIs should be preferred. The invoice_interface_status_code predicate is the operative control within this package: it is the field that separates genuinely uninvoiced commitment value from value already recognized in Receivables.