Search Results fm_rout_dtl

Overview

The FM_ROUT_DTL table is a core data object within the Oracle E-Business Suite Process Manufacturing (GMD) module, specifically under the Product Development family. It serves as the detailed repository for routing steps, which define the sequence of operations required to manufacture a product. A routing is a master recipe that specifies the process flow, and this table stores the granular, step-by-step instructions that constitute that flow. Its primary role is to maintain the operational blueprint for production, linking individual process steps to a parent routing header and defining critical execution parameters. The table's integrity is enforced through its primary and foreign key relationships, making it a central hub for process definition data that feeds into production execution, quality management, and recipe management.

Key Information Stored

The table's structure is designed to capture the specifics of each step in a manufacturing process. The metadata indicates a composite primary key (FM_ROUT_DTL_PK) based on ROUTING_ID and ROUTINGSTEP_NO, uniquely identifying each step within a routing. A surrogate key, ROUTINGSTEP_ID, is also defined as a primary key (FM_ROUT_DTLI1), likely used for internal system references. Essential columns, inferred from foreign key relationships, include OPRN_ID, which links the step to a master operation definition in the FM_OPRN_MST table, and TEXT_CODE, which associates descriptive text from the FM_TEXT_HDR table. The table's design facilitates the definition of step sequences, dependencies, and associated process controls.

Common Use Cases and Queries

This table is fundamental for generating production instructions, analyzing process flows, and configuring recipes. Common operational scenarios include retrieving the complete sequence of steps for a given routing for shop floor documentation, or identifying all steps that use a specific operation for impact analysis. A typical reporting query would join FM_ROUT_DTL with the routing header (FM_ROUT_HDR) and operations master (FM_OPRN_MST) to produce a human-readable process sheet. For technical analysis, one might query step dependencies by joining with the FM_ROUT_DEP table. A sample SQL pattern to list routing steps is:

• SELECT hdr.routing_no, dtl.routingstep_no, oprn.oprn_no, dtl.oprn_id FROM gmd.fm_rout_dtl dtl, gmd.fm_rout_hdr hdr, gmd.fm_oprn_mst oprn WHERE dtl.routing_id = hdr.routing_id AND dtl.oprn_id = oprn.oprn_id AND hdr.routing_no = '<ROUTING_NAME>' ORDER BY dtl.routingstep_no;

Related Objects

As evidenced by the extensive foreign key relationships, FM_ROUT_DTL is a pivotal table integrated with several key Process Manufacturing and Quality modules. Its primary parent is the FM_ROUT_HDR (and GMD_ROUTINGS_B) table, which defines the routing master record. It references FM_OPRN_MST for operation details and FM_TEXT_HDR for descriptive text. Crucially, it is referenced by numerous child objects: FM_ROUT_DEP for defining step dependencies, GMD_RECIPE_PROCESS_PARAMETERS for attaching process parameters to a step, and PM_ROUT_DTL for production batch execution. Furthermore, integration with Quality (QC) modules is shown through QC_RSLT_MST, QC_SMPL_MST, and QC_SPEC_MST, allowing quality specifications, samples, and results to be linked directly to specific routing steps.