Results for “wsm_lot_move_txn_interface”

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

Overview

The WSM_LOT_MOVE_TXN_INTERFACE table is an open interface table owned by the WSM schema within the Shop Floor Management module of Oracle E-Business Suite. It serves as the staging area for the import of lot-based job shop floor move transactions in Oracle Shop Floor Management (OSFM). External systems, custom programs, and feeder processes populate this table with move transaction records that are subsequently validated and processed into native OSFM transaction tables by the OSFM move transaction worker. The table is populated before processing and acts as a bridge between external transaction sources and the core OSFM engine.

From a dimensional modeling perspective, the mined foreign key structure — which references multiple independent dimension tables such as WIP_ENTITIES, BOM_DEPARTMENTS, GL_CODE_COMBINATIONS, MTL_TRANSACTION_REASONS, and MTL_KANBAN_CARDS — suggests a heuristic Data Vault classification of a link table. It functions as a transactional association between many business entities, though in EBS it is more accurately described as a transient staging interface rather than a persistent analytical link.

Key Information Stored

The table contains 80 documented columns. The primary key is HEADER_ID, enforced through both WSM_LOT_MOVE_TXN_INTERFACE_PK and the unique index WSM_LOT_MOVE_TXN_INTERFACE_U1, making HEADER_ID the sole documented business-key candidate and surrogate identifier. The most significant columns include:

• INTERFACE_ID and TRANSACTION_ID — the surrogate record identifier and the source transaction reference from the feeder system.
• ORGANIZATION_ID / ORGANIZATION_CODE — the inventory organization context, with ORGANIZATION_ID referencing WSM_PARAMETERS.
• WIP_ENTITY_ID / WIP_ENTITY_NAME — the job or repetitive schedule header for the transaction, referencing WIP_ENTITIES.
• LINE_ID / LINE_CODE — the specific WIP line, referencing WIP_LINES.
• FM_DEPARTMENT_ID / TO_DEPARTMENT_ID — the from and to departments for the move, both referencing BOM_DEPARTMENTS.
• TRANSACTION_QUANTITY and TRANSACTION_UOM — the primary quantity moved and its unit of measure.
• PRIMARY_QUANTITY, SCRAP_QUANTITY, and PRIMARY_SCRAP_QUANTITY — supporting quantity and scrap handling columns.
• SCRAP_ACCOUNT_ID — the GL account for scrap, referencing GL_CODE_COMBINATIONS.
• REASON_ID / REASON_NAME — the transaction reason, referencing MTL_TRANSACTION_REASONS.
• STATUS and ERROR — the processing state and any validation error text.
• GROUP_ID, REQUEST_ID, and PROCESSING_ORDER — concurrency and processing-sequence controls used by the interface worker.

Common Use Cases and Queries

Typical usage involves inserting externally captured move transactions, invoking the OSFM import concurrent program, and monitoring STATUS and ERROR to resolve failures. A common diagnostic query identifies unprocessed records:

SELECT HEADER_ID, WIP_ENTITY_NAME, TRANSACTION_QUANTITY, STATUS, ERROR FROM WSM_LOT_MOVE_TXN_INTERFACE WHERE STATUS IS NULL OR ERROR IS NOT NULL;

Reconciliation reporting joins the interface to WIP_ENTITIES and BOM_DEPARTMENTS to confirm the intended from/to routing. Batch cleanup is frequently performed by GROUP_ID after a successful run.

Related Objects

• WIP_ENTITIES — joined on WIP_ENTITY_ID; supplies the job header context.
• WIP_LINES — joined on LINE_ID; identifies the specific line.
• BOM_DEPARTMENTS — joined on FM_DEPARTMENT_ID and TO_DEPARTMENT_ID; provides from/to department names.
• GL_CODE_COMBINATIONS — joined on SCRAP_ACCOUNT_ID; drives scrap accounting.
• MTL_TRANSACTION_REASONS — joined on REASON_ID; supplies reason codes.
• WSM_PARAMETERS — joined on ORGANIZATION_ID; provides OSFM organization configuration.
• WIP_REPETITIVE_SCHEDULES — joined on REPETITIVE_SCHEDULE_ID for repetitive environments.
• MTL_KANBAN_CARDS — joined on KANBAN_CARD_ID for kanban-driven moves.