Search Results pa_period_type




Overview
Explore in AI Chat

Overview

APPS.PA_FP_PERIODS_V is a reporting view in Oracle E-Business Suite that exposes the accounting period calendar associated with the Oracle Projects implementation for a given operating unit (ORG_ID). It resolves the relationship between the General Ledger period calendar defined in GL_PERIODS and the period configuration recorded in the Projects implementation table, PA_IMPLEMENTATIONS_ALL. The view is read-only and is used primarily by Oracle Projects and Oracle Project Manufacturing reporting logic that must align GL accounting periods to Projects period types.

The relevance of the object to a search for "pa_period_type" is direct: the view exposes a column named PA_PERIOD_TYPE, drawn from PA_IMPLEMENTATIONS_ALL. This column identifies the Projects-side period type (for example, a GL-defined period type such as a fiscal calendar type) that the implementation uses, distinguishing it from the GL period type and from the accounted period type in the set of books. The view therefore serves as the join point between GL calendar data and the Projects implementation's declared period type.

Underlying Base Objects

The view is defined over three referenced objects:

  • GL_PERIODS (SYNONYM) — supplies the period rows themselves: PERIOD_NAME, PERIOD_TYPE, PERIOD_SET_NAME, START_DATE, and END_DATE. The view filters out adjustment periods by requiring GL.ADJUSTMENT_PERIOD_FLAG = 'N', so only standard accounting periods appear.
  • GL_SETS_OF_BOOKS (VIEW) — supplies the PERIOD_SET_NAME and ACCOUNTED_PERIOD_TYPE of the set of books associated with the Projects implementation. The join is made on GSB.SET_OF_BOOKS_ID = PIM.SET_OF_BOOKS_ID.
  • PA_IMPLEMENTATIONS_ALL (SYNONYM) — the Oracle Projects implementation table. It supplies ORG_ID, PERIOD_SET_NAME, and PA_PERIOD_TYPE, tying each period row to a legal entity/operating unit context.

The view is therefore a three-way join: GL_PERIODS is not joined to GL_SETS_OF_BOOKS directly on an explicit key in the displayed text; the driving relationship is gsb.set_of_books_id = pim.set_of_books_id, with period rows joined by period set name and period type. The view additionally computes a surrogate sequence number, RN, using ROW_NUMBER() partitioned by ORG_ID, GL.PERIOD_SET_NAME, and GL.PERIOD_TYPE and ordered by GL.START_DATE, so periods are numbered in chronological order within each organization/calendar/period-type grouping.

Key Columns

  • RN — chronological sequence number of the period within an ORG_ID, PERIOD_SET_NAME, and PERIOD_TYPE group.
  • START_DATE / END_DATE — the GL accounting period start and end dates (from GL_PERIODS), used for period-boundary calculations and date-range reporting.
  • PERIOD_NAME — the GL period name (for example, "JAN-24").
  • PERIOD_TYPE — the period type of the GL period row itself.
  • PERIOD_SET_NAME — the period set name of the GL period row.
  • GL_PERIOD_SET_NAME — the period set name of the set of books.
  • PA_PERIOD_SET_NAME — the Projects implementation period set name.
  • PA_PERIOD_TYPE — the Projects period type from PA_IMPLEMENTATIONS_ALL, the column of primary interest.
  • ACCOUNTED_PERIOD_TYPE — the accounted period type of the set of books.
  • ORG_ID — the operating unit / organization identifier from the Projects implementation.

Common Use Cases and Queries

Typical uses include validating that Projects period types align with GL calendars, generating period lists per operating unit, and enumerating the standard periods available to Projects reporting.

List periods for an operating unit's Projects period type:

  • SELECT period_name, start_date, end_date, pa_period_type FROM apps.pa_fp_periods_v WHERE org_id = :p_org_id AND period_type = :p_period_type ORDER BY rn;

Compare the Projects period type to the GL period type and accounted period type for a set of books:

  • SELECT DISTINCT gl_period_set_name, pa_period_set_name, period_type, pa_period_type, accounted_period_type FROM apps.pa_fp_periods_v WHERE org_id = :p_org_id;

Retrieve the period covering a transaction date:

  • SELECT period_name, rn FROM apps.pa_fp_periods_v WHERE org_id = :p_org_id AND pa_period_type = :p_period_type AND :p_txn_date BETWEEN start_date AND end_date;

Because the view derives its rows from GL and PA implementation data with no adjustment periods, results reflect only standard periods for implemented organizations.