Search Results gmd_recipe

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

Overview

The APPS.GMD_RECIPE_HEADER package is a public PL/SQL API within the Oracle E-Business Suite Process Manufacturing (OPM) module, identified by the product code GMD and the business entity GMD_RECIPE. Its stated purpose, per the embedded header documentation, is to provide a programmatic interface for creating, updating, and deleting recipe header information. A recipe header represents the top-level definition of a manufacturing formula or recipe, capturing the product, version, organization, and governing attributes that drive downstream process execution. This package is classified as an OTHER API under the ETRM repository and carries an active lifecycle status with a compatibility designation of S (supported). The source header identifies version 120.3.12010000.2, dated November 2008, indicating the interface has remained stable across the 12.1.1 and 12.2.2 release lines.

The package exposes strongly typed record structures — notably FLEX and UPDATE_FLEX — that carry the 30 descriptive flexfield attribute columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30). These structures allow callers to pass flexfield context and segment values as part of a recipe header transaction, which is essential for customers extending the recipe header with industry-specific or site-specific data.

Key Procedures and Functions

The package documents three procedures, each addressing one lifecycle operation on a recipe header:

• CREATE_RECIPE_HEADER — Inserts a new recipe header record, establishing the recipe identity and its associated flexfield attribute values.
• UPDATE_RECIPE_HEADER — Modifies an existing recipe header, including changes to descriptive flexfield data passed through the UPDATE_FLEX record type.
• DELETE_RECIPE_HEADER — Removes a recipe header, providing the API-based deletion path rather than direct table manipulation.

Parameter lists are intentionally omitted here; integrators should consult the package specification directly for exact signatures. The consistent naming and the presence of a dedicated update flex structure indicate the API performs row-level validation and enforces the integrity rules OPM expects before committing changes.

Tables Accessed

The package operates against several core OPM tables, accessed through APPS synonyms:

• GMD_RECIPES — The base recipe header table; the primary target of insert, update, and delete operations.
• GMD_RECIPES_TL — The translated (language) table holding recipe header descriptive text, maintained in step with the base row.
• FM_FORM_MST — The formula master table, referenced to keep formula and recipe definitions aligned.
• FM_ROUT_HDR — The routing header table, accessed because recipes and routings are linked in process manufacturing.
• FND_USER — Used to resolve the acting user for auditing and WHO column population.
• PLITBLM — A PL/SQL index-by table interface used for bulk or array-style processing within the API.

Usage Notes

GMD_RECIPE_HEADER is typically invoked rather than called directly against the underlying tables. The OPM Recipe and Formula forms consume this API when users maintain recipes through the standard UI. It is equally suited to concurrent programs and custom PL/SQL extensions that need to load, migrate, or interface recipe headers in bulk — for example, converting legacy formulation data or integrating recipes from an external PLM system. Because the package is referenced by five other packages, callers should treat it as a shared dependency and avoid modifying its behavior. Direct DML against GMD_RECIPES and GMD_RECIPES_TL is discouraged, as it bypasses the validation and translated-table synchronization the API performs.