Search Results gmd_migration

Overview

GMD_MIGRATION is a table in the GMD schema, owned by the Oracle Process Manufacturing (OPM) Product Development module. Its documented purpose is to store error messages generated during data migration from Oracle E-Business Suite 11i to 11i+ (and, by extension, into later releases such as 12.1.1 and 12.2.2). Rather than holding transactional product-development data, the table functions as a diagnostic log: each row captures a specific migration attempt and records whether the source record was successfully mapped to its target, or reports the message text associated with a failure.

Because migration logs are narrow, append-oriented records that describe the outcome of a single event, the heuristic Data Vault classification mined from the foreign-key structure is standalone. In Data Vault modeling terms, this suggests the table behaves closest to a satellite attached to its migration and target parents, rather than a hub or link. Modelers should treat this classification as a suggestion only; the physical table is a conventional relational log with two foreign keys and no dependent children of its own.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains six columns. The most significant are:

• MIGRATION_ID — Foreign key to HR_DM_MIGRATIONS. Identifies the parent migration run or migration definition under which the error or mapping occurred. This is the primary grouping key for reporting.
• SOURCE_TABLE — Name of the source table from which the record was being migrated.
• TARGET_TABLE — Name of the destination table into which the record was to be written.
• SOURCE_ID — Identifier of the specific source row involved in the migration attempt.
• TARGET_ID — Foreign key to AMS_DM_TARGETS_B, identifying the target definition or target record participating in the mapping.
• MESSAGE_TEXT — The error or informational message produced during the migration, which is the primary diagnostic payload of the table.

No surrogate primary key is documented in the provided metadata, and no unique index or business-key candidate is specified. In practice MIGRATION_ID, SOURCE_TABLE, SOURCE_ID, and TARGET_ID together form the natural composite identifier of a single migration event. The absence of a documented single-column PK reinforces that this is a log-style table where multiple rows per migration run are expected.

Common Use Cases and Queries

The principal use case is post-migration reconciliation: identifying which records failed to migrate and why. A typical query lists all errors for a given migration run:

• SELECT migration_id, source_table, source_id, target_table, target_id, message_text FROM gmd.gmd_migration WHERE migration_id = :run_id ORDER BY source_table, source_id;
• Grouping by source_table and target_table to quantify failure counts per mapping, which highlights the specific interfaces requiring remediation.
• Filtering on message_text patterns (for example, LIKE '%constraint%' or LIKE '%invalid%') to triage errors by class.
• Joining to HR_DM_MIGRATIONS to obtain migration descriptions and to AMS_DM_TARGETS_B to resolve target names, producing a human-readable error report for the migration team.

Reporting use cases include migration health dashboards, audit evidence that all source records were accounted for, and root-cause analysis when a target table is under-populated after an upgrade.

Related Objects

The documented foreign keys connect this table to two parents, and these are the most significant related objects:

• HR_DM_MIGRATIONS — joined via GMD_MIGRATION.MIGRATION_ID = HR_DM_MIGRATIONS.MIGRATION_ID. Provides the migration definition and run context.
• AMS_DM_TARGETS_B — joined via GMD_MIGRATION.TARGET_ID = AMS_DM_TARGETS_B.TARGET_ID. Supplies the target definition being populated.

Beyond these, the table is referenced by the migration processing logic within the GMD and HR Data Migration components. Because it is a standalone log with no documented child tables, dependents are procedural rather than declarative: the migration programs that insert into GMD_MIGRATION, and the concurrent programs and reports that read it, constitute the remaining related objects of interest.