Results for “inv_rcv_integration_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.INV_RCV_INTEGRATION_PVT is a private PL/SQL package in Oracle E-Business Suite that provides the core validation and data-persistence logic used during receiving and inventory integration transactions. The package header comment identifies it as INVRCVVB.pls (revision 120.92.12010000.5), and it operates as a companion to the public INV_RCV_INTEGRATION API. Its stated responsibility is to integrate receipt, License Plate Number (LPN), lot, and serial information into the inventory transaction tables, performing structural and business-rule validation before any data is written to the interface tables. The package declares the full LPN context enumerations used across the suite — Inventory, WIP, Receiving, Stores, Pre-generated, Intransit, Vendor, Packing, Loaded for Shipment, Prepack for WIP, and Picked — along with return status constants sourced from FND_API and receipt transaction-type literals such as RETURN TO VENDOR, RETURN TO CUSTOMER, and RETURN TO RECEIVING. It also maintains package-level globals (g_lpn_group_id, g_epc_group_id) for grouping LPN and EPC records created during a transaction. A debug utility, print_debug, gates diagnostic output on the INV_DEBUG_TRACE profile option.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions. The LPN-explosion routines EXPLODE_LPN and EXPLODE_LPN_CONTENTS break a parent LPN into its constituent nested LPNs or items so downstream validation and insertion can process each child individually. CALL_ATF_API invokes the Application Transaction Framework to create or resolve the transaction grouping context. VALIDATE_LPN_INFO and VALIDATE_LPN_LOCATOR verify LPN attributes and the target locator, while VALIDATE_RECEIVING_LPN and CHECK_OVER_RECEIPT enforce receiving-specific rules such as over-receipt tolerance. INSERT_WLPNI and INSERT_MTLI persist LPN and lot/serial interface rows. SPLIT_LOT_SERIAL and VALIDATE_LOT_SERIAL_INFO — the routine matching the user's search term — govern lot and serial number validation and decomposition, the primary entry points for serialized or lot-controlled receipt lines. GET_PRIMARY_QTY derives the primary-unit quantity from transactional quantity. PROCESS_TXN orchestrates the overall integration flow, calling the validations before committing interface rows. Parameter lists are not documented in the available metadata and should be verified against the deployed source.

Tables Accessed

The package reads and writes a defined set of interface and operational tables through APPS synonyms. MTL_TRANSACTION_LOTS_INTERFACE, MTL_TRANSACTION_LOTS_TEMP, MTL_SERIAL_NUMBERS_INTERFACE, and MTL_SERIAL_NUMBERS_TEMP are written with validated lot and serial rows. MTL_MATERIAL_TRANSACTIONS, its _S and _TEMP variants, and MTL_MATERIAL_TRANSACTIONS_TEMP hold the inventory transaction records. MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, and MTL_ONHAND_QUANTITIES_DETAIL are consulted to confirm existing lot/serial definitions and on-hand balances. MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV supply item attributes such as lot and serial control codes; MTL_PARAMETERS and MTL_INTERORG_PARAMETERS supply organization and inter-org setup. MO_GLOB_ORG_ACCESS_TMP supports organization-access checks.

Usage Notes

INV_RCV_INTEGRATION_PVT is classified as a private package and is referenced by six other packages; it is not intended for direct customer invocation. It is called at runtime through the public INV_RCV_INTEGRATION API, typically from Receiving forms, mobile supply chain applications, and the receiving transaction open interface. Debugging is enabled by setting the INV_DEBUG_TRACE profile option to a non-zero value, which activates the print_debug output. Developers extending receiving integrations should treat this package as read-only and route custom calls through the supported public API layer to remain compatible across 12.1.1 and 12.2.2 releases.