Results for “step_qty”

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

Overview

FM_ROUT_DTL is the routing detail table in the Oracle EBS Process Manufacturing Product Development module (GMD). It stores the individual operation steps that make up a routing, which is the sequence of manufacturing operations applied to produce a product. Each row represents a single step within a routing header, capturing the operation performed, the quantity to which the step applies, and the release logic that governs when the step becomes active. The table resides in the GMD schema and is documented as VALID in the ETRM 12.2.2 reference for Oracle EBS 12.1.1 and 12.2.2 environments.

From a dimensional modeling perspective, the mined Data Vault classification suggests treating FM_ROUT_DTL as a hub. The heuristic derives this from the relationship structure: the table sits at the center of a wide fan-out of dependent tables and is referenced by multiple foreign keys from downstream objects. Its surrogate identity is the ROUTINGSTEP_ID, and the natural business key is the composite of ROUTING_ID and ROUTINGSTEP_NO. This classification is a modeling suggestion rather than a stored attribute.

Key Information Stored

FM_ROUT_DTL contains 46 documented columns. The most operationally significant are described below.

• ROUTINGSTEP_ID — The surrogate primary key, defined by the unique index FM_ROUT_DTLI1. It is the column referenced by most downstream child tables.
• ROUTING_ID — The routing header identifier, forming the business-key candidate together with ROUTINGSTEP_NO via unique index FM_ROUT_DTL_PK. It links to FM_ROUT_HDR and GMD_ROUTINGS_B.
• ROUTINGSTEP_NO — The sequence number of the step within the routing, defining operation order and completing the business key.
• OPRN_ID — The operation performed at this step, referencing the operation master FM_OPRN_MST.
• STEP_QTY — The quantity basis for the step, typically expressed relative to the routing batch quantity.
• STEPRELEASE_TYPE — Controls how the step is released, such as immediate or dependent release logic.
• TEXT_CODE — Reference to descriptive text stored in FM_TEXT_HDR, allowing documentation to be attached to the step.
• MINIMUM_TRANSFER_QTY — The minimum quantity that must be transferred before the step proceeds.
• X_COORDINATE and Y_COORDINATE — Spatial positioning values, typically used for graphical representation of the routing network.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — The standard Oracle flexfield descriptor and attribute columns for extensibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO audit columns tracking record creation and modification.

Common Use Cases and Queries

Typical reporting scenarios include listing the operation sequence for a given routing, identifying the operation assigned to each step, and tracing which quality specifications, recipes, or batch steps reference a particular routing step.

A basic query returning the ordered steps of a routing:

SELECT d.ROUTINGSTEP_NO, d.OPRN_ID, d.STEP_QTY,
       d.STEPRELEASE_TYPE, d.MINIMUM_TRANSFER_QTY
  FROM GMD.FM_ROUT_DTL d
 WHERE d.ROUTING_ID = :routing_id
 ORDER BY d.ROUTINGSTEP_NO;

To retrieve step descriptions alongside the operation master:

SELECT d.ROUTING_ID, d.ROUTINGSTEP_NO, o.OPRN_CODE,
       d.STEP_QTY
  FROM GMD.FM_ROUT_DTL d, GMD.FM_OPRN_MST o
 WHERE d.OPRN_ID = o.OPRN_ID
   AND d.ROUTING_ID = :routing_id;

Because ROUTINGSTEP_ID is the hub key, reverse lookups are common: given a batch step, quality sample, or recipe parameter, a join back to FM_ROUT_DTL resolves the originating routing step. Reconciliation and migration scripts frequently use FM_ROUT_DTLI1 and FM_ROUT_DTL_PK to enforce uniqueness when loading routing data.

Related Objects

• FM_ROUT_HDR — Parent routing header, joined on ROUTING_ID.
• GMD_ROUTINGS_B — Base routing table in the GMD schema, also joined on ROUTING_ID.
• FM_OPRN_MST — Operation master, joined on OPRN_ID to resolve operation details.
• FM_TEXT_HDR — Text header, joined on TEXT_CODE for step documentation.
• FM_ROUT_DEP — Routing step dependencies, referencing ROUTING_ID plus ROUTINGSTEP_NO and DEP_ROUTINGSTEP_NO.
• GMD_RECIPE_PROCESS_PARAMETERS — Process parameters keyed by ROUTINGSTEP_ID.
• GME_BATCH_STEPS — Executed batch steps referencing the routing step via ROUTINGSTEP_ID.
• QC_SPEC_MST, QC_SMPL_MST, QC_RSLT_MST — Quality specification, sample, and result tables referencing ROUTING_ID and ROUTINGSTEP_NO or ROUTINGSTEP_ID.
• GMD_RECIPE_STEP_MATERIALS — Materials consumed or produced at a step, keyed by ROUTINGSTEP_ID.
• PM_ROUT_DTL — Parallel routing detail structure referencing ROUTINGSTEP_ID.