Search Results pmi_gl_time_v




Overview
Explore in AI Chat

Overview

PMI_GL_TIME_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Process Manufacturing Intelligence (PMI) product family. Within the 12.1.1 and 12.2.2 releases, PMI is classified as obsolete, meaning that the view is retained for backward compatibility but is no longer the target of active development. Its purpose is to expose General Ledger calendar data at three simultaneous levels of granularity — period, quarter, and year — in a single denormalized row, thereby allowing downstream reports, dashboards, and integrations to resolve time hierarchies without performing self-joins against GL_PERIODS.

The view is particularly relevant to users searching for quarter_start_date style attributes. Because PMI analytics frequently aggregate transactional balances by fiscal quarter, the view pre-computes the quarter boundaries and surfaces them as first-class columns, removing the need for consumers to derive quarter start and end dates from period-level records.

Underlying Base Objects

The view text references two documented base objects: GL_PERIODS, exposed through a synonym, and GL_SETS_OF_BOOKS, itself a view. GL_PERIODS is joined to itself three times within the view definition, once aliased as PRD (the accounting period), once as QTR (the quarter-level row), and once as YR (the year-level row). These aliases are correlated on PERIOD_SET_NAME and PERIOD_YEAR, with PRD.QUARTER_NUM matching QTR.PERIOD_NUM and row type filters restricting QTR to PERIOD_TYPE = 'QUARTER' and YR to PERIOD_TYPE = 'YEAR'. GL_SETS_OF_BOOKS supplies the set of books name and links to the period set while constraining the accounted period type to the period row. Adjustment periods are explicitly excluded at all three levels via the ADJUSTMENT_PERIOD_FLAG <> 'Y' predicate.

Key Columns

Common Use Cases and Queries

The view is typically used to label fact tables with quarter attributes. A report requiring the quarter start date for a given ledger and period can select directly:

  • SELECT set_of_books_name, period_name, quarter_start_date, quarter_end_date FROM apps.pmi_gl_time_v WHERE period_set_name = :p_set AND period_year = :p_year;
  • SELECT quarter_name, MIN(quarter_start_date) FROM apps.pmi_gl_time_v GROUP BY quarter_name ORDER BY 2;

Because PMI is obsolete, new development should prefer current GL calendar views; however, existing Process Manufacturing Intelligence reports and any custom SQL referencing quarter_start_date remain dependent on this view, and its validity in 12.1.1 and 12.2.2 ensures continued execution.