Search Results gme_migration

Overview

The APPS.GME_TRANSFORM_BATCH package is an Oracle Process Manufacturing (OPM) Process Execution migration utility supplied by Oracle E-Business Suite. Its documented purpose is to transform GME (Process Execution) data from release 11.5.10 to release 12, as stated in the package header comment: "This package transforms GME data from 11.5.10 to 12." It belongs to the OPM Process Execution APIs family and is owned by the APPS schema. The package is classified under the "OTHER" API category in ETRM, indicating that it is an internal migration/upgrade component rather than a public, supported integration API.

The header revision ($Header: GMEVTRFS.pls 120.3 2005/11/21 …) confirms it was authored in the 11.5.10-to-12 upgrade timeframe and has been carried forward into the 12.1.1 and 12.2.2 codelines. It is not referenced by any other package, which reinforces its role as a top-down upgrade driver invoked during the upgrade cycle rather than a reusable library.

Key Procedures and Functions

• GET_PROFILE_VALUE — A function that retrieves the value of a named profile option for a given application identifier. It is used internally to obtain migration-related profile settings.
• GME_MIGRATION — The top-level driver procedure for the GME data transformation. It accepts a migration run identifier and a commit flag, and returns a failure count. It orchestrates the subordinate transformation steps.
• CREATE_GME_PARAMETERS — Creates GME parameter records required by the transformed data set, returning an exception count.
• UPDATE_BATCH_HEADER — The procedure most commonly referenced in upgrade troubleshooting. It updates batch header records as part of the migration, keyed by the migration run identifier, and returns an exception count. This is the object returned when users search on "update_batch_header."
• UPDATE_WIP_ENTITIES — Updates WIP entity records associated with GME batches, returning an exception count.
• UPDATE_FROM_DOC_NO — Populates or corrects document-number-derived values for the migration run.
• UPDATE_REASON_ID — Populates or corrects reason identifiers on migrated records.

Tables Accessed

The package reads and writes the following documented objects (through APPS synonyms):

• GME_BATCH_HEADER — The primary batch header table updated by UPDATE_BATCH_HEADER.
• GME_PARAMETERS — Populated by CREATE_GME_PARAMETERS.
• GME_RESOURCE_TXNS and GME_RESOURCE_TXNS_MIG — Resource transaction data and its migration staging counterpart.
• WIP_ENTITIES and WIP_ENTITIES_S — Work-in-process entity records and their sequence source, updated by UPDATE_WIP_ENTITIES.
• GMD_RECIPE_VALIDITY_RULES — Recipe validity data consulted during transformation.
• GME_GANTT_DOCUMENT_FILTER — Gantt view filtering data.
• FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — Profile option definitions and values used by GET_PROFILE_VALUE.
• MTL_GEN_OBJECT_ID_S and SY_DOCS_SEQ — Sequence sources for document and object identifiers.
• SY_ORGN_MST and SY_REAS_CDS_B — Organization master and reason code seed data.
• DUAL — Used for singleton queries.

Usage Notes

GME_TRANSFORM_BATCH is not a form-driven or concurrent-program-invoked API in the normal operational sense. It is executed by the Oracle Applications upgrade driver during the 11.5.10-to-12 (and subsequent 12.1.1/12.2.2) upgrade path, typically under the control of GME_MIGRATION with an appropriate migration run identifier and commit mode. Because it is classified as "OTHER" and is referenced by zero other packages, it should not be called directly from custom code. The individual procedures are separately addressable for diagnostic reruns when a migration run reports exceptions, but any such invocation should be performed only under Oracle Support guidance, as direct execution against production batch header data carries data-integrity risk.