Results for “regular_date_earned”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PER_TIME_PERIODS is the core Human Resources (PER) table that stores time period definitions used throughout Oracle E-Business Suite for payroll processing and HR budget calendars. Owned by the HR schema and valid in both 12.1.1 and 12.2.2, it functions as the authoritative calendar dimension for anything that must be bounded by, or attributed to, a defined period of time. Each row defines a single time period — for example a weekly, bi-weekly, semi-monthly, or monthly payroll period, or a budget calendar period — with explicit start and end dates, cut-off dates, and payment dates.

Although the table sits in the PER (Human Resources) product, its consumers span payroll (PAY and PSP), budgeting (PQH), time and labor (HXT), and training (OTA) modules. In practice it is the reference table that ties payroll runs, payroll distribution lines, budget worksheets, budget periods, and encumbrance balances to a common, consistent period identifier.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is hub-leaning. This suggests treating PER_TIME_PERIODS as a hub entity keyed on its business key, with surrounding transactional tables (payroll actions, distribution lines, budget values) acting as links or satellites that reference the period. Analysts designing a warehouse layer over EBS should consider modeling TIME_PERIOD_ID as a durable, non-volatile hub key.

Key Information Stored

The table is physically documented with 80 columns in ETRM 12.2.2. The most business-significant columns are:

• TIME_PERIOD_ID — the surrogate primary key (PER_TIME_PERIODS_PK) and the single unique index / business-key candidate. This is the value propagated to every foreign-key table that references a period.
• PERIOD_NAME — the human-readable identifier for the period (e.g., "JAN-2024"), used in reporting and displayed on payroll output.
• START_DATE and END_DATE — the inclusive boundaries of the period; these are the fields most often used in date-range filtering and in "period containing date X" lookups.
• CUT_OFF_DATE — the deadline after which transactions are no longer accepted into the period.
• PAY_ADVICE_DATE, REGULAR_PAYMENT_DATE, and PAYSLIP_VIEW_DATE — the dates on which pay advices are produced, employees are paid, and payslips become viewable.
• PAYROLL_ID — identifies the payroll to which the period belongs; combined with period name this distinguishes overlapping calendars across different payrolls.
• PERIOD_TYPE and PROC_PERIOD_TYPE — classify the period (for example, regular versus supplemental processing).
• PERIOD_NUM, PERIOD_YEAR, YEAR_NUMBER, and QUARTER_NUM — the numeric position of the period within its year and quarter, useful for sequencing and year-over-year reporting.
• PERIOD_SET_NAME — identifies the period set / calendar to which the period belongs.
• STATUS — indicates whether the period is open, closed, or otherwise unavailable for processing.
• RUN_DISPLAY_NUMBER and QUICKPAY_DISPLAY_NUMBER — numbering conventions used when presenting run results.
• TIME_DEFINITION_ID — foreign key to PAY_TIME_DEFINITIONS, linking the concrete period back to the reusable time definition that generated it.
• DESCRIPTION, DEFAULT_DD_DATE, REGULAR_DATE_EARNED, and the PRD_INFORMATION_CATEGORY / PRD_INFORMATION1–30 flexfield columns — descriptive and descriptive-flexfield attributes.

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ATTRIBUTE_CATEGORY / ATTRIBUTE1–20 descriptive flexfield columns are also present.

Common Use Cases and Queries

The most frequent access patterns involve resolving a date to a period, listing periods for a payroll, and generating period-bounded reports.

• Find the period containing a given date: SELECT period_name FROM per_time_periods WHERE :query_date BETWEEN start_date AND end_date AND payroll_id = :payroll_id;
• List the payroll calendar for a year: SELECT period_name, start_date, end_date, cut_off_date, regular_payment_date FROM per_time_periods WHERE payroll_id = :payroll_id AND period_year = :year ORDER BY start_date;
• Resolve an employee's payroll period from payroll actions: join PER_TIME_PERIODS to PAY_PAYROLL_ACTIONS on time_period_id.
• Budget worksheet reporting (the PQH_WORKSHEET_PERIODS search): the required join is on both PQH_WORKSHEET_PERIODS.start_time_period_id = PER_TIME_PERIODS.time_period_id and PQH_WORKSHEET_PERIODS.end_time_period_id = PER_TIME_PERIODS.time_period_id, since worksheets are bounded by a start and end period.
• Distribution and encumbrance analysis: join the PSP distribution and summary tables (PSP_PRE_GEN_DIST_LINES, PSP_SUMMARY_LINES, PSP_ENC_SUMMARY_LINES) on time_period_id to aggregate cost by period.
• Open-period checks before processing: SELECT COUNT(*) FROM per_time_periods WHERE payroll_id = :payroll_id AND status = 'O' AND SYSDATE BETWEEN start_date AND end_date;

Related Objects

PER_TIME_PERIODS is heavily referenced. The most significant related objects are:

• PAY_TIME_DEFINITIONS — referenced by PER_TIME_PERIODS via time_definition_id; defines the reusable calendar rule behind each period.
• PAY_PAYROLL_ACTIONS — joined on time_period_id; the driver of payroll runs.
• PQH_WORKSHEET_PERIODS — joined on start_time_period_id and end_time_period_id; the object in the user's original search, defining worksheet period ranges.
• PQH_BUDGET_PERIODS — joined on start_time_period_id and end_time_period_id; budget calendar definitions.
• PER_BUDGET_VALUES — joined on time_period_id; budget amounts attributed to a period.
• PSP_PRE_GEN_DIST_LINES and PSP_SUMMARY_LINES — joined on time_period_id; payroll distribution lines and summaries.
• PSP_PAYROLL_CONTROLS and PSP_PAYROLL_INTERFACE — joined on time_period_id (and payroll_period_id in the interface); processing controls.
• PSP_ENC_SUMMARY_LINES and PSP_ENC_LINES — joined on time_period_id; encumbrance balances and lines.
• HXT_TIMECARDS_F — joined on time_period_id; timecard facts bound to periods.
• OTA_TRAINING_PLANS — joined on time_period_id; training plans scheduled against periods.