Search Results per_job_requirements

Overview

The PQH_TXN_JOB_REQUIREMENTS table is a core transaction table within the Oracle E-Business Suite Public Sector Human Resources (PQH) module, specifically supporting the position control functionality. It serves as a staging and audit table for changes made to job requirements associated with position transactions. When a user initiates a transaction that modifies a position's job requirements—such as creating a new position, reclassifying an existing one, or updating its criteria—the system records the proposed or approved changes in this table. This transactional model ensures data integrity, supports workflow approvals, and maintains a historical record of changes separate from the master job requirement definitions stored in PER_JOB_REQUIREMENTS.

Key Information Stored

The table's primary purpose is to link a specific position transaction to the associated job requirement data being modified. Its key columns, as indicated by its foreign key relationships, include TXN_JOB_REQUIREMENT_ID (the primary key), POSITION_TRANSACTION_ID (linking to the parent transaction in PQH_POSITION_TRANSACTIONS), and JOB_REQUIREMENT_ID (linking to the master record in PER_JOB_REQUIREMENTS). Other critical foreign key columns are BUSINESS_GROUP_ID for security and organizational context, JOB_ID linking to PER_JOBS, and ANALYSIS_CRITERIA_ID linking to PER_ANALYSIS_CRITERIA, which holds the detailed analysis and criteria for the job requirement. The table effectively captures the snapshot of job requirement attributes (via its foreign keys) at the time of the transaction.

Common Use Cases and Queries

This table is central to reporting and auditing position control activities. A common use case is generating a report of all pending or completed position transactions that involve changes to specific job criteria. For instance, an HR analyst might query for all transactions within a business group that modify the analysis criteria for a particular job family. A typical SQL pattern involves joining PQH_TXN_JOB_REQUIREMENTS to PQH_POSITION_TRANSACTIONS to get transaction details (status, effective date) and to PER_JOBS and PER_ANALYSIS_CRITERIA to get descriptive information about the job and the specific requirement criteria being altered. This is essential for compliance reviews, budget impact analysis, and tracking the lifecycle of position definitions.

Related Objects

The table maintains defined foreign key relationships with several master and transactional tables, as documented in the ETRM metadata. These relationships are fundamental to its role in the application's data model:

• PER_JOB_REQUIREMENTS: Linked via JOB_REQUIREMENT_ID. This is the master table for job requirement definitions.
• PQH_POSITION_TRANSACTIONS: Linked via POSITION_TRANSACTION_ID. This is the parent transaction header table.
• HR_ALL_ORGANIZATION_UNITS: Linked via BUSINESS_GROUP_ID. This provides the business group context for the transaction.
• PER_ANALYSIS_CRITERIA: Linked via ANALYSIS_CRITERIA_ID. This table stores the detailed analysis and criteria data for the requirement.
• PER_JOBS: Linked via JOB_ID. This master table defines the job associated with the requirement.

These relationships ensure that transactional data in PQH_TXN_JOB_REQUIREMENTS is consistently validated against the application's core master data tables.