Search Results gr_inv_recipe_v1




Overview
Explore in AI Chat

Overview

GR_INV_RECIPE_V1 is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GR (Process Manufacturing Regulatory Management) product family. Its documented purpose is to return a distinct list of recipe numbers, joined to their corresponding formula numbers and formula versions. The view is defined as VALID in the ETRM 12.2.2 metadata, confirming that it is a supported, compiled database object available for querying in both 12.1.1 and 12.2.2 environments.

Because the view resolves recipe, formula, and status relationships through a single DISTINCT projection, it serves as a lightweight integration and reporting surface for downstream processes that need a clean, de-duplicated inventory of recipes and their associated formulas. It is typically consumed by custom reports, concurrent programs, interfaces, and analytics that must enumerate recipes without traversing the full GMD_RECIPES and FM_FORM_MST relationship structures directly.

Underlying Base Objects

The view is defined over three documented base objects, each accessed through a synonym:

  • GMD_RECIPES (SYNONYM) — aliased as R in the view text; supplies the recipe number and recipe status, and is the primary driver of the DISTINCT projection.
  • FM_FORM_MST (SYNONYM) — aliased as F; supplies the formula number and formula version through the formula identifier.
  • GMD_STATUS (SYNONYM) — aliased as S; provides the status lookup that is joined to the recipe status. This is the object most closely associated with the user's search term gmd_status.

The view joins these objects on the following conditions as documented in the view text:

Note that although GMD_STATUS is included in the FROM clause and joined on STATUS_CODE, no column from GMD_STATUS is projected in the SELECT list. Its role is therefore a validation/reference join rather than a source of output columns.

Key Columns

  • RECIPE_NO — the recipe number from GMD_RECIPES. This is the primary identifier returned and the column around which the DISTINCT clause operates.
  • FORMULA_NO — the formula number from FM_FORM_MST, identifying the formula associated with the recipe.
  • FORMULA_VERS — the formula version from FM_FORM_MST, distinguishing revisions of the same formula.

Because only these three columns are exposed, the view presents a compact, three-attribute result set suitable for lookup and validation use cases.

Common Use Cases and Queries

The view is most commonly used to retrieve a clean list of recipes and their formulas for reporting, LOV (List of Values) population, and interface validation. A basic query returns all active, non-deleted recipes:

  • SELECT RECIPE_NO, FORMULA_NO, FORMULA_VERS FROM APPS.GR_INV_RECIPE_V1;

To restrict results to a specific formula, a WHERE clause on FORMULA_NO is typical:

  • SELECT RECIPE_NO, FORMULA_NO, FORMULA_VERS FROM APPS.GR_INV_RECIPE_V1 WHERE FORMULA_NO = :p_formula_no;

For integrations that need to confirm recipe-to-formula mappings before posting regulatory or inventory data, the view provides an efficient validation source without requiring direct joins across GMD_RECIPES, FM_FORM_MST, and GMD_STATUS. Purely as a reference point, the inclusion of GMD_STATUS in the view definition reflects the standard practice of validating recipe status against the status master, ensuring that only recipes with a defined status are surfaced.