Search Results inv_comingling_utils




Overview
Explore in AI Chat

Overview

APPS.INV_COMINGLING_UTILS is an Oracle E-Business Suite inventory utility package that supports co-mingling validation during material transactions and cost group assignments. Co-mingling occurs when material from different cost groups becomes physically mixed within the same storage location, lot context, or LPN, creating valuation ambiguity under a cost group–enabled organization. In Oracle Inventory, cost groups provide a method for segregating and valuing on-hand balances when items are held in subinventories or locators where multiple cost groups coexist. The INV_COMINGLING_UTILS package encapsulates the business logic needed to determine whether a proposed transaction will result in such mixing, and to return the minimum number of co-mingling instances that the transaction data would produce.

The package is classified as OTHER within the ETRM catalog and is owned by the APPS schema. The header comment attributes the source file to INVCOMUS.pls, with an original header revision dated 2005/05/25, indicating that the package has been stable across the 12.1.1 and 12.2.2 release streams and that the core logic predates the 12.2 architecture. It is referenced by four other inventory packages, reflecting its role as a shared utility rather than a standalone entry point.

Key Procedures and Functions

The documented interface exposes three PL/SQL units, of which COMINGLE_CHECK is the principal and most fully described procedure.

  • COMINGLE_CHECK — Evaluates a prospective material transaction or cost group assignment and reports whether co-mingling will result. It accepts the organization, item, revision, lot, subinventory, locator, LPN, and cost group that define the transactional context, and returns a standard API-style result set: x_return_status (success, error, or unexpected error), x_msg_count, and x_msg_data for message propagation. In addition, it returns x_comingling_occurs, a flag whose value of Y indicates that co-mingling results from the transaction and N indicates that it does not, and x_count, which reports the minimum number of co-mingling instances for the supplied data.
  • Additional packaged units — Two further PL/SQL units complete the package. The documented source excerpt does not expose their specifications; based on the package’s stated purpose they support the co-mingling determination performed by COMINGLE_CHECK, such as resolving cost group context or computing instance counts.

Tables Accessed

The package reads and, where applicable, writes the following tables through APPS synonyms:

  • MTL_MATERIAL_TRANSACTIONS_TEMP — the pending transaction interface, supplying the transaction rows under evaluation.
  • MTL_ONHAND_QUANTITIES_DETAIL — existing on-hand detail used to determine the cost groups already present at the target location.
  • MTL_SECONDARY_INVENTORIES — subinventory attributes and the source/destination context of the transaction.
  • MTL_SYSTEM_ITEMS — item attributes relevant to cost grouping and lot control.
  • MTL_TRANSACTION_LOTS_TEMP — lot-level transaction detail, including lot and revision information.
  • MTL_SERIAL_NUMBERS_TEMP — serial number detail associated with the pending transaction.
  • WMS_LPN_CONTENTS — contents of the license plate number into which material is packed, used to detect mixing within an LPN.
  • DUAL — used for scalar evaluations and default value resolution.

Usage Notes

INV_COMINGLING_UTILS is a backend utility rather than a user-facing component. It is typically invoked from within the inventory transaction processing flow — most commonly by the transaction manager and its related validation packages during receipts, subinventory transfers, staging transfers, and inter-organization transfers — to enforce cost group segregation rules before a transaction is allowed to proceed. Because four other packages reference it, customizations and extensions that hook into inventory transaction validation should be aware that COMINGLE_CHECK may already be executing in the call stack. Custom code invoking the procedure directly should observe the standard return-status contract and inspect both the message list and the x_comingling_occurs flag before committing any transaction that would alter cost group composition. The package is consistent across Oracle EBS 12.1.1 and 12.2.2; no 12.2-specific behavioral divergence is documented.