Search Results mtl_lot_numbers_temp

Overview

APPS.INV_COMINGLING_UTILS is a technical utility package in Oracle E-Business Suite Inventory (INV) that determines whether a given material transaction will cause lot, revision, or serial-controlled inventory to be co-mingled within a locator. Co-mingling occurs when on-hand material sharing the same item, revision, lot, locator, and subinventory attributes is combined with material of differing controlled attributes as a result of a receipt, subinventory transfer, staging transfer, or inter-organization transfer. The package evaluates the prospective transaction against existing on-hand and pending transaction data, then returns whether co-mingling will occur and the minimum number of co-mingling instances for the supplied context. This validation supports inventory accuracy, lot genealogy, and quality traceability in regulated environments where mixing controlled lots is prohibited or requires explicit handling. The package body is delivered under the source header INVCOMUB.pls (version 120.4, dated 2005/12/06) and is classified as an OTHER API, indicating a supporting utility rather than a public transactional interface.

Key Procedures and Functions

The documented metadata exposes a single public procedure, COMINGLE_CHECK, supported by one internal helper, PRINT_DEBUG. ETRM records three procedures/functions in total for this package body.

• COMINGLE_CHECK — The core validation routine. It accepts the transaction context (organization, inventory item, revision, lot number, subinventory, and locator) and returns a return status, message count, and message data in the standard EBS API error-handling pattern. Its output flag x_comingling_occurs indicates whether co-mingling results from the transaction, and x_count reports the minimum number of co-mingling instances for the given data. Parameter semantics distinguish receipt, subinventory/staging transfer, and inter-organization transfer scenarios by how source and destination organizations and subinventories are interpreted.
• PRINT_DEBUG — A diagnostic helper that writes trace output through INV_LOG_UTIL when the INV_DEBUG_TRACE profile option is enabled. It is used to instrument the package during troubleshooting and is not intended for direct invocation by application code.

Tables Accessed

The package reads and, in the case of temporary transaction tables, may write or interrogate the following objects through APPS synonyms:

• MTL_MATERIAL_TRANSACTIONS_TEMP — Pending transaction rows used to detect co-mingling that would result from transactions not yet posted.
• MTL_TRANSACTION_LOTS_TEMP — Pending lot assignments associated with temporary transactions. Because users searching this package frequently arrive via mtl_lot_numbers_temp, it is worth clarifying that the documented package references the transaction lot temporary table, not the legacy base lot table; the lot master itself is MTL_LOT_NUMBERS.
• MTL_ONHAND_QUANTITIES_DETAIL — Existing on-hand balances by locator, lot, revision, and subinventory, which form the basis for co-mingling comparison.
• MTL_SECONDARY_INVENTORIES — Subinventory definitions, used to interpret the transaction subinventory context.
• MTL_SYSTEM_ITEMS — Item attribute validation, including control levels that determine whether lot, revision, or serial co-mingling is relevant.
• MTL_SERIAL_NUMBERS_TEMP — Pending serial number data for serialized items.
• WMS_LPN_CONTENTS — License plate number contents used in warehouse-managed (WMS) environments to evaluate LPN-level co-mingling.
• DUAL — Standard PL/SQL invocation support.

Usage Notes

INV_COMINGLING_UTILS is an internal utility invoked by other inventory packages rather than called directly from forms or concurrent programs. ETRM records it as referenced by four other packages, which perform the orchestration and error handling around COMINGLE_CHECK. Typical invocation points include receipt processing, subinventory and staging transfers, and inter-organization transfers where the transaction logic must verify whether controlled material can be combined in the target locator. The profile option INV_DEBUG_TRACE controls diagnostic tracing at level 1. Because the package operates on temporary transaction tables, it must be called within the same transaction context as the pending material movement. Customers and integrators should not call this package directly; instead, they should invoke the owning public inventory APIs, leaving co-mingling enforcement to the standard validation flow.