Search Results pqh_worksheet_periods




Overview
Explore in AI Chat

Overview

The PQH_WORKSHEET_PERIODS table is a core data structure within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as a detailed transactional ledger, storing period-wise financial data for budget versions. Its primary role is to support complex budgeting and workforce planning processes, particularly in public sector environments where fiscal accountability and period-based financial tracking are mandated. The table enables the system to associate specific budget transaction details with defined time periods, forming a critical link between budget worksheets and the enterprise's fiscal calendar. This facilitates accurate accruals, forecasting, and variance analysis across multiple accounting periods.

Key Information Stored

The table's structure is designed to establish relationships between budget worksheet details and time periods. Its key columns, as defined by its primary and unique keys, are fundamental to its integrity and purpose. The primary identifier is the WORKSHEET_PERIOD_ID. The table enforces a unique constraint on the combination of START_TIME_PERIOD_ID, END_TIME_PERIOD_ID, and WORKSHEET_DETAIL_ID, ensuring that a given worksheet detail line cannot have duplicate period ranges. The WORKSHEET_DETAIL_ID is a foreign key linking back to the parent transaction line in the PQH_WORKSHEET_DETAILS table. The START_TIME_PERIOD_ID and END_TIME_PERIOD_ID are foreign keys to the PER_TIME_PERIODS table, defining the inclusive date range for which the associated transaction data is applicable.

Common Use Cases and Queries

This table is central to generating period-specific budget reports and conducting fiscal year-to-date analyses. A common operational use case is the allocation of a single budget line item, such as a salary increase, across multiple accounting periods, where each period's portion of the total amount is stored via this table. For reporting, a typical query would join this table to PQH_WORKSHEET_DETAILS and PER_TIME_PERIODS to produce a ledger showing budgeted amounts by GL period. Sample SQL to retrieve period details for a specific worksheet would be:

  • SELECT pwp.WORKSHEET_PERIOD_ID, pwd.DESCRIPTION, ptp1.PERIOD_NAME AS START_PERIOD, ptp2.PERIOD_NAME AS END_PERIOD
  • FROM PQH_WORKSHEET_PERIODS pwp
  • JOIN PQH_WORKSHEET_DETAILS pwd ON pwp.WORKSHEET_DETAIL_ID = pwd.WORKSHEET_DETAIL_ID
  • JOIN PER_TIME_PERIODS ptp1 ON pwp.START_TIME_PERIOD_ID = ptp1.TIME_PERIOD_ID
  • JOIN PER_TIME_PERIODS ptp2 ON pwp.END_TIME_PERIOD_ID = ptp2.TIME_PERIOD_ID
  • WHERE pwd.WORKSHEET_DETAIL_ID = :p_detail_id;

Related Objects

The PQH_WORKSHEET_PERIODS table exists within a tightly integrated schema. Its relationships, as documented, are as follows:

  • Parent Tables (Foreign Key References):
    • PQH_WORKSHEET_DETAILS via WORKSHEET_DETAIL_ID
    • PER_TIME_PERIODS via START_TIME_PERIOD_ID
    • PER_TIME_PERIODS via END_TIME_PERIOD_ID
  • Child Table (Referenced by Foreign Key):

This relationship hierarchy indicates that a worksheet period record is a child of a specific budget worksheet detail line and the time period master, and can itself be a parent to records in the PQH_WORKSHEET_BUDGET_SETS table, which likely groups these periods into higher-level budget sets.