Results for “select_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQH_COPY_ENTITY_PREFS is a table owned by the HR schema within the Oracle E-Business Suite Public Sector HR (PQH) product family. It stores user-level preferences that determine whether dependent entities associated with a copy transaction should be included when that transaction is processed. In practice, the table acts as a configuration record: for a given copy entity transaction and a given routing definition, it captures the user's selection decision about propagating associated dependent rows.

Because the table is primarily a junction between a transaction header and a routing definition, the metadata's heuristic Data Vault classification is link. This suggests that PQH_COPY_ENTITY_PREFS is best modeled as a relationship record connecting PQH_COPY_ENTITY_TXNS and PQH_TABLE_ROUTE, rather than as a standalone hub or a descriptive satellite. The table also carries audit columns typical of EBS "who columns," so limited descriptive attributes are present alongside the link keys.

Key Information Stored

The most important columns fall into three groups: identity, foreign-key linkage, and the preference value itself.

• COPY_ENTITY_PREF_ID — the surrogate primary key, enforced by the unique index PQH_COPY_ENTITY_PREFS_PK. This is the only documented business-key candidate in the metadata.
• COPY_ENTITY_TXN_ID — foreign key to PQH_COPY_ENTITY_TXNS. Identifies the parent copy transaction to which the preference belongs.
• TABLE_ROUTE_ID — foreign key to PQH_TABLE_ROUTE. Identifies the routing definition that governs how the dependent entity is reached.
• SELECT_FLAG — the core preference indicator. It records whether the user has chosen to include the dependent entity associated with the transaction.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording who last modified the preference and when.
• CREATED_BY, CREATION_DATE — standard audit columns recording initial creation of the row.

The ten documented columns are deliberately lean. No descriptive name or code columns exist beyond the identifier and flag, confirming that the row functions as a preference toggle keyed to a transaction and a route.

Common Use Cases and Queries

Typical usage centers on reconstructing which dependent entities a user elected to copy for a given transaction, and on validating that preference flags are consistent across transactions and routes.

SELECT p.COPY_ENTITY_PREF_ID,
       p.COPY_ENTITY_TXN_ID,
       p.TABLE_ROUTE_ID,
       p.SELECT_FLAG
FROM   HR.PQH_COPY_ENTITY_PREFS p
WHERE  p.COPY_ENTITY_TXN_ID = :copy_entity_txn_id;

To list only preferences where the dependent entity was included:

SELECT p.COPY_ENTITY_TXN_ID, p.TABLE_ROUTE_ID
FROM   HR.PQH_COPY_ENTITY_PREFS p
WHERE  p.SELECT_FLAG = 'Y';

Joining to the parent transaction and route definitions supports audit and reporting:

SELECT t.TXN_HEADER_ID, r.ROUTE_NAME, p.SELECT_FLAG
FROM   HR.PQH_COPY_ENTITY_PREFS p,
       HR.PQH_COPY_ENTITY_TXNS t,
       HR.PQH_TABLE_ROUTE r
WHERE  p.COPY_ENTITY_TXN_ID = t.COPY_ENTITY_TXN_ID
AND    p.TABLE_ROUTE_ID     = r.TABLE_ROUTE_ID;

These queries support diagnostics, configuration review, and reconciliation of user preferences following a copy or mass-update operation.

Related Objects

• PQH_COPY_ENTITY_TXNS — parent transaction table; joined via COPY_ENTITY_TXN_ID.
• PQH_TABLE_ROUTE — routing definition; joined via TABLE_ROUTE_ID.
• PQH_COPY_ENTITY_PREFS_PK — the unique index backing the primary key on COPY_ENTITY_PREF_ID.
• HR schema objects in the PQH product — other copy and routing tables that participate in the same transaction framework and share the audit column conventions.

Together, these objects form the dependency chain through which copy entity transactions resolve their dependent entity preferences.