Search Results update_recipe_header

Overview

APPS.GMD_RECIPE_HEADER_PVT is a private PL/SQL package within the Oracle E-Business Suite Process Manufacturing (OPM) module. It encapsulates the core business logic for creating, maintaining, copying, and validating recipe headers, which serve as the master definition of manufacturing formulas and their associated routings. In Oracle EBS 12.1.1 and 12.2.2, this package acts as the private implementation layer that supports the recipe designer and recipe generation functionality exposed to end users. Because it is classified as a PVT (private) API rather than a public API, it is intended for internal consumption by other OPM packages and forms rather than for direct customer invocation. The package depends on the GMD_RECIPE_HEADER table and the GMD_RECIPES_B base table, and it is referenced by several higher-level components, including GMD_RECIPE_DESIGNER_PKG, GMD_RECIPE_GENERATE, and GMD_RECIPE_HEADER itself. Its ETRM status is VALID, confirming it is a supported and active object in the APPS schema.

Key Procedures and Functions

The documented package exposes five procedures that collectively manage the recipe header lifecycle:

• CREATE_RECIPE_HEADER — Establishes a new recipe header record, initializing the recipe with its identifying attributes and organizational context so that formula and routing details can subsequently be attached.
• UPDATE_RECIPE_HEADER — Modifies an existing recipe header, allowing changes to header-level attributes such as recipe name, status, and validity information.
• DELETE_RECIPE_HEADER — Removes a recipe header and its related definition from the system, honoring referential integrity against associated formula and routing data.
• COPY_RECIPE_HEADER — Duplicates an existing recipe header to create a new recipe based on an established definition, a common operation when engineering variants of a product.
• VALIDATE_FORMULA — Performs validation logic against the formula structure associated with a recipe, checking consistency and completeness before the recipe can be used in production.

These procedures are the mechanism through which recipe data is safely manipulated while preserving the relationships between the recipe header and its subordinate structures.

Tables Accessed

The package interacts with a broad set of OPM tables through APPS synonyms. It reads and writes GMD_RECIPES_B and GMD_RECIPES, the base and translation tables for recipe definitions, and uses GMD_RECIPE_ID_S to obtain surrogate keys. Formula structure is handled via FM_FORM_MST, FM_FORM_MST_B, and FM_MATL_DTL, while routing details rely on FM_ROUT_HDR, FM_ROUT_DTL, GMD_ROUTINGS_B, and GMD_RECIPE_ROUTING_STEPS. Additional recipe detail is captured in GMD_RECIPE_STEP_MATERIALS and GMD_RECIPE_VALIDITY_RULES. GMD_STATUS supplies status code validation, and FND_USER provides the application user context for auditing.

Usage Notes

As a private package, GMD_RECIPE_HEADER_PVT is not called directly by end users or typical custom code. It is invoked indirectly through the Recipe Designer form, the recipe generation concurrent program (GMD_RECIPE_GENERATE), and the GMD_RECIPE_DESIGNER_PKG and GMD_RECIPE_HEADER packages that reference it. Developers extending OPM functionality should prefer the public APIs; if internal invocation is unavoidable, it must respect the private nature of the package, because its signature may change between releases. The package is valid in both 12.1.1 and 12.2.2, though behavior and underlying table structures should be verified against the target release during implementation.