Search Results gma_migration_central_log

Overview

GMA_COMMON_LOGGING is an Oracle EBS PL/SQL package owned by APPS that provides shared logging utilities for the Oracle Process Manufacturing (OPM) migration and upgrade framework. In EBS 12.1.1 and 12.2.2, OPM upgrade activities—data conversions, schema migrations, and other batch-driven transitions—generate large volumes of diagnostic output that must be captured in a consistent, queryable repository. This package supplies that centralized logging service, allowing migration programs across the OPM product family to record messages, error context, and database exceptions in a uniform format.

The package is classified under the ETRM API classification "OTHER," indicating that it is an internal framework utility rather than a supported public API. Its header comments identify it as a "noship" object, meaning it is not shipped as part of a customer-facing interface but is nonetheless present in the APPS schema and relied upon by numerous dependent objects.

Key Procedures and Functions

The package exposes a single documented procedure, GMA_MIGRATION_CENTRAL_LOG, which is the programmatic entry point for writing a log record to the central migration log. As the name implies, the procedure funnels individual log events into a central repository so that all migration activity can be reviewed from one location rather than scattered across operating-system log files or temporary tables.

From the parameter naming conventions visible in the package specification, the procedure accepts a run identifier, a log-level indicator, an application short name, a message token, and a context descriptor. It further supports optional table-name and parameter/token pairs that allow callers to embed substitution values and additional diagnostic detail into the emitted message. A dedicated database-error parameter permits capture of native Oracle error information, typically a SQLCODE or SQLERRM value, alongside the application-level message. Because the parameter list must not be inferred beyond what is documented, callers should reference the shipped specification for exact argument names, ordering, and data types.

Tables Accessed

The procedure interacts with two documented objects, both referenced through APPS synonyms. The first, GMA_MIGRATION_LOG, is the primary target of the logging operation; each invocation inserts or updates a row representing a single log event, keyed in part by the run identifier so that related messages can be grouped by migration run. The second, GMA_UPGRADE_ID_S, is a sequence used to supply unique identifiers, most likely for the log entry itself or for the run under which entries are grouped. Together these objects form the persistence layer that makes migration diagnostics durable and reportable after a run completes.

Usage Notes

GMA_COMMON_LOGGING is an internal dependency of the OPM upgrade and migration codebase. ETRM documents it as being referenced by 20 other packages, confirming that it is invoked programmatically by sibling migration routines rather than directly by end users. Typical invocations occur inside concurrent-program worker logic, PL/SQL batch drivers, and upgrade scripts that need to record progress, warnings, and fatal errors. It is not normally called from Oracle Forms, and there is no documented responsibility or menu function associated with it.

Because the package is classified "OTHER" and marked noship, customizations should avoid calling it as a supported interface. Sites that need to review migration outcomes should query GMA_MIGRATION_LOG rather than invoke the procedure directly, and any customer code that does call GMA_MIGRATION_CENTRAL_LOG should treat the signature as subject to change in future patches.