Search Results gma_common_logging




Overview

GMA_COMMON_LOGGING is a PL/SQL package body owned by the APPS schema and validated in the E-Business Suite 12.1.1 and 12.2.2 environments. It belongs to the Process Manufacturing (GMA) product family and provides centralized logging infrastructure for migration and upgrade operations. Its core purpose is to capture diagnostic and audit information generated during data migration activities, persisting that information into dedicated logging tables so that administrators and support personnel can trace the progress and outcome of upgrade routines.

The package is classified as OTHER in the ETRM registry, meaning it is not part of a published public API surface but rather an internal utility that supports the migration subsystem. The dependency listing confirms that GMA_COMMON_LOGGING references FND_LOG, the standard Oracle Applications logging facility, along with two GMA-specific tables. This dual-target design allows migration processes to write both application-level debug messages through FND_LOG and structured migration records through the GMA tables.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit within this package body:

  • GMA_MIGRATION_CENTRAL_LOG — The central logging routine for migration processing. This procedure is the entry point through which migration and upgrade components record their activity. It is responsible for accepting logging input from calling programs and writing the corresponding entries into the migration log repository, while also integrating with the standard FND_LOG facility where appropriate.

No additional procedures or functions are enumerated in the documented metadata. Callers should treat GMA_MIGRATION_CENTRAL_LOG as the supported surface of this package; other internal program units, if present, are not part of the documented interface.

Tables Accessed

The documented dependencies show the following database objects referenced by this package body:

  • GMA_MIGRATION_LOG — The primary persistence target for migration log records. Messages written through GMA_MIGRATION_CENTRAL_LOG are inserted here, forming a durable audit trail of migration activity that survives beyond the lifetime of an individual concurrent request.
  • GMA_UPGRADE_ID_S — A sequence used to generate unique identifiers for upgrade or migration log entries. Invoking the sequence ensures each logged record receives a distinct key, supporting reliable ordering and retrieval of log rows.
  • FND_LOG — The standard Oracle Applications logging package. GMA_COMMON_LOGGING calls into FND_LOG so that migration messages also participate in the framework-wide logging and diagnostic infrastructure, respecting the FND logging level configuration.

The package is listed as not referenced by any other database object, confirming its role as a terminal utility rather than a shared dependency within the schema.

Usage Notes

In the ETRM 12.2.2 registry, GMA_COMMON_LOGGING is documented as being referenced by twenty other packages, indicating that migration and upgrade components across the GMA product call GMA_MIGRATION_CENTRAL_LOG to record their progress. Typical invocation occurs from within migration driver routines, data conversion programs, and upgrade scripts rather than from online forms. Because the package writes to GMA_MIGRATION_LOG, it is most active during upgrade windows, patch application, and data migration runs.

From a customization perspective, developers extending GMA migration logic should invoke the documented procedure rather than inserting directly into GMA_MIGRATION_LOG, so that sequence-based key generation and FND_LOG integration remain consistent. Because the package status is VALID in both 12.1.1 and 12.2.2, the behavior is stable across those releases. Administrators troubleshooting a migration can query GMA_MIGRATION_LOG directly to reconstruct the sequence of events recorded through this package.