Search Results gmd_status




Overview
Explore in AI Chat

Overview

APPS.GR_INV_RECIPE_V1 is a reporting and integration view in Oracle EBS Process Manufacturing (OPM/GMP) that exposes the relationship between recipes and their governing formulas. It is designed to answer a common functional question: which formula number and formula version correspond to a given recipe number? The view collapses three base entities — recipes, formulas, and status codes — into a single, de-normalized result set that returns only distinct combinations of recipe number, formula number, and formula version.

The view is relevant to users who search on "gmd_status." Because GMD_STATUS is joined into the view definition, GR_INV_RECIPE_V1 becomes the linkage point between a recipe's status code and the human-readable status records maintained in GMD_STATUS. In Oracle EBS 12.1.1 and 12.2.2, this view is typically consumed by inventory, costing, and production reporting where recipe-to-formula traceability is required without navigating the full OPM data model. It supports read-only reporting and is not intended for transactional DML.

Underlying Base Objects

The documented view text references three base objects, all exposed to APPS through synonyms: GMD_RECIPES, FM_FORM_MST, and GMD_STATUS.

  • GMD_RECIPES (SYNONYM) — aliased as R, the driving table. It supplies RECIPE_NO, RECIPE_STATUS, FORMULA_ID, and the DELETE_MARK soft-delete indicator. The join to GMD_STATUS occurs on STATUS_CODE = R.RECIPE_STATUS.
  • FM_FORM_MST (SYNONYM) — aliased as F, the formula master. It supplies FORMULA_NO and FORMULA_VERS, joined to GMD_RECIPES on FORMULA_ID.
  • GMD_STATUS (SYNONYM) — aliased as S, the status reference table. Although no column from S is projected in the SELECT list, the join is material to the result set: it restricts output to recipes whose RECIPE_STATUS matches a valid status code, and it is the object users investigate when searching "gmd_status."

Key Columns

  • RECIPE_NO — the recipe identifier from GMD_RECIPES. It is the primary business key returned to consumers.
  • FORMULA_NO — the formula number from FM_FORM_MST, linked through FORMULA_ID. It identifies the formulation the recipe is based upon.
  • FORMULA_VERS — the formula version from FM_FORM_MST, indicating the revision of the formula in effect.
  • RECIPE_STATUS / STATUS_CODE — used in the join predicate rather than projected. The status code from GMD_RECIPES must match GMD_STATUS.STATUS_CODE for a row to qualify.
  • DELETE_MARK — a soft-delete flag; only rows with DELETE_MARK = 0 (active, non-deleted recipes) are returned.

Common Use Cases and Queries

Typical uses include validating recipe-to-formula mappings during data migration, reconciling inventory recipes against formulas for costing, and producing audit extracts of active recipe/formula combinations.

  • List all active recipe and formula combinations:
    SELECT recipe_no, formula_no, formula_vers FROM apps.gr_inv_recipe_v1;
  • Retrieve the formula for a specific recipe:
    SELECT formula_no, formula_vers FROM apps.gr_inv_recipe_v1 WHERE recipe_no = :recipe_no;
  • Join to GMD_STATUS to surface the status description: since RECIPE_STATUS is not projected, resolve status by joining from the view's recipe back to GMD_RECIPES and GMD_STATUS on the recipe number.

Because the view applies DISTINCT and a status-based join, consumers should treat it as a reporting convenience rather than a complete recipe master; recipes without a matching GMD_STATUS row will be excluded from the output.