Results for “wsm_lot_split_merges_interface”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WSM_LOT_SPLIT_MERGES_INTERFACE table resides in the WSM (Shop Floor Management) schema and serves as the interface (staging) table for lot-based inventory lot transactions, specifically capturing header-level information for split and merge operations initiated from the shop floor. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the inbound hand-off point between shop floor execution logic and the Oracle Inventory transaction processing engine. Records written here drive subsequent inventory lot split and merge transactions, with line-level detail supplied by companion interface tables in the same schema.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table depends on parent references such as ORGANIZATION_ID (pointing to WSM_PARAMETERS) and REASON_ID (pointing to MTL_TRANSACTION_REASONS), while its HEADER_ID is referenced downstream by child interface tables. This pattern is characteristic of a transactional satellite hanging off a hub/link structure within the shop floor lot transaction domain.

Key Information Stored

The table contains 39 documented columns. The most functionally significant columns are:

• HEADER_ID — Surrogate primary key, enforced by unique index WSM_LOT_SPLIT_MERGES_INTER_UK and the business-key candidate WSM_LOT_SPLIT_MERGES_IFC_U1. It uniquely identifies each interface header and is the join key to child interface tables.
• TRANSACTION_ID and TRANSACTION_TYPE_ID — Identify the inventory transaction and its type (split versus merge context).
• ORGANIZATION_ID — The inventory organization where the lot transaction is executed; foreign key to WSM_PARAMETERS.
• SPLIT_FLAG and WIP_FLAG — Control flags indicating whether the transaction is a split operation and/or linked to WIP activity.
• REASON_ID and TRANSACTION_REASON — Reason reference (FK to MTL_TRANSACTION_REASONS) and free-text reason description.
• TRANSACTION_REFERENCE and TRANSACTION_DATE — Reference number and effective date of the transaction.
• PROCESS_STATUS and ERROR_MESSAGE — Concurrency control fields capturing interface processing outcome and failure detail.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program tracking columns.
• GROUP_ID — Groups related interface rows into a single logical execution unit.
• XML_DOCUMENT_ID — Links the header to an XML payload representation where applicable.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Flexfield descriptor and DFF segments for extensibility.

Common Use Cases and Queries

Typical uses include monitoring the status of lot split/merge interface processing, diagnosing failed transactions, and reconciling shop floor activity to inventory. A common diagnostic query retrieves unprocessed or failed headers:

• SELECT HEADER_ID, TRANSACTION_ID, ORGANIZATION_ID, PROCESS_STATUS, ERROR_MESSAGE FROM WSM_LOT_SPLIT_MERGES_INTERFACE WHERE PROCESS_STATUS IS NULL OR ERROR_MESSAGE IS NOT NULL;
• Trace a full transaction by joining the header to WSM_STARTING_LOTS_INTERFACE and WSM_RESULTING_LOTS_INTERFACE on HEADER_ID.
• Report lot activity volume by organization and reason using ORGANIZATION_ID and REASON_ID.
• Audit concurrent program runs via REQUEST_ID and PROGRAM_ID.

Related Objects

The following objects are most significant given the documented relationships:

• WSM_STARTING_LOTS_INTERFACE — Child table referencing HEADER_ID; holds the source lots consumed by the transaction.
• WSM_RESULTING_LOTS_INTERFACE — Child table referencing HEADER_ID; holds the lots produced by split or merge.
• WSM_PARAMETERS — Referenced via ORGANIZATION_ID; supplies shop floor configuration.
• MTL_TRANSACTION_REASONS — Referenced via REASON_ID; provides valid transaction reason codes.
• MTL_MATERIAL_TRANSACTIONS — Downstream posting target once the interface is processed into inventory.