Search Results pa_periods




Overview
Explore in AI Chat

Overview

PA_PERIODS is a single-organization (Single-Org) reporting view within the Oracle Projects (PA) module. It presents Oracle Projects accounting period definitions — the calendar segments against which project transactions are processed, distributed, and transferred to General Ledger. In Oracle E-Business Suite 12.1.1 and 12.2.2, the physically stored, multi-organization table is PA_PERIODS_ALL; the PA_PERIODS view applies a security predicate so that each operating unit sees only its own period rows. This makes the view the standard access point for period-based reporting, concurrent program logic, and integrations that must respect operating unit partitioning without writing explicit ORG_ID filters. Note that the documented metadata identifies this view as "Single-Org," indicating its design purpose is to constrain results to the current organization context derived from the session, rather than returning all periods across every operating unit.

Underlying Base Objects

The view is defined over a single base object, PA_PERIODS_ALL, aliased as PER. The view text selects columns from PA_PERIODS_ALL and applies a WHERE clause that compares the stored ORG_ID to a value derived from the session environment. The predicate uses USERENV('CLIENT_INFO'), extracting the first ten characters via SUBSTRB (with a single-space prefix mapped to NULL), converting the result to a number, and defaulting to -99 when no value can be resolved. Rows are returned where the row's ORG_ID matches this session-derived organization value. This is the standard multi-organization security pattern used throughout Oracle EBS. Because the view is a thin projection over PA_PERIODS_ALL with no joins or aggregations, its performance characteristics closely track those of the base table, and period query performance depends on indexing on the underlying table.

Key Columns

  • ROW_ID — The physical row identifier of the underlying PA_PERIODS_ALL record, exposed as PER.ROWID.
  • PERIOD_NAME — The name of the Oracle Projects period (for example, a weekly or monthly period label).
  • START_DATE / END_DATE — The beginning and ending dates that bound the period.
  • STATUS — The current status of the period (for example, open or closed), which governs whether project transactions may be entered or adjusted.
  • GL_PERIOD_NAME — The corresponding General Ledger period name to which the Projects period maps, essential for cross-module reconciliation.
  • CURRENT_PA_PERIOD_FLAG — Identifies the period currently designated as the active Projects period.
  • ORG_ID — The operating unit identifier used to partition records under multi-organization security.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard EBS audit tracking.

Common Use Cases and Queries

The view is commonly used to determine the current open Projects period, to map Projects periods to their GL counterparts, to drive period-close reporting, and to validate period status during transaction interfaces. A typical query retrieving the active period is:

SELECT period_name, start_date, end_date, status, gl_period_name
FROM pa_periods
WHERE current_pa_period_flag = 'Y';

To list all open periods with their GL mapping for a reconciliation report:

SELECT period_name, gl_period_name, start_date, end_date
FROM pa_periods
WHERE status = 'O'
ORDER BY start_date;

Because the view automatically enforces operating unit security through the USERENV('CLIENT_INFO') predicate, queries executed from a correctly initialized Projects responsibility return only the periods belonging to that organization. Integrations and reports that require cross-organization visibility must query PA_PERIODS_ALL directly with an explicit ORG_ID filter, since PA_PERIODS restricts results to the current session organization context.