Search Results gma_migration_utils




Overview

GMA_MIGRATION_UTILS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM API taxonomy as OTHER. Its name and public signatures indicate that it serves as a utility layer for data migration within the Process Manufacturing (GMA/GMD) product family. The package declares the AUTHID CURRENT_USER directive, meaning that its SQL statements execute with the privileges of the invoking user rather than the package owner — a deliberate choice that allows migration routines to be run by a DBA or migration operator whose credentials already grant access to the underlying legacy and interface tables.

The source header ($Header: GMAUMIGS.pls 120.1 2005/07/19) establishes that the package has been stable since the 11i era and was carried forward unchanged into 12.1.1 and 12.2.2. The package exposes four public program units: three scalar lookup functions and one migration driver procedure. Together they support the conversion of legacy Process Manufacturing master and transactional data — items, lots, grades, actions, reasons, units of measure, and organization references — into the Oracle EBS data model.

Key Procedures and Functions

  • get_reason_id (p_reason_code) — Returns the numeric reason identifier corresponding to a supplied reason code. It resolves legacy reason codes to the surrogate keys used by the EBS reason tables, allowing migration logic to translate human-readable values into foreign key references.
  • get_organization_id (P_orgn_code) — Returns the organization identifier for a given organization code. Because migration source systems frequently store organization codes rather than numeric organization IDs, this function is the standard translation point between the two. It is the routine most commonly targeted by developers searching for "get_organization_id" in the context of GMA migration code.
  • get_uom_code (P_um_code) — Returns a validated unit-of-measure code for a supplied input code. It performs the mapping and, where appropriate, normalization required before the value can be stored against item or lot records.
  • GMA_EDIT_TEXT_MIGRATION (err_buf, ret_code, migration_var) — A procedure that drives the migration of edit-text data. It follows the standard EBS concurrent-program error convention, returning a message buffer and a numeric return code to the caller while accepting a migration control variable that selects the scope of the run.

Tables Accessed

The package reads and writes a combination of current EBS tables and dedicated migration staging tables. Current-data access includes IC_ITEM_MST and IC_ITEM_MST_B for Process Manufacturing item masters, IC_LOTS_MST and IC_LOTS_MST_MIG for lot data, GMD_ACTIONS_B, GMD_GRADES_B, MTL_ACTIONS_B, MTL_GRADES_B, and MTL_LOT_NUMBERS for action, grade, and lot number definitions, MTL_SYSTEM_ITEMS and MTL_PARAMETERS for inventory item and organization parameter validation, and SY_ORGN_MST, SY_REAS_CDS_B, and SY_UOMS_MST for organization, reason-code, and unit-of-measure lookups. The "_MIG" suffixed tables (IC_ITEM_MST_B_MIG, IC_LOTS_MST_MIG) are staging interfaces populated by external extraction programs and consumed during the migration run.

Usage Notes

GMA_MIGRATION_UTILS is invoked almost exclusively from custom migration code, SQL*Loader control scripts, or concurrent programs built for data conversion projects — not from standard Oracle Forms. The three lookup functions are typically called inside INSERT ... SELECT statements to resolve codes to IDs at load time, while GMA_EDIT_TEXT_MIGRATION is invoked as a standalone batch step, with its err_buf and ret_code parameters logged to a migration log table. ETRM records the package as referenced by one other package, indicating a narrow, migration-specific call graph. Because the API classification is OTHER rather than a supported public API, Oracle does not guarantee signature stability across releases; organizations should wrap calls defensively and re-validate behavior after any upgrade.