Search Results wsm_split_merge_transactions




Overview
Explore in AI Chat

Overview

The WSM_SPLIT_MERGE_TRANSACTIONS table is a core transactional data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Shop Floor Management (WSM) module. It functions as the primary header table for recording Work in Process (WIP) lot split and merge transactions within the Oracle Shop Floor Management (OSFM) application. This table is essential for maintaining the integrity and audit trail of lot quantity adjustments, which are fundamental operations in discrete and process manufacturing for managing production lots, sub-lots, and their consolidation.

Key Information Stored

The table's primary key is the TRANSACTION_ID, which uniquely identifies each split or merge transaction header. As indicated by the documented foreign key relationships, the table stores critical contextual information for each transaction. The ORGANIZATION_ID links the transaction to a specific manufacturing organization, enforcing data isolation and referencing the WSM_PARAMETERS table. The REASON_ID column provides a link to the MTL_TRANSACTION_REASONS table, allowing users to assign a predefined business reason (e.g., "Quality Hold Split," "Consolidation for Shipping") to the operation for reporting and compliance. While the provided metadata does not list all columns, typical data stored would include transaction dates, reference numbers, the parent lot identifier, user who performed the action, and status flags to indicate the processing state of the transaction.

Common Use Cases and Queries

This table is central to troubleshooting and reporting on lot quantity changes. Common use cases include auditing the history of a specific lot to understand how its quantity was altered through splits or merges, generating reports on transaction volumes by reason code for operational analysis, and reconciling inventory discrepancies traced to lot management activities. A typical query would join this header table with its related line-level transaction details table (often named similarly, e.g., WSM_SPLIT_MERGE_TXN_DETAILS) to get a complete picture.

Sample Query Pattern:
SELECT smt.transaction_id, smt.transaction_date, mtr.reason_name, smt.organization_id
FROM wsm_split_merge_transactions smt,
     mtl_transaction_reasons mtr
WHERE smt.reason_id = mtr.reason_id
AND smt.organization_id = 123
AND smt.transaction_date > SYSDATE - 30
ORDER BY smt.transaction_date DESC;

Related Objects

The documented foreign key relationships explicitly define this table's dependencies within the EBS schema. The table has two key foreign key constraints:

  • WSM_SPLIT_MERGE_TRANSACTIONS.REASON_ID → MTL_TRANSACTION_REASONS: This ensures that any reason code applied to a split/merge transaction is valid and defined in the central MTL_TRANSACTION_REASONS table.
  • WSM_SPLIT_MERGE_TRANSACTIONS.ORGANIZATION_ID → WSM_PARAMETERS: This ties the transaction to a valid organization configured within the WSM module's parameters.

In practice, this header table is the parent to one or more detail tables (not listed in the provided metadata but inherent to the design) which store the specific lot numbers, quantities, and item details involved in the split or merge operation. Transactional data from this table is also integral to the underlying WIP and inventory transaction interfaces and corresponding material transaction tables (e.g., MTL_MATERIAL_TRANSACTIONS).