Search Results wsm_split_merge_txn_interface




Overview
Explore in AI Chat

Overview

The WSM_SPLIT_MERGE_TXN_INTERFACE table is a critical interface table within the Oracle E-Business Suite (EBS) Shop Floor Management (WSM) module, specifically for versions 12.1.1 and 12.2.2. Its primary role is to serve as a staging area for lot-based Work in Process (WIP) transactions, particularly those involving the splitting or merging of manufacturing lots. This table enables the submission of complex lot quantity adjustments from external systems or custom programs into Oracle's core manufacturing transaction processing engine. Data populated into this interface table is subsequently processed by standard concurrent programs or APIs to create final inventory and WIP transactions, ensuring data integrity and auditability.

Key Information Stored

The table stores transaction headers and details necessary to process lot splits and merges. While the full column list is not detailed in the provided metadata, the structure implies the presence of key identifiers and control attributes. The primary key column, HEADER_ID, uniquely identifies each transaction batch. The ORGANIZATION_ID links the transaction to a specific inventory organization, enforcing organizational security. The REASON_ID, via a foreign key to MTL_TRANSACTION_REASONS, captures the business justification for the lot adjustment. Other typical columns in such an interface would include transaction quantities, source and destination lot numbers, item identifiers, transaction dates, and process status flags (e.g., PENDING, ERROR, PROCESSED) to manage the interface lifecycle.

Common Use Cases and Queries

The primary use case is the programmatic execution of lot management operations. For instance, splitting a large parent lot into several child lots for quality segregation or merging partial lots to consolidate inventory. A common reporting query involves monitoring the interface for errors. A sample SQL pattern to find pending transactions would be: SELECT HEADER_ID, ORGANIZATION_ID, TRANSACTION_QUANTITY, LOT_NUMBER FROM WSM_SPLIT_MERGE_TXN_INTERFACE WHERE PROCESS_STATUS = 'PENDING' AND ORGANIZATION_ID = :org_id;. Another critical operational query joins with the error table (often named with a _ERR suffix) to diagnose failed records: SELECT i.*, e.ERROR_MESSAGE FROM WSM_SPLIT_MERGE_TXN_INTERFACE i, WSM_SPLIT_MERGE_TXN_INTERFACE_ERR e WHERE i.HEADER_ID = e.HEADER_ID AND i.PROCESS_STATUS = 'ERROR';.

Related Objects

  • WSM_STARTING_JOBS_INTERFACE: Shares a foreign key relationship via HEADER_ID, indicating a potential integration point where lot split/merge transactions may be associated with or triggered by job creation processes.
  • MTL_TRANSACTION_REASONS: Provides the valid reason codes for the transaction via the REASON_ID foreign key, ensuring referential integrity for audit trails.
  • WSM_PARAMETERS: Validates the ORGANIZATION_ID against configured WSM organizations.
  • Standard WSM APIs: Programs typically call APIs such as WSM_SPLIT_MERGE_PUB to validate and process records from this interface into base tables like MTL_MATERIAL_TRANSACTIONS and WIP_TRANSACTIONS.