Search Results g_serial_row_table_rec

Overview

INV_DETAIL_UTIL_PVT is a private (PVT) PL/SQL package in the APPS schema that provides the utility layer for the Inventory and Warehouse Management detailing engine. The package spec header identifies its purpose explicitly as "utilities used by the detailing engine (both inv and wms versions)." It was originally created on 10/22/99 and carries a modification history extending to bug fix 2286454 (2002) and header revision 120.4.12010000.2 dated 2008/11/10, indicating that the same package body has been carried forward unchanged through the 12.1.1 and 12.2.2 releases.

The package is not an application programming interface intended for external callers. It is invoked internally by the detailing engine to resolve and validate the transactional attributes that govern material movement: lot and serial control indicators, locator control, revision control, transaction UOMs, picking and put-away strategy identifiers, reservation eligibility, and on-hand status restrictions. The package also supports the derivation of pick detail levels, splitting of prefixed serial numbers, and the arithmetic reduction of serial quantities. Its data structures, including the request context record type and the serial row table record, are consumed by both the Oracle Inventory and WMS variants of the detailing engine.

Key Procedures and Functions

The documented interface comprises 22 procedures and functions, organized around initialization, serial number handling, output accumulation, and validation.

• VALIDATE_AND_INIT — performs the initial validation of the detailing request and populates the working context used by subsequent calls.
• INIT_OUTPUT_SERIAL_ROWS and INIT_OUTPUT_PROCESS_TBL — initialize the output collections for serial rows and general processing results.
• GET_SERIAL_NUMBERS, SEARCH_SERIAL_NUMBERS, ADD_SERIAL_NUMBER, and LOCK_SERIAL_NUMBER — retrieve, locate, append, and lock serial number records during detailing.
• SUBTRACT_SERIALS — reduces serial quantities in the working set when serial numbers are consumed or allocated.
• ADD_OUTPUT and PROCESS_OUTPUT — accumulate and finalize detailing output rows.
• COMPUTE_PICK_DETAIL_LEVEL — determines the level of detail required for the pick operation.
• SPLIT_PREFIX_NUM — parses and splits serial numbers carrying a prefix component.
• GET_LOT_EXPIRATION_DATE — returns the expiration date associated with a lot.
• BUILD_SQL — constructs dynamic SQL used by the detailing engine.
• IS_SUB_LOC_LOT_TRX_ALLOWED, IS_SERIAL_TRX_ALLOWED, IS_SUB_LOC_LOT_RESERVABLE, and IS_ONHAND_STATUS_TRX_ALLOWED — validation predicates governing whether a transaction, reservation, or on-hand status is permissible.
• GET_ORGANIZATION_CODE — returns the organization code for a given inventory organization.
• SET_MO_TRANSACT_DATE — establishes the transaction date for manufacturing order transactions.

Tables Accessed

The package accesses documented APPS synonyms spanning the inventory, serial, lot, reservation, and trading partner domains.

• MTL_TXN_REQUEST_LINES — source of the detailing request line record type (g_request_line_rec_type).
• MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_TEMP, and INV_MSN_GTEMP — serial number lookup, staging, and global temporary storage during detailing.
• MTL_LOT_NUMBERS — lot attributes including expiration dates.
• MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_ONHAND_QUANTITIES_DETAIL — transaction and on-hand quantity sources.
• MTL_RESERVATIONS — reservation validation and creation.
• MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, and MTL_PARAMETERS — locator, subinventory, and organization-level control settings.
• MTL_STATUS_TRANSACTION_CONTROL — on-hand status transaction permissions.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — customer and party information referenced in the request context.

Usage Notes

INV_DETAIL_UTIL_PVT is referenced by 17 other packages and is not directly callable from Oracle Forms or stand-alone concurrent programs. It is invoked from within the detailing engine during transaction processing of move orders, pick waves, and WMS-directed tasks that require serial, lot, locator, and revision validation. Because it is a PVT package, Oracle does not guarantee interface stability across upgrades; custom code should never call it directly. Configurations that affect its behavior include item lot and serial control codes, locator control, reservation and on-hand status rules, and the detail_serial and detail_any_serial flags in the request context. Despite the 2008 header date, the package remains compiled and available in both 12.1.1 and 12.2.2 environments. Customizations should be confined to the validation flags and control codes it reads, rather than to the package itself.