Results for “pa_exp_type_gl_view”

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

Overview

PA_EXP_TYPE_GL_VIEW is a reporting view within the Oracle Projects (PA) module that aggregates actual cost and revenue totals for projects and tasks, organized by General Ledger period and expenditure type. According to the ETRM documentation, this view is designated "R10SC Only," indicating it was created specifically to support the Release 10 Projects reporting requirements and is not implemented in all databases. Its primary role is to provide a consolidated, period-based snapshot of project financial performance, enabling both standard Oracle Projects reporting and custom integrations to retrieve summarized cost, revenue, quantity, and labor hour data without querying the more granular underlying accumulation tables directly.

Because the view groups data by GL_PERIOD, GL_START_DATE, and GL_END_DATE, it is particularly well suited to period-over-period analysis and to reconciliation between Projects subledger figures and General Ledger balances. Users searching for "gl_period" in the context of Projects reporting will find this view relevant because GL_PERIOD is one of its core grouping keys.

Underlying Base Objects

The documented view text defines PA_EXP_TYPE_GL_VIEW as a SELECT over a single underlying object, PA_ACCUM_VIEW. The view applies GROUP BY on PROJECT_ID, TASK_ID, GL_PERIOD, GL_START_DATE, GL_END_DATE, EXPENDITURE_TYPE, and EXPENDITURE_CATEGORY, and applies ROUND to each aggregated amount and quantity measure. The ETRM metadata lists no additional referenced base objects, so PA_ACCUM_VIEW is the sole documented source. PA_ACCUM_VIEW itself typically resolves against Projects accumulation tables such as PA_ACCUM_ACTUALS, which store summarized actual cost and revenue data at the lowest reporting grain before further aggregation. The view therefore serves as a period-level rollup layer above the accumulation view.

Key Columns

• PROJECT_ID / TASK_ID — Identifiers for the project and task to which the aggregated amounts belong.
• GL_PERIOD — The General Ledger period name used as the primary time-based grouping dimension.
• GL_START_DATE / GL_END_DATE — The start and end dates of the GL period, useful for date-range filtering and reporting.
• EXPENDITURE_TYPE / EXPENDITURE_CATEGORY — Classification of the cost or revenue, distinguishing expenditure types and their parent categories.
• TOTAL_REVENUE, TOTAL_RAW_COST, TOTAL_BURDEN_COST — Aggregated revenue and the raw and burdened cost components.
• TOTAL_QUANTITY, TOTAL_LABOR_HOURS — Aggregated entered quantities and labor hours.
• BILLABLE_RAW_COST, BILLABLE_BURDEN_COST, BILLABLE_QUANTITY, BILLABLE_LABOR_HOURS — The billable portions of cost, quantity, and labor hours.
• BUDGETED_COST, BUDGETED_REVENUE, BUDGETED_LABOR_HOURS — Budgeted comparison figures for cost, revenue, and labor hours.

Common Use Cases and Queries

Typical usage includes period-based cost and revenue reporting, expenditure type analysis, and comparison of actuals against budgets by GL period. A representative query filtering on a specific period is shown below.

SELECT project_id,
       task_id,
       gl_period,
       expenditure_type,
       total_raw_cost,
       total_burden_cost,
       total_revenue,
       billable_burden_cost,
       budgeted_cost
FROM   pa_exp_type_gl_view
WHERE  gl_period = :gl_period
ORDER BY project_id, task_id, expenditure_type;

A second common pattern aggregates across expenditure categories to summarize cost and revenue by GL period:

SELECT gl_period,
       SUM(total_burden_cost)  AS burden_cost,
       SUM(total_revenue)      AS revenue,
       SUM(total_labor_hours)  AS labor_hours
FROM   pa_exp_type_gl_view
WHERE  gl_period BETWEEN :from_period AND :to_period
GROUP BY gl_period
ORDER BY gl_period;

Because the ETRM indicates the view is "Not implemented in this database" and labeled R10SC Only, availability should be verified against the specific release and configuration before use in custom code or reports.