Search Results contiguous_ind




Overview
Explore in AI Chat

Overview

GMD_RECIPES_VL is a validation-level (VL) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Process Manufacturing Product Development module (GMD) and exposes recipe header information maintained within Oracle Process Manufacturing. The view joins the base recipe entity to its translation table, presenting translated descriptive text alongside the operational and descriptive attributes of each recipe, so that consumers see the recipe description in the session's current language.

Because it is a VL view, it is the canonical read interface for recipe headers in forms, concurrent programs, and custom reports. It abstracts the underlying base/translation table split, meaning report authors query a single object rather than performing the join manually. This pattern is standard across EBS for translatable entities and makes GMD_RECIPES_VL suitable for both online form data sources and ad hoc reporting.

Underlying Base Objects

The view is defined over two synonym-referenced base objects:

The join predicate is B.RECIPE_ID = T.RECIPE_ID combined with T.LANGUAGE = USERENV('LANG'), so each row returned represents one recipe version in the language of the current session. The view also surfaces B.ROWID as ROW_ID, which is significant because a pure join of two tables would otherwise not expose an updatable row identifier.

Key Columns

Common Use Cases and Queries

The view is typically used to report recipe headers by organization, to drive LOVs in custom extensions, and to reconcile recipes against their formulas and routings. A common requirement is finding all recipes created within a given organization, which maps directly to the CREATION_ORGANIZATION_ID column the user searched for:

  • List active recipes for an organization: SELECT recipe_id, recipe_no, recipe_version, recipe_description FROM gmd_recipes_vl WHERE creation_organization_id = :org_id AND delete_mark = 0 ORDER BY recipe_no, recipe_version;
  • Join to the formula for traceability: SELECT r.recipe_no, r.recipe_version, r.formula_id FROM gmd_recipes_vl r WHERE r.creation_organization_id = :org_id;
  • Audit recently changed recipes: SELECT recipe_no, recipe_version, last_updated_by, last_update_date FROM gmd_recipes_vl WHERE last_update_date > SYSDATE - 30;

Because RECIPE_DESCRIPTION is language-sensitive, queries executed under different session languages return the corresponding translation, so no additional language filter is required in consumer SQL.