Search Results wsm_sm_starting_lots




Overview

The WSM_SM_STARTING_LOTS table is a core transactional entity within Oracle E-Business Suite's Shop Floor Management (WSM) module, specifically for versions 12.1.1 and 12.2.2. As the base table for Starting Lots for Inventory Lot Transactions in OSFM (Oracle Shop Floor Management), it plays a critical role in tracking and managing the source lots used in manufacturing lot-based transactions. Its primary function is to record the specific lot numbers and their associated inventory locations that serve as the starting point for operations such as lot splits and merges. This data is essential for maintaining complete lot genealogy, ensuring inventory accuracy, and supporting traceability requirements within a discrete manufacturing environment.

Key Information Stored

The table's structure is designed to link a manufacturing transaction to the precise inventory lots it consumes. The primary key is a composite of TRANSACTION_ID and LOT_NUMBER, ensuring a unique record for each lot involved in a given transaction. Key columns include TRANSACTION_ID, which links to the parent transaction in WSM_LOT_SPLIT_MERGES, and LOT_NUMBER, which identifies the specific inventory lot being used. Critical inventory context is provided by ORGANIZATION_ID, SUBINVENTORY_CODE, and LOCATOR_ID, which pinpoint the exact physical or logical location of the lot within the inventory structure. Other columns typically track quantities, revision, and other lot attributes necessary for the transaction's execution and audit.

Common Use Cases and Queries

This table is central to reporting and troubleshooting lot genealogy and material consumption in manufacturing. A common use case is tracing the source lots consumed in a finished assembly lot. For instance, to identify all starting lots used for a specific lot split or merge transaction, one would query this table using the TRANSACTION_ID. Another critical scenario is inventory reconciliation, where analysts verify that lot quantities consumed in manufacturing align with inventory deductions. A sample query to retrieve starting lot details for a transaction would be:

  • SELECT transaction_id, lot_number, subinventory_code, locator_id FROM wsm_sm_starting_lots WHERE transaction_id = :p_transaction_id;

Reporting often involves joining this table to WSM_LOT_SPLIT_MERGES for transaction details and to MTL_SYSTEM_ITEMS_B for item descriptions, providing a complete view of material movement.

Related Objects

The WSM_SM_STARTING_LOTS table maintains defined foreign key relationships with several fundamental inventory and manufacturing tables, as documented in the ETRM. These relationships are crucial for data integrity and join logic:

  • WSM_LOT_SPLIT_MERGES: Linked via TRANSACTION_ID. This is the primary parent table, containing the header details of the lot split or merge operation for which this table records the source material.
  • MTL_SECONDARY_INVENTORIES: Linked via SUBINVENTORY_CODE and ORGANIZATION_ID. Validates the subinventory from which the starting lot was sourced.
  • MTL_ITEM_LOCATIONS: Linked via LOCATOR_ID and ORGANIZATION_ID. Validates the specific locator within the subinventory.
  • WSM_PARAMETERS: Linked via ORGANIZATION_ID. Ensures the organization is defined within the Shop Floor Management setup.

These relationships position WSM_SM_STARTING_LOTS as a key junction between transactional manufacturing data and the core inventory master and transactional tables.

  • Table: WSM_SM_STARTING_LOTS 12.2.2

    owner:WSM,  object_type:TABLE,  fnd_design_data:WSM.WSM_SM_STARTING_LOTS,  object_name:WSM_SM_STARTING_LOTS,  status:VALID,  product: WSM - Shop Floor Managementdescription: Base table for Starting Lots for Inventory Lot Transactions in OSFM. ,  implementation_dba_data: WSM.WSM_SM_STARTING_LOTS

  • Table: WSM_SM_STARTING_LOTS 12.1.1

    owner:WSM,  object_type:TABLE,  fnd_design_data:WSM.WSM_SM_STARTING_LOTS,  object_name:WSM_SM_STARTING_LOTS,  status:VALID,  product: WSM - Shop Floor Managementdescription: Base table for Starting Lots for Inventory Lot Transactions in OSFM. ,  implementation_dba_data: WSM.WSM_SM_STARTING_LOTS

  • Table: WSM_LOT_SPLIT_MERGES 12.1.1

    owner:WSM,  object_type:TABLE,  fnd_design_data:WSM.WSM_LOT_SPLIT_MERGES,  object_name:WSM_LOT_SPLIT_MERGES,  status:VALID,  product: WSM - Shop Floor Managementdescription: Base table for Lot based Inventory Transactions - Header Information. ,  implementation_dba_data: WSM.WSM_LOT_SPLIT_MERGES

  • Table: WSM_LOT_SPLIT_MERGES 12.2.2

    owner:WSM,  object_type:TABLE,  fnd_design_data:WSM.WSM_LOT_SPLIT_MERGES,  object_name:WSM_LOT_SPLIT_MERGES,  status:VALID,  product: WSM - Shop Floor Managementdescription: Base table for Lot based Inventory Transactions - Header Information. ,  implementation_dba_data: WSM.WSM_LOT_SPLIT_MERGES

  • Table: WSM_PARAMETERS 12.1.1

    owner:WSM,  object_type:TABLE,  fnd_design_data:WSM.WSM_PARAMETERS,  object_name:WSM_PARAMETERS,  status:VALID,  product: WSM - Shop Floor Managementdescription: To define an organization parameter for OSFM, the organization should satisfy the following conditions;1. Standard Costing organization.2. LotNumber Uniqueness in Inventory parameters should be NONE.3. LotNumber Default Type in WIP paramete ,  implementation_dba_data: WSM.WSM_PARAMETERS

  • Table: WSM_PARAMETERS 12.2.2

    owner:WSM,  object_type:TABLE,  fnd_design_data:WSM.WSM_PARAMETERS,  object_name:WSM_PARAMETERS,  status:VALID,  product: WSM - Shop Floor Managementdescription: To define an organization parameter for OSFM, the organization should satisfy the following conditions;1. Standard Costing organization.2. LotNumber Uniqueness in Inventory parameters should be NONE.3. LotNumber Default Type in WIP paramete ,  implementation_dba_data: WSM.WSM_PARAMETERS