Search Results pqh_tjr_shadow_pk

Overview

The PQH_TJR_SHADOW table is a core data object within the Oracle E-Business Suite (EBS) Public Sector HR (PQH) module. As a shadow table, its primary role is to support transactional integrity and data auditing for job requirement transactions. In the context of HRMS, job requirements define the necessary qualifications, skills, and criteria for a specific position. This table acts as a staging or historical ledger, capturing the state of job requirement data at specific points during a transaction lifecycle, such as during approval workflows or before a batch update is applied to the master tables. Its existence is critical for ensuring data consistency, enabling rollback capabilities, and maintaining a reliable audit trail for compliance within public sector HR operations in versions 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is centered on the transaction identifier for a job requirement. Based on the provided ETRM metadata, the single, explicitly documented column is the primary key: TXN_JOB_REQUIREMENT_ID. This column uniquely identifies each transactional record within the shadow table. While the full column list is not detailed in the excerpt, a shadow table of this nature typically stores a snapshot of all columns present in its corresponding master transaction table (potentially named similarly, e.g., PQH_TXN_JOB_REQUIREMENTS). This would include data points such as the associated position, effective dates, requirement details, and transaction status. The primary key constraint PQH_TJR_SHADOW_PK enforces the uniqueness of the TXN_JOB_REQUIREMENT_ID column, which is the fundamental link to a specific job requirement transaction.

Common Use Cases and Queries

This table is primarily accessed by the application's internal processes rather than through direct end-user queries. Common use cases include monitoring the progress of pending job requirement transactions, troubleshooting failed batch processes, and auditing historical changes. A typical query would join this shadow table to its master transaction table to compare data states or to isolate transactions in a specific status. For example, to find shadow records for a particular job requirement transaction, one would use:

• SELECT * FROM hr.pqh_tjr_shadow WHERE txn_job_requirement_id = <ID_VALUE>;

Reporting use cases are generally administrative and focused on transaction lifecycle analysis, such as generating reports on the volume and duration of job requirement updates within approval cycles.

Related Objects

The documented relationship data indicates that the table's sole primary key is PQH_TJR_SHADOW_PK on the column TXN_JOB_REQUIREMENT_ID. This primary key is almost certainly referenced by foreign key constraints in other transactional or audit tables within the PQH schema. While the specific related tables are not listed in the provided metadata, logical related objects would include:

• The main transaction table for job requirements (e.g., PQH_TXN_JOB_REQUIREMENTS), likely sharing the same TXN_JOB_REQUIREMENT_ID as a foreign key.
• Workflow or approval history tables that track the progression of the transaction recorded in the shadow table.
• Other shadow or staging tables for related entities (like positions or budgets) that are part of the same overarching transaction.

Joins to these related objects would consistently use the TXN_JOB_REQUIREMENT_ID column as the primary link.