Search Results pjm_unit_serial_history

Overview

The MTL_SERIAL_NUMBERS table is a core transactional table within the Oracle E-Business Suite Inventory (INV) module. It serves as the master repository for all serialized inventory items across the enterprise. Its primary role is to store and track the unique identity, current status, and location of each individual serial number throughout its lifecycle. This table is fundamental to serial number control, enabling traceability from receipt through internal transactions to final shipment. The data integrity is enforced by a primary key that uniquely identifies a serial number by the combination of the SERIAL_NUMBER itself, the INVENTORY_ITEM_ID, and the CURRENT_ORGANIZATION_ID, ensuring a serial number is unique for an item within a given organization.

Key Information Stored

The table's columns can be categorized into several key areas of information. The primary identification is held by SERIAL_NUMBER, INVENTORY_ITEM_ID, and CURRENT_ORGANIZATION_ID. Status and location are tracked through columns like CURRENT_SUBINVENTORY_CODE, CURRENT_LOCATOR_ID, LOT_NUMBER, REVISION, and STATUS_ID. Transactional history is maintained via LAST_TRANSACTION_ID, LAST_TXN_SOURCE_TYPE_ID, and various date stamps (e.g., CREATION_DATE, LAST_UPDATE_DATE). For traceability and genealogy, the table supports parent-child relationships for assembled units through PARENT_SERIAL_NUMBER, PARENT_ITEM_ID, and ORIGINAL_WIP_ENTITY_ID. Additional vendor and unit information can be stored in ORIGINAL_UNIT_VENDOR_ID and END_ITEM_UNIT_NUMBER. The LPN_ID column links the serial number to a specific license plate for Warehouse Management Systems (WMS) integration.

Common Use Cases and Queries

This table is central to numerous operational and reporting processes. Common use cases include generating serial number status reports, tracing the history of a specific serial unit, validating serial numbers during transactions, and reconciling physical inventory counts. A fundamental query retrieves the current status and location of serial numbers for a specific item:

• SELECT msn.serial_number, msn.current_subinventory_code, msn.current_locator_id, msn.lot_number, ms.status_code FROM mtl_serial_numbers msn, mtl_material_statuses_tl ms WHERE msn.inventory_item_id = :item_id AND msn.current_organization_id = :org_id AND msn.status_id = ms.status_id AND ms.language = USERENV('LANG');

Another critical pattern finds the complete transaction history for a serial number by joining with MTL_MATERIAL_TRANSACTIONS using the LAST_TRANSACTION_ID and traversing the transaction interface tables. For genealogy, queries use self-joins on PARENT_SERIAL_NUMBER to build a hierarchical view of assembled serials.

Related Objects

As indicated by its extensive foreign key relationships, MTL_SERIAL_NUMBERS is deeply integrated with the EBS supply chain fabric. It has direct foreign key references to major base tables, including MTL_SYSTEM_ITEMS_B (for the item definition), MTL_LOT_NUMBERS, MTL_ITEM_REVISIONS_B, MTL_SECONDARY_INVENTORIES, and MTL_ITEM_LOCATIONS. Its transactional link is to MTL_MATERIAL_TRANSACTIONS via LAST_TRANSACTION_ID. For manufacturing and work order processes, it relates to WIP_ENTITIES. The table also integrates with other modules through references to AP_SUPPLIERS (Purchasing), PJM_UNIT_NUMBERS (Project Manufacturing), WMS_LICENSE_PLATE_NUMBERS (Warehouse Management), and AHL_WORKORDER_MTL_TXNS (Complex Maintenance, Repair, and Overhaul). This network of relationships underscores its role as the central hub for serialized item tracking.