Search Results gmd_recipes_b

Overview

The GMD_RECIPES_B table is the fundamental base table for storing recipe header information within Oracle E-Business Suite Process Manufacturing Product Development (GMD). It serves as the central repository for the master definition of a recipe, which is a core entity governing the formula, process instructions, and quality specifications for manufacturing a product. Every operational recipe used in production, planning, and costing is anchored to a record in this table. Its role is critical as it establishes the unique identity and version control for all recipes in the system, forming the primary point of integration between product development and manufacturing execution modules.

Key Information Stored

The table stores the essential metadata that defines a recipe's identity and lifecycle. The primary identifier is the system-generated RECIPE_ID, which serves as the surrogate key for all related child tables. The business key is composed of RECIPE_NO (the unique recipe number or code) and RECIPE_VERSION, which together enforce uniqueness and manage revisions. While the provided metadata does not list all columns, typical attributes stored in this or associated detail tables include the recipe description, status (e.g., Active, Inactive), effective dates, owner, the associated product (ITEM_ID), and the recipe type. The dual primary key constraints (GMD_RECIPES_B_PK on RECIPE_ID and GMD_RECIPES_B_U1 on RECIPE_NO, RECIPE_VERSION) underscore the importance of these columns for data integrity and access patterns.

Common Use Cases and Queries

This table is central to numerous operational and reporting activities. Common use cases include retrieving a list of all active recipes for a specific product, validating recipe existence and version before creating a production batch, and generating master recipe lists for audits. A typical query pattern involves joining to inventory tables to get product details:

• SELECT r.recipe_no, r.recipe_version, r.description, msi.segment1 item_code FROM gmd_recipes_b r, mtl_system_items_b msi WHERE r.item_id = msi.inventory_item_id AND r.recipe_status = 'ACTIVE';

For version analysis, queries often use the RECIPE_NO and RECIPE_VERSION to find the latest or a specific revision of a recipe, which is essential for ensuring the correct manufacturing instructions are used.

Related Objects

As the core header table, GMD_RECIPES_B has a one-to-many relationship with numerous detail tables in the GMD schema. The documented foreign key relationship explicitly shows that the GMD_RECIPE_PROCESS_PARAMETERS table references GMD_RECIPES_B via the RECIPE_ID column to store specific processing instructions and targets for the recipe. Other critical related tables not listed in the excerpt but integral to the recipe structure typically include GMD_RECIPE_VALIDITY_RULES (for effectivity), GMD_RECIPE_INGREDIENTS (for the formula), and GMD_RECIPE_OPERATIONS (for routing steps). All these child entities use the RECIPE_ID from GMD_RECIPES_B as their foreign key to maintain referential integrity.