Search Results lot_number_table

Overview

APPS.INV_LOT_TRX_VALIDATION_PUB is a public PL/SQL package in Oracle E-Business Suite (documented for both 12.1.1 and 12.2.2) that centralizes validation logic for lot-based inventory transactions. Its principal business function is to enforce the integrity rules that govern lot split, lot merge, and lot translate operations before they are written to the transaction interface and ultimately posted to inventory. The package verifies that all records participating in a lot transaction share the same organization and item, that a split presents exactly one parent lot with at least two resultant lots, and that a merge presents at least two parent lots with one resultant lot. Beyond structural validation, it validates serial numbers, LPN information, material status, cost groups, quantities, descriptive lot and serial attributes, and organization context. It also exposes a utility (COMPUTE_LOT_EXPIRATION) for deriving lot expiration dates, reflecting the package's role as the single authority for lot and serial transaction checks in the Inventory module.

Key Procedures and Functions

The metadata documents fifteen public procedures and functions:

• VALIDATE_LOTS – Validates lot transaction records (split, merge, translate), checking organization/item consistency and parent/resultant lot counts.
• VALIDATE_SERIALS – Validates serial number records associated with the lot transaction.
• VALIDATE_START_LOT – Validates the source (starting) lot for split or translate transactions.
• VALIDATE_RESULT_LOT – Validates the resulting lot records produced by the transaction.
• VALIDATE_LOT_TRANSLATE – Applies validation rules specific to lot translation (renumbering) operations.
• VALIDATE_LPN_INFO – Validates license plate number (LPN) information linked to the lot transaction.
• VALIDATE_MATERIAL_STATUS – Validates material status codes to ensure only permissible statuses are applied.
• VALIDATE_COST_GROUPS – Validates cost group assignments for the lots involved.
• VALIDATE_QUANTITY – Validates transaction quantities, including consistency between parent and resultant lots.
• VALIDATE_ATTRIBUTES – Validates user-defined lot attribute values against configured flexfield context.
• VALIDATE_SERIAL_ATTRIBUTES – Validates user-defined serial attribute values.
• VALIDATE_ORGANIZATION – Validates the organization context of the transaction.
• COMPUTE_LOT_EXPIRATION – Derives or computes the expiration date for a lot, typically from item shelf-life attributes and transaction date.
• GET_ORG_INFO – Returns organization-level information needed during validation.
• UPDATE_ITEM_SERIAL – Updates item serial information as a result of the transaction.

Global collection types (NUMBER_TABLE, LOT_NUMBER_TABLE, SERIAL_NUMBER_TABLE, PARENT_LOT_TABLE, PARENT_LOC_TABLE, PARENT_SUB_TABLE, and the attribute tables) support bulk validation of lot/serial records.

Tables Accessed

The package reads and writes the following key tables via APPS synonyms:

• MTL_TRANSACTION_LOTS_INTERFACE / MTL_TRANSACTIONS_INTERFACE / MTL_MATERIAL_TRANSACTIONS_TEMP – transaction staging for validating and updating lot records.
• MTL_TRANSACTION_LOTS_TEMP – temporary lot transaction data used during validation.
• MTL_LOT_NUMBERS / MTL_SERIAL_NUMBERS – master lot and serial definitions.
• MTL_ITEM_LOCATIONS – subinventory and locator validation.
• MTL_SECONDARY_INVENTORIES / MTL_PARAMETERS – subinventory and organization defaults.
• MTL_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS_B – item attributes including lot control and shelf life.
• MTL_FLEX_CONTEXT – descriptive flexfield context for attribute validation.
• WIP_ENTITIES – work-in-process entity validation.
• WMS_LICENSE_PLATE_NUMBERS – LPN validation for warehouse-managed operations.
• ALL_TAB_COLUMNS – metadata lookup used to introspect column definitions.

Usage Notes

INV_LOT_TRX_VALIDATION_PUB is invoked by Inventory transaction forms and concurrent programs prior to commit, and is referenced by five other packages, indicating it is a shared validation service rather than a standalone entry point. The COMPUTE_LOT_EXPIRATION routine, which the user searched for, is called to populate expiration dates during lot creation and receipt processing. Customizations should call these APIs rather than duplicating validation logic, and should avoid direct DML against the interface tables outside the supported API path.