Search Results gmd_recipe_migration




Overview
Explore in AI Chat

Overview

The APPS.GMD_RECIPE_MIGRATION package body is a Process Manufacturing (OPM) utility that supports the migration of recipe data between Oracle EBS releases and within the OPM recipe data model. It is classified as an OTHER API, meaning it is not part of the published, externally supported API surface but is instead a targeted internal utility used to convert, copy, or re-establish recipe structures when underlying table layouts change. In the context of Oracle EBS 12.1.1 and 12.2.2, this package is most closely associated with the recipe migration path that moves legacy recipe formulations from older OPM structures into the current GMD_RECIPES family of tables, reconciling header, translation, validity, customer, and step-material records. The package is owned by APPS, has a status of VALID, and is documented as being referenced by three other packages, indicating it is consumed by higher-level migration or validation drivers rather than being invoked directly by end users.

Key Procedures and Functions

The documented package metadata lists three procedures/functions:

  • MIGRATE_RECIPE — The primary driver of the package. It performs the end-to-end migration of a single recipe, orchestrating the copy of recipe header, translation, customer, validity rule, and step material rows into the target structures. It is the entry point through which callers submit a recipe for migration.
  • INSERT_MESSAGE — A message-handling utility that records informational, warning, or error messages generated during migration. It integrates with the Oracle message stack (via FND_MSG_PUB) so that migration outcomes can be surfaced to the caller or to a concurrent program log.
  • QTY_UPDATE_FXD_SCALING — A quantity-update helper that adjusts scaled quantities for recipe materials when fixed-scaling logic applies. It ensures that material quantities remain internally consistent after the recipe structure is migrated.

Parameter lists are not documented in the ETRM metadata and are therefore not reproduced here. Developers should treat these procedures as internal and verify signatures against the deployed source before any custom invocation.

Tables Accessed

Through APPS synonyms, the package reads and writes the core OPM recipe tables: GMD_RECIPES, GMD_RECIPES_B, and GMD_RECIPES_TL (base and translation headers), GMD_RECIPE_STEP_MATERIALS, GMD_RECIPE_CUSTOMERS, GMD_RECIPE_EFF_ASSOC, and GMD_RECIPE_VALIDITY_RULES. It also touches the migration control table GMD_MIGRATION and the sequence GMD_RECIPE_ID_S. Legacy formulation and routing tables — FM_FORM_MST_B, FM_FORM_EFF, FM_FORM_EFF_BAK, FM_MATL_DTL, FM_ROUT_DTL, and FM_ROUT_MTL_BAK — are referenced to source or back up data during conversion. Supporting lookups include CM_CMPT_DTL (component detail), GL_ITEM_CST (item cost), IC_ITEM_MST (item master), PM_BTCH_HDR (batch header), FND_LANGUAGES, and the validation API GMD_RECIPE_VAL.

Usage Notes

GMD_RECIPE_MIGRATION is an internal migration utility and is not intended for direct interactive use. It is most commonly invoked indirectly through recipe migration concurrent programs or through the higher-level packages that reference it, particularly during upgrade or data-conversion activities when legacy formulation data must be transformed into the current OPM recipe model. Because it writes to production recipe tables, any invocation should be preceded by a full backup of the affected GMD_RECIPES and formulation tables, and should be executed within a controlled migration window. Message output is routed through FND_MSG_PUB, so error triage should be performed against the message stack rather than relying solely on return codes. Custom code should avoid calling this package directly; where recipe manipulation is required, the supported OPM recipe APIs and validation routines should be used instead, and any dependency on this package should be re-verified across the 12.1.1 to 12.2.2 upgrade boundary.