Search Results pqh_position_transactions




Overview
Explore in AI Chat

Overview

The PQH_POSITION_TRANSACTIONS table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It serves as the central transactional ledger for all position management activities. This table is responsible for capturing and staging requests to create, modify, or maintain positions before they are formally applied to the HRMS database. Each record represents a distinct position transaction that must undergo a structured approval workflow involving pre-identified approvers. Upon final approval, the transaction data is processed and applied, resulting in the creation or update of a position in the system. This design ensures controlled, auditable, and compliant management of an organization's position hierarchy and funding.

Key Information Stored

The table stores comprehensive metadata for each position transaction. Its primary key is POSITION_TRANSACTION_ID, which uniquely identifies each transaction record. Critical foreign key columns define the transaction's context and proposed changes, including POSITION_DEFINITION_ID (linking to the position template), JOB_ID, ORGANIZATION_ID, LOCATION_ID, and BUSINESS_GROUP_ID. The table also holds attributes specifying the proposed position's characteristics, such as ENTRY_GRADE_ID, PAY_BASIS_ID, and AVAILABILITY_STATUS_ID. A crucial column is WF_TRANSACTION_CATEGORY_ID, which links to PQH_TRANSACTION_CATEGORIES and determines the type of transaction (e.g., create, update, freeze) and governs its associated approval workflow rules.

Common Use Cases and Queries

Primary use cases revolve around position lifecycle management and audit reporting. Administrators use this table to track the status of pending position requests, analyze approval bottlenecks, and generate historical reports on all position changes. Common SQL queries include retrieving all transactions for a specific organization, finding transactions pending approval, or listing transactions of a particular category within a date range. For example, a report to show approved creation transactions would join PQH_POSITION_TRANSACTIONS with HR_ALL_ORGANIZATION_UNITS and PER_JOBS, filtering on the relevant transaction category and approval status columns. Data from this table is also integral to budgeting and position control worksheets within the PQH module.

Related Objects

The table has extensive relationships with other HR and PQH objects, as documented by its foreign keys. Key parent tables it references for validation include:

It is a parent table to several child transactional tables that store supplemental data, including: These relationships form a complete schema for managing complex position transaction data.