Results for “run_display_number”

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

Overview

APPS.PER_TIME_PERIODS_V is a validated database view in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, owned by the APPS schema and associated with the PER (Human Resources) product family. According to its ETRM documentation, the object exists primarily "to support user interface" functionality, meaning it is a presentation-layer construct consumed by Oracle Forms, OAF pages, and related payroll and time-period maintenance screens rather than a standalone reporting entity. The view presents time period definitions stored in the PER_TIME_PERIODS table in a denormalized, ready-to-display form, most notably by resolving the numeric STATUS code into a human-readable status meaning via a lookup join.

For users searching on the column default_dd_date, this view is significant because it is one of the exposed surfaces through which the DEFAULT_DD_DATE attribute is surfaced to the application layer. The view does not introduce new business logic beyond the status decode and the ROWID projection; it is essentially a window onto PER_TIME_PERIODS. Its principal value in reporting and integration is that it provides a stable, fully qualified APPS-level object that exposes every descriptive and descriptive-flexfield column of the underlying table, including the PRD_INFORMATION and ATTRIBUTE flexfield segments.

Underlying Base Objects

The documented base objects referenced by the view metadata are HR_API (PACKAGE), HR_LOOKUPS (VIEW), and PER_TIME_PERIODS (SYNONYM). The view text confirms this relationship:

• PER_TIME_PERIODS (via synonym TPE) — the primary data source. The view selects directly from this object, qualified with the alias TPE, joining on ROWID to expose ROW_ID and projecting the complete set of payroll time-period attributes.
• HR_LOOKUPS (via alias HL) — joined on HL.LOOKUP_CODE = TPE.STATUS with LOOKUP_TYPE = 'PROCESSING_PERIOD_STATUS'. This resolves the stored status code into the D_STATUS meaning column, providing the display-friendly status text used by the user interface.
• HR_API (PACKAGE) — documented as a referenced object, reflecting the HR API layer that governs time-period maintenance. Application logic that maintains PER_TIME_PERIODS rows is expected to operate through HR_API rather than direct DML.

Because the join to HR_LOOKUPS is an inner-style equijoin on the status code, rows in PER_TIME_PERIODS whose STATUS value has no corresponding PROCESSING_PERIOD_STATUS lookup entry will not appear in the view result set.

Key Columns

• ROW_ID — the ROWID of the underlying PER_TIME_PERIODS row, exposed for update and drill-down access.
• TIME_PERIOD_ID — primary identifier of the time period.
• PAYROLL_ID — the payroll to which the period belongs.
• PERIOD_NAME, PERIOD_NUM, PERIOD_TYPE, PERIOD_YEAR, YEAR_NUMBER, QUARTER_NUM — descriptive identifiers of the period within its period set.
• START_DATE, END_DATE, CUT_OFF_DATE, PAY_ADVICE_DATE, REGULAR_PAYMENT_DATE — the key date attributes used by payroll processing and date-effective reporting.
• DEFAULT_DD_DATE — the default direct-deposit date associated with the period; this is the column of primary interest to users searching on that term.
• PERIOD_SET_NAME — the accounting period set to which the period belongs.
• STATUS and D_STATUS — the stored processing status code and its resolved lookup meaning.
• PRD_INFORMATION1–30, ATTRIBUTE1–20 — descriptive flexfield segments retained for reportable flexibility.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include validating direct-deposit date defaults for an active payroll period, confirming the payment calendar for a period set, and supporting integration extracts where a display-ready status is preferred over the raw code. A representative query to inspect the default direct-deposit date is:

• SELECT period_name, start_date, end_date, default_dd_date, regular_payment_date, d_status FROM apps.per_time_periods_v WHERE payroll_id = :payroll_id ORDER BY start_date DESC;
• SELECT time_period_id, period_name, default_dd_date FROM apps.per_time_periods_v WHERE default_dd_date BETWEEN :from_date AND :to_date AND status = 'O';
• SELECT period_name, d_status, cut_off_date, pay_advice_date FROM apps.per_time_periods_v WHERE period_set_name = :set_name;

Where downstream systems require the raw status code without lookup dependency, or require periods whose status is not represented in PROCESSING_PERIOD_STATUS, querying PER_TIME_PERIODS directly is appropriate. All access should be made through the APPS schema, and any maintenance should respect the HR_API layer rather than relying on DML against the base table.