Search Results enhanced_pi_ind




Overview
Explore in AI Chat

Overview

GMD_RECIPES_B is the recipe header base table within the Oracle EBS Process Manufacturing Product Development (GMD) module. It stores the master definition of a manufacturing recipe — the combination of a formula (bill of materials) and a routing (process instructions) that together specify how a product is manufactured at a given organization. Recipes are the central engineering and production planning construct in Process Manufacturing, and GMD_RECIPES_B serves as the anchor record from which process parameters, validity rules, sampling definitions, and dispensing configurations are derived.

The table resides in the GMD schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. Its primary key is GMD_RECIPES_B_PK on RECIPE_ID, a system-generated surrogate key. A secondary unique index, GMD_RECIPES_B_U1 on (RECIPE_NO, RECIPE_VERSION), enforces the natural business key of recipe number and version. The documented physical schema for 12.2.2 contains 59 columns.

Based on the foreign key topology — eleven dependent tables referencing RECIPE_ID and no upward foreign keys from this table to other recipe headers — the heuristic Data Vault classification is hub-leaning. In a Data Vault model, GMD_RECIPES_B would be modeled as a hub keyed on RECIPE_ID, with descriptive attributes such as RECIPE_STATUS and RECIPE_TYPE housed in an adjacent satellite.

Key Information Stored

The following columns carry the greatest functional significance:

Common Use Cases and Queries

A frequent requirement is retrieving the current approved recipe for a given formula and organization:

  • Join GMD_RECIPES_B to dependent tables on RECIPE_ID to assemble the full recipe definition, including process parameters (GMD_RECIPE_PROCESS_PARAMETERS) and validity rules (GMD_RECIPE_VALIDITY_RULES).
  • Trace master-to-production recipe hierarchy by self-joining on MASTER_RECIPE_ID = RECIPE_ID.
  • Filter out soft-deleted rows using DELETE_MARK = 0 in every query, since Oracle does not physically delete recipe records.

A representative query pattern:

  • SELECT r.RECIPE_NO, r.RECIPE_VERSION, r.RECIPE_STATUS, r.RECIPE_TYPE FROM GMD.GMD_RECIPES_B r WHERE r.DELETE_MARK = 0 AND r.RECIPE_STATUS = 'APPROVED';
  • Reporting on recipe version counts by formula, or listing reciprocal recipes by owner organization, relies directly on RECIPE_NO, RECIPE_VERSION, OWNER_ORGN_CODE, and RECIPE_STATUS.

Related Objects

GMD_RECIPES_B is referenced by eleven dependent tables, all joined on RECIPE_ID. The most significant are:

  • GMD_RECIPE_PROCESS_PARAMETERS.RECIPE_ID — Process parameter setpoints and variables for the recipe.
  • GMD_RECIPE_VALIDITY_RULES.RECIPE_ID — Effective-date and validity windows governing recipe use.
  • GMD_RECIPE_EFF_ASSOC.RECIPE_ID — Association of recipe effectivity with organizational context.
  • GMD_RECIPE_PROCESS_LOSS.RECIPE_ID — Detailed step-level loss definitions.
  • GMD_SAMPLES.RECIPE_ID and GMD_SAMPLING_EVENTS.RECIPE_ID — Quality sampling definitions tied to the recipe.
  • GMD_WIP_SPEC_VRS.RECIPE_ID — Work-in-process specification versions.
  • GMO_DISPENSE_CONFIG.RECIPE_ID and GMD_SS_MATERIAL_SOURCES.RECIPE_ID — Dispensing and material source configuration for shop-floor execution.