Search Results pqh_ptx_dpf_df




Overview
Explore in AI Chat

Overview

The table PQH_PTX_DPF_DF is a critical transactional staging object within the Oracle E-Business Suite Public Sector HR (PQH) module. Its primary function is to temporarily hold deployment factor data associated with a position transaction before that transaction is finalized and applied to the core HR system. This table acts as a buffer, ensuring data integrity during complex position management processes, such as creating or updating positions with specific deployment-related attributes. It decouples the transaction entry process from the permanent update of employee records, allowing for validation and review before changes are committed to the master table, PER_DEPLOYMENT_FACTORS.

Key Information Stored

The table's structure is designed to link position transaction records with specific deployment factor details. The primary key, PTX_DEPLOYMENT_FACTOR_ID, uniquely identifies each staging record. Two essential foreign keys define its relationships: POSITION_TRANSACTION_ID links to the parent transaction in PQH_POSITION_TRANSACTIONS, and DEPLOYMENT_FACTOR_ID links to the corresponding factor definition in PER_DEPLOYMENT_FACTORS. While the provided metadata does not list all columns, the table typically stores the specific values or adjustments for deployment factors (such as hazard pay, location differentials, or other compensable elements) that are proposed as part of the position transaction. These records persist only for the lifecycle of the transaction, from entry until application or cancellation.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting position transaction workflows. Administrators can query this table to verify which deployment factors are pending for a specific transaction. Common reporting needs include identifying all pending deployment factor changes or reconciling transaction data before batch submission. A typical diagnostic query would join to the position transaction and deployment factor master tables:

  • SELECT ptf.segment1, pdf.* FROM pqh_ptx_dpf_df pdf, pqh_position_transactions ptf WHERE pdf.position_transaction_id = ptf.position_transaction_id AND ptf.transaction_status = 'PENDING';

Data in this table is predominantly managed by internal Public Sector HR APIs and processes. Direct manipulation is not standard practice, as the data is transient and controlled by the application's business logic for creating and applying position transactions.

Related Objects

PQH_PTX_DPF_DF is centrally connected to two key tables, as defined by its foreign key constraints.

  • PQH_POSITION_TRANSACTIONS: This is the parent transaction table. Every record in PQH_PTX_DPF_DF must be associated with a single, valid position transaction record.
  • PER_DEPLOYMENT_FACTORS: This is the target master table. The DEPLOYMENT_FACTOR_ID in the staging table references the definitive list of deployment factors. Upon successful application of the position transaction, data is moved from PQH_PTX_DPF_DF to this table.

Consequently, this table is integral to the data flow between the transactional interface (PQH_POSITION_TRANSACTIONS) and the permanent employee deployment data repository (PER_DEPLOYMENT_FACTORS).