Search Results fm_rout_dep




Overview
Explore in AI Chat

Overview

The FM_ROUT_DEP table is a core data object within the Process Manufacturing Product Development (GMD) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves a critical function in defining and managing the production workflow by storing routing step dependencies. In Process Manufacturing, a routing details the sequence of operations required to produce an item. This table explicitly defines the predecessor-successor relationships between individual steps (or operations) within a given routing. It ensures that the manufacturing execution system enforces the correct order of operations, which is essential for maintaining product quality, safety, and efficient resource scheduling.

Key Information Stored

The table's primary purpose is to link a dependent routing step to the step it depends upon. Its structure, as indicated by its primary and foreign keys, centers on identifying the routing and the specific steps involved. The primary key is a composite of ROUTING_ID, ROUTINGSTEP_NO, and DEP_ROUTINGSTEP_NO. This design enforces uniqueness for each dependency relationship within a routing. Key columns include ROUTING_ID, which links to the master routing definition; ROUTINGSTEP_NO, identifying the dependent step that cannot proceed until its predecessor is complete; and DEP_ROUTINGSTEP_NO, identifying the prerequisite step that must be finished. The TEXT_CODE column, linked to FM_TEXT_HDR, allows for storing descriptive notes or instructions associated with the dependency.

Common Use Cases and Queries

This table is primarily accessed for workflow validation, scheduling, and reporting. A common operational use case is verifying the sequence of steps before releasing a batch for production. For reporting, analysts may query dependencies to understand process bottlenecks or to document standard operating procedures. A typical query retrieves the full dependency chain for a specific routing.

  • Sample Query: List all dependencies for a routing:
    SELECT routingstep_no, dep_routingstep_no, text_code
    FROM gmd.fm_rout_dep
    WHERE routing_id = :routing_id
    ORDER BY routingstep_no;
  • Sample Query: Find steps with no predecessors (starting steps):
    SELECT DISTINCT rd.routingstep_no
    FROM gmd.fm_rout_dtl rd
    WHERE rd.routing_id = :routing_id
    AND NOT EXISTS (SELECT 1 FROM gmd.fm_rout_dep rd2 WHERE rd2.routing_id = rd.routing_id AND rd2.routingstep_no = rd.routingstep_no);

Related Objects

FM_ROUT_DEP is centrally connected to other key tables in the GMD routing schema. It has two foreign key relationships with the FM_ROUT_DTL table, which stores the detailed definition of each routing step (operation). One foreign key links ROUTINGSTEP_NO to FM_ROUT_DTL, and another links DEP_ROUTINGSTEP_NO to FM_ROUT_DTL, ensuring that both steps involved in a dependency are valid, defined steps. The TEXT_CODE column references the FM_TEXT_HDR table, enabling rich text storage. The primary table for the routing header, FM_ROUT_HDR, is indirectly related through the shared ROUTING_ID column present in FM_ROUT_DTL and FM_ROUT_DEP.