Search Results per_time_periods




Overview
Explore in AI Chat

Overview

The PER_TIME_PERIODS table is a core master data table within the Oracle E-Business Suite Human Resources (HR) module. It serves as the central repository for defining and storing time period definitions, which are fundamental to the system's time-based processing. Its primary role is to support payroll processing cycles and HR budget calendars, providing the temporal framework against which employee compensation is calculated, reported, and budgeted. The integrity of this table is critical, as its period definitions are referenced extensively by transactional tables in Payroll (PAY), Projects (PSP), and Budgeting (PQH) modules to ensure financial and operational data is correctly aligned to specific accounting and reporting periods.

Key Information Stored

While the provided metadata does not list specific columns, the table's description and foreign key relationships indicate it stores essential period attributes. The primary key is TIME_PERIOD_ID, a unique system-generated identifier for each period record. Based on standard Oracle HRMS table structures, other critical columns typically include PERIOD_TYPE (e.g., 'Calendar', 'Weekly', 'Bi-Weekly', 'Monthly'), START_DATE and END_DATE to define the period's duration, and PERIOD_NAME for descriptive identification. The table likely also contains a PAYROLL_ID column to link the period to a specific payroll definition, and a PERIOD_NUM for sequential ordering within a year. These attributes collectively define the chronological structure used for all periodic HR and financial operations.

Common Use Cases and Queries

This table is central to reporting and data validation across multiple modules. A common use case is generating payroll registers or audit reports for a specific time period. For example, to retrieve all payroll actions for a given period name, one would join with PAY_PAYROLL_ACTIONS. Another frequent scenario involves budget versus actual reporting, requiring joins to PER_BUDGET_VALUES. A typical diagnostic query would verify period definitions for a payroll, such as: SELECT period_name, start_date, end_date FROM per_time_periods WHERE payroll_id = &payroll_id ORDER BY start_date;. For Projects Accounting integration, queries often join PSP_SUMMARY_LINES to analyze labor distribution by time period. Ensuring period dates are contiguous and non-overlapping for a payroll is a critical validation step performed by administrators.

Related Objects

As evidenced by the extensive foreign key relationships, PER_TIME_PERIODS is a heavily referenced parent table. Key dependent objects include:

  • PAY_PAYROLL_ACTIONS: Links each payroll run to its corresponding time period.
  • PER_BUDGET_VALUES: Associates budget figures with specific HR calendar periods.
  • PQH_BUDGET_PERIODS / PQH_WORKSHEET_PERIODS: Define budget and worksheet cycles using start and end period references.
  • PSP_* tables (e.g., PSP_SUMMARY_LINES, PSP_PAYROLL_INTERFACE): Critical for Projects Accounting, linking labor distribution, adjustments, and payroll controls to the correct payroll period for cost collection and reporting.
This network of relationships underscores the table's role as a cornerstone for integrated period-based processing across HR, Payroll, and Financials.