Search Results call_rcv_manager




Overview
Explore in AI Chat

Overview

INV_TRX_UTIL_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). It provides the programmatic interface for creating, copying, updating, and deleting material transaction records within Oracle Inventory. The package operates on the transaction tables that form the core of Inventory's audit and cost-of-goods-sold trail, bridging user-facing transaction entry, move order processing, receiving integration, and warehouse management flows into a consistent set of write operations against MTL_MATERIAL_TRANSACTIONS and its companion tables.

The package is designated as a PUBLIC API classification, and its procedures are called from a wide range of EBS modules, including Inventory transaction entry forms, the transaction manager interfaces, and external integration code. The header comment indicates a continuous evolution of the interface, with parameters added across patchsets and eIB builds.

Key Procedures and Functions

The package exposes nine documented procedures:

  • INSERT_LINE_TRX — Creates a header- and line-level material transaction. Its extensive parameter set covers item, revision, organization, transaction action and type, subinventory and locator (including transfer equivalents), transfer organization, quantity and UOM, reason, freight and shipping attributes, cost group, LPN references (from, content, and transfer), consignment and VMI planning and owning organization attributes, secondary quantity and UOM, move order line, posting flag, and ship-to location.
  • INSERT_LOT_TRX — Inserts lot-level transaction records, referencing MTL_LOT_NUMBERS and MTL_TRANSACTION_LOTS_TEMP to associate lot-controlled items with a transaction.
  • INSERT_SER_TRX — Inserts serial-level transaction records, using MTL_SERIAL_NUMBERS and MTL_SERIAL_NUMBERS_TEMP to tie serialized units to a transaction.
  • COPY_INSERT_LINE_TRX — Copies an existing line transaction record to create a new one, the procedure most frequently referenced in searches such as "copy_insert_line_trx". It is used when a transaction must be duplicated, for example to replicate a previously posted movement without re-entering all attributes.
  • DELETE_TRANSACTION — Removes a transaction record, including its associated detail rows.
  • UPDATE_PARENT_MMTT — Updates the parent record in MTL_MATERIAL_TRANSACTIONS_TEMP, maintaining the temporary staging hierarchy used during transaction processing.
  • DELETE_LOT_SER_TRX — Deletes lot- and serial-level transaction detail rows for a given transaction.
  • CALL_RCV_MANAGER — Invokes the Receiving manager interface, bridging inventory transaction creation with RCV_TRANSACTIONS_INTERFACE and RCV_INTERFACE_GROUPS_S.
  • TRACE — A diagnostic utility used to control and emit debug tracing during package execution.

Tables Accessed

The package reads and writes the core Inventory transaction tables: MTL_MATERIAL_TRANSACTIONS and its _S (sequences) and _TEMPorary counterparts, which hold the persistent and staged transaction records. MTL_TRANSACTION_LOTS_TEMP supports lot detail staging, while MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS (with MTL_SERIAL_NUMBERS_TEMP) provide lot and serial validation and detail. MTL_SYSTEM_ITEMS supplies item validation and attribute defaults.

For receiving integration, RCV_TRANSACTIONS_INTERFACE and RCV_INTERFACE_GROUPS_S are referenced by CALL_RCV_MANAGER. WMS_DISPATCHED_TASKS links warehouse management task execution to transaction creation, and DUAL and PLITBLM are used for standard PL/SQL and utility purposes.

Usage Notes

INV_TRX_UTIL_PUB is typically invoked from Inventory transaction entry forms, move order and receiving integration flows, and custom extensions that need to create or manipulate material transactions programmatically. Because it is a public API, it is the supported entry point for custom code; direct inserts into MTL_MATERIAL_TRANSACTIONS are not recommended. With 88 dependent packages, any interface change has broad impact, so callers should pin to the documented parameter signatures and avoid relying on undocumented behavior. Typical usage patterns include copying an existing line transaction via COPY_INSERT_LINE_TRX, inserting lot and serial detail after a line transaction, and calling CALL_RCV_MANAGER when a transaction must be pushed back through the receiving interface.