Search Results pqh_worksheets




Overview
Explore in AI Chat

Overview

The PQH_WORKSHEETS table is a core transactional data store within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as the primary repository for worksheets, which are the central working documents used during the creation and iterative refinement of budget versions. A budget version represents a specific iteration or scenario of a budget plan within the system. The worksheet serves as the user's workspace to model, adjust, and finalize personnel-related budget allocations before they are formally approved and integrated into the official budget version. Its role is critical to the budget preparation workflow, capturing all proposed changes and calculations in a structured format that can be reviewed, updated, and processed.

Key Information Stored

The table's structure is designed to manage the worksheet's lifecycle and its relationship to the broader budgeting framework. The primary key, WORKSHEET_ID, uniquely identifies each worksheet instance. Two critical foreign keys establish its core dependencies: BUDGET_ID links the worksheet to its parent budget definition in the PQH_BUDGETS table, and BUDGET_VERSION_ID links it to the specific version of that budget being worked on in the PQH_BUDGET_VERSIONS table. Another significant foreign key, WF_TRANSACTION_CATEGORY_ID, references the PQH_TRANSACTION_CATEGORIES table, connecting the worksheet to a specific workflow transaction category. This linkage is essential for routing the worksheet through the appropriate approval and processing steps. Additional columns typically track status, creation and last update dates, and the user responsible for the worksheet.

Common Use Cases and Queries

The primary use case is the interactive management of budget worksheets within the Public Sector HR application. Common reporting and data extraction needs involve analyzing worksheet activity. For instance, a query to list all active worksheets for a specific budget, along with their associated version and creator, would be fundamental:

  • SELECT w.WORKSHEET_ID, w.BUDGET_VERSION_ID, bv.VERSION_NUM, w.CREATION_DATE FROM HR.PQH_WORKSHEETS w, HR.PQH_BUDGET_VERSIONS bv WHERE w.BUDGET_VERSION_ID = bv.BUDGET_VERSION_ID AND w.BUDGET_ID = :p_budget_id;

Another common scenario is tracing the workflow status of worksheets by joining to the transaction categories table. Data from this table is also frequently aggregated for audit trails, showing the history of changes made to budget versions throughout the planning cycle.

Related Objects

The PQH_WORKSHEETS table sits at the center of a key data relationship. It is a child table of both PQH_BUDGETS and PQH_BUDGET_VERSIONS, deriving its core budgetary context from them. It is also a parent table; the PQH_WORKSHEET_DETAILS table holds the granular line-item transactions (e.g., proposed salary changes, new positions) that constitute the worksheet's content, linked via the WORKSHEET_ID foreign key. Its relationship to PQH_TRANSACTION_CATEGORIES governs the workflow process. Consequently, any integration, data fix, or custom report involving budget worksheet data will typically require joins to these related tables to present a complete picture.