Search Results hr_dm_resolve_pks




Overview
Explore in AI Chat

Overview

The HR_DM_RESOLVE_PKS table is a Human Resources (PER) module data object in the Oracle E-Business Suite HR schema. As documented in the ETRM metadata, it "contains the values of the primary key for both the source and destination database for each table for use by the TUPS package." In practice, this table functions as a cross-reference or key-mapping repository that supports Oracle's TUPS (Transactional Upgrade/Data Migration Processing) infrastructure, allowing records to be correlated between a source database and a destination database during clone, migration, or upgrade operations. The object resides at HR.HR_DM_RESOLVE_PKS and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Under a heuristic Data Vault modeling assessment (mined from the foreign-key structure), HR_DM_RESOLVE_PKS is classified as standalone. It does not exhibit the linking behavior typical of a Data Vault link table and carries no parent hub dependency within its own FK graph beyond the referenced lookup tables, so it is best treated as a self-contained reference/satellite-style entity rather than a core hub or link.

Key Information Stored

The table contains 11 documented columns. The most significant are:

The surrogate key (RESOLVE_PK_ID) provides fast internal joins, while the composite unique key (TABLE_NAME, SOURCE_ID, SOURCE_DATABASE_INSTANCE) enforces the business rule that a given source primary key on a given instance for a given table resolves to only one destination value.

Common Use Cases and Queries

This table is primarily consumed by the TUPS package during data migration and reconciliation. A typical lookup resolves a source identifier to its destination counterpart:

  • Translating a source key to a destination key for a specific table and database instance.
  • Auditing which records were successfully mapped during an upgrade or clone.
  • Validating that no source primary key maps to multiple destinations (uniqueness enforcement via HR_DM_RESOLVE_PKS_UK1).
  • Reporting unresolved or missing mappings where a source key has no destination entry.

A representative query:

SELECT resolve_pk_id, source_id, destination_id
FROM hr.hr_dm_resolve_pks
WHERE table_name = :p_table
  AND source_database_instance = :p_instance
  AND source_id = :p_source_key;

Related Objects

The documented foreign keys and surrounding PER/TUPS infrastructure connect HR_DM_RESOLVE_PKS to the following significant objects:

  • IGI_DOS_DESTINATIONS — referenced by DESTINATION_ID; identifies the destination for resolved keys.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; controls Multi-Org access to rows.
  • TUPS package — the documented consumer that reads and writes these resolution records.
  • HR_DM_* migration tables — the companion data-migration entities that this table resolves keys for.
  • FND_FLEX_VALUE_SETS / FND tables — standard reference objects invoked during key resolution and validation.

Consumers should treat HR_DM_RESOLVE_PKS as an internal TUPS support structure and avoid direct DML outside the supported migration APIs.