Search Results qty_update_fxd_scaling

Overview

The APPS.GMD_RECIPE_MIGRATION package is an Oracle EBS Process Manufacturing (OPM/GMD) utility that migrates recipe data from the legacy Oracle Manufacturing formulation structures into the current Oracle Process Manufacturing recipe schema. Its header timestamp ($Header: GMDRMIGS.pls 115.6 2003/04/10) places its development within the 11i-era OPM codebase, and the package remains shipped under schema APPS in EBS 12.1.1 and 12.2.2. The migration path reads legacy formulation and routing master/detail records and writes the modern recipe entities represented by GMD_RECIPES_B, GMD_RECIPES_TL, GMD_RECIPES, and associated customer/effectivity tables. It also normalizes quantity and scaling attributes as part of the conversion. The package is classified as an API of type OTHER, meaning it is not one of the public, externally supported OPM APIs but is instead an internal data conversion routine invoked by Oracle-supplied migration processes or by customers performing one-time upgrades of formulation data. The AUTHID CURRENT_USER declaration means it executes with the privileges of the calling user, and callers must therefore hold the necessary object privileges on the GMD, FM, and FND objects referenced.

Key Procedures and Functions

• MIGRATE_RECIPE — The central driver of the package. It accepts the standard FND API parameter conventions (API version, initialization of the message list, commit control) together with the standard OUT parameters for return status, message count, and message data. It additionally takes a recipe-number choice parameter that governs how the recipe number is determined or reconciled during migration. The procedure performs the actual conversion of a recipe from formulation structures to the GMD recipe tables and reports success or failure through the FND API message stack.
• INSERT_MESSAGE — A logging helper. It records a migration message by passing the source table, target table, source identifier, target identifier, message text, and an error-type code defaulting to 'E' for error. Messages are presumably written to the GMD_MIGRATION table that appears among the referenced objects, providing an audit trail of migration events and failures.
• QTY_UPDATE_FXD_SCALING — A quantity/scaling maintenance routine, taking no documented parameters. It adjusts fixed-scaling quantity values, almost certainly to reconcile unit-of-measure or quantity conversions between the legacy formulation detail quantities and the target recipe quantities. Its results are reflected in the FM_FORM_EFF structure.

Tables Accessed

The package reads legacy formulation and routing data from FM_FORM_MST_B, FM_FORM_EFF (and its backup FM_FORM_EFF_BAK), FM_MATL_DTL, and FM_ROUT_DTL/FM_ROUT_MTL_BAK. Component detail and cost information come from CM_CMPT_DTL and GL_ITEM_CST. Target recipe data is written to GMD_RECIPES_B, GMD_RECIPES_TL, GMD_RECIPES, GMD_RECIPE_CUSTOMERS, and GMD_RECIPE_EFF_ASSOC. Migration logging uses GMD_MIGRATION, while FND_LANGUAGES supports the multi-language recipe descriptions written to GMD_RECIPES_TL.

Usage Notes

Given its internal classification, GMD_RECIPE_MIGRATION is normally invoked by Oracle-supplied migration logic or by custom PL/SQL during a one-time conversion, rather than from a standard EBS form. The package is referenced by three other packages, and one of those callers most likely acts as the orchestrating concurrent program or migration driver. The API follows FND API conventions: the p_init_msg_list flag controls message-list initialization, p_commit controls transaction commit, and callers must inspect x_return_status, x_msg_count, and x_msg_data after each call to detect errors. Because the package writes to log tables, commits should be issued only at appropriate boundaries by the caller. It should not be treated as a public or supported API in 12.1.1/12.2.2.