Search Results wip_move_transactions




Overview
Explore in AI Chat

Overview

The WIP_MOVE_TRANSACTIONS table is a core transactional data store within the Oracle E-Business Suite Work in Process (WIP) module for versions 12.1.1 and 12.2.2. It serves as the primary ledger for recording and tracking all shop floor move transactions. These transactions represent the physical movement of assemblies from one operation or department to another within a discrete manufacturing job or repetitive schedule. The table's existence is critical for maintaining real-time production status, enabling accurate costing, and providing an audit trail for manufacturing execution. Its data is fundamental to the calculation of manufacturing variances, work-in-process valuation, and production throughput analysis.

Key Information Stored

The table's primary key is TRANSACTION_ID, which uniquely identifies each move transaction. Foreign key relationships define its integration with other EBS modules. Key columns include WIP_ENTITY_ID, linking to the specific job or schedule in WIP_ENTITIES, and LINE_ID, referencing the manufacturing line from WIP_LINES. Departmental movement is captured via FM_DEPARTMENT_ID and TO_DEPARTMENT_ID, both referencing BOM_DEPARTMENTS. Accounting integrity is maintained through ACCT_PERIOD_ID (ORG_ACCT_PERIODS) and SCRAP_ACCOUNT_ID (GL_CODE_COMBINATIONS). The REASON_ID (MTL_TRANSACTION_REASONS) allows for categorizing the transaction purpose. Each record is also tied to a specific ORGANIZATION_ID, enforcing inventory organization context.

Common Use Cases and Queries

This table is central to operational reporting and troubleshooting. Common use cases include analyzing production flow bottlenecks, auditing transaction history for a specific job, and reconciling WIP balances. A typical query retrieves the move transaction history for a job to understand its routing progression:

  • SELECT wmt.transaction_id, wmt.transaction_date, bd_fm.department_code from_dept, bd_to.department_code to_dept FROM wip_move_transactions wmt JOIN bom_departments bd_fm ON wmt.fm_department_id = bd_fm.department_id JOIN bom_departments bd_to ON wmt.to_department_id = bd_to.department_id WHERE wmt.wip_entity_id = :p_job_id ORDER BY wmt.transaction_date;

Another critical scenario involves investigating scrap transactions by joining to the reason codes and scrap account. Data from this table is also essential for custom cost accumulation or yield analysis reports, often joined to WIP_TRANSACTIONS and MTL_MATERIAL_TRANSACTIONS for a complete picture.

Related Objects

As indicated by its foreign keys, WIP_MOVE_TRANSACTIONS is deeply integrated with the manufacturing and cost management schema. It is the parent table for WIP_MOVE_TXN_ALLOCATIONS, which details component material allocations for each move. Crucially, its TRANSACTION_ID is referenced by MTL_MATERIAL_TRANSACTIONS and its temporary table (MTL_MATERIAL_TRANSACTIONS_TEMP), forming the link between WIP movement and inventory material transactions. For costing, WIP_COST_TXN_INTERFACE references it via MOVE_TRANSACTION_ID. The WIP_TRANSACTIONS table also holds a key reference, further tying move transactions to the broader WIP transaction umbrella. These relationships ensure data consistency across inventory transactions, cost collection, and production reporting.