Search Results wsm_lot_split_merges




Overview
Explore in AI Chat

Overview

The WSM_LOT_SPLIT_MERGES table is a core transactional entity within the Oracle E-Business Suite (EBS) Shop Floor Management (WSM) module. It serves as the primary header table for recording and managing lot-based inventory transactions, specifically those involving the splitting of a parent lot into multiple child lots or the merging of multiple source lots into a single resultant lot. This table is fundamental to the lot control and traceability features in manufacturing and inventory operations, providing the master record for each discrete split or merge event. Its integrity is critical for maintaining accurate inventory balances, lot genealogy, and compliance with traceability requirements in regulated industries.

Key Information Stored

As the header table, WSM_LOT_SPLIT_MERGES stores the overarching attributes of each transaction. The primary key, TRANSACTION_ID, uniquely identifies each split or merge event. The table links the transaction to the specific inventory organization via the ORGANIZATION_ID foreign key to WSM_PARAMETERS. It also captures the business rationale for the operation through the REASON_ID, which references the MTL_TRANSACTION_REASONS table. While the specific detail columns are not enumerated in the provided metadata, typical header information in such a table would include transaction dates, reference numbers, the user who performed the action, and status flags. The detailed lot information—specifically the starting (source) lots and the resulting (destination) lots—is stored in the related child tables, WSM_SM_STARTING_LOTS and WSM_SM_RESULTING_LOTS.

Common Use Cases and Queries

This table is central to auditing, reporting, and process inquiries related to lot transformations. Common operational queries involve tracing the history of a specific lot to understand its origins from a split or merge. For reporting, one might join this header with its detail tables to generate a summary of all split/merge activities within a date range for a given organization. A typical analytical query pattern would be:

  • Identifying all transactions for a specific lot number by joining WSM_LOT_SPLIT_MERGES with WSM_SM_STARTING_LOTS or WSM_SM_RESULTING_LOTS on TRANSACTION_ID.
  • Generating an audit report of transactions performed by a particular user, including the transaction reason.
  • Troubleshooting inventory discrepancies by verifying that all split/merge header records have corresponding and consistent detail records in the related tables.

Related Objects

The WSM_LOT_SPLIT_MERGES table exists within a defined relational schema, as evidenced by its foreign key constraints. It references master data tables and is referenced by transactional detail tables.

  • Referenced Tables (Foreign Keys):
    • MTL_TRANSACTION_REASONS: Joined via WSM_LOT_SPLIT_MERGES.REASON_ID to provide the descriptive reason for the split or merge.
    • WSM_PARAMETERS: Joined via WSM_LOT_SPLIT_MERGES.ORGANIZATION_ID to validate and link to the organizational context.
  • Referencing Tables (Child Tables):
    • WSM_SM_STARTING_LOTS: References WSM_LOT_SPLIT_MERGES.TRANSACTION_ID. This table holds the specific lot numbers and quantities that were the sources (inputs) for the transaction.
    • WSM_SM_RESULTING_LOTS: References WSM_LOT_SPLIT_MERGES.TRANSACTION_ID. This table holds the specific lot numbers and quantities that were created (outputs) from the transaction.