Results for “pa_gl_view”

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

Overview

PA_GL_VIEW is a reporting view in the Oracle Projects (PA) module that consolidates actual cost and revenue totals at the project and task level, aggregated by General Ledger period. Its stated purpose is to provide period-by-period summaries of expenditures, revenue, quantities, labor hours, and budgeted amounts, allowing project accountants and reporting analysts to reconcile project performance against the GL calendar without writing their own aggregation logic against the underlying accumulation tables.

The ETRM metadata explicitly flags this object as "R10SC Only," meaning it is a legacy construct retained from an earlier release rather than a supported artifact in current 12.1.1 or 12.2.2 implementations. The metadata records that the view is "Not implemented in this database," and no owner or referenced base objects are documented for the 12.2.2 file. In practice, this means PA_GL_VIEW should be treated as a historical reference object: it may appear in older customizations, migration scripts, or deprecated reports, but it is not available for querying in a standard current installation.

Underlying Base Objects

The view text documents a single documented source: PA_ACCUM_VIEW. PA_GL_VIEW selects from PA_ACCUM_VIEW and applies a GROUP BY over PROJECT_ID, TASK_ID, GL_PERIOD, GL_START_DATE, and GL_END_DATE, wrapping every measure in SUM() and ROUND(). PA_ACCUM_VIEW is the Projects module's accumulation view that joins and summarizes the project transaction and cost distribution tables into period-level buckets, so PA_GL_VIEW is effectively a thin grouping layer on top of it rather than a view over physical base tables directly.

Because the ETRM metadata documents no referenced base objects and no owner for 12.2.2, the exact dependency chain cannot be confirmed from this source alone. Analysts encountering legacy references to PA_GL_VIEW in current environments should verify object existence in ALL_VIEWS and inspect ALL_DEPENDENCIES before attempting to reconstruct equivalent logic from PA_ACCUM_VIEW or the current period-summary views shipped with 12.1.1 / 12.2.2.

Key Columns

• PROJECT_ID / TASK_ID — Composite key identifying the project and task to which each aggregated row belongs.
• GL_PERIOD — The GL period name used for bucketing, together with GL_START_DATE and GL_END_DATE defining the period boundaries.
• TOTAL_REVENUE — Summed actual revenue for the project/task in the period. This is the column most frequently associated with the "total_revenue" search term.
• TOTAL_RAW_COST / TOTAL_BURDEN_COST — Actual raw and burdened cost totals.
• TOTAL_QUANTITY / TOTAL_LABOR_HOURS — Aggregate quantities and labor hours recorded.
• BILLABLE_RAW_COST / BILLABLE_BURDEN_COST / BILLABLE_QUANTITY / BILLABLE_LABOR_HOURS — The billable portions of cost, quantity, and hours.
• BUDGETED_COST / BUDGETED_REVENUE / BUDGETED_LABOR_HOURS — Budget-side comparators used for period variance analysis.

Common Use Cases and Queries

The primary historical use case is period-level revenue and cost reporting for a project or task, particularly where a GL-period-bucketed total revenue figure is required. A representative query would resemble the following, filtering by project and period range:

• SELECT project_id, task_id, gl_period, total_revenue, total_burden_cost FROM pa_gl_view WHERE project_id = :p_project_id AND gl_period BETWEEN :p_from AND :p_to ORDER BY gl_period;
• Revenue-to-budget comparison using TOTAL_REVENUE against BUDGETED_REVENUE per GL period.
• Billable versus total cost analysis using the BILLABLE_* columns relative to TOTAL_* columns.
• Labor-hour utilization reporting across periods using TOTAL_LABOR_HOURS and BILLABLE_LABOR_HOURS.

Given the "Not implemented" designation, any query against PA_GL_VIEW in a current 12.1.1 or 12.2.2 instance will fail unless a custom object of the same name has been created locally. The recommended approach is to reproduce the documented aggregation against PA_ACCUM_VIEW or the supported period-summary views, preserving the same GROUP BY and ROUND semantics shown in the view text.