Search Results wip_trans_id




Overview
Explore in AI Chat

Overview

The PM_OPRN_WIP table is a core data repository within the Oracle E-Business Suite (EBS) Process Manufacturing Process Execution (GME) module. It serves as a detailed transaction history log for completed Work in Process (WIP) movements associated with process manufacturing batches. Specifically, it records all finalized incoming and outgoing material transactions that occur during batch step execution, such as the consumption of ingredients, the production of co-products, and the generation of by-products. This table is essential for providing a complete audit trail of material flow, supporting costing calculations, and enabling detailed production analysis and reconciliation within the manufacturing process.

Key Information Stored

The table's primary key is WIP_TRANS_ID, which uniquely identifies each completed WIP transaction record. Based on its foreign key relationships, the table stores critical identifiers that link the transaction to its manufacturing context. This includes BATCH_ID to associate the transaction with a specific production batch, and BATCHSTEP_NO or TRANSFER_STEP_NO to pinpoint the exact step within the batch routing where the transaction occurred. Other significant columns include TRANS_UM, which stores the unit of measure for the transacted quantity, and TEXT_CODE, which links to descriptive text entries in the PC_TEXT_HDR table. The table fundamentally captures the material, quantity, timing, and operational context of every completed WIP movement.

Common Use Cases and Queries

This table is central to post-transaction reporting and analysis. Common use cases include generating detailed material consumption reports for a batch, tracing the production history of a specific output item, and reconciling theoretical versus actual material usage for cost variance analysis. A typical query might join PM_OPRN_WIP with batch header (GME_BATCH_HEADER) and material master (MTL_SYSTEM_ITEMS_B) tables to produce a comprehensive batch yield report. For example, to find all output transactions for a completed batch, one might use a SQL pattern such as:

  • SELECT wip.*, bh.BATCH_NO, msib.SEGMENT1 ITEM
  • FROM GME.PM_OPRN_WIP wip,
  • GME.GME_BATCH_HEADER bh,
  • INV.MTL_SYSTEM_ITEMS_B msib
  • WHERE wip.BATCH_ID = bh.BATCH_ID
  • AND wip.INVENTORY_ITEM_ID = msib.INVENTORY_ITEM_ID
  • AND bh.BATCH_NO = '<BATCH_NUMBER>'
  • AND wip.TRANSACTION_TYPE = 'YIELD'; -- or appropriate type

Related Objects

PM_OPRN_WIP maintains integral relationships with several key EBS objects. Its primary foreign keys establish direct dependencies: it references PM_ROUT_DTL (batch routing details) via BATCH_ID and STEP numbers to tie transactions to process steps. It links to SY_UOMS_MST for unit of measure validation via the TRANS_UM column. The TEXT_CODE column creates a relationship with PC_TEXT_HDR for storing additional transaction notes. As a transactional detail table, it is fundamentally sourced from and feeds into the GME batch execution engine, and its data is often aggregated for reporting through views or consumed by cost management (CST) and inventory (INV) modules for settlement and perpetual cost updates.