Search Results gmd_recipe_designer_pkg




Overview
Explore in AI Chat

Overview

GMD_RECIPE_DESIGNER_PKG is an Oracle EBS Application Object Library package owned by the APPS schema. It belongs to the Oracle Process Manufacturing (OPM) product family and is classified as an "OTHER" API (that is, it is not a formally published public API, but rather an internal designer/utility package). It exists to support the Recipe Designer and Routing Designer functionality, providing the server-side logic that the OPM Recipe/Routing design forms require when creating, updating, and deleting recipe header records, recipe routing steps, step material links, and supplementary text rows.

The package is the transactional engine behind recipe authoring. Recipes define the formula (materials, quantities, charges) and the routing (steps, operations) used to manufacture a product. GMD_RECIPE_DESIGNER_PKG encapsulates the DML and the calculation logic that keeps those two structures synchronized, allowing the designer UI to commit individual changed rows without writing SQL directly. In ETRM documentation the package is listed with STATUS VALID in both 12.1.1 and 12.2.2, and the dependency map confirms it references the FM_* tables while being referenced by the sibling package GMD_ROUTING_DESIGNER_PKG.

Key Procedures and Functions

The documented interface exposes 32 procedures and functions, which fall into several functional clusters:

No parameter signatures are published in the ETRM metadata; callers should treat the procedures as internal designer contracts. Because the package is not a formal public API, its signatures may change between releases without the compatibility guarantees that apply to published PL/SQL APIs.

Tables Accessed

The package reads and writes the core OPM recipe and FM (FM = "Formula/Routing") tables, referenced through APPS synonyms:

Usage Notes

GMD_RECIPE_DESIGNER_PKG is invoked indirectly rather than directly. Its primary caller is the OPM Recipe Designer form and the related Routing Designer form; the forms call these procedures to persist row-level changes made in the designer blocks. It is also referenced by the sibling package GMD_ROUTING_DESIGNER_PKG, which orchestrates routing-level operations and delegates recipe-side work here.

Because the package is classified as OTHER rather than a published API, customizations and extensions should call it with caution and should preferably be routed through supported APIs or form-based transactions. Typical safe usage patterns are:

  • Form-driven inserts, updates, and deletes of recipe headers, steps, material links, and text rows.
  • Recalculation of step quantities and charges when a recipe is saved or when the recipe size/customer is changed.
  • Validation before delete or warehouse release, using IS_RECIPE_USED_IN_BATCHES to prevent removal of a recipe already consumed in production.

Custom code that calls these procedures must supply the recipe identifier, organization, and step context expected by the internal designer model, and should commit within the form's transaction boundary. The package is version-stable across 12.1.1 and 12.2.2 in terms of status, but its detailed signatures are undocumented in ETRM and should be verified against the deployed database before use.