Search Results gmd_recipe_routing_steps




Overview
Explore in AI Chat

Overview

GMD.GMD_RECIPE_ROUTING_STEPS is a Process Manufacturing Product Development table that stores updates to routing steps at the recipe level. In Oracle EBS Process Manufacturing, a recipe defines the master manufacturing instructions for a product — combining a formula (materials) with a routing (operations, steps, and activities). While the base routing definition typically resides in the routing master, this table captures recipe-specific overrides and quantity information for individual routing steps, allowing the same routing structure to be reused across recipes with tailored step-level attributes.

The table is owned by the GMD schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. It carries a 46-column physical schema, of which the vast majority are generic descriptive flexfield segments (ATTRIBUTE1–ATTRIBUTE30) plus a ATTRIBUTE_CATEGORY discriminator. The heuristic Data Vault classification mined from the FK structure is standalone, suggesting the object operates as an independent satellite-style table keyed on the recipe/step combination rather than participating in an explicit link relationship with other hubs. This modeling suggestion should be validated against the actual FK constraints in the environment.

Key Information Stored

The primary key is GMD_RECIPE_ROUTING_STEPS_PK, defined over the composite business-key candidate pair (RECIPE_ID, ROUTINGSTEP_ID). This composite unique index confirms that a recipe may associate each routing step at most once, making the pair the natural business key and the recommended join predicate for lookups.

  • RECIPE_ID and ROUTINGSTEP_ID — the composite primary key linking a recipe to a specific routing step; these are the definitive join columns to recipe and routing masters.
  • STEP_QTY — the quantity associated with the step at the recipe level, representing the amount produced or processed during the operation.
  • MASS_QTY, MASS_REF_UOM, MASS_STD_UOM — mass-based quantity, its reference unit of measure (as entered), and the standardized UOM used for calculations.
  • VOLUME_QTY, VOLUME_REF_UOM, VOLUME_STD_UOM — the volume equivalent of the above, allowing dual mass/volume tracking of step output.
  • TEXT_CODE — a short descriptive text or lookup code associated with the step update.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit lineage for each override record.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the descriptive flexfield context and segment columns reserved for customer-specific extensions.

Common Use Cases and Queries

Typical usage centers on recipe explosion, step-level quantity reporting, and audit of recipe-specific overrides. A common query joins this table to the recipe header to retrieve all step updates for a given recipe:

SELECT rrs.recipe_id,
       rrs.routingstep_id,
       rrs.step_qty,
       rrs.mass_qty,
       rrs.mass_std_uom,
       rrs.volume_qty
  FROM gmd.gmd_recipe_routing_steps rrs
 WHERE rrs.recipe_id = :p_recipe_id;

Reporting use cases include comparing reference versus standard UOM values to detect unit conversion discrepancies, auditing who modified step quantities and when using the WHO columns, and extracting DFF attribute values for integration. Because the table captures recipe-level updates, it is also used when validating that a recipe's step quantities are internally consistent before releasing the recipe to production.

Related Objects

FK and PK relationship data classifies this object as standalone, but functional dependency flows through the composite key to the following objects in the GMD Process Manufacturing model:

These joins should be confirmed against the live FK constraints, as documented relationship data for this table is classified as standalone.