Search Results wsm_resulting_lots_interface




Overview
Explore in AI Chat

Overview

The WSM_RESULTING_LOTS_INTERFACE table is a critical data interface within Oracle E-Business Suite's Shop Floor Management (WSM) module. It functions as a staging area for processing lot split and merge transactions within Inventory. Specifically, it holds detailed information about the new or "resulting" lots that are created as an output of lot split or merge operations. As documented, it is explicitly a child table to WSM_LOT_SPLIT_MERGES_INTERFACE, which holds the header-level transaction data. This interface structure allows for the batch import and validation of complex lot transactions before they are posted to the core inventory tables, ensuring data integrity in manufacturing and inventory execution processes.

Key Information Stored

The table's primary purpose is to define the attributes of each resulting lot from a split or merge. The composite primary key, consisting of HEADER_ID and LOT_NUMBER, uniquely identifies each resulting lot record within the context of its parent transaction. Key columns include HEADER_ID, which links to the parent transaction in WSM_LOT_SPLIT_MERGES_INTERFACE; LOT_NUMBER, which specifies the identifier for the new lot; and PRIMARY_QUANTITY, which defines the quantity assigned to this resulting lot. The table also stores inventory location details via SUBINVENTORY_CODE and LOCATOR_ID, both validated against MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS, respectively, within the specified ORGANIZATION_ID.

Common Use Cases and Queries

The primary use case is the programmatic execution of lot splits and merges, often integrated from external manufacturing execution systems (MES) or custom scripts. A typical process involves inserting a parent record into WSM_LOT_SPLIT_MERGES_INTERFACE and its child resulting lot records into this table, followed by calling the standard interface import program. For reporting and troubleshooting pending interface transactions, common queries involve joining to the parent interface table and validating location references. A sample diagnostic query is:

  • SELECT rli.lot_number, rli.primary_quantity, rli.subinventory_code, lsmi.parent_lot_number FROM wsm_resulting_lots_interface rli INNER JOIN wsm_lot_split_merges_interface lsmi ON rli.header_id = lsmi.header_id WHERE lsmi.process_status = 'PENDING';

Related Objects

This table maintains defined foreign key relationships with several core EBS objects, ensuring referential integrity for the data it processes. The documented relationships are:

  • WSM_LOT_SPLIT_MERGES_INTERFACE: The direct parent table. Joined via WSM_RESULTING_LOTS_INTERFACE.HEADER_ID = WSM_LOT_SPLIT_MERGES_INTERFACE.HEADER_ID.
  • MTL_ITEM_LOCATIONS: Validates the locator. Joined via WSM_RESULTING_LOTS_INTERFACE.LOCATOR_ID and ORGANIZATION_ID.
  • MTL_SECONDARY_INVENTORIES: Validates the subinventory. Joined via WSM_RESULTING_LOTS_INTERFACE.SUBINVENTORY_CODE and ORGANIZATION_ID.
  • WSM_PARAMETERS: Validates the organization context via WSM_RESULTING_LOTS_INTERFACE.ORGANIZATION_ID.

Successful processing by the interface concurrent program ultimately posts transactions to core Inventory tables such as MTL_TRANSACTION_LOTS_INTERFACE and MTL_MATERIAL_TRANSACTIONS.