Search Results gmd_recipe_validity_rules

Overview

The GMD_RECIPE_VALIDITY_RULES table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing (GMD) module, specifically for Product Development. It serves as the central repository for defining and managing the validity rules associated with a recipe. These rules, historically termed "effectivities," govern the conditions under which a specific recipe version is applicable and can be used for production. The table's primary role is to enforce business logic by linking a recipe to specific organizations, usage contexts (like production or costing), and effective date ranges, thereby ensuring the correct recipe is selected during manufacturing execution and planning processes in releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores the parameters that define a recipe's validity. The primary identifier is the RECIPE_VALIDITY_RULE_ID. Key columns typically include the foreign key to the recipe header (RECIPE_ID), the organization code (ORGANIZATION_ID), and the intended USE (such as 'PRODUCTION' or 'COSTING'), which specifies the operational context. Crucially, the table holds the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, which establish the temporal window for the rule's applicability. It may also store quantity-based effectivity fields, allowing rules to be defined for specific batch size ranges, aligning with the Process Manufacturing requirement for scale-dependent recipes.

Common Use Cases and Queries

A primary use case is validating and retrieving the appropriate recipe version for a given production schedule. For instance, a planner creating a batch in a specific organization for a given date requires the system to identify the valid, effective recipe. Common reporting needs include listing all validity rules for a recipe or identifying which recipes are valid for a particular organization. Sample SQL patterns include:

• Finding the currently valid production recipe for a given item and organization:
  SELECT r.recipe_no, r.version
FROM gmd_recipes r, gmd_recipe_validity_rules v
WHERE r.recipe_id = v.recipe_id
AND v.organization_id = :org_id
AND v.use = 'PRODUCTION'
AND SYSDATE BETWEEN v.effective_start_date AND NVL(v.effective_end_date, SYSDATE);
• Auditing all validity rules for a recipe to understand its change history and organizational deployment.

Related Objects

GMD_RECIPE_VALIDITY_RULES is intrinsically linked to the core recipe definition tables. Its primary foreign key relationship is with GMD_RECIPES (RECIPE_ID). It is also closely related to organizational structures via INV_ORG_PARAMETERS (ORGANIZATION_ID). The table is central to the recipe validation APIs and is referenced by various views and forms within the Product Development and Process Execution suites. Changes to validity rules directly impact production scheduling and execution workflows managed by the GME and GMP modules.