Search Results get_activity

Overview

GMD_OPRN_MIGRATION is an Oracle E-Business Suite PL/SQL migration package owned by the APPS schema and classified under the ETRM taxonomy as an OTHER API. Its purpose is to migrate legacy process manufacturing operation and resource structures into the current Process Execution (GMD) model. The package reconciles data originally held in legacy routing, recipe, and formula effectivity tables with the modern operation, activity, and resource entities that drive shop-floor execution. It is particularly concerned with deriving a correct operation status for migrated records so that inactive, obsolete, or purged operations are not inadvertently reintroduced during upgrade runs.

The package header comment reflects a maintenance lineage extending to 2006, and the body carries bug-fix annotations referencing specific defects. Bug 3601848 added an existence filter to prevent the migration from re-adding deleted activities and resources when a customer upgraded from 11.5.9 to 11.5.10. Bug 5383916 reinforced the default assignment of operation status, and related logic ensures that operations whose effectivity is locked are treated differently from ordinary ones.

Key Procedures and Functions

• INSERT_GMD_OPERATIONS — The primary driver procedure. It scans GMD_OPERATIONS_B for rows whose operation_status is null, resolves the associated routing and formula identifiers, and calls GMDFMVAL_PUB.locked_effectivity_val to determine whether the effectivity is locked. A locked formula yields status 900; otherwise the default status 700 is retained. Operations flagged inactive or marked for deletion are set to status 1000 (obsoleted). The procedure then updates GMD_OPERATIONS_B with the resolved status, the effective start date derived from the creation date, and the owner organization code obtained through FND_PROFILE.VALUE_SPECIFIC for the GEMMS_DEFAULT_ORGN profile option.
• INSERT_GMD_OPERATION_COMPS — Migrates the component or ingredient relationships associated with an operation into the corresponding GMD component entity, establishing the material inputs required by the operation.
• INSERT_OPERATION_ACTIVITY — Populates GMD_OPERATION_ACTIVITIES, creating the activity records that are linked to migrated operations. This is the closest documented analogue to the user search term "get_activity"; the package does not expose a standalone getter named GET_ACTIVITY, and activity retrieval is handled through the migration cursors and this insert procedure.
• INSERT_OPERATION_RESOURCE — Populates GMD_OPERATION_RESOURCES, transferring legacy resource details from CR_RSRC_DTL into the current operation resource structure used for capacity and scheduling.

Tables Accessed

The package reads from FM_OPRN_DTL_BAK, FM_ROUT_DTL, and FM_FORM_EFF_BAK to resolve routing and formula effectivity relationships that originated in the legacy Oracle Process Manufacturing model. CR_RSRC_DTL supplies the source resource definition data. GMD_OPERATIONS_B and GMD_OPERATIONS serve as the primary write targets for operation headers and their translations, while GMD_OPERATION_ACTIVITIES and GMD_OPERATION_RESOURCES hold the migrated child entities. GMD_STATUS is referenced for the status code domain (values 700, 900, and 1000 represent the active, locked, and obsoleted states used here). DUAL is used for trivial row selection within the PL/SQL logic.

Usage Notes

GMD_OPRN_MIGRATION is not an online API invoked from standard EBS forms. It is a migration utility executed during upgrade or data-conversion activity, typically through a concurrent program or an ad hoc SQL*Plus session run by a DBA or implementation consultant. It is not referenced by any other package, confirming its role as a terminal, one-way migration routine rather than a reusable library. Because it mutates GMD_OPERATIONS_B and its children, subsequent re-runs depend on the null-status filter to remain idempotent; the exists-style guard introduced for Bug 3601848 is the mechanism that prevents duplicate activity and resource rows. Custom code should avoid calling these procedures outside a controlled migration window, since status derivation and profile-dependent organization assignment would otherwise alter live operational records.