Search Results split_mmtt




Overview

INV_RCV_INTEGRATION_APIS is a public Oracle E-Business Suite PL/SQL package owned by the APPS schema that encapsulates the integration logic between Oracle Inventory (INV) and Oracle Receiving (RCV) for mobile and high-volume material handling workflows. Its principal business purpose is to support License Plate Number (LPN) and container-based warehousing operations — including warehouse execution, mobile receiving, putaway, and cross-docking — within the Oracle Warehouse Management (WMS) and Advanced Supply Chain Planning footprint. The package provides programmatic insert and validation routines for LPN records, material transaction lines, lot and serial information, and sub-inventory/locator data, exposing these operations as callable APIs rather than requiring direct DML against base tables. The $Header value (INVRCVIB.pls 120.12.12010000.2, dated 2009) confirms the object is a long-standing, versioned component of the INV code family. A private mol_rec record type is declared to carry material order line attributes such as line identifiers, quantities (primary, secondary, delivered and detailed), UOM codes, item and organization identifiers, backorder delivery detail, and crossdock type, and is used across the package's internal processing.

Key Procedures and Functions

The package documents eighteen callable procedures and functions. Their purposes are as follows.

  • INSERT_WLPNI — Inserts warehouse LPN information records, carrying organization, LPN, group, parent, item, revision, lot, serial, sub-inventory and locator attributes.
  • INSERT_MTLI — Populates material transaction line interface records for subsequent processing.
  • INSERT_MSNI — Inserts material serial number interface records.
  • VALIDATE_LOT_NUMBER — Validates a supplied lot number against inventory rules.
  • VALIDATE_SERIAL_RANGE — Validates a serial number range for correctness and completeness.
  • VALIDATE_LOT_SERIAL_INFO — Performs combined lot and serial validation for an item/organization context.
  • GENERATE_LOT_NUMBER — Generates a lot number according to configured numbering rules.
  • GENERATE_SERIAL_NUMBERS — Generates serial numbers for a specified quantity or range.
  • VALIDATE_LPN — Validates that an LPN exists and is eligible for use.
  • VALIDATE_LPN_INFO — Performs broader validation of LPN attribute data.
  • GENERATE_LPN — Generates a new License Plate Number.
  • EXPLODE_LPN — Breaks an LPN down into its constituent contents.
  • VALIDATE_SUB_LOC — Validates sub-inventory and locator combinations.
  • SPLIT_LOT_SERIAL — Splits lot and/or serial quantities across transaction lines.
  • PROCESS_TRANSACTION — Drives processing of a material transaction through the interface.
  • COMPLETE_LPN_GROUP — Marks an LPN group as complete.
  • SPLIT_MO — Splits a material order/move order line into multiple transaction lines.
  • SPLIT_MMTT — Splits MTL_MATERIAL_TRANSACTIONS_TEMP records, the routine most frequently sought by users investigating temporary transaction splitting behaviour.

Tables Accessed

The package reads and writes the following APPS-synonym tables, which align with its LPN, lot/serial and transaction-processing responsibilities.

Usage Notes

INV_RCV_INTEGRATION_APIS is an internal integration API layer rather than an end-user interface. It is invoked by Oracle mobile supply chain applications, WMS-driven receiving and putaway forms, and other Inventory/Receiving APIs that need LPN, lot/serial, or transaction-splitting logic. The metadata records it as referenced by twenty other packages, indicating it sits on the dependency path for a substantial portion of INV/RCV programmatic processing. Diagnostic output is governed by the INV_DEBUG_TRACE profile option through the private print_debug helper, which routes messages to INV_MOBILE_HELPER_FUNCTIONS.TRACELOG when the profile is set to 1. Customizations should treat the package as a support-level component: calling its public procedures requires adherence to the standard p_api_version/p_init_msg_lst/x_return_status/x_msg_count/x_msg_data API signature convention. Users tracing split_mmtt should note that SPLIT_MMTT operates against MTL_MATERIAL_TRANSACTIONS_TEMP and is normally triggered implicitly during transaction processing rather than called directly.