Search Results fm_oprn_mst

Overview

The PM_ROUT_DTL table is a core transactional data object within the Oracle E-Business Suite Process Manufacturing (GME) module, specifically for Process Execution. It serves as the detailed repository for batch routing steps. In Process Manufacturing, a batch is a specific production run, and its routing defines the sequence of operations or steps required to manufacture it. This table stores the instantiated, batch-specific execution steps derived from the master routing defined in the product's formula and routing. Each record represents a discrete step in the production process for a particular batch, forming the backbone of work-in-process tracking and operational control on the shop floor.

Key Information Stored

The table's structure is designed to link batch execution steps to master data and track their progress. The primary key is a composite of BATCH_ID and BATCHSTEP_NO, uniquely identifying each step within a batch. Critical foreign key columns establish essential relationships: BATCH_ID links to PM_BTCH_HDR (the batch header), OPRN_ID references FM_OPRN_MST (the master operation definition), and ROUTINGSTEP_ID connects to FM_ROUT_DTL (the master routing step). Other significant columns include TEXT_CODE for attached instructions, and various planning and scheduling fields such as PLAN_START_DATE and PLAN_CMPL_DATE. The table also holds status indicators that reflect the current state of the step within the production lifecycle.

Common Use Cases and Queries

This table is central to operational reporting and process traceability. Common use cases include generating batch work orders, tracking step completion status, and analyzing production line performance. A fundamental query involves joining to the batch header and master operation table to list all steps for a batch:

• SELECT b.BATCH_NO, rd.BATCHSTEP_NO, om.OPRN_DESC, rd.PLAN_START_DATE FROM GME.PM_ROUT_DTL rd JOIN GME.PM_BTCH_HDR b ON rd.BATCH_ID = b.BATCH_ID JOIN FM_OPRN_MST om ON rd.OPRN_ID = om.OPRN_ID WHERE b.BATCH_NO = '<BATCH_NUMBER>' ORDER BY rd.BATCHSTEP_NO;

Another critical pattern is analyzing step duration or identifying bottlenecks by comparing planned versus actual dates. The table is also the primary source for inquiries into what specific operations were performed on a given batch, which is vital for quality assurance and regulatory compliance.

Related Objects

PM_ROUT_DTL sits at the nexus of several key transactional tables in Process Execution, as evidenced by its foreign key relationships. It has a direct parent-child relationship with PM_BTCH_HDR. It is heavily referenced by subordinate detail tables that manage specific aspects of a routing step: PM_OPRN_DTL for operation resources, PM_OPRN_WIP for work-in-process transactions, PM_ROUT_MTL for material consumption, and PM_ROUT_DEP for step dependencies. Its links to foundational master data tables FM_OPRN_MST and FM_ROUT_DTL ensure consistency between batch execution and the defined product manufacturing process. The TEXT_CODE column links to PC_TEXT_HDR for storing detailed operational instructions.