Search Results pm_rout_mtl




Overview
Explore in AI Chat

Overview

The PM_ROUT_MTL table is a core data object within the Oracle E-Business Suite Process Manufacturing (GME) module, specifically for Process Execution. It functions as a relational junction table, establishing and maintaining the critical operational links between batch steps and batch material lines. This mapping is fundamental to the execution of a manufacturing batch, as it defines which specific material components are consumed or produced at which defined steps in the batch's routing. The table's integrity is enforced by primary and foreign key constraints, ensuring data consistency across the batch execution lifecycle in versions 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to store relational keys. The primary columns are BATCH_ID, BATCHSTEP_NO, and BATCHLINE_ID, which together form the composite primary key (PM_ROUT_MTL_PK). The BATCH_ID column identifies the specific manufacturing batch. The BATCHSTEP_NO references the sequential step number within the batch's routing, while the BATCHLINE_ID points to the specific material line item from the batch's bill of materials. An additional TEXT_CODE column provides a foreign key link to descriptive text stored in the PM_TEXT_HDR table, allowing for step-specific instructions or notes related to the material usage.

Common Use Cases and Queries

This table is essential for queries that analyze material flow and step-wise consumption within a batch. A common reporting use case is to generate a component requirement list per process step for shop floor documentation. Another critical scenario is tracing material usage, such as identifying which batch step consumed a specific raw material, which is vital for lot genealogy and compliance reporting. A typical SQL pattern joins PM_ROUT_MTL with PM_ROUT_DTL (for step details) and PM_MATL_DTL (for material details).

  • Sample Query: SELECT rmt.batch_id, rmt.batchstep_no, mdt.item_no, mdt.item_um FROM gme.pm_rout_mtl rmt JOIN gme.pm_matl_dtl mdt ON rmt.batch_id = mdt.batch_id AND rmt.batchline_id = mdt.batchline_id WHERE rmt.batch_id = :p_batch_id ORDER BY rmt.batchstep_no;

Related Objects

PM_ROUT_MTL has defined foreign key relationships with several key GME tables, as documented in the ETRM. It references PM_MATL_DTL via BATCH_ID and BATCHLINE_ID to validate the material line. It references PM_ROUT_DTL via BATCH_ID and BATCHSTEP_NO to validate the routing step. The link to PM_TEXT_HDR via TEXT_CODE allows for associated textual instructions. These relationships position PM_ROUT_MTL as a central hub connecting the batch's material definition (PM_MATL_DTL) with its procedural routing (PM_ROUT_DTL), forming the executable blueprint for the batch.