Search Results pa_rep_quarter_gl_v




Overview
Explore in AI Chat

Overview

PA_REP_QUARTER_GL_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to return General Ledger quarter numbers, providing a concise, reusable source of quarter-level period information for Projects reporting. Rather than querying the underlying General Ledger period and set-of-books structures directly, report developers and integrators can reference PA_REP_QUARTER_GL_V to obtain the distinct quarter numbers available to the operating units configured in Projects.

The view is delivered as a VALID object in both EBS 12.1.1 and 12.2.2. It functions as a lightweight lookup or reference object, translating the accounting calendar defined against a set of books into the corresponding quarter values. This is particularly useful where reporting logic must group project transaction, expenditure, or revenue data into GL quarters rather than individual accounting periods.

Because the view exposes only two columns — a quarter number and an operating unit identifier — it is intentionally narrow in scope. It does not hold transactional data and does not perform any aggregation. Its value lies in decoupling report logic from the join complexity of GL_PERIODS, GL_SETS_OF_BOOKS, and PA_IMPLEMENTATIONS.

Underlying Base Objects

The view is defined over three documented base objects, consistent with ETRM 12.2.2 metadata:

  • GL_PERIODS (referenced as a synonym) — supplies the QUARTER_NUM value and the PERIOD_TYPE and PERIOD_SET_NAME used to align periods to the accounting calendar.
  • GL_SETS_OF_BOOKS (referenced as a view) — provides the SET_OF_BOOKS_ID, PERIOD_SET_NAME, and ACCOUNTED_PERIOD_TYPE used to establish the correct calendar and period type.
  • PA_IMPLEMENTATIONS (referenced as a synonym) — supplies the SET_OF_BOOKS_ID linkage and the ORG_ID returned in the result set.

The view text joins PA_IMPLEMENTATIONS to GL_SETS_OF_BOOKS on SET_OF_BOOKS_ID, then joins GL_SETS_OF_BOOKS to GL_PERIODS where the period set name and the accounted period type match. The DISTINCT keyword eliminates duplicate quarter rows that would otherwise arise from multiple periods sharing the same quarter, yielding one row per distinct QUARTER_NUM and ORG_ID combination, ordered by QUARTER_NUM.

Key Columns

  • QUARTER_NUM — The GL quarter number derived from GL_PERIODS.QUARTER_NUM. This is the primary value presented by the view and represents the quarter of the accounting calendar in which a period falls.
  • ORG_ID — The operating unit identifier sourced from PA_IMPLEMENTATIONS.ORG_ID, indicating the organization context against which the quarter numbers are valid.

The combination of ORG_ID and QUARTER_NUM reflects the set of books assigned to each operating unit through the Projects implementation, ensuring that returned quarters correspond to the correct accounting calendar.

Common Use Cases and Queries

The view is typically used as a reference set for quarter-based Projects reporting, for validating available quarter values in a given operating unit, and for driving list-of-values or parameter queries in custom reports and concurrent programs.

A simple query returning all quarters for all operating units:

  • SELECT QUARTER_NUM, ORG_ID FROM APPS.PA_REP_QUARTER_GL_V ORDER BY ORG_ID, QUARTER_NUM;

Filtering to a specific operating unit:

  • SELECT QUARTER_NUM FROM APPS.PA_REP_QUARTER_GL_V WHERE ORG_ID = :p_org_id ORDER BY QUARTER_NUM;

Using the view to constrain a Projects fact query to a chosen quarter, the developer joins the fact table to GL period/quarter information and applies the QUARTER_NUM selection obtained from this view. Because the object is a view and read-only, it should be queried rather than updated. As with all APPS-owned reporting views, access should be granted through the standard APPS synonym and responsibility-based security rather than direct grants to base tables.