Search Results manage_existing_validity

Overview

GMD_RECIPE_GENERATE is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, and its status is VALID in both the 12.1.1 and 12.2.2 environments. In the context of Oracle Process Manufacturing (OPM), the package provides the core server-side logic for generating production recipes and their associated validity rules from source definitions. It is a member of the GMD (Process Manufacturing) family of APIs and is classified under the generic "OTHER" API category, indicating that it is primarily a procedural utility rather than a formally published interface.

Functionally, GMD_RECIPE_GENERATE automates the creation of recipe records far beyond what manual form entry would allow. It reads header, detail, routing, and formula master data, then writes generated recipes, validity rules, and generation audit records into their respective base tables. By centralizing this logic, the package ensures consistency between recipe headers, details, routings, and the time-phased validity rules that govern when a recipe is effective.

Key Procedures and Functions

ETRM documentation lists eight documented procedures and functions within this package:

• RECIPE_GENERATE — The primary entry point. It drives the overall generation of recipes from the given source, orchestrating the remaining routines.
• CREATE_VALIDITY_RULE_SET — Creates a grouping (set) of validity rules that apply to a recipe or range of recipes.
• CREATE_VALIDITY_RULE — Creates an individual validity rule, typically supplying the effective-date boundaries for a recipe.
• CREATE_RECIPE — Inserts a new recipe record, presumably using the recipe header and detail private APIs and base tables.
• CALCULATE_DATE — Computes derived dates used during validity and generation processing, such as effective start or end dates.
• MANAGE_EXISTING_VALIDITY — Evaluates and manages validity rules that already exist, resolving overlaps or conflicts during regeneration.
• CREATE_VALIDITY — Inserts the validity record linking a recipe to its validity rules.

These routines collectively implement the recipe-generation workflow: parse input, compute dates, create the recipe, build validity rules and sets, and reconcile with any pre-existing validity data.

Tables Accessed

Through APPS synonyms, the package reads and writes several core OPM and shared tables:

• GMD_RECIPES_B and GMD_RECIPES_TL — Store recipe header base records and translated descriptions.
• GMD_RECIPE_GENERATION — Tracks generation runs and their output.
• GMD_RECIPE_VALIDITY_RULES — Persists the validity rules created by the package.
• GMD_ROUTINGS_B and FM_ROUT_HDR — Supply routing and formula routing header data.
• FM_FORM_MST and FM_FORM_MST_B — Provide formula master information used as source data for recipes.
• GMD_STATUS — Supplies status codes applied to generated records.
• GMD_PARAMETERS, IC_ITEM_MST, and FND_USER — Provide setup parameters, item master validation, and user context.

Usage Notes

The package is not referenced by any other database object, though it in turn depends on utility and private packages such as GMD_RECIPE_HEADER_PVT, GMD_RECIPE_DETAIL_PVT, GMD_PROCESS_INSTR_UTILS, GMD_STATUS_PUB, and the FND_API/FND_MSG_PUB stack. It is typically invoked from the OPM recipe-generation concurrent program or from the Recipes form when a user triggers generation of one or more recipes. Custom code may call RECIPE_GENERATE directly to bulk-create recipes for a product or routing, provided the standard FND message and API initialization conventions are observed. Because the package writes to base recipe and validity tables, it should be run within a controlled transaction and validated against GMD_STATUS and GMD_PARAMETERS setup before execution.