Results for “gmd_recipe_validity_rules_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMD.GMD_RECIPE_VALIDITY_RULES is a Process Manufacturing Product Development (GMD) table that stores the quantity ranges and effective date ranges under which a recipe is considered valid for a given combination of organization and item. In earlier releases of Oracle Process Manufacturing these records were known as "effectivities"; the object retains that conceptual role while adopting the term "validity rules" in the E-Business Suite 12.1.1 and 12.2.2 data model. Each row binds a recipe to a usage context, expressed through RECIPE_USE, ORGN_CODE, ITEM_ID, and the START_DATE/END_DATE window, and further constrains that context with minimum, maximum, and standard quantity limits.

The table sits directly beneath GMD_RECIPES_B through the RECIPE_ID foreign key, meaning a recipe may own many validity rules, each qualifying a different organization, item, use, or effective period. Because the recipe-to-validity-rule link is the dominant relationship, the metadata's heuristic Data Vault classification of "standalone" can be refined as a modeling suggestion: GMD_RECIPE_VALIDITY_RULES behaves most naturally as a satellite of the GMD_RECIPES_B hub, since it carries descriptive and time-bound attributes keyed to a recipe rather than acting as an independent hub or a pure intersection link between two hubs.

Key Information Stored

The surrogate primary key is RECIPE_VALIDITY_RULE_ID, enforced by the unique index GMD_RECIPE_VALIDITY_RULES_PK. No separate business-key unique index is documented, which means the surrogate identifier is the only guaranteed uniqueness constraint in the physical model. The most operationally significant columns are:

• RECIPE_ID — foreign key to GMD_RECIPES_B; identifies the recipe the rule qualifies.
• ORGN_CODE / ORGANIZATION_ID — the organization context in which the rule applies.
• ITEM_ID / INVENTORY_ITEM_ID — the item to which the recipe validity is scoped.
• RECIPE_USE — the intended use of the recipe (for example, production versus costing), a key discriminator among competing rules.
• START_DATE / END_DATE — the effective window during which the rule is active.
• MIN_QTY / MAX_QTY / STD_QTY — the quantity boundaries and standard quantity for the rule.
• ITEM_UM / DETAIL_UOM — units of measure for the quantity columns.
• INV_MIN_QTY / INV_MAX_QTY — inventory-oriented quantity limits.
• PREFERENCE — ranking used to resolve the preferred rule when several rules match.
• VALIDITY_RULE_STATUS — lifecycle status of the rule.
• PLANNED_PROCESS_LOSS / FIXED_PROCESS_LOSS / FIXED_PROCESS_LOSS_UOM — expected yield-loss parameters.
• REVISION — revision context for the item/recipe combination.
• DELETE_MARK — logical deletion flag.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

The most frequent reporting need is determining which recipe is valid for a given item, organization, use, and date. A typical query filters on the effective window and quantity range:

• SELECT recipe_id, recipe_use, preference FROM gmd_recipe_validity_rules WHERE orgn_code = :org AND item_id = :item AND :txn_date BETWEEN start_date AND end_date AND delete_mark = 0 ORDER BY preference;
• Joining to GMD_RECIPES_B to retrieve recipe names and versions for a validity listing.
• Resolving quantity-based selection by comparing a requested batch size against MIN_QTY and MAX_QTY.
• Auditing expired or future-dated rules by filtering END_DATE or START_DATE relative to SYSDATE.
• Reporting process-loss expectations by aggregating PLANNED_PROCESS_LOSS and FIXED_PROCESS_LOSS.
• Reviewing descriptive flexfield values through ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30.

Related Objects

The table is referenced by several dependent objects that record which validity rule was applied at transaction or batch time:

• GMD_RECIPES_B — parent recipe definition; joined via GMD_RECIPE_VALIDITY_RULES.RECIPE_ID = GMD_RECIPES_B.RECIPE_ID.
• GMD_RECIPE_EFF_ASSOC — association table linking recipe effectivity/validity rule records via RECIPE_VALIDITY_RULE_ID.
• GME_BATCH_HEADER — batch headers capture the RECIPE_VALIDITY_RULE_ID used for the batch.
• GME_BATCH_HEADER_MIG — migration staging of batch headers retaining the same rule reference.
• GMD_VAL_RULE_GTMP — temporary staging table for validity rule processing.

Together these relationships make GMD_RECIPE_VALIDITY_RULES the central control point for recipe selection logic in Process Manufacturing, with downstream batch and migration tables preserving the chosen rule for traceability.