Search Results gmd_recipe_process_loss




Overview
Explore in AI Chat

Overview

GMD_RECIPE_PROCESS_LOSS is a table in the GMD schema owned by the Oracle Process Manufacturing Product Development module. It stores process loss at the recipe level, allowing formulators and production planners to define expected yield losses that occur during the manufacture of a product defined by a recipe. Unlike operation-level loss definitions, which attach to individual routing steps, this table captures the aggregate or organization-specific loss behavior associated with the recipe header, making it a foundational element for yield planning, cost rollup, and material requirement calculations in process manufacturing.

From a Data Vault modeling perspective, the mined foreign key structure suggests this object behaves as a standalone entity. The heuristic classification therefore recommends treating it as a satellite-like structure anchored to the recipe hub (GMD_RECIPES_B via RECIPE_ID), rather than as a true link between multiple hubs. This classification is a modeling suggestion only; the table participates directly in the EBS operational model and is not physically implemented as a Data Vault artifact.

Key Information Stored

The table contains fourteen documented columns. The most significant are:

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all process loss definitions for a given recipe or organization, validating that expected loss percentages are within tolerance, and feeding yield calculations into cost rollups or MRP planning. A representative query joining the recipe header follows:

SELECT r.recipe_no, r.recipe_version, l.orgn_code, l.process_loss, l.fixed_process_loss, l.fixed_process_loss_uom FROM gmd.gmd_recipe_process_loss l, gmd.gmd_recipes_b r WHERE l.recipe_id = r.recipe_id AND l.orgn_code = :p_orgn_code;

Additional scenarios include reconciliation reports comparing operation-level and recipe-level loss, extracts for manufacturing execution systems, and validation scripts confirming that no recipe lacks a loss definition for an active organization. Because the primary key is a surrogate and the business key is composite, upsert logic in interfaces should key on RECIPE_ID and ORGN_CODE rather than on RECIPE_PROCESS_LOSS_ID.

Related Objects

The following objects are most significant in relation to this table:

  • GMD_RECIPES_B — The recipe header table; joined on RECIPE_ID, the sole documented foreign key.
  • GMD_RECIPE_OPERATIONS — Operation-level definitions where per-step loss is captured and compared.
  • GMD_RECIPE_INGREDIENTS — Ingredient lines whose quantities are affected by recipe-level yield loss.
  • GMD_RECIPE_VALIDITY_RULES — Rules governing recipe applicability by organization and date.
  • MTL_SYSTEM_ITEMS_B — Item definitions for products produced by the recipe, connected via the recipe header.
  • ORG_ORGANIZATION_DEFINITIONS — Organization validation for ORGN_CODE and ORGANIZATION_ID.

No public PL/SQL API is documented specifically for this table; maintenance is performed through the Process Manufacturing Product Development forms and concurrent processes that operate on the parent recipe.