Search Results insert_operation_resource

Overview

GMD_OPRN_MIGRATION is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the process manufacturing (Process Manufacturing / OPM) migration of legacy routing and operation data into the Oracle Manufacturing tables. It is an internal, non-public API classified as OTHER rather than as a supported business API, meaning it is intended to be executed by Oracle migration utilities or seeded concurrent programs rather than called directly by customer extensions. The package moves operation detail records from a legacy staging structure (FM_OPRN_DTL_BAK) into the production OPM operation, activity, and resource tables. In release 12.2.2 the package body is documented as VALID, confirming it remains compiled and available.

Key Procedures and Functions

• INSERT_GMD_OPERATIONS — Inserts the primary operation header records into the OPM operations tables, establishing the operation identity and its translatable/attribute rows.
• INSERT_GMD_OPERATION_COMPS — Inserts operation component records, associating the material or product components consumed or produced by each migrated operation.
• INSERT_OPERATION_ACTIVITY — Inserts operation activity records that link operations to the activities performed against them.
• INSERT_OPERATION_RESOURCE — Inserts operation resource records, capturing the resources (equipment, labor, or other resource detail) assigned to each operation.

These four procedures follow a consistent pattern: each reads the corresponding staged rows and writes normalized records into the target GMD and FM operation tables. No parameters are documented in the ETRM metadata, so the procedures should be regarded as internal drivers invoked in a fixed sequence rather than as parameterized APIs.

Tables Accessed

The documented target tables include GMD_OPERATIONS and GMD_OPERATIONS_B (the base and attribute operation definitions), GMD_OPERATION_ACTIVITIES, and GMD_OPERATION_RESOURCES, which receive the header, activity, and resource data respectively. GMD_STATUS is consulted for valid operation status codes. The staging and reference sources include FM_OPRN_DTL_BAK (the backup of operation detail rows), FM_ROUT_DTL (routing detail), CR_RSRC_DTL (resource detail), and FM_FORM_EFF_BAK (formula effect rows). DUAL is used for single-row lookups. Together these tables show that the package reads legacy/backup manufacturing structures and writes the corresponding operations, activities, and resources into the OPM model.

Usage Notes

GMD_OPRN_MIGRATION is referenced by no other packages, so it sits at the top of its own call chain and is not part of a wider OPM API family. It is typically invoked from migration or upgrade concurrent programs, or from conversion scripts that load legacy routing and operation data into OPM during an implementation or data conversion project. Because the procedures are unparameterized and operate against fixed backup tables, the staging data must be populated before the package is run. Practically, the sequence should be executed in dependency order — operations first, then components, activities, and resources. The package should be treated as an internal utility: it is not supported for direct customer calls, it should be run inside a controlled maintenance window with table backups taken, and results should always be verified against the target OPM operation tables before the data is committed for production use in 12.1.1 or 12.2.2.