Search Results validate_desc_flex_definition

Overview

GMI_PRE_MIGRATION is a public PL/SQL package body owned by APPS that supports the Oracle Process Manufacturing (OPM) convergence migration. The package contains the logic used for pre-migration validation, ensuring that legacy OPM and discrete (ODM) data structures can be reconciled before the migration proceeds. The package header comment identifies it as part of the OPM convergence effort, created in 2005 during the 11i/12.x release cycle and carried forward into EBS 12.1.1 and 12.2.2.

The central concern addressed by this package is conflict detection in descriptive flexfield usage. When discrete manufacturing and OPM coexist in the same instance, both may attempt to use the same descriptive flexfield structures for item definition. Left unresolved, such overlaps produce ambiguous or corrupt flexfield data after convergence. GMI_PRE_MIGRATION provides a programmatic pre-flight check so that conflicts are surfaced and corrected before migration begins.

Key Procedures and Functions

The ETRM metadata documents a single public procedure: VALIDATE. The source excerpt shows that this package exposes a procedure named validate_desc_flex_definition, which performs the descriptive flexfield conflict validation. Its documented purpose is to detect conflicts in descriptive flexfield usage between discrete and OPM item flexfields, taking parameters for the migration run identifier, the OPM descriptive flexfield name, and the ODM descriptive flexfield name. Per the documented synopsis, it is invoked in the form validate_desc_flex_definition('ITEM_FLEX', 'MTL_SYSTEM_ITEMS'), reflecting typical OPM and ODM flexfield naming.

The procedure opens a cursor that joins FND_DESCR_FLEX_COLUMN_USAGES with FND_DESCR_FLEX_CONTEXTS, filtered to application_id 551 and the supplied OPM flexfield name, with only enabled columns considered. This query identifies column usages that may collide with the discrete definition. Consistent with the package's stated purpose, the procedure logs or reports the resulting conflict for the given migration run.

Tables Accessed

The documented tables fall into two groups. Flexfield metadata tables — FND_DESCR_FLEX_COLUMN_USAGES and FND_DESCR_FLEX_CONTEXTS — are read to resolve column usages and contexts for the descriptive flexfields under comparison. These are the core tables used by validate_desc_flex_definition.

The remaining tables are OPM and inventory structures read during the broader pre-migration validation: IC_ITEM_MST_B, IC_LOCT_INV, IC_LOCT_MST, IC_LOTS_MST, IC_WHSE_MST, and IC_XFER_MST supply OPM item, location, lot, warehouse, and transfer data; MTL_ITEM_LOCATIONS, MTL_PARAMETERS, and MTL_SECONDARY_INVENTORIES supply the corresponding discrete inventory definitions. Access is read-only, consistent with a validation-only role.

Usage Notes

GMI_PRE_MIGRATION is invoked as part of the OPM convergence migration workflow rather than from standard application forms. It is typically executed by migration scripts or concurrent programs that orchestrate pre-migration checks, and can also be called from custom code that performs readiness validation. The package is not referenced by other documented packages, indicating it acts as a leaf-level validation utility. The flexfield conflict check derived from validate_desc_flex_definition is a specific, targeted validation that should be run and its results reviewed before the convergence migration is authorized to proceed.