Search Results wsm_starting_lots_interface




Overview
Explore in AI Chat

Overview

The WSM_STARTING_LOTS_INTERFACE table is a critical interface object within the Oracle E-Business Suite (EBS) Shop Floor Management (WSM) module. It functions as a staging area for data related to the starting lots involved in inventory lot transactions, specifically lot splits and merges. As a child table to WSM_LOT_SPLIT_MERGES_INTERFACE, it holds the detailed lot, quantity, and location information for the source lots that will be consumed in a transaction. Its primary role is to facilitate the import and validation of lot transaction data via the Open Interface before the data is processed into the core inventory tables, ensuring data integrity and supporting automated manufacturing execution processes.

Key Information Stored

The table stores transactional details for each source lot. While the full column list is not provided in the metadata, the documented primary and foreign key relationships highlight its essential data elements. The composite primary key (HEADER_ID, LOT_NUMBER) uniquely identifies a starting lot record within a specific transaction header. The HEADER_ID column links the record to its parent transaction in WSM_LOT_SPLIT_MERGES_INTERFACE. Critical inventory attributes are stored, including the LOT_NUMBER itself, the ORGANIZATION_ID, and location details via SUBINVENTORY_CODE and LOCATOR_ID, which reference MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS, respectively. The table would also typically store the TRANSACTION_QUANTITY for the starting lot.

Common Use Cases and Queries

The primary use case is the batch import of lot split and merge transactions from external manufacturing execution systems (MES) or legacy data sources. Data is inserted into this interface table along with its parent header table, and then the standard WSM Lot Split/Merge Open Interface program is executed to validate and process the records. A common diagnostic query involves checking for pending interface records that have failed validation or remain unprocessed. For example:

  • SELECT header_id, lot_number, organization_id, subinventory_code FROM wsm_starting_lots_interface WHERE header_id IN (SELECT header_id FROM wsm_lot_split_merges_interface WHERE process_flag = 'ERROR');

This table is also pivotal for reporting on the source data of lot transactions before they are committed to inventory history.

Related Objects

The table has defined foreign key relationships with several core EBS tables, as documented in the metadata:

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

Successful processing by the interface program will ultimately result in transactions posted to core inventory tables such as MTL_MATERIAL_TRANSACTIONS and updates to MTL_TRANSACTION_LOTS_INTERFACE.