Search Results pqh_copy_entity_prefs_pk




Overview
Explore in AI Chat

Overview

The HR.PQH_COPY_ENTITY_PREFS table is a configuration and transactional data store within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the HRMS module. As indicated by its documentation, it stores user preferences for including dependent entities associated with a transaction. This table functions as a critical junction table, linking copy entity transactions (PQH_COPY_ENTITY_TXNS) with specific table routes (PQH_TABLE_ROUTE) to record user selections. Its primary role is to support data replication or copying processes, likely within the context of global HR or workforce structures, by persisting which dependent data paths a user has chosen to include or exclude during a batch copy operation.

Key Information Stored

The table's structure is designed to track user selections, maintain referential integrity, and support standard EBS auditing. The key columns are:

Common Use Cases and Queries

This table is central to operations where users configure data copy jobs. A typical use case involves a user initiating a copy of a workforce entity (like a position or assignment) and being presented with options to include related data (like grades, salaries, or competencies). Each selected or deselected option generates a record in this table. Common queries include retrieving all preferences for a specific transaction or verifying the inclusion status of a particular table route.

Sample SQL to fetch all preferences for a given copy transaction:

SELECT pref.TABLE_ROUTE_ID, pref.SELECT_FLAG, route.<route_details>
FROM hr.pqh_copy_entity_prefs pref
JOIN hr.pqh_table_route route ON pref.table_route_id = route.table_route_id
WHERE pref.copy_entity_txn_id = :p_txn_id
ORDER BY pref.copy_entity_pref_id;

Reporting use cases focus on auditing historical copy configurations and analyzing which dependent entities are most frequently included in data replication processes.

Related Objects

The table maintains defined foreign key relationships with two core entities, as documented in the ETRM metadata:

  • PQH_COPY_ENTITY_TXNS: Linked via the COPY_ENTITY_TXN_ID column. This is the parent transaction batch controlling the copy operation.
  • PQH_TABLE_ROUTE: Linked via the TABLE_ROUTE_ID column. This defines the specific dependent data path or entity that can be included.

The primary key constraint PQH_COPY_ENTITY_PREFS_PK on COPY_ENTITY_PREF_ID ensures record uniqueness. The table is also referenced by the PQH_COPY_ENTITY_PREFS_WHO view, which is a standard EBS "WHO" view exposing the audit columns.