Search Results pqh_copy_entity_results




Overview
Explore in AI Chat

Overview

The table PQH_COPY_ENTITY_RESULTS is a core transaction entity within the Oracle E-Business Suite Public Sector HR (PQH) module. It functions as a detailed log or audit trail for data replication processes. Specifically, it stores granular results for individual data elements processed during a copy operation, such as duplicating a position or a job structure. Each record in this table represents the outcome of copying a single entity from a source to a target, making it critical for tracking the success, failure, and lineage of data within complex HR configuration and setup activities in versions 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to capture the transactional details of a copy process. Its key columns, as indicated by the provided metadata, include:

  • COPY_ENTITY_RESULT_ID: The unique primary key identifier for each result record.
  • COPY_ENTITY_TXN_ID: A foreign key linking to the parent transaction header in the PQH_COPY_ENTITY_TXNS table. This associates multiple result records with a single copy job.
  • SRC_COPY_ENTITY_RESULT_ID: A self-referencing foreign key within the same table. This is a critical column that establishes a hierarchical relationship between result records, allowing the system to trace the provenance of copied data through multiple generations or iterations of a copy process.

While the full column list is not detailed in the excerpt, typical data in such a table would include identifiers for the source and target records, the type of entity copied (e.g., position, grade), status codes (success/error), and timestamps.

Common Use Cases and Queries

This table is primarily accessed for auditing, troubleshooting, and reporting on data migration or configuration copy jobs. A common scenario involves investigating a failed setup copy process. An administrator would query this table to identify which specific entities failed during a transaction. A typical SQL pattern would join to the parent transaction table to filter by a specific job or date range:

SELECT per.* FROM pqh_copy_entity_results per JOIN pqh_copy_entity_txns pet ON per.copy_entity_txn_id = pet.copy_entity_txn_id WHERE pet.request_id = :req_id AND per.status = 'ERROR';

Another key use case is tracing data lineage. The self-referencing foreign key allows for recursive queries to map the entire history of a copied entity back to its original source, which is essential for compliance and impact analysis in public sector HR environments.

Related Objects

As per the documented metadata, PQH_COPY_ENTITY_RESULTS has defined relationships with several other objects in the PQH schema:

  • PQH_COPY_ENTITY_TXNS: This is the primary parent table. The foreign key on COPY_ENTITY_TXN_ID links each detailed result to its overarching copy transaction, which holds high-level information like the requester, submission date, and overall process type.
  • Self-Reference: The table has a foreign key relationship with itself via the SRC_COPY_ENTITY_RESULT_ID column. This creates a hierarchical structure where a result record can point to its immediate source, enabling multi-level process tracking.

This table is central to the copy entity engine in Public Sector HR and is likely referenced by various internal APIs, concurrent programs, and diagnostic reports within the PQH module.