Results for “processing_period_status”

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

Overview

APPS.PER_TIME_PERIODS_V is a reporting and integration view in the Oracle E-Business Suite Applications schema that exposes payroll time period definitions maintained by Oracle Payroll. It is a denormalized wrapper around the PER_TIME_PERIODS base entity, and its defining characteristic is that the raw STATUS code column is translated into a human-readable meaning by joining to the HR_LOOKUPS view restricted to the lookup type PROCESSING_PERIOD_STATUS. This translation is precisely what users search for under the term "processing_period_status," since the D_STATUS column produced by that join is the descriptive processing period status associated with each payroll period.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as a stable, read-only interface for external reports, concurrent programs, and interfaces that need period names, dates, and statuses without re-implementing the lookup join themselves. Because it is defined in the APPS schema and references synonyms and views rather than raw tables exclusively, it abstracts the underlying key and lookup mechanics from consuming code.

Underlying Base Objects

Per the documented ETRM metadata, PER_TIME_PERIODS_V is defined over the following referenced objects:

• PER_TIME_PERIODS (SYNONYM) — the primary source, aliased as TPE, supplying virtually all columns including TIME_PERIOD_ID, PAYROLL_ID, PERIOD_NAME, dates, and STATUS.
• HR_LOOKUPS (VIEW) — aliased as HL, joined on HL.LOOKUP_CODE = TPE.STATUS with HL.LOOKUP_TYPE constrained to 'PROCESSING_PERIOD_STATUS', supplying HL.MEANING as D_STATUS.
• HR_API (PACKAGE) — documented as a referenced object, reflecting the HR security and API layer that underpins payroll period access rather than a direct columnar source.

The view text confirms the join condition and the ROWID-based ROW_ID column, and it carries the full descriptive flexfield and developer flexfield column sets (ATTRIBUTE1–20 and PRD_INFORMATION1–30) through from the base period entity.

Key Columns

• TIME_PERIOD_ID — primary identifier of the payroll time period.
• PAYROLL_ID — the payroll to which the period belongs.
• PERIOD_NAME, PERIOD_NUM, PERIOD_YEAR, YEAR_NUMBER, QUARTER_NUM — period naming and numbering attributes.
• START_DATE, END_DATE, CUT_OFF_DATE, DEFAULT_DD_DATE, PAY_ADVICE_DATE, REGULAR_PAYMENT_DATE — the calendar and payment-related dates that drive payroll processing.
• STATUS — the raw lookup code for the processing period status.
• D_STATUS — the decoded meaning of STATUS from HR_LOOKUPS (PROCESSING_PERIOD_STATUS), the column most relevant to status-oriented queries.
• PERIOD_TYPE, PROC_PERIOD_TYPE, PERIOD_SET_NAME — period classification and the accounting period set reference.
• RUN_DISPLAY_NUMBER, QUICKPAY_DISPLAY_NUMBER, PAYSLIP_VIEW_DATE — display and payroll run presentation attributes.
• ATTRIBUTE1–20 / PRD_INFORMATION1–30 — descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view is typically queried to list periods for a payroll with readable statuses, to find open periods before running payroll, or to reconcile period dates for costing and reporting. The following sample retrieves period details for a specific payroll using the decoded status column:

• SELECT period_name, start_date, end_date, cut_off_date, status, d_status FROM apps.per_time_periods_v WHERE payroll_id = :p_payroll_id AND d_status = 'Open' ORDER BY start_date;
• SELECT period_year, period_num, period_name, d_status FROM apps.per_time_periods_v WHERE period_set_name = :p_period_set AND end_date BETWEEN :p_from AND :p_to;
• SELECT DISTINCT status, d_status FROM apps.per_time_periods_v ORDER BY status; — used to enumerate the valid PROCESSING_PERIOD_STATUS codes and their meanings.

Because D_STATUS is derived from the lookup join, D_STATUS returns NULL for any STATUS value lacking a matching PROCESSING_PERIOD_STATUS lookup entry; queries filtering on status should account for this. All access should respect HR security, given the HR_API dependency documented in the metadata.