Results for “minimum_delay”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FM_ROUT_DEP is a table owned by the GMD schema within the Oracle E-Business Suite Process Manufacturing Product Development module. It stores routing step dependencies, defining the predecessor and successor relationships that govern the sequence in which routing steps are executed for a manufactured product. In process manufacturing, a routing describes the ordered set of operations required to produce an item; FM_ROUT_DEP supplies the explicit dependency graph that constrains that order, including the type of dependency, delay tolerances, and transfer quantities between steps.

From a Data Vault modeling perspective, the FK structure suggests this table behaves as a link entity. Its function is inherently associative: it connects two routing steps within the same routing, capturing the relationship between them rather than describing a single independent business entity. This classification is a heuristic derived from the foreign key pattern and should be treated as a modeling suggestion rather than a documented architectural assertion.

Key Information Stored

The table contains 19 documented columns. The most significant are the key and dependency-defining attributes:

• ROUTING_ID — Identifies the routing to which the dependency belongs; part of the composite primary key and a foreign key to FM_ROUT_DTL.
• ROUTINGSTEP_NO — The routing step that acts as the dependent (successor) step; part of the composite key and FK to FM_ROUT_DTL.
• DEP_ROUTINGSTEP_NO — The predecessor step on which the successor depends; part of the composite key and FK to FM_ROUT_DTL.
• DEP_TYPE — Classifies the nature of the dependency between steps.
• REWORK_CODE — Indicates rework behavior associated with the dependency.
• STANDARD_DELAY, MINIMUM_DELAY, MAX_DELAY — Timing tolerances applied between the dependent steps.
• TRANSFER_QTY, TRANSFER_PCT, ITEM_UM, ROUTINGSTEP_NO_UOM — Quantity and unit-of-measure attributes governing material transfer between steps.
• CHARGEABLE_IND — Flag indicating whether the step is chargeable.
• TEXT_CODE — Foreign key to FM_TEXT_HDR for associated descriptive text.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The surrogate primary key is FM_ROUT_DEP_PK, defined over (ROUTINGSTEP_NO, DEP_ROUTINGSTEP_NO, ROUTING_ID). This unique index also serves as the business-key candidate, since the same composite of routing and step pair must be unique.

Common Use Cases and Queries

Typical uses include validating routing sequences, explaining production scheduling constraints, and reporting on interdependencies for capacity and lead-time analysis.

• List all dependencies for a routing:

  SELECT ROUTINGSTEP_NO, DEP_ROUTINGSTEP_NO, DEP_TYPE, STANDARD_DELAY
  FROM   GMD.FM_ROUT_DEP
  WHERE  ROUTING_ID = :routing_id;

• Identify predecessor steps (prerequisites) of a given step:

  SELECT DEP_ROUTINGSTEP_NO
  FROM   GMD.FM_ROUT_DEP
  WHERE  ROUTING_ID = :routing_id AND ROUTINGSTEP_NO = :step_no;

• Find successors that depend on a step:

  SELECT ROUTINGSTEP_NO
  FROM   GMD.FM_ROUT_DEP
  WHERE  ROUTING_ID = :routing_id AND DEP_ROUTINGSTEP_NO = :step_no;

• Join to step details for reporting:

  SELECT d.ROUTINGSTEP_NO, d.DEP_ROUTINGSTEP_NO, d.DEP_TYPE, dt.OPERATION_SEQ
  FROM   GMD.FM_ROUT_DEP d, GMD.FM_ROUT_DTL dt
  WHERE  d.ROUTING_ID = dt.ROUTING_ID
  AND    d.ROUTINGSTEP_NO = dt.ROUTINGSTEP_NO;

Related Objects

• FM_ROUT_DTL — Routing step detail; referenced twice via ROUTING_ID/ROUTINGSTEP_NO and ROUTING_ID/DEP_ROUTINGSTEP_NO. This is the primary parent of routing step dependencies.
• FM_TEXT_HDR — Header descriptions referenced by TEXT_CODE for dependency textual attributes.
• FM_ROUT_DEP_PK — Composite unique index enforcing business-key uniqueness across the routing and step pair.
• FM_ROUT_HDR — Routing header, providing the parent routing definition context.
• Routing APIs — Process Manufacturing routing maintenance APIs that manage step sequencing, which populate and consume this table.

Together these objects form the routing dependency framework underpinning process manufacturing execution in EBS 12.1.1 and 12.2.2.