Search Results pqh_copy_entity_prefs




Overview
Explore in AI Chat

Overview

The PQH_COPY_ENTITY_PREFS table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as a repository for user-specific configuration preferences that govern the behavior of entity copy transactions. Specifically, it stores a user's selection regarding whether to include dependent entities—such as associated data from related tables—when a primary transaction entity is being copied or replicated. This table is essential for enabling flexible and user-controlled data replication processes within complex HR implementations, particularly those in public sector environments where position and transaction management often requires copying structures with their full dependent hierarchies.

Key Information Stored

The table's primary purpose is to link a user's preference to a specific copy transaction and a dependent table route. Its key columns, as indicated by its constraints, include:

  • COPY_ENTITY_PREF_ID: The primary key column, uniquely identifying each preference record.
  • COPY_ENTITY_TXN_ID: A foreign key column linking to the PQH_COPY_ENTITY_TXNS table. This identifies the master copy transaction for which the preference is set.
  • TABLE_ROUTE_ID: A foreign key column linking to the PQH_TABLE_ROUTE table. This identifies the specific dependent table or "entity route" that is the subject of the inclusion preference.

While the explicit column for the preference value (e.g., an INCLUDE_FLAG) is not detailed in the provided metadata, the description confirms the table's role in storing the "User preference of including" a dependent entity. The structure implies a record is created to denote a user's affirmative choice to include a specific dependent table route within a transaction copy.

Common Use Cases and Queries

The primary use case occurs during setup or execution of a copy transaction, such as duplicating a position definition along with its associated grade steps, funding sources, or comments. The application queries this table to determine which ancillary data sets should be replicated. A common reporting query would join this preference table to the transaction and table route master tables to audit or list configured copy behaviors.

Sample SQL Pattern:
To retrieve all inclusion preferences for a specific copy transaction, a query would typically join the related tables: SELECT pref.copy_entity_pref_id, txn.transaction_name, rt.table_name
FROM pqh_copy_entity_prefs pref,
pqh_copy_entity_txns txn,
pqh_table_route rt
WHERE pref.copy_entity_txn_id = txn.copy_entity_txn_id
AND pref.table_route_id = rt.table_route_id
AND txn.copy_entity_txn_id = :transaction_id;

Related Objects

PQH_COPY_ENTITY_PREFS is centrally connected to two other key PQH tables, as defined by its foreign key constraints:

  • PQH_COPY_ENTITY_TXNS: This is the parent table defining the master copy transaction. The preference is always set in the context of a specific transaction defined here.
  • PQH_TABLE_ROUTE: This table likely defines the hierarchy and relationships between different entities (tables) within the PQH module. The TABLE_ROUTE_ID points to the specific dependent table that the user can choose to include or exclude.

The table's primary key constraint, PQH_COPY_ENTITY_PREFS_PK, ensures data integrity for these preference records. As a configuration table, it is typically populated and maintained through the application's user interface for setting up copy transactions rather than via direct data manipulation.